what does this mean ?? [ assert failed:getprop("ro,product.device") == "maguro" ll getprop("ro.build.product") == "maguro"
E:Error in akop_maguro_build-35.zip (Status 7 )
Any Ideas on what i can do to fix this and what it means?
Any help would be much appreciated!
Are you trying to flash this rom on a non GSM phone?
Sent from my Galaxy Nexus using xda premium
WonkyYew said:
what does this mean ?? [ assert failed:getprop("ro,product.device") == "maguro" ll getprop("ro.build.product") == "maguro"
E:Error in akop_maguro_build-35.zip (Status 7 )
Any Ideas on what i can do to fix this and what it means?
Any help would be much appreciated!
Click to expand...
Click to collapse
Are you sure you downloaded the right version for your phone?
You need the maguro version.
Try download it again and make sure its the maguro version.
If that doesn't work try reflash cwm to the newest version.
---------- Post added at 02:12 AM ---------- Previous post was at 02:11 AM ----------
El Daddy said:
Are you trying to flash this rom on a non GSM phone?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
We don't have cdma in Ireland only GSM.
i downloaded the GSM and didnt work but ill try it again but it's weird cause i used the Android Revolution Wipe and i flashed that and it worked fine but soon went to install Rom it gave me that :S
It could be a bad download too.
Try flashing another version of cwm by fastboot and see of that works if flashing the rom again doesn't work.
What the error is saying is that the zip doesn't match the type of phone you have so either its the wrong version, corrupt download or cwm isn't working properly.
Are you downloading on your computer and the transferring to your phone via USB??
nodstuff said:
We don't have cdma in Ireland only GSM.
Click to expand...
Click to collapse
Sorry. The xda app doesn't show country flags
nodstuff said:
It could be a bad download too.
Try flashing another version of cwm by fastboot and see of that works if flashing the rom again doesn't work.
What the error is saying is that the zip doesn't match the type of phone you have so either its the wrong version, corrupt download or cwm isn't working properly.
Are you downloading on your computer and the transferring to your phone via USB??
Click to expand...
Click to collapse
Turns out it was the CWM after all !! Thanks for the help man much appreciated !!
WonkyYew said:
Turns out it was the CWM after all !! Thanks for the help man much appreciated !!
Click to expand...
Click to collapse
No hassle bud.
Related
When installing CM7 in cwm I get the folowing error:
assert failed: getprop("ro.product.device")=="
R800x" || getprop(ro.build.product") == "R800x"
|| getprop("ro.build.product") == "R800x " ||
getprop ("ro.product.board") =="R800x" ||
getprop ("ro.build.product") == "zeusc" ||
p("ro.product.board") ==zeusc"
E:Error in /sdcard/update-cm-7.1.0-RC1-XperiaPla
y-R800x-KANG-signed.zip
(Status 7)
Installation aborted.
I downloaded the zeusc_beta_FXP025 archive twice, and it extracted multiple tmes as well, to be sure it want user error, sounds like a corrupt download, but two in a row? Others seem not to have this issue...
Any thoughts?
I miss CM7
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
thanks, I'll try that when I get my new play. the old one got bricked... hit the ok for ota by accident.
I think this guy can help you ---> http://forum.xda-developers.com/showthread.php?t=1252038
cosvel said:
I think this guy can help you ---> http://forum.xda-developers.com/showthread.php?t=1252038
Click to expand...
Click to collapse
Sorry it took so long to update this post, I've been super busy, and unable to reply. Just to let every body know, Alejandrissimo did me right he got me fixed up and back to normal (unlocked and functional) in about 5 minutes. If any body has trouble with a soft brick (i.e. no fastboot) Alejandrissimo is your man.
AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
AndroHero, I some how managed to get it figured out just by folowing the directions (Imagine that) on the FXP post. Running 41 goodness now.
Moderators please close thread.
I'm getting the same error when trying to install and it's driving my head in.
Scottish Husky said:
I'm getting the same error when trying to install and it's driving my head in.
Click to expand...
Click to collapse
Use the link in this post:
http://forum.xda-developers.com/showpost.php?p=18378348&postcount=80
The original 7.1.0 release seems to have been bugged, this is 7.1.0.1. Seems to be fixing any install issues.
blindingshadow said:
Use the link in this post:
http://forum.xda-developers.com/showpost.php?p=18378348&postcount=80
The original 7.1.0 release seems to have been bugged, this is 7.1.0.1. Seems to be fixing any install issues.
Click to expand...
Click to collapse
I'm getting the same error but with the .1 update... this is too weird
AndroHero said:
You can always try opening the update .zip and deleting the get .prop lines from the update script
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Where do I find that?
This question is being asked quite a lot, it should probably be a sticky. Anyways follow this using Notepad++ to fix error status 7:
http://forum.xda-developers.com/showpost.php?p=20003695&postcount=1773
DISCLAIMER:
Flash at your own risk
I take no responsibility for what happens to your device
although if some thing goes wrong I will try to help
Hi Everyone!
I compiled Paranoid Android from source for the TF300T!
I decided to share my work
PA has alot of customation options
So check out there website
http://www.paranoid-rom.com/
SOURCES:
https://github.com/ParanoidAndroid
Updated to P.A. version 2.53 for build 2
also I fixed the density/DPI issues on initial boot
I had to edit and add a bunch of code
DOWNLOAD:
pa_tf300t-2.53-03NOV2012-152643 Build 2
WARNING: this is for the JB bootloader only
How to install:
1. reboot to recovery
2. make a nandroid backup
3. wipe data/factory reset
4. wipe cache
5. wipe dalvic cache
6. Install zip from sdcard
7. Choose zip from sdcard
8. flash gapps (optional)
9. reboot and enjoy
Possible Future Plans
init.d scripts
some tweaks
maybe some battery icons
some light theming
Bugs:
GPS wont lock
Possibly more
credits:
XpLoDWilD
timmytim
gokussjx
Paranoid Android
CyanogenMod
Changelog
Code:
Nov. 3
-updated to 2.53
-fixed density issues
Nov. 1
- first build
Can't wait to try this tmrw!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
This is awesome man, nice work.
Finally new ****. I will test this mother trucker
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Paranoid Android is great on Toro. I'm thinking I'll be upping to the JB bootloader today.
Sent from my Galaxy Nexus using xda premium
gchild320 said:
Paranoid Android is great on Toro. I'm thinking I'll be upping to the JB bootloader today.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I assume I have to flash stock ROM to get jb boot loader right, including the kernel and RE ROOTING?
Sent from my Transformer Pad TF300T using xda app-developers app
diamantericos said:
I assume I have to flash stock ROM to get jb boot loader right, including the kernel and RE ROOTING?
Sent from my Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
yes you would have to flash the latest Asus stock rom you should not have to reroot but you will have to install a recovery
but I recommend using NVflash first
Has anyone tried this?
Drgravy said:
yes you would have to flash the latest Asus stock rom you should not have to reroot but you will have to install a recovery
but I recommend using NVflash first
Click to expand...
Click to collapse
Going to use the Asus hydro method seems simpler I'm lazy this weekend . Then ill just flash this when I'm done.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
New Build is up!
new P.A. version 2.53
also fixed the density issues
let me know what you think
Drgravy said:
New Build is up!
new P.A. version 2.53
also fixed the density issues
let me know what you think
Click to expand...
Click to collapse
About to flash. I'll give feedback soon
Edit
Im having trouble flashing this
E:Error in ' /sdcard/<name of zip>.zip '...
(Status 7)
Error flashing zip ' <name of zip>.zip '
I also had this problem when flashing the latest cm10 nightly.
Can anyone help?
Thanks
RolloJarvis said:
About to flash. I'll give feedback soon
Edit
Im having trouble flashing this
E:Error in ' /sdcard/<name of zip>.zip '...
(Status 7)
Error flashing zip ' <name of zip>.zip '
I also had this problem when flashing the latest cm10 nightly.
Can anyone help?
Thanks
Click to expand...
Click to collapse
What recovery?
Sent from my SGH-T989 using xda app-developers app
I used CWM 6.0.1.4 touch recovery
Which rom are you coming from?
Sent from my MB865 using XDA Premium HD app
What recovery?
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
TWRP for Jelly bean.
Can make backups fine in recovery, just dont seem to be able to flash ROMs. It did let me flash the superuser script in order to root the stock JB rom however...
Here is the exact error from the TWRP log file:
Code:
Installing '/sdcard/Download/paranoid.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
script aborted: assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
E:Error in /sdcard/Download/paranoid.zip
(Status 7) Error flashing zip '/sdcard/Download/paranoid.zip'
Updating partition details...
EDIT: im coming from stock rooted. latest JB firmware (WW i think)
I'll try to use a different recovery maybe
RolloJarvis said:
TWRP for Jelly bean.
Can make backups fine in recovery, just dont seem to be able to flash ROMs. It did let me flash the superuser script in order to root the stock JB rom however...
Here is the exact error from the TWRP log file:
Code:
Installing '/sdcard/Download/paranoid.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
script aborted: assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
assert failed: getprop("ro.product.device") == "tf300t" || getprop("ro.build.product") == "tf300t"
E:Error in /sdcard/Download/paranoid.zip
(Status 7) Error flashing zip '/sdcard/Download/paranoid.zip'
Updating partition details...
EDIT: im coming from stock rooted. latest JB firmware (WW i think)
I'll try to use a different recovery maybe
Click to expand...
Click to collapse
All fine here, 2.53 with TWRP, no issues. US Model
Installed and running fine, other than GPS not working, I noticed that wallpaper changes don't stick after reboot, the tablet reboots to a black screen. Other than that the build is solid and snappy.
Thanks for the work.
Erik
Sent from my Transformer Pad TF300T using Tapatalk 2
Closed as per OP's request.
Hello, i have Xperia S (26i) rooted. I download and install CWM, copy files of new rom to internal SDcard, reboot in recovery and make all steps, but process stops and error message appears:
assert failed: getprop("ro.product.device") == "LT26i" I I getprop(ro.build.product") == "LT26i" ==getprop(ro.product.device") ==nozomi I I getprop(ro.buil.product) == nozomi
I think the problem is conflict with lt26i and nozomi. It´s correct ? How i do to change ?
Thanks and sorry... my english is very bad..... lol
Is your bootloader unlocked?
Sent from my Xperia S using xda app-developers app
Fastboot advanced stock kernel first then try again
Sent from my JB Xperia S
I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app
Nvm.
sr_redhot said:
I have Locked B. But try to install MIUI and error came again, the same.
Using Google i found xda link and resolution is edit build.prop and change "nozomi" to "LT26I". I try to do this :
Unzip ROM, edit build.prop and zip.
But now i have another error. I think MD5 maybe is the key..... I do no if "rom zip file" have signature or other Type of file confirm.....
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
There's your problem, you have a locked bootloader, YOU NEED A UNLOCKED BOOTLOADER to install PAC, I dont know about miui, but anything with custom kernel YOU NEED UNLOCKED BOOTLOADER. So first unlock you bootloader then it should work perfectly fine. You seriously need to read the requirements to install a custom Rom.
Sent from my Xperia S using xda app-developers app
I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app
sr_redhot said:
I know if a lot of custom roms needs unlocked bootloader. In PAC V19 i do no, But MIUI are ok with Locked bootloader. I try muiu first, But when error appears i try PAC. Im thinking if i really want to unlock bootloader.....
But thanks for that.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.
m1st3r1 said:
flash stock rom first.. preferably using flashtool, use fw .50 or below (as long as it's ics one), root it, and install cwm. then u can flash miui.
Click to expand...
Click to collapse
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Updated:
TurboROM installed..... But MIUI and PAC get the same error
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
I follow you tip,
Download new files from PAC and MIUI
Unzip, make changes, zip, copy to sd reboot into recovery, make all steps in PAC tutorial and nothing done:
"Finding update package
Opening update package
Installing update
Instalation aborted"
I do know what´s gonna hell ........
So hard to do one simple thing.... :crying:
sr_redhot said:
I try all :
-Format
-unlock BL
-Install FW .55
But the same error appears. I really thing : in some moment custom rom say "nozomi" and my cell say"LT26i" and stopped instalation.
Now i´m downloading more ROMs to testing instalation,
Click to expand...
Click to collapse
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Dr.Alexander_Breen said:
WTF. No one ever gave right advice. Wow.
Well, I've got sometimes the same error.
There is one solution:
Unzip installation file.
Delete this line inside META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
Then zip this file back to it's place in archive. Try to install, and BOOM - it's fine now!
Click to expand...
Click to collapse
Is the wtf really necessary? Ofc, I know this solution, but I don't think it is a good solution. As you know this phone is lt26i with nozomi as its codename, and the rom op want to flash is built for lt26i, so in my opinion, it's kinda wrong change something that supposed to be working.
Sent from my LT26i using Tapatalk 2
m1st3r1 said:
Try flash advanced kernel first. Then try flash Miui. Wipe all (wipe data, format system and dalvik cache).
I'm in relocked bootloader, using .55 kernel, got no problem flashing miui.maybe u did something wrong in the first steps...
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
GREAT !!! Now it´s working !!! MIUI installed. And next step is testing PAC.
Tks !!:laugh:
Alright i'm in a pickle, tonight I was about to flash to CM 10.1.2 however when I rooted my phone I didnt update to the latest CWM. I've already wiped Data/ factory reset but when try to flash to CM 10.1.2 I get assert failed: getprop("ro.product.device") == "d2att' ||getprop("ro.build.product") == "d2att" (Status 7)
I understand I need to update CWM but how can I if I have no rom on the device currently. Whenever I try to reboot I just get the andrid guy with the red triangle on top of him and it sends me back to CWM.
Should I just pull the battery and put it in Download mode to update CWM? I don't even know if i'd be able to get into download mode 0.0 please help.
Thanks
Do you have an external SD card? If you do, simply load the new cwm zip there, insert it in your phone, and flash in cwm. It'll overwrite the old cwm.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Domoo said:
Do you have an external SD card? If you do, simply load the new cwm zip there, insert it in your phone, and flash in cwm. It'll overwrite the old cwm.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Do you know where I can find the Zip download?
Here you go:
http://forum.xda-developers.com/showthread.php?t=2152769
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
khep24 said:
Do you know where I can find the Zip download?
Click to expand...
Click to collapse
clockworkmod com
you can download latest CWM from here.
so i somehow managed to delet the files in system/bin and now im unable to boot my kindle can i have some help here?
Do you have recovery installed if so just find either stock or cm and just use them
Sent from my YP-G1 using Tapatalk 4
goldflame09 said:
Do you have recovery installed if so just find either stock or cm and just use them
Sent from my YP-G1 using Tapatalk 4
Click to expand...
Click to collapse
i have TWRP but it keeps failing when i try to flash software
crasher925 said:
i have TWRP but it keeps failing when i try to flash software
Click to expand...
Click to collapse
What exactly are you trying to flash. You may have to wipe your stomach and/or data before anything will boot and/or flash
Sent from my YP-G1 using Tapatalk 4
goldflame09 said:
What exactly are you trying to flash. You may have to wipe your stomach and/or data before anything will boot and/or flash
Sent from my YP-G1 using Tapatalk 4
Click to expand...
Click to collapse
lol im trying to flash the stock kindle os form stcokroms i already renamed it to .zip but its comes up with an error when i try to flash it
crasher925 said:
lol im trying to flash the stock kindle os form stcokroms i already renamed it to .zip but its comes up with an error when i try to flash it
Click to expand...
Click to collapse
Try installing cm and I'm mobile and that was supposed to be system not stomach damn you google voice
Sent from my YP-G1 using Tapatalk 4
goldflame09 said:
Try installing cm and I'm mobile and that was supposed to be system not stomach damn you google voice
Sent from my YP-G1 using Tapatalk 4
Click to expand...
Click to collapse
LOL thank you for that laugh!
crasher925 said:
LOL thank you for that laugh!
Click to expand...
Click to collapse
No problem but if you could post the error at some point, that could be helpful
Sent from my YP-G1 using Tapatalk 4
goldflame09 said:
No problem but if you could post the error at some point, that could be helpful
Sent from my YP-G1 using Tapatalk 4
Click to expand...
Click to collapse
the error is:
assert failed: getprop ("ro.build.product") == "blaze"
E: unknown command [err_strcng]
getprop ("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3_D01E_4019920.zip
Error flashing zip /sdcard/update-kindle-6.3_D01E_4019920.zip
updating partition details...
crasher925 said:
the error is:
assert failed: getprop ("ro.build.product") == "blaze"
E: unknown command [err_strcng]
getprop ("ro.build.product") == "blaze"
E: unknown command [err_string]
E: Error executing updater binary in zip '/sdcard/update-kindle-6.3_D01E_4019920.zip
Error flashing zip /sdcard/update-kindle-6.3_D01E_4019920.zip
updating partition details...
Click to expand...
Click to collapse
What version of TWRP do you have?
soupmagnet said:
What version of TWRP do you have?
Click to expand...
Click to collapse
i have 2.6
crasher925 said:
i have 2.6
Click to expand...
Click to collapse
otter or blaze?
soupmagnet said:
otter or blaze?
Click to expand...
Click to collapse
CM is otter and TWRP is blaze
Have you tried the otter version of TWRP to see if it makes a difference?
soupmagnet said:
Have you tried the otter version of TWRP to see if it makes a difference?
Click to expand...
Click to collapse
the otter version will make a difference
I tried both the otter and the blaze a couple weeks ago for giggles and got the same result failed. It could by a TWRP bug try COTR instead or just try ADB sideload see if that works best do a full wipe prior to flashing stock.
Thepooch said:
I tried both the otter and the blaze a couple weeks ago for giggles and got the same result failed. It could by a TWRP bug try COTR instead or just try ADB sideload see if that works best do a full wipe prior to flashing stock.
Click to expand...
Click to collapse
what is COTR and ADB?
crasher925 said:
what is COTR and ADB?
Click to expand...
Click to collapse
Cannibal Open Touch Recovery http://forums.projectopencannibal.n...pen-touch-v2-0-2-(latest-update-08132012)-60/ if you don`t know what ADB is maybe you should not be modifying your device anyway ADB sideload is a feature in twrp that anything you push via ADB it will flash while sideload is enabled. http://forum.xda-developers.com/showthread.php?t=2225405
Thepooch said:
Cannibal Open Touch Recovery http://forums.projectopencannibal.n...pen-touch-v2-0-2-(latest-update-08132012)-60/ if you don`t know what ADB is maybe you should not be modifying your device anyway ADB sideload is a feature in twrp that anything you push via ADB it will flash while sideload is enabled. http://forum.xda-developers.com/showthread.php?t=2225405
Click to expand...
Click to collapse
ah ok just wanted to verify
Thepooch said:
I tried both the otter and the blaze a couple weeks ago for giggles and got the same result failed. It could by a TWRP bug try COTR instead or just try ADB sideload see if that works best do a full wipe prior to flashing stock.
Click to expand...
Click to collapse
I'm running 2.6 otter no problems at all
Sent from my Amazon Kindle Fire using Tapatalk 4