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.
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
**EDIT**: Just did format on /data on stock recovery and it seems to have booted... False alert guys. Soft bricked, but nothing else.
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Blaze9 said:
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
Click to expand...
Click to collapse
Did you try factory restore / reset in recovery?
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
goobieracing said:
Did you try a factory reset in stock recovery? Or maybe try odining the pit file also that somewhere on the forum. Maybe your partitions got corrupt flashing some how.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
goobieracing said:
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
scott14719 said:
Did you try factory restore / reset in recovery?
Click to expand...
Click to collapse
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
Click to expand...
Click to collapse
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
I had to do a stock reset recovery the other day for something like this. Probably just left over files from previous stopping it from booting.
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
Click to expand...
Click to collapse
Sorry I learned something new today. Back in the infuse 4g days whenever I'd odined back to stock I always used the pit. I was under the influence that set everything up the way it came stock. Hope to see some of your work coming to sthe s4. Maybe you help the sense port going on in the international thread lol. Not trying to add work to ur day but I OK know if u, jt, and entropy can bring ICS to a out dated phone u might have the skills to ad your 2 cent.
Sent from my SGH-M919G using XDA Premium 4 mobile app
---------- Post added at 02:18 AM ---------- Previous post was at 02:01 AM ----------
Blaze9 said:
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Click to expand...
Click to collapse
I had to Odin to stock the first time two days agao but mine booted and I only had stock recovery. When it started up the ROM everything was crashing and that's what fixed it. Glad you fixed it though.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
gerard0986 said:
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
Click to expand...
Click to collapse
The PW TWRP asks for? IT's just TWRP, if I remember correctly.
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!
KT kernel is causing my phone to reboot on Super S4 when launching various apps. I could only find one place to snag the stock kernel which I tried and it fixed those problems. But now dropbox fails when trying to export files. Also the Amazon market fails when trying to download apps. I couldn't even update Lucky Patcher without getting a parse error. It seemed like a permissions issue so I tied to fix permissions in TWRP but that didn't help.
Any suggestions? Should I go back to KT kernel and try to figure out why it reboots my device? Or stick with stock and try to figure out the permissions problems? Or should I try a different kernel completely? Or should I just stick my phone up my ying yang and get an etch a sketch? Any help would be appreciated.
You can try flashing the stock kernel. Its located in the thread or a quick search in the Dev forum.
Did the MD5 SUM match?
Did you follow the install instructions? (Reboot recovery - full wipe)
Did you update Google services framework?
Sent from my SPH-L720 using XDA Premium 4 mobile app
---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------
Stock kernel
http://forum.xda-developers.com/showthread.php?p=53630603
Sent from my SPH-L720 using XDA Premium 4 mobile app
This is what worked for me
I am happy to report absolutely zero issues on my S4 installing and using Super S4. Let me detail what I did, and maybe you can go back to square one and start over with better results. Prior to installing SS4 I had the OTA version 4.4.2 with NAE modem.
1) After reading through the Super dev thread, I decided to use Philz recovery. I downloaded this one: philz_touch_6.23.9-jflte.tar.md5 and flashed it with Odin 3.07. I made sure to disable the auto reboot, as that has caused trouble for me in the past.
2) I downloaded 1.4 odexed and copied the file to my ext sd card. Then I checked the Md5 sum of the file on the card.
3). Booted to recovery, used the "Wipe Data/Factory Reset>-Clean to Install a new ROM" feature. Twice.
4) Under "Advanced" wiped Dalvik, twice also.
5) Rebooted recovery. DON'T FORGET THIS!
6) Flashed the ROM zip.
7) After flash, Selected "no" instead of "disable install recovery"
Everything came up beautifully. Be careful which KTweaker profiles you use, I had weird stuff happening with the "battery saver" profile. I am using Ktoonsified V6 now and battery life is great.
Hope this helps!
Try the 5-28 build of Kt. Wipe your ktweeker data and cache then flash an older build and redownload your profiles of choice is reset your own. I had some reboots on the latest which I'm sure you can retweek and solve but I've not had time so reverted to 5-28 and smooth criminalv5 just to keep me going though bonfire season lol.
Sent from my SPH-L720 using xda app-developers app
A few days ago my USB port on my Telus SGH-I337m gave out, leaving me with no data connectivity and extremely limited charging capabilities.
I rooted the phone using ODIN and TWRP when I originally got it last summer, but i forgot all about that and brought it over to best buy for an exchange. We did a factory reset before the guy noticed it was rooted and told me to un root and come back. However, after the factory reset, I'm now stuck on the samsung galaxy s4 splash logo, but I do still have access to recovery booting. I've tried downloading stock and custom roms and flashing those to no avail. I switched my recovery manager from TWRP 2.5.0.0 to CWM 6.0.4.4, but still nothing. ODIN flashing is impossible because the USB port isn't working. Any suggestions?
Are you using super SU? There's an unroot option in it
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
jd1639 said:
Are you using super SU? There's an unroot option in it
Can you flash a rom in recovery using adb side load or pushing a rom to it
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Free mobile app
I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo
SgtBuzzkilll said:
I don't have access to super SU at the moment. The phone hangs during boot at the Samsung galaxy s4 splash logo
Click to expand...
Click to collapse
You said you flashed cwm over twrp, if you did so you must be able to flash a rom too.
The bright side, if it's not booting you could take it to a best buy and they couldn't tell it's rooted
Edit, when you boot into recovery is it the stock recovery now, or cwm?
Sent from my Nexus 5 using XDA Free mobile app
Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
edit: it recovery boots into CWM 6.0.4.4 only, hangs on normal startup with any rom
SgtBuzzkilll said:
Any custom roms I've tried to flash have still left me stuck at the splash logo. Any chance you could point me to a stock ROM download? None of the stock roms i've found will install. And since it does still boot into recovery mode the guys at bestbuy will still know i have it rooted though right? worst case i might just drain the battery and bring it in since it takes about 20 mins to charge 1%.
Click to expand...
Click to collapse
If it boots into a custom recovery, twrp or cwm, yes they're going to know you modified the device. But you're not going to be able to get rid of that without Odin.
Sent from my Nexus 5 using XDA Free mobile app
If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it
SgtBuzzkilll said:
If I'm able to fix the boot error, would I be able to use mobile odin or super SU to unroot it?
Either way any other suggestions for getting past the splash screen?
What I've tried exactly is:
-boot into CWM recovery
-wipe data/factory reset
-wipe cache partition
-wipe dalvik cache
-install ROM from zip
-reboot
custom ROMS install ok but give me the boot error
stock roms don't install at all
And thanks for the help i do appreciate it
Click to expand...
Click to collapse
I'm not sure what to tell you. First, you're flashing the custom roms correctly and I'm not sure why they're not booting. I don't know what stock rom you're trying to flash.
Having the custom recovery is going to kill you at best buy. They'll try to boot into recovery to do a factory reset and they'll see you modified the device.
I don't know if mobile Odin works on the s4, I don't think so, but you'd have to boot into something first. And that's a problem right now.
Sent from my Nexus 5 using XDA Free mobile app
---------- Post added at 09:07 PM ---------- Previous post was at 08:48 PM ----------
@SgtBuzzkill I'm not at a pc tonight but tomorrow I'll make you a stock recovery zip that you can flash in cwm. That will take care of the custom recovery issue
Sent from my Nexus 5 using XDA Free mobile app
I managed to get past the splash logo. Turn out i needed to format all the partitions as well as clear them before installing a rom.
The stock roms i was (mistakenly) trying were the odin tar.md5 files. But now I've got mobile odin running and I found a couple videos with mobile odin and the gs4 so im going to give it a shot. The procedure recommends >50% battery though so I'm going to have to let it charge overnight.
We'll see if it works in the morning
Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
It will stuck at samsung logo after flashing, boot to recovery & perform a factory reset, and you are good to go.
King regards.
Starnel said:
Reflash lastest 4.4.2 (Colombia) Firmware from Sammobile, Tick "NAND Erase All", "Re-partition" & "Phone EFS Clear", also put the unziped attached file on the PIT section.
This will completely wipe your NAND, this means a complete Full wipe of the whole phone, I also have a i337M from Telus & deleted all the remains of previus modifications that normal recoveries can't wipe. thus reformatting Boot, Cache, System, EFS & all other partitions to their correct state.
Make sure your Odin window looks as the attached image.
Click to expand...
Click to collapse
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Read the op. His usb port doesn't work. No Odin
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Boot partition most likely to be damaged, Only Odin can repair it afaik.
Starnel said:
Boot partition most likely to be damaged, Only Odin can repair it afaik.
Click to expand...
Click to collapse
It's a broken usb port. It's hardware, not software.
Sent from my Nexus 5 using XDA Free mobile app