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.
Hey guys, I followed one of the tutorials on how to unroot your EVO 3D and bring it back to stock. Before I unrooted my phone, I kept getting a notification that an OTA update was available, specifically version 2.08.651.2 (August 18, 2011). Right now, my software number is 1.11.651.2. I want to update to the newer version, but when I go to Settings > System updates > HTC software update > Check now, it shows no updates are available. I've tried rebooting the phone and checking repeatedly. I'm kinda lost here and not sure what to do. I was wondering if the PG86IMG I downloaded to return to stock disabled OTA updates, but I highly doubt that since it's just a stock image. If I could find a download link to the updates, I could apply them manually through the bootloader. If not, I might suck it up and take my phone into Sprint and get them to see what's up and update my phone there. Either way, what do you think I should do? I want it updated though. Thanks in advance.
so u unrooted using the approved method and then tried to update to 2.3.4 via HTC but it would'nt find the update? Just wanna make sure u know that if u take this update ur only option is to root via HTC's unlocked bootloader which isn't a true unlock... secondly if that is ur desire and the stock image won't find the update then i would check ur source and make sure it's not missing something. I turned off my update check cuz once it checks and finds an update that little icon stays in ur taskbar unless u factory reset and i was waiting to root with teamwin's method so i didn't take the update. if i knew how to pull the image without updating id post it for ya...
Yes sir! I understand that updating my software to version 2.8.651.2 will prevent my phone from being rootable until somebody figures out a method to make it rootable. I have no need for rooting my phone actually. I tried out a few roms, and I would rather stick with a stock unrooted rom in case I ever need to take my phone into Sprint for service. The Sprint store where I live won't do any service to a rooted phone, so I need to be on the safe side. I went to the store today, and unfortunately the only people available at the time were sales representatives, so they were of no help. They just told me to wait and keep trying to update the phone periodically. If it doesn't show any updates within the next month, my only choices will be to either call Sprint and see if they can push the update to my phone or find an update image, transfer it to my phone, and manually update it through the bootloader. I also read on an EVO 4G thread that the phone won't update if it's missing SprintUpdater.apk. I doubt a stock rom would be missing that app though. I had the update notification when I was rooted, but I didn't download it because it would break my root, and now that I'm completely back to stock, I should get the notification. What gives? I wish Sprint would send out the updates all at once instead of in waves. Anybody wanna chime in?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Having the same problem. But i havent tried unrooting the phone.
So I have a rooted One M8 with TWRP recovery running 4.4.2. Recently an update came through for 4.4.3, to get rid of the notification I froze the updater. Now for the purpose of getting Viper One, I need 4.4.3. But when I press software updates it says 'There are no software updates avalible for your phone'. But there was prior to freezing the updater. Help me :silly:
(PS. Apologies if this thread is poorly located)
http://forum.xda-developers.com/showpost.php?p=51623014&postcount=7
es0tericcha0s said:
http://forum.xda-developers.com/showpost.php?p=51623014&postcount=7
Click to expand...
Click to collapse
Hey thanks for the reply but I don't think my problem is that complicated, is there anything you could recommend? The option to update was available until I froze the updater, now it's not.
:good:
Can anyone help?
I gave you a direct link from the rom you are trying to install that tells you what needs to be done. Not sure what else you would need. If you aren't getting prompts to update via OTA, there's 2 ways to update the firmware needed. Either via the official RUU for your phone and carrier (which probably isn't even available yet)or via a firmware package that's flashable via fastboot but you must be S-Off. Sometimes you can force the phone to check for updates by clearing the Google Services Framework, but this is not advised as it can have unintended consequences with how Google sees the phone and sends notifications and such. Plus just because there IS an available update does not mean you're next in line. Many carriers have staged roll outs and it'll get there when it gets there.
If it's too difficult for you then you either shouldn't be messing with custom roms or seek help from a qualified shop.
es0tericcha0s said:
I gave you a direct link from the rom you are trying to install that tells you what needs to be done. Not sure what else you would need. If you aren't getting prompts to update via OTA, there's 2 ways to update the firmware needed. Either via the official RUU for your phone and carrier (which probably isn't even available yet)or via a firmware package that's flashable via fastboot but you must be S-Off. Sometimes you can force the phone to check for updates by clearing the Google Services Framework, but this is not advised as it can have unintended consequences with how Google sees the phone and sends notifications and such. Plus just because there IS an available update does not mean you're next in line. Many carriers have staged roll outs and it'll get there when it gets there.
If it's too difficult for you then you either shouldn't be messing with custom roms or seek help from a qualified shop.
Click to expand...
Click to collapse
Thank you, the problem did however solve it's self. It turns out OTA updates are queued and by freezing the app I had reset my position. The update is now available.
I'm going to flash a stock recovery and update the firmware.
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Beartooth01 said:
I just received an extended refurbished warranty replacement for a dead VZW Galaxy S4 SCH-I545 NC5. My old model was rooted, safestrapped, custom rommed, and had ota apps disabled. This new phone is also an NC5 (build date before June, so no problem rooting with TowelRoot). However, when I activated it and rooted it, the upgrade for NG6 was downloaded but not installed. I've rooted the phone and frozen the OTA apps, but I get an annoying popup every few minutes asking if I want to install the new upgrade now or later (clicking later produces a clock to set the time for an automatic upgrade). There is no option for not upgrading. I DON'T want the NG6 build, but the constant popup, which I have to clear with the Back key each time is a roaring PITA.
Anybody know how to disable the popup? The upgrade is already downloaded and I'd like to delete this as well as it is no doubt taking up #*%@^ unnecessary storage, but haven't found the right directory yet.
Any help will be appreciated.
Click to expand...
Click to collapse
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Thanks - worked for a while - then popup returned
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
I did try that. The popup went away for several days and then came back. There must be at least one root-level app I haven't disabled.
Thanks for the help, but I'm afraid I still need a bit more.
Still having popups...
socal87 said:
Yout best bet would probably be to do a full wipe, such as an Odin, and restore the phone that way, then immediately root and freeze OTA updates before the phone has the chance to downloaf them.
Click to expand...
Click to collapse
When I first got the phone, I disabled OTA, I ran the update - which failed, of course. It got rid of the popup, but I did not wipe the phone as I am a longtime Motorola Droid user and am not totally comfortable using Odin (This is my first Samsung and it's like going from Droid expert to Odin newbie). I have since restored nandroid and Titanium backups from the previous phone (this is a warranty refurb). The backups also included disabled OTA apps from my previous S4. Apparently, I missed one somewhere, as the behavior just recently returned. I'm going fishing on the root level again [sigh].
If anybody would be so kind as to list the exact .apks and their directories involved in OTA, I can make sure they are still disabled and run another failed update. This may be different from my Droids, since it is being referred to as a Samsung build update, and not an Android version update.
If anybody knows where the downloaded update is hiding, I can remove that as well.
Thanks in advance.
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Thanks also.
fxwrangler said:
Im pretty sure the app u need to freeze is listed as SDM.. That should stop the update and popup.
Click to expand...
Click to collapse
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
i just made a post about the same problem. I renamed them. so we will see what happens
To delete the OTA zip use a file explorer with root privileges like "ES File Explorer" navigate to /data/fota and delete update.zip
Beartooth01 said:
I always rename SDM.apk and FWUpgrade.apk, but, with Samsung (with the OTA already pushed, but not installed), I had to jump through several other hoops. To see what else you can do to solve the problem, check out:
http://forum.xda-developers.com/show....php?t=1856632
Click to expand...
Click to collapse
That link is dead. Can you please direct me to a good link for that? Thank you
re-rooting after MJ7 kernal pushed by google?
swolh said:
That link is dead. Can you please direct me to a good link for that? Thank you
Click to expand...
Click to collapse
Well - renaming SDM.apk and FWUpgrade.akp stopped the totally annoying push notification for google's new MJ7 build for the S4. But by renaming SDM.apk, my Verizon app visual voice mail stopped working. When I returned the SDM.apk file to it's original name, the visual voice mail works, but I get the annoying notification from google over and over.
I'm trying YouMail app for visual software and am waiting to hear from them about whether their app uses SDM.apk. If YouMail is like Verizon's visual voice mail and uses SDM.apk, then my next thought is to unroot the phone, let Google do their update to MJ7, then re-root. I'm wondering if anyone has done this.
My phone came with NG6. To root, I had to flash the NG5 stock kernal, then root using towelroot. Once rooted, I flashed the NG6 kernal. If I unroot and let google flash their new MJ7 kernal, will I be able to repeat the root process (flash NG5, the root, then flash MJ7)? If that route were possible, would I need to find a separate place to download the MJ7?
Is there any other way to stop google's annoying notificaton and pushing MJ7 at me? All help greatly appreciated.
---------- Post added at 09:58 PM ---------- Previous post was at 09:16 PM ----------
XRSTOY1 said:
Try this,
http://forum.xda-developers.com/showthread.php?t=1856632
you'll still get the pop up so go ahead and hit update, it wont be able to find the update so it will bomb out, and not bother you again.
Click to expand...
Click to collapse
My apology. I missed this link first time thru this thread. That link to a thread titled "[HOW TO] Disable OTA Update Notifications!!!!!!!!!!!!!" is pretty helpful. We'll see in a day or two if the notification and push attempt continues, but I'm pretty optimistic following the instructions in that thread will stop it.
http://www.droid-life.com/2014/12/05/lg-g3-on-verizon-gets-advanced-calling-1-0-volte-in-update/
The update mainly brings Advanced Calling 1.0 and updates to some LG apps.
It looks like Advanced Calling also needs to be enabled on your account.
http://www.verizonwireless.com/supp...Turning Advanced Calling On/Off on Your Phone
Personally, I'd like to know if someone who is stock/rooted with no system files changed can accept the update and keep root. If anyone gets it and tests that, please report back. Also, include whether or not SuperSU is in survival mode.
With the previous update, I was stock/rooted with 1 system file that dealt with headphone volume changed. I had to restore the original version of that file, then the update completed and root was kept (without SuperSU survival mode being required).
I've done the check for updates on my phone, but nothing yet.
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
david_hume said:
I've actually just accepted the update and I still have root. However it may appear to run slowly at the beginning, but eventually everything came back. So if you're worried a root app won't work, then wait around 3 to 5 minutes and everything should be working again and back to normal as well. I was rooted from 10C and now I'm on the latest update.
Click to expand...
Click to collapse
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
lexluthor said:
I see the update available to be pulled now.
SuperSU in survival mode or not? I'm on 11C, but I wouldn't think going from 10C/rooted to 12B or 11C/rooted to 12B would make a difference. I guess I'll give it a go here as soon as I can restore that system file.
Click to expand...
Click to collapse
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
I don't think survival mode is required. It wasn't went I went from 10C to 11C.
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
hawkswind1 said:
I'm holding off on this one. I bounce between 4g and 3g a lot and I heard that if you start a call on 4g and it drops to 3g, you will drop the call. Not sure if this is true, hope someone can chime in
Click to expand...
Click to collapse
From what I read somewhere, I think you can turn it off if you don't like it. My update completed, it's optimizing apps now. Will post once I confirm I've kept root (or not).
I just updated mine. I upgraded from 11C and still have root. I put my SU in survival mode just in case, but I'm not sure if that was necessary or not.
Also, for those that are worried about being stuck on VoLTE. There's a new entry in the Settings menu that lets you turn the "Advanced Calling" on/off at will.
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
EDIT: nvm, got it.
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
xdabbeb said:
If someone could pm me with a link to a system partition dump (or kdz) it would be appreciated, thanks.
Click to expand...
Click to collapse
I 2nd this!
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Same thing here. I hope there is something else other than using LG Flashtool to download the stock firmware
taihard said:
I've been doing some searching and still haven't found an answer yet... anyone know how to get rid of the error 0x1117008 when trying to update? I originally was getting error 0x11110004 but found out that was related to the hacked hotspot apk... put the original back and am now getting the new error. I've uninstalled pretty much every app that requires root and am trying to update with super su in survival mode but still a no go. Anybody know what I need to do besides factory restore?
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Here's another thing i'm noticing... before, I downloaded a couple UI themes to change the nav buttons at the bottom through g3 tweaksbox and after removing g3 tweaksbox, the buttons changed to stock on the home screen but if I go in to settings or any other app it still shows the "LG" logo as my "home" button... maybe some left behind changes that are preventing update?
lexluthor said:
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
I did this earlier, it shouldn't be difficult for you, assuming your admin isn't a jerk of course. It's a feature that needs to be checked on your account, but it's also a free feature, so I'm not sure what excuse they'd have for denying your request.
taihard said:
**EDIT** Could it be because my software status shows up as "modified"? Those that have applied OTA with root, did/does your software status say "modified" and update still worked?
Click to expand...
Click to collapse
Can't help you with your error code, but I can say that my rooted phone also reported as "modified" status before applying the OTA and it still does afterwards as well.
Please help
Phone is rooted and has oem rom ... and xposed framework for tweakbox philz recovery mode just keeps loading after i treid the update what can i do i cant get back into my phone at all please help
Also tried resotring a backup i made yesterday before any of this and its still doing the same thing please please please helpl
j0hnnyn said:
I'm still on 10b rooted using xposed installer with some system apps uninstalled. Any chance I'll be okay taking the update?
Click to expand...
Click to collapse
No. Xposed will block all OTA and removing system Apps will also.
david_hume said:
I had SuperSU on survival mode. That's what I've always done for each of the updates Verizon released and I've been able to keep root because of it.
Click to expand...
Click to collapse
lexluthor said:
I'm back up. I had to restore the sound system file, do the update, then put my custom file back. My frozen apps stayed frozen. I had to re-install xposed framework (didn't have to uninstall it first) and I still have root (I did not have SuperSU in survival mode). All in all pretty easy. Yes, I know the update could have included a shut out of root, but it didn't (for me).
You'll probably have to restore those system apps if you did any type of "hack" uninstall (as opposed through some sort of regular OS menu).
Other than that, you should be good. Just re-install xposed framework through the xposed installer that's still there after the update.
I see a new settings menu for advanced calling with an activate button. It doesn't work for me though because I'm on a business account. I'll have to see if I can get the admin to do it for me. I guess it can be activated either there or through the link in the OP to the My Account portal.
Click to expand...
Click to collapse
can one of you guys (or anyone else who took the update) use this code to pull the modem for us please?
(use terminal emulator)
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/modem-12B.img
Thanks!!
tech_head said:
No. Xposed will block all OTA and removing system Apps will also.
Click to expand...
Click to collapse
I had Xposed installed and it updated no problem. But I would think the system apps would make it fail though.