Hello,
I've bricked my phone. I've seeking tutorials ..etc and figured out everything exept spliting firmware, could someone please split firmware for me and upload?
sammobile.com/firmwares/3/?download=15840
I've GT-5830i
THanks in advance!
iznogouda said:
Hello,
I've bricked my phone. I've seeking tutorials ..etc and figured out everything exept spliting firmware, could someone please split firmware for me and upload?
sammobile.com/firmwares/3/?download=15840
I've GT-5830i
THanks in advance!
Click to expand...
Click to collapse
What do you mean splitting the firmware? Are you talking about decompiling it and breaking it into system.img, boot.img, etc?
timmytim said:
What do you mean splitting the firmware? Are you talking about decompiling it and breaking it into system.img, boot.img, etc?
Click to expand...
Click to collapse
Splitting so i could have PDA Phone CSC files to flash with ODIN.
btw sorry wrong fiarmware link sammobile.com/firmwares/3/?download=22788
iznogouda said:
Splitting so i could have PDA Phone CSC files to flash with ODIN.
btw sorry wrong fiarmware link sammobile.com/firmwares/3/?download=22788
Click to expand...
Click to collapse
Are you trying to flash the entire firmware or are you trying to install those separately? I ask because it is already in tar.md5 format to flash the entire thing with Odin.
In fact the instructions to flash the entire firmware are on the page if you scroll down.
Instructions
Extract (unzip) the firmware file
Download Odin v3.09
Extract Odin zip-file
Open Odin v3.09
Reboot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait a few minutes
Click to expand...
Click to collapse
If you still want to break it apart I can probably help you
timmytim said:
Are you trying to flash the entire firmware or are you trying to install those separately? I ask because it is already in tar.md5 format to flash the entire thing with Odin.
In fact the instructions to flash the entire firmware are on the page if you scroll down.
If you still want to break it apart I can probably help you
Click to expand...
Click to collapse
youtube.com/watch?v=3d7AS3Is4bk
My phone is stuck on Samsung logo, so im going to completely reinstall firmware. (+ it was constantly having some process problems everytime not responding pop-up was showing..
I would appreciate if you could help me.
https://www.youtube.com/watch?v=3d7AS3Is4bk
In this video tutorial that guy has splitted firmware, that's why i asked it.
iznogouda said:
youtube.com/watch?v=3d7AS3Is4bk
My phone is stuck on Samsung logo, so im going to completely reinstall firmware. (+ it was constantly having some process problems everytime not responding pop-up was showing..
I would appreciate if you could help me.
https://www.youtube.com/watch?v=3d7AS3Is4bk
In this video tutorial that guy has splitted firmware, that's why i asked it.
Click to expand...
Click to collapse
To completely reinstall the firmware use the directions on the Sammobile download page.... the ones I posted above. You only need the one file. Besides, I am splitting the tar.md5 apart now and there is only boot.img, system.img, etc.... they are not Odin files like in the video
timmytim said:
To completely reinstall the firmware use the directions on the Sammobile download page.... the ones I posted above. You only need the one file. Besides, I am splitting the tar.md5 apart now and there is only boot.img, system.img, etc.... they are not Odin files like in the video
Click to expand...
Click to collapse
All right, if it's so do't bother yourself continuing to split.. Now i got it, i have to point only PDA and flash..aa
Thank you...
iznogouda said:
All right, if it's so do't bother yourself continuing to split.. Now i got it, i have to point only PDA and flash..aa
Thank you...
Click to expand...
Click to collapse
No rpboelm, let me know how it goes and please click that Thanks button for me if I've helped you
timmytim said:
No rpboelm, let me know how it goes and please click that Thanks button for me if I've helped you
Click to expand...
Click to collapse
Did it!. Ps i followed sammobile instruction but i got error
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830iXXMJ2_S5830iITVMK1_S5830iXXMJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/005> sbl.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> BcmCP.img
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
P.S fails when reach MODEM
Related
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Emperia said:
Hi i've had CM9 in my phone for a half year now without any issues, however two days ago i woke up and went to check my phone, it froze and after that i haven't been able to boot it up, it just hungs at the samsung logo with the triangle and all that, so i've been trying to sort out this for two days straight now and i'm getting really sick of this, what i've done so far is:
* tried to flash alot of rom's and such with no success, stucks at: NAND Write Start!!
* tried to flash on a different computer
* tried to flash with different usb ports
Oh and i can't get into the recovery mode, only the download mode.
This is the files i've tried to flash and such to get my phone working again:
Kernel_I9100XXLPH
I9100XXLPQ_I9100HTSLP3_HTS
I9100XWLPG_I9100XXLPX_I9100NEELP4_NEE
I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar
I9100XWLPG_I9100NEELP4_NEE
GT-I9100_Kernel_Gingerbread-supercurio-3
GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4
cm-10-20120927-EXPERIMENTAL-i9100-jb_mali-changmin
cm-10-20120926-NIGHTLY-i9100
cm-9-20120330-ODIN-galaxys2.tar
CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5
CF-Root-SGS2_XX_OXA_KP8-v5.2-CWM5
GT-I9100_NEE_I9100XWLPD_I9100XXLPW_I9100NEELP4
Please, can anyone try to help me? I can't explain how tired i am of this, i really need and want my phone to work again! Thanks
Click to expand...
Click to collapse
try flashing a stockfirmware which comes with a .pit file and see
Sun90 said:
try flashing a stockfirmware which comes with a .pit file and see
Click to expand...
Click to collapse
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Emperia said:
Could you please help me out, i'm not really sure where i can find that.
Edit: I live in Sweden, Europe so i need a nordic firmware.
Click to expand...
Click to collapse
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Sun90 said:
check the link below read the main post(#1) of that thread and proceed carefully to revive back ur phone
http://forum.xda-developers.com/showthread.php?t=1457458
Click to expand...
Click to collapse
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Emperia said:
Thanks, i've read that guide earlier and tried a few steps with no luck.
Is this what i should do?
"WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
8) Download the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partitioning
9) Flash the Kernel, as in step 5
10) Flash the recovery package, like in steps 1-4 And that will fix any of your issues "
Click to expand...
Click to collapse
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
look for this in that thread
Recovering a soft bricked phone
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC and .PIT. Put each one in its place.
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a yellow box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!
Sun90 said:
no dont mess with that 'Bootloader' one ma8, there is one on how to use pit file look into that
Click to expand...
Click to collapse
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Emperia said:
Hmm, well the only files i got when i downloaded the recovery package via that thread is:
MODEM_I9100XXLPH_REV_02_CL1104396.tar
I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar
I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar
GT-I9100-MULTI-CSC-OXALPH.tar
thanks for trying to help me, it's appreciated!
Click to expand...
Click to collapse
did u dwnld'd that file under Gingerbread or ICS?
Sun90 said:
did u dwnld'd that file under Gingerbread or ICS?
Click to expand...
Click to collapse
The ICS one, is that wrong?
Emperia said:
The ICS one, is that wrong?
Click to expand...
Click to collapse
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Sun90 said:
yes its correct, The ICS one is the right one for u
now follow the instruction over that thread for where to put those files in ODIN and flash the same
Click to expand...
Click to collapse
Alright, we'll see what happens, there is no pit file thought, correct?
Emperia said:
Alright, we'll see what happens, there is no pit file thought, correct?
Click to expand...
Click to collapse
its only needed in the worst case scenerio
Sun90 said:
its only needed in the worst case scenerio
Click to expand...
Click to collapse
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Emperia said:
Ah alright, so i should put all those files even the bootloader in odin and try to flash? Just making sure!
Click to expand...
Click to collapse
yes
ps- and remember that u r doing all this thing at ur own risk, do not complain in the Future if something goes wrong there
Sun90 said:
yes
Click to expand...
Click to collapse
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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.bin
<ID:0/006> NAND Write Start!!
Emperia said:
This is what happens:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100_APBOOT_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> I9100_CODE_I9100XXLPH_CL118559_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXLPH_REV_02_CL1104396.tar.md5 is valid.
<OSM> GT-I9100-MULTI-CSC-OXALPH.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.bin
<ID:0/006> NAND Write Start!!
Click to expand...
Click to collapse
do u see a red 'fail' message in the big rectangle box in odin
Sun90 said:
do u see a red 'fail' message in the big rectangle box in odin
Click to expand...
Click to collapse
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Emperia said:
Nope, it just seems like it's stuck, this is what always happens, i never get fail messages or such.
Click to expand...
Click to collapse
which version of windows ur using is it XP or 7
Sun90 said:
which version of windows ur using is it XP or 7
Click to expand...
Click to collapse
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Emperia said:
Windows 7, i've tried to flash on windows xp as well, and it gets stuck too, no fail error.
Click to expand...
Click to collapse
try to reflash using the PIT file att below, extract the file put it in the pit section on odin along with the other files in there respective section also check the re-partition and see
Hello XDAdevelopers,
My GSII wont turn on after i auto reboot or auto reboot into recovery.
So i installed the stock ICS rom via ODIN, everything went fine. but when the installation finished, the phone stay dead, it wont reboot unless i remove the battery, wait a few seconds and put it in again.
So i booted into download mode, flashed the Root BOX JB, with syah via ODIN, everything fine. But it wont boot again.
I removed the battery, wait few seconds, place it again, then it turns on.
Every time i reboot my phone or turn it off, it wont turn on unless i remove the battery.
Do you guys know why this is happening ?
Already flashed stock AOKP, CM, STOCK and now trying with ROOT BOX, always the same problem.
Update1: Flashed the stock ICS ROM and Kernel trough Odin and still cant boot without removing the battery =/
Update 2: Flashed with PIT and Re-partition checked, still the same =/, what else should i try ?
update 3: Flashed the stock XXLPH kernel after the PIT, still the same =/
Exact Same problem
How can u get out of this.....
I have also the same problem
I went to samsung care & they just want to change my motherboard ...
but i don't think that motherboard have any fault.
plz help mee........ if u got any..
syama35 said:
How can u get out of this.....
I have also the same problem
I went to samsung care & they just want to change my motherboard ...
but i don't think that motherboard have any fault.
plz help mee........ if u got any..
Click to expand...
Click to collapse
Heyy,
well, i don't know what else to do, i'll keep searching and trying, any update ill post in here.
Trying flashing a full stock firmware.. do a factory reset too..
Sent from my GT-I9300 using xda premium
saywhatt said:
Trying flashing a full stock firmware.. do a factory reset too..
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
i did it before the PIT. gonna try it now.
Give some solution
Sorry saywhatts .........................:angel:
I didn't get u ...............
plz give any solution if any...?????
syama35 said:
Sorry saywhatts .........................:angel:
I didn't get u ...............
plz give any solution if any...?????
Click to expand...
Click to collapse
Okay, go to sammobile.com and download a firmware there.. flash it via odin
Sent from my GT-I9300 using xda premium
Glowing_Potato said:
i did it before the PIT. gonna try it now.
Click to expand...
Click to collapse
no deal, =/
I'm trying to flash a bootloader now,
Btw, the phone should auto boot when the installation finish right ? its not happening here...
I get the firmware but not working dear.........:angel:
Hey is the Bootloader require???????
hey guys,
The first thing i did was to flash a stock ICS rom from sammobile.
the flash was successful but the phone didn't auto reboot and the problem persist.
I just trying the android 2.3.3
lets see what happen
syama35 said:
I just trying the android 2.3.3
lets see what happen
Click to expand...
Click to collapse
Ok, let me know if you did it :cyclops:
Glowing_Potato said:
Ok, let me know if you did it :cyclops:
Click to expand...
Click to collapse
I think 2.3.3 have a lots of different file so .. i just stuck in it what to put where in odin...(there is files like kernel, code ,modem,EFS & Multi....)
Help me..
syama35 said:
I think 2.3.3 have a lots of different file so .. i just stuck in it what to put where in odin...(there is files like kernel, code ,modem,EFS & Multi....)
Help me..
Click to expand...
Click to collapse
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
after this, flash the kernel on PDA
got it ?
Yes i get u ....... & thanks..
what about the auto reboot check box.. is it checked or after kernel ...........
syama35 said:
Yes i get u ....... & thanks..
what about the auto reboot check box.. is it checked or after kernel ...........
Click to expand...
Click to collapse
the auto reboot and F.Reset Time needs to be checked.
just flashed a single file firmwara from samMobile, the odin process was successful, but the problem persist.
odin log:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100VJLP7_I9100UHLPF_I9100ZTOLP4_HOME.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.bin
<ID:0/009> NAND Write Start!!
<ID:0/009> Sbl.bin
<ID:0/009> param.lfs
<ID:0/009> factoryfs.img
<ID:0/009> zImage
<ID:0/009> hidden.img
<ID:0/009> cache.img
<ID:0/009> modem.bin
<ID:0/009> RQT_CLOSE !!
<ID:0/009> RES OK !!
<ID:0/009> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/009> Removed!!
after this the phone still dead, no auto reboot. cant manually reboot either.
Glowing_Potato said:
the auto reboot and F.Reset Time needs to be checked.[/QUOTE
where to put this EFS_I9100XWKE8_CL214845_REV02_user_low_ship.tar file ..............
---------- Post added at 09:07 PM ---------- Previous post was at 09:03 PM ----------
I already did the single file of 4.0.3 & 4.0.4 UK EDITION..
THATS NOT WORK
i just didn't get what about the EFS file to do
Click to expand...
Click to collapse
syama35 said:
Glowing_Potato said:
the auto reboot and F.Reset Time needs to be checked.[/QUOTE
where to put this EFS_I9100XWKE8_CL214845_REV02_user_low_ship.tar file ..............
Click to expand...
Click to collapse
i think you dont need to flash this one.
either way, its go on PDA.
Click to expand...
Click to collapse
don't know what else to try.
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Under the root66 image the phone is only registering 4 gigs of available space.
Junior member, where did you find the alternate restore method?
exmeaguy said:
Junior member, where did you find the alternate restore method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
exmeaguy said:
Thanks for checking. When I run the first method (3 times now) it fails at the sboot.bin step. I did download the alternate method once from the first site, but it said the file was not a PDA file. How did you get the alternate method file to work? I appreciate the help.
---------- Post added at 12:40 AM ---------- Previous post was at 12:38 AM ----------
The file extension ends with XZ, which Odin said was not a PDA file.
Click to expand...
Click to collapse
It has an odd file extension .xz (perhaps meant to be .gz) so I told 7zip to extract it. resulting file ended in .tar.md5. Then it works.
Hope this helps.
Thanks Junior member I will try that.
exmeaguy said:
Thanks Junior member I will try that.
Click to expand...
Click to collapse
I'm curious why you keep calling him junior member?
Sent from my SCH-I605 (AKA NOTE 2)
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
exmeaguy said:
Oops, sorry rdeckerr, I was looking too quickly at the name and looked at the wring line.
Click to expand...
Click to collapse
hahahaha
Wasn't sure if it was a newbie hazing kind of thing. That's funny though. No worries!
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
exmeaguy said:
I thought I saw on one of your posts that you used root66 (same as me) and that your phone only shows 4gb of space. Did you re-root with root66 or did you use another method?
Click to expand...
Click to collapse
Originally I was rooted with Adam Outler's casual / ODIN method (which was flawless first time round). I had tried the root66 this time just to see if it would actually take with ODIN since the stock restore kept failing. I was just desperate to find a rom that would "pass" on ODIN. I just needed to know my phone was still capable of booting fully back into android. Even if it happened to be without radio / activation capability or a wrongly registered internal storage space (which was friggin wierd, couldn't even take a screenshot).
I will re-root with Adam's process, when the kinks are out (say next weekend when I have a couple days it doesn't matter if my phone is dead . I had A.O.'s original root running for a couple weeks and it was great. The implementation was smooth, not requiring reinstalling / restoring anything. I'd backed up of course but it was one of those nice times the backups weren't necessary.
So at the moment for the sake of my job, I'm leaving it stock for the week. I just can't be without a phone for work.
rdeckerr said:
http://forum.xda-developers.com/showthread.php?t=2040264
Took me a moment to find it. The only difference between the 2 is that the alternate one is without sboot.bin.
Click to expand...
Click to collapse
Welli have the same exact issue. I am so lost its riddiculous. I have been working on this for over 20 hours and have gotten no where.
The only thing. Can add is that I attempted to root my device with the method that injects the 1 gig file in the system. Worked fine and installed cwm. Restarted and bricked with the unauthorized by verizon message. Downloaded the stock file without bootloader first and worked fine. I then tried every sinfle methodand trick I coild find to no avail.
Every time I try to install the baseline bootloader so I can unlock it fails at the end. If itry to put a full stock image on it fails at the beginning.
They both fail when tryinf to do the sboot.bin. so its obviously with that.
I need some ind of fix but no one seems to have it. I cant be doomed to a uncustomized device!
I am thinking of seeing if my verizon store will take it back and give me a fresh one so I can do the original exploit method.
It might work. Ive had the phone for less than a month.
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
universexda said:
Don't you need to flash a pit file if you're not doing so when you run into sboot.bin issues?
Click to expand...
Click to collapse
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot.
Sent from my SCH-I605 using Tapatalk 2
rdeckerr said:
**** Major Update: Thanks to imnuts and his alternate restore, I'm back on track and unrooted stock again.
For some reason the sboot.bin causes ODIN to fail. If this is just an isolated incident, cool, if not, this could mean getting back to stock out of necessity may be harder than we expected. Something to keep an eye on.
For reference, imnuts' post with the stock restore images:
http://forum.xda-developers.com/showthread.php?t=2040264
*** UPDATE: Still can't update with the stock image but I used the root66 stock rooted image and ODIN was able to complete. I'm able to boot the phone normally however it won't activate. I am completely lost here. ***
Was stock rooted no mods, so I flashed back to stock so I could perform the OTA update. That went fine so I installed the update.
Using Adam's new post OTA root the process didn't take so I tried a second time. The process hung and I had to do a battery pull.
Now it either boots into the Plug into Kies for emergency firmware upgrade or the Samsung Galxy Note 2 boot logo and goes no further.
Again attempting to restore to stock I flashed with Odin and here's where it gets interesting.
The process FAILS at the sboot.bin element.
*** Is it posible the OTA update made the stock recovery image incompatable? ***
Using the instructions here: http://forum.xda-developers.com/showthread.php?t=2024207
----- ODIN LOG -----
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
----- END ODIN LOG -----
ODIN and Casual see the phone and can talk to it however KIES cannot so I can't do this emergency recovery the phone is telling me to do. KIES says the device is not responding and to reboot it.
I can boot into Download Mode. I was able to get into Recovery Mode but can't now. The error in Recovery Mode was something about /system not being found.
I have no idea what to do. I have tried the process on 2 different computers. Am I Bricked Bricked?
Thanks in advance.
Click to expand...
Click to collapse
Is there a fix for this? I have been getting the same error message via odin. Can someone post the fix or link so we can get back up and running...thanks.
kintwofan said:
No it fails at sboot because the ll4 boot loader is set to block any writing of a boot loader at all. That's why you need the alternate restore because it didn't write sboot
Click to expand...
Click to collapse
The alternate restore won't attempt to restore the bootloader to stock right?
universexda said:
The alternate restore won't attempt to restore the bootloader to stock right?
Click to expand...
Click to collapse
That's right. It will restore everything except the boot loader. It's really to restore and keep boot loader unlocked, but add an added benefit let's unbrick the new ota.
Sent from my SCH-I605 using Tapatalk 2
Same problem
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
aka113 said:
I have the same problem as the original post i keep getting stuck at shoot.bin, as it is know my phone is unusable! I was wondering if their is any method to get it back to the original FW.
Click to expand...
Click to collapse
Did you actually read any of this thread? We got his phone working.
Sent from my SCH-I605 using Tapatalk 2
As the title states, I am currently trying to flash my phone back to stock to fix a soft brick. I was trying to get the latest update since I was on a custom ROM and couldn't get the OTA. I got the firmware from Sammobile, from what I understand to be a reputable place to get them. The flash in Odin seemed to go normally until it had the phone restart, It is now is a loop of flashing the "Galaxy Note II" screen. And I had CWM installed, but I cannot get to the recovery with it in this loop.
Yes, I have read the sticky before posting this. I am doing the only recommended thing I can find to do for this sort problem, flash it back to stock. I have the stock firmware, directly from the link in the sticky, and when I go to start it on Odin this is what I get:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> SingleDownload.
<ID:0/005> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there something I'm missing/doing wrong? I have installed a few ROMs before, but I am fairly new to using Odin and flashing the firmware.
I would greatly appreciate any help with this
Thank you!
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
nikhil.kdhand said:
Hi,
Hope you used pit file in odin along with rom file. Also, do a factory reset after successful odin.
Thanks,
Nikhil Dhand
Chat: [email protected]
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I believe that was the problem. I didn't know it needed the PIT for this.
The phone lives again, but it's strange. The flash was almost done, got to the sboot, and failed. My phone had "unsupported version" in red on the Odin screen. I rebooted the phone, it went to the android update screen, and now it is working like it did before all this.
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
It is possible that the usb port I used was bad, I seriously need to remember not to use the front ports for something like this...
I need to read up more on this so I don't screw it up next time.
SFBob9 said:
Now the question is, why did the 4.3 firmware send it into a boot loop? Is the file on Sammobile the right one? Would it be better to just get my phone back to stock with a stock recovery, and get the update OTA?
Click to expand...
Click to collapse
It is important to note that if you take the OTA, it WILL relock your bootloader. This means no custom recovery and no custom ROMs.
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Naweed Reza said:
Hey guys. I've run into an issue with my GT-i9300 International version just yesterday at it's racking my brains up.
Here's the lowdown about the device
It's the international GTi9300 (3G version)
It runs ArchiDroid v2.1.4 ROM
This rom was installed a year ago and gave no issues what so ever.
Just yesterday the device did not boot up. i Managed to get it into philz recovery to see whats the problem. i get the error message that it couldnt mount /data, /system & etc.
I have posted the screenshots. I've tried backing up, mounting and even factory wiping but it does not work
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure :crying:
I hope this is not the case since i have lots of important data on this phone (it's my secondary phone)
Have a look at the screens. lemme know the fate of my S3, whether it is possible to recover this device or not
p.s: I've checked all over the net. i've only come across the /efs not mounting issue. not what im going through
Click to expand...
Click to collapse
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
i'll try flashing the stock rom via odin
Yeah, now i gave up on caring about the data. i really need the phone to work tho
i'll get back on the progress
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
tallman43 said:
Have you flashed stock firmware with Odin yet? This is the first thing you need to do to see if Odin works or gives errors....don't forget to factory reset after flashing. I'm afraid you may have to live with losing your data if you can't back it up in recovery.
Click to expand...
Click to collapse
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tallman43 said:
Be careful the thread is for verizon you can't flash any pit files from there be 100% sure the pit file is for S3 international try looking here this is the rescue firmware >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << there is a pit file in the 4.1.2 download but you need to flash the 4.3 in the link to stop efs issues. But to be honest it doesn't look too good if this fails I recommend a service repair.
Click to expand...
Click to collapse
I had downloaded the pit from another site. it was the international one
But i'll try your link. i just saw your reply
I'm downloading the 4.3 GT-I9300XXUGMJ9_KOR_MULTI_FACTORY package
Naweed Reza said:
Tried flashing the pit. I got the following error messages on odin
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
tallman43 said:
You need to flash everything at once pit file and rom look at the link I sent you but it looks like you need a new motherboard:crying:
Click to expand...
Click to collapse
Oh maan
Last resort is the link you gave. i'm downloading the 4.3 package. will put everything and flash at once. if this doest work. rip i guess :/
I never did anything. I installed the custom rom a year ago and let the phone be. didnt bother tweaking or adding to the custom rom
Then all of a sudden it doesnt boot
Naweed Reza said:
@tallman43
Status report.
I tried flashing a stock rom which is on 4.3
It says NAND write failure. screenshot uploaded.
So i'm guessing my eMMC is corrupt or has failed :crying:
I did more research and found out that i could repartition it using a .pit file
This thread shows the relevant pit files
http://forum.xda-developers.com/showthread.php?p=30547929#post30547929
GT-I9300_mx_20120220.pit is for the 16 gb s3.
i'll flash with with the ROM
Lemme know if this is alright :good:
Click to expand...
Click to collapse
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
So flashing all 4 stock files (including pit) via odin turned out to be a Fail
I guess the eMMC is not functional resulting in a hardware failure
Thanks for the help @tallman43
If anyone else has suggestions, feel free to post them here
Dz-Horse said:
I have a feeling the eMMC flash storage has failed and therefore i have a hardware failure
This is true
Click to expand...
Click to collapse
Has this happened to your S3?
I havent tinkered with anything and this happens
I just installed a ROm and left it for a year
Oh well
Yes it happened to me same problem