why don't we put together a vm, that has all we need to develop SGY ROMs and what not ?
#1 commonsware 1,6 GB, fast download (but in it's current shape no great time saver)
#2 or an older one, open sourced: http://sourceforge.net/projects/androidva
saves a lot of time and keeps developers "on the same page"
#3 the xPerfect 0.1 appliance is very large 6.8 GB + updates. very big.
#1 just has eclipse & SDK, not yet really kickass dev system. user account is android , password: bugdroid
stuff yet to be added:
everything for UOT online kitchen
dixdas kitchen
various scripts for makefiles, V6, wireless ADBshell asf.
sources of: aroma, CWM, cyanogen, SGY ROM, some open apps like SGS tools and tuxility,
links:
http://htc-linux.org/wiki/index.php?title=Ubuntu_VirtualBox_Dev_Environment
http://forum.xda-developers.com/showthread.php?t=570452 USB pass through in VM
great working ICS vm
seems kinda good stuff..
pls can you explain whats this?
a vm image is a fully set up "hard disk" if you wish. just run a copy and start a developer system. saves you hours of installation of devkits and all that stuff.
Any updates on this vm? I'm very interested.
the vms I found really did not save you that much time. mostly sdk installed and nothing else.
a proper dev vm has much more software on it . dozens of tools.
Related
I just had a quick question, haven't been able to find any answers elsewhere. Figured I'd ask it here. I Was wondering if it's possible to build the Android source so that the resulting Android Emulator disk images contains all of the apps of a normal Android 1.5 system?
I've tried building the source twice now but, the disk images are just the normal emulator disk images (missing most of the default apps & some of the graphical improvements of the 1.5 update). I feel like it must be some sort of setting in the makefile to say what platform to build for.
Any help would be greatly appreciated.
Do I need to follow the instructions listed here? Will this enable the build process to build the emulator disk images so that they mimic the G1 completely (including all default Android apps, etc) ?
http://source.android.com/documentation/building-for-dream
Those apps you are referring to are closed source and no matter how you build it, they won't show up in the emulator. You could possibly install them after the fact, but that is truely hit or miss.
Hey everyone. I am on my fourth Android Device now and want to start developing (cooking) custom ROMS. I have a pretty solid understanding of Linux fundamentals and have a programming background, but no java. I know this isn't a huge roadblock, as I am not looking to develop apps right now, but I figured I would mention it.
My current development environment:
- Mac OS 10.6 (Primary)
And any number of the following virtual Machines
- Windows 7 32 bit
- Windows XP Professional
- Fedora 12
- Kubuntu 9.1
- openSuSE 11.2
- Ubuntu 9.1
I am trying to develop for the Motorola Droid. Many of the Droid Roms are currently being delivered as Nandroid backups, with the exception of a few coming through as update.zip or .rom.tgz.
Here is where I need some help. I realize that update.zips have to be signed. I have seen a lot of methods on signing update.zips /apks on this forum, and have tried a ton (AndroSign, testsign, and several others) and any time I get a signed update.zip, the installation halts on my device. Is the signing method device specific??
To create an update.zip or a .rom.tgz, do you need to have boot.img, recovery.img, data.tar, META-INF and system.tar? or can you create any combination of them?
Finally, what source file should I be using? One thread I saw recommended creating a nandroid backup of a clean 2.0.1 install + su + busybox and pulling apart system.tar. To my knowledge, there is no "factory recovery rom" for the droid like the RUU for some HTC devices. I pulled /system from a fresh backup and tried to pack THAT into an update.zip and rom.tgz and could not succeed either time. update.zip wouldnt install and rom.tgz installed but got stuck at boot loader.
Any help would be much appreciated!
I have scoured google, xda, modaco, alldroid, etc. and havent found the right answers, so now I am reaching out here.
I stumbled across this, i hope the developers on XDA can help...
This is a SD card bootable version of the OS.
It's based on the projectGus release for the eken m001, modified so it uses 256M of ram and the calibration is customized so it can run on the flytouch without the inverted axises.
THIS IS A ALPHA STAGE ROM, maybe the developers here on XDA can create a stable flashable NAND version out of this ?
DOWNLOAD ROM
This is NOT my work, credits go to kiarov for the flytouch 1 build, check original thread HERE.
Instructions :
1. Flash to a SD card,according to instructions found HERE
(Rename the "froyo_flytouch.img" to "debian-m001."(without "img")) before flashing
2. Copy the stuff ("script" folder) from the RUDROID version available HERE
If you don't know what to do with the file, you should take a look at instructions HERE
There are the instructions on how to copy the disk image for linux and windows.
Be aware that you'll need an at least 2gb sd card to copy the files.
Everything works....
BUT:
Kernel version 'unavailable'
when it sleeps, it dismount SD, when it 'wake up', it shows message 'damaged SD'
when you remove SD and put it again, it doesn't recognize
Market apps are only 1.6
Credits go to projectgus for the original eken m001 rom where the flytouch 1 build is based on. Check original thread HERE
Note from projectgus for the EKEN M001 BUILD :
''All the scripts & patches I used are available on github. There should be enough there for a savvy person to fairly easily build this again from an AOSP release.
The kernel used is “my” copy of Wondermedia’s kernel source release. Hopefully as Alexey’s from-scratch kernel adds more features, it will eventually be able to run Android as well.
If you do build anything using this, please please please share source/instructions for what you improve. Every “secret” someone hoards away is a step away from making these devices properly usable.
This Froyo build comes unsupported (sorry), and I’m not likely to do a whole lot more on it. However, one thing I do intend to do is get it running on my Eken M003 (my M001 has serious hardware problems so I can’t really use it as a tablet any more.)
However, I really hope that others will jump in, build on it, and make something good. Enjoy!''
ULTIMATE xda developers' challenge
Android OS 2.1/2.2 > For Flytouch 1
As lately some people are asking me about ROM porting I decided to create this new thread where we can share knowledge about this hard task.
Please note this is a Dev talk thread, so DON'T ASK about fixing a particular ROM problem here. Also don't ask questions like "My phone is bricked! please help!". This IS NOT the appropriate place for it. There are plenty of other threads to help you out.
Also note that this is not a step by step guide (and not a guide at all), it's just a point where you can start from. Android is a very complex system and there are many things I don't know yet. So, research and hard work is what you need to learn it deeply. My first tip is Google really works. Don't be afraid to search
Ok, to the basics. Porting a ROM is no simple task. It requires advanced understanding of how android works and how it is organized. Previous Linux/Unix knowledge helps A LOT. As android is based on this O.S. there are many similarities between both. In fact many ppl consider android to be a kind of linux distro.
The very first task to port a ROM is finding a device which is compatible with your own. For example Defy/Milestone2. Then you are going to choose a ROM to port to your device.
As our devices (Milestone2) have a locked bootloader we now need to find a system image that have a compatible kernel with the ROM we are trying to port. This is mainly based on trial and test and takes a long time. You'll be ending flashing your phone several times with RSD Lite. You should learn how to use MotoAndroidDepacker and how to create a fixed SBF.
The basic procedure to try that:
1. Open original ROM update.zip and remove any files/commands that flashes boot/devtree/recovery/anything.
2. Install this new file on your phone via CW Recovery.
3. Boot into bootmenu and enable ADB so you can read logcat while phone boots.
4. Choose Boot/Normal. If your ROM uses 2nd-init you will need to place/edit/adapt bootscripts into bootmenu 2nd-init folder.
5. Check logcat for errors:
- If you're getting HAL errors you're going to need a new kernel;
- If you can start android without getting HAL errors but still getting errors and bootloop on android animation you should try to replace libs with appropriate original ones.
6. Once you are able to boot android you should test it's features to see what needs to be fixed.
This is what I have to say for now. The thread is now open for discussion.
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
jorgebaruchi said:
At this week, motorola has just pushed the GB official update for Droid 2 and Droid 2 Global....
Can i try to port this new rom to milestone 2 and after a success boot, fix the radio..??
I was asking that, because some people has success on port CM7 to milestone 1, when it originally maked for droid 1...
tks a lot..!!
Click to expand...
Click to collapse
It may be possible, but you'll have a hard time fixing the baseband.
You may have to mod the init.rc scripts and find the right radio binaries (rild is one of them) and drivers.
Ask those ms1 people for help, if they are still with the same phone...
Sent from my Milestone 2 XDA App
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
i guess it is second-init. but not sure
thanks a lot for this !!!
WeeDv2 said:
The only thing i can get from SBF is a bunch of smg files.
But the only ones i can open are
preinstall.smg
CG39.smg
Is there a way to open/see the rest?
2)
Im trying to modify the CM7 rom, what boot does it use? 2nd-init or 2nd-boot?
Click to expand...
Click to collapse
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
sahilarora911 said:
I don't know if this will be relevant or not.
I wanted to know if to do any of this, having a Linux distro as OS a must or can I try my hands at it on a windows based machine. I mean I'm sure that a Linux distro will give certain advantages (as Android is based on UNIX/Linux) but can we get things to work a 100% on windows.
If yes, then will someone be kind enough to get give the list of all softwares etc. which will be required to do the job on Windows machine as well as a Linux machine.
I do know a few softwares but I'm not sure if I have an exhaustive list. I would like to learn and try and at least be able to modify in bits n pieces to begin with.
I apologize if this wasn't supposed to be asked in this thread.
Click to expand...
Click to collapse
Don't worry, this is the right place
As for your question: yes you can work in windows if you like, but using at least a Linux VM is more productive. I don't have a full list of applications to give you, as different mods may require different tools, but I advice you to have at least:
- Notepad++ (essential for editing text files and keeping linux end-line format);
- dsixda's Android Kitchen (http://forum.xda-developers.com/showthread.php?t=633246)
- 7zip (or some other compress tool you like)
- Moded putty for ADB as working with windows command prompt really suck (http://forum.xda-developers.com/showthread.php?t=803225)
- Oracle Virtual Box (if you are going to use linux VM).
r2beta0 said:
SMG files are disk images of certain partitions of your flash memory.
You can only open CG39.smg and preinstall (CG66.smg) because they are the only images in ext3 format. The rest of images may be on ramdisk format or some proprietary format. For more details on partition codes take a look here:
http://and-developers.com/partitions:cdt
You may be able to open and see contents of other partitions but the only one that matters aside from system and preinstall is the boot partition (CG35.smg), which contains the init scripts we should mod in order to make they work with 2nd-init. Boot partition is in ramdrive format. More details here:
http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
http://elinux.org/Android_on_OMAP
It is easier to unpack boot image using Dsixda's Kitchen here:
http://forum.xda-developers.com/showthread.php?t=633246
Edit: To see what boot your CM7 uses just go inside /system/bootmenu/config and look for a file called default_bootmode.conf. That should be the boot method used. It's normally 2nd-init.
Click to expand...
Click to collapse
Thanks again r2beta
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
sahilarora911 said:
thanks r2beta0
- Notepad++ -- got it
- dsixda's Android Kitchen -- downloaded (need some link for a how-to on its usage)
- 7zip -- got it
- Moded putty for ADB -- got it
- Oracle Virtual Box -- can't install Linux on my system as this is a work machine
dunno if I can do without the last option.
Click to expand...
Click to collapse
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
r2beta0 said:
Oracle Virtual Box is an application that lets you run an operational system on a virtual machine, in other words, it doesn't install linux on your real computer. It's a very useful tool that I use everyday. Google for it and learn a bit, you won't be disappointed. About kitchen: the link I provided was download + guide. Read it again. If necessary read the full thread.
Click to expand...
Click to collapse
I know a bit about virtual box but as I said I'm not allowed to have softwares not approved by the IT team to be present on the system. Though I can get away with small things like notepad++ and 7-zip, having virtual box on my system may raise some eye brows.
I'm trying to arrange an alternative system.
Me neither. I must do almost everything at home, and at this very moment I simply don't have any free time. I'm afraid you're not going to see me here very often anymore (maybe in a few months? a year? well, it might be a bit too late for milestone2...)
hi. Have a question, I want to remove baseband from a flashable zip (lets say, CM7 from Tezet) , is it posible? I dont know where to look for it (baseband). Thanks!!
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
---UFO--- said:
Baseband is located in \system\etc\motorola\bp_nvm_default\
But don't remove it, just replace it with files from ROM, which have baseband you want.
Click to expand...
Click to collapse
Ok thanks for the info.
Sent from my A953 using XDA
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Megalith27 said:
Hi All,
Just a quick question. I have ported Paranoid Android 2.10 to MS2 but the problem I am facing is that Reboot goes through Bootmenu and I have to choose reboot from Bootmenu again.
Any inputs?
Thanks in advance
Click to expand...
Click to collapse
I meant to get to it last night, but I was tired after work and fell asleep watch tv. Eventually, later tonight, I'll be uploading PA for MS2. Check my Defy PA thread in 12-14 hours cause I'm about to go to work and I'm not gonna feel like making a MS2 PA thread or updating my Bravo PA thread -- but the Defy Thread is always up to date when I put out new roms.
Also, I'm looking to get either a Defy or MS2 -- I've heard that there's 3G issues with AT&T users (which I am) with the MS2 -- Apparently the MS2 has different 3G frequencies than AT&T. Are there any AT&T MS2 users who are knowledgeable about that? While I can deal with no 3G, edge only, calls only -- I need to make sure I can at least do that before I commit to something.
I'd rather have the MS2 because I want a hw keyboard and I don't have the $300+ to try and get a Photon Q LTE from eBay (and I don't have to change up my repos if I get a MS2). If anyone here knows of a phone that's AT&T compatible, Defy code compatible, and has a keyboard, please let me know.
Thanks.
//Normally I'd post the latter half in the Q&A section, but ya'll don't have one so I'm just gonna piggyback
//My Bravo doesn't have a Q&A page either -- it needs one that's not my PM box...Don't PM me on how to root your phone and flash CM7 -- read one of the 5 guides on the first page of both General & Dev...:silly:
Ok devs need some help here.
I am trying to port a rom to our Milestone 2...but it bootloops on rom animation.
I tried to logcat it but I don't think it gets as far as adb server to detect the device.and just keeps saying "waiting for device"...so I end up with no logcat to diagnose the problem.
I can logcat my current working rom but only after the phone boots....am i missing something here? please, help
Any help is very much appretiated.
Thanks a lot in advance
this rom is only for S7100B
S7100B Zip's Custom Rom 1.5
the philosophy that underlies this first rom (do not expect miracles) is this:
If Android is not at 100% open, with the modifications of the house JXD, it is certainly less
for that cause this rom came WITHOUT any frills, so that the user choose what to have or not have on your console since the emu (not upgradeable) to app (not removable)
v1.5 changelog
-add theme faenza
-add advance task killer
-add my backup of vtl launcher settings
here is the v1.0 changes:
Based on the last official rom for JXD s7100b
- Removed ALL emulators series (since they could not raise it to update)
- Removed all serial applications to be added jxd (because there people who do not use FB Skype etc.)
- Removed serial launcher (really crappy)
-VTL.Launcher 1.6.5-added info link (ADW launcher launcher based on tablet-oriented
-FileManagerHD-added as a manager (much higher than 2 managers istallabili Series)
-Added superuser.apk
Changed clock font
changhed menu font
and that's it for now ..
The next thing I want to add (2.0) have a different boot animation, add a simple task killer, the theme for whiteware adw (if it works on VTL) default background, and another music video player
and then study how to make a backup of the settings of the launcher so who installs from scratch and restore my rom does not have to configure the home
A special thanks goes to SNESFAN and its forum: http://forum.openhandhelds.net/
Bitrider I create a custom rom for the first Android console,
to the reference point of android modding XDA
Android and the whole community
My community reference point for italian open source console users
www.OPENCONSOLE.it
BRIEF-Up Guide
1) get yourself a micro sd and put the files ZCR1.zip
2) make a backup of everything you need to save, (the new rom is really skinny)
3) Introduce the sd in the console
4) turn on the console by holding the keys POWER + MENU(the last button on the right of the 3 keys Android)
5) Wait and you will find in "bootloader)
6) Optional: make wipe of data/user
7) go to apply update from sd and start pressing the start / select
8) navigate and select ZCR1.zip and start the process
9) if all goes well should start installing the custom rom
10) when the process is finished you reboot system
you will come round to set up a launcher!
do not fear the next version will provide a backup of the settings in order to have everything already set
download: http://filesmelt.com/dl/ZCR1.zip
edit 16 may:
there is the 1.5 vers + my vtl launcher setting
download 1.5+ setting: http://www.openconsole.it/download/ZCR1_5s7100b.zip
extract on your sd card
follow the past guide
then go on vtl setting and restore setting
Thanks !
Hello,
First, thanks for your job !
i have linked your work on my french community openconsoles : http://caanoo.forumactif.org/t3185-rom-jxd-s7100b-zcr-v1#24052
Keep On the Good Work
Thanks a lot for this first ROM !
...microsd ordered, my s7100b will be flashed in few days ...
hello i know openconsoles france, and i know BAfelton
you tried out my rom?
i sold my s7100b, but before i made a last version of rom 1.5
-add advance task killer
-add theme faenza for adw (vtl is based on adw)
and i made a backup of my desktop configuration
ill post asap
00Zip00 said:
hello..
ill post asap
Click to expand...
Click to collapse
Thanks !
too bad you sold it, no more versions :/
I regret the lack of bluetooth ( no keyboard ..) but for the price ...
@ openconsoles france users
i read you made a screenshot of my rom
but i had problem to register account on that forum and i cant see it
could you post screenshot here?
Thanx
sorry i can't share them here...
"To prevent spam to the forums, ALL new users are not permitted to post outside links in their messages. After approximately eight posts
"
maybe this works for small link : goo.gl/2gzZV ?
...
ok thanx
updated my friends
post new screenshot if you can
link
filesmelt.com 7100b_ZCR_v1_5_+_setting.zip [/url]
link doent work anymore by chance is there something new out there for roms that i am missing?
Thank you and a question
First, I want to thank you for the ZCR 1.5 custom rom. It has really been great to have an alternate to the stock firmware. I've been trying to determine how to build my own custom rom for the JXD S7100B, but appear to be missing a step somewhere.
I've constructed a ROM and created the .zip image and then attempted to sign it with signapk.jar with the typical android testkeys. However, every time I attempt to update from sdcard zip file in the recovery menu, I'm greeted with an E:signature not verified error. I've tried to create my own certificates using OpenSSL and sign with those, I've compared the ZCR 1.5 custom rom to the latest firmware update from JXD, I've even tried to simply resign the ZCR1_5.zip image with the testkeys. All attempts have failed. I've scoured the internets for as much information as I can find and I can't see any difference between what I am doing and what I am reading. I've tried executing the signapk.jar under 32-bit XP and under 64-bit Windows 7 just on the off chance that there was a precision discrepancy between the two versions of java.
I'm at a loss and would like to know if you would consider outlining the process you use to sign the .zipped image? Do you use jarsign or signapk or some other tool? Are you signing with something other than the testkey certs?
Thanks,
jkgamer
http://www.multiupload.nl/IQP6BJUK15
jkgamer said:
...
I'm at a loss and would like to know if you would consider outlining the process you use to sign the .zipped image? Do you use jarsign or signapk or some other tool? Are you signing with something other than the testkey certs?
Thanks,
jkgamer
Click to expand...
Click to collapse
follow that guide
http://forum.openhandhelds.net/index.php/topic,47.msg118.html#new
Hey Zip,
no ICS update for S7100B coming from you?
i'v sold my s7100B but you can follow the custom rom scene in our site www.openconsole.it
and this is the topic whit all the custom rom for the console whit android:
http://www.openconsole.it/forum/viewtopic.php?f=25&t=869
how good does the JXD S7100B run n64 and psx games with this rom? im thinking about getting one.
not Perfect emulation, but most games run 80 % speed
hm, too bad. what about snes/gba ?
really well
I tried to upgrade on my s7100 and it gives me error
The error is as follows
E: error in /tmp/sideload/package.zip
Can someone help me ?