If I use the portadroid and insert the updated oxygen rom, can I use the old data.img? Thanks, looks like alot of potential with this kit.
So, I tried this with Darkstone's build, which I love and used for a long time until the build kept giving me many FC's.
2 things: 1 - I couldn't find a META INF file in Darkstone's build. 2 - when I went to edit the startup txt, it already said ported_rom=desire
I can't get this build to boot up. The first time it did a quick reboot to WM. Now it just hangs on the screen with the small writing. Several battery pulls and the same result.
I have followed instructions to a T, as outlined above.
Also reformatted SD card and re-installed stock ROM prior to loading Android.
To quote darkstone himself in the first post of the above linked thread:
- 'The base rom is from AdamG's OxygeN Desire rom which has been modified by myself.'
I may be way off - I am not a hip techie like most of you - I am a 52 year old grandma who likes android on her HD2 and has been using android SD builds for quite awhile. I know how to follow instructions pretty well, which has taken me a long way here in the android world of HD2
I just can't figure out what I'm missing to get DS's SuperRAM build loaded with Portadroid.
ok, just to give one insight:
amazing, i still cant believe we can boot desire and hd2 nand roms directly..
very easy and fast installation, tried the recomended desire rom that is very light and it seems to have a good battery drain;
the kernel used is tytung_r10 that we already know, but this time bluetooth is working
wifi is working with adhoc connection, phone is working, camera and camcorder working, no FC´s, no slowdowns, so far so good, will make more tests tomorrow, have to sleep..
I had Darkstone's SuperRAM Froyo before. There isn't a meta-inf and system folders. There is only a system.ext2.
This Portadroid build is for porting Desire ROM and nand ROM. Both have meta-inf and system folders in their zip files.
So it's possible this will not work. Are you using a old data.img?
Edit: Just a thought
Since the contents in meta-inf and system folders are copied into the newly created system.ext2, maybe you can try placing the system.ext2 (that you have from darkstone's build) into the main folder itself (ie. Android) and not in the "root" folder. And also to delete the reboot file as well. The reboot file will cause the system to rebuild once the system.ext2 is created (it is not there originally) and gets deleted after that. If you keep trying to copy the whole thing into the directory everytime it fails, then, well, it gets rebooted always.
There IS a system folder inside the Root folder of Darkstones unzipped zipfile. And there is a system.ext2. I may download the zip again to see if the meta-inf file is missing for some reason. There is not this file in my darkstone zipfile.
I tried Portadroid first with a blank 1 gb data img that I use in all my SD builds, but after failed boots, I removed it and tried to reboot. This time I got hung on the small text screen.
Hmmm. Maybe I needed to reformat after removing the data img? do I need to include a smaller blank data img? Don't most builds build their own data img if it's not included in the android file?
Well, headed to get some sleep. I'll try again in the morning.
|Thread Tools||Search this Thread|