Hi everyone, the title says it all.
The mediatek version has a very poor ROM pool ...
Thanks!
That is imposible, although phones look the same, they are completely different.
If u flash it, u will probably get Error 7 on TWRP, due to most ROMs include device checker, but if it is flashed, your phone will probably become unusable, an unrecoverable brick will probably take place.
Sorry about poor ROM pool, all MTK have such problem. The next phone u buy, pls carefully check wether u want another MTK/Kirin/etc which all have same issues.
Regards!
Thanks a lot for the quick answer!
Unkk said:
Hi everyone, the title says it all.
The mediatek version has a very poor ROM pool ...
Thanks!
Click to expand...
Click to collapse
cannot
Their many custom ROMs which van be flashed for both Kenzo & Kate. For example, Lineage, RR, NOS, As long as ur on correct firmware, it is ok.
Below is the 1st line from updater script of NOS
assert(getprop("ro.product.device") == "kenzo" || getprop("ro.build.product") == "kenzo" || getprop("ro.product.device") == "kate" || getprop("ro.build.product") == "kate" || abort("This package is for device: kenzo,kate; this device is " + getprop("ro.product.device") + ".");
waleed.ibrahim said:
Their many custom ROMs which van be flashed for both Kenzo & Kate. For example, Lineage, RR, NOS, As long as ur on correct firmware, it is ok.
Below is the 1st line from updater script of NOS
assert(getprop("ro.product.device") == "kenzo" || getprop("ro.build.product") == "kenzo" || getprop("ro.product.device") == "kate" || getprop("ro.build.product") == "kate" || abort("This package is for device: kenzo,kate; this device is " + getprop("ro.product.device") + ".");
Click to expand...
Click to collapse
Lol nah.
He was asking about mtk variant of Redmi-note3 not about kate, FYI - kate is also Snapdragon variant!
sachin n said:
Lol nah.
He was asking about mtk variant of Redmi-note3 not about kate, FYI - kate is also Snapdragon variant!
Click to expand...
Click to collapse
Lol, my bad. I thought Kate for hennessey
waleed.ibrahim said:
Lol, my bad. I thought Kate for hennessey
Click to expand...
Click to collapse
Aha
Related
I was rooted a while back with CM mod and something messed up and I had to go back to stock and unroot my device. For the longest time I couldn't re-root it but now I finally did. When trying to flash I come up with this long error.
assert failed: getprop("ro.product.device") == "asies" || getprop"ro.build.product") == "aries" || getprop("ro.product.device") == "fascinate" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500"
E:Error in /sdcard/teamhacksung_fascinatemtd-ota-eng.BUILD5.zip
(Status 7)
Installation aborted.
Now it doesn't matter which rom I flash, it does about the same thing. I flashed a recovery just to see if it'd work and it did. I currently now have 3.x and it's still doing the same thing. I read online and people said to revert to stock, but I already am at stock. And I just rooted it today. So I have no clue what this means. Any help would be much appreciated, thanks!
Maisum said:
I was rooted a while back with CM mod and something messed up and I had to go back to stock and unroot my device. For the longest time I couldn't re-root it but now I finally did. When trying to flash I come up with this long error.
assert failed: getprop("ro.product.device") == "asies" || getprop"ro.build.product") == "aries" || getprop("ro.product.device") == "fascinate" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.build.product") == "fascinatemtd" || getprop("ro.product.device") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500" || getprop("ro.build.product") == "SCH-I500"
E:Error in /sdcard/teamhacksung_fascinatemtd-ota-eng.BUILD5.zip
(Status 7)
Installation aborted.
Now it doesn't matter which rom I flash, it does about the same thing. I flashed a recovery just to see if it'd work and it did. I currently now have 3.x and it's still doing the same thing. I read online and people said to revert to stock, but I already am at stock. And I just rooted it today. So I have no clue what this means. Any help would be much appreciated, thanks!
Click to expand...
Click to collapse
You need cwm4 there is a link to everything you need in droidstyle's guide. Due to being on the app I cannot post links. But its in general section. Hope that clears it up.
Sent from my SCH-I500 using XDA App
Wow that worked! Thanks a lot!
Maisum said:
Wow that worked! Thanks a lot!
Click to expand...
Click to collapse
Your welcome dude
Sent from my SCH-I500 using XDA App
Hi,
I just tried to install this rom on my i9100p (the one with NFC) but failed the initial test... looks like it can be installed only on plain 9100, 9100M and T but not P... why is that? i've read that apart from the NFC it's just the same (in fact i had no problem installing CWM and after that when the phone boots it says i9100)...
i tried to search for the piece of code that it show on the screen as an error, but unfortunately I couldn't find where it is... the error is:
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") == "i9100M" || getprop("ro.build.product") == "i9100M" || getprop("ro.product.device") == "i9100T" || getprop("ro.build.product") == "i9100T"
so it should be matter of adding a couple ORs and voila... or maybe is there a way to change my model name somewhere?
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
GaboWinter said:
Mmm some info. here, maybe help http://forum.xda-developers.com/showthread.php?t=1465816
Click to expand...
Click to collapse
wel thank you, it did help, cause i understood that i had to modify the updater-script!
but now i get another error it just says error in .zip and (status 6), before it was status 7...
but i'm not really sure if i'm doing it correctly... when i'm in recovery mode, i go to install zip from sdcard->choose zip from sdcard and then i choose update-cm-9...zip
instructions only say "flash cm9"...
i have rooted the phone with CWS and nothing else...
Hello everyone,
I wanted to try the 4.2 camera app and I changed my build.prop to have Galaxy Nexus in the device name. I did backup the original build.prop but forgot to restore it., and I think it is causing me the Status 7 error.
What can I do now to finish the FXP151 installation? Should I try to restore a previous NAND? Thanks for your time.
Installing update...
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/FXP151-cm-10-20121214-UNOFFICIAL-haida.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Edit update script..delete the assert and its sublines
bluestricker_21 said:
Edit update script..delete the assert and its sublines
Click to expand...
Click to collapse
Many thanks for the swift reply, it worked. Another question if I may, the LED lights are now brighter/stronger, is this normal?
Konosuke said:
Many thanks for the swift reply, it worked. Another question if I may, the LED lights are now brighter/stronger, is this normal?
Click to expand...
Click to collapse
yup it is normal in cm10
I tried to flash JellyBam and a MIUI ROM, but both failed with status 7.
I saved a log from Aroma installer after trying to flash the MIUI ROM:
Code:
AROMA INSTALLER version 2.56
(c) 2012 by amarullz xda-developers
ROM Name : M1UI
ROM Version : 2.10.26.v2
ROM Author : a1exander
Device : Samsung Galaxy S2
Start at : Sun Dec 23 16:11:05 2012
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"
Installer Error (Status 7)
End at : Sun Dec 23 16:11:05 2012
EDIT: Did some more digging and found that the ROMs that failed to flash had an assert command in the beginning of the script,
while the ROMs that worked didn't have an assert command. Is it safe to disable assert command from recovery or remove it from the script?
Or what should I do to flash these ROMs?
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Thanks, that worked.
P990 - same issue
Will this solution work for the Optimus 2x as well?
Thanks.
ilovefls said:
Will this solution work for the Optimus 2x as well?
Thanks.
Click to expand...
Click to collapse
A kernel for the i9100 has ZERO chance of working on an Optimus 2x.
ctomgee said:
A kernel for the i9100 has ZERO chance of working on an Optimus 2x.
Click to expand...
Click to collapse
Then what solution do you recommend for the same issue encountered on the P990?
ilovefls said:
Then what solution do you recommend for the same issue encountered on the P990?
Click to expand...
Click to collapse
Maybe a solution found in the forum for that device?
This thread is in the forum for the GT-i9100 Galaxy S II. Chances of you finding a solution for whatever problem you're having on your Optimus 2x in this forum are pretty small.
ctomgee said:
Maybe a solution found in the forum for that device?
This thread is in the forum for the GT-i9100 Galaxy S II. Chances of you finding a solution for whatever problem you're having on your Optimus 2x in this forum are pretty small.
Click to expand...
Click to collapse
OMG! Can someone at least try to give an answer that is useful?
The reason I posted it here was because it is the exact same problem I have that has been described here. I am fully aware this is an S II thread, thanks for pointing that out!
The error shared is because the update script is c comparing the value of the device identity with a pre-set value in the update (Galaxys2 & Gt-I9100) another solution would to be open the update file hash the lines for the assert and continue to flag bit that would mean disabling a security feature that was put there to prevent faulty flashs.
And yes you re far from where you need to be and I'm no expert in Optimus.
Sent from my GT-I9300 using xda app-developers app
ilovefls said:
OMG! Can someone at least try to give an answer that is useful?
The reason I posted it here was because it is the exact same problem I have that has been described here. I am fully aware this is an S II thread, thanks for pointing that out!
Click to expand...
Click to collapse
Seeing as how I am an i9100 user, and know nothing about the Optimus 2x, my suggestion for you to go to the Optimus 2x forum to ask other Optimus 2x users is perfectly useful.
Just because you got the same error doesn't mean the solution is the same.
And it didn't seem like you knew where you were, because you asked if flashing an i9100 kernel would fix your problem on your Optimus 2x. Kernels for specific devices do not typically work on other devices. Especially if there are major hardware differences. There is a piece of useful information you apparently did not know.
@ilovefls - More to the point, if you flash something meant for the I9100 on whatever the hell phone you have (didn't notice/don't particularly care), there's a fair chance you'll brick it.
So....You can either take the well intentioned advice (and it was well intentioned; nobody told you to get nicked like I am now) you were given & ask in the forum specific to your device, or you can break your phone. No skin off our nads either way.
Actually, the latter would be pretty funny given how dopey you obviously are. I figure it would be just deserts.
So....You can either take the well intentioned advice (and it was well intentioned; nobody told you to get nicked like I am now) you were given & ask in the forum specific to your device, or you can break your phone. No skin off our nads either way.
Actually, the latter would be pretty funny given how dopey you obviously are. I figure it would be just deserts.
OWNED
Sorry very childish of me ..
1Chef said:
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Click to expand...
Click to collapse
Worked for me, thanks for this information now my phone is back up and running.
1Chef said:
Flash a dorimanx kernel http://forum.xda-developers.com/showthread.php?t=1617219 (don't boot) then reboot recovery (in advanced), wipe data (backup with titanium) then flash rom, wipe cache and devlik cache and then reboot
Click to expand...
Click to collapse
thanks...finally on JellyBAM......
Hello all.
I recently saw a post about cm 10.1 for xperia p and i rushed to download and install it. I am using xperia p stock jb rom with unlocked bootloader , rooted with CMW and when i tried to flash it from CWM the instalation was aborted.(status 7) can someone help me please? i really want the android 4.2.2 thanks.
Just delete in zip archive in file \META-INF\com\google\android updater-script first 3 lines and flash archive!
Thanks for your interest but i already did, installation aborted status 0.
assert(getprop("ro.product.device") == "C5502" || getprop("ro.build.product") == "C5502" ||
getprop("ro.product.device") == "C5503" || getprop("ro.build.product") == "C5503" ||
getprop("ro.product.device") == "C5506" || getprop("ro.build.product") == "C5506" ||
getprop("ro.product.device") == "dogo" || getprop("ro.build.product") == "dogo");
but there are 4 lines not 3.
Download the zip again, or flash CM10.1 kernel, then install the rom.
kostasroussis66 said:
Thanks for your interest but i already did, installation aborted status 0.
assert(getprop("ro.product.device") == "C5502" || getprop("ro.build.product") == "C5502" ||
getprop("ro.product.device") == "C5503" || getprop("ro.build.product") == "C5503" ||
getprop("ro.product.device") == "C5506" || getprop("ro.build.product") == "C5506" ||
getprop("ro.product.device") == "dogo" || getprop("ro.build.product") == "dogo");
but there are 4 lines not 3.
Click to expand...
Click to collapse
This is archive not for Xperia P!
For Xperia P need LT22i!
And wrong forum!
For Xperia P only tihs: http://forum.xda-developers.com/showthread.php?t=2341139
@dimon it was the 1st file i used and appeared a problem. I will try again and i will try removing the 3 lines.
@razorka link for cm 10.1 kernel pls?
The kernel is in the zip:
boot.img
thanks guys i just deleted the 3 lines from updeter script and now it is installed! Ty all
An another question: Is it good and stable for everyday use? And when can i insert my PIN code? :S ty
Yes, it's able for daily use, very stable and smooth!