Database Users

[HELP]Galaxy note 3 stuck on boot logo

hi i am using note 3 N9005 model with official poland lollipop 5.0 update for over a month but today suddenly my phone got some lag and tried restarted but fail as it kept stuck on samsung boot logo forever...i tried removing battery and waiting but still there was no good... then when i tried booting in recovery ( TWRP which i flashed while rooting) the same thing happened and mobile kept stuck on samsung logo and at top left it was written -
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit: recovery
I have a good experience in flashing , odin and all this recovery stuff but i have never seen mobile not even getting into recovery...as last resort i thought of flashing the official rom image from odin .. but when i tried it showed me FAIL message in red box where connected shows...and in log it said -
<ID:0/004> Added!!
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
I am very much in need of some serious help as i use this mobile as my daily driver..any help will be appreciated!!:good:

some silent update from samsung messed your phone.
put in download mode and reflash another official rom with odin.

dancapitan said:
some silent update from samsung messed your phone.
put in download mode and reflash another official rom with odin.
Click to expand...
Click to collapse
thanks for help but that also doesnt work...same error again in odin..

[Q] [Troubleshooting] Soft Bricked NJ4/NB1

Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MF3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Update: Even though there are a bunch of warnings against it I went ahead and used Odin to redo my PIT file. Now I can boot into recovery. About to wipe data/factory reset.
Update 2: After the factory reset I tried to flash NB1 again using Odin. Still failing near the beginning, but with all my resetting I was finally able to get into the phone itself (WiFi still won't turn on). Also when starting up I no longer have the Samsung Custom with the lock (I'm assuming this means my root is gone for now). Now to figure out a way to fix the WiFi....
Update 3: My baseband version is NJ4 and the build version is NB1. I'm pretty sure this is why the WiFi is not working. I am now following this guide http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814 to get to OC3. Hopefully this will fix the WiFi issue...

ava12ice said:
Hey everyone,
So I've finally had my first soft brick :crying: Hopefully I am missing some easy solution. So here's the background. This morning I was running MK3 with root. Using this guide http://forum.xda-developers.com/galaxy-s4-att/general/guide-odin-to-stock-updating-rooting-t2926642 I was able to upgrade to NB1 using Odin. Then I upgraded to NJ4 using stock recovery added root using towelroot v3. Then the trouble began.
I noticed my WiFi wouldn't switch on so I performed a stock recovery wipe data then factory reset. This didn't fix the problem. I then tried to use Odin to go back to NB1 because my WiFi was working back then. It failed halfway through (message on Odin) so I left it sitting for about 30 min. The phone never changed anything so I removed the battery and tried Odin again. It failed again. I decided to try to boot into stock recovery and was unable to do so. I have the screen with a phone (dot)(dot) yellow triangle (dot)(dot) computer saying Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Tried Odin again and I actually got about 75% through the process but it failed again. Now it makes the same amount of progress every time and continues to fail.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<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> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
My overall goal is to upgrade to OC3 with root access but right now it seems like I just need to unbrick my phone. Any ideas?
Click to expand...
Click to collapse
Mk3 is a sprint s3 modem, make sure you're in the right forum. As far as what else to try, I'm not sure.

Sorry not MK3, I meant MF3 (original post edited as well)

S4 does not run anymore after flashing TWRP

Hey guys,
i gut some serious problems with my Galaxy S4 (GT-I9505)
I was running Cyanogen Mod 12.1 with CWM Recovery. After trying to update to CM13 and the appropriate Gapps i noticed some problems installing gapps with CWM. After searching the internet i decided to try it with TWRP instead of CWM. So i used the App Rashr Flash Tool to Flash the latest TWRP Recovery.
After flashing TWRP i rebooted the device and got stuck at the Samsung welcome screen. In the right upper corner is displayed the following:
RECOVERY BOOTING. . . .
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Unfortunatelly the phone does not load the recovery or start the OS. The only option i recognized is to enter the download mode by pushing Home + Vol.Down + PWR.
So i tried to use Odin to reinstall TWRP correctly over download mode and this is what Odin puts out.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
When i now restart the phone i got following message on the screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
After installing Kies it says that my device is not supportet...
So no i have no idea what else i can do to get my phone running again...
Does anyone has an idea?
Best Regards and thanks

Did you try flashing the latest stock ROM from sammobile.com?
Maybe use Odin to flash the latest version of TWRP to see if you can enter recovery?

The solution is easy. Use a different usb port / different usb cable.

Well a different USB-Port got me one step further.
It seems that odin flashed the recovery successfully:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that my phone booted back into my current android / cm OS
Unfortunatelly, if i try to reboot directly into the recovery, i get stuck in the samsung welcome screen again. Means i can not access the recovery...

Use a different recovery thats my advice, i have a same issue as you maybe someone could help me, i open a new thread there also

Try this: unchecked everything except f.reset time in Odin before flashing TWRP, connect phone, flash TWRP, when you see the word "RESET" in the status windows, remove USB cable, remove battery, replace battery, use button combination to boot into recovery. When the phone powers up, let the power button go but keep holding home and volume up.

somehow i fixed it...
i re-re-reflashed twrp and suddenly everything went fine.
Thanks for your help and real quick responses!
great forum!

[Need Help] G935A Bootloop

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

Reset G950FD with detection and start up issues

Recently, I reset my old Galaxy S8 and restarted it but was met with the "Only Official Binaries are Allowed to be Flashed" issue.
After a large amount of time spent trying to flash official stock firmware on, I am faced with :
"<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed."
I have reinstalled drivers as well as attempted to go into TWRP recovery which is presumably why this issue occurred.
Any suggestions or solutions are greatly appreciated.
Changed to Odin 3.12.7 from 3.13.1 and got:
"<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4"
Is also stuck on set partition

av3nje said:
Recently, I reset my old Galaxy S8 and restarted it but was met with the "Only Official Binaries are Allowed to be Flashed" issue.
After a large amount of time spent trying to flash official stock firmware on, I am faced with :
"<ID:0/005> SetupConnection..
<ID:0/005> Complete(Write) operation failed."
I have reinstalled drivers as well as attempted to go into TWRP recovery which is presumably why this issue occurred.
Any suggestions or solutions are greatly appreciated.
Changed to Odin 3.12.7 from 3.13.1 and got:
"<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1207)..
<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> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin.lz4"
Is also stuck on set partition
Click to expand...
Click to collapse
youre probably using the wrong version of Odin. Go get a fresh copy of v3.13.1 and try it with that
and/or a fresh download of the firmware from www.sammobile.com/firmwares but id use frijas firmware download tool in all honesty, its about 12 times faster

youdoofus said:
youre probably using the wrong version of Odin. Go get a fresh copy of v3.13.1 and try it with that
and/or a fresh download of the firmware from but id use frijas firmware download tool in all honesty, its about 12 times faster
Click to expand...
Click to collapse
Just attempted to flash Oreo 8.0 with a fresh Odin 3.13.1 and I was given the same "Complete(Write) operation failed."

av3nje said:
Just attempted to flash Oreo 8.0 with a fresh Odin 3.13.1 and I was given the same "Complete(Write) operation failed."
Click to expand...
Click to collapse
After using a different firmware, it worked fine. Thank you for your suggestion.

av3nje said:
After using a different firmware, it worked fine. Thank you for your suggestion.
Click to expand...
Click to collapse
glad to help!