I installed the 4.3 update rooted and installed twrp. My hotspot stopped working so I restored a nandroid of mf9 and now im stuck on 4.2.2 with mja software version. Knox has been tripped. Should have done more research before diving in. How could I get this back to 4.3. Re applying the update has failed.
prc292 said:
I installed the 4.3 update rooted and installed twrp. My hotspot stopped working so I restored a nandroid of mf9 and now im stuck on 4.2.2 with mja software version. Knox has been tripped. Should have done more research before diving in. How could I get this back to 4.3. Re applying the update has failed.
Click to expand...
Click to collapse
And restoring my nandroid of 4.3 just puts in a bootloop
prc292 said:
And restoring my nandroid of 4.3 just puts in a bootloop
Click to expand...
Click to collapse
Been there and not fun. Go to my post about how to fix the boot loops. http://forum.xda-developers.com/showthread.php?t=2506562
So I took as he to get the files due to some busy servers, but I restored them and factory restored but still ended up with a boot loop.
prc292 said:
So I took as he to get the files due to some busy servers, but I restored them and factory restored but still ended up with a boot loop.
Click to expand...
Click to collapse
Just wanted to post back and say the reason it didn't work is Because I didn't follow the directions. I assumed that because they were two files I could use twrp. Not the case. Must use philz. I am back to 4.3. Thank you soon much!
Anyone else having issues restoring nandroid on Philz recovery. I'm running stock mja fully updated bootloader and modem. My backups always bootloop.
prc292 said:
Anyone else having issues restoring nandroid on Philz recovery. I'm running stock mja fully updated bootloader and modem. My backups always bootloop.
Click to expand...
Click to collapse
Are those backups of 4.3 or 4.2.2?
Sent from my SPH-L720 using Tapatalk
prc292 said:
Anyone else having issues restoring nandroid on Philz recovery. I'm running stock mja fully updated bootloader and modem. My backups always bootloop.
Click to expand...
Click to collapse
You have to check process SE context JB 4.3 settings in philz recovery UNDER misc Nandroid settings before making back up :sly:
ParkerParker said:
You have to check process SE context JB 4.3 settings in philz recovery UNDER misc Nandroid settings before making back up :sly:
Click to expand...
Click to collapse
Thanks ill give that a shot. And they are 4.3 backups.
prc292 said:
Thanks ill give that a shot. And they are 4.3 backups.
Click to expand...
Click to collapse
That will work, I also uncheck md5 at the top and mine all restore perfect, it's all preference I guess, just as long as the 4.3 box is checked you will be good to go :thumbup:
Sent from my SPH-L720 using Tapatalk
Related
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 have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
csrredcoat said:
I have had several custom roms using TWRP with no problems. Today I decided to try pacman rom and nandroid backed up my negalite wonderom. downloaded pacman to external card, rebooted to TWRP. I formatted internal storage and did full wipes on everything but external sd. I tried installing pacman zip and get FAILED unzipping and updating partition. so I then try flashing my old rom and get same error. I then nandroid back to previous rom and boots as expected. If i reboot again, I get stuck on samsung galaxy s4 boot screen. I've tried repeating all these steps but now I am without a phone until one of you nice people help me. What can I do? Please help.
Click to expand...
Click to collapse
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
ROMANTiC KiD said:
Odin back to stock.
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
csrredcoat said:
I did odin back to stock, ut i am stuck on galaxy s4 boot screen. What can I do to fix? Thanks
Click to expand...
Click to collapse
Take out battery. Put in back in. Go to stock recovery (by pressing volume up and power button and letting go when you see tiny blue letters) from there just do a factory reset then reboot. Dont worry if you a dead android its ok. Then you should be ok.
---------- Post added at 11:28 PM ---------- Previous post was at 11:12 PM ----------
csrredcoat said:
During this whole ordeal, I was trying to install CWM over TWRP and accidentally checked repartition in ODIN, it didn't seem to do anything ..just hanged and I pulled battery. I am now wondering if this screwed anything up and if so, what can I do?
Click to expand...
Click to collapse
Well from my understanding we should not have repartition checked. Dont know the outcomes tho but im pretty sure now you need pit files for gs4 sprint to remap the partitions for your phone back the way it was. Should be here in xda but if you cant find them then just odin again a stock tar and do a factory reset in stock recovery. See if that works.
Back to Stock but have a question
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Software/Baseband Version MDC to MF9
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
csrredcoat said:
So I was able to successfully odin back to stock. I am confused about format data vs wipes. I had some issues on a ROM and someone in a forum advised to format to truly erase any junk left behind by other roms. I did this in TWRP and installed a rom and it fixed the former issues I had on that rom. So I thought I had a new strategy, to format not just wipe.
So now I have CWM and don't even see the option to format data. If I want to make sure I erase everything, how do I ? Just doing factory reset, wipe data, cache and dalvik seems to leave files behind including personal files on internal storage. Just want to learn the best practices to avoid issues. I am kinda glad this happened, been a learning lesson. Thanks to all!
Click to expand...
Click to collapse
Im not so sure on CWM since ive been using twrp so I can help you there.
csrredcoat said:
After ODIN back to stock I am on MDC and want to get back to MF9. This is the procedure I used a few months ago HERE Is this the best way? Thanks.
Click to expand...
Click to collapse
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
ROMANTiC KiD said:
Im not so sure on CWM since ive been using twrp so I can help you there.
Its better if you just accept ota (*optional* do a factory reset when already at mf9.) Or just get the mf9 stock tar and just odin that when you have problems
You can download the mf9 tar here
http://forum.xda-developers.com/showthread.php?t=2375523
Click to expand...
Click to collapse
OK, I am confused but eager to learn. I just did a ODIN back to stock, I am now unrooted. I did a factory reset in stock recovery. Now I think I should be able to click update firmware to get to MF9 but it says no updates found or I am up to date. I don't get this. Why is it not finding any updates?
Even More Confused!
edit
Ok, it is downloading MF9 in background now. Not sure why it initially said no updates found. I should be good now. Thanks!
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.
So, I've been searching around the forum for "restore", "restore nandroid backup", etc. and I've always been directed to the method that's described here. Is that the only way to go back to stock? Can I not just restore my backup from my current Paranoid Android ROM?
If not, can I use my nandroid backup once I go back to stock using the aforementioned method?
KitKat does not allow custom recoveries.
Backup nand backup to PC, flash back to stock 4.2.2, install custom recovery, and then restore PA backup.
Should work.
Thank you for your answer!
I think I wasn't clear, though. I was on Paranoid Android at the time of writing the question. That's what I refered to as KitKat. And I wanted to go back to stock by restoring my nandroid backup of it. But, I've never seen anyone do it like that on the forums. Everyone used the LG flashtool. So, that's why I asked.
Ended up going to CloudyFlex, and I'm really happy about it!
Thanks again!
Sent from my LG-D802 using Tapatalk
robogo1982 said:
KitKat does not allow custom recoveries.
Click to expand...
Click to collapse
Technically, neither does JB. The Loki exploit is why we have any custom kernels/recoveries. I'm going to be submitting a request tomorrow to have Loki updated with the new aboot info.
My phone's backup does nothing when I try to restore it. I've also tried rebooting without the backup and nothing works. My phone will only boot into recovery. I am rooted, running JELLY BEAN, NEGALITE ROM r52, and CLOCKWORKMOD for my custom recovery. My firmware is MF9. What do I do to get my phone up and running again? Please list step by step or direct me to where I can follow the directions.
Thank You
Droid X_46 said:
My phone's backup does nothing when I try to restore it. I've also tried rebooting without the backup and nothing works. My phone will only boot into recovery. I am rooted, running JELLY BEAN, NEGALITE ROM r52, and CLOCKWORKMOD for my custom recovery. My firmware is MF9. What do I do to get my phone up and running again? Please list step by step or direct me to where I can follow the directions.
Thank You
Click to expand...
Click to collapse
Forget the backup for now and re flash and see if that helps... wipe all as you would with any rom install
Sent from my SPH-L720T using XDA Free mobile app
Droid X_46 said:
My phone's backup does nothing when I try to restore it. I've also tried rebooting without the backup and nothing works. My phone will only boot into recovery. I am rooted, running JELLY BEAN, NEGALITE ROM r52, and CLOCKWORKMOD for my custom recovery. My firmware is MF9. What do I do to get my phone up and running again? Please list step by step or direct me to where I can follow the directions.
Thank You
Click to expand...
Click to collapse
If you want to try and save some stuff reflash the Rom over itself without flashing (dirty flash) this might get the phone up and running allowing u to save stuff like messages or app data via titanium backup
Sent from my HTCONE using Tapatalk