I've been trying to flash Marshmallow on my BTU G900F, but it won't actually flash the bootloader. Odin reports successful but bootloader is still the old version and MM won't boot. Any suggestions? So far I've tried a few versions of Odin and the Sri Lanka and Netherlands MM roms and with/without ticking bootloader update in Odin.
Odin log:
Code:
<ID:0/003> 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..
<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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> rpm.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> tz.mbn
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> NON-HLOS.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Put the phone off, or remove the battery from it for about 15 seconds.
And boot directly to download mode. And oh, you should flash bootloaders along with modems!
Hope this helps.
Happy flashing
Are you flashing the modded BTU MM ROM?
This one works for my G900F BTU
Code:
https://mega.nz/#!SMRlERrY!oeOX8W_4tbQbArTN-LzTKWJ1xi_8LLrN_ZoSg-Dzs1Q
Greatness_GH said:
Put the phone off, or remove the battery from it for about 15 seconds.
And boot directly to download mode. And oh, you should flash bootloaders along with modems!
Hope this helps.
Happy flashing
Click to expand...
Click to collapse
I'll give that a try tomorrow. I'm flashing both. Forgot to say, I've even factory reset and flashed the whole stock rom and it still wouldn't update it.
*Detection* said:
Are you flashing the modded BTU MM ROM?
This one works for my G900F BTU
Code:
https://mega.nz/#!SMRlERrY!oeOX8W_4tbQbArTN-LzTKWJ1xi_8LLrN_ZoSg-Dzs1Q
Click to expand...
Click to collapse
Thanks, if the above fails, I'll try that.
No need to flash separate bootloaders and modems with the modded one
It is a stock G900F Marshmallow ROM, the only mod is to convert it to BTU and remove a partition that wiped the phone during install
Hey i want help i have galaxy s5 sm-g900f and m still on lolipop i want to manually install marshmallow but my device is by three.co.uk career can u send me a appropriate link plzzzzz...
Thnks in advance !!!
Harsh_singh said:
Hey i want help i have galaxy s5 sm-g900f and m still on lolipop i want to manually install marshmallow but my device is by three.co.uk career can u send me a appropriate link plzzzzz...
Thnks in advance !!!
Click to expand...
Click to collapse
BTU should work fine with Three
Help
*Detection* said:
BTU should work fine with Three
Click to expand...
Click to collapse
I checked on sammobile, g900f btu doesn't get a marshmallow update yet???
Harsh_singh said:
I checked on sammobile, g900f btu doesn't get a marshmallow update yet������
Click to expand...
Click to collapse
Figured that my device is h3g and there is no update available by three yet so i think i will wait for official firmware to be aired but thats for ur concern
Harsh_singh said:
I checked on sammobile, g900f btu doesn't get a marshmallow update yet������
Click to expand...
Click to collapse
G900F 6.0.1 Stock (Just modded to change the region to BTU)
Code:
https://mega.nz/#!SMRlERrY!oeOX8W_4tbQbArTN-LzTKWJ1xi_8LLrN_ZoSg-Dzs1Q
Will trip KNOX
Greatness_GH said:
Put the phone off, or remove the battery from it for about 15 seconds.
And boot directly to download mode. And oh, you should flash bootloaders along with modems!
Hope this helps.
Happy flashing
Click to expand...
Click to collapse
Thanks, that worked And it seems it failing to boot was caused by using system-mode supersu
NHellFire said:
Thanks, that worked And it seems it failing to boot was caused by using system-mode supersu
Click to expand...
Click to collapse
Great! I'm glad it worked. Welcome back
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 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.
i have make downgrade form 4.4.2 to 4.2.2 i9500
and it's working fine
but i need flash this rom [ I9500XXUBMG9_I9500OJVBMG9_LYS.zip ]
it's show massage on phone
SW REV Invalid Magic Strings
and on odin
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md 5 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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
note [ i check icon for knox on phone it's removed after downgrade ]
i use this rom for downgrade [ XFE-I9500XXUBMH1-20130927115211.zip ]
same problem with me.. any help guys?
EgyMan said:
i have make downgrade form 4.4.2 to 4.2.2 i9500
and it's working fine
but i need flash this rom [ I9500XXUBMG9_I9500OJVBMG9_LYS.zip ]
it's show massage on phone
SW REV Invalid Magic Strings
and on odin
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md 5 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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
note [ i check icon for knox on phone it's removed after downgrade ]
i use this rom for downgrade [ XFE-I9500XXUBMH1-20130927115211.zip ]
Click to expand...
Click to collapse
i have the same case my phone is hang up on logo and cant flash with any firmware its i9500
EgyMan said:
i have make downgrade form 4.4.2 to 4.2.2 i9500
and it's working fine
but i need flash this rom [ I9500XXUBMG9_I9500OJVBMG9_LYS.zip ]
it's show massage on phone
SW REV Invalid Magic Strings
and on odin
note [ i check icon for knox on phone it's removed after downgrade ]
i use this rom for downgrade [ XFE-I9500XXUBMH1-20130927115211.zip ]
Click to expand...
Click to collapse
vbfather said:
same problem with me.. any help guys?
Click to expand...
Click to collapse
alialjorany said:
i have the same case my phone is hang up on logo and cant flash with any firmware its i9500
Click to expand...
Click to collapse
Hi mates ,
If you have a 4.4.2 bootloader you can not flash ( odin) any firmware with a bootloader older that that. You can only flash (odin) firmware with the same bootloader or newer. This apply to stock firmware not custom firmwares as they do not have bootloaders
@alialjorany can you get into download mode? flash firmware again
Finally some hope!
MAX 404 said:
Hi mates ,
If you have a 4.4.2 bootloader you can not flash ( odin) any firmware with a bootloader older that that. You can only flash (odin) firmware with the same bootloader or newer. This apply to stock firmware not custom firmwares as they do not have bootloaders
@alialjorany can you get into download mode? flash firmware again
Click to expand...
Click to collapse
Sounds like you know what you're talking about, so could you clarify how and what files we would need to flash firmware via download mode instead of Odin.
Thanks!
fperezlopez said:
Sounds like you know what you're talking about, so could you clarify how and what files we would need to flash firmware via download mode instead of Odin.
Thanks!
Click to expand...
Click to collapse
look at google page for more infotmation check this:
fperezlopez said:
Sounds like you know what you're talking about, so could you clarify how and what files we would need to flash firmware via download mode instead of Odin.
Thanks!
Click to expand...
Click to collapse
Hi
You can only flash custom rom with custom recoveries , stock firmware only with odin
can i downgrade bootloader to 4.2.2?
vbfather said:
can i downgrade bootloader to 4.2.2?
Click to expand...
Click to collapse
Hi,
No you can not , Odin will not let you flash an older bootloader than the one you have
vbfather said:
can i downgrade bootloader to 4.2.2?
Click to expand...
Click to collapse
Never try doing that again or else you shall have a $450 brick :/
If youre on 4.3, flash 4.3 or higher
If youre on 4.4.2 flash 4.4.2 or higher
If youre on 4.2.2 flash 4.3 or 4.4.2 but remember there is no way back..
Press Thanks if I helped
Sent from my Samsung Galaxy S4 via XDA app.
thnx guys, i just downgrade my 4.4.2 i9500 to 4.2.2 using this file "I9500XXUBMH1_I9500OJVBMH2_I9500XXUBMG9_HOME.tar.md5"
but i failed to flash it with other 4.2.2 versions, and i later known that its because "I9500XXUBMH1" has same bootloader of 4.4.2. so any idea?
here in turkey we have problem with repair imei at 4.4.2
thanks in advance
How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM
Thanks
Just fixed my baby s6
I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Reflash with stock 5.1.1 via odin.
ROMs for G920F:
http://www.sammobile.com/firmwares/database/SM-G920F/
Is there a 920T version of this?
Here you go:
http://www.sammobile.com/firmwares/database/SM-G920T/
G920I version?
Is there a 920I version as well?
Found it.
http://www.sammobile.com/firmwares/database/SM-G920I/
Criticalstriker said:
I get error..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:
gamekill said:
>>>>>>>>>>>>>First of all thank you very much to the OP!! <<<<<<<<<<<<<<<
I got the same error and solved it.
I think the reason was that I tried flashing a 502 stock when I had already flashed the 511 bootloader and modem. In my case I have a Brazilian SM-G920I GS6 and the 511 stock rom is/was not readily available for it. So I tried downloading the latest available official stock version (502) and it resulted in the error you mentioned.
So I dowloaded the India 511 version (region INU) for 920I and it finally worked.
I used samfirm to download it (http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647).
You need to input the exact model name (for me it was literally SM-G920I) and the region code for your phone. Then download it, DON'T close samfirm software, then click on Decrypt and you will finally have a ZIP from which you can extract the stock rom. And to find out your region code, you can go to www.sammobile.com and click on Firmware in the main menu at the top. Then you enter the model number and after that you will get to a screen with a dropdown menu for all available regions and their codes (for instance, region codes for Brazil are ZTO, ZTA..).
You can also download the stock roms from sammobile diretcly but it is too slow (takes a day or so).
Good luck!
:fingers-crossed:
Click to expand...
Click to collapse
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade
andifds said:
Ok, now I'm stuck.
I've downloaded the same version as you (INU 5.1.1 for G920I) and flashed. Used for some days and now I have to take my SGS6 to service to check if they can give me a new one because I´m having some trouble with the radio of my network (the problm was before flashing any ROM). Any way, I've tried to flash stock 5.0.2 and Odin still giving the same error. In my case I tried many of 5.0.2 stocks ROMs for the G920I and none of them worked, even the stock from Claro (my carrier) doesn't work.
This is the log in Odin, after reflashing INU 5.1.1, wiping and apply download mode.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920IDVU1AOD1_G920IUWA1AOD6_G920IDVU1AOD1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1005)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what to do. I can't downgrade
Click to expand...
Click to collapse
It's not possible to downgrade to 5.0.1 if your bootloader is on 5.1.1.
Downloading now. So like all the other Odin roms it passed but does it pass in download mode on the phone that then blocks the download ?
hello!
This works on any 5.1.1?
i mean can i download any 5.1.1. for 920F and it will be fixed or i have to use exactly the rom that is posted on OP?
Once in download mode flash the latest TWRP 2.8.7.1
[url said:
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570[/url]
After flashed you'll be able to boot into recovery and flash your custom ROM [/COLOR][/SIZE]
[/CENTER]
Click to expand...
Click to collapse
hi! can someone help me to flash this recovery.img ?
thanxx in advance.
Thank you so much for this topic, Rossyyy! :good::good::good::good::good::good::good:!!!!!!!!!
Edit; The only thing is that i still get a message (top left) in really small red letters every time i boot. For a few seconds and than boot proceeds by itself....
Rossyyy said:
How to fix system rev. check fail device: 2 binary 1 error when flashing a custom 5.1.1 ROM
If this error has appeared after flashing the new Bootloader and Modem for BOFJ
Download this: https://mega.co.nz/#!E05hTYaS!_vad3fvvKCwWiMmgWGrGgc69KYdgYRa1wFCmxYzwH3s
(Stock 5.1.1)
Once installed and passed with ODIN (Flash as AP)
Power off the phone and boot into download mode
Once in download mode flash the latest TWRP 2.8.7.1
http://forum.xda-developers.com/showpost.php?p=61548356&postcount=570
After flashed you'll be able to boot into recovery and flash your custom ROM
Click to expand...
Click to collapse
Hey, once I am facing the "system rev. check fail device: 2 binary 1 error", I don't think I can power off the phone completely. I can just reboot the phone into the download mode. If I try to reboot into recovery it will say "recovery is not seandroid enforcing"...
How do I power off the phone completely or how do I reboot into recovery?
aeroxy said:
How do I power off the phone completely or how do I reboot into recovery?
Click to expand...
Click to collapse
Volume up, home and power button.
richajax said:
Volume up, home and power button.
Click to expand...
Click to collapse
Oh yes, I have tried this. It will reboot and says "recovery is not seandroid enforcing"...
I think you will find your answer in one of these topics?
http://forum.xda-developers.com/search.php?searchid=379334690
Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE
brettule said:
Thanks, fixed the soft brick on my 920i. Used the Indian 5.1.1 version but it takes an age to download. Here is an alternate link.
https://mega.co.nz/#!VZcARCrC!-Zj8gwLGkqmlEnSBemyfqsTrr4C_ilf3koUOS6_w2pE
Click to expand...
Click to collapse
Thanks for the link. I panicked when this happened, glad i was able to find this topic through google
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
Okay, so it failed. Now what?
I'm starting to panic lol.
<OSM> Please wait..
<OSM> G920IDVU2COF8_G920IODD2COF8_G920IDVU2COF8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Can't open the specified file. (Line: 2012)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
**EDIT**
for anyone else that may ever encounter this.. .make sure your "re-partition" option is unchecked in odin.
Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!
If you can access download mode, your phone is not bricked.
Simply download last firmware for your model from sammobile, and flash it with odin...
ok thanks, will do.
But how do I safely root the note 4 5.1.1? CF-Autoroot isnt compatible
Ok, I just finished download a stock rom for my phone (.tar.zip) but when I click start in Odin it always fails for some reason...<ID:0/003> Can't open the serial(COM) port.
Edit: tried a different port now it fails at:
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
What can I do?
Does upgrading via Kies will result in losing all data?
I'm working on this issue for hours now but I'm stuck
Using Odin it will fail at sboot.bin
And kies doesnt recognize my note 4
Here's the log:
<ID:0/003> 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/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone: SW REV. CHECK FAIL, DEVICE 2, BINARY 1
Nixdax said:
Hey guys,
i tried to flash my note 4 using the openrecovery method
but i forgot to flash the kernel and now my phone is stuck in the booting at the Samsung symbol. Can someone please help? i can still get into the download mode
Thank you!!!
Click to expand...
Click to collapse
Restore your backup in recovery
What is your exact model, G or F, what? You download the ROM from sammobile with your exact model no., and then flash.
It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........
Never heard about the H version before! Anyway, make sure you are flashing the correct Xposed, that is Wanam's, but Arter's, and read the installation instructions closely.
Nixdax said:
It's N910H
I resolved it by recovering my phone via Kies though I lost all my data
Then I tried to install Xposed framework and now it's stuck in the bootloop again ...........
Click to expand...
Click to collapse
Please, search before flash.
H model is with Exynos processor.
http://www.sammobile.com/firmwares/database/SM-N910H/