My phone is asking me to update. should I update or not? If not how do I keep it from popping up the message?
Sent from my Eris using XDA Premium App
I forgot to mention I have the July OTA and have a custom Tom on there already.
Sent from my Eris using XDA Premium App
the ota will kill your root!! heres an ota disabler, just load this zip on sd and flash like a rom....hope this helps...
Thanks!
Sent from my Eris using XDA Premium App
yea no problem, definetly post back if you have any issues...
frosteddroid said:
the ota will kill your root!! heres an ota disabler, just load this zip on sd and flash like a rom....hope this helps...
Click to expand...
Click to collapse
Not true for any phone with a custom recovery. If you accept the OTA, the phone will boot into the custom recovery, and the update will immediately fail. With Amon_RA, it will fail due to a signature verification error, and with ClockworkMod it will fail due to an assert() check at the beginning of the script
In both of these cases, the termination of the install occurs before a single thing is changed. Moreover, because the OTA downloader never even checks to see if the OTA install succeeded, the nag popup will disappear after the failure, and will never reappear again (unless you did a wipe data/factory reset procedure on that ROM).
[ Edit ] the exact assertion that occurs is
Code:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/htc_desirec/desirec/desirec:2.1/ERD79/185970:user
/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/htc_desirec/desirec/desirec:2.1/ERD79/335228:user
/release-keys");
So, I guess - in the ClockworkMod case - it depends on whether or not your ROM dev changed the "ro.build.fingerprint" in their ROM file. If it wasn't changed, and your recovery boots to ClockworkMod instead of Amon_RA, then it is possible that the install will run, which would over-write the custom recovery. Not really a disaster, even if that happens, as you still have a rooted ROM from which you can run
Code:
flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
.
If you went into a bootloop after the install, and you had the 1.49.0000 S-ON bootloader, and you did not have USB debugging turned on... well, that would be a possible disaster (soft bricking). (Another reason to use Amon_RA with a current version of ROM Manager, rather than having Clockwork being written into the recovery boot.)
If you have a stock ROM which is rooted, and you DO want the update to happen, gnarlyc put together a flashable .zip which performs the same patching update, but does not overwrite either the recovery boot or the radio. You can find that flashable .zip here.
Obviously, you ought to know which stock ROM your rooted ROM is based upon before flashing either of these.
sweet! thanks for the link to gnarly's zip. i got the install failed on the wife's rooted eris (still stock rom) but was worried i would have to unroot to do it. no way im going to do it on my gsb 1.7 eris.
Related
Hi everyone. So i followed the s-off guide the other day and completed it. Today, I got a notification that system update 1.13.651.7 was available. Updating didn't work though. After running the update, the phone rebooted and the black/green team win recovery screen was brought up saying the update was aborted. I then tried to apply the update manually through the Install from zip option but the thing fails at the stage where it is verifying the signature.
My question is should and be trying to apply these updates and if so, how do I do it?
Sent from my PG86100 using XDA App
abdeviation said:
Hi everyone. So i followed the s-off guide the other day and completed it. Today, I got a notification that system update 1.13.651.7 was available. Updating didn't work though. After running the update, the phone rebooted and the black/green team win recovery screen was brought up saying the update was aborted. I then tried to apply the update manually through the Install from zip option but the thing fails at the stage where it is verifying the signature.
My question is should and be trying to apply these updates and if so, how do I do it?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If you want the update, flash a rom from the dev forum that has it in it otherwise you will lose root.
Stock rom: http://forum.xda-developers.com/showthread.php?t=1192670&highlight=stock
or flash a custom rom see my sig for my suggestions. For future updates, it is generally recommended you wait for a developer to post it rooted in the forum.
abdeviation said:
Hi everyone. So i followed the s-off guide the other day and completed it. Today, I got a notification that system update 1.13.651.7 was available. Updating didn't work though. After running the update, the phone rebooted and the black/green team win recovery screen was brought up saying the update was aborted. I then tried to apply the update manually through the Install from zip option but the thing fails at the stage where it is verifying the signature.
My question is should and be trying to apply these updates and if so, how do I do it?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
if you're ever going to apply an official update .zip, whether it be an OTA or an RUU, load the stock recovery first.
even though teamwin recovery project and clockworkmod are based on the public AOSP recovery code, the stock recovery is not open sourced and manufacturers could very well modify AOSP when creating their stock recovery.
i haven't really seen anybody do a lot of research on the topic, i.e. decompiling a stock recovery and matching back to AOSP.
it is best practice to let the stock recovery handle the stock OTA or RUU .zip files. it is also considered best practice, if you're not experienced/developer, to not load an OTA/RUU unless you are comfortable with the possibility of permanently losing root. if you're not comfortable permanently losing root, then use a custom ROM which has incorporated the updated software, as suggested above and can be found in the CDMA Dev section or GSM Dev section of this forum.
hope that gives a bit of background and helps clarify!
Thanks guys. That's really helpful.
Sent from my PG86100 using XDA App
I have a rooted Amaze with just some bloatware removed. Yesterday I received a notification in the status bar that a system update was available. When I try to run the update the phone reboots and then freezes with a big green X on the screen. Doesn't look like something official. Has anyone seen this before or know what it's about? I'm thinking maybe it's just failing to run the update because of being rooted or a related issue but can't find any info on Google about the green X.
I finally pulled the battery out because it wouldn't respond and then turned the phone on again. It booted fine and I still have the notice about the update. I'm reluctant to try again until I find out what's going on. Thanks.
I don't think you're able to install an update through a custom recovery..There should be a ROM with that update already in it.
If you have a Custom ROM you can't take the update that is intended for stock unrooted ROMS.
Sent from my HTC Amaze 4G using xda premium
Thanks for the feedback. I don't have a custom rom - just the stock minus some bloat. I can see how the custom recovery, however, might interfere.
I can't find any info on the update and what it includes or why I might want/need it but assuming it would be good to install then is there an easy way to remove the custom recovery? Would running the stock update.zip do this or do I need to go through the full un-root process?
If you have CWM recovery already,
1. Go to /downloads folder inside the internal Storage. You can find the OTA.
2. Rename it to "update.zip" and copy to External SD.
3. Reboot the device to recovery.
4. Select update.zip and update manually.
5. After update & reboot, delete both original files to get rid of notification.
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
droidux said:
Thanks for the directions. Tried and got this error
Code:
verifying current system...
assert failed: apply_patch_check("/system/app/FriendStream.odex", "some very long hex number", "some other long hex number")
E:Error in /sdcard/update.zip
(stage 7)
Installation aborted.
Click to expand...
Click to collapse
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
skr_xd said:
Seems its not possible as you have removed some programs
Think you removed friendstream also.
It seems to work only if the ROM is unmodded
Click to expand...
Click to collapse
Yes, I removed facebook and friendstream. Not sure why those would be necessary to run a system update but you may be right about not being able to update a modified phone. Maybe the update isn't anything I need anyway if it wants to update an app I don't want.
Thanks for the help.
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
droidux said:
In case anyone has a similar issue, here is what I've figured out.
The update won't run on a modified system - even if it's a stock, but changed, rom. In the interest of exploration, I restored my backup using clockwork and then ran the update. It still didn't work, but following skr_xd's advice above I was able to run the update manually. The result was a more or less stock phone without root but with the most current software. I then re-rooted the phone and re-removed all the bloat with no apparent ill effects.
Thanks for the help.
Btw, I didn't know what the green X was all about, but I think it's related to clockwork mod. Could be wrong though.
Click to expand...
Click to collapse
yes its the custom clockworkmod i made
xboarder56 said:
yes its the custom clockworkmod i made
Click to expand...
Click to collapse
Thanks for the confirmation and awesome software. I noticed there is work on version 5.0.2.7. Assuming it would be wise to update once released.
Same issue here. I have stock rom without any bloatware removal.
I just unlocked the bootloader than installed CWM and rooted the phone.
when I try to update phone OTA it stucks in splash screen (With Big Green X logo)
Flash prerooted rom you good to go
Sent from my HTC Amaze 4G using xda premium
I just spent abut 4 hours trying t figure this out...
This is my journey..
Relock bootloader
Flash one of the stock tmobile ruby rom in development section
Did the OTA update on stock
Unlocked my bootloader again
Then i tried to root using one click zerg method but it didnt work
So i flashed clockwork mod using fast boot
Then applied a su binary update i found in the development section.
In less than a minute i got root back.
Then i restored my data from nandroid backup.
My phone is pretty much rooted, bootloader unlocked, bloatware free alongside having the ota update that enabled wifi calling installed.
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
bmbrad said:
You don't need to relock your phone to do the update. If you do xboarder's recover to stock method just skip the relock part you can update your phone. So far going back to stock is the only way to get the radio updated as well which I am noticing way better 4g coverage than before!
Click to expand...
Click to collapse
working on a way maybe this weekend will have it ready
xboarder56 said:
working on a way maybe this weekend will have it ready
Click to expand...
Click to collapse
NICE! Dude you must never sleep! Always the first to get something done!
I figured out what to do. You just need to rename this update file to update.zip. then reboot in recovery and choose install update from sd card. Next navigate to download folder and install update.zip file. You will be updated and stay rooted at the same time.
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
darll said:
This worked for you because you didn't remove any of the t-mobile bloatware from your phone.. This will not work for people who messed with the pre-installed bloatware.
Click to expand...
Click to collapse
Maybe, but 8m I've got another problem after updating this way. Wifi doesn't work anymore. I receive an error while trying to switch on wifi.
I have the sprint EVO3D. I unlocked it and its rooted, but at the moment I'm still running the stock image. I keep trying to install the latest OTA update from HTC (the one that removes CarrierIQ) but it keeps failing to install...no message, no error, essentially the phone just reboots when I tell it to install the update.
Does it have something to do with CWM being flashed for recovery? I'd like to have CarrierIQ removed. Is there a way around this that anyone knows of?
I had CM7 and MIUI installed at one point, but I wanted the 3D camera that I don't get with either of those.
DarkNemesis618 said:
I have the sprint EVO3D. I unlocked it and its rooted, but at the moment I'm still running the stock image. I keep trying to install the latest OTA update from HTC (the one that removes CarrierIQ) but it keeps failing to install...no message, no error, essentially the phone just reboots when I tell it to install the update.
Does it have something to do with CWM being flashed for recovery? I'd like to have CarrierIQ removed. Is there a way around this that anyone knows of?
I had CM7 and MIUI installed at one point, but I wanted the 3D camera that I don't get with either of those.
Click to expand...
Click to collapse
If you're running into issues applying an OTA while on a rooted ROM, my first suggestion would be to suggest you grab a rooted stock ROM which already contains the OTA.
The steps to installing an OTA are fairly simple, but if done improperly whether due to lack of following directions or any other myraid of reasons, COULD damage the device or at least set the user back a few hours.
In order to process an OTA with 100% certainity, the stock recovery should be loaded. Manufacturers ARE able to add and use edify scripting language which could only be interperted and executed probably by a stock recovery image as they are not required to release the source code to their recovery image.
With that said and no mention of htc official unlock or revolutionary unlock, the process I would take on my own personal EVO 3D which would be unlocked with revolutionary is as follows:
1) Flash stock recovery image from most recent RUU via Flash Image GUI while in normal android mode.
2) Accept OTA and allow to fully process.
3) Flash custom recovery back using a PG86IMG.zip file.
4) Boot into custom recovery and via adb shell chmod 4755 /system/bin/su.
5) Reboot and everything should be set.
Another word of caution will be at step 2 to understand this will remove root access by removing the setuid flag on the /system/bin/su binary. This will be restored by step 4.
These steps might have to be tailored/changed for an HTC unlock device. Probably step 3 can be replaced by the fastboot flash recovery c:\recovery.img command.
Hope that helps!
Yes, it is because of CWM. You need the stock recovery to update officially.
Where would I download the stock recovery? I tried googling for it, but wasn't getting any straight answer that I could understand...
http://forum.xda-developers.com/showthread.php?p=22554153#post22554153
There you go
Just download a stock rooted rom zip and flash it. Much easier, and much less hassle than trying to go back to the stock recovery.
Thanks everyone, got stock recovery flashed and update is installed...now to get my apps reinstalled
sitlet said:
Just download a stock rooted rom zip and flash it. Much easier, and much less hassle than trying to go back to the stock recovery.
Click to expand...
Click to collapse
I agree, but the man wanted the stock recovery, so the stock recovery is what he got lol
DarkNemesis618 said:
Thanks everyone, got stock recovery flashed and update is installed...now to get my apps reinstalled
Click to expand...
Click to collapse
Glad it all worked!
Some people like sticking with stock, and there isn't a huge issue with that as the stock ROM is pretty good on the Note 2. However, if you want to be stock and remained unlocked, it's quite difficult to do as every new OTA re-locks the bootloader. It's also difficult to stay stock and keep a custom recovery as it will be over-written on every boot.
Now, users that want to stay unlocked and have custom recovery have an option available. This will require you to be fully stock, if you've modified anything in /system, it won't work. The only change you can have is root, but if you've modified build.prop, the kernel, or removed any files, you need to restore. If you have any doubts, flash the alternate restore file (after extracting it) from here.
There is one other requirement for this, and that is you need a custom recovery installed. If you've unlocked, you'll already have one. If not, you'll need to be rooted and you can use ROM manager or GooManager to flash a custom recovery (after going back to stock of course).
Now you have the pre-requisites down, stock rom and custom recovery, so all you need are the files. There are two updates available, so there are currently two files to flash to be on the latest OTA. You can download them below, and installation is as simple as downloading them to your phone and installing them via recovery. If you went back to stock VRALJB, you'll start with the VRALJB to VRALL4 file, then flash VRALL4 to VRAMC3 to get to the latest system. It should be fairly easy to figure out.
If you have any errors when flashing, odds are, you did something to files in /system and caused a problem. If that is the case, start over and flash the alternate restore file and proceed from there. I'll continue to update this as new OTAs are released then as well.
[size=+2]Downloads[/size]
VRALJB to VRALL4
VRALL4 to VRAMC3
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Digbob said:
Will this update baseband also?
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
It updates everything except for sboot.bin, tz.img (both bootloader files), and recovery.
hey thanks for this!
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
it says you must be on completely stock rooted with a custom recovery. being you have a custom kernel is most likely the problem. anything modified in /system will cause a fail. flash back to vraljb alternate restore file, then upgrade...or boot into recovery and flash beans mc3 stock rooted .zip rom
either way you will most likely need to wipe data to upgrade...atleast thats normallya prerequisite when changing bases.
FAUguy said:
I'm on VRALJB stock, rooted and unlocked with CWM.
But I added Google Wallet working, and using a different kernel for overclock.
I tried the first update to LL4 just to see what it would say, and errored when applying the NFC.apk file, which is from the Wallet patch.
Not sure if it's easier for me to try and get the phone back to stock by restoring the original NFC files and kernel, and then try the LL4 update again, or just flash the phone with the rooted C3 ROM, but then would have to reinstall all my apps and settings.
Click to expand...
Click to collapse
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
imnuts said:
I said completely stock, and if you modified anything on /system it would fail, and you're surprised that it failed? You installed the Google Wallet hack, which modifies files on /system, and then you have a custom kernel as well, both of which will cause this to fail (as I already stated). Just be happy that the file checks were left in place and your phone still works at this point.
Click to expand...
Click to collapse
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Hey thanks for this! This'll make my wife very happy. I thought I'd have to clean install beans stock rom. She just loves stock.
Sent from my Note II using Tapatalk 2
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
OTA fails if you have a custom recovery.
Sent from my Note II using Tapatalk 2
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
FAUguy said:
I knew that it wouldn't work, but have tried it just to see which error message it would show, which it stopped when it got to the NFC.apk. I know it needed to be fully stock with nothing changed in the /system.
I was just asking, at this point, would it be easier (or better) to try and get it back to stock by replacing the modified files with the original ones and try again.....or flash the modified C3 rooted ROM. I think Adam is still trying the get his root/unlock for C3 to work right for everyone.
Click to expand...
Click to collapse
You're setting your phone up again either way.
radio five said:
If you have to go all the way back to stock, why not just take all of the OTA updates and then root/unlock your phone?
Click to expand...
Click to collapse
Not everyone is running a custom ROM. Some people are unlocked and on stock rooted with custom recovery and that's it. This is meant so they can stay up to date and remain on stock, rooted, and custom recovery.
TonikJDK said:
I am unlocked with recovery running beans stock vramc3. I flashed the new modem afterwards. How is this different?
Click to expand...
Click to collapse
This will be fully stock (minus recovery over-write). Beans did some other stuff to his ROM package from what I saw the last time I looked at the thread. Nothing major or groundbreaking, but it isn't as close to stock as this is.
pmazz850 said:
If I deleted a couple of apps that were pre installed after rooting, will it fail? Its all stock otherwise, rooted, custom recovery.
Click to expand...
Click to collapse
Really?
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Mac of York said:
It did it to me too. I'm just going to clean flash beans stock.
Sent from my Note II using Tapatalk 2
Click to expand...
Click to collapse
Yah, I think I'm gonna wipe/flash beans odex rom VRAMC3 & radio/restore data from NAND backup from VRALL4, hopefully it should be fine. Unless anyone would know otherwise?
Systom said:
VRALL4 to VRAMC3
Update fails, verified hash matches;
E: Error in /sdcard/Download/vrall4_to_ramc3.zip
(status 7)
I don't think I changed anything on this phone...all I did was unlock bootloader/flash custom recovery TWRP 2.3.2.3, just to NAND & Wifi Tether, completely stock.
Click to expand...
Click to collapse
What change for Wifi Tether?
imnuts said:
What change for Wifi Tether?
Click to expand...
Click to collapse
WifiTether_TrevE_Mod_11_22_2012.apk
I'm rooted, s-off, stock Android 4.0.3, amon recovery.
The latest firmware update from Verizon keeps trying to push through. It downloads (laboriously). Then pesters me to install or reschedule. When it tries to install, it just loads up amon. I just restart and it's back to normal. Don't know how to install if I have amon. Not sure I want to install anyway, my rezound gets great reception already.
Is there a way I can get my phone to stop trying to install this new OTA?
bloodymurderlive said:
I'm rooted, s-off, stock Android 4.0.3, amon recovery.
The latest firmware update from Verizon keeps trying to push through. It downloads (laboriously). Then pesters me to install or reschedule. When it tries to install, it just loads up amon. I just restart and it's back to normal. Don't know how to install if I have amon. Not sure I want to install anyway, my rezound gets great reception already.
Is there a way I can get my phone to stop trying to install this new OTA?
Click to expand...
Click to collapse
This is because you are on a stock ROM, with a custom recovery. Most Custom ROMs disable the ability to check verizon for updates, the stock ROM doesn't know any better.
The stock recovery is responsible for installing updates, AmonRa gets the update command and goes WTF is this and ignores it.
Grab root explorer and look in /system/etc/security (assuming you have root)
rename otacerts.zip to otacerts.zip.bak
This will prevent the HTC ROM from checking with verizon for an update.
or try out some of the custom ROMs, alot of them have cool features like turning on the camera flashlight by holding home on the lockscreen