Develop Bugs

Can't access CWM recovery

Whenever I try to get into my CWM recovery it takes me to the stock android recovery. I've been stuck at EG30 (which is rooted) for a while now. Is there some trick I need to know to get into CWM?

http://www.youtube.com/watch?v=jZRnH-_XZmM

Thanks, I had already installed CWM through the root method I used when I first rooted then phone and then afterwards by using CWM Rom Manager. I'll try using this method as well, but I don't have high hopes.

LPChris said:
Thanks, I had already installed CWM through the root method I used when I first rooted then phone and then afterwards by using CWM Rom Manager. I'll try using this method as well, but I don't have high hopes.
Click to expand...
Click to collapse
Use this to flash a new recovery. There's a free one somewhere but i'm too lazy to look.
https://market.android.com/details?id=eu.chainfire.mobileodin.pro
---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------
Also don't ever use ROM manager to flash a recovery.

CBowley said:
Also don't ever use ROM manager to flash a recovery.
Click to expand...
Click to collapse
So ROM Manager doesn't work? It's what was recommended by the first instructions I came across. Does it just not work with the Epic 4G Touch? If so, it's strange that it has the device as an option when flashing cwm recovery.

Brent212 said:
So ROM Manager doesn't work? It's what was recommended by the first instructions I came across. Does it just not work with the Epic 4G Touch? If so, it's strange that it has the device as an option when flashing cwm recovery.
Click to expand...
Click to collapse
It works its just not recommended by those of us who actually flash a lot. It will get you in more trouble than its worth at times. Stay away from it and just learn how to do things I guess the longer way....

It's not like it takes that much longer anyways.

[Q] CWM not replacing Android Recovery after newest OTA update / Lost Root

I recently purchased this SGS3, installed CWM and rooted it. Everything was going great - but then i was offered the most recent OTA update, so i reflashed the stock recovery via Odin, did the update which is:
4.0.4
T999EVLH2
same kernel
bld #: IMM76D.T999EVALH2
now, its saying the phone is no longer rooted (yet superSU is still there) but checkroot is saying that it isnt rooted, and no matter what i do, flashing CWM via Odin passes, but will not stick (as in, i boot into recovery mode and that damned stock recovery is STILL THERE, wtf?)
can anyone offer any assistance or insight into my issue.
Thanks
~Wikkid

Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.

Aerowinder said:
Flash CWM v6. If that alone doesn't fix it, disable auto reboot in Odin, after flash, reboot phone manually into recovery mode.
Click to expand...
Click to collapse
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.

mikewikkid said:
thats the version i've been using. tried to redownload, both touch and regular versions. tried disabling autoreboot and manually rebooting into recovery mode, but the recovery mode remains stock recovery. super weird.
Click to expand...
Click to collapse
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.

Aerowinder said:
Can you describe for me, in the greatest detail possible, how to reproduce your exact problem?
I've done it countless times in the past days, and it has worked every time.
Click to expand...
Click to collapse
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.

mikewikkid said:
as have i, for myself and for others - this is the first time an Odin flash says pass but simply wont take.
Like i said, i flashed stock recovery onto phone using Odin3 1.78 while in download mode
rebooted and took OTA update a few days ago
now i tried to flash multiple versions of CWM v6, touch and regular using Odin and everything looks good, it says pass and everything.
when i reboot into recovery mode by holding powerup, home, and power - it takes me into stock recovery still.
its as if the recovery is either not being written to the right place or it is loading from another location on the device. i dont know how to make this issue happen on a phone, ive never seen it happen before myself. which is why i come to the pros seeking help - im no n00b myself, but i certainly am no developer.
Click to expand...
Click to collapse
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/jv6pHg8b

Aerowinder said:
Proper CWM Touch: http://forum.xda-developers.com/attachment.php?attachmentid=1287723&d=1346158787
Proper Odin: http://db.tt/sUJixYID
Click to expand...
Click to collapse
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!

mikewikkid said:
now THAT version of CWM worked, dunno why the one's i had worked a couple days ago and now they wouldn't, and even the ones that i downloaded fresh - must have been the wrong versions.
for the record, i did have Odin3 3.07 also, and i tried using that one as well, so it must have needed the newest CWM, which i obviously wasnt downloading. thanks alot mate!
Click to expand...
Click to collapse
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.

Aerowinder said:
Sure thing. If I were to guess, I'd go with incorrect permissions on recovery.img file. I learned that lesson the hard way.
Click to expand...
Click to collapse
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."

mikewikkid said:
found what was probably causing the issue too - as you first suspected, but in greater detail on how to avoid this in the future:
"Apparently for those who have ran the official update by samsung are having this issue where the stock recovery is overwriting CWM recovery after reboot. Here is how to fix the issue. Credit to Max from Galaxys3root
You will need to rename or delete these two files.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
I just renamed them. I'm thinking once there is a offical update such as jelly bean that I want to update too ill just rename them back so the stock recovery will reload and allow the update."
Click to expand...
Click to collapse
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.

You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.

xanderman said:
Thanks a bunch for that information, I've been trying to get the CWM to stick and was getting extremely frustrated with it reverting after every boot. Deleting these files fixed it and I now have CWM v5.5.0.4 installed and surviving a couple boots. It took a few tries to delete the files, though, finally used ES file explorer and went in to settings to allow root acess.
Click to expand...
Click to collapse
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
Aerowinder said:
You wouldn't have had any issues at all if you were using a version of CWM even somewhat recent. Because it prompts you to remove those files.
Click to expand...
Click to collapse
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/

Thistleknot said:
this worked for me guys
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
---------- Post added at 01:37 AM ---------- Previous post was at 01:34 AM ----------
try these instructions
http://www.droidviews.com/root-and-...-s4-sph-l720-and-t-mobile-galaxy-s4-sgh-m919/
Click to expand...
Click to collapse
Umm, 2 things....
You realize this thread is over a year old and the last post was over 9 months ago?
And those links look like they are for the S4....
Sent from my SGH-T999V using Tapatalk 4

How to change TWRP recovery

I have a t-mobile Galaxy s4 that is rooted and uses TWRP 2.6.3.0. The recovery keeps hanging at the Teamwin Blue screen. I downloaded the flashable TWRP 2.5 which is said to be more stable so can I just flash this with Goo Manager or will I have to remove the TWRP 2.6.3.0 first. If so how can I downgrade

Just flash in twrp like you would a Rom but don't do any wipes

No Boot into revcovery
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed

josephh71 said:
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed
Click to expand...
Click to collapse
Download 2.5.0.2 version tar here http://www.teamw.in/project/twrp2 click on Get TWRP for your device and type s4 and click on T-Mobile version jfltetmo, you should flash it through Odin. Whenever you flash another recovery to your phone, it replaces the older recovery.

Where did you get the 2.5 twrp? I flash between different versions of twrp and cwm often.

Here is the post for twrp 2.5.0.2 zip also. http://forum.xda-developers.com/showpost.php?p=43469920
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
jd1639 said:
Where did you get the 2.5 twrp? I flash between different versions of twrp and cwm often.
Click to expand...
Click to collapse
SERIOUSLY?!?!
I just explained to you in the post, did I just waste my time? You can get it by yourself in the future by following my instructions, ANY version, tar or img is on their site.

josephh71 said:
I flashed the TWRP but when I try to go into recovery it opens to the Samsung screen with the blue writing and then it turns off, vibrates twice and boots normally. I did not wipe as you instructed
Click to expand...
Click to collapse
Some people have huge issues with TWRP I know I did. You might want to flash CWM touch. I did and haven't had a problem since. You can easily download and flash from Rom manager. You can get that from play store. It will give you latest version of cwm touch. Easily. It should solve your recovery problems.i know it solved mine. Don't know why some can use twrp and others have nothing but problems with it. I know I couldn't use it.i needed a stable recovery and twrp was NOT stable for me. CWM touch had never given me a problem once..it might be time to give CWM touch a try...it worked out really great for me.

norml said:
Here is the post for twrp 2.5.0.2 zip also. http://forum.xda-developers.com/showpost.php?p=43469920
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
SERIOUSLY?!?!
I just explained to you in the post, did I just waste my time? You can get it by yourself in the future by following my instructions, ANY version, tar or img is on their site.
Click to expand...
Click to collapse
What? that was meant for the op

jd1639 said:
What? that was meant for the op
Click to expand...
Click to collapse
Why don't you use features like "reply , like you just did by quoting me, or is this a special thread for just you two? San Fransisco thing going on here, LOL? You can just ask any question and everyone automatically knows who it is directed to?

norml said:
Why don't you use features like "reply , like you just did by quoting me, or is this a special thread for just you two? San Fransisco thing going on here, LOL? You can just ask any question and everyone automatically knows who it is directed to?
Click to expand...
Click to collapse
You snuck you post in on me while I was writing lol. No worries

jd1639 said:
You snuck you post in on me while I was writing lol. No worries
Click to expand...
Click to collapse
If you two want to be alone, hey, to each their own. JK

Working great!
Thanks for the update. I finally got it installed and working. I really appreciate your help

Thank you
thanks for all the help. I finally got it working. I initially got the dl from another link in the help section but when I flashed it I couldnt get into recover so I just followed the instructions and now it works.

[Q] After root no rom is working.

Hello
I have a GT-P5220 (ie. Galaxy Tab 3 LTE). I have rooted the tab using this procedure: http://forum.xda-developers.com/showthread.php?t=2642796
After that everytihng seemed ok. I flashed via TWRP tihs deodexed rom: http://forum.xda-developers.com/showthread.php?t=2624466. The tab boots up but i only get lots of FC messages and can't continue to use the tab. I tryed reflashing other roms, but with the same results all the time.
Can anyone help?
Thank you!

imprz said:
Hello
I have a GT-P5220 (ie. Galaxy Tab 3 LTE). I have rooted the tab using this procedure: http://forum.xda-developers.com/showthread.php?t=2642796
After that everytihng seemed ok. I flashed via TWRP tihs deodexed rom: http://forum.xda-developers.com/showthread.php?t=2624466. The tab boots up but i only get lots of FC messages and can't continue to use the tab. I tryed reflashing other roms, but with the same results all the time.
Can anyone help?
Thank you!
Click to expand...
Click to collapse
Download your stockversion from sammobile. and flash it with Odin.
Download CWM and the root.zip flash it with odin,so your tab are rooted.
Make an nandroid backup with the recovery.
so is sure that you can go back when you have probs.

bierma32 said:
Download your stockversion from sammobile. and flash it with Odin.
Download CWM and the root.zip flash it with odin,so your tab are rooted.
Make an nandroid backup with the recovery.
so is sure that you can go back when you have probs.
Click to expand...
Click to collapse
Thank you for your quick reply. I will try this asap. I allready flashed cwm before, but i can't see the zip files I copy too root. That's why I switched to TWRP. Any ideas how to see the .zip files in cwm?

imprz said:
Thank you for your quick reply. I will try this asap. I allready flashed cwm before, but i can't see the zip files I copy too root. That's why I switched to TWRP. Any ideas how to see the .zip files in cwm?
Click to expand...
Click to collapse
root the is wrong folder.
from recovery you can only go to your int. sdcard or ext, sdcard

bierma32 said:
root the is wrong folder.
from recovery you can only go to your int. sdcard or ext, sdcard
Click to expand...
Click to collapse
Sorry my bad. I meant in internal SD, but when I try to mount it in CWM says: E: Cant mount intsd or something similar.
Any ideas?

imprz said:
Sorry my bad. I meant in internal SD, but when I try to mount it in CWM says: E: Cant mount intsd or something similar.
Any ideas?
Click to expand...
Click to collapse
Please post a picture from your recovery.
This message mine are you have stockrecovery.
edit:
which recovery you have flashed?

bierma32 said:
Please post a picture from your recovery.
This message mine are you have stockrecovery.
edit:
which recovery you have flashed?
Click to expand...
Click to collapse
OK I'm back. Just flashed the stock firmware from sammobile, as you suggested. The tab is working now? Can you tell me wich version of cwm should i flash and where do I find the root.zip for my tab?

imprz said:
OK I'm back. Just flashed the stock firmware from sammobile, as you suggested. The tab is working now? Can you tell me wich version of cwm should i flash and where do I find the root.zip for my tab?
Click to expand...
Click to collapse
I'm not sure ,you have got the lte tab.
here are the link to the CWM thread http://forum.xda-developers.com/showthread.php?t=2432467&page=13
Important uncheck autoreboot by odin. After flash boot with the button combo into recovery snd flash the root.zip
Than make an backup of your rom.

bierma32 said:
I'm not sure ,you have got the lte tab.
here are the link to the CWM thread http://forum.xda-developers.com/showthread.php?t=2432467&page=13
Important uncheck autoreboot by odin. After flash boot with the button combo into recovery snd flash the root.zip
Than make an backup of your rom.
Click to expand...
Click to collapse
OK. I have flashed CWM and i can get into recovery. When i go to: choose zip from sdcard i get the following message: E: Can't mount /sdcard/
I have CWM-based recovery v6.0.2.8
Any clues on how to acces the root.zip from here?

imprz said:
OK. I have flashed CWM and i can get into recovery. When i go to: choose zip from sdcard i get the following message: E: Can't mount /sdcard/
I have CWM-based recovery v6.0.2.8
Any clues on how to acces the root.zip from here?
Click to expand...
Click to collapse
please post a picture ,so i can see the recovery
can you load it from ext. Sdcard ?
---------- Post added at 03:04 PM ---------- Previous post was at 02:44 PM ----------
imprz said:
OK. I have flashed CWM and i can get into recovery. When i go to: choose zip from sdcard i get the following message: E: Can't mount /sdcard/
I have CWM-based recovery v6.0.2.8
Any clues on how to acces the root.zip from here?
Click to expand...
Click to collapse
please post a picture ,so i can see the recovery , looks your recovery so ?
http://www.android-hilfe.de/attachm...t-accounts-uploadfromtaptalk1380439869871.jpg

bierma32 said:
please post a picture ,so i can see the recovery
can you load it from ext. Sdcard ?
---------- Post added at 03:04 PM ---------- Previous post was at 02:44 PM ----------
please post a picture ,so i can see the recovery , looks your recovery so ?
http://www.android-hilfe.de/attachm...t-accounts-uploadfromtaptalk1380439869871.jpg
Click to expand...
Click to collapse
No. My recovery is CWM now. But it says it can't mount sdcard.
I will later try using sideload and adb. Having a look into this now: http://forum.xda-developers.com/showthread.php?t=2559200

imprz said:
No. My recovery is CWM now. But it says it can't mount sdcard.
I will later try using sideload and adb. Having a look into this now: http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
Also comes this error,when your format of the ext.sdcard than other than fat32 and the size is more than 32gb
Format a sdcard to fat32 with size less 32gb, i found some post at CWM thread.

bierma32 said:
Also comes this error,when your format of the ext.sdcard than other than fat32 and the size is more than 32gb
Format a sdcard to fat32 with size less 32gb, i found some post at CWM thread.
Click to expand...
Click to collapse
I have no external sdcard inserted in the tab. I hoped i would be able to flash the files i copied on the tab.

I kinda have the same problem, Im going to follow this thread...

I may be late for dinner but here is how I flash roms on my 5210. If the rom is the OEM Stock Rom, I flash it from ODIN. This HAS to be done this way. There is no other way to flash OEM Stock Rom.
If I am going to flash something like Grievous or Pimpdroid or BinDroid, I will load the rom on to my internal memory Download folder. Then from TWRP I select install and it goes straight to the download folder. However, before I install any of these roms I will wipe the cache and dalvik cache. Is this wise? I don't know, I just do it because most of what I have read has indicated it should be done.
So if you are still having issues, reload from fresh the OEM Stock Rom for you device. Then reload your favorite Recovery (CWM or TWRP). Set up your device for the minimal way you want to use it. Now, from either CWM or TWRP (or whatever backup app you have) backup your device and save it to your PC. This way you can always go back to standard/stock.
From here you would load the Root.zip AND the rom you want to load on the internal download folder (note - if the rom is already rooted there is no need to load root.zip). Now go into recovery and install the root. Restart then shutdown. Note - you may have to update the SuperSU or Superuser app. Go back into recovery and install the rom.
This is how I have done it and it has worked for me. I am sure I have loaded and reloaded several times different roms. However, I always come back to the Stock ROM via backup restore. I haven't found a rom worth using.
This is how I do it. Your device may not react in the same way mine does. So I advise you on the side of caution that you could damage your device if you follow what I do. Not saying what I do is wrong, but it is how I go about loading and unloading different roms. The key for me is I use the backup/restore from TWRP. I find it to be very fast.
Good luck!
ps... if you have already done this and it did not work, my apologies for coming to party too late.

Thank you for your help. I allready tried this procedure. It all works well, the problem starts with the custom roms i try to install, They install fine but when they boot up I get various forceclose messages. Unusable.
I suspect the isue is with the roms. I have not yet found a working rom for GT-P5220.
Has anyone found some working rom for this specific device?

Need help unbricking T-mobile N900TUVUBMI7

Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.

re: md5 error
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse
Before doing anything else you need to re-download the TAR.MD5 firmware.
If you get MD5 errors it simply means that for some reason the download
had an error in it (checksum error).
You need to have a error free download of the TAR.MD5 firmware in order
to solve the issues you are having. Your phone is NOT bricked at all and all
it needs is a error free TAR.MD5 file to flash with odin and your phone will
work perfectly. You should never flash a TAR.MD5 file which has errors.
Your problem has nothing to do with the versions of the firmwares like 4.4.2
and or 4.3 you are trying to flash, it all has to do with errors during the actual
download process of the TAR.MD5 file.
Good luck!

Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.

Call me to un brick your phone
HEY CALL ME TO UNBRICK YOUR PHONE AM A REPAIR SHOP IF YOU MAIL ME THE PHONE I COULD FIX IT FOR A SMALL FEE [email protected] HAVE A GOOS DAY :fingers-crossed:
Silvist said:
Hello everyone,
For the longest time I had just had my note 3 rooted with chainfire. Being familiar with modding androids I decided to give it a go on my note 3. As you can see from the title, I failed lol.
I've tried to use any tar.md5 I can find of the T-mobile US version; but most come up with md5 check failed. The only one i've gotten to work on the many odin versions i've tried is N900TUVUDNF4_N900TTMBDNF4_N900TUVUDNF4_HOME.tar.md5.
The phones state is it currently freezes loading on the samsung logo screen. I was able to install twrp custom recovery version 2.6.3.2. Before I installed the rom I was trying "X-note", I did a backup of the system. Though when I use the restore, it only does the boot and system files. The data fails everytime I try.
Before all this I was in 4.3.
If you guys could help me out, and point me in the right direction to at least get my phone working I'd appreciate it.
Click to expand...
Click to collapse

For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
Click to expand...
Click to collapse
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.

blu422 said:
For anyone else with this problem: I had this problem I flashed the firmware a few times talked about earlier. Then I performed a factory reset through recovery and boom it works again. Maybe that's all I needed to do in the first place maybe odin wasn't even necessary... This may also work with other cf auto-root bricks across many phones.
---------- Post added at 06:18 PM ---------- Previous post was at 06:10 PM ----------
Scratch that. This is what I believe happened. The way CF Auto-root works is it roots through a temporary custom recovery I believe. What happened is during the process something went wrong and the phone ended up with both a corrupted system and a corrupted recovery. You need to flash the stock tar to fix both then factory reset to make it boot the rest of the way. Again this is just for future reference with more people running into this problem... I do realize OP already got helped.
Click to expand...
Click to collapse
I always ODIN flash the newest firmware, let the phone boot up, then I just ODIN flash TWRP... and then in recovery I flash my personnel rom and flash SU from chainfire...
then I just install busybox which I have a copy of all the on my sdcard, a folder I call apk files.... then I install titanium backup and restore my apps.. all done in less then 10 minutes...
when ever u think u have a problem, flash the firmware your on, or the newest, that should always fix any issues.. I have all of the versions on my site, and stock odex roms...

Silvist said:
Thank you for replying!
So what should I look for in terms of flashing then? Just full stock of the t-mobile US version?
Reason I asked is because I'd downloaded about 15 different ones from all different sources, and only that one didn't have the issue. Should I try to flash through twrp over Odin?
Edit:
Like for instance I tried the one from here:
http://forum.xda-developers.com/not...900tuvudnf4-extracted-stock-firmware-t2834398
This was the only one that worked actually. Though after I flash it with odin it just shows the samsung logo with "recovery booting" in the top left corner.
Wow..holy crap after like attempt number 40 with the same flashing in odin it actually booted up. That's just crazy lol.
Click to expand...
Click to collapse
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin

xxjahasotoxx said:
I'm actually having this exact issue how exactly did you fix it? mine just says booting recovery and then it loops and I've downloaded at least 4 different versions of the nf9 odin
Click to expand...
Click to collapse
I just kept trying to flash to the stock image that's in the link in my post. It kept giving me md5 errors, so I re downloaded the file until it passed. I also ran odin as administrator, which helps. I used an older version of odin, 3.5 I believe.
Everything else I tried failed, like hemdall. I did attempt it, but it failed when I tried to flash through it. I'm not really familiar with it, just followed the guide on these forums. It can supposedly do more than even odin can do, that's if you can get it to work lol.