Hi,
Yesterday i tried flashing some custom roms, which result in showing some error messages as mentioned below.
[ "Assert failed: get prop("ro.product.device')
Error in /sdcard /......
(Status 7) ]
"Downloaded all the roms thrice.... the file size was correct"
Now, the model im using is Maguro (GSM Version).., and i downloaded the correct versions from all the Rom's thread. My ClockWorkmod Recovery version is 6.0.0.5.
I usually follows this procedure before flashing:- (I) formats /system,formats /dalvik cache,formats /factory reset, & then flash the appropriate rom.
The Roms i able to flash successfully are Bigxie odexed Rom (4.1.1) & AndroidME GNex v1.4.0 ....
The Roms i'm not able to flash are BAMF Paradigm v2.0, MiNCO v1 & Miui 2.7.20.....(which i eagerly waiting to give a try)
so, its the problem with my phone (may be clockworkmod or something else).
Have anybody face this issue before, if so, how do you overcome this ??
THANKS !!
Will try to update my CWM to 6.0.1.0 and check ...
fairyshacker said:
Hi,
Yesterday i tried flashing some custom roms, which result in showing some error messages as mentioned below.
[ "Assert failed: get prop("ro.product.device')
Error in /sdcard /......
(Status 7) ]
"Downloaded all the roms thrice.... the file size was correct"
Now, the model im using is Maguro (GSM Version).., and i downloaded the correct versions from all the Rom's thread. My ClockWorkmod Recovery version is 6.0.0.5.
I usually follows this procedure before flashing:- (I) formats /system,formats /dalvik cache,formats /factory reset, & then flash the appropriate rom.
The Roms i able to flash successfully are Bigxie odexed Rom (4.1.1) & AndroidME GNex v1.4.0 ....
The Roms i'm not able to flash are BAMF Paradigm v2.0, MiNCO v1 & Miui 2.7.20.....(which i eagerly waiting to give a try)
so, its the problem with my phone (may be clockworkmod or something else).
Have anybody face this issue before, if so, how do you overcome this ??
THANKS !!
Click to expand...
Click to collapse
Typically this happens when the Rom dev alters the build.prop and renames the device, often times this can be remedied by flashing a custom kernel first followed by the rom but you will probably want to post in the particular rom thread to find out which kernel you should flash
You should also check our MD5 sums to make sure there wasnt an error in the download.
- Cheers
Related
I don't have the post count to ask this question so I hope I'm not violating forum rules posting here. As per the title, I'm trying to install the latest nightly of CM10 on my T999v SGS3. I've installed CWM Touch (latest build) and copied the latest nightly to the root of my phone. I then boot into recovery and then factory reset, wipe cache, wipe dalvik cache and then proceed with the installation.
I then get this error.
assert failed: getprop("ro.product.device") == "E:Error in /sdcard/cm-10-20121014-NIGHTLY-d2tmo.zip
(status 7)
Installation aborted.
Would anybody knowledgeable with this be able to direct me to a solution please?
Thanks.
My phone is rooted
My previous ROM was FREEGS3v6 rom with the Trinity Kernel
All I can think of is a bad download. The error it's throwing you says you don't have the correct device/file for the device, so if you have a T-Mobile S3 all I can think of is a bad download.
I have a WIND version so T999v, and after reading the CM10 thread a few WIND users have successfully flashed it. I redownloaded the file but still the same error message.
what recovery are you using? try updating to 6.0.1.2 and try again
It sounds like you have a modified build.prop by the assertion error being thrown. Try flashing another rom first and then reflash cm
Edit: if you want check your build prop and verify that the line ro.product.device has d2tmo as its value
Sent from my SGH-T999 using xda app-developers app
I checked out that value with build prop editor and it was d2can so do I change it to d2tmo or flash another rom first?
I doubt this will be of much help but who knows. I am a tmo S3 user who just rooted and updated to CM10 (cm-10-20121011-EXPERIMENTAL-d2tmo-M2) yesterday. I had the same error that you did but all I did to fix it was update to ClockworkMod v6.0.1.2 and then it installed fine. I doubt the v6.0.1.2 would work but Touch would not. I was just happy that I didn't have to mess with the build.prop or anything else to resolve. Good luck.
X-Nemesis said:
I don't have the post count to ask this question so I hope I'm not violating forum rules posting here. As per the title, I'm trying to install the latest nightly of CM10 on my T999v SGS3. I've installed CWM Touch (latest build) and copied the latest nightly to the root of my phone. I then boot into recovery and then factory reset, wipe cache, wipe dalvik cache and then proceed with the installation.
I then get this error.
assert failed: getprop("ro.product.device") == "E:Error in /sdcard/cm-10-20121014-NIGHTLY-d2tmo.zip
(status 7)
Installation aborted.
Would anybody knowledgeable with this be able to direct me to a solution please?
Thanks.
My phone is rooted
My previous ROM was FREEGS3v6 rom with the Trinity Kernel
Click to expand...
Click to collapse
I had the same problem as you and this is what I did.
I rooter my phone. Am I then install CWM Touch and do the wipes and install CM10 but all this without restart my phone. And this time I did not have the error.
I was having the same problem, so I reverted back to factory stock. Then I rooted my phone and installed cm10 and it worked fine.
So I am an HTC owner but doing some root & ROM work for a friend of mine. Normally, I load a ROM onto the SD card, boot into recovery, wipe, flash zipped ROM from SD card, reboot, enjoy. However, The GS3 I am working on does not recognize the SD card within recovery. Everytime I try to flash a ROM (CM10 & MIUI thus far) none of them work. I get the following when trying to flash:
-- Installing /sdcard/miuiandroid_d2tmo_jb-3.1.11.zip
Finding Update package
Opening update package
Installing Update
assert failed: getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product) == "d2tmo"
E: Error in /sdcard/miuiandroid_d2tmo_jb-3.1.11.zip
(Status 7)
Installation Aborted
Now, this tells me that my download is corrupt somehow. However, I get this exact same message when trying to flash CM10. Furthermore, both ROMs were acquired directly from the dev download links. Has anyone else had a similar problem and can provide a solution?
Update CWM. Link in my signature.
Aerowinder said:
Update CWM. Link in my signature.
Click to expand...
Click to collapse
Wow! I feel like a moron! I use TWRP on my LTEvo so it has been a long time since I've even touched CWM. Looks like the update did the trick. Flashed MIUI and accompanying gapps perfectly! Thank you!
One more question, is there a generic gapps that I can flash across ROMs or no? For instance, I have the gapps that was posted next to MIUI. However, I'd like to see how CM10 runs. Am I able to flash the gapps posted with MIUI or is there a specifically designed gapps file for CM10? I ask because with the Evo gapps are generic and can be interchanged with AOSP ROMs.
I am not exactly sure where things started to go wrong. I just recently installed the latest ROM of Task650's Jellybean 4.2.2
I have been trying to update to the latest ROM and I recieve:
[assert failed: getprop("ro.product.device") == "E: Error in /external_sd/ROMs and Gapps /aokp_JB_4.2.2_d2att-ota-eng.task650-4.26.2013.zip
(Status 7)]
I have looked up the issue and updated the Kernel and updated to the latest CWM and still get the same error.
Another thing I have noticed is that I cannot flash any other ROMs like CyanogenMod or anything
I also noticed in my devices folders, that I basically have mulitple of the same folders in multiple directories... I am not sure if this is from flashing too many times... I have never had this many problems with my device before. I like to have everything updated, which I have been able to do before, but now I can't do anything.
Can I get some advice on what to do?
if you have an i747 (d2att), was that a d2att cwm update you applied? it will say in the updater-script (in the recovery zip) what model it's for.
each time you flash a 4.2.2 ROM you're likely adding the multiple folders. a known issue. follow the link in my signature for some more details on this down in post #2 of that thread. essentially, back everything up (either to a micro sd card or your PC) and perform a full wipe before flash (including /system and /data + /media) to avoid this problem. we'll work on that once you've got this first issue fixed.
Fixed my issue!
I'm guessing I had flashed the wrong CWM:good: for my phone.
Hi everybody!
I feel like giving [ROM][4.2.2 JDQ39 AOSP] Eos4.0 - - Nozomi a go, but there are some things that confuse me with the instructions. I don't want to spam the roms thread with my questions, so i hope that this thread is ok. Here we go:
Currently i am on stock JB, but if i need to there is no problem with downgrading and rooting. My BL is unlockable, but i will not do it until i am actually ready to install the rom.
1) "MAKE SURE YOU HAVE THE LATEST 4.2.2 COMPATIBLE RECOVERY." - How do i know which one is?
2) "Going to EOS4.2.x from a rom < 4.2.x:
Backup everything !
Go to recovery
Make a full wipe / factory reset
format /system
Flash the rom
Flash optional kernel
Flash gapps
Wipe cache/dalvik
Reboot" - This is where my real confusion sets in. When i installed CM10 on my Arc S the first thing i had to do was flash the kernel which contained the recovery. Here the instructions say i have to flash it after flashing the rom. Am i to shutdown my phone after flashing the rom in order to install the kernel?
Thanks for reading.
+++
My curiosity got the better of me. :silly: I tried the CM-method of flashing the kernel first and it worked.
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
matg55 said:
I am unable to install the following ROM, continue to get this error (E:error (Status 7) Installation Aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
The ROM I choose is the'd2spr' and I have used several other (d2spr) ROMs that work, for my 'Sprint Samsung Galaxy S III' (SPH-L710).
Anyone able to advise/assist?
Things already attempted..
1) Updated to the latest CWM recovery
2) Updated to the latest PHILZ recovery
3) Toggled 'signature Verification' to "on"
4) Tried several other ROM's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
Which baseband you currently running?
sent from my GS3
matg55 said:
i am unable to install the following rom, continue to get this error (e:error (status 7) installation aborted):
http://forum.xda-developers.com/showthread.php?t=2634672
the rom i choose is the'd2spr' and i have used several other (d2spr) roms that work, for my 'sprint samsung galaxy s iii' (sph-l710).
Anyone able to advise/assist?
Things already attempted..
1) updated to the latest cwm recovery
2) updated to the latest philz recovery
3) toggled 'signature verification' to "on"
4) tried several other rom's from the same developer that were d2spr
..all resulted in the same error, above.
Click to expand...
Click to collapse
joeyhdownsouth said:
which baseband you currently running?
Sent from my gs3
Click to expand...
Click to collapse
l710vpucmk3
matg55 said:
l710vpucmk3
Click to expand...
Click to collapse
I am also having this issue
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Mr. Struck said:
Which recovery are you guys using? If it isn't Philz Touch, switch NOW! Then, under Wipe Data/Factory Reset, choose Clean to Install New ROM, and then flash whatever version of Carbon you want. If it helps to get you started, here is my download of the very first KitKat nightly that Carbon released, the assert lines have been removed in order to make it compatible for Virgin Mobile/Boost, and it is guaranteed to flash if all else is equal (as in you are using Philz Touch and did a proper wipe; I flashed this version just fine, otherwise I would not post it).
http://d-h.st/KTA
And the link to the Philz thread:
http://forum.xda-developers.com/showthread.php?t=2446393
Make sure to give @Phil3759 a "Thanks" while you are there!
Click to expand...
Click to collapse
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
matg55 said:
Thank You.. I do have the latest Philz Touch installed and did the full "new rom" wipe while trying the other Carbon ROM's, with the same error.
However, the ROM link you shared does work.. just hoping to be able to maintain the latest nightlies; wonder if I just have to remove the assert lines. Anyway, thanks again!
Click to expand...
Click to collapse
Which carrier are you on?
Mr. Struck said:
Which carrier are you on?
Click to expand...
Click to collapse
Sprint... and have tried the latest 'd2spr'
matg55 said:
Sprint... and have tried the latest 'd2spr'
Click to expand...
Click to collapse
That is strange; as a Virgin Mobile user, I have to modify or delete the assert lines for any Sprint ROM that is AOSP based, but for a Sprint user the ROM should have downloaded and flashed just fine. That's a shame too, because in my opinion, Carbon is the best ROM available.