Hi there,
Originally submitted to the note 4 section and realised it may not be quite as active and probably posted in the wrong place, I do apologise for that.
First off, I messed up. I've root my android phones over the years now and it came to the point I wanted to unroot my note 4 and get it back to stock.
This time I forgot to enable usb debugging before flashing to stock
So I can get into download mode, but not recovery mode. If I try to enter recovery mode I get the "firware upgrade issue, connect to kies" message. Trying to flash with odin fails, with multiple firmwares (5.0.1 and 5.1.1) and with my pit file, and trying different usb ports.
I've been googling for 4 hours now, I know how annoying it is for same old threads to be brought up, but nothing has helped me get to the bottom of it.
If someone could go through what I need to do step by step it would be much appreciated. Pretty sure there's a way of sorting it since I can at least access download mode, but I also know it may well be completely messed up.
Many thanks chaps.
Alright guys, looks like I've fixed it. So this is for anyone that stumbles across this thread with the same issue.
So after trying to install stock firmware from Samsung (I also used the pit file for my phone, don't think this is necessary though), and odin failing to flash it (I'll paste the odin log at the bottom of this post), I used "All samsung recovery" that I downloaded from here. http://www.4shared.com/file/bIYubEevba/All_samsung_recovery.html
Using odin v3.09, make sure your phone is in download mode and connect to the PC. Odin should recognise it's detected with a blue box.
Click AP (or PDA in earlier versions I believe) and select the All_Samsung_Recovery.tar zip file downloaded from the link above.
Might take a second to load into odin, it's not crashed be patient. And then click start.
Took my phone about 10 seconds and it was all done, just booted straight into the OS I originally tried to flash, so obviously it didn't fail like odin said.
Ok, so hopefully this will help someone. Let me know if I missed any information that I should add.
Here is the odin log when trying to flash the stock firmware originally:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COI3_N910FEVR1COJ1_N910FXXU1COI3_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Related
hi there i have a live demo unit set with snapdragon chipset i updated my bootloader which i cant downgrade and now i am getting bootloop so i flashed some 4.4.2 rom which didnt worked though and now i am going back to stock rom N9005XXUGNG1_N9005DBTGNG1_DBT [Germany] using odin and it gives me error
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Help me what should i do and when i install twrp and clear cache i manage to boot somehow but i keep giving me error samsung keyboards stops working
or you root, install recovery and flash custom rom
or you do odin again and maybe change version 3.09 or older
or you root, install recovery and flash custom rom
or you do odin again and maybe change version 3.09 or older
Click to expand...
Click to collapse
tried changing odin version 3.07 still the same
now dowloading poland stock rom
is there any way to fix samsung keyboard has stopped workig every 2 sec
cybertron_001 said:
tried changing odin version 3.07 still the same
now dowloading poland stock rom
is there any way to fix samsung keyboard has stopped workig every 2 sec
Click to expand...
Click to collapse
Try this
http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
I had some issues in the past with kitkat and flashing roms so i ran across this. It helped me.
Hi, I'm looking for the Stock Rom for Note 3 SM-N9005 Stock Rom 4.4.2 KitKat for my father, because he wants Bluetooth.
I already found N9005-DBT-NG1-201408 from samsung-updates.com
But if I use Odin 3.09 to flash the .tar.md5 file, I got an error: Invalid ext4 Image
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I do not know what problem causes it or how to solve it, but really I just want one Stock-ROM I can install so I download now:
/download/n9005xxugni4-aut-4-4-2-switzerland/ from samdownloads.de (2hrs download time)
and
/Galaxy_Note_3_Snapdragon/SM-N9005/XSI/N9005XXUGNJ2.html from samsung-updates.com (4hrs download time)
So what I want to know, is one of these the right stockrom for Note 3 SM-N9005 (in Austria)? If not, can you point me to the right one?
Or is it possible to fix Bluetooth in 5.0?
Its just very frustrating to wait so long, to find out I was downloading the wrong Rom -.-
I hope I did everything with asking the question and I'm in the right subforum.
Also I can't provide links yet, so if you want to check them out, please google it.
Oh yeah, I can install from Recovery too...
UPDATE:
I installed cwm-recovery-6.0.4.7-kk and that rooted the phone and now it works. (Just needed a new tastatur and sometimes error messages come along, with the google apps crashing)
I will install the other roms, since the crashing part is annoing. (flashing gapps should work to)
norax1 said:
Hi, I'm looking for the Stock Rom for Note 3 SM-N9005 Stock Rom 4.4.2 KitKat for my father, because he wants Bluetooth.
I already found N9005-DBT-NG1-201408 from samsung-updates.com
But if I use Odin 3.09 to flash the .tar.md5 file, I got an error: Invalid ext4 Image
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005DBTGNG1_N9005XXUGNG1_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I do not know what problem causes it or how to solve it, but really I just want one Stock-ROM I can install so I download now:
/download/n9005xxugni4-aut-4-4-2-switzerland/ from samdownloads.de (2hrs download time)
and
/Galaxy_Note_3_Snapdragon/SM-N9005/XSI/N9005XXUGNJ2.html from samsung-updates.com (4hrs download time)
So what I want to know, is one of these the right stockrom for Note 3 SM-N9005 (in Austria)? If not, can you point me to the right one?
Or is it possible to fix Bluetooth in 5.0?
Its just very frustrating to wait so long, to find out I was downloading the wrong Rom -.-
I hope I did everything with asking the question and I'm in the right subforum.
Also I can't provide links yet, so if you want to check them out, please google it.
Oh yeah, I can install from Recovery too...
UPDATE:
I installed cwm-recovery-6.0.4.7-kk and that rooted the phone and now it works. (Just needed a new tastatur and sometimes error messages come along, with the google apps crashing)
I will install the other roms, since the crashing part is annoing. (flashing gapps should work to)
Click to expand...
Click to collapse
Seriously. What a mess.
Dont touch your phone if you dont even know sammobile for stock firmwares. Dont dowload from those crap sites.
Yeah, but
Not my Phone^^
Used another rom and everything is fine now^^
1. &2. are enough^^
But yeah thank you for the tip^^
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
UDC Start
ERASING USERDATA PARTITION..
ODIN : invalid ext4 image
Click to expand...
Click to collapse
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
mp3geek said:
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
Click to expand...
Click to collapse
Are you using a branded phone (vodafone) or unlocked one? Coz, i think, you are flashing wrong firmware for your device.
Its an unlocked N9005 (LTE)
As far as I know the ROMs which are for 16 gigs devices won't get flashed on 32 gigs devices and vice versa, so you probably need to find a ROM which will match your device's size.
This is a 32G device
The Roms I've attempted (and failed) to flash:
N9005XXUEND3_N9005VNZENC1_N9005XXUENC2_HOME.tar.md5
N9005XXUGNG1_N9005VNZGNG1_N9005XXUGNG1_HOME.tar.md5
N9005XXUGNG1_N9005XSAGNG1_N9005XXUGNG1_HOME.tar.md5
N9005XXUEND3_N9005NZCENF2_N9005XXUENC2_HOME.tar.md5
N9005XXUGNK1_N9005VAUGNK1_N9005XXUGNK1_HOME.tar.md5
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there a ROM (any) that I can I can flash via ODIN which includes a bootloader such as CMW? If I install CMW by itself, it'll be successful. But It'll go through a boot loop.
Maybe a screwed up the bootloader of the SM-9005?
Try a newer base, those are really old ones! Try OF3! Can't say of which country, as I don't know which are for which sized devices! I am not sure at all, but I think ROMs for UK devices are pretty popular, so I guess those might work.
You can simply flash the deodexed OF3 which comes as a zip package from here, http://forum.xda-developers.com/galaxy-note-3/development/rom-qs-n9005-lp-t3037655
It's basically a stock ROM with few added features and deodexed. If you don't want deodexed then you can try flashing a pre made ROM from alexandar's topic, it's same as stock ROM with even less features from the previously mentioned one. I am suggesting you these because it's better to flash a ROM which will work straight after download rather than trial and error method of sammobile ROMs.
I don't think you can flash "QS-N9005-LP-FINAL-OH3.zip" in ODIN, doesn't show up
mp3geek said:
Help!
I attempted to follow through with this: http://www.cultofandroid.com/53963/save-galaxy-note-3-failed-kitkat-update-odin-tip/
But its failing currently:
I've tried 3 different images (I'm NZ based), tried 2 different pit files also. I don't know what do to do next, since it keeps failing the same error message.
Click to expand...
Click to collapse
Rename .tar.md5 rom in .zip and extract all images from it.Delete hidden.img file then compress everything with forum.xda-developers.com/showthread.php?t=2446269 then flash every tar separatly.
mp3geek said:
I don't think you can flash "QS-N9005-LP-FINAL-OH3.zip" in ODIN, doesn't show up
Click to expand...
Click to collapse
Course you can't! You need to flash it from a custom recovery, TWRP for example.
Argh still not wanting to do it I thought grabbing N9005ZSUGOH3_N9005OZSGOH3_N9005ZSUGOH3_HOME.tar.md5 (matching the other 2 versions) would maybe help
Code:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> rpm.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> sdi.mbn
<ID:0/005> tz.mbn
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Should I touch any additonal ODIN options such as Phone EFS Clear, or Phone Bootloader Update, or Nand Erase All?
You don't need to touch anything. I always flash only the PDA (AP), that's enough! Don't know what's going on here, but I am pretty sure it is because of the size issue.
Actually I got a new error message "Volume Size is too big 614400 < 712704
(Note this a 32GB) What should I do to get space? I happy to wipe the internal storage at this stage, just not sure how
Both up volume and down volume (with power/menu give me ODIN modes currently), a bit slight different
Down volume goes into download mode (Odin mode), and up volume goes to recovery mode. Both are quite different actually.
If you are willing to do a wipe then do it properly. Flash the custom recovery first, TWRP. Then go to Advanced Wipe and wipe everything (except external SD), but BEWARE, this will wipe EVERYTHING. You won't even have any ROM installed. So until you plan to flash a ROM basically you will have a brick. Do take backup of your needed stuffs before wiping, photos, musics etc. in your PC and use Titanium for apps' backup if you will so.
Then try to flash through Odin again (have you found same country's firmware matching your device? I mean I have a device which was assembled in UAE, so all the UAE ROMs work, so check that). If Odin still fails, then have that zip ROM (OF3) downloaded beforehand. I am repeating once again, if you do what I said above it will erase everything from your phone, so please be informed about that before proceeding further.
I flashed twrp-2.8.7.0-hlte-4.4.img.tar, which according to ODIN, it was successful. but when I reboot (volume up/menu/power). Says "Recovery is booting.." but shows nothing.
Okay, got in into it.
Advanced Wipe? Tick everything in TWM? and Format data?
Thanks heaps for the support
Weird! Take the battery out for 10 seconds, re-insert, then press Volume Up and Power only simultaneously (No need to press Menu), it should boot right into TWRP.
Sent from my SM-N9005 using Tapatalk
Hi there,
First off, I messed up. I've root my android phones over the years now and it came to the point I wanted to unroot my note 4 and get it back to stock.
This time I forgot to enable usb debugging before flashing to stock :crying:
So I can get into download mode, but not recovery mode. If I try to enter recovery mode I get the "firware upgrade issue, connect to kies" message. Trying to flash with odin fails, with multiple firmwares (5.0.1 and 5.1.1) and with my pit file, and trying different usb ports.
I've been googling for 4 hours now, I know how annoying it is for same old threads to be brought up, but nothing has helped me get to the bottom of it.
If someone could go through what I need to do step by step it would be much appreciated. Pretty sure there's a way of sorting it since I can at least access download mode, but I also know it may well be completely messed up.
Many thanks chaps.
Alright guys, looks like I've fixed it. So this is for anyone that stumbles across this thread with the same issue.
So after trying to install stock firmware from Samsung (I also used the pit file for my phone, don't think this is necessary though), and odin failing to flash it (I'll paste the odin log at the bottom of this post), I used "All samsung recovery" that I downloaded from here. http://www.4shared.com/file/bIYubEevba/All_samsung_recovery.html
Using odin v3.09, make sure your phone is in download mode and connect to the PC. Odin should recognise it's detected with a blue box.
Click AP (or PDA in earlier versions I believe) and select the All_Samsung_Recovery.tar zip file downloaded from the link above.
Might take a second to load into odin, it's not crashed be patient. And then click start.
Took my phone about 10 seconds and it was all done, just booted straight into the OS I originally tried to flash, so obviously it didn't fail like odin said.
Ok, so hopefully this will help someone. Let me know if I missed any information that I should add.
Here is the odin log when trying to flash the stock firmware originally:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COI3_N910FEVR1COJ1_N910FXXU1COI3_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
webby93 said:
Alright guys, looks like I've fixed it. So this is for anyone that stumbles across this thread with the same issue.
So after trying to install stock firmware from Samsung (I also used the pit file for my phone, don't think this is necessary though), and odin failing to flash it (I'll paste the odin log at the bottom of this post), I used "All samsung recovery" that I downloaded from here. http://www.4shared.com/file/bIYubEevba/All_samsung_recovery.html
Using odin v3.09, make sure your phone is in download mode and connect to the PC. Odin should recognise it's detected with a blue box.
Click AP (or PDA in earlier versions I believe) and select the All_Samsung_Recovery.tar zip file downloaded from the link above.
Might take a second to load into odin, it's not crashed be patient. And then click start.
Took my phone about 10 seconds and it was all done, just booted straight into the OS I originally tried to flash, so obviously it didn't fail like odin said.
Ok, so hopefully this will help someone. Let me know if I missed any information that I should add.
Here is the odin log when trying to flash the stock firmware originally:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910FXXU1COI3_N910FEVR1COJ1_N910FXXU1COI3_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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Thanks for this same problem but how did u get into download mode?
Hello,
I've been trying to upload the Telus Andorid 6.0.1 to my Samsung S5 and have been unsuccessful. I continually get "Complete(Write) operation failed".
I have tried versions of Odin 3.09, 3.11 and 3.12 to no success.
I have ensured the driver of the S5 is on the computer (Windows 7, latest patches).
I have used multiple cables (OEM) and ports (front and rear).
I am in download mode (power, volume down, and home button).
Finally, Kies has been fully removed.
Here is what I'm trying to install: G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar.md5.
Here is a snapshot of the log.
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1101)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> sbl1.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm doing all of this because my stock phone is bootlooping. I tried a new battery and it did not resolve my issues. Any help would be appreciated as I've searched this site and others for multiple hours and I'm now stuck on the firmware update screen telling me to recover using Kies (not the logo). It automatically starts there.
Thank you.
Hi
You're sure to put the phone in download mode?
grandshervee said:
Hello,
I've been trying to upload the Telus Andorid 6.0.1 to my Samsung S5 and have been unsuccessful. I continually get "Complete(Write) operation failed".
I have tried versions of Odin 3.09, 3.11 and 3.12 to no success.
I have ensured the driver of the S5 is on the computer (Windows 7, latest patches).
I have used multiple cables (OEM) and ports (front and rear).
Finally, Kies has been fully removed.
Here is what I'm trying to install: G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar.md5.
Here is a snapshot of the log.
<ID:0/014> Added!!
<ID:0/014> Odin engine v(ID:3.1101)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> aboot.mbn
<ID:0/014> NAND Write Start!!
<ID:0/014> sbl1.mbn
<ID:0/014> rpm.mbn
<ID:0/014> tz.mbn
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm doing all of this because my stock phone is bootlooping. I tried a new battery and it did not resolve my issues. Any help would be appreciated as I've searched this site and others for multiple hours and I'm not stuck on the firmware update screen (not the logo). It automatically starts there.
Thank you.
Click to expand...
Click to collapse
Sent from my SM-G532F using Tapatalk
merwan said:
Hi
You're sure to put the phone in download mode?
Click to expand...
Click to collapse
Hi, yes I'm in download mode (power, volume down and home button).
Also, I noticed I miswrote something and have corrected it. I meant to write:
I'm NOW stuck on the firmware update screen telling me to recover using Kies (not the logo).
grandshervee said:
Hi, yes I'm in download mode (power, volume down and home button).
Also, I noticed I miswrote something and have corrected it. I meant to write:
I'm NOW stuck on the firmware update screen telling me to recover using Kies (not the logo).
Click to expand...
Click to collapse
Try to redownload the md5 file
Change USB port. And if u another 2.0 cable to. Somwnthing it happend dont worried
I have tried all of these files and get the same error for each. brand new S5 USB 3 cable and different port too.
G900W8VLU1DPD3_G900W8OYA1DPD3_G900W8VLU1DPD3_HOME.tar
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3_HOME.tar - same file as above but from a different download site.
What is the line after:
<ID:0/007> tz.mbn
that causes it to fail?
Don’t use the usb 3 cable, the old HTC and BlackBerry cables are the best as theyre 21 pin connectors. Where are you downloading the tarball from? Sammobile.com/firmwares is the only truly reputable place altho there are many sites that have them as well, but if youre having trouble flashing them, get a tarball from the source directly. I agree with a previous post, try a different port, different cable and fresh download. One of those is bound to work.
Sorry for such a late reply. I am still unsuccessful with the S5. Redownloaded from Sammobile
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3
I loaded a Note 4 with Odin 3.12, a micro-USB cable, and this specific USB port and it woudln't work with the S5. Is it possible that there is internal hardware damage shorting something?
grandshervee said:
Sorry for such a late reply. I am still unsuccessful with the S5. Redownloaded from Sammobile
G900W8VLS1DPF3_G900W8OYA1DPF3_G900W8VLS1DPF3
I loaded a Note 4 with Odin 3.12, a micro-USB cable, and this specific USB port and it woudln't work with the S5. Is it possible that there is internal hardware damage shorting something?
Click to expand...
Click to collapse
i guess its possible, but id try a different odin version before i jumped to that conclusion
Ok, so somehow I got the phone to boot up and go through the setup menus, then it failed.
It then rebooted and displayed
Set Warranty Bit : kernel
I now ran ODIN again.
This was on the phone
Product Name: SM-G900W8
Current Binary: Custom
System Status: Official
Reactivation Lock(KK): OFF
Knox Warranty Void: 0x1 (1)
Qualcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
UDC Start
Secure Check Fail : aboot
and this was the output within odin:
<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/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try with different odin version, like 3.11, also reinstall drivers or flash using another pc
Just rebooted phone and got this.
Recovery Booting.....
Set Warranty Bit : recovery
Also, tried with 3.11, no success. Drivers have been reinstalled twice over.
now it hangs at tz.mbn before failing.
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
grandshervee said:
Just rebooted phone and got this.
Recovery Booting.....
Set Warranty Bit : recovery
Also, tried with 3.11, no success. Drivers have been reinstalled twice over.
now it hangs at tz.mbn before failing.
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
ive had that error a few times before when using the stock samsung cable. do you have another cable? preferably an old school blackberry or htc one. The older cables from those manufacturers seems to have always worked best for me and others