i am new to custom rom flashing and while flashing lineage OS to my redmi 4 (indian variant) it came up with this error. this package is for santoni deivces, this is a "" device. can someone help me with that? thanks
if are you definitely sure that you have redmi 4x device then unzip archive, find META-INF/com/google/android/updater-script, delete first string which contains ` "assert(getprop("ro.product.device") == "santoni" || getprop("ro.build.product") == "santoni" || abort("E3004: This package is for device: santoni; this device is " + getprop("ro.product.device") + ".");" `
ucollider said:
if are you definitely sure that you have redmi 4x device then unzip archive, find META-INF/com/google/android/updater-script, delete first string which contains ` "assert(getprop("ro.product.device") == "santoni" || getprop("ro.build.product") == "santoni" || abort("E3004: This package is for device: santoni; this device is " + getprop("ro.product.device") + ".");" `
Click to expand...
Click to collapse
can i just simply unzip the rom, do the modifications as told by you and then again simply zip it. Will the zip be flashable then?
Dcentvlogger said:
can i just simply unzip the rom, do the modifications as told by you and then again simply zip it. Will the zip be flashable then?
Click to expand...
Click to collapse
Of course, besides it just code prevention to make sure you had the exact firmware. Just remove those line if you sure your phone is redmi 4x (santoni), it's safe and it'll work like a charm.
Related
Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?
swe.rider said:
Hi guys, please take a minute to help a fellow Sony fan out...
I managed to unlock bootloader via flashtool, root and install recovery as on istux's guide http://forum.xda-developers.com/showthread.php?t=2798411
But when I try to flash DirtyUnicorns_Unofficial_Tsubabsa_build2, it tells me..."This package is for LT25i Tsubasa devices; this is a mint."!
I don't know if this is related at all, but when I try to wipe the cache, it says "failed to unmount /cache"
Why does it think it is a "mint" (whatever that is) and how do I fix this?
From being stuck in recovery after wiping data, the only thing I can do is flash stock 4.3 FTF (9.2.A.2.5) again using flashtool. Is there a better way out of this?
Click to expand...
Click to collapse
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.
Antiga Prime said:
If you're completely sure you're installing the correct ROM for your phone, then you need to use 7zip to open the ROM zip file (Open Archive) and navigate to "\META-INF\com\google\android\" and extract the "updater-script" file. Edit it with Notepad++ (or use Linux, do not use Windows notepad) and delete the first command:
Code:
assert(getprop("ro.product.device") == "lt29i" || getprop("ro.build.product") == "lt29i" ||
getprop("ro.product.device") == "hayabusa" || getprop("ro.build.product") == "hayabusa" ||
getprop("ro.product.device") == "LT29i" || getprop("ro.build.product") == "LT29i" || abort("This package is for \"lt29i,hayabusa,LT29i\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
The example above is from a ROM for a TX. Yours should similar.
The first line of the script should start with:
Code:
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/System", "/system");
Save the file and re-add it to the ROM zip file, replacing the previous updater-script, then you can connect your phone to your PC and use ADB to push the file back to the sdcard on the phone.
Also, if you only wiped /data, then you could just reboot, wait for Android to start up and copy the file normally. Then reboot back to recovery and reflash. On the other hand, if you wiped /system, ADB is your only option, unless you want to reflash a stock FTF.
I'm pretty sure this is because the command checks the phones build.prop to see if the device/product matches certain strings that identify your device, but apparently they don't always match.
Click to expand...
Click to collapse
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?
swe.rider said:
Antiga, thank you very much, I actually succeeded by following your advice from post #10 here http://forum.xda-developers.com/showthread.php?t=2581336
I wiped everything but just restored a nandroid backup I made in recovery before wiping and that worked when i needed to copy different files after things went wrong with the flash.
Would there be any problem caused by not being able to unmount /cache during wiping?
Click to expand...
Click to collapse
You're welcome. It's happened to me before, never known why, but after flashing a different ROM you can always try wiping /cache again; it generally works.
Well as I see people asking this, I thought I'll just make a thread about this issue which is pretty simple to solve.
The reason why you got this issue may be caused by flashing some Roms( such as installing Rizal's Roms' CWM Backup versions )
If you accidentally brick your device, please don't blame on me, as it's you deciding to do this.
Well anyway, here's how you get rid of this:
1. Open your Rom's Zip file with Winrar or 7zip (or something similar)
2. Navigate to "[Your Rom Name].zip\META-INF\com\google\android" and you'll see a file called "updater-script"
3. Open the file with any file editor such as Notepad++ and remove the following lines
Code:
assert(getprop("ro.product.device") == "LT25i" ||
getprop("ro.build.product") == "LT25i" ||
getprop("ro.product.device") == "tsubasa" ||
getprop("ro.build.product") == "tsubasa" ||
abort("This package is for device: LT25i,tsubasa; this device is " + getprop("ro.product.device") + "."););
4. Save the file and close the editor, and the zip manager should automatically save the file back into the zip
5. Now flash the Rom and flash it, and it should work now.
P.S. You don't have to do this to every Rom you're going to flash, just do this when the problem occurs.
I can not install any current ROM, Lineage 14 - Viper OS - Ressurection 5.8.4, always gives the error 7 [Patching system unconditionally
E1001: Failed to update system image. ] currently use the RR 5.8.0 android 6.0, my cell phone is the Moto G2 LTE XT1078 (THEA) image of the event> https://imgur.com/a/jRZkT
Do you have the newest TWRP? https://dl.twrp.me/thea/
yes, I tested all versions, 3.1.1-0 to 3.0.0-0, they all gave the same error
pabli24 said:
Do you have the newest TWRP? https://dl.twrp.me/thea/
Click to expand...
Click to collapse
yes, I tested all versions, 3.1.1-0 to 3.0.0-0, they all gave the same error
Are you sure you are using one for thea? If not, then do get it from here (I am using it on my XT1072):
https://dl.twrp.me/thea/twrp-3.2.1-0-thea.img.html
Reboot to fastboot (shut down, then pwr+vol up for 5 seconds then release) and plug your phone to a PC with mfastboot.
then execute in a copy of mfastboot the following command:
mfastboot flash recovery twrp-3.2.1-0-thea.img
Click to expand...
Click to collapse
Now take your phone and choose "Normal Powerup", then interrupt the boot and get again to fastboot, this time choose "Recovery".
You should be booting TWRP right now.
Now wipe /cache, /data, /storage, dalvik and /system.
Now flash CyanogenMod/AOKP/Carbon/AOSPA/LineageOS or any other custom ROM (optional: flash GApps of the same Android version afterwards to get Google support)
Now wipe /cache, /data and dalvik
Finally, reboot to system.
Not working? Make sure your bootloader is unlocked. Still not working and unlocked? Flash the stock ROM and try again.
Fixed the 7 TWRP error problem on the
Moto G2 LTE XT1078?
I'm having the same problem, I did not find a solution
Same problem. Managed to unlock bootloader, flash recovery, cannot flash any rom due to error 7. Any ideas?
Gupalupa123 said:
I can not install any current ROM, Lineage 14 - Viper OS - Ressurection 5.8.4, always gives the error 7 [Patching system unconditionally
E1001: Failed to update system image. ] currently use the RR 5.8.0 android 6.0, my cell phone is the Moto G2 LTE XT1078 (THEA) image of the event> https://imgur.com/a/jRZkT
Click to expand...
Click to collapse
So, if you're still looking for a solution, I can give you one, but stupid... You need to download the TWRP backup for XT1068 and install it.
https://forum.xda-developers.com/moto-g-2014/general/moto-g-indian-xt1068-marshmellow-6-0-t3313148
Al least the phone will work, but you'll also face some problems like laggy auto-rotation (the picture will be upside down in landscape mode) and also you'll have 2 SIM cards (XT1072 has only one sim card slot)
That means we should ask someone to make a backup of stock firmware (or at least stable LineageOS firmware) and restore it with TWRP.
Please, if anyone still has this phone (XT1072) on stock or any other firmware which WORKS make a backup and upload it to the internet.
:good::good:IT WOULD BE REALLY COOL, BECAUSE A LOT OF PEOPLE HAVE THIS PHONE AND THEY CAN'T FLASH ANY ROM WITH ERROR 7!!!:good::good:
A photo of succesfully restored device:
https://photos.app.goo.gl/shNVhtpJP4x432Sm6
Thank you.
Possible solution for error 7
in my case for moto e i opened the flashable zip with winrar, go to meta-inf/com/google/android and opened update-script with notepad++ and delete the first lines, in my case i deleted these
assert(getprop("ro.product.device") == "titan" || getprop("ro.build.product") == "titan" || getprop("ro.product.device") == "titan_umts" || getprop("ro.build.product") == "titan_umts" || getprop("ro.product.device") == "titan_udstv" || getprop("ro.build.product") == "titan_udstv" || getprop("ro.product.device") == "titan_umtsds" || getprop("ro.build.product") == "titan_umtsds" || getprop("ro.product.device") == "titan_retaildsds" || getprop("ro.build.product") == "titan_retaildsds" || getprop("ro.product.device") == "XT1068" || getprop("ro.build.product") == "XT1068" || getprop("ro.product.device") == "XT1064" || getprop("ro.build.product") == "XT1064" || getprop("ro.product.device") == "XT1063" || getprop("ro.build.product") == "XT1063" || getprop("ro.product.device") == "XT1069" || getprop("ro.build.product") == "XT1069" || abort("E3004: This package is for device: titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4886" || getprop("ro.bootloader") == "0x4887" || abort("This package supports bootloader(s): 0x4882, 0x4883, 0x4886, 0x4887; this device has bootloader " + getprop("ro.bootloader") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
and rom is actually flashing
GuestD0668 said:
in my case for moto e i opened the flashable zip with winrar, go to meta-inf/com/google/android and opened update-script with notepad++ and delete the first lines, in my case i deleted these
assert(getprop("ro.product.device") == "titan" || getprop("ro.build.product") == "titan" || getprop("ro.product.device") == "titan_umts" || getprop("ro.build.product") == "titan_umts" || getprop("ro.product.device") == "titan_udstv" || getprop("ro.build.product") == "titan_udstv" || getprop("ro.product.device") == "titan_umtsds" || getprop("ro.build.product") == "titan_umtsds" || getprop("ro.product.device") == "titan_retaildsds" || getprop("ro.build.product") == "titan_retaildsds" || getprop("ro.product.device") == "XT1068" || getprop("ro.build.product") == "XT1068" || getprop("ro.product.device") == "XT1064" || getprop("ro.build.product") == "XT1064" || getprop("ro.product.device") == "XT1063" || getprop("ro.build.product") == "XT1063" || getprop("ro.product.device") == "XT1069" || getprop("ro.build.product") == "XT1069" || abort("E3004: This package is for device: titan,titan_umts,titan_udstv,titan_umtsds,titan_retaildsds,XT1068,XT1064,XT1063,XT1069; this device is " + getprop("ro.product.device") + ".");
assert(getprop("ro.bootloader") == "0x4882" || getprop("ro.bootloader") == "0x4883" || getprop("ro.bootloader") == "0x4886" || getprop("ro.bootloader") == "0x4887" || abort("This package supports bootloader(s): 0x4882, 0x4883, 0x4886, 0x4887; this device has bootloader " + getprop("ro.bootloader") + ".");
ifelse(is_mounted("/system"), unmount("/system"));
and rom is actually flashing
Click to expand...
Click to collapse
Nope. That's just not working for me...
P.S
I'm still waiting for a proper backup for XT1072 and it will help to restore this phone. So... Please, somebody make a backup!
Hey Guys,
i managed to root, unlock the bootloader and install the twrp recovery.
Now i have the problem that i can't install any custom rom.
This is the code:
E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "z3"
E: unknown command [log]
Installing zip file....
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/carbon-cr5.1.zip'
I also deleted the assert commando line in the updater-script file of the carbon rom.
Still doesn't work.
How can i install a custom rom?
Am i missing something?
TWRP-Version: 3.0.2.0
Android-Version: 6.0.1 Build-Number: 23.5.A.1.291
Thank you for your help
Now i erased the getprob lines in the update-script.
These are the lines i deleted:
(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" ||
getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" ||
getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" ||
getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries") || abort("E3004: This package is for "D5803,D5833,z3c,aries" devices
this is a "" + getprop("ro.product.device") + "".");
Now i get this error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing zip file.
I have the same problem. Not sure what to do?
Edit: Updating TWRP solved my issue. (Went from 3.0.2 to This one)
Btw, if you are on Linux and fastboot is giving you an error, check "fastboot --version" to see which you are on. I was on 29.0.2 and had to do a system update to get 29.0.4 before I could install this ROM.
I have h870, i unlocked its bootloader, installed twrp, then rooted it. I then tried to flash the pixel experience rom through twrp recovery, however its fails and gives error: this rom is for h870 lucye. Now the phone has no os and is stuck on lg g6 logo.
How can i fix this?
Reboot in recovery mode and try flashing another ROM (or if you have a backup of the previous one, try restoring backup)
5warafat1 said:
I have h870, i unlocked its bootloader, installed twrp, then rooted it. I then tried to flash the pixel experience rom through twrp recovery, however its fails and gives error: this rom is for h870 lucye. Now the phone has no os and is stuck on lg g6 logo.
How can i fix this?
Click to expand...
Click to collapse
don't use the official twrp, use orangefox recovery
To avoid the error, go into
(ROM ZIP)/META-INF/com/google/android/updater-script
and delete these lines
Code:
assert(getprop("ro.product.device") == "g6" || getprop("ro.build.product") == "g6" ||
getprop("ro.product.device") == "lucye" || getprop("ro.build.product") == "lucye" ||
getprop("ro.product.device") == "h870" || getprop("ro.build.product") == "h870" ||
abort("E3004: This package is for device: g6,lucye,h870; this device is " + getprop("ro.product.device") + "."););
or if you don't want to delete too much, just delete the "abort" line.
Hope this helps
Use orange recovery project and try flashing another ROM like havocOS.