Database Users

[Android] Tattoo and new rootfs

Okay, I finally cleaned up what I've been working on the past few weeks
New sqsh with tattoo senseui!
so this is senseui from the tattoo, so it runs at native resolution 240x320. I have not tested it at *any* other resolution.
I haven't done a lot of testing so I can't guarantee everything works... ie I think that bluetooth might be broken? who knows... other folks please post your experiences!
Please note: I *have* seen the whole thing crash due to WifiService dying on my vogue once... and I've also seen a hard lockup on the polaris once... not sure why or workaround, but it doesn't seem to be commonplace.
I use the tattoo.user.conf and I *don't* use rosie, and it runs nice and speedy... YMMV.
New rootfs that cleans up a *lot* of little things... you can now use the volume-down installer to *update* your nand partitions and back up your nand data! (you first have to have a the nand flash complete before this will work, and you need to use the rootfstonand with the updated rootfs)
Maybe I'll post some screenshots? who knows...
Everything is HERE
EDIT: Forgot the most important part... Credits!
This build is almost entirely from the Belgian HTC Click image posted somewhere out there. Lots of time was spent getting the RIL to talk to the phone application without crashes, but it seems somewhat stable now.
At my disposal I had donut and tattoo builds from enatefox, zenulator, plemen, and maybe a couple others.
Some bits needed to be swapped out to work, and that took the bulk of my time... oh well
I'll also give some creds to the folks over in kaiserland, but I'm not sure who (sorry).

Thanks muchly! Been beating my brains out trying to dyi a port of Tattoo and you've done all the hard work. Made my day, now I can go to sleep....

Trying this out tomorrow. I'll write about anything I see. Nice job.

Thanks Vilord
I'm a big fan of tattoo native resolution senseui.
testing.

lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes

vilord said:
that is likely due to my new partition/nand management code...
What is your partition setup?
I'll poke at it in a few minutes
Click to expand...
Click to collapse
I don't know what could be causing the bootup issue
I dropped in some debugs and catchalls that might help

The faster!
This is the fastest version ever.
i'm using haret and no paritions, works perfect!
i wish i could put it on nand, but i'm using a NIKE and the NBH is for vogue...
NICE JOB VILORD!

Hi,.
Thanks vilord, this is the best build with sense that i have tried.
I have the mount system error the first time i try to boot it, the second time it boot without problem.
Im wrting this from this build

arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
all: I'm still not 100% sure why the installer's choking, but I'll poke it when I get home (I still need to partition the SD on my POLA200, so I should be able to see exactly what you see when I do it)

Sigh, more user freindly
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?

no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.

vilord said:
arleybarros: what is the state of android on NIKE at this point? Do you still have no vibrate?
Click to expand...
Click to collapse
Since the vibration was disabled (2009-09-22) all the builds works almost like vogue, except for:
Camera: never worked, maybe because the drivers are diferent or because nike camera max resolutuion is 2MP (force close)
Bluetooth: never worked, maybe drivers
Vibration: disabled
everythig else works perfect.

gjbnh said:
I really don't mean to sound a negative note, your hard work , along with the other devs is sooo appreciated and admired. But for the many newbies that are out here, drooling other the new toys you guys are providing, I would really like to see complete bundles, which are updated as needed, with maybe a version number assigned to each updated build. Because of the modular nature of the OS, it is far to easy to to mismatch components resulting is a royal mess, and a real bad taste for potential users.
Or am I just full of it?
Click to expand...
Click to collapse
I think this is a good idea too..thanks.
Im having trouble with data connection. it was one for a moment then stopped. Any suggestions?
Never mind I got it working. It was turned off in the settings. great build!

I'll make this nandable and post soon.

got it booted - without ext partitions
lauyanyameric said:
it says:
No sys found on SD, booting Part/NAND
(e2fsck 1.41.4 (27-Jan-2009)
ext2fs_check_if_mount: No such file or directory while determining whether /dev/block/mmcblk0p3 is mounted.
/dev/block/mmcblk0p3: clean, 11/130560 files, 18794/522112 blocks
Using partitioned system
e2fsck 1.41.4 (27-Jan-2009)
/dev/block/mmcblk0p2 is mounted.
e2fsck: Cannot continue, aborting.
mount: Device or resource busy
Failed
Failed to mount /system
_
Click to expand...
Click to collapse
I am really looking forward to this, but get the same result as lauyanyameric on my Kaiser, afterwards I am dropped to shell .... Anything I can do to help debug?
Tried it without partition, and I get data error and it created a 34 mb data.img.
Tried with a blank data.img (no partitions) and I was able to boot!
Grateful for your work! Thanks.

try formating your sd card again...

So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick

First off thanks for all the hard work you and others have done bringing android to the vogue. I have donut running off of nand right now and love it but am wanting to try this build but have no idea how to reflash it on there. i have tried searching and searching but i havent found a good answer on how to do it.

nabicat said:
So far, so great.
Running via Haret and this is working superbly. Everything that should be working, is working.
So far have tested audio, data, GPS, camera (via Camera Pro), and apps such as Voice Search, Exchange Sync, Market and they all work and are quite responsive.
Noticed a few rosie reloads after using memory intensive apps, so I added a 32mb swap in the conf file. So far no more rosie reloads.
Also, the USB to PC app doesn't appear to like my work machine. Not sure if this is an issue with the desktop or the app.
Will be flashing to NAND after a bit more testing.
Thanks again Jesse!
Cheers
Nick
Click to expand...
Click to collapse
Im getting the Rosie reloads too... how do you add the 32mb swap or better yet can you just upload your conf file? Thanks

vilord said:
no you're completely right.
Once I get things ironed out with the installer, and after I've gotten some more feedback, I'll put it together with two zip downloads, one for NAND installation and one for haret/SD installation.
Click to expand...
Click to collapse
Thank you I think doing this will add a layer of usability to the releases, and gain a greater community of users as a result. Personally I would rather have releases further apart in time with this kind of thing rather than a rush to try the newest toy.

Eris Dual Boot ROM

I'm posting this in General as I don't have the knowledge to port this or develop a similar version for the Slide and I don't want to clutter up the Development forum.
Team ADX over in the Droid Eris forum came up with this gem; a dual boot Eclair Sense/2.2 AOSP ROM. http://forum.xda-developers.com/showthread.php?t=824072
I don't know if this can be done on our phones, but I thought it possible as you don't need to flash a custom recovery.

man this would awesome... the best of both worlds, run and "stock" ROM so we can still receive updates and still have CM.

i was actually thinking about dual boot just the other day! i dont feel like id be switching back and forth from 2 roms but itd be a great feature for those who do. unfortunately i dont think we have that much developers :/

I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started

KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App

migueltherocker said:
I'll take a look. No promises as I'm an übernoob but I would love to have this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.

heybobitsme said:
I don't think S-OFF is the issue. The partitioning instructions only refer to sdcard. This command:
Code:
mkpartfs primary fat32 0 3500 (can be adjusted to your needs. This partition will be used by the 2.1 rom and by recovery)
I think is only for the phone ROM storage and the for the recovery to find the boot scripts. According to the instructions, they're only partitioning the sdcard to run the AOSP ROM in it. They install the 2.1 Sense ROM to the phone, get it set up, run the boottosd script to boot into the 2.2 AOSP ROM on the sdcard, then set that up and run the boottophone script to go back to 2.1 Sense. They're running a ROM on the sdcard!
As I said before, I think something like this can work for our phones because it doesn't require flashing a recovery. The problem is we don't have the devs to do it.
Click to expand...
Click to collapse
Ok that makes sense. I thought it was pointing to the partitions on the phone telling it to format to a different size for some reason. Then what's preventing us from doing this? Just a lack of a proper script?

I have not poked around with how they are going about doing everything, but I was the one who got the ball rolling with my dual boot linux script. Conap took the basic setup and made some changes to just install them both on the phone and sdcard. Here is the basic of what it is doing....
The init.rc file found in boot.img has been modified for the froyo rom on the sdcard. The lines where it mounts [email protected] , [email protected], and [email protected] have been changed to the partitions on the sdcard (/dev/block/mcblk0px) The updater-script for froyo has been modified to flash the rom to the partitions on the sdcard. There are some gscripts which are ran from the phone that either modify or replace the boot.img for the rom you want to boot into.
The froyo ROM is running completely off the sdcard and the recovery is left untouched. The script that is required if you are using clockworks is because clockworks sbin and folder locations are setup a little different. I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. I am working on something that should run from all android phones and allow you the option of installing whatever ROM you want.
One Last Thing..
Anyone is capable of learning how to do some development work. It just takes some patience and "Google". I had no knowledge of linux or any other scripting languages, except windows batch scripts, until 3 months ago.
There is not much activity on my thread, but once I get a working version finished it will be posted there-----Dual Boot Android

When you get it done and own working, post it in development. I only posted the thread in general because I knew I wasn't going to be the one to develop it. I'm a welder by trade and java and linux are a little beyond me. Although I am trying as I'm using Ubuntu as my main OS and starting reading java tutorials.
Sent from my CM6 Slide

heybobitsme said:
You won't be able to do a simple port. I posted about it more of as a proof of concept. Take the same idea, but obviously using our espresso sense and CM6.
Click to expand...
Click to collapse
If there was ever a reason to get a dev started on a project, this would be it. I would reconsider upgrading from the Slide if we had something this awesome.

unCoRrUpTeD said:
I was running into some problems with froyo not recognizing the sdcard after making more than 4 partitions. Several had reported to me that their phones also did not recognize the sdcard, but the Eris phones somehow still did. [/URL]
Click to expand...
Click to collapse
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.

s off is tmobs response to....
KCRic said:
I was reading the instructions for it and it looks like we'll have to wait for S-OFF before we can try it.
Part of the scripting is telling the phone how to partition the phone, sizes of those partitions, and so on. The slide is, generally speaking, un-brickable and it's the measures used to give us that luxury that also prevent us from doing so much like R/W on the system while in a non-recovery boot and changes we do make while booted are just wiped on reboot *sigh* man I love that ramdisk image.
Once we get S-OFF let's get this project started
Click to expand...
Click to collapse
The "companies" wanted s-off due to the large number of brix getting returned for handest exchange and assurion claims, just to figure out somebody pooched sumthin up trying to be a HAXOR, if you haven't done anything like this before. Id suggest peeps get a g1 or some other root & rom-o-matic type for and play with it till you take on your brand new handset trying to install some bleenin edge hack...
You gotta learn to wank off before you can try it with somebody else in the room.
I remember my early days at xda, hacking my mda, xcaliber, and esato hacking SonyEricsson fones before they jumped the shark. People who had the ability to read and follow directions (emphasis on the read part) would study till they were sure they would still have a working fone at the end. Hung out and did great stuff with there handsets. And the noobs were wary enough to investigate before they just started mucking about.
So the handset manu. Had to do sumthin and now we have s-off.
the moral of my high and mighty rant an rave, if you don't know how to do sumthing or if you understand what to do but not the why, then keep reading, read more do less

KCRic said:
From what I understand, android can not *see* more than 4 partitions so they had to do something a bit different. Somewhere in the thread that's linked it states what they did to get it to work.
Click to expand...
Click to collapse
In the newest builds they have 2.1 system on the phones system partition and froyo system on the phones data partition. The data is moved to the SD. 2.1 and previous Rome had no problem with extra partitions on the sdcard.froyo changed the way it mounts the sdcard and could only see 4.
I am actually releasing a dual boot method very shortly that should work on any android phone with very little setup required on your part. I am in the process of finalizing it. Anyone interested in testing please let me know as I want to test on as many devices ad possible
Sent from my HERO200 using XDA App

unCoRrUpTeD Dual Boot

After some thinking about how I wanted to pursue this project and the recent release of an app that has made this possible, I decided to start working on an app of my own. While I have no experience in making an app, I have already begun working on it. Boot Manager is an awesome app for those that like flashing and running different ROMS frequently, however I have found some things that I do not like about it and features that could be added. My short term goal is to create an app with support for either 2 or 3 Roms and would be free. I'll then release a paid one that will support 5 or more roms and add some other features.
As I said, I have already begun working on it and although it won't utilize the method I wanted to use, I will implement some of it in the future. Right now I have parts of it setup and can already use certain features, but for anyone that has created an app, you know there is a lot of scripting that needs to be done.
Thanks to Conap for the motivation to get my a** back on track.

Partition your sdcard
PARTITION YOUR SDCARD
​I have made this really easy to partition your sdcard while preserving all data on the fat32 partition.
You have the option of specifying the size of the ext partitions in /sdcard/dualbootmap.txt
Code:
adb shell
echo 150 200 0 > /sdcard/dualbootmap.txt
The 1st number is cache partition for both rom2 in Mb. For right now I would not do anything less than 125 until I incorporate settings for dalvik-cache on data.
The 2nd number is ROM2 data partition in Mb. Pick whatever size you want.
The 3rd number which isn't used yet will be for a2sd on ROM1. For now this should be kept at 0.
If there is no dualbootmap.txt file the partitions will be automatically set to
cache=150
data=200
a2sd=0
Make sure you have enough free space on the card to accommodate the extra partitions plus an extra 200. If you only have a fat32 partition and use the default values above you would need 550mb of free space. After setting up the roms you will get the extra 200mb back. Its just used as temporary storage.
INSTRUCTIONS:
1. Download sdpart.zip
2. Reboot into recovery
Code:
adb shell reboot recovery
3. Unzip the contents of sdpart.zip and push the files inside sdpart folder to /tmp/
Code:
adb push c:\xxxxxx\sdpart /tmp/
4. run /tmp/sdpart.sh in adb shell
Code:
adb shell /tmp/sdpart.sh
If sdpart.sh doesn't run then you will have to chmod it before running it, but it should already have permission to run.
Code:
adb shell chmod 777 /tmp/sdpart.sh

HELP
Reserved until release day

Can't wait to try it out.
Is it going to support the aria?
12c00000-257fffff : System RAM
THANKS
Sent from my HTC Liberty using XDA App

FFXTDS said:
Can't wait to try it out.
Is it going to support the aria?
12c00000-257fffff : System RAM
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
Updated OP. Thats it for today. I'll post others in the morning

Can I restore a nandroid and then flash the dualboot.zip to make that Rom store to SD instead of wiping everything and flashing the roms?

jblazea50 said:
Can I restore a nandroid and then flash the dualboot.zip to make that Rom store to SD instead of wiping everything and flashing the roms?
Click to expand...
Click to collapse
You should be able to as long as there is a boot.img in the nandroid which I think there is

I really like this idea. Is there any way that you could modify a recovery to incorporate a bootloader? I believe clockwork is open source and should allow for this to be possible.

I don't know any c programming, but am looking at alternatives. Maybe an app or 1 script that does everything.
Sent from my HERO200 using XDA App

This is F'in epic dude. Thank you!

got this working on my evo,
1. what if i want to flash a new nightly or a update, do i go through the process again? and does it matter if it's on the SD or Phone?
2. how do you nandroid the rom on the SD?
basically should i keep CM6.1 on the Phone or the SD for easy updating
EDIT: i lied it works then when i tried to boot to SD it just sat at the white screen. going to play around with this some tonight

Wow man. This is freaking amazing. I'm definitely going to give this a try. Run CM as my daily rom, but this will help when I am traveling to 4G areas, and I can just flip over to a Sense rom.
Awesome, awesome work.

so if i wanted to put cyanogenmod nightlys on and then update them to a newer nightly version how would i do that without redoing everything?
edit: been messing with this and had my question sitting without hitting submit for like 15 min and apperently in that time someone else asked same question

I can't figure out how to get my base address... Can someone please explain more... I'd love to use this on my incredible
Sent from my Incredible using XDA App

Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.

sd card
So how is the speed when running on a class two SD card or a Class 4
Does the rom bog down?

Tried it and when I tried to boot into the rom on sd it got stuck on splash screen. Running miui on phone and had ava 10 on sd.
Sent from my PC36100 using XDA App

PikkonX said:
Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.
Click to expand...
Click to collapse
What recovery and phone do you have. Run this from command or terminal and post inside code tags
Code:
adb shell cat /sdcard/dualboot/recovery.log
or attach /sdcard/dualboot/recovery.log so I can look at it. It sounds like I may have the wrong base address. I'm going to sleep now. but will check and update this in the morning

kevinniven said:
So how is the speed when running on a class two SD card or a Class 4
Does the rom bog down?
Click to expand...
Click to collapse
im no expert to android, linux, sd cards (lol)... but i think it doesnt matter, once the ROM is loaded it runs off the phone's memory, so the speed shouldnt be affected.
somebody correct me if im wrong

PikkonX said:
Booting into the rom on the SD doesn't seem to be working. The phone just stays at the initial boot screen. This happens whether I have CM6 or a Sense rom on the SD.
Click to expand...
Click to collapse
yeah i'm getting the same thing wont get past initial bootscreen
Phone = HTC EVO rev 0003
recovery = psfMod 0.7.2 (aka clockwork)
sdcard = 8gb (w/2.2gb free)
and i checked my adress base before hand so i know i got correct one
i will try again tomorrow as i gotta get some sleep now

[Experimental][ROM][12/8/10] SPGinger HD2 [MDJ kernel S7.5HD][WIP]

PLEASE READ CLEARLY FIRST BEFORE DOWNLOADING ANYTHING
Disclaimer
Im gonna pull this straight from infinitybiff when I say, "I'm not a dev, nor do I claim to be, yes this is easy, sharing is caring. If your phone explodes, not it."
This rom is extremely alpha, it is more of a proof of concept than anything.
Just in case you didnt understand, this rom is highly experimental.
Flash at your own risk. If you have any ideas to make this rom better, please, by all means, contact me.
This rom was made using the sdk dump that I pulled out yesterday, however Darkstone1337 made the rom bootable and passed on the knowledge,
then M-deejay took that knowledge and made the core of this rom. I am just putting some things in it to make it a little better.
Installation
Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe, and you're off!
Downloads
Im gonna say version 0.1 http://www.mediafire.com/?7o7mgkqpb3falg6
Credits
Darkstone1337 - For making Gingerbread on our phones possible.
M-deejay - For then using that knowledge and making the core of this rom.
atoore - Used his 262mb data.img
dakluck - Found the fix for BSOD (temporary)
m-deejay - Used his kernel. They rock.
IcedCube - Currently making me a data.img that seems to fix some problems.
Testers
dakluck - Awesome dude for finding the temp BSOD fix
MotoMudder77 - Provides me with all the logcats I could ever need
Legioner79 - Still waiting for him to get on Gtalk
If I use anything else, credit will be given.
Known bugs
White screen after animation/menu popup, just swipe or touch anywhere in the white area and it should go away. Its just slow screen redraw.
Home button does not work.
Slow (of course)
Quick edit
Wow, 45 downloads in less than 10 minutes? Thanks all!

Changelog
Changelog
V0.1
Added 262mb data.img courtesy of atoore.
Temp BSOD fix
After pressing power button once, press and hold power button till vibrate, then press back button. May take a few attempts but persistance is key.
(Credit to dakluck)

second thanks...

cool stuff, if you need any help, add me on gtalk... or join jdms-team irc channel, yall can use it if you want...

Hi
First to download and first to test hi hi !!!!
Feeds back soon

spbeeking said:
PLEASE READ CLEARLY FIRST BEFORE DOWNLOADING ANYTHING
Disclaimer
Im gonna pull this straight from infinitybiff when I say, "I'm not a dev, nor do I claim to be, yes this is easy, sharing is caring. If your phone explodes, not it."
This rom is extremely alpha, it is more of a proof of concept than anything.
Just in case you didnt understand, this rom is highly experimental.
Flash at your own risk. If you have any ideas to make this rom better, please, by all means, contact me.
This rom was made using the sdk dump that I pulled out yesterday, however Darkstone1337 made the rom bootable and passed on the knowledge,
then M-deejay took that knowledge and made the core of this rom. I am just putting some things in it to make it a little better.
Installation
Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe, and you're off!
Downloads
Im gonna say version 0.1 http://www.mediafire.com/?7o7mgkqpb3falg6
Credits
Darkstone1337 - For making Gingerbread on our phones possible.
M-deejay - For then using that knowledge and making the core of this rom.
atoore - Used his 262mb data.img
dakluck - Found the fix for BSOD (temporary)
m-deejay - Used his kernel. They rock.
IcedCube - Currently making me a data.img that seems to fix some problems.
Testers
dakluck - Awesome dude for finding the temp BSOD fix
MotoMudder77 - Provides me with all the logcats I could ever need
Legioner79 - Still waiting for him to get on Gtalk
If I use anything else, credit will be given.
Click to expand...
Click to collapse
hi "htc" logo screen ?????

Great work team ! Im sure this will be stable very quickly with such great men on the job.
Thanks heaps for all the time Developers. HD2 should win HTC top unit 2 years running...

Kezzainc said:
Great work team ! Im sure this will be stable very quickly with such great men on the job.
Thanks heaps for all the time Developers. HD2 should win HTC top unit 2 years running...
Click to expand...
Click to collapse
Yes it should.

Downloading now

1. incredible fast boot
2. extremely lag

tritran18518 said:
1. incredible fast boot
2. extremely lag
Click to expand...
Click to collapse
Thats Gingerbread for ya

am i just stiupid or is my english too bad for understanding this?^^
when i read ROM, my brain says "u have to flash it"
but installation says:
"Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe, and you're off!"
so what exactly is the improvement in this version?^^
edit: its 2.3...now its makes sense^^

5had said:
am i just stiupid or is my english too bad for understanding this?^^
when i read ROM, my brain says "u have to flash it"
but installation says:
"Extract the "Android" folder in the ZIP file below to your MicroSD Card, pop it into your HD2, open File Explorer from WinMo, find the Android folder, tap CLRCAD.exe and then Haret.exe, and you're off!"
so what exactly is the improvement in this version?^^
Click to expand...
Click to collapse
Slight increase in speed because of MDJs S7.5 kernel, and atoores data.img. I still dont know why, but that data.img helps with warding off boot issues.

This boots very quickly!
Has a long way to go but its awesome to see gingerbread booting on our hd2s. If you need any testing done, I'd be more then happy to do what I can.
Thanks to those who have put the work into this so far!
Sent from my HTC HD2 using Tapatalk

Just copied, Boot was very fast. The preparing SD Card, and Boom Black Screen for now 5 Mins. Just waiting

Ok finally start android, boot very fast, and i see avery 5 minutes i lost signal cell

Say Hello World!
Send from my HD2 gingerbread.!
What I like;
-No chopper on scrolling, but maybe is because SDK don't have hardware acceleration, let's see in future.
- fast data

Great first try of getting Gingerbread on our beloved HD2. Great to see that it boots up. Hope there will be new builds with extended functionality in the future.
Big thanks to the devs!
My experience so far.
- Quick boot
- Installs .apk files from the AdroidApps folder
- A lot of lag. In fact it hangs most of the time
- No or very bad signal
- No or very bad data connection
- menu graphics are messed up

Video
Wow,
thanks so much!
I was able to record a short video of my HD2 running SPGinger:
http://www.youtube.com/watch?v=Z-bBS8Ihyj4
Of course there are some bugs but data connection is fine for me (Vodafone Germany).
Also I can install the most apps with the FileExplorer.
I think in about one week we'll all run around with the perfect GingerHD2beast!
So long.
Wowa Trader

mekz77 said:
Wow,
thanks so much!
I was able to record a short video of my HD2 running SPGinger:
http://www.youtube.com/watch?v=Z-bBS8Ihyj4
Of course there are some bugs but data connection is fine for me (Vodafone Germany).
Also I can install the most apps with the FileExplorer.
I think in about one week we'll all run around with the perfect GingerHD2beast!
So long.
Wowa Trader
Click to expand...
Click to collapse
Thx for the vid
Sent from my HTC HD2 using XDA App

Anyone know if we are able to use CWM?

Has CWM been ported to this device yet? Or something like the Droid X recovery?
If so, I'd like to start making a pseudo-ROM of sorts.
If not, I'll start working on making some batch files

PixoNova said:
Has CWM been ported to this device yet? Or something like the Droid X recovery?
If so, I'd like to start making a pseudo-ROM of sorts.
If not, I'll start working on making some batch files
Click to expand...
Click to collapse
To make a long story short I find if you use Fedya/bootstrapped_recovery, HERE: https://github.com/fedya/bootstrapped_recovery. And you substitute Dexter_nlb's "mot_boot_mode.p2.sh" file from his recovery, HERE: http://forum.xda-developers.com/showthread.php?t=942160. You have a recovery you can do things with. Just had problems with mounting usb for file transfers, and one or two unmount options. CAUTION... if like me you have a second partition on your sdcard to work with link2sd, it will wipe your second partition. And you'll find that Nandroid works and will backup your second partition but will NOT restore it. But it's progress... I used ubuntu to extract Dexter_nlb's apk. Let me upload the recovery I threw together and I'll post a link. Naturally credit goes to the authors, I did nothing but swap files and pull what's left of my hair out trying to fix what I ultimately couldn't . The link is on the way...

Here's the Link: http://www.mediafire.com/?618nl545za0b6ax
Just install like Fedya specified on Github: https://github.com/fedya/bootstrapped_recovery

Nice! Thanks so much!
Sent from my MB508 using XDA Premium App

I think we will be able to soon!

Working on it
I am in talks with the people at CyanogenMod forums, and they are giving me pointers and lessons on how to build a custom ROM from their source tree. Hopefully I will begin this weekend (and won't brick my wifes phone more than 10 times). I will let you guys know what I come up with when I have something.

Yay that's exciting....i'm in talks with a guy at those forums too and he said he's almost done building a custom recovery