[Q] LT25i (XV) flashing error - "this is a mint" - Sony Xperia T, TL, TX, V

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.

Related

I bet you cannot solve this problem.

I flashed Koodo/TLS stock Via oiden. And it worked fine. I was able to Root it as well. But when I tried to install CWM, it game me and error.
[email protected] getprop("ro.product.device"
GT-s5570 getprop("product...
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
I've tired CWM 5 & 6. Even the Zip from different places.
Then I unrooted, and tried to root with different root files, This time around it gave me the same error.
I managed to reroot via super one click, yet I am still getting this error trying to install CWM recovery.
I have also tried to connect to Oiden once again and flash the latest stock rom from Sammobile, however the PC detects the download mode, oiden does not.
Good luck solving this one. :good:
Open thr cwm zip file then go to
Meta inf and some folders deeper
Find updater-script
Open it with NOTEPAD++
Then remove the assert prop lines
And rezip the files done
Sent from my ST25i using xda app-developers app
SpaceCaker said:
Open thr cwm zip file then go to
Meta inf and some folders deeper
Find updater-script
Open it with NOTEPAD++
Then remove the assert prop lines
And rezip the files done
Sent from my ST25i using xda app-developers app
Click to expand...
Click to collapse
Assert prop or get prop? Or is it the same? :\
K.A. said:
Assert prop or get prop? Or is it the same? :\
Click to expand...
Click to collapse
Get prop is to get the build.prop to open
And assert prop is to search the lines
Sent from my ST25i using xda app-developers app
So essentially
assert(getprop("ro.product.device") == "GT-S5830L" ||
getprop("ro.product.board") == "GT-S5830L" ||
getprop("ro.build.product") == "GT-S5830L" ||
getprop("ro.product.device") == "GT-S5830B" ||
getprop("ro.product.board") == "GT-S5830B" ||
getprop("ro.build.product") == "GT-S5830B" ||
getprop("ro.product.device") == "GT-S5830T" ||
getprop("ro.product.board") == "GT-S5830T" ||
getprop("ro.build.product") == "GT-S5830T" ||
getprop("ro.product.device") == "GT-S5830" ||
getprop("ro.product.board") == "GT-S5830" ||
getprop("ro.build.product") == "GT-S5830" ||
getprop("ro.product.model") == "GT-S5830"
);
Thank you so much. I Spent 3 hours trying to fix this, and you fixed it in a matter of minutes. It flashed.
Unfortunately, I think something has gone wrong with the Data & Cache part of my phone. It does not mount either in the recovery...That might explain why it wont connect to oidien. Any suggestions?

[Q] Assert failed whenever trying to flash zip

Im getting this error when trying to flash any zip files..
assert failed: getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" || getprop("ro.product.board") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830"
assert failed: getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" || getprop("ro.product.board") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830" || getprop("ro.product.board") == "GT-S5830"
Click to expand...
Click to collapse
things i do before:
- flashing The Ultimatum ROM and edited the build.prop to change the density to 140..
- updating my recovery to CMW 6 and got these error..
what should i do??
please help..
EDIT :
Today it's getting worse, my phone is bootloop now, and i can't flash any zip files, so i can't use my phone at all...
so guys, how to fix it??
(yes, this is my first time posting a thread, sorry for my bad english and thank you for viewing)
What does the last line say it is usually something like status 7 or status x
Sent from my LG-D802 using xda app-developers app
lingarajug said:
What does the last line say it is usually something like status 7 or status x
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
yes, it says "Installer Error (Status 7)"
Maliivers said:
yes, it says "Installer Error (Status 7)"
Click to expand...
Click to collapse
2 options
1. Your sdcard is corrupted >>> back up your data and format it in fat32 file system (use an USB adapter e.g.)
2. The file downloaded is corrupted >>> try to download it again
I advise you to use CWM 5.0.2.6 Fixed insted of CWM 6.x... but... it should work too
Viper The Ripper said:
2 options
1. Your sdcard is corrupted >>> back up your data and format it in fat32 file system (use an USB adapter e.g.)
2. The file downloaded is corrupted >>> try to download it again
I advise you to use CWM 5.0.2.6 Fixed insted of CWM 6.x... but... it should work too
Click to expand...
Click to collapse
- already format my sdcard, still result in error
- already redownload, still error
i'm using CWM 6.0.4.6 and can't flash to CWM 5, because any zip files i flash will result in error.. (oh,except for aroma filemanager, but what can i do with that?)
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
hmm.. it looked like advanced tips.. haha
but i'll try, will post the result later
SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
WOAH, IT WORKED ! THANKS !
(just in case someone else face the same problem) so this is what i did:
edit updater.script in META-INF\com\google\android folder
it looked like this:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
format("ext4", "EMMC", "/dev/block/stl12", "0", "/system");
mount("ext4", "EMMC", "/dev/block/stl12", "/system");
blahblahblah...
Click to expand...
Click to collapse
just delete this line on any zip:
assert(getprop("ro.product.device") == "cooper" || getprop("ro.build.product") == "cooper" ||
getprop("ro.product.device") == "GT-S5830" || getprop("ro.build.product") == "GT-S5830");
Click to expand...
Click to collapse
and you're done.
----------------------------------------------------------------------------------------------------
but, just for fulfill my curiosity, why this error can occur? i used the same zip file days ago and it worked just fine.
SpaceCaker said:
edit updater.script from rom.zip meta inf folder.
its a problem wich happens on lots of devices.
simply remove the 1/3 first lines from assert and rezip the rom
Sent from my S500 using xda app-developers app
Click to expand...
Click to collapse
Win!
Thanks, this worked a treat for me too. I'd installed the CWM 6.0.4.6 for the Gio so i could install KitKat and buggered up my phone, but this has fixed it.

[FAQ]Recovery recognizing "tsubasa" as "mint

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.

Can't install Custom Rom over TWRP [Error 7]

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.

lg g6 stuck on boot

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.

Categories

Resources