Database Users

[Q] System update 1.82.720.1

I received this OTA update on my HTC Desire Z. I'm from India.
Can anyone tell me how to update my phone with this update? I'm currently running the stock OS but with permanent root.
My phone details are
Android version : 2.2
Kernel version : 2.6.32.21-g9d69527
Build Number : 1.34.720.6
Forgot to mention why I'm asking this question. When I tried to update this new FOTA I got an error. Installation aborted.
Thanks

by clicking on accept?? maybe restart first ? probably a app is blocking the update, maybe you can do a whipe first?

I even tried updating it via clockwork mod by manually selecting the zip file. During that I got signature failure. Installation aborted

OTA updates do not work reliably on rooted phones, the problem you are having is beacuse of Clockwork what you should do is try to flash the stock htc recovery and then try to update,this worked for me but do remember you will loose root possibly forever (or atleast until a root comes out for 1.82 if at all) and all the advantages that go with it.
here is a tutorial for flashing recover images
http://forum.xda-developers.com/show...ht=flash_image
this is the default htc recovery image you can use in the above guide
http://www.sendspace.com/file/gu11ed

Thanks, the link doesn't work, can you fix this please?
Also wondering if I really lose my root etc, isn't using this guide: http://forum.xda-developers.com/showthread.php?t=985584 not a way to get back perm root etc?

If you don't want to loose root but you want the latest Sense, I suggest using VirtuousROM
Here: http://forum.xda-developers.com/showthread.php?t=837042

here you go
http://www.mediafire.com/?93fef9ac9webd4j
about the root i don't know it may or may not work, the thing is you can't be sure because no official root for 1.82 has been announced, i would tread with caution.

UK CWR Backup needed Desperately (Any Version)

Hi, My UK tablet is stuck on a testing update that was on the FTP and now I cannot update my tablet. My Tablet is stuck on ThinkPadTablet_A310_02_0039_0080_UK_testing but the ThinkPadTablet_A310_02_0039_0086_UK patch only works from 02_0037_0075_UK
My only hope is that I can load on a CWR backup of someones stock tablet from any version. Then I could proceed with standard updates.
Any one who rooted their tablet and had a Nandroid / Clockwork Recovery from a UK tablet and could get that to me would be amazing.
Thanks Steven Richardson

I'm copying my backup now from my sdcard. Will zip it and upload for you in a couple of hours. Its a stock 86 UK backup. Hope that's what you need.

Thats amazing thank you so very much! Cannot wait!

Sorry for the delay. Couldn't find a decent place to upload the file. Haven't used Google drive before but had to upload there as even my dropbox couldn't take it. The file is in a self-extracting archive, just run it and copy the folder "stock.ota2.clean" to your clockworkmod/backup/ folder in your external SD card.
https://docs.google.com/open?id=0B9_U8cZCMA1NS0FHRXRHUTFfWjg
Edit: The file is 401mb.
Edit 2: Finally managed to get it on dropbox. Link: https://www.dropbox.com/s/ohbf1odrvsfzamb/Stock.ota2.Clean.exe
If you don't trust the .exe archive, scan for viruses before running it.

Thanks ever so much. It works great. Have given you Thanks on the forum as well.

I installed your backup. Now i'm not able to update anymore. (Like before )
Does anyone know why?

I just uploaded a clean backup, I dont know if you can update or not. Lenovo always find a way to mess up updates so I haven't tried to update, waiting for positive news from others.

I used it an now am sitting pretty on Ice Cream Sandwich!
Had to install 87 and 89 first
I then rooted it and put in CWR and then updated to ICS and kept root!
Once again thanks

Unfortunately it is not an update to ICS is possible.
Error message every time "failed to verify whole-file signature"
It is probably better to wait for a finished backup of ICS.
I think you must CWM Uninstall before an update is possible.

You can install all of the updates. To get 87 on you have to modify the update-script file inside the update and remove the Indigo assert lines. Then use CWR to install the update.
When i installed 87 it over wrote CWR with the stock android revocery so you could continue on from there with stock recovery.
I used stock recovery to install 89 then I re-rooted and put CWR back on so I could fix the busybox error that comes with the ICS update.
I got mine fully working with root and CWR (although havent check CWR since ICS come to think about it)
Steven
EDIT: just checked ICS update puts stock recovery on.

Just got ICS working with this backup
Sent from my ThinkPad Tablet using XDA

folkommen said:
Just got ICS working with this backup
Click to expand...
Click to collapse
Can you post a short tutorial, how did you proceed?
Did you have Root on ICS?

I lost root during the update. Even the OTA Root keeper wasn't able to restore it.
But then I have to try rooting it myself.
Short instruction to get ICS with this backup:
1. Restore the backup with cwr
2. Modify the updater-script in the 0087_UK update
2.1 open updater-script (/META-INF/com/ google/android/updater-script)
2.2 delete the lines 4 and 5
3. install the 0087_UK update using cwr (install zip from SD)
(This is going to overwrite the cwr)
4. Use the normal ota updates (in the settings)
5. Finished

Thats it.
My TPT has now ICS.
Thanks for help.

I'm happy for you guys that have updated to ICS but some people (me for example) still have reservations about updating to ICS. I'd be grateful if you guys could post some feedback about ICS on this thread:http://forum.xda-developers.com/showthread.php?p=26792555#post26792555
It would also help others as well

ok to update ?!

ive got clean rom installed and the google update has come up....should i install it !?!?

Have you received KitKat already?

Running a custom ROM you cannot install Google updates. It will fail and you will come back here asking why it failed.
Sent from my Nexus 5

onisuk said:
ive got clean rom installed and the google update has come up....should i install it !?!?
Click to expand...
Click to collapse
Hi, onisuk...
Any particular reason why have you created two threads asking the same question?
OTA's aren't full ROM's... they are 'patches' to files the OTA update expects to find ONLY if you are currently running official Google factory stock. This is accomplished by the OTA first running checksum tests on all files in /system and elsewhere on the Nexus 7. This is to confirm/ascertain that nothing has been changed or modified from official Google factory stock. It would, after all, be impossible for a Google OTA to apply a 'patch' (ie. update) to an important system file, if that system file had already been modified by the user, as would have occurred in the event of a Custom ROM being flashed.
If just one file fails this checksum test, the OTA will abort, with no changes made. And since Custom ROMs are a departure from the official Google factory stock ROM, the OTA will fail. And thus, this is why Googles OTAs can never be successfully applied to Custom ROMs.
So the answer to your question... is 'no'. It would be pointless.
Any subsequent updates to CleanRom would have to come from the developer of that particular Custom ROM itself... and not from Google.
Rgrds,
Ged.

just installed it and didnt say it failed was just a 3.4 patch only a few mbs .... didnt realise id double posted if some mod could remove the other one please !

[Solved] OTA update fails on Yoga Tab 2 1050F

Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay

jayp57 said:
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
Click to expand...
Click to collapse
the thing is that not always the 'unroot' works for doing a system update, the unroot (have you performed the full one?) could leave behind modified binaries or maybe apps you installed have did that (for eg if you installed busybox it will leave the new binary) and the first step of the OTA update is to do a check of all the files that are going to be updated (patched) and if one of them doesn't match the sha1 checksum the update will abort (will not change anything on your tab when aborting). you can fix it by:
1. (complicated) restore the orginal files (you can check the recovery log on your cache partition to see where it failed)
2. (recommended) flash a stock rom matching your existing Android (you are on lollipop so you can use this for a stock lollipop install)
ps. factory reset doesn't save, that one just erases 'data' partition, has nothing to do with the ota (that usually updates files on the 'system' one or the 'boot/recovery/fastboot' partitions)

Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay

jayp57 said:
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
Click to expand...
Click to collapse
if you start with tmp_root it will open an early adb shell as root (regardless of whether your tab was or not rooted)
check after you shell in to see if the /cache is mounted (input a simple mount) and if it is not you need to mount it
afterwards you will need to go and do an adb pull on your recovery log (if i recall is on /cach/recovery ) and check inside to find on what did the ota failed
however this is cumbersome and even if you find on what it fails you still will have to find the original files (and after you try to OTA again it can fail many more times on other files as the OTA is aborted on the first non matching file and if there are many you will need to repeat these steps over again). i never did this, i am just saying that it could be done, but why would one waset maybe hours just so he can bring his system back to the same state it could bring in 3 minutes by flashing a stock rom? but if you want the complicated way feel free
if i were you i would just flash the stock rom in 3 minutes (that is how long it takes) and move along
what security reasons you are talking about?

I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.

jayp57 said:
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
Click to expand...
Click to collapse
oh, i see... i doubt they are tampered by anyone (except Lenovo of course ) the files i provide have already been used by others (and if they were to be tampered they would have failed future OTA's, the boot image is checked and it won't load if modified etc)
as a personal thought, to tamper a stock rom (to whatever purpose one would want) so that they cannot be detected by a future ota requires a level of knowledge that i think keeps us safe (i think one who is able to do such a thing would not 'waste' his time and resources on doing it to a normal/casual user like we are), so if you are able to take ota's you can safely assume that the files are the ones Lenovo put in there (not to say that Lenovo could not do funny things tho)
i wish you to become so important that one day this could be a real concern

yeah you are right.
thanks for your support. i managed to update my tablet.

Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.

saupiquet said:
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
Click to expand...
Click to collapse
the link is in my first reply here

Searching for NPJS25.93-14.7-3

Hi! I'm on NPJS25.93-14.7-3 (December 2017 security update). My phone is Moto G4 Plus XT1644 and I'm rooted with Magisk.
I want to install the new OTA update (NPJS25.93-14.7-5), but since I'm rooted I need a stock NPJS25.93-14.7-3 so I can restore the recovery. I have been searching for weeks but I can't seem to find this version.
Anyone know where I can find it?
Thanks.

As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12

echo92 said:
As far as I know, there is currently no NPJ25.93-14.7-3 or NPJ25.93-14.7-5 firmware uploaded to either firmware.center or the Motorola Firmware Team Android FileHost page.
There is a way to revert back to the stock ROM (credit to Danny1976 and pastorbob62 https://forum.xda-developers.com/showpost.php?p=76081679&postcount=110 ), though you will have to flash the NPJ25.93-14.7 stock ROM (Sept 2017 security patch). Though normally downgrading isn't a good idea, in this case you're only downgrading to the directly preceding firmware and then the OTA should bring you back up to NPJ25.93-14.7-3, after which you could flash the OTA update to the Feb 2018 security patch.
So the general procedure is:
1)Back up your device (make a TWRP backup and keep it safe).
2)Download the NPJ25.93-14.7 stock ROM (retail US: https://androidfilehost.com/?fid=817906626617945295 or Amazon software channel: https://androidfilehost.com/?fid=817906626617956922 )
3)Flash as per the above linked XDA post. You may wish to ignore security downgrade errors with GPT/bootloader as the next OTA update should flash the same bootloader as you currently have. These set of flashing commands should not affect your data but nonetheless, at least you have a backup.
4)Reboot and update to NPJ25.93-14.7-3
5)Reboot and update to NPJ25.93-14.7-5
Then you should be up to date. I do not know if this procedure will work for the next OTA update , so perhaps best to boot TWRP, do not swipe to allow modification in TWRP and take a backup of your NPJ25.93-14.7-5 installation. This should be okay to revert back to if there is no firmware still available.
You may wish to read the posts from this page and the subsequent pages for more information: https://forum.xda-developers.com/mo...e-security-patch-usa-february-t3745147/page12
Click to expand...
Click to collapse
I will look in to this in more detail. Thank you very much!

This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!

juanml said:
This worked like a charm! I followed the steps and now I'm on NPJS25.93-14.7-5.
I read somewhere that this version fixes the screen ghosting effect, but sadly not for me, so I had to root again and correct the RGB values.
Thanks!
Click to expand...
Click to collapse
Yeah, it seems that if you are one of the unfortunate who has the ghost touch issue it isn't fixed by this version. I am on 14.7-5 and I don't have that problem at all, which leads me to believe it is a hardware issue. Doesn't explain why some versions don't have it though.

Hi! Anyone know if this method still works for updating to NPJS25.93-14.7-8?