Hey everyone,
Not a total NOOB but feel like one today...
I was stock ATT S8+ and accepted the OTA Update on Friday 6/23. After restarting the device, and optimizing apps, phone is stuck on unlocking padlock circle screen. Cleared cache through recovery, but have not done factory reset because I have data I'm trying to retain.
Downloaded Odin3 v3.13 and v3.13B and have tried all the Stock firmware I can find...but Odin keeps failing with similar logs:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1301)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> apdp.mbn
<ID:0/007> msadp.mbn
<ID:0/007> persist.img.ext4
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 4636 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> abl.elf
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone, I get SW REV CHECK FAIL : [abl] 4 > Binary 3
By Googling it looks as though I need BL v4? and I'm not seeing anything past BL v3 (CRD4 CRE2)...
Any thoughts (other than factory reset...that's my last option...well that and replace it through ATT/Samsung)...
What's up with Sammie anyway? Two months ago I lost access to my micro SD that was encrypted after taking an OTA update...not a happy customer..
Thanks and sorry for previously asking in the discussion forum...
That FAIL: 4 > Binary 3 means you need a Firmware with bootloader V4. Once you're on v4, you can't go back to v3. G955USQU4CRE9 is an example of a firmware with BL v4.
hazmad said:
That FAIL: 4 > Binary 3 means you need a Firmware with bootloader V4. Once you're on v4, you can't go back to v3. G955USQU4CRE9 is an example of a firmware with BL v4.
Click to expand...
Click to collapse
Thanks Hazmad! So, how long has it been taking after the OTAs come out for the files to show up? Really trying to avoid a factory reset (at least until I can pull some pictures off my phone!)...
dinglayne said:
Thanks Hazmad! So, how long has it been taking after the OTAs come out for the files to show up? Really trying to avoid a factory reset (at least until I can pull some pictures off my phone!)...
Click to expand...
Click to collapse
Not sure, it's different for each carrier. I hope you have backups, at least an adb backup. Samsung cloud backup does a decent job too. If you have a recent backup, it might be easier to factory resset, and then restore. If you don't have any backup, you risk losing all your data.
You can try odin flashing the BL & AP from T-Mobile's firmware https://androidfilehost.com/?fid=746163614322275144 (Don't mess with the CP or CSC). If you do that without the nand erase option checked, this should keep your user data (app data, pictures, etc) intact. If you'd like, you can try the BL file on it's own first. If that doesn't fix it, then try the AP file. Flashing the AP file (without nand erase) will reset your system settings, but leave your user data. Flashing the BL by itself should leave your system settings alone.
If you can't boot to system after that, you can also try a combo BL v4 firmware. That might be a lot more work than it's worth though.
Related
I was installing android 4.4 and when I rebooted my phone I got a message saying that I'm running an authorized version of software and I need to go to a verizon store. I am not able to boot in recovery mode, it always goes back to the verizon screen. I've been trying to flash my backup ESF I made through EFS Professional using Odin but I always get this:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> efs.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> nvrebuild1.bin
<ID:0/003> nvrebuild2.bin
<ID:0/003> tz.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1).
I also get SECURE CHECK FAIL : tz in odin mode on my phone.
Any suggestions for me?
Okay for your problem, if you can go to Download Mode and your recovery back to its stock form, your last option will be flashing it through Odin. There are several method and guides How to Flash via Odin. I will link to you all the guide and try it so your phone will be back to normal. Choose only 1 method
1.) [HOW-TO] Unbrick your soft bricked Galaxy S III (+ bootloader brick)
2.) Verizon Offcial VRBMB1 Odin Files, VRBMF1 Odin Files, and VRBMF1 Update Files
Must read first the guide and download all the necessary.
If your phone gets revived, you can try this method and choose TWRP recovery and update the recovery.
Click Here If Your Ready To Root/Unlock Bootloader/Flash Recovery
Note: You know the responsibility when you root your phone, I am not nor them who created this thread have no responsibility to your phone, it is your choice.
Hi everyone,
On my S6 all of a sudden I got the blue screen saying that I need to connect it with Smart Switch for a Recovery. Smart Switch wont recognize the S6. So I tried with Odin to flash a new stock firmware but I keep getting NAND Write Operation Failed after boots.img.
This phone hasnt been used for several months, but I want to recover it because there are very valuable holiday photos on it. So the internal memory cant be wiped. I a hoping that flashing a stock rom will make the phone boot again.
Odin Log
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried various stock roms and also various usb cables. The phone was last used in the 1st week of october, so the first rom (6.0.1.) I tried to flash was the lastest prior to it (september). After that I tried August and then I jumped in time to January because I read about a rollback isnt possible. After January (the last month for 6.0.1) I decided to try the latest stock rom avaible for 7.0.
My phone is unbranded but just incase I also tried the 3 branded roms for my country (the netherlands) for vodafone, T-Mobile and Ben. All tried roms gave the same response as stated above.
I also tried to unpack the tar file and use TarCreator to create a separate Tar file for each .img. Then flash them 1 by 1 in Odin. But again the same Nand write error is given.
Odin versions that I used: 1.85 and 1.10.6
Things I didnt try yet:
Pit I kept the Pit empty on Odin. After some research it still wasnt clear to me if using a stock Pit file would not wipe the internal memory.
I hope some here could clarify that. And if I can safely use a Pit file, do i then 1st run the pit file, restart Odin and then flash the Rom. Or can i just enter them both at the same time/session?
BootloaderI found some info that said that boatloader might be corrupted? Again also about that I couldnt find a clear answer if it would wipe the internal memory. Also I am not sure where to find good boatloader files.
I've spend now 3 days on google searching solutions and trying different roms and I dont know what to try next. I hope one of the experts on this forum might know another solution or can give a clear answer on the Pit or Boatloader options.
Kind regards.
Try with Newest ODIN (3.12.7) instead of a Very Old ODIN for at Android 2.2 only (3.08) -> thedroidguru.com/download-latest-odin-odin3-all-versions-full-collection
Illutorium said:
Try with Newest ODIN (3.12.7) instead of a Very Old ODIN for at Android 2.2 only (3.08) -> thedroidguru.com/download-latest-odin-odin3-all-versions-full-collection
Click to expand...
Click to collapse
Thanks! Somehow I was under the assumption that 3,18 was higher but I see the mistake now.
<ID:0/003> 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..
<ID:0/003> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
After boot.img the phone turns off black screen, then goes back to the smart switch recovery screen. Gave it a few more tries and tried with Auto Boot enable and disabled. After the last attempt the phone screen stays black, even when plugged into the charger
Also Ive noticed that the right side of the phone now gets very hot when plugged in.
The screen still stays black. The phone wont even turn on anymore :/
Flashing stock will wipe your data anyway. There is a chance it won't format your internal storage though. If there is VERY important data, you should go to a professional data recovery service.
Mods, please move/remove this if its in the wrong area.
I updated to Oreo via OTA on my G930T. It rebooted just fine. After I used it for awhile, my phone got super hot so I decided to power it down. I turned it back on and it would only get to the Galaxy S7 splash screen and no where else. I tried factory resetting and wiping cache via recovery and flashing the stock firmware again in Odin.
When I tried to flash in Odin, I tried Oreo and Nougat and this error comes up on the Download Mode screen: "Unsupport dev_type." I made sure that I had the right firmware. The File said SM-G930T and my phone says SM-G930T on the back and in Download Mode. I even reinstalled drivers and opened odin in both admin mode and normal mode.
I should also add that in recovery it says at the following:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE-SKU
Any ideas? I'm at a complete loss.
EDIT: Here's the log in Odin after I hit start:
<ID:0/007> Odin engine v(ID:3.1207)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> emmc_appsboot.mbn.lz4
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try get regular Odin 3.13 version. i had same error when i used odin 3.12 patched one.
Yesterday my Samsung Galaxy s7(SM-g930f) had a notification for an update. While doing this update, my phone turned off, I turned it back on, a red text apeared in the top left section of the screen (at galaxy logo) saying "Binary Blocked By frp Lock". I followed a youtube guide to flash my firmware.
What I did:
Download my phone model firmware from sammobile.
Install odin v3.14
Put my phone in download mode.
Select the AP file from the Firmware.
Click start.
Odin failed. (Log below)
Error on screen now displays "Kernel rev check fail. Device 6 binary 5"
The issue with the firmware is that I do not know 100% sure what firmware is/was on my phone. I could/can not get into recovery mode to check the build/country details etc. Is there any chance I can still save the data?
Odin logs:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> param.bin
<ID:0/007> modem_debug.bin
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 3984 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
ellarddk said:
Yesterday my Samsung Galaxy s7(SM-g930f) had a notification for an update. While doing this update, my phone turned off, I turned it back on, a red text apeared in the top left section of the screen (at galaxy logo) saying "Binary Blocked By frp Lock". I followed a youtube guide to flash my firmware.
What I did:
Download my phone model firmware from sammobile.
Install odin v3.14
Put my phone in download mode.
Select the AP file from the Firmware.
Click start.
Odin failed. (Log below)
Error on screen now displays "Kernel rev check fail. Device 6 binary 5"
The issue with the firmware is that I do not know 100% sure what firmware is/was on my phone. I could/can not get into recovery mode to check the build/country details etc. Is there any chance I can still save the data?
Odin logs:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> skip file list for home binary
<ID:0/007> param.bin
<ID:0/007> modem_debug.bin
<ID:0/007> Home Binary Download
<ID:0/007> Total Binary size: 3984 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> sboot.bin
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Why did you turn the phone on while it was auto rebooting? This is part of the update process, you interrupted it, your data is lost from that point on.
Anyway, now you need to flash G930F firmware from the country your in, where is that?
The Device 6 binary 5 error means you are trying to flash an older firmware than the one which was already on your device. You can only upgrade firmware never downgrade.
The FRP lock is protection against theft and anyone trying to reset the device. Even after you flash the correct firmware the FRP will reappear, you need to input the Google account and password you were using with the phone for it to start.
cooltt said:
Why did you turn the phone on while it was auto rebooting? This is part of the update process, you interrupted it, your data is lost from that point on.
Anyway, now you need to flash G930F firmware from the country your in, where is that?
The Device 6 binary 5 error means you are trying to flash an older firmware than the one which was already on your device. You can only upgrade firmware never downgrade.
The FRP lock is protection against theft and anyone trying to reset the device. Even after you flash the correct firmware the FRP will reappear, you need to input the Google account and password you were using with the phone for it to start.
Click to expand...
Click to collapse
The update had been done for an hour. I believe. It was just a regular update like I had done x times before.
I figured out the right firmware that I need. I live in Austria, phone is in german so the country code is DBT (its on the original packaging). After attempting to flash that firmware I get a new error saying "SV REV FAIL(BOOTLOADER) device 8 binary 7". Though I believe the firmware is binary 8 too.
BL file name is "BL_G930FXXS8ETC6_CL14843133_QB29774695_REV00_user_low_ship.tar.md5".
The FRP lock thing was causing a boot loop, so I never actually got to the point of filling any details in. Recovery mode also did not work sadly
ellarddk said:
The update had been done for an hour. I believe. It was just a regular update like I had done x times before.
I figured out the right firmware that I need. I live in Austria, phone is in german so the country code is DBT (its on the original packaging). After attempting to flash that firmware I get a new error saying "SV REV FAIL(BOOTLOADER) device 8 binary 7". Though I believe the firmware is binary 8 too.
BL file name is "BL_G930FXXS8ETC6_CL14843133_QB29774695_REV00_user_low_ship.tar.md5".
The FRP lock thing was causing a boot loop, so I never actually got to the point of filling any details in. Recovery mode also did not work sadly
Click to expand...
Click to collapse
This is the firmware you need https://www.sammobile.com/samsung/galaxy-s7/firmware/SM-G930F/DBT/download/G930FXXS8ETC6/327913/
Make sure you place the correct files into Odin.
Thanks a lot, that one worked, I had tried that one before but somehow while downloading the firmware it got corrupted. Fixed it now!
UPDATE! Was able to resolve my issue. Simply just had to flash an updated firmware. Guess I updated the bootloader, or knox / whatever it is. Hate working on samsungs. Peace out pplz!
OK! Sorry havent been here in a long time since my htc desire days. ANYWAYS. Here is what ails me.
My mother buys old storage lockers, and procured a used device. A sprint Samsung SM-j337p, with firmware J337PVPU1ARF1. Obviously the phone was used, and indeed was google account locked. My goal was to unlock the device, so my mother can do with it what she likes, sell it or use it. I feel somewhat ashamed I may have broken it.
So here's what happened. I forgot about xda, and was frantically searching for ways to achieve my goals. This is how I found the original firmware (I the have files). I also came across combination files (COMBINATION_FAC_FA80_J337PVPU3ASC1_FACFAC_CL13704061_QB22911276_REV00_user_mid_noship)
So being frustrated not finding a work around or working solution to unlock the device from it's previous google account. I odin flashed the combination file J337PVPU3ASC1. It did frp unlock the device. Now however I cannot reflash the original firmware back. Odin fails to flash. The phone does boot, and the combination rom seems to work fine. I would like to try to flash this back to original condition now though.
While trying to odin flash back the firmware J337PVPU1ARF1. Odin fails on recovery.img (I believe, it moves fast, it's last file I see being flashed before failure.) I get the error message in download mode of
Code:
KERNEL REV. CHECK FAIL. DEVICE:2, BINARY:0
Code:
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestions? I know it was a stupid thing to flash that combination file, It was late, and I was being tested. Any help appreciated.
where u got the updated firmware from?