I used Odin 3.10.7 and the file T535XXU1BQC1_T535DBT1BQD1_T535XXU1BQC1_HOME.tar.md5. When the process progresses to the end I'll get an error and everything does not work anymore.
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> 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> 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)
[/code}
That is from Odin.
Can someone help me here? MAybe there is a partition too small??? I got this thing gifted with a very buggy rooted Firmware. Which I wnated to get rid of.
Tried it again and now I get on the screen of the 535 the followinf error.
UDC Start
Volume SIze is too big 40960 < 307200
ODIN Invalid ext4 mage
Try with another firmware version, or use PIT file too
Where do I get a PIT file and another Firmware?
Drake008 said:
Where do I get a PIT file and another Firmware?
Click to expand...
Click to collapse
Try before with pit file. Use frija to download the firmware and pit. https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
Then, when you open that program, go in the 3 dots, and go to settings and there you should find an option to download pit file too. I don't remember how it's called, unfortunately. But you should find that. At the end, you will get the firmware splitted likely in 3-4 pieces with pit.
Found a newer one. Now it works. Thanks for the hint to search for a new one.
Related
Hi, i didn't have enough patience for the BTU 4.4.2 soft and tried to install the NEE version but at the end of the update i got this:
<ID:0/005> Added!!<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNB9_I9505NEEFNB2_I9505XXUFNB9_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> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> NON-HLOS.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Click to expand...
Click to collapse
Then i tried to install DBT 4.4.2 and got stuck with this:
<ID:0/005> Added!!<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNB8_I9505OXAFNB8_I9505XXUFNB8_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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> sbl2.mbn
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Click to expand...
Click to collapse
What should i do next except going to service?
THX in advance
grofudaniel said:
Hi, i didn't have enough patience for the BTU 4.4.2 soft and tried to install the NEE version but at the end of the update i got this:
Then i tried to install DBT 4.4.2 and got stuck with this:
What should i do next except going to service?
THX in advance
Click to expand...
Click to collapse
How did you start your phone in download mode? Via power menu or did you hold volume down and power button?
Very important is:
use only the two button combo.
In Odin untick autoreboot.
Start windows task manager and stop all Kies processes.
Use only the original Samsung USB cable.
If all that not works try another USB port.
And do not remove your phone from PC before Odin says PASS.
When Odin shows pass, remove the phone and hold the power button until it reboots.
I tried different ports with different softs and different data cables but no results.
Instead, i tried install nee from my laptop and it worked from the first time.
So, i supose it's from my pc's drivers.
Hi,
I've been trying to install the 5.0 update on my G900F S5 using firmware files from sammobile according to my region but Odin fails (trace bellow). Did anybody manage to get over this? I've seen people saying that this requires using a PIT file in order to perform a repartition while others argue against it. I would greatly appreciate any help.
Later edit:
The issue was that I've used a different carrier's firmware (I've used Romania Cosmote firmware instead of the unbranded version as it was not available at the time), thus having an incorrect partition table. Looks like using firmware from another region (even carrier) can require changing the partition table (using an appropriate PIT file). This might be helpfull for other people in the same situation.
<ID:0/005> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL9_G900FVFG1BNL1_G900FXXU1BNL9_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> 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! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Hi,
I'm in the UK and have a Note 3 (SM-N9005) and as there is no BTU 5.0 ROM yet I was looking to move to a ROM from my carrier (Vodafone), without ROOT or tripping KNOX etc. This doesn't appear to be a straight forward flash with ODIN. Has anyone had success with this? I've tried the N9005XXUGBOA5/N9005VFGGBOA2 but it appears to fail at the end of the process.
Any advice or help?
Kind regards
SONiKz
The Log for ODIN 3.10.6:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOD6_N9005VFGGBOD2_N9005XXUGBOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> 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)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
sonikz said:
The Log for ODIN 3.10.6:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOD6_N9005VFGGBOD2_N9005XXUGBOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<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> 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)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You are trying to do a stupid thing. Why you are flashing branded firmware for one device that is unlocked? Try other unlocked firmware if you wish Lollipop (For example: Poland one).
I had the same problem. Its because of size mismatch. I don't remember which ROM I tried to flash and then failed, but its because the ROM is meant for a Note 3 which is not your size, I mean 16 gigs, 32 gigs etc. The ROM which I was able to flash successfully on mine was Polish one I think. So you need to know which ROM are meant for 32 gigs, and which are for 16 gigs. It's not mentioned in sammobile.com, and I don't know where else you could ask/ know that either.
Yeah, I'm not sure how to easily identify the ROM size. I assume that it may have something to do with PIT files/Paritioning. But I don't think there is a real resource for PIT's. In the event anyone has a Vodafone 32GB Note 3 I could do with a copy of one(assuming they're not device specific).
-SONiKz
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^^
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?