This is going to be simply a collection of links with important points...Please read ALL directions and comments carefully...as no one is responsible for any damage to your phone.
NOTE 1: IF YOU ARE UNROOTED AND ALREADY UPDATED WITH OTA, YOU CAN STILL USE THE PROCESSES BELOW TO ROOT AND FLASH RECOVERY.
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 2: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 3: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you want to stop the OTA update notification, use this file which provides simple edits...but be careful as it may make further updates more difficult >> SCH-I500.DI01 Update
UPDATED:
OTA Update with Root and Busybox >> DH12 to DI01 update with root and busybox
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
My path.
1) Stock with root mentioned in this dev section
2)restored CW backup
3)used CW to install the update mentioned in this thread.
No problems so far.
After reading this thread again I went to stock and stock kernel. Rooted and gold again.
I think that CPU Scale app causes the Fascinate to shut down, so if you use it and getting them.... remove the app or let me know if you fixed.
Thanks!!!
Now, here is something I didn't try yet. I am still stock (not rooted), ran the OTA...and with all people having issues, I am scared to root. I want to try but I think I will wait and see if anyone else does this.
tats_06 said:
This is going to be simply a collection of links with important points...
>> Rooting Samsung Fascinate
>> Flashing Clockwork Recovery
NOTE 1: IF YOU ARE ROOTED AND WANT TO KEEP ROOT, DO NOT INSTALL VERIZON OTA UPDATE. WAIT FOR DEVELOPERS TO POST A ROOTED UPDATE.
If something went wrong and you did not have recovery installed, use Odin to restore system to stock >> Odin Restore files to get you to stock
If something went wrong, but you are still able to get into clockwork recovery >> Stock Nandroid Image
NOTE 2: IF YOU ARE ROOTED, HAVE LAGFIX AND APPS REMOVED, DO NOT INSTALL VERIZON OTA UPDATE. YOU WILL RUN INTO ISSUES. YOU NEED TO COMPLETELY GO BACK TO STOCK, THEN UPDATE. YOU WILL LOSE ROOT.
If you don't care about root and want to install the OTA update manually >> SCH-I500.DI01 Update
Please post corrections and I will update the OP...I see too many people messing up their devices. Just want to help.
Click to expand...
Click to collapse
I thought the post about doing the OTA manually would allow you to keep root, seeing that it's a stripped down version.
Let me clarify that. If that's the case, I can update the OP.
Restored, updated and Rerooted
All is well. No problems so far.
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
namebrandon said:
Guys, pay attention to that update file. It is only updating modem.bin, and then updating your version number so you don't get nagged for an update. There are many more patches/updates in this fix than just modem.bin, and by doing only modem.bin you make it a bit more difficult on yourself to update down the road.
If that's all you want, go ahead and use it, but in no way did JT intend for this to get distributed as "this is what you should use if you have root" update.
Read before using, that's all I ask.
Click to expand...
Click to collapse
Thanks for heads up...first post updated.
Bump.... Back to top till this gets stickied!
wasupwithuman said:
Bump.... Back to top till this gets stickied!
Click to expand...
Click to collapse
Thanks! I just reported it too to request for sticky.
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
azalvarez03 said:
Just thought I would menetion that phone is auto updating the software once it is downloaded to phone at night I woke up this morning and just reposed at work when I went to use wireless tether it wouldn't work looked at my phone and realized it had been auto updated time to go back to stock and reroot
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
tats_06 said:
Do you have to go back to stock first before rooting? Or can you just run the root OVER the update? Thanks.
Click to expand...
Click to collapse
I don't think the update blocks root. you should be able to install the OTA as long as your not rooted, then once it is installed go ahead and root your device.
Ok...looks like root went thru...working on cwm recovery now.
OK, recovery installed successfully...running a backup right now.
Should I test restoring? Or should I assume I am safe?
Rooting after OTA update.
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
If you have CWM installed, you always have root via adb, which means you can get your root apps working.
If you're not running CWM, I don't know. Someone who's tried rage.bin post-update could tell you.
lukaro said:
Can someone give a diffinative answer please. Can we root after the OTA update or does the update block root?
Click to expand...
Click to collapse
Yes you can root after update, I did it fine, but had to attempt it twice, the first try it hung, so had to do a battery pull, and then the second time it worked fine.
Nothing in the update seems worth it to return to stock (I've removed so many stock apps already.)
I'm having the Force Close loop issue. My CWR seems to be missing, as all I can access is Android system recovery <2e> with the options of:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Using the Odin method didn't work for me, on multiple tries. My SD card appears to be wiped clean and I can't enter debug mode.
Is there anything short of a miracle that I can do to fix my phone? I've seen a few posts with people saying they had similar problems as mine, but there was never and explanation of how or if they fixed there phone.
Thanks in advance
Related
Help.
I have a rooted Thunderbolt and I have been able to reject the update from Verizon until this afternoon when my phone started to update on its own. The update didn't go through and I got an error icon. Now my phone just goes through the same cycle of turning it self off and trying to update and crashing.
I am able to get to the Clockwork Mod recovery page but the only option that works is the 'reboot system now', which starts the phone and the whole cycle of trying to update is started.
Does anyone have an idea of how to get my phone working again?
Thanks in advance.
Mike
I'm really sorry to hear that happened, I'm not sure what you can do. Hopefully someone will be able to help you out. But at least I can tell you that you are not alone! I wasn't rooted, but my phone did autoupdate on its own at about 2:30pm today.
I posted about it here: http://forum.xda-developers.com/showthread.php?t=1234844
Pull your SDcard, wipe the pg05img.zip file, and try again. You might have to reflash clockwork.
This is the problem with running rooted stock ROMs. I know flashing a new ROM isn't what a noob wants to do, but it will avoid these very confusing headaches.
whats if you rooted using revolutionary? As far as i know there wont be that pg05img.zip file to delete.
Would you always be in danger is this if you are rooted and stay stock?
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
loonatik78 said:
This is the problem with running rooted stock ROMs
Click to expand...
Click to collapse
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Are you sure it is the Verizon update?
I have the same behavior on my T-bolt since about 10 pst today. However, just before the phone shuts down to reboot, I see a note about a new version of Clockworkmod Recovery 4.0.1.5.
So I have been working on the assumption that it is CWM Recovery that is doing an automatic update.
I also am running rooted stock, and have not updated to latest release.
OK, it isn't the update to CWM Recovery that is the problem; it is the Verizon OTA update, which they have figured out how to force on us. I fixed my phone using the solution given by Mike later in this thread.
jbh00jh said:
Why would someone want to root their phone and stay stock ??????
Sent from my Verizon LTE 4G Thunderbolt
Click to expand...
Click to collapse
Debloating. Stock is pretty damn nice without all the extra crap.
*Madmoose* said:
Debloating. Stock is pretty damn nice without all the extra crap.
Click to expand...
Click to collapse
This, plus "root while you can" - there's no guarantee that rooting will be possible with each subsequent (unrooted) release, but you can root now and stay rooted to keep your options open. Also, getting full backups of everything is easier when rooted.
Did the fix work?
Mike, did you try what loonatik suggested? Did it work? Waiting breathlessly...
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Wait.. what? Most ROMs I've seen are debloated.. At the very least they have VZW crap removed
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
JBO1018 said:
Unless I am misunderstanding the problem wiping cache from Clockwork recovery should clear out the update and it will quit trying to install it. For the future if you go to settings in the about phone or software update section (dont remeber which) there is an option to de-select scheduled update checks.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
Yes you are correct wiping the cache fixed the problem.
mjkusa said:
Thanks guys for all your help and interest. I tried the solution offered by lunatic but it did not work. Thanks any way I was still looping through continuous on and off cycle. I did however did find a solution on another site. Here is the solution from Sele.
http://www.thunderboltforums.com/forum/htc-thundebolt-hacking-guides/2257-rs-guide-how-get-rid-ota-forced-reboots-rooted-phone.html
It was easier fix than I thought it would be. Step #1 worked.
I also did this to stop the update from happening again.
"If you are rooted use root explorer or super manager and set system to R/W. Then navigate to /system/etc/security. Find the file named otacerts.zip and rename it to otacerts.zip.bak and reboot. Should fix you up."
I'm sorry I can't remember who offered this solution to give credit to. I haven't had any updates yet but only time will tell.
Good Luck with your phone.
Click to expand...
Click to collapse
Definitely a handy resource.. Every time a new OTA comes out, this is a very frequently asked question.
I suppose you could always use an RUU too
mike.s said:
Nope. One only has to keep up with the current releases, rooted versions of which come out within days of official release.
Click to expand...
Click to collapse
Based on how many of these threads I see, that clearly isn't what's being done.
Help.
So, my boss asks me to root his thunderbolt, so I do. Then, he goes and tries to install an OTA update on the thunderbolt and wonders why it won't work. I get into work this morning and he says, "I need you to unroot my phone so I can install OTA updates"???
I'm very confused, but hey, he wants it unrooted. Problem is, I can pull the battery, startup like normal, boot into the rooted OS and immediately the thing shuts down and tries to install the OTA update he installed.
This results in the android guy and the triangle with an exclamation point in it showing and I can't go any further.
ADB DOES see the device when I do adb devices.
How do I push the stock ROM back on to the phone and have it update that back to stock?
Help.
WHY he wants the phone unrooted or even decided to update it with an OTA ROM is beyond me.
Please and thank you in advance.
Wrong section but if the bootloader still has s-off, I would install custom recovery again and flash the rooted ota rom.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=1009423
You should be able to flash the latest ota by booting into bootloader. If adb is working then I believe you can...
adb reboot bootloader
here is a link to the file you will need with instructions...
how to flash the latest ota
1. I realized too late it was the wrong section, apologies.
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Can I, using recovery, flash PG05IMG_MR1_no_hboot.zip over what is there now and go back to unroot and stock?
I use an Evo and can do almost anything on that, but the thunderbolt is a little new to me. Not my device, shouldn't have offered to root it for my boss without knowing he was going to try to install an OTA update.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
It's one of the big issues with running stock rooted. Nothing stopping it from trying to update itself and screw the pooch
Honestly, if he wants OTAs just for the latest goodies/stability and battery improvements he'd be better off with something cooked... Just my opinion though
Sent from my ADR6400L using XDA App
sanjsrik said:
2. I don't need to flash a ROOTED ROM, he wants this device back to being stock UNROOTED.
Any help with unrooting and reflashing the Stock OTA would be very helpful.
Click to expand...
Click to collapse
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom.
thepolishguy said:
Hmmm - not sure why you didn't just use the link that I provided? I will quote from there...
Code:
Using this RUU will wipe all data on your device!
Please make a backup of all sensitive data before
proceeding. Similarly, you will [B]LOOSE ROOT IF
YOU FLASH THIS[/B]. It is unclear right now
whether or not this version is easily rootable.
[B]PROCEED WITH CAUTION[/B]
This is not a link to a rooted rom. It is a link to the full unrooted ota ruu that has been put in a flashable (from hboot) PG05IMG.zip.
Click to expand...
Click to collapse
Update: Worked like a charm.
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
sanjsrik said:
Thanks, polishguy, that wasn't clear originally, will follow your link. Much appreciated.
Click to expand...
Click to collapse
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
thepolishguy said:
No problem. It wasn't clear originally bc I am not sure how XDA views links to "this sort of file". As in a "Romeo Uniform Uniform"
Click to expand...
Click to collapse
I would guess it's fine considering there are an abundance of RUU links in the dev section.
https://doc-0k-1o-docs.googleuserco...009/*/0BzrP5DWIlpplYjFOY1MwOXFNLWc?e=download
here is the ota zip
if we flash this can we flash 4.5.141 with rsd?
any answers?
I wouldn't count on it. The ZIP seems to contain what looks like the bootloader, or at least a piece of it (ap20bl.img). Who knows what might happen after that. Motorola said a downgrade is not possible.
I would just wait for the .145 fruitcake. Then switching back and forth should be safe and painless.
ok thanks for answer
Installed 4.5.145 for fun
blttalas said:
ok thanks for answer
Click to expand...
Click to collapse
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
sn0wba11 said:
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
Click to expand...
Click to collapse
Did you do this via the standard update or by flashing that zip yourself?
vikingarcher said:
Did you do this via the standard update or by flashing that zip yourself?
Click to expand...
Click to collapse
Standard
Su ota survival
Has anyone tried to install the update after activating the superuser ota survival option
Root after sys 4.5.145 update?
fdaconta said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
This response is from the developer thread. I would respond there but the policy for members with less than 10 posts is silly.
None of the existing preinstall methods (e.g. atrix-4g-moto-fastboot or superoneclick 2.3.3) work with 4.5.145.
sn0wba11 said:
Standard
Click to expand...
Click to collapse
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
vikingarcher said:
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
Click to expand...
Click to collapse
Came across a link at Android Central that used Voodoo OTA RootKeeper to restore --> Forgot I installed this awhile back; reinstalling app restored my superuser access
Re-rooted 4.5.145 after OTA
I successfully re-rooted mine last night using the pre-install method.
Read my topic here:
http://forum.xda-developers.com/showthread.php?t=2153422
From 141, to 145, back to 141.... and finally ended up with a working (and rooted) 145.
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
scott500 said:
If anyone is interested, I saw this posted today. A small OTA update released by AT&T today.
http://www.androidcentral.com/att-pushes-out-update-htc-one-m8-brings-android-444-and-hd-voice
Click to expand...
Click to collapse
This is merely a rumor. The ATT link is to the old May 2014 update.
Pay no attention.
The link to the att sight yes is for old 1.58 build, does not mean there isnt an update coming...as its being reported with a build number by more and more sights, could just be a rumour but it could also be rolling out.
Well, they finally released the update today. Finally have 4.4.4. On my m8. Now to wait for lollipop
Does anybody know where the OTAPkg file gets downloaded to? I'm trying to preserve the file and not have to download it again and again after a fail update. Thanks.
Edit: n/m found it, it's under the FUMO folder within the internal SD.
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
johnnyutah22 said:
Please save a copy. We need it for a custom rom
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
bford152 said:
I'm lost. I installed the 4.4.4 OTA, installed the latest CM12 nightly, and now I have no cell service nor options to select/enter an apn. Under apn it states "access point names not available for this user" HElP?!
ALSO, what custom roms can I run using this 4.4.4 OTA?!
Click to expand...
Click to collapse
I can't help you with CM12, but I just installed Viper One and it seems to work fine.
I updated to the 4.4.4 via OTA yesterday, and Viper installed without a hitch.
NB: Make a Nandroid Backup before flashing please.
Whats the best way to update my girlfriend's rooted M8? Currently running 4.4.2 rooted S-ON. Can she just take OTA and then will have to re-root?
I'm S-OFF on my phone so I haven't had to deal with this. Already updated my firmware months ago and have been running 4.4.4 roms.
Thanks!!
Downloading it now.
You'll have to re-flash stock recovery, take the OTA update, then restore twrp (or other custom recovery) and re-root.
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
jeremyenos said:
Same situation here I think... stock rom (never changed it yet), rooted, unlocked, s-off. Downloaded OTA then realized I needed to flash original recovery back. Did that, now AT&T sw update is of course telling me to wait 24 hours to check again. Any way around that?
Click to expand...
Click to collapse
Yeah just manually change the date one day ahead and try it again. It might take a couple of secs for it to prompt that there is an update.
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Also is there anyway to flash twrp without using a pc? I tried flashify but it doesn't seem to be working cause it would revert back to the fastboot no matter what.
Click to expand...
Click to collapse
There's a boot loader flashable twrp in the dev section posted by jball
dottat said:
I just posted a pre-rooted ruu in the dev section.
Backup data in twrp to your ext sd. Flash ruu via sd card method. Flash twrp using the free app flashify. Reboot to twrp and restore data.
No pc required.
Just make sure you backup files on internal.
Click to expand...
Click to collapse
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
johnnyutah22 said:
I noticed that flashify also will install CWM or Philz. Is your method specific to TWRP or can you use the others. The reason I ask is because I currently use Philz and would need that to restore my backup.
Click to expand...
Click to collapse
You can flash whichever you use.
I thought I read where this update would include the EYE Experience. Did I read that wrong or do I just not know how to use my camera anymore?
volcalstone said:
Could someone help me with the OTA update. I'm on stock 4.4.2 rooted and s-off. I placed back all the at&t crap in systems and tried my best to restore everything back to stock even recovery. I'm still getting a red triangle approx like 1/4 the way during the update. What sucks is that I have to download the whole update file again and it's 800+megs versus the prior updates which were a lot smaller. It's just very time consuming and would like to find out the root of the issue is.
I've done so many mods on the phone like the HK mod and various other ones. I'm trying to think back now to see if there is anything else and now I'm stuck. I don't want to restore my stock nandroid cause I would have to install everything all over again which would suck big time. I uninstall the drivers for viper4android, xposed, and even reverted the host file back from adaway. I just feel like there might be something within the system files that isn't suppose to be there. I even got rid of the att boot logo and sound but I had restored that back to stock as well. Please help if you could. Thanks.
Click to expand...
Click to collapse
I don't think root changes are the issue; as typically it will fail before it even goes into recovery with a message that the system has been modified. It might just be a bad download.
Setting up your phone again is really not that bad a proposition; especially if you use Titanium to restore apps. And it will also restore your Xposed installer and modules. Using Titanium, I can easily be up and fully configured again in about a half hour after a factory reset or RUU. Although, of course this will depend on the amount of customization in settings, etc.
You might consider updating with the new RUU (relocking bootloader required if s-on). Not only will this bypass the OTA install issue you are having, but makes for a cleaner install. Yes, you will have to set the phone up again; and you will also need to backup any data on internal storage, as it will be wiped by RUU.