Database Users

[Q] return to stock rom failed, other roms failed

So long story short I'm trying to return to stock rom after using triforce, it was fun but I can't get the few "bloatwear" I actually use to install or work. (Exp.Sbeam, Snote) so each time ether it be odin, twrp, Phillis I get a message saying failed to install. On start up I get a message about know my kernel isn't correct and on odin download I have write protection enabled along with eMMc enabled. I've tried triangle away but it only reset my counter. And if I try any other rom it fails. Is there hope for me? And will you guild me out of this rutt?

Could you show us the Odin error you get?
Sent from my SPH-L720 using XDA Premium 4 mobile app

Based on your screen shot, I'm going to assume that you're not trying to Odin NAE. Download the NAE tar and you should be good to go.
Sent from my SPH-L720 using Tapatalk

I'll Give the NAE a shot thank you (sorry for the late reply work has been killing me for the last few months)
Phone Screen in Download mode
(Red) Odin Mode
(White)Product Name: SPH-L720
Current Binary: Custom
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
CSB-CONFIG-LSB: 0x30
(Gray)WRITE PROTECTION: Enable
eMMC BURST MODE enabled
(Red) START [224,1140]
SECURE CHECK FAIL : aboot
ODIN v1.85 on PC
<ID:0/005> File analysis...
<ID:0/005> SetupConnection...
<ID:0/005> Initialization...
<ID:0/005> Get PIT for mapping...
<ID:0/005> Firmware update start...
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All Threads completed (succeed 0 /failed 1)

holy ****
frostedunit I could kiss you! it worked!

i9500 no recovery partition, and unable to restore stock using odin

Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. Long story short, I no longer have a functioning recovery partition.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is factory unlocked.
The text displayed in Odin Mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<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> boot.img
<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)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!

Coolcise said:
Hello.
I got a new Galaxy S4 (I9500) this October, and decided I would go ahead and install custom recovery on it. Me thinking I can get anything to work did not heed the warnings that this model does not support it go ahead and try anyway. Long story short, I no longer have a functioning recovery partition.
I have tried to follow several guides, most of which tell me the same thing:
Get Samsung drivers (not Kies)
Download Odin (one version or another)
Get the I9500 Firmware and install using Odin.
My phone is (from the sticker below the battery):
MODEL:GT-I9500
FCC ID: A3LGTI9500
SSN:-I9500GSMH
It is factory unlocked.
The text displayed in Odin Mode:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
I have tried flashing both 4.4.2 (as it was delivered with) and 5.0.1, but I get the same error:
<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> boot.img
<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)
The error that is displayed on the phone is:
SECURE MAGICCODE CHECK FAIL : boot
Any help would be greatly appreciated!
Click to expand...
Click to collapse
You don't have an i9500. Whoever told you that was lying. You have an SGH-I337 which is a completely different model. You got an AT&T model. You are trying to flash the wrong firmware.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-att
Bottomline you got a ****ty device with a locked bootloader. You can forget about custom recoverys and custom roms.

Lennyz1988 said:
You don't have an i9500. Whoever told you that was lying. You have an SGH-I337 which is a completely different model. You got an AT&T model. You are trying to flash the wrong firmware.
Here is the section for your device.
http://forum.xda-developers.com/galaxy-s4-att
Bottomline you got a ****ty device with a locked bootloader. You can forget about custom recoverys and custom roms.
Click to expand...
Click to collapse
Model number in settings say GT-I9500, and I can use my Norwegian GSMH SIM card with it, which I would not have been able to on a AT&T phone. Anyway, at this point I don't care about custom recovery etc, I just want it working.
Edit: I also got Cyanogenmod working before I messed up the recovery

Coolcise said:
Model number in settings say GT-I9500, and I can use my Norwegian GSMH SIM card with it, which I would not have been able to on a AT&T phone. Anyway, at this point I don't care about custom recovery etc, I just want it working.
Edit: I also got Cyanogenmod working before I messed up the recovery
Click to expand...
Click to collapse
It's irrelevant what it says in the settings menu. It really easy to change it.
It's the part in download mode that matters.
PRODUCT NAME: SGH-I337
Alright if you say the already had CM on it, then you still have an unlocked bootloader. Whatever you do, do not flash a stock AT&T rom or it will upgrade your bootloader.
Here is TWRP recovery.
https://www.androidfilehost.com/?fid=24052804347763625
Flash it using Odin. 99% of Odin errors can be resolved by using a different usb port and/or using a different usb cable.

You've a franken phone.
Sent from my GT-I9500

system upgrade, firmware, USB debugging problem

Hello everybody,
I bought a Samsung Galaxy Note 3 (SM-N9005) phone. Firmware: N9005ZHUENF1. Android 4.4.2.
I tried to update the system, but the phone said "I am fresh". But, it is not true, because my girlfriend has a same phone and it updated across the OTA.
I installed the KIES to the my PC and my phone do not work with it. When I connect the phone to the PC with a USB cable, not working. When I connect my girlfriends phone everything nice.
I enabled the USB debugging mode, but it is not working. When I connect the phone to the PC with a USB cable the question is not arrive that I would like to enable the debugging mode. When I connect my girlfriends phone everything nice.
I think my phone is rooted, because I checked it with an app, and the app said "Yes, rooted".
My questions are:
- is it possible to upgrade my phone to the Lollipop?
- is it possible to put into the phone the original firmware (if it will be necessary)?
- is it possible to enable the USB-debugging mode?
I am waiting for your asks.
Best regards,
Zoltan

is it possible to upgrade my phone to the Lollipop?
Yes flash a firmware via Odin see stickies .
- is it possible to put into the phone the original firmware (if it will be necessary)?
Yes as above .
- is it possible to enable the USB-debugging mode?
Yes but its not required .

This the message in the Odin window:
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone:
SECURE CHECK FAIL: about
Please help!

What are you flashing ??

I downloaded the 5.0 lollipop and I would like to upgrade.

What firmware there are multiple firmwares for many variety 's of Note .

In the phone:
N9005ZHUENF1
ok, now i see that not the same what i downloaded

Odin failed flashing aboot.mbn which means the rom was not made for the phone or the bootloader in the rom is too old.

OK, I do not understand.
When I step into the download mode (volume down+home+power) I see these:
Odin mode
Product name: SM-N900A
Current binary: Samsung official
System status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
Qualcomm Securebot : Enable (CSB)
Ap SWRev: S2, T2, R2, A3, P2
Write Protection: Enable
OK, but in the settings menu my model number is: SM-N9005.
SM-900A or SM-N9005?
Please help somebody!

SM900A.
If that's what Odin mode says .
If its a new phone return to the vendor .
What does it say under the battery ??

under the battery: SM-N9005
in the recovery menu: kot49h.n900aucucnc2

Reads as possible fake.
Sent from my SM-N920C using XDA-Developers mobile app

The phone is a note 3 with a motherboard from AT&T based on the model number of Sm-n900a in download mode.
It appears that the phone has an AT&T motherboard in a note 3 international body.

So, what can I do?

All you can do is flash the latest rom for the n900a which is lollipop. The bootloader is probably locked which means you cannot install cwm or twrp. Only custom recovery that will work is safestrap.

thx, but I do not find it. Give me a link please.

gutanier said:
thx, but I do not find it. Give me a link please.
Click to expand...
Click to collapse
Your device is an AT&T Note 3 disguised as an international one, as said before.
I already had this experience with a Sprint Note 2.
So if you want simply upgrade to Stock Lollipop, here is the stock image.
If you want root, custom recovery and maybe custom ROMs, please follow this guide.
There are many customs roms supporting your device, so head to the AT&T Note 3 forum for more infos.
Good luck

THX folks, I did it, I have Lollipop on my Note 3. THX again. :good:

Hi folks again.
Mission 2: root.
How can I do it simple? SM-N900A Lollipop 5.0

http://forum.xda-developers.com/note-3-att/general/root-lollipop-att-note-3-safestrap-t3132475

Another bootloop issue

Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy

Hello again:
Zero replies, did I omit important information in my first request -- or am I just rehashing previous inquiries about boot loop problems? (I have read through all posts relating to boot loops but found no answers that solved the to write to Nand failures). Forgive me if it's here and I simply didn't recognize it. . .
So (succinctly) why might Odin fail to write when attempting to reload the original firmware: . . . NAND Write Start!! . . . FAIL! (Auth) . . .Complete(Write) operation failed. . . .All threads completed. (succeed 0 / failed 1)
What might I be doing wrong, or what might I try instead?
Thanks again
flyyboyy said:
Apologies for the repost, found this to be a better place to pose the plea for assistance
_____
Hello all. . .
Longtime reader (learner), first time poster. Trying to bring son's GS5 back to life -- it's stuck in boot loop ("Samsung GALAXY S5" splash screen appears, reboots). Unknown cause, not due to any flashes, ROMs, ROOT, etc
All attempts to enter recovery mode (Vol up + PWR + Home) initially successful (get blue text: RECOVERY BOOTING. . . .) then display goes black, repeats. -- never see Recovery screen. Yes, I've cycled power, battery out, wait, etc, etc.
Can successfully enter Download mode, Odin v3.09 recognizes connection, but all attempts to write to memory fail.
GS5 displays:
ODIN MODE:
PRODUCT NAME: SM-G900P
CURRENT BINARY: Samsung Original
SYSTEM STATUS: Official
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1 T3 A1 A3 P1
SECURE DOWNLOAD: ENABLE
UDC START
<press Odin Start button>
Odin displays:
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Device display adds line:
SW REV CHECK FAIL : [aboot]Fused 3 > Binary 1
____
Cannot determine build number and original box long gone. I've downloaded a couple firmware zips from sammobile (Sprint CDMA) using files nearest to best guess for purchase date. Is it necessary to match the exact files which originally came installed or should later firmware releases also normally load? In other words, is the fail due to trying a wrong firmware revision?
Any other info I need to include here? Thanx in advance!
flyyboyy
Click to expand...
Click to collapse

Same thing with me.. patience gets you through it..
The same thing happened to me, same phone and same contract carrier (Sprint).
I bought my phone from a third party who apparently restores it to near-mint condition. The OS it had was one of the first releases of 6.0 /marshmallow. I tried downgradingit back to 5 / lollipop because i heard that call recording was still enabled with that OS.
I used Odin versions 3.7 thru 3.10 i believe and flashed every version of 5 that was listed on sam mobile and samsung 's site and all of them either failed to initiate- citing the same readings and failure reasons in odin that you mentioned - or they "succeeded" and resulted in boot loops.
I also failed to flash any of the earlier ROM versions of android 6 than the one my SM-G900P phone came with.
Finally, i succeeded in flashing 2 types of ROMS, the version of 6 my phone started with, then subsequently the most recent version released earlier in march 2017 (this month).
Conclusion: i believe the order that you flash these roms for our model phone with our carrier matters. Flash your phone with ROM images from the version that it came with, and continue sequentially and chronologically until your boot screen finally shows something other than that lovely little sprint logo
Good luck with your son's phone, and please let us k ow how it goes..... as i think this may be a recurring theme we may see more often in the future. I imagine the problem lies with either odin, samsung sm-g900p, or the sprint/cdma ROMa we're dealt.
-Rob

Have you tried samsung kies yet? Odin is for rooting your phone. Samsung kies will put updated firmware in your phone. I have used it several times in the past on a sam phone. It will work. Its from samsung company.

SM-T580 Soft Bricked - Odin Wont Flash Stock Firmware

I have the Galaxy Tab A 10.1 SM-t580. It was on 8.0 stock prior to this. I attempted to flash TWRP a couple of ways to no avail. I did a factory reset and attempted another method, but I believe I forgot to turn on OEM Unlock after the reset. Odin now will flash a TWRP successfully, but trying to boot into recovery either loops or presents me with glitchy horizontal lines. Trying to flash the 7.0 stock firmware (XAR) from Sammobile results in failure (maybe because it has an older bootloader?). I've tried just the AP, AP and BL, and AP, BL, and CSC. They all fail. There doesnt appear to be any working OS on the device at this point. The only thing I can access is download mode.
After trying the flash stock firmware I get this message in odin:
Code:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in download mode I have the following messages at the top:
Code:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-T580
CURRENT BINARY: Custom
SYSTEM STATUS: Official
FRP LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0500)
RP SWERV: B:4 K:1 S:2
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 2
Any help would be super appreciated.

Took a lot of figuring out. But My bootloader would only accept the latest version of the stock firmware (Oreo) and I had to dig to find a working TWRP. If anyone has any questions I gothca.

I was having the same issue and bricked/unbricked my tablet a few times before figuring out it will only take the latest firmware. Which version of TWRP worked?
I'm trying to downgrade as the last update caused an "Authentication Error" every time I tried to connect to wifi.

Sykoknot said:
Took a lot of figuring out. But My bootloader would only accept the latest version of the stock firmware (Oreo) and I had to dig to find a working TWRP. If anyone has any questions I gothca.
Click to expand...
Click to collapse
Did you find a working TWRP for Oreo? Can you post the link or say the versión of TWRP?
I used the twrp-3.2.3-0-gtaxlwifi.img.tar (lastest by now) but only had the red vertical lines in recovery mode
---------- Post added at 01:11 PM ---------- Previous post was at 12:47 PM ----------
Sykoknot said:
I have the Galaxy Tab A 10.1 SM-t580. It was on 8.0 stock prior to this. I attempted to flash TWRP a couple of ways to no avail. I did a factory reset and attempted another method, but I believe I forgot to turn on OEM Unlock after the reset. Odin now will flash a TWRP successfully, but trying to boot into recovery either loops or presents me with glitchy horizontal lines. Trying to flash the 7.0 stock firmware (XAR) from Sammobile results in failure (maybe because it has an older bootloader?). I've tried just the AP, AP and BL, and AP, BL, and CSC. They all fail. There doesnt appear to be any working OS on the device at this point. The only thing I can access is download mode.
After trying the flash stock firmware I get this message in odin:
Code:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<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> sboot.bin
<ID:0/006> param.bin
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in download mode I have the following messages at the top:
Code:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-T580
CURRENT BINARY: Custom
SYSTEM STATUS: Official
FRP LOCK: OFF
Secure Download: Enabled
WARRANTY VOID: 1 (0x0500)
RP SWERV: B:4 K:1 S:2
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 4, BINARY: 2
Any help would be super appreciated.
Click to expand...
Click to collapse
Same problem and I solved it flashing the content of this file CF-Auto-Root-gtaxlwifi-gtaxlwifixx-smt580.zip
Extrated from this documentation: w ww.techmoviles.com/rootear-galaxy-tab-a-sm-t580-sm-t585-con-cf-auto-root/ (fix the blank between the w)
This flash don't load a working TWRP in oreo, (because it is for nougat), but it fixes the recovery on oreo restoring the Android recovery.
I hope it helps you

OK. Got given a TAB 10.1 a few weeks back and decided to boot up Odin for the first time since my Note3. Hated the Samsung stock ROM so went through the same journey of trying to install TWRP over Android 8 only to find it soft bricks the tab. EVENTUALLY realised I could only recover with Android 8 which i have.
SO question is can I install TWRP over Android 8 or do i have to downgrade. If yes to a downgrade is it just a case of grabbing Android 7 off Sammobile?
Thanks in advance.

Use this TWRP. It should work: https://forum.xda-developers.com/showpost.php?p=78148216&postcount=169

RedNas74 said:
Use this TWRP. It should work: https://forum.xda-developers.com/showpost.php?p=78148216&postcount=169
Click to expand...
Click to collapse
There was a newer one on the same day though - it's what I'm using and it works fine
Then again my tablet was on stock Nougat - so no idea if @xballumx can use it on Oreo ... but I don't see why not since it still works on an Oreo custom rom :fingers-crossed:

Hey bro
you are using the wrong flash file your phone Binary is 4
check that the flash file name contains U4

wahidkurdo said:
Hey bro
you are using the wrong flash file your phone Binary is 4
check that the flash file name contains U4
Click to expand...
Click to collapse
Pretty sure that over a year and a half later they've sorted their issues ... or threw the device under a moving truck already :laugh: