Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Try the cache clean up after the nandroid is restored.
Also try to install some other compatible kernel (if it's stock it should be also to find on the forums) after the restore with its modules if the cache clean up doesn't help.
Sent from my HTC One X using Tapatalk 2
Wipe the cache and dalvik cache again.
shadehh said:
Hey guys, this post is not for me but for a friend.
As the title already mentions, he's trying to get to stock
so the step he follows are:
Move boot.img from his stock rom nandroid backup to his fastboot folder
so lets begin
first step-> boot into bootloader
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
--> boot into recovery
wipe data/factory reset
wipe cache
wipe delvik cache
-> back up and restore
--> restore
--- nandroid backup gets installed ---
... so far i can't see where he is doing anything wrong
so he proceeds to reboot his phone.. and now i asked him multiple times about the taken procedure and he claims his phone boots normally to the point where the wallpaper shows up and then he talks about the phone falling into a constant bootloop
What went wrong? Why is he experiencing this?
I've taken into consideration that he might be doing something wrong, but then i even wrote the steps above and he says he did it exactly that way.
i'm clueless to say the least and i hope someone here could help me help him
thank you
Click to expand...
Click to collapse
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Thanks for the help guys. I mentioned all the suggestions on this thread to him and it he was able to get it running
Sent from my HTC One X using xda app-developers app
bradmax57 said:
I restored my original 4.0.3 nandroid backup yesterday and got exactly the same problem coming from arhd 9.7.2 4.0.4. I want to get back to stock so I can get JB ota when its available. Mine also loaded the wallpaper and then rebooted. All I did to fix it was copy the boot.img from my nandroid backup and reflash that after I had restored again.
So the way I did it was
Boot into recovery
Full wipe
Restored rom
booted into bootloader
flash boot.img (from original nandroid)
rebooted and worked a treat
Click to expand...
Click to collapse
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
squirrelbo1 said:
OK I had the same issue and followed these steps, however when I try to flash boot.img I get an error in command prompt saying it cannot load boot.img (even though the file is copied to root of the 'sd card')
any idea what I'm doing wrong
Click to expand...
Click to collapse
The file shouldn't be on the phone, but on the PC.
Place it in the folder in which you have your fastboot files.
oh of course. I'm being a moron again.
I cant believe I did that. so very very simple. sorry for being a numpty guys. wasn't thinking strait. Done a few custom rom installs but never flashed a backup. Didnt even think. You even have to type the directory into command prompt.sorry guys I can't believe I didn't think that. (was thinking along the lines of installing from zip way)
to be fair the only reason I'm doing all this is because my screen is playing up and I need to return it so getting everything as close to stock as possible so got other things on my mind
everything is working now. Thanks guys. My god stock rom on HTC one x from orange is ugly.
No worries mate. You're not a moron, just a beginner.
TToivanen said:
No worries mate. You're not a moron, just a beginner.
Click to expand...
Click to collapse
thanks heaps for the thread guys, this has been a great help as I'm doing a similar thing and had the same problem.
Related
Hello,
My Galaxy Nexus went in to a boot loop for some reason on it's own, it's been working fine for the last few months (I'm on AOKP b24) but today during the middle of the day it just rebooted and then went in to a boot loop. No matter what I do, I can't get it to boot up without hard wiping it. I've pulled the battery for a while, charged it up etc but it's still stuck in the boot loop.
I can still get in to CWM, so that's the good news.
The BAD NEWS is that I don't know how pull my Titianium Backup files from the phone. I'm trying to use the Galaxy Nexus Toolkit, but when I go to option 15 to pull the files, it asks me if I'm running a custom ROM. I answer yes and then it asks me for a path. I've tried entering these: /sdcard, /sdcard/, /mnt/sdcard/titaniumbackup, /mnt/sdcard/titaniumbackup/ etc. but no matter what I enter, it gives me an error saying I'm not running an insecure boot image.
How can I pull down my nandroid backups from the phone so that I can wipe it and then get my data back? Please help..
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
neotekz said:
have you tried clearing the cache partition and delvik cache? lots of bootloops can be fixed by just doing this.
if you have a nandroid backup theres no need to wipe anything before doing the restore.
Click to expand...
Click to collapse
Yep, tried wiping cache and dalvik a few times, no dice. I also tried a nandroid restore from CWM but it errors out and doesn't restore..
CMNein said:
Nandroid's won't restore? The correct path is: /sdcard/TitaniumBackup/ but if the toolkit is giving you no love I'd try it via adb.
adb pull /sdcard/TitaniumBackup/
For nandroids: adb pull /sdcard/clockworkmod/backup/
BUT
If you do a wipe data/factory reset your backup folders aren't lost, so a completely fresh ROM install won't affect your existing b/u's as long as you don't format your sd card.
Click to expand...
Click to collapse
Thank you. I managed to get the files pulled, just had to manually kill adb and restart it and then I could pull the files.
Now I have also done a factory reset through CWM and the flashed the same ROM again, it's still in a boot loop!!
I'm at a complete loss.. what else can I try?
Could a part of the internal memory be corrupted or something like that?
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
neotekz said:
was the phone a yakju build? if so you can use fastboot or the toolkit to flash them, this will flash the stock bootloader, recovery, kernel and system image.
https://developers.google.com/android/nexus/images#yakju
Click to expand...
Click to collapse
Thanks, that's exactly what I just did and it worked. No more bootloop! Phone booted up and I'm now in process of flashing my old rom and then hopefully restoring the nandroid.
I have no idea what caused all this after months of stable operation, but at least the phone is alive now..
Thanks all!
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
lKoRTy said:
Is there a way to pull files/photos from a boot looping phone that's unrooted? :-/
Click to expand...
Click to collapse
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
the7thson said:
Install the Galaxy nexus Toolkit (search for this on xda), then get it connected to your phone by following instructions in the tool.
Then select the option to pull files and give it the right path, which should be \sdcard\DCIM\Camera\.
This will pull the files to your computer where the Toolkit is installed.
Hope this helps!
Click to expand...
Click to collapse
For some reason while reading about toolkit last night I gathered that it wouldn't work.. Perhaps I was wrong so this morning went ahead and did a reset to factory :-/
Thanks for the suggestions - I will definitely look into it if it occurs again. If it does, I will be posting a video on YouTube of burning it down
So I decided to root my phone and upgrade to JB. But after I unlocked the bootloader, rooted the phone, flashed CWM Recovery and downloaded "Vicious JellyBean V2- No SU Zip necessary- Francos kernel and WiFi fix Zip" then went in to fastboot mode and installed it, my phone is hanging up on the new multicolored x splash screen and will not load. I waited 30 mins, I bricked it. So I went back into fastboot mode and reinstalled the JB, but still same thing.
So I am without a phone because I dont know what to do. :crying:
Any help is greatly appreciated!!!!! TIA
what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again
Get this set up.
I don't feel like debugging for two hours via text and reply.
I'll recover as much as I can.
Edit:
http://www.teamviewer.com/en/index.aspx?utm_expid=60202728-6
Lol, meant to paste that link.
Once that's installed I'll remote connect to your PC and try to fix this.
NeoMagus said:
what do you mean by fastboot mode. You should have been flashing it through clockwork. Did you wipe your data, cache and Dalvik cache before hand? Or make a nandroid backup before installing Liquid?
If not sounds as if you are going to need the toolkit or push the stock files via adb to flash back to stock then start again
Click to expand...
Click to collapse
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?
skinnytoo2 said:
I wiped with toolkit didnt cache or Dalvik cache. I have a replacement device coming today and want to try again. Is there a link to somewhere with step by step directions. I would assume the replacement device has factory settings so do I have to wipe, etc?
Click to expand...
Click to collapse
Manual Method
Toolkit Method
Just download a JB rom from the Development forum after you've unlocked bootloader, flashed a custom recovery, and have rooted your phone. Most are bug and glitch free...
I reflashed JB and it worked!!! Thanks guys!! Love JB
skinnytoo2 said:
I reflashed JB and it worked!!! Thanks guys!! Love JB
Click to expand...
Click to collapse
grats. next time, please dont incorrectly use the term 'brick'
brick = unable to turn on. no bootloader mode [fastboot], no recovery, no download.
as said above this fixes the non delete issue
as sooon as i flased with adb it booted =into cwm so i thought i would nandroid backup my rom which i did then i touched the restart system i then get a message saying (rom may flash stock recovery on boot fix ? ) i pressed yes=disable recovery flash then rebooted then deleted my nandroid to check the delete worked.
i then rebooted into bootloader and tried to get into cwm no joy but it worked with the cable plugged in
i then made another nandroid and got the same message again after touching reboot (rom may flash stock recovery on boot fix ? ) yes= disable recovery flash
is yes the right answer?
Click to expand...
Click to collapse
I saw this in one of the forums, but couldn't ask my doubt there coz i'm a newbie. I have unlocked rooted and installed JB. Went to recovery mode and cleared dalvik cache and after that before exiting i got the prompt "rom may flash stock recovery on boot fix ?" as above.
My question is : should i select yes or no? and what happens when i select both yes and no does actually? . plz explain for both options..
and also, as i am unlocked and rooted, what all should i do once in a while with CWM? like clearing caches?? and if there is anything else..
You need only wipe data or cache when flashing a rom, or if you're device is giving you issues (force closes, etc.)
Randomly wiping the cache or dalvik-cache will not merit any performance enhancements.
Sent from my Galaxy Nexus using Tapatalk 2
If you are unable to find anything by searching please post your questions in the Q&A section.
Thread moved.
Srivatsa said:
I saw this in one of the forums, but couldn't ask my doubt there coz i'm a newbie. I have unlocked rooted and installed JB. Went to recovery mode and cleared dalvik cache and after that before exiting i got the prompt "rom may flash stock recovery on boot fix ?" as above.
My question is : should i select yes or no? and what happens when i select both yes and no does actually? . plz explain for both options..
Click to expand...
Click to collapse
Stock JB roms as a default will flash a "stock recovery" so yes is a good answer though only necessary if you are flashing a "stock" ROM which would be somewhat unlikely. That said I generally choose yes just to be certain though I have chosen no with no ill effect.
Hope to have helped
Hey guys,
Got a very weird problem here. I have previously flashed a CM10 nightly to my One X (international) and everything has been fine for around 3 weeks. Decided i wanted to try our the ViperX ROM. Previously upon flashing this ROM it just bootlooped but after another try with a slightly different method, i managed to get it to boot and all was merry. After titanium restore i rebooted, and this once again put me into a bootloop. Cannot get the ROM to boot. Why is this!!! Switched back to CM10. :good:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
BenPope said:
You need to do
fastboot flash boot boot.img
You may have done
fastboot boot boot.img
Click to expand...
Click to collapse
Still doesnt boot man, im sure i flashed the boot image properly. This is the rundown of my flash process:
1: install from sd
2: in recovery, factory reset, wipe cache, wipe dalvic cache
3: Boot into fastboot and flash the boot.img
4: Reboot.
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
I also tried "fastboot erase cache" to no avail
In fastboot type fastboot erase cache
Jamekerr said:
So it booted but into viper X, but after restoring with Titanium i was unable to get it to boot again.
Click to expand...
Click to collapse
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
eyosen said:
With tb, make sure you restore user apps only, none of the system apps.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
Sorry forgot to mention I also used the "fast book erase cache" command.
As for titanium I restored all user apps and data and now that you mention it that could be the problem. I'll have another crack tomorrow and let you know.
Main reason I want to switch is I need much better battery life than CM10 but only temporarily. Can anyone recommend viperx as being a significant improvement?
BenPope said:
Did you restore system apps or data?
Where does it stop booting, what is on the screen?
Click to expand...
Click to collapse
It comes up with "HTC" vibrates then the viper crawls across the screen and it stops at the "htcONE" logo.
Restored apps and app data and guess what. Still doesn't boot. WHY! Going to just try apps, no data at ALL. Will report back.
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
same issue
Hi i am also getting the same problem, i used the viper rom and others but it goes past the HTC logo looks as though it works but the lock ring is froze up and then it reboots itself over and over doing the same thing each time. Ive tried One_X_All-In-One_Kit_v1.2 and the manual CMD fastboot tutorial i dont know what to do to fix this, can anyone help me please?
EDIT* I seem to have it working now (fingers crossed), i used 'Nocturnal_Special_Edition_4.0_Odex' so thx to their good work that i now have a working rom for my phone phew
EDIT 20 MIN LAter* OK looks like i did something i shouldnt, it seemed to work, i made a change in the settings and then it rebooted and continued to reboot over and over so i tried installing a rom again and now it just stays at the htc quietly brilliant screen, what have i done this phone is now not so brilliant as its looking more and more that ive goosed it Any help apreciated.
boot.img
Help please
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
BenPope said:
I dunno why it won't start, double check you have the right boot.img (download it again and flash it again), in recovery erase cache and dalvik cache.
Click to expand...
Click to collapse
If I restore apps only it does boot however any sort of data and it refuses to. Very annoying as I am not able to retain texts accounts etc. I have a feeling it's because I originally backed up on a jellybean ROM and the data just doesn't want to work on ics
Squbbe said:
Hello,
I have 1x (CID 203) unlocked and rooted with cwm recovery. I had Cyanogenmod 10 nighly on it, well in hope of no bugs like in CM10 I flashed this http://forum.xda-developers.com/showthread.php?t=1763240 to it. Well it seemed to work a moment but then the device started rebooting randomly. I couldn't boot to recovery (strange?), the recovery screen flashed less than a second and the phone started to boot normally again. After a few tries (and reflashing recovery) I luckily got into the recovery. Tried to restore a nandroid backup which I made earlier yesterday. CWM said that the restore was successful but the device didnt boot anymore. Only shows htc logo and cyanogenmod loading screen. But nothing happens. Well, then I flashed Android Revolution HD 10.3. (with wiping the system data and so on) but it wont load any longer than the htc one logo screen. Rom installed fine and I flashed the boot.img.
Now I'm able to get into recovery and fastboot and charge my phone but how could I safely and surely return my phone to stock or make the ARHD work without completely bricking it? I'm thinking that relocking my device is not very safe if the RUU fails to install. What do you think? Can the firmware updates cause this problem to happen? Can I flash ARHD 9.7.2 to my device? Too bad I can't ask these questions in the ARHD thread....
In bootloader my phone says
Code:
hboot-0.94.0000
radio 1.1204.104.14
Any advice is highly appreciated, I'm not ready to bury my phone yet
Edit. ARHD 9.7.2 flashed correctly. Any ideas why the ARHD 10.3 keeps bootlooping? Yes, I have flashed the correct boot.imgs.
Click to expand...
Click to collapse
Try the fast boot erase cache command and see if that solves the boot issue. If not make sure in recovery your have cleared cache partition performed a factory reset and also cleared the dalvik cache. Again if none of these work try re flashing the boot.img or perhaps try another rom that is known to be stable.
Every time I take a nandroid backup in TWRP and boot the phone up, I seem to get boot loops.
Yesterday
------------------
I was running HTC's factory 4.4.2 firmware that came with my phone when I bought it. It was rooted and I was using XPosed. I wanted to upgrade to 4.4.3 via OTA, but I wanted a roll-back method. So I took a nandroid, all is well.
I flash stock recovery and take the OTA. All is well. I re-root, install xposed, tinker with some modules and then the phone reboots itself.
I did the upgrade from 4.4.2 to 4.4.3 again after restoring my nandroid backup. All is well. I decide not to tamper with root stuff, but the su binary has been flashed. I restored a majority of my apps and app data by using titanium backup to load application data from my TWRP backup. Everything is STILL fine.
Today
------------------
My TWRP backup of 4.4.2 was at work so I had to wait until I got back to move the backup back onto my phone. So here I am. I decide to do the following:
1. I shut my perfectly working 4.4.3 ROM down so I can take a nandroid before I load the 4.4.2 nandroid and try another fresh update
2. I make the nandroid backup and boot the OS back up so I can copy the TWRP folder over to my computer
3. Phone boot loops again.
What is causing this? I've tried a bunch of things like fixing permissions from TWRP, clearing the dalvik and cache. I tried sending "adb logcat" to a file on my computer to examine the output but nothing sticks out before it reboots.
Only fix I know is to factory reset and start the long process all over again.
M8_UL
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
Carrier: Wind Mobile (Canada)
Have you tried fastboot erase cache, and flash TWRP again?
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
What does fastboot erase cache do? Is it the same cache I can clear from TWRP?
One thing I just remembered... I'm using TWRP 2.7.1.0, where prior to upgrading I was using TWRP 2.7.0.2 from Hasoon2000's toolkit. Not sure if this matters or not yet.
ninjai117 said:
No I have not. Once I try that, what point will I be at? Will I be able to boot into my OS or will I need to restore my backup again?
Click to expand...
Click to collapse
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
OK well I reverted back to my nandroid I created with my previous version of TWRP, and did the OTA again. Have not bothered to root or create further nandroids. So far everything is great. Just wish I could create a nandroid without the thing going crazy on me.
ninjai117 said:
Just wish I could create a nandroid without the thing going crazy on me.
Click to expand...
Click to collapse
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
redpoint73 said:
The point is to re-install TWRP. As I don't have issues with the phone rebooting after doing a nandroid, I'm just guessing that maybe its just a bad TWRP install.
For that matter, try to download the TWRP file again, to make sure the file isn't corrupt.
You won't be able to boot into the OS just from what I suggested, you will still need to restore the nandroid.
erase cache is suggested as sometimes folks have trouble re-installing TWRP, and erase cache will often solve this. I always install TWRP by fastboot, so fastboot erase cache just takes 2 more seconds, which is time well spent to reduce headaches.
Click to expand...
Click to collapse
redpoint73 said:
I haven't had this happen to me. Only issue with TWRP for me so far on this device, is a backup failed to restore on an earlier TWRP version (so I had to flash a ROM and setup again) and I haven't had this issue on more recent TWRP versions.
Again, I'd suggest downloading TWRP again, and doing a fresh install of it and see if the problem persists. Or try CWM.
Click to expand...
Click to collapse
I instead flashed TWRP from Hasoon2000's HTC M8 All In One Kit, which is what I previously had and created my 4.4.2 nandroid with. Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again. I'm currently on 4.4.3 with SuperSU.zip flashed. No problems yet.
ninjai117 said:
Every time after that I was using the latest version from TWRP's website. I suspect that is the culprit, but I have no evidence yet as I have not created a nandroid again.
Click to expand...
Click to collapse
I always get TWRP from their website.