Related
Sorry about this question, but when i try to update my rom [ROM] MoDaCo FR15 Fear Edition 8.2 12/5-11 to another one, for exemple to this one [ROM] (15-05) Slick2X-G V4.0 (cm7 .19) (with 64mb ramhack), with clockworldmod recovery v3.0.1.4 (modaco r1) , the device display this error :
assert failed: getprop("ro.product.device") == "p990" || getprop("ro.build.product") == "p990" || getprop("ro.build.board") == "p990" E:error in /sdcard/download/cm_p990full-19.zip (status 7)
thanks for the help
You have to install ROM manager from market and within let the newest recovery install. This one will work...
Sent from my LG-P990 using XDA App
thkx, i will try it..
I stumbled upon this when going through the update-script for the updates and found these lines of code
ifelse(motorola.omapdevtype() == "HS", ui_print("updating HS mbmloader..."));
ifelse(motorola.omapdevtype() == "HS", assert(package_extract_file("mbmloader_hs.bin", "/tmp/mbmloader.img"),
write_raw_image("/tmp/mbmloader.img", "mbmloader"),
delete("/tmp/mbmloader.img")));
ifelse(motorola.omapdevtype() == "NS", ui_print("updating NS mbmloader..."));
ifelse(motorola.omapdevtype() == "NS", assert(package_extract_file("mbmloader_ns.bin", "/tmp/mbmloader.img"),
write_raw_image("/tmp/mbmloader.img", "mbmloader"),
delete("/tmp/mbmloader.img")));
it looks like there are two options NS and HS thoughts?
EDIT: A solution has been found, courtesy of XDA member titanic_fanatic, who compiled a Windows version of aapt that accepts uppercase letters in XML filenames! (Read his original message here.) I've attached it to this post. One of the biggest hurdles to effective theme creation in Windows is finally solved!
----------------------------------------------------------------------------------------
Forgive me if this has already been asked, but I know that it's something that's annoyed theme developers under Windows for a while now. I seem to recall seeing hints about fixing this, but I've done search after search, and can't find it to save my life.
Theme Chooser theme developers under Windows are hobbled by the fact that XML filenames can't contain uppercase letters, which prevents us from theming certain applications (example: com_keramidas_TitaniumBackup.xml would be needed for Titanium Backup). I know that this is a problem related to aapt.exe. Has anyone come up with a workable solution for this issue? If not, I'd like to take a crack at it. I might not get anywhere, but I have nothing to lose.
Obviously, in order to do this, I'll need the source for it. I can do the heavy lifting regarding getting the source and working out how to compile it for Windows, but I need to know where the source is, what to get, and other requirements. If anyone can help and point me in the right direction(s), I'd really appreciate it!
MJPollard said:
Forgive me if this has already been asked, but I know that it's something that's annoyed theme developers under Windows for a while now. I seem to recall seeing hints about fixing this, but I've done search after search, and can't find it to save my life.
T-Mobile/CM7 theme developers under Windows are hobbled by the fact that XML filenames can't contain uppercase letters, which prevents us from theming certain applications (example: com_keramidas_TitaniumBackup.xml would be needed for Titanium Backup). I know that this is a problem related to aapt.exe. Has anyone come up with a workable solution for this issue? If not, I'd like to take a crack at it. I might not get anywhere, but I have nothing to lose.
Obviously, in order to do this, I'll need the source for it. I can do the heavy lifting regarding getting the source and working out how to compile it for Windows, but I need to know where the source is, what to get, and other requirements. If anyone can help and point me in the right direction(s), I'd really appreciate it!
Click to expand...
Click to collapse
Hmm .. + 1 with you .. but the only way is ... ask brut.all ....
Sent from my Galaxy Nexus using XDA App
qazsxdcfv said:
Hmm .. + 1 with you .. but the only way is ... ask brut.all ....
Click to expand...
Click to collapse
Thanks, I guess I'll have to after all (not that I mind doing it). Over 250 views and only one person to respond isn't giving me much hope that someone has an answer.
Have you found a solution for windows ?
Any solution?
Randomly came across this thread looking for info on compiling the aapt binary for Windows. I'm still looking for the answer for that but I do know the change that needs to be made and how to do that part, as I have already done this mod for aapt on Linux. You have to have a full build environment set up, and by that I mean set up to build a full ROM, like CM10 for example. The change to make is in the frameworks source code at frameworks/base/tools/aapt/Resource.cpp.
See this commit for the details:
http://review.cyanogenmod.org/#/c/24204/
Add the parts I highlighted in blue to the two lines below:
Code:
String16 baseName(it.getBaseName());
const char16_t* str = baseName.string();
const char16_t* const end = str + baseName.size();
while (str < end) {
if (!((*str >= 'a' && *str <= 'z')
[COLOR="RoyalBlue"][B]|| (*str >= 'A' && *str <= 'Z')[/B][/COLOR]
|| (*str >= '0' && *str <= '9')
|| *str == '_' || *str == '.')) {
fprintf(stderr, "%s: Invalid file name: must contain only [a-z[COLOR="RoyalBlue"][B]A-Z[/B][/COLOR]0-9_.]\n",
it.getPath().string());
hasErrors = true;
}
str++;
}
m4570d0n said:
Randomly came across this thread looking for info on compiling the aapt binary for Windows. I'm still looking for the answer for that but I do know the change that needs to be made and how to do that part, as I have already done this mod for aapt on Linux. You have to have a full build environment set up, and by that I mean set up to build a full ROM, like CM10 for example. The change to make is in the frameworks source code at frameworks/base/tools/aapt/Resource.cpp.
See this commit for the details:
http://review.cyanogenmod.org/#/c/24204/
Add the parts I highlighted in blue to the two lines below:
Code:
String16 baseName(it.getBaseName());
const char16_t* str = baseName.string();
const char16_t* const end = str + baseName.size();
while (str < end) {
if (!((*str >= 'a' && *str <= 'z')
[COLOR="RoyalBlue"][B]|| (*str >= 'A' && *str <= 'Z')[/B][/COLOR]
|| (*str >= '0' && *str <= '9')
|| *str == '_' || *str == '.')) {
fprintf(stderr, "%s: Invalid file name: must contain only [a-z[COLOR="RoyalBlue"][B]A-Z[/B][/COLOR]0-9_.]\n",
it.getPath().string());
hasErrors = true;
}
str++;
}
Click to expand...
Click to collapse
Thank you for your help but could you tell me where can I find frameworks/base/tools/aapt/Resource.cpp?
I don't understand where to find it?
Sorry to resurrect an old thread, but I've finally come across a Windows version of aapt.exe that accepts uppercase letters in XML filenames, courtesy of XDA user titanic_fanatic. I've modified the first post in the thread with the details. Happy theming!
MJPollard said:
Sorry to resurrect an old thread, but I've finally come across a Windows version of aapt.exe that accepts uppercase letters in XML filenames, courtesy of XDA user titanic_fanatic. I've modified the first post in the thread with the details. Happy theming!
Click to expand...
Click to collapse
That link does seem to work anymore (and the webpage gives malware warning in Norton).
Does anyone else have this file?
hi people i have problem flashing alpha 2 AOSP JB 3g version see the image
so what is the problem
mmostafanyw said:
hi people i have problem flashing alpha 2 AOSP JB 3g version see the image
so what is the problem
Click to expand...
Click to collapse
same problem here...
look inside de zip, in directory: \META-INF\com\google\android\updater-script with u favorite text editor.
the first line say:
Code:
assert(getprop("ro.product.device") == "p5" || getprop("ro.build.product") == "p5" ||
getprop("ro.product.device") == "GT-P7300" || getprop("ro.build.product") == "GT-P7300");
remove and save....
and then works..... usually this message is for is prevent brik your tablet.... if the device does not match.
best regards.... sorry for my eng
gerickt said:
same problem here...
look inside de zip, in directory: \META-INF\com\google\android\updater-script with u favorite text editor.
the first line say:
Code:
assert(getprop("ro.product.device") == "p5" || getprop("ro.build.product") == "p5" ||
getprop("ro.product.device") == "GT-P7300" || getprop("ro.build.product") == "GT-P7300");
remove and save....
and then works..... usually this message is for is prevent brik your tablet.... if the device does not match.
best regards.... sorry for my eng
Click to expand...
Click to collapse
What version of CWM are you using? It looks like the error that occurred for the version before kallt_kaffe rebuilt CWM. Try updating CWM to this before reflashing: http://forum.xda-developers.com/showpost.php?p=21194554&postcount=2
Also why don't you ask this question on the ROM thread? It makes far more sense to do it there than here.
im using cwm 5.0.4
i have download the 3g version of the rom why it is going to break my tablet you mean the version i had downloaded is for the wifi version he write above it 3g version?
sorry for my very bad english
gerickt said:
same problem here...
look inside de zip, in directory: \META-INF\com\google\android\updater-script with u favorite text editor.
the first line say:
Code:
assert(getprop("ro.product.device") == "p5" || getprop("ro.build.product") == "p5" ||
getprop("ro.product.device") == "GT-P7300" || getprop("ro.build.product") == "GT-P7300");
remove and save....
and then works..... usually this message is for is prevent brik your tablet.... if the device does not match.
best regards.... sorry for my eng
Click to expand...
Click to collapse
i have open the file and this is the code they are the same
Code:
assert(getprop("ro.product.device") == "p5" || getprop("ro.build.product") == "p5" ||
getprop("ro.product.device") == "GT-P7300" || getprop("ro.build.product") == "GT-P7300");
Where did you download cwm?
Did you install kallt_kaffe's version of cwm?
Flash the new CWM version from here: http://forum.xda-developers.com/showpost.php?p=21194554&postcount=2
After that, install and enjoy jelly bean.
Solved.. Thx
But very unstable.... Reboot unespecttly many times, ' back to overcome
Sent from my GT-P7300 using xda app-developers app
Q&A for [KERNEL][SINGLE/DUAL BOOT][KK]CM / CM Based / Stock 4.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
help!!!sd card problem!!!
i've flashed everything(including next kernel,BH recovery and the 2 ROMs)i'm running novafusion cyanogenmod 11 as primary BUT I'VE CHOSEN EXT4 FILESYSTEM TO FLASH,the secondary rom as virginity,everything works fine the dualboot is working,secondary recovery exist and the kernel is on both ROMs,but i keep losing apps stored on the extsd card(on cm11)whenever i reboot from primary to secondary then back to primary :crying: ,the apps on the sd seems to be uninstalled so i had to install everything on internal sd which is already taken by the secondary rom(virginity),lease i need your help man,i mean 4 gb are nothing then you can't install apps on sd that destroys my hopes to have the perfect device,please help :crying:
Hi Andi
What do you think about PhilZ-Touch-Recovery (blackhawk-f2fs) for big size SD cards (64GB) ?
Best regards
tomaasz
Can't update NF 10.2
Good afternoon everybody,
i'm using NF's CM10.2 as primary, golden's Omni as secondary rom with this kernel and andi's blackhawk recovery.
i've tried to update my cm10.2 to the latest version, but the installation failed. Since i have no idea how to this in recovery, i can't provide a screenshot or a log of the failing process. I've started the update from the first recovery, the aroma-installer showed up and asked me which file-system i would like to use for several partitions. I've choosen either "leave as is" or "ext4". Then, the installer quits, saying something like "ro.model=GT-i8190-error".
Updating Omni works flawlessly. Unfortunately, i still rely on CM10.2 since thats the only rom i've tested so far without a freezing clock.
Thanks for your help!
I have high battery drain with all next-kernel sinse 1.5 on slimkat in second boot.
benstyle1 said:
Good afternoon everybody,
i'm using NF's CM10.2 as primary, golden's Omni as secondary rom with this kernel and andi's blackhawk recovery.
i've tried to update my cm10.2 to the latest version, but the installation failed. Since i have no idea how to this in recovery, i can't provide a screenshot or a log of the failing process. I've started the update from the first recovery, the aroma-installer showed up and asked me which file-system i would like to use for several partitions. I've choosen either "leave as is" or "ext4". Then, the installer quits, saying something like "ro.model=GT-i8190-error".
Updating Omni works flawlessly. Unfortunately, i still rely on CM10.2 since thats the only rom
Mayby you try to install the cm 11 with f2fs. There is no problem with ext4 and show on OP from android-andy number 3 good luck
Click to expand...
Click to collapse
yorkberliner said:
Mayby you try to install the cm 11 with f2fs. There is no problem with ext4 and show on OP from android-andy number 3 good luck
Click to expand...
Click to collapse
Tried again with today's release. Still the same. I didn't select f2fs. Here's the aroma-log:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : NovaFusion ROM Installer
ROM Version : 1.0
ROM Author : NovaFusion
Device : Samsung Galaxy S3 Mini
Start at : Tue Oct 21 21:34:54 2014
installing samsung updater extensions
script aborted: assert failed: getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden" ||
getprop("ro.product.device") == "i8190" || getprop("ro.build.product") == "i8190" ||
getprop("ro.product.device") == "GT-I8190" || getprop("ro.build.product") == "GT-I8190"
assert failed: getprop("ro.product.device") == "golden" || getprop("ro.build.product") == "golden" ||
getprop("ro.product.device") == "i8190" || getprop("ro.build.product") == "i8190" ||
getprop("ro.product.device") == "GT-I8190" || getprop("ro.build.product") == "GT-I8190"
Installer Error (Status 7)
End at : Tue Oct 21 21:34:54 2014
Sent from my GT-I8190 using XDA Free mobile app
Meight depend on the update-binary Novafusion is using. You can try removeing the assert get prop lines from updater-script
Send from OnePlus One using Tapatalk
Android-Andi said:
Meight depend on the update-binary Novafusion is using. You can try removeing the assert get prop lines from updater-script
Click to expand...
Click to collapse
That did the trick, thank you!
Hi there,
Unfortunatly, i'm still getting clock-freezes / -delays with golden-guys omnirom and this kernel. Is that a kernel-related issue or is it just my device or installed software which causes this problem? My other rom's clock (cm10.2 by novafusion) runs just fine.
Thanks in advance!
Android-Andi said:
Meight depend on the update-binary Novafusion is using. You can try removeing the assert get prop lines from updater-script
I can`t install CM11 or carbon it`s says installer status 7 you say to remove assert from updater-scrpt can you say how to do it please
Click to expand...
Click to collapse
Hi, does this kernel support power settings like "Ignore unstable power" using STweaks or a config file? thanks!