Database Info

[Q] Unable to get phone to boot after Odin flash

Hope someone has some info.
I have recently tried to recover my phone via Odin flash. I'm flashing the GummyCharged 1.9 FE odin file. I've done this SEVERAL times w/ out any problems.
My problem now is that when the Odin flash is complete it shows "Pass" and when I reboot my phone it boots with an old version of CWM (4.0.0.1). Not only that but when I try to "reboot phone" it boot loops back to CWM and will not load ANY for of an OS. I've tried multiple Odin files with no luck. Same thing over and over.
Anyone have any suggestions? I'm used to having to recover my phone from a bricked state... but never had an issue where I push a file to the phone and it will not boot after. Tried wiping data/cache after Odin as well... Still nothing.

I would try going back to stock using Imnuts' stock ROM and PIT file which can be found here: http://forum.xda-developers.com/showthread.php?t=1111486
That has always fixed any and all issues I've been having with the phone after messing something up.
EDIT: Here is the stock EE4 ROM http://forum.xda-developers.com/showthread.php?t=1172182

hazard209 said:
I would try going back to stock using Imnuts' stock ROM and PIT file which can be found here: http://forum.xda-developers.com/showthread.php?t=1111486
That has always fixed any and all issues I've been having with the phone after messing something up.
EDIT: Here is the stock EE4 ROM http://forum.xda-developers.com/showthread.php?t=1172182
Click to expand...
Click to collapse
Hey man, I cant thank you ENOUGH!!!! After A LOT of trial and error (had to download the ee4 file from another link) I was able to get this beast to boot back up. I REALLY appreciate your quick response and help!

KaneD20 said:
Hey man, I cant thank you ENOUGH!!!! After A LOT of trial and error (had to download the ee4 file from another link) I was able to get this beast to boot back up. I REALLY appreciate your quick response and help!
Click to expand...
Click to collapse
No problem. Glad you got her back up and running. No one likes a $500 paperweight.

Props to hazard he's always helping people... just want to let you know
Your a good dude...
SENT FROM THE DOG POUND

hazard209 said:
No problem. Glad you got her back up and running. No one likes a $500 paperweight.
Click to expand...
Click to collapse
Yeah, no doubt. And I was able to do a restore on the Imnuts PBJ OBT kernel from 7/30... my problem started when I installed the new kernel version (from 8/8) and tried to backup/restore. Working perfectly now though!

Having same issue still getting recovery mode
I did a fix sd cardupdate for the rom clocking.
I had gumicharge rom on it
After 4 hours my battery was at 50% so I decided hey i can just load the rom on it again and no problem clean free.
It did not work. I am using odin.
It did not work so I got the pit file from this and it gave my system life and the ed1 file wont download it stalls out and failes i tried using
CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
or
CI510_VZW_EP1F_ALL_ONE-LTE-CP_REV3_user_CL300919_Rooted_Debloated.tar.md5
both do nothing.
My phone just sits there reboots into Manual mode and looks like my blue recovery console.
Clear cache
Upload from SD Card
and clear memory so forth.
Thats all my options.
I am now stuck with phone i cant use or update. I am at work so now i cant use the megaupload since those are blocked by our firewall.
I was able to remote to pc to get a pit file.
At this point i dont know what to do or just do insurance claim on my phone and get another one. I dont know how to fix it now.
I cant read the sd card on any computer to put stuff on it and odin is writing things to it The pit file on this fix did give me a recovery enviroment but nothing on roms are on the sd card.
roms ive tried dont load for automaticaly its just in that manual mode thing with the icon of the little android dude.
it says
Android system recover (3e)
Enter: OK key, select:Vol Up/Vol Down
Reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
bewlo it syas #manual mode* and little android guy with eclamation point next to him.
I have tried severla tiems 3 different roms

2Much2Ask4 said:
I did a fix sd cardupdate for the rom clocking.
I had gumicharge rom on it
After 4 hours my battery was at 50% so I decided hey i can just load the rom on it again and no problem clean free.
It did not work. I am using odin.
It did not work so I got the pit file from this and it gave my system life and the ed1 file wont download it stalls out and failes i tried using
CI510_VZW_EE4_ALL_ONE-LTE-CP_REV03_user_CL1014954.tar.md5
or
CI510_VZW_EP1F_ALL_ONE-LTE-CP_REV3_user_CL300919_Rooted_Debloated.tar.md5
both do nothing.
My phone just sits there reboots into Manual mode and looks like my blue recovery console.
Clear cache
Upload from SD Card
and clear memory so forth.
Thats all my options.
I am now stuck with phone i cant use or update. I am at work so now i cant use the megaupload since those are blocked by our firewall.
I was able to remote to pc to get a pit file.
At this point i dont know what to do or just do insurance claim on my phone and get another one. I dont know how to fix it now.
I cant read the sd card on any computer to put stuff on it and odin is writing things to it The pit file on this fix did give me a recovery enviroment but nothing on roms are on the sd card.
roms ive tried dont load for automaticaly its just in that manual mode thing with the icon of the little android dude.
it says
Android system recover (3e)
Enter: OK key, select:Vol Up/Vol Down
Reboot system now
apply update from sdcard
wipe data/factory reset
wipe cache partition
bewlo it syas #manual mode* and little android guy with eclamation point next to him.
I have tried severla tiems 3 different roms
Click to expand...
Click to collapse
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck

vudiff said:
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck
Click to expand...
Click to collapse
I would do this but before starting the flash in odin put the battery back in and uncheck the auto reboot box, when its done unplug from pc and remove battery, put it back in then boot up phone
blazing through on my VZ Droid Charge 4G

anoninja118 said:
I would do this but before starting the flash in odin put the battery back in and uncheck the auto reboot box, when its done unplug from pc and remove battery, put it back in then boot up phone
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
don't put the battery in during flash & leave auto reboot checked. Auto reboot will not do anything as there isn't a battery installed... it'll just turn off. Unplug the phone after you flash it & put battery back in & boot

vudiff said:
Not sure if you're going into download mode properly but try this:
open ODIN
add the PIT file in the PIT section
add the EE4 OEM file in the PDA section (do not use the phone section)
leave everything else in ODIN as default except click on "re-partition"
take your battery out of the phone
hold the volume down button & plug in your USB cable (do not let go of the volume down button until you are in download mode)
ODIN should now now show a yellow com port for your phone on top left of ODIN and your phone should display "download mode"
select start
When it's complete ODIN will show in green that it passed. Unplug your phone, put the battery back in & boot
Hope this helps & good luck
Click to expand...
Click to collapse
This is pretty much what fixed it for me. DON'T GIVE UP! Trust me, I literally had to try this several times before it booted up. I know its frustrating, trust me, but if you stick with it you can fix the phone.
Each time you're able to get to recovery mode, if you're phone doesn't boot, do like five data wipes and wipe cache. Then Odin the .pit and the EE4 from the link above in the pda field (both at the same time).
Good luck! Stick with it I know you CAN fix this!
Sent from my SCH-I510 using XDA Premium App

KaneD20 said:
This is pretty much what fixed it for me. DON'T GIVE UP! Trust me, I literally had to try this several times before it booted up. I know its frustrating, trust me, but if you stick with it you can fix the phone.
Each time you're able to get to recovery mode, if you're phone doesn't boot, do like five data wipes and wipe cache. Then Odin the .pit and the EE4 from the link above in the pda field (both at the same time).
Good luck! Stick with it I know you CAN fix this!
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
No need to wipe anything... when you have "re-partition" checked it wipes everything but the sd card

vudiff said:
No need to wipe anything... when you have "re-partition" checked it wipes everything but the sd card
Click to expand...
Click to collapse
I'm sure you're right, these are just the things that I did when I finally got it working.

I got stuck myself last night and odin started to fail every attempt, even with the pit file and following numerous instructions found around the site. I actually thought my phone was bricked for good.
I installed PST lite and selected the PIT and EE4 and selected to repartition. It took longer to do but everything came back up. Then using odin I was able to flash back to the rom I had before.
This was after an hour of trying to fix it as I mentioned and Odin kept failing.

^attempting to reflash via samsung pst lite.
loaded PIT, stock EE4. checked "repartition". when I click download, it starts, but freezes at 9%. RX_TIMEOUT shows on the phone screen.
I'm trying this method b/c Odin is not working. Same thing, just hangs, sez RX_TIMEOUT. (repartition w/ PIT, stock EE4)

sushi_stalker said:
^attempting to reflash via samsung pst lite.
loaded PIT, stock EE4. checked "repartition". when I click download, it starts, but freezes at 9%. RX_TIMEOUT shows on the phone screen.
I'm trying this method b/c Odin is not working. Same thing, just hangs, sez RX_TIMEOUT. (repartition w/ PIT, stock EE4)
Click to expand...
Click to collapse
Have you tried putting the battery back in during the flash?
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
Have you tried putting the battery back in during the flash?
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
Yes. tried both with and without. Just hangs. Can never fully make it through the flash.
Stuck with soft bricked phone.
Waiting for my wife to get home with her PC laptop. Hoping it really is just a platform issue (running ODIN on Mac Boot Camp)

sushi_stalker said:
Yes. tried both with and without. Just hangs. Can never fully make it through the flash.
Stuck with soft bricked phone.
Waiting for my wife to get home with her PC laptop. Hoping it really is just a platform issue (running ODIN on Mac Boot Camp)
Click to expand...
Click to collapse
What version of Odin are you using? I'm pretty sure I'm using Odin v. 1.82 or something close to that. Not too sure that it would make the difference. Just a thought.
Also, I had to Odin QUITE a few times to get it back up. I had even run the Odin w/ JUST the .pit file. Thought I read somewhere to run the .pit an UNCHECK the repartition box (I know it says it'll give you an error but I did not get one).
All in all, not too sure what exactly it was that finally got it working. But I eventually ran the .pit and ee4 (both posted in post #2 of this thread). Then when my phone booted up, it looked like the problem remained. I had to get back to work from lunch so I just put the phone in my pocket. Then out of nowhere I heard the boot animation come on.
Just make sure you read through, pretty much, all of the threads that deal w/ this stuff. There is almost always someone that has come across the same problem that you may have and almost always someone who had figured out how to fix it.
Good luck, this CAN be fixed!

Soft Brick Tmobile Galaxy Tab Plus

Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!

kaizasoshi said:
Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!
Click to expand...
Click to collapse
this is very easy to fix fortunately you have not hard bricked LOL now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.

jmar8124 said:
this is very easy to fix fortunately you have not hard bricked LOL now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.
Click to expand...
Click to collapse
Thanks Bro, will try this when I get home from church

Do you know where I can find the tmobile firmware file I need?

There you have it :
www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
P_

pakalrtb said:
There you have it :
www.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-T869&r=5#regiona
P_
Click to expand...
Click to collapse
Thanks Bro!! It worked!!

soft brick galaxy tab 7.0 plus
I have the same problem as described by kaizasoshi on a GT-P6210 (WIFI only model) and can get to download mode. I haven't been able to find a copy of Odin 1.8 to download so I have Odin 4.0.3 - hopefully that'll work. The megaupload link for Odin 1.8 gives you software Odin 1.8.2 which turns out to be some sort of MRI operating software.
I used the link provided in the response for the GT-P6200 model, did a search, and I can't find the firmware file for the P6210 anywhere on the site. I found a file elsewhere on XDA supposedly is the firmware file for my model P6210 and when adding to PDA I get an error "Invalid Image File Type" The file name that I found is named GT-P6210_XAR_P6210UEKL1_P6210XARKL1_P6210UEKL1\P6210XARKL1_P6210UEKL1_HOME.tar.md5
Does this sound right? Does anyone have any guidance for me (besides stop bricking my Tab)? Thanks

soft brick galaxy tab 7.0 plus - continued
Well I found a version of Odin 1.8 and it took the tar file without an error message. I started flashing the file to my P6210 and it went well for a couple of minutes (about half a green bar in the first block). Then something went wrong and ODIN started alternating the below messages:
<ID:0/004>Added!!
<ID:0/004>Removed!!
<ID:0/004>Added!!
<ID:0/004>Removed!!
And while showing the above, the P6210 screen started alternating between a black screen and the below message:
Firmware upgrade encountered an issue.
Please select recovery mode in Kies & try again.
I watched this continue for over an hour in this loop (no progress on the green bar), then disconnected and reconnected the P6210. I launched Kies and tried troubleshooting but just got the alternating screen again on the P6210 and starts and stops of Kies troubleshooting. It looks like it's pretty hosed. Any suggestions?
Help would be greatly appreciated.
As an aside, the only thing I've done to the tablet was do a one step root about 3 months ago and I think two product updates afterwards (reapplied the root after each). The tablet ran OK but I started getting the auto shutdowns other have gotten, along with several instances of a warm battery and high battery rates of consumption. It didn't behave this way all the time. Finally two days ago, while on the charge,r I found it locked into the Tab startup screen. I could get it to boot into recovery but kept getting lots of red error messages, like it was looking for files that weren't there, then I'd reboot and it would go back to the locked startup screen.

Can you get into recovery by holding up and power on (release power after it boots, but hold volume up)
Sent from my HTC Glacier using Tapatalk

Yes I can get to recovery now. Since my previous post, I recharged unit overnight and attempted to reflash OS. This time, Odin runs all the way until the first green box says PASS! Odin Message box says <OSM> All threads completed (succeed 1/failed 0). Then message box cycles thru ID 0/004 Removed ID 0/005 added!! then ID 0/005 Removed!!, then ID 0/005 Added!!
At this point Odin doesn't do anything else. The P6210 then starts giving a bunch of failed messages - failed to mount cache(no such file or directory), Can't mount /cache/recovery/command, then goes into Manual Mode then message failed to mount /efs (no such file or directory) install application for customer: Can't mount /efs copy application failed. Then meesage Applying multi CSC then failed to mount /efs, then multi_csc can't mount/efs
Then multi-csc applied failed.then more messages on failing to mount cache can't mount cache recovery log/last log
Then at this point the top of the screen offers rebot/apply update from sd/wipe data-factory reset/wipe cache partition. Through all of this I have not unplugged the P6210 from the PC.
I select reboot system now and press power button (still connected)
Get a bunch more messages about cant open cache recovery log. Then it goes to the Samsung Galaxy tab screen and just hangs.
It seems there's some files missing that is causing the unit to hang.

added/removed sounds like could be faulty wire connection.
which firmware are you trying to flash may we ask?
May be useful to find a .pit file with stock firmware, if there are any around for your device.

kaizasoshi said:
Thanks Bro, will try this when I get home from church
Click to expand...
Click to collapse
no probs my friend happy to help haha

soft brick galaxy tab 7.0 plus - continued
I've also tried changing the usb/samsung cable from aftermarket to OEM and changing USB port used on PC. Reflashed PDA file, No change. The reflash appears to complete but is followed by the error messages identified previously. The file I'm attempting to flash w/Odin 1.85 is named P6210XARKL1_P6210UEKL1_HOME.tar.md5. The file is 894.011 MB. I've downloaded it twice and no difference in flash result. I'm not having any luck finding a PIT file for the P6210.
Still looking for PIT file.

kaizasoshi said:
Is there anyway to get out of this. It only shows the Samsung Galaxy Tab Logo, I can also get into recovery. I tried to wipe everything to see if it would boot up, but its still stuck on the startup screen. Any help would be much appreciated!!
Click to expand...
Click to collapse
May I ask what you did to soft brick? Be good learning experience for everyone. Thanks.

soft brick galaxy tab 7.0 plus - continued
I've also found these 3 other files associated with the P6210. They are:
GT-P6210-MULTI-CSC-OXEKK1_RST.tar.md5
P6210_APBOOT_P6210XXKL2_CL583761_REV02_user_low_ship.tar.md5
P6210_CODE_P6210XXKL2_CL583761_REV02_user_low_ship_16G.tar.md5
Would loading these files via Odin possibly help with my problem? I'm not sure which files would be loaded for the different parameters (PIT, BOOTLOADER, etc). It appears the CSC file would be loaded for CSC.
PS: I don't know what happened with kaizasoshi as far as how his TAB problem initiated, but mine had been experiencing SOD, auto shutdowns and warm battery when plugged into charger over night for the previous several weeks. I picked it up one morning off the charger and the P6210 was frozen on the startup screen and wouldn't finish boot or shut down. It would go into recovery using the power and volume switches.

hi all, i have the same similar problem as TS but mine's a P6200 tab, heard that i need a pit file & the firmware ver(singapore) to flash it...
where do i get those files including odin? i got the firmware via sammobile.com, but no idea to get the pit & odin files,... will any kind souls direct me to them?

I found a PIT file a few days ago, supposedly for the P6200 using Google. I don't know if it works or not. I have a P6210, so I don't think I can use a P6200 PIT.
PIT Link:
http://www.sammobile.com/forum/showthread.php?t=2856
ODIN Link:
http://www.cpkb.org/wiki/Samsung_Odin#Samsung_Odin3_download_links
Pick a version. 1.81 and 1.85 seem popular.

any new updates on this? im having the exact same problem and have tried all the previously mentioned files through Odin with no positive results. any help would be appreciated. i have a US version 6210

yeah.. dont flash a tab plus firmware unless you're sure its for your specific model
either T869-Tmobile/WifiGT-P6210/or G version GT-P6200. If youve flashed the previously mention files, you've probably done some serious damage.
Best option now: Find a device specific firmware WITH a .pit file, flash with Odin/Heimdall with fngers crossed.
Other options: tell them you hooked it up to iTunes to sync your media.. lololol
hope you get warrantied..

chrisrotolo said:
yeah.. dont flash a tab plus firmware unless you're sure its for your specific model
either T869-Tmobile/WifiGT-P6210/or G version GT-P6200. If youve flashed the previously mention files, you've probably done some serious damage.
Best option now: Find a device specific firmware WITH a .pit file, flash with Odin/Heimdall with fngers crossed.
Other options: tell them you hooked it up to iTunes to sync your media.. lololol
hope you get warrantied..
Click to expand...
Click to collapse
well that just sucks!! honestly with all the SODs and reboots i just wish samsung would give me my $350 because this thing hasnt worked well from the begining. guess its back to samsung

[Q] botched ROM load, now stuck in recovery hell

I got in a SK4g for my wife intent on upgrading her current phone. I own a 4g myself, and have Rooted/ROM'd it with no issues, we we thought it best to get her the same phone for ease of use/manipulation.
I got the phone in and used superoneclick to root it, then went through the process of putting CWM in place and installing GenericGinger_2.0_SK4G. The process ran smooth as glass (as expected) until it got to reboot. On reboot it hung up on the sidekick screen. After about an hour of waiting I pulled the battery and restarted the machine.
It came back up in recovery mode with the stock recovery (blue) text. Since then I haven't been able to get it to do anything but restart into that recovery screen. Odin doesn't see the phone in download mode and t839-Sidekick4G-UVKG2-One-Click does nothing. It shows it uploading, reboots the phone, and I'm back at the blue text. flashing the bootloaders with One-Click shows success on everything *except* uploading the bootloaders. If I tell it to re-install packages I get a 'cannot validate signature' response. I've tried using android commander to push CWM's recovery file to the phone and get 'permission' denied.
I've done a lot of searching on this site, trying most suggested fixes I've come across with no luck.
what can be done with this phone to get it back in operating condition?
Thanks in advance!

try installing kies odin wouldnt see my phone until i installed it

Kies installed and Odin saw the phone. excellent, thanks!
now, the next issue... lol
I used Odin to push KD1OdinSTOCK onto the phone. it's doing more than it was (going to the initial sidekick screen then dumping to recovery). Now it'll load through the sidekick and samsung splash screens, then reset and do it again. The same thing happens when I tried StockKG2ODIN. I'm using the sk4g.pit that I pulled from this site, could that have anything to do with it/is there another one around that I could try? Anybody have thoughts or ideas on what to do next? I've tried using t839-Sidekick4G-UVKG2-One-Click again, but it nuked the drivers kies put into place and dropped the phone back to what it was doing before.

okay, I did some light reading of this thread here
and followed the directions closely. I also went through sduvick's list of things to do with the following results:
Black screen, no logo.
1. Get into download mode by using VolDown+Touchpad+Power
2. flash full sk4g.tar.md5 as posted.
device will boot through the logo and splash screens, then repeat. note: if I leave the USB cable plugged in on reboot it will go to the battery screen, otherwise it just boot loops.
_________________________________
logo only
1. Download mode
2. Flash full package
device boot loops
_________________________________
Can't flash recovery/boot/sbl
1. Download mode
2. use PIT only, run with repartition checked
3. reboot/reDownload mode
4. run the full image in Odin.
PIT only returns a black screen on the device. running the full image in afterward returns to the boot loop.
_________________________________
Anything else
1. Download mode
2. Full tar.md5 flash in Odin
3. Ask if it doesn't work
okay, so I'm asking...
I'm still able to boot into recovery mode (blue text).
I've noted a bit of strange behavior when trying to boot into download mode. holding vol down + trackball + power does nothing. however, if I plug the phone in while powered down while holding down the trackball it'll boot into download mode, no power or vol down required.

If you can't flash with Odin, you may have a hardware problem.
Judging from your issue with installing Kies, you had a driver problem previously.
Seems that you are bumbling in the dark here. Once again, people need to be better prepared to Odin their devices before they start modding them.
In fact, getting Odin working should be the first thing a person should do with their phone after rooting and installing CWM.
Anyhow, try a different version of Odin. If that doesn't clear up your problem, I suspect some bad blocks in your flash memory are responsible here. It's a dorment issue that would really only be a problem when you flashed the device. If that's the case, you have a new paperweight.
Good luck.

i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda

I don't think the problem is that I can't flash with Odin, but that the device isn't loading the ROM that's flashed. poking around in the filestructure with android commander after a fresh load shows that the system makes it onto the phone.
Speaking of poking around with Android Commander, I've noted that the device is software rooted, but not hardware rooted. the default.class file shows ro.debuggable set at 0 where it should be 1. this is keeping me from just pushing the CWM recovery onto the system and restoring the backup I made before getting into this mess. Anybody want to help me pull/edit/flash the image to change that?
As for a driver issue, that's a good possibility given that the one-click uses a driver set, kies mini uses another, kies has a different one yet and we (as a community) started screwing with the t839's using vibrant drivers. I've got them all. thusfar the only drivers I've found that work with both flavors of Odin I have (1.61 and 1.85) would be those that came with the Kies (thanks for the tip pmp326).
On bumbling in the dark, yes, yes I am. There isn't much of an instruction manual for Odin past what's written here, and 90% of that is 'put your phone in download mode, connect Odin, plug the pit in pit and the tar in PDA make sure only auto-reboot is checked and hit start'. to be honest I haven't had to use the program previously as the stock one-click actually worked on my T839. This new device is being ... difficult.
the dormant bad blocks issue you spoke about, was this something found in new-out-the-box phones? I haven't seen a lot about that in the threads, can you point in at more info, please?
at any rate, it doesn't matter which version of Odin I use, I got the same result from both. I tried using a different cable/different USB port as well. I haven't tried using a different system (yet), but don't want to go through all the trouble of setting up everything on another box. Win7 is finicky enough, trying to get everything operating on Server2k3 would most likely end up a challenge. *lol*
I'll try repartitioning with KG1 when I get back to the house.

Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.

also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
I've gotta pop the debug lock in the default.class to be able to push anything into the system folders with Android Commander. I've found a nice walk-thru to do this, it just requires a little knowledge of c++ and some patience. with any luck I should be able to pull default.class out of its img, edit it and flash that back (most likely with Heimdall since it can do itemized flashing).
pmp326 said:
i never could get kd1 to work try kg2
use pit check repartion and place tar file in pda
Click to expand...
Click to collapse
tried it, no joy.
pmp326 said:
also i had some troubles a while back while in recovery wipe data and cache turn off phone pull sd card then flash with odin
Click to expand...
Click to collapse
tried this, brings me back to the boot loop.

orange808 said:
Sounds like you are getting far enough to get your device working again to me.
If you can manage to get access to the file system with adb or Android Commander, you may be able to push the rest of the OS files you need directly. This may provide a way to get around your flashing problems.
Try adding the missing files directly with Android Commander.
Click to expand...
Click to collapse
currently I'm running into issues with getting ADB to push onto the system as the system is claiming it isn't rooted. Is there a way I haven't read about or found to root the phone without getting into the actual O/S (i.e. from the blue recovery screen)?

If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)

rpmccormick said:
If you can get in to CWM Recovery you are fine.
If you cannot, just ODIN to stock.
If you cannot do that, or it doesn't boot after that, try a different PC, os, or drivers (x86 os is usually easier then an x64 os).
If it is still no good, buy a new phone on ebay .
Once booted, Root and install CWM first thing.
Once you are in CWM Recovery...
1) Check mounts (everything should be mounted, and therefore read "unmount [...]")
2) Format EVERYTHING one at a time: cache, data, system, sdcard (optional).
(sdcard should be fine, but to be sure you can format it too after backing it up to PC first and restore what you need after)
(you probably don't need to Wipe and Wipe-Dalvik as they should already be gone, but go ahead and do it anyway)
3) Check mounts again!
4) Install a ROM (must reload it to your sdcard first if you formatted your sdcard)
5) Check mounts one final time before rebooting.
That should ALWAYS work.
NOTE: This was said before: "2. flash full sk4g.tar.md5 as posted.", but that doesn't seem right... you should not be flashing a .md5 file... you need to flash the .tar... the .tar.md5 is just a checksum. (right?)
Click to expand...
Click to collapse
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
I like turtles.

Artemis257 said:
Wow... did you even *read* before posting? fail. I mean, thanks for taking the time to write that up and all, but you just repeated everything already said up to this point and included a summary of the ROM for n00bs thread.
Click to expand...
Click to collapse
Even the end... I mean, your not trying to odin a "tar.md5" are you?

rpmccormick said:
Even the end... I mean, your not trying to odin a "tar.md5" are you?
Click to expand...
Click to collapse
No....

Sorry man. I've never had to ODIN (this phone). I say check the md5 to make sure you downloaded a good copy, and maybe try a different USB cable. The ADB method seems nutz... if it doesn't boot after a successful ODIN, the phone is probably a paperweight.
Good luck!

[Q] Problem during rooting help

I was attempting to get root access to my galaxy tab 2 10.1 running android 10.2.1 (or whatever the latest Samsung update was it is 10.2 on my phone but am sure it was 10.2.1 on the tablet.
I was following this guide that someone here recommended
http://www.ibtimes.co.uk/articles/4...-p5113-android41-jellybean-android404-ics.htm
I set usb debug and made sure the drivers were on my pc and made sure KIES was completely not running
Followed the instructions to the letter but should have worried when I found the instructions to get to download were wrong - I found on videos that it was reboot using power and right volume key. That was successful
It connected to ODIN fine and the yellow box came up
I made sure the two boxes were ticked and then searched for the file
CF-Auto-Root-espresso10wifi-espresso10wifibby-gtp5113.zip and started ODIN
it seemed to be going fine until suddenly a red box came up with update failed
Now all I can get on the device is "firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
No matter how I try to restart this I get the same screen and imagine I couldn't connect to kies even if I should
Can anyone help as I am worried that I have bricked my device - I was looking for a simple way to get root without flashing a whole rom - or is that what I was doing anyway?

Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:

Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again

n0is said:
Here is a link that may can help you : http://forum.xda-developers.com/showthread.php?t=1722745
Try to do the point A to install CWM Recovery and root correctly the tab then do the point E to install the stock Android 4.0.4
ps : if you want to do something to your tab, try to search here before other websites, big community, good informations/tips (personnal advise) :good:
Click to expand...
Click to collapse
I will take a look but so far the only thing I get is the message to connect to KIES and it wont of course connect - cant get into any other modes - you would think they would have some kind of hard boot recovery button that gets you to basic screen to download the latest firmware.
And I did start here and believe that this led from a post here - I was trying to find the least complicated method of getting root access without changing what I already had too much - the only other process that I found on here seemed to have lots of people reporting problems if it wasn't a 3g model
It is beginning to look like I may have found out what bricking is - thanks for the reply anyway

would like to do that
mjrshark said:
Maybe file you downloaded is corrupted , redownload it from xda or sammobile and do steps again
Click to expand...
Click to collapse
In fact the instructions do say if it doesn't work first time, to run it again with the boxes unticked - the problem is that I cant get back to download mode, or any mode other than the message to connect to kies, so have no way of doing this. So looks like it may have bricked - is there any way of unbricking a tablet?:crying:
It's going to be an expensive mistake especially as I haven't even had the £50 cash back from Samsung yet and I would have to pay full price now to replace it,

So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium

not optamistic but will try!
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I will try but I don't think it is going to work. Whenever I connect the tablet by USB I get the usb connecting sound followed immediately by the USB disconnect sound - this just continues to happen every 4 seconds or so all the time that the device is connected. At the moment I have it on charge as once the error screen comes on it doesnt seem to go off for a very long time and then it wont start unless I charge it first. After a few minutes on charge - The firmware upgrade encountered an issue message comes up. I am going to leave it a while until I am sure it is fully charged and then try what you suggest - not optamistic though since I now realise that it is not even connecting properly. I just have a bad feeling about this. I had to disconnect it from the power yesterday because the error screen stays on continuously and the device starts to get warm
Assuming that I ever manage to get a stock image installed will this mean I can go back to normal kies updates - all I really wanted was the standard samsung android O/S but with super user added.
Unfortunately I had read the linked article a while back and what made me more confident was the statement that said it was "virtually impossible to brick this device"

Since it's still going into Charging mode and spitting out error messages, it's not completely bricked. It's just in a reboot loop (a.k.a. soft brick).
Keep trying to get it into Download mode. Sometimes the timing is a little tricky if it's in a boot loop.
1. Disconnect it before trying to get it into Download Mode. If it's plugged in (charger or PC), the device will go into Charging mode instead.
2. Hold the Power button for 10 seconds to make it reboot.
3. When you see the screen turn off, let go of Power and then press and hold Power and Volume Right/Up.
4. If done correctly, it will immediately go into Download Mode. If you see the Samsung logo instead, repeat from Step 2.

some progress but still stuck - any more ideas please
samsgun357 said:
So did you remove it from Odin after it failed?
If you connect and pull up Odin, even though its not in download mode, do you get an active com box showing its connected?
Have you tried kies yet?
There is a simple method of rooting in the link posted in the previous post by n0is. At this point you might have to flash a stock image before you try and root again. If you can get an active com port in Odin, run a stock image first, they can be found here in xda. Get it booted up and then make sure you are on the latest android version, its 4.1.1 here in the US. If you try and root first and then update, you will lose root so update first to avoid rooting twice.
Just to clarify the root procedures,
Odin the cwm recovery .tar from the thread.
Reboot to recovery then flash the super user zip for the p5113. It will ask you about erasing stock recovery or something like that, check yes.
And that's it, simple enough
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Hi well thanks -
when I connected Odin it did show up yellow and so I downloaded the P5110 stock from from the other thread - all went well and it reported all OK and re-booted - saw the animated sequence but now it has stalled on the samsung logo and still wont connect to kies
So still stuck but at least it has moved on - The instructions on the other page were a little unclear about one stage
It said if there was pit file included to set something and tick repartition - this was all in one line and so I assumed part of the pit instruction - as there was no pit file I did not tick re-partition - I wonder if I should have done?
I have just reconnected to ODIN and the ID Com is still lit up yellow so presumably I could try running it again, or should I look on here for another stock rom - I am wondering if I have somehpw scewed up the bootloader and if so how I go about restoring it
ODIN is the only thing it connects to right now

SOLVED: N986B/DS KSA and Odin is failing to flash. Would greatly appreciate assistance. Thanks!

Condensed for brevity:
Unlocked bootloader and Debug USB enabled. Went to flash an AP and it failed. Tried to use Frija to get the most recent update, found N986BXXS3EULH REV01, tried to flash the AP/BL/CP/CSC to refresh the phone and it's failing.
Everything matches my phone when I typed *#1234# (EULB/EULH) except the download has REV01 added to the end.
Phone is stuck in download mode no matter how I reboot it. Phone isn't bricked but won't do anything else.
Edit: Updated to using Odin 3.14.4 instead of 3.13.1
Edit 2: Figured out the phone is freezing after any fail (brightness doesn't change with volume keys). I get the failed PIT as well as "Can't open specified file (Line:2006)"
Edit 3: Re-opened Frija and it gave me an entirely different FW this time that superseded what I had on the phone originally and the DL'd file (*3EULH became *3EVA9).
Tried to use new CSC and it keeps failing at prism.img. It's progress but not really at the same time.
Edit 4: It lets me install the BL and CP for either/or EULH or EVA9 but neither CSC or AP work ever. I'm thinking I just have a bad firmware or something.
Final update for the night: The files are good. Compared hashes across multiple downloads. Phone isn't seen in Samsung Smart Switch and there doesn't seem to be a recovery menu. TWRP or otherwise.
If anyone has any ideas please let me know. I'm pulling my hair out because it's brand new. All I did was try to start by updating the stock firmware with Odin (after bootloader unlocking and USB debug enabling) and this happened.
-------------------------------------------------------------------------------------
Day 2: Moved back to Odin 13.1 and extracted PIT from EULH CSC, installed it, then did the BL/CP, installed fine. Still froze with CSC/AP. Then attempted to try it all at once. PIT, CP, BL, CSC, and AP. It actually starts installing now. But it specifically always freezes at the super.img portion. So while I'm unsure what's going on now since I'm still trying to install the correct official ROM, I'm starting to think the ROM is somehow incompatible with my phone.

HERE'S THE ANSWER! Many thanks to those who attempting to help. We were doing and advising everything correctly.
The problem is the PC itself. Which was why the issues seemed so varied. I attempted every USB in my computer, none would flash (they drop out randomly with my phone), and the first sign I didn't realize was a sign was the phone wouldn't work on my USB-C ports, only 3.0/3.1.
I run a Threadripper 3960x on an Aorus TRX40board. I had to go to a 2015 touchscreen laptop to do this. If you're having issues then literally try a new PC if possible. If you see that it isn't connecting to Odin on USB-C, then you may well have the same issues I was having.
Note: this may be a driver issue, as I used every one of my 20-ish ports and they all still failed, as well as about 5 different cable options to go between USB/USB to C and USB-C to USB-C.