Related
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
datzstr8 said:
Does clockworkmod overwrite the stock recovery? If it does then to me it is not a safe method to root a phone. If something goes wrong while flashing clockwork you will lose the stock recovery and can never reflash anything else. Is my understanding correct? This is why I am hesitant to root my phone. Please advice.
Thanks.
Click to expand...
Click to collapse
Its fairly safe. You could always flash the recovery thru odin found here:
http://forum.xda-developers.com/showthread.php?t=1332103
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
With my dilemma would it be best for me to not install clockwork and just use an insecure kernel? Thanks.
It does overwrite the stock recovery i believe. But its very safe to flash. Ive never heard of someone borking a phone installing cwm recovery.
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
kabuk1 said:
I have literally NEVER had a problem with clockworkmod, it's one of the best pieces of mobile software I've ever used.
Click to expand...
Click to collapse
Whole heartedly agree.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Has anyone tried to flash clockwork and failed? What happened afterwards? I assume odin won't work anymore because it requires a recovery partition to work.
I guess what I am still confused about is if clockwork writes over the stock recovery or does it keep the stock recovery in-tacked. I would prefer the later since then you can never break your phone.
Click to expand...
Click to collapse
Odin has NOTHING to do with the recovery partition. ODIN only works in download mode on your phone. You can have a blank recovery partition and it'll still work, as well as the rom, and flashing other things too. The recovery partition stock has one function, to do a factory reset incase of problems. (Not to be confused with the one from inside android, that only formats /data. This one replaces the system partition as well.) CWM is very safe, I really wouldn't worry about it. Just follow the instructions carefully and you'll be fine.
Also, once you get cwm installed on there, I'd suggest doing a backup before you make any changes. Always handy to have your stock image at hand, just incase.
And also, even with stock recovery, you can still break your phone. It's not easy to brick a GS2, but it can be done. Just remember, as long as you can get the phone into download mode, it's not bricked. You can always odin back the stock partitions if you run into issues.
I was a little worried about using it with this phone. No problems to report. Just had to make backup in recovery.
Sent from my SGH-T989 using xda premium
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
If you're going to be rooting/flashing at all, you'll have to get comfortable with cwm, Odin, and the other tools that are available for the phone.
This is my second Android phone, both have been rooted with custom roms, and at any point I've run into trouble (which is rare) I've found the tools and the help I need on here by searching a little bit. If you're willing to spend the time doing a bit of reading and know your way around a computer a bit, you won't have a problem. Just make sure you're 100% sure whatever you're flashing is for YOUR phone hardware.
It's not nearly as scary as it sounds once you get going on it and there's a lot to benefit from it.
Cheers and good luck.
Sent from my SGH-T989 using xda premium
datzstr8 said:
Thanks mstrk242 for the great explanation. I thought the "download" and "recovery" were two states of a single program. It is clear now that they are separate. You just cleared all my worries.
You said "It's not easy to brick a GS2, but it can be done," can you tell me how this can happen? Just curious. Thanks much.
Click to expand...
Click to collapse
Easiest way is to flash a rom for the wrong phone and mess up the partition table. (IE flash an international version of the gs2 rom, you'll brick.)
As long as you get cwm installed on there, and flash the correct roms, you should really be ok.
You can go back to the stock recovery easily. You can do it through Odin or flash an unroot rom
Sent from my SGH-T989 with ClockworkMod ★Touch★ Recovery 5.8.1.3
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.
I really hate to start a new thread but I really can't find a reason/solution to this issue. It's just as the title says. I tried flashing the MIUI ROM just as any ROM and got a failed error. Then went to do my nandroid restore and it just hangs on the splash screen (boot screen). Anyway I thought there could be a bad download so I took out the SD and redownloaded synergy on my laptop, then put it back in the phone and nothing but the nandroid should let me restore. I even tried moving the files to the internal SD and nothing. The only thing I can think of is to Odin back to stock? Is it the same method as rooting? I'm sure I can find that out, but I'm just confused why it seems TWRP doesn't want to work. Thanks for any help, it's 4 a.m. here and I'm dog tired.
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
DarkManX4lf said:
Are you on the latest TWRP?
If all else fails you could go back to stock and root again.
Click to expand...
Click to collapse
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
jtadak said:
I think so. Yeah, just didn't want to go throught it all, and didn't know why.
Click to expand...
Click to collapse
Can I just reflash recovery from the state I'm in, or do I still need to unroot? I've moved some of my files to the ext SD within recovery but some things won't move and I really don't want to wipe it.
jd14771 said:
Try wiping everything 3X, then go to the reboot menu, and reboot system, wipe both the cache and dalvik cache and try to restore.
Click to expand...
Click to collapse
Do you mean reboot recovery? I can't reboot system. Sorry, not trying to split hairs, just trying to be specific.
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
mexiking713 said:
Odin back to stock seems like the best option.
Sent from a galaxy note 2 far far away...
Click to expand...
Click to collapse
Yes, that's what I did. I'm just bummed I had to wipe storage. Oh well, it's inevedible... I dig that sig though, with phone line up.
lovekeiiy said:
are you able to flash a different rom, say a stock rom? It's possible you got a corrupted TWRP download.
Since they just released another update 2.4.3, you might want to try and download the zip file, wipe cashe and davick (may want to do it three times). Reboot back into TWRP 2.4.3 and see if it gives you some better luck.
I've had Nandroid backup that didn't work for whatever reason. I didn't test it prior to needing it, and got burned. It just wouldn't show up in the restore menu.
On a side note, what error did you get when you tried flashing MIUI?
Click to expand...
Click to collapse
I tried multiple ROMs, but not a stock one. Hmm, I was on 2.3.2.3. I did'nt get a special error, just said a red message saying failed.
Evo_Shift said:
Try rebooting recovery when you are in recovery already once before flashing/restoring anything anything.
Click to expand...
Click to collapse
Tried that. Did'nt work.
jd14771 said:
no, i meant reboot system, the recovery will warm you that there is no os installed but go fourth with it, it will turn off and reboot back to recovery. at that point in time, wipe cashe/dalvik cache and try to install.
Click to expand...
Click to collapse
Ok, I was'nt sure. I just went back to stock. I just wanted to know what exactly was going on and why.
The only thing different on my phone is I got a 32 gig SD card. I transfed some of my files a couple days before doing anything of this. That's the only thing I can think of. Even after root/unroot it STILL won't do my nandroid restore. I had so much time and work into the apps I set up, games, ect. Really freakin sucks. I even went into the the TWRP backup folder and made sure the backup files were there before doing anything. I never even got to flash many ROMs, I kinda just stayed on Jellybomb.
I had the uTorrent app installed and I noticed that it changed a lot of files with the "u" in front that the uTorrent app has. Anyone know why that is?
Sent from my SPH-L900 using xda app-developers app
This is what it did to a lot of my files. But not the ones I tried to flash.
Sent from my SPH-L900 using xda app-developers app
I installed paranoidandroid 3.96a today and I had some errors before I was able to install it so I ended up formatting the data and then clearing the caches.
I flashed PA. Then I flashed the latest google apps. Then I flashed PA again and rebooted. My phone loaded fine and I was able to install everything I want.
Then if I reboot my phone it get stuck on the splash screen and cannot load. If I go into TWRP 2.5.0.0 recovery it asks me for a password (I have not yet a password although I recently bought this phone used on swappa so I've contacted the seller to ask if he set a password). If I push cancel at the password screen then I can get into TWRP but if I go to wipe the dalvik cache it say sit "failed." The test printed to the console is:
Updating partition details...
E: Failed to wipe dalvik
Updating partition details...
I also cannot browse the internal memory of my phone. There is no folder named "android" or similar.
Any thoughts would be greatly appreciated. I'm going to try to update TWRP to the latest version. After that I'm out of ideas
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
how long do you let the phone sit after rebooting? I'm currently on the same rom and noticed it takes longer than usual to reboot the device. it's seems like it takes just as long to reboot the phone as it does to boot up the phone right after flashing the rom.
try letting the phone sit for 5-10 mins and see if it boots up. it's kind of ridiculous it takes that long to reboot a phone, but then again the rom is in alpha. I might try reflashing the rom to see if this still happens.
Just posted in the ROM thread to see if anyone else has the same issue.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried installing PA again and then upgrading TWRP to 2.6.0.0 but it still said that it had 2.5.0.0. Then I installed CM10.1 and used that to upgrade to TWRP 2.6.0.0 which worked. I then tried installing PA3.96a again with the same results.
I think that the problem is with TWRP not recognizing android 4.3 installs correctly because I have the same problem with CM10.2 that I had with PA3.96a.
I don't think the problem is that I'm not waiting long enough because after the first restart (i.e. I flash it and restart loading the ROM fine--then when I restart it for the first time it gets stuck). When I go into TWRP after it hangs the first thing it does is ask me for my password. I don't have a password. I think that something is happening to the system partition after install that makes TWRP unable to read it on this phone. Also it says that 0 MB have been used on my phone ram so I think the problem is with TWRP not being able to read the system partition in 4.3 correctly.
Has anyone gotten android 4.3 working on the t-mobile s3 yet?
Edit: And I can't restore from a nandroid backup (unless I put it on my SD card because the phone cannot read from the system partition).
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yes I did. If I mount it I still couldn't see /android or any other folders. I could also not clear the dalvik cache or do a factory reset.
Okay that's the consensus. I'll try restoring to stock sometime this weekend and see how that goes.
I just reverted back to stock using Odin. Reset the counter to be safe and then used odin to load a rooted stock. Then I installed goo manager and had it install TWRP 2.6.0.0.
Success! I can install and 4.3. Something must have been funky with the previous rooting job or something. Who knows. Thanks!
Right on! Good to hear you got it running good!
Sent from my SGH-T999 using xda premium
same thing
so i basically have the same thing but with mine i installed hyperdrive rom and flashing the stock rom like you said doesnt work and doesnt get rid of hyperdrive so it just has the hyperdrive boot screen and i cant get to my internal memory ect. like him please help i cant have ruined my phone by the way im a noob so please be specific and give me links thanks
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
links please
bmdubs said:
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
imfukked said:
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
Click to expand...
Click to collapse
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
bmdubs said:
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
Click to expand...
Click to collapse
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
imfukked said:
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
Click to expand...
Click to collapse
Reboot your phone and instead of pushing volume up to put it into recovery mode push volume down to bring it into download mode. This is also what you use to revert to stock via odin.
IT WORKED
HOLY **** IT WORKED I HAVENT HAD MY PHONE FOR A WEEK I THOUGHT I WAS SOO SCREWED YOU SAVED MY ASS THANK YOU SOOOOOOO MUCH!!!!!!!:laugh::laugh::laugh::laugh:
My understanding is that it's actually kind for of hard to brick your phone from doing software modifications. It is possible but I think only if you really screw something up. Like powering down while installing a recovery or something.
Sent from my SGH-T999 using xda app-developers app
Unplugging in the midst of a firmware flash, and flashing the wrong models firmware are the easiest ways people hard brick.
If you can get download mode and recovery to boot it can be fixed most of the time.
Sent from my SGH-T999 using xda premium
Yeah what happened with me is I downloaded hyperdrive to my internal and this was my first time and I didn't install cwm or anything like that so I did the factory reset and cleared cashe but then I relized there's no way to clear your dalvik and or launch hyperdrive so I tryed booting my phone and it got stuck on the samsung logo everytime so I used odin to put cwm on my phone and I couldn't access my internal or clear dalvik so I used an external and used my old galaxy s2 to download hyperdrive on to the external and then launched it on my s3 and it installed great it let me choose everything but when I went to launch the phone it got stuck on the hyperdrive boot animation so I tryed like 10 stock roms none of them worked it wouldn't get rid of the hyperdrive boot animation iether so then I was sher the link you gave me wasn't going to work but unlike the other odin ones I did it took time instead of only taking half a second and it worked
Sent from my SGH-T999 using xda app-developers app
I have the SGH-M919
I've rooted my phone and was running a GE rom
Everything was fine for MONTHS
Got in my car and plugged my AUX cable to my phone for music and the phone froze.
Force rebooted the phone and it started boot looping.
Rebooted to recovery (TWRP) and TRIED to wipe dalvik and cache and it FAILED, said it couldn't mount dalvik
Rebooted to recovery again and wiped all partitions and this time it worked so I proceeded to re-install GE rom, still bootlooping
Came home and tried to use ODIN to flash M919UVUAMDL and it failed.
Tried ODIN to flash M919UVUEMK2, also failed (sorry don't have the error messages right now)
Rebooted phone into download mode again and phone said there was an issue and to use Kies to recover
Installed Kies and started emergency recovery and that went through fine and the phone finished and STILLLLLLL BOOT LOOPS !!!!!!!!!!!
Copied the file that Kies downloaded (M919UVUFNB4) and tried ODIN again to flash that and it flashes fine but STILLL BOOT LOOPS
Obviously my Knox warranty flag is tripped and I don't have the money for the insurance right now.... so PLEASE FOR THE LOVE OF BOB does anyone have any other diagnostic tips or tricks to help me figure out why the F this phone is boot looping.
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
avelis26 said:
53 views and no replies.... come on people... someone HAS to have something that might help..
Anyone know if ANY possible way to reset the knox warranty void flag ?
Click to expand...
Click to collapse
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
lalec said:
Only Samsung can reset your Knox flag. You can't expect instant responses here. People read and answer the questions they know how to. Not doing a full wipe before installing a different ROM often causes soft bricks and bootloops. I would start there although that doesn't explain why you couldn't mount Dalvik. Try a different recovery. Many people have had trouble with TWRP. Philz Touch works well if you haven't already tried it.
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
1. Samsung WON'T reset my flag... they won't even TOUCH the phone in any way shape or form. I spent almost two hours dealing with them and being honest about the situation. And they STILL won't do anything at all. The rep I was speaking too even said the first thing they do is check that flag and if its popped, they put it back in the box and send it back with no further action. So I will not buy form Samsung ever again.
2. I'm not expecting instant responses at all and nothing I said should have been interpreted at such. I made the comment of 53 views in 4 hours and not a single reply ... I was hoping for a better ratio of responses than that.
3. Where are you getting "Not doing a full wipe before installed a different ROM..." I never said that I didn't... and if you read what I took the time to organize neatly, I specifically state that full wipe was what I tried BEFORE re-installing the SAME rom.
4. Can't try a different recovery if I can't even get the stock factory image to do an initial boot.
cybervyrus8587 said:
I literally just had the exact same problem as you. I googled and found http://forum.xda-developers.com/showthread.php?t=2265477, then googled some more and found my .tar file for my phone, then odined back to stock 4.2.2. It took 20 min.
Click to expand...
Click to collapse
Which one did you flash ?
M919UVUFNB4
M919UVUEMK2
M919UVUAMDL
M919UVUAMDB
I've tried #3 but it gives me an auth failure....
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
avelis26 said:
lol ummm ok I'm glad to hear that but how would flashing a recovery fix the fact that the factory stock image won't even work Not being a ****... I really do want to know
Click to expand...
Click to collapse
Post deleted
☞ Sent from here ☜
baseballfanz said:
Post deleted
☞ Sent from here ☜
Click to expand...
Click to collapse
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Ok so .... I guess installing PhilZ... then full wipe, then flashing M919UVUFNB4 TWICE back to back did the trick.... no freaking clue how but it worked
I spoke too soon. Went through first boot. Got all the way to the end setup and then it rebooted on its own ... and now its stuck in a boot loop again
avelis26 said:
Sooooo umm what ?
Anyway... I flashed PhilZ on my phone, did full wipe, tried installing the same GE rom I was using... didn't work.
Tried installing stock rom, didn't work.
Tried flashing M919UVUFNB4 via ODIN... and it flashes fine but again, first boot wont work.
Click to expand...
Click to collapse
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
TigerDNA said:
Since your using philz, choose install new ROM, then go to advanced and wipe dalvik, THEN go to mounts and select the one close to the bottom, wipe SD/data or something..... This will wipe your internal SD, OK so then install your rom and reboot.....
I am starting to think you flashed a non GE kernel and didnt realize it You just got to give the phone some love, thats all. It knows when your upset you know.
Click to expand...
Click to collapse
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
avelis26 said:
lol
The weirdness continues
sooo it started boot looping again. Then I rebooted to recovery (which obviously after flashing NB4, its no longer PhilZ) and did factory reset. Now its working again with latest firmware.
Also I flashed the GE rom from HERE in XDA and used it for like 2 or 3 months then it suddenly stopped working so I don't think the kernal was the issue... I'm so freaking confused
Click to expand...
Click to collapse
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
TigerDNA said:
Flash something else, GE is boring, Flash something crazy like Slim or something, that might work... Possibly it could be a bootloader issue, did you ever get on the MK2? Maybe you got one of the female phones. Sammy made some by mistake. they can be real finicky every now and then, like they work just fine most of the time, but about once a month or so they just crap out. Could be that too.
Click to expand...
Click to collapse
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Yea your Knox flag is tripped alright, you have zero chance if ever getting back to 0x0.... Nobody knows how to do that brother.
Sent from my GT-I9505G using xda app-developers app
avelis26 said:
No never got MK2... went straight to NB4
And I LIKE GE lol...
Well whatever happened it seems stable again now currently on stock NB4
Next thing to check is if the knox warranty flag is still tripped... Do you know how to do that ?
Click to expand...
Click to collapse
Just put the phone in download mode. Power off then volume up, home and power. You'll see it when you get into download mode.
TigerDNA said:
Just ODIN philz on there. TWRP has given me issues on this phone off and on. Philz will let screw around in there. Your phone isn't dead, it just needs some love
Click to expand...
Click to collapse
Philz's and TWRP both had small glitches on the GS4 4.2.2 Stock Rom.
I downloaded and installed the OUDHS-Recovery-jfltetmo-1.0.3.3.tar and have it all PERFECT now! You can search using exactly that filename and download it for your use. IT IS THE flashable Recovery Version.
I can, using Rom Manager, NAME THE BACKUP before booting into recovery, and it makes the backup just as I named it!
I can also recover using Rom Manager, and visually select what backup file I want to restore to, again, before booting into recovery!
CWM type backups take longer then TWRP backups to complete, but I have not had any instance that a backup I made couldn't be restored.
I did have that problem using "TWRP" and "On Line Backup". (No longer do I trust using those)
Hope this info helps your decision!
Good Luck and Aloha!