Database Users

Help rooting phone. Trouble getting green recovery screen.

So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.

Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App

creglenn said:
Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I went into ROM Manager and clicked "boot into recovery". Where it brings me to the blue recovery screen. So you think I should unroot then re root? Because everything with the root seemed to work fine. It installed superiser and I had no problems downloading Titanium Backup or ROM Manager and allowing superuser permissions. Which made me think I was just forgetting something...but I might just try that. Thanks!

if your rooting stock 2.2 your gonna need a modded 3e recovery or one of supercurios voodoo kernels with CWM & root already built in. Superoneclick will root stock 2.2. If its 2.1, then you may need to hit reinstall packages a couple of times to get it to take.

drscott333 said:
So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.
Click to expand...
Click to collapse
All you should need to do is hit reinstall packages again. When you do it the first time it will boot back into the same blue recovery again. Hit it once more then it should boot to the green recovery. If that doesn't work you probably have a bad zip file on the phone. In which case you'd re flash CWM again.
If you're not getting the superuser request when you flash CWM then root didn't take. Make sure root works first.

Did you actually run install cwm from rom manager so the update. zip is there?

Just make sure with Astro or another file manger that you have a .zip file and it should be 1.72 MB in size and you want that on your internal SD card....Then when you boot to recovery it should let you hit reinstall packages with no problem

I'm new here, but I have flashed 3 vibrants since last week. I had the same problem you did.
When I flashed my phone last week it was stock 2.2, so I had to flash the modified 3e recovery which fixed my issue getting into CWM to install my ROM. Today i was flashing a co-worker's vibrant who also was on stock 2.2. However, on his it would keep rebooting when reinstalling packages, even though i did the 3e recovery flash. I ended having to Odin back to 2.1 on his phone before i could flash the new ROM.
I just used AIO Vibrant Toolbox 2.5. Hope this helps.

Thanks for all the feedback!! I don't have the phone with me to check if the update.zip folder was for sure there. But if it is, I'll try reinstalling the packages again. Otherwise I'm just going to unroot and try rerooting with the AIO Toolbox. I'm not going to be able to do this until tomorrow though since our work schedules were pretty much opposite today. But once again, huge thanks to all of you!!! However I've never unrooted before...if I haven't flashed any ROMs, I shouldn't have any problems should I? Just click unroot?

[Q] Internal memory volatile?

I can't seem to get a stable rom on my phone anymore. I noticed when I upgraded to triforce rom 3.0 some of my apps were disappearing randomly on reboot (all installed on internal mind you). After doing a full complete wipe and reinstall I cannot reboot my device anymore. I install the rom go into it once and that's it. If I reboot my phone for any reason it wont go past the samsung galaxy s4 logo. I even restored a nandroid of my forcerom 2.0 that I had backed up. It's showing the same issue of not being able to restart. Does anyone have any ideas? or is my hardware screwed.
To make clear of what is happening
wipe
install rom
boot into rom (everything is cool/works)
restart phone
stuck at black screen with galaxy s4 logo
can still boot into TWRP, but not the rom

Quiksmage said:
I can't seem to get a stable rom on my phone anymore. I noticed when I upgraded to triforce rom 3.0 some of my apps were disappearing randomly on reboot (all installed on internal mind you). After doing a full complete wipe and reinstall I cannot reboot my device anymore. I install the rom go into it once and that's it. If I reboot my phone for any reason it wont go past the samsung galaxy s4 logo. I even restored a nandroid of my forcerom 2.0 that I had backed up. It's showing the same issue of not being able to restart. Does anyone have any ideas? or is my hardware screwed.
Click to expand...
Click to collapse
To update right now, in TWRP Internal Storage (0MB)
When I format in TWRP the internal storage went back to (9673 MB)
Once I format the storage and restart the phone I'm able to get past the Black galaxy s4 screen and get to the boot screen, but since there obviously isnt a rom installed it wont go past that.
It looks like after the reboot (where I can't boot into the rom anymore) the internal storage is labeled as "(0MB)"

Something must have gotten corrupted and your best bet is to star new, I would download the stock mf9 tar. Do a factory reset and then install the tar through Odin. That way you are starting from scratch with everything working , hopefully. Then use cf-autoroot to root the phone and install whatever recovery you prefer. At that point, I would make a nandroid of your stock rooted rom so its easier to restore if you run into problems again.
Sent from my icrap 2 using Tapatalk HD

Im having the same exact problem... I did a mdc full restore in odin. Wiped internal storage and my sdcard and im going to try to root and flash again...its got me stumped.
Also when u try to install rom after u flash does it say ur device does not appear to be rooted?
Sent from my SPH-L720 using Xparent Red Tapatalk 2

noXcape said:
Im having the same exact problem... I did a mdc full restore in odin. Wiped internal storage and my sdcard and im going to try to root and flash again...its got me stumped.
Also when u try to install rom after u flash does it say ur device does not appear to be rooted?
Sent from my SPH-L720 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
didn't have that issue of "device does not appear to be rooted"
I was able to fix my issue. I downloaded the rooted stock rom listed below along with stock kernal and recovery.
Download Odexed With Data Wipe Zip
MD5: 6700c52d8a9f7d6c0ff8d6cb453b74a1
Download Stock MF9 Kernel
MD5: ae6e8712be9492d4de374ade043851b5
Download Stock MF9 Recovery
MD5: f843028f419e68aedda2742ce65405a9
from thread: http://forum.xda-developers.com/showthread.php?t=2357471
I formatted everything in TWRP, I then installed the odexed with data wipe zip, followed by the kernal, followed by the mf9 recovery. I then booted into the new recovery after flashing (stock recovery) and did a factory reset. I booted into the stock rom and did a reboot. It worked. Once I verified I was back by restarting a few more times, I installed goo manager and installed twrp from there. After that, I went into TWRP and continued along my merry way of flashing back to my custom rom.
Throwing out all details I can for anyone else that experiences this problem. Thanks!

cruise350 said:
Something must have gotten corrupted and your best bet is to star new, I would download the stock mf9 tar. Do a factory reset and then install the tar through Odin. That way you are starting from scratch with everything working , hopefully. Then use cf-autoroot to root the phone and install whatever recovery you prefer. At that point, I would make a nandroid of your stock rooted rom so its easier to restore if you run into problems again.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the help!

[Q] I guess I bricked my phone. Can't restore via ODIN. Options? -Solved-

Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
**EDIT**: Just did format on /data on stock recovery and it seems to have booted... False alert guys. Soft bricked, but nothing else.

Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app

Blaze9 said:
Alright so here's what I did, and how I got to my current situation and what the situation is.
What I did:
Had CM10.2 working fine on my rom. Recovery was TWRP (latest). Decided to flash PAC 4.3 cause I really like that rom. Flashed PAC 4.3. Worked fine, decided I wanted to restore titanium backups. Read in a few places that I needed to flash the SuperSU zip from chainfire. Downloaded the latest version from him and flashed in TWRP. TWRP took a -really- long time to flash the zip. After it finished I restarted the phone Wouldn't get past the samsung screen. Uhhh okay no problem.
I still have access to TWRP right? Yup, Still do. Do a full wipe and flash PAC 4.3 and Gapps. Flash is taking forever again. PAC gives no information at all (none of the usual ASCII artwork or anything). GApps loads the installer script but I get a can not mount /data and can not mount /system error.... Oh ****. Now I'm worried.
Download the PDA file from the sticky in the general section. (I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5) Pop the phone into download mode, and flash the PDA file via odin. Great, everything's going well. It flashes System, Flashes recovery, and everything else. Get a message saying All threads completed, Succeeded 1/failed 0. Awesome Right? No....
Phone restarts, goes into the stock recovery screen while something happens and restarts again. Now the phone's stuck on the samsung screen again. I can still access download mode and still access recovery (stock). When I access stock recovery it says "failed to mount /data (stale NFS file handle).... can't mount /data (stale NFS file handle)... E: failed to mount /data (stale NFS file handle).
Now what?... What can I do to fix this?
Click to expand...
Click to collapse
Did you try factory restore / reset in recovery?

Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...

goobieracing said:
Did you try a factory reset in stock recovery? Or maybe try odining the pit file also that somewhere on the forum. Maybe your partitions got corrupt flashing some how.
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.

goobieracing said:
Did you try a factory reset in stock recovery?
Sent from my SGH-M919G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
scott14719 said:
Did you try factory restore / reset in recovery?
Click to expand...
Click to collapse
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
---------- Post added at 02:52 AM ---------- Previous post was at 02:50 AM ----------
It sounds like to me you need to do a lot more reading and learning before you do anything else. It has been a well known fact, and widely discussed in the AT&T S4 forums that a factory reset needs to be done after flashing firmware in ODIN in order for the previous data to be wiped from the phone and for it to boot up again.
Click to expand...
Click to collapse
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.

Blaze9 said:
Sorry, I forgot to update. The second I posted this I tried to go into the recovery and do a stock wipe. it worked. Thanks for the tip regardless!
I wonder why stock recovery was able to fix it, but TWRP wasn't? I did /data wipes on both recoveries...
Click to expand...
Click to collapse
I had to do a stock reset recovery the other day for something like this. Probably just left over files from previous stopping it from booting.
scott14719 said:
Odining the PIT file is a bad idea. At best, it will not work, at worst, it will cause a hard brick
A. Regardless of what anyone has said or what ODIN reports, there is no evidence that the PIT files that are pulled from AT&T phones work on any other device than the one it was originally pulled from. Signing issues are to blame.
and
B. Messing with PIT files can hard brick a phone that was only soft bricked. PIT files (when they work) must be accompanied by a firmware files or else no data will be on the phone.
Click to expand...
Click to collapse
Sorry I learned something new today. Back in the infuse 4g days whenever I'd odined back to stock I always used the pit. I was under the influence that set everything up the way it came stock. Hope to see some of your work coming to sthe s4. Maybe you help the sense port going on in the international thread lol. Not trying to add work to ur day but I OK know if u, jt, and entropy can bring ICS to a out dated phone u might have the skills to ad your 2 cent.
Sent from my SGH-M919G using XDA Premium 4 mobile app
---------- Post added at 02:18 AM ---------- Previous post was at 02:01 AM ----------
Blaze9 said:
Ah, I never had to use ODIN on the S4 before. Didn't know that. On my S2 I didn't have to wipe after flashing via ODIN.
Good to know, anyway. Thanks.
Click to expand...
Click to collapse
I had to Odin to stock the first time two days agao but mine booted and I only had stock recovery. When it started up the ROM everything was crashing and that's what fixed it. Glad you fixed it though.
Sent from my SGH-M919G using XDA Premium 4 mobile app

Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.

gerard0986 said:
Pretty much got the same problem. Seems that somehow my device encrypted itself and since I didn't know...I don't have a password to give it. So I got a encrypted device that can't be decrypted, thus, I can't format, install, wipe, etc. Not sure if you got the same, but mine is about the same symptoms.
But is it ok to flash "I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5" on mine? Kinda confused with all this MDL, MDB, and MF3 stuff. Mine was an MDL. So is flashing MDB stock ok anyway? Or should I find the stock for MDL?
EDIT: Just flashed MDL stock anyway. Worked fine and now I'm starting from scratch. No more problems so far. I might stay away from TWRP for a bit now though. Surprised there isn't a guide or warning for this problem though.
Click to expand...
Click to collapse
The PW TWRP asks for? IT's just TWRP, if I remember correctly.

Major Problem using TWRP

Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.

doesntmatterx said:
Hey guys, I am not new to this scene and have been running, flashing, roms since the S2. Today I ran into a major problem I cant seem to fix. I am running TWRP 2.5.0.2, always have for about 4 months with no issues. Today I did a complete Titanium Backup + recovery backup of my rom. After that I wiped for a fresh new rom install and noticed the rom I placed onto my internal storage is not there (it was def there in its own folder but through TWRP its not there). No biggie right? Just mount USB storage and put it somewhere else that TWRP can get to, but then USB wont mount on Windows now. No biggie right? Ill just restore the rom, put it in another directory, then wipe and reflash. However none of my backups are showing up when I hit restore, I had like 3 backups and everything is gone.
At this point what do I do? I tried everything to mount usb from recovery but windows wont take it (win 7). Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)

doesntmatterx said:
Nevermind guys I was able to get around it by putting the SD card from my S4 into the S2 and putting the rom files into another location. Once that was done placed it back into the S4, booted into recovery and flashed it. (phew!)
Click to expand...
Click to collapse
:good:

xBeerdroiDx said:
:good:
Click to expand...
Click to collapse
I take it back, stuck in a boot loop even after 2 fresh ODIN unroot tasks. Nothing I do gets me out of this, been a long day getting longer now

Can anyone help? Been at it for hours, I have tried everything, phone still reboots at the Samsung logo (the bluish one )
Unrooted 3 times
Launched stock recovery, wiped factory reset
wiped partition cache
removed battery
Cannot connect to Kies for Emergency restore.

Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900

seanpr123 said:
Did you do an internal 'sd card'/media data wipe?
Best bet would be to Odin back to stock and start from scratch:
http://forum.xda-developers.com/showthread.php?t=2261573
Then from there just use casual to root and install TWRP in one easy step and you're back:
http://forum.xda-developers.com/showthread.php?t=2297900
Click to expand...
Click to collapse
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.

doesntmatterx said:
I know what I did, I was using Touchwiz and instead of doing a regular wipe I did a format and input "YES". I heard TW has major issues with this and thus screwed me up completely.
To add to my list above I tried this method and also did not work. http://androidfannetwork.com/2013/05/02/fix-your-soft-bricked-att-samsung-galaxy-s4/
Sean, I flashed from Odin like 3 times, how can I install TWRP if I cant get the phone to load up (boot loop)- Ill read up on casual. Thanks.
Click to expand...
Click to collapse
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.

Should I ODIN with the RE-Partition Option?

Just Odined again and no dice. I booted into stock recovery and noticed after wiping factory I get "Can't open /efs/log/boot_cause" which pointed me to this fix someone on the Galaxy note forum said they did and it worked but I dont understand the steps, need some elaboration.
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4

jd1639 said:
Did you do a factory reset in the stock recovery after Odin? That'll usually get you past the boot loop.
Click to expand...
Click to collapse
Yep did that mulitple times, also did wipe cache partition in the same stock recovery. I get to the Samsung logo where the blue halo spins around the name, then it freezes there and reboots.

Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day

seanpr123 said:
Hmm, never had to mess with EFS stuff on our phones before.
Did you make a backup ever in TWRP by chance?
Sorry if you tried the stock recovery options there's not much more I'm familiar with.
The good news is since you were able to Odin and get 3e back, you are technically warrantied again and could work with AT&T to get a new phone since your phone just stopped working out of the blue one day
Click to expand...
Click to collapse
LOL thanks, yes I may have to do that. I had a backup and it was wiped.

Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.

doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Try flashing using cwm. It'll probably work fine. Then you can go back to twrp. That's worked on other devices. Seems one you flash it once with cwm then twrp works from that point forward. Idk why

doesntmatterx said:
Anyone have any suggestions at all? I can't be the only one who has had this boot-loop / partition problem without a fix... or maybe I am lol.
Click to expand...
Click to collapse
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app

jds3118 said:
Did your odin flashes include the pit files ? Have you tried flashing twrp or cwm with odin?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I tried flashing with a PIT file I found online but it fails through ODIN everytime. I tried on multiple versions of ODIN as well. I also cant seem to find readily available PIT files to test as well, (perhaps the one I used does not work). Also I did try to flash a CWM through ODIN but failed, but again there isnt anything that I have read that says "hey you can do this that way and it will work".
From what I understand I need to be rooted to install CWM or TWRP, and since I unrooted to try and fix the problem I cannot root myself through conventional methods. Everything I found online requires the phone to completely start up. (to the menu screen etc)

What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.

jd1639 said:
What stock firmware are you flashing with odin? I get firmware from sammobile.com. since you had a custom recovery I'm guessing you where on mdl firmware to start with.
Click to expand...
Click to collapse
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.

doesntmatterx said:
I never flashed a custom recovery through Odin < I can try that though, where can I get one? Im assuming this firmware will have root with CWM or TWRP?
Ive only flashed using official Samsung firmware from sammobile.com I tried both that are available for SGH-I337 with the PIT file as well and no dice.
Click to expand...
Click to collapse
Do you know what firmware you were on? Was it mdl or mf3?

Flashed ROM in TWRP - custom recovery + root gone?

I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong

Depends on what custom rom you were installing.

Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.

Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom

XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.

Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?

Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data

Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful

Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done

XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?

Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.

Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers