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 ?

[Q] Try to go back in 4.2.2 but Odin Fail !

Hi,
I have a problem with my GS4.
I try the last I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar rom but like any other rom with new locked bootloader, i can't use the stock kernel because with it, all my apps crash on startup, with many many error messages.
But there is no custom kernel actually.
So i want to go back to 4.2.2.
But Odin fail every time i try to flash the I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar rom.
{
"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"
}
:crying:

By any ideas dont you have the famous KNOX on Your rom actually? It must be due to that i think.
Why do you want to Côme back in 4.2.2?
Ans Yes there us at least One custom kernel who match with the 4.3
Ktoonz kernel.
Go see on the tread of the développe or see the amazing Echoes rom ! It incluses inside! I am on actually ans lever disappointed ! In wlrst case ylu can ask to Friedrich for help.
Avoir to flash a rom stock if you can because this lne will have for dure the new bootloader ans KNOX (protection impossible to downgrade One you got it).
Édit: by the way tel me you have the 9505 version LF the s4? As me? I am on Echoes rom (best bases on Touchwizz) ans i have flash chère is a little time the MJ5 ni problème at all.BUT never flash the stock rom 4.3...si i have not KNOX.
I know that the Echoes rom dont have KNOX either .They have removed it^^
Ans it worked perfectly. I am on the version 5 actually MJ5 firmwire and MJ5 for MoDem (flash wirh Odin mobile for the 1st time no need to pc^^)

superbegita said:
By any ideas dont you have the famous KNOX on Your rom actually? It must be due to that i think.
Why do you want to Côme back in 4.2.2?
Ans Yes there us at least One custom kernel who match with the 4.3
Ktoonz kernel.
Go see on the tread of the développe or see the amazing Echoes rom ! It incluses inside! I am on actually ans lever disappointed ! In wlrst case ylu can ask to Friedrich for help.
Avoir to flash a rom stock if you can because this lne will have for dure the new bootloader ans KNOX (protection impossible to downgrade One you got it).
Édit: by the way tel me you have the 9505 version LF the s4? As me? I am on Echoes rom (best bases on Touchwizz) ans i have flash chère is a little time the MJ5 ni problème at all.BUT never flash the stock rom 4.3...si i have not KNOX.
I know that the Echoes rom dont have KNOX either .They have removed it^^
Ans it worked perfectly. I am on the version 5 actually MJ5 firmwire and MJ5 for MoDem (flash wirh Odin mobile for the 1st time no need to pc^^)
Click to expand...
Click to collapse
Hi, I'm like the same problem .. I'll have to try to go back to 4.3 ROM ?? Mine is LTE!

Not possible back to any stock 4.2.2

Please have a look on fail picture then u will see odin3 fails on aboot.mbn. So, if you want to downgrade your phone You have to remove aboot.mbn from the firmware. But KNOX will set to 0x1 byitself.

BOOT LOOP/Odin Fail - Has anyone ran into this problem (stated below) with odin while trying to return to stock firmware? I have the SM-N910T (T-Mobile note 4) im using odin v3.10, I have currently installed NOBLE Note 7 Edge UX 3.0 and want to return to Stock firmware MM6.0 or higher. I can access Download mode and for TWRP recovery, also i can install different recoveries using odin. How can i solve boot loop and install T-Mobile Note 4 MM 6.0 Stock firmware
***Using TWRP***
Clearing data and cache, Hard resetting, different cable and port, reinstalling custom roms is not soving the problem
***INSTALLED ON THE PHONE***
NOBLE Note 7 Edge UX 3.0
Beastmode1.9.2-N910T-RAGE
N910T-mm bootloader
MM-datafix-stockrebootmenu
***This Is The Problem With Odin***
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1EPE3_N910T3TMB1EPE3_N910T3UVU1EPE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
?

The firmware may be failing when flashing aboot.mbn because of the following:
need to use a different USB cable;
need to use a different USB port;
the firmware file is not meant for the phone; or
the bootloader in the firmware is older than the bootloader in the phone.

Any reason as to why am I unable to flash a previous firmware?

Thank
{
"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 was tinkering around with firmwares the past few days because I was getting tired of my signal dropping and having to manually do the "*#*#4636#*#*" method or turning airplane mode on and off to get signal back only temporarily. I rooted my SM-N910P phone with the 5.0.1 firmware but the CM12.1 nightlies I got were based on 5.1.1. I managed to successfully flash the 5.1.1 firmware through ODIN which meant I lost my rooting capabilities.
I already made the mistake of trying to get root access back by reflashing the cf auto root via ODIN which was based on 4.4.4 but ended up just getting in a bootloop. So I had to reflash the 5.1.1 firmware which got rid of the bootloop. But now that I have it on my phone, I am unable to flash any previous STOCK firmwares. I've tried both 5.0.1 and 4.4.4 firmwares on the Sammobile website and end up getting a "FAIL!" message despite my phone being recognized on ODIN and ODIN reading the tar md5 firmware successfully under AP/PDA.
Code:
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:5)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
aboot.mbn
NAND Write Start!!
sbl1.mbn
rpm.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
I've done a master/factory reset from recovery and it didn't help as I am still unable to flash a previous stock firmware. Since I already made the mistake of flashing two incompatible files that led to the bootloop, I was hoping to just go back to the 5.0.1 firmware I downloaded from Sammobile then just getting the last updated version of CM12 based on 5.0.1.
Is there something about the 5.1.1 firmware that prevents this? If so, I think I'm just gonna stay unrooted for now until there is a viable rooting method for 5.1.1.
Current 5.1.1 firmware for the SM-N910P version: N910PVPU4COG5_N910PSPT4COG5_N910PVPU4COG5_HOME.tar.md5
5.0.1 firmware from Sammobile I've tried to flash: N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.tar.md5
Any feedback will be very much appreciated!
UPDATE: I just ended up flashing TWRP via ODIN with the 5.1.1 firmware as I remembered that ROMs and custom recoveries don't interfere with each other. Wiped the dalvik cache, cache, system and data and flashed the CM12.1 nightlies and 5.1 gapps zips via TWRP. Needless to say, it succeeded and got root access back.

FRP locked A510F (A5 2016) Android Downgrade help!!

So i'm pretty sure my phone has android 7.0 but not sure tho , if i use RealTerm to dial a number that won't help as this version of android does not allow me to hit the message or add contact so i tried to downgrade it to 6.0.1 , the 5.1.1 failed on odin so i went for the 6.0.1 and when i started flashing it failed at cache.img and i think i softbricked my phone as it gives me the error message to use smart switch and emergency recovery thing but it still can boot in download mode so now i'm searching for a fix to the cache thing so i can fix it , it if helps somehow i have an OTG cable and USB memory stick.

Bro I'm not expert but I've walked your ways. when you download the rom remove .md5 extention from the file. so that it remains with A510F....tar.
now you can open it with Total Commander and unpack contents. repack it without cahe.img into tar file and flash it back. you should be good to go. give it a try

BananaRageee said:
So i'm pretty sure my phone has android 7.0 but not sure tho , if i use RealTerm to dial a number that won't help as this version of android does not allow me to hit the message or add contact so i tried to downgrade it to 6.0.1 , the 5.1.1 failed on odin so i went for the 6.0.1 and when i started flashing it failed at cache.img and i think i softbricked my phone as it gives me the error message to use smart switch and emergency recovery thing but it still can boot in download mode so now i'm searching for a fix to the cache thing so i can fix it , it if helps somehow i have an OTG cable and USB memory stick.
Click to expand...
Click to collapse
Desable frp lock and unlock bootloader before flashing
Sent from my Samsung SM-A9000 using XDA Labs

Got lost and standed..
(reusing 'identical' thread)
Hi XDA SMEs..
I have read through every article here regarding removal of FRP of A510F. And managed to get the phone from softbrick state to working yet still locked. Currently I am running A510FXXS5CRE3 fw which is 7.0 nougat and for that I have not been able to get through with any advice on the net (realterm call, voice asistant, samsung keyboard, smartswitch USB isntall, nor HARDRESET's combination file and tool etc etc.. hence I cannot use OEM installation and USB dev mode enabled). One would say hey dude just downgrade the phone to Marshmallow right? TBH I have not been able to find working 6.0.1 fw. Am I missing some crucial basic information? Is my IMEI valid for only specific FW? I am aiming to get there stock 6 un-lock and then re-flash to 7.
When I am trying to flash in A510FXXURBDQ1 using Odin 3.13 I am getting this:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2774 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And the phone shows - Device 5 Binary 4 - which i believe is wrong firmware that i am trying to flash due to the base got bumped by flashing 7.0
Could someone help me to determine what I am missing? After hours of downloads and hours of reading i am getting a bit :silly:
P.S. > fun part is that others here has the problem but sometimes thread gets locked with statement that OP found solution in different thread .. leaves me wonder which one tho..
Thanks in advance for your advice!

UDPATE: NO this does not work Still need your help
I got passed the DEVICE 5 BINARY 4 and ended up on DEVICE 5 BINARY 3
So ok I got one of the information that I have missed. It is not possible to downgrade to MM FW which has different version of BL and Modem.
So theoretically I f I have 7.0 A510FXXS5CRE and there is no S5 MM I will have to change version first to 7.0 A510FXXU4CQE6 and then I will be able to step down to 6.0.1 FW A510FXXU4BDQ1?
Is this correct or there is even more to it?
{
"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"
}
Then I should be able to proceed with the black magic for FRP unlock. I hope.

Got the same problem now....any solution?

Sorry no good news on my side. I gave up for now.
I have managed to downgrade to different versions of 7.0 but the boot loader version change stopped my chain whereas change from A510XXFU5CRA4 to A510FXXU4CQL7 was stopped by DEVICE 5 Binary 4 (was hoping for simple solution like downgrade one by one.. silly me).
My next step (if I find courage to do so) is to hack* (unpack) the working 7.0 and doodle with content of the file (merging it with MODEM from 6.0.1 tar as it is the step on which I have failed with Odin before).. other than that I am out of ideas..
*(theoretically I do not care if I hack it and get it working with unstable cellular connection or whatever since after the FRP unlock i plan to flash stock 7.0 anyways)

Custom binary blocked by FRP lock. Can't get into download mode.

Hi.
Today I encountered a brand new problem with one of my phones. After a few restarts (problem with battery) phone started to boot in safe mode.
I couldn't set it back to normal, meanwhile I disabled Developer Options - this is probably where I made mistake (OEM Unlock turned off?).
After this, phone doesn't boot. There is little notification (Custom binary blocked by FRP lock) and then phone restarts.
I can't get into recovery mode (TWRP gone?) and even Download mode doesn't seem to work (after pressing Vol+ phone restarts again).
Visual representation
https://www.youtube.com/watch?v=R4wLcckvtnQ
Any of you encountered this problem already? Any solution?

I did absolutely nothing, but I can boot into download mode now. So my problem finally remains something I can find on the web.
I tried to flash TWRP once again (to backup data), but I'm getting error.
<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> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On phone it looks like this:
{
"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"
}
So - what to do now? What is the best possible scenario? What I understand all I have to do is to unlock OEM.
Can I save data on phone somehow? If not - what I should do next? I already downloaded stock firmware, but I'm waiting for your response just in case there is something I can do.

If you downloaded the corret firmware installed the correct samsung drivers on your pc then just follow the instruction on any thread on flashing stock ROMS. MAKE SURE YOU HAVE THE RIGHT FIRMWARE.

Yeah, I know a thing or two about flashing ROMs and solved multiple problems already, that was something new. I never stuck before without access to DM.
Anyway, the problem is solved. I decided to sacrifice my data and flash stock rom to unlock OEM.

i have done all,so how i will repare it