[Q] assert failed getprop ro.product.device - Xperia Play Q&A, Help & Troubleshooting

I have SE X Play with Doomkernel with android 2.3.4 and build no .42 and baseband version -56.
When i try to flash Darkforest RC2 rom via recovery i get following error.
asset failed: getprop ro. product. device
I have ClockWorkMod Recovery 5.0.2.6 installed
Please help me
YES I AM A NOOB

Either flash a stock rom first or open the .zip, find the update script and delete the get prop line
Sent from my R800i using Tapatalk

stock rom??
Sorry for stupid question but what exactly is a stock rom? I mean my play shipped with android 2.3.2, then i got 2.3.4 on OTA update.
So to install this rom i shoud go back to 2.3.2??
Also where to find stock roms for X play? I searched android dev forum but could only find latest firmwares.
Could you please provide a link for stock rom
Thanks in advance.

AndroHero said:
Either flash a stock rom first or open the .zip, find the update script and delete the get prop line
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone

startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
I'm having the same problem on my r800x. Some help would be greatly appreciated!
I just recently unlocked my bootloader, and I can still flash kernels in fastboot. It's just that every time I try to install a custom rom I get either the Status 7 "getprop." error, or when I remove the .prop lines from the update script I get installation aborted. I also can not get into recovery from any of the custom kernels. I have had to boot into CWM using fastboot every time.

startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
What did you use to edit the update script? Try notepad+ if you use windows, the script has to be formatted for linux.
Sent from my R800i using Tapatalk

AndroHero said:
What did you use to edit the update script? Try notepad+ if you use windows, the script has to be formatted for linux.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Tried this, and it still doesn't work. Maybe I did it wrong? :/

PandaPropaganda said:
Tried this, and it still doesn't work. Maybe I did it wrong? :/
Click to expand...
Click to collapse
Just to clarify that I think he meant use notepad++ the + wasn't a typo. So don't use notepad but instead use notepad + +
Sent from my R800i using Tapatalk

fma965 said:
Just to clarify that I think he meant use notepad++ the + wasn't a typo. So don't use notepad but instead use notepad + +
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I know. Still doesn't work.
EDIT: I fixed it! Not only do you need notepad++, but you also have to EDIT the archive and not extract it then re-zip it. The archive software I had (PeaZip) wouldn't let me do this so I had to install 7zip. I'm uploading my edited update.zip for r800x's (based on fxp054) right now.

PandaPropaganda said:
I know. Still doesn't work.
EDIT: I fixed it! Not only do you need notepad++, but you also have to EDIT the archive and not extract it then re-zip it. The archive software I had (PeaZip) wouldn't let me do this so I had to install 7zip. I'm uploading my edited update.zip for r800x's (based on fxp054) right now.
Click to expand...
Click to collapse
um is this for a update.zip yh? i always extract them and repack them and it works fine. although this was on my old phone. are you sure you didn't do something different?

fma965 said:
um is this for a update.zip yh? i always extract them and repack them and it works fine. although this was on my old phone. are you sure you didn't do something different?
Click to expand...
Click to collapse
Sorry your right i did mean notepad++ there should be no issue unpacking the rom, as long as you repack it as a .zip, i use winrar and never had issues
Sent from my R800i using Tapatalk

AndroHero said:
Sorry your right i did mean notepad++ there should be no issue unpacking the rom, as long as you repack it as a .zip, i use winrar and never had issues
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
When I made .zip archives with PeaZip they never worked. I had also tried previously with the archiving utility IZArc to no avail. I installed 7zip and after making the .zip using that it fixed the problem. I'm just saying that may help for some who have has the same problems as me. Particularly with the r800x users. The .zip I put on my other post (and now this one --- in the reason for editing) has all the .prop lines removed from the update script and should work for anybody who has a r800x with an unlocked bootloader (providing you've installed the custom kernel, of course).

PandaPropaganda said:
When I made .zip archives with PeaZip they never worked. I had also tried previously with the archiving utility IZArc to no avail. I installed 7zip and after making the .zip using that it fixed the problem. I'm just saying that may help for some who have has the same problems as me. Particularly with the r800x users. The .zip I put on my other post (and now this one --- in the reason for editing) has all the .prop lines removed from the update script and should work for anybody who has a r800x with an unlocked bootloader (providing you've installed the custom kernel, of course).
Click to expand...
Click to collapse
Cool nice work
Sent from my R800i using Tapatalk

You can find the file in ./META-INF/com/google/android/updater-script

Thank you so much, you fixed my Galaxy Note with the simple deletion of a few lines.

startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse
I am having the same issue on my Xperia Arc, where can i find the update script to remove the equivalent lines?
Thanks
Andrew

Do not do this!
I am not sure how other people are having success with this suggestion, but please do not do it. This code must be doing a proper check because I followed the advice and removed the assert. Next thing you know the installation proceeded and messed up. I hard bricked my phone. Yes hard brick, not a soft brick that you can recover from, the hard brick that makes your phone a brick. Just a warning.
startherecca said:
I deleted the following from the update script.
HTML:
assert(getprop("ro.product.device") == "R800i" || getprop("ro.build.product") == "R800i" || getprop("ro.product.board") == "R800i" ||
getprop("ro.product.device") == "R800a" || getprop("ro.build.product") == "R800a" || getprop("ro.product.board") == "R800a" ||
getprop("ro.product.device") == "R800at" || getprop("ro.build.product") == "R800at" || getprop("ro.product.board") == "R800at" ||
getprop("ro.product.device") == "zeus" || getprop("ro.build.product") == "zeus" || getprop("ro.product.board") == "zeus");
Now when i try to flash via recovery again installation is aborted. No getprop error btw Just following error.
opening package..
installation aborted.
Help me out someone
Click to expand...
Click to collapse

It searches for specific lines onto build.prop, but having that check after wiping /system, and so erasing your build.prop will result into an error. Deleting those lines in the updater-script will only let you skip that check, but there's no way to brick unless you flash a rom that wasn't meant for your phone or a different kernel.

Related

[Q] My arc has changed to LT18a? Can't apply new update :(

Hi guys...
I was trying to install a new update (the cm7.2 fxp 116) but it failed and now my phone won't boot...
i've tried to install the fxp113 image and then apply that update, but I keep getting this message:
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||...
It continues to write a lot of these, all with == "LT18i" and "LT18a", but then a couple of lines down, it starts to write == "LT15i" instead...
Finally, it gives me an error saying "E:Error in /sdcard/A-IMAGES/cm72fxp113/update-cm-7.2.0-RC1-anzu-KANG-signed_fxp113.zip"
(status 7)
installation aborted
Please help me...
hjalte81 said:
Hi guys...
I was trying to install a new update (the cm7.2 fxp 116) but it failed and now my phone won't boot...
i've tried to install the fxp113 image and then apply that update, but I keep getting this message:
assert failed: getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||...
It continues to write a lot of these, all with == "LT18i" and "LT18a", but then a couple of lines down, it starts to write == "LT15i" instead...
Finally, it gives me an error saying "E:Error in /sdcard/A-IMAGES/cm72fxp113/update-cm-7.2.0-RC1-anzu-KANG-signed_fxp113.zip"
(status 7)
installation aborted
Please help me...
Click to expand...
Click to collapse
open the cm7.zip file, and go META-INF/com/Google/android/
and open update-script file with notepad++
delete the line
assert(getprop("ro.product.device") == "LT18i" || getprop("ro.build.product") == "LT18i" ||
getprop("ro.product.device") == "LT18a" || getprop("ro.build.product") == "LT18a" ||
getprop("ro.product.device") == "LT15i" || getprop("ro.build.product") == "LT15i" ||
getprop("ro.product.device") == "LT15a" || getprop("ro.build.product") == "LT15a" ||
getprop("ro.product.device") == "anzu" || getprop("ro.build.product") == "anzu");
save and replace it
install with cwm
Sent from my Xperia Arc
Hi Kes,
The problem was that the file I had downloaded was corrupted :/
I restored from an older backup, downloaded the file again (and again...) and got a working file.
Thanks anyway

CyanogendMOD 10 FXP Neo V haida

Installing: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
assert failed: getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" || getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" || getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
E:Error in /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
What steps will reproduce the problem?
bt4777 said:
Installing: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
assert failed: getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" || getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" || getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida"
E:Error in /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
What steps will reproduce the problem?
Click to expand...
Click to collapse
dude go to META-INF/com/google/android and extract updater-script of the zip file (u downloaded i.e ROM )and open extracted updater-script with Notepad++(for download notepad++ google it) there after delete first three line and save.there after zip it to the rom(META-INF/com/google/android) from where u extracted
Press thank if i helped u
cyanidekiller said:
dude go to META-INF/com/google/android and extract updater-script of the zip file (u downloaded i.e ROM )and open extracted updater-script with Notepad++(for download notepad++ google it) there after delete first three line and save.there after zip it to the rom(META-INF/com/google/android) from where u extracted
Press thank if i helped u
Click to expand...
Click to collapse
which are the first three lines? begins and ends where
bt4777 said:
which are the first three lines? begins and ends where
Click to expand...
Click to collapse
assert(getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida");
delete these 3 lines
Press thanks if i helped u
cyanidekiller said:
assert(getprop("ro.product.device") == "MT11i" || getprop("ro.build.product") == "MT11i" ||
getprop("ro.product.device") == "MT11a" || getprop("ro.build.product") == "MT11a" ||
getprop("ro.product.device") == "haida" || getprop("ro.build.product") == "haida");
delete these 3 lines
Press thanks if i helped u
Click to expand...
Click to collapse
trying this now. will get back with the results in 5 mins
edit: didnt work:
symlink: some symlinks failed
E:Error in /sdcard/FXP133-cm-10-20120813-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
Did you try with CWM 6?
I had this problem with CWM 5 so i used the boot.img in the RAR of the cyanogenmod i.e. extracted it to android tools folder
then used the command
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
So it booted on CWM 6 and installation was done without any issues.
If you want to reproduce the problem, try installing CM10 with CWM 5.
What version of CWM to use so i can install FXP137?
5.0.2.7 , 5.5.0.4 or 6.0.1.0 and from where to download it and install it for Neo V (MT11i - haida)? I understand that 5.0.2.7 is for GB, 5.5.0.4 works with ICS and now i see that 6 is recommended for JB... Please advise me, it will be helpfully if you give me a link, i have search on a lot of threads and read all this NoobGuide but the version presented is 5.0.2.7 also i have rooted and unlocked my bootloader using testpoint method. Thanks in advance.

[SOLVED] Unable to install custom ROMs on Xperia S

Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.
just delete the error text on updater-script on android floder on your zip flashable rom
I have already had this error
Cht0in3 said:
just delete the error text on updater-script on android floder on your zip flashable rom
I have already had this error
Click to expand...
Click to collapse
I've accesed the updater-script. Now can you tell me which text to remove from there?
sirius_gamer said:
I've accesed the updater-script. Now can you tell me which text to remove from there?
Click to expand...
Click to collapse
Check this
http://forum.xda-developers.com/showthread.php?t=1607135
Sent from my LT26i using Tapatalk 2
sirius_gamer said:
I've accesed the updater-script. Now can you tell me which text to remove from there?
Click to expand...
Click to collapse
The first 2 lines generally that say about get prop
Or flash advanced stock kernel then try flash
Sent from my 4.2.2 Xperia S via Tapatalk
Ben36 said:
The first 2 lines generally that say about get prop
Or flash advanced stock kernel then try flash
Sent from my 4.2.2 Xperia S via Tapatalk
Click to expand...
Click to collapse
These are the updater-script of two different ROMs. Can you tell me exactly which lines to delete?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone?
Sent from my LT26i using Tapatalk 2
sirius_gamer said:
Anyone?
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
I saw your post, but really don't know.
Never had that problems, have you tried to flash different kernel then ROM?
Or extract kernel from this and tried to flash with PC.
Sent from my LT26i using Tapatalk 2
sirius_gamer said:
Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.
Click to expand...
Click to collapse
Check the md5 hash..
Redownload. Looks like a bad download to me..
Sent from The Beauty - Xperia S
-Harsh- said:
Check the md5 hash..
Redownload. Looks like a bad download to me..
Sent from The Beauty - Xperia S
Click to expand...
Click to collapse
You're right, we forgot md5.
I'm guessing he already tried different ROM's or download again that MIUI.
If not, then you know for the future.
Always check your downloaded file, that's the first thing you need to check.
Sent from my LT26i using Tapatalk 2
Maybe you should try to wipe everything, then flash new kernel, then the rom ( clean install ). Download the file again, to make sure they are proper!
or may check you build.prop file on the current rom to see if the asserted lines match those in updater-script
Did anyone had that kind of problem on MIUI 5 thread?
If no, then you doing something wrong.
If this ROM is made for XS, then it should work without editing any file (if should OP would said).
Re-download zip, check md5 or just flash other JB kernel then flash MIUI.
Sent from my LT26i using Tapatalk 2
---------- Post added at 09:50 AM ---------- Previous post was at 09:49 AM ----------
******
And please, write results.
You opened this thread and you should "close it".
Sent from my LT26i using Tapatalk 2
Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'
sirius_gamer said:
Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'
Click to expand...
Click to collapse
You cannot convert a zip into a ftf file. Only Sony can build .sin files
sirius_gamer said:
Nothing's working. If anyone can tell me how to convert a zip file to ftf then I can try flashing through Flashtool. I've also tried renaming the file from .zip to .ftf using Total Commander but Flashtool is giving error while preparing files. The only ROM that I've managed to flash successfully is this: http://forum.xda-developers.com/showthread.php?t=2102798 The one with build '6.1.A.2.55'
Click to expand...
Click to collapse
You can't do that, what could you do and I already said that.
Find different kernel and flash that or just extract boot.img and flash that via fast boot.
Command:
fastboot flash boot boot.img
Then flash ROM
Sent from my Xperia S using Tapatalk 2
funky0308 said:
You can't do that, what could you do and I already said that.
Find different kernel and flash that or just extract boot.img and flash that via fast boot.
Command:
fastboot flash boot boot.img
Then flash ROM
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
Problem solved! I was missing the step in which we have to flash boot.img Thanks alot bro :')
sirius_gamer said:
Problem solved! I was missing the step in which we have to flash boot.img Thanks alot bro :')
Click to expand...
Click to collapse
Sent from my Xperia S using Tapatalk 2
sirius_gamer said:
Hey guys I've an Xperia S. I've rooted it, installed CWM recovery on it, unlocked the bootloader, then wiped cache partition and dalvik cache and also the data but im getting this error everytime I try to install a custom ROM:
-- Installing: /sdcard/MIUIv5_3.3.29_nozomi.zip
Finding update package...
I:Update location: /sdcard/MIUIv5_3.3.29_nozomi.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" ||
getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
assert failed: getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" || getprop("ro.product.device") == "LT26ii" || getprop("ro.build.product") == "LT26ii" || getprop("ro.product.device") == "LT26" || getprop("ro.build.product") == "LT26" || getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi"
E:Error in /sdcard/MIUIv5_3.3.29_nozomi.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUIv5_3.3.29_nozomi.zip")
Dont know whats this 'status 7' is. Please help! I've tried many ROMs many times but none working.
Click to expand...
Click to collapse
Hello,You need to upgrade you cwm recovery.Then try to flash ok!
tania247260 said:
Hello,You need to upgrade you cwm recovery.Then try to flash ok!
Click to expand...
Click to collapse
Thanks but the problem has been solved already
Sent from my Xperia S using Tapatalk 2

[Q] Baseband 10.1

I have a S3 with Virgin Canada,I747-baseband "I747MVLLH1" , currently running 4.1.2 CM nightly. I went to update to the CM 10.1 d2att stable today and it gives me error 7 ro.bootloader .I have the most updated recovery.So I opened the rom and in the check sequence my baseband is not there ?
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
So does that mean d2att is no longer good for my phone,,thats the last rom I used was the d2att? or could I edit it to put my baseband in?
Thanks alot
Flash the latest jb stock rooted Rom for your phone ( I747M, right?). Use Rom manager or goo manager to install recovery. Flash cm.
I already have a recovery on and I'm running CM 10. The problem is when I try to update to the 10.1 Stable that just came out I get an Error 7 because my baseband is not in the status check before it loads the rom,what I would like to know could I just add the line
"getprop("ro.bootloader") == "I747MVLLH1" || into the below code? thanks
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
Frost5555 said:
I already have a recovery on and I'm running CM 10. The problem is when I try to update to the 10.1 Stable that just came out I get an Error 7 because my baseband is not in the status check before it loads the rom,what I would like to know could I just add the line
"getprop("ro.bootloader") == "I747MVLLH1" || into the below code? thanks
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
Click to expand...
Click to collapse
Your bootloader is out of date.
There are multiple threads on how to do it and will have the necessary files.
Sent from my SGH-I747M using xda app-developers app
Thanks KorGuy123, I'll read up on updating the bootloaderu

Unable to install cyanogenmod 12.1

Hi!
I just aquired a Samsung Galaxy S4 Mini GT-9195 this week and got stuck at installing CyanogenMod 12.1.
TWRP 2.8.7.0 samsunggalaxys4mini64bit is up and running.
Next i tried to install the official builds serranoltexx (first stable, then nightly) and i got this error message:
This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is serranoveltexx.
E: Error flashing zip 'cm-12.1-*.zip'
I'm not quite sure what is going on right now. Did the devs just forget to add this deviceName to their updater-script, or is there a reason for this?
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" || getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" || getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + ".");
If there's no chance or it's at least veary unlikle the smartphone gets damaged i'll just try to add this rule manually.
Any help appreciated
Nuke
Nukesor said:
Hi!
I just aquired a Samsung Galaxy S4 Mini GT-9195 this week and got stuck at installing CyanogenMod 12.1.
TWRP 2.8.7.0 samsunggalaxys4mini64bit is up and running.
Next i tried to install the official builds serranoltexx (first stable, then nightly) and i got this error message:
This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is serranoveltexx.
E: Error flashing zip 'cm-12.1-*.zip'
I'm not quite sure what is going on right now. Did the devs just forget to add this deviceName to their updater-script, or is there a reason for this?
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" || getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" || getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" || getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for device: serranolte,serranoltebmc,serranoltektt,serranoltexx; this device is " + getprop("ro.product.device") + ".");
If there's no chance or it's at least veary unlikle the smartphone gets damaged i'll just try to add this rule manually.
Any help appreciated
Nuke
Click to expand...
Click to collapse
Your phone is the new GT-I9195I ''serranoveltexx''
Currently, there is no custom ROMs for this device because of its different specs.
Please refer to this thread for more explanations : http://forum.xda-developers.com/galaxy-s4-mini/general/galaxy-s4-mini-plus-t3041208

Categories

Resources