Develop Bugs

[Q] What Am I Doing Wrong...?

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.

[Q] I wished upon a shooting star... and this brick still isn't fixed.

Hi xda,
I ran into a problem I've never faced today. Before you start assuming, I've done my research. I've searched all over the forums, tried multiple solutions (none worked) and... potentially permabricked it?
Rooted for 7 months, running Jedi Mind Tricks v5.1 Android 4.0.3
How it happened: Today I noticed my phone running really wierdly. It would crash apps constantly, which didn't happen yesterday. So I put it on *close all apps after exiting* on developer options and limited it to run 2 background apps. Throughout the day, my phone would just restart out of absolutely nowhere: in the middle of a text, after unlocking my phone. Each time progressively got shorter between the restarts. It would also freeze a lot of the time. This never happened before today. Maybe a freeze or two, but not this bad.
Did a few battery pulls, no dice. Then this is where it gets worse. The time between boot loops were from 1-2 minutes now. I was getting pissed, so I decided I needed to wipe it and install a new rom. I enter recovery mode CMW 5.0 and do an initial factory reset. Half way through, it crashes again. Now all it does is vibrate constantly until I turned it back on into recovery. Launches recovery. I try to super wipe it. Half way through, crashes again. I try this several times in conjunction with battery pulls. Doesn't work.
I pull sim card, SD card and battery out, let it rest before I reset it.
Then I tried to Odin its ass. I bricked it into the yellow warning screen about a updated system error because I fail with Odin. I searched around to find a solution. I redid Odin to stock kernel it. When it revived, it went into the loading screen. Yes! Progress! It was 99% done with loading when it froze on it. Fml. Battery pull, reboot, and it goes back into its habitual boot loop pattern. I can still access CMW, but it still crashes when I try to super wipe/wipe it.
I have to fix this because, well I bought this from someone with no warranty and using a no contract provider.
Help?

UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.

eaudexs said:
UPDATE: I was able to successfully superwipe my phone, then reinstall Mind Tricks as the rom of choice onto it. It doesn't freeze. Simply bootloops again and again. I don't know what to do.
Click to expand...
Click to collapse
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

elesbb said:
Firstly I suggest upgrading your recovery to 6.x via odin. Then superwipe. Redownload mind trick fresh, flash mind trick, wipe data/factory reset via recovery and try to boot letting it settle for about five minutes. If this fails, flash back to stock via Odin to rule out hardware faults.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been looking through some how-to's but I can't seem to find how to upgrade recovery using odin. I can only find the .img file and instructions on how to do it via command lines. Any advice?
Thanks

Good suggestion but better yet ...... I had the same issue on cwm.... get twrp 2.2 look for the flashable download....... 2.3 has a few bugs so stick wit .2
Sent from my SGH-T989 using xda app-developers app

Definitely get twrp on it. Flashing twrp solved 99% of my problems running cm10. Zero rr in weeks. If I were you I would go back to stock for your device. After confident its running like it should. Then root and and go nuts.
I've personally never really had to pull the battery, very rarely. I'm worried about your ram. Could it b corrupted? A short somewhere? All unrecoverable.
I wonder if you could somehow mount your device using Linux. And run memory tests or drive diagnostics.(just thinking out loud).
Twrp is definitely a must. Good luck
Sent from my cm_tenderloin using xda app-developers app

Try doing complete wipes and reflashing a different more stable rom and see if it happens again. There are scripts to do complete and total wipes just to make sure you get a clean install (kind of like the others suggested) atleast yours can turn on so your not hard-bricked.

That's great how you guys are saying twrp solved your issues! It's really funny when cm10 supports cwm recovery. But op, let me see if I still have mine.
Sent from my SGH-T999 using Tapatalk 2

Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!

eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
my sgs2 did this last month i did the same you did. after no fix i installed a cwmtouch through odin just to be able to restore a back up and worked flawlessly. After that i switched to TWRP again flashed it with no problem through odin and my s2 has been working fine ever since, but fyi i updated twrp to its 2.3.1.1 version and now i get errors can still restore but cant flash jb roms and can only do dirty flashes of ics roms

I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?

eaudexs said:
I'm currently in the process of trying to flash twrp. Is it uncommon that when I went into recovery, it also boot looped on me several time?
Click to expand...
Click to collapse
what version of TWRP are you trying to use? NO it does not bootloop

I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.

eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Nah my man you do not use the script with CWM6 thats your problem right there
---------- Post added at 03:39 PM ---------- Previous post was at 03:38 PM ----------
eaudexs said:
I did a full wipe, script wipe, with Darkside using CMW6 and restored an old backup. It still crashes. I'm starting to think it's hardware problems. I haven't gone to TWRP because I can't find a flashable 2.2 version.
Click to expand...
Click to collapse
Come on now the flashable version is in the thread...tisk tisk tisk also there are a few version in flashable form in there as well my friend. Got to get your hands dirty sometimes.... LOL Good luck
http://forum.xda-developers.com/showpost.php?p=32984410&postcount=380

Thank you my friend. I was able to finally find a 2.2 TWRP and I flashed it via odin. Did full wipes, full cache wipes, flashed a rom. Fixed permission and all that good stuff. Left it off for 10 minutes. Came back, it started running through initialization. About 4 minutes in, it crashes again. I'm starting to think this could be hardware problem.

eaudexs said:
Thank you guys for all the suggestion. I was able to finally install CMW 5.5 on Odin, then go to 6.0 through flashing it. Then I super wiped it several times, normal wipe data/user settings, Darkside super wipe, then install Jedi Mind Trick X, super cache wipe, mount system, then rebooted. It worked for several minutes before locked on boot loop again.
Can someone post the link to TWRP touch for flash? That would be awesome.
I've also been thinking if it could be an external hardware problem and not a software problem. How could I run the diagnostics like you had suggested?
Thanks!
Click to expand...
Click to collapse
Do not use scripts with the new CWM 6 as it will cause this. Manually wipe everything and do not use scripts. You can use scripts with twrp but not the latest cwm
Sent from my SAMSUNG-SGH-T989 using xda premium

Galaxy S 3 Rom installation Problem

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 :/

SGS III L710 Unable to Mount /anything

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

4.3 General wiping and preparatory instructions - Sprint Galaxy Note 2 L900 all ROM's

I was happy as a lark with TWRP. But 4.3 happened and it is a new process. There are variations, here is one way to get your phone and 4.3 to play nice together. I'm on Sprint Galaxy Note 2 and if you are coming to a 4.3 or 4.4 for the first time, or having trouble. Try this first! I give credits Below, but it's for all ROM's. "Google process stopped" is a common sign that this wasn't done. Or if it just hangs on the samsung screen... Btw it does seem like an eternity sometimes. Lol
General theory: skip to the next paragraph if you dont care. I've Googled and read. You should too. We are trying to clean and prepare your phone for 4.3. "Wipe" is not the same as "format. " We need to remove all the little pieces of data that may still be there from before. We need to start fresh. Also, the partitions sizes are different in 4.3. In general we need to clean.
PROCESS A is this link. Billard412 This is back to stock, completely cleaning your phone. It requires odin and a computer. If you want to try procees B alone, you can skip A and just do "process B" and see if that works. If you still have trouble, you know you need to do the full thing. Just a note, you might think it works, but then your nandroids don't restore.. Time for process A. Back to stock. It's good to do this once in a while to start fresh, also.
http://forum.xda-developers.com/showthread.php?t=2086769
Then install USE PHILZ recovery 6.07.9 (link below)
-Install philz. Some people have luck with TWRP , i didn't. I don't think TWRP works with 4.3
There is a newer Philz version, not sure all the bugs are worked out, use 6.07.9
One thing that might be confusing, the process A restore from billard recommends TWRP and I'm recommending Philz recovery. So best advice, although possibly confusing, is install TWRP, billard restore, then flash Philz. It's not any more work really. The back to stock will put you in a stock recovery. So you have to flash something. I was a TWRP fan too, but Philz has had less problems in 4.3.
1. You can follow billard 's instructions
2.there is a YouTube if you want to follow that in billards thread
or3 . Jlmancuso provided this to try and simplify the process:
a. Boot into download/bootloader mode.
b. Connect to pc and use odin to flash TWRP. Make sure you uncheck reboot and flash twrp in the pda slot.
c. Once flashed pull battery and disconnect from pc.
d. Press vol+ menu power buttons while inserting battery (yes it is difficult but can be done)
e. Now in recovery perform factory reset.
f. Flash this http://forum.xda-developers.com/showthread.php?p=36388145
g. Now reboot it will act/look weird but dont worry this is normal. It will reboot and take a long time to boot.
Now you are on stock mc2 (no knox anymore). Root using cf autoroot http://forum.xda-developers.com/showthread.php?p=33278464
Now use odin once again and flash your recovery again, this time Philz. Now you are rooted and have a custom recovery. Oh and you have a working phone again.
PROCESS B.
This is done before any ROM install and before any nandroid restore.
Preparation: BACK UP INTERNAL IF DESIRED, I WILL RECOMMEND WIPING IT in the next steps . NOT REQUIRED, BUT RECOMMENDED. You can move it to external, external doesn't need to be wiped.
In PHILZ recovery 6.07.9 (link below)
1. Mounts and Storage
Format / system​Format / cashe​Format / data​ Recommended optional. Format internal SD card
Format / data and /data /media (/sdcard) ALL INTERNEL SD CARD DATA IS LOST.​PREVIOUS IS NOT EXTERNAL, EXTERNAL IS "SDCARD1" which i would not recommend
2. Power Options > reboot recovery
3. Wipe cashe partition
4. Advanced > Wipe dalvik cashe
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
I would stick with 4.3 and Philz backed up things. Don't restore something from before. Neither a 4.2 rom or a TWRP backup. Once you know you have got this process down, then try / do those sorts of things. Philz is supposed to be able to do that, but let's keep it simple until you have this figured out.
If you want to try process B first only , it may be all you need. But if it doesn't work, do all of it.
I hope this helps - LINKS & CREDITS in next post

4.3 general wiping and preparatory instructions
LINKS
same as above Billard412 back to stock - http://forum.xda-developers.com/showthread.php?t=2086769
alternate back to stock - Rwilco http://forum.xda-developers.com/showthread.php?t=2591898
Philz Recovery Thread - http://forum.xda-developers.com/showthread.php?t=2552653
On the Philz recovery site the "L900" looks more like "l900" and is confusing - so here is a more direct link - select 6.07.9 http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900
TWRP http://teamw.in/project/twrp2/117
To get root- one option is CF Autoroot-
[SPH-L900] CF-Auto-Root
http://forum.xda-developers.com/showthread.php?t=1956180
WIFI FIX just in case. Flash in the PDA tab of Odin http://d-h.st/6qX
If you want to change modems i use this (not required / optional) - http://forum.xda-developers.com/showthread.php?t=2537713
General
I am not trying to take credit for anything. Notice how none of this is my work. Just hoping to pull together and clarify this process. Others my post different ways, and you can try other ways, but if it doesn't work, use this process exactly. It works for many. If you want to post that you tried another way and it didnt work, you are welcome to, but then my reply will be to try it this way...or i wont reply. I just had to keep typing this over and over to many, and i figured I would put out a detailed version. This works. (you know the drill, its your phone, not my responsibilty, of course)
CREDITS AND ROMS
I picked up a lot of this process from Lorjay589's thread. His OP pointed me at the Billard412 back to factory
jlmancuso has posted refined and explained this process 100 times as well.
this is for SMOOTHEST ROM, CUSTOM ROM, SYNERGY ROM, DIGIBLUR ROM, FTW ANNIHILATION, ROM AND MANY OTHERS.
therfore jlmancuso, chaz187, ianmb, digiblur, lorjay589, rwilco12, phil3759, fryingpan0613, jimmydene84, cbucz24, wwjoshdew, agent soap AND MANY OTHERS.

constructive criticism is always welcome i have a tough skin, just be nice and don't hold back to let me know. i am not that knowledgeable, this is my first thread. Just been following some 4.3 threads for a while and saw a recurring problem.

Very nice guide Cole
Sent from my SPH-L900 using Tapatalk

Reserved

Darn it I want a reservation too!!
Thanks now I have a thread to link to instead of a single post.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Very nice tutorial. U nail all that we need to do for a smooth install
Thanks
SGNote2

Any reason why we should not use the latest version of Philz Recovery version 6.15.4?

justppc said:
Any reason why we should not use the latest version of Philz Recovery version 6.15.4?
Click to expand...
Click to collapse
Some people have just had some problems when using the new version, therefore the previous version is more reliable. Better chance of everything working. Once you have your phone running smoothly using this process, you are welcome to try it. If you have problems... Revert back.
Start with post 87 of the Philz thread, if you like.
http://forum.xda-developers.com/showthread.php?t=2552653

Thanks, this resolved an issue with 'Inconsistent System UIDs"

KNOX with options A/B
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks

Dedline said:
Will this process A or B or both, untrip your knox and reset everything to stock? Or does it just get you closest to stock as you can, with KNOX still tripped?
Thanks
Click to expand...
Click to collapse
Process A completely wipes your phone and resets it to stock. B is just general wiping process when flashing a new rom. You shouldn't have a Rom on your phone when you are done with either. (other than the one backed on you external sd)
Head on over the the Ballard thread to read more about process A

justppc said:
Thanks, this resolved an issue with 'Inconsistent System UIDs"
Click to expand...
Click to collapse
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?

mr.pope said:
This hasn't worked for me. I've repeated this several times with no luck. I also can't install gmail. Any suggestions?
Click to expand...
Click to collapse
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.

justppc said:
You could try to start all the way over by using ODIN to install stock MA7, then root it and take it from there.
Click to expand...
Click to collapse
alas, I have tried that as well. I finally made some headway and think I have it. I had to fix permisions for all apps using Rom Toolbox Lite Looks like that has fixed it. Flashing forward as I type.

Just a bump to keep this where everyone can see it.
Sent from my SPH-L900 using XDA Premium 4 mobile app

Gotta try this on my note 2
K
Sent from my SPH-L710 using xda app-developers app

Just a reminder

Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!

Lyvewire said:
Hello,
I ended up getting a replacement phone from Best Buy and I ended up flashing a older version of twrp before trying the latest 2.7.0. I did a few backups just to have a stock rom to return to if all failed. Somehow after I tried flashing the new mk4 roms, I lost my 4g LTE in the process of flashing different ROMS and none of my back ups for twrp would work so I ended flashing Philz recovery and then Digiblur just to get my phone working again.
I ended up requesting another replacement so I can have my 4g LTE again. My question is. Is it possible to wipe a 4g LTE key when rooting and also is Philz the way I should of went when I rooted to make a stock backup if everything fails? Anything I should make sure to back up in particular to make sure I dont wipe nothing important. I just want to be extra careful this time around.
The phone was already updated to MK4 when I received it. Any help is appreciated!
Click to expand...
Click to collapse
Philz is the only way to go when choosing a recovery. Twrp will not backup or restore mk4 properly and wont woek correct with 4.4 aosp either. When ypu do your first backup choose custom backup and backup everything but Efs. When that is done go back into custom backup and only backup efs (it must be done by itself). I would then suggest copying both backups to a pc or cloud storage for safe keeping.
Sent from my SPH-L900 using XDA Premium 4 mobile app