Hi there,
it's matteios1984 first of all i'd like to say hello to the comunity and thank you all for interesting post about Android!
I'm here to asking help about a tricky case. I've a Samsung Galaxy S3 (i9300) bricked. In other words the phone behaves as follow:
- If i try to turn on the device it remains stuck on Samsung S3 logo
- No possible to boot in recovery mode
- When I connect it to the charger it's stucked showing the battery image and not showing any progress about charging status
- The device is still able to boot in download mode both with buttons combo and with resistor trick, but Odin is not able to flash anything on the device (my idea is to flash a Customer Recovery, perform a full wipe of the device and after restore original italian firmware)
Here following a log taken from Odin:
<ID:0/003> 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/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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If i try to flash a file containing PIT informations here following the log from Odin:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've heard about the possibility to boot the device by a MicroSD card that allows me to flash the device... Do you think this will fix my issue? Or do I need a box? If so, any suggestion about the model is appreciated.
Thanks in advance for your support
Try downgrading the bootloader to BLFB before flashing firmware or pit.
Related
Ok so after looking everywhere for a solution and screaming like a mad man in the process i decided to make a thread here and see if someone can help me.
I was running the leaked Android 4.0.3 (got the files from software2tech.com/2012/01/26/complete-guide-update-android-4-0-3-i9100xxlp6-for-samsung-galaxy-s2-video/) and i was running fine. Now i decided to root my phone using software2tech.com/2012/01/27/how-to-root-samsung-galaxy-s2-android-ics-4-0-3-i9100xxlp6/#more-16920
When Odin restarted my Phone all i got was that yellow triangle and i wasn't able to do anything at all but go into download mode (recovery mode is not working) so i thought i could just flash the 4.0.3 Android again and it will all be fine right?....WRONG. Got an error in Odin and after that my phone just said "Firmware Upgrade encountered an error. Please select recovery mode in Kies and try again". Tried it but Kies is not recognizing my phone (neither on the "Firmware upgrade error" screen nor in download mode).
Tried Pistachios Recovery guide but the recovery is not working...i can flash the kernel (which sends me back to the yellow triange) but when i try to flash the recovery files or the bootloader i just get more errors. Also read that flashing a stock kernel could be able to fix a problem like this but how am i supposed to find out what my kernel version is, and choose the right one for my phone if i can't start my phone?
Edit: Ok so here are the errors i get when i try to flash
Recovery files:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKI3.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.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Bootloader:
<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> Sbl.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PS: My Provider is Alice
bump bump bump
tried with stock files....error
<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> param.lfs
<ID:0/003> zImage
<ID:0/003> boot.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
tried the stock files again with the recovery kernel as pda (yeah probably not a good idea but i'm at the point where i don't really care anymore) got this error
<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> zImage
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003>
<ID:0/003> Receive Response form LOKE
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Miigi said:
Ok so after looking everywhere for a solution and screaming like a mad man in the process i decided to make a thread here and see if someone can help me.
I was running the leaked Android 4.0.3 (got the files from software2tech.com/2012/01/26/complete-guide-update-android-4-0-3-i9100xxlp6-for-samsung-galaxy-s2-video/) and i was running fine. Now i decided to root my phone using software2tech.com/2012/01/27/how-to-root-samsung-galaxy-s2-android-ics-4-0-3-i9100xxlp6/#more-16920
When Odin restarted my Phone all i got was that yellow triangle and i wasn't able to do anything at all but go into download mode (recovery mode is not working) so i thought i could just flash the 4.0.3 Android again and it will all be fine right?....WRONG. Got an error in Odin and after that my phone just said "Firmware Upgrade encountered an error. Please select recovery mode in Kies and try again". Tried it but Kies is not recognizing my phone (neither on the "Firmware upgrade error" screen nor in download mode).
Tried Pistachios Recovery guide but the recovery is not working...i can flash the kernel (which sends me back to the yellow triange) but when i try to flash the recovery files or the bootloader i just get more errors. Also read that flashing a stock kernel could be able to fix a problem like this but how am i supposed to find out what my kernel version is, and choose the right one for my phone if i can't start my phone?
Edit: Ok so here are the errors i get when i try to flash
Recovery files:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9100XXKI3_CL577579_REV02_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9100XXKI3_REV_02_CL1062028.tar.md5 is valid.
<OSM> GT-I9100-CSC-MULTI-OXAKI3.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.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Bootloader:
<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> Sbl.bin
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
PS: My Provider is Alice
Click to expand...
Click to collapse
my friend
if u don't use software from xda forum, why u make posts here. go to software2tech.com and make posts there. u asked us to give a solution to something we never used and we don't know nothing about.
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI500_VZW_EH03_GB_CM.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> param.lfs
<ID:0/003> Sbl.bin
<ID:0/003> boot.bin
<ID:0/003> recovery.bin
<ID:0/003> zImage
<ID:0/003> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!
Click to expand...
Click to collapse
lolreconlol said:
Phone is 'bricked', and gets stuck on Samsung logo. How do I fix this? I'm trying to follow threads on how to get back to stock, but most of the links are dead - so if anyone can help, that would be great! When following some guides, I get the following error:
Click to expand...
Click to collapse
If you're coming from ICS or CM7, you need pit file for re-partition.
jhssal said:
If you're coming from ICS or CM7, you need pit file for re-partition.
Click to expand...
Click to collapse
Ah! Thanks, worked that time.
Hi,
I have a Verizon Samsung Galaxy Note II, (SCH-1605), and I have apparently soft-bricked / boot-looped my device.
I followed droidstyle's tutorial titled, "[GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!."
Installed Odin on my Win8 x64 desktop
Downloaded the proper pit and tar files from his tutorial
ran odin from the "downloading" screen
How can i fix my phone and/or reset it to factory condition?
What may have caused my phone to boot-loop?
P.S. (I still wish to root the phone and try some custom roms once it is operational)
try flashing root66 with no pit file.
Thank you for your response.
I tried flashing with "rooot66_VZW_stock_system.tar.md5," in both bootloader and PDA slots in Odin3 v1.85.
I ran at least one attempt of both with and without the pit file. The yellow highlighting is present.
The phone still seems to be in a boot-loop. Could it be that I'm using the wrong Samsung Drivers on my PC? They were plug-and-play as far as I could tell. I did run the OTA updates before I knew they had something to do with locking down the bootloader.
Below I will paste the various Odin logs...
Root66 in PDA w/ Pit file
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<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)
--
Root66 in PDA w/o Pit file
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<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)
--
Root66 in BOOTLOADER w/ PIT file
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img
<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)
--
Root66 in BOOTLOADER w/o PIT file
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_VZW_stock_system.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> system.img
<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)
--
Ok what you need to do is reflash root66 in pda with pit, power the device off, press and hold the volume up/home/power buttons and boot into recovery, then wipe data/factory reset, and reboot.
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
and dont flash anything in bootloader...simply trying random techniques is a good way to turn your device into a paper weight.
taylorp0994 said:
Hi,
I have a Verizon Samsung Galaxy Note II, (SCH-1605), and I have apparently soft-bricked / boot-looped my device.
I followed droidstyle's tutorial titled, "[GUIDE][VZW Edition]How to Root/Rom/Return to Stock the VZW Galaxy Note II!."
Installed Odin on my Win8 x64 desktop
Downloaded the proper pit and tar files from his tutorial
ran odin from the "downloading" screen
How can i fix my phone and/or reset it to factory condition?
What may have caused my phone to boot-loop?
P.S. (I still wish to root the phone and try some custom roms once it is operational)
Click to expand...
Click to collapse
After flashing with Odin you must do a factory reset.
I also had this on my Galaxy S2 Plus.
Sent from my GT-I9105P using xda app-developers app
droidstyle said:
Ok what you need to do is reflash root66 in pda with pit, power the device off, press and hold the volume up/home/power buttons and boot into recovery, then wipe data/factory reset, and reboot.
---------- Post added at 10:07 AM ---------- Previous post was at 10:05 AM ----------
and dont flash anything in bootloader...simply trying random techniques is a good way to turn your device into a paper weight.
Click to expand...
Click to collapse
Thank you. I was previously unaware of the power/home/vol.up combination for factory reset. I re-flashed root66 in PDA w/ the PIT file, however this time it went to the android with a neutron-like animation inside signifying updates. It worked w/o running a reset, but I ran one anyways to ensure I know how it works.
Again, thank you for your support.
So my friend was trying to fix the wifi on his Note while on Sky Rom (4.3), but, for some reason he happened to have clicked a link to the wrong section and was in the n7100 (international) section. He used Odin to flash the MJ5 bootloader which is the international version. Now his phone will only bootloop with the N7100 boot screen appearing. We are not able to access recovery but we can get to download mode. Once we got to download mode I have tried flashing the PIT file, root66, and the official VRAMC3. Each attempt without a PIT file causes this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And any attempts with the PIT file causes this
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be very much appreciated because I have run out of ideas at this point.
Jet5195 said:
So my friend was trying to fix the wifi on his Note while on Sky Rom (4.3), but, for some reason he happened to have clicked a link to the wrong section and was in the n7100 (international) section. He used Odin to flash the MJ5 bootloader which is the international version. Now his phone will only bootloop with the N7100 boot screen appearing. We are not able to access recovery but we can get to download mode. Once we got to download mode I have tried flashing the PIT file, root66, and the official VRAMC3. Each attempt without a PIT file causes this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And any attempts with the PIT file causes this
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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be very much appreciated because I have run out of ideas at this point.
Click to expand...
Click to collapse
I went through this last month and check these things:
- Try a different USB cord
- Try a different USB port
- Disable your antivirus
- May have to reboot your computer
When I softbricked a few weeks ago I went through this process for the first time, and I found I had to keep trying over and over but it finally ended up working.
Remember to unlock your bootloader after this process - which I did not and had to redo everything after rooting and flashing and getting the Verizon discovered unauthorized software etc.
Also, I wonder if this is part of the issue, while in download mode I get "PRODUCT NAME: GT-N7100" instead of sch-i605, could this be part of the issue?
And thanks for the ideas Darbylonia, I tried those and even different computers and still no luck.
Jet5195 said:
Also, I wonder if this is part of the issue, while in download mode I get "PRODUCT NAME: GT-N7100" instead of sch-i605, could this be part of the issue?
And thanks for the ideas Darbylonia, I tried those and even different computers and still no luck.
Click to expand...
Click to collapse
Did you try looking through the top stickied post about how to recover from a soft brick? I would go there and see if the info helps and post there. I do think it is strange about the product name but there's got to be a fix so keep on...
hi guys..
is there any wat to downgrade this version (i545VRUFNK1) to 4.3..?
t-mobile_mda said:
hi guys..
is there any wat to downgrade this version (i545VRUFNK1) to 4.3..?
Click to expand...
Click to collapse
yes downgraded..
first flash with this;
MK2_system_4downgrade
then flash,
MK2VZW-downgrade4rooting-AIOdin-gogolie
Bricked S4 SCH-I545
NEED HELP PLEASE!!!
I tried the Odlin3 approach for full wipe (with 3.09, 3.07, 3.10 version) but I get a fail as posted below. I'm completely stuck. I tried using Kies approach posted on another tread and the approach on http://forum.xda-developers.com/showthread.php?t=2751461. Both approaches failed. I've downloaded about 20GB of firmware and each fails. When I just try to power on the device it shows the SAMSUNG name and the "Unlocked" icon. Any suggestions?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
treaklet said:
NEED HELP PLEASE!!!
I tried the Odlin3 approach for full wipe (with 3.09, 3.07, 3.10 version) but I get a fail as posted below. I'm completely stuck. I tried using Kies approach posted on another tread and the approach on http://forum.xda-developers.com/showthread.php?t=2751461. Both approaches failed. I've downloaded about 20GB of firmware and each fails. When I just try to power on the device it shows the SAMSUNG name and the "Unlocked" icon. Any suggestions?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_I545VRUFNC5_I545VZWFNC5_1151670_REV06_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
BladeRunner said:
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
Click to expand...
Click to collapse
ODIN Mode.
BladeRunner said:
When you boot into download mode what version does it say you are on? (it's the red lettering at the very top)
Click to expand...
Click to collapse
Odin Mode