I took my 5.1.1 VZW Note 4, and rooted it with King Root. I proceeded to follow the instructions to change my CID here. I used adb, performed the commands, and everything seemed golden. I used odin to flash TWRP, but something went wrong. I booted into the recovery, and tried to "update from external storage". I soon recieved a "dm-verity verification failed in recovery" messaged. It did not occur to me that I was still in the stock recovery; I did not bother to check it's initial look and feel, and assumed the TRWP programmers were just lazy. After reading up on this "dm-verity" error, xda posters said I should flash it with Kies. Thinking nothing wrong could happen, I gave it a shot. It updated to 6.0.1. This is where the problems start happening.
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.ta r" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.ta r" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.ta r" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
Since then, I can't reflash to 5.1.1. I've tried every version I could get my hands on, including the 5.1.1/6.0.1 hybrid posted here. I have 3 total verions of 5.1.1. I then tried to downgrade to 5.0.1. The first version of 5.0.1 started artifacting the screen, but booted and stopped promptly. It only artifacted the "Samsung" loading screen. I couldn't, however, root the device. Feeling desperate, I tried the only other version of 5.0.1. Success! I rooted and reran the adb commands and the script provided to change CID. This time, it skipped the first half of the script. It went directly to "backup up loader to external card". This tells me something about my CID will forever be changed, and is probably the reason my phone is boot looping. This time, I was able to flash TWRP. I installed CM 13 only to find out my sim wasn't recognized (when I used it to download King Root in 5.0.1 before). I figured it was because I was usig a 5.0.1 bootloader/modem. I tried reflashing to 5.1.1, the 5.1.1/6.0.1 hybrid, and 5.0.1 again. 5.11 boot loops and 5.0.1 hangs. Advice please... Thanks
Versions flashed:
"N910VVRU2BPA1_N910VVZW2BPA1_N910VVRU2BPA1_HOME.ta r" - 5.1.1, boot loops at Verizon screen
"N910VVRU2BPA1_N910VVRU2CPD1_FullFirmware.tar" - 5.1.1/6.0.1 hybrid, boot loops
"N910VVRU2BOG5_N910VVZW2BOG5_N910VVRU2BOG5_HOME.ta r" -5.0.1, boots but artifacts and cannot root
"N910VVRU2BOF1_N910VVZW2BOF1_N910VVRU2BOF1_HOME.ta r" - 5.0.1, booted and rooted/flashed to TWRP, caused hiccups in MM custom roms, cannot get to boot again after a reflash
"N910VVRU2BPA1_StockRestore.tar" -5.1.1 unincremented stock restore, fails on ~90% of odin flash
from xda-developers http://ift.tt/2b4IZ72
via IFTTT
Aucun commentaire:
Enregistrer un commentaire