TWRP -> Stock Recovery - AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin

What would the process be to go from TWRP recovery to the stock recovery?
There is a folder in my phone called TWRP and if I delete that would it delete the custom recovery or is the custom recovery buried deep in the system files?
Would I have to use odin to get back to the custom recovery?
Thanks!

Someone has already extracted the stock (MDL) recovery and posted it here somewhere. A quick search might find it. Are you running the stock firmware?

xBeerdroiDx said:
Someone has already extracted the stock (MDL) recovery and posted it here somewhere. A quick search might find it. Are you running the stock firmware?
Click to expand...
Click to collapse
Forgot to provide some information:
Firmware: MDL
ROM: CM10.1 RC2
I don't plan on going back to stock for a while, unless I have a problem with my device but just want to gather some information ahead of time.
Would I use the stock recovery with odin?

The twrp folder just holds the backups. The recovery is part of the whole android system. Don't go looking for recovery or twrp stuff and just deleting it or you could Bork your whole recovery. Odin would be another way to return to the stock recovery, but the rest of your phone would be stock too. Why do you want the stock recovery?

jd1639 said:
The twrp folder just holds the backups. The recovery is part of the whole android system. Don't go looking for recovery or twrp stuff and just deleting it or you could Bork your whole recovery. Odin would be another way to return to the stock recovery, but the rest of your phone would be stock too. Why do you want the stock recovery?
Click to expand...
Click to collapse
Ohh that explains a lot. I totally forgot about the TWRP NANDROID backup capability.
I don't plan to go into the android operating system and deleting random files I don't know. That's just plain out idiotic.
I don't plan on going back to stock recovery and stock firmware anytime soon. Just gathering some information ahead of time just in case.

emckai said:
Ohh that explains a lot. I totally forgot about the TWRP NANDROID backup capability.
I don't plan to go into the android operating system and deleting random files I don't know. That's just plain out idiotic.
I don't plan on going back to stock recovery and stock firmware anytime soon. Just gathering some information ahead of time just in case.
Click to expand...
Click to collapse
If you forgot about nandroid and you haven't made a backup yet and you're still on the stock rom, make one now. You'll be happy down the road you did.

jd1639 said:
If you forgot about nandroid and you haven't made a backup yet and you're still on the stock rom, make one now. You'll be happy down the road you did.
Click to expand...
Click to collapse
It's too late for that now. I'm currently on CM10.1 and didn't do a Nandroid backup. Guess I'll have to do odin in the far future.

Is Nandroid backup important if I don't flash that often?
I don't plan on flashing my device every week, maybe once every couple of months.

emckai said:
Is Nandroid backup important if I don't flash that often?
I don't plan on flashing my device every week, maybe once every couple of months.
Click to expand...
Click to collapse
Even on the odd weeks I don't flash anything, I still make a backup at least once a week. IF something goes wonky or I accidentally tweak the wrong thing, a quick restore quickly fixes it and with little to no data loss.
Sent from my GT-I9505 using XDA Premium 4 mobile app

lordcheeto03 said:
Even on the odd weeks I don't flash anything, I still make a backup at least once a week. IF something goes wonky or I accidentally tweak the wrong thing, a quick restore quickly fixes it and with little to no data loss.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Alright. I'll do a backup sometime this week. Guess better safe than sorry.

emckai said:
Alright. I'll do a backup sometime this week. Guess better safe than sorry.
Click to expand...
Click to collapse
Do a separate backup of your efs folder. so important! More important than any other backup!!!
Download your stock firmware and use kies to do emergency firmware recovery. That will return everything to stock including recovery. Make sure you reset your flash counter with triangle away before doing so.

Related

CWM recovery not working on HC 3.2.1

After the OTA 3.2.1 update, CWM Recovery would just not install. After flashing the CWM recovery image on stock 3.2.1 and rebooting into recovery, I get the android guy with the exclamation mark. I saw another person in the CWM thread having the same issue.
I did flash CWM before on HC 3.2 successfully, but for some reason it is not working after the last OTA update.
Any thoughts ?
Any luck on this? I'm trying to root my Xoom 3.2.1 and have no idea what to do and looks like the one click tool has been removed...any direction is better than no direction ;-)
Thanks!!
Faslane
I had this same issue yesterday.
Use adb and fastboot to manually install clockwork again...and then if you need to root you can use one click root.
I would give you the code for fastboot command but I'm not home.
Sent from my ADR6350 using xda premium
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
okantomi said:
Do not use one click root-you'll brick it.
Use the Univetsal Xoom Root.
http://forum.xda-developers.com/showthread.php?t=1242241
Click to expand...
Click to collapse
Thank you okantomi that's what I meant.
Sent from my ADR6350 using xda premium
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
That is exactly right.
Yazan76 said:
well, it seems that you need to immediately boot up into CWM recovery after flashing it without letting your device boot up completely, then you need to root it from there to retain the CWM recovery. This worked for me.
Click to expand...
Click to collapse
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
these instructions seem to work
http://forum.xda-developers.com/showpost.php?p=17832798&postcount=78
texasez said:
Can you expand on this a little bit? I am on stock rom, rooted and unlocked, and running 2.6.36Tiamat_Xoom kernel and build HTJ85B.
IF i do the new update what do I need to do to keep root? Will I have to wipe everything?
Thanks
Click to expand...
Click to collapse
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Yazan76 said:
Yes. What I did is backup everything, flash back to stock, wait for my device to download and install the 3.2.1 update, and finally flash the recovery, root my device, and install the tachi kernel. Restored all my applications after making sure that everything is fine.
I know it looks like a long a process but google market applications restore saved me a lot of time.
Click to expand...
Click to collapse
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
.
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
okantomi said:
To save even more time and get back your app data, first back up aps and data in Titanium Backup and make sure the backup is on your external sdcard, just to be safe. Then, after wiping, and once you have rebooted, reinstall TB and then run a batch restore of missing apps and data. It is much faster and better than letting google restore the apps.
Click to expand...
Click to collapse
Even simpler... fastboot flash just boot, system, and recovery stock images. Leave userdata alone. Allow the update. Don't worry about letting it fully boot.. let it.. no harm.. but no root.
Then flash CWM (using fastboot).. boot to recovery.. CWM univ root. Good to go. Or CWM a different kernel
CARLITOZ18 said:
Yesterday just rooted my xoom but now i have a problem when i try to flash something or do something in recovery doesnt work it say cant open sd or cant mount sd any help
Click to expand...
Click to collapse
You need to have an exernal sdcard for the recovery images to work.
Chipster0 said:
... Fastboot flash just boot, system, and recovery stock images.
Click to expand...
Click to collapse
Do you (or anyone else) have any (US VZ 3G MZ600) stock images later than HMJ37? Moto stopped carrying at HRI66 for some reason

[Q] Problems with stock rooted rom when flashed from recovery.

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.

Major Problem using TWRP

Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
doesntmatterx said:
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
doesntmatterx said:
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
Click to expand...
Click to collapse
:good:
xBeerdroiDx said:
:good:
Click to expand...
Click to collapse
I take it back, stuck in a boot loop even after 2 fresh ODIN unroot tasks. Nothing I do gets me out of this, been a long day getting longer now
Can anyone help? Been at it for hours, I have tried everything, phone still reboots at the Samsung logo (the bluish one )
Unrooted 3 times
Launched stock recovery, wiped factory reset
wiped partition cache
removed battery
Cannot connect to Kies for Emergency restore.
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
seanpr123 said:
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
doesntmatterx said:
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
Click to expand...
Click to collapse
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Should I ODIN with the RE-Partition Option?
Just Odined again and no dice. I booted into stock recovery and noticed after wiping factory I get "Can't open /efs/log/boot_cause" which pointed me to this fix someone on the Galaxy note forum said they did and it worked but I dont understand the steps, need some elaboration.
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
jd1639 said:
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Click to expand...
Click to collapse
Yep did that mulitple times, also did wipe cache partition in the same stock recovery. I get to the Samsung logo where the blue halo spins around the name, then it freezes there and reboots.
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
seanpr123 said:
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
Click to expand...
Click to collapse
LOL thanks, yes I may have to do that. I had a backup and it was wiped.
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Try flashing using cwm. It'll probably work fine. Then you can go back to twrp. That's worked on other devices. Seems one you flash it once with cwm then twrp works from that point forward. Idk why
doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
jds3118 said:
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I tried flashing with a PIT file I found online but it fails through ODIN everytime. I tried on multiple versions of ODIN as well. I also cant seem to find readily available PIT files to test as well, (perhaps the one I used does not work). Also I did try to flash a CWM through ODIN but failed, but again there isnt anything that I have read that says "hey you can do this that way and it will work".
From what I understand I need to be rooted to install CWM or TWRP, and since I unrooted to try and fix the problem I cannot root myself through conventional methods. Everything I found online requires the phone to completely start up. (to the menu screen etc)
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
jd1639 said:
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
Click to expand...
Click to collapse
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
doesntmatterx said:
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
Click to expand...
Click to collapse
Do you know what firmware you were on? Was it mdl or mf3?

Backups on Phillz Recovery

Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Got backup to work. But still unable to get custom rom aka update.zip to get past bootloader. Anyone kno how to fix this.
TeamBlaze
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
leaderbuilder said:
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
Click to expand...
Click to collapse
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
yotaking said:
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
Click to expand...
Click to collapse
Never tried that (make ROM from recovery in philz) myself.
I just make and restore loads of backups using Philz and TWRP. I consider a full backup (complete image(s) of all phone partitions) to be my ROM(s).
I would bet that with what you're doing that if, after you flash your custom made zip (and before rebooting) you stayed in recovery and then flashed (install zip) of the same recovery, rebooted back to recovery and flashed the kernel it may work.
Rebooting the recovery (or a battery pull) often clears out hangs.
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
do you have 4.3 compatability checked off?
same issue
yotaking said:
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Click to expand...
Click to collapse
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
androidaddicted said:
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
Click to expand...
Click to collapse
I like twrp as well but dnt wrk on 4.3
TeamBlaze
dewrust said:
do you have 4.3 compatability checked off?
Click to expand...
Click to collapse
Conito11 said:
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Imma look into these
TeamBlaze

There's something really satisfying about...

...rebooting to recovery and making a nandroid backup.
I plan to add an audio mod to my phone (Extreme Beats or whatever) and it's so nice to just reboot to recovery from the modified boot menu, make a nandroid in a proper version of TWRP and then flash whatever I want and move on, knowing that I'll be able to revert should I need to.
SubliminalME said:
...rebooting to recovery and making a nandroid backup.
I plan to add an audio mod to my phone (Extreme Beats or whatever) and it's so nice to just reboot to recovery from the modified boot menu, make a nandroid in a proper version of TWRP and then flash whatever I want and move on, knowing that I'll be able to revert should I need to.
Click to expand...
Click to collapse
Indeed.
Just remember a nandroid for our phone is a limited backup. There are partitions that only a firmware restore can fix making it a 2 step job.
Also persist is only, IS ONLY on phone not in firmware & only Philz can back that up!
aviwdoowks said:
Indeed.
Just remember a nandroid for our phone is a limited backup. There are partitions that only a firmware restore can fix making it a 2 step job.
Also persist is only, IS ONLY on phone not in firmware & only Philz can back that up!
Click to expand...
Click to collapse
Interesting. I didn't know this...is there a thread or article you can link me to where I can learn more?
SubliminalME said:
Interesting. I didn't know this...is there a thread or article you can link me to where I can learn more?
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/development/xt10xx-philz-touch-t2612149
The same RAZR HD thread is where I last backed up persist

Categories

Resources