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.
Related
After trying to install a custom recovery I have not been able to boot into my phone for about 4 hours now. During this time I have tried multiple times, using multiple methods and have found nothing to work.
My problem is when I try to boot up my device it wants to boot into recovery mode but it cant so it takes me right to download mode. In download mode I attempted multiple time to flash the default Samsung GS 4 .tar.md5 file and bring my device back to life but I get this error each time. (I've tried all my USB ports and still get the same error)
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / 1 failed
I cannot find any fixes to this problem and have resulted in additional help from these forums.
Additional Info: When I was flashing my custom recovery, it was to overwrite the one I had previously installed (Safestrap v3.5x) with (OUDHS Touch CWM-based Recovery 1.0.3.4 by Shabbypenguin) and thats when I got the issue. Also, when I'm taken into download mode there is an additional red text above the "ODIN MODE" text that says, "Could not do normal boot." I'm thinking that Safestrap was attempting to boot along with the CMW-based and the device cant choose, so I'm forced into Download Mode.
Any help with this issue would be greatly appreciated. This phone is only 2 days old so I'm somewhat aggravated.
Video of Problem:
Cant post until 10 post...
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
Hello,
Ineed help on installing stock firmware too for samsung s7 SM-G930A AT&T mobile.
https://drive.google.com/drive/folders/0Bz4qV62uoY6aQXpfZWpRV0MxUkE
These are errors videos. I'm stuck here with this issue
I rooted my phone, ran the S7 fixes script, the debloat script, then the root seemed to work fine for a day. Then the wireless charging stopped working, then it unplugged and replugged itself over and over and over in the charging mode, like it "recognizes" the charging cable over and over all day long while it's plugged into the charger, making the "beep beep" sound that it makes when you plug in the charger. So I rebooted the phone to see if it would fix it, and now it hangs at the at&t logo screen forever. I can't power it down. I can get into odin mode, but odin fails every time I try to reinstall the factory ROM. I tried to clear the cache, but it didn't work. I tried booting into recovery mode, but it fails. basically I've tried just about everything to unbrick and it's still bricked.
also note that I used odin 3.12.3, the lastest. and I tried to install G930AATT1APB5_User_Binary, which fails every time.
also tried smartswitch, but the program just shuts off instantly after entering the SN in the device initialization in the emergency software and device initialization tab.
I enter the SN and hit okay and then it just shuts down the program, it just disappears.
ERROR 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> 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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
try using odin prince comesy, and make sure your using the latest firmware PI2. Try installing the PI2 firmware with odin 3.12.3. should work.
rzenks said:
Hello,
Ineed help on installing stock firmware too for samsung s7 SM-G930A AT&T mobile.
https://drive.google.com/drive/folders/0Bz4qV62uoY6aQXpfZWpRV0MxUkE
These are errors videos. I'm stuck here with this issue
I rooted my phone, ran the S7 fixes script, the debloat script, then the root seemed to work fine for a day. Then the wireless charging stopped working, then it unplugged and replugged itself over and over and over in the charging mode, like it "recognizes" the charging cable over and over all day long while it's plugged into the charger, making the "beep beep" sound that it makes when you plug in the charger. So I rebooted the phone to see if it would fix it, and now it hangs at the at&t logo screen forever. I can't power it down. I can get into odin mode, but odin fails every time I try to reinstall the factory ROM. I tried to clear the cache, but it didn't work. I tried booting into recovery mode, but it fails. basically I've tried just about everything to unbrick and it's still bricked.
also note that I used odin 3.12.3, the lastest. and I tried to install G930AATT1APB5_User_Binary, which fails every time.
also tried smartswitch, but the program just shuts off instantly after entering the SN in the device initialization in the emergency software and device initialization tab.
I enter the SN and hit okay and then it just shuts down the program, it just disappears.
ERROR 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> 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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
rzenks, I just had literally the exact same problem as you for the past day. I tried so many firmwares and the Smart Switch recovery option, but had the same problems as you did. I thought I was going to be killed by my dad, as my phone was only 6 days old. But after a lot of specific search results, I found a firmware that worked for my phone.
You can find the firmware here: http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
Also be sure to use the Odin3 v3.12 Prince Comsy, found here: http://forum.xda-developers.com/android/software/odin-3-12-3-worlds-att-s7-odin-firmware-t3401470
Let me know if it works for you.
Why are you flashing such old firmware?? PB5 is SEVERAL updates back. I've uploaded the latest FW, try it. That's probably why it's failing.
when it says fused while in DL mode it means you are trying to flash a firmware thats older than the current firmware.
ok, so i tried rooting and it totally screwed up my phone...
i tried unrooting by installing stock firmware through odin, and this is the error i got.
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
make sure your phone is in download mode. once your in download mode plug in your phone into a usb connection to your computer. make sure to also use the stock odin that you can find on xda and you can also just download the firmware
HTML:
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-stock-sm-g930a-ph1-odin-files-t3458890
load up all the 3 files normally and it will wipe the phone off completely to stock.
normally if the ids don't match that means the firwmare you downloaded is not the correct version for your handset.
Looks like you're either putting old firmware on or incorrect firmware.
Which model S7 do you have and which firmware are you installing?
Hello all,
Model: SM-J727T1
I think my phone is soft-bricked, meaning that no matter what I do all I get is the same boot up screen. To explain, despite trying all manual input combinations to turn on my phone it appears to show the download mode screen, but I don't think the phone truly recognizes its in download mode because any flashes that I have tried making by using Odin have failed. Additionally from screenshots I've seen what download mode looks like, it shows some snippets of code in the top left corner I think signifying its in Odin mode, that is not present on the phone. Trying to boot into any other mode fails and returns to the same "Downloading... Do not turn off target" screen. I have tried flashing the phone using Odin 3.13.1 and older with the most recent firmware but it gets stuck and fails. I followed the guide posted on samsmobile
/firmwares/galaxy-j7-pop/SM-J727T1/TMK/download/J727T1UVS4BRK1/248730/
and this is the error I get....
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> userdata.img
<ID:0/005> Home Binary Download
<ID:0/005> Total Binary size: 2287 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> cm.bin
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Other things I have tried:
Samsung Kies: can't recognize device
Samsung SwitchPlay: can't recognize device
Other firmware packages: same error
Extra Info:
Bought the phone from Metro but recently switched to TMobile (suspiciously convenient), performed all updates and never rooted nor anything custom to it. Problem started when the phone was low on battery and I decided to charge it. In the middle of charging the phone restarted randomly and went black for a minute. Tried turning it back on and thus began getting taunted by this phone. Pretty sure I'm gonna have to bite the bullet on this one and get a new phone, just wanted to make sure that I gave my due diligence in seeking help for something beyond my understanding and possibly delete the information that was on there. Last note, don't really care about anything on the phone and thusly any suggestions about completely wiping it are okay in my eyes. I just really hate having a phone that can turn on but is essentially useless.
Thanks for reading and any help is very much appreciated. Let me know if any additional information is needed.