Related
hi,
I searched all the related threads to find a solution to this with no result. I'd appreciate if anyone can help me with this. Here's the case:
1- I downloaded the first OTA update with no problem.
2- I downloaded the second OTA update (2.1 firmware) with no problem.
3- Installation went fine. The status bar came to 100%, it waited a while and then showed an error triangle next to a phone icon.
4- Pressing HOME+POWER button (I learned it after reading some posts here) the screen showed the following error:
E: Can't chown/mod /system/xbin (No such file or directory)
E:Failure at line 1007:set_perm_recursive 0 2000 0755 0755 SYSTEM:xbin
Installation aborted
Now just note that I have re-flashed the 1.5 using the RUU at HTC website just to make the phone up and running again. I tried the steps described above several times and every time the same result. Can anyone help please? I'll be eternally grateful!
Hmm...
I would guess you run out of disk space...
Delete some apps.
Get 70 mb minimum and 100mb to be safe.
Then update the phone...
(Remember to install the first update again)
Come back and tell me if it worked...
well, disk space can't be the problem. After I flashed the 1.5 again I didn't install any apps. I once even formatted my SD card but still the same.
Did you find a soulution to this? I have the same error on a customer's Hero. Flash a clean 2.73.405.5_WWE from RUU downloaded from htc.com and immediately after that apply the 2.73.405.6 OTA. The following 2.1 OTA verifies in the phone and it reboots and run the installation untill you get the triangle/phone screen.
I also downloaded 3.32.405.1 RUU from shipped-roms but that also fail to install when installing system, so I'm starting to think that there is something wrong with the phone itself.
Have you tried contacting HTC with this error? If you're running official builds they should be able to point you in the right direction.
Yeah, I'll talk to the HTC support and send it to a service center. Thanks for replying, gave it a long shot asking in case there was some known issue we could resolve ourself.
Make sure you let everyone know if they do give you an easy solution.
Unfortunately there was no easy solution so we had to send the device to a service center.
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
GeNiO426 said:
I was excited that I received a message to update my firmware to 2.2 Froyo, but when I tried doing so I kept getting errors at the installation screen. It would download then go to the installation screen and give me an error.
I'm not sure if I bricked the phone without knowing or something, but I get the following error message when trying to upgrade:
E:Can't open /cache/recovery/command
I have no idea what that is/where it is. I checked my SD Card, but I didn't see anything like that there. I'm guessing I'm missing that folder/file, but I don't know where it would have went or if I can get it back.
I've tried to do the update both through my Bravo and downloading a ZIP file and trying to do it through the Recovery screen. I tried everything Motorola suggests on their website as well as searched Google a lot, but came up with nothing.
I should add that even when I click "applysdcard:update.zip" it gives me a few errors and aborts the installation.
I'm just wondering if there's any way to fix this so I can upgrade my firmware?
Thanks to anyone that can help.
Click to expand...
Click to collapse
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
gosunta said:
i have the same error, but i do have modified the bravo with sqlite editor en root explorer. Does somedoby has the original build.prop please? i cant remember what i have changed in mine so i can not update
Click to expand...
Click to collapse
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Finally working , i replace the file and i did upgrade my phone. Thanks a lot for all the info
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
seraphielx said:
I get a the update downloaded but when it restarts I am getting a white triangle with a yellow explination point.
If I pop the battery I can get past the error and back to the phone
I have it rooted with one click
Any info?
Click to expand...
Click to collapse
touch the screen at right-bottom and you will see a list. Select update.zip and touch ok
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
I'm sure there is a solution, but just forget it and install 2.2 SBF.
hippyman said:
Have you done any sort of modding using SQLite Editor or Root Explorer to your phone?
Click to expand...
Click to collapse
Yes, I used Root Explorer. I'm guessing by MCFarmfresh's post that there issome sort of original build for the phone? I've looked everywhere for hours all night last night before resorting to asking somewhere, but I couldn't find anything and the "solutions" I've seen all did not work. I kept getting the same errors.
Thank you for replying. If you can help, it'll be very much appreciated.
I have a rooted Bravo and I deleted some of the bloatware, and I received the Froyo update and everytime I download and the system resets I get an error and the update stops. Selecting from memory card doesnt work for me, and I dont have a backup of the original settings to re-install (which I'm not sure how to do that either). If anyone has any suggestions I'm open.
its checking for att apps
if you renamed them name them back to apk
I didn't rename them, I deleted them off my phone.
Sent from my MB520 using XDA App
I don't know much about these things but I would think that would be a bad thing to do...
I was able to get the update to install to my phone but now it is running slow
Any more info on how to fix this issue?
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
GeNiO426 said:
OK, so I tried everything that's suggested pretty much everywhere and I'm still unable to update. I'm not sure if I'm doing something wrong or what, but I've tried resetting the phone via the phone/recovery screen, tried updating via the phone, and I also tried replacing the original build, but nothing worked so far.
I have no idea what else I can do, but any help would be appreciated.
Click to expand...
Click to collapse
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
jorgonv said:
If nothing else works, you can always sbf. It sounds scarier than it really is, actually it is pretty easy. Just make sure you follow the directions. I've done several sbf's and they have all turned out perfectly.
Click to expand...
Click to collapse
Thanks. I'm not sure what it was, but I switched to my Windows XP desktop (from my Windows 7 Home 64-bit laptop) and the SBF Flash worked perfectly, thanks bandroid, yourself, and others. I really appreciate all of the help given. 2.2 looks and feels a lot better than 2.1 so I'm really happy about that.
MCFarmfresh said:
Just emailed you the original build.prop you need in order to get the update to work. Let me know how it goes.
Click to expand...
Click to collapse
please send me one too and where do i put it.????
mismisgh said:
please send me one too and where do i put it.????
Click to expand...
Click to collapse
If you will give me your email I can get it to you. For the life of me I cannot figure out hhow to attach files through pm using my phone lol. You can also use the .sbf method to upgrade but I'll definitely get the files to you if you send me your email.
SBF'in it...
Okay....so one of your gentleman above (I'm new to the forum ish) stated that he had deleted some apps off of his OS. I did the same thing with AT&T Hotspot Locator (unfortunately, AT&T was quick on merging this standalone app into MyAT&T so I couldn't get the atthotspotlocator.apk back). I fixed this using the SBF file.
I won't give you the step by step but I can tell you RSD Lite is a free program from Motorola. It's basically the program they use to flash boot SW onto an otherwise dead device.
Don't be intimidated by it because it really is rather easy to facilitate. Just do like I did and YouTube how to load an SBF into a motorola device. You can pause and replay as you go along to assure no errors. Takes like 15 minutes once you've got all the necessary files downloaded.
Well, that lasted long...
Everything was going fairly well until this morning when I clicked on the phone button (default launcher) and tried to go into the dialer, then it just closed every time I tried doing so.
To try to fix this I rebooted my phone, nothing; restored, nothing; factory reset, nothing; re-installed 2.2.1 FroYo via flashing the SBF with RSD Lite and 'apply:sdcard:update.zip' through Android's Recovery Screen, nothing.
When I tried doing the last 2, however, I received these errors (the first one I had with the first problem and the other 2 are new):
E:Can't mount CACHE: recovery/command
E:Can't mount CACHE: recovery/caller
E:Can't mount CACHE: recovery/log
Now, with the "caller" error, I did NOT touch anything having to do with the dialer and whatnot. That I know.
The last time I had problems with my laptop so I tried it on my desktop and it worked, but now I tried the desktop and it still isn't working properly. Some of the features that I had with the update are now gone such as the "third party apps" option and the sliding "lock screen" is now permanently present.
Any help with this is appreciated.
Hello All
First post here.
I bought a refurbished TF101 with dock from the Netherlands a week ago and updated to WW 8.6.5.7 OTA right after setting the device up. Then rooted it and used the ad hoc guide by qwer23 (thank you!) from this tutorial (via adb) in order to tether my Nokia N9 with the Joiku wifi hotspot app...
I got the notification yesterday that I could update to 8.6.5.9 OTA but after it checks firmware integrity and reboots, it shows an icon of the android robot with an exclamation mark after it tries to install the installation file.
I did a hard reset to the whole device, and again, OTA notification saying i could update and still shows the same error message when i press on install and it shuts the device down.
possible to get some help regarding this situation? any advice?
cheers
I've got the same problem.
I rooted 3.1 to get AdHoc tethering.
I got the 3.2 ww 8.6.5.7-20110730 OTA update and it installed without losing root or the modified wpasupplicant.
I just got the 8.6.5.9. notification, tried to update and got the android ! warning.
Rebooted/restarted and back to 8.6.5.7. but now no update available.
Can somebody point us to a restoration thread please?
Thanks
so far as I am aware this update wont work on rooted devices so you will have to un root to get it. There are a number of posts stating this on here.
v8code said:
so far as I am aware this update wont work on rooted devices so you will have to un root to get it. There are a number of posts stating this on here.
Click to expand...
Click to collapse
Yes, I know that, I'm perfectly capable of un-rooting.
As I pointed out, the previous 3.2 update installed while rooted, and I remained rooted, so I didn't suspect that this one might not.
There are also posts stating that the update won't show again once it's been downloaded once and the install has failed.
It's not on the Asus firmware downloads page.
So, once I've un-rooted, is the update still stored on the machine or do we have to wait for or find a ww zipfile somewhere?
cozzykim said:
So, once I've un-rooted, is the update still stored on the machine or do we have to wait for or find a ww zipfile somewhere?
Click to expand...
Click to collapse
As far as I know - since I'm in your same situation - there's nothing left to do but:
- bring the device back to stock;
- wait for the update to become available on Asus site, because we will not get any other notification for 8.6.5.9.
Well, this seems merely a question of time and also, some geeky dude out there could dump 8.6.5.9 stock ROM for easy Nvflash flashing
If you've downloaded the update and your TF101 is asking you to check notifications but you no longer have a update notification then you'll need to clear the DMClient cache in order to reactivate the update.
Check this this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
juscoll said:
If you've downloaded the update and your TF101 is asking you to check notifications but you no longer have a update notification then you'll need to clear the DMClient cache in order to reactivate the update.
Check this this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
Click to expand...
Click to collapse
Not my case, unfortunately. I received the FOTA notification, made the update process start and then something's gone wrong (green android with an exclamation mark). Now no more update notification is shown; actually searching for an update manually from the tablet returns a message saying that no update is available for my device.
KaylordTheuZ said:
Not my case, unfortunately. I received the FOTA notification, made the update process start and then something's gone wrong (green android with an exclamation mark). Now no more update notification is shown; actually searching for an update manually from the tablet returns a message saying that no update is available for my device.
Click to expand...
Click to collapse
Same here, I had already tried clearing the DMClient Data and Cache.
Somebody must have the downloaded WW file available in their cache, pretty please
i've unrooted my phone, did a full system reset and the update notification appeared. it was showing the android robot with the cogs working in its belly then again i got the exclamation error screen.
i looked at this thread: http://forum.xda-developers.com/showthread.php?t=1232810 where it says to check what the updater script checks for. have es explorer installed and it showed that the wpa supplicant and wpa supplicant.original is still in there. should i overwrite the wpa supplicant file with the original one? shouldn't this already happen when i do a full system reset?
aSIMULAtor said:
i've unrooted my phone, did a full system reset and the update notification appeared. it was showing the android robot with the cogs working in its belly then again i got the exclamation error screen.
i looked at this thread: http://forum.xda-developers.com/showthread.php?t=1232810 where it says to check what the updater script checks for. have es explorer installed and it showed that the wpa supplicant and wpa supplicant.original is still in there. should i overwrite the wpa supplicant file with the original one? shouldn't this already happen when i do a full system reset?
Click to expand...
Click to collapse
My answer is being based of your post and my assumptions.
I'm guessing that when you rooted, you changed other things after that were located in /system?
If so, then you didn't change it back when you unrooted.
All factory resetting does is make your tablet /look/ like it just came out the box. Users that aren't tech savvy do not modify /system files. So when they reset, it /looks/ like it's just out of the box.
In short, factory reset will clear your /data but it will not reset everything back to factory settings in /system.
You will need to re-root, replace the file with the original, then unroot again.
Just my thought process.
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
aSIMULAtor said:
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
Click to expand...
Click to collapse
This thread http://forum.xda-developers.com/showthread.php?t=1093778 has the original in the OP, just choose the 3.1 original.
aSIMULAtor said:
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
Click to expand...
Click to collapse
You could just copy the file into your external sdcard.
I believe you could do that. Apparently the new update doesn't require that fix anymore.
I believe that is correct.
I just look at them as a complete update.zip where everything is included in /system.
alex5790 said:
This thread http://forum.xda-developers.com/showthread.php?t=1093778 has the original in the OP, just choose the 3.1 original.
Click to expand...
Click to collapse
I've done all this, exchanged the AdHoc wpa_supplicant for the original (which I kept on a removable microsd), unrooted, rebooted (though not factory reset) and manually searched for the update......nothing.
The wpa_supplicant was the only change I had made, to connect to my HD2 Wm6.5
So, I still need the update package, unless I really do need to hard reset?
cozzykim said:
I've done all this, exchanged the AdHoc wpa_supplicant for the original (which I kept on a removable microsd), unrooted, rebooted (though not factory reset) and manually searched for the update......nothing.
The wpa_supplicant was the only change I had made, to connect to my HD2 Wm6.5
So, I still need the update package, unless I really do need to hard reset?
Click to expand...
Click to collapse
From what I have seen during my research, it looks like you will need to flash the NVFlash, update to a offical firmware provided by Asus on their website, and THEN check if you can recieve the update.
I'm just hoping.
Thanks, that might be the way, I'll check it out
did the same thing as you...before my device notified me of the update, then it almost updated, but now i'm just not getting any notifications anymore.
will try what The Dark Lestat suggests and will report back when it's done.
aSIMULAtor said:
did the same thing as you...before my device notified me of the update, then it almost updated, but now i'm just not getting any notifications anymore.
will try what The Dark Lestat suggests and will report back when it's done.
Click to expand...
Click to collapse
please help, I will not reveal more.
I tried to wipe data and hard reset, but nothing.
balls!!!!!
well, updating to the 3.6.5.7 via the zip file worked...but, still not receiving any notifications of 3.6.5.9 update AT ALL.
I guess, have to wait till someone uploads the WW 3.6.5.9 zip file and will try to install it that way...
(i hope someone does this! )
i've the same problem here. update failed, wiped everything, installed stock hc3.2 but no update available anymore.
It's possible that ASUS blacklists pad's with modified system files? how coul this be done? with gmail account? with wifi mac address? or this sounds too stupid to be true.
Twice, actually. After the second download (courtesy of the now-warned-against 'Framework Services forcing' trick) I got the identical error message via CWM Recovery:
Code:
Verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
Any suggestions about the next move, please?
You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.
Visa Declined said:
You can't install the update from Google the natural way if you have a custom recovery. Just download the update, boot into recovery, and run the zip.
Click to expand...
Click to collapse
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.
pofadda said:
Thanks, I know that. I did not use CWMR for updating - The update ran - 'Installed' - conventionally both times... It made the trip into Recovery on its own where the resident tool is CWMR. Is this a known issue?
I do have a copy of the update elsewhere than in /cache in case I need to copy it back there for some possible next move.
It would be great to hear of a way to get this update to install successfully.
Click to expand...
Click to collapse
This seems to be a known issue. When the update installs, it boots into recovery to install the update. If you're using a custom recovery instead of the default one, the install will fail.
The same thing happened to me. I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.
ahoyland said:
I simply copied the update .zip from /cache into a folder on /sdcard, rebooted into CWMR, backed up and installed the .zip from there. Easy peasy.
Click to expand...
Click to collapse
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not
Visa Declined said:
That's what I was trying to get the op to do in the second post of this thread, I'm not really sure if it's working for him or not
Click to expand...
Click to collapse
Thank you for that, VisaDeclined & Ahoyland! I quite misread the intent of your message. 'Normal' reboot is problematic, I read, so I have downloaded 'Quick Boot (reboot)' from here (Play Store seemed to be having difficulty - maybe because I had done the 'Framework' hack earlier?) and the little thing is now done and saying 'Build No. JZ054K' . I am now a much happier bunny!
Thanks is on its way, folks.
Happiness can be so short-lived... (but good things come to those who try)
Life took a turn for the worse when I noticed that updates and downloads from Play were not getting through. The errors are:
DF-BPA-13 'trying to install',
RPC-AEC-0 'Error while retrieving information on server' &
923 (dunno)
However - THE GOOD NEWS! - I tried these two actions and all is well now:
(ex Google, the poster said)
First Make sure you're signed into Talk.
Go to setting>apps>all>Google play store
Then clear data and uninstall updates.
Then go to Google account manager, clear data and force stop.
Power off and leave it off for a minute or two, re-boot and it should work, if not go to talk and make sure you're still signed in.
Tr
y updating or downloading one thing at a time to see if it works.
Still 'RPC etc.', so
I went Settings>Accounts>Google>(account name)>(Menu)>Remove account.
Ran PlayStore,
was prompted for and re-entered my (existing) account.
Thereafter all was as before and updates were working again! :laugh::laugh:
HTH
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...