Database Users

Odin Fails at MODEM.bin - How to fix it.

So I finally decided to flash firmware 4.1.2 on my G.Cam (AT&T). I downloaded the firmware from SamMobile and started flashing through ODIN but it got stuck on Modem.Bin and failed. I tried several other firmware and all of them failed on Modem.bin
When I tried to turn on my camera a screen with "Error on Upgrading, try Recovery with Kies" came out. I must admit I panicked so I searched all the forums here on XDA and the same thing happen to somebody on their Galaxy Tab 10.1 The solution for them and for me was to root through Odin.
Like magic, it worked. I flashed through odin the CF-Auto-Root Adam have us on this thread: http://forum.xda-developers.com/showthread.php?t=1995245
And after that my camera boot once again and now I have Android 4.1.2
I'm happy everything turned out ok, so I that's way I'm sharing this so that other users that have the same problem as me can know what to do (this should be a sticky).
Happy Flashing.

Saved me too! Thanks!

My GC stuck on boot screen and continually reboot on Chainfire SU. I tried to re flash CF Auto Root from Adam by ODIN but still the same. How can i do? Please kindly advice.

becooled said:
My GC stuck on boot screen and continually reboot on Chainfire SU. I tried to re flash CF Auto Root from Adam by ODIN but still the same. How can i do? Please kindly advice.
Click to expand...
Click to collapse
What did you do?

Flash fail with Odin for Galaxy Note 10.1 N8000
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000. I have read all tutorials etc. and prepared all according to it.
I was able to succesfully root to Clockwork Recovery so i though flashing another firmware to turn the Note into a European one instead of Chinese would be easy too. WRONG!!
Every time i want to flash with Odin it fails in the beginning of the process, see below:
Is there anyone who could comment me on what to do? I was able to recover from the failed flash attempt but i really want to flash another firmware from Europe for this Chinese version.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XXCLL3_N8000OXECLL1_N8000XXCLL1_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> boot.img
<ID:0/005> NAND Write Start!!
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> modem.bin
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks a lot far any help.
Dave

davaze said:
Hi,
I'm trying to flash another firmware for my GIalaxy Note 10.1 N8000.
Click to expand...
Click to collapse
You need to be posting this in the Galaxy Note 10.1 N80xx Q&A forum. This one is for the Galaxy camera!
However, make sure you don't have Kies running. I turn it off completely using Microsoft's autoruns program. Good luck.
Sent from my GT-P6810 using xda app-developers app

FarmBoi said:
You need to be posting this in the Galaxy Note 10.1 N80xx Q&A forum. This one is for the Galaxy camera!
However, make sure you don't have Kies running. I turn it off completely using Microsoft's autoruns program. Good luck.
Sent from my GT-P6810 using xda app-developers app
Click to expand...
Click to collapse
Hi i already moved this topic to the Galaxy Tab 10.1 Q&A section.
However i just installed the USB drivers only, never used KIES on my pc before at all so this should not be the reason.
I tried two different Firmwares already both flash in a different sequence but both fail at modem.bin. I have no idea why.
Please if anyone has some idea please comment on this topic under the Galaxy Note 10.1 Q&A section of this forum, i moved this to there.
Thanks a lot.
Dave

This is the newest post that closed to the issue I get that I could find on Google. So I also got this problem that odin seems to stops (it just never finish) at modem.bin.
{
"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"
}
I am trying to root my Samsung note 10+ and here is the whole process:
I used SamFirm (v0.5.0) to download firmware (Model SM-N975F, region: SIN, auto), extract it.
Then I used Magish manager to patch AP... file from extracted folder, then copy it back to the extract folder on the computer.
Then use Odin (tried both v3.13.3 and v3.14.1, same results) to flash the files to the phone.
(I following this tut: https://www.thecustomdroid.com/root-samsung-galaxy-note-10-plus-magisk/)
However when I tried for note 10+ I got this issue.
If I load AP file by the original AP file from extracted folder above, then I can flash it to PASS! and recover the phone to fresh state.
The strange thing is I have done similar process and success for my note 10.
Is there anything else I can try here ?

[HELP]After EFS Bootloop->All attemps verified failed

Good Morning @ll.
I hope one of you can help me. I´m here for years with my HTC. Than i change to iPhone and now I´m back with my Samsung Galaxy Note 3.
What I do:
- became "root", no problem.
- searching for one ROM, no problem.
- Install from the Play Store the "GooManager"
- Now I start in Recovery Mod
- Then I see i must be make an Backup. I Download the "EFS BACKUP" from the AppStore.
Now the problem starts.
After rebooting I have messages from Android with "problems by starting the system" Wait or OK" I can´t Reset in the Settings the Note 3. I do in the Recovery Mode first the Install from the new Rom.
Now I have the problem with the Bootloop. When Android starts, after a few try, I can´t go to Settings->Infos for the system or do a complete Restore. I can´t connect to the Internet because Wifi doesn´t connect and the sim card the have in the right corner an "ban" logo.
Ok, i search here for somethink. I use this:
http://forum.xda-developers.com/showthread.php?t=2507403
I use the Java JDK and the Android SDK for ADB. Install it and use it under System->Path! ADB is working in CMD.
When I go to the CustomRecoveryMod, the PC doesn´t Notifite it. Only when I say "apply update from ADB" I can send with "adb sideload c:\update.zip" a file.
I want to connect it and want to try the "adb shell", but I can´t
{
"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"
}
Ok. Then I see an Zip file for it. Download it, put it on the MicroSD and go to the CustomerRevocerymenu and want to update it.
I use the Odin Updater with a German Rom and a PIT File to debrand the Note 3: http://www.android-hilfe.de/anleitungen-fuer-samsung-galaxy-note-3/509516-anleitung-note-3-debranding-alle-eu-modelle-zu-dbt.html
But everythink I do, I have the error "E: verified failed.
Now, I hope anyone can help me
Thanks.
How can I install TWRP with Terminal? - I have download it. Save it on C:\ Now I go to the Revocer Mode und Press "apply update from ADB" After I say in the cmd Box "adb sideload C:\update.zip" I have the E:signature verification failed"....i hate this!

No one can help me ?

Deathack said:
No one can help me ?
Click to expand...
Click to collapse
You didn't have any custom recovery installed?
Try to boot into download mode and flash TWRP by using Odin.
Make sure the driver has been installed.

vndnguyen said:
You didn't have any custom recovery installed?
Try to boot into download mode and flash TWRP by using Odin.
Make sure the driver has been installed.
Click to expand...
Click to collapse
Thanks for your Answer.
Has you one Download Link for me for the TWRP? Odin I have it.
Thanks.

Deathack said:
Thanks for your Answer.
Has you one Download Link for me for the TWRP? Odin I have it.
Thanks.
Click to expand...
Click to collapse
How can u go without any custom recovery!
U can find the correct TWRP for your device here: http://teamw.in/twrp_view_all_devices
I personally use CWM recovery, but they are both quite good.
Make sure the correct version of TWRP for your device and the correct driver installed.

Thanks for the Link.
For Germany I Download: openrecovery-twrp-2.6.3.8-hltetmo.img.tar
TWRP for Samsung Galaxy Note 3 (T-Mobile) [hltetmo]
<ID:0/005> Added!!
<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> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Whats wrong? Pit File?
Thanks.
EDIT
OK now I have it.
Thanks first....Now I want to use the Terminal and answer.

So now i have CWM based Recovery v6.0.4.4 on the device and install the zip from here:
http://forum.xda-developers.com/showthread.php?t=2507403
Wipe data and reboot! But the same error such before.
Than I use this:
http://forum.xda-developers.com/showthread.php?t=2471421
But here also the same mistake.
What can I do
Thanks for your Help.

Deathack said:
So now i have CWM based Recovery v6.0.4.4 on the device and install the zip from here:
http://forum.xda-developers.com/showthread.php?t=2507403
Wipe data and reboot! But the same error such before.
Than I use this:
http://forum.xda-developers.com/showthread.php?t=2471421
But here also the same mistake.
What can I do
Thanks for your Help.
Click to expand...
Click to collapse
May be there is a problem with the modem?
What region is your Note 3 from? What firmware version are u using?
Go to http://www.sammobile.com/firmwares/?page=1 and search for your stock rom, then flash it via Odin.
Hope that helps.

vndnguyen said:
May be there is a problem with the modem?
What region is your Note 3 from? What firmware version are u using?
Go to http://www.sammobile.com/firmwares/?page=1 and search for your stock rom, then flash it via Odin.
Hope that helps.
Click to expand...
Click to collapse
How can i look witch I have?
I´m from Germany with Vodafone or T-Mobile. I mean its DBT. This is the Last Firmware I Flash:
Now I check from Vodafone...I buy it with a Vodafone payment, but the Note 3 came first, without Branding.
Update with Odin was ok:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005DBTDMJ4_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<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> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But the Mistake is the same....and now

http://forum.xda-developers.com/showthread.php?t=2567133
It worked for me

Deathack said:
...
But the Mistake is the same....and now
Click to expand...
Click to collapse
follow this instruction step-by-step exactly: http://forum.xda-developers.com/showthread.php?t=2567133

Deathack said:
Good Morning @ll.
I hope one of you can help me. I´m here for years with my HTC. Than i change to iPhone and now I´m back with my Samsung Galaxy Note 3.
What I do:
- became "root", no problem.
- searching for one ROM, no problem.
- Install from the Play Store the "GooManager"
- Now I start in Recovery Mod
- Then I see i must be make an Backup. I Download the "EFS BACKUP" from the AppStore.
Now the problem starts.
After rebooting I have messages from Android with "problems by starting the system" Wait or OK" I can´t Reset in the Settings the Note 3. I do in the Recovery Mode first the Install from the new Rom.
Now I have the problem with the Bootloop. When Android starts, after a few try, I can´t go to Settings->Infos for the system or do a complete Restore. I can´t connect to the Internet because Wifi doesn´t connect and the sim card the have in the right corner an "ban" logo.
Ok, i search here for somethink. I use this:
http://forum.xda-developers.com/showthread.php?t=2507403
I use the Java JDK and the Android SDK for ADB. Install it and use it under System->Path! ADB is working in CMD.
When I go to the CustomRecoveryMod, the PC doesn´t Notifite it. Only when I say "apply update from ADB" I can send with "adb sideload c:\update.zip" a file.
I want to connect it and want to try the "adb shell", but I can´t
Ok. Then I see an Zip file for it. Download it, put it on the MicroSD and go to the CustomerRevocerymenu and want to update it.
I use the Odin Updater with a German Rom and a PIT File to debrand the Note 3: http://www.android-hilfe.de/anleitungen-fuer-samsung-galaxy-note-3/509516-anleitung-note-3-debranding-alle-eu-modelle-zu-dbt.html
But everythink I do, I have the error "E: verified failed.
Now, I hope anyone can help me
Thanks.
How can I install TWRP with Terminal? - I have download it. Save it on C:\ Now I go to the Revocer Mode und Press "apply update from ADB" After I say in the cmd Box "adb sideload C:\update.zip" I have the E:signature verification failed"....i hate this!
Click to expand...
Click to collapse
I had similar issue "System not responding" and boot loop,and I managed to fix it check my thread and follow the steps in post #1
http://forum.xda-developers.com/showthread.php?t=2540822
Hope it helps

Raphy511 said:
http://forum.xda-developers.com/showthread.php?t=2567133
It worked for me
Click to expand...
Click to collapse
By me, no. But thanks for you Help.
Dahdoul said:
I had similar issue "System not responding" and boot loop,and I managed to fix it check my thread and follow the steps in post #1
http://forum.xda-developers.com/showthread.php?t=2540822
Hope it helps
Click to expand...
Click to collapse
I Love you This is the right answer. I complete make all you write and it works. Many Thanks.

[Q] Soft brick - Fail flashing Stock ROM at hidden.img Odin

Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?

RixNox said:
Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?
Click to expand...
Click to collapse
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.

Wrathlon said:
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.
Click to expand...
Click to collapse
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?

RixNox said:
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?
Click to expand...
Click to collapse
Correct

Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
{
"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"
}
You rule mate!!! Thanks a lot!!!!!!!!!!!

Thankfully Samsung have a secondary bootloader. The picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
You can also forget Kies, since the MJ3 bootloader Kies doesn't recognise the Note 3....

ultramag69 said:
Thankfully Samsung havce 2 bootloader modes, the picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
Click to expand...
Click to collapse
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?

RixNox said:
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?
Click to expand...
Click to collapse
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...

ultramag69 said:
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...
Click to expand...
Click to collapse
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?

RixNox said:
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?
Click to expand...
Click to collapse
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....

ultramag69 said:
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....
Click to expand...
Click to collapse
Very risky.... I wonder how they manage at Samsung OTA/Kies updates... are they any safer? Maybe it's a bad habit to download firmwares from other sites?

It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...

ultramag69 said:
It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...
Click to expand...
Click to collapse
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...

Still Stuck
RixNox said:
Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
You rule mate!!! Thanks a lot!!!!!!!!!!!
Click to expand...
Click to collapse
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?

RixNox said:
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...
Click to expand...
Click to collapse
Nope... The bounty is over $3000 USD...

jebanec said:
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?
Click to expand...
Click to collapse
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)

RixNox said:
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)
Click to expand...
Click to collapse
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.

jebanec said:
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.
Click to expand...
Click to collapse
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot

RixNox said:
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot
Click to expand...
Click to collapse
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.

jebanec said:
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.
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.

Note 4 SM-N910W8 - Help

Hi
So I got this note from a seller online. The seller was forth coming in letting me know of the problem with the phone. It was stuck ultra-saving mode and the person didn’t know how to get it out of it, hence I got a good deal to tinker with.
NOW, I am stuck. As you can see from the pics below I am trying to flash it with kies. However, its unable to write.
There was an instance where download screen was telling me that I was missing PIT file, and now its just unable to write to system………
{
"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"
}
Any help will be highly appreciated.
I tried flashing TWRP, but after brute forcing it via odin, it shows “Pass” but when I try to boot into recovery, again it displays that unable to write…….so I cant even flash a stock rom.
Model # SM-N910W8
Thanks.

Flash the full recovery firmware.
Reporting via N910G.

@yashthemw, Could you please direct me to the recovery .tar for my model..... Model # SM-N910W8 - Canadian version.
Can i use any model's recovery? N910F/C/T?
Really appreciate it.
Could you also please clarify the PIT partition message i got:
Should i flash .pit file first with a recovery image (via odin) OR do flash pit first and then flash recovery.
Thanks again.

your best bet would be to google "how to flash a galaxy note 4" from there take your time you"ll see anything you need....its not that hard at the end.....your phone only need a brand new flash!!

Hey guys, so i did do a re-flash
followed this guide
https://www.youtube.com/watch?v=1TsTQeSXJBA
How To UnRoot, UnBrick, and/or Flash your Samsung Galaxy Note 4 Stock!
Got the firmware from samobile (that took 2 hours :S)
here is the log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
Any thoughts? really appreciate the help...........

Try to flash the c.f. auto root file.
There is no recovery firmware available for n910w8 .
Reporting via N910G.

HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?

samsha said:
HI
So i flashed CF root via odin and have this showing up...............I am clueless as to what to do next...............any suggestions?
Click to expand...
Click to collapse
Now try to flash stock rom.
Reporting via N910G.

Hi
I tried flashing a stock rom.............its still asking for a pit file :S
I am totally lost now what to do, anyone with ideas??
Does it matter if i use a different model (eg: f/g etc) note 4 firmware??? recovery? to flash??
Or am i stuck with N910W8 files............. :S

i think u need a pit file if u search for the pit file there should be one on xda

Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….

samsha said:
Solved!
Hi guys,
So after weeks of reading up on possible solutions, I got the N4 to work.
Here are the steps to try out, this is for the SM-N910W8 model, but you can find the pit files and your specific files online or from the links I post.
You will need 3 things;
1) Odin – I used the 3.09 version.
http://odindownload.com/Samsung-Odin/#.WCvgpeYrKMo
2) Pit file: http://www.sammobile.com/forum/showthread.php?t=30022
Search your model, for me it was the SM-N910W8.
3) Download the latest firmware from online - http://www.sammobile.com/firmwares/
Try to get the original carrier brand you have but I used a unknown one.
(on a side note, this step will take 2 hours, at-least for me it did. Damn you regular download)
2016-05-30 Unknown 6.0.1 N910W8VLU1DPE2 N910W8OYA1DPE2
Steps:
I loaded up the pit file, and the AP file extracted from the firmware on ODIN.
NOW MAKE SURE – IMP – when you load the files on ODIN have the following boxes ticked off!!
 Auto-Reboot
 Re-Partition
 F. Reset Time
Make sure your device is in Download mode and plugged in the PC as well as recognized by ODIN with a COM ID.
Press START and cross your fingers and legs and whatever you can find.
Hopefully, it went smooth and worked out.
All credits goes to the contributors in XDA and Sammobile and various other forums for providing insights and technical knowledge. You have to do your reading and above all be patient and something will work out………….
Click to expand...
Click to collapse
Hey there, I'm getting the following error: "Device does not have DRK, (Device Root Key), ...." please install DRK etc... (sorry, didn't get the rest of error msg, got distracted by wife)
I was hoping your solution would fix my problem but it didn't.
I did however find the files I needed on various sites but these bastards are all charging for it. Any ideas where I can find these files for free or if you know of an alternate solution?
COMBINATION_OYA_FA44_N910W8VLU1AOC2_OYA_3357306_RE V00_user_mid_noship_MULTI_CERT.tar.rar
https://firmware.gem-flash.com/index...tegory&id=1280