Hey errbody, sorry if this has been asked somewhere already but it's hard to sift through the hundreds of pages of good questions! But I seem to have a slightly handicapped TWRP thing going on in that it successfully makes backups but upon restoring then when needed, it says failed and then factory resets my phone when I boot into system...Anybody getting this weird vibe?
I've never experienced that before. Are you using the correct TWRP for your phone? Have you tried CWM recovery? Use flashify and flash an older version of TWRP... you should not be having this issue.
I'm unable to restore from Nandroid backups either. No idea how to remedy the problem. This is the 5th phone I've successfully rooted and put a recovery on so I'm not a noob, just can't figure this one out. Have you found a solution yet?
Sent from my LG-D801 using xda app-developers app
andy10259 said:
I've never experienced that before. Are you using the correct TWRP for your phone? Have you tried CWM recovery? Use flashify and flash an older version of TWRP... you should not be having this issue.
Click to expand...
Click to collapse
Hey I've used flashify to flash the newest version of twrp, never tried cwm on the g2 saw twrp was the more reccomebd recov. No idea why its going down like this. I'm running pa 4 so don't I need to keep my new version of twrp?
Related
So ive been having this issue and it started all after i tried to flash the ubuntu zips that were supposed to work with a custom recovery. I flashed correctly as everyone said to do so, and my recovery would restart during flashing of the armhf.zip(the larger zip). The armhf.zip would get around 2/3 done and then just restart the recovery but now i am having the problem that i cannot recover from any of my recoveries without my recovery restarting. TWRP will recover the system and then while it is recovering the /data partition it restarts back into the recovery, but does not finish the restore. I am running the latest twrp 2.4.1.0. Please let me know if anyone knows how to fix this issue, or if you have experienced this.
Thanks in advance,
I am wondering if i am going to have to flash factory firmware and rom from google and unroot, and then reroot and what not. Just let me know if any of this would help.
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
melvis02 said:
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am able to flash ROMs fine, its just restoring from nandroid that messes it up, did you do the kernel cleaner and superwipe or just the super wipe zip?
Edit: nevermind I just flashed super wipe, and everything is all good now, I can fully restore. Thanks for the help, I appreciate it.
Sent from my Nexus 10 using xda app-developers app
Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.
I've had TWRP 2.6.0.0 lock up on me a few times in the past two days. Now that I'm trying on a few mods, It takes maybe 5 tries to get recovery to start. Using GooManager never works. That route just hangs on the splash page.
Should I consider a different version of TWRP, or just go with CWM? Whichever I choose, is there a file I can simply flash in recovery (assuming I can get into recovery just...one...more...time...please, oh, please)?
I am on US i337UCUAMDL, stock rooted ROM, AT&T if that matters.
There's a twrp 2.5.0.2 and a 2.6.3.0 flashable zip under my Sig in the general forum.
jd1639 said:
There's a twrp 2.5.0.2 and a 2.6.3.0 flashable zip under my Sig in the general forum.
Click to expand...
Click to collapse
I need that link...I flashed Jeboo's CWM and did a backup. On the next boot, I got stuck in a boot loop. I know I have a TWRP backup of a good state, but can't restore that without a TWRP recovery. Can you give me the link so I can get this going again?
duckredbeard said:
I need that link...I flashed Jeboo's CWM and did a backup. On the next boot, I got stuck in a boot loop. I know I have a TWRP backup of a good state, but can't restore that without a TWRP recovery. Can you give me the link so I can get this going again?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=45656348
http://forum.xda-developers.com/showthread.php?p=45511518
Sent from my SGH-I727 using xda app-developers app
Thanks for the links.
I flashed 2.5.0.2 and tried to restore a backup that was made when I was on 2.6.0.0. I got a "Restore Failed" just after the data. I am wondering if it is because I went backwards in TWRP versions. I may have to flash a newer TWRP, I guess.
duckredbeard said:
Thanks for the links.
I flashed 2.5.0.2 and tried to restore a backup that was made when I was on 2.6.0.0. I got a "Restore Failed" just after the data. I am wondering if it is because I went backwards in TWRP versions. I may have to flash a newer TWRP, I guess.
Click to expand...
Click to collapse
I had the same problem, you could keep trying to get this to work, or quit wasting time, and just odin back to stock, root, then install a recovery other than the newer twrp releases, they have issues, I was thru with all this in 1 hour, or keep getting bad flash messages....that is the easiest and quickest method.
And after you get that fixed, come take a look at Vision X, nice rom.
I have tinkered with your ROM. I did install it and make a few mods. Had issues with what kernel to pick, resolved apn issues. Was impressed enough to make a backup of it for later. I'm saying goodbye to my stock ROM, backing up data and configs for whatever ROM I go with. Yours is on the top of the list, but the kernel question lingers.
As for kernels, I want what will work on AT&T without having to jump through hoops.
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
Which twrp recovery you using?
Sent from my SPH-L720 using xda app-developers app
openrecovery-twrp-2.6.0.0-jfltespr
excessive81 said:
openrecovery-twrp-2.6.0.0-jfltespr
Click to expand...
Click to collapse
Twrp version 2.6.0.0 seems to be buggy either try 2.5.0.2 or 2.6.0.3 they seem to be working for people the most
Sent from my SPH-L720 using xda app-developers app
excessive81 said:
not sure what is going on but i have twrp recovery and running the triforce rom at the moment. though every rom has done same thing that i have tried. i swap batteries alot rather then charge the phone so this is a pain since the only fix i have found is reboot to recovery which also sometimes freezes on the twrp logo and do complete wipe. then it will boot up fine. but of course everything is gone.
Click to expand...
Click to collapse
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.
smizak said:
This has been a problem for me as well. I've used TWRP 2.5.0.2 and the 2.6.x.x versions with the same issue. Typically only happens after flashing an AOSP based ROM then restoring a TW nandroid. For me, one of the partitions gets corrupted, I've had /data and /system both get borked. Formatting in TWRP and CWM does nothing to fix the problem. My only solution so far has been to ODIN crawjs rooted stock MF9 .tar and factory reset in stock recovery. This seems to restore the partition. After that, reboot into download again and flash TWRP 2.5.0.2 .tar. Only then can I successfully restore a previous Nandroid.
It's weird, the first boot always works. Haven't heard a definitive answer to why this happens. I may experiment flashing an AOSP with CWM and see if the same issue persists.
Click to expand...
Click to collapse
the 2.6.3 worked thanks
excessive81 said:
the 2.6.3 worked thanks
Click to expand...
Click to collapse
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app
ParkerParker said:
That one still gets stuck on team win curtain,,, This one has been the best yet and I've flashed a ton with it :beer::thumbup:
http://www.androidfilehost.com/?fid=23159073880933366
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.
excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore but now after rebooting sd card no seen/working. it is there you can see it in settings menu which says it is mounted but the apps i moved to it dont work and the music is gone. if i unmount the card i can not remount it.
Click to expand...
Click to collapse
stock recovery, factory reset. trust me.
excessive81 said:
that file for 2.6.3.1 is not a tar file how do you flash it?
also i dont have freezing issues anymore
Just give it some time you will have curtain hangs... If you flash a lot.. But onto the zip, just flash in recovery, done
Heres the twrp thread if you feel like a read, http://forum.xda-developers.com/showthread.php?t=2262999
Click to expand...
Click to collapse
I was running (and am after the restore) Android 4.3.1 slimBean jflteatt build.2official.
So my friend convinced me to try CM12 lolipop nightly.
I made a backup wiped everything and installed CM12 and the gapps.
upon boot after the instalation all the play services were crashing so we reinstalled CM 12 but without GAPPS and all was fine.
BUT now i CAN"T reboot my phone. Regardless of ROM (except stock) the att galaxy s4 gets stuck on the boot splash screen (the screen before the boot screen) The screen it gets stuck on looks like this: http://img18.imageshack.us/img18/8910/20120813002112.jpg
The screen used to look like this: http://2.bp.blogspot.com/-aCD7kATq-to/UaIBfYW5oKI/AAAAAAAAO88/ShlHR6459kk/s1600/boots4.gif
I have tried restoring and installing a clean ROM but that did not solve my problem. Only way for me to restore is to wipe everything, then format the data and the restore. I restored to stock TW MDL via a TWRP backup i have.
I am running TWRP 2.5.0.1 (I think). I am currently using the SlimRoms 3.4.0 kernal. I am rooted according to root checker.
Can someone please help me solve the reboot problem? (Could it have anything to do with Xposed?)
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I would update twrp and try again. You have an old version.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
sharpknight said:
i have 2.5.0.2, what do you suggest i update to ? (and how?)
I've been afraid to update anything because if it aint broke don't fix it.
Do you suggest TWRP 2.8.0.1 touch recovery [2014-09-12]
as this suggests?: http://forum.xda-developers.com/showthread.php?t=2413746
thank you for your reply.
Click to expand...
Click to collapse
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Flashing roms in an old version of twrp won't work. If your rooted, which I assume you are, get flashify forum the play store. Then download the latest twrp.img and flash it in flashify. http://dl.twrp.me/jflteatt/ The link is for the at&t s4, if you have a different variant you'll need a different image.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
sharpknight said:
ok i have succesfully updated to TWRP 2.8.4.0 (newest on the link you provided) via flashify as you suggested.
What do i do now? BTW really appreciate the help.
Click to expand...
Click to collapse
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
If you want cm12 download the zip and gapps and flash those in twrp. Do the default wipe in twrp first. Note, it will wipe your apps but if you have had Google backup your device it will restore them.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I don't wan't CM12 at this moment. I just need to have old SlimRom working without the reboot issue. too much business related data there at the moment. So should i reinstall slimRom and the restore that data maybe?
Could it be the slimKernal? Ive had the problem where it gets stuck at that screen for a long time now but id just do a batery pull and turn it on and it would work after 2-3 tries.