Update 8-5-09 12:13am est
I've started a new thread @ http://forum.xda-developers.com/showthread.php?t=544906 this should avoid a lot of confusion since this thread contains a lot of old information about previous builds. Some of the information contained here does apply but read carefully because most of it is old information. If your coming here and your not using a vogue then your questions most likely won't get answered. Right now this works on most vogues and kaisers. I do not know if this works on any other device other than those and I am not going to be porting it over to anything else. If you want to try I suggest you ask in other forums specific to your phone. Before you download anything read the tutorial on the new thread or at http://code.google.com/p/vogue-hero/ follow the directions. If you have general questions related to android on the vogue then post them in the android help desk thread.
The new full build I've been testing the past couple days has been holding up pretty good. Sense UI, GPS, Market, partial SMS, flash, data all work fine for me. I ran it all day with 4 widgets and animations turned on and had no lag on the home screen. It is back to using vilord's regular initrd.gz and rootfs.img. I'm going to do some minor changes and release it sometime tomorrow. After that I will be done with hero for a while. I'm most likely going to take a look at some of the new donut stuff google has been cooking up. Don't expect this release to be feature complete. It's not. It works for what I do with my phone since I use email and IM and I don't rely on sms. I don't have time to test every part of the build. For example I don't use exchange or active sync. If you don't see your city in the weather app or widget then use google maps and turn on gps. Stand outside in a clear area for around 5min until it finds your location. Then switch back to the weather app and tap on my location it should pick up your location and city and give you the option of adding it. This worked for me today. I've sent sms and the person received it even though it said it failed to send. They replied back and I didn't receive the reply this is already a know problem. I've made and received several phone calls and haven't had a problem. I've used market to download apps it works. If you need sms and want a everyday android I suggest you take a look at vilord's Ion builds or mssmision's themed Ion builds or his hero-lite without sense ui. While I use my builds and they work fine for me it's really only a proof of concept and shouldn't be relied on if you need to receive important calls or messages.
Update 8-4-09 7:53am
I'm testing a new build right now. It has all the widgets and apps. The speed is like the current build posted at the site. I'm going to test it for a day or two to see if there are any major bugs. If all goes good I will put out a release. Thanks for testing and thanks to mssmision and vilord for all their help.
Update 8-4-09 3:28am
This isn't a Sense UI theme. This is the real thing. It is a minimal build with some apps and widgets removed to improve speed and stability. It won't void your warranty as nothing is flashed and nothing is permanent. It runs android from your sdcard and only uses the devices memory and doesn't touch devices main storage other than the sdcard. When you boot back into WinMo everything is just the same as it was before. The files featured at the google code site are the latest and most stable. If you want to ask questions or have problems be specific. I'm not going to be following this thread that much as there are users out there that are already experienced enough to take care of the questions for new users. I'll put out a new build sometime in the future to merge back with vilords original initrd.gz and rootfs. It will most likely include some missing widgets and apps that people have been asking for. I hope you enjoy this build as much as I do. Thanks for testing.
Update 8-02-09 8:01pm est
I've uploaded a new Hero build. It uses the new initrd.gz with a modified rootfs.img. The original rootfs.img can be found @ http://code.google.com/p/vogue-android. The Orange logo has been removed and it's sporting the wallpaper from my full build. No widgets loaded up on initial startup except for two toggle switches for Mobile and GPS. It's really fast. Initial startup without a data.img should take less than 5 min. The zip contains everything you need except zImage. Clear out the root of your sdcard. Download Hero-8-2-09.zip and zImage. Extract Hero-8-2-09.zip to the root of your sdcard. Rename system-8-02-09.img to system.img. Copy zImage to the root of your sdcard. Do not use an existing data.img. A new one will be created on first boot. Edit your default.txt to work with your vogue keeping the lcd density at 160 and the resolution at 320x480. If you don't know how to edit your default.txt then read the file it has examples. If your still not sure to then ask around in the vogue android threads. Execute haret and tap run. Wait a couple minutes you will see the HTC/Android boot logo and hear the chime. Wait a little bit more and the setup screen will come up. When the HTC keyboard comes up press the gear icon to the left of the space bar. Tap on Text input. Scroll down and tap on Calibration tool. The Calibration tool will walk you through the rest of the way. Push back (volume rocker up) to get back to the setup screen and continue the setup. I suggest you set up a google account to use market. After setup you are taken to a minimal home screen with two toggle widgets for GPS and Mobile. I suggest you download another messing app like chompSMS or handsentsms if you want sms because the HTC messenger is not 100% it will send sms but it will tell you it failed even though it really went through. I also changed the default home page in the browser to google.com so you don't have to sit and wait for HTC.com to load up. Hope everyone enjoys this as much as I do.
Direct Link to zip: http://vogue-hero.googlecode.com/files/Hero-8-2-09.zip
Direct Link to zImage: http://vogue-hero.googlecode.com/files/zImage
Project Home: http://code.google.com/p/vogue-hero/
Thanks to dzo vilord and mssmision for all their great work.
Internet enabled, I'm assuming?
working on it.
When modem runs it isn't getting the right permissions it seems. What did you change? Have you compared to the cupcake build on the other google code page?
No I haven't. pppd needs to be run as root and i think this might be the problem. As for compairing to the cupcake build there are no parts of it in there. This is a port of a sapphire rom with a modified initrd from the ion build. I'll check and see later what the diffs are between the builds as far as getting pppd to work. Anyway here is the output from the adb shell when setupmodem.sh is executed.
# ./setupmodem.sh
grep: /proc/cmdline: Permission denied
./setupmodem.sh: line 17: can't create /smodem/setupmodem.pid: Permission denied
Initialising Modem:
===================
./setupmodem.sh: line 24: can't create /smodem/ppp.log: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
Username=
Password=
APN=
./setupmodem.sh: line 37: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/working: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
/bin/pppd: must be root to run /bin/pppd, since it is not setuid-root
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
rm: cannot remove '/smodem/working': No such file or directory
^C./setupmodem.sh: line 77: can't open /smodem/control: Interrupted system call
I'm going to sleep. I'll start back at it tomorrow.
Interesting, thanks for the release. I like some of the new features that hero has, but don't like what they did with the appdrawer bar. I liked the swipe up motion and it was a big target. I'm just happy I finally got to play around with hero a little, thanks again for all the work.
zenulator said:
No I haven't. pppd needs to be run as root and i think this might be the problem. As for compairing to the cupcake build there are no parts of it in there. This is a port of a sapphire rom with a modified initrd from the ion build. I'll check and see later what the diffs are between the builds as far as getting pppd to work. Anyway here is the output from the adb shell when setupmodem.sh is executed.
# ./setupmodem.sh
grep: /proc/cmdline: Permission denied
./setupmodem.sh: line 17: can't create /smodem/setupmodem.pid: Permission denied
Initialising Modem:
===================
./setupmodem.sh: line 24: can't create /smodem/ppp.log: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
grep: /proc/cmdline: Permission denied
Username=
Password=
APN=
./setupmodem.sh: line 37: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/working: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
/bin/pppd: must be root to run /bin/pppd, since it is not setuid-root
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
./setupmodem.sh: line 77: can't create /smodem/ppp.log: Permission denied
rm: cannot remove '/smodem/working': No such file or directory
^C./setupmodem.sh: line 77: can't open /smodem/control: Interrupted system call
I'm going to sleep. I'll start back at it tomorrow.
Click to expand...
Click to collapse
Rather than comparing to the cupcake release, maybe get in touch with mssmison. I've been testing his Hero build for the past 2 days. He's got the network going just fine.
I dunno what kind of feedback you're looking for at this point, but I tried yours, and it hung in the startup wizard. Kept telling me I had no network connection, and I couldn't back out of it to disable the "Auto-sync with Internet" option, or whatever it's called. So I was stuck. I'll try again when you've got the pppd permissions fixed.
Updated Build
I'm testing a new build right now. The problem with pppd is now fixed. I'm going to make sure it will work with a fresh data.img before posting it to the google code site.
does this build have a problem mounting the sdcard
New build up.
The new hero-black build is up at the google code site. No data.img is required. Internet is working now. I'll keep trying to tweak things here and there over the weekend.
sdcard
I haven't had any problem mounting the sdcard or heard of any problems yet.
The version from earlier was missing a lot of widgets and was really slow.
Did you add any widgets back/improve speed?
When you go through the initial boot and set up everything starting from a fresh data image everything is there for me in the new build. The over all initial boot and setup is alot better experience as far as I'm concerned. The only draw back with going this route is that it loads 5 screens full of widgets. The widgets really bog down the system. The max I recomend is maybe 2 widgets at a time until I get the speed and swap sorted out. On my system right now I have a swap file enabled and it's running decient with two widgets and touchflo.
zenulator said:
When you go through the initial boot and set up everything starting from a fresh data image everything is there for me in the new build. The over all initial boot and setup is alot better experience as far as I'm concerned. The only draw back with going this route is that it loads 5 screens full of widgets. The widgets really bog down the system. The max I recomend is maybe 2 widgets at a time until I get the speed and swap sorted out. On my system right now I have a swap file enabled and it's running decient with two widgets and touchflo.
Click to expand...
Click to collapse
yeah I haven't noticed if it used a swap file. that should give it a moderate speed boost.
derekwilkinson said:
yeah I haven't noticed if it used a swap file. that should give it a moderate speed boost.
Click to expand...
Click to collapse
im running zenulator's system with mmsmisons swapfile, it doesnt seem to be too fast
I'm working on another build right now that has more optimizations. Can't really expect much from a build that didn't exist 24 hours ago.
zenulator said:
I'm working on another build right now that has more optimizations. Can't really expect much from a build that didn't exist 24 hours ago.
Click to expand...
Click to collapse
oh no im not trying to put you down or anything im just stating the facts as of now. thanks for your hard work!!!!
It's all good. Just sayin it's only going to get better.
Umm.... anyone else having a problem where the keyboard doesn't appear during the initial setup wizard?
EDIT: Crap, nevermind. I hit submit on this post, and then the KB popped up on my phone. :S Took like 3 or 4 minutes though.
zenulator said:
This is a port from the sapphire rom hero-black.
Click to expand...
Click to collapse
So wait, this is a Hero ROM, or a Sapphire ROM that has TouchFLO included in it?
Would it be possible to set the phone up so that on first boot there are no HTC widgets loaded? After finishing the first-run wizard, it was about 15 minutes before I could do anything with the phone, and even that wasn't easy. As I've (slowly) been able to remove widgets, it's become more usable. It'd be nice if there were no widgets to start, and people could add them as they please.
Related
registered just to find some help with this...
just got a N1, used to have a G1. both rooted, and i'm trying to migrate my mmss and smss to the N1. copied the mmssms.db out of the G1 and saved it to the sdcard. placing it in the N1's /data/data/com.android.providers.telephony/databases/mmssms.db (via Better Terminal Emulator Pro) does not restore the texts. could this be a permissions issue or did they move the mms and sms database?
How does this fit in the Development Section? I am not trying to be rude... but...
why you dont try an sms backup ap?
Solution
This is because you do not have busybox installed yet (cyan will be posting later). You can push it via adb using the following command:
Code:
adb push c:\mmssms.db /data/data/com.android.providers.telephony/databases/mmssms.db
Reboot your N1 after you push to see your messages. Worked like a charm for me.
seraph1024 said:
How does this fit in the Development Section? I am not trying to be rude... but...
Click to expand...
Click to collapse
The problem is that there is no Q&A section and it makes more sense that the General section since it will take a dev's solution to fix the issue. A Q&A section needs to be added.
seraph1024 said:
How does this fit in the Development Section? I am not trying to be rude... but...
Click to expand...
Click to collapse
sorry, i figured this was more tech-y to go in the General section.
also, i'm able to copy the mmssms.db to the location, but after restarting my messaging app crashes (both the default and handcent).
permissions on my mmssms.db file after the copy are:
----rwxr-x 1 0 0 (size) (date) mmssms.db
i'm able to chmod 777 this file and restart and see it, but i assume that the "correct" way to fix this would be to chown to whoever is user "1001" and group "1001" ("1001" because that's the group and owner of the other file in this folder)
quick unix question i guess: how can i find out what "1001" refers to, as "chown 1001 mmssms.db" gives me a "No such user '1001'"?
also, it looks like the MMSs (which were what i was actually trying to save) don't get restored. causes a force close in Messaging and a "Handcent cannot display this" in Handcent.
in case anyone wanted to know. i guess that single database doesn't keep the actual images.
niiiick said:
also, it looks like the MMSs (which were what i was actually trying to save) don't get restored. causes a force close in Messaging and a "Handcent cannot display this" in Handcent.
in case anyone wanted to know. i guess that single database doesn't keep the actual images.
Click to expand...
Click to collapse
The other easy solution is MyBackup Pro. If you don't want to shell out the $5 you can get a 30 trial of the full version (all features work) for free in the Market. It will backup and restore both SMSes and MMSes. Hope this helps.
one of the comments says that even with the 30 day trial you can't restore to a different phone, it has to be to the same phone the backup is from. plus i'd really just kinda like to learn
Hmm...the main reason I wanted to root the phone was to be able to push my old mmssms.db file onto the new Nexus, interesting that it doesn't work.
The db file is just a sqlite database, I wonder if maybe the database schema has changed slightly, hopefully I can pull the one from the Nexus today at work and compare it to my backed up G1 db...
Swervo said:
Hmm...the main reason I wanted to root the phone was to be able to push my old mmssms.db file onto the new Nexus, interesting that it doesn't work.
The db file is just a sqlite database, I wonder if maybe the database schema has changed slightly, hopefully I can pull the one from the Nexus today at work and compare it to my backed up G1 db...
Click to expand...
Click to collapse
actually it was my mistake, it works, just so far not the MMS part. copy the mmssms.db to your new phone, restart. i had to change the permissions to 777 (because i don't yet know who to chown to). is the mmssms.db supposed to hold the actual images too? do you know how that's supposed to work?
AndroidAppCritic said:
The other easy solution is MyBackup Pro. If you don't want to shell out the $5 you can get a 30 trial of the full version (all features work) for free in the Market. It will backup and restore both SMSes and MMSes. Hope this helps.
Click to expand...
Click to collapse
thanks for the suggestions. one of the comments says that restored MMS's can't be viewed.
this is the only problem i'm running into doing it manually. i just need to know where the mms's are kept in the system or why they won't read from mmssms.db...
ok, if anyone cares, i've successfully manually moved my SMSes and MMSes from my rooted G1 to my rooted N1.
had to use ADB.
used superuser'd terminal in the G1 to copy the following to the sdcard (though i suppose you could ADB pull them off the G1)
/data/data/com.android.providers.telephony/databases/mmssms.db
/data/data/com.android.providers.telephony/app_parts/*
copied them to my comp
then
adb push c:\mmssms.db /data/data/com.android.providers.telephony/databases/mmssms.db
adb push c:\app_parts /data/data/com.android.providers.telephony/app_parts/
or somethin like that. basically move mmssms.db and all the files in app_parts to the nexus one, same directory.
if you don't do it through adb, then you might have some permission errors and the messaging apps would force close. just chmod 777 all of these files (and the app_parts folder) unless you know who to chmod to (cuz i didn't) and it should work. let me know if you do it that way, cuz i haven't tested it.
edit: after this, sending an MMS would force close, and trying to download one would fail. back in the adb shell:
cd /data/data/com.android.providers.telephony/
chown radio app_parts
chmod 771 app_parts
i suspect that this is because i had created the app_parts folder via ADB instead of letting the system create one when the first mms is sent/received on an N1. either way, afaik all mmses work now.
I missed your reply to this, doh!
[Removing bad instructions]
The method I posted works great, as long as you never try to send any texts. Once I sent some, they ended up in random order in the thread, then the phone started spewing multiple copies of the same message, at least 15 or so to my wife in about 30 seconds, I had to go into airplane mode to stop them, and then just restored from a nandroid backup. And I don't have unlimited texts...oops...
Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889
bowtieduece said:
Ran across this thread in the evo section, seeing how we also have htc's flash lite. It made me hopeful of attaining root. Ive tried every card mentioned as being successful on three different systems:-(
http://forum.xda-developers.com/showthread.php?t=718889
Click to expand...
Click to collapse
Even though I didn't really think it would work, I gave it a shot anyway. Naturally, it was unsuccessful. The Eris take FOREVER to load that website, and it never triggers the shell script to ask for a reload, therefore permission is denied for the second part when you reboot with adb shell.
Interesting exploit, though. I wonder if there is some way to modify it for the Eris. Maybe you could contact the devs.
Really, nobody else is interested in this?
MyFixofAndroid said:
Yep that's what I expected. Yea there's gotta be someone here that can do the changes to the EVO files so they work with Eris, and upload the proper files to file sites and have us downloading in no time, so we can get root finally. Yes please anyone here up and willing
Click to expand...
Click to collapse
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.
sickbox said:
Toastcfh used to do some work for the Eris someone may want to start there since he provided what looks to be a pretty main part of the EVO root.
Click to expand...
Click to collapse
Thanks for the tip. I sent him a PM. Will report back when I find something.
Anyone with an Eris can help out - rooted or unrooted.
I looked at those scripts last night - what seems like the necessary conditions for the beginning of the exploit (part1) are:
(1) there is a directory read/write/traversal permission security flaw in the data area for flash-lite;
(2) apparently, when flash-lite is running it must have root privilege at a moment when it performs a file "chmod" operation
So, an unprivileged user goes in, and makes a symlink (at the correct moment in time) in flash-lite's data area that points to a mtd partition - moments later, flash-lite "chmods" what it thinks is a file in it's data area, but instead, it is chmod'ing the target of a symlink - the normally protected mtd partition.
This allows use of flash_image to write whatever is wanted to that partition - even as an unprivileged user.
It should be easy enough for someone with Linux/Unix command line scripting experience to test to see if these conditions prevail on the Eris. You don't even need to be root - make your symlink point to something in /data/local if you are worried about something bad happening to a mtd partition. Chmod it initially to 600, and see if it get's changed by flash-lite when (and if) you drop the symlink into place.
I would do it, but I've got to go buy all the parts for ( & build) a new computer (no dev station as of last night ).
bftb0
bftb0 said:
Anyone with an Eris can help out - rooted or unrooted.
bftb0
Click to expand...
Click to collapse
Thank you for the detailed explanation. I'll have a look at the scripts, though it's more about learning new things for me, as this exceeds the current state of my unix knowledge. Hope others with more immediate knowledge of the subject will take a crack at it.
The shell script points to sharedobjects within /data/data/com.android.browser/flashlite, but sharedobjects, nor any folder for that matter, exists within that directory on the Eris. Is there a different place this could point; does the Eris have the same objects stored in a different location?
UPDATE: I'm searching my filesystem on my Eris right now to find it. I will report back later with results.
Also If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.
MyFixofAndroid said:
Maybe the "sharedobjects" folder and other missing folders are really on the Eris, one of you should look for them. Use ASTRO or a different file manager and search most of the whole filesystem and see if you can find "sharedobjects" on your Erises.
In the meantime I'll try the same thing. Maybe there's a search engine for the file system of the Eris that you can get in the Android Market, that would do the trick. A file and/or folder search engine.
If we find a sharedobjects folder (and the right one) then we can point the script in the proper direction and have root very soon.
Click to expand...
Click to collapse
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.
I checked on my other Eris which is rooted. It seems that these may be the directories that we are looking for. However I don't find anything in an app-cache directory.
# find / -name *flashlite
find / -name *flashlite
/data/data/com.android.browser/flashlite
find: /proc/851: No such file or directory
# find / -name com.android.browser
find / -name com.android.browser
/data/data/com.android.browser
Well this appears to be the deal breaker then. Because non-root users of Eris cannot access /data as non-root, they cannot see anything in app-cache, and therefore cannot root yet, at least with this particular method unless there's another way to do it.
We should think of a way to still exploit Flash Lite on Eris, but use a different folder/folders in the Part? scripts that they point to for the operations of the script. This may be possible to do, however, still unlikely to work, and it is still going to be hard at this point.
But does anyone want to give my modified EVO method but for Eris a try? One of you should, so that we can root this thing and get it over with.
jimbonj said:
From what I see (and this may just be my eris), the directory probably does exist but we can't touch it:
ls -l
...
drwxrwx--x system system 2010-04-15 02:23 data
...
No read or write permissions to the directory using adb or Astro.
I do have permissions for /sdcard/data on my Eris:
d---rwxr-x system sdcard_rw 2010-06-26 13:26 data
but it doesn't contain the referenced folders and I don't think the browser downloads temporary files to the SD card.
Click to expand...
Click to collapse
I dont think we would need read write permissions to begin with to use this root, if we had them to start we would be rooted
Because is he using a exploit in flash lite to write to a restricted folder, hes not just found a folder where the permissions aren't set correctly.
If flash lite can invoke admin access and we can exploit it there should be a way to root this.
I am going to the bar going to get some beers for my friends birthday, when I get home I am going to see if I can modify this into an eris root
Yeah JVWARD!
On your rooting effort, all the better, try modifying it for Eris and let all of us know if you succeed, hope you can, so we can get root too. Keep trying it with different changes until you get it to work.
Thanks.
You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.
You are able to cd directly into /data/data/com.android.browser/ and then ls, so all hope may not be lost yet. The flashlite directory does not show up, I'm guessing because I haven't used my browser yet so I need to try and get to a flash site and see if it is created. I'm having some problems with the touch screen my leak Eris right now that I'm trying to fix right now if anyone else wants to give it a shot.
Click to expand...
Click to collapse
Yes sickbox, by all means, keep trying stuff, and finding that "flashlite" directory etc. till you get it to root. Hope your touchscreen returns to normal, and that you can create the directory that you mentioned in your previous post by using a flash site.
Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.
hey can someone with a rooted Eris using a an almost 100% stock Rom setup dump there file system and post it. Anyone using a highly customized Rom don't bother.
Sent from my Eris using Tapatalk
lostpilot28 said:
Hey guys, I know this is a tall order, but I want to help. Any chance you could do a "step by step" set of instructions, or at least copy & paste the Evo instructions with the appropriate changes to try this on the Eris? I'm still not rooted, and the SD card Timing root method isn't working for me. I'd like to try something different.
Click to expand...
Click to collapse
Link to the Evo instructions is in the OP. Currently working to see if it's possible on the Eris, so that's a no-go for now.
Stay tuned.
Team,
I've been working with the scripts with the awesome folks on IRC and have currently gotten thus far:
Part1 - http://pastebin.com/FUJWM3zW
Part2 - http://pastebin.com/6h07zrdm
I believe at this point I've screwed up my FlashLite plugin with my testing, so I'm going to try to recover that and keep moving along.
LR
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
I wonder if other people are having these issues, story follows.
I was trying to install the updated ADW.launcher via the adb install command and was getting errors such as "/sbin/sh pm not found". This led to an investigation and it turns out that all the standard applications used to install stuff under android are in /system/bin BUT... The path in the CM6 rom does not have /system/bin in the PATH variable. The only path element as far as I can tell is /sbin. So the solution I came up with was to copy over all the tools from /system/bin to /sbin and this worked.
So here is the real question. How do I change the path on the android device? I have already tried export PATH=$PATH:/system/bin but this does not stick after I close the adb shell.
Update: oh great when you reboot the phone all the copied tools disappear and you have to do it all over again to install another file. Did not expect that one. This makes my need to change the path even more urgent.
Update2: I found it easier to just push the new file over top of the old one in /system/app. This will work for system apps and if I need to install other apps I can just load them from the sdcard.
Is there a reason you are not installing it from market? ADW is the default launcher in CM6, so the one from market is not the same, but they can coexist.
so the one from market is not the same, but they can coexist.
Click to expand...
Click to collapse
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
anika200 said:
Yea I was not really sure about that so I felt it was safer to download the one for CM6. If that works I will do that in the future. I ended up just doing a push over the older version in /system/app, this worked fine.
Is there a reason this rom does not have /system/bin in its path? Is it to avoid toolbox?
Click to expand...
Click to collapse
It is in the path.
# echo $PATH
/sbin:/system/sbin:/system/bin:/system/xbin
#
Can you help me to change the path? Mine is only /sbin for some reason.
Normal export command did not work for me. Thanks
Maybe its baked into the boot.img? What about the init scripts? Any clues where to start? Maybe I will just flash on a new nightly, would that over write the existing path info?
Ok, I found some clues. A document on the android init scripts describes the path settings. I will poke around in there and see what I can muck up. http://www.netmite.com/android/mydroid/1.6/system/core/init/readme.txt
Sent from my Liberty using XDA App
Answered my own post.
To change the path you need to edit init.rc and add the correct path.
For some reason the nightly I was using had the wrong path in there and would not let me use adb install correctly. I would get an error back "/sbin pm not found". The adb installer was looking for a tiny program (a shell script really) named "pm" but it could not find it because pm is located in /system/bin which was not in the search path. Probably would have caused other problems too.
On a side note, why could I not get an answer to this simple question on a developement thread. Seems like rom creators/moders would know this second hand. Not complaining just makes me wonder.
Sounds a lot like a complaint to me.
I've been busy working on issues that are not isolated to a bad nightly, such as why we can't read telnos and contacts from the sim card.
/system/bin/sysinit gets pulled in from the cm6 repository, so things on nightlies are very fluid - I never know what to expect. Looking at my build, there is no way I could answer your question in any definitive way that would explain the discrepancy. Since I could not verify the problem, I deemed it a non-issue and moved on.
That did sound like a complaint, sorry. It was not really directed at you as I assume there is more than one developer on this site. I got it solved no problems. Maybe this will help someone else down the road. I have seen a few of these posts around and never saw a concrete answer.
I am surprised the phone ran so well with the path mangled so bad. I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
anika200 said:
I am also a little surprised that init.rc gets touched at all on a nightly cycle. One of those things I guess.
Click to expand...
Click to collapse
I was a little surprised as well.
Hi,
Can anybody extract the APK for the LED Torch app preinstalled in Froyo?
I saw that the one include with Froyo on the Desire works with a Desire with Eclair. (But doesn't work with my Legend) So I would like to check if the one included in Froyo for the Legend will also work with the Legend on Eclair.
The package name is com.htc.flashlight
Thanks!
U don't have to wait....
Try this APP: Lamppu
But first u have to (Soft)root your Legend with (Universal Androot)
After that, install superuser APP. Now start Lamppu and allow superuser rights...
Now u can use your LED as torch.
Tried it self on my legend v.2.1
Sure about the name?
The only thing I found in the Modaco ROM was Flashlight.apk
Then again...I have no clue what I am doing
above file is not working
Yeah it doesn't install
Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Sorry for the video but I just found out how to do screencasts and love it
Its German but you should be able to understand it.
Notice that it is now uninstallable and listed as downloaded app.
denisman said:
Ok gentlemen, one more try.
Extracted, re-zipped and signed the apk using apk-manager.
Removed the system app from my phone using TitaniumBackup and installed the signed apk through Root Explorer.
Works for me. No guarantee that it does for any other ROM or Android version though.
Click to expand...
Click to collapse
Installed and ran for me in stock 2.1 but it didn't do anything with the flash when playing with it
Thanks for trying!
This one is installing correctly, and also loading correctly, but it doesn't light up the LED.
So it isn't working
Are you phones rooted?
First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend
BlaY0 said:
First of all, you have to have deodexed apk and second, you need to set right permissions in sysfs.
Sent from my HTC Legend
Click to expand...
Click to collapse
The apk is deodexed. As for the permissions. No clue how to set them right
Had to read up an hour last night just to learn enough to extract it. Big newbie here hehe. Guess I'll check some threads about sysfs permissions and try it again later.
Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend
BlaY0 said:
Sysfs is everything under /sys directory. File /sys/class/leds/flashlight/brightnes should have read-write permission set for everyone.
Sent from my HTC Legend
Click to expand...
Click to collapse
Ahhh thanks! I guess I understand now.
Ok I just flashed whitetigerdk's rev03 ROM which is a rooted 2.03 ROM.
Than I did the following in adb shell:
Code:
chmod 777 /sys/class/leds/flashlight/brightness
checked permissions with:
Code:
cd /sys/class/leds/flashlight
ls -l
and it has rw permission for everyone now.
Code:
-rwxrwxrwx root root 4096 2010-12-01 16:29 brightness
Problem is, that booting the phone resets the permissions.
EDIT:
I just repeated the procedure while the phone was booted in normal mode.
Permissions successfully changed AND flashlight is working correctly, including all three different light settings!
Still, a reboot resets the permissions.
Guess I have to find a way to make this change permanent now and all is done
Hah so cool. Never used chmod or any other linux command until today. Had to google everything while I was testing. Nice how much one can learn here.
Another EDIT:
Found something else that is interesting.
http://developer.android.com/reference/android/Manifest.permission.html#FLASHLIGHT
Would adding this to the AndroidManifest.xml help aswell? I'd do it myself but I have to work soon. Just tried it decoding the xml with AXMLPrinter and adding it. Unfortunatly I don't know how to save the xml in the right format again and just saving it corrupts the apk. If noone else wants to give it a try I'll check back after work.
denisman said:
Still, a reboot resets the permissions.
Click to expand...
Click to collapse
Yeah... this is done via init.rc which is inside initrd image. So you have two options... tweak init.rc (you would need to unpack boot.img image and extract initrd image, edit init.rc, make new initrd image and construct back boot.img... this can all be done in one swoop with dsixda's kitchen) or make a script that is run every boot (we are doing it via run-parts which also requires editing of init.rc... once again dsixda's kitchen can add this functionality in a single swoop)...
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
You are quite a fast learner, congrats.
Back home Got pretty late.
I don't actually need this since I am running a rooted Froyo ROM anyways but thought it would be an interesting task to get this working for others to easily use it and for me to learn more about Android. The first option sounds like it would require a bit too much end-user activity and would be limited to a certain set of ROMs if I understand it correctly.
Leaving the second and third option as the most user-friendly ones I guess.
I will read up more on init.rc and ways to script for it tomorrow. Sounds like a very powerful "tool" to know.
For now I will concentrate on the XML. Might be the most comfortable and ROM-independent way if I get it to work.
BlaY0 said:
As for "android.permission.FLASHLIGHT" I'm not sure about it as I can see that HTC is doing it avoiding it (setting permissions to 666 by default in FroYo)...
If you want decoding/encoding xmls use ApkManager. It's a nice CLI tool that can decompile and compile apks back...
Click to expand...
Click to collapse
Used Apk Manager to extract, zip and sign the apk in the first place. Really nice tool. Just didn't find an option to convert the xml from binary to readable, that's why I used AXMLPrinter2.jar which can do the conversion one-way but not back to binary.
I'll find a way
Thanks again for the input! Helped me a lot!