Hi there,
I really need a quick few minutes of help. I began the night last night by trying to upgrade safestrap from 3.72 to 3.75, for what I later learned to be for no good reason. Anyway, I ended up wiping my entire internal storage including the root files, which forced me to odin back to MJE from NC2. So then I installed MJE and let the system upgrade to NC4. Then I proceeded to root and safestrap my system with success (including installing busybox). I then rebooted into recovery and flashed the Eclipse rom (I've tried stock and Rom-Slot1) and then rebooted into download mode and Odin'ed the NC2 kernel, which results in a fail every time. The odin log says it falis after aboot.mbn every time.
Please consider helping me!
Thanks!
P.s. This is the odin fail log.
<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> NON-HLOS.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've been recently trying to unlock my new S5 Sport. The problem I have is I didn't know that by upgrading to Lollipop I wouldn't be able to use some tools designed to unlock it. The next thing I tried was downgrading to make my device compatible with the tools, but I keep on having the same issue in Odin. Here is the log btw:
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<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> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now, if anyone has found a solution to this problem or can tell me what I am doing wrong I would really appreciate it.
I just can't seem to find any root method for my galaxy a3 SM-A300FU running on marshmallow 6.0.1.
So if anyone can help it would be very appreciated.
Check out this thread
http://forum.xda-developers.com/showthread.php?p=69290521
Sent from my SM-N910C using Tapatalk
Still can't even install twrp, this is the log file from odin.
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/005> Removed!!
OK I did it. Here is how. I went to chainfires website then I found cf auto root file for my device. I downloaded that then,
flashed it through odin and it was rooted. Once it was rooted I downloaded flashify app to flash twrp recovery but it didn't work,
so I went back to my computer and flashed twrp recovery image through odin. And now it works perfectly.
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
i just recently got gifted an old s8 and i want to root it with all the mods i have on my s5 (system wide adblock, custom rom, xposed framework mods, root ect.) but any time i try to flash TWRP with odin it ends up with a fail. from some research i think its the knox security **** that Samsung installs but im not sure how to bypass it. i have already tried to flash the SM-G950F_1_20200324151741_69ybtdjdbt_fac rom.
odin logs:
<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> Removed!!
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)