SM-G935T bootlop after succesful flash with odin - T-Mobile Samsung Galaxy S7 Edge Questions & Answer

Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards

bassist82 said:
Hi guys, I tried to factory reset my phone by flashing the latest firmware. These are the files that I used:
AP_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G935TUVSBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G935TUVSBCTA2_CP14916856_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar
CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_TMB_G935TTMBBCTA2_CL14365146_QB28658134_REV02_user_low_ship_MULTI_CERT.tar.md5
I am a noob and I accidentally flashed the HOME_CSC file in the USERDATA section but every other file was in its place. Then after the successful flash, the phone restarted and entered a boot loop with the galaxy s7 and t-mobile logo. Also, I could't boot into recovery. It shows " recovery booting..." and stays there. After that, I tried to flash several different firmware versions but I always get errors like "fw ver check failed" and stops flashing. I only managed to reflash the first firmware again with success but the phone still doesn't boot. Does anyone know what is causing the problem? Am I using wrong firmware? can anyone help on this?
regards
Click to expand...
Click to collapse
What country are you in?

cooltt said:
What country are you in?
Click to expand...
Click to collapse
USA

bassist82 said:
USA
Click to expand...
Click to collapse
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.

cooltt said:
Oops! Very temperamental phone, the bootloader is locked.
You can only flash the same firmware that was on the device before you started but if not the latest G935T firmware should work.
p. s. Factory reset is an option in the settings menu, there's no need to flash new firmware.
Click to expand...
Click to collapse
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.

bassist82 said:
I don't know what firmware the phone had installed before. What are my options now? I can't get into recovery menu, only download menu works. Tried already a bunch of different android 8.0 ROMs for g935t but Odin fails to install them. It only works with just one but it goes into boot loop.
Click to expand...
Click to collapse
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members

cooltt said:
If the phone is a T Mobile device you just need to install a T Mobile firmware from sammobile.
This is the latest for your device (and I'm assuming it is a G935 edge?)....
https://www.sammobile.com/samsung/g...e/SM-G935T/TMB/download/G935TUVSACSI1/297176/
Sammobile is a little slow for non premium members
Click to expand...
Click to collapse
I already tried to flash this rom, I downloaded it from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<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
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!

bassist82 said:
I already tried to flash this rom, I downloaded from a faster source and fails to flash it.
<ID:0/007> Odin engine v(ID:3.1303)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 4575 M
<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
<ID:0/007> lksecapp.mbn
<ID:0/007> FAIL! (Auth)
<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
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.

cooltt said:
Fail (auth) means your phone is not in download mode or the firmware file is not in the correct box in Odin.
I think you may be better reading a step by step guide on how to flash firmware.
If you manage to flash and get stuck in a bootloop do the following.
1. No matter what the phone is doing just press volume down+home+power (in that sequence)
2. When the screen goes black quickly move your finger to volume up while still pressing home + power. This will boot you into recovery menu.
3. Choose "wipe cache partition" then "reboot system now"
4. Allow phone to go through the first boot up, it could take 10 minutes just leave it until you get the welcome screen.
Click to expand...
Click to collapse
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.

bassist82 said:
When I press volume down+home+power it gets me to a screen says "warning: a custom o/s can cause critical problems bla bla bla..." and underneath it shows these options: 1) Volume up: continue 2) Volume Down: Cancel (restart phone) 3) Home Button: Show Barcode. If I proceed with the 1st option it goes to download mode where I flash with odin. I tried also the combination volume up+home+power with the phone witched off and it shows the message "recovery booting..." on screen with blue text but then it shows the android icon and says" installing system update, then restarts and falls into boot loop again with the samsung logo.
Click to expand...
Click to collapse
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.

cooltt said:
Yes that's fine, just keep trying to get it into recovery, it can take a few attempts for recovery to boot successfully.
The locked bootloader models are a nightmare unfortunately but there's lots of info on the forum about all the different issues and how to resolve.
Sometimes the only solution is to try flash the firmware which was there before you did anything to it eventhough there is a newer version.
Click to expand...
Click to collapse
I tried a lot of times already but it finally gets to a point that says "no command" with the android icon on top and if I press some times the volume up/down or home it finally gives some error messages and stuck there. It seems to me that the recovery menu is missing completely for some reason and the second problem is I don't remember which firmware version it had exactly before my attempt to flash another.

Anyone? Do I need a pit file to fix this problem?

Related

I'm trying to update ClockworkMod...

Ok, so first of all I want to apologize, because I'm fairly new at this. And second off, I dont have enough posts yet to post in the Development forums.
I'm going along the lines of the "[RECOVERY] Updated ClockworkMod for all (non-voodoo) ROMs" thread, trying to update my phone, because somehow somewhere something got messed up. I finally got Odin to connect to the phone, I selected pda and the "cwm_froyo.tar" file, and pressed start. It took about 10 seconds, and said that it had passed and the phone turned off.
Then it booted into the blue recovery, and I selected apply update from sdcard. Phone kinda rebooted, then brought me back to the same recovery screen. I retried it one more time, then I saw the red recovery screen, but I'm not too sure what selection to make from here.
Am I going about this totally wrong, or somewhat right? I'm so confused with this all. My buddy that I worked with set up all this on my phone, and now that he no longer works with me, I'm trying to figure it out myself. I appreciate any help given, thank you!
Similar issue
I am having a similar
I can no longer boot to Green Recovery... everytime I select Update.zip, it reboots right back to Blue Recovery..
Anyone?
I cant even get my phone to boot into "Download" mode anymore. I'm afraid I did something and now I cant fix it myself.... Ugh
Xxw0lfxX said:
I cant even get my phone to boot into "Download" mode anymore. I'm afraid I did something and now I cant fix it myself.... Ugh
Click to expand...
Click to collapse
I was having this problem too, but I finally got it to work
Try leaving your battery out when you do it.
Also, try using a different USB port.
rushfanx1 said:
I was having this problem too, but I finally got it to work
Try leaving your battery out when you do it.
Also, try using a different USB port.
Click to expand...
Click to collapse
I'll try that, but I've done it a few times with no luck so far... But IF I do get it working, once it's in Downloading mode, I press start in Odin right? Then once it's passed what then?
Xxw0lfxX said:
I'll try that, but I've done it a few times with no luck so far... But IF I do get it working, once it's in Downloading mode, I press start in Odin right? Then once it's passed what then?
Click to expand...
Click to collapse
Correct... Once you see the Yellow Triangle and it says Downloading, you should see in Odin a Yellow Box on the COM line.. SHowing you are connected,
Then, in the files area, select the CWM Tar file you want to install.. Make sure you select in in the PDA area...
Then press START
rushfanx1 said:
Correct... Once you see the Yellow Triangle and it says Downloading, you should see in Odin a Yellow Box on the COM line.. SHowing you are connected,
Then, in the files area, select the CWM Tar file you want to install.. Make sure you select in in the PDA area...
Then press START
Click to expand...
Click to collapse
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
Then it turned off my phone. But still, when I want to change something in the rom, it reboots, verifys package install, then loads into blue recovery mode again....?
Xxw0lfxX said:
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!
Then it turned off my phone. But still, when I want to change something in the rom, it reboots, verifys package install, then loads into blue recovery mode again....?
Click to expand...
Click to collapse
From Blue Recovery, you should select Update.zip...
That should bring you to Green Recovery
What does it mean when it won't boot green recovery? I'm having the same problem too.
rcs7 said:
What does it mean when it won't boot green recovery? I'm having the same problem too.
Click to expand...
Click to collapse
There are 3 different color Recovery Screens
Blue
Green
Red (Voodoo)
As long as Ive been doing this (which is about 2 months), ive always booted to Blue, selected Apply update.zip and then it booted to Green.
From Green, you can then wipe your cache/stats etc.. and then install your custom ROM.
I decided to try installing EB01 Stock using the RED recovery and all seems to have worked fine... So, I guess green is no longer needed
If anyone has any additional comments, please help us out.
So from blue, I apply update from sd card, then it takes me into red... LOL I'm so lost
copy cm folder from.other i 500
Sent from my SCH-I500 using XDA App
Ok, I'm still confused on where I should go from here
So let me start out from the beginning....
I'm running the latest Cwm, with Blackhole-4.01 . When I went to change the theme or anything on the rom, the phone reboots, verify package, then shows me the samsung screen, and from there it shows me the Blue Recovery.
So I was told to flash a custome recovery via odin from http://forum.xda-developers.com/showthread.php?t=942021 . So I start my computer into Downloading mode, and flash cwm_froyo.tar
That then gives me
"<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!"
and shuts off the phone.
So now I put the battery in, and turn on the phone and it reboots into blue recovery. From what I understand I'm suppose to apply sdcard:update.zip . From there it now shows me CwM Voodoo Lagfix Recovery v2.5.1.x Red. At the bottom of the screen it shows
"E:Missing bitmap progress_empty (Code -1)"
"E:Missing bitmap progress_fill (code -1)"
"CwM Voodoo Lagfix Recovery v2.5.1.x"
What do I do from here? Lol, or am I not even suppose to be in this screen. It seems I'm missing bits and pieces of the whole process
Xxw0lfxX said:
So let me start out from the beginning....
I'm running the latest Cwm, with Blackhole-4.01 . When I went to change the theme or anything on the rom, the phone reboots, verify package, then shows me the samsung screen, and from there it shows me the Blue Recovery.
So I was told to flash a custome recovery via odin from http://forum.xda-developers.com/showthread.php?t=942021 . So I start my computer into Downloading mode, and flash cwm_froyo.tar
That then gives me
"<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/011> Removed!!"
and shuts off the phone.
So now I put the battery in, and turn on the phone and it reboots into blue recovery. From what I understand I'm suppose to apply sdcard:update.zip . From there it now shows me CwM Voodoo Lagfix Recovery v2.5.1.x Red. At the bottom of the screen it shows
"E:Missing bitmap progress_empty (Code -1)"
"E:Missing bitmap progress_fill (code -1)"
"CwM Voodoo Lagfix Recovery v2.5.1.x"
What do I do from here? Lol, or am I not even suppose to be in this screen. It seems I'm missing bits and pieces of the whole process
Click to expand...
Click to collapse
You can ignore the error message it does not affect recovery functions.
Choose the option you need and proceed as with green recovery.
uslacson1 said:
You can ignore the error message it does not affect recovery functions.
Choose the option you need and proceed as with green recovery.
Click to expand...
Click to collapse
But when I apply update from sd on red, the screen turns blank and just sits there with the four lights on the bottom lit up.
Xxw0lfxX said:
But when I apply update from sd on red, the screen turns blank and just sits there with the four lights on the bottom lit up.
Click to expand...
Click to collapse
What update are you trying to install?
uslacson1 said:
What update are you trying to install?
Click to expand...
Click to collapse
The Updated ClockworkMod for all (non-voodoo) ROMs. I was told that I had to do that seeing as how when I try to modify my existing rom to make changes, that the phone reboots into blue recovery, and wont allow me to make any changes
Xxw0lfxX said:
The Updated ClockworkMod for all (non-voodoo) ROMs. I was told that I had to do that seeing as how when I try to modify my existing rom to make changes, that the phone reboots into blue recovery, and wont allow me to make any changes
Click to expand...
Click to collapse
From your previous post you have mentioned the error message associated
with the new red CWM, if you are able to get to that then you already have the updated recovery.
uslacson1 said:
From your previous post you have mentioned the error message associated
with the new red CWM, if you are able to get to that then you already have the updated recovery.
Click to expand...
Click to collapse
Ok, so why is it when I modify my rom, and the system reboots to apply the modification, does the phone reboot showing blue recovery. And when I actually get the phone booted back up, the changes were not made?
Xxw0lfxX said:
Ok, so why is it when I modify my rom, and the system reboots to apply the modification, does the phone reboot showing blue recovery. And when I actually get the phone booted back up, the changes were not made?
Click to expand...
Click to collapse
if you're doing it with rom manager you need to copy update.zip from your sd card rename it recovery-update and replace the file in clockworkmod folder
Sent from my SCH-I500 using XDA App

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!
titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

Galaxy S5 "bootlocked" after attempted downgrade

Hello,
I am having some issues with my S5 G900A (AT&T). Any help I could get in order to get any functionality back out of my phone would be greatly appreciated.
I recently update via OTA to lollipop, but I wanted to get it rooted to try it out. The first thing I attempted to do was to revert the firmware back to 4.4.2 by using Odin. I used three different sources for the G900AUCU1ANCE model, the last of which I got from here, which I found from this post.
However, this did not work, and now I am forever stuck on the firmware update page.
When I ran the Odin program, the program failed and output the following:
<ID:0/007> Odin engine v(ID:3.1005)..
<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> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> persist.img.ext4
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone side, I get the following messages on the screen. The messages that appear after running Odin are bolded.
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (csb)
RP SWREV: S1, T2, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
(Downloading... Do not turn off target!!)
Click to expand...
Click to collapse
At this point, if I restart by pulling out (the battery), and then turn it back on normally, then I get back to the 'Odin Mode' screen, but with the large message on the bottom: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
This message will appear when the following keypresses are used to turn the phone on:
Volume up + Lock
Volume down + Lock
Lock
Home + Lock
Volume up + Volume down + Lock
Volume up + Lock + Home
The following keypresses don't do anything
Volume up + Volume down
Volume up + Volume down + Home
Volume down + Home
Volume up + Home
Finally, if I do the following keypress:
Volume down + Lock + Home
I get the familiar warning screen:
Warning!!
A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel.
Click to expand...
Click to collapse
If I press the volume down key, then I go back to the same Odin Mode screen with the "firmware upgrade encountered an issue" message from before. If I press the volume up key, then I get the Odin Mode screen (that always stays the same), but with "Downloading... Do not turn off target!!" as the message instead.
I also tried using Samsung Kies, though that method seems to be frowned upon by everyone. It clearly downloaded something and looked like it was installing something, but then it told me that I should run the emergency recovery process using an emergency recovery code. In the alert window, there was clearly a space where an emergency code was supposed to be, but there was no emergency code. Therefore, I was not able to get any farther using Kies.
I have read many posts mentioning that Odin can be very fickle, so I took the liberty of trying using two different USB cables and tried all 4 USB ports that are on my laptop, and I tried each of those three times. I also ensured that Kies and its background processes were not running when I utilized odin.
I also tried re-writing the PIT file, which I found from here, but when I did that, I got
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
In Odin and "SECURE CHECK FAIL : PIT" on my phone window.
After exhaustive googling, I am not too sure of what to do anymore, and would appreciate if someone could help.
Bootloader is locked, not sure there is anything you can do
*Detection* said:
Bootloader is locked, not sure there is anything you can do
Click to expand...
Click to collapse
2 questions, which error message points out to you that the "bootloader is locked," and does this mean that I would need to take my phone to AT&T to get it serviced?
<ID:0/007> FAIL! (Auth)
Tells me the Secure Boot Key is failing to authenticate
--
From what I've read, AT&T S5s are bootloader locked, as are a few other carrier branded ones
What is actually wrong with the phone? Just that you want to downgrade to Kitkat and root?
Or is there actually something wrong with Lollipop?
It is a very well known fact that after upgrading from KK to LP, you should factory reset the phone, KK leaves behind rubbish files that cause all sorts of issues, resetting cures a lot of them
Oh I see, thanks!
Nothing really wrong with it, I just wanted to try rooting the phone.
Unfortunately the only known method to root Lollipop is via ODIN, but it's still a fairly new OS so never say never about the devs finding an exploit that can be used with a locked bootloader
You cant downgrade from lollipop to kitkat once you take the ota for lollipop, as you can see here. You need to get the oc4(lollipop) firmware files and flash that to unbrick, they are in the att s5 general section.
Sent from my twi5ted SM-G900A using Tapatalk
Thanks, I ended up taking it to best buy and having the guy there reset the firmware. Pretty sure he used something called SMART or something to do it

SM-G930A Cannot boot. Attempting to flash offical firmware using odin fails

I get this error while attempting to flash official ROM using Odin. the phone currently cannot boot. Please assist in any way possible. I just would like to get my phone to function like normal again. I attempted to flash only AP
ON PC LOG
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
<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)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ON PHONE
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Any way I can get the phone usable again? I really would like if anyone could assist in get it working again. It does not need to be rooted, it only needs to boot and function
Mine did same thing. I fixed mine by doing a factory reset from recovery mode. Reboot the phone and hold power+volume up+home key at same time until u see recovery mode in top left corner. It will say installing system update then go to a menu. Hit volume down till factory reset is highlighted. Hit the power button. After its complete go to wipe cache and wipe it also. Then click reboot system now and should now boot fine
Js7bla said:
Mine did same thing. I fixed mine by doing a factory reset from recovery mode. Reboot the phone and hold power+volume up+home key at same time until u see recovery mode in top left corner. It will say installing system update then go to a menu. Hit volume down till factory reset is highlighted. Hit the power button. After its complete go to wipe cache and wipe it also. Then click reboot system now and should now boot fine
Click to expand...
Click to collapse
I've had to do the same thing in a similar situation and it fixed it for me. Good fix!
Are you sure the stock version you are trying to flash is the same or newer than the version you had installed?
jpasher said:
Are you sure the stock version you are trying to flash is the same or newer than the version you had installed?
Click to expand...
Click to collapse
I think you have to Flash all 4 of the files, AP,BL, CP, CSC in Odin Latest version of stock is APK1
I flashed just this AP_G930AUCS4API2_CL8575098_QB10880146_REV02_user_low_ship_MULTI_CERT.tar in the AP section and my phone worked again. I don't know if that' might be bad thing or not though
I choose Phone Bootloader Update in Odin. It was the only thing that worked for me.

j530f recovery is not seandroid enforcing

Hi guys, I have an j5 2017 (j530f/DS), and I rooted him, but, when I tried to unroot it, and get to default rom, it gets into a boot loop with the Samsung Galaxy J5 screen, and in the left corner is says "Recovery is not seandroid enforcing"
Did i birck it forever? Can i do something about it?...
Please help me guys... Thanks...
EDIT: I can't get into the Recovery mode, or Download Mode neither
I can't take the battery out, because is unibody tho...
Vol+ & Vol- & Power should force your phone to reboot properly.
Then with Vol- & Home & Power you should be able to enter the download mode.
gooodly said:
Vol+ & Vol- & Power should force your phone to reboot properly.
Then with Vol- & Home & Power you should be able to enter the download mode.
Click to expand...
Click to collapse
Ok, I i tried to install the software again, but i get this an error has occurred while updating the device software use the emergency recovery function in the smart switch PC Software , I didn't found my phone, and can't add by the S/N and phone name. I got into Download mode, and i am trying to install the default firmware, but it stucks at <ID:0/003> meta-data/fota.zip ...
Any solve for this?
Which FW and client program did you use?
There's Samsung Smart Switch which allows to update to the latest firmware or Odin which requires that you download the firmware manually, e.g. from Sammobile. Downgrading to an old version may fail. I could downgrade from Lineage OS (8.x) back to stock ROM (7.1) but I could not downgrade to stock ROM 7.0. Anyhow here flashing failed immediately.
In Odin I selected all 4 files (AP, BL, CP and CSC) and had no issues. Up to now I never heard of a problem with fota.zip, so I have no clue about this issue.
gooodly said:
Which FW and client program did you use?
There's Samsung Smart Switch which allows to update to the latest firmware or Odin which requires that you download the firmware manually, e.g. from Sammobile. Downgrading to an old version may fail. I could downgrade from Lineage OS (8.x) back to stock ROM (7.1) but I could not downgrade to stock ROM 7.0. Anyhow here flashing failed immediately.
In Odin I selected all 4 files (AP, BL, CP and CSC) and had no issues. Up to now I never heard of a problem with fota.zip, so I have no clue about this issue.
Click to expand...
Click to collapse
I got my device to the J530FXXU1AQF5 firmware
I need to update it to J530FXXU2ARA2. *who is the actual stock rom* can i do it whithout getting any problem?
Go into DL mode and flash it (ARA2 = Security Patch Level 2018-01-01) . J530FXXU2ARB3 (Security Patch Level 2018-02-01) is more recent.
As long as you can enter the DL mode flashing will work unless you encounter an hardware error.
gooodly said:
Go into DL mode and flash it (ARA2 = Security Patch Level 2018-01-01) . J530FXXU2ARB3 (Security Patch Level 2018-02-01) is more recent.
As long as you can enter the DL mode flashing will work unless you encounter an hardware error.
Click to expand...
Click to collapse
I tried to install the most recent version but i got an error, and i downloaded this one
EDIT:
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I did wrong?
Bobita said:
What I did wrong?
Click to expand...
Click to collapse
What did you do exactly? From the log file it's obvious that you used Odin.
Did you select AP, BL, CP and CSC in Odin?
Or did you use CSC_Home?
Hey bro download latest twrp available for ur device it should be latest and updated if odin is able to detect ur phone just install the twrp first then u should download the stock firmware u wanna install and boot it from recovery u dont need any odin if u can able to get into recovery u can just install ur stock rom by placing it in ur external storage if ur recovery options work .try this

Categories

Resources