[Q] SM-N9005 HK softbricked. Please help - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi ,
My phone is soft-brocked and I can't get it back. Let me explain what happened, maybe you can suggest next course of action:
1- I tried to install KitKat official release via ODIN (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_HOME.tar.md5 version). Odin FAILED in the middle of the process, and got soft-bricked. When I turn the phone on now I get "Firmware upgrade encountered an issue. Please selecr recovery mode in Kies and try again" :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2- I tried to install previous Poland version, so that I could just perform an OTA update, and it also failed. Then I investigated further and realized my Note 3 is actually a model from Hong Kong (16GB) and seems to be the only version not compatible with other SM-N9005 firmwares.
3.- I found a version of the FW for this specific device (TGY-N9005ZHUDMK1-20131111204936) and tried to install it, then I got to a ext-4 error in Odin (again), unresolved)
4- I got a FW version for my phone with all files separate (N9005ZHUBMI7_China) and tried to upload individualy, I got everything but BL and AP
5- I tried with a forum suggesting to upload Bootloader from leaked KitKat version, and PI, AP, CP and CSC from Chinese version, that did not fix the problem
6.- Now, for any version I try to install I get this:
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> NON-HLOS.bin
<ID:0/012> NAND Write Start!!
<ID:0/012> aboot.mbn
<ID:0/012> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried with ODIN 3.07 and 3.09. Results are exactly the same
7- I tried Kies and I get "The connected device is not supported by Kies 3 (I have the latest version)
8- In Kies, when I try to perform a "Firmware upgrade and initialization" after requesting Model and seial# I get "SM-N9005 does not support initialization"
9- I took my phone to the official Samsung Support in my country (argentina) and they said the model is not sold in Argentina, so there's nothing they can do
What do I have
1.- I can still access download mode and upload via Odin (works fine for CSC, CP and PIT, not for AP and BL)
2.- I can still access recovery mode (after installing CSC alone, the phone starts in recovery mode)
3- Fortunatelly, I have 2 batteries and an external charger, so no battery issues
I have ran out of ideas. Is there anyone around who can lend me a hand with this, please? I am desperate.
Thanks a lot!!!

Have a look at the procedure mentioned here..
http://forum.xda-developers.com/showthread.php?p=49527507
Edit: From the same thread-
* Is this Poland KitKat support Hong Kong N9005 - No, Hong Kong N9005 is not friendly with others country N9005, cannot cross flashing.
* What to do if I accidentally flash it under Hong Kong N9005 and soft brick now - The only solution now is flashing custom recovery (Knox trip due to custom recovery) for KitKat and later flash SweetROM v7 KitKat custom ROM.
Sent from my SM-N900 using Tapatalk

Same thing happened with mine, flashed Cwm with odin and it sprang to life...

Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
rinuvimal said:
This is for Hong Kong 16GB N9005 who were stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Many Thanks to @Volrath for his/her post in another forum with this solution. I have tried and it worked. I've tried almost every other solution without avail. So, this is probably the only solution available at the time I'm writing this post.
Binary: Custom
Knox: 0x1
Method:
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/showthread.php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/showthread.php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)
Click to expand...
Click to collapse

FeralFire said:
Your phone has the kitkat bootloader but no ROM. The only thing you can do is either wait for the official Hong Kong Kitkat ROM or install a custom ROM based on Kitkat.
EDIT:
Here.
Click to expand...
Click to collapse
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.

con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Try some other custom ROM. Try Echoe.

http://forum.xda-developers.com/showthread.php?t=2616103
Sent from my SM-N9005 using Tapatalk

con2vp1 said:
I have the same issue and im just waiting for the Official KitKat HK version. As of right now im stuck basically a phone has no ROM. And since i cannot downgrade to 4.3 because my bootloader already says 4.4.2 and I have tried installing SweetRom KitKat but it keeps crashing on the Samsung Setup Wizard and yes i have every wipe that you can think of still has the same issue.
You can try installing Sweet Rom KitKat and let me know if it works for you because for mine i just cant get it to work and pass the Samsung Setup Wizrd thing it will just crashed.
Click to expand...
Click to collapse
Please delete. Wrong post.

i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m

uglybb88 said:
i got the same problem before and i manage to fix it... but KNOX is triggered.. better bricked ..
so i manage to get HK Note 3 fixed from a soft brick. (flashed kitkat and didnt realize the poland rom is not for HK version LOL)
I got all the file it needed to make it work since i cant post direct link to my mega account.
so i give u guys the file name to search in google
(1) N9005ZHUBMI7.rar
(2) Note 3 Kitkat.zip
(3) n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar
(4) SweetROM_V7.00_NA6_4.4.2_N9005.zip
i used ODIN 3.07 for the progress... it might work on 3.09 or even better
so here is the procedure
a) unzip all the file in (1) and (2)
b) phone in download mode
c) open 3.07 .
d) pick the PIT file from (1). bootloader/BL from (2), PDA/AP, Phone/CP and CSC all from (1)
e) flash and wait until it reboot.
f) download mode again and use ODIN 3.07 to flash (3) in the PDA
G) after root (shall into a boot loop) . take the battery out and put into recovery (vol up , home , power)
H) make sure u have the (4) inside the root of the SD card (rename to update.zip) and do a wipe/ reset . then flash
i) when is done .. ur phone will boot fully.. then shut off and flash CP again one more time. CP is from (2) and use ODIN 3.07
now ur phone will be up and running
any question let me know
and if u need the file
email me and i give u the link
u g l y b b @ h o t m a i l . c o m
Click to expand...
Click to collapse
Do you have the 16gb or the 32gb hongkong version?

Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.

is a 16gb
filchi756 said:
Do you have the 16gb or the 32gb hongkong version?
Click to expand...
Click to collapse

Question
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
maumarti2k said:
Hi guys, thanks a lot for your comments. I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flashed bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flased bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flased AP from N9005ZHUBMI7 (Honk Kong version)
4.- Entered recovery mode and wiped system, cache and dalvik (just in case)
4.- Flashed autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flased CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/showthread.php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
Click to expand...
Click to collapse

Maybe I can help
fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Maybe I can help.
Please read my article at http://forum.xda-developers.com/showthread.php?p=49831876

fbasbas said:
Hi there,
I reached step 4 and flashed AP N9005ZHUDMJ8 (HK version too) but got an error. Is it a must to use your suggested version?
Thank you.
Click to expand...
Click to collapse
Actually, I only got it to work with the version I mentioned in the post, I don't think I tried with the version you mention. If it failed, I'd suggest you start over, but this time try with the version I suggested, since at least I know this worked for 2 people already. Also, I believe you need to own a 16GB HK version, just in case, Hope this helps

Ask for Help
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl1.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)
can not..............hix hix hix

working solution
Download and ODIN flash N9005ZHUENB5 in sam mobile. Works on my HK Note 3
minhluansgk said:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N9005ZHUBMI7_1626679_REV03_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N9005XXUBMI5_REV03_CL1252918.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_ZZH_N9005ZZHBMI7_1626679_REV03_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<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> sbl1.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)
can not..............hix hix hix
Click to expand...
Click to collapse

Related

The end of my S4? (Brick/dead) - Help..

Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
lethcore said:
Hi guys, long time lurker here anyway i've always flashed my S4 with odin and not a single problem always flashed STOCK firmwares
but today i recently discovered a new firmware on the list for the GT-I9500 Exynos Octa (version) - this firmware to be in fact I9500ZNUCMI1
but now its bombed... it hanged and hanged at booting for 20 min then it shut it self off turned it back on 'the firmware encounter a problem' message popped up... i cannot go into recovery mode AT ALL (just download mode) so i thought i will flash my previous stock firmware known as I9500XXUBMG9 but now i cant even do that..... odin just gives me a god damn fail - FOR THE LOVE OF ANDROID HELP ME
- Kies is not running in the background
- USB connections are fine
- Cables are fine
So do i have to fear this is the end ? lol i cannot believe this happened to me on a STOCK firmware.... (lucky for me... all my stuff is backed up on sd)
Any help would be greatly appreciated
Click to expand...
Click to collapse
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
donalgodon said:
If you can get into Download mode, all hope is not lost. Uninstall and resinstall drivers, Odin, etc. reboot.
Odin back to stock, immediately boot into stock recovery, wipe data, reboot.
Done.
Click to expand...
Click to collapse
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
The good news is that Download mode is still working. AS long as that's the case, you can get it back. Just keep trying. Switch PCs, switch cables, switch ports, re download a different stock ROM, etc. do whatever it takes to try every variable you can think of.
Eventually, you'll find what's causing it and the ROM will flash successfully. When that happens, get immediately into recovery and wipe data.
(Remove the battery after it flashes, but it back in and hold vol-up+home+power.)
After the data wipe....
Reboot.
Like I said, Download mode means you can find a way to flash, but working with Odin to resolve these issues can sometimes be a PITA. I've had the same thing myself before. Just don't give up. Try to stay calm, and work your way through it. You'll get it eventually.
Edit: Just noticed that you flashed a CHINA firmware. (Why? ) You may be facing this issue because (I think) they use a different pit. There's a thread devoted to resurrecting the device with pit. Maybe check it out.
lethcore said:
Thx for reply
Still says FAIL when i try to flash I9500XXUBMG9 what am i doing wrong ?
rebooted laptop twice plug in S4 via usb says unknown device when in download mode but odin reconise it flash it and nothing happens on the screen then i get the big fat RED FAIL ............... AHHH
Click to expand...
Click to collapse
dont flash China or Hong kong firmwares.
please post odin progression
samersh72 said:
dont flash China or Hong kong firmwares.
please post odin progression
Click to expand...
Click to collapse
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
lethcore said:
Nothing to post just says 'completed' but its failed.... i'll remember this next time stay away from china/hong kong firmwares...
im still tyring now and will let you guys/girls know how it pans out! wish me luck!
Click to expand...
Click to collapse
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
lethcore said:
INFO HERE
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> persdata.img
<ID:0/005> system.img
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
recovery is flashed, try to boot into it and make the wipe then re-flash stock, re-wipe.
if not, flash a custom recovery, format system, cache, re-flash stock, re-wipe
@donalgodon
Why ? well i got the I9500 in hong kong (im actually based in china now) (not Chinese though) thought i'll see some nice changes? but seems i fK'ed the phone.... pit? i haven't a clue man pit number? think i've KILLED HER... lol (i never knew the dangers of Chinese firmware) - wont be going down that route again.
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
lethcore said:
@samersh72
Are you sure? i cannot get into 'recover' mode... the phone just hands at 'Firmware upgrade encounted an issue please select kies & try again
i canm only enter download mode.... when i try to enter recover mode it just flashes at the firmware message.
Click to expand...
Click to collapse
flash custom recovery,
if not see my signature for flashing right pit with the firmware
samersh72 said:
flash custom recovery,
if not see my signature for flashing right pit with the firmware
Click to expand...
Click to collapse
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
lethcore said:
Well i just grabbed a I9500 pit file and have my stock firmware just add these 2 to odin and click start? that simple or ??
Click to expand...
Click to collapse
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
samersh72 said:
yes, make sure that you are using the right pit, put it in "pit" window in odin, and the firmware in "pda", make sure "re-partition" is ticked, start.
Click to expand...
Click to collapse
Well you be happy to know
installed the previous firmware and that pit file for I9500 from your sig and everything seems well... booted correctly nothing lost all seems good to early to tell but will keep you informed !
THANK YOU!!!

Note 3 is "not supported" by Kies 3

EDIT: At this point, I'm just trying to flash official firmware via ODIN but every attempt is ending with ODIN: Invalid ext4 image on various firmwares and via various USB ports
Hi everyone,
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I have tried reinstalling Kies, different USB ports (USB 2.0 & 3.0) after turning off USB 3.0 charging too, reseating the battery etc but each time, Kies tells me "The connected device is not supported by Kies 3. Check which devices are supported and try again." except Kies 3 is what the Note 3 uses...
Reinstalling the driver as well doesn't appear to do anything either. The Note 3 shows up in device manager as SAMSUNG Mobile USB Modem so it's detected but I can't exactly say if that is correct?
Anyway, any help is appreciated! I'll see when Samsung's contact centre is open next being Christmas and all and since I was only flashing official firmware, my Knox counter is still at 0x0 so my warranty is still in place should the need to use it arise.
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
ione2380 said:
If you flash with odin then why do you need kies for? Just put it in download mode and flash it again.
Sent from Note 3 SM-N9005
Click to expand...
Click to collapse
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Having the same problem
Sentryism said:
Flashing with ODIN has been stopping on "Invalid ext4 image" every time but I'm downloading another ROM to try out at the moment. Hopefully that should work. I was trying to avoid ODIN since I wasn't sure if repeatedly try to flash a ROM (even official firmware) and having it fail would make things worse.
Click to expand...
Click to collapse
What's the solution? Do you already could find the problem?
bgantenbein said:
What's the solution? Do you already could find the problem?
Click to expand...
Click to collapse
Well, I don't have one yet. I'm still going through various firmwares but the second one I've tried threw up the same error. Basically, I'm just waiting for firmwares to download at the moment. I'll report back if I manage to fix it. I would assume it's due to not having debugging mode enabled but I can't exactly enable it in my current situation.
Here is the ODIN log if it is of any use:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005OXADMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> sbl1.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> aboot.mbn
<ID:0/009> rpm.mbn
<ID:0/009> tz.mbn
<ID:0/009> sdi.mbn
<ID:0/009> NON-HLOS.bin
<ID:0/009> boot.img
<ID:0/009> recovery.img
<ID:0/009> system.img.ext4
<ID:0/009> FAIL! (Ext4)
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
It seems that you might have a severe case of bad blocks on the eMMC (internal flash) - that in itself should be enough reason for a warranty replacement.
If you can not do a warranty replacement you should look (inside Odin) into erasing all NAND and repartitioning (there are some posts around with similar info, read a few of those until you understand what you are doing before starting to do anything on that direction).
Hello!
I made the switch from iOS to Android a couple of days ago and as well own a Note 3 device. After a couple of days of reading around the forums I decided to flash the MK2 Uk rom since in my country we're only up to MJ7 and I've been experiencing very weird battery drains. I am aware that the update won't likely fix them and I'll have to wait for the next one in January but I hope to at least make things better. Unfortunately today I downloaded Kies3 and I'm getting the same error when I click on the firmware check or upgrade menu (or whatever it is called). I haven't tried Odin yet because the firmware was taking too long to download and I had tl go out for work. Still I very doubt it will work since the official program isn't even working.
tl;dr; Please post in the topic when you find a solution as I am experiencing the same problem as well. Especially if I have to do a warranty replace since I have a wiggly button and I was wondering whether to do that in the first place.
Possible not a genuine Note 3?
This is absurd, I said I am new to Android, this doesn't mean I have grown in a pot. My device came with all the appropriate stickers, branding and everything and is purchased through a local carrier. Unfortunately I got one from Vietnam with the wiggly home button but it is a legit device. Anyways I even tried contacting my local support but they were most unhelpful, only forwarded me to an Authorized Service Provider (what an awful chat app, they disconnected me and I even lost the details). I think I will soon try flashing a custom firmware through CWM or something..
Sentryism said:
...
I recently picked up a Galaxy Note 3 which I soon realized was a parallel import and so I decided to flash firmware from my country with Odin. It failed (I soon realized I had forgotten to enable USB debugging) and my phone currently displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
...
Click to expand...
Click to collapse
I believe KIES 3 in Emergency Firmware Recovery mode does NOT YET support the updated bootloaders - so if your device has a bootloader >= MJ3 it will not be seen in KIES 3. I am still using Kies v3.1 but I have seen a v3.2 available, however I do not know if the problem is solved.
Sentryism said:
Well, I've gone through about 5 or 6 various ROMs and each fail at system.img.ext4 so I'm at a loss as to if I can even flash back to stock. I plan on contacting Samsung Support since my Knox counter is safely at 0x0 and I've run out of relevant posts to read that I have found.
Click to expand...
Click to collapse
Hi
Just had exactly the same problem as yours, and odin continuously failed just after 'hidden img'. Tried several roms to no avail. Phone was already rooted before the issue, and knox flag was already 0x1. I decided to flash cwm recovery (via odin) from here:
http://forum.xda-developers.com/showthread.php?t=2454079
The note 3 (SM-N9005) booted all the way surprisingly but with some issues (back button not working/Samsung keyboard stopping). I can now flash rom zip.
Tip: As your Knox flag is 0x0, try flashing stock recovery via odin.
Flashed Rom zip. Note 3 back to health.
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
shayind4 said:
Flashed Rom zip. Note 3 back to health.
Click to expand...
Click to collapse
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
R2D2_NZ said:
Which ROM worked? I'm having a trying old time finding one that installs AND boots.
TIA for any help you can offer.
Cheers,
R2
Click to expand...
Click to collapse
Hi
I flashed Djembey's deodexed pre-rooted jb 4.3 SM-N9005 XXUDMJ7 superslim rom (cwm) from here (second post):
http://forum.xda-developers.com/showthread.php?t=2461929
I used CWM recovery. After flashing the superslim rom, I was able to flash stock rom via odin.
Shayind4
---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------
androidlover287 said:
\given the fact it was a Zip file he flashed, it would a CWM flashable ROM that worked
Click to expand...
Click to collapse
You are right.
If you tried to flash a firmware from another country than the original one, it might be that the partition size is not correct. You probably need to flash a pit file that is matching the partition size of the new firmware. Try to search for one that is matching to one of the firmware you downloaded and flash it with the new firmware ( tick repartition in Odin - this will erase your data !!!).
This is just a proposal and I do not know it it will work, but I got that hint from a thread in a German forum about changing from EU version to DBT firmware.
Im having a similar issue, except my note3 is the exynos (sm-n900), kies3 says my phone is not supported and odin fails at flashing my phone, it shows this
<ID:0/026> Added!!
<ID:0/026> Removed!!
<ID:0/027> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900ZSUCML1_N900OZSCML1_N900ZSUCMJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/027> Odin v.3 engine (ID:27)..
<ID:0/027> File analysis..
<ID:0/027> SetupConnection..
<ID:0/027> Initialzation..
<ID:0/027> Get PIT for mapping..
<ID:0/027> Firmware update start..
<ID:0/027> modem.bin
<ID:0/027> NAND Write Start!!
<ID:0/027> sboot.bin
<ID:0/027> boot.img
<ID:0/027> cache.img
<ID:0/027>
<ID:0/027> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have no idea on what else to do, any help please?
I've got the system.img.ext4 issue as well. Knox is still 0x0 and I was only trying to flash (Odin) a ROM from Sammobile - MI7, same level as the original but XSA instead of TGY. Bloody annoying.
Anyone got the Aussie Samsung support number?
I resolved my issue by DL'ing and flashing the TGY ROM - got an MI7 version so I should be still OK for RDLV. Apparently flashing with the ROM from another country is a problem - Odin passed teh XSA one without an issue, so I don't think it was a corrupt DL. I did see a reference in my searching to perhaps the partitions are different sizes in different CSC's or something.
So, now to enjoy my Note for a few days before rooting...

Odin wont flash stock firmware, please help :(

Okay so I am using a AT&T Galaxy S5, SM-G900A. I was being an idiot and I wiped everything on my phone. So now when I downloaded Odin, downloaded the SM-G900A stock firmware, tried to flash it with odin and I kept getting this error no matter what I do, someone please help me....
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900AUCU1ANCE_G900AATT1ANCE_G900AUCU1ANCE_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> SingleDownload.
<ID:0/003> aboot.mbn
<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)
When my phone is in download mode, after I get the error in odin heres what my phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Nevermind, got it fixed. All thanks to Davew41's post: http://forum.xda-developers.com/showthread.php?t=2785363
Hi, I have j510fn and I was a rom tester,
I have a problem since I flashed
J510FNXXU2APK6_J510FNODD2APK2_J510FNXXU2APK2_HOME.tar.md5
to test light stock rom v3 from Kingraheel
what happens is that NOW I can't flash any other firmware by odin... when I click START it says FAIL and in my device there is this text in red
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I just want to flash my OFFICIAL firmware
J510FNXXU1APG1_J510FNPHE1APG1_J510FNXWU1APFC_HOME.tar.md5
but I can't... only APK6 firmware works on odin... any other firmware works.... can you help me?
I don't have any NANDROID backup of previous versions... only of my actual firmware... APK6
My computer does not detect my device... I have the drivers installed, and I tried on all the USB ports... it charges but not open files.... PLEASE HELP
TheWalkingSans said:
Hi, I have j510fn and I was a rom tester,
I have a problem since I flashed
J510FNXXU2APK6_J510FNODD2APK2_J510FNXXU2APK2_HOME.tar.md5
to test light stock rom v3 from Kingraheel
what happens is that NOW I can't flash any other firmware by odin... when I click START it says FAIL and in my device there is this text in red
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
I just want to flash my OFFICIAL firmware
J510FNXXU1APG1_J510FNPHE1APG1_J510FNXWU1APFC_HOME.tar.md5
but I can't... only APK6 firmware works on odin... any other firmware works.... can you help me?
I don't have any NANDROID backup of previous versions... only of my actual firmware... APK6
My computer does not detect my device... I have the drivers installed, and I tried on all the USB ports... it charges but not open files.... PLEASE HELP
Click to expand...
Click to collapse
have you tried a different cable? I know it sounds rather sophomorish, but its a very common cause of the computer not being able to flash via Odin. Or can you get to another computer to try it there?
youdoofus said:
have you tried a different cable? I know it sounds rather sophomorish, but its a very common cause of the computer not being able to flash via Odin. Or can you get to another computer to try it there?
Click to expand...
Click to collapse
I just changed CSC with solid explorer, and flashed another stock firmware from samfirm downloader
But my computer continues without detecting my device... but ODIN does
TheWalkingSans said:
I just changed CSC with solid explorer, and flashed another stock firmware from samfirm downloader
But my computer continues without detecting my device... but ODIN does
Click to expand...
Click to collapse
that is odd indeed. I have 4 computers that all recognize all of my samsung phones. Are you getting the unrecognized device message in the area down by the clock?
My other computer detects it, okay, but I still cant flash any other stock firmware by odin AND BEFORE I COULD
---------------------------------------
EVERYTHING SOLVED, SAME PROBLEM? CONTACT ME
Here is HOW I SOLVED IT:
This error happens when you before have updated from "U1" to "U2" and then you try to flash a firmware with "U1" (UX appears in the firmware "name")
So, the simple solution is to flash the stock firmware with the same "UX" that you had before your device gor bricked.
In my case, testing KingRaheel's ROMS I flashed an Indian firmware (...U2APK6...) at this moment I didn't know I ****ed up. But don't worry, I simply had updated the "U" and how I didn't know it, I tried to flash lots and lots of firmwares with "U1" without knowing what was happening. After long nights, I tried to flash my last firmware from SPAIN (PHE) with "U2" and it worked.
I hope I helped you. I used SM-J510FN (J5 2016)
If you have another device, try the same but with your current model, any questions, ask by twitter/dm
Sent from my SM-J510FN using XDA Labs

[Solved] Need help with SHV-E300L - Cannot load most roms - stuck with bad rom

Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?
nicenormalfiend said:
Hi,
So I'm a bit of a noob with regards to roms and kernels and all that stuff and I've found myself with a bit of a problem.
I ordered a Samsung Galaxy S4 (i9500) from Korea and received it a few days ago. The phone worked fine but was Android 4.2.2. There was no updates available OTA or in Kies so I decided to try flash my own rom.
I went about doing this and discovered that CWM recovery was already on the phone...it must have been added by the supplier, however the CWM version was in Korean.
I downloaded a rom, the first one I found, called Ozcran Rom. It's Android 4.4.2. On my phone it's very unstable, it keeps rebooting and it cannot recognize my sim card but it kind of works. I've tried to change the rom to many other ones but they all either fail to install or if I can install them they load but get no further than the boot animation.
Because the CWM was in Korean and because I'm a fool I never made a backup of the original. I've since been able to update CWM to an english version and figured out how to make a backup of the (barely working) Ozcran rom but I'm not having any luck installing a rom that actually works.
I've tried loading roms with both CWM and Odin but usually Odin fails. Odin was able to update CWM recovery for me but it seems to fail everytime I try to install a rom.
I've attached a screenshot of the About screen (when it's working with Ozcran Rom). When the phone is in download mode (in korean) it says Product Name: SHV-E300L, Current Binary: Custom, System status: Custom.
Can someone please help with this?
Click to expand...
Click to collapse
can you tell us what odin says when it fails? give us a picture please, most odin fails are because of wrong firmware for wrong devices. also did you get your stock rom from here http://www.sammobile.com/firmwares/2/ ? most recommended place.
Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_HOME.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
nicenormalfiend said:
Hi.
One of the stock roms I tried was from sammobile yes.
I've attached an image of Odin when it fails and I've pasted the content of the message box here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUGNH4_I9500OJKGNI1_I9500JKUGNH1_HOME.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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.
Trozzul said:
you say its a i9500 but you said its a SHV-E300L in download mode, try flashing one of those stock roms from sammobile might have to deal with Korean language for awhile unless Samsung Korean phones come with english. You are sure its a i9500? take out the battery and tell me the model number where the battery is supposed to go.
Click to expand...
Click to collapse
I thought perhaps SHV-E300L was the model number of the i9500 in Korea.
Under the batter the model number says GT-i9500. Is the SHV-E300L supposed to be different from the i9500?
I'll try downloading firmware from sammobile for the SHV-E300L...
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Ok, thanks for the lead. I'll give the SHV-E300L firmware a go
Trozzul said:
I'm not sure about that model number question. All I know is i9500 sounds international so maybe that says its international but runs on shv e300l firmware.
Click to expand...
Click to collapse
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!
nicenormalfiend said:
Amazing, the firmware for SHV-E300L works perfectly. Thank you so much!
Click to expand...
Click to collapse
Enjoy i hope you are able to get non-korean languages if you need it. if you have any other questions please be sure to ask!
я
мне тоже дайти
nicenormalfiend said:
ok, thanks for the lead. I'll give the shv-e300l firmware a go
Click to expand...
Click to collapse

S5 Active (G870A) stuck at AT&T logo

I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the 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/003> Added!!
<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> aboot.mbn
<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)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Guess no one can help me. Lame. :[
I'm just trying to find root package so I can downgrade my active and root it. But I'm having trouble finding it. Can you give me any help please?
S5 Active
My little cousin soft bricked (same issue).
My little cousin said he went into SU and did "full unroot" and after the reboot got stuck on the AT&T logo, the kid brought the phone to me in search of help.
I've tried every which way I could think of using odin to try and reflash everything under the sun and cannot find a solution. I can get into download and recovery fine but I cannot flash anything: odin flashes fail except when I when I use odin to flash boot.tar (AP), modem.bin (CP), recovery.tar (BL), it's one of the few times the flash is a pass instead of a fail; recovery won't authenticate any roms.
stumbled on this thread and downloaded an official rom but flashing fails after authentication:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
He said he was on 5.0, stock rooted stock rom - he told me he was sick and tired of the 5.1 update notification and tried to unroot to update and now it's soft-bricked.
here's a screen of all the firmwares and softwares and roms I've tried flashing every which way possible
Smart Switch and Kies3 asks for a recovery code (no idea where to get that); Sammobile only has FW for 4.3, this phone was at 5.0 - my understanding is that it's very difficult to go back from 5.0. I was thinking I could root again and then install custom recovery but can I even do that with no rom installed? any help would be much appreciated!
one more pic for good measure:
Fancy resizing your image?!
*Detection* said:
Fancy resizing your image?!
Click to expand...
Click to collapse
image 1 - error after authentication: http://imgur.com/1mPpRls
image 2 - list of what i've been using http://i.imgur.com/NqZeQlL
image 3 - booting: http://i.imgur.com/ygHqDWn
extra images:
trying to update via kies screen shots: http://imgur.com/GZV20R8
failes kies on the phone: http://imgur.com/07dilCW
I mean your already posted 16k screenshot above
*Detection* said:
I mean your already posted 16k screenshot above
Click to expand...
Click to collapse
sorry, i don't follow
phi303 said:
sorry, i don't follow
Click to expand...
Click to collapse
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)
*Detection* said:
This post you made with your photos of your phone, the photo is huge
http://forum.xda-developers.com/showpost.php?p=65637433&postcount=4
You need to remove it, resize it, and upload it again
Maybe you can't see if you are browsing from a phone, from a PC, the image is ridiculously big
This is what we see from a PC (EDIT - Seems to be the XDA Classic forum theme that doesn't resize automatically)
Click to expand...
Click to collapse
I haven't changed any themes on xda and the images are automatically resized to width on the desktop:
SS: https://imgur.com/NvCyid7
I know, I mean I am using the classic theme, and it doesn't resize it
Don't worry
If you want to check, switch the theme down at the bottom left of the forum to XDA Classic
Then go look at your screenshot
Muunia said:
I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the 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/003> Added!!
<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> aboot.mbn
<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)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?
The assasin said:
I have the same problem, I want to flash stock firmware but it was always failed like what poested. I dont know how to fix it until now. What i did was flash TWRP then flash custom ROM but i want to flash stock firm. Did you manage to fix this problem?
Click to expand...
Click to collapse
Nope, never could find any more information on it. AT&T just told me to file an insurance claim that it was lost, and I got an s6 active for 99$ instead of a new s6 active.

Categories

Resources