I updated my phone Samsung S4 Mini GT-I9195 today and after the update it's completely locked and any attempt at fixing it has been unsuccessful so far.
When I restart my phone it gives the message "Unfortunately, the process com.android.systemui has stopped". After I click that away the screen has a message "The device has been updated." and is completely stuck on that.
I can't connect it to Samsung Kies as it tells me the connected device is locked and I have to enter password on the connected device, but that's impossible because the phone is completely locked. The firmware emergency recovery option is also not available.
I don't have any access to the files on my phone either. I can open the file directory but it's not showing anything, I need to have the main screen on my phone opened/unlocked for it to do so.
Other searches on the web have for the most part been unproductive and I'm now at a complete loss for how to fix this. Any help will be greatly appreciated.
Cheers,
Axel
Axelzzz said:
I updated my phone Samsung S4 Mini GT-I9195 today and after the update it's completely locked and any attempt at fixing it has been unsuccessful so far.
When I restart my phone it gives the message "Unfortunately, the process com.android.systemui has stopped". After I click that away the screen has a message "The device has been updated." and is completely stuck on that.
I can't connect it to Samsung Kies as it tells me the connected device is locked and I have to enter password on the connected device, but that's impossible because the phone is completely locked. The firmware emergency recovery option is also not available.
I don't have any access to the files on my phone either. I can open the file directory but it's not showing anything, I need to have the main screen on my phone opened/unlocked for it to do so.
Other searches on the web have for the most part been unproductive and I'm now at a complete loss for how to fix this. Any help will be greatly appreciated.
Cheers,
Axel
Click to expand...
Click to collapse
ohk download stock firmware from "samsung updates dot com" or "sam mobile dot com". ( Google for exact website address)
then flash it with odin .
search on google about odin if you don't know what it is.
Good luck
Thank you for your reply.
I have been trying to fix it with Odin but I'm running into problems. Whenever I try to flash it with odin I get the following error in my phone: SW REV CHECK FAIL : FUSED 2 > BINARY 1
Also in Odin 3.09 at the top it shows my phone model is I9505 while my phone is I9195.
I have tried it with both Odin 1.85 and 3.09, in both it gives the following:
<ID:0/006> Added!!
<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> SingleDownload.
<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)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flashed 4.4.2 instead of 4.2.2. Apparently it's not possible to downgrade the firmware version. Had some other minor problems along the way but they are all easily fixed with google searches
Related
First off, I am a complete Android/PC noob (have used solely apple products until this phone, and an Acer aspire comp. i got 2 weeks ago).
I have been using the Exhilarate with android GB, and wanted to upgrade to ICS. I downloaded Samsung Kies, backed up my phone, and began the firmware upgrade, however once the progress reached 70%-80%, the device came unplugged. after restarting the phone, it is stuck on a screen that says:
upper left corner of screen:
Odin Mode
Product Name:SGH-I577
Custom Binary Download: YES(2 counts)
Current Binary: Custom
Center of screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
When I reconnect and attempt to do the emergency firmware recovery using kies, it completes the downloading of the file for firmware emergency recovery, but once it moves on to "proceed to firmware emergency recovery", it stops working (the progress bar is stuck at 0%)
After waiting a little while, the emergency recovery closes, and a message shows saying:
Notice-F PC failed to recognize the mobile phone. Please follow the guide shown below to try again
I gave up on kies, and did some searching of my own. I downloaded the latest version of Odin, as well as the Clockworkmod-Blaze-4G.tar. I made sure there was nothing Kies-related running on my computer, opened up Odin, loaded the clockwork .tar, turned the phone on into download mode (it says Warning!, asks if I want to go into download mode, and then returns to the Odin Mode screen once I say yes). the device is shown as added to odin, I clicked start, and it seemed to be working, and then a big red FAIL appeared in the top left box, and the message box said:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried re-installing drivers, different versions of the .tar file (i think they are diff. versions, but not completely sure) rebooting the device many many times, among other things. If anyone has any idea of where to go from here, i would be EXTREMELY grateful.
thank you guys
One more thing
OP here still:
I tried again with a different version of Odin. this time it failed once again, but got a bit further. (everything else was the same):
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
also, I have only checked the Auto reboot box in odin. All others were left blank
I am having a very similar problem with my SGS3 - were you able to solve your problem? If so, can you share how you did?
hello
I have the Samsung Galaxy Note 10.1 in 8013 16 GO there, exactly.
I intallé anderoid jelly bean 4.1.1 OTA and did not finish the tablet and restart nonstop. I started handling but nothing goes as planned, ODIN said fail Action! and my tablet is in download mode. And when I reboot I have a small andriod man with the percentage bar with the screen that pops by gray bars. suddenly I think I scrub the tablet and I do not really know what
thank you in advance for helping me because odin know my tablet (the tablet comes into download mode and not in recovry mode) it may not complete the installation with the following message:
<ID:0/006> Added!!
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
3achour said:
hello
I have the Samsung Galaxy Note 10.1 in 8013 16 GO there, exactly.
I intallé anderoid jelly bean 4.1.1 OTA and did not finish the tablet and restart nonstop. I started handling but nothing goes as planned, ODIN said fail Action! and my tablet is in download mode. And when I reboot I have a small andriod man with the percentage bar with the screen that pops by gray bars. suddenly I think I scrub the tablet and I do not really know what
thank you in advance for helping me because odin know my tablet (the tablet comes into download mode and not in recovry mode) it may not complete the installation with the following message:
<ID:0/006> Added!!
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Re download factory rom and flash again in odin.. . You can also go in the recovery and clear cache and so on.. This will often stop a boot look . But it looks like you have a bad d/load
I'd agree with that.
I find it best to download the roms from Sammobile as they generally provide an MD5 sum you can check to make sure its not a bad download. Especially when using ODIN 4.03/07... ODIN 4.03 does the check before it flashes and ODIN 4.07 checks when the .tar file is selected.
temp
how temp for odin finish their installation
I think it's hang on: "<ID:0/006> NAND Write Start!! "
erica_renee said:
Re download factory rom and flash again in odin.. . You can also go in the recovery and clear cache and so on.. This will often stop a boot look . But it looks like you have a bad d/load
Click to expand...
Click to collapse
I have not access in the recovery mode
3achour said:
how temp for odin finish their installation
I think it's hang on: "<ID:0/006> NAND Write Start!! "
Click to expand...
Click to collapse
odin did not finish the installation process about 2 hours and even post thank you for helping me
You need to download the rom again to see if it's not a corrupted copy. Use a PC to download it from sammobile.com.
If the flash file you are using is corrupt you can flash it til this century ends and it won't work...
If it still doesn't get past nand write then I believe you may need a pit file to repartition your internal memory. THIS IS A VERY DANGEROUS OPERATION. Make sure you have the correct pit file and if possible get it with an MD5 checksum so you know there is nothing wrong with the downloaded file. It MUST be for your device or bricking may occur, it MUST not be corrupted or bricking will occur.
Good luck and remember, you have been warned...
So I have the AT&T variant of the Samsung Galaxy S7 (SM-G930A). I had installed root using a tutorial I found on these forums and everything went great for months. I started getting some errors after automatic updates ran (the Play Store kept crashing) so I tried to flash back to the stock firmware. Doing this, I ended up at the "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software" page.
I've tried using Smart Switch, but the application tells me that my device is unsupported and entering my model and serial numbers into the software just causes it (the smart switch app) to crash.
On the Android Recovery screen, I can see that I have the G930AUCS2APH1 firmware running Android 6.0.1. I believe I have found the original stock firmware for this version here: https://forum.xda-developers.com/at...rmware-stock-sm-g930a-ph1-odin-files-t3458890
But whenever I try to flash anything other than CP to my phone in Odin, I end up with a FAIL! (Auth) error.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried using different USB ports and cables, as well as a few different firmwares (admittedly, even some that are not the PH1 update) but all end up with the same result.
Can anyone help me out? I believe I'm doing everything right but I cannot get my phone up and running again for the life of me.
OKAY so I believe I fixed the problem before anyone could get to this so this is for anyone that stumbles across this thread. I was able to successfully flash the PK1 update to my phone. I found the firmware here: https://drive.google.com/drive/folders/0B_lsL4sQwjajY2dxSkFjYmw4OGM
Just flashing the AP package seems to have worked fine.
New to messing with android and odin so bear with me.
I have confirmed the target device is a verizon phone model and I am using a verizon stock firmware.
I had a friend give me a Galaxy S6 SM-G920V as he wasn't using it anymore and my S5 bit the dust. I got a sim card put in it and activated. During the init the phone lost power and bricked the rom. So, I got the latest odin build and what I thought was a good firmware build and flashed the phone. I still get the startup failed message when I boot. So I called verizon and got some information about their specific firmware and started searching again. I found this thread that claimed to have the firmware I needed.
https://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
I have tried to use Smartswitch and verizon utilities to detect and repair my device but neither of them will recognize my phone is connected even after installing the samsung drivers.
My process for flashing the device are as follows:
Power on phone into download mode.
Select AP and load the .tar.md5
Check boxes for auto reload and F. Reset time
Connect Phone, it gets recognized
Click start
The firmwares I have tried:
ODIN version: 3.10.6
1st attempt :
Android 6.0.1
PDA: G920VVRS4CQA3
CSC: G920VVZW4CQA3
result: PASS, does not boot, teal screen of death with startup failed. flashed a second time and now its boot looping.
2nd attempt:
Android 5.0.2
PDA: G920VVRU1AOC3
CSC: G920VVZW1AOC3
result: NAND write fail. Flash aborts.
Is there something I am doing wrong here? Someone with more experience please correct me.
Also here is the log for the whole operation for the 2nd attempt:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mwdaue01 said:
New to messing with android and odin so bear with me.
I have confirmed the target device is a verizon phone model and I am using a verizon stock firmware.
I had a friend give me a Galaxy S6 SM-G920V as he wasn't using it anymore and my S5 bit the dust. I got a sim card put in it and activated. During the init the phone lost power and bricked the rom. So, I got the latest odin build and what I thought was a good firmware build and flashed the phone. I still get the startup failed message when I boot. So I called verizon and got some information about their specific firmware and started searching again. I found this thread that claimed to have the firmware I needed.
https://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
I have tried to use Smartswitch and verizon utilities to detect and repair my device but neither of them will recognize my phone is connected even after installing the samsung drivers.
My process for flashing the device are as follows:
Power on phone into download mode.
Select AP and load the .tar.md5
Check boxes for auto reload and F. Reset time
Connect Phone, it gets recognized
Click start
The firmwares I have tried:
ODIN version: 3.10.6
1st attempt :
Android 6.0.1
PDA: G920VVRS4CQA3
CSC: G920VVZW4CQA3
result: PASS, does not boot, teal screen of death with startup failed. flashed a second time and now its boot looping.
2nd attempt:
Android 5.0.2
PDA: G920VVRU1AOC3
CSC: G920VVZW1AOC3
result: NAND write fail. Flash aborts.
Is there something I am doing wrong here? Someone with more experience please correct me.
Also here is the log for the whole operation for the 2nd attempt:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<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> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You can't downgrade the S6 back to 5.0.2. Verizon locked the bootloader so you can't downgrade it to 5.0.2 and only around 5.1.1 around OK1 to QD1. (5.1.1 - 7.0)
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!