Database Users

Tried to flash my phone with an older kernal and now i'm stuck in recovery mode.

Hello the phone I'm using is s5 active at&t.
I followed this guide http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g870aucu1ang3-gs5-active-t2868776
used this G870A_NE4_Stock_Kernel.tar.md5
But for some reason everything went to the dumps. I then looked up some guides and got a stock firmware from sammobile G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar.md5
Odin recognizes the phone as it shows it in the ID:COM area but then it fails.
<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> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
this is what appears on my phone: sw rev check fail fused 2 binary 1
My first time trying to root. It brings me to the recovery screen with a bunch of options and I'm capable of getting it to the download screen holding volume, home, power.
Please any help would be great.
edit. also tried this https://www.youtube.com/watch?v=8481Qm0l010 didn't do anything, but it passed on odin
edit. trying this guide out doing note.4 http://forum.xda-developers.com/att...w-to-update-to-g870aof2-5-0-keeproot-t3161733
edit I went through this process a few times http://www.modifyandroid.com/stock-...ck-rom-for-samsung-galaxy-s5-active-sm-g870a/ and it always fails on odin

This is what the recovery menu looks like
Android system recovery <3e>
Volume up/down to move highlight;
power button to select.
reboot system now
apply update from adb
apply update from external storage
apply update from cache
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
enable cp logging
disable cp logging
My main problem right now is that it fails whenever I try to flash it with a stock rom. But when I flash it with a kernal or other stuff it passes.

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

s7 edge 935f jammed on powered by android screen

Hey guys/gals . my phone locked up after a restart from updating magisk and now stuck on the s7 edge powered by android screen. i have tried to open twrp but it wont leave the earlier mentioned screen. i can however enter download mode. i tried using ODIN3 v3.12 reflashing the same BL, AP, CP and CSC but with no luck. i have also tried to flash the stock FW but get error on phone saying SW REV. CHECK FAIL. DEVICE: 2 BINARY: 1 after Odin fails and the log reads
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The flash files I have used previously that worked are
twrp-3.1.0-0-hero2lte.img.tar (Used in BL for Root)
AP_G935FXXU1APD1_CL7538748_QB9125704_REV00_user_low_ship.tar.md5 (stock)
BL_G935FXXU1APD1_CL7538748_QB9125704_REV00_user_low_ship.tar.md5 (Stock)
CP_G935FXXU1APD1_CL7538748_QB9125704_REV00_user_low_ship.tar.md5 (Stock)
CSC_XSA_G935FXSA1APD1_CL7688684_QB9120478_REV00_user_low_ship.tar.md5 (stock)
HOME_CSC_XSA_G935FXSA1APD1_CL7688684_QB9120478_REV00_user_low_ship.tar.md5(Stock)
Is this recoverable or am I looking at an expensive paperweight. cheers
Edit. I can now boot into TWRP and download mode now, Just can't seem to get it to take an OS, the storage it showing up fine in TWRP and on a pc, except its empty space.
Any advice to solve this would be much appreciated

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.

Help Need. Flash TWRP Custom Rom to Samsung Note 4 (SM-N910F)

Note sure if this is the right thread to post.
Phone Model : Samsung SM-N910F (Samsung Note 4)
I am using Odin v3.13.1.
TWRP -twrp-3.6.2_9-0-trlte.img
Here are my steps.
1. Factory Reset Wipe out all Data
2. Go Back into the phone and enabled USB Debugging.
3. Go into Recovery (Down + Home + Power)
4. Odin Flash with Auto-reboot off (TWRP -twrp-3.6.2_9-0-trlte.img)
5. I got error from odin
--------------
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 13 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> recovery.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
--------------
It keeps failing. with the error log above.
I tried a couple of TWRP version, it fails with same error.
I tried a couple of Odin version, it fails with same error.
Is the bootloader lock ? Please help and shine me a light with this lost soul.
Thank you very much.

mixtmxim said:
Note sure if this is the right thread to post.
Phone Model : Samsung SM-N910F (Samsung Note 4)
I am using Odin v3.13.1.
TWRP -twrp-3.6.2_9-0-trlte.img
Click to expand...
Click to collapse
afaik Odin can only flash tar or tar.md5 files so choose
twrp-3.6.2_9-0-trlte.img.tar.​Personally on that old device I use Odin 3.09 as I somewhere read it suits better.
mixtmxim said:
......
Is the bootloader lock ? Please help and shine me a light with this lost soul.....
Click to expand...
Click to collapse
No. Not on this old device (at least not on my N910F)

kit kat or marshmallow?