Database Develop

Soft Brick after failed 4.3 OTA

I've been running 4.2.2, rooted, SafeStrap'd and SuperSU. Today, I went back to stock ROM (I switch back and forth, between stock and Hyperdrive), I forgot I had rebooted during a forced update for 4.3. Well, update finished downloading, and automatically went to install, of course, with my phone, it always fails @ 29-30%. Phone went to start back up, went thru the SafeStrap and stayed at the AT&T logo. Pulled battery and went to SS, and activated Slot 2 (Hyperdrive). Phone just boot looped thru the SS and then shut off and so on and so forth. So I tried to do a factory reset, and that failed. So I tried to restore backup, in SS and that failed. I'm thinking that even though the 4.3 update failed, it somehow put enough of info, into the bootloader, to change it to a 4.3. I'm going to try to ABD MF3, then MI2 and if that fails, ML2.
Just wanted to give you a heads up....seems AT&T is hellbent on pushing this locked down update through.
Sent Via Smoke Signals

wow
captaincado said:
I've been running 4.2.2, rooted, SafeStrap'd and SuperSU. Today, I went back to stock ROM (I switch back and forth, between stock and Hyperdrive), I forgot I had rebooted during a forced update for 4.3. Well, update finished downloading, and automatically went to install, of course, with my phone, it always fails @ 29-30%. Phone went to start back up, went thru the SafeStrap and stayed at the AT&T logo. Pulled battery and went to SS, and activated Slot 2 (Hyperdrive). Phone just boot looped thru the SS and then shut off and so on and so forth. So I tried to do a factory reset, and that failed. So I tried to restore backup, in SS and that failed. I'm thinking that even though the 4.3 update failed, it somehow put enough of info, into the bootloader, to change it to a 4.3. I'm going to try to ABD MF3, then MI2 and if that fails, ML2.
Just wanted to give you a heads up....seems AT&T is hellbent on pushing this locked down update through.
Sent Via Smoke Signals
Click to expand...
Click to collapse
did you get a fix.att is being a real pain in the ars

Not yet....won't be near a computer until Saturday.
Sent Via Smoke Signals

captaincado said:
Not yet....won't be near a computer until Saturday.
Sent Via Smoke Signals
Click to expand...
Click to collapse
download the odin files but for any reason install the bootloader so you can probably go back to MF1 if everything fails.

alphabeast said:
download the odin files but for any reason install the bootloader so you can probably go back to MF1 if everything fails.
Click to expand...
Click to collapse
To clarify he's saying DO NOT flash the ML2 bootloader so that you'll have the option to downgrade later.

The closest I want to get to ML2 is to use most of ML2's files, but use MI2's boot loader.
Sent Via Smoke Signals

[Q] S5 Active... Water damage, boot loop, "custom" on boot screen.. seeking advice

[Q] S5 Active... Water damage, boot loop, "custom" on boot screen.. seeking advice
Hi XDA - here's my story.
Took my S5 Active on vacation. Decided to make a cool underwater video (in fresh water). About 30 seconds, only a few inches under the surface. Since the phone is supposed to be rated to 1 meter for 30 minutes. Big mistake. Soon after I start seeing NO SIM. So I take the back cover off and see moisture in there....
A few hours later and everything is working on the phone again except there's moisture in the camera "lens" so I take out battery, sim, etc and leave it on the table to dry out for about 12 hours.
Now when I put the battery back in I start boot looping. Argh.
I've heard that Samsung is "quietly" replacing water damaged phones which are advertised as water resistant etc. But I have the "Custom" with the unlocked lock on the bootscreen, as I previously rooted the phone. I don't have a custom recovery or ROM installed though. I rooted and used some mods from xposed. I don't want to get rejected because of that damn bootscreen!
I'm home now and trying to fix. I can boot into download mode, but not recovery for some reason. I used Odin to re-flash the stock firmware. It passed, all messages OK and turned green. But same bootloop, and the "Custom" remains.
Also, I have 0x0 for knox status in the download mode.
Any thoughts or advice guys?

you are ok.
I was able to reset custom by uninstalling all my root apps like towelroot etc. Then flash the files from
http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299
as if I were trying to root but without actually installing towelroot.
As long as you uninstall everything and reboot and clear cache between flashes it should take the lock off assuming that you did not fry the device.
I don't know what is or isn't working after your water damage. Your boot loop may actually prevent this idea from working.
Worth a shot. I had a custom unlock and I cleared it doing this.

I don't know how I could uninstall anything when I can't get into the OS?

yes like I said may not work
richie138 said:
I don't know how I could uninstall anything when I can't get into the OS?
Click to expand...
Click to collapse
I know that my custom unlock would not go away after multiple flashes of stock firmware until I unistalled the application Towelroot from the application manager and only after that was I able to clear the unlock icon from boot by flashing firmware.
If you have actually damaged your phone by putting water in it and you have already tried using Odin to flash the entire 1.5gig original stock OS and that did not work then I can't help you.
But if you have the AT&T insurance like me there was wording in my confirmation email from the insurance that said Your enrollment includes:
Comprehensive coverage for loss, theft, damage, and out-of-warranty malfunction
Declining Deductibles, which can save 25% to 50% off the standard deductible if you are claim-free for 6 months or more2
As soon as next day3 device replacement to help you stay connected
Out of warranty malfunction.
It might be covered.

richie138 said:
I don't know how I could uninstall anything when I can't get into the OS?
Click to expand...
Click to collapse
If this hasn't been resolved can you get into download mode?
"All we know is...He's called the Stig!"
Sent from my G900A Rockin ClinchRomL

Yea I was able to get into download mode, my phone was recognized by Odin, I flashed a full stock firmware, then my phone rebooted and said "BOOTING RECOVERY" but just continued bootlooping with BOOTING RECOVERY. Odin said PASS. All of this multiple times, same results. Attempted not auto-restarting in Odin and pulling battery, etc.

richie138 said:
Yea I was able to get into download mode, my phone was recognized by Odin, I flashed a full stock firmware, then my phone rebooted and said "BOOTING RECOVERY" but just continued bootlooping with BOOTING RECOVERY. Odin said PASS. All of this multiple times, same results. Attempted not auto-restarting in Odin and pulling battery, etc.
Click to expand...
Click to collapse
you should be able to get a warranty replacement then. I would take it to a corporate AT&T store where they can flash new firmware. If they can't they should replace it.
"All we know is...He's called the Stig!"
Sent from my G900A Rockin ClinchRomL

I'm worried that the "Custom" showing when the phone starts booting is going to make them say that my warranty is void.

richie138 said:
I'm worried that the "Custom" showing when the phone starts booting is going to make them say that my warranty is void.
Click to expand...
Click to collapse
You tell them you have no idea it's water damaged. It would be one thing if you bricked your device flashing but since it's a factory defect I wouldn't worry about it.
So what you're saying is you've flashed stock firmware and Odin gives you pass but it still loops. Can you get into stock recovery?
"All we know is...He's called the Stig!"
Sent from my G900A Rockin ClinchRomL

What do you think about doing some additional water damage so it doesn't boot at all... lmao

i had similar problem on a friends phone and flashing stock rom did not do it
SM-G900A 4.4.2 G900AUCU1ANCE Firmware. extract - each file in the correct location in ODIN 3.09
Ap
BL
Cp
CSC
but i had to extract 4 files from the stock zip file and flash each one after that phone booted up
it may be worth trying again i used 4.4.2 stock rom in the forum

saj070 said:
i had similar problem on a friends phone and flashing stock rom did not do it
SM-G900A 4.4.2 G900AUCU1ANCE Firmware. extract - each file in the correct location in ODIN 3.09
Ap
BL
Cp
CSC
but i had to extract 4 files from the stock zip file and flash each one after that phone booted up
it may be worth trying again i used 4.4.2 stock rom in the forum
Click to expand...
Click to collapse
Yep I agree give it a shot
"All we know is...He's called the Stig!"
Sent from my G900A Rockin ClinchRomL

look at the top of your battery. If there is now a red square it indicates water damage. They guy at the AT&T store noticed this when I had an insurance replaced phone activated. Now if your screen was damaged they could not see the unlock either, and replacement is replacement ....
I killed my screen when I changed the DPI settings for android.sysemgui and returning to stock didn't help me either.

i'm stumped. s5 will not boot past samsung logo

after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.

Could it have been a bad download of ANCE. I've seen that happen before. Either a bad download or a bad transfer from comp/phone to sd card. I'd try re downloading

will do
will try that now. hoping it works.

nope. tried and same results.

Perhaps try Odin 3.10? Could it be that simple.
Also did you try a different source for the file you were trying to flash?

magnumglock said:
after a FULL wipe bad flash to cm12 on my part, i restored with odin 3.09 with g900auc1ance firmware. it shows success on odin, but upon reboot, i still get the samsung "custom" with open padlock. then it attempts to boot and the samsung logo does it's thing and only completes about 80% of the logo, then goes dead/blank with blue led lightly pulsing. i took it to bestbuy to the samsung kiosk hoping the tech could help. he scolded me and showed me his at&t s5 running cm12. i'm stumped. any help would be appreciated.
i've rooted and rommed every android i've had and have always been able to fix it., all thanks to XDA.
Click to expand...
Click to collapse
Number one you CANNOT run CM 12 or ANY AOSP or custom kernel on the G900A due to the locked bootloader whoever told you that flat lied to you
I'm assuming you've taken the 444 update correct??
Go to this thread http://forum.xda-developers.com/showthread.php?t=3021120read OP scroll down to the troubleshooting section and download the downgrade to NCE rar. Extract the downgrade to NCE tar md5 place phone in download plug it in and using Odin 3.09 place the tar in the ap slot then flash let it complete wait til phone boots then you'll be back to bone stock NCE phone.

I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.

Odin 3.10 works fine. Don't forget to wipe cache and Davi. Sometimes that's all you need. And I agree, do some research first before you try flashing anything. Our locked bootloader makes us different.

Will do. I'll update what I find this evening.

magnumglock said:
I did the 4.4.4 and I'll give this a shot this evening. Again, thank you for the help.
*edit*
I have not tried Odin 3.10. I downloaded the files from the restore threads link to a google drive storage.
Click to expand...
Click to collapse
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.

OPOfreak said:
OK I figured you took the 4.4. 4 update go to the link I provided and if you read OP it states that if one has trouble with the first downgrade rar to go to the troubleshooting section.
Download the Downgrade to NCE rar in the troubleshooting section and extract the Downgrade to NCE md5 tar.
Using Odin 3.09 put phone into download mode plug it in you'll see added in the box.
Place the Downgrade to NCE tar md5 file into ap slot and press start it will work. I've done it several times myself and helped quite a few people in your place as well
Let phone completely boot up and you'll have a bone stock device ready to start over.
Click to expand...
Click to collapse
this solved my problem. i cannot express how appreciative i am for your help.

magnumglock said:
this solved my problem. i cannot express how appreciative i am for your help.
Click to expand...
Click to collapse
A simple thank you is sufficient I'm glad you're squared away now.
The good thing is now if you soft brick your device you know how to get back to stock.
Happy flashing :thumbup::thumbup:

The same exact thing has happened to me.
OK, I am panicking now. My ATT GS5 is doint the exact same thing.
I will try the NCE rar too and let ya'll know how it went.
---------- Post added at 11:27 PM ---------- Previous post was at 10:59 PM ----------
Dodged that bullet. Got rid of Custom status too. Very cool

I am having the same issue but with a "there is no PIT partiton" error
I have tried everything that I could to get my phone working again. I even downloaded a so called pit file that apparently didn't work because the error keeps coming up. Is there a legit PIT file that I can download and if so could someone please point me in that direction? Also if someone could please help me to get my phone working again I would also appreciate that. I just bought this phone off of ebay and I am trying to get it working as my regular phone. when I start the phone up there are two lines at the top of the screen 1 is a white line that says MMC read fail error or something to that effect, and there's another line in red that says movinand confirmation error. After about 3 to 4 minutes of waiting the phone will go into download mode by itself and give me a whole bunch of lines one of which will say: Knox 0x0.
is there a way I can either repair or repartition the phone? I spent 6 hours trying to figure this out. I am tired.
Thanks in advance for any helpful response.

FRB wont let me boot!

First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!

jfviwerbnv said:
First of all, I *cannot* lose my data. But for obvious privacy and security reasons I *don't* keep Google Sync enabled.
I have a rooted, but stock 5.1.1 T-Mobile Note4. Custom recovery (honestly don't recall if it's TWRP or CWM, I don't use it often). At one point I turned the phone off (actual *off*, not screen lock), but now when I try to turn it on, it refuses to allow it and says "Custom binary blocked by FRP". Same problem when I try to boot into recovery, too. I can only boot into download mode, but attempting to flash the stock 5.1.1 firmware or the stock recovery just simply fails. It just won't allow it.
If I boot into download mode, connect it to my computer via USB, and do "adb devices", no devices show up.
Need help!!!! I need my phone and my data!!!!
Click to expand...
Click to collapse
It's a real pain in the butt.... I just went through this 10 minutes ago. The problem: "Custom binary blocked by FRP" - or, FRP lock.
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
It works. Not elegant, but I don't think there is any way round this. No way to use ADB that I can figure, but ODIN will work.
Once you get back up and running, make sure to go into settings and enable developer options. When you get there, allow USB debugging and click on the "bootloader unlock" option. That will keep FRP from screwing you up again.
If you need a more detailed explanation, let me know- but that's the skeleton of the fix. Once you get running again you can set up the phone the way you want it.
Cheers! (argh)
Steven.RN
Get the Odin file here: https://www.androidfilehost.com/?fid=24269982087008345 (N910T3UVU1DOK2_N910T3TMB1DOK2_TMB.zip)
Unzip the file and it will end in ....tar.md5 Just knock off the .md5 so that it simply ends up as .... .tar, and use "AP" placeholder in Odin.
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.

steven.rn said:
The answer is: get the phone into download mode and use ODIN to flash the stock DOK2 tar image.
[...]
PS: way important.... the above TAR is for the N910T3 - if you have the N910T, There's a different ODIN file, easy to find.
Click to expand...
Click to collapse
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.

jfviwerbnv said:
That's what I did when I tried to flash the stock rom before, ODIN tried for a few seconds and then bailed out with a failure.
However, I had no idea there was such a thing as a N910T3, or that there were two T-Mobile models of Note4. The rom I tried to flash before was for N910T (the only T-Mobile Note4 I knew existed). Sure enough, I popped out my battery, looked at the specs, and my device is a N910T3. Downloading that rom now. Fingers crossed it will work this time.
That *might* also explain a mystery glitch I had been experiencing, but had resolved to just live with: About 10-20% of the time the device would load an image (in any app, system or third party, from gallery or downloaded by the app..didn't seem to matter), random parts of the image would be corrupted - usually obscured by green lines (note, this is NOT the camera issue other people have experiences, but the results look very similar). One of the first things I did when I got the phone was root it (one of the reasons I went to T-Mobile, b/c Verizon's Note4's apparently can't be rooted). But if the root I installed was for N910T and not my N910T3 then maybe that might explain those glitches...or so I hope.
Click to expand...
Click to collapse
Yup.... make sure you get the right flavor of ROM or stock files. I think some devs might have roms that work with either version. But that's the first thing to check, if it's compatible.
Once I reflashed my wifey's phone, I ODIN'ed in the stock twrp recovery TAR file, then got into the recovery and flashed supersu 2.64 in a zip. Rooted, working fine, done (YaY)
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Let me know how things turn out; I don't think you'll have any surprises. It took me about an hour and a half to make sure I had the right solution fer shurrrre, so I think I saved you some time.
You always this lucky? :highfive:
Cheers,
Steven.RN
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this

steven.rn said:
Yup.... make sure you get the right flavor of ROM or stock files.
Click to expand...
Click to collapse
Yep, that turned out to be the problem. Device is a N910T3, I had the stock 5.1.1 rom for the N910T, that's why flashing with ODIN was being blocked. Grabbed the stock 5.1.1 rom for the correct variant, N910T3, and ODIN and the phone were both happy. No factory reset or warranty repair necessary!
Thanks soooo much for the tip!
Unfortunately that image-loading glitch is still there even though I haven't re-rooted yet (now that I think about it, it's maybe more like 5%, and some images don't seem to be vulnerable. maybe it's like a weird bad build of libjpeg or something, I dunno) Well, that's a mystery for another time.
BTW, once you flash SU in recovery, when you go to reboot, TWRP will say "hey, do you wanna root with SU?" DONT DO IT- just let it go to boot up. It will be there.
Click to expand...
Click to collapse
Thanks, I'll keep that in mind. (Don't remember offhand what exactly I did there before.)
You always this lucky? :highfive:
Click to expand...
Click to collapse
Nah, I'm just one stubborn SOB, and once in a while it actually pays off
PS on an odd note, I dumped all my Verizon phones (5 lines) because I couldn't root my Verizon Note 4. Got rid of the VZW Note 4 for a T-mobile Note 4. Looks like we both went the same way! Verizon lost years and years of my business over this
Click to expand...
Click to collapse
Yea. There were actually several reasons I jumped Verizon -> T-Mobile, but that was one of them. Little over two years ago when I got an S3, all the lockouts from Samsung/Google/Verizon were so heavy it wound up bricking within the first couple weeks (complications trying to downgrade an OTA update I didn't want - long story). Anyway, trying to get a proper working replacement took them several tries (one replacement was DOA, another wasn't even a Samsung at all, let alone the right model) and just trying to even communicate with them at all was like having a roundtable with a cage of chimps. (just one example, I couldn't convince them there really were different models of any phone, like the S3, between different carriers, dev versions etc. Nevermind that I'm a career programmer, I couldn't possibly know what I'm talking about ) Plus Verizon's so much more expensive, and T-Mobile just strikes me as a vastly more level-headed pro-consumer company overall. And with the new Band 12 (the reason I got Note4 instead of Note3, oddly enough), their network's been every bit as good as Verizon's for me anywhere I've taken it.

Flashing DOK2 firmware via Odin will wipe internal memory.

ShrekOpher said:
Flashing DOK2 firmware via Odin will wipe internal memory.
Click to expand...
Click to collapse
Doing that didn't wipe internal memory for me (Odin 3.10.6). It did unroot my phone and I'm sure it probably reset my recovery image back to stock (didn't actually try booting into recovery again yet), but all my data was still 100% intact. And not just the data on the "external" SD but also all user data on the internal storage. (It never wiped user data for me on my old S3 or Nexus S either, but maybe the wiping after flashing is just a newer thing?)
Maybe it only wipes internal memory if you're flashing a different version of android? I was simply flashing 5.1.1 overtop rooted 5.1.1.

Help me bring my SM-G870A back to life.

So I don't keep up with android news, and I Upgraded OTA to what I believe was 5.1.1 on my S5 Active. Then a few weeks later I accidentally deleted some pictures and saw the best way to recover them was to root the phone. So I thought no biggie I'm sure it's much easier nowadays to root and followed this guide
http://forum.xda-developers.com/att-galaxy-s5/general/g900and3tong3keeprootota-zip-t2862299
Odin gave me a pass result I was like cool that was easy, but when the phone rebooted it just got stuck at the Samsung Android screen.
I have probably searched every single forum on the internet with every possible keyword to fix my problem, and I just can't find a solution so I hope you guys can help.
The phone goes into download mode and recovery mode and my computer recognizes it., so that gives me a little bit of hope.
My brother has an S5 active as well if this would be of any help. I can't find the 5.1.1 G870A FW on sammobile so is there a way to extract that from another S5 Active on 5.1.1?
I hope someone can help, I did learn the lesson though never buy a phone with a locked bootloader since I'm prone to stupid mistakes like this.
Cheers

Do you know exactly what 5.1.1 version you were on? or what date you received the OTA? I can point you in the right direction for the OTA but I don't know if that will help. I have never repaired a soft brick but if I had the OTA I would load it to my SD card and try to load it in recovery mode. Maybe someone reading this can jump in and tell us if this would work.

Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754

Sgt.CM said:
Do you know exactly what 5.1.1 version you were on? or what date you received the OTA? I can point you in the right direction for the OTA but I don't know if that will help. I have never repaired a soft brick but if I had the OTA I would load it to my SD card and try to load it in recovery mode. Maybe someone reading this can jump in and tell us if this would work.
Click to expand...
Click to collapse
It shows this update in the android recovery menu, not sure if that was my current version at the time i bricked my phone
LRX21T.G870AUCU1BOC5
This is apparently 5.0 but I'm sure I got an update from att in april or may.
more info
thanhvien89 said:
Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
i tried that already but i'll try it again
EDIT: just tried it getting [aboot] Fused 2 > Binary 1

thanhvien89 said:
Odin Back to s5 Active Stock. NE4
http://forum.xda-developers.com/showthread.php?t=2799754
Click to expand...
Click to collapse
This only works if you are already rooted. Can't go back if you are 5.0 or above.