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.
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
Hi,
I'm trying to install PAC-MAN ROM on my mobile but i'm a little bit lost with build versions m7, m7att, m7spr, m7tmo, m7ul, m7vzw, m7wls. On my mobile informations with adb ro build project is :
ro.build.project=M7_UL_JB43_SENSE55_MR:338159
So i took the m7ul version. Wipe data/factory reset is okay bit when i flashing, I have an assert failed when he check two properties at the installation. But if i seach this two properties on my mobile information, they seem correct :
It fails at: assert(getprop("ro.product.device") == "m7" || getprop("ro.build.product") == "m7" ||
getprop("ro.product.device") == "m7ul" || getprop("ro.build.product") == "m7ul");
ro.product.device=m7
ro.build.product=m7
I don't know why it dosen't work.
ClockworkMod recovery v6.0.4.6
HBOOT-1.55.000
Here is a solution (sorry but i haven't 10 posts, i can't write an url on my question): androidgadgematic. com/2012/12/fix-custom-rom-installation-status-7.html
But before i want be sure that i must use m7ul version.
This is the HTC one X forum....not the ONE forum !!!
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
Moderator EDIT content removed.
Moderator Information,
Thread closed. Please remember our forum rules. When posting the work of others, please ask for permission first. Also only ROMs built by the person belong in the development forum.
Many thanks,
Stephen