Extra notes: I took the Verizon Update Last Week while rooted which screwed up my system so I thought I start fresh, that's what caused this whole fiasco.
I'm having some issues here following this guide: http://forum.xda-developers.com/veri...volte-t2879348
I ran into a problem after flashing the vulnerable kernel.
When I tried to flash a full stock rom(or any rom) I get an error in 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> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on the phone
SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1
I can still seem to flash both the kernels in Odin with no issues, and I tried to repartition with the pit file from this thread: http://forum.xda-developers.com/show....php?t=2784880 But still with no luck.
I have a Verizon S5
Booting again!
I found I was able to boot again, but will hold off on rooting again. Here's what I did:
Downloaded Modem and Kernel for OC4 from http://forum.xda-developers.com/show....php?t=2784880
From Odin 10.4 Entered Kernel in PDA and Modem in CP.
Flashed it successfully!
Let it sit at the Verizon Logo for about 5 minutes!
Not sure if I can flash full roms from Odin or not, but I'm relaxing with this for now.
I'm not sure if it may be related to OC4's update blocking downgrading?
Extra Info:
Version: 5.0
Baseband: G900VVRU1BOC4
Kernel: 3.4.0
Build: LRX21T.G900VVRU2BOE1
I am having same fail, I've read that it's due to us taking that last update a week ago, that's impossible to downgrade from or root.
Sent from my SM-G900V using XDA Free mobile app
gerland said:
I am having same fail, I've read that it's due to us taking that last update a week ago, that's impossible to downgrade from or root.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I did take that update, it screwed up my system so I thought I'd start fresh... may have been a mistake. But I'm up and running now fortunately, I still can't flash any kind of ROM anymore though.
Did you stay on OE1 or OC4?
XNO said:
Did you stay on OE1 or OC4?
Click to expand...
Click to collapse
I'm on OC4
I am running into the same issue. odin won't flash anything. so now I am soft bricked. I tried to flash a stock image and bootloader but it keeps failing.
Related
Hi
My phone is N910U and it's CSC code is BRI (Thailand)
I was waiting for lollipop update, but it seems that only some countries have received the update.
So I decided to chage CSC to whatever the New Zealand CSC is to get the official update.
My phone isn't rooted and it runs stock rom.
While I was trying to flash recovery.tar via odin, it shows an error:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I used correct recovery file, and this happens when I want to flash autoroot too.
USB debugging on, download mode, stock USB cable, reinstalled driver
Does anyone know how to resolve this issue?
Also, can I just download New Zealand firmware and flash it via odin?
Will my phone not brick and be able to use it in the UK?
Any help would be very appreciated
EDIT: FIXED - Disable reactivation lock
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
absinthesummer said:
Do you have reactivation lock enabled? If so, disable it before flashing stuff in odin
Click to expand...
Click to collapse
Thanks for your reply
the reactivation lock was enabled, so I disabled it. But it is still not working.
It shows slightly different error
<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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I really have no idea what went wrong.
Do you have any clue?
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
absinthesummer said:
Have you tried flashing cf auto root since disabling reactivation lock? Typically in my experience you need to have root access before you flash a custom recovery.
Edit: that's not always the case, but when it comes to Samsung devices and odin, you should try to follow the usual steps: root then recovery.
Click to expand...
Click to collapse
Thank you for your suggestion.
I tried to root it first, and it gave me the same error(new one) as above.
I never had an issue when I was playing around with my SGS3 couple of years ago. Rooting, recovery, custom rom all flashed well via odin.
Any idea?
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
cosmostronomer said:
Thank you very much.
I was just redoing all the procedures, and found out that the reactivation lock is reactivated!
I disabled, again, and it worked!
Thank you again XD
Click to expand...
Click to collapse
Very glad to hear it! That reactivation lock is the number one issue when odin fails (on this device anyway)
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
So there was a game promotion that if you had an S6/EDGE, you would get free content in that game. The only way (to me) that I could get it was change my ro.device.model number to appropriate S6 model number to fake having an S6/EDGE. I rooted my Note 4 (SM-N910P) using chainfire's auto-root. Everything went fine inthe rooting process. I downloaded the application that changes my build.prop (In play store it is titled "build.prop editor"). So I changed the ro.device.model to SM-G920F. I restarted my device so the game could notice that I "had" G6/EDGE. I was stuck in a bootloop. All I see is the Samsung logo. I can access download mode (power home voldown) and recovery (power home volup). I was freaking out that I was stuck in a bootloop. Then someone else in the reddit thread (reddit dot com/r/hearthstone/comments/3dkwew/how_to_get_the_samsung_s6_3_packs_and_card_back) said that he tried it on his Note 4 and he also got the same bootloop but he fixed it by reverting back through stock. I downloaded stock Note 4 4.4.4 firmware and flashed....
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
try download diffrent firmware
try wipe data/cache (volum up+power button +home button) if you cant access it .try rooting your device and then install recovery then wipe(cache data) and try flashing stocks firmware again
it may also be bad cable try diffrent one
reinstall kies 3(after unistalling it first)
use diffrent odin (3.04 ECT)
and try kikat firmware i believe its just firmware issue (try russian kitkat if your device varient is supported )
savev1 said:
Okay guys, I have screwed up...
I will try to explain my situation as thoroughly as possible:
here are the logs: <ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/008> Added!!
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> sbl1.mbn
<ID:0/008> rpm.mbn
<ID:0/008> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
and on my phone: UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
I am screwed, aren't I?
Click to expand...
Click to collapse
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.
xxSTARBUCKSxx said:
No youre not screwed(shouldnt be).
And No, dont continue to flash KitKat firmware or youre going to be wasting time and continually disappointed, no matter how many times you download it.
Once you get to a certain bootloader, youre not able to downgrade to prior(kitkat in this case) bootloaders. Flash the LATEST stock.tar through Odin and start all over.
Click to expand...
Click to collapse
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...
savev1 said:
Ummm, okay could you possibly link my to the current tars? I have tried flashing everything from kitkat to lollipop. (I was originally on the BOB7 lollipop build).)
From what I've read (hence why I am scared) is that my eMMC chip is broken and cannot be written to...
Click to expand...
Click to collapse
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint
xxSTARBUCKSxx said:
Well, lets hope that isnt the case and stick to what we do know. That message you received points to one thing, Trying to Odin a .tar firmware that contains an older bootloader that people with OE1 and up bootloaders cannot downgrade to.
OF5 Stock tar.
http://forum.xda-developers.com/note-4-sprint/general/of5-tar-t3158006
FYI SM-N910P Forum
http://forum.xda-developers.com/note-4-sprint
Click to expand...
Click to collapse
It worked! It worked! I pressed thanks bro ^.^
savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
Lol. Np bro. Glad it worked. Thats what the community is here for.
Get your phone situated and the way you like it (launchers or what have you) and make a backup in recovery and youll be good to go.
Note 4 sm-n910f
savev1 said:
It worked! It worked! I pressed thanks bro ^.^
Click to expand...
Click to collapse
I've been had the same problem having this error
----------------------
UDC start
SW Rev Check FAIL: [aboot] Fuused 2 > Binary 1
[1] eMMC write fail: ABOOT
-----------------------
and I badly need to flash to stock since I am using custom and having problem with my sim not being detected .
but i just cant seem to get it flashed once more like i did the first try with a stock rom ?
would you suggest me to download several stock rom in sammobile and try all.
I am having the same problem with N910W8 getting emmc write fail
Just tried to downgrade the Note 7 after updating to PHE and it's a no go.
Message on the phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Here is Odin's log:
<ID:0/005> Odin engine v(ID:3.1205)..
<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)
I don't think I'm doing anything wrong. I've upgraded and downgraded with Odin a few times before without any problems.
I've tried both PH3 and PH9 firmware versions.
It's not looking good for rooting...
lightning413 said:
Just tried to downgrade the Note 7 after updating to PHE and it's a no go.
Message on the phone says: SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Here is Odin's log:
<ID:0/005> Odin engine v(ID:3.1205)..
<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)
I don't think I'm doing anything wrong. I've upgraded and downgraded with Odin a few times before without any problems.
I've tried both PH3 and PH9 firmware versions.
It's not looking good for rooting...
Click to expand...
Click to collapse
No you're correct. It doesn't have the ability to downgrade.
Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.
zeroempathy said:
Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.
Click to expand...
Click to collapse
I grabbed my replacement today and it came with PH9, though it sure wanted to install PHE shortly after initial boot. It's giving the option to delay for now.
zeroempathy said:
Do the replacement notes come with the PHE update? Is the update forced? I need to get my phone replaced at Best Buy but I can't lose root.
Click to expand...
Click to collapse
I just got mine and while I was there, I saw them activating and updating everyone's phone so when it came to my turn, I ask for them not to activate. I told them I didn't have time to go through it and would do it later when I got home.
It's still at PH9.
I just grabbed the full PHE firmware update and am talking to another dev to try to find out if there is a chance we can modify this update to remove the rev lock and root.
Will keep everyone posted.
Did you disable OEM lock in developer tools?
Sent from my SM-N930P using XDA-Developers mobile app
richardjrdeal said:
Did you disable OEM lock in developer tools?
Sent from my SM-N930P using XDA-Developers mobile app
Click to expand...
Click to collapse
by my understanding, that only relates to bootloader unlocking, and does not work for said purpose.
How can I use the IMEI to find the telephone number that was attached to the device???
Sent from my SM-N930P using Tapatalk
Sterist said:
by my understanding, that only relates to bootloader unlocking, and does not work for said purpose.
Click to expand...
Click to collapse
It keeps someone from wiping your phone. Pretty sure if you unlock it, it will allow you to Odin back.
Sent from my SM-N930P using XDA-Developers mobile app
I was reading on a Note 7 thread was someone that reset their phone ( http://forum.xda-developers.com/note-7/how-to/note-7-n930fd-f-downgrade-to-100-t3469787/page3) to get it back to pre- PHE update. Has anybody with a sprint phone tried to reset their phone before flashing in odin to downgrade.?
There is no way to have it downgraded
Sent from my SM-N930P using Tapatalk
sterstar2012 said:
There is no way to have it downgraded
Sent from my SM-N930P using Tapatalk
Click to expand...
Click to collapse
hi. i have a question. When my phone sprint note 7 has pk1 made unlock carrier. First using odin put a combine rom COMBINATION_FA60_N930VVRU2APIB_CL9208905_QB11007042_REV00_user_mid_noship_MULTI_CERT and then using samsung tool pro to unlock. after this put a PHE by odin and now working unlock. is this a downgrade or not?. i want to have ph3 or ph9 for root and avoid kill my phone and use my phone like a smartphone.
https://drive.google.com/file/d/0Bw6tEApjkJtRRm05bHN4SXhEUkU/view
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
iscream612 said:
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
Click to expand...
Click to collapse
You may be on a newer bootloader which is why you are receiving the pit file error when flashing lower firmware
Sent from my SM-G930P using XDA-Developers mobile app
iscream612 said:
AT&T
Galaxy S7
Android security patch level: Sept 1, 2016
Baseband version: G930AUCS4API2
Build number: MMB2M.G930AUCS4API2
I attempted to root my phone with the guide you can find by The Unlockr (David Cogen)
I followed the steps exactly but unfortunately it would freeze on AT&T symbol...
So I tried flashing stock firmwares with no luck. So I wiped data/restored factory settings and fortunately my phone runs. However I keep getting a popup saying "Security Notice: Unauthorized actions have been detected." Which I am assuming means I tripped KNOX. =(
Is there a way to remove this trip? Does anyone know a firmware that SHOULD flash properly on my phone?
Here is the error I get when I try to flash the 2 firmwares I have found (G930AUCS2APF2, G930AUCU1APB5)
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help you can provide..
Click to expand...
Click to collapse
The september patch has a new bootloader which means you can't downgrade below API2. And no, you didn't trip knox. That notification pops up regardless when the security log detects that the phone is rooted, So you should be fine. API3 G930U firmware flashes perfectly and works really well, I recommend using it.
G930U Firmware >
http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
VenomMOD said:
The september patch has a new bootloader which means you can't downgrade below API2. And no, you didn't trip knox. That notification pops up regardless when the security log detects that the phone is rooted, So you should be fine. API3 G930U firmware flashes perfectly and works really well, I recommend using it.
G930U Firmware >
http://forum.xda-developers.com/att...4api3-firmware-download-t3481159#post69147585
Click to expand...
Click to collapse
You are the man, thank you so much! And big thanks to joe3681 for paying/uploading the firmware for us! :good:
VenomMOD said:
G930U Firmware >
Click to expand...
Click to collapse
Also, what firmware is this? Custom? From another carrier? It's definitely different than my old at&t firmware..
iscream612 said:
Also, what firmware is this? Custom? From another carrier? It's definitely different than my old at&t firmware..
Click to expand...
Click to collapse
It's the firmware of the Unlocked S7 variant, which is Official Samsung firmware. No AT&T bloat or anything.
Performance and battery life have gotten better on this Firmware, and no overheating either.
VenomMOD said:
Performance and battery life have gotten better on this Firmware, and no overheating either.
Click to expand...
Click to collapse
I really do enjoy the idea of no bloat and better performance/battery life. Theres just some things that I will miss, like at&t advanced text messaging..
Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.
tri0xinn said:
Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.
Click to expand...
Click to collapse
What errors are you getting with Odin?
What firmware are you trying to flash?
spawnlives said:
What errors are you getting with Odin?
What firmware are you trying to flash?
Click to expand...
Click to collapse
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
tri0xinn said:
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
2 things I can see
1. Use Odin version 3.13.1 it supports the new compression format of newer firmware.
2. The software check fail is due to trying to flash older firmware than what is on your phone. You will need to download firmware with a bootloader version 5 ( 5th number from right of firmware(PDA) name ).
OP can you confirm if it worked?
Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!
tri0xinn said:
Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!
Click to expand...
Click to collapse
Glad you got it sorted
Home_CSC - will keep your apps and data.
CSC - clean install same as a factory reset.