Related
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.
I know that Acer pulled today's update, but will it be possible to switch when it is released again?
Leaked 3.1 to official 3.1
Yes it is, just a little confusing though. You have to know which region your tablet is from http://secure3.tx.acer.com/FindSystem/FindSystem.aspx?title=Information About Your System. And then go about flashing a couple of ROMs to get you ready for the update. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1155664
I am a total noob and wasted my whole day yesterday trying to figure this out. In the end texonex helped me out. Starting with the leaked 3.1 update here's what I did (courtesy texonex):
1. Root the device (http://forum.xda-developers.com/showthread.php?t=1138228). Download Acer Recovery Installer from the market, and from there install the clockwork recovery image. Choose no for a backup of the current recovery.
2. Download the backup file for 1.104.02 here, thanks to camelot1972
dl.dropbox.com/u/34113636/2011-06-24.12.20.13.zip, I guess you could also use the file from here: http://forum.xda-developers.com/showthread.php?t=1113878. This is for the US version.
If your tablet is from another region you would have to find the appropriate "default" version number in the how-to (what firmware is right for my country).
3. Extract the contents from the zip file and put them in the backup folder for clockwork mod on your SD card (take your SD card out of the tablet and connect directly for all the steps), if you do not see the backup folder, I suppose you can make one,e.g. [micro sd]\clockworkmod\backup\2011-06-25.22.14.07. I guess this exact string will still show up in clockwork recovery. I made a backup of the leaked 3.1 and that gave me the folder, and I just replaced the files. The date part is obvious in the name however I wouldn't venture a guess what are the other digits in the folder name.
If you downloaded the file from [OTA] Full Package and Update page, you'll need first to decrypt the file using the decrypter and then extract the contents of the decrypted file. One of the extracted files is update.zip which goes on to the SD card no subfolder in this case.
4. Restore the firmware using CMW using full restore for the US version, or update from the sd card zip if using a full package zip file.
At this point I think you need to save the recovery image for the non-US versions. Follow the instructions in the how-to or just use acer recovery installer to flash the clockword recovery again and this time choose yes to backup the current image.
5. Download 1.104.02 to 1.141.07 update and flash it with CMW.
Or the appropriate latest update file from your region(highest version number).
6. Flash recovery image to 1.141.07, this is option 4 in Acer recovery installer.
For non-us versions restore the recovery image, unroot and restore factory defaults.
7. I stopped here and now am waiting for the OTA. According to the how-to, you roll back to the full defualt package by using the standard ACER recovery (Power + -Vol) after copying the zip file on to the SD card, delete the zip file copied before.
8. Go to settings and trigger update manually. OTA will prompt you the new 3.1 update. I suppose you do not need to unroot.
You can also install the stock ROM from here:
http://forum.xda-developers.com/showthread.php?t=1159443
Thanks to Bec07 (how-to), vache (stock roms) and sc2k (un-rooting) for their contributions or I would have been totally lost in trying to downgrade my tablet from the leaked 3.1. Hope this is helpful, and goes smoothly because if it does not I wouldn't have clue how to fix it.
Sorry for this off-topic post, but you said that acer pulled the update: And I still have it (haven't updated and cant anyway). Is this not right?
What I meant was its not being pushed to more users for now.
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
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Recovery stock and SD card seem to be the most reliable method.
Did you check the md5 of the zip? Also update.zip to put on root of the SD card should be the final zip, not the zip that contains another zip.
Also when booting in Android, I assume your SD is recognized, isn't it?
If so, instead of going to recovery then update from SD card, you can try to update from inside Android, from Phone settings, then Update item.
The phone should indicate the current version and the version to be updated to. Then follow the phone indication to update.
Nope, i dont checked MD5. But shouldn't be the problen. I tried many different update files, always same error.
Yes, after booting the SD card is connected and i could use it. Just the recovery mode cant mount the card.
Also the updater recognize my update. But he just boot in the recovery mode and try to update -> Same error: "couldn't mount /sdcard"
Edit 1:
But i can check the MD5 files if necessary. I just need the "correct" MD5 value to compare.
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
t4ggno said:
Hello,
i bought my Axon this week from Amazon Warehouse.
My problem is, that im not able to update my ROM.
I tried OTA, Install over Recovery (SD-Card), Install over Recovery (ADB Sideload).
All methods failed..
OTA is downloading the update, rebooting and than crashing. Hard to tell why, because i dont see any error logs. Just the information "Update Failed".
Next method i tried was to install over SD-Card. I downloaded the Update from ZTE, moved to my SD and tried to update. But my Smartphone always tells me "Couldn't mount /sdcard".. I tried to Format it with extFAT and FAT32 but both failed.
The last method I tried was using the ADB Sideload. I tried it with the update file, and also with the STOCK-Rom from this site: https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547. But also i get an error message.. ADB tellst me "Total xfer 0.00x"...
Have i bougth a bricked Axon? Can I update somehow to the new version?
I have the option to send it back to Amazon, but it was 100€ cheaper, so i would love to fix the problem.
Kind regards,
t4ggno
Click to expand...
Click to collapse
Also, bricked means totally unusable, so no it isn't bricked lol
dnlilas said:
Just a guess:
Is your micro SD card size greater than or equal to 128 GB? Some version has this bug, size less than or equal to 64 GB should work better. To try if this is the case.
Click to expand...
Click to collapse
Its a 64 GB card Should i try a <= 32 GB card? Could be I have some lying around. Just to be sure its not a special case.
I will test it tomorrow if i found one
Choose an username... said:
Why are you using an SD card though? Put it in the root of the internal storage and it will surely pop up, then try again from Updates, not the recovery (and get the SD off the phone to avoid the phone from detecting the zip there)
Otherwise root and get TWRP and flash Tron1's stuff
---------- Post added at 11:30 PM ---------- Previous post was at 11:29 PM ----------
Also, bricked means totally unusable, so no it isn't bricked lol
Click to expand...
Click to collapse
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
t4ggno said:
Hm, last time it only recognize the update file on my SD card. I will try it tomorrow again and will post the result.
TWRP isnt a option, because i dont want to lose my warranty. Also i read that TWRP can be incompatible with Stock-ROM?!
Click to expand...
Click to collapse
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Choose an username... said:
I don't know where you read that, but the closest answer that I can give you is: if you don't install SuperSU, Magisk, or the dm-verity patch, TWRP will get replaced with the stock recovery and you'll have to flash it again (~2 minutes anyways). But it is in no way incompatible. Also you can relock and stuff, but yeah better keep the warranty at least until you're sure that your phone is good.
You unpacked the zip that you downloaded right? to get the update.zip inside? Or did you download it from raysteff's thread? It should work anyways
Another thing: What is your phone's model (G, U, chinese) and what is the update that you're trying to install? I guess it will fail if it is from another model, and if you're trying to jump fron a very old MM build to a very new N build it will probably fail too. Keep that in mind.
Click to expand...
Click to collapse
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I tried the package A2017G-MM-B11 and A2017G-N-B01 from the link I posted, also i tried the oficiell patch files from the axon website (B10 and Nougat)
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
I have a A2017G (that information i found on the back of my phone).
My phone overview tells me:
Modelnumber: ZTE A201G
Build-Number: ZTE A2017GV1.0.0B08
Android-Version: 6.0.1
Security-Patch: 1. December 2016
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
karlkarloff said:
Don't know if it applies to your situation, but when the OTA for 7.x came out, there was a bug that would not allow the update to be applied if there was an SD card installed. I know I had to pull my card to get the update to take. Might try running the OTA without the card installed and see if it works.
Click to expand...
Click to collapse
I tried it, but doesn't work :/
The update stops at 33% with the error message "Package Mismatch".
t4ggno said:
I didnt unpacked the folder. A recovery normally installs zip files?! The zip file isn't packed twice. The zip contains the files directly.
I can try to install the B09. Probably this patch is required to go to version 10 (and than to nougat)?
Click to expand...
Click to collapse
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Choose an username... said:
No, B09 was a patch only for Spain.
The zip you download from the ZTE website has a bunch of numbers as name and has an update.zip inside and a PDF or sth like that. The one you have to flash is the update.zip inside, just sayin'...
If you download the zips from raysteff's thread they are already unpacked.
Try installing an older zip, like B03, then B10
Click to expand...
Click to collapse
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
t4ggno said:
The big problem still exists -> I cant mount my SD card in recovery mode, so I cant install any patch.
I really want to try B03 as you suggested, but i am unable to install it.
I will search another SD card an try to use it. Probably my SD card has some problems.
Edit: I download my files from these side: http://www.ztemobile.de/support/downloads/?product_id=2100
They dont contain a update.zip. Only many .dat, .bin, .img and .mbn files.
Click to expand...
Click to collapse
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Choose an username... said:
But install it from the internal storage and with thr Updates option on Android itself... You need to put it in the root of the internal storage or it most likely won't find the zip
Click to expand...
Click to collapse
Thanks! That worked very well. I did a factory reset and moved the update file directly to the root of my internal storage. After that the updater detected my update and I could install the Patch B011. After that i was able to update to Nougat trough OTA. No errors, every worked fine.
otaconremo said:
First, what is the version of your device?
I'm guessing you are using a chinese device with modified rom. Those units can't install updates unless you first restore to original chinese rom.
Click to expand...
Click to collapse
it seems that I got this one with modified rom. is there anyway to get it back to the official chinese rom?
Long story short; I wiped system and everything on this device, so all I really have on it working now is TWRP. The official FullOTA updates fail in TWRP, erecovery fails, and recovery in hisuite fails. I assume the last two will fail because of the third party recovery. So I guess I'm wondering if anyone can point me in the direction of the official recovery that I can fastboot flash, or any other way to reload the ROM?
Full story; I got this new tablet last week, and I unlocked, installed TWRP, and rooted successfully. Then I broke google services with a dodgy gapps install that I didn't need, couldnt figure out how to unflash it, and wiped everything like an idiot.
Thanks if anyone can help.
Update; I guess the root of the problem is that I'm unable to mount /data? Any actions I take in TWRP give me the error "Failed to mount '/data'", including if I do a wipe data or try to change the file system. I've used "Huawei Update Extractor" to see if there is a data.img, but it looks like no.
Update 2: Still not sure what this was all about, but I extracted system.img from "Huawei Update Extractor" and fastboot flashed that, and it looks like everything is working again. Haven't checked TWRP to see if it still gives errors on the data partition, but I'm at least in the OS and google play services are working.
Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Sent from my BTV-DL09 using Tapatalk
30adi said:
Download latest firmware for your device from Huawei server and extract it. Make a new folder on external sdcard, named dload. Copy extracted file (update.app) in this folder. Power off device and turn it on using 3 button method: volume up + volume down + power - old all 3 buttons simultaneously.
It will start the update/flash process. It will install factory firmware on your device.
When you download Firmware, in the archive you will find these steps (PDF file).
Next time you can try this
Click to expand...
Click to collapse
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.
nicolap8 said:
Wrong. He installed TWRP so there is not a functional recovery.
The right thing is to extract the Recovery from the Update.app and flash it, then use the dload method.
Click to expand...
Click to collapse
Actually, I did try that, but I put stock recovery back on and and tried the dload method, it still failed int he same way as with TWRP installed.
What ended up working was extracting system.img from the update and fastboot flashing it. Not very intuitive. I am still getting "Failed to mount '/data'" errors in TWRP now, but haven't looked much into it yet. That is weird, I guess if everything is working it is more a problem with TWRP, because if everything is running and booting /data should be fine.