Any one here port this rom cm 2.3.8 - myTouch 4G Q&A, Help & Troubleshooting
forum.xda-developers.com/showthread.php?t=2101999
Like ics rom look.
Sent from my HTC Glacier using xda app-developers app
http://cyanmobile.github.com/
Fairly easy to port give it a try its GB easiest ports ever
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
http://cyanmobile.github.com/
Fairly easy to port give it a try its GB easiest ports ever
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
I dont know, how they do it? can you build it?
This looks kinda cool for our device new features in GB. Wish I had time to build it.
can you build it?
Sent from my HTC Glacier using xda app-developers app
I will port it at morning
Sent from my myTouch 4g using xda premium
coderzs said:
I will port it at morning
Sent from my myTouch 4g using xda premium
Click to expand...
Click to collapse
Great... you are the best.
Sent from my HTC Glacier using xda app-developers app
I'm going to compile this for myself and see if I can get it to work. I got everything going just got to wait to see if the zip file I end up with works lol wish me luck.
Dragonswithin said:
I'm going to compile this for myself and see if I can get it to work. I got everything going just got to wait to see if the zip file I end up with works lol wish me luck.
Click to expand...
Click to collapse
Goooooood luck
Sent from my HTC Glacier using xda app-developers app
Bad news got an error near the end. Don't have time to try again hope someone else can get it.
This is the last part I get when it fails I sure would like to fix it but well I'm not that good. Anyone able to help out here?
Code:
target StaticExecutable: recovery (/home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery)
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/recovery/ui.c:403: error: undefined reference to 'get_menu_icon_info'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/recovery/ui.c:403: error: undefined reference to 'get_menu_icon_info'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/recovery/ui.c:403: error: undefined reference to 'get_menu_icon_info'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function device_handle_mouse:bootable/recovery/ui.c:403: error: undefined reference to 'get_menu_icon_info'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_wait_key:bootable/recovery/ui.c:928: error: undefined reference to 'TOUCH_CONTROL_DEBUG'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function ui_handle_mouse_input:bootable/recovery/ui.c:481: error: undefined reference to 'TOUCH_CONTROL_DEBUG'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/recovery/ui.c:556: error: undefined reference to 'MT_X'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/ui.o: in function input_thread:bootable/recovery/ui.c:558: error: undefined reference to 'MT_Y'
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/../../../../arm-eabi/bin/ld: /home/ken/android/source/out/target/product/glacier/obj/STATIC_LIBRARIES/libbusybox_intermediates/libbusybox.a(mktemp.o): in function mktemp_main:external/busybox/debianutils/mktemp.c:94: warning: warning: tempnam() possibly used unsafely; consider using mkstemp()
collect2: ld returned 1 exit status
make: *** [/home/ken/android/source/out/target/product/glacier/obj/EXECUTABLES/recovery_intermediates/LINKED/recovery] Error 1
make: *** Waiting for unfinished jobs....
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
How are you compiling it for the Glacier? You have to compile it and then port it. Not possible to compile it when its not supported.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
How are you compiling it for the Glacier? You have to compile it and then port it. Not possible to compile it when its not supported.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
I'm just using the how to port from the site you linked. And I compiled the kernel from CM 7.2 I trust you that what I was doing is not going to work. I'm just messing around to see how this works and I would really love to see this ROM on our device.
Port it from this one.
http://forum.xda-developers.com/showthread.php?t=2032685
http://github.com/TaichiN/Crespo-ROM
Sent from my HTC One S using Tapatalk 2
Don't have a time ... Sorry (((
Sent from my MyTouch 4G using xda premium
Gave this a shot but must have done something wrong in the port because it will not boot. Just stuck on splash screen. And I'm out of time as well :'(
No builders...
Sent from my HTC Glacier using xda app-developers app
vidura1991 said:
No builders...
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
If the wife would leave me alone I could keep working on it but I don't think that is going to happen,
Dragonswithin said:
If the wife would leave me alone I could keep working on it but I don't think that is going to happen,
Click to expand...
Click to collapse
Break her off a couple of times and get back to it while she recovers?
Ill take a crack at it today hopefully successfully
Sent from my HTC Glacier using xda premium
Related
quick question
I've ported a rom from the cdma hero to Eris using the kitchen at grd website, but when I try to flash it it says failure at line 2. how would I fix this failure. thanks for ur future help Sent from my T-Mobile myTouch 3G Slide using the XDA mobile application powered by Tapatalk
T.C.P said: I've ported a rom from the cdma hero to Eris using the kitchen at grd website, but when I try to flash it it says failure at line 2. how would I fix this failure. thanks for ur future help Sent from my T-Mobile myTouch 3G Slide using the XDA mobile application powered by Tapatalk Click to expand... Click to collapse I think you might have missed the update script. Go into meta inf and open up update script using a texteditor and change the device name in "" to "desirec"
Spencer_Moore said: I think you might have missed the update script. Go into meta inf and open up update script using a texteditor and change the device name in "" to "desirec" Click to expand... Click to collapse ok thank you will try that right now
In app billing
I'm trying to code the dungeon in app. The issue I'm having in eclipse. Imarketbillingservice.stub cannot be resolved. Are there any fixes. None of the quick fixes work. I was able to copy the aidl file correctly into correct directory. Thanks. Sent from my SAMSUNG-SGH-I997 using xda premium
mulcahyd said: I'm trying to code the dungeon in app. The issue I'm having in eclipse. Imarketbillingservice.stub cannot be resolved. Are there any fixes. None of the quick fixes work. I was able to copy the aidl file correctly into correct directory. Thanks. Sent from my SAMSUNG-SGH-I997 using xda premium Click to expand... Click to collapse Also I'm getting this too asinterface(ibinder) is undefined for the object
[Q] need help in cooking custom rom
hello i have been trying to build a custom rom for my phone usually i am able to pass installation phase in recovery mainly on sense base rom(i think it pure luck) but always have problem when rom boots up and start up phase come. But now i was trying to add my own flavor to miui rom but always end up with this massage :- EEROR 6 can anyone tell me what i am doing wrong and solution to remove this error??????? i am one big idiot nooooooob
Error 6 is a tough one. Its probably your updater-script. One single out of place character or space and you will get an error 6. Did you edit the updater-script after ROM kitchen generated it?
I think I have Thanks Its working thanks again Sent from my HTC Glacier using xda premium
Awesome! What fixed it? Sent from my HTC Glacier using XDA App
estallings15 said: Awesome! What fixed it? Sent from my HTC Glacier using XDA App Click to expand... Click to collapse I started again from scratch I did not make much changes this time just added some apps, new themes, bootanimation and boot audio I am still a noob and learning thanks for help Error 6 problem was because I think I replace updater -script with update - script when creating the update.zip Sent from my HTC Glacier using xda premium
Ah, it happens Hate it when I do that though xD Sent from my Infernalized Glacier! -Team Inferno
It really is a pain especially when working with a customized updater-script with ascii art and stuff
Yes u both r right me too hate it now lol Sent from my HTC Glacier using xda premium
[APP] HTC Quick Root - Root ANY HTC Device!
Building on the Framework of my other apps, I present to you my easy, quick and efficient Rooting solution for ANY HTC Device. Check out the link for more info and Download: http://forum.xda-developers.com/showthread.php?t=1870652 Sent from my HTC Desire S using Tapatalk 2
Going to check this out. Thanks
I wonder if,this would solve my issue.... Thank u!, gonna try it later. Sent from my PG06100 using xda app-developers app
Does "any HTC device" include the Incredible 4G? We are having a lot of trouble with that one... Could use some help. Sent from my ADR6410LVW using xda app-developers app
CaptainRewind said: Does "any HTC device" include the Incredible 4G? We are having a lot of trouble with that one... Could use some help. Sent from my ADR6410LVW using xda app-developers app Click to expand... Click to collapse As long as the exploit has not been patched by HTC then it will work otherwise you need to dev-unlock and flash insecure boot.img then run HTC Quick Root. Sent from my HTC Desire S using Tapatalk 2
lyriquidperfection said: As long as the exploit has not been patched by HTC then it will work otherwise you need to dev-unlock and flash insecure boot.img then run HTC Quick Root. Sent from my HTC Desire S using Tapatalk 2 Click to expand... Click to collapse The Incredible 4G is locked up tight. We can't get root via any exploit, and dev unlock was only available for a short time after release, then was removed. Nobody can get s-off, either. I bought mine thinking dev unlock still worked, then found out that it was revoked the very next day. Needless to say we need help rooting. Thanks for the effort, though. If you have any ideas on the Incredible 4G, please share on the threads over there. We really need help. Sent from my ADR6410LVW using xda app-developers app
I share your pain Captain. Stuck with the Inc4G myself with no s-off. Got it locked down tight, really missing my shift right about now
Doesn't work for the latest OTA of Evo Shift 4G. =/ There is a chance I might have done something wrong, but I have continuously tried different ways so I highly doubt it.
[Calling All Developers] CyanogenMod 11 BringUp for HTC Desire 816
Hello All, I have been working CyanogenMod bring up for Desire 816 since a few weeks now. Currently, I have prepared the device tree and the vendor tree that I guess should be enough to get it booted(Or bootloop atleast ), except one thing - > I'm having troubles implementing dt.img in the device tree to use with kernel/recovery and I did used the flag to use the dtb but, when I tested it with recovery, it got stuck on "Entering Recovery" screen for a few seconds and then rebooting and I'm pretty sure that it'd be a single silly mistake stopping from it to boot. And if recovery boots, theb most probably kernel boots(Using a prebuilt one) amd therefore increasing the chances for the ROM to boot! EDIT - We are using prebuilts but we got recovery to boot. Here are the latest trees - https://github.com/desire816-dev
Great... Im no developer but..... Thanks for ur efforts.. And all the best for further development... Sent from my HTC Desire 816 dual sim using XDA Free mobile app
Not sure, but I think you are using the wrong recovery fstab style. This is the cm 10.1 style, not cm 11 It needs to looks somewhat more like this You don't have the kernel source, right?
dummie999 said: Not sure, but I think you are using the wrong recovery fstab style. This is the cm 10.1 style, not cm 11 It needs to looks somewhat more like this You don't have the kernel source, right? Click to expand... Click to collapse This is the fstab that my boardconfig links to - https://github.com/v-superuser/android_device_htc_a5dwg/blob/cm-11.0/rootdir/etc/fstab.qcom The other one's useless. Sent from my HTC Desire 816 dual sim using Tapatalk
My mistake. Try tearing apart your current recovery and check for differences.
Make sure you have the correct offsets for the ramdisk and devtree image https://github.com/JackpotClavin/an...72f80986171c7e401528457942/BoardConfig.mk#L34
JackpotClavin said: Make sure you have the correct offsets for the ramdisk and devtree image https://github.com/JackpotClavin/an...72f80986171c7e401528457942/BoardConfig.mk#L34 Click to expand... Click to collapse Sorry for a late reply but, ramdisk offset and other stuff is right. Must be something else. Wondering why @kinghunki doesn't shares his trees.
View /proc/last_msg after it reboots Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said: View /proc/last_msg after it reboots Sent from my LG-VS980 using XDA Free mobile app Click to expand... Click to collapse Here is the last_kmsg - https://www.mediafire.com/?m2h8f54qbic6llz
That doesn't look like the last kmsg of the failed boot Sent from my LG-VS980 using XDA Free mobile app
JackpotClavin said: That doesn't look like the last kmsg of the failed boot Sent from my LG-VS980 using XDA Free mobile app Click to expand... Click to collapse IDK, I flashed recovery, it got stuck on Entering Recovery, rebooted, and I pulled the last_kmsg just after it rebooted to system.
Okay then it seems that the kernel never booted far enough to initialize the ram console. I'd double check your devtree offsets. Sent from my LG-VS980 using XDA Free mobile app
i will pm Grarak he is great developer maybe he can help you
Is the kernel source already available? If yes please upload it to github Can anyone send me stock boot.img? Sent from my GT-I9205 using XDA Free mobile app
Grarak said: Is the kernel source already available? If yes please upload it to github Can anyone send me stock boot.img? Sent from my GT-I9205 using XDA Free mobile app Click to expand... Click to collapse There's no kernel source yet. Here's the stock boot.img http://www.androidfilehost.com/?fid=23501681358558515 !
you don't have any devtree offset, that's your problem should be: BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02008000 --dt device/htc/htc_a5dwg/prebuilt/dt.img --tags_offset 0x01e00000
JackpotClavin said: you don't have any devtree offset, that's your problem should be: BOARD_MKBOOTIMG_ARGS := --ramdisk_offset 0x02008000 --dt device/htc/htc_a5dwg/prebuilt/dt.img --tags_offset 0x01e00000 Click to expand... Click to collapse Oh, well, I'll check and post. Thanks a lot. Sent from my HTC Desire 816 dual sim using Tapatalk
I just forked your tree https://github.com/Grarak/android_device_htc_a5dwg You really need a clean up Almost all files are useless and you should also use 8960-common tree I will send you some pull request or you can just pick my commits if you want
Grarak said: I just forked your tree https://github.com/Grarak/android_device_htc_a5dwg You really need a clean up Almost all files are useless and you should also use 8960-common tree I will send you some pull request or you can just pick my commits if you want Click to expand... Click to collapse The device uses MSM8226 chipset! Thanks for your efforts.
v_superuser said: The device uses MSM8226 chipset! Thanks for your efforts. Click to expand... Click to collapse Yes I know But I checked other htc snapdragon 400 (actually only found htc one mini msm8930) they use msm8960 common tree But I guess you're right I will try to put everything in one single tree Sent from my GT-I9205 using XDA Free mobile app