Related
Everyone is allowed to make changes to the VMWare image and re-upload it. If you re-upload the VMWare image with the made corrections, post the download link(s) in this thread. I will update the first post.
If there is a AOSP Developer that is willing to make a complete tutorial, please make one that works and is up-to-date with 2.3.7
The more people we have working on making ROMs, the better.
This VMWare image is:
- Base: Ubuntu 10.04 LTS
- ICS ready
- Gingerbread ready
- Fully updated
- Eclipse with ADT Plugin
- Android Kitchen Integrated
PASSWORD: root
Latest changelog (Coming soon)
- Based on 10.04 LTS instead of 11.10
- Different approach
Download link:
Bypass 24h wait time, limit reached --> Solution? Reset your ip! In Belgium this is easy by restarting your modem/router. This may be different in other countries.
more mirrors will come!
Part 1
Part 2
Part 3
Image is extracted, where do I start?
Continue from this link
How to build 2.3.7 for Nexus S
This is just a snippet that may help you.
repo init -b android-2.3.7_r1 < /dev/null (This branch is ready to use with Nexus S and Nexus S 4G)
repo sync
source build/envsetup.sh
lunch full_crespo-userdebug
make -j8 (-j8 = for eightcores like 2600k, 2630QM / -j4 = for quads 2500K/2620M/Q6600 / -j2 for dual cores / ...)
Click to expand...
Click to collapse
Don't forget to add the vendor files of the device. You need to download the scripts as well of the driver binaries.
Click to expand...
Click to collapse
I tested a quick build. And it's working.
A virtual machine with limited RAM in order to compile AOSP? Definitively not a good idea. Why not dual boot? Sooooo easy to install the worst distro ever (*buntu).
This is awesome. My only problem is that I only have VMWare Workstation 7.
Super! Waiting for this
djjonastybe said:
Dear community,
I made a AOSP developer environment for VMWare Workstation 8 or latest VMWare Player (free).
You can use this VMWare image as a base to build AOSP ROMs. Imade it for those having trouble getting it to work or maybe if you don't have time to set it up properly. Well if you are downloading this you might have a good reason!
Anyway have fun!
If there are any errors let me know.
This VMWare image is:
- ICS ready
- Gingerbread ready
- Fully updated
Download link:
...uploading...
Click to expand...
Click to collapse
Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
You do not have to be an Android Dev to compile Android. I haven't written a single line of code for Android and can compile AOSP 2.3.7 fine.
This is simply to save time. And if you have good enough hardware (like myself) compiling Android AOSP in a VM session works perfectly fine.
Most people that are into computers have a rocking system. I have 12GB ram, I dedicate 8 for my VM and the rest for my main OS (windows 7). Works fine, what's the issue?
Some people don't want to dual boot and sometimes a Linux distro doesn't support certain hardware or can't be installed.
I would appreciate it. THANKS
nice.....this could be very useful
Sent from my Nexus S using xda premium
FeaRThiS: Who would have guessed that an android dev would have difficulty setting up a linux enviroment . . . go figure.
Click to expand...
Click to collapse
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
suksit said:
@FeaRThiS just stated the obvious. I also think the first step to understand how to build an AOSP ROM is knowing how to setup the development environment.
I don't have anything against using a VMWare image. But, IMHO, considering the time for uploading/downloading the file, if you do the setup yourself (in VMWare or whatever), you should have already been compiling your ROM by now.
Click to expand...
Click to collapse
Okay, its not useful for you two.
Next!
I like it and i will try it.
djjonastybe said:
You seem to be the only one against uploading this.
Guys I am still trying to upload it. I am splitting it in 700MB sizes. Crocko's uploadservice is down. I will upload it on depositfiles and multiupload
12,5%
Click to expand...
Click to collapse
I have nothing against it and it may even be useful in case of emergency when you can not access a linux machine, but as stated by @S suxeN the first step for any dev would be learning to create their own dev enviroment.
i didnt say that.
but the statement is right. Anyways i yet think this image is of great use, as you can always start from there, if u did something wront, what can always happen to nun-linux users.
I don't know anything about linux. Is Eclipse with ADT on here by any chance? If not, what IDE is there to develop with in this VM?
I didn't think that far. Eclipse is not installed.
But I will work on it for next release. For now you have to install it manually. I hope tomorrow evening the new vmware will be uploaded!
Hey guys, don't be so hard on the fella. He's doing us a great service in a way. Not all of us are able to bring laptops wherever we go, dual-boot, etc. I just downloaded this to my external drive that I use to keep my stuff on for work and it'll come in handy when I wanna test apps without worrying about nuking my phone.
Also, it helps that I can demo apps on the thing to co-workers on screen than using a phone. That way I won't have to worry about them screwing things up if they decided to 'explore.'
http://code.google.com/android/nexus/drivers.html#crespogwk74
Can someone help me with this? This has the binaries for the Nexus S.
Where do I place the scripts?
I have a vendor folder with several maps in it now. But I don't know what I have to do now.
I placed the 'vendor' folder in my working directory. But lunch isn't showing up crespo in the list.
These are my steps:
Building
I executed lunch. I realised I did not have crespo in the list. So next, I read the line 'Building for devices'.
Eventually I ended up here:
Building devices
Obtaining proprietary binaries
Starting with IceCreamSandwich, the Android Open-Source Project can't be used from pure source code only, and requires additional hardware-related proprietary libraries to run, specifically for hardware graphics acceleration.
Official binaries for Nexus S, Nexus S 4G, Galaxy Nexus, and PandaBoard can be downloaded fromGoogle's Nexus driver page, which add access to additional hardware capabilities with non-Open-Source code.
There are no official binaries for Nexus One, ADP2 or ADP1., ADP2 or ADP1.
Click to expand...
Click to collapse
I clicked the link and downloaded the GWK74 binaries.
Now then I read further:
Extracting the proprietary binaries
Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree.
Click to expand...
Click to collapse
I have the vendor hierarchy...
Do I have to put these files in:
my home folder/bin
OR
home folder/workingdirectory_name
Or what do I have to do now?
updated first post with small hint on how to download 2.3.7 for our Nexus S. Good luck!
yep, i think this is pretty awesome. for me, i'm not an android dev but i've dabbled with theming and porting mods from other phones to the epic 4G previously. i'd love to be able to start with a system ready to go and mess around with some guides to learn how to compile source, etc... thanks.
Nice image man, gonna give it a go later. Thought I'd put my word in the discussion , sure there lots of talented devs, but they have all got different hardware/software and time requirements. So this becomes a useful tool to add to the inventory.
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
demonoid phenomenom said:
this is not to rush the devs, just asking, are they gonna wait till ( i really hope it actually hapens) jb update comes to us to start developing? couse i think our phone haves a lot more to give to us than the stock rom can, again i am not rushing the devs, just asking your oppinion, and since im kinda new to theese forums hardly think any dev is going to bother to even answer this thread
so im pretty much.asking your oppinion
this is just a question , please dont kill me
sent from the gray stuff inside my skull
Click to expand...
Click to collapse
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
jeah thats right, i was wondering because my expirience with atrix 2 , previous to the ics update, i was using supercharger rom series, but again i understand that they got a leak to work on, and a bootstrap to flash the restores they where creating, and that stock leaked rom was awesome
sent from the gray stuff inside my skull
mattlgroff said:
If you mean Custom Roms... we can't do anything until we can pack / unpack the boot.img/or recovery.img to make a custom recovery.
Click to expand...
Click to collapse
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Le_Poilu said:
Only for my own curiosity: what's prevents that ? The x86 arch ? or something else ?
Click to expand...
Click to collapse
Would be nice to know for sure. The current methods cannot find 'Android Magic'.
I'm looking forward to seeing this forum get some custom ROMs too...
Looks like progress is getting on with it now
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
tiberiu24 said:
Any updates on custom ROM making for this device?
I've followed the README from <link to Motorola's sourceforge for razr i, deleted because I'm a new user> , got to the final step, but now I'm stumped. What make target should I choose? 'make full_x86-eng' and 'make generic_x86' have no make rules. A simple 'make' generates a framework build error.
What do I have to do in order to get a bootable image (built from source) for the Razr i?
I'd appreciate any kind of advice. Thanks in advance.
PS: Many thanks Matt, turl1 and the other developers that worked on this device.
Click to expand...
Click to collapse
You won't be able to build a full android system from that source. The most you can do is
Code:
$ . build/envsetup.sh
$ lunch generic_x86-eng
$ make [I]target[/I]
Where target is something like out/target/product/generic/system/bin/bluetoothd or bluetoothd
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Sent from my GT-I9300 using xda app-developers app
hiemanshu said:
I am working on a device tree. Writing it from scratch isn't easy because there is no device I can base this on. No other x86 tree out there. And I still dont have a device. I did make threads requesting for a device but they got closed down. So once I have something built I'll make a new thread.
Click to expand...
Click to collapse
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
turl1 said:
There's at least 10 device trees on the android-x86 project. And AOSP itself has a generic one, to build the x86 emulator platform. And I made a basic one to build recovery already, with support to generate the newer x86 boot image format.
Just saying
PS: I don't own the phone either
Click to expand...
Click to collapse
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
hiemanshu said:
Generic x86 and the razr I are too far apart. Also the android x86 ones are too far apart too (I am working on a android x86 tablet). I have already written more than 450 lines of the device tree by hand, and there is a lot more to go right now. I have patched bionic for x86 builds, I need to patch the build folder next, and even busybox needs patching, etc. I am now working on making a perfect set of the 3 important files, BoardConfing.mk, device.mk and proprietary-files.txt. My android x86 tree is a total of 181 lines (which in itself is twice the size of the trees on android-x86). Its fun, but really time consuming. Also the AOSP ones are generic ones, they will work on any system if you have all the correct drivers installed or compiled via the kernel, but Razr I needs the files to be pulled from the stock build, and it needs a lot of them, including kernel drivers.
-H
Click to expand...
Click to collapse
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
turl1 said:
I'm playing a bit with AOSP 4.2 as I got some free time. This is what I found out so far:
bionic needed no patches. I seriously doubt it needs any on 4.1 (CM) either as recovery built fine.
build needed no patches either on both cases.
dalvik needed a 4-liner to build on AOSP (makefile fixes), I haven't tried to build it on CM
there's no busybox on AOSP, I patched the one on 4.1 already to be able to build recovery, it's all on CM Gerrit as you'd expect from a CM developer like myself
my tree is already 120 lines, as soon as you add the media decoder config and audio routing config you'll go over 180 lines
having proper drivers isn't enough, you need proper HALs too. And I haven't really looked, but I'd be surprised if you had to pull kernel drivers from the stock rom
Click to expand...
Click to collapse
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
hiemanshu said:
1) bionic needs patching, patch already submitted to CM gerrit libdvm basically
2) build needs patching for the boot.img
3) dalvik has been patched
4) Odd, didn't notice that
5) Probably wont required pulling in kernel drivers, but would required pulling in the correct drivers for the defconfig
I'd be happy if you wanted to work together to get this working. PM me
Click to expand...
Click to collapse
Let's continue talking on PM then
re. 2, I actually did need to patch build on AOSP after all . CM on the other hand, has BOARD_CUSTOM_BOOTIMG_MK from the tf tablets.
Hey I posted a rom over at droidrzr.com for use till aosp is ready. This should be enough till we get a jb leak
Sent from my XT890 using Tapatalk 2
Hi Folks
While I don't own a RAZR I , I have been Jaffing around with building CM10.1 and AOSP for x86, I've been getting in going on my FX8120, just need to sort the OpenGLES MESA drivers out.
Anyways I've got CM10.1 built for x86 using the mr1-staging branch ( I think it's been merged to cm10.1 ) and an edited mini-x86 device tree .
Busybox was a B**stard to build though, although on one of the branches there is an .config-minimal-x86 .config-full-x86, still needed tweaking tho.
I submitted my patches http://review.cyanogenmod.org/#/c/27377/ and http://review.cyanogenmod.org/#/c/27373/, however It seems x86 isn't top of cm's agenda.... or I'm missing something about assigning reviewers.
Obviously a base x86 build is only part of the story for you guys as you'll face all the regular problems that emedded devices have, not checked the specs for the RazR but I'm sure there's some binary blobs in your future,
Hack On Folks! :good:
Welcome to the XPERIA TABLET Z MEGA-(INDEX)-THREAD
As the name suggests, this will be a MEGA THREAD maintained by me keeping in place all the ROOT/RECOVERY/ROMS for the XPERIA TABLET Z , under one single thread.
Thread will be regularly updated as and when new updates are out.
INSTRUCTIONS
To help me maintain this thread please drop in a PM whenever you create a thread or spot one which isn't here!
**ROOTING**
[ROOT] Xperia Tablet Z {WORKING!}
*RECOVERY*
**CUSTOM ROMs (Stock based)**
**CUSTOM ROMs (Original Development)**
AOSP
**KERNELS**
Need help!
Who can help? How to install ROOT on SGP321 build 10.1.1.A.253 ?
Suitable ROM for SO-03E
Hello,
I have a Japanese version of the Sony XTZ (SO-03E) with 32gb, wifi, 4G LTE, 1Seg tv tuner (?).
I have been searching for a suitable firmware to flash over the stock. The Cyanogenmod firmwares fail to install through CWM due to the difference in hardware numbers (all of the CM 10 pollux builds are coded for the european units it would seem). Clockworkmod just states that I don't have the SGP### model.
Any guidance for the ROM you have listed or a point in the right direction?
Thanks,
Devices:
HP Touchpad 32gb firesale running CM9 ICS :laugh:
Sony Xperia Tablet Z (SO-03E) running stock Sony/Docomo FW .269 :crying:
CM10 for Tablet Z WiFi SGP311
I have been looking all over for a working root and recovery that will run CM10 for this thing and I cant believe there is NOTHING out there.
I did find a 1 click root solution that worked, but the only recovery I could find that would even boot up was some strange duel recovery that did'nt even work with CM10... Ugggg...
Anyone else have any luck with this tablet?
Hey, I'm a new Xperia tablet Z user...
So I'm going to build my ROM for Xperia tablet Z (LTE), But the problem is that I don't know much about the Xperia devices... As what I can see is that xperia tablet Z is using same CPU, GPU and Qualcomm Snapdragon APQ8064 as nexus 4...
But confusing part is the recovery. Isn't it possible to use recovery as recovery.img instead of including it into the zImage...? I don't want to break anything so I am not going to mess with this device.
thunderising said:
Thread will be regularly updated as and when new updates are out.
(Last edited by thunderising; 17th May 2013 at 08:42 PM.)
Click to expand...
Click to collapse
hmmm....
technaudio said:
hmmm....
Click to expand...
Click to collapse
Lol... ya I know I was thinking the same thing.
Hi, i try to install the adb driver for my xperia tablet z manually (windows 8 64bit) but i dont know wich one is the right one...
I have a "Sony sa0101/Sony sa0103/Sony sa0105 and Sony sa0106/7/8/9) 7 different drivers...
With my Xperia Z i found a Guide wich Driver to use, with my Tablet z there is no guide wich driver to use...
I hope someone can Help... thx in advance
EDIT: Driver is "Sony sa0107"
If you have Problems with the ADB Driverinstall on Windows 8 use option to manually select drivers from the list on your Computer and look for ony sa0107
Ordoron said:
Hi, i try to install the adb driver for my xperia tablet z manually (windows 8 64bit) but i dont know wich one is the right one...
I have a "Sony sa0101/Sony sa0103/Sony sa0105 and Sony sa0106/7/8/9) 7 different drivers...
With my Xperia Z i found a Guide wich Driver to use, with my Tablet z there is no guide wich driver to use...
I hope someone can Help... thx in advance
EDIT: Driver is "Sony sa0107"
If you have Problems with the ADB Driverinstall on Windows 8 use option to manually select drivers from the list on your Computer and look for ony sa0107
Click to expand...
Click to collapse
I believe there is an FAQ answer for installing drivers on windows 8 on flashtool.com
hey!! help
i want to know hot to swap SD without root
Someone update this thread already
Why start a thread with promise to update.... its been almost five months with nothing added when there has been some things going on in the tab Z forum scene. Someone should un-pin this cause I see the tumble weed drifiting around.
KanjiMan1977 said:
Why start a thread with promise to update.... its been almost five months with nothing added when there has been some things going on in the tab Z forum scene. Someone should un-pin this cause I see the tumble weed drifiting around.
Click to expand...
Click to collapse
my thought exactly....close this thread!!!
heeeeeeeeeeeeeeeelppppp MEEEEEEEEEEEEEEEE
wanna install the games on the memory caaaaaaaaaaaaaard
be7ery said:
wanna install the games on the memory caaaaaaaaaaaaaard
Click to expand...
Click to collapse
You won't find that here. Still.
Secondly, how many more times, and in how many more threads are you going to ask this question??
You have already been given a few suggestions as to what might work, but you have failed to give any feedback as to whether they do. So I can only assume you haven't tried it And you expect somebody else to do all the hard work and testing for you.
Sent from my C5303 using Tapatalk now Free
Hello All,
I'm working on porting KexecBoot, the kernel-based graphical bootloader to the A500. While we already have a wonderful multiboot bootloader, it's fairly limited. Being able to load up a Linux environment before booting into another kernel allows us to mount virtually any sort of filesystem, boot images from a networked drive, and change boot configurations by just editing a text file. Nothing really "works" as of right now, but hopefully something cool will come of this. I'll clean up this post once I get the kexec kernel to boot properly.
Changelog:
14Nov2014
ext4 detection and boot.cfg loadable from data partition!
Initial touch control working, no keyboard needed!
Fixed up graphical errors. No more random black streaks of debug on screen.
Initial release
Crappy proof-of-concept. Nothing works.
To Do:
Boot Android from kexec-enabled kernel
Boot kernel from USB
Current Version
kexecboot-picasso-14Nov2014.img
Original, crappy demo:
kexecboot-poc.img
Just run:
Code:
fastboot boot kexecboot-picasso-14Nov2014.img
Kernel Source (Thanks digetex!)
Reserved for Future Use
anticipation
Excellent!! - Mr. burns (Simpsons)
Can't wait to see this working. I have a Nexus 7 using MultiRom, really cool. So something like that for our A500's is going to be awesome. Wish I knew more about developing to help you out.
Have safe and merry holiday.
Need a Guinea pig?
Will do some testing for you if needed. Just let me know what I can do to help this venture out. I have V8 bootloader right now.
HasH_BrowN said:
Will do some testing for you if needed. Just let me know what I can do to help this venture out. I have V8 bootloader right now.
Click to expand...
Click to collapse
I'll be posting all updates publicly, so you'll be able to test things out as soon as they're released. My Uni courseload is a bit heavy this semester, which has slowed development down significantly. I'm still working on things though, don't worry.
Not a problem, I'm just looking forward to this. This is a big leap for our tablets. What limits will be set on how many ROMs can be installed side-by-side? (Secondaries would be ramdisk?).
Thanks for the fast reply.
HasH_BrowN said:
Not a problem, I'm just looking forward to this. This is a big leap for our tablets. What limits will be set on how many ROMs can be installed side-by-side? (Secondaries would be ramdisk?).
Thanks for the fast reply.
Click to expand...
Click to collapse
Eh, not really. The current Alt bootloader already supports booting multiple kernels. This is nothing more than a way to achieve the same goal through kexec, with the possibility of booting images from extsd.
Sent from my LGUS990 using XDA Free mobile app
apapousek said:
Eh, not really. The current Alt bootloader already supports booting multiple kernels. This is nothing more than a way to achieve the same goal through kexec, with the possibility of booting images from extsd.
Sent from my LGUS990 using XDA Free mobile app
Click to expand...
Click to collapse
But with V8/V9 boot loader you can only have 2 OS's installed. With kexec MultiRom on the N7 the limit on how many ROMs would be how much storage space you have. I've had 14 ROMs installed at one time (for testing purposes).
While the V8/9 boot loader is good, it still has its limitations; I am absolutely in no way putting down the developers work. The interface can be daunting to some, where a GUI would be inviting and end-user friendly (to me it isn't relevant what interface it has). The ability to have more than just those 2 ROMs, that would be the icing on the cake.
HasH_BrowN said:
But with V8/V9 boot loader you can only have 2 OS's installed. With kexec MultiRom on the N7 the limit on how many ROMs would be how much storage space you have. I've had 14 ROMs installed at one time (for testing purposes).
While the V8/9 boot loader is good, it still has its limitations; I am absolutely in no way putting down the developers work. The interface can be daunting to some, where a GUI would be inviting and end-user friendly (to me it isn't relevant what interface it has). The ability to have more than just those 2 ROMs, that would be the icing on the cake.
Click to expand...
Click to collapse
The v9 bootloader can boot as many different kernel + initrd combos as we want. There's no limit in the amount of things it can boot. Even though they're both based on kexec, I am not porting MultiRom to the A500. I'm just getting a kernel-based bootloader up and running.
Glad to hear, I was hoping you weren't just going to port multirom. So I'll just wait to see what you do with this. Take your time with classes, enjoy it. I will keep checking this thread for updates. Thanks
Okay, so i just saw the xperia acro s got an alpha lollipop build
with nothing working, but hey!
Its a start!
I need help to port it to the xperia ion, xperia s.
THough not functional, but a first build will help.
So can someone please tell me how to port the rom from Acro S to Ion!
ACRO - S / ION / Xperia S Have the same specs too!
So if anything starts working in the hardware section, it probably would be easy to fix the bug on Ion/S too.
So please!
Can someone guide this complete noob to cross port a rom to device of completely same specifications!??
Lets build lollipop and put sony to shame! :highfive:
arjun921 said:
Okay, so i just saw the xperia acro s got an alpha lollipop build
with nothing working, but hey!
Its a start!
I need help to port it to the xperia ion, xperia s.
THough not functional, but a first build will help.
So can someone please tell me how to port the rom from Acro S to Ion!
ACRO - S / ION / Xperia S Have the same specs too!
So if anything starts working in the hardware section, it probably would be easy to fix the bug on Ion/S too.
So please!
Can someone guide this complete noob to cross port a rom to device of completely same specifications!??
Lets build lollipop and put sony to shame! :highfive:
Click to expand...
Click to collapse
You need a kernal, drivers, porting knowledge .
JustPlayingHard said:
You need a kernal, drivers, porting knowledge .
Click to expand...
Click to collapse
Same chipset
Same Resolution
Same Processor
Same Ram
Same GPU
Same Camera
I thought cross porting to devices with completely same hardware was easier than building from source:crying:
Heres the specs comparision anyways
http://www.gsmarena.com/compare.php3?idPhone1=4798&idPhone2=4781
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Felimenta97 said:
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Click to expand...
Click to collapse
I know!
Theoretically, older android roms could be ported without any hassles. to devices of same specs.
Replacing app, framework,media in the two zips should technically hvae a fully running rom.
BUt on extracting the zip for acro S, theres nothing that looks familiar:crying::crying::crying:
can anybody help!?
Felimenta97 said:
Just to complement, the devices are pretty much indentical, hardware wise. The differences are VERY minor:
Ion has an MicroSD and a 4.55 inch screen, and 16 Gb internal.
Acro S has MicroSD, 4.3 inch screen, 16 Gb internal, is waterproof.
S doesn't have MicroSD, 4.3 inch, 32 Gb internal.
Except for that, they are exactly the same.
Click to expand...
Click to collapse
Hi old buddy...what's up...long time no see...
arjun921 said:
I know!
Theoretically, older android roms could be ported without any hassles. to devices of same specs.
Replacing app, framework,media in the two zips should technically hvae a fully running rom.
BUt on extracting the zip for acro S, theres nothing that looks familiar:crying::crying::crying:
can anybody help!?
Click to expand...
Click to collapse
You tried to Google that?
I'm almost 100% sure Google will show many tutorials on XDA...
If those devices are exactly the same - that shouldn't be difficult task.
But what are you planning to do with a kernel?
funky0308 said:
Hi old buddy...what's up...long time no see...
You tried to Google that?
I'm almost 100% sure Google will show many tutorials on XDA...
If those devices are exactly the same - that shouldn't be difficult task.
But what are you planning to do with a kernel?
Click to expand...
Click to collapse
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies
Neways in those guides, it shows to replace files from the Port Rom and replace it with Base Rom.
For that, when i opened the zip of acro s, there are no folders!
And for the record, those guides are quite dated...
I cant even manage to port Kitkat roms. It always goes into a bootloop
For the kernel, i was hoping to use Xperia S's kernel, since that device is supported by AOSP.
arjun921 said:
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies
Neways in those guides, it shows to replace files from the Port Rom and replace it with Base Rom.
For that, when i opened the zip of acro s, there are no folders!
And for the record, those guides are quite dated...
I cant even manage to port Kitkat roms. It always goes into a bootloop
For the kernel, i was hoping to use Xperia S's kernel, since that device is supported by AOSP.
Click to expand...
Click to collapse
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
funky0308 said:
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
Click to expand...
Click to collapse
You're exactly right. But I'm not quite sure how to extract .dat files
The system consists of .dat system files
I've Attached a screenshot of the contents of the zip too
And thanks a ton for atleast trying to help!:good:
In the mean time, I'm also setting up An Ubuntu Machine to build from source.
funky0308 said:
What you mean by that "when i opened the zip of acro s, there are no folders!"?
Which zip is that? AOSP Lolipop for Acro S?
If there's only META-INF folder, then you should have system image in that folder (system.ext4), you have to repack that image to see all folders and files (app, framework, bin etc...)
I don't know much about compiling or porting ROMs but if you provide more informations I'll try to help.
Post a link pf that zip for Acro S so I can see file structure or...better solution, please post screenshoots of ZIP structure (that one that doesn't have folders)
If you have a ftf file for a base you should repack it using flashtool but this is, obviously, something different.
Still....
Flashtool should be the tool you need.
Post some more informations and we'll find solution together..
Searched google first.
Then asked here, cause last time i posted a nooby question, i was fired with Rude replies...
Unfortunately...you are right...XDA has changed and there's not many users who are ready to help
Click to expand...
Click to collapse
The same developer who's developing for Xperia Acro S is going to develop for Xperia Ion and acro S too!!
http://forum.xda-developers.com/showpost.php?p=56753406&postcount=37
Should we still continue??
arjun921 said:
You're exactly right. But I'm not quite sure how to extract .dat files
The system consists of .dat system files
I've Attached a screenshot of the contents of the zip too
And thanks a ton for atleast trying to help!:good:
Click to expand...
Click to collapse
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
arjun921 said:
The same developer who's developing for Xperia Acro S is going to develop for Xperia Ion and acro S too!!
http://forum.xda-developers.com/showpost.php?p=56753406&postcount=37
Should we still continue??
Click to expand...
Click to collapse
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
I'll try that. Mean while, waiting for repositories to get downloaded
Sent from my Xperia ion using XDA Free mobile app
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
And yeah
Most probably gonna stick to building a new ROM from source but after a trial with Acro S rom. The thing is i dont know how to build from source. Though RIL, wireless etc. Might take some time, but at least its better than not sitting hand in hand!
I'll update with how it goes!
Again thanks a tonne for helping out!
Sent from my Xperia ion using XDA Free mobile app
funky0308 said:
No problem...that's why we are all here...
I'm using FTK Imager for ext4 files you can try with it maybe...
It's very simple to work with and it'll mount that image so you can extract/work on files and folders you need.
You just have to extract image from zip and mount it with FTK Imager.
File will mount to one separate virtual disk (check screenshoots)
---------- Post added at 03:13 PM ---------- Previous post was at 02:56 PM ----------
Why not?
It's not bad to learn something new..
And you can build your version different, add or remove some apps and features.
Also, it's great if there's recognised developer who will build ROM for those devices.
That way, if you bump into wall you can ask him or check how did he built ROM.
As I said, I'm themer, not developer but I know few things... So if you need anything just tag me here and I'll try to help.
BTW - apparently, you have working kernel built by AOSPXS team, so that's good.
I guess you saw this already but I'll post again.
LINK
You have all sources on github (check that link), why don't you compile ROM from sources?
You'll have same problems like all the others but you'll learn many new things .. Maybe you find a solution for RIL, GPS, wifi...or something else.
Click to expand...
Click to collapse
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
arjun921 said:
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
Click to expand...
Click to collapse
If it passes kernel logo and stuck/loop on OS bootanimation - you are certain that problem isn't in kernel - that's good... (at least, kernel should be OK)
Try to remove everything except necessary apps for system to boot.
It could be anything...
Driver probably...really don't know...
funky0308 said:
If it passes kernel logo and stuck/loop on OS bootanimation - you are certain that problem isn't in kernel - that's good... (at least, kernel should be OK)
Try to remove everything except necessary apps for system to boot.
It could be anything...
Driver probably...really don't know...
Click to expand...
Click to collapse
For starters the fact that it got past the kernel splash screen was great news! Atleast that's a start!
I'll try removing unnecessary apps.
Mean while, I might have another theory. Kitkat by default runs on Dalvik. Lollipop runs on ART.
Could that be a reason, why it isn't booting up?
Any idea which are the folders that house the drivers in kitkat and lollipop?
arjun921 said:
@funky0308
Bro,
Repositories still havent finished downloading.
Mean while i managed to build few Lollipop zips based off these guides
http://apcmag.com/port-roms-to-your-android-device.htm
http://forum.xda-developers.com/showthread.php?t=1957219
Anyways, 13 builds later.
I finally managed to get into the boot animation.
But again, its in a bootloop!
How do i know what is wrong with my zip!?
Btw first 5 builds were using the acro s's lollipop zip.
Rest were using Xperia S's lollipop zip
USing Base rom as AOSP 4.4.4 for ion for porting
Click to expand...
Click to collapse
That is the problem. You are using 4.4.4 ROM as a base ROM. You have to use same android version to cross port. Otherwise it won't work.
You need a Lollipop kernel and a system to do that.