Database Users

Droid has been rooted!

I know. This is the hero forum. But if anyone has a droid or knows someone with one maybe we can get a dump?

Forgot to, post the link
Http://alldroid.org/viewtopic.php?f=210&t=567

awesome! i'd expect you goons to have vanilla 2.0 ready for the mass sprint crowd by tomorrow right? lol isn't a dump all we'd need? pardon for my ignorance but what changes would be made to be compatible to the cdma hero?

Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).

flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
+1
I could use those apk's to build a "fuller" AOSP... that is assuming data can be made to work.

Thats what I'm hoping for. So please everyone who has access to a droif, root it and get a dump for us. Please

I was excited for droid users to find out it had been rooted. Now I am really excited because I didn't even think of the benefits it would bring to us!

flipzmode said:
Excellent! Now we just need a full rom dump (not just the /system folder which is all that's available right now).
Click to expand...
Click to collapse
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570

WhiteWidows said:
Request made @ AllDroid
http://alldroid.org/viewtopic.php?f=210&t=570
Click to expand...
Click to collapse
Sweet. Post back here if they provide it please. I can only watch so many forums. heh.

So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.

NCX001 said:
So let me get this straight, a full dump from the Droid will help us get 2.0? If so AWESOME! I have a friend who has one, I'm sure he'll be rooting tonight I can get a dump tomorrow if you don't get one sooner.
Click to expand...
Click to collapse
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.

flipzmode said:
It's more of a theory than anything. But if we can get their rom booting on our phone then we have a much better chance of getting things working rather than the gsm version we've been hacking up to try and work.
If anyone has access to a rooted droid then let me know. Although it will be much better once they have access to nandroid because pulling these files while the phone is booted up doesn't always work.
Click to expand...
Click to collapse
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org

nelson8403 said:
I don't think that's true.. our kernel/drivers are way different than theirs.. we will be about the exact same point that we are now, and there are full rips out of the droid now on alldroid.org
Click to expand...
Click to collapse
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.

flipzmode said:
I agree but it's a lot easier to make a trackball work, to make leds work, and to make wifi work rather than trying to make it work on a radio that it wasn't designed for.
The image that the guy posted on alldroid is corrupted. It won't unyaffs. And based on the file size I would say it's just a system dump anyways.
Thanks to whitewidow I was able to get my hands on the boot.img by copying it off of /dev/mtd. The build went smoothly however it reboots instantly after the HTC logo. It is never recognized by the debugger. So this is either caused by corruption from how we obtained the boot.img, or the architecture / processor are just too different to work on ours at all. I am not the type that can build kernels from scratch though so maybe someone out there better than me will get it soon.
Click to expand...
Click to collapse
I'm pretty sure stuff compiled for the OMAP arch. Droid is not going to work in our Qualcomm arch. Heroes. I tried using "chat-ril" executable from Droid on my Hero and that doesn't work at all. OMAP and MSM have their own kernel trees as well, so their kernel probably won't boot on the Hero.

It's OMAP alright.
You wont get any of the normal binaries to run.
You can however grab some apks from it.
There is a dump out already btw, has been for almost a month now.

There has been a system dump yes but we are talking about a full dump including the boot.img file.

Boot image contains nothing useful for our purposes.
If you absolutely have to have the boot image someone posted it over on alldroid.org.

is it possible to get the new lockscreen from newly updated droid as verizon has spreaded 2.01 update for droid? cheers

T-mobile VoicePlus Beta

So has anyone on here gone into the VoicePlus Beta? A lot of people on there are curious if anyone has looked into rooting the img or extracting the Apk. http://forums.t-mobile.com/t5/Voice...ash-the-Voice-Plus-Beta-ROM-Image/ta-p/325923 Even one of the mods has said he uses Cyanogen and was wondering if anything was going on over here.
p.s. Cyanogen....you ROCK!

wm1 said:
So has anyone on here gone into the VoicePlus Beta? A lot of people on there are curious if anyone has looked into rooting the img or extracting the Apk. http://forums.t-mobile.com/t5/Voice...ash-the-Voice-Plus-Beta-ROM-Image/ta-p/325923 Even one of the mods has said he uses Cyanogen and was wondering if anything was going on over here.
p.s. Cyanogen....you ROCK!
Click to expand...
Click to collapse
why not just extract the apk yourself using an appmanager? the post to forums
complete

Honestly...because I've never done it. ;-) I know not a really good reason, but between school, work and the fam...I haven't been able to take the time to learn. I'm hoping that over my next deployment (I'm in the Army also) that I can learn to create an app and maybe cook a ROM.

Interesting
I like the CityID and the call divert and call defer seems neat - hopefully better visual voicemail than T-mobile's other app.
I'd like to see it integrated in Cyanogen, and SuperD roms

its a waste, dont flash u will LOOSE ROOT

i pulled the system image
ok, I've been picking this up as I'm going... I extracted the nbh file and now have .nb files, but I dont know where to go from here...
anyone can point me in a direction would be helpful. I have SDK installed and can make and start a virtual device.

possible to port over samsung moments 2.1?

ok samsung just got their 2.1 leak
http://www.engadget.com/2010/04/08/eclair-shocker-android-2-1-leaked-for-samsung-moment/#comments
is it possible to somehow get this on the hero? like complete transfer, with no sense etc...

Already talked about.....
http://forum.xda-developers.com/showthread.php?t=660179

Have are own leak who care's just adding more of the same posts. If you must have it go to the market and download home switcher and switch to stock android launcher. There now you have the moment leak.
DO A SEARCH

chippillie said:
Have are own leak who care's just adding more of the same posts. If you must have it go to the market and download home switcher and switch to stock android launcher. There now you have the moment leak.
DO A SEARCH
Click to expand...
Click to collapse
1. you are being unnecessarily rude.
2. yes there is a post on this already.
3. I am working on getting a port of this to boot tonight.

obelisk79 said:
1. you are being unnecessarily rude.
2. yes there is a post on this already.
3. I am working on getting a port of this to boot tonight.
Click to expand...
Click to collapse
Your a **** I was about to go to bed!
But I am still going to bed, drop me a PM if ya need any help on this would love to try it out!
Roman

Seriously not worth the time to port it. You'll end up with virtually the same functionality as Darchstars AOSP 2.1 build. Depending on what kernel your using if you use 2.6.26 then camera and video recording aren't going to be possible and I'm afraid that if you use the leaked HTC 2.6.29 kernel your going to run into problems with the touch screen since HTC has a non standard power management implementation in that kernel that doesn't play nice with android and the touchscreen even though getevent will show screen presses from event1. Unless someone has the source for that 2.6.29 kernel so you could revert the changes. The only good that might come out of the leak is functioning mms and visual voice mail.

I'm merely doing a straight port, going to get it to boot then release it for someone else to mess with.

I'm just saying that for others just because it's a phone from sprint doesn't meant that it's magically going to work. Some people here understand and some don't. It's not impossible port it just that it's not going to be fully functional when it is ported. Your working with something built for different hardware. Sure you can swap the libs to get it going but you'll end up with something we pretty much have already in the AOSP 2.1 build.
I gave in to temptation and I'm working on it too. Converting the factoryfs.rfs is taking forever.

I wasn't able to find a way to convert them... I'd love to know how, but I managed to find a system.img someone dumped shortly after the leak was posted. Thats what I've been working on.

Link? Cause this is taking forever. It's a ruby script I'm using.

http://www.mediafire.com/file/0ncjzjnymzm/Moment 2.1 DD03 System Dump.zip

thanks. i attached the ruby scrips that convert the rfs to a mountable vfat image.

pretty fresh build from 04.03.2010

awesome... I just need the ramdisk from the leak to get this booting now.

Did u try using the ruby script to extract rootsfs.rfs? The init.rc might be in there. Unless there is a boot image floating around the web that we can extract and use.

Havent tried it yet

Making a Gingerbread NAND ROM for HD2

Ok, I'm loving Gingerbread, but m-deejay has been including Cyanogenmod in his recent builds, which I don't want.
I'm REALLY keen to work on my own Gingerbread build...but need pointers on the steps I need to take.
I want to use a clean custom Nexus One Gingerbread build, such as http://forum.xda-developers.com/showthread.php?t=885784
Then I'll have to replace the Nexus drivers and stuff with the HD2 ones...this is where the problem starts...how do I know which files are needed for HD2 specifically?
And then I need to add/remove apps etc to customise it?
I don't want anyone to hold my hand, just to at least point me in the right direction, as finding this information seems to be very difficult, unlike Windows Mobile cooking, which has lots of good tutorials...even though I'd expect that to be the other way around
I taught myself WM cooking & dev, but this is a whole new ballgame to me....
Appreciate any help I can get...
I'll happily donate a few $ to anyone who can help me get a stock build going...

No one able to shed ANY light? Give me ANY pointers?
Like I said, I'm willing to donate $ if I get help to get a ROM built...

Good pointers!!!
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.

NemanjaLO said:
Have you tried with this tutorial?
SEE THIS!!!
This is the best step by step guide, and there is everything you need to port/make good working ROM for LEO.
Regards.
Click to expand...
Click to collapse
Yea I saw that, thanks...only problem is that it's an old build, and it's miui.
Where do I find the latest drivers etc? And how is a NAND build different? How do I package up a NAND ROM?

I was thinking the very same thing but when I started looking into it I got put off by the complexity and the time it would take.
Have you thought about just modding MDj's ROM, stripping it back to bare ginger and replacing the bits we dont want, this might be easier that building one from scratch.

Yea, it's a possibility...but I won't learn as much doing it that way...and I'd rather try to create my own than use someone else's hard work as a base, if you know what I mean.
I have time, and am willing to learn as much as I need to...I just need some pointers...there are plenty Android HD2 chefs now, surely one of them is willing to help out

It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.

I'd love to see this too!

SamanthaMarquez said:
It's really not that difficult. I didn't really like the CM mod either, so created my own stock rom. I'm now at the point where I got it all working. I don't mind to give you a helping hand if you really are interested.
Click to expand...
Click to collapse
Hey,
yes I've VERY interested...I'm hoping to get a stock-ish one together with my own little touches...maybe release one if I learn enough about it.
Any help you can give would be much appreciated...
Even to start with, a list of the basics...ie get ROM dump, extract xyz, do this...anything at all...
I just got back from a swim at the beach to relax, intending to come back and try to figure it out on my own with what help I can get from that page linked above...but if you have managed to get one together, thats even better

This might be of some use for windows users (I've successfully tried extracting MDJ's Gingerbread system.img with it).
http://android.modaco.com/content/z...-boot-recovery-system-userdata-kitchen-ready/

yea extracting is easy...but I would prefer to use a clean build to start from, rather than m-deejays...trying it using the guide in the link above with the Nexus S dump...having to use some donor files from m-deejays build though...still trying to get my head around it all

Well I gave it a quick try using the above guide, and it gives "NAND Kernel Open Fail".
I used m-deejays kernel, and put all the relevant files into the correct directories before making the system.img, and i put initrd.gz and zimage into boot.img, so I dont know what I did wrong...?

You don't use system.img on nand. You need to create a yaffs.img. Which I've never done before. I've only made builds the sd way, not nand. Maybe all you have to do is rename the .img after you create it. You should jump on irc, room #htc-linux-chat. You would get your answer in like 5 secs;p

NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2

i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G

Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.

g.lewarne said:
i think what would be a cracking idea is if someone were to create 3 "standard" kitchens for anyone to download and start modding with.
kitchen 1) desire / desire HD with NO mods
kitchen 2) Froyo / gingerbread with NO mods
kitchen 3) Froyo / gingerbread with Cyanogen included
they should just be 100% stock but able to build a fully working rom. This way everyone can start to learn, and its always easier with a complete kitchen and just as educational - moreso as you get to see the correct layout for files / directories and all the correct tooling is already in place.
I will add to davids "donation" pot if someone were to make these available, whatever david is willing to donate and i will add another $20 (US) or £15
Whether they be Windows or Linux based kitchen does not matter to me, but i believe that android being open source these resources should be made available
G
Click to expand...
Click to collapse
Yea, something like that would be handy...but even to start with, I'd just love to know the basic processes needed to get a basic Android build running on the HD2, without having to rely on someone elses current build.
I tried the link above, and it did sort of help understand a little of whats going on...but this stupid kernel error is preventing me from knowing how my test build works/or doesnt work...
I mean I had too use m-deejays gingerbread dump to get some of the driver files etc from...but where does he get them from? Thats the stuff I dont know...
It's obviously not overly difficult as there are so many devs pumping out HD2 ROMs...would just love one of them to share the secrets
Cash - not sure ... depends on how much help I get, but I'm willing to donate along the lines of US$20 or so...
mattfmartin said:
Your right, not thinking clearly from all the jack daniels. You do need yaffs tools to mess around with the system.img though...#htc-linux is the dev channel. #htc-linux-chat is where you go to ask questions. Devs don't even go in that channel. Just chefs fire the most part. That's where everyone goes to learn how to build.
Click to expand...
Click to collapse
hehe...
What server is that chat room on?

the_scotsman said:
NAND ROMs do use system.img, have a look in any NAND ROM, you'll see system.img, boot.img and the flash files.
Yaffs is the filesystem...I created the img files with the "mkyaffs2image" command.
(As per this thread: http://forum.xda-developers.com/showthread.php?t=897940)
I've made all of these but get the damn kernel error...it can't be difficult, lots of devs have released ROMS...surely someone is willing to help?
I'd rather not go into irc, as thats the dev channel isnt it? Dont want to be a noob popping in asking hwo to cook Android for the HD2
Click to expand...
Click to collapse
Is it possible that the img files need to be created as ext4 rather than yaffs? I know gingerbread runs on the ext4 system (where froyo ran on yaffs2) but I'm not sure how this relates to building the rom.

Nah, don't think so...not accroding to: http://forum.xda-developers.com/showthread.php?t=897940
Ive tried a few more times but am still getting the kernel error...so I cant even test if my build works or not as it wont even boot...so very frustrating...

Lets break it down........
1st
Here's a brief intro I did a few days ago read it..
http://forum.xda-developers.com/showthread.php?t=897940&page=2
The above goes for any .img used with DAF, they are yaffs2 images.
2nd
The sensible option for a clean build would be an existing stock gingerbread rom on a sister device. AdamG just happens to make the cleanest Desire roms around. I've had my eyes on this build for a minute, check it out and see if this what your looking for. Oxygen v2.0-RC6
3rd
I've been able to unyaffs disect, reassemble and get some 'customized' roms running. They flash, boot, & work great.....but I lose root permissions. lol
I was acutally doing this with the 1.6 NAND rom of MDJ that came as a single.img
That particular file was just system.img & boot.img yaffs2'd together. After I disected it I was able to unyaffs the 2 images and edit/modify change kernels, etc. etc. The only problem I have run into is the root issue.
Conclusion:
----------------------------------------------------------------------------
I'd be glad to help out any way I can in porting a ROM worthy of our devce
Any serious inquries can be directed to my inbox for private discussion on gtalk .
I'm no dev and am in no way claiming to be. I do have some findings and that's why I'm offering my help. Cheers

[ROM][PORTING] Galaxy S3 ROM for the S2

Hi all,
Sadly, I have irrecoverably bricked my S2 and I am no longer as active in the S2 forums. This does not mean you guys should stop trying to port this ROM to the S2 - It is a great device that should still be considered as one of the high-end phones in the market. Even though I've moved on to the S3 I will gladly try to help this project that I started and I am following this thread post by post.
I think it would be a good idea if everyone that has done something for the porting post exactly what they did and what were the results.
Hi guys,
I know that I've been fairly quiet over the past week, and that is because this project is going nowhere. I know we have some general direction of what we have to do, but a lot of fine details are unclear to me and everybody else. These details are ones such as: how to decompile & recompile the apks, which images to resize & how, what folders should be renamed, what files are needed in the new Rom, and more.
I have asked for assistance from the people porting the Sense 4 One X Rom to the S2, and I am waiting for a reply.
Sit tight, and hope for the best!
Hi guys!
This thread is meant to organize the porting of the Galaxy S3 firmware to our Galaxy S2.
The first thing we have to do is make the /system folder of the Rom smaller than 500MB, because that is how our phone is partitioned. To achieve that the first thing we have to do is convert all the XHDPI images in the apks to HDPI images because it will make the apks smaller and anyways - our phone is a HDPI device. After we do this, we will see if we have to trim down on more space in our /system folder.
To test if the Rom will boot after we do the above steps, I deleted a bunch of non-essential apps such as voice talk to make the /system folder smaller than 500MB. I then replaced the /system/app & /system/framework with the modified S3 ones, but unfortunately the Rom did not boot fully and got stuck at boot animation. To figure out why it didn't boot, Pulser suggested that we use a kernel that has adb force enabled and then we can get a logcat and see what the problem is.
For people who want to help meanwhile:
The task that is needed to be done is convert all the XHDPI images in the apks to HDPI images.
How to do this:
1. Download the S3 Rom (below).
2. Download Resizer 1.0 (below).
3. Resize all XHDPI images in all the apks in /system/app & /system/framework.
Download Links:
I9100 Rom - http://www.mediafire.com/?4v6i6isqa3pa4lw
I9300 Rom - http://www.mediafire.com/?9xk39miljh3l9vw
Resizer 1.0 - http://www.mediafire.com/?d6h6lpwm8jxdjxr​

Resized Apps: (0/190)
/system/app (0/188)
/system/framework (0/2)

Would love to see this happen, not sure how viable it is though.

please post in gereral ore q&a thead
request move

it would be more then WOW to get it ported to the sgs2.
But is it posible to run quad-core kernel/modem/radio software on a dual-core carrier

I thing good intentions are not enough. There must be several developers interested in thic project

mad-monk said:
Have to agree repost it to Q/A.......but it would be more then wow to get it ported to the sgs2.
But is it posible to run quad-core kernel/modem/radio software on a dual-core carrier
Click to expand...
Click to collapse
And that is where porting comes in!

Patroy said:
I thing good intentions are not enough. There must be several developers interested in thic project
Click to expand...
Click to collapse
That is why this thread was opened, to get developers interested...

Please do that awesome devs !

this is very interesting.

A great idea, I'll be watching to see com evolves.

They have ported the ICS based ROM to the SGS. Why can the SGS3's ROM not be ported to ours as well? :/

Now that we have a few dozen users interested within a few hours of this thread existing, we have to try to raise the awareness of developers in the hope that some of them join the project.
Whoever has names of developers that might be interested, please try and contact them and see if they are interested in joining the project.

Well if any devs are going to do this...There is not much use in porting the UI and the SGSIII theme. Rather shouldn't the emphasis be on the handy features and new apps that Samsung have made?
Sent from my GT-I9100 using xda premium

very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user

Yandvoiris said:
very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user
Click to expand...
Click to collapse
Then I guess we'll need one hell of a developer!

Yandvoiris said:
very problematic idea
have you seen how much space take an I9300 rom ?
to do a proper port the developer will need to creat a new pit file (wich will re format the space on the phone to give larger drive for the system)
and a new bootloader wich he will have to make to work with the new pit
without cusing hard brick to the user
Click to expand...
Click to collapse
app folder and framework folder of sgs3 is 470 MB and our system partition is 500 MB so not enough space for other files such as libs,bins,media,etc
Maybe if its ported then devs can remove some bloatware and move some apps to data partition

ata1918 said:
Well if any devs are going to do this...There is not much use in porting the UI and the SGSIII theme. Rather shouldn't the emphasis be on the handy features and new apps that Samsung have made?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I tend to agree with this
Sent from my GT-I9100 using XDA

Won't the apps be portable anyway its all 4.0.4 - not sure why you would want the whole ROM for a different phone?

Have been thinking about this all morning... glad people are already on the case!! After using an S3 yesterday, I'd personally be keen for a straight/similar ported ROM where possible rather than pulling out all the best bits. I've had enough of AOSP ROMs for now....