Hellow. I have a problem. Could you help me? I have Nozomi RC1 and when I want to instal RC0-2 in CWM error sign comes up:
Installing /sdcard/cm10....
Finding...
Opening...
Instaling...
Assert failed: getprop("ro.product. device") == "LT26i" getprop ("ro.product.device")...
....
...
E:Error in /sdcard/cm-10....
Status 7
Installation aborted.
Help
Remove that from the script file in the zip.. It has been mentioned a couple of times in the CM thread.. If this does not help then search that forum.. You could also have luck in changing the lt26i to Nozomi
Sent from my LT26i using xda app-developers app
Thread closed as per OP request.
Whenever I try to install a custom d2tmo ROM from XDA on my T999v GS3, I get this error:
assert failed: getprop("ro.build.product") == "d2tmo"
E:Error in /emmc/_Download/pa_d2tmo-2.52-27OCT2012-163709.zip
(status 7)
What do I need to do to fix this? I've tried using both TWRP and CWM with the same result. Also I've formated the phone and still no positive results.
moving to right section. I suggest to use search function. Regards,
You need to change your build.prop to reflect a t999, you either flashed a rom from a different section or a Google wallet fix that changed your build.prop probably
Sent from my SGH-T999 using Tapatalk 2
bfranklin1986 said:
You need to change your build.prop to reflect a t999, you either flashed a rom from a different section or a Google wallet fix that changed your build.prop probably
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
How do i do this! sorry, im to new to rooting
Search. Reading is the foundation of knowledge.
They call me "Jelly" cuz jam don't shake like this!
Download ROM manager. Install clockwork.
I'm pretty good at this stuff, but I wouldn't be running the latest cm10 nightly on an island if I hadn't given koush his 5 dollars.
Better than editing build prop
Sent from my SGH-T999 using xda premium
Android_Monsters said:
Download ROM manager. Install clockwork.
I'm pretty good at this stuff, but I wouldn't be running the latest cm10 nightly on an island if I hadn't given koush his 5 dollars.
Better than editing build prop
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
ive already tried this and it didnt work
Hi, I tried to install Evervolv ICS on my LG P350 but I got error:
Code:
assert failed: getprop("ro.product.device) == "p350" || getprop("ro.build.product") == "p350"
E:Error in /sdcard/evervolv--2.2.0 - p350.zip
(Status 7)
Installation aborted.
Note: I have wiped all data/cash/dalvik case before I tried to flash rom.
Thanks in advance
You should post in Evervolv's thread so that the respective dev can help you.
Try an updated version of recovery...
Sent from my Xperia Neo V using xda app-developers app
If ur getting error 'status 7' means rom not downloaded properly. Re-download and check rom size original n downloaded. Also check md5 is same.
Sent from my LG-P500
@ankitshankar, I can't post there because I don't have 10 post's so I have to do it here
@Attitude.SSJ, I am using CWM 5 if I remember correctly, but I don't think that that is problem because I install other rom's without any problem
@pmvyas, I also thought about that, but I downloaded it two times, and both showing same error... I'll try to download it again tomorrow and try
Thanks all for answering
Try cwm 6 once...
Sent from my Xperia Neo V using xda app-developers app
I uploaded a fix ;D
I have had the same problem
---------- Post added at 07:02 PM ---------- Previous post was at 06:51 PM ----------
https://docs.google.com/file/d/0Bygk3Qc8L1O3VUQ0WUlNRWVoLWM/edit
thx man, I'll try it as soon you allow me to download file xD
AW: [Q] Error while installing "Evervolv" ROM
Ogi_Kifla said:
thx man, I'll try it as soon you allow me to download file xD
Click to expand...
Click to collapse
No Problem
Gesendet von meinem LG-P350 mit Tapatalk 2
pmvyas said:
If ur getting error 'status 7' means rom not downloaded properly. Re-download and check rom size original n downloaded. Also check md5 is same.
Sent from my LG-P500
Click to expand...
Click to collapse
OMG...status 7 mean that the META-INF folder is not cmpatible change it with a working rom for this device (CM9-CM7) etc
Hi, i have some trouble.
I had install CyanogenMod 10.1.3 on my Galaxy Nexus (maguro), and all work fine.
Now i will try AICP 3.0 (http://forum.xda-developers.com/showthread.php?t=2493380&page=5).
As usual i download the .zip, and i put it on virtual sd.
I start phone at recovery mode, i wipe chache, davlik, clean system.
Then i try to install zipp from sd, but he crash
"
Finding update package..
Opening update package..
Installing update...
assert failed: getprop("ro.product.device") =="gruoper" || getprop("ro.product.device") =="tilapia" || getprop("ro.product.device") =="gruopertilapia"
Installation aborted."
Somone have some idea?
It's strange that he try to update, maybe i forgot do something..
That's because that ROM is not for a gnex its for another device "grouper" which I think its a nexus 7 tablet.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Esteway.619 said:
That's because that ROM is not for a gnex its for another device "grouper" which I think its a nexus 7 tablet.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well.. thanks.. I found it here http://forum.xda-developers.com/showthread.php?t=1792896 but in general doc, not on gNext specific...
And, if i may ask, what rom you use?
Lord_Gorthan said:
Well.. thanks.. I found it here http://forum.xda-developers.com/showthread.php?t=1792896 but in general doc, not on gNext specific...
And, if i may ask, what rom you use?
Click to expand...
Click to collapse
I use my port of miui but right now I'm on cm10.2 with some kitkat addons.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Just started learning this stuff about a month ago. Decided to use my Infuse and Captivate as sacrificial phones to learn on before I do anything on my S3. I have been successful with rooting the Infuse and Captivate along with installing several custom roms on each.
A couple of weeks ago I sucessfully rooted my S3 which had the AT&T 4.3 OTA update on it. I rooted using this method by Loxla http://forum.xda-developers.com/showthread.php?t=2562802.
I have enjoyed the advantages of a rooted S3. Now I would like to install a custom rom on this S3. In consideration of the bootloader dangers, what are my options for installing a custom rom?
Many thanks. And thanks to Loxla for a successful root.
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
kevinga said:
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
Click to expand...
Click to collapse
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
kevinga said:
Maybe I need to rephrase my question. I rooted my S3 AFTER I did the 4.3 AT&T OTA update. What ROM's can I flash from this point forward? Any rom that is based on 4.3 or higher? I understand that there is an issue if the bootloader is downgraded. But what about going UP? I have done extensive searching on this scenario but can't come up with an answer.
Thanks.
Click to expand...
Click to collapse
You could try Dandroid 5, its 4.3 touchwiz with asop looks.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kevinga said:
Just started learning this stuff about a month ago. Decided to use my Infuse and Captivate as sacrificial phones to learn on before I do anything on my S3. I have been successful with rooting the Infuse and Captivate along with installing several custom roms on each.
A couple of weeks ago I sucessfully rooted my S3 which had the AT&T 4.3 OTA update on it. I rooted using this method by Loxla http://forum.xda-developers.com/showthread.php?t=2562802.
I have enjoyed the advantages of a rooted S3. Now I would like to install a custom rom on this S3. In consideration of the bootloader dangers, what are my options for installing a custom rom?
Many thanks. And thanks to Loxla for a successful root.
Click to expand...
Click to collapse
I answered this question in a different thread here.
dntesinfrno said:
I answered this question in a different thread here.
Click to expand...
Click to collapse
Thanks for the reply and the link. Could I install the Beanstalk 4.4 rom? I can't find any information regarding the bootloader. Here is the link to the rom http://forum.xda-developers.com/showthread.php?t=2485628
Cooro said:
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
Click to expand...
Click to collapse
I am assuming that you rooted AFTER you did the 4.3 OTA?
Cooro said:
For me, I used cyanogenmod 10.2 d2att stable rom and it flashed successfully with twrp recovery. My phone was a samsung s3 i747m and it had android 4.3 OTA update and it was also rooted.
Click to expand...
Click to collapse
I thought once someone updated to 4.3, installing custom recovery would crash the device?
I know Verizon and at&t are different, I was just curious.
Sent from my SCH-I535 using XDA Premium 4 mobile app
No, custom recovery won't brick your phone. Just trying to downgrade the boot loader will.
To the OP, most custom ROMs do not change the boot loader. If know of no ROM that changes the boot loader when you install thru recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
indymx said:
No, custom recovery won't brick your phone. Just trying to downgrade the boot loader will.
To the OP, most custom ROMs do not change the boot loader. If know of no ROM that changes the boot loader when you install thru recovery.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
Click to expand...
Click to collapse
So could I flash a 4.4 ROM? I miss cm 11.
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
So could I flash a 4.4 ROM? I miss cm 11.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Certainly, the only potential road block would be the bootloader assert in the updater script. If the list of acceptable bootloader's doesn't include MJB then it wont flash. The updater script is located under \META-INF\com\google\android in the rom zip. Here is a sample of the code :
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
If your bootloader isn't listed you can either add a new line for it to add it to the check, or delete the entire segment. Be warned that this will force and/or skip the check and go straight into installing the ROM regardless of the bootloader on your device, do so at your own risk. From what i've read the only functional difference between MJB and the earlier bootloaders is the addition of the Qfuse disallowing bootloader downgrading, adding the warranty bit counter, and implementing KNOX support in the security chain of trust so it shouldn't be a big deal but just sayin.
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 06:07 PM ---------- Previous post was at 06:05 PM ----------
dntesinfrno said:
Certainly, the only potential road block would be the bootloader assert in the updater script. If the list of acceptable bootloader's doesn't include MJB then it wont flash. The updater script is located under \META-INF\com\google\android in the rom zip. Here is a sample of the code :
assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");
assert(getprop("ro.bootloader") == "I747UCDLK3" ||
getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747MVLDLK4" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MUMBLK3" ||
getprop("ro.bootloader") == "I747MUMBLL1");
If your bootloader isn't listed you can either add a new line for it to add it to the check, or delete the entire segment. Be warned that this will force and/or skip the check and go straight into installing the ROM regardless of the bootloader on your device, do so at your own risk. From what i've read the only functional difference between MJB and the earlier bootloaders is the addition of the Qfuse disallowing bootloader downgrading, adding the warranty bit counter, and implementing KNOX support in the security chain of trust so it shouldn't be a big deal but just sayin.
Click to expand...
Click to collapse
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
OK thanks, I'm not real comfortable getting in to code just yet I'm still learning.
I just didn't want to brick my phone, I couldn't care less about the KNOX warranty or whatever. I'm due for a new phone in a few months anyway.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I've installed CM11.. I had minor issues going back to stock after, but installing CM11 on top of the OTA 4.3 boot loaders is no problem.
indymx said:
I've installed CM11.. I had minor issues going back to stock after, but installing CM11 on top of the OTA 4.3 boot loaders is no problem.
Click to expand...
Click to collapse
Awesome! Thanks, I really wanted to know if anyone out there had done successfully. Will it make a big difference since I'm on Verizon?
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
Awesome! Thanks, I really wanted to know if anyone out there had done successfully. Will it make a big difference since I'm on Verizon?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Shouldn't.. CM11 doesn't change the boot loader.
I've heard good things about the CM11 version for your phone. I'm not happy with it on mine, but my buddy who's got a Verizon S3 says it runs great on his.
indymx said:
Shouldn't.. CM11 doesn't change the boot loader.
I've heard good things about the CM11 version for your phone. I'm not happy with it on mine, but my buddy who's got a Verizon S3 says it runs great on his.
Click to expand...
Click to collapse
Its great. I was on cm11 before I lost all good sense and updated to stock 4.3.
Sent from my SCH-I535 using XDA Premium 4 mobile app
XXDroidZillaXX said:
Its great. I was on cm11 before I lost all good sense and updated to stock 4.3.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
There are some things in TW I like.. Like the calendar app.. I love that thing.. But, there are features of CM11 that rock too..
The camera in CM11 on ATT S3 sucks balls. TW's is a lot better. I use Nova Launchers, So the interface is mostly the same. And I'm currently running without any of the bloat. Also, TW has emoji working right.. I don't think CM11 does.
Minor issues true, but still..
The major issue I had with CM11 is the battery. CM11 took forever to charge, and would only charge with the screen off. They may have fixed that by now, but I'm thinking I'll wait a bit before I try again. It's too much hassle to get back to 4.3 Stock TW for me to want to try it too quickly.
indymx said:
There are some things in TW I like.. Like the calendar app.. I love that thing.. But, there are features of CM11 that rock too..
The camera in CM11 on ATT S3 sucks balls. TW's is a lot better. I use Nova Launchers, So the interface is mostly the same. And I'm currently running without any of the bloat. Also, TW has emoji working right.. I don't think CM11 does.
Minor issues true, but still..
The major issue I had with CM11 is the battery. CM11 took forever to charge, and would only charge with the screen off. They may have fixed that by now, but I'm thinking I'll wait a bit before I try again. It's too much hassle to get back to 4.3 Stock TW for me to want to try it too quickly.
Click to expand...
Click to collapse
I agree about the camera on CM.. It sucks. That is my only real issue.
How difficult was it to return to stock?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Well, its not horrible. Just have to have a nandroid backup plus a backup of all of your app data.
When I booted up after restoring my nandroid, I got a million FC's. Only good way out of it was a reset.
Sent from my SAMSUNG-SGH-I747 using XDA Premium HD app
So far the latest nightly of CM11 is pretty good.. Camera is working as good as stock, battery seems to charge normally, and no other oddities.. I'll keep my eye on it for a day or so and see how it goes. No fancy calendar, but I can live with that.