Hi Everyone!
Can anyone helpe me with following trouble? I have a SM-9005 Dubai version.
I tried to flash lolipop 5.0 rom to my device via odin. but when installing system it said fails, even if i tried that several times the result is same. I used Odin 3.09 and then tried V1.85 after reading some suggestions for another guy in similiar situation. But unfortunately didn't help my case. on the device screen i see 3 lines of red messages saying :
UDC start
Volume size is too big 4620288<4718592
ODIN: Invalid ext4 image
and Odin messages:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I don't know what to do. Please help.
BR
FIRAT
is it locked to carrier?
When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?
fuel3100 said:
is it locked to carrier?
Click to expand...
Click to collapse
Hi, no, It was sim free. Any sim could use.
speedyjay said:
When it fails on NAND write that shouldn't brick your phone because nothing on the device has been written by Odin. Is your device still working or are you just wondering how to flash Lollipop?
Click to expand...
Click to collapse
But when i switch on the device i always use the same screen. I can't do anything. Recover mode doesn't work too.
Well, i would like to flasg lolipop but sure my priority is to save the phone first. Then i can think about rom version.
So, what do you think about it ?
Related
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration
Hi,
I'm trying to flash the new lollipop rom which I've downloaded from sammobile. However, Odin keeps on giving me this error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me with this?
Thanks
version
Which version you are using for Odin?
I tried 3.07 and 3.09
The same problem for both!
I downloaded two different roms
Same problem for both..
xhamadeex said:
I tried 3.07 and 3.09
The same problem for both!
I downloaded two different roms
Same problem for both..
Click to expand...
Click to collapse
I noticed that when i enter download mod on my phone, there is "Write Protection: ENABLE" option. I saw the tutorial video and the phone in the video does not have that option!
any ideas?
xhamadeex said:
I noticed that when i enter download mod on my phone, there is "Write Protection: ENABLE" option. I saw the tutorial video and the phone in the video does not have that option!
any ideas?
Click to expand...
Click to collapse
Not sure what is that for but it's not the root cause for the flashing error
Been doing alot of reading across the forum and alot of google'ing. Need some help. Was running a rooted version of lollipop and reflashed a stock version ( so i thought). Now im stuck in recovery mode. Formated system memory and cache. no luck. Odin always fails on the auth. Can't find any solutions that work for me!! Need help badly as this is my only phone. I've tried different versions of ODIN, different usb ports and different usb cables. Also tried reinstalling drivers.
I've read somewhere that you can't downgrade from the newest version of lollipop. Is there any way I can just get my phone to working again? I can access recovery mode or download mode, whichever is needed. Any help is greatly appreciated!!
I finally got it to flash stock kernels, but don't know where to go from here. After flashing kernels and formatting it still doesn't boot.
Bump. I also get error 7 when installing from sd card.
Installing from sd card:
error in sideload package.zip status 7
odin error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I'm thinking it could be the partition table?.. If anyone could link me to a pit file or guide to create my own.
Hi,
OK guys, I'm really stuck here so any help would be very much appreciated.
I have Galaxy S5 SM-G900F phone.
My current status is pretty much described in the title...
Trying to boot puts me in a boot loop with Warranty Bit: kernel or Warranty bit: recovery (depends if the last thing I flashed was root or recovery - both succeed with Odin)
Trying to enter recovery mode I get Warranty Bit: recovery.
When I try Odin to flash a stock ROM get this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOI4_G900FOJK1BOI1_G900FXXU1BOI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
At this stage I'm pretty desperate. I don't care which ROM or if I'm rooted or nor. Just need something working on my phone.
Help!!
Thanks.
basgruv said:
Hi,
OK guys, I'm really stuck here so any help would be very much appreciated.
I have Galaxy S5 SM-G900F phone.
My current status is pretty much described in the title...
Trying to boot puts me in a boot loop with Warranty Bit: kernel or Warranty bit: recovery (depends if the last thing I flashed was root or recovery - both succeed with Odin)
Trying to enter recovery mode I get Warranty Bit: recovery.
When I try Odin to flash a stock ROM get this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOI4_G900FOJK1BOI1_G900FXXU1BOI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
At this stage I'm pretty desperate. I don't care which ROM or if I'm rooted or nor. Just need something working on my phone.
Help!!
Thanks.
Click to expand...
Click to collapse
Thanks for using XDA Assist.Thread will be moved to Galaxy S 5 Q&A, Help & Troubleshooting.You'll get better support there
__
v7
XDA Assist
You can flash just the recovery using odin and see if it works out
basgruv said:
Hi,
OK guys, I'm really stuck here so any help would be very much appreciated.
I have Galaxy S5 SM-G900F phone.
My current status is pretty much described in the title...
Trying to boot puts me in a boot loop with Warranty Bit: kernel or Warranty bit: recovery (depends if the last thing I flashed was root or recovery - both succeed with Odin)
Trying to enter recovery mode I get Warranty Bit: recovery.
When I try Odin to flash a stock ROM get this:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOI4_G900FOJK1BOI1_G900FXXU1BOI4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
At this stage I'm pretty desperate. I don't care which ROM or if I'm rooted or nor. Just need something working on my phone.
Help!!
Thanks.
Click to expand...
Click to collapse
androidtweaker1 said:
You can flash just the recovery using odin and see if it works out
Click to expand...
Click to collapse
Tried it. didn't change a thing.
But it doesn't matter because i was wrong about the model (came in a 900F box but was actually a 9006V).
Once I tried flashing to correct ROM for my version everything was OK.
Thanks everyone...
Hi, my problem is I followed this post and installed CM 13 on the phone (Samsung Galaxy S4 SM-S975L(AT+T Refurb on Straight Talk)) and most of it works, but the calling/ texting/ data doesn't and I noticed the model number in >settings/ about phone now reads SGH-M919. any assistance to get call/ text/ data back would be appreciated.
Does the phone display the correct IMEI when you dial *#06#?
Did you try flashing a stock ROM with Odin: https://www.sammobile.com/firmwares/database/SM-S975L/ ?
audit13 said:
Does the phone display the correct IMEI when you dial *#06#?
Did you try flashing a stock ROM with Odin: https://www.sammobile.com/firmwares/database/SM-S975L/ ?
Click to expand...
Click to collapse
I appologise for the time it took me to reply, and thank you for the snappy one.
Yes the IMEI matches, and I have been trying to flash the stock rom for the past three days, it always fails though.
Boot into download mode and confirm that the model # is SM-S975L or m919.
What error are you getting in Odin? Posting the Odin log can sometimes help find a solution.
audit13 said:
Boot into download mode and confirm that the model # is SM-S975L or m919.
What error are you getting in Odin? Posting the Odin log can sometimes help find a solution.
Click to expand...
Click to collapse
Download mode says SM-S975L, that's how I found out the OS was wrong.
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S975LUDUANB1_S975LTFNANB1_S975LUDUANB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl3.mbn
<ID:0/007> rpm.mbn
<ID:0/007> aboot.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I don't actually know if it has a Log dump, but this what the readout says when I run v3.7
Are you using the original Samsung USB cable on a USB 2.0 port?
Odin is not flashing aboot.mbn because the file doesn't match the phone.