Database Develop

Bricked phone, can't access download mode. Please HELP!

OK So,
I recieved a Galaxy S today, and having some experience with a HTC Desire HD I knew how rooting/flashing roms work. But this is different.
I have flashed twice so far. Once trying to get to CM7 MIUI but that failed, leaving me in a recovery loop. So I panicked. I then used someones one click odin restore on these forums, however being the idiot I am didn't read that that was vibrant firmware and not i9000 firmware. Download mode was working 100% before I did this, and now I can't get it to work for the life of me. Can someone please help? I am stuck at the AT&T boot logo and I can't do anything. I have the correct firmware from my carrier, I know how to flash it back to stock, but I can't get into the freaking download mode. Why is this? Is it disabled for good?
Please don't tell me my phone is a brick now....

Try the jig method. You can make your own or plenty on eBay. But I think you are in the 'not good ' realm. But usually you don't get to the boot screen either so there is some hope.
Sent from my GT-I9000M using XDA Premium App

I've bought a jib off ebay so I will see if that works. What I am trying to understand is why would doing what I did somehow disable download mode? That makes no sense to me. And the phone isn't fully bricked since the boot screen comes up.

Download mode is software based and you flashed new software on the wrong hardware. It's on the bootloader I believe. The jig tries to get it forced as I think there is a backup bootloader but not at all sure on the details.
Sent from my GT-I9000M using XDA Premium App

I see. Well I will try the jig and see what happens. If that doesn't work I will send back to Samsung and blame Kies for the problem. Which will be a bit sus since I have an at&t bootlogo and I live in Australia but oh well
One other question I have is if I do get into download mode, I have all the stock firmware files from SAMfirmware, however the files are only a pda file and a 512 pit file. I was under the impression I needed a csc file and something else? Or is it all included in the .tar PDA file?
Thank you for all your help I really appreciate it!

Usually what you need is in the tar for the pda spot. The others are more for mix and match. Just be aware that some firmware does not have all the files as they aren't meant to be flashed with pit. You will want to flash a pit so you'll need a complete one. My stock has no dbdata.rfs for example and if you use a pit then you get a mounting error as no partition is created.
Sent from my GT-I9000M using XDA Premium App

I had a look inside the .tar file which is for I9000DTJP5 (exact firmware that I had on stock) and there is no dbdata.rfs like you said. So you are saying this firmware that I got from samfirmware.com is incomplete? And if I flash with the PDA + 512.pit I will get mounting errors? So do I just flash the PDA firmware by itself and tick re-partition?
Thanks.
PS I used this http://forum.xda-developers.com/showthread.php?t=731989
So I'm guessing this changed my kernal and modem? I beleive the kernel does not come included in the pda .tar... or does it?

The pda will have the zImage in it (which is the kernel).
But try to find one with the dbdata.rfs file. For some reason I think jpy is one people use (anyone else following this thread). There are some roms that people describe as 'working everytime' and I think that its because they are complete roms. I'd also look at ezboot thread as you will want to make sure that any capivate bootloader gets removed and updated with an i9000 one but stock roms usually have the bootloader I believe.
Have you (out of curiousity) tried the captivate download sequence (vol down and power - I think - maybe while battery is inserted)?
Also might try the ADB method of prompting download for captivate.

Yeah none of samfirmware comes with the dbdata.rfs file. Other option would be to flash to something like Darky's rom. I must have screwed the boot loader since I came from froyo > CM7 bootloader and that's when things went wrong. What file removes & affects the bootloader from Odin?
Yes I've tried the captivate download mode which is Volume Down + Power like you said. ADB is impossible since the phone isn't operational.
So that easy one click odin that I used flashed the modem, the bootloader, and the rom. This is going to be hard to fix.
I need to use firmwares from my country... and JPU isn't listed under australia on samfirmware website

Well the bootloader for froyo and cm7 are the same but the problem was the file system was not (cm7 uses yaffs or something - not a linux person...) so you had to do a full flash with pit (and of course not with captivate rom in retrospect) which did screw up the bootloader and more.
You can also get a service (professional shops) called JTAG that opens up the phone and reflashes just the bootloader from point on the motherboard. Some information here on XDA. Its a specialized deep hardware fix but it solves even hard bricks that won't turn on (unless there is physical damage of course). Might cost $100 or so though.... Might be worth a search for local shops that do that.

found this post (and it references another thread).
http://forum.xda-developers.com/showthread.php?t=749641
But its not good news... These are from last year but it looks like people were hooped in similar situations though i think the JTAG method has been formalized since then.

OK! The Jig works!!!!!!!!!! SO happy. However I am facing the problem of flashing now. Odin gets stuck at cache.rfs for about 20 minutes until I disconnect the phone and try again.
The files I am using with a 512.pit with re-partition checked are...
Phone:MODEM_I9000DTJP3.tar.md5
PDA:CODE_I9000DTJP5.tar.md5
CSC:CSC_I9000XSAJP4.tar (my countries correct csc file)
Here is my log:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> Enter CS for MD5..
<ID:0/004> Check MD5.. Do not unplug the cable..
<ID:0/004> Please wait..
<ID:0/004> Checking MD5 finished Sucessfully..
<ID:0/004> Leave CS..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> zImage
<ID:0/004> dbdata.rfs
<ID:0/004> factoryfs.rfs
<ID:0/004> param.lfs
<ID:0/004> modem.bin
<ID:0/004> cache.rfs
What am I doing wrong?
Thanks

Try another version of odin? Or another rom I've had bad versions of both.
Looks like more lines about md5 stuff than I recall too.
Sent from my GT-I9000M using XDA Premium App

Found the culprit... the csc file which I obtained from XDA was corrupt... so I used a different one. My phone is now up and running. I just want to say a big thanks for your time and advice. Thanks

[Q] Can only use 'Download Mode'

Hi guys and girls.
I've been frantically searching XDA for the last few hours for a definitive answer, but to no avail, so thought it's about time I just asked!
I have in my possession a Samsung Galaxy S19000, that will only go into download made.
Here's how it happened........
This morning, I was given the phone by my brother in law and asked to root it and upgrade it to a newer/better rom. When it was passed
to me, it was.....
Firmware: 2.2.1
Baseband: 19000XXJY
Kernel: 2.6.32.9
[email protected] #1
Build: FROYO.XXJPY
After a successful root and upgrade, the phone ended up like this...
Firmware: 2.3.7
Baseband: 19000XXJVK
Kernel: 2.6.35.14-g3088622
Build: CyanogenMod-7.2.0-galaxysmtd
The new Rom, as nice as it was, wasnt what he wanted, so he asked me to restore it back to it's stock state. I went into CMW and did a restore, but it failed, and now the phone will only go into download mode.
I've tried flashing a stock rom via Odin, but it got as far as the 'Nand write' stage, then hangs.
Kies doesn't show up the device in 'Emergency firmware recovery' either.
I no all is not lost, so I'm not giving up. Any help will be much appreciated.
:fingers-crossed:

Can you post the whole Odin Log?
Normally this happen when the partitions on the embedded multi media card gets corrupted for whatever reason, also known as the emmc.
Maybe it helps to flash the pit file to repartition.

To add.....
When the phone is off, it displays the 'phone and computer with an explanation mark triangle inbetween symbol', and Kies doesnt recognise it. When I enter download mode, Kies hangs at 'Connecting' for.....well..ever! So atleast I know it's recognised by my PC (ish) and it isn't completely dead :silly:

I had the same thing with the triangle a few months ago.
I just flashed a Stock Firmware with Repartition. Just be sure with Odin that you have ticked the right things Afterwards it worked.

Thankyou for you reply, and sorry for the delay posting back. God damn new user restrictions!!!
KUN1 said:
Can you post the whole Odin Log?
Click to expand...
Click to collapse
Heres what Im getting...
Code:
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I9300XXDLJ4_I9300OXADLJ4_368423_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.img
<ID:0/009> NAND Write Start!!

First try it with Repartition. If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12

KUN1 said:
First try it with Repartition.
Click to expand...
Click to collapse
You'll have to excuse me, I've never had problems problems before, so I've only had to use the PDA box till now.....
Is that the re-partition tick box, or the re-partition PIT file box??
KUN1 said:
If that doesn't work, you may have a look at this thread http://forum.xda-developers.com/showpost.php?p=26285877&postcount=12
Click to expand...
Click to collapse
Christ that looks involved doesn't it! I think that be a last resort as it looks like I'll need to clear a day in my diary before I start!

For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.

KUN1 said:
For the moment you can ignore the second thread
Find a 3 File (PDA, Phone, CSC) Firmware ( maybe samifirmware.com ) , then download the 512 pit file for the GALAXY S! and the flash the Firmware with pit file and repartition.
Click to expand...
Click to collapse
SOLVED
I couldnt sleep, so decided to have another bash at getting this phone going again.
Many many thanks to KUN1 for hunting down and PM'ing me the necessary Odin MD5 and PIT files to use for the method he posted above.
:victory:Success:victory:
You've been a life saver sir :good:

haha no problem

[ODIN][TAR] 4.3 I9505GUEUBMH1 Full Rooted Restore

Hello Everyone
This is the Full Odin Firmware package including the Modem Fix from SamuriHL. This firmware package comes Rooted 4.3 I9505GUEUBMH1. If you do not want the hassle of pushing the OTA, you can flash this. ( THIS IS NOT FOR THE I9505/I9500 or any other carrier branded S IV) please don't ask. You must be bootloader Unlocked to flash this. If you want to restore your phone to 100% stock simply click Full unroot in SuperSU and then Re-lock your bootloader.
(DISCLAIMER) Please read and follow the instructions carefully. I nor anyone else on this forum is responsible if you brick your phone, lose your job, or life as you know it ends. Make sure you fully Understand what your doing before you do it. Modifying any phone comes with a risk.
Instructions
1. Download the I9505GUEUBMH1_FULL_ROOTED.tar package from HERE
2. Make sure you have the USB Drivers installed and you have Odin 3.07
3. Please do not flash this if your low on battery, Go charge your phone!
4. Open up Odin and click on PDA, then select the I9505GUEUBMH1_FULL_ROOTED.tar package you downloaded from #1
5. This is a massive file give it time to load up in Odin and Make sure you have a COM PORT in Odin ( any )
6. Click Start and wait till it finishes flashing
7. If your phone does not boot right back up then boot into stock recovery and Wipe Data Factory Reset.
That's it profit.
BIG THANKS TO connexion2005, Chainfire, SamuriHL, and Illogic6, sextape, rwilco12, Tana
If you appreciate the work a THANKS or DONATE would be great!

Reserved
Sent from my GT-I9505G using Tapatalk 2

Link is up finally!!
Sent from my GT-I9505G using Tapatalk 2

This is great. Thanks for posting this! Now we can feel a bit more confident playing with the phone knowing we can restore it.

After having previously flashing the 4.3 OTA I flashed this 4.3 MH1 with ODIN to try out the new radio. Everything seemed to flash fine but the phone is still showing MFD baseband.
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505GUEUBMH1_FULL_ROOTED.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> modem.bin
<ID:0/006> NON-HLOS.bin
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flash this as phone:
http://www.mediafire.com/download/xtp9844uj42ov58/modem.tar.md5

SamuriHL said:
Flash this as phone:
http://www.mediafire.com/download/xtp9844uj42ov58/modem.tar.md5
Click to expand...
Click to collapse
Still showing MFD radio after flashing that.
Code:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NON-HLOS.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> modem.bin
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
<ID:0/006> Receive Response from boot-loader
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!

Then you've got some issues. Stuff I can't even begin to help with.

I am not sure why your modem is not changing did you do anything different the what the instructions are in the OP?
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
I am not sure why your modem is not changing did you do anything different the what the instructions are in the OP?
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I flashed just like the OP. I ended up flashing your 4.2.2 MFD restore, fully unrooting, locking bootloader, and then just taking the 4.3 update straight from Google over the air, settings/about/system updates. Now I have the MHL radio.
I'm not sure why my phone wouldn't take the modem but your 4.2.2 restore worked nicely. Thanks.

Yeah I am not sure why you had that issue I reflashed MH1 many times with no trouble making MH1 modem stick if I was on MFD.
Sent from my GT-I9505G using Tapatalk 2

MJHawaii said:
Yeah I am not sure why you had that issue I reflashed MH1 many times with no trouble making MH1 modem stick if I was on MFD.
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
Dumb questions... Do we have to put the phone in download mode? Or will Odin take care of that, also, does USB debugging need to be turned on?
---------- Post added at 09:51 PM ---------- Previous post was at 09:38 PM ----------
Sammy4Life said:
Dumb questions... Do we have to put the phone in download mode? Or will Odin take care of that, also, does USB debugging need to be turned on?
Click to expand...
Click to collapse
Answered my own questions.... the answering is yes and yes.

does this work for m919v?

Mateoftw said:
does this work for m919v?
Click to expand...
Click to collapse
No
Sent from my GT-I9505G using Tapatalk 2

Anyone has the CSC package from this firmware?
Or older firmwares?

Hi there,
Can someone explain to me why this can't be used to convert a standard i9505 into a i9505G?
I'm currently running a GE ROM on my i9505 and the phone is, for all intents and purposes now a Google Edition phone, it jas the same HW and can run the same software, so where are the limitations that stop us from flashing a package like this in Odin and getting an official i9502G with OTA support and all?

CommanderROR said:
Hi there,
Can someone explain to me why this can't be used to convert a standard i9505 into a i9505G?
I'm currently running a GE ROM on my i9505 and the phone is, for all intents and purposes now a Google Edition phone, it jas the same HW and can run the same software, so where are the limitations that stop us from flashing a package like this in Odin and getting an official i9502G with OTA support and all?
Click to expand...
Click to collapse
The partition layout is extremely different between the I9505/USA Variants and the I9505G, this prevents y'all using ODIN as it looks for a I9505G pit file, doesn't find one that matches, so it stops.

tublah said:
The partition layout is extremely different between the I9505/USA Variants and the I9505G, this prevents y'all using ODIN as it looks for a I9505G pit file, doesn't find one that matches, so it stops.
Click to expand...
Click to collapse
Hmmm...could we use a correct. pit file then?
Flash with repartition enabled? I guess we need proper GE factory restore images from Samsung, right?

CommanderROR said:
Hmmm...could we use a correct. pit file then?
Flash with repartition enabled? I guess we need proper GE factory restore images from Samsung, right?
Click to expand...
Click to collapse
It's been explored extensively already. PIT files are signed by Samsung for particular devices only.

SamuriHL said:
Flash this as phone:
http://www.mediafire.com/download/xtp9844uj42ov58/modem.tar.md5
Click to expand...
Click to collapse
How necessary is it use the new modem with 4.3. I am having data trouble on cm 10.2 using baseband MFD
Sent from my GT-I9505 using xda app-developers app

[Q] Help needed. Bricked Samsung 8.9.

Require help to revive my bricked Samsung 8.9 3G. Any assistance/advice would be greatly appreciated. Background
of issue faced are as follows:
Attempted factory reset failed. Ended up in Kernel Panic Upload Mode. Unable to startup, unable to shutdown.
Booted into download mode, flashed stock 4.0.4 ROM (obtained within forum from omarainea) with Odin.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P7300XXLQJ_P7300XFVLP4_P7300XXLQ6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.md5
<ID:0/003> hidden.img.md5
<ID:0/003> modem.bin.md5
<ID:0/003> recovery.img.md5
<ID:0/003> system.img.md5
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Process completes but tablet is stuck at boot animation of Samsung logo.
Performed power on/off to find error screen stating "Power Reset or Unknown Upload Mode". Once again unable
to start up or shutdown.

I would try flashing a custom recovery with ODIN, and using that to flash a custom rom.

upconvert said:
I would try flashing a custom recovery with ODIN, and using that to flash a custom rom.
Click to expand...
Click to collapse
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Downloaded recovery.img from CWM website. Applied conversion tool found in forum :
http://forum.xda-developers.com/showthread.php?t=2281287
Proceeded to flash with Odin, only to be met with failure.
Am I doing something wrong?
Also, I read somewhere that bootloader has to be unlocked for Odin to be able to flash recovery. Could that possibly be the issue and if
so how do I unlock the bootloader on this device?

tangene said:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Downloaded recovery.img from CWM website. Applied conversion tool found in forum :
http://forum.xda-developers.com/showthread.php?t=2281287
Proceeded to flash with Odin, only to be met with failure.
Am I doing something wrong?
Also, I read somewhere that bootloader has to be unlocked for Odin to be able to flash recovery. Could that possibly be the issue and if
so how do I unlock the bootloader on this device?
Click to expand...
Click to collapse
Try it with the .tar from the stickies in the android development forum.

Attempted to flash ClockworkMod Recovery v5.5.0.4 found in http://forum.xda-developers.com/showthread.php?t=1312218
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img.md5
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Tablet then reboots directly to download mode. Unable to enter newly installed recovery, unable to shutdown.
Retried several times to same result.

Are you doing the right key combo to get to recovery? Restart tab, as soon as the 8.9 logo pops up, press and hold volume down (the one closer to the power button). When bootloader screen comes up press volume down one more time to select recovery, and volume up once to select. Sorry if this is obvious, just wanted to make sure.

Correct me if I'm wrong but power+vol down basically brings you to a screen where you're given a choice
between download mode (denoted by a blinking green Andy) and recovery mode (Andy coming out of a box).
I select recovery, tried all buttons, no response. The "icon" flashes for a moment when key is pressed but
nothing happens.

That's correct. It sounds like your bootlader might be borked. Unfortunately, idk how to flash a new one without a working recovery. Sorry.
You might be able to flash a bootloader.zip in odin as a pda. I have never tried this, and I have no idea if it will work, or if it will further break your tab.
Am I correct that you have a p7300? If it is a p7300 or a p7310, this is the right bootloader:
http://forum.xda-developers.com/showpost.php?p=32802991&postcount=1085

upconvert said:
That's correct. It sounds like your bootlader might be borked. Unfortunately, idk how to flash a new one without a working recovery. Sorry.
You might be able to flash a bootloader.zip in odin as a pda. I have never tried this, and I have no idea if it will work, or if it will further break your tab.
Am I correct that you have a p7300? If it is a p7300 or a p7310, this is the right bootloader:
http://forum.xda-developers.com/showpost.php?p=32802991&postcount=1085
Click to expand...
Click to collapse
I read some replies about flashing this bootloader, and it seems like it works
but I noticed that @kallt_kaffe mentioned that you should flash the bootloader using the bootloader option instead of the PDA:
kallt_kaffe said:
Unzip and flash with Odin (using the Bootloader option instead of the PDA option that you use when you flash a full rom)
Click to expand...
Click to collapse
so I'am not sure but I think you should try to use the bootloader option first
good luck

Thanks for all the help I've gotten from both of you, I've managed to get CWM to work on my tab.
Now what? How exactly would I fix my problem using CWM from this point forward and what files would I need to do so?

tangene said:
Thanks for all the help I've gotten from both of you, I've managed to get CWM to work on my tab.
Now what? How exactly would I fix my problem using CWM from this point forward and what files would I need to do so?
Click to expand...
Click to collapse
Flashing the bootloader was the solution ???
I can think of two things
ether you should try to flash a stock Tar ROM by Odin
or you should transfer any flashable Zip ROM by USB adb connection and flash it through CWM

omarainea said:
Flashing the bootloader was the solution ???
I can think of two things
ether you should try to flash a stock Tar ROM by Odin
or you should transfer any flashable Zip ROM by USB adb connection and flash it through CWM
Click to expand...
Click to collapse
Actually I'm not sure whether it's the bootloader OR the fact that I switched to a laptop and a different USB from the one I was
using before.
That said, I have tried flashing the ROM you gave me the link to in mail. Didn't work. As before the installation completed only to be stuck at
the Samsung logo upon reboot.
How would I proceed with the flashable zip ROM USB adb thing with CWM? And what files would I need? Pardon my ignorance but I'm just
pretty new to all this.

You need to use cwm to flash a custom rom. There are several in the android development section. You need to download the rom.zip and gapps.zip from one of those threads, and put them on the internal storage of your tab. Hopefully, when you hook it up to a pc it will pop up as a media player or storage device, and you can just drag and drop them on there. If not, you may need to set up adb and push the files over to the tab.
Once you get the files on there, normally one would do a nandroid backup. In your case, without a working rom, I don't think that will be usefull. You need to wipe (format) system, data, cache, and dalvik, then install the rom.zip, then the gapps.zip.

I am having similar issues with my tab, flashed an official rom from sam mobile through odin, just hangs on the samsung boot screen. Could it be a boot loader issue?

upconvert said:
You need to use cwm to flash a custom rom. There are several in the android development section. You need to download the rom.zip and gapps.zip from one of those threads, and put them on the internal storage of your tab. Hopefully, when you hook it up to a pc it will pop up as a media player or storage device, and you can just drag and drop them on there. If not, you may need to set up adb and push the files over to the tab.
Once you get the files on there, normally one would do a nandroid backup. In your case, without a working rom, I don't think that will be usefull. You need to wipe (format) system, data, cache, and dalvik, then install the rom.zip, then the gapps.zip.
Click to expand...
Click to collapse
Device doesn't register as a storage device. No idea how to push files over with ADB or even how I would access ADB with
the Samsung 8.9. Could someone take the trouble to give me some step-by-step idiot proof instruction I could follow?

Ok, sorry for being late, I was collecting information and doing some experiences
on my tab to get all the details you need
So, to transfer a file through adb USB connection while in recovery you should
Install ADB Drivers and use the ADBGUI to copy the files to the tab
First of all mount /sdcard from the mount and unmount section in CWM, connect your tab through USB cable while in CWM and then
when you open the ADBGUI tool it should automatically detect your tab and show you figures like number 1 in the screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you see any figures in the same place, then your device is connected through adb
now open the Basic Commands tab (number 2)
Select File and browse it to the ROM.Zip you want to flash (number 3)
[it is recommended to be small file cuz you might need to do this more than once]
I use for this matter a Stripped CM9 (67MB) just to boot and then I transfer through normal USB any ROM I want
write (/sdcard) in (number 4) to guide the tool to put the file on the sdcard
click Push File (number 5) and wait for 2 - 6 minutes [it depends on the size of the file]
now the file should be on your sdcard
just flash it and reboot
I hope I am not exaggerating in this guide

Hey All,
Just managed to get mine to stock! . I was having the issue of it hanging on the Samsung Boot screen, but I managed to fix this by, flashing CWM through odin AFTER flashing the stock rom. Then entering CWM and doing a factory reset/wipe and wiping dalvik cache. Tablet booted perfectly into stock 4.04! Now just need to flash stock recovery and everything is back to stock

TwinCalibre said:
Hey All,
Just managed to get mine to stock! . I was having the issue of it hanging on the Samsung Boot screen, but I managed to fix this by, flashing CWM through odin AFTER flashing the stock rom. Then entering CWM and doing a factory reset/wipe and wiping dalvik cache. Tablet booted perfectly into stock 4.04! Now just need to flash stock recovery and everything is back to stock
Click to expand...
Click to collapse
That was easy,,,,
I created This Zip from the last Stock Framewok
you just need to flash it through CWM
Note: this is a stock kernel so you if you install it you won't be able to flash anything anymore
but you'll still be able to enter it and do wipe data and cache only
Enjoy

Thankyou!!! Ill flash it now and report back
---------- Post added at 06:23 PM ---------- Previous post was at 06:18 PM ----------
omarainea said:
That was easy,,,,
I created This Zip from the last Stock Framewok
you just need to flash it through CWM
Note: this is a stock kernel so you if you install it you won't be able to flash anything anymore
but you'll still be able to enter it and do wipe data and cache only
Enjoy
Click to expand...
Click to collapse
Works absolutely perfectly! Thank you so much for your help! This is going on Ebay now

There doesn't seem to be an option in CWM mount/storage for me to mount /sdcard. Options available for selection:
mount /efs
mount /system
unmount /cache
mount /data
mount /preload
format /system
format /data
format /preload
ADB Drivers and GUI installed though.

[Help] Samsung Galaxy S4 5.0.1 SGH-I337 won't reboot properly

This is my first post so I'm sorry if I did not post this in the right place or didn't do something else regular-place to these forums. Please guide me in the right direction if I didn't. So I rooted my phone with Kinguser and then switched it to SuperSu pro using the in-app instructions ins SuperSu. My goal is to install Xposed onto my phone but part of the problem is that I have to boot and manual recovery with TWRP or something similar for Xposed to work on my S4 (specifications above). But every manual recovery app I download works up to the point I actually try to reboot. All of them can find my root access and say they install successfully, but when I hit reboot and recovery, it always goes into Odin mode (and in the top left corner of Odin mode it says cannot reboot normally). I can get out of Odin mode easily so the problem isn't that I'm stuck there. I just want to know how to proceed with reboot and recovery when every time I try it goes into Odin mode.

Christian.Kodele said:
This is my first post so I'm sorry if I did not post this in the right place or didn't do something else regular-place to these forums. Please guide me in the right direction if I didn't. So I rooted my phone with Kinguser and then switched it to SuperSu pro using the in-app instructions ins SuperSu. My goal is to install Xposed onto my phone but part of the problem is that I have to boot and manual recovery with TWRP or something similar for Xposed to work on my S4 (specifications above). But every manual recovery app I download works up to the point I actually try to reboot. All of them can find my root access and say they install successfully, but when I hit reboot and recovery, it always goes into Odin mode (and in the top left corner of Odin mode it says cannot reboot normally). I can get out of Odin mode easily so the problem isn't that I'm stuck there. I just want to know how to proceed with reboot and recovery when every time I try it goes into Odin mode.
Click to expand...
Click to collapse
Easiest way is to go into download mode(Odin mode) and flash TWRP via Odin. In Odin make sure to uncheck reboot and f. reset once TWRP is flash unplug and pull the battery and reboot directly to recovery (power & volume+) once you get into TWRP it'll stay after that. Then just reboot your phone normally. Also within TWRP you can flash SuperSU.
TWRP download:
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar.html
Sent from my SPH-A120

mattzeller said:
Easiest way is to go into download mode(Odin mode) and flash TWRP via Odin. In Odin make sure to uncheck reboot and f. reset once TWRP is flash unplug and pull the battery and reboot directly to recovery (power & volume+) once you get into TWRP it'll stay after that. Then just reboot your phone normally. Also within TWRP you can flash SuperSU.
TWRP download:
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar.html
Sent from my SPH-A120
Click to expand...
Click to collapse
Thanks for the response!! I found the twrp file on their website (one which is a .md5 and one which is a .img which both don't work). They would both just freeze in Odin. So I found a tool online that turns .img files to .tar file. Link to tool below
http://forum.xda-developers.com/showthread.php?t=2281287
with another thread that helped to fix the runme.bat file
http://forum.xda-developers.com/showthread.php?p=42511844#post42511844
and that helped make a .tar file which doesn't freeze up Odin, but when I run the .tar file made from that tool, the manual flash using Odin runs through and fails. the Odin prompt is shown below.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Anything I'm doing wrong so far??

Anything I'm doing wrong so far??
Click to expand...
Click to collapse
Pretty much everything. I would not trust converting files like that. High potential for bricking your device.
The link I gave you is a .tar file that Odin likes. The md5 is at the top, yes, but you need the tar file just a little further down.
I linked you the latest one that is .tar. Newer versions are in .img that can be flashed in recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-A120

mattzeller said:
Pretty much everything. I would not trust converting files like that. High potential for bricking your device.
The link I gave you is a .tar file that Odin likes. The md5 is at the top, yes, but you need the tar file just a little further down.
I linked you the latest one that is .tar. Newer versions are in .img that can be flashed in recovery.
Sent from my SPH-A120
Click to expand...
Click to collapse
I downloaded the .tar file you linked above and tried it and it still failed. So to be descriptive as possible the first thing I do is plug my phone (without twrp installed) into my pc. Then I turn it off. Then I try to reboot. Phone can't reboot and forwards directly to Odin mode. I download the .tar file you linked me above. I do not unzip the file. I have Odin3 v3.07 installed. I open Odin and uncheck Auto Reboot and F. Reset Time. I click on PDA and select the unzipped zip file for flash. Nothing is said in the message display after that and is still at.
<ID:0/005> Added!!
Then I click Start. Flash still fails and message displays
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone isn't bricked but it seems that the .tar file linked above isn't working as well. Is it my phone probably?? Samsung Galaxy S4 AT&T SGH-I337 5.0.1 Lollipop rooted with Kinguser and then switched over with SuperSu pro via in app instructions?

Christian.Kodele said:
I downloaded the .tar file you linked above and tried it and it still failed. So to be descriptive as possible the first thing I do is plug my phone (without twrp installed) into my pc. Then I turn it off. Then I try to reboot. Phone can't reboot and forwards directly to Odin mode. I download the .tar file you linked me above. I do not unzip the file. I have Odin3 v3.07 installed. I open Odin and uncheck Auto Reboot and F. Reset Time. I click on PDA and select the unzipped zip file for flash. Nothing is said in the message display after that and is still at.
<ID:0/005> Added!!
Then I click Start. Flash still fails and message displays
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone isn't bricked but it seems that the .tar file linked above isn't working as well. Is it my phone probably?? Samsung Galaxy S4 AT&T SGH-I337 5.0.1 Lollipop rooted with Kinguser and then switched over with SuperSu pro via in app instructions?
Click to expand...
Click to collapse
Jeez I'm an idiot, I thought you were on jfltespr not jflteatt, I believe you need to use the safestrap, check out this thread:
http://forum.xda-developers.com/showthread.php?t=2448925
Sent from my SPH-A120

mattzeller said:
Jeez I'm an idiot, I thought you were on jfltespr not jflteatt, I believe you need to use the safestrap, check out this thread:
http://forum.xda-developers.com/showthread.php?t=2448925
Sent from my SPH-A120
Click to expand...
Click to collapse
Thanks so much for all the help!! After that linked I found a bunch of conversations that helped. If you every help out with someone with the same specifications on their phone then I had there's not much I can say that can help as far as Lollipop goes. I could not find a way to get Xposed on my device as is. But if anyone really does want it, I found that if you find the right .PIT file and the stock ROM for a previous version of Android (I tried a few which all work, but I would suggest KitKat because why not) then you'll be able to do anything you want without all the heartache. After I used Odin to flash KitKat onto my device, I found that I didn't even need TWRP, Xposed installed quite nicely, and even though the layout doesn't look quite as nice as Lollipop, you can find a bunch of display modules in Xposed that fit the bill quite well.
All in all, Samsung Galaxy S4 AT&T SGH-I337 5.0.1 and want Xposed?? You're screwed. Flash KitKat.