Related
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
vivelafrance said:
Hi guys,
My SGS4 won't boot anymore. At all.
I can (with difficulty) access my custom recovery menu (TWRP 2.5.1) and the download menu.
But whatever I'm trying to flash using ODIN from download menu, it fails! Whether it's the current ROM, official UK BTU ROM, stock recovery etc... So can't use Odin.
Can't put anything on the device either as I can't boot. When I use the "mount USB" from the TWRP menu, my PC doesn't recognize the phone so I can't put any ZIP on the phone that I could install from TWRP.
This happened when I used Triangle Away to reset the counter from 1 to 0....
I'm afraid my phone is bricked (although it's a temp phone and will be getting mine in 2 days), but I wanted to be sure that I didn't forget to do anything....
ANy ideas how to make this work pls?
thnx
Click to expand...
Click to collapse
where odin failed exactly?
did you try changing usb port? kies totally disabled? original usb cable?
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
vivelafrance said:
thnx for your help.
- Kies is definitely not running, stopped all services and processes
- Using samsung USB cable
- Tried on several USB ports of my PC
- Using Odin 3.4
- this is what I can read in ODIN after it has failed:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAMDD_I9505VODAMD9_I9505XXUAMDD_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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Thnx again.
Click to expand...
Click to collapse
one more thing, remove battery for a couple of minutes, then try with odin 1.85
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
vivelafrance said:
All of these were really good ideas, but I'm afraid none of them work!
Same error message, it seems it can't write on the damn phone. I tried to reflash TWRP, the green bar went further but at the end, same thing, fails.
Click to expand...
Click to collapse
i dont know if flashing pit file along with the firmware will work
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
vivelafrance said:
yeah that's exactly what I was thinking, after clickingon your "unroot, back to stock" link in your signature...
So can I flash the firmware + Pit at the same time or should I flash pit first and then the ROM?
Click to expand...
Click to collapse
pit file is flashed with the firmware. choose the right pit for your device! re-partition will be checked automatically when you select the pit file.
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
vivelafrance said:
still doesn't work unfortunately, don't know what 's happening....
I flashed PIT file alone, it worked fine.
Tried to install anything else, it fails again, all the time...
Click to expand...
Click to collapse
did you flash firmware with the pit file at same time and didnt work?
almost you did everything.
try to change computer if available.
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
vivelafrance said:
no I flashed the pit file alone, cause if I flash the pit and PDA at the same time, it doesn't work either:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUAME2-PRE-ROOTED-DEODEX-SUPER-SLIM.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
ok well, thnx anyway for your help
Click to expand...
Click to collapse
If you haw acess t dawnload mod you are nhot bricked pleas go and try other pc
Sent from my GT-I9505 using xda premium
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
this is surely NOT a mobile issue if you can enter into download mode.
i had the exact issue a month ago when i had note2.
if you can't try it on another pc, try :
1) uninstall skies completely
2) unisnstall usb drivers
3) reboot the pc
4) connect your s4 in download mode to your pc.
5) let your pc install freah usb drivers
6) start odin and flash
7) if still you get the same error download a different verison of the official rom and try flashing.
i followed the above procedure couple of times and was finally able to install the rom. the issue is either with the drivers or the rom.
Sent from my GT-I9500 using xda app-developers app
bricked for sure
vivelafrance said:
First, thanks for the info that if I can access the download mode, then the phone is not bricked, I didn't know that, so thanks.
And yes, you were both right, I plugged my phone into my laptop and it worked! THANK YOU.
So the next question is: What could be the issue on my PC? It's not Kies cause it's not installed, and I already uninstalled and reinstalled the Samsung Drivers....
thnx
Click to expand...
Click to collapse
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Bluetoth10 said:
expirienced exactly same situation with i9300. Able to get to recovery but failed to flash. Tryed everything on PC and on the phone itself. You have to try different odin versions, but in my case it was NAND failure. If you failed to flash PIT your phone is for sure bricked. Sorry.
Got mainboard replacement in my case.
Click to expand...
Click to collapse
thnx. yeah, flashing the PIT actually always worked but it was the only thing that worked! lol
DenmarkRootN00b said:
Have you tried putting a rom on the sdcard with an adapter.. And then put it in the phone and flash the zip from recovery?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
vivelafrance said:
no but good idea. Actually all the flashing work now, but I still can't boot into the phone! This is madness...
before I couldn't flash anything. Now, I flashed the original BTU ROM, Stock recovery but can't boot into recovery anymore, can't boot into the OS, the only thing that works is the download mode.
Will try to get the phone to a repair thing. I'm gonna try with samsung repair centre first cause the right ROM is installed (original) and the counter is at zero so should be fine with warranty.
Click to expand...
Click to collapse
good luck at least i just thought it would work by doing it in recovery but yeah... warranty is better.. if not.. then keep trying if they wont replace it
ok I FINALLY could access the stock recovery, did a full wipe and everything is back in order now, works perfectly.
THANKS to all!
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.
Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
jmjoyas said:
Your phone has a locked boot loader which prevents a full downgrade. If you are on stock NB1, you can adb sideload the NC1 OTA update file. The all things AT&T should have the link.
Sent from my SGH-I337 running GPE using Tapatalk
Click to expand...
Click to collapse
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
N12X93R said:
If I sideload NC1, will I be able to install custom recovery and flash custom ROMs? Or will that require the MK2 downgrade to flash custom recovery after root?
Click to expand...
Click to collapse
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
jmjoyas said:
You will be able to root using towelroot and install touchwiz based custom roms. There is a version of the google play edition that works (there are some known issues though).
The stock recovery cannot be replaced. We have a special recovery (this recovery is available during normal boot itself) called safestrap that can be used to flash the custom roms.
All things AT&T
Click to expand...
Click to collapse
Oh, wow. What happened? I guess Samsung stuck it to us one final hard time. Made things so much harder. Thanks for the clarification.
Unfortunately you cant install Safestrap Recovery while on NC1. At least I haven't been able to at all. Really f'n hating this crappy updated phone I got from ATT as a replacement for my broken old on with the good bootloader.
You should be able to, once you set selinux to permissive mode. Towelroot was also updated to do the same.
Sent from my SGH-I337 running GPE using Tapatalk
N12X93R said:
Hey, guys. I left my G2 to go back to my GS4, and I'm having a bit of trouble. I'm trying to get back to an earlier firmware to gain root and flash custom recovery. Currently on NB1 firmware. TowelRoot does not work.
Anyway, I downloaded the stock ATT Firmware for my phone. UCUAMDL. When I go to Odin, Auto reboot and F reset time is checked. Re-Partition is not checked. Odin sees my phone. I hit PDA or AP and load my firmware file and hit start. Everytime, it fails after Nand write start.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have tried v1.85, 3.04, 3.08, and 3.09. I have tried various USB ports on my computer. I have tried 2 different cables. I always run as admin. I have tried running in compatibility mode. Kies is not installed. I have uninstalled and reinstalled drivers.
Any help?
Click to expand...
Click to collapse
If you are on NB1 you can go back to MK2 to root or update to NC1 to use TowelRoot .
If you want to downgrade to MK2 and root please follow the steps in post 1, 2, 3 at here.
.
I have been searching threads for 6 hours, but haven't found anything conclusive.
I rooted my phone a while back, but today I decided to install a new custom ROM. I backed up the ROM to my external SD and installed the new one through safestrap. However, when I tried to reboot, I just got stuck on a screen that says samsung and has an open lock.
I am able to get into download mode, but not into recovery. After I boot into download mode, it says write protection:enabled (not sure that is normal, but I thought I would mention it). I open up Odin and the drivers seem to load fine. I have tried a a few versions of ODIN and two different Stock ROMs, but it fails every time. On my phone, after it fails, I get a message that says SW Rev. Check Fail: fused 2, binary: 1.
In ODIN, I get the following:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me? I'm getting kind of desperate.
Have you tried another USB cable?.
I have actually. The original cable and just another one I had. Also, tried it on 3 computers.
Should I be loading a PIT file? some places say to do it and others say not to.
marcymtz92 said:
Should I be loading a PIT file? some places say to do it and others say not to.
Click to expand...
Click to collapse
The problem is you're trying to flash mdl firmware and you're not on that version. It looks like you're on mf3. There is no Odin flashable mf3 firmware so I'd suggest you flash the nb1 tar file. See the general forum for the file. http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
You are freaking amazing. That file totally worked. Thanks so much.
marcymtz92 said:
You are freaking amazing. That file totally worked. Thanks so much.
Click to expand...
Click to collapse
Glad you got it working
Sent from my Nexus 5 using XDA Free mobile app
Currently I'm running touchwiz on the latest 5.0 lollipop version. I've tried several different rooting methods and I keep getting stuck on this one error code in odin. Here are the codes:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.57.8-klte.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
You can't install Philz on the Verizon S5 because the boot loader is locked. You can root OA8 using these instructions: http://forum.xda-developers.com/showthread.php?t=3020546 just make sure to go back to NK2 first then follow the old NCG root method.
Thanks this for sure helped. I got it to pass and work, but how long should it take, because my phone has been stuck on the verizon screen for about 10 to 15 minutes. My odin window said it passed so it should work, but how long does this take?
calebp123 said:
Thanks this for sure helped. I got it to pass and work, but how long should it take, because my phone has been stuck on the verizon screen for about 10 to 15 minutes. My odin window said it passed so it should work, but how long does this take?
Click to expand...
Click to collapse
I had that problem as well. I think you need to factory wipe from recovery (volume up+home+power on boot), but there might be a better way to fix the problem.
Hey man, thanks for all the help. I got it rooted, and I installed safestrap. Now I was wondering if I could install cm12 and lollipop on this device, you know of anyway?
calebp123 said:
Hey man, thanks for all the help. I got it rooted, and I installed safestrap. Now I was wondering if I could install cm12 and lollipop on this device, you know of anyway?
Click to expand...
Click to collapse
No, you cannot install CM12 or any other AOSP ROMs. With a locked bootloader and safestrap you are limited to only installing touchwiz (TW) ROMs based on the same build you currently have on your phone. For you that means TW ROMs based on BOA8. Look in the Verizon Galaxy S5 Android Development section, I think there are only two right now.
Currently I'm running on NK2 so are there any that you recommend for that, or is there anyway I could upgrade to lollipop?
calebp123 said:
Currently I'm running on NK2 so are there any that you recommend for that, or is there anyway I could upgrade to lollipop?
Click to expand...
Click to collapse
Same advice as I gave for the BOA8 ROMs, look in the development section for ROMs based on NK2, pick the one that has the most features you want or looks the best to you and try it out. For upgrading to lollipop, follow this guide:
http://forum.xda-developers.com/ver...l/how-to-update-to-g900vvru1boa8-5-0-t3020546