Database Develop

Cyanogen Mod Offically Supports the IS! - No Download yet, still in beta

UPDATE: 2 Cyanogen developers have picked up the Incredible S and it is being officially supported!! The ROM is in Beta and will be released when ready.
Remeber, the first rule of cyanogen: Don't ask for deadlines!!​
Click to expand...
Click to collapse
Previous version of this post, kept for historical reasons:
Code:
I am sure everyone here wants to see CM7 hit this device. I am also sure that in our collective efforts, we can do it. At the moment, it is just me (or no one else is saying they are trying ;)) I basically want to try and get a team of people to crack the porting problem, because so far I am unable to do it on my own.
Finding information is proving difficult, and I just keep hitting dead ends. Is anyone willing to help? Has anyone ported a ROM from one device to another before? Can anyone point me towards information on how to start / debug?
As a community, this will get done a lot quicker, so if anyone can help please post here. If you idea of helping is posting "[I]I can help, what can I do / tell me what to do /give me something to do[/I]" then thanks, but no thanks.
[SIZE=3][B]Please keep this thread clear of chatter so it can be used for discussing the problem at hand.[/B][/SIZE]

I have ported from the HTC Dream to the HTC Diamond ...
If you wish to get started the way i do it ... Take a cm build from the closest device ... Say the DHD ... And chuck the system.img into an official update zip or any other zip with a working boot.img etc ... Then try booting directly ... If it bootloops ... The first thing you should try is to replace /lib from a stock rom ...
This will get you to boot surely ... But if you manage to boot directly then keep the libs ... After that we need the appropriate libs extra things like the secondary cam that u can take from the stock rom ...
A more detailed way to do it would be to get the ported libs working by using logcat to see whats wrong and replace only the related libs from a stock rom ... Keeping stock libs will make performace related things such as battery in the same state as stock ... So it is best to keep the ported libs ...
I would have done this myself by now but i have a s-on devoce :-/
Anyway can you tell me whats wrong with your attempts? Where do you get stuck? Which device are u trying to port from?
EDIT: idon see why you hit dead ends if u port from a similar device it should be no problem to boot ... Heck ports from the dream to the bloody winmo diamond worked out of the box ... The dream libs worked fine ... Would be nice if u could chuck us a logcat ... Even if i cant figure it out ill ask neopeek ...hes a pro but idon think this will go that far
Sent from my HTC Incredible S using XDA App

I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25
I will try what you said, it's a good starting point, thanks!
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...

Hehe ... Good point ... U cant get a bootloop if u dont even start boot ... I admit ... U sure have a funky way of trying things out ...
EDIT: that logcat ... Did u get it with what i said or what u tried?
Sent from my HTC Incredible S using XDA App

Both gave me that result. Can't really find out what it means other than it couldn't mount the system partition, no idea why
Sent from my HTC Incredible S using Tapatalk

I think the problem comes earlier ... Look at what you have said ... That failed to format part ... I think it screwed up halfway and now its empty ... Have you compared the update script with the one from the dhd? You are porting from the dhd right? Its the best option ...
Sent from my HTC Incredible S using XDA App

I use the same script I use for lpremix so I know the script is fine. Which is why I am stuck.
Sent from my HTC Incredible S using Tapatalk

Hmmm ... We need to narrow this down ... Try copiying in only /app /framework /media ... And also try using the older setup with the stock build.prop ... If u can boot this then the problem is in the rest ...
EDIT: did u also try different update scripts? Try using the dhd one as it is ... I think the problem is there might be a difference in the way the IS is partitioned compared to the dhd ... Cuz idon think we really have a mmc's upto 25
Sent from my HTC Incredible S using XDA App

Have you tried converting the Ace updater script to update script then changing the mount partitions to say from:
Code:
format("ext3", "EMMC", "/dev/block/mmcblk0p25");
format("ext3", "EMMC", "/dev/block/mmcblk0p27");
format("ext3", "EMMC", "/dev/block/mmcblk0p22");
to
Code:
format SYSTEM:
format CACHE:
format BOOT:
Then convert back?

K bro i think ive got some thing ... In /system/etc there is a file called vold.fstab ... Please do a comparison ... There might be a difference there ... Check the cm one with stock ... Also compare the cm7 update script from ace and the update script from a lp remix ... Maybe you just need to change the partition name ... Also try removing those lines completely from the script you are using ... Chuck all the lines related to format...
EDIT: its getting a little late ... Its around 330 am now ... I think ill go to sleep ... Ill see if i can think up of anything else for u bro ... Gnite every1 -_-
Sent from my HTC Incredible S using XDA App

looks like u have the same prob as me bro

l0st.prophet said:
I tried it the other way round, taking an ACE rom and chuckign the INC S kernel into it and i just got
format: format_ext3_device failed (-1) on /dev/block/mmcblk0p25...
Click to expand...
Click to collapse
As far as i know Desire HD is ext3 and IS/DS are ext4.
Try to change the partition information.
See my previous post.
l0st.prophet said:
EDIT: Can't even get a boot loop Logcat just says exec '/system/bin/sh' failed: No such file or directory (2) which is annoyingly obscure...
Click to expand...
Click to collapse
Also here in your script you have a reference to /system/bin/sh which is probably missing from your rom.

hmm didnt even read that, but yes it shud be 4 o.0 or is that why my script is fkin me up?
imma test 3 anyway...

Im back from bed ... Maybe marylandcookie is right ... But where can that problem be? He is using the lpremix update script that usually works not the dhd script ... So why is it trying to chuck up ext3? Are u sure we are ext4?
@marylandcookie: do you have a nickname ... Ur name is real handfull to type out -_-
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Sent from my HTC Incredible S using XDA App

Ext3 works fine, but I will try ext4 anyway. It's us more likely to be a problem in the system files so I will check void.fstab file
The sh file is there, the system partition just isn't mounts properly
Sent from my HTC Incredible S using Tapatalk

it's too diffcult for me...but i believe we can

knightrocker said:
EDIT: do we even have a mmcblk025? The furthest ive seen is 4 or 5 ...
Click to expand...
Click to collapse
I'm not sure what you mean, I suggest you look at the partition table. It's differant from mtd blocks cause its nand, system is definately mmcblk025
Sent from my HTC Incredible S using Tapatalk

Really? Still not used to this whole nand partition thing
Much better with android itself have made any progress?
Sent from my HTC Incredible S using XDA App

I won't today or until Tuesday as I am on holiday and away from a pc, but I will get back to it next week
Sent from my HTC Incredible S using Tapatalk

Ok then ... Ill see if i can think of something by then ...
Sent from my HTC Incredible S using XDA App

[APP] NexusLight - Change ROM for you

Hello,
Here is developed a small software who work on Windows called NexusLight, which allows you to create a ROM for your needs from the flash.
He was appointed NexusLight because I have only tested on the Nexus, but it should work with all phones / roms if the signature verification is disabled in the recovery.
This is actually an adaptation of the software GaospLight (frandroid forum) I had created for the Galaxy's first name.
It allows you to remove applications from the ROM but also to add.
The software interface is in French but in English except for description of the applications (in fact it is the language depending on the language of the OS)
Moreover a video presentation is often better than a thousand words I have made a video where you see the software in operation:
http://www.youtube.com/embed/eNXXEGTUnQA
Download Link
The program will automatically update itself if a higher version available.
Warning: Some antivirus software can detect as malware.
But it is totally wrong is due to the UPX compression when compiling software.
GalaxyUser
NB: I can't post un dev' forum because i'm a new member

Isn't it easier to use 7-zip or WinRAR to open the zip and add/remove any apks you want?

Does Zipping Unizpping Works ? Never tried it to asking ?

So...wow...
Umm?
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.

wpxbox said:
Does Zipping Unizpping Works ? Never tried it to asking ?
Click to expand...
Click to collapse
You don't have to actually unzip the package. Just open it and add/remove apks from there. Though I think unzipping and re-zipping should work too

I agree this app is sort of silly since you can easily do the same thing with winrar/7zip. It might be useful if more features were added to it (e.g. change the kernel, change the boot animation, etc), until then...

7zip.
One zip to rule them all.
Sent from my SGH-T959 using xda premium

[REQUEST]How to insert Reboot option?

Hello,
i search for any guide to how to get Reboot option in power menù, but are for other models and ICS version.
If i try to follow those guides but result are my Nexus S i9023 doesn't boot.
There are someone that want to explain me how to?
Thanks
P.S: Sorry for my bad english

Anyone can teach me? Thanks

look under frameworks / systemui in your build tree. compare stock code to cyanogenmod using deductive reasoning and you will find that cyangenmod has a few extra xml files. One is named powerbutton or something. good luck.
Sent from my Full Android on Crespo4G using xda premium

Modern Combat 3 issues

Got it working! i've had loads of people PM me about this issue so i have now edited second post with the fix to the issue
Hi All, im having issues getting MC3 to run on my HD2 i keep getting a bootloop on 2 of my roms, im using SD builds of AmeriCanAndroid AOSP HD2 GB2.3.7 CM7.2 and NexusHD2-ICS-4.0.4-CM9-HWA-SD V2.0 and it will start to load, download the last 4MB of the game using the Asus TF101 Mod v1.1.1 apk then i click play it goes through the first video then as it gets to start loading the menu it will loop back to before the video, edited my build.prop on both build so phone appears as the Desire HD and im from the uk so language is already UK in android OS, what else do i need to do? i've tried several apk's and several sets of Adreno SD data, not sure what else there is i can do? any help will be appreciated, thanks

To get MC3 working on my HD2 i first had to switch to a Android NAND ROM im using tytungs NexusHD2-ICS-4.0.4-CM9-HWA V2.1 (Kernel: tytung_HWA_r2.4-uniMAC) i then had to edit my build.prop to match this, its from the Inspire/Desire HD
i'd recommend getting ROMtoolbox, backing up your current build.prop then editing the lines mentioned below
ro.product.model=Desire HD
ro.product.brand=htc_wwe
ro.product.name=htc_ace
ro.product.device=ace
ro.product.board=spade
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US/UK <-- Depending on your region, mine was set to UK as its where im from and users reported UK can help as some devices won't boot the game unless system language isn't set to UK
i used this apk *REMOVE WAREZ* then downloaded data etc via wifi if you then wish to you can backup the modified build.prop and then restore your original build.prop in ROMtoolbox but market and everything else works fine for me without restoring the original build.prop
if you have any more issues PM me and will help you out!

htc sensation xl
I want to run mc3 on my sensation xl but it isn't compatible with my device
inse

bump for those interested in getting this working and to
insevanhouts said:
I want to run mc3 on my sensation xl but it isn't compatible with my device
inse
Click to expand...
Click to collapse
just follow second post and it should work for your device, same applies to all other HTC devices of similar spec to the HD2 getting this incompatibility error

besides changing the the build.prop one should go to settings/applications/all/google services.../ and clear data. should work

i have the same problem on skyrocket... how do i do that on the second post? where and how do i edit that build.prop?

[GUIDE]How to Port ROMS from same resolutions phones- Easy way

Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev

Thanks..
Very Interesting and useful..
Infact i find some guide simple to try...
Good Job!

Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app

SnXo said:
Very nice Tobi good job :thumbsup:
Hopefully that gives power to the people for making some good Roms and Programms for us. It isn't that difficult to do just a little bit reading and then learning by doing.
Best regards SnXo
Notice that will work with every rom. The easy way is snap from HOX but you can choose Roms from others too... To keep it iesy you should have the same resolution and Androidversion nothing more... That's it!
Maybe a admin can make this as sticky that would be nice
Sent from my LG-P880 using XDA Premium HD app
Click to expand...
Click to collapse
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app

tobixdev said:
thanks
anyone tried yet ?
Sent from my LG-P880 using xda app-developers app
Click to expand...
Click to collapse
I tried a while ago with this rom: http://forum.xda-developers.com/showthread.php?t=1562603.
The end result was a bootloop. I will maybe try to do it again when I have more time.

this doesn't work with sense without additional work.
Sent from my LG-P880 using xda app-developers app

tobixdev said:
Hi.
If someone have improvement advices for this thread PM me.
This won't work for sense ir smth similar.
I'm not responsible for bricked(or smth similar) devices cause of ROMS ported by this method.
I don't know if this works for non-aosp/cm based ROMS. You may need to do some more things to get it working.
Try to use the same android version for both ROMS For 4.2.2 use Cm For 4.1.2 use Stock ROM.
You won't have a compatible source code. This means you can't update the ROM through syncing and recompiling. But you won't need a Linux distro fot this Method.
Actually its very easy.
firstly follow this tutorial: http://www.fesilo.com/forum/android/guides/113-guide-guide-to-port-roms-fast-and-easy to get a booting ROM
then download this Tool -> http://www.virtuous-ten-studio.com/ it makes de/re-compiling very easy.
now you just have to fix those anoying bugs
to fix Phone.apk FC.
Be sure to put in the submenu smali API level to Android 4.2.2(in VTS) and tick use smali debug output and in the submenu build tick use old signature
Decompile telephony-common.jar from both ROMS.
Copy the X3RIL.smali found in /com/android/internal/telephony from the .jar of your base ROM (cm 10.1,stock rom) to the .jar of the ROM you're trying to port.
Recompile and replace the one within your old one from HOX ROM.
Decompile framework-res.apk from both ROMS.
open /res/values/arrays.xml
press Control+f to use the search function.
enter auto
copy the arrays config_autoBrightnessLevels,config_autoBrightnessLcdBacklightValues,config_autoBrightnessButtonBacklightValues,config_autoBrightnessKeyboardBacklightValues to the .xml off your ROM and overwrite the old ones.
then copy and overwrite power_profile.xml and storage_list from your base ROM to the ROM your trying to port.
Recompile and replace the one within your old one from HOX ROM.
actually this was the magic.
I hope I forgot nothing. Please Excuse me If I did. It's half past 23 here and I had a very exhausting Weekend.
I will update this thread in a few days to make it more userfriendly
You can PM me if you have Questions.
BIG THANKS TO SNXO FOR GIVING ME THE KNOW-HOW TO FIX BIG ISSUES.
and sorry for my English
reagards tobixdev
Click to expand...
Click to collapse
ths very much