Database Users

Bricked from voodoo? Try this

Credit goes to Sombionix for this tip, Eugene, and all the others how helped me out when my phone was messed up. This is from the thread for Sombionix's ROM.... Works great!
Did You Flash Something Before Disabling Voodoo? Then This Fix is For You.
So you forgot to disable the voodoo lagfix before you flashed a new rom and now you're getting an error, similar to the one posted below. Even Odin won't allow you to flash back to stock. Well, pay close attention and with some luck, you'll be good as rain...or something like that.
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /data/!
Skipping format...
Copying files...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
E: Can't mount DATA:
E: Failure at line 372:
copy_dir PACKAGE:data DATA:
Installation aborted.
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!

how long did it took you to re-partition the SD? i tried to re-partition but it just sits in there and it does not show any indication it is being partitioned.. so i just did evrything except the repartitition part it it works great for me..

My Galaxy S from Bell I9000M, It was installed with JM8 with Voodoo lagfix. Last night phone freeze, i pull the battery, and reboot always stuck in black screen after S log and music. Today, without uninstall Voodoo lagfix (obivious I couldn't), I have been flashing it with all kind of ROM (with repartition), and same issue "always stuck in black screen".
Recovery Mode, it show error message:
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
Looks like Voodoo Ext4 is causing SDCARD not able to be mounted by system.
Do you know if this method will work on Galaxy S? it is safe for me to try it (I guess if I try it, at step #9, I will use I9000M stock ROM)? also where can I download " Eugenes 'Froyo that does not brick' file."?
PLEASE HELP!!

mingqlin said:
My Galaxy S from Bell I9000M, It was installed with JM8 with Voodoo lagfix. Last night phone freeze, i pull the battery, and reboot always stuck in black screen after S log and music. Today, without uninstall Voodoo lagfix (obivious I couldn't), I have been flashing it with all kind of ROM (with repartition), and same issue "always stuck in black screen".
Recovery Mode, it show error message:
E:copy_dbdata_media:Can't mount SDCARD:copy default media content failed.
Looks like Voodoo Ext4 is causing SDCARD not able to be mounted by system.
Do you know if this method will work on Galaxy S? it is safe for me to try it (I guess if I try it, at step #9, I will use I9000M stock ROM)? also where can I download " Eugenes 'Froyo that does not brick' file."?
PLEASE HELP!!
Click to expand...
Click to collapse
Do you guys have an Odin 1-click back to stock rom for the i9000? Does it have a Master Clear button? I have a Captivate so sorry for posting in here folks.
(The usual disclaimer - if this finishes bricking your phone - not my fault - but it worked for my phone )
My buddy just restored my phone by doing the following:
Downloaded Odin 1 Click back to Stock for Captivate
It has a MASTER CLEAR button on it - put the phone into Download Mode and hit the button... and let it ride for 15-20 minutes.
It didn't finish - he just unplugged and pulled the battery and when it came back up it was at the "computer++++" message.
Turned Odin 1 Click back up - put the phone into Download Mode - phone restored as normal.
Back to stock with a the ugly live wallpaper!

Thank you!!! I was screwed!!!!
Edit: Quick question, before I did this, when I was running fine, I had an option at the bottom of the pop up window you get when you hold home and see recent applications - this option would let me go in and kill running apps - it isn't there anymore and I can't remember if it was something I added - any ideas?

this worked for me ..... thank you!

How to unbrick a vibrant without Eugene's Froyo ROM?
I'm new - but searching doesn't seem to help much , i get all dead ends.
I've got a softbricked brant because of voodoo and a rom flash. The vibrant boots past the galaxy S logo and then goes black with all 4 buttons lit up at the bottom.
Everywhere I look seems to indicate I need to reflash with Eugenes Froyo that doesn't brick, but that seems to have been pulled from XDA.
Is there some other way around this or is the ROM stored offsite somewher else still?

Crankycoder said:
I'm new - but searching doesn't seem to help much , i get all dead ends.
I've got a softbricked brant because of voodoo and a rom flash. The vibrant boots past the galaxy S logo and then goes black with all 4 buttons lit up at the bottom.
Everywhere I look seems to indicate I need to reflash with Eugenes Froyo that doesn't brick, but that seems to have been pulled from XDA.
Is there some other way around this or is the ROM stored offsite somewher else still?
Click to expand...
Click to collapse
Froyo that does not brick can be found here:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8
After flashing this via Odin, reboot to download mode again, and flash a stock rom of your choice in Odin, and you'll be up and running in no time.
The instructions in the OP of this thread are the short and sweet of this process, follow it, being sure to check repartition in Odin only at the last flash, ie stock firmware.
Ginger Clone's of the World Unite! Via the XDA App

not good
I hate it when that happens

thank you thank you thank you so much it work again

This should be in the bible sections if it's not yet there.

Phone not resonding whilst doing the Upgrade

Guys,
I'm in need of help fast.....
Just tried to do the Froyo Upgrade and have hit an almighty problem.
Kies downloaded and went to the next stage 'Upgrade'.
It got about 5% into doing this when the bar stopped moving and the phone switched off.
It's been like this now for over 30mins..... The phone won't power up (it's still connected to the PC).
HELPPPP.

Well you get my sympathy vote! But other then that I think you know yourself what to do. You've been around... Good luck!

Yes..... Bloody Phone, Bloody Kies, Bloody Samsung.
I unplugged the phone in the end and Kies offered to do a Firmware Recovery so I thought why not give it a try.
I went into Download mode, reconnected and Kies started the recovery procedure only for again the bar to stop moving again and it's stopped doing the recovery.
The screen on the phone remained a constant bright Yellow.
I unplugged it again and tried once more... It again stopped about a quarter way into the recovery only this time the screen has turned a constant Green.
Damn.................

The sad thing is that this reminds me so much of my sinclair zx81. 25 years later and we still have to deal with the same problems. Never sure the data gets from point A to point B.

Right.... Now I need to find the address for UK returns.
Don't have my warranty card info with me either so looks like I'll have to Google the returns.... but I'm busy as hell and have an Op to carry out soon.
If anyone comes up with it (or the link) I'll be grateful.
Bugger....

I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.

Geryatrix said:
I'm probably teaching the teacher, but are you using the USB lead supplied with the phone? I tried to download some music using another lead and the download stopped halfway.
Sorry if this is too obvious.
Click to expand...
Click to collapse
No problem on the 'techer', any advise or assistance is better than nothing.
Yes, I used the cable supplied by Samsung... Nothing seems to sort this out.

As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.

sargasso said:
As you are thinking of returning it, I conclude you can't get to any recovery/download mode. I don't know if Kies messed up the bootloader or keymappings but there is still the diy jig you might try. Also I have come across many devices in my day that needed repetitive flashing to get to the 100%. It would be bad if this was the case with a 2010 phone but hey its a Samsung.
Click to expand...
Click to collapse
Well I've tried the Firmware Recovery at least a dozen time, each time it starts and stops at different parts.
I nearly got to three-quarters through when the bloody thing hung again.
No problem with the 3 Botton access and getting the Yellow Android Man on screen.. No problems connecting to Kies but as soon as you try the recovery it stops at some point during the process simply saying "An unexpected error has caused firmware upgrade to fail. Do you want to perform firmware recovery now?"....... and that came up whilst doing the firmware recovery.

Doesn't work to flash with odin either?

xExisioNx said:
Doesn't work to flash with odin either?
Click to expand...
Click to collapse
I don't want to use Odin if possible.
With that many different phones and ROMS available I don't want to end up screwing the phone totally.

Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D

Don't be scared of Odin. It has recovered my phone a million times
Really, the time and effort of getting a replacement when you can fix it in 2mins with odin in your own home... seems crazy.
You can flash a UK firmware if theres one available, or otherwise flash any firmware and update to UK firmware using kies reg hack, as far as i understand.

sargasso said:
Well Kies does not have a reputation to be very functional but there are two or three other tools to flash your phone. Although I am not a compulsive flasher, I did use Odin a couple of times. I am not sure exactly why you are having stage fright (referring to your other post on this matter).
Bringing it back to Eclair with a stock rom, using the rom, pit and instructions on http://www.samfirmware.com might help you to restore sanity. Once you are sure you haven't lost your phone you can then retry to use Kies.
The problem for you might be a partialy broken bootloader or incompatibility between the rom mappings and your phones current setup. Flashing a low rom might solve that. (As I understand from heimdall there are high and low packages, the low packages contain a bootloader and are more risky to flash since replacing the bootloader might truly brick your phone)
Also I read about people just flashing a pit file to force a repartition and format of the phone.
Make sure to get it fixed before op, I wouldn't want my doctor to worry about his phone, stiching me up with a pair of siccors stil in me ;D
Click to expand...
Click to collapse
Thanks... Need to find out now which is the right PIT to download.
I was on JF3.
God... if only I had more time on my hands.

Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.

When you flashed did you remove your sim card? I had that same problem with ki es. Removed the sim card and redid the flash and it continued on it's way.
How this helps.
Sent from my GT-I9000M

Well, if you have an account at samfirmware you can use this link http://www.samfirmware.com/WEBPROTECT-i9000.htm.
Make sure before you do anything to check your phone model is the one I linked to. Making a backup of your efs directory is not possible anymore but normally that should be done also. As a precaution I always remove my external sd card and sim card before flashing and - as you know - have the battery loaded to the max.
It might be an idea to skip jf3 and go to JM8 with a 512 pit and repartition on. This because it seems to be the recommended way of doing things at samfirmware as preparation for the flashing of current froyo releases.
I have never had problems with their way of doing things but opinions differ.
[EDIT]
I downloaded their JF3 package to see if there was a pit file included as there is some discussion what PIT file to use 512 vs 513. The package contains no information on that. It does however contain the word LOW in one of the filenames ...

Beards said:
Okay... got to go guys... Surgery to do.
I'll do the Odin later.
To save me time searching could someone please post below the relevant links I need to get Odin and the procedure....
Cheers.
Click to expand...
Click to collapse
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1

Fornowagain said:
I don't think you need to use a pit, odin should use the information from the phone assuming partitions remain intact. I've flashed a dozen times without one. If you do use one then use 512.
First off, get into recovery try and clear, reset what you can. Remove the sim and external SD as a precaution. Then back to download mode without the phone usb connected.
Grab the JPO firmware > http://www.multiupload.com/MX8XW7BG24
Grab odin 1.3 > http://www.megaupload.com/?d=MADK0XTB
Extract the firmware somewhere, open odin then select JPO_JPO_U_JPP.tar as PDA. Leave everything un-ticked except reboot. Plug the phone into your PC make sure Kies is not running and the battery is charged. In odin you should see a yellow window under ID:COM with a COM port open. If you do hit start, if all goes well a green bar will move across until the phone reboots. Leave it to do its thing at the big S (I usually unplug USB by now, to avoid problems) wait upto 10mins first time. If it hangs try a reset and cache clear and reformat SD. That's all I do, worked with all the firmwares I've downloaded from Samsung's FUD server.
The PIT files are templates for partition information so Odin can manage the size of the internal device partitions. Your standard device should already be on 512 layout, the other PIT's were development hacks. Like I said you shouldn't really need to repartition, but if you do > http://www.multiupload.com/I5WICSBFJ1
Click to expand...
Click to collapse
Surgery postponed until tonight so I have some free time.....
Okay, I got Odin 1.3 & JPO Firmware.
I loaded the JPO into Odin (in the PDA section).
Next I put the SGS into Download Mode and connected via USB and sure enough the ID:COM came up yellow with COM7 so I hit Start.
The green line went so far across under KERNAL but just as it was about to finish that box the SGS screen changed to a solid Blue screen and nothing further is happening in Odin.
Any advice??

Odd never seen that before, maybe your root problem. Should have rebooted automatically once the progress bar reached the end assuming you had the reboot option selected. Try a manual reboot, hold the power button down until it restarts. My next step would be the repartition and try again, load the PIT file (as PIT). Same flash procedure as before just using the 512 PIT, reset it all and try again.

Internal SD Card Not Mounting ... Please Help!

Hey guys,
I just messed up my phone pretty bad. I forgot to disable lagfix before flashing a new kernel and now my sd card cannot be mounted. This is the error i get:
Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0p1)
Can't mount SDCARD: copy default media content failed.
I tried flashing using odin but no luck. My phone either goes in a boot loop or a black screen with the menu and back buttons glowing. Please help!

i have the same problem since 40 day i look too much and i dont find any solution and samsung says i had to change the mainbord its coast 250$. i dont know what to do wait more or what?

HI,
Try the following, worked for me
1) Go into recovery mode and wipe both cache and partition data
2) go to samfirmware.com and download the original rom for your phone (the one that came with it)... since you don't say what region you're from, I'll give you an example with mine. Mine is from Bell, and factory comes with UGJH2, so i downloaded that with ODIN and the PIT FILE, make sure to extract the TAR file from inside the RAR file. Put all 3 files in the same folder
3) Enter download mode, when the phone is in that state sometimes it's hard to access download, best way is... remove the battery, put it back in, then hold VOL DN + HOME + POWER until you see a working android bot inside a triangle. When you see that, connect your phone to your PC, double click on ODIN, then load the PIT file (CHECK BOX RE-PARTITION leave the others to default) and Select PDA and find the TAR file you extracted in STEP 2... then click on START, it's gonna take a few mins, and even after it's done, it's going to reboot, and it'll stay at the "S" logo for a bit, leave it, then it'll boot.
At least we hope it will.
Keep us posted,
Thank you,
Rodi.

Tried this on my buddies phone and it wasn't that easy.
It would boot up again, but only with the help of an External SD Card. Also, once you take it out, everything would FC and phone shuts down.
Also, there was a notice in notification bar saying "Unable to mount to External SD. Please remove, Mount point incorrect"
Wasn't able to revive it so buddy got rid of it.
Sad to say, but you're not the only one who has had these problems. Which is why I got rid of my i9000. Its an amazing phone and loved it, but once problems happened out of nowhere, I lost faith in it. Don't want to end up with a lemon. Phones are meant for emergencies afterall. When you start questioning if the screen will turn on, really makes one worry.

I have the internal SD problem too and i tried that..
I get stuck at ODIN where it says "File Analysis.."
It just stays there..

I did try flashing the stock 2.1 firmware using odin but no luck. I'm with Bell too and I'm sure I used the right .tar files, and I did repartition the memory with the right pit file, I'm not that much of a noob . Anyway, after searching every where to find a solution, I was pretty sure there was no easy way of reviving the phone. So I just went to Bell and they shipped it to Samsung to repair it. The problem is that when you don't disable the lagfix, your internal memory card remains partitioned under different formats and the system won't be able to read stuff off it ... or something like that.

i think the pit file couldn't repartition the sdcard we need to find another way to repartition the sdcard, but how we can do this? any suggestions?

sjouni said:
i think the pit file couldn't repartition the sdcard we need to find another way to repartition the sdcard, but how we can do this? any suggestions?
Click to expand...
Click to collapse
Well, in my case the pit file did repartition my sdcard, as odin successfully "past". Did you try other pit files to see if it works?

Yup same thing happened to mine. Its just stuck with buttons lit up but nothing on the screen. Went into recovery and wiped the hell outta everything there, but still nothin.
Im just gonna try to return it and get a diff phone all together. Its been only 3 months since I got the damn thing. So they better take it back.

shaahinjjj said:
Well, in my case the pit file did repartition my sdcard, as odin successfully "past". Did you try other pit files to see if it works?
Click to expand...
Click to collapse
we need a 512 pit other not work, but on my sdcard as your's if the pit repartition the sdcard then no problem, what the lagfix do to sdcard? we need to back it to default state, how?

sjouni said:
we need a 512 pit other not work, but on my sdcard as your's if the pit repartition the sdcard then no problem, what the lagfix do to sdcard? we need to back it to default state, how?
Click to expand...
Click to collapse
If I knew how, i wouldn't have taken my phone to Bell to fix it for me. I don't mean to disappoint you but I don't think there's any easy way of fixing the phone. Our phones are basically bricked! I suggest you do the same I did.

[Q] I have a semi-bricked Vibrant and CANNOT FIX!!! HELP!!

I have been on this forum for 3 days going through many fixes for this problem.
NONE of them have worked.
I have been able to get into download mode, and the phone is recognized via com3 in odin.
I have re-flashed it with Eugenes no-brick version, then re-flashed it with tons of different stock and non-stock roms. It gets to various stages but does NOT work.
Any ideas or fixes will be a lifesaver!! Thanks in advance!

If you can still get into download mode and Odin recognizes your phone, flash it with these two files, they work:
http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
DO NOT check the re-partition checkbox in odin.

why not repartition as long as you put pit file in pit field repartitoin like crazy if you like .
and repartition would be required if you coming from vodoo based kernel or if you ran anyother partiton than rfs .

Thanks for the quick response.
I tried these files again (I have tried them before) both with and without checking the re-partition box.
It boots then says Vibrant Samsung, then crashes. When I turn it back on it again crashes and turns itself off after the initial splash screen.
Any other ideas? It says that I passed in Odin

charge your phone ?

bartek25 said:
charge your phone ?
Click to expand...
Click to collapse
Hahaha ya I wish it was something so simple (maybe it is!) but it isn't that!

download this ! http://forum.xda-developers.com/showthread.php?t=734475
put JFD in to PDA
also downlaod PIT from the same lik i gave you and seriously charge your phone , and when you odin with the files i gave you from the link check rapartition . check phone efs clear and f.reset time and auto reboot .

come back report resoults if not we help more .

also by any chance u didnt play with ROM MANAGER when your wibrant was working and didnt play with repartiton while there right ?

The same crashing loop has happened with the latest advice. I checked Phone efs clear, re-partition, auto-reboot, and f.reset.time.
I used tVhe T959UJFD PDA, and the 512 Pit.
This phone has been plugged in for days I really doubt the battery is dead.
It just is a constant loop of crashing,h whether at te "off battery" logo or the vibrant splash screen.
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
I am starting to think there may be a hardware issue.

To be completely honest, I got this phone from a friend who had bricked it. If I can get it working then I have a galaxy on the cheap.
On the downside I have no idea what he did to brick it, and he is not tech-savvy enough to know himself.
I come from an original G1 and Cliq, so this is a tad different then I am used to.

from my point of view your phone is fried (it happends) or you are not doing something right or someone is more tech savy to help more , did you pull battery out for at least a min and let it sit and try again to boot ...

Ohhh i know whats wrong with the phone ........if your friends gave it to you broken i think good advice is ,download a program that can repartition hard drive from windows like any program that can do format of anydrive from windows i recomend PARAGON PARTITION MANAGER , find your phone while in the program and u need some skills lol for it but find the phone and click delete partiton after you do that click apply 2. after deletion and applaying the actions click on the phones formated drive in the program i recomended you and click submenu wher you will see create partiton click FAT32 apply 3. click again on the disk you created and click format . 4 done , its easy just get to hang of it

Good advice, I will work on this and get back to you later tonight.
Thanks again!

sounds like your friend bricked his phone from ROM MANAGER by creating EXT4 partion in phones memmory not on SD thats why phone cant find a drive to install the system , happend to me by my own mistake but i got it to work so if that help you You have free vibrant so try hard if not u have paper weight toy

if u dont want the phone i buy back from you for 20 bucks so i cant smash it against the wall , always want it to do that

Intim said:
The ONLY flash that has given me any different results is the "eugene no brick froyo" which takes me to the Android Recovery screen but does not allow me actually select any of the options.
Click to expand...
Click to collapse
Just so you know when you get to this point you need to make sure you had ADB set up on your pc and then plug in the phone and do adb reboot and that will boot the phone up, then you can shut it down and go into DL and flash back to stock. if you read the directions from Eugene's no brick it stated you need to do a adb reboot to get it to work, so you can fix it if your getting to the recovery of that flash.

Ok so for the paragon partition manager it does not recognize my phone's harddrive. Unsure how to fix that as it is just a wizard type program.
I have been able to recognize the phone in ADB, although I cannot push any files to the phone (access denied) and have not been able to get SU access either as I am assuming he did not have root when he bricked it.
Any ideas?

you dont need to push any files to the phone with the adb, after you flash the eugene rom and it boots into recovery you just need to load up your adb and type this
adb reboot
thats it, and it should reboot your phone and if it does boot up fine then you can flash back to stock with odin from there.

Did you perchance happen to have installed the Team Whiskey DOW kernel on this phone?
Your symptoms match the symptoms of quite a few others.
http://forum.xda-developers.com/showthread.php?p=11704550&posted=1#post11704550
http://forum.xda-developers.com/showthread.php?p=11680374#post11680374

Samsung Galaxy Note 3 (SM-N900) - Rooting failed (Odin stuck), need to recover

Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!

GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.

Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !

GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.

Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.

GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!

Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !

GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.

Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?

GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.

Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/

GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?

Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots