I tried to do a cyanogenmod update, but something went wrong and now I can't boot into android. I've tried going back into the recovery mode to reflash the rom, but it freezes there. I've also tried flashing clockworkmod recovery through ODIN and download mode, but the download back never moves at all, so I'm not sure if I can't use download mode or if it's just that ODIN isn't doing anything. I'm not sure what to do anymore, does anyone have any idea how to get me out of this?
Clothbox said:
I tried to do a cyanogenmod update, but something went wrong and now I can't boot into android. I've tried going back into the recovery mode to reflash the rom, but it freezes there. I've also tried flashing clockworkmod recovery through ODIN and download mode, but the download back never moves at all, so I'm not sure if I can't use download mode or if it's just that ODIN isn't doing anything. I'm not sure what to do anymore, does anyone have any idea how to get me out of this?
Click to expand...
Click to collapse
you could try heimdall.
it seems like you got a corrupted download or the boot.img is jacked up.
it wont help to flash the same rom.
grab stock files (need pit file) and flash with heimdall or odin.(preferably not using windows 8/8.1)
http://forum.xda-developers.com/showthread.php?t=2363213 does this link help?
Lgrootnoob said:
you could try heimdall.
it seems like you got a corrupted download or the boot.img is jacked up.
it wont help to flash the same rom.
grab stock files (need pit file) and flash with heimdall or odin.(preferably not using windows 8/8.1)
http://forum.xda-developers.com/showthread.php?t=2363213 does this link help?
Click to expand...
Click to collapse
Yeah, I'll try this approach. Where do I get the pit file?
Clothbox said:
Yeah, I'll try this approach. Where do I get the pit file?
Click to expand...
Click to collapse
should just be a part of the odin packages they provide.
dont worry about it.
just follow the instructions.
Lgrootnoob said:
should just be a part of the odin packages they provide.
dont worry about it.
just follow the instructions.
Click to expand...
Click to collapse
I tried it, and the phone is stuck in download mode with the progress bar never moving past a little dot. Is it hopeless?
Clothbox said:
I tried it, and the phone is stuck in download mode with the progress bar never moving past a little dot. Is it hopeless?
Click to expand...
Click to collapse
screenshot odin,
try different usb port, and different cable, and use the latest odin for sure, use kies to install drivers and different pc
Lgrootnoob said:
screenshot odin,
try different usb port, and different cable, and use the latest odin for sure, use kies to install drivers and different pc
Click to expand...
Click to collapse
Wow, thanks! I got it to work. I don't think I can boot into android but I can definitely boot into recovery. But it's just the standard recovery, I'm not sure if I can flash a rom through it. Where do I go from here?
Clothbox said:
Wow, thanks! I got it to work. I don't think I can boot into android but I can definitely boot into recovery. But it's just the standard recovery, I'm not sure if I can flash a rom through it. Where do I go from here?
Click to expand...
Click to collapse
what happened in odin? I can't really tell if something happened when it flashed system.img
.....
---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------
just copy and paste the output of the message box here from odin.
Lgrootnoob said:
what happened in odin? I can't really tell if something happened when it flashed system.img
.....
Click to expand...
Click to collapse
Not sure if this will help, but here:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Clothbox said:
Not sure if this will help, but here:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
wtf....
how can you not boot into android?
did you do the repartition check thing?
Lgrootnoob said:
wtf....
how can you not boot into android?
did you do the repartition check thing?
Click to expand...
Click to collapse
No, the only thing I checked was "Auto Reboot" and "F. Reset Time". Should I do it one more time or should I find a way to flash cyanogenmod again?
Clothbox said:
No, the only thing I checked was "Auto Reboot" and "F. Reset Time". Should I do it one more time or should I find a way to flash cyanogenmod again?
Click to expand...
Click to collapse
dont check auto reboot, manually reboot with power + volume up this time.
Lgrootnoob said:
dont check auto reboot, manually reboot with power + volume up this time.
Click to expand...
Click to collapse
Yeah, it still won't let me boot. Is there a way I can flash a rom or put in a different recovery mode from here?
Clothbox said:
Yeah, it still won't let me boot. Is there a way I can flash a rom or put in a different recovery mode from here?
Click to expand...
Click to collapse
yea, just install a different odin recovery img.
you can also take any recovery.img you want and format it as odin file with md5 igning etc
Lgrootnoob said:
yea, just install a different odin recovery img.
you can also take any recovery.img you want and format it as odin file with md5 igning etc
Click to expand...
Click to collapse
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Clothbox said:
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Click to expand...
Click to collapse
yes, take a cynagoen mod flashable zip, put it into an ext4 system.img if it isnt already one, then make an odin tar.md5 out of it.(if your already lost then your screwed)
It's not uncommon to need to reboot to recovery to factory reset after flashing the firmware through Odin or Heimdall as many of the packages do not wipe data as they are meant to be update versions.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Clothbox said:
Is there a way I can flash cyanogenmod through ODIN? I'm still lost at this point, sorry...
Click to expand...
Click to collapse
^ he made a good point
Related
Just noticed my phone was on the Samsung boot screen, it was just sitting on my desk I wasn't even using it.
The phone was only rooted via Odin about a month ago, using a stock 4.1.1 rom (Norway, Telenor)
I managed to get into the Odin mode so I can try ans re-flash the stock rom hoping this may fix it.
I could only find this ROM (which is a norway telenor 4.04 rom)
I9300XXBLFB_I9300TENBLF1_I9300XXLFB_HOME.tar.md5
My question is about why Odin fails, here is the message;
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300TENBLF1_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
is the fone borked?
so you tried to flash a pit file?
Flash the stock FW from sammobile and leave all the ODIN checkmarks as it.
sleepingsword said:
Just noticed my phone was on the Samsung boot screen, it was just sitting on my desk I wasn't even using it.
The phone was only rooted via Odin about a month ago, using a stock 4.1.1 rom (Norway, Telenor)
I managed to get into the Odin mode so I can try ans re-flash the stock rom hoping this may fix it.
I could only find this ROM (which is a norway telenor 4.04 rom)
I9300XXBLFB_I9300TENBLF1_I9300XXLFB_HOME.tar.md5
My question is about why Odin fails, here is the message;
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXBLFB_I9300TENBLF1_I9300XXLFB_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
is the fone borked?
Click to expand...
Click to collapse
I just manged to help others over this soft brick problem, by flashing one of Darkys roms !!
Just find your country/region dl it and flash following his instructions
http://www.darkyrom.com/index.php?forum/#rom-darkyrom-iii-i9300.122
---------- Post added at 09:11 AM ---------- Previous post was at 09:07 AM ----------
xSpeced said:
Flash the stock FW from sammobile and leave all the ODIN checkmarks as it.
Click to expand...
Click to collapse
Sammy rom wont solve the problem - Darkyrom will :laugh:
Glebun said:
so you tried to flash a pit file?
Click to expand...
Click to collapse
Nay, didnt have much luck finding one, can you give me any pointers to finding it?
xSpeced said:
Flash the stock FW from sammobile and leave all the ODIN checkmarks as it.
Click to expand...
Click to collapse
Tried again but still have this ''<ID:0/004> There is no PIT partition.'' error
sleepingsword said:
Nay, didnt have much luck finding one, can you give me any pointers to finding it?
Tried again but still have this ''<ID:0/004> There is no PIT partition.'' error
Click to expand...
Click to collapse
Are you blind ??
Stock wont do, Darky will!
Get CWM again do this>
*Installation
1. Download Odin3 and CF-Root-SGS3-vxx.zip
2. Power off your phone
3. Boot into download mod (Press vol down + Home + Power on)
4. Unzip CF-Root-SGS3-vxx.zip. You need to end up with a .tar file, dont extract .tar file.
5. Open Odin
6. Select PDA as CF-Root-SGS3-vxx.tar
7. Connect the phone to your computer
8. Make sure that re-partition is not ticked
9. Click Start Button
10. Wait for phone to reboot.
Now you successfully installed CWM + Super User + CWM Manager.
spoonymoon said:
Are you blind ??
Stock wont do, Darky will!
Click to expand...
Click to collapse
Help me see...
Darky guides say I need to install CWM first but ODIN still says there is no PIT partition when I try to install it...
sleepingsword said:
Help me see...
Darky guides say I need to install CWM first but ODIN still says there is no PIT partition when I try to install it...
Click to expand...
Click to collapse
Look one post above
spoonymoon said:
Look one post above
Click to expand...
Click to collapse
I think you misunderstand me, look at that CWM guide you gave me, it says use ODIN for flash CWM
but when it try to flash CWM via ODIN i get the same error: <ID:0/004> There is no PIT partition.
sleepingsword said:
I think you misunderstand me, look at that CWM guide you gave me, it says use ODIN for flash CWM
but when it try to flash CWM via ODIN i get the same error: <ID:0/004> There is no PIT partition.
Click to expand...
Click to collapse
No you dident read properly
3. Boot into download mod (Press vol down + Home + Power on)
4. Unzip CF-Root-SGS3-vxx.zip. You need to end up with a .tar file, dont extract .tar file.
5. Open Odin
6. Select PDA as CF-Root-SGS3-vxx.tar
7. Connect the phone to your computer
8. Make sure that re-partition is not ticked
9. Click Start Button
10. Wait for phone to reboot.
You must flash the excracted tar file in PDA in Odin (whitout reparation) thats all
Link>http://speedy.sh/kcqvD/CF-Root-SGS3-v6.2.tar
spoonymoon said:
No you dident read properly
3. Boot into download mod (Press vol down + Home + Power on)
4. Unzip CF-Root-SGS3-vxx.zip. You need to end up with a .tar file, dont extract .tar file.
5. Open Odin
6. Select PDA as CF-Root-SGS3-vxx.tar
7. Connect the phone to your computer
8. Make sure that re-partition is not ticked
9. Click Start Button
10. Wait for phone to reboot.
You must flash the excracted tar file in PDA in Odin (whiteout reparation) thats all
Link>http://speedy.sh/kcqvD/
Click to expand...
Click to collapse
as i said, trying to add the file CF-Root-SGS3-v6.2.tar give this result
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
sleepingsword said:
as i said, trying to add the file CF-Root-SGS3-v6.2.tar give this result
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1
Click to expand...
Click to collapse
then tick re-partition and try again
edit- whitch odin version are you using? gotta be 1.85
spoonymoon said:
then tick re-partition and try again
edit- whitch odin version are you using? gotta be 1.85
Click to expand...
Click to collapse
I need a PIT file for re-partition, i cant find one on the forums...
I have tried both ODIN versions 3.04 and 1.85
both say the same no pit partition.
this is looking like I will have to try and get a replacement from Samsung...
EDIT:
tried this PIT file: GT-I9300_mx_20120329
Code:
<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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sleepingsword said:
I need a PIT file for re-partition, i cant find one on the forums...
I have tried both ODIN versions 3.04 and 1.85
both say the same no pit partition.
this is looking like I will have to try and get a replacement from Samsung...
Click to expand...
Click to collapse
Try Odin v.3.07
dont work
Not sure but think , its possible a corrupted emmc !
But flashing a wrong pit file could make things even worse - lets investigate a bit more ?
Try latest odin 3.07
Btw: its a long shot but try flashing whitout external sd - remove it first
same result with Odin 3.07, no PIT partition...
so I found 3 PIT files.
GT-I9300_mx_20120220
GT-I9300_mx_20120322
GT-I9300_mx_20120329
alas none work, ODIN 3.07 just hangs on <ID:0/003> Get PIT for mapping..
this happens if i select any .tar file (CWM or Sammy Firmware) with the PIT file, or Just the PIT file on its own....
its dead Jim....
Thanks for trying to help me Spoonymoon
sleepingsword said:
same result with Odin 3.07, no PIT partition...
so I found 3 PIT files.
GT-I9300_mx_20120220
GT-I9300_mx_20120322
GT-I9300_mx_20120329
alas none work, ODIN 3.07 just hangs on <ID:0/003> Get PIT for mapping..
this happens if i select any .tar file (CWM or Sammy Firmware) with the PIT file, or Just the PIT file on its own....
its dead Jim....
Thanks for trying to help me Spoonymoon
Click to expand...
Click to collapse
Damm sorry to hear br0
And you're welcome
TRY THIS COULD WORK
http://www.androidauthority.com/galaxy-s3-gt-i9300-clockworkmod-recovery-6-0-1-0-install-103347/
sleepingsword said:
same result with Odin 3.07, no PIT partition...
so I found 3 PIT files.
GT-I9300_mx_20120220
GT-I9300_mx_20120322
GT-I9300_mx_20120329
alas none work, ODIN 3.07 just hangs on <ID:0/003> Get PIT for mapping..
this happens if i select any .tar file (CWM or Sammy Firmware) with the PIT file, or Just the PIT file on its own....
its dead Jim....
Thanks for trying to help me Spoonymoon
Click to expand...
Click to collapse
Heey mate,
I have the same as you,no pit.
The emmc is burned.
I take it to the repair center,and they told me it was the screen,cost 216 euros.
I say the screen is good it's the main board that's bad.
No warranty they say,f..k it.
Now I buy a main board from someone,100 euro.
Put it in and voila,it works.
Warranty samsung sucks.
Good luck.
Do you have the blue one.
It happens a lot with the blue ones.
painterceessie said:
Heey mate,
I have the same as you,no pit.
The emmc is burned.
I take it to the repair center,and they told me it was the screen,cost 216 euros.
I say the screen is good it's the main board that's bad.
No warranty they say,f..k it.
Now I buy a main board from someone,100 euro.
Put it in and voila,it works.
Warranty samsung sucks.
Good luck.
Do you have the blue one.
It happens a lot with the blue ones.
Click to expand...
Click to collapse
with what excuse did they tell you no warrenty?
even if you flashed it they cant say no warrenty, a ok phone dosent burn emmc because of a flash, actually in eu theres a eu statement proven at court that says they cant say so, ill find the page for you, print that and throw that in their faces!
Searching is not really painful....have you tried it?
Follow the screenshots and use the Odin version included.
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Posklapenzi said:
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Click to expand...
Click to collapse
Try flashing a custom recovery like twrp or philz touch. But it actually sounds like a soft brick. worst case scenario you would have to flash a new firmware/
this is the last one http://forum.xda-developers.com/showthread.php?t=1835931
Posklapenzi said:
hey,
so my friend brought me his S3, never rooted or tampered with. He just said the phone went into boot and never recovered. I can go in download mode but not recovery (my initial plan was to wipe cache).
he would kind of want his data intact but I don't know how viable that is by now..
Any advice?
Thank you
Click to expand...
Click to collapse
The phone's own recovery mode is not much flexible as other third-part recoveries. So I guess you have to install CWM recovery and wipe dalvik cache from there before booting. Try installing CWM recovery via Odin and then wipe dalvik cache. And don't worry, installing custom recovery won't root your phone.
If the stock recovery can, wipe the cache and dalvik cache
Sent from my GT-I9300 using Tapatalk
It appears I can't flash any recovery:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Report from Odin. Could I flash a stock firmware tho?
Can't mount stock rom either. I tried ticking repartition too, this is what comes out:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMG4_I9300DBTEMG3_I9300XXEMG4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<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> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Bump.. Please help someone.
Make sure you have the latest odin and the correct drivers and also make sure kies is not open
Sent from my SAMSUNG GT-N7105 using XDA Premium 4 mobile app
Posklapenzi said:
It appears I can't flash any recovery:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Report from Odin. Could I flash a stock firmware tho?
Click to expand...
Click to collapse
Try to flash PIT partition via odin( be careful you must have the PIT file sweatable for your model )
abidifethi said:
Try to flash PIT partition via odin( be careful you must have the PIT file sweatable for your model )
Click to expand...
Click to collapse
How can I know what that is? I can't boot the phone to see the exact model? Says I9300GSMH on the back behind the battery so I should assume that's accurate?
Posklapenzi said:
How can I know what that is? I can't boot the phone to see the exact model? Says I9300GSMH on the back behind the battery so I should assume that's accurate?
Click to expand...
Click to collapse
http://widefide.com/mobile/galaxy-s3-boot-problem-solution
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
KizzleKat said:
This is my first thread, so hello!
Me and my sister both have a S5839i, and my sisters just randomly bricked, and it is on a boot loop.
I have tried EVERYTHING online- recovery mode, downloading firmware with odin...you name it.
I have used the totoro_0623.pit file, and on Odin, it said it passed. But then trying with all the other firmware, it didn't work.
Yes, I am using the right version of Odin, and I don't have Kies running at the same time as Odin.
This is what happens when I put S5839IBULL1_S5839IVD2LH1_VD2.tar.md5 into the PDA section in Odin. This is the Germany Vodafone firmware, someone else posted in the forums. I have tried the UK one with the 3 network (what my region and network is) , but that doesn't work either, and comes up with the same thing in Odin.
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULL1_S5839iVD2LH1_S5839iBULK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> BcmCP.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Am I just stupid, and have missed something, or is there another way? Please note : The phone is not modded in anyway, not even rooted, but the warranty has run out.
Thankyou
Click to expand...
Click to collapse
Get the official firmware needed on Sammobile.com, you need an account on there. Don't worry it's free. Flash it as PDA on Odin. Make sure your phone is in download mode (volume up+volume down+power). If it boots, the boot animation might start looping. From theres you can access recovery (volume up+power+home). In recovery you wipe data and wipe cache and select reboot. It should work.
Sent from my GT-I8190N using Tapatalk
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Galaxy_Ace_Love said:
Hi
Don't panic !
Is not a brick, but Odin doesn't support one file (PDA) package.
You need to use Odinatrix to create a 3 files firmware or download a 3 files firmwares
Click to expand...
Click to collapse
Odin 3.07 supports one file package
Humm...
iamareebjamal said:
Odin 3.07 supports one file package
Click to expand...
Click to collapse
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
KizzleKat said:
I used Odin 3.07, and that worked... but when the phone loaded and installed - it said "Failed to mount /data (invalid argument)" and continued to boot loop. I thought by installing the firmware and re-partitioning it would fix that :/
Click to expand...
Click to collapse
Format the data
Put the pit file and tick Repartition. And then flash with Odin.
And you have to use Cooperve pit, not Totoro, it's for SGY
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
KizzleKat said:
Yeah, I have ticked the re-partion and stuff. Apparently totoro works with Ace as well? All the tutorials say that...
I will still try though
Edit: Tried and still no luck....
Sent from my GT-S5839i using xda app-developers app
Click to expand...
Click to collapse
Follow these Guidehttp://forum.xda-developers.com/showthread.php?t=1840645
Sent from my GT-S5830i using Tapatalk 2
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Portisface said:
I am trying to flash phone back to stock ROM due to my phone only booting in Odin mode, but I keep getting FAIL! flash attempts in Odin. The failure occurs at the message line FAIL! (Auth). I have tried flashing VRUAMDK_NoWipe.tar and CF-Auto-Root-jflte-jfltexx-gti9505.
Click to expand...
Click to collapse
Were you originally on MDK? If so, have you checked MD5?
riker147 said:
Were you originally on MDK? If so, have you checked MD5?
Click to expand...
Click to collapse
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Portisface said:
Sorry the full filename is VRUAMDK_NoWipe.tar.md5. Is that what you're talking about?
Click to expand...
Click to collapse
No. What build were you on before your problems?
riker147 said:
No. What build were you on before your problems?
Click to expand...
Click to collapse
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Portisface said:
I don't remember other than I was at 4.3. I had my phone rooted using SuperSU and I tried unrooting so I could download the latest OTA. I was still getting errors to install updates after disabling SuperSU and was getting sick of my phone constantly trying to update so I decided to try to revert back to stock. I downloaded Odin and the TAR file I mentioned and followed the instructions to restore back to stock ROM. I received that error and found in another forum that someone got it to work using CF-Auto-Root-jflte-jfltexx-gti9505. I tried that to and same issue. I can't find any other solutions.
Click to expand...
Click to collapse
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
riker147 said:
You need to find what build you were on because you can't flash an older build. You can only flash your original build or newer. If you want the latest OTA, (Kit Kat), you need to download the .tar file for that.
Click to expand...
Click to collapse
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Portisface said:
I am currently downloading Kit Kat. However, I was trying to flash it one more time to copy and paste the message lines here and now the error is "There is no PIT partition." I have already downloaded the PIT for my phone. I am I gonna have to use that now?
Click to expand...
Click to collapse
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
riker147 said:
I think you might me be over complicating things. If you're going with NC5 (Kit Kat) and you can use Odin, I think all you're going to need is the .tar file.
Click to expand...
Click to collapse
So the "no PIT partition" message isn't a problem?
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
gotshot87 said:
Hi,
I've been trying to revert to stock rom just like the OP. As you'll see my adventure ends at aboot.mbn. I downloaded the latest build (SCH-I545_MDK_562219_Stock_Restore.tar.md5) according the tutorial I'm using. I'm using the latest version of Odin3 1.85 (also according to the tutorial. Also, I'm using the Samsung Galaxy S4 VZW (SCH-1545) phone. Any and all help will be appreciated!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hi guys,
1st thing thank you for the informations and knowledge i have learned here at XDA.
I have the same problem . I have done all i believe i can from all the research i have done and come acrossed. Hands up in the air and i surrender.
Need some help
If anybody could please fhank you so much...
It looks like you are trying to unlock the wrong baseband version.
The only Verizon Samsung Galaxy S4 (SCH-I545), aka jfltevzw, that has an unlockable bootloader is the one that has the baseband version "I545VRUAMDK".
And once the baseband is updated to a newer one, it cannot be downgraded.
Sent from my SCH-I535 using XDA Free mobile app
I kind of brick my phone , after it stopped in the middle of a flash due to a bad cable. Now all i have is a black screen with a phone, a yellow triangle and a PC icons.
I changed the cable and when trying to flash with this rom: I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar
the flash process always stops at about 99%. This is the log:
Code:
OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> MLO
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HOW can I solve this, please.
PS: I live in Morocco.
AhmedElakrab said:
I kind of brick my phone , after it stopped in the middle of a flash due to a bad cable. Now all i have is a black screen with a phone, a yellow triangle and a PC icons.
I changed the cable and when trying to flash with this rom: I9100GXXLSR_I9100GXXLSP_I9100GXEFLSR_HOME.tar
the flash process always stops at about 99%. This is the log:
Code:
OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1205)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> cache.img
<ID:0/006> factoryfs.img
<ID:0/006> hidden.img
<ID:0/006> MLO
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HOW can I solve this, please.
PS: I live in Morocco.
Click to expand...
Click to collapse
Try extracting a copy of the stock recovery.img from the firmware, then convert it to an Odin flashable .tar.md5, flash it via Odin, then boot into stock recovery, then factory reset and wipe cache, then reboot. Then try flashing the firmware.
Or, try flashing TWRP via Odin, then boot into TWRP, wipe everything, then reboot, then try flashing the firmware.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Try extracting a copy of the stock recovery.img from the firmware, then convert it to an Odin flashable .tar.md5, flash it via Odin, then boot into stock recovery, then factory reset and wipe cache, then reboot. Then try flashing the firmware.
Or, try flashing TWRP via Odin, then boot into TWRP, wipe everything, then reboot, then try flashing the firmware.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
AhmedElakrab said:
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
Click to expand...
Click to collapse
Have you tried booting to stock recovery then factory reset and wipe cache partition? Sometimes there is stuff left on the device from before you flashed it, that remaining data causes bugs, factory reset and wipe cache fixes that.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Have you tried booting to stock recovery then factory reset and wipe cache partition? Sometimes there is stuff left on the device from before you flashed it, that remaining data causes bugs, factory reset and wipe cache fixes that.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you, again.
I already did a factory reset but haven't cleared the cache yet.
I'm on it. And will tell how it goes.
AhmedElakrab said:
Thank you, again.
I already did a factory reset but haven't cleared the cache yet.
I'm on it. And will tell how it goes.
Click to expand...
Click to collapse
On stock? For me this was the horrid media scanner glitch. I had to root my phone to force the device from scanning for new content and this was via a play store app.
Sent from my iPhone using Tapatalk Pro
AhmedElakrab said:
Thank you. It was a problem with the firmware. I Downloaded the right firmware for my country and it has flashed ok.
But now I have a bigger problem. The Phone over heats near the camera and randomly freezes and restarts.
Do you have any Idea why he's doing that.
Click to expand...
Click to collapse
jr866gooner said:
On stock? For me this was the horrid media scanner glitch. I had to root my phone to force the device from scanning for new content and this was via a play store app.
Click to expand...
Click to collapse
I had similar problem a few years ago. Phone was extremally hot near the camera and a process called media scanner (I think that's it's name) was running all the time forcing CPU to go up to 1,2GHz
To fix that problem I had to install SD main pro and run it. It turned out I had many, many gigs of some kind of cache files. After painfull long time and boiling hot temperature near camera SD main managed to get rid off all of that useless staff. After that phone felt lighter and media scanning process after reboot was taking less then 45 seconds to finish
Sent from my whyred using XDA Labs