So I've just rooted my GT-P7510 using this guide:
http://forum.xda-developers.com/showthread.php?t=2361571
and I'm trying to flash the latest CM 10.1 nightly but having difficulties. Every time I try to flash I get the error message:
assert failed: getprop("ro.product.device") == "p4wifi" || getprop("ro.build.product") == "p4wifi"
E:Error in /sdcard/goomanager/cm-10.1-20130708-NIGHTLY-p4wifi.zip
(Status 7)
Click to expand...
Click to collapse
I've tried downloading it from get.cm, through goomanager, as well as different nightly builds from the last 6 months with no results. This is the third device I've rooted so I'm not new to the scene but for some reason this is just above my knowledge. Any help would be appreciated!
What version of recovery are you using?
Sent from my GT-P7500 using Tapatalk
I believe V 2.2 of TWRP, which was in the tutorial's download package. I know they've updated to 2.6.3 but I couldn't find a version for the Tab.
There's one in the A1 kernel thread. There's another v2.5.0.0 beta from Infamous AOKP 4.2 thread. You should use the 2.5.0.0 from kasper_h because the newest version is only intended for flashing KitKat ROMs only.
Sent from my GT-P7500 using Tapatalk
112 64998696
Awesome, that did the trick, thank you!
Related
I get ASSERT FAILED: GETPROP("RO.BOOTLOADER") == P7100BUKB7.
or
getprop("ro.bootloader")=="P7100BUKB7"||getprop("r o.bootloader")=="P7100BUKC8" depending on the ROM
When attempting to flash stock ROM using CWM 4.0.0.4.
What does this mean?
Digging around I noticed that 'assert(getprop("ro.bootloader") == "P7100BUKB7" || getprop("ro.bootloader")' is the first line in 'updater-script' in the ROMs zip packages that fail to install.
The only ROM that I have that does install. the starburst ROM, doesn't have a line referring to bootloader.
What does 'getprop("ro.bootloader")=="P7100BUKB7"||getprop("r o.bootloader")=="P7100BUKC8"' do in this script.
Thank you
rlowens44 said:
I get ASSERT FAILED: GETPROP("RO.BOOTLOADER") == P7100BUKB7.
or
getprop("ro.bootloader")=="P7100BUKB7"||getprop("r o.bootloader")=="P7100BUKC8" depending on the ROM
When attempting to flash stock ROM using CWM 4.0.0.4.
What does this mean?
Digging around I noticed that 'assert(getprop("ro.bootloader") == "P7100BUKB7" || getprop("ro.bootloader")' is the first line in 'updater-script' in the ROMs zip packages that fail to install.
The only ROM that I have that does install. the starburst ROM, doesn't have a line referring to bootloader.
What does 'getprop("ro.bootloader")=="P7100BUKB7"||getprop("r o.bootloader")=="P7100BUKC8"' do in this script.
Thank you
Click to expand...
Click to collapse
The ROM is checking what bootloader your device has for compatibility, and deciding it doesn't like what it sees.
Which Tab variant do you have? It looks like you're trying to flash ROMs meant for the 10.1v (P7100) on something else (most likely P7500 or P7510 - the non-v 10.1 variants)
Entropy512 said:
The ROM is checking what bootloader your device has for compatibility, and deciding it doesn't like what it sees.
Which Tab variant do you have? It looks like you're trying to flash ROMs meant for the 10.1v (P7100) on something else (most likely P7500 or P7510 - the non-v 10.1 variants)
Click to expand...
Click to collapse
I think you're right. I have GT-P7510.....
I guess I need to find the correct stock ROM.
Thank you for your response!
rlowens44 said:
I think you're right. I have GT-P7510.....
I guess I need to find the correct stock ROM.
Thank you for your response!
Click to expand...
Click to collapse
Make sure to stick in the 10.1 and not 10.1v dev forums.
Whenever I tried to install CM10 and variants (eg CM10 or Superlite CM10) on my T989 Hercules, I get this error
assert failed: getprop(ro.product.device)==hercules
E:Error in (/sdcard/cm10-20121015-nightly-hercules)
(status 7)
I flashed using TWRP 2.2.2. Currently running AOKP b4.
Many thanks.
Solved. Updated to TWRP 3.2.1.1
pakron said:
Whenever I tried to install CM10 and variants (eg CM10 or Superlite CM10) on my T989 Hercules, I get this error
assert failed: getprop(ro.product.device)==hercules
E:Error in (/sdcard/cm10-20121015-nightly-hercules)
(status 7)
I flashed using TWRP 2.2.2. Currently running AOKP b4.
Many thanks.
Click to expand...
Click to collapse
You have a T989. This is the I9100 forum.
T989 forum.
I seem to have issues flashing down to my canadian rom for the release from spain. Also I don't seem to be able to flash over to things like super nexus, Im on speed mod for my kernel. I may try flashing cm10.1 as well.
sujeethan said:
I seem to have issues flashing down to my canadian rom for the release from spain. Also I don't seem to be able to flash over to things like super nexus, Im on speed mod for my kernel. I may try flashing cm10.1 as well.
Click to expand...
Click to collapse
Mobile Odin.
gastonw said:
Mobile Odin.
Click to expand...
Click to collapse
would using mobile odin be any different from Odin3 v3.04 outside of ever root? The files are .zip I can't seem to find a .tar of those roms. :S
Thought you meant stock jb.
Custom ROMs = CWM falshing.
If you are having problems go stock and then go back to custom.
There are a couple of scripts that remove all crap left behind from previous flashed ROMs, you could try that.
Sent from the little guy
gastonw said:
Thought you meant stock jb.
Custom ROMs = CWM falshing.
If you are having problems go stock and then go back to custom.
There are a couple of scripts that remove all crap left behind from previous flashed ROMs, you could try that.
Sent from the little guy
Click to expand...
Click to collapse
Im using the CWM recovery found in the speedmod kernel. I tried going down from stock 4.1.2 to my canadian stock 2.3 as i could not find 4.0.3. IT didn't work out well as i found my self in a bit of a boot loop. I flashed back up to 4.1.2 and i was back to normal. This was through odin. Prior to trying to go down i tried installing cm10 and super nexus at which points i kept getting installation aborted errors where the scripts seem to be trying to find my model number which isn't working out. I think the issues my model number changing from i9100m to i9100 in the upgrade from 4.0.3 to 4.1.2
Shouldn't, but could be.
Sent from the little guy
gastonw said:
Shouldn't, but could be.
Sent from the little guy
Click to expand...
Click to collapse
Do you have any other tips possibly?
Try the scripts I mentioned
Might do the trick.
Sent from the little guy
links?
look in the development section, they are there somewhere.
Sent from the little guy
gastonw said:
look in the development section, they are there somewhere.
Sent from the little guy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2100558&highlight=scripts would this be it ? Closest thing to your description but I doubt its it since it says its meant to be used before flashing a rom and I've already flashed out of my last rom unless it helps to use it before flashing to my next rom.
It'll get you all cleaned up (not as clean as format system to).
Try it out and see how it goes.
Sent from the little guy
-- Installing: /sdcard/SuperNexus-2.0-i9100-BUILD2.zip
fd: 12
ev: 1 116 0
fd: 12
ev: 0 0 0
Finding update package...
I:Update location: /sdcard/SuperNexus-2.0-i9100-BUILD2.zip
Opening update package...
Installing update...
script aborted: assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" ||
getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" ||
getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" ||
getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" ||
getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" ||
getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T"
assert failed: getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2" || getprop("ro.product.device") == "i9100" || getprop("ro.build.product") == "i9100" || getprop("ro.product.device") == "GT-I9100" || getprop("ro.build.product") == "GT-I9100" || getprop("ro.product.device") == "GT-I9100M" || getprop("ro.build.product") == "GT-I9100M" || getprop("ro.product.device") == "GT-I9100P" || getprop("ro.build.product") == "GT-I9100P" || getprop("ro.product.device") == "GT-I9100T" || getprop("ro.build.product") == "GT-I9100T"
E:Error in /sdcard/SuperNexus-2.0-i9100-BUILD2.zip
(Status 7)
Installation aborted.
I seem to get issues like this BTW. I'll try the nuke tonight. Are the any risks with brick bug and it?
Sent from my GT-I9100 using xda app-developers app
no brick bug danger (don't perform on 4.0.4, just in case).
Search for status 7 here at Q&A.
Sent from the little guy
Remember to backup EVERYTHING before nuking the device.
Sent from my digital submersible hovercraft.
f-r said:
Remember to backup EVERYTHING before nuking the device.
Sent from my digital submersible hovercraft.
Click to expand...
Click to collapse
That reminded me to try online nandroid back up now.
It's a good day for bricks.
See y'all
Edit: Don't feel like backing up.
Sent from the little guy
sujeethan said:
I seem to have issues flashing down to my canadian rom for the release from spain. Also I don't seem to be able to flash over to things like super nexus, Im on speed mod for my kernel. I may try flashing cm10.1 as well.
Click to expand...
Click to collapse
There are some issues flahsing older cwm based roms on the JB kernels.
What you need to do is flash a different kernel via ODIN like Siyah v4. Once you have new kernel reboot into recovery and give a clean using the rom nuke/kernel wipe scripts from here then flash your rom zip.
if i try siyea v5 it flashes the kernels logo and powers down when booting O-o
sujeethan said:
if i try siyea v5 it flashes the kernels logo and powers down when booting O-o
Click to expand...
Click to collapse
What ROM? JB?
Siyah v5 and JB don't get along.
Siyah v6's got no beef with JB tho.
And if it's not JB, Factory Reset makes it all good again.
gastonw said:
What ROM? JB?
Siyah v5 and JB don't get along.
Siyah v6's got no beef with JB tho.
And if it's not JB, Factory Reset makes it all good again.
Click to expand...
Click to collapse
Version 6 is the beta how stable is it ?
Also the rom was stock 4.1.2 from spain.
EDIT: This one boots! Now try to attempt flashing
EDIT again : IT WORKS ITS ALIVE! THANK YOU ALL! Freaking older kernel was my issue. I should probably do a nuke though...
Hey guys... Lately I installed the leaked version of Jelly Bean on my S2... Now when I am trying to flash CM10 via binary flash counter it's not letting me do that... It gives me some type of error(PROP.something) and says installation aborted... I really need help!!
Is it giving status 7 error
Please provide more details regarding how you were flashing it
And if it is status 7 error then there is nothing to worry it can be fixed by flashing another kernel using odin
Sent from my GT-I9100 using xda app-developers app
I am not sure what kind of error but everything gets done and after the final installation of CM10 files I get
--Installing: /sdcard/FXP133-cm-10-20120813-haida.zip
Finding update package...
I:Update location: /sdcard/FXP133-cm-10-20120813-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"
E:Error in /sdcard/FXP133-cm-10-20120813-haida.zip
(Status 7)
Installation aborted.
I gave you an example because I can't take a screen shot of that error... It shows me all the model numbers of your phone and then say it stops... One of my friend advised me to edit my PROP files but I really don't know how to do that... Maybe you can provide me a link to that or some instructions from your side....
Change the kernel. I had the same problem and solved it by changing the kernel.
dareas said:
Change the kernel. I had the same problem and solved it by changing the kernel.
Click to expand...
Click to collapse
How would you do that bro?
Are you sure you picked the correct CM binaries for your phone? As I can see from your error messages it's checking for a different hardware and not for the i9100. So be happy, that flashing fails otherwise you would have a new piece of paperweight now ... :fingers-crossed:
AndDiSa said:
Are you sure you picked the correct CM binaries for your phone? As I can see from your error messages it's checking for a different hardware and not for the i9100. So be happy, that flashing fails otherwise you would have a new piece of paperweight now ... :fingers-crossed:
Click to expand...
Click to collapse
I know that buddy that's why I said that I am giving you an example of what kind of error I am getting. It's not from my device I understand but I won't be able to take a screen shot of that while doing it. It's related to some PROP issue only but I don't know how to solve it.
AW: [Q] Official jelly bean installed and now unable to flash CM10... HELP!!!
What's the text of the error message? That's important, because it tells you exactly, what's the mismatch.
Edit: you should look for "assert failed:"
Sent from my Nexus 7 using xda app-developers app
Ran into the same problem and found a solution that worked. Downloaded and installed philz Kernel first. Worked perfectly and was able to use any other kernel and rom after and they installed perfectly.
Sent from my GT-I9100 using xda app-developers app
Hey guys.... I am on leaked 4.1.2 Samsung touchwiz for GT-I9100... I was trying to install CM10.1 on my device and while trying to install it via CWM binary method it never installs the package and gives me this error-
GT-I9100M" || getrop("ro.build.product")=="GT
-I9100M" || get.prop("ro.product.device")
== "GT-I9100P" || get.prop("ro.build.product") ==
"GT-I9100P" || get.prop("ro.product.devic
e") == "GT-I9100T" || getprop("ro.build.product"
) == "GT-I9100T"
E:Error in /tmp/sideload/package.zip
(Status 7)
What can be done in this situation?
Wasn't this your question at the first post..? And did you try to change the kernel first, like people told you?
Donnie Sins said:
Wasn't this your question at the first post..? And did you try to change the kernel first, like people told you?
Click to expand...
Click to collapse
Yes that was the question at the first post and I am going to delete that post now because I didn't have the exact error which I was getting on y phone... Tried it just now and wrote the error info here so we can discuss about it and find a solution...
No, I have not changed the kernel.... I don't know how to do that... I have flashed CM 9 and 10 using the binary method however never tried changing the kernel.... Any links would be appreciated... Can't it be fixed without changing the kernel?
timtimrana said:
Hey guys... Lately I installed the leaked version of Jelly Bean on my S2... Now when I am trying to flash CM10 via binary flash counter it's not letting me do that... It gives me some type of error(PROP.something) and says installation aborted... I really need help!!
Click to expand...
Click to collapse
Flash latest Siyah Kernel via CWM and retry installing CM
Flash another kernel
Sent from my GT-I9100G using xda app-developers app
zgalvin said:
Flash another kernel
Sent from my GT-I9100G using xda app-developers app
Click to expand...
Click to collapse
I tried to flash Siyah Kernel and again the installation failed... I was advised to flash Philz kernel as well however I wasn't able to find the basband version for my device which is XXLS6... Should i install Philz Kernel?
Please provide me the link for my baseband version as well... And do I need to install this Kernel through Odin?
i'm s-off and unlocked ... i tried 4 different recoveries
philz_touch_6.08.7-dlx
recovery-clockworkmod-6.0.4.5-dlx-unofficial
recovery-clockwork-6.0.4.6-dlx
recovery-clockwork-touch-6.0.4.6-dlx
none of them will install cm10.2 stable
i was able to install a different kernal cm11 and cm11 gapps but whenever i install the cm10.2 stable it gives me an error message in cwm complaining about the device name?!?!?
error message is
assert failed: getpropro.product.device: )= "dlx: || asset failed: getpropro.product.device: )= "dlx:
So what's your actual question or what you need help with.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
jack_d12 said:
i'm s-off and unlocked ... i tried 4 different recoveries
philz_touch_6.08.7-dlx
recovery-clockworkmod-6.0.4.5-dlx-unofficial
recovery-clockwork-6.0.4.6-dlx
recovery-clockwork-touch-6.0.4.6-dlx
none of them will install cm10.2 stable
i was able to install a different kernal cm11 and cm11 gapps but whenever i install the cm10.2 stable it gives me an error message in cwm complaining about the device name?!?!?
error message is
assert failed: getpropro.product.device: )= "dlx: || asset failed: getpropro.product.device: )= "dlx:
Click to expand...
Click to collapse
Use an older recovery version or (my recommendation) flash cm11.
i wanted to install a stable cm 10.2 rom instead of a nightly cm11 rom ... i search and search for the this error message on the dna forums and i can't find the answer ... i search on google and i find out that i need to remove the first line of the updater script. i didn't try that yet.
i didn't think a nightly would be as stable as a "stable" build.
just weird that i don't see anyone getting this error message on xda.
the threads for the recoveries had no info saying to use an older one .. the thread for official cm10.2 say just use a compatible cwm?!?!?
cm11 nightly 0124 seems stable enough ...
thanks!