Related
Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
MrBrickedPhone said:
Hello all,
First I must congratulate all of you technically minded people who've guided me through rooting and custom rom-ing my G1, S2 and now S4, but it seems now that I have a phone beyond repair.
Background
I have a GT-I9505 from the 3 network [h3g] here in the uk.
A couple of months ago I used CF auto root to give root privileges to install ad-away to remove those pesky advertisments yet all was not well.
Around once a week main core processes would hang or crash the phone completely and when the phone was rebooted or powered on, it would hang on the 3 logo.
Booting into recovery and wiping cache and data would fix it, as would a re-flash of the CF auto root using Odin.
A week ago, after a call, the phone hanged - i did a hard reset, removing the battery but the phone was stuck on the 3 logo screen again.
After becoming annoyed by this happening every week i decided to revert to stock rom.
What I have done
I flashed I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 via Odin.
Odin said it was successful although the phone still wouldn't boot.
I went into recovery mode and attempted to wipe data and cache, but wiping of the cache failed.
Repeated efforts led me to flashing a PIT file with the above ROM and again ODIN said it was a success, but still the phone hung on the 3 logo.
Booting into stock recovery, again the phone failed to wipe cache,
How my GT-I9505 is now in a worse state
After stock recovery failing to write cache i downloaded TeamWin recovery and flashed it to my phone and attempted to write cache. Again failed.
Now i did something stupid - i saw in the recovery menu something along the lines of "reset permissions", thinking this would let me delete the cache I applied it and proper bricked my phone.
I cannot boot into recovery - I am stuck on the TeamWin logo.
I'm not sure the battery is charging. (Grey battery icon with a 'refresh style' logo, no animated charging(
I can boot into ODIN mode.
Since this, I've been reading around and tried GT-I9505-Factory-Firmware-Full-Wipe-DBT
When attempting this, Odin gives:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_FULL_WIPE_I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> aboot.mbn
<ID:0/025> NAND Write Start!!
<ID:0/025> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Download mode says
ODIN MODE
Product name: GT-I9505
Current Binary: Custom
System Status: Custom
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
START [224, 1440]
But of course, the blue bar to show progress has barely started.
When trying to write stock rom with PIT file, Odin v3.07 displays this:
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMEA_I9505H3GBME3_I9505XXUBMEA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.img
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025> FAIL! (WP)
<OSM> All threads completed. (succeed 0 / failed 1)
hen flashing just the pit Odin says
<ID:0/025> Removed!!
<ID:0/025> Added!!
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Set PIT file..
<ID:0/025> DO NOT TURN OFF TARGET!!
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> RQT_CLOSE !!
<ID:0/025> RES OK !!
<ID:0/025> Removed!!
and phone reboots to samsung screen but progresses no further.
So this is real squeaky bum time and i really don't want to do anything else without advice as a true hard brick is not something I want nor can afford.
I've used the original white USB cable and other official samsung cables, I've tried different usb ports and computers with ODIN, all with the same results.
If anyone has any suggestions on how to unbrick this marvellous yet expensive phone, I will be truly and forever grateful and may buy you a pint if you're ever in Nottingham or perhaps do some statistics for you!!
Click to expand...
Click to collapse
Go to this website
You will learn how to unbrick your soft bricked s4
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Lalssa said:
Go to this website
You will learn how to unbrick your soft bricked s4
Click to expand...
Click to collapse
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
MrBrickedPhone said:
Been there - all methods do not work:
Cannot boot into recovery
Odin is not flashing ROMs with or without PIT
Click to expand...
Click to collapse
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html
If didnt work try again
angus_mcfisher said:
Hsve you tried just the pit and repartition on its own, and then trying from there to flash the rom? I've read others who had success this way
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
MrBrickedPhone said:
Thanks for the reply, yes I've tried just flashing the PIT, then the rom with all variations e.g. unticking auto-reboot in ODIN, hard reset, boot into ODIN mode, then attempting to flash the ROM.
ODIN will flash the PIT but refuses to flash the ROM
Fail (WP)
I'm assuming (WP) is some kind of write protection
Click to expand...
Click to collapse
Download another version of odin
Lalssa said:
Download another version of odin
Click to expand...
Click to collapse
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
MrBrickedPhone said:
I've just tried it with ODIN v3.04 and v1.85, with combinations of PIT alone with no auto reboot followed by flashing the rom along with doing both at once and unfortunately even though ODIN writes the PIT it fails to write the ROM.
<ID:0/025> NAND Write Start!!
<ID:0/025> recovery.img
<ID:0/025> system.img.ext4
<ID:0/025>
<ID:0/025> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It appears to be a non-standard brickage to say the least i'm afraid.
Click to expand...
Click to collapse
Try flashing using heimdall you can find some interesting tutorials if you google it
Lalssa said:
Try flashing using heimdall you can find some interesting tutorials if you google it
Click to expand...
Click to collapse
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
MrBrickedPhone said:
Thanks, reading up on it now. Will report back when i've learned enough to attempt to flash things
Click to expand...
Click to collapse
Using Heimdall:
As with ODIN, writing the PIT is completed.
Alas, Heimdall cannot write ANY partitions from the extracted .tar files from the GT-I9505-Factory-Firmware-Full-Wipe-DBT ROM.
It does seem that the flash memory is write protected - it certainly cannot be written to.
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Obagleyfreer said:
If I were in this situation I would do the following:
Download latest PhilZ recovery for i9505.
Flash this in PDA section of Odin.
Boot to recovery and go to mounts and storage.
Format system, data, cache, preload (and format SD card if there's nothing important you need like photos etc)
You now have a TOTALLY clean device.
Boot to download mode and flash MGA stock firmware with Odin.
I would download the MGA firmware from Sammobile as these are untouched stock firmware files.
If flash is successful boot to recovery (it will now be stock) and wipe data factory reset.
Now reboot.
Hopefully you should be good to go
P.S If once again Odin fails on nand write start the you probably have a corrupt nand and I hate to say it but a whole board replacement might be needed.
Good luck mate!
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for taking the time to provide the advice, I've tried flashing PhilZ recovery via ODIN and it tells me it has been successful, however when i try to boot into recovery it appears it's not flashed at all as I get stuck on the previous recovery TeamWin loading screen - it looks as if the nand maybe corrupted after all.
chickentuna said:
Have you tried to flash the pit + stock firmware with the re-partition box checked?
BTW, be careful using Heimdall. I've hardbricked my phone to the point that I cannot go to recovery and download mode while using that tool. It was impossible to turn the phone off and charge the phone as well. I didn't know what caused it (probably incorrect bootloader/pit) but as a result I needed a board replacement. Luckily Samsung replaced it for free as they cannot revive the phone anymore lol.
Click to expand...
Click to collapse
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
MrBrickedPhone said:
Yes, I've attempted to flash the pit + correct stock firmware with the re-partition box checked and while it writes the pit, Odin starts to write the firmware then fails about halfway through.
Perhaps, reading between the lines, it would be better for me if indeed I hard bricked the phone to a state where the recovery and download mode are not accessible as then it would not be obvious I had invalidated the warranty by previously rooting the phone and would get a free replacement!
Thanks for taking the time to reply.
Click to expand...
Click to collapse
Damn that's quite unfortunate. Sorry mate, I'm out of ideas. I wouldn't actually advise to hard brick the phone intentionally because as far as I know there's still hope as you can still access download mode.
Well if you can't really flash anything it's probably best to just hard brick the phone to the point that the Samsung guys wouldn't be able to revive it then send the phone for repairs than having to send it in it's current state because they'll most likely find out that you've modified your phone. Again I strongly suggest not to do it.
Good luck. Hope you fix it soon buddy.
Sent from my GT-I9505 using Tapatalk 4
Download Kies and install samsung drivers with it. Click on tools tab and click emergency firmware restore. Type in your phone model e.g GT-I9505 and then type in your Serial Number (can be found in the battery compartment of the phone) Kies will then ask you to go to download mode and then it will start downloading firmware and installing it on your device.
The write protection enabled message suggests to me that you've previously had one of the stock firmwares with the new bootloader. Have you had MH8 on there?
If you're desperate you could always try flashing MH8 firmware. The new bootloader won't let you downgrade to an older firmware giving a message as above.
Sent from my GT-I9505 using Tapatalk 4
Had this issue
Hey There, i had this issue last night infact, i had bricked my phone, recovery not accessible and download mode only possible by plugging it in and then starting it, try this put your phone into download mode, via plugging it in then turning it on, when it is in download mode flash PhilZ recovery via the PDA option then turn it off after flashing by taking out the battery (after it has rebooted and flashed), then plug it in again, launch into recovery and wipe/format etc.. install a new MH8 stock firmware (with the new bootloader) then you should be okay.
It should be noted that i did these step and it worked, except i didn't ever install a new rom and kept stock and i used a nandroid backup instead of installing the stock rom
You say twrp logo shows up. Does it start adb ? Maybe u can remount partitions as RW with terminal . manually wipe it. And then try adb sideload to install a .zip
All I can think of as every other suggestions seem to have been mentioned.
Sent from my GT-I9505G using xda app-developers app
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
hello. have you tried another version of odin? im sure someone can help you revive your phone
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
hypnodaz said:
Mine did the same thing,put it into download mode and flash cwm recovery and it'll come to life..
Click to expand...
Click to collapse
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
---------- Post added at 09:37 AM ---------- Previous post was at 09:31 AM ----------
Mamba25 said:
Thanks, once I have used Odin v3.09 to flash cwm recovery, will I still need to flash back to stock or will it simply work?
Click to expand...
Click to collapse
Have you tried using Odin V3.09 to flash 4.4?
hey_joe said:
You will have to flash stock firmware 4.4 before your phone will work again. Simply flashing cwm will get you to cwm recovery but not a working phone.
Click to expand...
Click to collapse
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Mamba25 said:
Hi, I have found a tutorial on flashing ClockworkMod Recovery v6.0.4.5 but it states:
"Must enable USB Debugging first" and also "Must let Reactivation lock off first", is this absolutely necessary as I can't access my phone, let alone its settings? Can I still proceed with installing ClockworkMod Recovery?
Click to expand...
Click to collapse
Don't follow that one.
Go here and download the right file for your phone's model, put phone in download mode and flash using odin in ap/pda slot.
Btw, have you tried flashing 4.4 using odin v3.09?
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
hypnodaz said:
When odin gives you the fail message technically you've already flashed the stock, but for some reason odin doesn't recognise it as a pass. .leave your phone plugged in, reset odin, put your phone into download phone and then flash recovery. . Hey presto your phone will wake up..
Click to expand...
Click to collapse
I don't think this is the case because when I first tried flashing from 4.3 to 4.4.2 it tried for a few seconds then failed and been stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“ despite resetting Odin and going back into download mode, tried reflashing but keep getting the 'FAIL' (logs posted in original first post).
Is there any reason why my phone is being detected as 'Samsung GT-S5690' in MobileGo? I'm thinking if Kies could detect it as the Note 3 again my problems would be solved.
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Mamba25 said:
I haven't tried Odin v3.09 because to be honest I thought the firmware file once extracted as a RAR file could only be read by Odin v3.07 is that not the case?
Soz everyone
Click to expand...
Click to collapse
No it's not.
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
“Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“
I have looked extensively through the threads already started but couldn't find a solution particularly as Kies is not recognising my device anymore stating it is an unsupported device, furthermore, 'MobileGo' software is showing the device as being a 'Samsung GT-S5690', instead of Note 3??. I tried Odin to recover back to original firmware but failed both times and phone now stuck on “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again“.
My Mobile details are:
Model Number: SM-N9005
Serial Number: RF1DA5NMM5M
This is a log of 2 different attempts using Odin, one to 4.4.2 and the other back to stock:
Odin3 v3.07
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXADMK2_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<OSM> All threads completed. (succeed 0 / failed 1)
Please advise as I am left without a phone and only had it two months.
Your expertise and help would be gratefully appreciated.
Many thanks
John
Click to expand...
Click to collapse
looks like u r trying to flash 4.3 & 4.4 one after one, now dont try 4.3 at all, make sure kies is not running in baground, disable antivirus if any.
I had the the same issue with kies myself, tried every trick in the book before I tried the method I mention above.. maybe it's an issue with the phone itself, or a certain batch of phones?
Mamba25 said:
Hi all,
I've heard great things about this website and joined up hoping to God you could help me. I tried updating the firmare on my phone to 4.4.2 from 4.3 using Odin3 v3.07 and it stopped suddenly with an error message and now my Note 3 continuously displays:
...
Click to expand...
Click to collapse
The writing of stock 4.3 fails since your bootloader was updated by your failed attempt. You will probably never be able to write a 4.3 stock image.
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
xclub_101 said:
The writing of 4.4 NB1 fails since probably it is for a slightly different region with a slightly different partitioning scheme. Ideally install the 4.4 for your specific model/region. If that fails you might need to write some 4.4 with repartition - there are some threads around (I think also the Hong-Kong version had serious problems with 4.4 because of that).
Click to expand...
Click to collapse
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
There is AP in 3.09 in place of PDA.
Mamba25 said:
I saw the Hong Kong thread and to be honest got lost reading the posts, i'm beginning to think this is going to be a task beyond my capabilities as not the most technologically minded of people and need to be spoon fed. Is there an easy way to find out if I have a Hong Kong version phone? I brought it from e-cell on Ebay a couple of months ago?
If using a different version of Odin such as v3.09 once the firmware file is extracted where does it go as v3.07 is goes in the PDA section?
Many thanks
Click to expand...
Click to collapse
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
xclub_101 said:
I don't think there is an easy way to see what the original version was as long as you can no longer boot the phone. I think the EU model is generally listed as N9005ZWE while the HK is N9005ZKA and that might be written somewhere on the box. Also it might be a different partitioning model even if it is not a Hong-Kong model.
Click to expand...
Click to collapse
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
madsus said:
Could you please let me know if the update be completed successfully. I have the same problem so want to know the steps of the
same. Please help me.
Click to expand...
Click to collapse
I've taken the phone to a repair shop recommended by Samsung themselves, they've had it a week now and I rang yesterday and they said it is the first Hong Kong Note 3 they've received and are waiting to hear from Samsung as to how to repair it. BIG YAWN!
Will keep you posted - miss my phone
Note 3 SM-N9005 firmware upgarade issue
Hi , i am having the same problem in my Note 3 i upgraded phronesis rom and after the phone was not detected in computer. so tried to flash custom kitkat rom again then it got disconnected and then showing error as firmware upgrade issue,
tried to download firmware and update by Odin, tired cmw recovery and tried many firmwares, Odin shows Failure and Kies dosent shown code or phone in emergency recovery , all ways failed, is it possible to make the phone work normal.
hi
i wanted to update my phone from 4.4.4 to 5.0.2 but odin stuck on aboot.mbn then i downloaded 4 files firmware include bl ap cp csc but odin said aboot,mbn fail and then i flashed just ap file but i saw an error on writing system.img and now my phone dosnt boot and auto goes to download mode.
please help
here odin log :
Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> A300FXXU1BOD5_A300FOXY1BOD5_A300FXXU1BOD5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/037> Added!!
<ID:0/037> Odin engine v(ID:3.1005)..
<ID:0/037> File analysis..
<ID:0/037> SetupConnection..
<ID:0/037> Initialzation..
<ID:0/037> Get PIT for mapping..
<ID:0/037> Firmware update start..
<ID:0/037> SingleDownload.
<ID:0/037> aboot.mbn
<ID:0/037> NAND Write Start!!
<ID:0/037> FAIL! (Auth)
<ID:0/037>
<ID:0/037> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i have downloaded 10 different files but problem still doesnt solve. also i have tried recover phone with Kies but it doesnt know phone
you may have reactivation lock ticked under the security settings.
PlutoDelic said:
you may have reactivation lock ticked under the security settings.
Click to expand...
Click to collapse
now phone doesnt boot
can you do me favor ?
If it boot to download mode, try flashing a 4 file package stock rom. You can get it with SamFirm.
Sounds like a soft brick, but if the reactivation lock is on, you wont be able to flash anything through odin.
i have tried with 4 part firmware but that error apears.
i dont acces to disable reactivation lock . so what shoud i do now? do you have any idea?
try using the pit file as well, it's included on the CSC package of the 4 part files. Load it on the PIT tab.
If that wont make a difference, your eMMC (internal storage) is either locked or done.
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> Added!!
<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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> Added!!
<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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file
Owen007 said:
Download odin from this thread:- https://forum.xda-developers.com/grand-prime/general/tut-how-to-install-xposed-framework-t3508071
And download stock recovery for your device model and add open odin add the stock recovery to pda and flash it.
Note: make sure u have samsung drivers installled and do not add pit file
Click to expand...
Click to collapse
Did it, but still have the problem that i described earlier. Odin3 from the thread that you suggested, gives me the above text:
<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)
I didn't test with the pit file that i found for the 531F variation
->EDIT: tried to flash the pit file and it didn't work. It says Repartition Failed
jhonatann989 said:
So, a friend of mine brough me his phone; he told me that it just didn't turn on again and it hasn't no waranty so i decided to try to do something to fix it.
Is not the first time that i worked with samsung phones, so i technically know what to do; i downloaded Odin v3.12, the latest Samsung drivers and the correct firmware
The phone boots inmediately to download mode but it shows that doesn't find some JPG images. The exact text is below:
NO IMAGE: warningmessage.jpg
NO IMAGE: download_image.jpg
ODIN MODE (MULTI CORE DOWNLOAD)
PRODUCT NAME SM-G531m
CURRENT BINARY: Samsung official
SYSTEM STATUS: Custom
FAP LOCK: OFF
KNOK WARANTY VOID: 0x0
Secure Download: Enable
RP SWREV: S0, L0, M0
I tried to flash an oficial firmware but ODIN tells me that there is no pit partition. I understand that this error means that PIT partition is screwed or something. I have no pit file for this phone so i searched the internet and found the Pit file for the 531F variation. I couldn't find any descriptive information that explains me if there's a diference in the internal memory between 531M and 531F so y decide to take the risk.
What i found is that ODIN give's me error every time y try to flash with de PIT file, saying that there were an error whith the repartition.
<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/004> Added!!
<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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I downloaded another versions of ODIN and the only one tha't doesn't give me error is the 3.07 version but the flash process stuck at <ID:0/004> NAND Write Start!!
The only clue that i have is an hipothesis: Maybe the pit file is not the correct one, but more than that, i don't know anything else. The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M.
- is there a chance that some of you could helpme to find a correct pit file?
- could this happend for another reasons rather than a pit partition screwed out?
- is there something else that i should do?
-is this phone bricked?
Click to expand...
Click to collapse
odin only works with the correct version is on the device
tran nam hoang said:
odin only works with the correct version is on the device
Click to expand...
Click to collapse
i wrote this:
The log of ODIN is not very descriptive and i don't know what else i can do, except to try to find a Pit file extracted from another SM-G531M
Click to expand...
Click to collapse
then i asked for this:
- is there a chance that some of you could helpme to find a correct pit file?
Click to expand...
Click to collapse
If you have a PIT partition for the SM-G531M i will be gratefull if you share it with me
PD: BTW I HAVE the Correct firmware, my problem is PIT partition as i can conclude
Hello dear xda communtity,
i recently tried to root my samsung galaxy s4 (gt-i9515) and i somehow managed it to brick or soft brick my phone so i cant restore it with any flash. everytime is try to flash the stockrom on my phone with odin it failes with the message:
complete(write) operation failed.
i downloaded the original firmware and a pit file for the complete EU so it should work but it didnt.
Here is the full code after i try to flash the Original firmware on my phone:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9515XXU1BOJ3_I9515YIA1BOJ1_I9515XXU1BOJ3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
i tried a lot of usb cables and every usb port on my pc to flash it but nothing worked. i tried it multiple times but nothing helped.
When i want to turn on my phone it says me that i should get kies and select recovery mode. The problem is that kies dont have initials for my phone so that woudnt work.
I hope i dont completely destroyed my phone and someone could help me.
Thanks
Don't use kies, user smart switch.
Did you try flashing without the pit? The pit file is needed if Odin doesn't recognise the partition information in the phone.
Tried different versions of Odin?
audit13 said:
Don't use kies, user smart switch.
Did you try flashing without the pit? The pit file is needed if Odin doesn't recognise the partition information in the phone.
Tried different versions of Odin?
Click to expand...
Click to collapse
thanks for the fast anwser
i used the pit file which is for my phone and my country. I used the odin version 3.12.3 , odin 3.09 and the first odin version 1.85 and no version worked for me. i also used every usb port on my pc and 3 different usb cables
Does flashing work without the pit file?
audit13 said:
Does flashing work without the pit file?
Click to expand...
Click to collapse
flashing a firmware without a pit file doesnt work
i can flash nothing on my phone i tried almost everything but maybe there is some solution out there.
i'm thinking about changing the motherboard of my phone because i think that there is the internal memory and if i change it would be like a new phone. would that work?