I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
dude the error is written in plain English: the process expects one type of thing in your system, but it finds another, doesn't like that so quits. trying to find the exact source of the error would be futile. I received an error too, not sure if it was the same since I didn't bother reading it. I just downloaded the stock 4.4.4 firmware from Google and extracted system.img and flashed it with fastboot. I'd suggest you go that route. you can try flashing from twrp again after that, personally I went the adb sideload route: http://forum.xda-developers.com/nexus-7/general/lollipop-ota-update-via-adb-data-t2941175
arimaidana said:
I have a Nexus 7 2012 Wifi only, currently with Android 4.4.4 Kit Kat. The tablet is rooted and has TWRP installed. I downloaded this OTA package: http://android.clients.google.com/p...signed-nakasi-LRX21P-from-KTU84P.4939a9ff.zip
When I try to install it using TWRP, I get this:
mount: failed to mount /dev/block/platform/sdhci-tegra3/by-name/APP at /system: Device or resource busy
Package expects build fingerprint of google-nakasi-grouper:4.4.4/KTU84P/1227136:user/release-keys or google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper:4.4.2/KVT49L/8d195fb610:eng/test-keys
I looked for this error but didn't find anything. What can I do? (Thanks in advance!)
Click to expand...
Click to collapse
You are using OmniROM. Pretty obvious you can't upgrade a custom ROM with a stock OTA.
This has nothing to do with omnirom at all, it all has to do with twrp using a custom .prop with wrong preset values. It wasn't an issue until Google decided that the 5.0 update checks more things, hence this stupid error. Btw that's exactly the 1st thing the upgrade script checks!
twrp must change its way of providing props because it's so obviously a major bug and will prevent using it to install any future updates.
What I did is use the factory image to do a custom non-wiping upgrade (there's a topic about how to do that), got incredibly slow performance and then do a wipe to get performance back and start with a clean slate with Lollipop, like I did with Kitkat.
So I think if your Kitkat was starting to be slow, better start anew and anyway Lollipop lets you choose exactly what to reinstall.
Related
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
JFMFT said:
I'm getting an error in recovery I've never seen before in my 3+ years with Android, rooting, etc. The error is this:
"assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so"
I get the error when I try to apply the 4.2 OTA .zip package in Clockworkmod Touch Recovery. I am on the newest (3.41) bootloader and obviously I have root. The system files all pass the check, but I'm getting this error and despite having Googled some answers, I've come up empty handed. Apart from flashing back to full stock, I am not sure what to do. Any thoughts from anyone?
Click to expand...
Click to collapse
dont know how to fix the error, but there is a newer bootloader version (4.13)
http://forum.xda-developers.com/showthread.php?t=1989319
Have you flashed a custom kernel? Some of the custom kernels also update that file so it is no longer stock, and hence it fails the assertion check on upgrade.
You can download the original stock 4.1.2 file here:
http://forum.xda-developers.com/showpost.php?p=34057950&postcount=221
:good:
Forgot to mention, you'll also need the stock 4.1.2 kernel installed if it isn't already, you can grab a copy here:
http://forum.xda-developers.com/showpost.php?p=33030559&postcount=4
Cheers,
Dave.
I have the same issue with assert failed: apply_patch_check("/system/vendor/lib/hw/power.grouper.so").
I have the stock kernel 4.1.2 and even installed 4.13 bootloader but this error is still there.
I'm under 4.1.2 stock, unlocked/rooted, that's all.
Any idea how to solve that ?
OK I'm trying to update to 5.0 on my Nexus 7. I have the OTA file on both my PC and my Tablet. I'm rooted and unlocked. I'm using TWRP and Wug's
When I try to flash the file it gives me this message before bombing out
Code:
Package expects build fingerprint of google/nakasi/grouper:4.4.4/KTU84P/1227136:user/release-keys or google.nakasi/grouper:5.0/LRX21P/1570855:user/release-keys; this device has Android/omni_grouper/grouper:4.4.4/KTU84P/eng.dees_troy.20141028.111642:eng/test-keys
How do I fix this so I can get the OTA flashed. I don't care about losing root because I can use Wug's to get it back.
Im getting the same :S
seems to be complaining about your custom recovery (TWRP?) note the "dees_troy" string in the message.
if you have an unlocked bootloader, you could flash the stock recovery from KTU84P* into your recovery partition, and then take the OTA**. After that, just use fastboot to flash your custom recovery back into place.
cheers
* assuming you were on rooted-KTU84P to begin with.
** attempting to run an OTA on a modified ROM generally only works correctly on very lightly rooted stock, and sometimes not even then. If you have removed stock (system) apps, diddled with the stock frameworks, or installed something that replaced a system shared library (.so), it is pretty unlikely that the OTA will succeed. Take full backups before you start.
Hey guys,
Actually my Rooted device with unlocked Boot Loader is running on Kitkat with build number KTU84P. I am trying to finally Updating the System after it tell me all the Time "Your system have an update on the 5.0.2" and to hopefully get the bugs away from this System Version.... My system run not smooth enough for me actually....
Well if I try to Update OTA i get everytime the Error Status 7, i guess that caused of that my Boot Loader is unlocked, but i won't to lock it just to be able to Update it on an newer version.
I was already looking for another CM Version for my Device who is maybe working better than my actual System, but didn't found anything really who was made me happy... So I am still looking, the most of Version here are just Beta, i want a system with no or very less bugs, well the best will be a final CM version..... Or is it another Way to do the OTA Update on a Rooted Device and maybe after that just reinstall SU and get SU right back?
Thank you in Advance for your help.
Edit: For clearance, it is a WiFi Only Device
No, it's not because of your unlocked bootloader but due to the boot and/or system partition modified e.g. by installing SuperSU / busybox / etc.
The only way to get the OTA is flashing original images, applying the OTA and then flash SuperSU again ... but that doesn't make much sense. It's much more easy to directly fastboot flash the factory image.
Thank you for your answer, how's "fastboot flash" working? Will i flash the New Android img or just rechange the Boot/sys partition to be able to install another OTA android version?
I guess actually the easiest way will maybe be to just install CM/omsi and use a custom made Android Build... If you tell me its easier, but idk which kind i can use without any issues.....
Hi,
I have rooted my Nexus 7 and installed TWRP, but when tried to flash slimkat 4.4.4 it failed with error message "set_metadata:recursive: some changes failed". An important details was that I did this after a couple of glasses of wine (genious, i know) and of course I messed up and did a backup after the my first attempt at flashin the slimkat rom, so restoring the back up is no good. I did all of this from the device itself, except the OEM unlocking.
How do I access the the Nexus 7 and add other rom files in the state it is now. I can see that Android filemanager in OSX detects it when I try to start normally, but is not able to gain access, then the device goes to TWRP
How do I move forward from here? I guess I need to get a nother rom zip file to flash, but I'm not sure.
I want to have lightweight custom rom, before trying to flach slimkat my Nexus 7 was on android 5.1.1 and it was not really usable. My goal is to use the device for not heavier than kitkat, please help me.
------------------------------------------------------------
format and mount systems, mount system data...
symlinks and permissions...
set_metadata:recursive: some changes failed
E: error in sdcard/download/slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
(status 7)
Error flashing zip 'sdcard/download/slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
updating oartition details
------------------------------------------------------------
Details:
device: Nexus 7 grouper
rom that failed: slim.grouper-4.4.4.build.9.0.-OFFICIAL-8258.zip
TWRP ver. 2.4.4.0
Computer OS: Ubuntu 16.04
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
EDIT: Flashed Recovery.img (Only recovery.img, via fastboot)
Results: Recovery is flashed and working.
Phone does boot up perfectly fine, no issues
Data is NOT lost.
Flashing the 7.0 update(A2017UV110B15) (Via stock recovery) [Remember to put it on your SDCard]:
Verifying update package...
Verified.
"EMC /dev/block/bootdevice/by-name/boot****load of numbers)" has unexpected contents
Aborted
Click to expand...
Click to collapse
( Same error as when I removed device verification.. maybe this is a user error and not a system/update error )
( Maybe I failed to download the update zip properly? I'll try the OTA update instead )
Downloading..
Rebooting..
Installing System Update...
Has unexpected contents
Package mixmatched
Aborted
Click to expand...
Click to collapse
( No, not a user error I suppose.. I don't know what is wrong then! This is odd )
System update failed
Reason: The system update package did not match the phone
Click to expand...
Click to collapse
And for the record, I am on A2017UV1.0.0B29
Andrew S.S. said:
I'm unable to unpate as of right now because I have TWRP recovery installed.
When I try to, it tells me " Package expects fingerprint of *original device fingerprint* this device has TWRP\Team_Win_Recovery_Proejct/ailsa_ii
Updater process ended with ERROR: 8
Error installing zip file '@/cache/recovery/block.map'"
I tried removing the part of the script that checks this, but then I got a different error (I don't remember what it was, it said something about "Boot:1826459185:1U57126581(Random numbers not the actual ones) contains unexpected content" or something like that
So I was wondering, how would I go and update to the new Android 7.0 update? (I also have the zip file of the update locally)
I would assume that I could flash stock recovery but a. I don't have the stock recovery.img, and b. I was reading around and someone mentioned that if I flashed stock recovery it'd delete all my data.
I'd be highly disappointed if the only way I could update to the 7.0 update is by deleting all my data. I'm sure there must be some way around it.
Can anyone help me out? I'm sure I'm not the only one that'll have this issue
Click to expand...
Click to collapse
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
lafester said:
Flashing stock recovery will not delete your data. Find your stock firmware download on the forum or zte, pull recovery.img from it and flash in twrp.
Of course those who whine about wiping data usually are the ones who need to do it most.
FYI I updated, flashed twrp and then restored data from my b29 backup without issue. At least this way you can make a new backup before attempting.
You can also wait for the flashable .zips to show up and avoid all the hassle.
Click to expand...
Click to collapse
Read my updated comment; Sorry that I didn't just edit the thread. And that makes sense. I think it would be wise for me to just wait.
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
WesTD said:
First of all, flash rollback zip from DrakenFX.
Then update via OTA. That's all. I've done these steps yesterday and I'm using Nougat now.
Click to expand...
Click to collapse
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Only use ota if you don't want twrp/root anymore.
Andrew S.S. said:
I saw your post then had forgotten about it til now ( haven't checked ) but in the last month I've forgotten where the rollback zip is located / what thread. Any help would be appreciated.
Click to expand...
Click to collapse
Here you go; https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2