Database Users

stuck in bootloop even after flashing new rom

Hello,
So to start off I had encrypted CyanogenMOd 12.1 nightlies running on my T-Mobile Samsung Galaxy S5 with TWRP 2.8.7 recovery without any problems. I went to reboot and it got stuck in a bootloop, I tried restarting it and same thing. I tried wiping cache/dalvik and same thing. Sometimes it would make it to the "optimizing apps" screen and indefinitely hang on "starting apps", but mostly it gets stuck on the boot animation. I hadn't added or deleted anything prior to this happening. I had tried a number of possible solutions from various threads, none of which solved my issue. (Also, it never asked me to enter my password to startup which it usually did)
I then tried wiping dalvik, system , data, internal storage, and cache and flashing a fresh rom which did not work either. This time the bootloop only ever occurs on the boot animation screen.
What should be my next course of action?

Flash a stock ROM along with the PIT file for your model S5 (Flash both at the same time in ODIN)

*Detection* said:
Flash a stock ROM along with the PIT file for your model S5 (Flash both at the same time in ODIN)
Click to expand...
Click to collapse
I'm having trouble getting a stock rom, they keep corrupting at the end of the download and the download speed is throttled. Do you know of a good source to obtain a stock rom that won't take 2+ hours to download?

What model S5 is it?
Eg: Mine is G900F

*Detection* said:
What model S5 is it?
Eg: Mine is G900F
Click to expand...
Click to collapse
G900T

EzStyles said:
G900T
Click to expand...
Click to collapse
Try this link
Code:
http://am4-r1f7-stor06.uploaded.net/dl/42f1fae6-1bca-4e2b-ae7a-f1959a6f1f9e

*Detection* said:
Try this link
Code:
http://am4-r1f7-stor06.uploaded.net/dl/42f1fae6-1bca-4e2b-ae7a-f1959a6f1f9e
Click to expand...
Click to collapse
Awesome thank you that is working great! Much faster than the download links I have been finding. I will report back shortly with results

Good luck

*Detection* said:
Good luck
Click to expand...
Click to collapse
So I tried flashing the file from that link along with a PIT file that I found on another thread on this site but it fails to flash.
The message from Odin is:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The message on my phone says:
Secure check fail : PIT
Would this be a bad pit file?

EzStyles said:
So I tried flashing the file from that link along with a PIT file that I found on another thread on this site but it fails to flash.
The message from Odin is:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The message on my phone says:
Secure check fail : PIT
Would this be a bad pit file?
Click to expand...
Click to collapse
Are you 100% sure about the model S5 you're trying to flash?
Check Settings > General > About
I've just spent the day with another member, who had the same error FAIL! message, and he was trying to flash a G900F ROM and PIT onto a G901F

*Detection* said:
Are you 100% sure about the model S5 you're trying to flash?
Check Settings > General > About
I've just spent the day with another member, who had the same error FAIL! message, and he was trying to flash a G900F ROM and PIT onto a G901F
Click to expand...
Click to collapse
100% positive. It's T-Mobile, I have the box with that model number and in download mode it shows product name: SM-G900T
Perhaps the files need to have a specific name in order to flash properly? I've run into that issue when reflashing motherboards
So I tried flashing without the PIT file and it "passed" according to odin but it is just stuck on the "Samsung Galaxy S5 Powered by Android" screen now

Ok, So i tried flashing the rom itself one more time and this time it worked! My phone is back to working now. Or, at least until I reboot again > I'll be back if there's any more issues haha. Thanks again for your help

Same Problem
EzStyles said:
So I tried flashing the file from that link along with a PIT file that I found on another thread on this site but it fails to flash.
The message from Odin is:
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The message on my phone says:
Secure check fail : PIT
Would this be a bad pit file?
Click to expand...
Click to collapse
Hi, I have a Galaxy S5 SM-G900M and it's in a bootloop, I tried to intall the stock rom with ODIN and Kies but still not work, maybe somebody have the PIT file for this model?

Cendrez said:
Hi, I have a Galaxy S5 SM-G900M and it's in a bootloop, I tried to intall the stock rom with ODIN and Kies but still not work, maybe somebody have the PIT file for this model?
Click to expand...
Click to collapse
Did you have ODIN and Kies running at the same time? Make sure Kies service is stopped in system before running ODIN

SM-G930A Bricked after trying to unroot.

Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> 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> 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)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan

DecDaddy said:
Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> 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> 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)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
I ran into same issue. Just hold power button until phone shuts down, power up into download mode and Odin flash the stock firmware for your phone again. It's a soft brick. Be sure you have correct firmware.

Currently stuck with a Bricked Galaxy S7 that is in a Recovery Boot-loop. I tried flashing the stock firmware to the device and it failed.
Here is the Odin log:
<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> 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> 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)
The Screen after this failure displays the "Downloading, Do not turn off target" screen. And in small red font in the upper left corner of the screen the statement, "SW REV CHECK FAIL : [system]fused 3 > Binary 1" is shown. I don't have any clue where to go from here so any suggestions would be lovely.
Cheers,
Declan
Click to expand...
Click to collapse
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron

aaron99 said:
Same issue here - phone bricked. Odin or the Download mode of the phone fails with 1 of several errors. I have found that only 1 version of Odin works with my SM-G930A now. The last trick I think I have in the bag here is to pry off the back of the phone and make sure the stock firmware I am trying to use i the one that matches the device...
I have tried these stock images (easily google-able):
- ATT_G930AUCS2APF2
- G930AATT1APB5_User_Binary
The only version of Odin that works is the one I used to root the SM-G930A phone:
- Odin PrinceComsy.exe
It can only flash the root file:
- Samsung_G930x_QC_Rooted_BOOT.TAR
I have tried so many different versions of Odin, I think I am going cross eyed. If anyone has a solution for a phone that is looking bricked, please give me a shout out.
Thanks,
Aaron
Click to expand...
Click to collapse
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
6. My phone loaded a long time through at the AT&T loading screen (it appeared locked, but was not)
- NOTE: You can always hard reset it and try to get through the AT&T loading screen
7. Go through Android/Samsung/AT&T welcome wizard
8. Root the phone: See permanent root section here: http://forum.xda-developers.com/ver...-to-notes-root-install-xposed-unroot-t3411039
- This root process side loads Chainfire's SU tool
-- NOTE: This is where things become unconventional, since my phone was not working with Google Play Services nor did the Google Store app work (I tried everything... they just would not work)
9. Open Chainfire's SU tool, go to the app's settings:
- enable SU at boot
- instead of "prompt", set app to auto-accept root access requests (normally this is stupid since some other random app could automatically acquire root access, but in this case, I was not in this state for very long. I actually had to do this because the system would not pop up notifications for apps requesting root access)
10. On a PC, download Chainfire's Flashfire app (I used this: eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk)
11. In a Windows command prompt running as adminitrator, put the APK from step #10 into the same root.bat folder used in step #8
12. With the phone connected (with Samsung USB drivers installed of course), run this command from that folder: adb install -r eu.chainfire.flash_0.53-53_minAPI17(armeabi-v7a,x86)(nodpi)_apkmirror.com.apk
13. Open app drawer and run Flashfire
14. Follow this guide from step #1 through step #9 (because my phone will not work with Odin nor the boot loader listed on step #10 of the guide): http://www.droidviews.com/install-deodexed-debloated-stock-rom-on-att-galaxy-s7-sm-g930a/
- If steps are followed through step #9, the phone will be in Download mode
15. Hard reset phone and boot into Recovery mode
16. Repeat steps #1-5 from my steps listed above to reset factory settings / wipe the phone again
17. Phone reboots and will appear to hang... Just wait. Wait and wait. It will load.
18. Go through Welcome wizard...
This time, all apps work, due to the ROM image used during step #14. This slimmed down ROM image has fully functional stock apps, which is great because that is now set as as the factory image for any future Recovery mode factory resets. Life saver! ...or more like a phone saver for me.
Hopefully this helps someone else.
-Aaron

aaron99 said:
I fixed my phone.
Answer for my case:
1. Load into Recovery mode
2. Reset factory defaults/wipe phone.
3. Clear cache
4. Reset factory defaults/wipe phone a 2nd time just for fun
5. Reboot phone
-Aaron
Click to expand...
Click to collapse
I know this is an old thread, but im having this problem after attempting to root to stock and im stuck on the samsung custom logo with recovery booting in the top left corner. the main problem though is i cant boot to recovery mode, it simply wont let me

Odin flashing firmware failed problem.

So I got pretty far in trying to flash nougat back onto my S7 (From Oero) but hit an error.
I'm going from the latest Oero to the latest Nougat firmware (G930AUCS4BRD1) for my phone
AP_G930AUCS4BRD1_CL12564870_QB17646051_REV02_user_low_ship_MULTI_CERT_meta.tar.md5
BL_G930AUCS4BRD1_CL12564870_QB17646051_REV02_user_low_ship_MULTI_CERT.tar.md5
CP_G930AUCS4BRD1_CL12564870_QB17646051_REV02_user_low_ship_MULTI_CERT.tar.md5
CSC_ATT_G930AATT4BRD1_CL12564870_QB17646051_REV02_user_low_ship_MULTI_CERT.tar.md5
Using these files Odin almost did the deed of downgrading my phone. I backed up everything on my sd card and ejected it, along with my sim card.
Using the latest Odin (13.13.1) and doing the whole activate OEM and USB debugging, it still failed. Do I need to be rooted?
What went wrong?
Odin Log
Odin engine v(ID:3.1301)..
File analyisis
Total Binary size: 4756 M
Setupconnection
Intialzation..
Set PIT file
DO NOT TURN OFF TARGET!!
Get PIT for mapping..
Firmware update start..
NAND Write Start!!
SignleDownload
emmc_appsboot.mbn
iksecapp.mbn
FAIL! (Auth)
>
Complete(Write) operation failed
All threads completed. (succeed 0 / failed 1)

download lastOdin3_v3.13.1

SM-J320M Stuck on Bootloop - Unable to flash Stock Firmware

Hello Guys,
Im pretty new here but I really need someome to help me with this as Im totally lost here.
Yesterday I rooted my j3 sm-j320m and all went fine I converted the app I needed into systemapp and then unrooted the phone however by mistake I turned off developer options and with that OEM unlock so as expected when phone rebooted its now stuck on bootloop and error on screen with Custom Binary Blocked by FRP all in green letters.
So I downloaded the Stock firmware from sammobile and tried to flash it with Odin V3.13 however it got stucked on hidden.img and them Failed
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1963 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried following another tutorial where it asked to Remove the hidden.img from Firmware by extracting the files and then use 7zip to create .tar image again and rename .md5 but Odin gives error hash value is invalid, tried removing .md5 from file and use it only as .tar but Odin wont read it.
I tried another tutorial where it says after error hidden.img Fails on Odin unplug phone and then re enter download mode and extract hidden.img file and rename .tar and flash it but now its stuck again on bootload but with two errors:
recovery is not seandroid enforcing
custom binary blocked by frp
All of that in green letters
Anyone knows how can I get the phone back up and running again?
Thanks

patbowling89 said:
Hello Guys,
Im pretty new here but I really need someome to help me with this as Im totally lost here.
Yesterday I rooted my j3 sm-j320m and all went fine I converted the app I needed into systemapp and then unrooted the phone however by mistake I turned off developer options and with that OEM unlock so as expected when phone rebooted its now stuck on bootloop and error on screen with Custom Binary Blocked by FRP all in green letters.
So I downloaded the Stock firmware from sammobile and tried to flash it with Odin V3.13 however it got stucked on hidden.img and them Failed
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 1963 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried following another tutorial where it asked to Remove the hidden.img from Firmware by extracting the files and then use 7zip to create .tar image again and rename .md5 but Odin gives error hash value is invalid, tried removing .md5 from file and use it only as .tar but Odin wont read it.
I tried another tutorial where it says after error hidden.img Fails on Odin unplug phone and then re enter download mode and extract hidden.img file and rename .tar and flash it but now its stuck again on bootload but with two errors:
recovery is not seandroid enforcing
custom binary blocked by frp
All of that in green letters
Anyone knows how can I get the phone back up and running again?
Thanks
Click to expand...
Click to collapse
Just flash the correct firmware for your device region and it will pass.

Samsung Galaxy A8 [SM-A800F] Odin complete(write) operation failed. HELP!!

I rooted my A8 with magisk and installed a module (that I don't remember the name of) and when I restart the device, it stuck in a bootloop. Usually I'd flash firmware via odin and fix it. But this time Odin failed and showed this when I try to flash the firmware:
Code:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It was stuck on 'Get PIT for mapping' for like 5 minutes and failed. It didn't even showed anything like BOOT or RECOVERY above the id com as it usually does.
Now my device is stuck in a screen which says:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software."
The smart switch software doesn't seem to help as it can not recognize my device.
HELP SOMEONE!!
Update: While I was writing this post, I was simultaneously trying to flash something from a sketchy youtube tutorial via odin. Now my phone does not show the error. Rather it shows the 'Samsung Galaxy A8' logo and turn off. I don't know if its an improvement or not. But atleast now it turns off and not show the error forever and drain the battery anymore. I tried flashing firmware with this 'improved' state but still odin shows the same error.