Related
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
SectorNine50 said:
I have unbricked this phone probably 15 times in the past day trying to just install a custom ROM.
I run through the unbricking process, get root, load the stock AT&T ROM, factory reset, and it boots just fine from there. However, after I load Clockwork Mod and try to load any custom ROMs at all, the phone will just bootloop forever. It also appears to remove the Clockwork Mod recovery image as well, since I no longer am able to get back into recovery after the flash of the new ROM.
I've scoured this forum for hours, and I'm at a complete loss. Any ideas?
P.S. I made a backup of my ROM before doing all of this using the latest version of Clockwork Mod, but was unable to restore it. It seems that the 6.x.x.x version of the recovery for this phone is busted in some way, it always reports that it can't access any of the root folders, even though the phone has been rooted. The 5.x.x.x versions don't seem to do this, but I still have issues flashing.
Click to expand...
Click to collapse
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
lordcheeto03 said:
Is it possible that your hosts file needs modifying when installing the AT&T ROM? If the LG Support tool connects to LG's servers instead of your local http you set up, it will load the official ICS and completely wipe your phone to install that ROM... With my limited amount of knowledge, that's about all I could see if the process removes CWM Recovery.
Also, CWM 6.x is working fine for me, even manually flashed the touch recovery a few minutes ago, backed up my ROM and installed an updated ROM. No problems at all.
Click to expand...
Click to collapse
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
Swetnes said:
I don't know if anyone has tried the unbrick method with the new version of cwm but you might try twrp. When a similar version of cwm was in beta there were all sorts of issues. So maybe they haven't been fixed. Also are you installing cwm from GB? ICS has a locked boot loader so that might also be an issue.
http://forum.xda-developers.com/showthread.php?t=1888910
Now I would start with the unbricking guide for a 16th time but follow the directions to install twrp instead of cwm. You might also find you like it better. Good luck.
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
SectorNine50 said:
I don't believe that the unbricking process would work if the hosts file was wrong, but I checked it again anyway, and it appears to be correct.
The AT&T ROM gets pushed via the abd shell after the unbrick and rooting process. The root appears to work, as the AT&T ROM that I push works fine, it's just not the ROM I want!
After the unbricking process (after I get through all the nonsense on the Korean ROM), the phone is running the GB AT&T ROM, from there I push the CWM recovery.img to the phone using the abd shell. All seems to be working perfectly up until I go to flash the custom ROM! I don't get any errors when I flash the .zip either.
Initially I had installed CWM 6.x.x.x using the ROM Manager application. That's before all this nonsense started, and the phone was on the stock (but rooted) AT&T ICS ROM, so I know that's why I "bricked" my phone the first time.
I'll give TWRP a shot, hopefully that will work.
Click to expand...
Click to collapse
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Ok so we know it's not the boot loader issue of ICS after dozens if not hundreds of successful installs using the unbricking guide the only thing left is the new version of cwm. Hopefully twrp will do the trick for you. Has anyone out there successfully completed the unbricking guide with the new version of cwm?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
SectorNine50 said:
I haven't tried the TWRP recovery a shot yet, since I haven't been home, but I figured it was worth pointing out that the CWM 5.x.x.x (can't remember exact version numbers right now) didn't work for me either. Every time I flashed a ROM, I'd end up with a boot loop on first boot, and then when I'd try to go back into recovery, I'd find that it wouldn't go back in there either.
It was basically acting like when I flashed the ROM that it overwrote the recovery partition, except no one else seems to have this same issue. Yet, if I didn't flash a ROM, I was able to go in and out of CWM recovery as often as I wanted.
Bah.
Click to expand...
Click to collapse
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
drumist said:
Can you clarify exactly what method you are using to flash the ROM? I just can't imagine a scenario where flashing a ROM would overwrite the recovery. What ROM are you flashing?
Also, please confirm what phone you have.
Click to expand...
Click to collapse
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
You are correct, the Nitro is P930. And I'm sure this doesn't need pointing out, but when you download the ROM, make sure it's for P93x and not SU640. Most of the ROMS in the developer section have versions for both models.
Also, when you say you can't access CWM after flashing a ROM, how are you trying to access it? Holding Power+Volume down until the Factory Reset screen pops up? It still shows that screen even with CWM installed, but when you press the power button to perform the factory reset it SHOULD take you into CWM Recovery instead.
SectorNine50 said:
Sure, I may be using the wrong term (my first experiences with custom ROMs date back to Windows Mobile, so the terminology probably blends together), but I'm basically loading the .zip from the SD Card in CWM. I've tried both the CM9 P930 ROM and Paranoid Android CM10.
That was my thought too, I didn't think that the custom ROMs even had recovery images in them. I may be wrong in saying that it deletes CWM, but after the wipe and flash I am no longer able to access it.
I have the LG Nitro HD, and from what I can gather, that is the P930, correct? I hope the issue I'm having is as simple as I'm flashing for the wrong phone...
By the way, thank you all for your help and input, I really appreciate it!
Click to expand...
Click to collapse
To access recovery, turn the device completely off. (If you're in a bootloop, pull battery or hold power button for ~20 seconds until screen stays off.) Then when phone is off, press and hold volume down and power buttons at the same time, not releasing until you see text asking if you want to factory reset. Press power button twice to confirm and you'll get to recovery.
Is this the method you're using to try to get to CWM?
My guess as to why you are getting bootloops is that you aren't wiping data first.
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
SectorNine50 said:
Yup, that's how I'm accessing CWM. After the flash, after I press the power button twice, I get something similar to a boot loop. A recovery boot loop, if you will.
Well, I've tried a couple ways now. I've tried using the "factory reset/wipe user data" menu item in CWM, and I've tried going into each partition and wiping them individually before flashing as well.
Just got home, I'll try flashing using the TWRP and let you guys know.
Click to expand...
Click to collapse
Good luck. Other possible things to try:
1) Check zip MD5 hash (or just redownload and replace) to make sure it's not corrupted.
2) Reformat entire SD card.
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
SectorNine50 said:
Interesting update:
I decided to give getting back into CWM recovery one more shot before I went through the process of re-unbricking again, and this time it managed to get in (for whatever reason).
So, I did a factory wipe, cleared dalvik cache, flashed the ParanoidAndroid ROM, backed out, did another factory wipe, and tried to reboot into the newly flashed ROM.
No luck. Boot looped, and didn't even get to the ROM animation. Following that, I had trouble getting back into the CWM recovery. Managed to try about 5 times and finally got in, however CWM stated:
Code:
CWM-based Recovery v5.0.2.7
E:Error in /cache/recovery/last_log
(Read-only file system)
So... my phone may have potentially unrooted it's self, somehow... Interestingly, it still shows the file systems as mounted.
So, now I'm doing a full SD card reformat. Figured I'd get that variable out of the way before I go any further.
Click to expand...
Click to collapse
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
drumist said:
You are installing the wrong version of CWM. Never use anything older than 5.8.2.0. This is the one you want: http://download2.clockworkmod.com/recoveries/recovery-clockwork-5.8.2.0-p930.img
Anything older than that is known to not work.
Second thing: You seem to have an incorrect understanding of what "root" means. Having "root" simply means you have administrator access to your current ROM. When you install a new ROM, whether you had root access to your old ROM is meaningless frankly.
Click to expand...
Click to collapse
Ah, thank you! I must've been viewing an old thread. Now that I look at the version number, it appears that's the version I had been hunting for since the newest one didn't work.
Interesting, I most certainly misunderstood, I was under the impression that "rooting" the device was a filesystem level permission change. Good to know!
It seems like we are getting closer to a solution here. Thanks for your patience!
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
SectorNine50 said:
Well, that appears to have been my problem the whole time! That's kind of embarrassing, considering how much time I sunk into this and how simple the solution was!
Anyway, thank you all very much! I assume that TWRP would have also solved my problems as well. It would seem that both the older and newest versions of CWM have some problems (at least for me!).
Click to expand...
Click to collapse
Yeah, the new one (6.0.1.5) just came out. I'll have to test it to see if it works for me.
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Malnilion said:
For what it's worth, I haven't had any issues with 6.0.1.5 yet. The touch version is a must, though.
Click to expand...
Click to collapse
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Swetnes said:
Have you had a chance to compare to twrp?
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
I really enjoy the integration Rom Manager/CM Updater has with CWM. If twrp is capable of running the install scripts those two use, I might consider trying it out, but I don't really like manually going through the steps to flash a rom every day.
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Does anyone know what would cause the phone to keep restoring its previous state ? As I mentioned I have looked for the recovery-from-boot script and cannot find it. Thanks!
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
I have attached the output I get from logcat. Please help!
***Removed logcat file***
1) did you wipe data/cache when you switched roms?
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Dr01d4l1f3 said:
Verizon Samsung Galaxy Nexus - Toro
Bootloader version: PRIMELA03
Baseband version: I515
Android version 4.1.1
Miui.US 2.9.14.0
Clockwork recovery v5.5.0.4
I was previously running Vicious Jelly bean and installed Miui.US. Since then my phone constantly reboots within a few seconds of booting up. I have tried flashing to a different ROM and flashing back to stock several times using different tools and also from command line. I have also tried going back to stock via ODIN. All have failed and the phone always restores itself to the previous state. I have searched for recovery-from-boot.p in /system and other locations but cannot find it.
My Droid is currently unusable. Any tips or tricks are greatly appreciated.
Click to expand...
Click to collapse
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
cdexsw said:
This is what do every time for ANY rom and never have issues.
I also restore data with TB after successful flash and startup, then I login into Google.
Using clockworkmod touch recovery 6.0.1.5
Under mounts & storage:
Format....system
Format....cache
Format....data
Then install ROM of your choice.
If installing custom kernel waiting until the device has fully booted up to setup screen and then reboot to recovery and install your favorite kernel.
If flashing mods and such you need to reboot after each flash otherwise you could bootloop or get stuck at Google logo....
If using twrp it has a feature that allows flashing multiple zips.....with miui it has caused intermittent problems on some users devices.
Hope this helps.....
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Dr01d4l1f3 said:
Zepius,
Thanks for the response.
1) did you wipe data/cache when you switched roms?
I have wiped data and cache several times after I switched. Both from within recovery and running command 'fastboot erase cache'
2) dont use odin, its not really supported for this phone. learn fastboot: http://forum.xda-developers.com/show....php?t=1626895
I have followed this manual and others and have become familiar with the process. I complete all the steps and issue the 'fastboot reboot' command. The phone reboots back into the previous state
3) recovery-from-boot.p has nothing to do with what you are talking about. all that does is restore the stock recovery. ODIN is failing for another reason.
I'm grasping for straws here, not sure what else I need/can do
Click to expand...
Click to collapse
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
eqjunkie829,
Is it lonely up there on your high horse ? This is not the first time or the first phone I have rooted.
eqjunkie829 said:
Ill never understand why people dont learn stuff like this before they start flashing roms in the first place. These steps are common knowledge and easily attainable information. Maybe this post will help some poor android noob fight the urge to post an unnecessary topic in the future and stop panicking and restoring their phone to stock when they soft brick it.
Click to expand...
Click to collapse
cdexsw,
Thanks for the tip, I will try that.
cdexsw said:
Odin fails because it is not fully compatible with CDMA radios....meaning that it cannot flash the baseband/radio for cdma devices....well at least it doesn't for Verizon gnex.
You need to manually flash your devices images using fast boot. This can take awhile.....if you don't know what you are doing then READ first before doing so. Make sure you have the proper images.
Or look for P3Droid All-n-One-JB-Installer zip, flash it from cwm recovery. It will get you pure stock running a rooted jelly bean ROM. That's the best you can hope for....
Also before flashing follow the steps I listed above.....
Goodluck
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Zepius said:
2) dont use odin, its not really supported for thisany phone. learn fastboot: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Odin is a leaked tool from Sammy, it is not supported on any device.
OP, read efrant's guide on flashing stock (sticky, general section)
Sent from my i9250
I've owned a Galaxy S II before, and had it rooted. I followed all the steps, did the odin CWM push, flashed su in recovery, phone has su on it, but locks up when requesting root permission. Use su fix, and it says not rooted. In recovery if I go to one of my older back ups from my old s II, it flashes 1 of them, it boots, but it's a very old version, not ICS which I want. I try to flash a new rom, and within seconds it says it's completed. I've tried MIUI, and CM10 stable version. They get to the boot screen, but goes no further. I let both of them sit for over 10 minutes, each time I would go back into recovery factory wipe, and davlik wipe multiple times to make sure the wipe went through, fix permissions, but still won't boot. I've tried to odin CWM again, and reflash su, and it always says it works, but I still don't have root. Any advise? I basically just want to get a good stable version of CM10. If anybody has a way to upload me a restore point I can flash, I'd be much appreciative of that. I don't know a whole lot to the rooting scene, but I've done it quite a few times, so I'm pretty sure I didn't screw up. The phone works fine, I just noticed after using su fix, my battery drains a lot faster now on stock rom, and that's only with wifi enabled, and bluetooth. I'll lose over 50% in less then 2 1/2 hours with maybe 20 min. of heavy use. I'm sorry if someone already posted this same issue, but I've been searching and searching and can't find a solution. Thank you for any help, or taking the time to read the post, I love XDA, it's the best forum, and you guys are amazing.
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
nashy10 said:
My past experiences with odin are terrible. Had to go through 4 phones because Odin ****ed em up. Carrier was mad, but oh well, imo just use another method if possible
Click to expand...
Click to collapse
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Dagouk said:
Never had problems with Odin, but when I restore to a backup that was rooted, it's still rooted. Tried to install ROM that way also, bit still hangs on boot screen.
Click to expand...
Click to collapse
Clean flash again, if it hangs again, go back to recovery, clear cache, reboot, might help
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
drakulina said:
Fix permissions maybe?
Try a different version of CWM.
There were several versions of SuperSU. Some of them were not working on Hercules. Make sure that you are using the files from this post http://forum.xda-developers.com/showthread.php?t=1311194 (md5sum to check that you do not have an incomplete download).
Click to expand...
Click to collapse
The links are dead links, I've already tried that post. I used the original cwm I users with my first have, just a different su.
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
sinfulgray said:
Make sure you dont need an updated binary for su....sometimes it will install and if not up to date will not allow su permission. Open the su app and check if it needs updated.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Did the play store su update already. Other then that don't see a way to update the binaries.
Hey guys,
Quick one, what would be the safest option if I wanted to restore to 4.2.2?
Option 1- use a toolkit and restore factory image so that the bootloader gets updated also... I think it does, haven't done it yet. Heard that you shouldn't ever touch your bootloader as it's the last defence against bricking your device.
Option 2- restore back to my original 4.0.2 factory rom, same version as my bootloader is and let Google do it.
Option 3 - do it manually using Adb and then update my rom to whatever rom I want.
Just heard that some of the new roms need the latest bootloader, not sure why.
I'm pretty keen to do a full wipe and get things fresh again, so option 1 is looking good but if I stuff up my bootloader doing any of these, I'm screwed.
Or if anyone has used mskips toolkit to restore to 4.2.2, I'd like to know how they went and if it all went well. I have the full donation version and I think his toolkit is the best thing on xda... Just my opinion. He's also a great help to everyone on this forum. He's the boss haha.
Thanks in advance guys.
Cheers.
Sent from LV-426...
I would say forget all the toolkits.
Download this https://developers.google.com/android/nexus/images#takjujdq39, run that *.bat file. This will wipe everything on your device (INC SDCARD), and will install the latest radio and bootloader as well.
Then flash the recovery of your choice (TWRP or CWM) via fastboot (in the bootloader)
Boot into recovery, flash superuser of your choice via ADB SIDELOAD and reboot.
Brand spanking new 4.2.2 rooted, custom recovery and ready for setup.
rickbosch said:
I would say forget all the toolkits.
Download this https://developers.google.com/android/nexus/images#takjujdq39, run that *.bat file. This will wipe everything on your device (INC SDCARD), and will install the latest radio and bootloader as well.
Then flash the recovery of your choice (TWRP or CWM) via fastboot (in the bootloader)
Boot into recovery, flash superuser of your choice via ADB SIDELOAD and reboot.
Brand spanking new 4.2.2 rooted, custom recovery and ready for setup.
Click to expand...
Click to collapse
I concur with your method. But couldn't you just fastboot flash each partition to avoid the sdcard wipe? I also think the toolkit is great, but it is a tool. Becoming familiar with what the toolkit does behind the scenes to achieve its ends will be invaluable if for some reason things go haywire using the toolkit. After possessing that knowledge, the toolkit is a blessing.
Sent from my Galaxy Nexus using Tapatalk 2
Thanks guys for that. Very valuable info there for a lot of users.
Well, one other great things about the "boss" mskip, he fully guided me through the unlocking and rooting process step by step, out of his personal time.
That was fully priceless information for me at the time. I was well, a complete noob then, not that I'm android king now by any means but at least I have a grasp on the basics.
This is why I'm probably asking these questions to start with. I always like to know my device before I go racing in breaking things or doing things I'm not really on top of. Haha.
Anyway, saying that, I have gone through all that at the start so I'm probably more than happy to let the toolkit do its thing for me. But, your right as well. Doing it manually, if something does crap out, I'll know what it was haha.
Just want to do it the cleanest way possible. Also, been sitting on the same bootloader since phone release so I'm still not really sure if it's necessary to update it. The old saying, if it ain't broke... Then on the other hand, with android these days, the latest "usually" is the best.
Thanks again guys. If anyone else wants to add opinions or info, please do. I might sit on this for another day or 2.
Cheers.
Sent from LV-426...
Google added security features to protect your data.
I was on 4.2.1 and flash a bunch of stuff that screw it up. I didn't have a backup so I figured I use the toolkit to push images back. Well it gets stuck on boot loop until you wipe the device clean. I lost all my pictures and gamesaves so be careful.
Sent from my Galaxy Nexus using Tapatalk 3 Beta
Adb side load it,! It worked for me using Windows xp
Update the bootloader as well. I believe it's required.
Sent from my Galaxy Nexus using Tapatalk 2
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I initially flashed all the way back to the TWRP build before 2.3.1 but stopped there. I'll report back with results of your recommendation in the morning!
prboy1969 said:
You can try Flash Image GUI from the Play Store. Or maybe even Rom Manager. Then Uninstall it when you are done.
Click to expand...
Click to collapse
ROM Manager was something I tried as a last resort as well, it flashed the custom recovery alright, but soft bricked it with a redundant recovery bootloop. I got past that by Odin-ing back to stock.
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
prboy1969 said:
Odd. I've used the Toolkit you mentioned in your OP. Also the other methods to install a Recovery. Did you manage to Root again, and install a Recovery ?
Click to expand...
Click to collapse
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
jdonmc1948 said:
I had the same issue on mine. Dropping back to TWRP 2.3.1 solved it for me. Some L-710s just seem to not like the updated version.
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
n3td3v said:
Yes, I can easily root every time with Mark's toolkit as well as install a recovery, but I always get the 'unable to mount...' message when I attempt to do anything and it will not recognize neither the internal nor the external sdcard.
UPDATE: Still in the same boat even after flashing all the way back to TWRP 2.2.2.0. Recovery can't find or mount anything!
Although I'm not sure why (since I used the same methods and the same toolkit on both phones), I have a feeling that the internal memory and/or partitions somehow got corrupted. The only thing I haven't tried is using Odin to repartition and reflash everything including the bootloader. Hopefully someone has posted the files for us!
Click to expand...
Click to collapse
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
prboy1969 said:
I believe you can do that with mskip's Toolkit. I would also reformat the SD Card. To format the SD Card you can use SD Formatter.
Click to expand...
Click to collapse
I tried formatting the sdcard as well as without the sdcard and even with a different one to no avail. I'm still on the hunt for pda, csc, etc. Odin files. My last resort will be to figure out how to get it replaced at Sprint as a defective device lol
Sent from my SPH-L710 using xda premium
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
billard412 said:
Have you tried using stock recovery? obviously not to flash anything but just to try and navigate the sd or wipe the cache for example. Just curious if the mounting issues are present in all recoveries or just twrp/cwm. Also a bit intrigued by the fact that the phone still boots and operates normally
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Yes, stock recovery allows clearing of cache, depending on whose stock recovery I flash. If I flash the toolkit version of stock, I can clear no problems. There are a couple of other stock recoveries, such as this one, in which everything fails as well.
FYI, I have even flashed the stock builds you have on sxtp with the same results.
Thanks for this -- you solved my problem...at least mostly.
I tried to root a new Sprint SG3 by ODIN'ing CWM and then flashing a root.zip file. That epic failed just like your situation where nothing would mount in recovery whether I used CWM or TWRP. I am assuming that something must've changed on the Sprint S3's and that root method must not work anymore (for whatever reason). So I decided to go back to stock recovery and just wait and see if anything further is discovered about this here (I'm not a dev, so I have to wait for other more talented people to solve my problems). However, the stock recovery image that I downloaded from the same "Easy Root" tutorial here didn't work and I still couldn't mount anything.
Saw your post where you stated that the Toolkit stock recovery image worked, so I just tried that and score! However...my poor little recovery android is on his back with a red triangle and a "!". Everything mounts, I can wipe cache, browse around for an update, etc., but I'm a little concerned that my little Android is sick. Should I be? Is that because I have a flash count of 5 so it thinks I have a custom ROM?
Sorry to hijack your thread a little, but my problems seems to be related.
n3td3v said:
A strange predicament indeed. Two identical SPH-L710 phones, both came packaged running 4.1.2 build MD4 and, using this toolkit, I was able to successfully root, flash TWRP recovery and proceed to flash a custom ROM with no issues...at least to one of the phones.
My problems began with the second device. I was able to successfully root and flash recovery (TWRP or CWM) here as well. I question the success of the recovery flash due to the picture as indicated where I get numerous 'unable to...' everything. I might also add that on recovery entry TWRP asks for a password. I am not bricked as I can boot normally into the OS and use the rooted phone. I feel like I have tried everything I could find on this forum as well as several other sites to no avail. I have downgraded to 4.1.1 build LJ7 with the exact same results. I have repartitioned as well. Right now the second device is running build LJ7 since I have come to a screeching halt until I find more things to flash and hack away at this stubborn thing!
This is by no means my first bout with the Android platform, but if anyone can give me a pointer or two to set me on the right path, I will gladly hand out some thank yous!!
Click to expand...
Click to collapse
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
swiggs98 said:
I just got a brand new GS3 today and am having the exact same problem you describe. I have rooted several GS3s before... normally is child's play. I am a bit embarrassed to get stuck here. CWM nor TWRP mount anything... major bummer. TWRP prompts me for a password as if it thinks it is an encrypted /data partition... strange.
Click to expand...
Click to collapse
Same boat. Rooted probably 6 S3 before now and my wife's new S3 I am seeing same thing.
Sent from my SPH-L900 using xda app-developers app
I'm having the same issue. I finally downloaded an image that allowed me to flash it but I still cannot mount anything in recovery? Any help would be nice
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
n3td3v said:
Thanks guys, it is comforting to know I'm not the only poor soul stuck in this rut! I'm pretty sure I have exhausted all flashing resources out there at this point, but I'm eager to try whatever new that has potential of working that anyone cares to conjure up.
One strange thing I have also noticed on the problematic phone is that the signal is significantly weaker than my phone, even when both were at stock. It is always dropping calls and/or going into roaming, etc. I haven't been able to produce a log of any sort as they won't write since recovery cannot mount ANYTHING! Lol
Click to expand...
Click to collapse
Folks, A quick search would have led ya here : http://forum.xda-developers.com/showthread.php?t=2183910&page=4 This is a known issue with both TWRP and CWM recoveries on newer S3's. Devs are working on it to find a solution. Just a matter of being patient and waiting. IF you just want root access, you can odin a pre-rooted rom to the phone with no issues. You'll atleast have root at that point. Just unable to change rom/kernels on the fly.
I achieved root with virtually no issues but thank you for the link!
Sent from my SPH-L710 using xda premium