file structures between builds are different - HD2 Android Q&A, Help & Troubleshooting and Genera

Hi.
I was checking each build today and noticed that the file structures between builds are different. Example, Matt's or Darkstone's has a rootfs.img and system.ext2 while shubcraft has htcleo_update.tar.gz and root folder, but no system.ext2 nor rootfs.img.
How come the structures are different? Hopefully one or some of the devs can chime in on this.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks

i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)

w0LfNiNja said:
i'm not a dev so i can't be 100% sure on this. i can tell you that when i load shubcraft's build up for the first time... the first screen says it is a htc hd2 on the setup screen. the other 2 say n1 or desire i think.
so my guess would be that shubcraft's build is more modified and the others is more image based from the other phones.
1 reason i loved shubcraft's build was that it kept my phone named correctly. i don't like going into my phone's about screen and seeing it named n1 or desire... cause it's not... heh, i have a HD2 and i'm proud of it dangit! =)
Click to expand...
Click to collapse
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1

It's just because Shu8i do not supply system and userdata images with it's build, instead he relay on creating that files on first start of Android, that is the main reason Shu8i's build take so much more time to start up at first.
It's just a trade-off, less file size you download, more time to wait for first boot.

bangsters said:
Hi.
Oh and how come the initrd.gz cannot be extracted? I tried extracting one and when I opened it I saw a bunch of garbled syntax....
Thanks
Click to expand...
Click to collapse
It can just use
gunzip initrd.gz
cpio -d -i < initrd
Its a gzipped cpio file

mr_billionaire said:
Actually, ita very easy to change the phones name on Android, im on Darkstones Froyo v1 and i changed it from saying" HTC Desire" to "HTC Leo" going to switch it back to HD2 tho. But the filesystems im not to sure about.
Sent from my HTC HD2 running DarkStone HD2Froyo v1
Click to expand...
Click to collapse
guess i'm not that smart just yet. heh.

There are currently (from the files I've checked) two ways of packaging Android builds; the "Zego" way and the "XDAndroid" way.
Inside both builds, you'll find a haret (kernel loader), clrcad (enables audio in android), initrd.gz (initial root filesystem), zImage (kernel), and startup (the script haret uses to set up linux).
The XDAndroid-based builds have, additionally, a rootfs which is a big package intended to allow the same XDAndroid build to run on a wide variety of devices.
IMHO, the Zego initrd is much better because: 1. it allows for "otapackage" updates, 2. It's for HD2 only, 3. It's much cleaner and can run AOSP builds straight from a make (as long as you specify that the build images use ext2).
The disadvantage, though, is that it uses a regular init.rc instead of a hero one (only difference is that hero core jars aren't loaded into the classpath), so it takes a slight modification to get sense builds running.
The XDAndroid initrd, instead, just loads the rootfs and then from the rootfs several scripts run to determine the kind of device that's being used and then when the device is detected, the files used for that device (included in the rootfs) are "pushed" to the system image to allow all hardware to work correctly.

Related

[Q] How do I update Android 1.5 to FroYo 2.2?

Hi, I'm new here and I have successfully installed Android 1.5 to my HTC Vogue with HaRET but I would like to have either FroYo or Eclair. How would I go about doing this?
I do not want to flash my rom quite yet. I want to have it dual booting WM6.1 and Android until I'm brave enough to flash it.
Playgr0und said:
Hi, I'm new here and I have successfully installed Android 1.5 to my HTC Vogue with HaRET but I would like to have either FroYo or Eclair. How would I go about doing this?
I do not want to flash my rom quite yet. I want to have it dual booting WM6.1 and Android until I'm brave enough to flash it.
Click to expand...
Click to collapse
First, you need to delete all the android system that already installed, or you could make a backup of your andboot folder - just in case, maybe you want to go back to 1.5 without starting all over again.
Download any Eclair or Froyo build by the dev here in the forum, and place it together with your base file - some build may include these file in their package, then run Haret again.
The process is the same as 1.5 except with the newer files. You will not be able to "update" to a 2.x OS, you have to start from a clean slate, so be aware of that. Make note of all your programs so you know what to install again.
So would I just replace the ZImage file to a newer build or is there other files I require aside from the basefiles?
Eg. If I want Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS12] [7/26/10] version of FroYo do I just download the ZImage file or also the NBH file. From my knowledge, I think the NBH is for installing on NAND and ZImage for SD cards.
I didn't understand my own wording so here is what I mean. Do I need the ZImage or NBH or both?
you'll need a newer ZImage and his androidinstall.tar (or .tgz). You are correct in that the NBH is only for NAND while the ZImage is for SD Card installs.
Thanks a ton! Just downloading the files and I'm ready to test it out
I've tried SDCard load and NAND load for Droid
NAND is much faster and much more stable
Some people have reported issues when running off SDCard that disappear when flashed to NAND
Once you start using Froyo 2.2 and get it sync'ed with google - you won't want to go back to WinMo
Running Froyo RLS 12 @ 320x480 / 160DPI / 500mhz OC
Playgr0und said:
Thanks a ton! Just downloading the files and I'm ready to test it out
Click to expand...
Click to collapse
did you ever get this to work, because I cannot.
I did get it to work and it runs pretty good off the SD card and I am just about to flash it to the NAND after reading the comment above yours from Does_It_Matter.
I used DZO's basefiles for installation.
Does_It_Matter said:
I've tried SDCard load and NAND load for Droid
NAND is much faster and much more stable
Some people have reported issues when running off SDCard that disappear when flashed to NAND
Once you start using Froyo 2.2 and get it sync'ed with google - you won't want to go back to WinMo
Running Froyo RLS 12 @ 320x480 / 160DPI / 500mhz OC
Click to expand...
Click to collapse
I am wanting to flash FroYo to the NAND now but where can I find detailed instructions on how to do so?
Playgr0und said:
I am wanting to flash FroYo to the NAND now but where can I find detailed instructions on how to do so?
Click to expand...
Click to collapse
Actually, there's a FAQ thread for android-vogue,
here.. http://forum.xda-developers.com/showthread.php?t=628353
Anyway, i think incubus super eclair is the perfect one if you wanna try..
Flash Android 2.2
Hello i need help! i Want to flash my HTC touch with Froyo 2.2 or Eclair 2.1.... right now i have daulbooting Android 1.5 and WM 6.1 useing harit....
Links please
link please for nand file n ZImage n process to installl both
Go look in the Vogue Android dev forum, everything is in there.
ok...actually I did go to htc cdma android forum. tried many different android files. can anyone please help me understand how to choose the right file in which the cdma 1x data voice and data would work.
so far all the packages I've tried, I've had 2 problems:
1. after the first normal outgoing/incoming call, the 2nd call will not make the phone ring though the caller can hear the ringback tone.
2. all packages I tried had gsm apn settings instead of a place where you configure the cdma 1x data account.
can someone explain what Im doing wrong? thanks so much.

[Q] Multiple Android Installations At Once.

Hey guys, I'm pretty new to the Android scene, but have been happily using FroyoStone for quite some time now. That being said, I have been looking around the Android Forum and have seen a lot of very pretty and exciting builds.
Being a man who cannot make up his mind, and too lazy to try them all one at a time, I was wondering if it was at all possible to install more than one Android build at any given time on my SD card. It's 16GB in size, so that wouldn't be an issue, I am just wondering what steps I would have to take to insure that none of the builds would conflict with each other. Would it be as simple as to put them all into their own seperate folders? ( I was under the impression that you HAD to run it from a folder named Android, would it require a Reg hack to change this? )
If anyone has any ideas or suggestions on this matter, I would like to hear from them.
I will update my post with any successes I achieve if anyone else is interested in hording builds
Edit
Wow I joined in October 2007 and this is my first post!
I currently have 3 builds on my phone. There are a couple of android loaders in that tell you how to load multiple builds. Check the development forum.
Will do, thanks for the speedy and to the point reply.
help setting up mulitiple builds
I've been having a problem with loading multiple builds. I've tried the multi build loader and was unsuccessful. I named each folder specifically (sdcard/android; sdcard/android evo; etc.) just to differentiate. I even changed the startup txt to reflect the folder accordingly. But the loader would always load the one that's in the "android" folder. Even when I go into the specific folder of a separate build and run clrcad and haret, it will still load the other build.
Using Shubcraft stock 1.5, Mdeejay evo sense 1.6, and darkstone. Any help appreciated. Thank you for your patience and time with me.
Each builds startup.txt should reflect its folder name.
This is example line from startup.txt
set cmdline "rel_path=Android_evo nand_boot=0"
(Change the red word to reflect yours)
You can use Exceller Multiple Build Loader for Android
http://forum.xda-developers.com/showthread.php?t=737001
You can tap to change which build to load.
With this setup you can have unlimited number of android builds in your sd card at the same time and they won't conflict with each other. (Well, of course sd card capacity is the limit )

There are phones who hates Android? (they cant boot it)

Hello,
I think there are phones (like mine) that doesn't work right with android os. I tried a lot of builds and most of them crashes while booting.
With WMO the phone WORKS PERFECT!!
I tried
-task29,
-rewrite radio (2.12.50.02_2)
-Change a lot of SDCards of different marks. Formatting with panasonic tool and XP format at diferents cluster size (16k and 32k)
-rewrite WMO ROM (without 2.14 drivers) a lot of times.
I think there is something in the HW that hangs on booting process. Maybe setting the vdd of voltage regulator becouse some builds crash inmediatly after of this message.
I only have 3 functionaly builds (only with any seconds screen freezes):
mattc froyo sense 1.7
mdeejay froyo sense 2.0
mdeejay froyo sense 2.1
The rest are crashing!!!
Im going to put android boot logs with the hope that some good developer can determine this bug.
HANGS WHILE WHITE HTC WHITE SCREEN. Sometimes boot itselfs
-Shubcraft 1.5
http://pastebin.com/HH1ayhvF
-Hyperdroid 1.2
http://pastebin.com/RR1RXStG
-Froyostonev2
(no paste bin yet available)
HANGS WHILE ANDROID TEXT LOGGING
-Bangsters1.3b: Last line: Slab Corruption
http://pastebin.com/jtd52ZGb
-mdeejay sense 1.3b: Last lines: acpuclk_set_vdd_level got regulator. BUG: workqueue. leaked lock or atomic
(no pastebin yet available)
Thanks for any help!!
Reading your post it seems you've tried almost everything, so just keep trying different radios and roms. And hope!! For everyone else who's confused about what to do when android wont boot:
1) Install Chuckys Droid Rom with the recommended radio, i believe 2.11/2.10 is the most stable.
2) Format your SD Card in Ubuntu as MBR then create a single FAT Partition. This is because once the partitioning is messed up xp cant fix it, this was the only way i found to get mine to boot properly.
3) Choose your android build carefully, my best luck has been with the CM6 based versions. As far as I know Shubcraft 1.5 is the most stable, but hyperdroid is very close and faster. If you use hyperdroid make sure you edit the startup.txt as the path to the android folder is incorrect and will fail to boot.
4) Enjoy Android!!

[Q] Froyostone v2 Installation

I haven't seen a thread for this question, I don't know, it could be possibly because its a bad question. But basically, I'm new to putting Android on the HD2 so I don't completely understand 100% of what I am reading. I've installed Android about 3 times, but always deleted it and went back to WinMo cause of the calling issue.
All I would like to know is, do I have to download anything specific or run anything before or after I run the CLCRD and HaRet in the Android folder from the Froyostone v2 .rar?
In the Froyostone v2 thread I noticed this, and I am wondering if I need to download anything from the following threads in order to run this version perfectly.
Code:
Build base: http://forum.xda-developers.com/showthread.php?t=742371
--------------------------------------------------
darkstone 2.6.32.9 #3 Kernel:
- Based on GIT (latest revision: 30/08/2010)
- Overclock enabled and undervolted (by huanyu - http://forum.xda-developers.com/showthread.php?t=746997)
- Interactive governor added
- KGSL shadow writes modification
Kernel Diff patch: included in build, also available here: http://www.multiupload.com/S8XHK89HRG
Rootfs based on dan1j3l's Froyo V1 build
I have a regular TMO USA HD2 with only HSPL3 in it. Radio 2.10.50.26
Thank you
idk but i have tried five different builds and mine runs a few lines then gets to "booting android kernel" then stops as the screen slowly fades to black. I want android on this damn thing. WTH am i doing wrong??
First, I am no expert on Android. However, I was able to get the Froyostone V2 working, and have been using it awhile.
You do need to format your SD card to FAT 32. You need to make sure the Android folder is on the root of your SD card (for Froyostone anyway-I think it is different for other builds). According to Darkstone, you should not have any other "Android" folders on your card.
Once all that is done, just open the folder and run CLRCAD and HARET.
As far as the robo voice, I don't have it running the Energy ROM.
EDIT: Forgot to answer your original question: I did not download anything other than the original build. I believe that is just an FYI from Darkstone you are referring to, and he says "included in build".

[Q] Only hyperdroid 1.7 works. Why?

Hey,
Til now i have tried 12 Android 2.2 Builds. But only Hyperdroid 1.7 worked. But i like shubcract and all the other builds more. Everytime I used the correct Installation ways but 11 builds ended at a green HTC Logo. Thats sad
Can you help me? That would be great.
Oh, and i also tried 6 different custom roms. With hyperdroid I use the new Energy Rom. Thanks
Reltih2200 said:
Hey,
Til now i have tried 12 Android 2.2 Builds. But only Hyperdroid 1.7 worked. But i like shubcract and all the other builds more. Everytime I used the correct Installation ways but 11 builds ended at a green HTC Logo. Thats sad
Can you help me? That would be great.
Oh, and i also tried 6 different custom roms. With hyperdroid I use the new Energy Rom. Thanks
Click to expand...
Click to collapse
You might want to reformat your micro SD card to FAT32 and do a complete install from scratch. My combo has served me well with no issues.
That's what I have done, too.
Aww, it looks like there is no way out :/
Your card may be faulty.
Even when ONE build works every time? Is that possible.
I used an 2GB one and an 1GB one (stupid idea, i know ).
Now I am waiting for my new 8GB one, I'll try it with that, but I can't believe that this could be the problem.
But maybe you are right, thanks for your answer
Reltih2200 said:
Hey,
Til now i have tried 12 Android 2.2 Builds. But only Hyperdroid 1.7 worked. But i like shubcract and all the other builds more. Everytime I used the correct Installation ways but 11 builds ended at a green HTC Logo. Thats sad
Can you help me? That would be great.
Oh, and i also tried 6 different custom roms. With hyperdroid I use the new Energy Rom. Thanks
Click to expand...
Click to collapse
Have you checked startup.txt?
What do I have to check there?
Some builds do take time to load.
Do you have a "loader" to automatically load droid or do you do it through selection of "clrd" and "haret"?
Are you installing the complete build folder?
I tried it with ,,LaunchAndroid'' on the Energy Rom (thats what works perfectly with HyperDroid) and on the other tested Roms, I used the casual method. Even this method worked with HyperDroid really well!
Everytime, I saw the green HTC Logo, I waited over one hour and nothing happens.
Then I gave up.
On HyperDroid, I see the Linux-Penguin and it goes through a black field with white commands on it and then it starts.
When I start all the other builds, I see the black field with the white commands for one second, then the green Logo appears!
To your last question:
I throw the folder on the root of my sdcard and that was it.
That's how it works as hyperdroid 1.7
Or is there another thing for the other builds, which I have to do?
Reltih2200 said:
What do I have to check there?
Click to expand...
Click to collapse
You have to check that rel_path directs to the folder where Android is stored. Some builds are stored in folders named after the builds, whilst others are stored in the default 'Android' folder. If rel_path isn't linked correctly, you will not boot.
This could explain why only Hyperdroid works.
And also, as mentioned by others, wait 20-30 minutes on first boot, it may take a while to create your data.img
This seems to be the reason for it. I didn't tested it yet, but I took a look into the builds folder.
On HyperDroid it looks like this:
set cmdline "rel_path=HyperDroidV1.7"
And on Moto234 EVO v0.3 it looks like this:
set cmdline "rel_path=Android nand_boot=0"
Do I have to change something there?
I see that for HyperDroid, there is no Android Folder, only the folder ,,HyperDroidV1.7''. Thats what the cmdline says, too.
Do I have to change the Moto234 startup.txt-cmdline into
set cmdline "rel_path=Moto234_EVO_Black&Blue_V0.3"
In fact, THERE IS an Android-Folder. For HyperDroid, i put the files directly on the root, not in an android folder. When I take the files out of the Android Folder (for example the Moto234 build) and put it directly to the root of the sd card and I edit the startup.txt like, is it possible, that everything works fine?
I will try it and when it works, I am so happy
Reltih2200 said:
This seems to be the reason for it. I didn't tested it yet, but I took a look into the builds folder.
On HyperDroid it looks like this:
set cmdline "rel_path=HyperDroidV1.7"
And on Moto234 EVO v0.3 it looks like this:
set cmdline "rel_path=Android nand_boot=0"
Do I have to change something there?
I see that for HyperDroid, there is no Android Folder, only the folder ,,HyperDroidV1.7''. Thats what the cmdline says, too.
Do I have to change the Moto234 startup.txt-cmdline into
set cmdline "rel_path=Moto234_EVO_Black&Blue_V0.3"
In fact, THERE IS an Android-Folder. For HyperDroid, i put the files directly on the root, not in an android folder. When I take the files out of the Android Folder (for example the Moto234 build) and put it directly to the root of the sd card and I edit the startup.txt like, is it possible, that everything works fine?
I will try it and when it works, I am so happy
Click to expand...
Click to collapse
First of all, make sure Android is installed in 1 folder on root, and not in a subfolder of that folder. This means that the files should all be put in, for example, H:\Android\ or /sdcard/Android/, and not for example H:\Moto234blablabla\Android\, that's one folder too much (well actually I'm not sure this is - it probably isn't - a requirement, but do it anyways).
Then just change rel_path to the exact spot your startup.txt, or haret and clrcad for that matter, are located. For example: rel_path=Android , or rel_path="Moto234blabla".
Simples, see?
Edit: in case I'm not being very clear: of course don't change the folder structure inside of the Android folder. Files in for example /root/ or /data/ should remain where they are, obviously.
Yeah, but when it is, how you explain it to me, HyperDroid shouldn't work.
As I said, it is this:
set cmdline "rel_path=HyperDroidV1.7"
But the files of Hyperdroid I directly on the sd card, there is no folder or subfolder.
That means, the files are on H: and nothing more.
So, why does it work? I will test it at weekend, because when I have to start all over again with HyperDroid, after nothing worked, it takes to much time.
Maybe it works
Reltih2200 said:
Yeah, but when it is, how you explain it to me, HyperDroid shouldn't work.
As I said, it is this:
set cmdline "rel_path=HyperDroidV1.7"
But the files of Hyperdroid I directly on the sd card, there is no folder or subfolder.
That means, the files are on H: and nothing more.
So, why does it work? I will test it at weekend, because when I have to start all over again with HyperDroid, after nothing worked, it takes to much time.
Maybe it works
Click to expand...
Click to collapse
Do a usb link and check the "Hyper" folder to see if there is another "Hyper" sub folder, this may be the problem. Sometimes one creates a folder and then places the build in that folder which it automatically creates its own.
If there is an "Android" folder, check that as well and make sure there isn't a sub "Hyper" folder; when you open either folders it should open a list consisting of "root" folder, zimg, etc.
So, I did everything mentioned here.
And...nothing works. ONLY HyperDroid 1.7
I mean, that couldn't be. I did everything, i changed the startup.txt, again I used thousand different ROM's. It sucks :/
I am glad to see, that you tried to help me, but it seems to be useless.
I have no idea what to do. Maybe it's better to sell the HD2 and buy a Dell Streak or a Desire HD. Then I have no problems like this.
When you have a nother possible reason for this phenomenon, tell it to me. Maybe this one works
Format your SD card and try again (do a full format, not the default quick one), maybe that'll solve it.
Does not help, sorry
EDIT: For anyone, who wants to know...i finally solved the problem.
I mean, I am so happy, I could cry
And everything because of the user ,,shekerdothis''. He is just a god. He saved my life
So, he said in another post:
I had the same issue for about a day, and after research of stuck on green HTC Logo with no help, and thousands of post later I came acroos an article regarding EncFiltLog.menc. Do not format your SD card with MAC or windows PC, but rather the secret is to format your SD card with your winmo phone by going to "settings" | "format SD card". It will create an exec file "EncFiltLog.menc" This file is, I guess, a partition index??? The file "EncFiltLog.menc" is hidden in windows mobile 6.x but is visible when you mount your SD card to your PC. Do not delete this file!!!!
After that just drop your android folder and it will boot up in less than 3 mins. After that, u may add all your other files. I use a 16GB card with Android and all my music and stuff with no problems. Hope this helps you.
Click to expand...
Click to collapse
And yeah, it worked. I went to settings in Winmo, then to System and then format SD Card. It took 1 Second (even faster then the quick Format on my PC) and everything works brilliant!
Thanks to you all, what a great Forum
Reltih2200 said:
Does not help, sorry
EDIT: For anyone, who wants to know...i finally solved the problem.
I mean, I am so happy, I could cry
And everything because of the user ,,shekerdothis''. He is just a god. He saved my life
So, he said in another post:
And yeah, it worked. I went to settings in Winmo, then to System and then format SD Card. It took 1 Second (even faster then the quick Format on my PC) and everything works brilliant!
Thanks to you all, what a great Forum
Click to expand...
Click to collapse
Am I missing something? I don't have a Format SD Card option under Settings on WM
Ok soooo only hyper droid works and other build dont
well play around with the kernel in Hyperdroid and mess with the data IMG ,
voila
then even hyper droid wont work,,,,,
Sorry mate , just kidding,
your issue seems to be with startup txt,
best regds
xnifex said:
Am I missing something? I don't have a Format SD Card option under Settings on WM
Click to expand...
Click to collapse
I don't know!? I have the newest energy rom and on basic Windows Mobile 6.5, you also can find this option. Use the newest energy rom, go to Settings and then to system. There you can find KeyLock-Settings,Device Information,Format SD-Card,Remove Programs,Memory,Screen,External GPS,aGPS Settings,G-Sensor, Certificates, About,Uploader,Wipe,Power etc.
Ok soooo only hyper droid works and other build dont
well play around with the kernel in Hyperdroid and mess with the data IMG ,
voila
then even hyper droid wont work,,,,,
Sorry mate , just kidding,
your issue seems to be with startup txt,
best regds
Click to expand...
Click to collapse
Yeah, as I said, it has nothing to do with the startup.txt. I solved the problem with the method, explained in another Thread. Now I tried 11 Builds (MDJ has the best ) and everyone works.
It's a mistery to me, why hyperdroid worked without to format the sd card via winmo, but who cares? Everything works fine, and thats awesome )

Categories

Resources