I rooted my phone and installed a rom, once I installed it and it wouldn't boot. It got stuck on the "Samsung Galaxy S7 Edge" screen. So I have tried to return the phone back to stock firmware via odin on download mode, it all works but everytime, it wont go past the "Samsung Galaxy S7 Edge" screen. I dont know what to do. The bootloader is unlocked, I can boot into download mode and install stuff but I have tried installing stock and its not working. It installs but when the phone boots it stays on the aforementioned screen. Please can you try and help me! I have the SM-G935F version and its unlocked.
SOVLED: The guides have it wrong. Traditionally when you download the stock firmware, you will get a AP, BL, CP, and CSC files. The "unbrick guides" tell you to just tick and select the AP in odin but you have to select and tick all the AP, BL, CP, and CSC files you get from the stock zips and put them into odin. From what I can gather this is because it cannot "Receive Response from boot-loader" if you just have the AP file loaded. Try this anyone who is having the same issue as me. I am so happy, I thought I had a very shiny expensive paperweight.
In ODIN, this should be your status report. If so you should be fine:
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> param.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005> modem.bin
<ID:0/005> Transmission Complete..
<ID:0/005> Now Writing.. Please wait about 2 minutes
<ID:0/005> Receive Response from boot-loader
<ID:0/005> cache.img
<ID:0/005> hidden.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Added!!
Related
Now I've searched just about all of Google on this, but I haven't been able to find a solution yet. Everyone here seems to know the most about this kind of stuff so I figured I'd make an account and explain my situation.
Backstory / How it happened
So, earlier today I figured I'd root my AT&T S7 Edge, I used a tutorial from Max Lee (I can't post links yet but if you need to find it I'm sure you can Google it) to get the job done, and after a while I managed to get the thing rooted. I knew absolutely nothing about what the hell flashing, roms, bricked phones, bootloops etc. were and now I only know a bit about them. So the phone was rooted just fine, I had SuperSU running, and a few other root apps, but then I figured I'd install xposed installer. So I went ahead and downloaded the wrong version (whoops) and it installed its framework and then said it needed to reboot my phone, low and behold we have a bootloop. It stays at the AT&T logo indefinitely if I'd let it. I'll happily admit to that being completely my mistake, I read the warning that it may cause a bootloop but I went ahead and installed it anyway thinking I could fix it if it happened. (This thread is my walk of shame I suppose)
Solutions I've tried
Now that the background has been explained, I'll go through the list of solutions I've tried, mind you I'm no expert at any of this so some of the info I give may seem redundant or nonsensical.
- Rebooting into recovery and clearing cache and factory resetting in every order you can imagine
* Only interesting thing I could find is that it still says custom on both the download mode (the one where you press vol down, power, and home) and when you reboot the phone and it goes through the initial animation, it shows custom with a little settings-looking icon just before it goes through the AT&T animation and takes a **** on my self esteem.
- Waiting ~1 hour for the AT&T logo to change to something other than an AT&T logo (I was desperate)
* Yeah nothing came out of that one...
- Flashing every stock firmware I could find on the internet, with every version of Odin I could find.
* Kept getting the same error, "FAIL! (Auth)". I looked it up and all I found was old threads from 2013 on the Galaxy S4, with some now-irrelevant information, I couldn't seem to get it to work, but I'm positive that's what I need to do unless you guys know another solution. Here's the full log:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what I did but after that at the download screen it says at the top left "SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2
Sorry for the wall of text, I tried to format it as nicely as possible to make it somewhat readable. If anyone needs more info let me know.
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
alehawk said:
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
Click to expand...
Click to collapse
Thank you for the response
I've tried getting TWRP to work, but apparently there still isn't a way to get it working on the AT&T, I was under the impression that it was only for international and Korean versions. I haven't been able to find any version of TWRP that works for my device.
However I just did try some newer stock firmware from, "theandroidsoul" which partially worked, being that I'm desperate and don't know what I'm doing I just tried flashing all three:
G935AUCS4API2 - This one worked more than the others, but it seems at some point it disconnects for whatever reason, causing it to fail. After that my phone gave me the whole "You messed up go use smart switch" deal, and smart switch was saying my device was unsupported. That said I'm not sure what is causing the fake USB disconnect cause I can hear the windows sound for the USB disconnecting, but I'm not sure why.
Here's the log:
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> rpm.mbn
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> cmnlib64.mbn
<ID:0/005> sec.dat
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
And here's the log after another try (I factory reset and wiped cache again to give it another go)
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I found it interesting that it got even less far than before.
G935AUCS2APH1 - Stopped at lksecapp.mbn then went to FAIL! (Auth). There was no disconnect or reconnect
G935AATT2APG1 - Same as above
I seem to be stuck in a similar situation. Did you ever find a fix?
wunderkinder said:
I seem to be stuck in a similar situation. Did you ever find a fix?
Click to expand...
Click to collapse
I had the at&t s7 edge before and had the same problem but not sure if it was the same odin error.
But this is how you flash a stock rom on the at&t:
-You must use the princecomsy odin (search for it on google)
-Here is the stock rom with the latest security update (type "G935AUCS4BRA1" in the google search bar)
(I wasn't allowed to post links)
unzip and flash
tell me how it goes
SM-935F from XSG region. Unlocked and Qualcomm processor. Never enabled debugging mode or OEM in developer tools. I tried to flash my phone with the following firmware. However when I tried to do it, Odin failed. Also Smart Switch Samsung doesn't initiate/emergency recovery says cannot proceed due to an error.
Samsung Smart Switch shows the below data while trying to initiate the recovery which eventually fails.
PDA: QH8 / CSC: QG2 / PHONE:QG3 (COS)
Phone doesn't go to recovery mode at all. I can get it to Download mode however everytime I try to run a firmware, it shows "Complete(Write) operation failed."
Also tried to do abd enable reboot which said "device(null) not found". Just need this working and I don't care about losing data. Please let me know how to proceed.
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> skip file list for home binary
<ID:0/005> param.bin
<ID:0/005> modem_debug.bin
<ID:0/005> Home Binary Download
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> cm.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can someone please help me out
This morning i was running AlexisRom on my Galaxy s8 (SM-G950FD) which is an s9 port for s8 but the headphone jack wasn't working on the rom so i downloaded a stock rom from Sammobile and tried to flash it through odin, and after i put in the BL, AP, CP and CSC file and pressed start, it gives me a fail and says :
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2753 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone in the download mode, it comes up in red writing:
[CM] SW Rev. CHECK FAIL. DEVICE 3. BINARY 2
Also, i cannot get into recovery at all by pressing Bixby + Vol up + Power, it just bootloops
If i try install TWRP, my phone boots and shows the Samsung screen and says in pink writing on the top:
RECOVERY image signature check fail!!!!
Reboot to avoid warranty bit set!!
And i am 100% sure that the phone works as i had it working yesterday perfectly fine.
The roms i have installed before this one:
Stock S8 Rom
AMBASADII ROM FOR S8/S8+
Alexisrom s9 port for s8
Someone please help me out, if you need more details please ask!
THANKS <3
For anyone who has the same problem as me, here is a fix i found after almost giving up,
Go to Sammobile.com or Shell.BoxWares.com and download the latest firmware for your phone model, even if it isn't your country, still download and flash it, i live in ireland, so i should have 3IE Firmware but i downloaded the Indonesian firmware and it flashed without a single hassle
Its due to bootloader issue
xNexeon said:
Can someone please help me out
This morning i was running AlexisRom on my Galaxy s8 (SM-G950FD) which is an s9 port for s8 but the headphone jack wasn't working on the rom so i downloaded a stock rom from Sammobile and tried to flash it through odin, and after i put in the BL, AP, CP and CSC file and pressed start, it gives me a fail and says :
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 2753 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<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> param.bin
<ID:0/005> sboot.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on my phone in the download mode, it comes up in red writing:
[CM] SW Rev. CHECK FAIL. DEVICE 3. BINARY 2
Also, i cannot get into recovery at all by pressing Bixby + Vol up + Power, it just bootloops
If i try install TWRP, my phone boots and shows the Samsung screen and says in pink writing on the top:
RECOVERY image signature check fail!!!!
Reboot to avoid warranty bit set!!
And i am 100% sure that the phone works as i had it working yesterday perfectly fine.
The roms i have installed before this one:
Stock S8 Rom
AMBASADII ROM FOR S8/S8+
Alexisrom s9 port for s8
Someone please help me out, if you need more details please ask!
THANKS <3
Click to expand...
Click to collapse
You are trying to flash a old bootloader on top of new bootloader version, downgrading is not allowed AFAIK
There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.
Hello Guýs,
Iam helpless and dont kow what to do right now. I got me TWRP and wanted to install a Rom but i bricked my phone i guess.
Iam trying to get back to stock rom with Odin 3.12.3 but i always get fails. I got a new PIT file with odin.
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any tipps would be very helpfull to me.
p.s. if i check the re-partition box i dont get any connection.
p.s.s. i have no kies but the Samsung USB Drivers installed
Michel93 said:
Hello Guýs,
Iam helpless and dont kow what to do right now. I got me TWRP and wanted to install a Rom but i bricked my phone i guess.
Iam trying to get back to stock rom with Odin 3.12.3 but i always get fails. I got a new PIT file with odin.
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
any tipps would be very helpfull to me.
p.s. if i check the re-partition box i dont get any connection.
p.s.s. i have no kies but the Samsung USB Drivers installed
Click to expand...
Click to collapse
kies is useless. your drivers are properly installed if Odin recognizes your device.
Download Odin 3.13.1 and try it again
Thanks I'll try when I am back home. I Cann only access download mode BTW. Else I stuck in a boot loop with this blue installing update screen.
Michel93 said:
Thanks I'll try when I am back home. I Cann only access download mode BTW. Else I stuck in a boot loop with this blue installing update screen.
Click to expand...
Click to collapse
as long as you can get to download mode, youre in good shape. From there, its merely a try-and-fail process of different Odin and firmware versions
Ty I was getting pretty despred after hours of fails and disappointment
Michel93 said:
Ty I was getting pretty despred after hours of fails and disappointment
Click to expand...
Click to collapse
it can get that way especially if youre downloading your firmwares from sammobile.com/firmwares directly. Takes FOREVAAAAAAR and then when it fails it gets SUPER irritating. Get the Frija firmware download tool here and the speed difference will blow you away. There is another firmware download tool out there too and i have it on my computer at home, but i cant remember what its called and the Frija tool is as good as that other tool anyways.
youdoofus said:
kies is useless. your drivers are properly installed if Odin recognizes your device.
Download Odin 3.13.1 and try it again
Click to expand...
Click to collapse
got the same problem with 13.1
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 5582 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<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> sboot.bin
<ID:0/005> param.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
HELL YEAH!!!
i think i got it!
I used the Firmware from "Frija", Odin 3.13.1 and a PIT-File from https://zfirmware.com/download-samsung-galaxy-s8-g950f-pit-file/.
The Problem with the connection was i had to enter Download Mode every time new an had to do the Pit with the Firmware together.
Thanks for ur help!
I will stay active here and try to helb other poor guys like myself.
Michel93 said:
HELL YEAH!!!
i think i got it!
I used the Firmware from "Frija", Odin 3.13.1 and a PIT-File from https://zfirmware.com/download-samsung-galaxy-s8-g950f-pit-file/.
The Problem with the connection was i had to enter Download Mode every time new an had to do the Pit with the Firmware together.
Thanks for ur help!
I will stay active here and try to helb other poor guys like myself.
Click to expand...
Click to collapse
right on, right on! yeah if you can get to download mode, youre usually good. From there its just getting the right Odin/firmware combo. Same holds true on 90%+ of most newer samsung phones
Hi,
I can't find stock for T555.
I have international model (according to samsung us support) but I did have some built in Hotel booking app on German language.
It's bricked and I can't turn it off.
On sammobile it's archived and I am not premium. So I downloaded firmware from galaxyfirmware.
Btw, any other method to root?
This one below didn't worked for me since I got seandroid problem:
[ROOT][TWRP]Samsung Galaxy Tab A SM-T550/T555/P550/P555/T350/P350/T355/P355
Port of CF-autoroot for the Tab A and Tab A plus. Supports all models. See the link below for details: http://forum.xda-developers.com/showthread.php?t=3124284 NOTE: does not support Marshmallow. To root MM install TWRP provided below and...
forum.xda-developers.com
I also tried to flash latest twrp and it didn't work.
How, tablet is still flashing btw.
It says binary size is too large : aboot
and warranty void 0x1 (4)
Tried flashing UK rom SM-T555_BTU_T555XXU1CRG1_T555BTU1CRH1_T555XXU1CQHA_T555XXU1CRG1:
Here is log:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> sec.dat
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> persist.img.ext4
<ID:0/005> userdata.img.ext4
<ID:0/005> meta-data/
<ID:0/005> meta-data/fota.zip
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device gave:unsupport dev_type
It almost flashed, like 90% then failed.