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.
Related
Hello,
I am having some issues with my S5 G900A (AT&T). Any help I could get in order to get any functionality back out of my phone would be greatly appreciated.
I recently update via OTA to lollipop, but I wanted to get it rooted to try it out. The first thing I attempted to do was to revert the firmware back to 4.4.2 by using Odin. I used three different sources for the G900AUCU1ANCE model, the last of which I got from here, which I found from this post.
However, this did not work, and now I am forever stuck on the firmware update page.
When I ran the Odin program, the program failed and output the following:
<ID:0/007> Odin engine v(ID:3.1005)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> persist.img.ext4
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the phone side, I get the following messages on the screen. The messages that appear after running Odin are bolded.
ODIN MODE
PRODUCT NAME: SM-G900A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (csb)
RP SWREV: S1, T2, R1, A3, P1
SECURE DOWNLOAD : ENABLE
UDC START
SYS REV CHECK FAIL : Refer 2 > Binary 1
SECURE CHECK FAIL : system
(Downloading... Do not turn off target!!)
Click to expand...
Click to collapse
At this point, if I restart by pulling out (the battery), and then turn it back on normally, then I get back to the 'Odin Mode' screen, but with the large message on the bottom: "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
This message will appear when the following keypresses are used to turn the phone on:
Volume up + Lock
Volume down + Lock
Lock
Home + Lock
Volume up + Volume down + Lock
Volume up + Lock + Home
The following keypresses don't do anything
Volume up + Volume down
Volume up + Volume down + Home
Volume down + Home
Volume up + Home
Finally, if I do the following keypress:
Volume down + Lock + Home
I get the familiar warning screen:
Warning!!
A custom OS can cause critical problems in phone and installed applications.
If you want to download a custom OS, press the volume up key.
Otherwise press the volume down key to cancel.
Click to expand...
Click to collapse
If I press the volume down key, then I go back to the same Odin Mode screen with the "firmware upgrade encountered an issue" message from before. If I press the volume up key, then I get the Odin Mode screen (that always stays the same), but with "Downloading... Do not turn off target!!" as the message instead.
I also tried using Samsung Kies, though that method seems to be frowned upon by everyone. It clearly downloaded something and looked like it was installing something, but then it told me that I should run the emergency recovery process using an emergency recovery code. In the alert window, there was clearly a space where an emergency code was supposed to be, but there was no emergency code. Therefore, I was not able to get any farther using Kies.
I have read many posts mentioning that Odin can be very fickle, so I took the liberty of trying using two different USB cables and tried all 4 USB ports that are on my laptop, and I tried each of those three times. I also ensured that Kies and its background processes were not running when I utilized odin.
I also tried re-writing the PIT file, which I found from here, but when I did that, I got
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
In Odin and "SECURE CHECK FAIL : PIT" on my phone window.
After exhaustive googling, I am not too sure of what to do anymore, and would appreciate if someone could help.
Bootloader is locked, not sure there is anything you can do
*Detection* said:
Bootloader is locked, not sure there is anything you can do
Click to expand...
Click to collapse
2 questions, which error message points out to you that the "bootloader is locked," and does this mean that I would need to take my phone to AT&T to get it serviced?
<ID:0/007> FAIL! (Auth)
Tells me the Secure Boot Key is failing to authenticate
--
From what I've read, AT&T S5s are bootloader locked, as are a few other carrier branded ones
What is actually wrong with the phone? Just that you want to downgrade to Kitkat and root?
Or is there actually something wrong with Lollipop?
It is a very well known fact that after upgrading from KK to LP, you should factory reset the phone, KK leaves behind rubbish files that cause all sorts of issues, resetting cures a lot of them
Oh I see, thanks!
Nothing really wrong with it, I just wanted to try rooting the phone.
Unfortunately the only known method to root Lollipop is via ODIN, but it's still a fairly new OS so never say never about the devs finding an exploit that can be used with a locked bootloader
You cant downgrade from lollipop to kitkat once you take the ota for lollipop, as you can see here. You need to get the oc4(lollipop) firmware files and flash that to unbrick, they are in the att s5 general section.
Sent from my twi5ted SM-G900A using Tapatalk
Thanks, I ended up taking it to best buy and having the guy there reset the firmware. Pretty sure he used something called SMART or something to do it
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
Hello, so I'm having a huge problem right now, that seemingly came out of nowhere.
My phone is stuck on "Samsung Galaxy S7 Edge" screen logo and can only enter download mode, nothing else.
All I did was download the firmware update that popped up OTA. Something must have failed and I was greeted with a permanent freeze on that part.
The update that I've downloaded was called - G935FXXU1DQB7/G935FSEB1DQB2/G935FXXU1DQB3 with the file size of 1224.14 MB
It has failed once before but it wasn't a brick. Said something about mounting data error in a recovery mode. A day later I've tried to re-download and install the update again and this is the place I'm in right now.
My phone is the European Exynos variant, not sim locked. I'm from Lithuania, but I somehow doubt my model had the Baltics firmware as I don't think the 7.0 is released there yet.
So far I've tried installing stock firmwares from UK, Poland, Baltics region. Both 6.0.1 and 7.0 yield the same results. Different Odin versions. I can confirm that the USB ports work and there is a connection, because flashing a single random .tar file passes and reboots the phone., but does nothing for me (like installing extracted hidden.img.tar). Ends up at the same splash screen.
Every attempt to flash anything has to be with the download mode rebooted or else it doesn't do anything. (Maybe this is normal)
All threads completed. (succeeded 0 / failed 0)
When I flash the AP, BL, CP, after a while (a minute or so) I get a fail without seemingly any progress.
Complete(Write) operation failed
Usually hangs on the recovery.img, depending on what I try to flash.
When I flash CSC, Pit file, or leave a ticked repartition box without including any of them, I instantly get
Re-Partition operation failed.
So naturally this always triggers if I flash all 4 of the items.
I have also tried Smart Switch. The only problem is I currently don't have my S/N number, because some internals and all of the outside of my phone was changed under the insurance, including the back where I believe the number is found, so I've tried S7 Edge S/N number of a friend of mine. I believe our phones are different, because his firmware is from Baltic region (SEB) which doesn't even have 7.0 out. I'll try getting my S/N number through the carrier I bought the phone in. Anyway, Smart Switch throws an error about "Failed to recognize software update mode" after downloading the (SEB region) firmware and stops there. I'm afraid even my own S/N number won't help.
This is what my download mode says
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-G935F
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
FRP LOCK: ON
Secure Download: Enabled
WARRANTY VOID: 0 (0x0000)
RP SWAEV: B:1 K:0 S:0
I feel like all of this mess is caused mostly by the Factory reset prevention lock?
I don't want to trip Knox and void the warranty by installing a custom recovery, which would maybe help me? Does anyone have any ideas? I'm at this for like 10 hours already and desperate. Hope I don't need to give it in. No ability to even turn off the phone, what BS is this...
Can't post images yet, sadly.
same here. but for me now odin say:
<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> sboot.bin
<ID:0/005> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
bassini said:
same here.
Click to expand...
Click to collapse
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?
Rakanoth said:
greenman from sammobile forums suggests
that "This is looking like you have a damaged emmc. The re-partition should have been successful."
I think we're out of luck on this one. The only strange thing is that we've probably installed the same piece of software that killed it. What are the odds?
Click to expand...
Click to collapse
For me it was a newest XEO firmaware.
And also its after trying re-pa...
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:
I'll try to give as many details as I can.
Recently I did a root, which worked perfectly fine. Didn't know what I was doing, so I looked around and downloaded Xposed and did all the steps to get it on my phone. After opening it, it asked to download additional firmware or updates or something. I agreed, and the system rebooted once it downloaded what it needed to. Then, when it rebooted, it told me that it was unable to authorize or verify, or something. Essentially it wouldn't let me back into my phone and I didn't know what to do. So I downloaded the most current firmware for my model from Updato, but it didn't seem to work. I tried doing just the AP, then doing the BL-AP-CP-CSC, tried both Home and non home versions as well. After that, if I'm not in download mode, it tries to update software, and then runs a quick string, and then repeats, which I assume is just a textbook case of boot looping.
Information on Download screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-G935U
SYSTEM STATUS: Custom
FRP LOCK: ON
WARRANTY VOID: 0x0
DUALCOMM SECUREBOOT: ENABLE
RP SWREV: B8(2, 1, 1, 1, 1)
SECURE DOWNLOAD: ENABLE
SW REV CHECK FAIL: [boot] Fused 8 > Binary 1
Click to expand...
Click to collapse
The last line comes after trying to use the AP only
Odin log:
<ID:0/006> Odin engine v(ID:3.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 4797 M
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> NAND Write Start!!
<ID:0/006> SingleDownload.
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Can't post links, but on Updato, under SM-G935U, the first one with 8.0.0 is the one I used.
I tried some suggestions I found looking around, like changing out the USB cable, but ultimately it didn't help and it was fine to use to flash the original root in the first place, and I have Samsung drivers installed.
I would really appreciate some insight. Appreciate it.
sounds like you took an OTA while rooted.
I think you're ODIN flash might be failing because you're OTA might've updated your bootloader.
You need to determine the build you're on from recovery if you can get there and make sure you're flashing a build with the same (preferably) or greater (bad if you want to go back) bootloader. The 5th digit from the right is the bootloader version.
First of all - are you sure the phone got rooted in the 1st place? As your KNOX seems still 0x0 you probably did not modify too much...
Anyway - something to try is to flash the stock with additional PIT file included which rewrites the partitioning from scratch. Try that one