Related
Im having the worst time in the world trying to get this froyo for my evo. I have it in the root of the sd card, "O:" and removed known file extensions just to make sure its update.zip and not update.zip.zip.
everything is what it should be according to every post ive looked at. Yet no matter what I do, i still get signature verification failed, installation aborted.
Any ideas?!
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
This is how it's done.
Follow the step by step directions I copied from androidpolice below. When you get to step 8, you will most likely see the red triangle with exclamation point. Don't worry. Just hold the up volume button and press the power key. This will activate the menu where you will see "apply update.zip". Proceed with step 8. It takes care of the rest.
We’ve provided some simple instructions for installing the update:
1. Download the update file and rename it to update.zip.
Note #1: DO NOT UNZIP THIS FILE
Note #2: Make sure you didn’t rename this to update.zip.zip by accident, if your Windows is configured to not show file extensions.
2. Place in the root of your SD card (connect via USB and mount as a drive, transfer via bluetooth, download directly on the phone – pick your poison).
3. Reboot into recovery mode (hold the Volume Up button while your phone is booting).
4. You will be presented with the boot loader. The Volume Up/Down buttons navigate the menu, and the Power button selects.
Note: you may see the red exclamation (!) point at this stage. Try mashing the up/down/power buttons and wait for 10-15 seconds. The recovery should eventually come up.
5. Select Bootloader.
6. Scroll down to Recovery and select it.
7. The phone will reboot again, this time into recovery.
8. Select “apply update.zip” or “install from .zip” (depending on your recovery image).
9. The installation process will take 15-20 minutes and a few reboots.
10. Enjoy!
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
I think I had the same issue with the file after I renamed it update.zip (it was hidden and already there). I renamed it but did not help.
I would recommend deleting it from the card and downloading a fresh copy of the update. Copy it to the SD card and try again.
This is the source I used and it worked.
herehttp://www.megaupload.com/?d=LCONCXF1
xcodesterox said:
i can get to that point just fine, its the install that fails due to signature verification failure, i have followed all the steps to prevent any mishaps, but still cannot get past it.
Click to expand...
Click to collapse
You are probably going to need to download a different file, as a lot of the mirrors here are corrupted. If your file size is 70 something, that is corrupt. The correct file size is 80 something (sorry, I'm on my phone).
Look for a different mirror to download from.
Did everything and nothing, not even the (!) thing, everytime I scroll down to recovery it just takes me back to the main menu (bootloader) and nothing seems to work, am I doing something wrong?
yeah ive only downloaded the 84mb ones, i even had the original from HTC with no results. my evo refuses to evolve lol
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
fsuwade said:
I could the same thing last night. But what I had to do was to update to 1.47 then go in and update it another time name the file update and that is it. And it should work.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Im Hoping thats what the case is, I'm installing 1.47 now, if this doesnt work then im at a loss
well, no luck. i guess i have to wait till the 3rd
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Kornsaq said:
I had to remove all the excess files from my sd card root for it to finally work correctly. I think the only thing i had left on my sd card root were folders and the froyo renamed to update.zip
Click to expand...
Click to collapse
I have many folders and I cleaned up the excess files, still though, no result.
thanks for the tip though, i got really excited to try that,.
jahnile said:
If you are rooted why not boot into recovery and install update from zip. Note that this option will un-root your phone in the process. There are also post on the forum with the stock Rom for non rooted phones, if you are not rooted. You can try using that file rather than the one you got. This may get u on 2.2 b4 u know it.
http://WWW.rootznculture.com
Click to expand...
Click to collapse
Im rooted, i tried being rooted, and unrooted. Ive been going at it since it released when i was at the movies.
thanks for the tip
Same problem
Hey xcodesterox.
I had the exact same issue and even download the linked file from ckombo.
I was finally able to get it to work.
What was happening for me was, I would download the file and my Mac is set to unzip a downloaded file from Safari, I would then just zip it myself after this. This was not working so I switched to Firefox, where I do not have it set to autoextract, and therefore I did not have to re-zip. THAT time it worked.
I hope you had the same issue.
Ok so you said right now you are in rooted. You should try removing all zip files that are current on the root of your SD card. U can back it up to your pc. Then use the file/ method found in this post. http://forum.xda-developers.com/showthread.php?t=740319
http://WWW.rootznculture.com
1:42am day two and im finally enjoying my fozen yogurt.
if anyone cares, i had to use the rooted version of this update, so its still a mystery as to why it wouldnt install. thanks for everything
I had some problems workign so i did this
1.did factory reset(backup date)
2.did the ruu 1.47 update
3.copy zip file to sd (drag and drop in windows, just dont drop into esisting file and dont unzip)
4.name the file update windows will add the .zip checkby right clicking on the file going to preferances then details tab (in win7 anyway)
5.power down phone
6.reboor by holding vol down and power wait for it to read you card
7.might get a cant open cache error, didnt prevent my update
8. using vol keys nav down to recovery, hit power button to select
9.vol down to highlight the update.zip file and powr to select
i was running 1.17 firmware so i had to update from that to 1.32 then 32-47 so check your version and update accourding, is it worth it? my bat life does seem a lil better flash is smother than the flash update i ran in 2.1, and browsign does seem smother, also landscape mode works in both left and right!
Where did you found this rooted version? I have the same problem...
There still seem to be a few people with problems so I thought I'd try to collect the steps and add a bit more info:
Notes
- So far this is only confirmed to work on full stock 2.2. For the leaked 2.3.3 you'll need to downgrade first; see this thread: http://forum.xda-developers.com/showthread.php?t=1180733&highlight=temp+root+downgrade
- The only confirmed root so far requires s-off BEFORE you follow this guide: http://forum.xda-developers.com/showthread.php?t=1206930
- I have had no reports of anyone doing this with anything other than 100% stock recovery, hboot, etc. Please let me know if you do try and what happens; I'll update this post.
- Following this procedure will not wipe your apps or your data.
Steps
1. Download http://android.clients.google.com/p...MOUS_2.15.531.3-1.22.531.8_release_197463.zip and rename to update.zip. Turn off 'Hide extensions for known file types' and make sure it's not update.zip.zip!
2. To verify your download didn't get corrupted, check its md5sum. It should match 3c7b0c2253f72f86b06d2c85b2c8c294 (you can get a dos tool to do this here: http://etree.org/md5com.html. Run cmd.exe and type md5sum.exe update.zip from a folder that contains both files) If your result doesn't match, download again.
3. Place update.zip on the root of your SD card, not in any folders.
4. Power down your phone.
5. Press and hold both VOLUME DOWN and POWER until you get a menu
6. You may not be able to navigate the menu yet. Wait for 10-15 seconds until it says it's checking some files, then automatically returns to the menu. Now you can use VOLUME UP/DOWN to choose menu options.
7. Choose Recovery from the menu by highlighting with VOLUME UP/DOWN and pressing POWER.
8. Wait until you get a picture of a phone with a red triangle and !
9. Press & hold VOLUME UP, wait one second, then also press POWER. You should get a menu with blue text.
10. You will see "E:Can't open /cache/recovery/command" at the bottom of the screen. This is OK!
11. Again with VOLUME UP/DOWN and POWER, select "Apply sdcard:update.zip"
12. From this point, just wait until it tells you to reboot and choose that menu option. If you get any errors here, consult the troubleshooting below.
13. There are several more automatic reboots and wait screens to go. Be patient!
Troubleshooting
- "E:failed to open /sdcard/update.zip (no such filler or directory)" - your file isn't named update.zip! Reboot your phone and use Astro or another file manager to make sure you've got the name right.
- "E:failed to seek in /sdcard/update.zip (Invalid argument)" - your download probably got corrupted! Check the md5sum again, redownload, and try again!
- "assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"" - you probably don't have the latest 2.2 that this update is designed to replace. You might be on 2.3.3 or possibly the original pre-wifi-calling 2.2. To fix this, downgrade from 2.3.3 or wait for the OTA to get the newer 2.2.
Has anyone noticed any bugs in the new OTA? Waiting for bug reports before I flash.
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Thank you for the link I'm updating my wife's phone tonight
Sent from my LG-P999 using Tapatalk
Cimer said:
Well I would wait until someone makes a rooted version of this, I don't think you want to loose root over an update that is kind of outdated compared to Cyanogenmod.
Click to expand...
Click to collapse
I don't mind losing root. I'm running stock 2.2 with s-off and clockworkmod. I just want the update to work.
The instructions above don't work for me. When I attempt an update in clockworkmod I get an error "(Status 7) installation aborted", something like that.
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Cimer said:
That's because it's not meant for clockworkmod yet. You can follow his instructions, loose root and be updated, or just wait a little until someone makes a rooted version and just flash it via clockworkmod.
Click to expand...
Click to collapse
Following his instructions, I get to clockworkmod recovery after step 7. I then choose update from .zip and get an error message.
attempted this with Indian HTC Desire Z and official htc update from another user with Canadian HTC Desire Z.
Getting the error: "Invalid Operation"
Why do I have an Indian HTC Desire Z ? Amazon told me it was American. I didn't know better.
How did I get the Canadian update ? A friend kept a copy of the file when he was updating his.
Ideas ?
I get the following output:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Copying fotaBoot to /data/system for customize reload...
Verifying current system...
assert failed:apply_patch_check("/system/bin/dnsmasq", "0ca7c8c9c5d267665622497df4c67dec65166adb", "1d717ab5c2bfc75d16bf6a9ec7936158cdc65aef")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Received the following error:
assertfailed: file_getprop("/system/build.prop", "ro.build.fingerprint") == tmobile/htc_vision/vision/vision:2.2/FRF91/277427:user/release-keys"
and a bunch of other gobbletygook...ending with
E: Error in /sdcard/update.zip
(status 7)
Installation aborted
OP needs to add "Status 7" error to OP.
You cant use clockworkmod recovery to update using the official OTA update.zip.
no - i don't have clockwork or any mods at all.. I think I screwed up the downgrade slightly, anyhow, what happened was shortly after posting this i got an OTA update that updated my system - but it didn't update it to 2.3.4 just to a newer 2.2 evidently. THEN I was able to use the update file and force it so now I have 2.3.4! (albeit still without my apps..)
wireless hot spot
can anyone tell me if wireless hotspot still works with this update?
All i know is some devs need to rip this stuff apart and get to cooking up some CM type features into it and it's my new daily driver
leech1980 said:
Will this work with clockworkmod recovery?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
It looks like you can't use a custom recovery to apply this update. It likely tries to verify the recovery image. You could open the update up and remove the file version verification, and various other things to prevent it from taking away your S-Off and SuperCID. You would then HAVE to apply it with a custom recovery with signature verification off.
A quick look in the firmware.zip portion of the update and you find this in an info file:
modelid: PC1010000
cidnum: T-MOB010
mainver: 2.15.531.3
hbootpreupdate:12
As well as hboot_7230_Vision_GEP_0.82.0008_110413.nb0
I don't know if that info file actually does anything, but I would still start with changing cidnum to 11111111.
The real meat of what is going on is in the Meta-inf folder, that is what handles copy files and performing updates. You can simply remove things you don't want updated. If modified correctly, you could then apply a superuser su.zip before rebooting and keep root with your update.
Unfortunately, I don't know enough to trust my own handywork. Maybe some people more familiar with the innards of Anroid could help out the Vision/G2 community?
The more I look at it, the more it seems like you could just delete the recovery.img (or replace it with clockworkrecovery) from the firmware.zip and delete the assert(apply_patch_check crap from the updater-script in META-INF\com\google\android and apply the modified update.zip with clockworkrecovery (signature verification off).
You could then apply an su.zip before rebooting and you should come back up with custom recovery at least, if not root also.
No one do this just yet. Surely someone from the N1 community can guide us as to how to chop up the update.zip
Installed successfully on my stock 2.2 G2. Thanks! Was getting tired of constantly checking my phone to see if I had gotten the OTA update yet!
Well just ran this on my roomie's stock phone. Fingers crossed.........
As soon as I posted this the phone booted up. So far so good. Thanks, I was beginning to think this phone was never going to get GB.
Drthunderer said:
can anyone tell me if wireless hotspot still works with this update?
Click to expand...
Click to collapse
WiFi hotspot is working fine for me after updating.
I just recently performed an "Over the air" update on my Motorola Atrix in hopes of upgrading to 2.3.
The 200mb file downloaded so I selected "install".
I walked away and then came back to the following error screen:
www [DOT] hardreset.eu/images/nexus_one_android_hard_reset_3 [DOT] jpg
Upon resetting the handset it appears that not only did I experience an error during the update, but now I also will have to re-download the entire file.
Can anyone please advise if there is anyway to manually install 2.3? Surely it's still on the phone somewhere.
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
Verifying current system...
assert failed: apply_patch_check("/system/app/MagicSmokeWallpapers.apk", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "9870b02dba63f6f0047e4d104329cf4c1d0a48a5", "94389fda652df9e0eaaddf25bbbac0b0dececa1c")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted...
Click to expand...
Click to collapse
I hope someone can shed some light on this!
humanix said:
**Update:**
I tried downloading the file again but this time backed it up just incase.
It failed a second time so I tried renaming it and doing a manual update.
I received the following errors:
I hope someone can shed some light on this!
Click to expand...
Click to collapse
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
the key question is, have you done any modding to your phone? webtop hack, rooting, anything that would change system files?
geekygrl said:
Is the the Telstra over the air update? (as I just did mine yesterday)
It basically means that the update is doing a check to make sure certain files are still in place - in other words somehow or someone has deleted that .apk (is your phone rooted?!) and since the update cannot find it it aborts the process.
I ended up just re-flashing with RSDLite back to stock as I had exactly the same drama (I had removed helpcentre.apk), downloaded the update yet again (third time lucky...) and it worked perfectly.
I also did a full factory reset as well as formatted my internal SD card prior to updating.
Hope this helps
Click to expand...
Click to collapse
Yes, it's a rooted Telstra Atrix.
I did a re-flash using RSDlite and it did the trick. Thanks!
Hey everyone,
I'm having trouble getting my Nexus 7 to update to 4.2.2. My device is rooted, I recently performed a factory reset.
The update has never appeared in my "System updates" menu, so I looked around and saw that if you force stop "Google Services Framework" and clear its data, the update will appear in "System updates."
It did, but when it finishes downloading, it says "Verification failed."
I tried another factory reset, and I had to again force stop and clear data on "Google Services Framework" to get the update to appear, but again it downloads and say "Verification failed."
I'm stumped now. Do I have to unroot and reroot? Do I have to keep waiting for this update? Do anything with the bootloader? (I really hope not...)
Thanks everyone!
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
Is flashing the stock 4.2.1 rom the same thing as doing a factory reset to 4.2.1?
If it isn't, would flashing the 4.2.1 rom wipe my tablet?
Leonhan said:
If some files in your system got changed for whatever reason, then you wont be able to update. You can flash the 4.2.1 stock rom and try ota update again.
Click to expand...
Click to collapse
If he is trying to do an OTA to 4.2.2, would it not be more straightforward to just flash the 4.2.2 factory image? The OP has already done a factory reset, so it doesn't look like he/she is particularly attached to his current setup.
Also - the language he used was vague - it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
But it doesn't matter - newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images. It's just too detailed a process to describe compactly.
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC. Yes, all of it. You can throw it away later if you find you didn't need it. But if you follow the instructions for the Google (factory) images install, everything gets wiped off of /data including your pseudo - SD card.
At a minimum, that will allow you to follow the SBS instructions for installing the 4.2.2 factory images, or - you can simply install a 4.2.2 Stock ROM from over in the dev forum.
Whatever you do, start getting in the habit of making backups - and at least occasionally also getting copies of those off of the tablet.
Oh boy, lot of information to digest here....and a lot of questions
it sort of sounded like the OP observed "verification failed" in the main OS rather than in the recovery. Not sure.
Click to expand...
Click to collapse
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
newbs should not be trying to use OTAs on modified /system images or tabs with altered boot images.
Click to expand...
Click to collapse
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
@Horadrius
Before you do anything further, you should back up everything on the "SD Card" to your PC.
Click to expand...
Click to collapse
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Horadrius said:
Oh boy, lot of information to digest here....and a lot of questions
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
So, no updating the device from System Menu because I'm rooted/unlocked bootloader? I'll have to flash everything as it comes out?
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
Sounds like your download is bad if it fails at this stage. I believe it is saying the checksum of the download file doesn't match whatever is downloaded.
PS. not related to N7, why XDA use the re-captcha which I need to refresh several times to get something I can read
Horadrius said:
Yes, it was the main OS - Settings -> About Tablet -> System Update.
After force stopping Google Services Framework, the update showed up there, and when the download bar reached 100%, it said "verification failed." I did a factory reset, and now when I go to System Update it simply says that my system is up to date.
This makes me think I'm not "supposed" to have the update yet, and that it will arrive, eventually. Yes?
Click to expand...
Click to collapse
No. It means that for some strange reason, running a checksum program on the downloaded OTA file failed to produce the expected checksum. The most likely way this can happen is that the file is truncated - the download stopped short of the full file. Don't know why this is happening, but there you go. There could be other failure causes that are more rare, but it doesn't mean you are not "supposed" to have the OTA. It means that the download process is failing.
The *stock* recovery does a number of even more sophisticated checking than this; but it appears from your description that the recovery never even gets booted.
Horadrius said:
So, no updating the device from System Menu because I'm rooted/unlocked bootloader?
Click to expand...
Click to collapse
Yes and No. An unlocked bootloader causes no problems at all. ANY of the following CAN or WILL cause problems:
- attempting to run an OTA with a custom recovery installed instead of the stock recovery.
- having a modified boot partition (e.g. non-stock kernel, or slightly modified boot partition)
- having altered (or removed!) files in the /system partition that are targeted for patching.
- permissions changes performed by the installer script can cause root functionality to disappear
Horadrius said:
I'll have to flash everything as it comes out?
Click to expand...
Click to collapse
Not sure what you are asking here, but the basic answer is that if you stay on stock you can certainly apply OTAs easily. If you start altering things, you might or might not be able to apply an OTA; there are simply no guarantees.
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD. While it is possible that an OTA could succeed, it is unreasonable to have the expectation that it will do so.[/size]
Horadrius said:
Would Titanium Backup held in this regard? Or simply copy/paste the sdcard folder to my PC?
Click to expand...
Click to collapse
I presume you are talking about the future here, as you said that you already did a factory reset at least twice. If you have subsequently added stuff back in, then I suppose you might be talking about the present tense.
But, yes - either TiBu or the Carbon app can be used along with a strategy where you simply back up the apps & data you are interested in, (plus any "flashable zips" that you used to customize your device in the first place), and you simply start from scratch with a factory install followed by re-rooting, and then restore your apps & data (using TiBu or Carbon).
One other thing you can do which is EASY is this: simply wait until a developer/ROM cook publishes a "Stock" flashable ROM based on the release that the OTA is upgrading to. Don't worry about the OTA, just wait a little bit. (These ROMs are already out for the WiFi-only model, BTW).
1) Take a backup as the first thing you do. It's easy and gives you some insurance.
2) Don't wipe (no "factory reset") - just install the Stock ROM over the top of your existing ROM.
that's it. If you were using a custom kernel, re-install it.
Horadrius said:
This whole process has been very frustrating. Is this the price you pay for rooting your device? Making simple system updates into a maze?
Click to expand...
Click to collapse
[size=+1]OTAs are meant for stock installations - including a stock recovery. PERIOD.[/size]
Interpret that as you desire. It is unreasonable for you to expect that you can diddle with your phone any way you please, and a patch install upgrade methodology will be robust in the faces of arbitrary changes on your part. You are the person creating the maze, not Google.
Moreover, it is your choice to take an upgrade - it's not mandatory. My guess is your tablet was quite pleasing to you before any OTAs started rolling out. Nobody is forcing you to do anything.
OK, one last thing. It is still possible that a manual OTA can succeed on your phone if it is lightly rooted - but there are no guarantees. The procedure does not require you to wait around until an OTA arrives on your phone, but it is not for the faint-hearted:
1) Download the appropriate Stock OTA File.
2) Re-install the stock recovery onto your tablet. You will have to dig it out of the Google full factory image for the version of the OS you are currently running. (available here)
Code:
fastboot flash recovery factory-4.2.1-recovery.img
3) Soft-boot into a custom recovery, e.g.
Code:
fastboot boot openrecovery-twrp-2.4.1.0-grouper.img
5) Using the command line and adb to communicate with the soft-booted recovery, create a recovery command file:
Code:
C:\myPCsux> adb push 6ece895ecb23.signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip /cache/update.zip
C:\myPCsux> adb shell
# cd /cache/recovery
# cat > command
--update_package=/cache/update.zip
^D # ( that is a Control-D character )
# sync
# reboot recovery
This will either succeed or fail. Based on your comments though, you might just want to overflash a Stock-derived ROM over the top of your existing ROM (a "no-wipe" install).
[ROM][Factory Image][4.2.2] Nakasi -::- Odex, Deodex, Rooted -::- teshxx (02/14/13) <-- NOTE for WiFi (nakasi/grouper) ONLY
good luck with your tab.
Someone once said "Rooting is a lifestyle". There's some truth to that; it eats up your time. Perhaps it is not for you.
Thanks, bftb0.
Looking through your list of reasons for why my OTA might not work, none of them applied to me.
I didn't install any custom recovery (didn't install Clockwork Mod recovery specifically to avoid dealing with flashing roms) or kernels or modify any partitions, nor to my knowledge changed any files in the /system section.
I think I'm going to give this update a week or so to pop up on my update menu before I start tinkering again.
Don't get me wrong - I enjoy this kind of tinkering, and all the perks of rooting, but my knowledge is extremely limited, which is what makes it frustrating trying to find information. The only thing I've done before this is install Cyanogen on my HP Touchpad.
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
chimpanzeexda said:
if you haven't done anything other than rooting(i.e. copying a file su to it), OTA would go through. Your problem is about the download process. It can go wrong for many reasons from the download is bad to what saved to the temp area(where the download is) is bad(rare but still possible).
Click to expand...
Click to collapse
That's all I've done, root and unlock bootloader. The download only showed up when I cleared data and force stopped the "Google Services Framework" process. I reboot the system, and check for the update and nothing is there.
well, sounds like you have to flash it manually using fastboot then.
That said, I myself have no intention of doing the update any time soon as I don't find any specific problem with 4.2.1 and there isn't any specific feature i want in 4.2.2
Horadrius said:
Anyway, do I need to install CWM recovery to flash (overflash?) that 4.2.2 rom you linked?
Click to expand...
Click to collapse
TL;DR Yes and No.
People that use toolkits seem to use hard-flashed installs of custom recoveries, as they don't really understand what goes on under the hood, even if the toolkit offers them a means to soft-boot any image the toolkit operator downloads. (I assume that the toolkits probably allow this; as I don't use them I don't know for sure.)
What I am saying is that the answer depends on your knowledge. So long as you have an unlocked bootloader, you can soft-boot any boot image you like - including custom recoveries.. (This also pre-supposes correctly-functioning device drivers, but that is a Windows/user training issue, it has nothing to do with Android).
When I say soft-boot, I mean that the image is transferred to the tablet, which then hands over control and starts executing that image - but it is not "flashed" to Flash memory, so the next time a boot occurs, the same boot images are still stored in either "boot" or "recovery".
In this configuration, the phone should be much more likely to complete an OTA as it will have the stock recovery present most of the time, and only temporarily present when you attach to your PC and kick things off with a custom recovery.
The OTA could still fail, but it probably would succeed for a very lightly rooted stock configuration (other than problems with losing root).
The only downside to this arrangement is that you can't be flashing roms or making nandroid backups or other forms of rooter activities when you are away from the PC.
For the IT-OCD or obsessive ROM hopper, that could be a good thing.
good luck... the rest is up to you.
Ok, I installed Clockwork Mod from a toolkit because going into fastboot and choosing "Recovery mode" led me to a picture of the Android guy with a red triangle on his back saying "No Command."
I'm just going to install 4.2.2 myself now. Question regarding that link - odex/deodexed - I looked up the difference but can't tell which one is appropriate for me - I'm guessing it's odex because that seems to be closer to stock.
Edit: It worked! Thanks for your assistance, everyone!
IMO, google should not ship odex image now that we have fast enough hardware. odex is just a form of 'pre-compilation' which only benefit first time load(or when the cache is cleared). Too little gain for such a complicated setup.
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and when the device reboots it then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
MarkAllen said:
Went to update "YB1-X90L_170420" and as I have been normally doing I removed root, ran the update, and all was well. It installed fine and worked no problem.
I was then prompted for update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" So I started the download and it the device reboots then fails with this string, note the error about the "build fingerprint"
Supported API: 3
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Package expects build fingerprint of Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000408_170420:user/release-keys or Lenovo/yeti_10_row_wifi/yeti:6.0.1/MMB29M/LenovoYB1-X90F_S000426_170508:user/release-keys; this device has Lenovo/yeti_10_row
E:Error in @/cache/recovery/block.map
(Status 7)
Installation aborted.
I foolishly after some googling and not finding enough info opened a chat with Lenovo. The rep asked what the error was and once I showed it said that was just related to my fingerprint scanner .... really?!?!? I knew the chat was a dead spot at this point but tried to state this device has no fingerprint reader, etc.. and so on. Hope they could really tell me what the error was. Anyway the rep told me to 'ignore' the update and just carry on since my device is actually working. They then went on to state they are hardware only on the chat session, which the Lenovo site says nothing about that. They then also told me to take this up with Google as they make Android not Lenovo. So much for warranty helping anything but possibly replacing a physically broken device. Their techs are useless, seriously.
So anywho, as you see in the error the update is trying to apply but looks for "Lenovo/yeti_10_row_wifi" and is finding somewhere (in the update or my device?) "Lenovo/yeti_10_row", notice the missing "wifi" on the end of that. My 'build.prop' and other system files are untouched. I even tried resetting the device. Which after the reset I was able to once again install the "YB1-X90L_170420" update but this next update "YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90F_USR_S000426_1705080316_WW06_BP_ROW" fails again on that same fingerprint mismatch.
Any clue what I should be looking for here? Has anyone else installed that update successfully?
Will anyone here supply me with the original (or as close as original) clean stock ROM without paying for it? I know I should have backed up with TWRP before I started doing updates, and this may well be my issue, but I didn't and not I can only restore back to an already rooted backup. Though I assume doing a reset of that rooted restore is considered clean (no root or 3rd party anything)?
thanks for any help or ideas!
Click to expand...
Click to collapse
From what i recall the fingerprint is what is shown in the buildprop. You could try editing this but i would tread carefully if its just a minor update as it may justmess up your system if there are other mismatches during the update process.
Lenovo technical support is a complete joke, you get much better help here. Lol
Sent from my F5121 using Tapatalk
Nope every line of my build.prop, where listed, has the proper "Lenovo/yeti_10_row_wifi" that the update claims is wrong. I personally think it is this update itself but no confirmation from other users if the update
"YB1-X90F_USR_S000408_1704201342_WW06_BP_ROW_TO_YB1_X90 F_USR_S000426_1705080316_WW06_BP_ROW"
has installed for them yet.
And I certainly knew how far I was *not* going to get with Lenovo but figured it couldn't hurt. I was really trying to get a stock ROM download from them or anywhere. I would love to just revert this to how it was out of the box and start over.
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
MarkAllen said:
Well for reference I think I finally realize what is causing this (unconfirmed, but sounds feasible).
I did at one time try the "YB1-X90L_USR_S000155_1609272258_WW06_BP_ROW" noted in another thread here from Easy firmware. I figured since it was a free download and others have done it, what could it hurt? lol (I think I know now). Anyway I forget what it was at the time but something with that rom just wasn't right for me and I decided to restore back to my TWRP backup I had made. I'm assuming my backup doesn't overwrite something that "L" version rom did and leaves some residue that reports itself as the "L" model now?
Anyway that is the only thing to me that makes sense to me that could be happening. Of course I have no original stock rom with IMG files to flash again to fix this. :/
Can anyone here confirm Easy Firmware is safe to use? Can anyone confirm their YB1-X90F rom is really that models rom?
Click to expand...
Click to collapse
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Broomfundel said:
Hi,
I registered for the free account. Had to email there support team to get it activate as there were problems their end. The 90F firmwares were not in the free tier so I paid the $15 through paypal to be safe, and got the 90F firmware fine. It was old and I had to run a lot of updates to get it up to date. But it got everything back to how it should be.
I blame Lenovo that we have to jump through theese hoops, but the files are legit.
Click to expand...
Click to collapse
Thanks for that confirmation! I did end up getting a registered account ($15) used Paypal and all looked good. I ended up downloading two versions of firmware. Initially I thought I would start with the oldest knowing many updates awaited but really wanted to be sure in erasing all my previous steps just in case it didn't work or the same thing happened again.
Used "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" from Easy Firmware. I opted to follow the included "installer.cmd" but did not do the "unlock" or "lock" as I already was unlocked of course and did not want to lock it again. When it completed I first noted my Halo keyboard not working and things were in Chinese here and there. This post resolved both items (thanks vimalbhimani!). Pretty sure that was because I formatted all the various partitions including "country", duh. Sadly however this version was showing no further OTA updates were available at all. Maybe Lenovo has deleted some of the really old OTA downloads and they are no longer available? Not sure.
I then installed the most recent rom "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". This time I did not format and only flashed this newer roms boot, bootloader, factory, recovery, and system images. After the system was backup everything was in great shape and updates were available. I made a TWRP backup straight away. Then I let the first and second updates listed below download and install via OTA and had no issues. The final two I opted to save time and installed using the standard recovery from my SD card after I downloaded them from my PC. Here are direct links to those if anyone wants them and they are in order of install (descending) based on already having "YB1-X90F_USR_S000196_161104"
http://tabdl.ota.lenovomm.com/dls/v...S000239_1612091428_WW06_BP_ROW_WCAC703BC6.zip
http://tabdl.ota.lenovomm.com/dls/v...S000340_1702251540_WW06_BP_ROW_WC365253B3.zip
http://tabdl.ota.lenovomm.com/dls/v6/YB1-X90F_170420_WC76FD00EF.zip
http://tabdl.ota.lenovomm.com/dls/v...S000426_1705080316_WW06_BP_ROW_WC80C2A0F2.zip (this is the failed update that incited this thread)
All updates went great and all is well at this point. Made another TWRP backup and I plan to root again now and see if any upcoming updates later have some issue?
I just wanted to report back here if anyone was interested that I unrooted, updated the June OTA update, and was able to root again without issue.
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
FreddeHamm said:
i got the same error message and now i'm stuck. I cant install any updates and so i bought a account from easy-firmware to get the firmware ... the firmware: YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip
doesnt not work with twrp or the stock recovery... it tells me "zip file is corupt"
@MarkAllen: Can you provide a guide how you got back to the stock rom? just flashing the zips doesnt work....
i really need help...
Click to expand...
Click to collapse
You cannot flash the ZIP file with TWRP or stock recovery. You have to unzip the file and then flash each IMG file that you need manually while in fastboot mode (there are seven of them).
**** IF YOU FOLLOW THESE DIRECTIONS IT IS NO ONES FAULT BUT YOUR OWN IF IT SCREWS UP SOMETHING!!! ****
**** WILL TRY TO HELP PROVIDE INFO IF I CAN BUT CANNOT GUARANTEE ANYTHING. ALSO THIS ERASE ALL YOUR DATA ****
First be aware as noted in the previous post above that I tried using "YB1-X90F_USR_S000036_1607280616_WW6_BP_ROW-flashfiles.zip" intially and it worked fine to get me back up and running but once I was done no new OTA updates were showing at all. No clue why so I ended up doing it again but used the ROM named "YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip". Also note I had erased my "country" partition and flashed "country.img" which requires the info posted by vimalbhimani again linked above in my previous post. It has to be used to correct for your country, no biggie at all and worked fine for myself.
1) Unzip the ROM you downloaded to a folder on your PC
2) From command prompt go to that folder
3) Make sure from the command prompt that ADB and fastboot commands are working properly
4) Put your tablet in fastboot mode ("adb reboot bootloader")
(these next commands are directly from the "install.cmd" included with the ROM from EasyFW, I just opted to run them manually one at a time in order and I omitted the unlock and lock commands)
fastboot flash gpt gpt.bin
fastboot erase misc
fastboot erase persistent
fastboot erase frp
fastboot erase metadata
fastboot format config
fastboot format country
fastboot format cache
fastboot format data
fastboot format factory
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash config config.img
fastboot flash country country.img
fastboot flash system system.img
fastboot flash bootloader bootloader
fastboot flash oemvars bootloader_policy-oemvars.txt
fastboot continue
That's it. Minus the Intel error code 03 for being unlocked, it should be a normal out of the box setup when it boots back up into Android.
good luck!
People that are looking for the YB1-X90F_USR_S000196_1611040312_WW06_BP_ROW-flashfiles.zip may want to take a look at this post.
In contrast to my experiences with devices made by other OEMs, it seems like the files can directly be used for downgrading the Yoga Book if you're currently using a newer version.
Moved...