Database Users

Error when trying to upgrade to 5.0 using TWRP

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.

How to move new rom files to Nexus 7 grouper after failed flash?

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

Asus zenfone 2 laser 6 ZE601KL - Can't change/install new ROM

Hi all,
I need some help please. I have an ASUS zenfone 2 laser 6 ze601kl. Came with a CN rom. No Google play services, go them installed using a google services installer. Trouble is, Android Wear dropped out and lost the watch details, backup failed randomly, google play services randomly crashed, play store etc. Wife wasn't too happy with me. Plus the random chinese apps updating and popping up with who knows what.
Current ROM CN_1.16.40.1715_20160623
Goal was to install a new WW rom which hopefully had working and stable google play services. Cannot install WW rom as it's CN - recovery error.
* gained root with KingRoot
* Debug mode on
* Unlocked bootloader using ASUS boot unlocker. Tried recovery, selected update from SD, same fail.
* installed ADB and fastboot (1.43) on windows 10 - nope, ADB recognised but always said 'cannot load <filename>.zip. Didn't matter which ROM or version.
* Tried to fastboot a new recovery and boot img, almost bricked it. Recovered using a CN ROM recovery and boot.img from
I have now:
* installed TWRP v3.0.2-5, which doesn't let me update to any ROM at all (WW official, WW rooted, resurrection remix etc)
Current error with UL-Z00T-WW-1.16.40.1524-user.zip is
Device SKU:
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR: 7
Error installing zip file 'path/filename.zip'
Can't install Marshmallow WW ROM - says
Can't install this M package (tues sep 27 <time>) L less than 20160426 build (date/time)
Can't install RR Rom
Comparing TZ version TZ.BF.3.0.C3-00025 to ZT.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.c3-00025") == "1"
Basically I'm stuck, I can't use ADB (I did reinstall Windows 10, ADB still can't read <filename.zip> on my PC), and I can't seem to install any rom and get rid of teh CN ROM which I really, really, really want to.
Help?

I still can't change ROM's, however I can flash nano GAPPS (anything bigger tells me theres not enough space in the system partition).
Does anyone else have this issue with changing CN rom to WW or other?

Z00T - can't install any custom ROM
Firmware issue: Solved:
https://forum.xda-developers.com/showpost.php?p=68328880&postcount=2291
Hi, I have the same or similar issue. Did you solve yours meanwhile?
Did I mess up an essential drive in my Z00T or do I have a problem with a version? Although the stock ROM came with the full load of google bloathware-**** - so it's likely not chinese.
What happened:
I tried to recover an old CM13 nandroid backup from a similar Z00T (ZD551KL) on a replacement device.
Unfortunatelly (?) I usedeach and every drive twrp offered me for this backup and I put the recovery it the same way. The rrecovery image is installed with no problems. However, when rebooting I end up in the bootloader mode. If only system or system and data are recovered, the device freeze at the ASUS logo.
Beforehand I made a nandroid backup of the stock android 5 system installed via twrp (i mixed several twrp, it could be 3.0.0-0 or max. 3.2.1-5) on my new replacement Z00T. I can easily go back to the stock-ROM backup - this works really fine - from each of above twrp after each and any failed other attempt.
Now, when trying to install either a lineage 14.1 (i still have two builds on my SD card) or a 15.1 I found somewhere the same error occurs: "Updater process ended with ERROR: 7 Error installing zip file 'path/filename.zip'". On my old device at least one of those 14.1 zips worked fine and the machine was updated to 14.1. So the ZIP is likely not corrupted.
I erased the device check in the install-ZIP by changing the "lineage-14.1-20180625-nightly-Z00T-signed-edit.zip\lineage-14.1-20180625-nightly-Z00T-signed-edit\META-INF\com\google\android\updater-script"
This however leads to the error message "Invalid zip file format" - nothing get's installed.
Any ideas what can help?
capt_bob74 said:
Hi all,
I need some help please. I have an ASUS zenfone 2 laser 6 ze601kl. Came with a CN rom. No Google play services, go them installed using a google services installer. Trouble is, Android Wear dropped out and lost the watch details, backup failed randomly, google play services randomly crashed, play store etc. Wife wasn't too happy with me. Plus the random chinese apps updating and popping up with who knows what.
Current ROM CN_1.16.40.1715_20160623
Goal was to install a new WW rom which hopefully had working and stable google play services. Cannot install WW rom as it's CN - recovery error.
* gained root with KingRoot
* Debug mode on
* Unlocked bootloader using ASUS boot unlocker. Tried recovery, selected update from SD, same fail.
* installed ADB and fastboot (1.43) on windows 10 - nope, ADB recognised but always said 'cannot load <filename>.zip. Didn't matter which ROM or version.
* Tried to fastboot a new recovery and boot img, almost bricked it. Recovered using a CN ROM recovery and boot.img from
I have now:
* installed TWRP v3.0.2-5, which doesn't let me update to any ROM at all (WW official, WW rooted, resurrection remix etc)
Current error with UL-Z00T-WW-1.16.40.1524-user.zip is
Device SKU:
OTA image SKU: WW
Please use the right SKU for updating...
Updater process ended with ERROR: 7
Error installing zip file 'path/filename.zip'
Can't install Marshmallow WW ROM - says
Can't install this M package (tues sep 27 <time>) L less than 20160426 build (date/time)
Can't install RR Rom
Comparing TZ version TZ.BF.3.0.C3-00025 to ZT.BF.3.0.R2-00064
assert failed: asus.verify_trustzone("TZ.BF.3.0.c3-00025") == "1"
Basically I'm stuck, I can't use ADB (I did reinstall Windows 10, ADB still can't read <filename.zip> on my PC), and I can't seem to install any rom and get rid of teh CN ROM which I really, really, really want to.
Help?
Click to expand...
Click to collapse

TWRP E1001 - Updater process ended with ERROR: 7

Hi,
I have recently decided to move my FIG-LX1 to Android 10 (previously using LineageOS 16.0), and after moving to LineageOS 17.1 (apparently unstable) and trying to install AOSP instead I seem to have screwed up something. I didn't manage to run the AOSP, but after playing around in recovery and fastboot, flashing ROMs via TWRP stopped working properly. Every time I try to flash any ROM using TWRP it shows "E1001: Failed to update system image" and "Updater process ended with ERROR: 7". AFAIK this error is connected to the device check and indicates that the ROM is not suitable for my device, but these are the same ROMs (i. e. LineageOS 16) i have previously installed with no problem (they are definitely compatible with my phone). I have also tried multiple TWRP versions (3.2.1, 3.3.1, 3.4.0) with no luck.
I have searched for this error a lot, but it's usually been connected with flashing on invalid devices, which is not the case here.
I would be grateful if someone could help me fix this error.
Thanks in advance!

LineageOS installation problems on Samsung A3 SM-A300FU a3xelte

Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.

honza1 said:
Hi,
I hope I post into the correct category.
I am trying to install on LineageOS on a Samsung A3 SM-A300FU a3xelte using twrp and start to be completely confused.
I try to explain "historically".
I purchased the unused device running Android 5.
Following the installation instructions under <https://wiki.lineageos.org/devices/a3xelte/install>I tried to install several versions of TWRP for Samsung Galaxy A3 2016 (Exynos) (twrp-3.5.2_9-a3xelte to twrp-3.2.1-0-a3xelte) using heimdall as well as odin.
Every attempt ended up in "image too large for recovery".
Searching a smaller compatible version I tried versions down to twrp-3.0.0 --> Same result "image too large for recovery".
Even lineageos recovery (lineage-17.1-20210411-recovery-a3xelte) could not be installed successfully.
In the meantime I installed a combination stock rom (COMBINATION_OXA_FA44_A300FUXXU1AOK1_OXAOK1_CL4447487_QB7014253_REV00) and the probably newest Stock Rom (Baseband version A300FUXXU1CPH3, Android 6.0.1) and repeated the installation attempts for twrp as mentioned earlier.
"USB debugging" was activated. This device does not have option "OEM unlock", but some research is telling me that this is most likely not the problem.
In order to proceed somehow I installed successfully "TWRP_2.8.7.0_A3_F-H-FU_5.0.2_v2" using Odin. I know, that this version should not be used on a3xelte
Nevertheless this version has only 12,8 MB.
I could boot into twrp. The installation of lineage-os failed - as expected - because of the "wrong" device. Therefore I deleted the leading "assert" lines from updater-script, packed the whole thing newly as zip and tried installing using "adb sideload" as well as twrp "Install".
Obviously these installations failed on line
block_image_update("/dev/block/platform/13540000.dwmmc0/by-name/SYSTEM", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") || abort("E1001: Failed to update system image.");
I examined the existence of /dev/block/platform/13540000.dwmmc0/by-name/SYSTEM. This path in fact does not exist on my device, but only /dev/block/platform/soc.0/by-name/SYSTEM
I changed the update script again using that path without installation success.
What completely screwed me up: If I run in twrp "blockdev --getsize64" it shows for
system : 2575302656 (2,4GB ?)
recovery : 15728640 (ca. 15 MB)
This explains why I could not install the twrp-a3xelte versions. They are actually too large for the recovery partition.
But the system partition seems to be large enough and I wonder why I found different pathes than the update-script expects.
Has anyone any idea how to get lineage-os installed on this device ?
Thanks in advance for any hint.
Click to expand...
Click to collapse
Hm ... unused device?
So it should be on stock firmware with original partition sizes.
Have you check to boot into stock recovery before?
Maybe there is something wrong with this "unused" device.
You can try to flash a recent stock firmware with original pit file to re-partition to stock partition sizes.
On windows pc use Odin for flashing.
When on stock Samsung firmware, try to flash twrp recovery again.