I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
I'm in the same situation exactly. At the moment I'm trying to download UK 5.1 to play with odin once again.
did you manage to fix it?
BettlePimp said:
I was using stock firmware and all of a sudden today the phone stuck into a boot loop. I flashed the stock firmware all the way back to 4.4.4 with Odin but right after the successful message I get on odin the phone restarts and it gets into the same boot loop. I suspected it might have been an issue with the partition since when I first got the phone 6 months ago I used a pit file in odin (I know I shouldn’t have) but the phone still worked fine. Now I googled the N910F+pit file, downloaded the first pit file I found, flashed it together with the kit kat stock rom but the results are still the same. I’ve tried flashing the stock lollipop rom for my Country and different countries with the same result. I have also tried flashing CF-Auto-Root and TW but odin gives an error and I get an error on the phone as well. One error that I have gotten which was not consistent since I can’t reproduce the result was “Custom binary blocked by Reactivation Lock”.
I would really appreciate any input.
Click to expand...
Click to collapse
It looks like your problem is that you forgot to turn off the samsung activation lock before flashing. If you forgot what that is see this I have not used this feature on my phone; however, I would suggest wiping with odin then flash the official stock ROM for your phone that you previously had on it when it did work, hopefully it will boot then login to you samsung account when it asks you about the reactivation lock. There are some activation lock bypass methods out there if you do a quick google search. Hopefully this will point you in the right direction.
The reactivation lock is indeed on. "Reactivation Lock(KK): On"
I have no way of turning it off since I'm stuck in a boot loop no matter what firmware I flash through Odin.
Any other suggestions?
I have same problem on my SM-910H
This problem was after updating 5.1.1 and isntallind micro-sd card (128gb)
In 4-5 days after this, bootloop began.
I deisntalled micro sd, checked it in computer for mistakes, fixed it and after this phone worked fine.
Today same problem, but when I deisntall micro-sd my problem does not go away.
I downgraded phone to 4.4 - does not help
Data wipe, cache wipe etc - does not help...
Waiting for solution from proffesionals (
update^
I've found 4 file Factory firware and tried to falsh it
What does Odin say:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> 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> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Do this, it worked for me. In ODIN, just AP/PDA Autoroot md5 file. It will not be successful and you will get "FAILED" message. Disconnect the phone from PC, pull out battery. Reinsert the battery and boot.
The same happened to me.
To all with this problem. My history:
1. Suddenly my stock device go in bootloop
2. Tried to flash it with official software it does not help
3. Tried to flash it with 3 or 4 file service firmware - did not help
4. Service center (not official, that was service center of my internet market) falshed it with some firmware and sad do not update it. It helped for 2 days.
5. They replaced the motherboard. Only this can help.
So, if you have bootloop in your stock device - try to falsh it with firmware if it does not help - take it to service center and say that they do not spent their and your time and change device or mother board.
Now its ok, working fine.
Wrote it because I spent a lot of time to repair it and maby it will help to some one.
Related
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
AhellHound said:
A couple of days ago I rooted my Galaxy S4 from AT&T, and used SafeStrap as a recovery tool. After, I attempted to partition a ROM slot with SafeStrap, but it said I didn't have enough room.
I then installed the Cyanogenmod ROM, but apparently I installed it incorrectly (maybe over the stock ROM, not sure). After, I booted my phone but it said that the recovery failed, and if I continued the screen would be horribly pixilated with bright purplish squares and stripes. Through SafeStrap, I went to ('wipe' or 'restore') and then used the advanced option, and then clicked the box marked 'System' and 'Data', which I now horribly regret. I had thought that they would be replaced, not completely wiped. I attempted to use a backup, but I had no luck.
Then the boot loops came.
For about 9 hours straight, I've been researching and troubleshooting my phone with Odin, stock recovery tool (Hold down Volume Up and Home button on start up), and tried custom ROM's, as well as a Stock ROM.
Through the boot menu, I've wiped the cache data and the partition data (I believe that's the name), then attempted to install custom ROM's with no luck.
I then downloaded a Stock ROM (http://forum.xda-developers.com/showthread.php?t=2502003) and used multiple versions of Odin with the original Samsung USB cable. I've also re installed the drivers multiple times. After trying Odin, I receive "FAILED (Auth)" messages.
Ever since I deleted the 'System' and 'Data' from the phone, Samsung's 'Kies' won't reconize the phone, but will attempt to install firmware if I try to through the 'Tools' menu and 'Firmware Upgrade and Initialization'. After entering the model number and serial number, I accept the lose of data messages and give administrative access to the program. After, the program freezes in a dark-gray tint and I must use task manager to close it.
At this point, on start up the phone will only go into download mode, and not the boot menu mode. The message that is shown is "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again".
If this post was too long, I apologize, but I'd like to give as much info as possible, as other people post very short posts that give no information at all.
If the phone is stuck in a 'soft' brick, I'll need to purchase a new one, as my phone is vital to my work and family communication, which will be unfortunate.
So, how would I go about restoring functionality to my phone, though stock ROM or custom?
Thanks for anyone who took the time to read this, and to anyone whose willing to share some advice!
Click to expand...
Click to collapse
Use Odin 3.07 Download the MF3 Firmware from https://mega.co.nz/#!WEEzSA7Z!aB46731_AwM7P83eMdDlmFYd1hUZfFBcQAZjc1X7wAE And put all the extracted files in the correct spot
compucanton said:
Use Odin 3.07 Download the MF3 Firmware from (your link) And put all the extracted files in the correct spot
Click to expand...
Click to collapse
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_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> BOOTLOADER_I337UCUAMF3_812098_REV06_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> MODEM_I337UCUAMF3_812098_REV06_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> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
AhellHound said:
Thanks for the reply!
After attempting this, it failed with the below message:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PLATFORM_I337UCUAMF3_812098_REV06_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> BOOTLOADER_I337UCUAMF3_812098_REV06_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> MODEM_I337UCUAMF3_812098_REV06_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> CSC_ATT_I337ATTAMF3_812098_REV06_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
The phone's status on the top right when in download mode is as followed:
Code:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURSRT MODE enabled
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Nurmi_CEO said:
I don't know anything about safestrap, but can you get into safestrap recovery and flash another recovery program like CWM or TWRP? From there you can wipe the phone clean and "mount usb storage" to transfer a custom rom to load and start fresh.
Click to expand...
Click to collapse
No
For future reference as posted in both the SS development thread and QA Thread OPs, Cyanogen and the like is not compatible with SS
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------
Also, if you are unable to restore with Odin and the MF3 files, I suggest mobitechvideos. They can possibly J-tag it.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
HELP NEEDED! soft brick at&T s4 i337
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
gtrijoe said:
hey i recently upgraded my at&t samsung galaxy s4 sgh-i337 from stock mf3 to stock 4.3 mk2 then upgraded to 4.4.2 nb1 then to 4.4.2 nc1 everything worked perfectly. then i decided to flash custom roms i succeeded to flash multiple roms via safestrap but then i flashed a rom and i got a msg saying that the firmware is not recognized by at&t probably because the kernel was different so i tried to flash stock mk2 again however i stupidly forgot to wipe data/system in recovery and odin failed during the flash and i recieved a msg saying firmware upgrade encountered an issue please select recovery mode in kies and try again. kies doesnt connect to the device and i dont know what to do please can someone assist me!!!!
Click to expand...
Click to collapse
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You can't flash mk2 any more since you've updated to nc1. You can however flash the nb1 tar file and get your phone working again.
http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Dude, you totally saved me. I soft bricked my galaxy s4 and tried everything to get it back up. couldnt get anything to take on it. Until I found this and I pushed it through via Odin 3.07 in the PDA slot. It took and I am back up. Much thanks my man
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
morphius2036 said:
Is there a download with the NC1 stock flash? I am soft bricked at the Custom boot screen and can get to Download mode but that is all. I have safestrap but won't post past Samsung Splash screen with Unlock on it.
If no option how can I hard brick this phone so employer won't be able to turn it on?
Click to expand...
Click to collapse
There's a nb1 tar file in the general forum. Use that.
Sent from my Nexus 5 using XDA Free mobile app
Here is my full story:
I bought my phone locally (never used) and the phone came with a Fido (Rogers alternate company) sim card but I never used that sim card inside the phone. I discarded the Fido sim and inserted my Koodo Sim (Telus alternate company)
I started with G935W8, on my phone box it says G935W8VLU1APG1 I was at 6.0.1 with latest updates in Canada, I wanted to try the official stable nougat ROM by ambasadii for SM-G935F .
After going through all the steps I find out that I do not have network connection when I boot to system. I asked on the ROM thread and was told "You should not have chosen the option in aroma to flash" which I don't know what it means and that I need to just flash the BL and Modem for Rogers.
I downloaded Rogers firmware and XAC Canada for G935W8 firmware to try. I extracted only BL and CP and tried to flash them with ODIN. It failed with both rogers and XAC and I get the following error. I tried flashing CP only and it worked but when I rebooted I still have no network. I tried flashing CP, BL and CSC and it didn't work. I checked and my IMEI and baseband are "UKNOWN".
I checked my root status and it said no root, I checked and I did not have supersu which got me confused because I thought it came with ROM. So I went and flahsed SR3-SuperSU-v2.79-SR3-20170114223742 with Odin and now root checker says rooted.
I tried to back up with 2 different EFS software but they both can't access EFS.
I tried this fix (Guide A) but it failed (I tried for G935W8, should I try for G935F since my phone is on that ROM?). I did not try guide B since I can't backup EFS and I don't want to mess things up.
This is my current phone info using the app
I wouldn't mind paying for your time to help me if you can guide me on skype or just writing the steps.
Will appreciate any help.
Update: Backed up EFS using TWRP and attempted the fix. I got stuck on Factory Binary unfortunately, it keeps looping.
you do not have a proper modem flashed! your baseband should show DPLT too, otherwise you won't get any connection...
try if flashing latest Helios rom works, it should flash the modem also! afterwards you can return to your existing rom!
if not, you have to search for DPLT modem.bin according to your CSC and flash it with odin!
hope this helps!
Sent from my SM-G935F using XDA-Developers Legacy app
Update after messing around in recovery and factory resetting factory binary started working and I restored my IMEI!!
Now I have to figure out how to go to stock
TML1504 said:
you do not have a proper modem flashed! your baseband should show DPLT too, otherwise you won't get any connection...
try if flashing latest Helios rom works, it should flash the modem also! afterwards you can return to your existing rom!
if not, you have to search for DPLT modem.bin according to your CSC and flash it with odin!
hope this helps!
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for the advice, I was able to get IMEI and connection but I am in factory binary mode. Should I try the ROM you mentioned or try to flash stock now?
Tried stock
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin engine v(ID:3.1203)..
<ID:0/009> File analysis..
<ID:0/009> skip file list for home binary
<ID:0/009> param.bin
<ID:0/009> Home Binary Download
<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> sboot.bin
<ID:0/009> cm.bin
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I had the same problem and this is the FW that worked for me. https://www.sammobile.com/firmwares/download/113261/G935W8VLU2APK3_G935W8OYA2APK3_TLS/
promaster9500 said:
Update after messing around in recovery and factory resetting factory binary started working and I restored my IMEI!!
Now I have to figure out how to go to stock
Click to expand...
Click to collapse
can you help me please. I have the same problem with my G930F. I had the superman-rom.zip and installed it through the manual on xda and now I have an unknown imei / Baseband and no sim. How did you solve this? I've been struggling with it for days. My thanks already are huge.
1eSkip said:
can you help me please. I have the same problem with my G930F. I had the superman-rom.zip and installed it through the manual on xda and now I have an unknown imei / Baseband and no sim. How did you solve this? I've been struggling with it for days. My thanks already are huge.
Click to expand...
Click to collapse
REcommended step is Just install the latest stock from sammobile(its too slow) or from here samfrew.com which is too fast.
but you can try below
i have lost IMEI as well when i update my BL boot loader. and then i installed CP provided by someone and got it back,
check page 156 and 157.
https://forum.xda-developers.com/s7...-devbase-v4-1-multi-csc-safe-t3591647/page157
just update both bootload and CP.
Thank you but I have already fixed couple of days ago. I Flash The csc and de module from the Stockrom Everything working Again.
I had used TWRP to install SuperSU to root. This seemed successful, but a day or two later the phone had powered itself off, and on power-up loops displaying the tiny red "Custom binary is blocked by FRP Lock" message. The phone will boot into download mode, but won't enter recovery mode.
I tried repeating the install of TWRP using ODIN 3.12, but now that fails. Tried installing factory images (\BL_G550T1UVU1APF1_CL8180604_QB9902404_REV00_user_low_ship.tar.md5 etc.) w/ ODIN, and that fails too.
Is this an indication I don't have the latest image files? ODIN messages below:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/004> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Made some progress
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
BHarris said:
Reviewing other threads I found a not that talked about installing only the "AP" file using ODIN. That seems to have worked.
Click to expand...
Click to collapse
what worked? and what firmware. I have 2 on5's one sm-G-550T and a sm-g550T1 that both ended up with the "custom binary blocked by FRP lock" on the same day..
Please help!
I just tried a bin I downloaded from S U site and it didn't work. Gotta love the On5 lol.
Custom Binary Lock
The same happened to me: i have not found a complete solution, the closest i get to anything is; i put the On5 in Odin3 v3.12 and select the AP option and putting the recovery.tar file and running it. it goes good till its done and the result is Custom Binary (recovery) blocked by FRP lock in green letters. but still no success. i have tried trwp recovery, the home.tar file, each file by them selves and having trouble. i may not be an expert at this type of programimng but i pick things up quickly if there is any solution to my problem please let me know. thx............ by the way i have also tried kies and wont connect to it as well
Same Problem FRP Blocked Bootlooping
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
SeleneKnightress said:
I did all the same as you and have the same problem. Everything was fine till the phone got restarted.
XDA HEEEEEEEELP!!
Click to expand...
Click to collapse
You need to reinstall the firmware using Odin. Then, when you root again, you need to make sure you have oem unlock and usb debugging on in the developer options. Not having those on and rebooting when rooted cause the custom binary problem.
Hi, tried to flash my a5 sm-a520f from 7.0 to 6.0.1 everything seems fine then it fails after cm.bin i've tried using A520FXXU1APLL VOD United Kingdom (Vodafone). and A520FXXU2AQF5 XEU United Kingdom.
I've searched but can't find a definitive answer. Tried as others suggested by changing ports several times and downloaded a second lot of firmware both for my phone and get the same.
Any help please?
Thanks
Below is log from the last time.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
<ID:0/006> skip file list for home binary
<ID:0/006> param.bin
<ID:0/006> Home Binary Download
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> cm.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
So no one can help me?
I found out it's the bootloader and found posts about taking all the .bin files out before flashing but that would leave the whole of the BL file out which is like 4gb the bulk of the whole thing. I've tried 5 different UK roms. Tried using CSC instead of home_CSC and that time after sboot.bin in place of cm.bin there's param.bin and no cm. The phone does say odin mode at the top.
Found loads of posts saying because 7 has a different bootloader than 6 it can't be done but many people have done it successfully without a problem. Is there a way to flash it a different bootloader to downgrade to 6.0.1.
I have done a lot of searching about 15 hours worth but can't find the right solution.
I can't get into the phones settings because like a prat i did a factory reset without knowing the password for the email address. Bought the phone, got the login passwords/pattern so was able to use it but it still had sellers gmail and couldn't get in touch with the seller, still can't. Decided to do an frp unlock which i've done many times for people but never on android 7.0. Found out after trying all other methods i had to downgrade which brings me to this problem.
The phone never had/has the the usual startup logos for service providers so i don't know if that means it came without bloatware. I bought it network unlocked, he had it on o2. I've tried stock 6.0.1 firmware for o2, Voda, EE, XEU & BTU.
Please help, already receding don't want to make it worse!
Thanks
Hi. I guess you're on either A520FXXU3 or A520FXXU4 firmware., and that's why you won't be able to downgrade to any lower binary version. Normally it works fine to downgrade without the .bin files as you would still use the updated sboot and baseband ,but with older system files without any problems. All good for daily use, but not for frp reset.
Problem is that it won't help you to bypass frp because you still have the updated binary version.
What you need is a factory combination firmware with the same binary version that you have installed.
That would make it possible to flash it, enable oem unlock to remove the frp protection, then flash a full 4-file firmware with factory reset.
Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks
skg76 said:
Hi thanks for replying. My firmware version is a520fxxu4brb1. Do you mean the combination file has to hav u4 in its name? Will this one work? A520FXXU4ARA4
Thanks
Click to expand...
Click to collapse
Yes, afaik it should work.
Sent from my Moto G5 using Tapatalk
Did you manage to get this working? I can't find any decent links anywhere for the A520FXXU4ARA4 combination file, found one on pakfirmware but md5 was invalid and wouldnt accept in odin..
Sorry mate just seen your message. Yes it did work was a pain though, took a week. I think i found a link on boxwares.
link is here. clicking download leads to a fast google download.
https://shell.boxwares.com/Download.aspx?L=4474
If link is gone just google the combi and look for shell.boxwares link.
Afterwards i just used any u4 stock rom and it worked. Done like 30 phones with this method since.
Odin fail
Help!!
I have the same problem..i've tried everything even turned the anti virus off and nothing works..if i flash a different costum rom would it fix the problem or should i downgrade the firmware to nougat couse last version i had installed was oreo..
Hey folks, not quite sure where to turn from here or if this phone just goes to the dump...I was looking originally to unlock the AT&T S7 Edge I have and give it to a coworker who is on Verizon. Come to find this is a much larger task than I anticipated.
Device info: Galaxy S7 Edge AT&T SM-G935A
I attempted to follow the guide which started here: https://forum.xda-developers.com/verizon-s7-edge/how-to/odin-stock-nougat-firmware-t3570156
I downloaded the Samsung drivers, Odin v3.12.3 Patched, and the corresponding VZW firmware which I was under the impression was correct, from https://updato.com
I loaded Odin and the phone, ran the installer, and it looked kosher. The device passed, and it began to reboot. However, after that, it got stuck in the nightmare of recurring boot. I entered recovery mode, cleared cache and tried doing a factory reset, to no avail. Device keeps rebooting. Tried re-flashing firmware, no luck.
Where I got to:
On the downloading screen on the Edge:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-6935U <- (this seems wrong given it was AT&T, but I could be misinterpreting as I requested to have the device unlocked from AT&T and the person attempted activating on Verizon before all this)
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
WARRANTY VOID: 0X0
QUALCOMM SECUREBOOT: ENABLE
RP SWREV: B8(2,1,1,1,1) K8 K8
SECURE DOWNLOAD: ENABLE
If I attempted to rerun any of the dozen or so firmware versions I've tried, I always got the following two errors:
In 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..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<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> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the device:
SW REV CHECK FAIL : [aboot] Fused 8 > Binary 4
After several hours I managed to get the phone semi-working.
I installed the G935UUEU8CRJ2 firmware from the web. It's the only one it would take as far as I can tell.
However there are two issues:
1. The device keeps restarting after 1-2 minutes of being powered on.
2. The firmware seems to be somehow Sprint? That doesn't make sense...
Android version: 9.0.0
Samsung Experience version: 9.0
Baseband version: G935UUEU8CRJ2
Kernel version: 3.18.71-13710210
Build number: R16NW.G935UUEU8CRJ2
Knox version: 3.1
I've tried running the factory reset from the GUI, but that didn't fix the restarting. Using the reset cache and factory wipe also did not fix the issue. Furthermore when booting into recovery mode initially it attempts to do a system update, then up pops the dead android with x's for eyes and the notorious yellow triangle, yet I can still access recovery mode after a few seconds.
Any suggestions?
Try this: https://www.mediafire.com/file/bzgzxqwafgpsk4c/G935AUCS8CRJ2_StockROM.zip/file
Leone/kyleproxx said:
Try this
Click to expand...
Click to collapse
There's a password on the file.
Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?
Leomacomp said:
Update: I found the password. The ROM worked. It's back to AT&T. That solves my softbricking issue, but the original idea to switch it to Verizon is still at hand.
Is there any way to successfully do this?
Click to expand...
Click to collapse
I dont know what to do to switch to verizon
Leone/kyleproxx said:
I dont know what to do to switch to verizon
Click to expand...
Click to collapse
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!
Leomacomp said:
No worries. I actually found the correct VZW ROM (For any of those looking in the future it's: G935VVRU8CRJ3-StockROM-G935V-(-BIT
I loaded this using "Odin 3.13.1 Patched" (The SHA256 bypass). It installed successfully and works now on Verizon's network.
Thanks for the assist!
Click to expand...
Click to collapse
Your Welcome :good:
Leomacomp said:
There's a password on the file.
Click to expand...
Click to collapse
Hello mate can you plz post the file pass TIA :good:
fabian108 said:
Hello mate can you plz post the file pass TIA :good:
Click to expand...
Click to collapse
The password is www.samkey.org/forum
Ps: and yes the actual website name is the password.
Thanks for solving my issue
I found this thread searching for a way to restore my AT&T branded Samsung Galaxy S7 Edge(SM-G935A), which I thought I might have bricked since it was stuck in a boot loop. Using the stock rom I found on this thread, I was able to get the phone going again. I spent many hours searching and trying different roms, and this was the only one I could get to work. It was FRP locked, but I knew the password. Just could not get past the loop to enter it.
Thus, I wish to say thank you for posting this thread, without it I would still be looking at a boot loop!
friends will have one for bynario 9 I have the same problem please