[Q] softbricked after OF2 OTA update - AT&T Samsung Galaxy S 5

Got a stock G900A that had gotten the OTA update to OF2, then I bricked it trying to flash what I thought was a stock ROM but wasn't. Seems to be soft-bricked now (stuck on AT&T logo at boot) Tried wipe/reset options also.
I tried flashing that 5.0 ROM from the http://forum.xda-developers.com/att...-s5-lollipop-stock-rom-g900aucu3boc4-t3137519 thread but it said SW REV CHECK FAIL: [aboot] Fused 4 > Binary 3 which I assume means that the image included the OC4 bootloader which the phone is loath to downgrade.
Any suggestions on how to get a stock image with the OF4 update installed? Or can I flash everything but the bootloader?

I just picked up an S5 last night and Im so glad I didnt try that,lol. But on a real note, Id like to have some suggestions for rooting after taking the of2 update. Im about ready to ditch it and keep running my S3.
thanatos2k, since you started this thread, would you mind keeping your findings posted here please.

thanatos2k said:
Got a stock G900A that had gotten the OTA update to OF2, then I bricked it trying to flash what I thought was a stock ROM but wasn't. Seems to be soft-bricked now (stuck on AT&T logo at boot) Tried wipe/reset options also.
I tried flashing that 5.0 ROM from the http://forum.xda-developers.com/att...-s5-lollipop-stock-rom-g900aucu3boc4-t3137519 thread but it said SW REV CHECK FAIL: [aboot] Fused 4 > Binary 3 which I assume means that the image included the OC4 bootloader which the phone is loath to downgrade.
Any suggestions on how to get a stock image with the OF4 update installed? Or can I flash everything but the bootloader?
Click to expand...
Click to collapse
You guys that don't know what you are doing should stop flashing your phones, this is getting old. Anyway, flash this in Odin's PDA/AP slot to recover:
G900A_OF2_Stock_Kernel.tar.md5

Related

[Q] Flashing Back to Stock Assistance Please?

Hey guys,
I purchased the Galaxy S5 back in April and now I am selling it so that I can purchase the LG G3. The problem is I'm trying to flash back to stock with Odin and it won't work. I downloaded the stock firmware from Sammobile and loaded it into Odin, put my phone in download mode and hit start and it says "fail." I can't get it to flash. I'm rooted but I haven't installed a recovery or custom rom. Any guidance would really help. I have no idea why I'm getting fail errors.
ImHavenHart said:
Hey guys,
I purchased the Galaxy S5 back in April and now I am selling it so that I can purchase the LG G3. The problem is I'm trying to flash back to stock with Odin and it won't work. I downloaded the stock firmware from Sammobile and loaded it into Odin, put my phone in download mode and hit start and it says "fail." I can't get it to flash. I'm rooted but I haven't installed a recovery or custom rom. I used the Supersu update by chainfire to disable knox. I remember on previous Galaxy S versions that if you took the OTA update it prevented you from flashing custom roms of flashing back to stock. But I haven't taken an OTA update or anything so I can't figure out why it keeps saying fail? Do you think I need to re-enable knox? If so, can I do that in Supersu? Or is there another problem? Any guidance would really help.
Click to expand...
Click to collapse
My thread here will get you back to stock with the included files
http://forum.xda-developers.com/showthread.php?t=2785363
DO NOT TRY TO FLASH THE BL FILE as our bootloader is still locked and it will just fail.
just flash the other 3 files
enjoy
davew41 said:
My thread here will get you back to stock with the included files
http://forum.xda-developers.com/showthread.php?t=2785363
DO NOT TRY TO FLASH THE BL FILE as our bootloader is still locked and it will just fail.
just flash the other 3 files
enjoy
Click to expand...
Click to collapse
Thanks a ton!!!!

Bricked, Unbricked, how to update?

So I was on 4.4.2 before and rooted and wanted to update and followed an old guide which led me to an old link to the toolkit. The result was downgrading to 4.2.2, OTAing, and then bricking. It took me awhile but somehow I flashed the 4.2.2 again and managed to unbrick myself. Now that I can access my phone again how do I update to the newest 4.4.4 without bricking again? I'm a bit afraid of doing anything at this point. Is it possible to just flash a custom rom to avoid it (I'm on developer edition)? Is it safe to RSDlite to 4.4.4 using the right carrier?
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
Same problem
nvertigo said:
edit:
nevermind... I turned the phone off to check the status of the bootloader and saw it was unlocked, did a normal power up. For some reason it said android is updating even though I didn't do any updates and it randomly turned off and now it's completely dead .
Click to expand...
Click to collapse
My girlfriends phone has the same issue. It received an OTA update on Friday and kept havin problems running programs and rebooting. This morning it was off and when it booted, it couldn't get past the "unlocked bootloader" warning. I could get to the recovery menu but could not run TwRP because it froze at the splash.
I have tried installing a new recovery via faastboot but after it "installs" , it still appears to be the old recovery.
If you can boot the phone to FastbootAP/Bootloader, check the bootloader version on your phone, and get the corresponding SBF version or NEWER.
Example:
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
xx.xx = 4.4 <-- I forgot the bootloader version.
30.B4 = 4.4.2
30.B7 = 4.4.4
using an OLDER version SBF will fail at GPT.BIN and Motoboot.img, or will brick your phone!!!
Flash the SBF by following option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Doing this (flashing the latest SBF for your phone/bootloader) should bring everything on your phone back in line, making it safe to take future OTA's

Safe to install OTA after downgrade?

I made the mistake to install the new stagefright fix OTA on my rooted XT1095. Of course this made my phone stuck on boot. I was able to fix my phone by flashing this [URL="http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945”]stock rom[/URL] (Thanks AGISCI!).
I would like to return to 100% stock now by installing the latest recovery image provided by Motorola (L-5.1-LPE23.32-21.3 TMO) and than taking the stagefright OTA. Would this be safe without a chance of bricking my phone? My understanding is that I would brick my device by flashing an older modem version on my phone. Is there a way to find out what modem version my phone is currently on?
Thanks for your help!
It is NOT safe to take OTA after any downgrade. Even I did a similar thing. I did not un root properly. Waiting for stock images with the patch to be uploaded by moto
Sent from my XT1095 using XDA Free mobile app
I was rooted with Xposed on my XT1095 with 5.1. In order to do the StageFright patch, I downloaded the factory image and extracted just recovery.img and system.img. I flashed just those two images (using the fastboot version included in the factory image). I rebooted and had a nice, back-to-factory system structure. I then took the OTA normally. Once that was done, I flashed TWRP back on the phone, re-rooted, and installed Xposed. No problems at all.
For your situation, I'd try the same thing. Just flash recovery and system, boot up, and take the OTA. Then re-root.
gabriel_hart said:
I was rooted with Xposed on my XT1095 with 5.1. In order to do the StageFright patch, I downloaded the factory image and extracted just recovery.img and system.img. I flashed just those two images (using the fastboot version included in the factory image). I rebooted and had a nice, back-to-factory system structure. I then took the OTA normally. Once that was done, I flashed TWRP back on the phone, re-rooted, and installed Xposed. No problems at all.
For your situation, I'd try the same thing. Just flash recovery and system, boot up, and take the OTA. Then re-root.
Click to expand...
Click to collapse
Your situation is not the same. He downgraded which means taking the OTA is dangerous and can brick it. You never downgraded, you just flashed the same system and recovery that you already had which is why the OTA is safe for you.
For those that want the new patched version and are on downgraded systems, you can use this stock rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
You can flash it with a custom recovery such as TWRP. This rom now has the stagefright patch baked into it and OTA is disabled on this rom to prevent bricks. You can use this until motorola releases the full firmware image officially.
AGISCI said:
Your situation is not the same. He downgraded which means taking the OTA is dangerous and can brick it. You never downgraded, you just flashed the same system and recovery that you already had which is why the OTA is safe for you.
For those that want the new patched version and are on downgraded systems, you can use this stock rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
You can flash it with a custom recovery such as TWRP. This rom now has the stagefright patch baked into it and OTA is disabled on this rom to prevent bricks. You can use this until motorola releases the full firmware image officially.
Click to expand...
Click to collapse
With all due respect, sir, I did note that our situations are different: "For your situation...". Also, I don't see where he mentioned downgrading. He installed your flashable 5.1 ROM and said he was holding off on flashing a modem due to fear of bricking.
And for the good of the community, thanks for putting together that patched stock ROM so others won't have to mess around with flashing stock images.
I seem to have inadvertently offended you. That was not my intention, I was merely trying to help out. So for that I apologize.
Oh and the title of the topic is where it says he downgraded.
Sent from my XT1095 using Tapatalk
No sweat, simple misunderstanding
AGISCI said:
Your situation is not the same. He downgraded which means taking the OTA is dangerous and can brick it. You never downgraded, you just flashed the same system and recovery that you already had which is why the OTA is safe for you.
For those that want the new patched version and are on downgraded systems, you can use this stock rom:
http://forum.xda-developers.com/moto-x-2014/development/rom-xt1095-flashable-stock-rom-t3185945
You can flash it with a custom recovery such as TWRP. This rom now has the stagefright patch baked into it and OTA is disabled on this rom to prevent bricks. You can use this until motorola releases the full firmware image officially.
Click to expand...
Click to collapse
Thanks for your help!
I’m not sure if I actually did downgrade my phone as I’m not sure what part of the OTA succeeded. Is there a way to lookup the modem version and ect. of my device to check if it would be safe to flash Motorola’s L-5.1-LPE23.32-21.3 TMO build?

Stuck at " recovery not Seandroid enforcing" after root n9208

Hi guys I have the latest firmware installed ( see screenshot) whenever I try to obtain root via chain fires autoroot or through custom kernel for n9208 my phone gets stuck at bootloader. Is there any way to fix this.
Ps the crom services app always force closes . And I followed every step on root tutorials
Hi, i got same problem with new firmware update, lost my root and tried to root again with chainfire autoroot, but didnt work, tried a couple of times...no luck, at this step i still can boot android, then tried flash xiaolu kernel...at this step i got boot loop, both space kernel also failed to boot, so if you havent flash any kernel with odin, you still can boot after flashing twrp recovery, but if you already messed with kernel, there no way to to fix it...better flassh new firmware, and use stock until someone can find a way to root 5.1.1, hope its help...
Dyosr said:
Hi, i got same problem with new firmware update, lost my root and tried to root again with chainfire autoroot, but didnt work, tried a couple of times...no luck, at this step i still can boot android, then tried flash xiaolu kernel...at this step i got boot loop, both space kernel also failed to boot, so if you havent flash any kernel with odin, you still can boot after flashing twrp recovery, but if you already messed with kernel, there no way to to fix it...better flassh new firmware, and use stock until someone can find a way to root 5.1.1, hope its help...
Click to expand...
Click to collapse
Isn't there a way we can simply downgrade to the last rootable firmware?
if you're on the latest firmware, i recall having to install the AOK2 bootloader to root my N9208 using the original root methods (not the Systemlesss Root method). check the TWRP thread for details. The situation may have changed, but when i upgraded my firmware to AOL1, i had to downgrade the bootloader to AOK2 to regain root.
cortez.i said:
if you're on the latest firmware, i recall having to install the AOK2 bootloader to root my N9208 using the original root methods (not the Systemlesss Root method). check the TWRP thread for details. The situation may have changed, but when i upgraded my firmware to AOL1, i had to downgrade the bootloader to AOK2 to regain root.
Click to expand...
Click to collapse
How did you downgraded your boot loader? I am sorry but I'm really new to galaxy development.
PS is it safe to flash a firmware from December over my current version which is from march
Lucas Eugene said:
How did you downgraded your boot loader? I am sorry but I'm really new to galaxy development.
PS is it safe to flash a firmware from December over my current version which is from march
Click to expand...
Click to collapse
check the TWRP thread for details and links to downgrade the bootloader. please note/remember, i downgraded from AOL1 to AOK2. not sure if this works with any firmware newer than AOL1. in my case, i reflashed the AOL1 firmware, then downgraded/flashed the AOK2 bootloader and then rooted using the original 9208 root method.
cortez.i said:
check the TWRP thread for details and links to downgrade the bootloader. please note/remember, i downgraded from AOL1 to AOK2. not sure if this works with any firmware newer than AOL1. in my case, i reflashed the AOL1 firmware, then downgraded/flashed the AOK2 bootloader and then rooted using the original 9208 root method.
Click to expand...
Click to collapse
Thanks so much for your advice! I was finally able to roof my phone. Realised that I was being too noobish
Thanks for your time
Lucas Eugene said:
Thanks so much for your advice! I was finally able to roof my phone. Realised that I was being too noobish
Thanks for your time
Click to expand...
Click to collapse
Hi, how do you do it can explain step by step, thanks, i believed many N9208 user need it
Note 5 N9208 6.0.1 Root without Seandroid Error - https://androidmtk.com/root-samsung-galaxy-note-5-duos-sm-n9208

Stock G900a downgrade from Marshmallow to Lollipop

Searching via cell isn't great for me at the moment. I've found a few threads with lollipop files to use in Odin. But I haven't read anything that says it's simple to flash them and downgrade properly from Marshmallow to Lollipop. Is there a tutorial/file thread already on here that I am missing via search? Is this something I can do without rooting?
Da hell is that chipmunk woman
Sammobile doesn't have the stock 5.1 firmware.. is that an omen against downgrading?
Most of the posts ive read are indicating Marshmallow is not able to be downgraded, bootloader locked.. looks like a dead end
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
johnkirchner said:
It's a different boot loader, will not be able to downgrade. There is no root option at this time as well.
Click to expand...
Click to collapse
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
At the time of my post months ago, this was not possible. It is very possible now, I have also done it.
gooch1006 said:
sorry, but i disagree. i just flashed from 6.0.1 to 5.1.1 using odin and firmware found here on XDA. I have no problems with phone so far.
Click to expand...
Click to collapse
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
johnkirchner said:
Downgrade instructions can be found here:
http://forum.xda-developers.com/showthread.php?p=67323522
Click to expand...
Click to collapse
Thanks for the link, i had searched without luck on my own.
https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
following this guide for rolling back to LP, work for me downgrade from MM and getting root on LP.
Mine didn't... version DPH4, october 1, 2016 security patch, odin gave me an error something like level 4 > 3 and didn't start the reflash process. I was able to reflash the same 6.0.1 and its not the same as what was on there, so maybe the ota updates had a problem? I'm still locked out of downgrading.
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
kecel said:
Mine also from DPH4 oct 1, 2016. Having issue with lte, i cant receive call but i can make call. So im rollback to COI5 and follow the instruction from page 2. Get odin 3.11.1 to flash BL,AP,etc. Have you try with other usb cable?
Click to expand...
Click to collapse
i had that issue at one point, i just flashed the CSC and CP again and it worked.. Idk if it's that simple for you guys tho..
g900a downgrade from 6.0.1 to 5.1.1
djs2571 said:
This is for the AT&T model, I haven't been able to crack into mine. I have battery issues since marshmallow and want to go back to 5.1.1 as well... where did you get the files, and what process did you use?
Click to expand...
Click to collapse
i also have the at&t model, but used some info in this post: https://forum.xda-developers.com/att-galaxy-s5/general/guide-merry-christmas-heres-t3516196
i used odin to flash full OI5 firmware, minus the bootloader file. Only use the AP, CP, and CSC files. the bootloader is the same. and really, i had already flashed the PA2 build earlier that day i remember now. would probably do that first. flashing the PA2, i used all four files, BL, AP, CP, and CSC . they both flashed the first time, if they dont then try a different cable first. usually that is my issue.
so , i flashed from 6.0.1 down to 5.1.1 pa2, then down to oi5. still have no problems other than getting root..... im focusing on bootloader now, i have unlocked them on htc's before, but havent tried any other phone yet. the work continues tonight.

Categories

Resources