Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This is a build of AICP for the Shield Tablet (WiFi Only) (wx_na_wf)
You need to have CWM recovery installed on your device See Here for instructions install CWM. Try this version of CWM when flashing
Or use PhilZ
Instructions on installing:
Make a backup of your current ROM (Optional but highly recommended)
Wipe --> Factory Reset (Data, Cache, and Dalvik Cache)
Flash ROM
Flash Gapps
Reboot
Downloads:
8/28/14 ROM
8/25/14 ROM
8/23/14 ROM
8/22/14 ROM
Gapps
Bugs
You tell me
Kernel Source
XDA:DevDB Information
AICP for Shield Tablet (WiFi Only), ROM for the Nvidia Shield Tablet
Contributors
joshuabg, Unjustified Dev For making the device tree compatible
ROM OS Version: 4.4.x KitKat
Based On: AOKP
Version Information
Status: Testing
Created 2014-08-22
Last Updated 2014-12-20
Reserved
Reserved
OK I done a full wipe factory reset/cache in the latest recovery then tryed flashing had an error saying
This package is wx_na_wf this device is shield tablet
Error status 7
I'm not much of a dev but will look through the build prop or meta data to see if its a simple name change?
MRobbo80 said:
OK I done a full wipe factory reset/cache in the latest recovery then tryed flashing had an error saying
This package is wx_na_wf this device is shield tablet
Error status 7
I'm not much of a dev but will look through the build prop or meta data to see if its a simple name change?
Click to expand...
Click to collapse
Just got to edit the META-INF/com/google/android/updater-script
proably have to change wx_na_wf to shieldtablet in line 2
I can do it and reupload the whole zip f you want
Edit: You could just erase that line
joshuabg said:
Just got to edit the META-INF/com/google/android/updater-script
proably have to change wx_na_wf to chield tablet in line 2
I can do it and reupload the whole zip f you want
Click to expand...
Click to collapse
That's OK I can do that give me 10 mins
MRobbo80 said:
That's OK I can do that give me 10 mins
Click to expand...
Click to collapse
OK, just edit the updater script, you should be able to just delete the second line without an issue.
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
MRobbo80 said:
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
What happened when you deleted the second line? It might be easier if you join the IRC channel so I can walk you though everything.
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
So it should look like this
").");
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || abort("This package is for \"shieldtabley\" devices; this is a \"" + getprop("ro.product.device") + "\".");
MRobbo80 said:
Deleted second line and did not have any luck so this second line below just change
"wx_na_wf" to ,"shieldtablet "
").");
assert(getprop("ro.product.device") == "wx_na_wf" || getprop("ro.build.product") == "wx_na_wf" || abort("This package is for \"wx_na_wf\" devices; this is a \"" + getprop("ro.product.device") + "\".");
So it should look like this
").");
assert(getprop("ro.product.device") == "shieldtablet" || getprop("ro.build.product") == "shieldtablet" || abort("This package is for \"shieldtabley\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Click to expand...
Click to collapse
What happened when you flashed this?
Says
Installing
Installation aborted
MRobbo80 said:
Says
Installing
Installation aborted
Click to expand...
Click to collapse
Do you have zip signature verification checked?
No I did not, now I enabled that I tried flashing the original rom it seems to start of by going through the normal process of flashing, then stalls with the first error message to start with. When I change the second line (name change) in the update script to (shieldtablet) it the gives me an error saying the footer is in correct when trying to flash. Think it is a very simple fix to get this going but having a dipstick trying to help you is not much kop sorry m8
Hold on think I know what I done
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
I'll upload that tommorow.
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
My ROM is made for wx_na_wf. The bad thing about that is that aicp checks to see if the device is a wx_na_wf before it flashes. The stock os shows the device is a shieldtablet. So you have to remove that line in the updater-script.
sorry man got it sort of working got it to flash but stuck in a boot loop, now I can not enter recovery or so far get adb working
Here's my recovery.img that generated with AICP (wx_na_wf)
https://s.basketbuild.com/filedl/devs?dev=joshuabg&dl=joshuabg/wx_na_wf/recovery.img
Unjustified Dev said:
@joshuabg You have to upload your recovery.img that compiled with it. I changed name because we shouldn't be using shieldtablet name in custom roms that's common to all versions.
Click to expand...
Click to collapse
https://s.basketbuild.com/filedl/devs?dev=joshuabg&dl=joshuabg/wx_na_wf/recovery.img
Related
I would prefer to ask this in the [ROM][NIGHTLY] CyanogenMod 7.2-RC3+ for Huawei U8150 (June 11th) thread but I can't post in there since I am a noob.
I have a Huawei Ideos U8150 which I bought from aldi, locked to the virgin mobile network.
Today I decided to try and install a third-party firmware to get extra performance, because as stock the phone is very sluggish and drives me bonkers. Well... I have been at it for hours and have run into a hurdle that I can't get over. Hence me posting here.
I've tried with three different builds of Cyanogenmod 7.2, one build from june, the latest build, and the stable build.
I've tried to follow the instructions in the above mentioned thread as close as possible, had to do it slightly differently since I can't figure out how to
access the phone after doing the 3-button combo (some Android 1.0 driver I need to install, googled it, nothing specific to my phone).
I downloaded and installed z4root, and successfully obtained root access.
I duplicated the problem just before for the purposes of this post, attempting to install the Cyanogenmod 7.2 stable build.
I downloaded and installed clockworkmod rom manager, opened it, pressed Flash ClockworkMod Recovery to install that, and I think this might be part of my problem, it says: Confirm Phone Model and the only option is Huawei U8160, I figure close enough.
Let it do its thing, pops up with the root access confirmation screen, I hit Allow, then it says successfully flashed clockworkmod revoery! I hit OK, then I hit reboot into Recovery.
I let it do a backup, then I do wipe data/factory reset as well as wipe cache partition as per the above mentioned thread (except doing it inside clockwork recovery instead of doing it using the 3 button method), then hit install from sdcard zip, hit choose zip from sdcard, browse to the cyanogenmod zip file (cm-7.2.0-u8150.zip), say Yes, and it ****s itself. Great, I wiped all my data, now I have to set my phone up again from scratch with the stock rom. Grrrr!
The important part of the log:
Code:
-- Installing: /sdcard/cm-7.2.0-u8150.zip
mtd: successfully wrote block at fffffd6800000000
I:Set boot command "boot-recovery"
Finding update package...
I:Update location: /sdcard/cm-7.2.0-u8150.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "u8150" || getprop("ro.build.product") == "u8150" || getprop("ro.product.board") == "u8150" ||
getprop("ro.product.device") == "ideos" || getprop("ro.build.product") == "ideos" || getprop("ro.product.board") == "ideos" ||
getprop("ro.product.device") == "U8150" || getprop("ro.build.product") == "U8150" || getprop("ro.product.board") == "U8150"
assert failed: getprop("ro.product.device") == "u8150" || getprop("ro.build.product") == "u8150" || getprop("ro.product.board") == "u8150" || getprop("ro.product.device") == "ideos" || getprop("ro.build.product") == "ideos" || getprop("ro.product.board") == "ideos" || getprop("ro.product.device") == "U8150" || getprop("ro.build.product") == "U8150" || getprop("ro.product.board") == "U8150"
E:Error in /sdcard/cm-7.2.0-u8150.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/cm-7.2.0-u8150.zip")
I have put the whole log into a pdf as well as a doc and attached it.
In one of my several attempts to do this, I made sure I ran the "Fix Permissions" tool before trying to install the ROM in the hope that would make it work but it made no difference (same error).
I have no idea what I've done wrong, it seems like I have done everything correctly but it just won't work because it hates me. Maybe it's because it is a Virgin Mobile phone, maybe it is because clockworkmod thinks it is a U8160 when it is really a U8150? Who knows.
Hopefully somebody can think of some trick I can apply to try and get around this issue.
Sorry for such a long post, I just wanted to make sure I was as thorough as possible to make sure there isn't some tiny little thing I am doing wrong that is screwing it up for me.
Should I try installing Cyanogenmod 6.x.x tomorrow to see if it likes that any better?
Should I try downgrading to an earlier version of Clockworkmod ROM manager (if that is even possible)?
Is there some other straight-forward way of installing Cynaogenmod on my phone other than Clockworkmod?
Thanks very much,
VirginIdeos
CWM 5.0.2.7 used.
recruit said:
CWM 5.0.2.7 used.
Click to expand...
Click to collapse
So, I have to use an earlier version of clockwork mod? It's easy to install the latest version, but were do I download an earlier version from? Or are you just posting this for information?
Bump: Got it working. You have to flash Clockworkmod recovery version 3.0.2.7 onto the device, the latest will not work with the U8150 (should work with the U8160). I will throw up a how-to when I have enough posts.
But I'm still having issues: WiFi does not work, even though it is supposed to be fixed in Cyanogenmod 7.2. This is a pity, because it means I won't be able to stream video from my helmet cam to my Ideos without using the stock software pre-installed on the Ideos, which is very very sluggish. It already took me a lot of frigging around to be able to download the app for this from google play.
There is a wifi fix here: http://forum.xda-developers.com/showthread.php?t=1177650 but the link to download Salsa Slide Final is no longer active (I'm not sure that the files would work with the Ideos anyway) AND the wifi fix flashable zip won't work because it requires an early version of clockwork mod recovery which will not work on the Ideos U8150. ARGH!! And I'm not sure that the zip would flash correctly onto the Ideos anyway. The only way this could work would be for someone to update the zip so it works with clockworkmod recovery 3.0.2.7, and port the changes to the Ideos (if need be). Beyond my abilities, especially the porting part!
Even more frustratingly, there are people who are posting in the CM 7.2 Ideos U8150 thread whose wifi seems to be working just fine. Blast them!
Bump:
If I had known CWM9 was out for the U8150, I would not have even bothered with 7.2.
So I've installed CWM9 on my Ideos. Everything works great, including WiFi , so I'm rapt. It is a little more sluggish than 7.2 in some respects, but much smoother and snappier in others, and the UI and startup screen are a lot cooler.
As an aside, the ActionConnect app for connecting an Android phone to the new Ego 727 helmet camera doesn't work fully with the U8150. I can connect with the app and change the camera's settings, but when trying to view the live stream, the app exits. I had to trick the Google servers into thinking I had a Samsung Galaxy S in the first place to be able to download the app (even tricking them into thinking I had a Nexus S did not work). I've contacted tech support about this and the compatibility list issue. I'll throw up a separate thread including the APK for those who are having trouble downloading the app.
I assume at least half of Android users get Error status 7 while flashing ROMs. This can be explained in 2 reasons.
Number 1:The developer of the ROM was too stupid to fix this mistake
Click to expand...
Click to collapse
or
Number 2: You are tying to port a ROM and those errors come to you
Click to expand...
Click to collapse
So lets start fixing Status 7.
This can happen because the ROM isn't meant for your device. To fix this extract the ROM open META-INF com google android updater-script with Notepad++Find the line assert(getprop("ro.product.device") == "device namer" || getprop("ro.build.product") == "devicename" ||. Change the device name to the name of your device. Example change assert(getprop("ro.product.device") == "flyer" || getprop("ro.build.product") == "flyer" || to assert(getprop("ro.product.device") == "grouper" || getprop("ro.build.product") == "grouper" ||
Click to expand...
Click to collapse
If you don't know Grouper is the code name for the nexus 7. So you need to find the code name for your device. It can be found easyly on the web.
And that's it. Hope i helped. leave a tnx or donate if I helped.
Ok, here's whats going on. I have a Galaxy S 4G (t959v) with TWRP recovery installed.
And it wont let me upgrade (or downgrade) to any other ROM than SlimBean.
I was on SlimICS trying to goto RemICS v1.2, because i couldnt get root and my USB port is broke,
(i use a wall battery charger to charge the 4 batteries i have for it, in case you were wondiering)
but it wouldn't let me install it, so i decided to go with (try) SlimKat and see if that would work,
but no its not working either. i've tried 4 different ROMs, none will install, finally i tried SlimBean 3.1.0 and it worked.
I am now on the rom named "Slim-3.1.0-GalaxyS4G-20130128-0043-UNOFFICIAL.zip"
it is the only rom that would install. and i still cant install any other rom. not even downgrade back to SlimICS.
Can anyone help me out?
ROM History of my T959V.
Stock Froyo>Stock GingerBread>Rooted Stock GingerBread>Installed CWM>Rooted SlimICS build 1>(forgot password, so i had to reset)>(Some how) Not-Rooted SlimICS build 1>(tried updating to different ROMs (none working)>(installed TWRP)>( ROMs still not working)>(Finally got one to work) SlimBean 3.1.0
UPDATE*
I was just able to update to "SlimSaber-galaxys4gmtd-4.4.2-20140320.zip" but still no others.
Basically it will only let me update to "Slim" ROMs and only in firmware order. (SlimICS>SlimBean>SlimSaber)
As you've run into, each ROM "says" what phone type it is in a "property" that is built into the ROM. That includes the recovery that is part of the ROM you flash. Each ROM zip file generally includes a list of "acceptable" phone types that the ROM will run on. If what your current recovery thinks you are (according to the last-flashed ROM build) isn't on the list of what the new ROM wants, it won't flash.
For example, if your current ROM is an "aries" ROM and you are trying to flash one that is for "herring, T959V, T959W, SGH-T959V, SGH-T959W, galaxys4g, galaxys4gmtd" then you can't flash it.
While the ICS ROMs were generally pretty good about this, some of the JB and KK ROMs are a little sticker. You sort of have to find a path that works for you (or learn how to tear apart a ROM zip and change the asserts).
Edit -- as a hint for the adventurous
Code:
BeanStalk-4.4.275-20140401-galaxys4gmtd$ head META-INF/com/google/android/updater-script
assert(getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries" ||
getprop("ro.product.device") == "galaxys4g" || getprop("ro.build.product") == "galaxys4g" ||
getprop("ro.product.device") == "galaxys4gmtd" || getprop("ro.build.product") == "galaxys4gmtd" ||
getprop("ro.product.device") == "SGH-T959V" || getprop("ro.build.product") == "SGH-T959V" ||
getprop("ro.product.device") == "SGH-T959W" || getprop("ro.build.product") == "SGH-T959W" || abort("This package is for \"aries,galaxys4g,galaxys4gmtd,SGH-T959V,SGH-T959W\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Mobiletechvideo, 35 bucks for a new usb port.
champ1919 said:
Mobiletechvideo, 35 bucks for a new usb port.
Click to expand...
Click to collapse
I had the same problem (USB port broken) a few months ago...called T-Mobile and asked if they could repair it...they did better than that...sent me a new phone.
Q&A for [ROM] [5.0] Samsung Galaxy S3 [d2usc][Nightly] LiquidSmooth Lollipop
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [5.0] Samsung Galaxy S3 [d2usc][Nightly] LiquidSmooth Lollipop. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
htrowpiks said:
First!... Androidfilehost says need to sign in and I don't have access to the folder....
Click to expand...
Click to collapse
Maybe they are working on a new nightly build.
liquidsmooth on d2mtr
@vuzedroid
I tried to answer your question in the liquidsmooth thread, but I get directed here because I have less than 10 posts. Anyways, I hope you see this...
I have this rom installed on my d2mtr. It works well, but I loose audio every once in a while and just have to reboot to get it back. Also install open camera if you need the camera.
Here's how to install it on the d2mtr. I recommend the 02/08 build since it has the cm theme engine instead of layers...
Unzip the package and open the "updater script" and change the "assert" line at the top from this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || abort("This package is for device: d2usc,d2lte; this device is " + getprop("ro.product.device") + "."););
To this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || getprop("ro.product.device") == "d2mtr" || getprop("ro.build.product") == "d2mtr" || abort("This package is for device: d2usc,d2lte,d2mtr; this device is " + getprop("ro.product.device") + "."););
Then zip it back up and wipe then flash the rom and gapps. I used the PA Pico gapps.
Before rebooting use the file manager in twrp recovery and go to "/system/priv-app" and delete "cmsetupwizard" then you can reboot. If you don't delete it then it will keep crashing during initial setup and not let you get to the home screen. That's it enjoy.
GameTheory. said:
@vuzedroid
I tried to answer your question in the liquidsmooth thread, but I get directed here because I have less than 10 posts. Anyways, I hope you see this...
I have this rom installed on my d2mtr. It works well, but I loose audio every once in a while and just have to reboot to get it back. Also install open camera if you need the camera.
Here's how to install it on the d2mtr. I recommend the 02/08 build since it has the cm theme engine instead of layers...
Unzip the package and open the "updater script" and change the "assert" line at the top from this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || abort("This package is for device: d2usc,d2lte; this device is " + getprop("ro.product.device") + "."););
To this...
Code:
assert(getprop("ro.product.device") == "d2usc" || getprop("ro.build.product") == "d2usc" || getprop("ro.product.device") == "d2lte" || getprop("ro.build.product") == "d2lte" || getprop("ro.product.device") == "d2mtr" || getprop("ro.build.product") == "d2mtr" || abort("This package is for device: d2usc,d2lte,d2mtr; this device is " + getprop("ro.product.device") + "."););
Then zip it back up and wipe then flash the rom and gapps. I used the PA Pico gapps.
Before rebooting use the file manager in twrp recovery and go to "/system/priv-app" and delete "cmsetupwizard" then you can reboot. If you don't delete it then it will keep crashing during initial setup and not let you get to the home screen. That's it enjoy.
Click to expand...
Click to collapse
I just noticed this message, thanks a ton! I think I can do all this xD I'll let you know once I try :good:
Unable to start camera after resotring backup
Hi,
I have install your ROM and it's nice but have some bugs. specially volume. It does not reduce volume to lower level. In min. level it is too loud. So I decided to revert. I reverted my old OS backup, after that my primary camera is unable to start. I thought it might have some issue so tried different ROM, But camera won't work.
I tried Open Camera, it says
FAILED TO OPEN CAMERA.
CAMERA MAY BE IN USE
BY ANOTHER APPLICATION?
Front camera is working with Open Camera application. Standard camera application stops by saying "camera failed".
Is there any hardware damage.
Please help me out. I am stuck.
LiquidSmooth Lollipop GApps zip file
Hello and thank you for the Lollipop ROM for the US Cellular SGS3! I've been having fun playing with that today. One question, however: when I download the GApps zip file from the drdrvs website:
drdevs.com
devs
teamliquid
Gapps
lollipop
gapps-L-2-25-15.zip
(Sorry, new members can't post outside URLs...)
unzip claims that it's not a complete archive:
$ unzip -l gapps-L-2-25-15.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
I've attempted to download it several times, just to make sure my browser isn't truncating the file. The downloader page says it's 10.9MB, which jives with ls:
10887168 Apr 10 14:44 gapps-L-2-25-15.zip
Thought you might want to check it out on your end.
Grouchicarpo
Dark UI
How do I find and enable the dark ui? I am coming from SlimKat and loved that darkness it had.
I am on LS-LP-v4.1-2015-05-14-liquid_d2usc version of LiquidSmooth.
Also, Mobile network WORKS FINE, but it complains about not having an APN and won't send MMS messages....
LiquidSmooth d2usc
I too eagerly await an update for my GSIII on USCellular. This phone runs Lollipop really well. My only real complaint is the long boot time on LiquidSmooth and the resultant (unsettling) looping of the boot animation.
Thanks Orion116
I just wanted to say thanks and for all your hard work on the quickly dying d2usc or all usc variants. I currently have the "LS-LP-v4.1-2015-05-14-liquid_d2usc" from the liquidsmooth website. Is this the most recent update?
يريد ت
(Galaxy) A32 tabs3 tabs7+
=(sm-a325n, sm-t820, sm-t976n)
These things and method
Thank you
What do you want exactly?
the way to find it.
for every device.
(thank you!)
Starwars8k said:
the way to find it.
for every device.
(thank you!)
Click to expand...
Click to collapse
Settings/about phone...
Do you mean a database of model numbers for all Androids?
no.
asserts like qssi
Assets? Inventory of devices that you own?
it is the helpful thing to not flash the different device's rom.
thank you
You can't flash a wrong rom.
If the build number doesn't match, the flash gets aborted.
Please read some tutorials about it.
matze19999 said:
You can't flash a wrong rom.
If the build number doesn't match, the flash gets aborted.
Please read some tutorials about it.
Click to expand...
Click to collapse
Worth to mention this is true only for odin.
Now a days it's really hard to hard break device but commonest cause that can easily hard brick device is flashing wrong/corrupt bootloader with twrp.
I never recommend anyone to use twrp to flash bootloader with twrp
Oh, asserts. They are not literally "assert".
They are found in update zips under META-INF/com/google/android/updater-script:
Code:
(!less_than_int(1651066150, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Wed Apr 27 21:29:10 CST 2022) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "Poke3" || abort("E3004: This package is for \"Poke3\" devices; this is a \"" + getprop("ro.product.device") + "\".");
They check device and version.
dr.ketan said:
Worth to mention this is true only for odin.
Now a days it's really hard to hard break device but commonest cause that can easily hard brick device is flashing wrong/corrupt bootloader with twrp.
I never recommend anyone to use twrp to flash bootloader with twrp
Click to expand...
Click to collapse
(big) thank you
it was really helpful
Renate said:
Oh, asserts. They are not literally "assert".
They are found in update zips under META-INF/com/google/android/updater-script:
Code:
(!less_than_int(1651066150, getprop("ro.build.date.utc"))) || abort("E3003: Can't install this package (Wed Apr 27 21:29:10 CST 2022) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "Poke3" || abort("E3004: This package is for \"Poke3\" devices; this is a \"" + getprop("ro.product.device") + "\".");
They check device and version.
Click to expand...
Click to collapse
(big) thank you
it was really helpful