I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
You need to be on this FW : 23.4.A.0.546.
But don't bother, there is no recovery. I can't enter it atleast.
undeniableturnip said:
I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
Click to expand...
Click to collapse
Extract the zip, goto to "META-INF\com\google\android" open the updater script and remove this line "getprop("ro.product.device") == "scorpion_windy" || abort("This package is for "scorpion_windy" devices; this is a "" + getprop("ro.product.device") + "".");
ui_print(" ");", save it and rezip.
Otherwise try using the official TWRP recovery.
ckyy said:
You need to be on this FW : 23.4.A.0.546.
But don't bother, there is no recovery. I can't enter it atleast.
Click to expand...
Click to collapse
A workaround for this is to reboot it into fastboot, flash the official twrp and reboot, you can get into recovery but the system won't boot, when you're done go back to fastboot and flash the boot.img from the PA zip.
Installing PA in Z3 Compact Tablet
undeniableturnip said:
I'm trying to install the new PA rom for our tablet and I'm getting a strange error. It says "This package is for "Scorpion" devices; this is a "z3".
Has anyone else faced this issue before?
Click to expand...
Click to collapse
I have been trying to install three time only ending with the error message that the package is not for "scorpion" but for "Leo" I will appreciate for clarification, thanks.
Related
I have flashed the CWM recovery http://forum.xda-developers.com/showthread.php?t=2295694 and tried to flash CM11 nightly, but I'm getting an error message that says "This package is for "SGP311, SGP312, pollux_windy" devices; this is a "pollux"."
I flashed the "SGP31x -> Advance Stock Kernel with Recovery v01 (FW: 10.1.C.0.344)" img.
I'm not sure why i'm getting this message, as I've ensure that I have installed the correct firmware and recovery, meant for my Xperia Z Tablet 16gb WIFI.
JoeSzymkowicz said:
I have flashed the CWM recovery http://forum.xda-developers.com/showthread.php?t=2295694 and tried to flash CM11 nightly, but I'm getting an error message that says "This package is for "SGP311, SGP312, pollux_windy" devices; this is a "pollux"."
I flashed the "SGP31x -> Advance Stock Kernel with Recovery v01 (FW: 10.1.C.0.344)" img.
I'm not sure why i'm getting this message, as I've ensure that I have installed the correct firmware and recovery, meant for my Xperia Z Tablet 16gb WIFI.
Click to expand...
Click to collapse
Isn't it so that that kernel is for *stock* based roms? But you're trying to flash a CM rom?
nickez2001 said:
Isn't it so that that kernel is for *stock* based roms? But you're trying to flash a CM rom?
Click to expand...
Click to collapse
I just received the same error message. Did you ever find an answer?
kevinsickles said:
I just received the same error message. Did you ever find an answer?
Click to expand...
Click to collapse
Open the ROM zip, go into META-INF folder, and keep going until you find a file called Updater-script. Open it with a text processing tool (Notepad++ recommended) and delete the three lines or so at the start of the file that mention build.prop. Save it (no archive type), and move back t o the same place, and try again
Inside that file this is what I am seeing for the top lines? Which ones do I want to get rid of?
assert(getprop("ro.product.device") == "SGP311" ||
getprop("ro.build.product") == "SGP311" ||
getprop("ro.product.device") == "SGP312" ||
getprop("ro.build.product") == "SGP312" ||
getprop("ro.product.device") == "pollux_windy" ||
getprop("ro.build.product") == "pollux_windy" ||
abort("This package is for device: SGP311,SGP312,pollux_windy; this device is " + getprop("ro.product.device") + ".");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
zayaabby said:
Inside that file this is what I am seeing for the top lines? Which ones do I want to get rid of?
assert(getprop("ro.product.device") == "SGP311" ||
getprop("ro.build.product") == "SGP311" ||
getprop("ro.product.device") == "SGP312" ||
getprop("ro.build.product") == "SGP312" ||
getprop("ro.product.device") == "pollux_windy" ||
getprop("ro.build.product") == "pollux_windy" ||
abort("This package is for device: SGP311,SGP312,pollux_windy; this device is " + getprop("ro.product.device") + ".");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
Click to expand...
Click to collapse
Same issue here. I removed the are from "assert" to right before "mount". Basically to get rid of the "getprops" and "abort"
and now it just errors out. I know not many people get this, but any ideas out there?
Thanks.
wingcook said:
Same issue here. I removed the are from "assert" to right before "mount". Basically to get rid of the "getprops" and "abort"
and now it just errors out. I know not many people get this, but any ideas out there?
Thanks.
Click to expand...
Click to collapse
it's better to use XZDualRecovery.
Rootk1t said:
it's better to use XZDualRecovery.
Click to expand...
Click to collapse
I have loaded the newest of that Recovery. Either recovery I have gone into gives me the same error.
wingcook said:
I have loaded the newest of that Recovery. Either recovery I have gone into gives me the same error.
Click to expand...
Click to collapse
you can't install custom ROM's with these recoveries.
Rootk1t said:
you can't install custom ROM's with these recoveries.
Click to expand...
Click to collapse
ARRRGH....
That would explain it. Can you send me a direction to a recovery that I can use then?
Thank you.
wingcook said:
ARRRGH....
That would explain it. Can you send me a direction to a recovery that I can use then?
Thank you.
Click to expand...
Click to collapse
You need to unlock bootloader and flash (or hotboot via flashtool) boot.img of the custom firmware you're interested in via fastboot. After enter recovery on boot of device and install .zip with firmware files.
Rootk1t said:
You need to unlock bootloader and flash (or hotboot via flashtool) boot.img of the custom firmware you're interested in via fastboot. After enter recovery on boot of device and install .zip with firmware files.
Click to expand...
Click to collapse
Since I get the same error for a couple of days, I'm interested, if someone has a solution to this.
ROM: OmniRom Nightly (for a very long time!). Last Nightly installed 22.12.2014. After that one, I can't boot to recovery. Installing XZDualRecovery gets me to recovery *once*. There I get the same error message, trying to install *any* ROM.
When I try to reboot to recovery I get the Sony Logo, an orange LED and *working* adb.
The last few hours I tried many things without a single thing working. (Except going back to a Stock ROM).
One thing was extracting boot.img from a current OmniRom and flashing it with 'fastboot flash boot boot.img', but it did not work.
Any help?
Jens1969 said:
Since I get the same error for a couple of days, I'm interested, if someone has a solution to this.
ROM: OmniRom Nightly (for a very long time!). Last Nightly installed 22.12.2014. After that one, I can't boot to recovery. Installing XZDualRecovery gets me to recovery *once*. There I get the same error message, trying to install *any* ROM.
When I try to reboot to recovery I get the Sony Logo, an orange LED and *working* adb.
The last few hours I tried many things without a single thing working. (Except going back to a Stock ROM).
One thing was extracting boot.img from a current OmniRom and flashing it with 'fastboot flash boot boot.img', but it did not work.
Any help?
Click to expand...
Click to collapse
seems that recovery in the latest nightly of OmniROM is screwed up.
Rootk1t said:
seems that recovery in the latest nightly of OmniROM is screwed up.
Click to expand...
Click to collapse
Tried to flash a boot.img from a current CM 11 Nightly. But it did not help. If this is an Omni-only-issue, with CM11 boot.img l should have been able to get into recovery?
Mines doing it too when trying to flash package rom. Although one thing to note is that I partially bricked my device then reflashed another firmware. But it said sgp311 but I have Xperia phone notifications that pop up and a hotshot option in the pull down. Any ideas?
I was able to fix my recovery by following the guide on twrp homepage. Not sure but I installed an older recovery.
What is this?
Modified HoaPham's cm12.1 and NikitaProAndroid's cyanogenextended kernel for d620
What it can do?
It can boot cm12.1 for D618 on our D620
How to do?
1.Open rom archive and go to META-INF/com/google/android and open updater-script
2.Delete the first line:
Code:
assert(getprop("ro.product.device") == "g2mss" || getprop("ro.build.product") == "g2mss" || getprop("ro.product.device") == "g2mds" || getprop("ro.build.product") == "g2mds" || getprop("ro.product.device") == "D618" || getprop("ro.build.product") == "D618" || getprop("ro.product.device") == "D610" || getprop("ro.build.product") == "D610" || abort("This package is for device: g2mss,g2mds,D618,D610; this device is " + getprop("ro.product.device") + "."););
3.Save, flash the rom, flash the kernel
4.Enjoy
Download link v2
Download link
Thanks to HoaPham98 for cm12.1 and to Nikita for his kernel
It works [emoji1] handle patches for double tap to wake doesn't work tough
Martiz said:
It works [emoji1] handle patches for double tap to wake doesn't work tough
Click to expand...
Click to collapse
Download terninal emulator, open it and type this:
su
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
Nice.. Now i'm on cm12.1.. Works as main rom with multirom too..
Sent from my LG-D620fr [CM12.1]
downloading cm12.1..i`ll test and report
System_F said:
Download terninal emulator, open it and type this:
su
echo "1 1" > /sys/devices/virtual/input/lge_touch/lpwg_notify
Click to expand...
Click to collapse
Is there a way to make it work even after reboot?
Sent from my LG-D620fr [CM12.1]
AntonPanos said:
Is there a way to make it work even after reboot?
Sent from my LG-D620fr [CM12.1]
Click to expand...
Click to collapse
maybe some1 can make a script or something to autoexec that command after boot
/del
I'm thinking about moving from stock lollipop on d620r to cm12.1
Just to make it clear, i need to flash stock KK, then unlock bootloader, and flash cm?
Or I can just flash from TWRP from lollipop? I'm bit confused about bootstacks, patched bootloader and those stuff. Guess I'm in a bit information overload.
P.S. Is CM12.1 ok as a daily driver?
culler said:
I'm thinking about moving from stock lollipop on d620r to cm12.1
Just to make it clear, i need to flash stock KK, then unlock bootloader, and flash cm?
Or I can just flash from TWRP from lollipop? I'm bit confused about bootstacks, patched bootloader and those stuff. Guess I'm in a bit information overload.
P.S. Is CM12.1 ok as a daily driver?
Click to expand...
Click to collapse
Reading a bit around the forum wouldn't be bad, every action is clearly listed and explained, but whatever. If you are on stock lollipop, you should get root, follow the instructions to install the patched bootloader for your mobile version, then flash kk bootstack for your mobile version trough latest TWRP via rashr or similar, and after that you can flash CM 12.1 rom and the kernel.
Martiz said:
Reading a bit around the forum wouldn't be bad, every action is clearly listed and explained, but whatever. If you are on stock lollipop, you should get root, follow the instructions to install the patched bootloader for your mobile version, then flash kk bootstack for your mobile version trough latest TWRP via rashr or similar, and after that you can flash CM 12.1 rom and the kernel.
Click to expand...
Click to collapse
Thanks, I just wasn't sure. I've read all threads but got lost in context what can and what i can't flash.
after half a day of usage the rom runs awesome very smooth and stable. also good battery like with ondemand and noop
the only problem was the camera that is overexposed but i fixed it changing the lib files..dt2w works great too
Ok, i've flashed it, and everything seems to be working, except one weird thing, power button is not working. I can't unlock my phone, or access power menu, or lock it. I've flashed it again but still didn't get it to work.
edit: volume keys also don't work
culler said:
Ok, i've flashed it, and everything seems to be working, except one weird thing, power button is not working. I can't unlock my phone, or access power menu, or lock it. I've flashed it again but still didn't get it to work.
Click to expand...
Click to collapse
Again, READ everything. If you go to cm12.1 thread you'll see there is a fix zip to solve the problem with buttons. Or just use the in-thread search tool.
tryed to install blisspop but i got bootloops, is it possible to install it?
panagiotisden2 said:
tryed to install blisspop but i got bootloops, is it possible to install it?
Click to expand...
Click to collapse
did u deleted the first row from update script?
Diaze said:
did u deleted the first row from update script?
Click to expand...
Click to collapse
solved it i forgot to wipe data i only wiped dalvik and cache
you dont need to delete anything from update script to install blisspop only for CM 12.1
thank you anyway
Well multitasking and speed on 5.1 is way better.. Nice having this kernel! :good:
Sent from my LG-D620fr [OwnRom 5.1.1]
does every blisspop user on d620 have camera errors and fc after some time using an app?
I've tried to copy paste d2w command into. sh file, put it in init.d folder and using kernel aduitor to start in on boot but id don't work. but, i can execute it manually and it works. at least I don't need to type it every time. maybe somebody know how to execute it on boot, or proper init.d syntax that will allow auto execution.
Edit: I was wrong about .sh file...
There should be no extension.
Just put this file in /etc/init.d/ folder and set permissions to 755 and d2w will work on boot.
https://dl.dropboxusercontent.com/u/13822451/xda/d2w
Phone was replaced by Motorola to a new device - after motherboard bug. A new device is UK version.
I have unlocked it and installed recovery, but I can't install any rom - I've tried with CWM and TRWP (2 different versions).
Every try ends up with "ERROR 7". In error logs:
You have an installed system that isn't signed with this build's key, aborting...
run_program: child exited with status 124
script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
Click to expand...
Click to collapse
I've tried with:
aokp_condor_mm_nightly_2017-01-16
AospExtended-v3.1-condor-20170124-0102-OFFICIAL
lineage-14.1-20170119-UNOFFICIAL-condor
I found a solution for "Error 7" (remove first lines from update-script) but it doesn't help.
Similar problem I found here: http://www.androidpit.com.br/forum/...o-para-lollilop-da-erro-mesmo-sem-root/page/2
In my CWM log there was also something like:
Package expects build fingerprint of motorola/condor_retbr_ds/condor_umtsds:4.4.4/KXC21.5-40/49:user/release-keys or motorola/condor_retbr_ds/condor_umtsds:5.1/LPC23.13-34.8/12:user/release-keys; this device has Motorola/omni_condor/condor:4.4.2/KOT49H/eng.bigbiff.20140616.171951:eng/test-keys.
Click to expand...
Click to collapse
So the problem is "omni_condor" fingerprint of a device. Is it a different hardware then all other versions?
The fingerprint is also checked in update-script:
run_program("/tmp/install/bin/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
Click to expand...
Click to collapse
I can remove that lines and try to install system, but I don't want to brick it.
Any ideas? Do I need special version of CWM/TRWP or just need to "fix" update-script and it should work ok?
Official twrp causes problem with nougat ROMs ! Try squid twrp ( http://www.mediafire.com/file/ca3rjwh43qbzmw5/twrp-condor-3.0.2-r5.img ) and if you want to flash gapps then you should flash pico gapps .
xterm1 said:
Phone was replaced by Motorola to a new device - after motherboard bug. A new device is UK version.
I have unlocked it and installed recovery, but I can't install any rom - I've tried with CWM and TRWP (2 different versions).
Every try ends up with "ERROR 7". In error logs:
I've tried with:
aokp_condor_mm_nightly_2017-01-16
AospExtended-v3.1-condor-20170124-0102-OFFICIAL
lineage-14.1-20170119-UNOFFICIAL-condor
I found a solution for "Error 7" (remove first lines from update-script) but it doesn't help.
Similar problem I found here: http://www.androidpit.com.br/forum/...o-para-lollilop-da-erro-mesmo-sem-root/page/2
In my CWM log there was also something like:
So the problem is "omni_condor" fingerprint of a device. Is it a different hardware then all other versions?
The fingerprint is also checked in update-script:
I can remove that lines and try to install system, but I don't want to brick it.
Any ideas? Do I need special version of CWM/TRWP or just need to "fix" update-script and it should work ok?
Click to expand...
Click to collapse
Flash stock lollipop and then flash mm or n
vinithv said:
Official twrp causes problem with nougat ROMs ! Try squid twrp ( http://www.mediafire.com/file/ca3rjwh43qbzmw5/twrp-condor-3.0.2-r5.img ) and if you want to flash gapps then you should flash pico gapps .
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash stock lollipop and then flash mm or n
Click to expand...
Click to collapse
Stock 5.1 with TRWP 3.0.2-r5 and still "error 7". It seems to be problem with fingerprint.
Looks like the only way to do it is to edit update-script and remove fingerprint check.
UPDATE/EDIT
After removing fingerprint check everything works ok - I can flash rom and it is working ok. Problem solved.
xterm1 said:
Stock 5.1 with TRWP 3.0.2-r5 and still "error 7". It seems to be problem with fingerprint.
Looks like the only way to do it is to edit update-script and remove fingerprint check.
UPDATE/EDIT
After removing fingerprint check everything works ok - I can flash rom and it is working ok. Problem solved.
Click to expand...
Click to collapse
I face the same issue.. Which line should be removed from the below
getprop("ro.build.fingerprint") == "motorola/condor_retaildsds/condor_umtsds:4.4.4/KXC21.5-40/46:user/release-keys" ||
getprop("ro.build.fingerprint") == "motorola/condor_retaildsds/condor_umtsds:5.0.2/LXC22.46-32/30:user/release-keys" ||
abort("Package expects build fingerprint of motorola/condor_retaildsds/condor_umtsds:4.4.4/KXC21.5-40/46:user/release-keys or motorola/condor_retaildsds/condor_umtsds:5.0.2/LXC22.46-32/30:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
While flashing In my Redmi Note 3
I get Error E3004 : This Rom is for kenzo,kate and your device is .
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz help
mohsiin4u said:
While flashing In my Redmi Note 3
I get Error E3004 : This Rom is for kenzo,kate and your device is .
Plzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzzz help
Click to expand...
Click to collapse
Update recovery.
Androbots said:
Update recovery.
Click to expand...
Click to collapse
Currently i am on zcx recovery. If i update i should have to formate data of mobile including internal storage too
mohsiin4u said:
Currently i am on zcx recovery. If i update i should have to formate data of mobile including internal storage too
Click to expand...
Click to collapse
Damn ZCX is very old around 2years.... Update to TWRP and if u rae coming from Miui then yes u need to format data not wipe and then flash rom and gapps
I'm having the same Issue, I had it before when upgrading from RR Marshmallow to Nougat
Here's what fixed it
Extract your your RR Zip,
Navigate to META-INF\com\google\android\
open the updater-script in a text editor (I prefer wordpad)
The first line should be something like this:
Code:
"assert(getprop("ro.product.device") == "kate" || getprop("ro.build.product") == "kate" || getprop("ro.product.device") == "kenzo" || getprop("ro.build.product") == "kenzo" || abort("E3004: This package is for device: kate,kenzo; this device is " + getprop("ro.product.device") + "."););"
Delete it, save the file and zip up the folder again and try flashing.
It didn't work going from Nougat to Oreo though, I'm still trying to figure out why.
Will try what Androbots said, I'm on TWRP 3.1.1, will update to newer one now
Hi Guys and Gals,
I have an bricked device of a Colleague.
His Wif updated an Acer A3-A40 and the battery died midway through.
Now the device is won't boot and is stuck on the Bootlogo.
I tried to update via SD-Card using latest official ROM OS_Acer_RV09RC01.WW.GEN1_A60M_A.zip. The installation always aborts.
Then I tried to format the device and flash another ROM via SPFlash Tool (ver. 5.2xxx) and modified a Scatter File.
But i always get error 4032 when i use the File. Can someone help me please?
I attached the File from the Update and my modified one.
It could be a bad file your trying to update with. Delete files and redownload file. https://forum.xda-developers.com/android/general/acer-ax-b1-t2875894/page135 firmware
dk0dave said:
It could be a bad file your trying to update with. Delete files and redownload file. https://forum.xda-developers.com/android/general/acer-ax-b1-t2875894/page135 firmware
Click to expand...
Click to collapse
Yeah.
You were right. It's an Update for the wrong tablet. I extracted the update Script and found, that the File was for the "asgardHD". Not for the "jetfireHD". But the File you linked is the same, that i had already.
Can I just change the Name inside the Script?
Sorry for being noob.
Greetings
Right one as it is mentioned on the Tab:
ui_print("Target: acer/a3-a40_ww_gen1/acer_jetfirefhd:6.0/MRA58K/1469171623:user/release-keys");
show_progress(0.750000, 0);
Click to expand...
Click to collapse
The one in the File:
getprop("ro.product.device") == "acer_asgardfhd" || abort("E3004: This package is for "acer_asgardfhd" devices; this is a "" + getprop("ro.product.device") + "".");
ui_print("Target: acer/B3-A40fhd_ww_gen1/acer_asgardfhd:7.0/NRD90M/1498008836:user/release-keys");
Click to expand...
Click to collapse
Push
give this link a try. I'm not sure if it will work... its a 50/50
http://global-download.acer.com/GDFiles/OS/OS/OS_Acer_AV0M0.RV03RC04.WW.GEN1_A60M_A.zip?acerid=636068469259919265&Step1=TABLET&Step2=ICONIA%20TAB%2010&Step3=A3-A40&OS=ALL&LC=en&BC=ACER&SC=PA_6