MY QUESTION:
Can anyone help me backdate my Hastarin r8.5.1 kernel to Hastarin r7.2 on my current rom?(Rom details below.)
I feel like I've tried everything, but I think I need an official kernel update with the proper system files(like w/ root files, kernel updater, zImage, etc). If needed, I can supply any files for the 7.2 kernel that I got from another rom package(also listed below). I've already attached the zImage file from it, although I'm not sure how helpful it might be.
THE DETAILS:
So, you're probably asking yourself, "Why 7.2?" Good question.
Well, first I should say, I've used many different Android builds on my HTC HD2 over the last year & with them I've tried many different kernels. I'm currently using this Sense 3.5, Android 2.3.5, v. 7.0, sd build by Boxmax here: http://forum.xda-developers.com/showthread.php?t=1256423...because I like the function & look of the HTC Sensation XL. The SD build version of the rom comes packed with the Tytung r14 kernel, but it is really laggy. I've tried many other versions of Tytung on the build, as well as many other kernels uploaded to the thread, including Hastarin r8.5.1 & r8.6 because I had read that the Hastarin kernels were still the best for SD roms & I would have to agree, but they still lag a bit as well.
Ironically, the fastest Android build I've tried so far, out of all of them, was one called Mdeejay FroYo Sense v.3.0a. It was Android 2.2.1 & came bundled with the hastarin r7.2 kernel. It worked perfectly from the beginning and never lagged. I originally found the rom here: http://www.jayceooi.com/2010/10/14/download-mdeejay-froyo-sense-2-2-1-frg83-android-rom-for-htc-hd2/
So, I thought what if I update my Boxmax rom with Hastarin 8.5.1 & then just replace the zImage file in my Android folder with the Hastarin 7.2 kernel from the Mdeejay installation package while in Windows Mobile. I know this isn't the right way to do it, but I wasn't sure how to make an update package for it, so I backed up my original configuration & gave it a shot.
Sure enough though, I powered on Android and the build was FLYING faster than any other Kernel I had previously installed & the Android software info was showing I had the Hastarin r7.2 kernel. However, everything seemed to be working perfectly except for the camera. It would open without error & seemingly had all the functionality, except there was no preview of the picture in the display & it wouldn't take a picture. If I didn't like taking pictures so much with my phone I would have just kept it, but alas I replaced it again with Hastarin 8.5.1. The camera works again now, but of course it's back to lagging again, even after reinstalling the whole rom.
Does anyone have any possible solutions to this by chance? Thank You In Advance For Any Help Or Advice You Can Give!!! Very much appreciated!
Related
Hi all,
I've got an HTC Magic from Rogers (EDI1 / 32A) and I've sucessfully loaded CyanogenMod on this unit. There are a few limitations with this ROM that I'd like to work around:
- No full exchange support
- Can't run other HTC apps like PDFViewer, teeter, etc...
Now from what I've read the HTC / Google stuff had to be stripped to avoid copyright infringment and that's fine. I'm just figuring since this phone came with these features I should be able to extract them from the stock ROM and apply them over the CyanogenMod ROM myself? Afterall these were licensed to this piece of hardware right?!? ;-)
I've started to figure my way around both fastboot and adb so I restored my original ROM and started pulling the apk files from that. Started with teeter and PDFViewer as a start... When running on the CyanogenMod ROM Teeter exits gracefully with a message telling me it only runs on an HTC, and PDFViewer dies and needs to be force closed. So there's obviously more than just the apk files for these apps that need to be moved.
So does anyone know what files need to be pulled from the stock ROM and copied to the CyanogenMod ROM to allow me to run the HTC stuff on there?
Also if anyone can point me to the files I need to transfer to restore the full exchange functionality that would be sweet!
I know the files had to be pulled out / replaced to meet legal requirements so someone must know which ones they are?!?
Oh and one issue I've been running into is that I obviously can't get root on the stock ROM so things like the data directory are off limits to me... But the system folder's accessible in a read only mode at least.
I'm also wondering which files actually make up the Android OS? Maybe it would be easier just to copy the 1.6 os files to the 1.5 stock image leaving the rest the same? So in a nut-shell trying to do HTC / Rogers' job for them as they are obviously not looking to get this done any time soon if at all by the looks of things...
Any insight would be greatly appreciated!
Sandy
OK, here is the latest update. Instead of using kernel extracted from Rogers stock ROM, I compiled HTC kernel source downloaded from developer.htc.com.
To make touch screen work, one has to update sapphire_defconfig. Only one configuration has to be changed -- that is, to make the following unset.
#CONFIG_TOUCHSCREEN_CONCATENATE_REPORT=y
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Hopefully, the above information is useful. Wifi is fine. But, camera is not working.
==================================
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.
the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider
sharpt71 said:
Guys, help is needed here.
In the past two weeks, I tried to compile AOSP Froyo (branch 2.2_r1) with HTC kernel (2.6.29) extracted from Rogers stock ROM. The compilation went fine. Boot also went smoothly until it reaches the screen that requires users to enter PIN code. At the moment, I found that I CANNOT enter anything from screen. (touch screen is gone)
As far as I can tell from the android architecture, touch screen is something related to kernel, right? HTC kernel does support touch screen. So, I was lost???
I tried to read init.rc, init.sapphire.rc, and init.goldfish.rc, and system/etc/ files to see if I missed some configurations. But found nothing.
What should I do? Any help is appreciated.
Click to expand...
Click to collapse
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
In regards to the 3.5mm headphone jack version (also known as Fender or 1.2) it has slightly different hardware drivers that require the patch made by Voxluna. Most developers include this in their roms by default however if you are using any other source then odds are that they won't include the patch thus creating your problem.
capychimp said:
the driver in the kernel .29 do not fit the android 2.2 you need a different kernel, i got touchscreen by using the .34 kernel from froyorider
Click to expand...
Click to collapse
Since HTC source code was just released, will you please point me to the right files/folders so that I can find out the reasons why .29 does NOT work with Froyo?
I had once compiled AOSP Froyo with HTC kernel .27 by following instructions on http://www.lingnu.com/en/howto/72-android-aosp-htc-32a.html. Although camera (and maybe other devices) did not work, touch screen worked fine. Due to this experience and the limited reading of android architecture, I thought I could simply replace the kernel without affecting other layers. Hmm, to use layers design, why didn't google keep APIs intact?
Binary100100 said:
I bet that you have a MyTouch with a 3.5mm headphone jack huh?
If not then you need to include more information.
Click to expand...
Click to collapse
Sorry for not making this clean in the first place. Mine is a 32A which is running Rogers stock rom with root (made by capychimp) + chinese support + htc_cime (cooked by myself).
Ciompilation involved roughly the follwings:
1. AOSP froyo branch 2.2_r1
2. Comppilation of Froyo by following http://xy0811.spaces.live.com/blog/cns!F8AECD2A067A6B17!1526.entry?wa=wsignin1.0&sa=474748515 (which is similar to dferreira's howto)
3. unziped capy's Rogers_21_capychimp.zip instead of signed-google_ion-ota-14721.zip.
4. extracted kernel and wlan.ko from the boot.img in Rogers_21_capychimp.zip
the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.
carz12 said:
the source from htc is for sense roms, way different drivers. I have a perfect .34 kernel for froyo but no cam so far.
Click to expand...
Click to collapse
Thanks for the info. I just updated the current status at the 1st post.
From what I did, I kind of wondering whether or not the not-working camera problem is related to "configurations" because camera works on 2.1. But, I am not a kernel guy and will not be one.
sharpt71 said:
Then, compile kernel as usual and touch screen works with AOSP Froyo.
Click to expand...
Click to collapse
A screenshot of software information is attached. Oh, sdcard cannot be mounted unless it has no ext/swap partitions.
nice on the touch screen, will come in handy thx will try it on my wildfire port
Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.
Hello, I'm new to all this Android stuff (I don't even have a phone yet, but its on it way)
I have been reading up on custom ROM creation but there are some things I don't quite understand.
Let's say I have a phone in Android 2.3. I want to create an Android 4.0 ROM to put on the phone.
Now... to compile Android 4.0 I need the drivers for my phone (which I doubt I will ever have access too since its only a cheap Android with a MediaTek CPU)
So I have a 2.3 ROM that contains all the compiled drivers and the Android 4.0 source code.
Is it possible to compile 4.0 and replace the zImage (if I'm correct) with the 2.3 zImage. From what I have read, that's where all the drivers are stored.
I guess its not that simple since I also think the zImage contains the OS. If so, is it then possible to extract the zImage and replace the invalid driver files in 4.0 with the correct drivers from 2.3?
Also, I think my phone will arrive with an annoying UI, is it possible to just get any 2.3 ROM (that doesn't have an annoying UI and shares the same CPU as my phone) and replace the zImage in that with my phones 2.3 zImage?
Sorry, if my questions are stupid but this is all new to me. I've tryed to read up on this but nothing is straight to the point.
Thanks
Anyone there?
try out some roms first. see what you like and dont like. it'll probably give you a better idea for how you would make your own rom.
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Kailkti said:
I don't think you could just port an entire zimage to ICs and say it will work (it might not even compile i think). It won't work. You could probably take some drivers' code (screen, speaker, etc), modify them a bit so it compiles, and test to so if it works. You more than likely have to modify the ICS code also so it works. And the zimage is just the kernel no? And the kernel really only has to do with low level system processes, drivers, etc. I think UI's and such are more fitted in frameworks and such.
Personally if it was so easy to port ICS by simply replacing the zimage or file with another, ICS would have been ported to many devices, fully working, by now.
Click to expand...
Click to collapse
Yeh, but my problem is I don't have the drivers for the phone. I just have the stock ROM that come with it.
Is not that simple. I am 99% sure that you can't do that.
The phone I'm getting has a horrible theme on it. Its running Android 2.3
I have the ROM for a very similar phone (also using Android 2.3), uses the exact same CPU so it should be compiled using the correct platform.
Is it possible to use that phones ROM but replace it with my phones Kernel and .prop (so it has all my phones drivers and settings etc...)?
the hard work required in making a custom rom
I think you can take from the stock rom and compared with existing custom rom
but some sources are not shared freely as an example Tegra
CMIIW
I will mess about with the ROM when I get my phone. Hopefully I wont brick it...
I too am fairly new to android. I spent a couple weeks reading and watching TONS of youtube videos on how to ROOT and Unlock my bootloader. My best advice from one n00b to another would be to do the same. In particular...research how to do it on YOUR phone. Also, Roms are device specific. I recommend you finding the forum here on XDA for your phone and read up on whatever ROMS are available here. This might not be the ONLY place to find ROMS, but this place simply rocks! Once you get your device rooted and if necessary, your bootloader unlocked...you can easily try out any ROM without much fear. Just make a good backup...make sure you also have a factory recovery image too...just in case. For backups...if you install and use Clockwork Mod (CWM) you can use the nandroid backup it offers. I bought Titanium backup from the market and used it to do a full backup before I started...it backs up to dropbox even, which was a nice feature for me. Extra safety so incase I hosed my external SD card which had my backups...I could easily retrieve a backup ANY place that had internet access. Lastly...get ready to have some FUN! Flashing ROMs is VERY addictive!! :-D
Ok, Thanks. I will see what I can do then.
Hey all, buying an XT720 today.
Looking to get it up from 2.1
What is the most stable update at the moment?
I have done CM 6.1 on a HTC Dream, was pretty happy with it.. would like to get up to 2.3 on this..
Suggestions? I am using Wind Mobile in Canada for this phone if it makes a difference.
James
Hi
Their are choices cm6 is very stable
I would try flfalcon cm7.
Their are J.Y.Daddy cm7 these were made for the motorio to use these you would need to apply bootfix.
J.Y.Daddy even ported miui ics 4.01.
You need check out the development page.
Sent from my XT720 using xda premium
I also have a list of most of the ROMs and their +/-'s. Ill find the link and post it. I'm mobile now so can't find it that way.
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Here is a somewhat dated list but a list nonetheless and here is the thread it came from.
http://forum.xda-developers.com/showthread.php?t=1298208
Woodrube said:
There are a host or ROMs for this phone right now and it is quite hard to narrow down to "The Best". Each as their own +/-'s and while one might be a monster in speed, it might have poor muti-tasking or bad camera. Here are some of the ROMs we have and some of the +/-'s they have (not all, just some +/-'s).
In no particular order other than the top came out first and bottom is the latest.
2.1 Stock - Came with the phone. You can falsh via RSDlite the sbf file for your region.
2.1 Stock~ESB (Eclair Strikes Back) - Same as above, but has aorking app2ext, camera, FM Radio. Still it is 2.1
Dexters 2.2 with MZ patch - First successful attempt to port 2.2 to our phones. All features of 2.2 but camera is sketch and FM radio doesn't work (unless you apply FJfalcon radio patch but then it is still loud), media button doesn't work.
Kahlpower's V2/3/4 - Optimized version of Dexters. Same issues as above but is more stable and generally was the choice as a "home" ROM for many users. I have my wife on this one as we speak. Low maintenance, a good everyday driver. Has App2ext/ Link2sd, native Froyo App2sd.
Cincinnati Bell's "official" 2.2 - More or less a glorified version of Dexters 2.2 but I think the Mioz7AE found a "listening" script that may or may not send info back to developer. I would stay away from this one. Plenty more to choose from.
Wanhu 2.2 (also Wanhu's Kahl's Optimized) - Korean port of 2.2. FM radio and camera does work. Number formatting is off. App2ext works fine as does native Froyo app2sd.
XDA Special/ Hellmonger Edition - This was moveing really well and then Hellmonger's phone crapped out on him and his carrier gave him an HTC Penache, so no more support for this one. But is DOES work and worth a try.
CM6 - our developer Mioze7Ae's masterpiece (for now until he moves on to something else) All the features of CM6, including themer. Has App2ext and Link2sd.
WIPs
Brianlili's Brovo 2.2 - This one is almost done, jsut a few little thing to finish it off.
JYDaddy's CM7 (nightly/ HoNo/ iceandfire...)
FJfalcon's CM7.1 (make massive progress daily on this one as it is being built from source).
Like I said there are +/-'s to each but the are all spelled out for you in the OP of each thread. Plus, unlike other phone forums, we actually answer your questions and dont respond with, "search".
Good luck and remember to always BACK UP.
Click to expand...
Click to collapse
S7icky said:
Im on wind also and i truthfully find bravo the best.... everything is really stable and HD cam and whatnot works
Click to expand...
Click to collapse
Where is this Bravo??
Also I have rooted..
but I have not found a good guide on Openrecovery. (EDIT) got this done, went through ADB shell.
I unzip the the openrecovery to the sd card.. gives me openrecovery.zip a directory and an images directory.
SO then to flash a new rom I just put the .zip file in the updates directory.. and bingo bongo?
Going to try Cyanogenmod 7.1 first.. not sure where to find the brovo? bravo? mentioned.
James
Custom Recovery is here
http://forum.xda-developers.com/showthread.php?t=1242259
Bravo is here
http://forum.xda-developers.com/showthread.php?t=1332410
All ROMs and Mods are in the Dev thread.
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
AllGamer said:
I vote for CM6 RC3 / RC4
it's by far the most stable & fast which allows you to run most resources intensive games
Click to expand...
Click to collapse
I might give this a try next.. I have bravo tweeked out.. and I like it for the most part.. but there are somethings that dont seem to work as well as my G1.
I will just save my current phone in nand and then I can just reload it all back in - correct??
James
Yes
10chars
this one fjfalcon's CM7 , http://forum.xda-developers.com/showthread.php?t=1350453
Nandroid and battery
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Well if its Rooted, then you should have Open Recovery on it.
When you boot the phone hold VOL up and it will boot in OR...
or when you power off.. it should give you the option to reboot into RECOVERY.
There are lots of threads on here about OR .. but if you follow the menus you should be fine.. on an XT720 you push the camera button (big one) to accept a selection in the OR menu.
You can back up - which will save EVERYTHING.. a Nandroid backup is the best thing to store away somewhere should you mess up your phone.
YES you will have to loose everything when switching from 2.1 to (anything else)
If you are just updating to a newer build of something you put on.. then no.
You do the RESET and clear caches etc.. in OR.
Do a search its all on here .. usually the first page of whatever rom you want to TRY.
Have fun.
James
Thanks for the reply, time to install some rom's
Hilarious...after wading thru a few hundred pages of replies on this phone and the various roms, I completely missed your thread here James which is about as close to what I'm trying to accomplish as imaginable..
I posted some of my saga over here: http://forum.xda-developers.com/showthread.php?t=1399242
Do you mind me asking James/BikerBob...how did you make out? Anything I should know (if you have a sec read my long winded post lol!)
Did you have 3G/Wifi switching issues with stock, or maybe you didn't bother testing that / noticed it..before rooting I mean..
thnks!
(don't know if mods merge threads in this forum but mine is probably a candidate! sorry!)
racer321 said:
I just bought an XT720 (Rooted and unlocked)
Is there any way to change the battery level increments from 10% to something more exact like 5% and how do we create a Nandroid back up?
I also want to install bravo2.2 do I need to do a factory reset before installing this rom?
I am running stock rom 2.1
Click to expand...
Click to collapse
No, kernal(maybe driver) can't support 5% or 1% percentage battery level.
OK, so I decided that changing the SD card to a class 10 might help app usage ..
I copied the old sd card to the new one.. and if I try and get into OR .. I get the exclimation mark in triangle instead of the OR logo.
What do I need to do to get back into OR? do I need to RE-Root?
James
If you don't have it already, grab Mioze's modded OR for the xt720 & follow the instructions. If that's all you did was to switch sdcards there should be no need to redo everything.
Sorry, never mind the OR issue, my bad.
I have played with this too much.. lol.. get things mixed up..
I had the OpenRecovery.zip from one version mixed with the directory of the other..
Jezz
OR runs from the files on the sdcard (the openrecovery folder & openrecovery.zip) if something is corrupted (or missing) you wont be able to boot into OR.