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
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> emmc_appsboot.mbn
<ID:0/006> lksecapp.mbn
<ID:0/006> FAIL! (Auth)
Please help me I dont know what im doing wrong. I tried rooting but got stuck in boot loop so i downloaded stock but keep getting error in odin
message on screen says SW REV CHECK FAIL : [system]Fused 3 > Binary 1
I tried 1 more time but without BL and got this
<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)
Ok so, I am trying to root my s8(SM-G950U) using this guide: https://forum.xda-developers.com/galaxy-s8/development/samsung-galaxy-s8-root-snapdragon-t3659305 But every time I try to flash it get
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> abl.elf
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
And if you cant tell it fails and dose not work! Any help would be Apprciated!
I've tried to root my G950U also and failed. My Verizon version of the S8 has the latest updates and no root is available.
Solved!
now im sure the emmc chip a.k.a. the storage on the mainboard is not working correctly I have to buy a new Mainboard. Does anyone know how much note 4 phones are affected by this?
If I try to reboot my Phone is wont start again. I need to remove the battery and wait at least 20 sec before I can boot up the device.
My phone curently operates with RR/N (restruction remix nugat) I have instaled this firmware over TWRP accoring tho this tread https://forum.xda-developers.com/note-4/snapdragon-dev/rom-resurrection-remix-5-8-0-t3523130
I had installed this rom on the same day I recived the phone (I dont think the error comes from the rom)
even in TWRP the boot to system doesn't work it seems like the phone stucks somewhere while reboot.
somtimes when I boot up the phone it automaticaly goes in the download mode and at the top line stands:
coud not do normal boot
mmc_read failed
In odin sometimes the feedback is PASS! and Sometimes failed
I have downloaded modem, bootloader and Stock_ROM from here https://androidfilehost.com/?w=files&flid=26335 and flashed it over odin:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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> sdi.mbn
<ID:0/005> NON-HLOS.bin
<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> 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)
the auto reboot funktion from odin seems to work well.
sometimes, after removing the battery and ~20 sec waiting the phone does not respond to the press on the powerbuton and seems to be dead. but if I plug it over usb in to my windows computer the system sound corresponding to "Error in device connection" comes.
After removing the Battery and waiting around 20 min sometimes less, I can sometimes turn it on
what should I do? buy a new Motherboard on ebay or is there something i can doo to fix it?
thank for your responses
PS: sorry for my bad english i'm from switzerland and 16 yo
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.