Database Users

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)
TnT 1.1-3588 recovery ROM, dated 01/24 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
md5sum: 0f07d710728640ea1e0f4a5d6d3fa72c
TnT 1.1-3389 recovery ROM, dated 12/23 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
md5sum: e6c09077f67b29c42643b7ae5f10d6e2
TnT 1.1-3316 recovery ROM, dated 12/19 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3316-user.zip
Alternate link: http://www.mediafire.com/?p9o52540baa5vfg
md5sum: 1333e22b6d802096d3c63757680777f0
TnT 1.0.1-3053 recovery ROM, dated 12/10 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
Alternate link: http://www.mediafire.com/?qy92jzoz8upy8xa
md5sum: 7b800e409b5324f2c69e7ba6f84eab97
TnT 1.0.1-2967 recovery ROM, dated 11/22 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-2967-user.zip
Alternate Link: http://www.mediafire.com/?99eb11cqhvrkkc7
md5sum: 43eb0358db25b492751b1b0a71568c51
These were grabbed from my over-the-air update. They are full recovery images that wipes everything except the user data.
NOTE: These are only for 1.0.1 or 1.1 based stock versions. For 1.2 based stock versions, they will be hosted in the same location as my 1.2-based mods./[/url]
===================================
Instructions for use with the internal memory:
1- Mount your device to your PC
2- Download the ROM you wish you use, and save it to the root of the mounted drive. Rename it to "update.zip"
3- Create a folder on your mounted drive callled "recovery".
4- In that recovery folder, create a file called "command", and add this line to that file:
Code:
--update_package=SDCARD:/update.zip
NOTE to Windows users: If you use notepad, it might name the file "command.txt". That won't work. It cannot have a file extension. I would recommend downloading and using the excellent program "notepad++" as a notepad replacement.
5- Shutdown the device and then boot into recovery (Hold Power button and volume up key for a few seconds). If you are using standard recovery, the install should run automatically. If you are using clockworkmod, you will need to manually choose the update.zip file.
6- Reboot when completed (standard recovery users will be rebooted automatically).
Other note: These stock ROMs WILL flash recovery, as they are designed to do that. If you are using clockworkmod, that recovery tool will most likely be wiped out. Also, if you experience a boot loop post-install, you won't have clockworkmod installed to correct it - there are ways to install a clockworkmod image off your microSD, if necessary, then wipe your user data. Most times, these reboot hangs are due to incompatible data partitions between mods - this is especially true for ROMs like gADAM.

This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!

nick325i said:
This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!
Click to expand...
Click to collapse
It's spotty with cwm - I've seen the same thing - cwm probably has an issue being overwritten, for some reason.
You might want to alter the ZIP and just rip out the line that's trying to overwrite recovery.

Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?

daCalifa said:
Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?
Click to expand...
Click to collapse
I don't think they'll catch it. Just don't leave your user data intact or anything in the internal memory!

Where can I find the "/recovers/command" file?

deleting that line from the updater-script file worked for me with clockworkmod recovery installed.. if anyone is a noob here's some instructions..
unzip the vanilla recovery rom.. go into the "update-smb_a1002-2967-user\META-INF\com\google\android" folder and edit the updater-script file. I had to use notepad++ to edit it, regular notepad wasn't showing the formatting correctly. then just delete this line "assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));" save the file, then zip up the contents of the update-smb_a1002-2967-user folder into an update.zip and copy it to your gtablet. make sure the inside of the update.zip shows the system.img etc files in the root of the zip and that you don't zip it up so those files are one folder deep into the zip. hold down volume + while turning the gtablet on and it should load clockworkmod and let you flash the new update.zip.

Wishmaster2 said:
Where can I find the "/recovers/command" file?
Click to expand...
Click to collapse
It's not in here -- 1.0.1 is a 100% vanilla ROM from Viewsonic so I did not touch it. Viewsonic even calls it 1.0.1.
For the command file, you can grab that in the homebrew 1.0.0 version.

I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
EDIT: I did tried the flash 1.0.0 on top of 1.0.1 but (not too surprisingly perhaps) nothing happens. I was able to get back to 1.0.1 from TnT Lite 2.0 so I believe I used the correct method.

case-sensitive said:
I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
Click to expand...
Click to collapse
Tmk, Viewsonic has never supplied a 1.0.0 of their own (technically they never supplied a 1.0.1 either, but we managed to grab it). Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.

roebeet said:
Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.
Click to expand...
Click to collapse
(1) The sears folks actually checked! (2) 1.0.1 is less broken so I have less excuses to return it :-(
This is lame, I know...
Thanks for all your work!

I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.

+1 on this... gotta get rid of that recovery before I take it back.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse

Please can someone help me out with this.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

How Do I Install: Step by Step, The Recovery ROM
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You

toddsworld34685 said:
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You
Click to expand...
Click to collapse
The standard recovery (not clockworkmod) has two components. They can live on the internal /sdcard or on a microSD:
update.zip
/recovery/command
update.zip is pretty standard on Android, so I won't go into it - it's basically the package that actually updates the device.
/recovery/command is like a startup script - it tells recovery where the update.zip package is. This file gets erased after an update, I assume to avoid you from accidentally re-running it. It's a text file that will run /sdcard/update.zip, by default. If you need to change this to the microSD card, you need to edit the file so that "SDCARD" reads "SDCARD2", instead.

I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?

jfholijr said:
I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?
Click to expand...
Click to collapse
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.

roebeet said:
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.
Click to expand...
Click to collapse
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?

jfholijr said:
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?
Click to expand...
Click to collapse
I don't think so because you have to get to recovery to actually use it, which is cwm.

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

[Q] Reverting CWR to Stock Recovery for ICS updates?

I am running a 1839 US 0089 Thinkpad Tablet w/Clockwork Recovery and want to restore back to my stock recovery to allow my ICS upgrades to go off w/o a hitch.
Since Lenovo sucks in that it does incremental patches/updates vs a full updates.zip build, can we extract this from an update build and push to our devices?
i have not seen much info on this on the interwebz. i have several nandroid backups but of course those where taken using CWR, ie vicious circle..
if i find out any info, i'll post updates here too. :good:
TIA!
UPDATE: on ICS! see notes below and link to thread that helped me get there!
this post: http://forum.xda-developers.com/showthread.php?t=1741623
resolved all of my issues! power button replaced and the new button looks much more beefier (reinstalled my gobi card after getting back from lenovo).
they did reset software BUT they did not restore the stock recovery image. grr.. anywho, for anyone interested i made notes on what i did to finally get on ICS. i recommend doing a factory reset after updating to ics too. helped w/my inital lag issues.
(my notes from in that post )
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again.
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip

close but not there yet..
Noticed on this thread an uninstall actions given you backed up the install-recovery.sh (which of course i didn't, doh!)
http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1
I am running CWR 64gb version (US) and ran these commands via commandline and adb:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
the "cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh " action came back with a file does not exist but i continued but now seem to have NO recovery. I am able to boot into Honeycomb no probs and can do any adb task i need. i have since repushed the cwr recovery.
any thoughts my TPT geeks?

i have a totally new approach on this. i have a work TPT (same exact model and build) that is 100% stock. i plan to try to temp boot to CWR on it w/o installing it and capturing a nandroid of it.
once i have a full 100% stock 0089 US nandroid and can confirm it updates to ICS, i will post a link to it (if that is kosher w/xda, i'll have to re-read the forum rules again)

seamonkey420 said:
Noticed on this thread an uninstall actions given you backed up the install-recovery.sh (which of course i didn't, doh!)
http://forum.xda-developers.com/showpost.php?p=21962380&postcount=1
I am running CWR 64gb version (US) and ran these commands via commandline and adb:
adb shell
su
mount -o rw,remount /system
cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
the "cat /system/etc/install-recovery.sh.backup > /system/etc/install-recovery.sh " action came back with a file does not exist but i continued but now seem to have NO recovery. I am able to boot into Honeycomb no probs and can do any adb task i need. i have since repushed the cwr recovery.
any thoughts my TPT geeks?
Click to expand...
Click to collapse
If you download the 89 update from the lenovo download site, you can pull the files you need from it.
However, I just updated to ICS with CWR on my tablet and now have ICS (with stock recovery).

no luck here on my end. i have a nandroid backup from after applying 89 updates and made sure not to remove any items. however my power button my tpt just broke and i think i even have a working update.zip i resigned (removed the indigo checks) but now can't test.
guess i'm waiting for ICS until i get my tpt fixed up.
UPDATE:
called lenovo support about power button and also inquired on reloading software/if i get same motherboard in tablet (which i do). Lenovo will be reloading my tpts rom to the stock rom after button fixing. gotta send it in but i got it through work so i have the awesome ez-warranty so perhaps (if you can wait and don't mind losing all data) others that are having upgrades may be able to send in their tpts. i honestly wish lenovo would just create a full/stock ICS rom that us w/issues updating can push via adb. i'll see if i can get that nandroid made of a stock ICS USA TPT (1839) w/o having to put on cwr but temp unrooted once mine's back.

Cannot update to 4.4.2 via otg.

I am having problems installing the 4.4.2 update via OTA. I am on rooted 4.4 android KRT16S build.
I have rooted.
I have installed xposed framework.
I have installed twrp recovery.
OTA update stucks on twrp and nothing happens.
I have tried the following things :
1) Uninstalled xposed framework and tried installing 4.4.2
2) flashed the zip instead of OTA, twrp says failed.
3) enabled survival mode in superuser app.
4) I have also tried flashing KRT16S first which installs successfully on twrp and then 4.4.2 which again fails.
My point is starting this thread is to know exactly what to do when an OTA updates comes so that you can successfully update to the latest android version and also retain your data back.
Sent from my Nexus 7 using Tapatalk

OTAs are meant only for 100% stock.
The fact that they can occasionally be installed on a non-stock ROM (or when using a non-stock recovery) is purely happenstance - not evidence that anyone should have an expectation of a similar success on a device with arbitrary modifications.
It really is just that simple.

Which means, no matter what, I'll have to start from scratch again? Install 4.4 images with data wipe and then install 4.4.2 via OTA or flashable zip, followed by all customization and data restore by TB??
Only solution?
Sent from my Nexus 7 using Tapatalk

There is no need for a wipe, you can also install boot.img and system.img by fastboot and root your device again afterwards. In that case you will keep your data.
Sent from my Nexus 7 using xda app-developers app

neo1691 said:
Which means, no matter what, I'll have to start from scratch again? Install 4.4 images with data wipe and then install 4.4.2 via OTA or flashable zip, followed by all customization and data restore by TB??
Only solution?
Click to expand...
Click to collapse
There are possibly 8 or 10 different ways to go about this:
[A] Don't worry about minor OTA updates - recently they don't seem to be very compelling.
Dirty-restore only the system and boot images from a Nandroid backup of the near-factory ROM corresponding to the same base ROM you are using. You DO make nandroid backups before you start modifying things, don't you?
[C] Use a well-supported dev ROM and wait for the dev to update the ROM to the new release base. Then, just dirty-flash the ROM (if the dev says that is OK). (Obviously, dirty-flashing is not a good idea between ROMs that are wildly different in origin.)
[D]* Treat it like you would any other ROM install. Launcher configuration backup, TiBu Backup, Nandroid Backup, (custom recovery) "factory reset", new ROM install, (root kit install if needed), TiBu restore, Launcher configuration restore.
[E] Attempt OTA install, inspect failures in /cache/recovery/recovery.log, hand-revert files back to factory**. Rinse and repeat.
[F] Pick apart the OTA installer and repackage your own version of the OTA zip to remove the parts that cause failure - both the individual checks and the corresponding file patch operations.
[G] Find a "flashable stock" ROM that matches the same base version as your current ROM and dirty-flash it. Obviously this nukes any of your customizations. Also note that if that the dev did something like "zipalign" or odexing/deodexing of the stock ROM, it is unlikely that the OTA will succeed - even though the ROM is close to identical in function to the factory ROM, the files have been diddled and so the OTA will fail.
[H] If you think the near-stock mods you have made are "minor", you could attempt a "dirty flash" of just the "system.img" and "boot.img" files from the factory images. This would mean avoiding the use of "fastboot erase" of anything and attempting a "fastboot -w update my-custom-image-nakasi-XXXX.zip" where your custom .zip file only has the boot.img and system.img files in it (remove recovery.img, userdata.img from the .zip archive and also check the "android-info.txt" file to see that it is consistent). I have not personally tried this; if you are going to try it, I would back up your entire device as a safety precaution.
* The Google factory image install instructions show a complete wipe of the userdata partition; this is fundamentally different than most ROM installs (potentially requiring hours of waiting on backup/restores of the "sdcard" area).
** Obviously, you need a source of factory original files. Yet another reason to make nandroid backups before beginning ANY customizations. You can dig them out of nandroid backups - for instance, TWRP ".win" files are just tarballs. Or get familiar with simg2img (or here), loopback mounts, and so forth. You can find older versions of Google factory images on oldblue910's site http://www.randomphantasmagoria.com/
OTA Installation Notes:
[size=+1]1 - OTA installation is a PATCHING process.[/size]
[size=+1]2 - OTA preliminary checks are STOP-ON-FIRST-FAIL.[/size]
[size=+1]3 - OTA installs are ALL OR NOTHING.[/size]
1) The patching process for any individual file that will be updated is like this:
[prior factory file] + [OTA patch file] ===>>> [replacement file]
From the above diagram, it is apparent that "replacement file" needs both the original (factory) file plus the OTA-delivered patching file. The patching process cannot succeed unless an exact version of the original file - down to the very last byte - is present on on the device and in it's original location. The reason things are done this way is that the patch (.p) files are typically much smaller than the originals - so it saves the carriers bandwidth to roll out updates this way to lots of customers. The OTAs do not contain replacement files! They only contain patching (.p) files! Even "blob" files such as boot images are updated this way (so, generally, having a custom kernel will also cause an OTA fail).
2 & 3) The OTAs are quite conservative in their checking; they don't do something like this:
check file1... patch file1... check file2... patch file2... ...
but rather do this:
check file1... check file2... ... check fileN... patch file1... patch file2... ... patch fileN
If any of the checks fail, the process stops immediately without running any further checks This is a good thing - if it didn't happen this way, the OTA could get partially through and then fail - and then it would be impossible to repeat the OTA because all the successfully patched files would no longer be the original versions; and you would have a ROM in a screwed up (inconsistent) state.
So, in light of those above observations, it is apparent that:
- usually it is safe to attempt an OTA install on a modified ROM. If any file (to be modified) is missing or altered, a preliminary file check (SHA-1 hash computation) will fail and nothing will be modified. It is a good thing that the OTA install process is conservative this way.
- this explains why sometimes OTAs succeed on lightly modified stock ROMs: it just happens that whatever files the device owner/user fooled with are not in the group of files to be patched by the OTA. But that's no guarantee for the next OTA that comes down the pike, nor the one after that....
- if there are several file checks that are going to fail as a result of user modification, when the OTA runs, you will only be shown the error for the first file that fails - instead of a list of all files which are screwed up. That means that if you thought you were going to hand-patch things, you might have to iterate the process (OTA-fail... hand-patch... OTA-fail... hand-patch...) several times. If you were going to go down that road, the amount of effort needed to get things back to an OTA-friendly state might be quite significant. The only alternative to avoiding this is to inspect the "updater-script" that the OTA uses, and manually go through every file mentioned in the OTA and compute the SHA1 hashes yourself (using the program "sha1sum"). At least then you would know ahead of time which files/blobs are going to cause a failure.
- Note that the the SHA-1 checksums require that the files be identical to the factory originals down to the very last bit and byte. If you used a "flashable factory image" where the dev decided to do something like "zipalign" the .apk files, or add or remove .odex files, an OTA isn't going to work correctly. The files don't just need to be identical in function, they need to be identical down to the last bit and byte.
So now you can see why you observe lazy rooters perpetually returning to this forum asking, "can anybody get me a copy of file such-and-such from version XYZ of the stock ROM?". They are trying to hand-revert their existing ROM so that an OTA will succeed. And the fact that they are asking that question means that they failed to make a (nandroid) backup of their near-factory ROM. If they had done that, they would have the file(s) in question, and -morover- they would also have the option of running a TiBu backup & nandroid backup, restoring the original (factory/near-factory) ROM, taking the OTA, repairing root, and restoring TiBu backups... and then re-applying their customizations. But failing to take a nandroid backup means that they have NEITHER
Well, hand-reverting a ROM so an OTA will succeed may not be "starting from scratch", but it could be quite a bit of effort, yes? You have to undo things by hand to get back to "close enough" to factory state so that you can get the OTA to work. And usually the OTA stomps on permissions of /system/{x}bin/su so that re-rooting is necessary (or else you involve yourself with some dumb "root saver app" ahead of time). And then re-apply the customizations that intersected the OTA causing its' failure(s). All of that takes time. Less time than biting the bullet and just making backups? Hard to say. But one approach paints you into a corner, and the other provides maximum repair/restore flexibility.
I get it that backups take time, and performing TiBu backup/restores takes time too. And if you don't use a launcher that allows configuration saves/restores, even more time wasted there re-configuring things to "the way they were". But really, there's no excuse for not making Nandroid backups - and copying them off the tablet for safe keeping. You can always delete them later if you don't use them.
whew. i'm done.

bftb0 said:
There are possibly 8 or 10 different ways to go about this:
Dirty-restore only the system and boot images from a Nandroid backup of the near-factory ROM corresponding to the same base ROM you are using. You DO make nandroid backups before you start modifying things, don't you?
[/0QUOTE]
Thanks for the awesome reply. I appreciate the time you spent in giving me such a concise and precise reply to my question.
So I have the nandroid backup ->
1) I will flash 4.4, with full wipe and update to 4.4.2
2) Flash twrp and root.
3) Restore my data from my old nandroid backup.
Click to expand...
Click to collapse

neo1691 said:
So I have the nandroid backup ->
1) I will flash 4.4, with full wipe and update to 4.4.2
2) Flash twrp and root.
3) Restore my data from my old nandroid backup.
Click to expand...
Click to collapse
Hmmm. By that do you mean a nandroid restore of /data only on top of a fresh (full wipe) install and OTA update? That's a bit unusual - if any changes occurred in the total count or naming of pre-installed system .apks, that could lead to UID mismatch problems. Also, sometimes OTAs do removal/cleanup of things in /data ... you ought to look in the updater-script (OTA .zip file META-INF/com/google/android/updater-script) to see if any of that is going on. That's why both AnDiSa and I suggested methods that leave the data in place during the OTA update.
I guess what I am saying is that what you are proposing *might* succeed but it's a little bit nonstandard. (It prevents the OTA process from cleaning anything up in /data. Admittedly, that's a little unusual, but I think I have observed it in the past.)
Whatever you do, take a full Nandroid of where you are now; if things get screwed up you can always go back to your current setup and try a different approach.

Thanks a lot for all your invaluable inputs. Too much for me to work on now. I'll report what happens.
Sent from my Nexus 7 using Tapatalk

I am ready to do a dirty wipe. But I am not able to find the boot.img and system.img in the zip of KRT16O.
It is the 4.4 base.
It has a folder called patch which contains boot.img.p , but no system.img

There should be Bootloader.IMG and another tgz. If you extract this tgz you will find boot.img, system.img, data.img.
Be careful to not mix up bootloader.img and boot.img.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 04:59 PM ---------- Previous post was at 04:58 PM ----------
... one question: are you sure you have the Google Factory Image?
Sent from my Nexus 7 using xda app-developers app

You were right, I was looking in the wrong file,
So extracted the real factory image and there was another zip in that which contained the respective files!! Lets see what I can do now!

Solved!!
Okay. I am now on 4.4.2!! Cheers!!
But dirty flashing didn't worked for me!
I flashed the system.img and boot.img from 4.4 base, and then tried flashing 4.4.1. It worked. But flashing 4.4.2 zip failed just like before.
So after that I took a backup of my sd card and did a full flash of 4.4 base. (KRTO) and then updated to 4.4.2>flashed twrp>waited for OTA>installed OTA from twrp. Worked like a charm.
Now the challenge lies in restoring the data back completely. I have a nandroid backup and TiBu. Guess I will be usin TiBu!!
This thread will be an excellent guide for people facing me problem update OTA over rooted stock rom!
Thanks everyone for their help and support!! Cheers

@neo1691
happy holidays indeed!
The nice thing about nandroids is that you can jump back and forth between two ROMs if necessary.
For instance, suppose you forgot to do TiBu in the prior ROM - no problem! Just make a nandroid of the current (new) ROM, restore the prior Nandroid, do the TiBu backup, restore the (new) ROM nandroid, and then perform the TiBu restores. Easy-peasy.
Backups are awesome. Make 'em often - you can always toss them after a while if you aren't going to use them.

Cheers.. Thanks again everyone
Sent from my Nexus 7 using Tapatalk

How do I update to Android 7.0 on the Axon 7 (USA Model) with TWRP Recovery installed

I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue

EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29

Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.

lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.

First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.

WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.

Only use ota if you don't want twrp/root anymore.

Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2