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
Related
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
matt99017d said:
How is one supposed to get out of a bootloop while loaded in a slot on safestrap? It only loops and never gives me a chance to load SS.
I recently took the update and was able to retain root. I am one of the few that it went from .51 to .54 and said failed update. luckily I was able to flash back to the original software and start over. So now for the time being I'll be staying with the ability to fxz back to stock and forgo the camera update.
So the real question is, how do you get out of a bootloop when your on a safestrap slot and you don't have the ability to flash back to stock because you took the update? @Hashcode
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
jayboyyyy said:
I'm assuming your non rooted motox sig is not accurate anymore lol. But I would take your question to rootzwiki. That seems to be where hashcode is doing his discussion and where others are posting questions who are in bootloops etc. You will probably get a better response. But if you can get to fastboot you should be able to flash recovery back on there and sort it out I think. But i haven't been keeping up with SS too much. I think i read some stuff over there about that though.
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v36x/
Click to expand...
Click to collapse
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
matt99017d said:
I flashed recovery first and tried to boot. No luck. Then I flashed back via rsd lite ( luckily ) and I'm back to being rooted.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse
next time just flash the system.img as well and you should have been good to go without losing any data.
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
Hasn't this already been discussed in the update thread? Flash the stock ATT JB, then accept the update.
bpc87 said:
My phone has been saying for a couple weeks now that I need to update it so i go to update it and it shuts down and then you see the android trying to complete the update then about halfway through it stops and i get the orange warning sign like it failed then the phone reboots and says update failed then i tryed rebooting it into recovery and it wont even boot into recovery.
Click to expand...
Click to collapse
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
devilsking said:
My friend also asked me about this prob today I also told him that but thanks for the info since it's just my thinking and i havent tried still on CM11 to wait official kitkat
Click to expand...
Click to collapse
Same here!
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
magocop said:
i have the same problem but i'm on stock jb. just rooted the phone and stock bootloader. i don't now if it has something to do with not being in usa and using an AT&T phone. but it's really annoying the message every hour.
Click to expand...
Click to collapse
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
audit13 said:
The OTA update should install even without an ATT SIM card in the phone. I have a Bell Atrix HD in Canada with an unlocked bootloader. I installed the stock JB ATT ROM, ran the update, installed a customer recovery, and went back to using a custom ROM.
Click to expand...
Click to collapse
Did you have to call Bell to get that customer recovery? And where can I get one at?
skeevydude said:
Did you have to call Bell to get that customer recovery? And where can I get one at?
Click to expand...
Click to collapse
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
audit13 said:
I apologize. I meant to say "custom" and not "customer". I was posting from my phone and didn't notice that auto correct changed the word to customer.
Click to expand...
Click to collapse
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
skeevydude said:
I know. Just having a bit of fun
Autocorrect....Adding the wrong word for the lulz since 2009
Click to expand...
Click to collapse
No worries. Good thing you brought the error to my attention; otherwise, Bell would start receiving requests for the "customer" recovery files:laugh:
skeevydude said:
If you ever rooted, ran a custom recovery, chances are you tweaked something under /system that's causing it to fail. Flash stock recovery and stock system then take the OTA.
Now, with my old Atrix HD, the OTA took just fine with a rooted system and Philz CWM, on my new Atrix HD, I had to be using stock recovery and unrooted...odd.
Click to expand...
Click to collapse
I probably did when i first figured out how to use custom roms i was trying a whole bunch of them but that was awhile ago and now i dont remember how to flash a stock recovery or where to get it and i did awhile ago use RSD Lite to flash a stock rom onto my phone but that is the last thing I did and know its been sooo long i dont remember how any help from anyone would be greatly appreciated and sorry i have not got back to this post in a few days been busy doing other things but once again if anyone could help me it would be appreciated
Thanks
- Bart
Try using Myth Tools to flash back to stock, take the update, install a custom recovery, and flash a KK ROM.
http://forum.xda-developers.com/showthread.php?t=2262726
So, I bought a rooted I537 and unrooted it with SuperUser. It has Baseband i537UCUAMF3;
Kernel Version 3.4.0-784654
[email protected] #1
Wed June 12 20:01:35 KST 2013
Build Number
JDQ39.i537UCUAMF3
I want to get to KitKat. I was attracted to the S4 for NFC payments but can't do that with 4.2.2. Can any of you figure out the problem?
change your USB cable and retry....
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app
tet1 said:
change your USB cable and retry....
I would have guessed you wrong given that Odin recognized my phone without a problem, but had nothing else to try. I tried switching to the usb cord I charge my phone with every night. That charges it fully so I thought it was a good sign. FAIL! Next, I took advantage of my daughter being out of the house and swiped her genuine Samsung cord she got with her Verizon phone. SUCCESS!
It worked. Thanks for your help!
So, for those of you playing along at home, to get to the latest Kitkat OS from a rooted 4.2.2 I537 S4, I had to unroot with SuperUser, install ML2, then NE3, then finally NH3
Click to expand...
Click to collapse
Crap, seem to have fried my phone. I tried to get from ML2 to NE3 with the OTA method. When the phone rebooted, it got stuck at the AT&T splash logo which didn't even look right. There was blue diagonally on the left bottom corner. I tried waiting to see if it would finish booting then eventually pulled the battery. When I rebooted, I saw the same damaged splash screen then it went to the initial setup screen where you choose your language. This deteriorated quickly and became unreadable
Any suggestions?
Booting into recovery mode also quickly deteriorates.
Booting into download mode looks fine, but attempting an Odin install of ML2 quickly fails.
Odin install of NE3 fails right away too.
p.s. where are you supposed to put the update.zip file? I put it in the root of my memory card.
Tried booting again. It's useable, but looks horrid. Try NH3 OTA?
Now 15 minutes later, the color is back but the touch screen is completely unresponsive.
LuckyInOhio said:
Tried booting again. It's useable, but looks horrid. Try NH3 OTA?
Now 15 minutes later, the color is back but the touch screen is completely unresponsive.
Click to expand...
Click to collapse
You should just flash the NE3 Odin package until it works. Just for future reference, you should have just upgraded to NE3 directly, there is no reason you should have flashed ML2 in the first place.
Well, trying to reflash the NE3 Odin package and it keeps failing. I think I saw "no pit partition" so I tried to find a PIT file to re-partition. I found a file named I537_18-4-2014_0-4-56.pit at 8kb in these forums, but that keeps failing too. Can anyone with a rooted i537 kitkat upload their pit file?
Okay so to start I followed this Tutorial http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 all the way through and my phone was rooted and I was happy. One day I tried to install TWRP since this is what I used on my Galaxy s3 before this phone. It got stuck on on a boot loop. I eventually tried flashing every stock ROM which did not fix the problem because ODIN would fail when trying to flash. Eventually I tried flashing the "G900A_ND3_Stock_Kernel" supplied in the tutorial. My phone magically booted up and all my APPS and stuff was the same as I left it and it was still rooted. I decided not to mess with it anymore. This happened about a month ago.
Today, my phone had a notification saying that there was an update and I tapped remind me later. Eventually, I installed Titanium Back up to force closed the AT&T Software Update app the phone came with. Then. it automatically updated and eventually got stuck into the boot loop again. No problem, I fixed this before. What I noticed from the first time was that I had a screen that said "Secure Fail: Recovery. System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help" Once I flashed the stock kernel from the tutorial I never checked to see if the recover menu was there.
So right now I have my phone working and its rooted. I installed the "Phone Info" app and it says Bootloader Version:G900AUCU2ANG3. Eventually, my phone will try to update itself again and it will fail causing it to boot loop. I am not sure on what to do. Is there a way for me to have my recovery menu back? I just want to have the option in the future to revert everything back to normal in case I sell it or feel like having the newest OS. Also it would be cool to have a recovery menu on my phone again.
I know this was long but I needed to solve this problem before it gets out of hand in the future. Also I am pretty sure others have followed the tutorial and might have had the idea to update the OS or something else and had a problem similar to mine.
Thank You Very Much.
xtremegamer13 said:
Okay so to start I followed this Tutorial http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 all the way through and my phone was rooted and I was happy. One day I tried to install TWRP since this is what I used on my Galaxy s3 before this phone. It got stuck on on a boot loop. I eventually tried flashing every stock ROM which did not fix the problem because ODIN would fail when trying to flash. Eventually I tried flashing the "G900A_ND3_Stock_Kernel" supplied in the tutorial. My phone magically booted up and all my APPS and stuff was the same as I left it and it was still rooted. I decided not to mess with it anymore. This happened about a month ago.
Today, my phone had a notification saying that there was an update and I tapped remind me later. Eventually, I installed Titanium Back up to force closed the AT&T Software Update app the phone came with. Then. it automatically updated and eventually got stuck into the boot loop again. No problem, I fixed this before. What I noticed from the first time was that I had a screen that said "Secure Fail: Recovery. System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help" Once I flashed the stock kernel from the tutorial I never checked to see if the recover menu was there.
So right now I have my phone working and its rooted. I installed the "Phone Info" app and it says Bootloader Version:G900AUCU2ANG3. Eventually, my phone will try to update itself again and it will fail causing it to boot loop. I am not sure on what to do. Is there a way for me to have my recovery menu back? I just want to have the option in the future to revert everything back to normal in case I sell it or feel like having the newest OS. Also it would be cool to have a recovery menu on my phone again.
I know this was long but I needed to solve this problem before it gets out of hand in the future. Also I am pretty sure others have followed the tutorial and might have had the idea to update the OS or something else and had a problem similar to mine.
Thank You Very Much.
Click to expand...
Click to collapse
So you're still rooted?
And if so using titanium backup just freeze the ATT update app I forget what it's called exactly but you'll know it when you see it and that'll stop your device from trying to automatically trying to update
OPOfreak said:
So you're still rooted?
And if so using titanium backup just freeze the ATT update app I forget what it's called exactly but you'll know it when you see it and that'll stop your device from trying to automatically trying to update
Click to expand...
Click to collapse
Yeah I'm still rooted and I found out about the freeze app option but do you know about the problem where I don't even have a recovery menu?
xtremegamer13 said:
Yeah I'm still rooted and I found out about the freeze app option but do you know about the problem where I don't even have a recovery menu?
Click to expand...
Click to collapse
You need to download the safe strap recovery menu. That is for rooted phones with locked bootloaders.
dirtydodge said:
You need to download the safe strap recovery menu. That is for rooted phones with locked bootloaders.
Click to expand...
Click to collapse
Thank You very much I was able to install the Safe strap Recovery and am now backing it up. Hopefully my last question Is there a way to update in the future for example if I wanted to have the OTA firmwares from AT&T without root in case I were to sell the phone?
Thank you guys for the answers.
xtremegamer13 said:
Thank You very much I was able to install the Safe strap Recovery and am now backing it up. Hopefully my last question Is there a way to update in the future for example if I wanted to have the OTA firmwares from AT&T without root in case I were to sell the phone?
Thank you guys for the answers.
Click to expand...
Click to collapse
Odin back to stock
OPOfreak said:
Odin back to stock
Click to expand...
Click to collapse
I've tried this in the past when my phone was stuck in bootloop, But it always failed since I have a different baseband or boatloader. Would you know which stock ROM I have to use because I tried many and had no luck in the past?
xtremegamer13 said:
I've tried this in the past when my phone was stuck in bootloop, But it always failed since I have a different baseband or boatloader. Would you know which stock ROM I have to use because I tried many and had no luck in the past?
Click to expand...
Click to collapse
Read here links are still working
http://forum.xda-developers.com/showthread.php?t=2868776
OPOfreak said:
Read here links are still working
http://forum.xda-developers.com/showthread.php?t=2868776
Click to expand...
Click to collapse
Wait, the thread is for Galaxy s5 Active. Will the G870AUCU1ANE4_Full_Odin.tar file work on my Galaxy s5 AT&T? Just making sure.
xtremegamer13 said:
Wait, the thread is for Galaxy s5 Active. Will the G870AUCU1ANE4_Full_Odin.tar file work on my Galaxy s5 AT&T? Just making sure.
Click to expand...
Click to collapse
No my bad
Here
http://forum.xda-developers.com/showthread.php?t=2862299
https://twitter.com/theHTCscene/status/632273058322096128
My phone automatically downloaded it and is asking me every 20 seconds to install. Does anyone know if this is an acceptable update if rooted on stock ROM?
If not, how to stop the notification from appearing?
SeriesOfTubes said:
My phone automatically downloaded it and is asking me every 20 seconds to install. Does anyone know if this is an acceptable update if rooted on stock ROM?
If not, how to stop the notification from appearing?
Click to expand...
Click to collapse
I tried on my stock rooted ROM (went back to stock recovery first) and my phone wouldn't reboot afterward. It went into recovery, finished the update, but then stayed on the HTC One boot screen for half an hour. May have been an issue with root, xposed, or something else. I had to go back to one of my nandroid backups. So, I'd stay away for now if I were you.
coal686 said:
I tried on my stock rooted ROM (went back to stock recovery first) and my phone wouldn't reboot afterward. It went into recovery, finished the update, but then stayed on the HTC One boot screen for half an hour. May have been an issue with root, xposed, or something else. I had to go back to one of my nandroid backups. So, I'd stay away for now if I were you.
Click to expand...
Click to collapse
What I did was disabled *updater* and *configupdater* in the Apps settings.
Hope that works for you.