Database Users

problem with android!!!

this is really getting irritating but every time i put android on my storage card it wont work , i download the basefiles zip from vogue android and extract that to my storage card then download the system image and put that on my storage card and every time i start haret and it boots to android but it gets to the part where its searching for the system image and it says it cant dind it

Have you renamed the system image to system.sqsh?

no it was system.img but i havw also tried another system.sqsh and neither works

Put the system image in the android folder on your Sdcard.

that could be why i will try thanks

If you use the latest Basefile HERE
And try this ION Donut build
Everything in root of your SD Card. Can be FAT32 or FAT32/Ext2/Ext2 (when you use F/E/E you must press Volume Down when he ask to run the installer)
And update your default.txt with this information:
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL "\Storage Card\zImage"
set initrd "\Storage Card\initrd.gz"
set cmdline "board-htckaiser.panel_type=2 ppp.apn=internet ppp.username= ppp.password= pm.sleep_mode=0 mddi.width=320 mddi.height=480 lcd.density=160 no_console_suspend board-kaiser-keypad.atttilt=1 msm_sdcc.msmsdcc_fmax=32000000"
boot
Then it will work. It work for me and for some other...

Cyanogen Rom 6 RC1

This thread was initially an inquiry on the Cyanogen Rom however is now a Rom thread so here we go.
Background on the Rom is here http://www.cyanogenmod.com/about
On the Hd2/Leo mod see here http://pastebin.com/BBf1hr50
memin1857 said:
INSTRUCTIONS
Cyanogen Mod RC1 - Leo build by Zego WITH ADOBE FLASH and 3G WORKING
There is a new nice build called CM6-HTCLEO (Cyanogen Mod RC1 - Zeto)
It needs a lot of prep work to get to good working order, then its really good.
I have also managed to get adobe flash working. (It doesn't work out of the box)
This build
(after all the steps) have gps, camera (with proper flash exposure), camcorder, camera flash/led/torch, adobe flash, nice look and most other goodies available.
Here are the steps
1) Download cm6-htcleo.7z from:
http://www.mediafire.com/?kzo7fxi2hp917s8
2) Download phone button (keypad) fix:
http://www.mediafire.com/?qrs4w0kd470keqm
3) Download MTU fix from:
http://www.mediafire.com/?tqggvgrzb79gm24
or
http://www.megaupload.com/?d=JL368N3N
4) Download Cotulla 23 July nospeed zimage from:
http://cotulla.pp.ru/leo/Android/Cotulla_zImage_CABDET_NOSPEEDDY.rar
5) Extract the cm6-htcleo.7z file and put the cm6-htcleo to your sd card root.
6) Extract the cm6-htcleo_keypadfix.7z file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. (Not to sd card root folder. I really mean a folder named root. You will see it in the archive)
7) Extract the cm6-htcleo-datafix.zip file and put the FOLDER NAMED root UNDER cm6-htcleo folder in your sd card. Just merge them. (Say yes when windows asks) Credit: ElBartoME
8) Extract Cotulla_zImage_CABDET_NOSPEEDDY.rar
and put zimage file to cm6-htcleo folder and overwrite.
credit: cotulla
9) ONLY DO THIS STEP IF YOU CANNOT BOOT (linux complaining about mmcblk0): Open startup.txt with notepad and
replace the line
set cmdline "rel_path=cm6-htcleo"
with:
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
credit: dusty_nz
10) Run clrcad and haret as usual but from cm6-htcleo folder. Once Android has booted start terminal app.
11) write
su
and press enter. It will ask for superuser permission. Tap allow.
12) write
mount -o rw,remount /system
and press enter. You should not get any response or error.
13) Now launch ES File Manager and tap \ on top left.
Navigate to /system/app and find
com.adobe.flashplayer apk file and delete it.
14) Power off your phone in a normal way and reboot to Android CM6.
15) Go to Market and install Adobe Flash 10.1 Beta 3 (use your gmail account)
Done!
Notes:
-FIRST BOOT WILL TAKE A LOT OF TIME! BE PATIENT. IT WILL TAKE A LOT LONGER THAN YOUR USUAL BUILDS.
-ADOBE FLASH does not work out of the box. You have to reinstall it but since it was cooked in to the rom as system app and you can't uninstall it, you need to mount /system directory read/write and delete flash so you can install it again. This time it works properly.
-You may not be able to boot if you do not edit the startup.txt
-You may not be able to wake up if you do not replace the zimage with the older 23 july one. You can use 25 july panel on off zimage if you CAN wake up from sleep. It depends on hd2 lcd panel type which is more than one.
Optional: Install Launcher Pro and make it default home screen to get a smoother experience.
After ALL these operations, this seems like the most functional build.
Cyanogen is normally a mod for android and someone named zego turned it into a hd2/leo build. A lot of stuff was missing and there was no central infromation. That was what I did. You don't need to read 6 pages to get this build working this good now.
I recommend disabling live wallpaper. Static wallpapers are faster. Formatting sd card beforehand and using a class 6 sdhc card is also recommended.
I don't have time to package all this stuff into a build. Maybe someone who does above steps can package it in a new single file and put to megaupload/mediafire (mskip/Mark?) For now you have to do it yourself. You will like the end result.
Packagers please don't call yourselves devs and give credit to original hard working people. Donation is also recommended.
I am sorry if I forgot to give credit to anyone.
I got all this information by reading all the pages of this thread and some more. Now you don't have to.
Click to expand...
Click to collapse
From makavelitha
Good
+ Successfully booted on the first try
+ Camcorder is finally working with the original HTC app (i hope someone will port this to the other android builds)
+ Flashlight is finally working with the original HTC Flashlight App
+ No SOD or GSOD with cotullas zImage 25.07 (maybe i have a Sharp Panel?)
Bad / Problems
- Bad Performance (especially at scrolling)
- Can't Download anything from the Market, i get always the message that my Storage Card is full, i've checked it and android shows me 0mb left on my SD Card, but i have more than 4GB free on this Card (it was working in all other Android Builds)
- Needs time to boot-up
- No or Bad Battery Management (already optimized in other Android Builds)
- USB Storage not working (already working in other Androids)
- Bluetooth finds other devices but can not be paired
- Compass works but it doesn't show magnetic north.
- Low volume issue is already known. During a call other party hears echo of his own sound when speaker is on. No echo in normal mode.
Performance Tweaks
Update I:
Using Cotulla zImage 7/25/10 makes a huge difference in speed!
The only thing still sluggish is scrolling through the apps....
Otherwise from that this is a very good build. Nice pre installed apps, good out-of-the-box build.
Update II:
Changing the application drawer to "Horizontal" like on the Galaxy S eliminates scrolling speed issues when scrolling through the apps.

dusty_nz said:
So looking at the Cyanogen rom, Swapping out the Zimage and trying to boot.
Has anyone tried this?
Would it work?
Looks like it has heaps of Qualcomm optimized components
Click to expand...
Click to collapse
http://www.mediafire.com/?kzo7fxi2hp917s8

And don't forget to add the phone button fix:
http://www.mediafire.com/?qrs4w0kd470keqm

any changelog of this mod/port ?

Readme:
http://pastebin.com/BBf1hr50

on this build flash doesn't work for me in the browser.

I am running it at this moment, it boots correctly until android froyo wizard.
It runs correctly for a minute and SOD
Ah it wake up, great
For the first time in the leo android world, the camera works
I give you more feedback later ...
Update:
- GPS works perfert
- Reboot not work, like other builds
- Import contact from SD not works
perhaps the one based on RC2 will be better, where have you find the links for this build ?

I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.

idcom said:
I can't get this to boot.
Initrd keeps looking to mount /mnt/sdcard against /dev/block/mmcblk0p1 and falling over. I only have the one FAT32 partition on my sdcard which normally is at /dev/block/mmcblk0.
Also should I be extract the .tar.gz file into the CM6 directory or put it up at the root of the sdcard.
Thanks.
Click to expand...
Click to collapse
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"

m4ck said:
Try replace cmd cmdline
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
Click to expand...
Click to collapse
Thanks. Worked a treat. Now to play.

Nuja said:
any changelog of this mod/port ?
Click to expand...
Click to collapse
Yeah I agree guys, can you please be a bit more specific about what is additional from other froyo with/witout sense or Eclair?
readme file does ntoe give much in fact.... A couple of screen shots would be fantastic...;-)
general statement: Donate, so all mods/chefs/devs can eventually pay some flowers or perfums or sex toys to their girls friends (all of them so angry that they spend so much time developing stuf !!!)

Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about

Anyone having problems with 3g on this build?

nordicfastware said:
Well.... more info on what cyanogenMod is on:
http://www.cyanogenmod.com/about
Click to expand...
Click to collapse
Thank you, but there is no mention of build for our HTC HD2
Who is the maker of this build for HD2 ?

the build is done by Zego from the IRC channel compiled from source of CyanogenMod 6.0.0 release candidate 1
I tried it last night and it gives me SOD repeatedly, it's fast, but the SOD is killing me, I am falling back to Darkstone's FroyoV1

Hmmmm
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument

lucian777 said:
Anyone having problems with 3g on this build?
Click to expand...
Click to collapse
Yes. I had the same with Dan's Froyo v.1 but Darkstones works a treat. Changed the apn's to voda uk and all that.

booted first time - took a while but OK
Loaded with apps
camera working
Video recorder working
GPS working
man it's fast..........
will test further and report back

dusty_nz said:
Not booting for me.
Formatted a SD card. Single Fat32 partition.
Extracted zip to \cm6-htcleo\startup.txt etc.
Changed the Startup.txt to
set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0"
error
/init: line 88: mmcblk0=mmcblk0: not found
Logical sector size is zero
mount: mounting /dev/block/mmcblk0 on mnt/sdcard failed: invalid argument
Click to expand...
Click to collapse
took out the set cmdline "rel_path=cm6-htcleo loop_partition=mmcblk0" ands its booting further. Got wizard

I for one am excited for this development. The collaboration from the devs here along with cyanogens work is fantastic. Any chance of getting cyanogen directly involved and/or once a build is completed would an official thread on this be desired?
I am not a coder but I'm working on it. Until then I'm just a fan and a donor. I've been a long term user of cyanogens work and I can safely say with the joint efforts of everyone here, this would be a powerful development. Keep up t the awesome work!
-------------------------------------
Sent via the XDA Tapatalk App

[Q] updateing your kernal?? ( going insane need a how to or something)

ok so im not a really noob to xda but i have been looking for 3 days on a clear how to update a new kernal... i just cant find it im not sure if im wording it wrong or what please help you will be my internet hero and my mind will stop going insane...
thanks

Is this for hd2? If it is then all u do is find the kernal u want and replace with the old one. What build are u using by the way.

Read this:
http://htc-linux.org/wiki/index.php?title=Leo/UpdateKernel#Installing_latest_Linux_kernel_image_.28zImage.29

All you need to do is copy in the zImage and .ko files. The .ko files go in the "modules" folder, a subdirectory of "root."

Most of the kernels will come with following files :
zImage - The Kernel
bcm4329.ko - Wireless Module
tun.ko - Networking Module
yaffs.ko - File System (Optional at this time)
The way I apply the kernel is shut down the phone and use card reader and attach to my laptop. Assuming your build is under SDCARD\Android, files are copied to following locations :
zImage -> Android
*.ko -> Android\root\system\lib\modules
Anything to do with the lights modules goes to Android\root\system\lib\hw
Anything to do with RIL (like libril*) goes to Android\root\system\lib
Create the \root\system\lib\* directories if they dont exist, like for Sense builds. Now just back normally.
Hope it helps

v-b-n said:
The way I apply the kernel is shut down the phone and use card reader and attach to my laptop.
Click to expand...
Click to collapse
Is it also possible to update kernel without external card reader, by connecting HD2 to the PC (USB) and replacing files while in Windows Mobile HD mode?
THANKS!

What if a certain developer updates his android build and version, do I just copy the new stuff on the SD card, overwrite, and keep the Image iso file so I dont lose my settings ?

Do any of the above and finally to verify that a kernel is installed start Terminal Emulator (or any available terminal program) and enter:
uname -r
Should give you the kernel version.

Hmmm usually, what I do is either connecting the phone in USB in Windows Mobile mode, or power off and use a micro-SD card reader. Then:
- BACKUP the DATA.IMG to desktop or whatever
- Delete the root directory in your Android folder if there is one
- Delete all the .something directories (temp dir created by android)
- Copy the content of the kernel in the Android dir : Haret (emulator), initrd.gz (boot logo), zImage (drivers/kernel)
>Ignore the dev folder in hastarin build for example
>DO COPY the "root" folder (of hastarin 7.6 for example) to the android folder : HARET will update the android OS "suppletive drivers parts" without any need to enter commands or else (what i've been told)
Done

[Q] Can some one please help me?

Can Someone please help me, I know this can't or haven't just been happening to me. Now I downloaded all roms thats suppose to be be able to be used with magldr so I can dual boot with Wp7. I have DL.DesireZ.v2.1.SD and this works when I boot it with magldr also copeNwarren 020211 works and Motoman's Mytouch4g works. Now when I try to boot DL.DesireZ.v3.4.final.SD and MDJ HD 4.6 with magldr it gets past the boot screen but once it starts to load and everything it freezes at the lock screen everytime i boot them and im not understanding why. Espeically when DL.DesireZ.v3.4.final.SD is just an update from DL.DesireZ.v2.1.SD. So can someone tell me why they are freezing before i even get to set them up. Thank You

What directory you are using for Dezire Z? Version 2.1 can use any directory, but 3.4 and higer can work only in Desire_DL directory. Also try to use clean data.img with new version of Desire.Z

If you want boot DesireZ 3.4 from Android directory, put in this directory only 3 files: startup.txt zImage & initrd.gz
In Desire_DL directory you must put conig.txt system.ext2 & data.img

thanks for responding. but im not sure what you mean. I leave the desire_dl 3.4 in the desire_dl folder and just place it on the root of the sd card like it says and then go to magldr and boot it. but it just always freezes before i get to setup it up. It runs when i go to haret from Winmo6.5 but when i run it in magldr it freezes at that lock screen before i get to set it up.

Problem about Manual Rooting + Gapps 1.1

I did exactly what was written in the Development Section and more but unfortunately i couldn't manage to root it
First of all do i have to say i am no expert in these matters. Well i am not.
Somethings are missing in the guide for people who are not familiar with these things. For example it doesn't mention about how to create platform-tools folder in android-sdk-windows. I thought maybe i could do it from software and updated&installed bunch of things. Than voila i got the platform-tools folder.
In the "Setting up adb on the nook touch:" section we were told that write noogie to sd boot it and eject it away. And are we done with the sd card in the next sections ? Anyway i assumed as i don't need the card anymore and put it away.
When i came to "Setting up root acces on NST through adb and installing busybox:"
do the steps and entered the commands to Command Prompt(CMD). Everything seems fine but Nook didn't boot. I think maybe i can go to next step and enter those commands. I did it but it didn't boot either. So i manually booted the device and entered first line of commands again right after that finally Nook booted!
So i thought i only did the first command line set in the "Settin up root access on NST thorugh...." section so that i entered the second command set again but it didn't booted. And than i have proceeded to the next steps for the chance that if it went fine but directions made me thought it didn't. But when i came to Launcher and gapss part , it didn't boot so i figured that somethings was not right.
I don't know wtf is wrong but i thought maybe i should format and plug the sd card or just plug with noogie right after i thought we were done with sd card. So i did all those steps with the sd card formated and with noogie sd... It was all same.
Sorry for my unpleasant english. Please help me. For the "please help me lord" line i am sharing this song with you youtu.be/kLCCEipgmJQ

xisini said:
In the "Setting up adb on the nook touch:" section we were told that write noogie to sd boot it and eject it away. And are we done with the sd card in the next sections ? Anyway i assumed as i don't need the card anymore and put it away.
When i came to "Setting up root acces on NST through adb and installing busybox:"
do the steps and entered the commands to Command Prompt(CMD). Everything seems fine but Nook didn't boot. I think maybe i can go to next step and enter those commands. I did it but it didn't boot either. So i manually booted the device and entered first line of commands again right after that finally Nook booted!
So i thought i only did the first command line set in the "Settin up root access on NST thorugh...." section so that i entered the second command set again but it didn't booted. And than i have proceeded to the next steps for the chance that if it went fine but directions made me thought it didn't. But when i came to Launcher and gapss part , it didn't boot so i figured that somethings was not right.
Click to expand...
Click to collapse
Download noogie, and burn it into an sd-card (http://www.multiupload.com/OFI609MP8V) use Win32DiskImage.exe.
Shut down the Nook Touch completely your NST http://www.multiupload.com/CJ981FWPJG
Insert the sdcard into your Nook, connect it to the pc and turn it on.
When the nook ends booting (you should see a rooted forever spash screen on it) wait 20 seconds, you should see a new drive named boot, if not, go to MiniTool Partition Wizard Home Edition look for a parition named boot and asign it a letter.
Open boot, and replace the uramdisk, with this one http://www.multiupload.com/CJ981FWPJG.
Eject the nook from the pc and reboot without the noogie sdcard.
Download java JKD http://www.oracle.com/technetwork/ja...ads/index.html
Download the android sdk (I recommend zipped) and extract it on C so that it looks like C:/android-sdk-windows
I will add an step next, that is open the sdk, and update it.
And for the second comand line...... its adb connect yourNSTip where yourNSTip means... your Nook Single Touch IP address, so find that out and right it instead.
Read carefully, if you dont know what you are doing, you are better off using the touchnooter method, wich is simple and just works as intended and you wont mess things up so easily.

I don't know why you enlarged reboot part which i did correctly. And there is nothing wrong about ip adress part. If you would read carefully! I wrote that it is just didn't reboot automaticly as it is in the command line.
Btw if i would know what am i doing i would not need a guide so did you open that topic for just to proove that you did this. What kind of behavior is this ? Reread what i wrote or just don't try to help me with your blindfold and arrogance. I suppose there will be polite person in XDA who can help me out.

I posted the topic to help someone in particular and of course anyone who wants to use it, and myself to remember.
I couldnt understand halve of what you wrote, and I know you appologised for it so I didn't mention it.
As it says, this is a first draft, there may be typos, next time just say where you got stuck clearly, it'll be easier............
Now, I know you got stuck on the reboot at rooting, you shouldn't but I'll change the code a bit.
I also didnt intend to be rude, maybe you read me wrong, maybe you are the one being arrogant here as you got mad because I enlarged reboot, allthough I was trying to help you even if I was wrong.
If you have 0 adb experience I recomend you try touchnooter, its easier and faster, if you intend to learn adb, my guide is self explainatory, and just copying one by one the commands on cmd is enough, learn to follow instructions.
Don't worry I wont help you again

This becoming a pissing contest and i don't want to talk about it anymore.
So here is the thing. I have tried this method
mobileread.com/forums/showthread.php?t=156539 "i couldn't make it a link because i had few posts"
And it worked out well until pushing Vending.apk
Here are the things i did to make it work
1- Opened up and turn on Adb wireless widget
2- Located the Vending.apk to c:/android-sdk-windows/platform-tools/system/app
3- And then wrote these commands
cd C:/android-sdk-windows/platform-tools
adb connect 192.168.2.20:5555
mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push vending.apk /system/app
C:\android-sdk-windows\platform-tool>adb push Vending.apk /system/app
182 kb/sn (2123059bytes in 11.380s)
Click to expand...
Click to collapse
It seems okay but when i try to search from market i see that it is not.