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.
I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.
ChronoXzX said:
I have a problem with my Galaxy S 3
When i bought it out the box i was able to root easily and install custom rom (Wicked) with no problems but then i had to restore back to stock using ODIN returning back to stock and running everything stock i also reset the counter beause i wanted to exchange the phone turn out i cannot
so i re-rooted the phone the same way and tried to install the custom rom it gave me status 7 error he only thing that worked is my Backups
so i returned back to stock again and re-root this time i didnt have the error i just get stuck at the boot logo
i have no idea what to do now. its very frustrating.
Click to expand...
Click to collapse
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help
Had that problem after Odin reboot into stock recovery and erase and reset, had to do it 2 days ago
Sent from my SGH-T999 using xda app-developers app
theory611 said:
same problem i had before. Bothered me for a few days.
1. download rooted stock ROM
2. download goo manager
3. user twpr to flash wicked ROM
hope this will help
Click to expand...
Click to collapse
Can you link me the rooted stock rom that you used
Plz ive tried everything its real annoying that my phone wont boot the custom rom
Its installed successfully but nothing after the reboot just the logo screen of the custom rom
Did you wipe the cache/dalvik?
psykhotic said:
Did you wipe the cache/dalvik?
Click to expand...
Click to collapse
Yeah I did
I do factory setting then I wipe cache then I do the dalvik cache
Then I finally install I do it everytime it doesnt work. Is it because maybe I unroot the phone wrong??? Is that even possible?? Lol
Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM
DroidDonX said:
Try This:
http://forum.xda-developers.com/attachment.php?attachmentid=1404381&d=1350325570
Flash this TWRP Recovery Through ODIN, and try to reinstall the ROM
Click to expand...
Click to collapse
ill try that when i get home
but note so far no rom has been working i can successfully install it with no errors
but when it wants to boot nothing happens just stuck at the Logo screen :/
i think its because i unroot using odin the wrong way or something idk but ever since i un rooted the device this started to happen..
I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.
jcbofkc said:
I think status 7 error is a md5 mismatch. Redownload the rom you want. Also some people have had issues downloading to the phone so use a pc and transfer it.
Click to expand...
Click to collapse
Ok ill do that but what if I dont get the error the rom finishes installing and the aroma installer says status 0 I do not know what it means
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei
Aerowinder said:
There are a couple possibilites here.
1) Your recovery is outdated. Update it. CWM will work just as well as TWRP. A lot of people have been advertising TWRP like they are being paid to do so. Either will work fine, but it must be updated to the latest version. The "CWM makes you lose IMEI" slander is starting to get old as well. There have been several documented cases on this forum where people have lost IMEI using TWRP. That's of course assuming the custom recoveries are actually causing it. We don't even know that. In any case, a reboot nvbackup would prevent all of this nonsense. I can't believe people still aren't doing this.
2) You are attempting to flash roms that are not for your device. Please give us a forum link to the rom you are attempting to flash.
Click to expand...
Click to collapse
I have the latest CMW recovery touch
tried it with both of the recoveries same deal :/
and the ROm im trying to flash is
http://forum.xda-developers.com/showthread.php?t=1804260
ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?
ANd noob question what happens when i lose my Imei?? does it brick or prevent installation?
Click to expand...
Click to collapse
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
mt3g said:
I would gladly take this slightly off course and ask you to find me one with the issue, as I've read lots and lots about the issue, it is and has been a CWM issue. Here are the Docs Spreadsheet
https://docs.google.com/spreadsheet/ccc?key=0Arzp20hXNPi4dFg3UUozS2FQaERYNVJRVm1hWmJYQ3c#gid=0
Click to expand...
Click to collapse
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
and here is the huge thread about the issue
http://forum.xda-developers.com/showthread.php?t=1794657&highlight=imei
Click to expand...
Click to collapse
What about it? I think I posted a backup script there a couple months ago.
Aerowinder said:
Might as well be a brick. Just back it up the way I said and you don't need to worry about it.
This spreadsheet doesn't prove anything. I see 18 CWM IMEI losses. 3 of which are on CWM v6. Out of 116 users reporting. The vast majority of reporting users are using CWM with success. This is hardly evidence. If anything, it implies CWM is more popular than TWRP. But, there is no proof of that in the spreadsheet, either. You would need thousands of reporting users to establish any kind of usable baseline. Last I checked, no one is sure why the IMEI loss happens or what, exactly, causes it. People do have their suspicions (or superstitions), though. I've flashed hundreds of files with CWM, and never had a single issue. And so have thousands of other XDA forum members.
What about it? I think I posted a backup script there a couple months ago.
Click to expand...
Click to collapse
But no one lossed it using TWRP, that's my only point. With out a doubt CWM is more popular, think of it this way. More people are going to respond and or look for a thread regarding the issue compared to those (TWRP) users who never had the issue, I've been on CWM for a couple weeks try to lose my IMEI and haven't done so yet. Either way I'm not defending either but trying to help people out.
Sent from my SGH-T999 using xda premium
When installing a Rom it just flashes through is that normal?
doesnt it usually take like 2 or 3 minutes to flash a rom that big?
because almost everyone rom i try
Darthstalker
furioustock
wicked
aeonflux
when i format everything using this guide
http://forum.xda-developers.com/showthread.php?t=1946701
The installation for the rom just takes 1 to 2 seconds i that normal?
since i used to have a samsung nexus s it usually takes about 1 - 2 minutes to flash a rom that is greater than 100mb
i just wanted to know maybe that can spark any conclusions.
i am still failing to install a rom and seeing it boot up pass the boot screen.. i really need help please :/
the recovery does not give me any errors at all its installed " successfully "
It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium
mt3g said:
It should take at least 20 to 45 seconds.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later
ChronoXzX said:
My phone takes 2 seconds to flssh it says starting flash please wait then it says complete about 2 seconds later
Click to expand...
Click to collapse
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.
mt3g said:
which is why it isn't working, how large are the files, what are download steps you are taking? Which recovery... You might have a borked recovery... Try reinstalling the recovery if all else seems normal.
Click to expand...
Click to collapse
the files that im trying to install into my phone are about 600mb +
the wiked rom is about 809mb
the darthstalker rom is about 776mb
im using internet download manager to download the roms
ive reinstalled the recovery via the apps ( rom manager and goomanager )
nothing seems to work :/
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
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
latrotoxin1986 said:
Alright guys, getting a little frustrated here. I'm trying to go from Carbon to OptimusDE ZVC, When I flash OptimusDE, everything boots up fine but there isn't data to start with. I go into settings to update PRL and as soon as it starts to update, the phone reboots. Try to connect to WiFi, the phone reboots. Also, Exchange Services crash immediately after boot up.
What I've tried - Re-flashing, wiping caches and then also doing a factory reset, flashing ZVC radio.
Nothing seems to be getting this working. Anyone know what I need to do to get things working here? Any help would be much appreciated. Thanks!
Click to expand...
Click to collapse
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
iamterence said:
Try flashing the new Stocktimus ROM and see if the same thing happens. If it does, you may just have to re-root.
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
I'm not sure how root would pertain to this issue. I'll give Stocktimus a try, but I tried engine's other stock ROM's a month or so back and had the exact same issue.
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
AFschizoid said:
Weird. Did you try actually activating?
Sent from my Optimus G using Tapatalk
Click to expand...
Click to collapse
The phone is activated, but trying to run the activation in settings causes reboot. Receives phone calls no problem. Just downloaded Stocktimus O and same thing. No data, crash on PRL update or Profile update, crash on WiFi activation. I really don't understand what's going on...
Yeah I've not had that issue and I've flashed back and forth from stock based to aosp and vice versa. Might be your efs got screwed up. Try lgnpst or LG flash tool (I prefer the latter because it takes it to an 'out of the box' state, activation required ) and try activating again
Sent from my Optimus G using Tapatalk
That has happened to me before going from an AOSP rom to one of the available stock roms. Don't remember which one.
But I remember flashing the TWRP recovery. I was on Philz Touch Clockworkmod.
And then performed all the required wipes and reset then flashed Stockimus-D and viola, no FC's. no reboots. No more problems.
If problems persist used TeenyBins via LGNPST
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
engine95 said:
A couple other things to try also:
Make sure you're wiping /system also.
Sometimes CM/AOSP Roms can mess up your SD. You may need to wipe it also. Just make sure you back it up first. That's happened to me a few times.
Sent from my LG-LS970 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
latrotoxin1986 said:
Lol, so funny story. I did LGNPST and got back to full stock. I had to use an oldddd ZVC .bin file, not a teenybin. Re-rooted, unlocked, put CWM 6.0.4.6 back on the phone and created a stock backup. I didn't mention before but I had long deleted my stock backups, so I didn't have a stock ROM on my phone at all to flash back to. Anyways, back on full stock, everything is working great, go into CWM, create a backup and flash Stocktimus O. It says it installed successfully, so I reboot...just the normal Sprint boot screen, everything is total stock. I'm wondering if perhaps, like a previous poster brought up, it's a CWM issue. I'll switch over to TWRP and give it a shot, report back later. I prefer CWM because I don't have any issues flashing AOSP ROM's whereas TWRP, on all versions I've tried, will fail with some ROM's while others work fine.
Click to expand...
Click to collapse
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
engine95 said:
So LGNPST got everything working. But when you installed Stocktimus O you got stuck on the Sprint boot screen?
Did you give it about 4min to make sure it booted up?
It should work with both TWRP and CWM. I installed with both when I built them.
I know you've flashed before, but just in case, wipe /system, /data, /dalvic, and /cache.
If you don't want to do this next part, I'll see if it's something on my end:
If it doesn't install with TWRP, could you wipe your SD and try it again? I know it'd be a pain, but at least it would let me know if I need to fix the updater scripts.
Make sure your phone boots up. Then in recovery wipe "internal data" or SD and reboot. Your phone should still boot as long as you don't wipe /system.
If for some reason it won't boot, you may need to ADB sideload a rom, or LGNPST again.
Just trying to cover everything.
Click to expand...
Click to collapse
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
latrotoxin1986 said:
It didn't get stuck, it just booted as though I hadn't flashed Stocktimus O even though it said it had successfully installed. Kinda weird...but it's definitely not on your end. I've done something, at some point, that has borked my ability to flash stock. I've thought about totally wiping SD....just LGNPST after that. I dunno.
TWRP didn't give me any different results. Same deal, just booted with the original Sprint screen, not your boot animation, nothing had changed...
Click to expand...
Click to collapse
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
engine95 said:
It's gotta be on the SD. I don't know how, or where, no file explorer shows anything weird, but CM/AOSP ROM'S have got to be putting something on it for it not to flash. I've had issues more than once when I've had to wipe my SD to fix it.
We gotta got you going so you can get us some more Carbon, LS970 style.
Click to expand...
Click to collapse
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
latrotoxin1986 said:
I'm TRYING to build it right now. Getting some really unusual errors. The last time I got one of them, I just restarted the build and it finished fine. This time though I'm getting Java Runtime Environment crashes though and something else...not sure what's up with that. Keep chipping away at it though
Click to expand...
Click to collapse
I had the reboot issue when it connected to data too when flashing back and forth from cm/aosp ROMs to stock. What resolves the issue for me is to use TWRP and go to advanced wrote and wipe everything EXCEPT internal. I used to have that issue all the time when using cwm recovery but philz recovery also seems to be ok when flashing back and forth hope this helps!
Sent from my LG-LS970 using XDA Premium 4 mobile app
I was hoping that someone could help me out with some advice. I'm having a lot of hiccups after installing CM11 (M12) and I thought flashing a newly downloaded and MD5 verified copy might fix some of the problems.
I originally had CWM installed on my e980, but I've recently swapped that out to TWRP 2.8.1.0. The issue that I'm seeing is that every time I try to flash a ROM, TWRP gives me an error that says CM 11 for my e980 isn't compatible with my device, which it's detecting as an LG F310LR (which appears to be a Korean variant).
Can anyone give me some suggestions on how to fix/bypass this? Flashing ROMS in CWM was working fine, but I've had a lot of problems with TWRP. So many in fact that I've reverted to CWM a couple of different times.
Thanks in advance!
racer25x said:
I was hoping that someone could help me out with some advice. I'm having a lot of hiccups after installing CM11 (M12) and I thought flashing a newly downloaded and MD5 verified copy might fix some of the problems.
I originally had CWM installed on my e980, but I've recently swapped that out to TWRP 2.8.1.0. The issue that I'm seeing is that every time I try to flash a ROM, TWRP gives me an error that says CM 11 for my e980 isn't compatible with my device, which it's detecting as an LG F310LR (which appears to be a Korean variant).
Can anyone give me some suggestions on how to fix/bypass this? Flashing ROMS in CWM was working fine, but I've had a lot of problems with TWRP. So many in fact that I've reverted to CWM a couple of different times.
Thanks in advance!
Click to expand...
Click to collapse
Did you ever figure this out, mine just did the same thing.
zole2112 said:
Did you ever figure this out, mine just did the same thing.
Click to expand...
Click to collapse
Use another version of twrp, that works for me.
Sent from my LG-F240L using Tapatalk
The same thing happened to me once , I had to do a full restore with the kdz , and redo everything.
but you can modify the build.prop or something and change it to your variant.
the thing gets messed up by the Unlocker app.
irt118 said:
Use another version of twrp, that works for me.
Sent from my LG-F240L using Tapatalk
Click to expand...
Click to collapse
Thanks. I'll try this tonite:
https://dl.twrp.me/e980/twrp-2.8.7.0-e980.img.html
If that doesn't work, I guess I'll have to revert to stock and start over.