Welcome happy campers
Here is a fully working pretty much fully tested port of Clockwork Mod Recovery 6.0.3.0
Big thanks to UTKANOS at #cyanogenmod irc channel for his help in building this for me to test till everything was working
FEATURES
All features in 6.0.3.0 based CWM recoveries are implemented
Touch screen working
Restore/Backup functions
All wipe functions
All Mount functions
Install from sd and Internal storage
Generally all features you expect from working ClockWorkMod recovery
without further ado here is the link to the recovery image: http://d-h.st/nMv
md5 Checksum : 8f7dda170425218f47717a9c9c931bea
source code at utkanos' github: https://github.com/utkanos/android_device_htc_golfu
Thanks goes out to mmmcfc for his initial work on the recovery we worked on to bring you this version, his original thread at :
http://forum.xda-developers.com/showthread.php?t=1785010
to install recovery is same as always for people who already know
for those of you who are new to this and do not know but are at the point of installing a custom recovery through a rom install guide please simply turn off your Desire C device, drop out the battery just in case fastboot is on in your rom settings, replace your battery then hold the volume down key and hold power button till you boot to bootloader.
Ensure phone is on fastboot setting (will have fastboot written in red if you are) plug in the usb cable and it should say fastboot usb now then enter this command from terminal window that is in the directory where you have this image downloaded to
Code:
fastboot flash recovery recovery-clockwork-6.0.3.0-golfu.img
with any joy you should now be able to reap the benefits of touch screen enabled up to date CWM recovery
enjoy
p.s. if you have issues installing this or do not know what our doing either do not install OR search the forums for root guide and recovery install guides and if you cannot find something relevant feel free to pm me
dont forget to come to our irc channel at irc.freenode.net ##HTCDesireCcm9 (dont forget to put two hash signs not one) we are friendly in the channel and are hoping it will begin to grow alongside development for the device
thanks
soon to come wifi fix for CM9, hopefully soon CM10 build and with all the fixes no doubt many custom roms from many users throughout our device section
Reserved this for maybe other information etc...
russell664 said:
Reserved this for maybe other information etc...
Click to expand...
Click to collapse
this is why we get along so well lol, albeit you do take forever to respond to irc chat but hey no one is perfect....
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
nikhil16242 said:
Great job :good:. Reboot is definetly fixed. Btw are you sure that device tree is updated with all the changes? I tried to build TWRP with that exact tree and still seem to have reboots.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
mehmehmen said:
Not totally sure dude about your question as this was actually built by utkanos with no device with me and russell testing the builds as they were made till we had it working with no reboots and with fully accessing adb rights when in recovery. i had massive issues when using th TWRP recovery that was posted so it may be TWRP specific that your issues lie. the source code is all available at utkanos github linked in the OP so you can surely tell from that if device tree is correct. if not maybe try to rebuild the trees. i myself have little experience in these matter XD
Click to expand...
Click to collapse
Ahh ok Np . Anyway.. good to have a recovery that doesn't reboot itself :thumbup:
Sent from my Nexus 4 using xda premium
A damn of a recovery, great work and thank your for this. Keep up the good work. Thank you again.
Thank u for this ,and thank u for keeping this phone alive , gl on ur cm work guys
Sent from my HTC Desire C using xda app-developers app
no worries guys, amazing to have 200+ views and what 4 users post in the thread lol all thanks is aimed to utkanos for his work making it happen, and mmmcfc for his original version build we worked on. i just tested and provided needed files to utkanos. all thanks is more than appreciated as we spent a whole day pretty much fixing the bloody thing
By the way, we should contact the guys from CWM to get official support like nikihil did.
TheRedHunter said:
By the way, we should contact the guys from CWM to get official support like nikihil did.
Click to expand...
Click to collapse
you need to shoot a mail to koush to get rom manager or cwm support.
Finally a non-rebooting recovery!! Thanks! :good:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
mehmehmen said:
your welcome, cant believe there wasnt one for so long, i only got the device around a month ago and found the xda development section lacking in a few areas im not used to seeing and so worked with a cm dev on getting the recovery up to date and stable
any thanks you guys want to click my way are welcomed and would be nice, amazing that over in my general section post to this thread there is a total of maybe 3 thanks per nearly 2,500 visitors to the link
now thats appreciation for ya
Click to expand...
Click to collapse
You are a great man, and your work is very appreciated. You have my thanks and I'll try to add as many thanks to you as I can.
I've shot you a few thanks as it's a damn fine cause, even if I strongly dislike cwm. I am afraid I am a Twerp through and through.
Ps I will try and get some extra thanks to you Redhunter as you are such a generous guy with your thanks and you always are upbeat and positive. It's good to see, thank you.
All the best rich
Sent from my Nexus 7 using xda premium
Dead link?
The download link to dev hub seems to be dead/broken ... is it just me?!?
AirCombat said:
The download link to dev hub seems to be dead/broken ... is it just me?!?
Click to expand...
Click to collapse
It works for me
calinorg said:
Just one question, am i blind, or this one has no clean battery stats?
Is it really needed, and is there a workaround (which file to delete)?
Click to expand...
Click to collapse
my ? too.i just updated to current version,and browsing around i noticed it is not there??
Can u make this in colours of mujenu touch recovery and create a guide for building recoveries
Sent from my HTC Desire C using xda app-developers app
Related
Mod Edit: Per Kraizk, please carefully read the thread & all posts. Not all links are updated & flashing the incorrect file may cause issues. The items posted in here are generally for advanced users or those knowledgeable enough to contribute to the project. I am in no way dissuading you from trying something new, just asking you to be thorough & certain about what you are downloading. Some links may be outdated, incomplete or outdated builds
This is a new dev chat area for my ICS builds. I finally have power, so am back to work on these builds all day today. I will be uploading each new testing build without updating this thread, so it's imperative you check the upload time on mediafire.
At the end of each build day I will be renaming the most stable/functional build as the beta for the day, or uploading an older build as the Beta for the day.
Some builds may not boot, may not have fully functioning cam, and may not have working cell due to attempting to get fully functional cell, and functioning mobile data. I'm also attempting to revert some very hacky workarounds and still maintain full functionality.
I'm not responsible for failure to read this, broken phones, or user error.
Install instructions:
-Flash ota zip in recovery
-Reboot to Fastboot, and flash boot.img
-YOU NEED THE NEW HBOOT!
If you don't know how to follow the instructions, then these testing builds are definitely not for you, and I would wait for the daily beta.
Download Testing Builds In the Test folders, boot.img will always upload before the ota zip, so please be patient.
Big Thanks and Credits: TwistedUmbrella, CM9 Team, TheCubed, TeamKang(AOKP Team), Evervolv Team, Cayniarb, Google, kevsthabest, IOMonster, DeamonFish for decoration and MisterSchnapps.
Holiday-Centric Github Page
I'm happy to do testing. What sort of reports are you after?
DallasJones said:
I'm happy to do testing. What sort of reports are you after?
Click to expand...
Click to collapse
Damn, you beat me to the second post! After logcats, or suggestions from dev minded folks really, but currently building test4 due to issues with test3(test3 is the current build up as labeled).
This just seemed like the most efficient way to continue moving forward, and then by the end of my build day there will be a stable/functional beta labeled as such for the less adventurous.
Excellent man!. I was wondering if you'd get this up before I returned from vacation.
Word to the wise, if you don't know what you're doing, stay away from here. This is a DEV AREA!
Please read and search before asking questions.
Reserved.
MisterSchnapps said:
Excellent man!. I was wondering if you'd get this up before I returned from vacation.
Sent from my HTC PH39100 using xda premium
Click to expand...
Click to collapse
Yeah! Test3 is quite broken actually, so working on Test4 also without using the prebuilt libril. If needed I'll revert to prebuilt by the time I need to upload a full beta.
Edit: And I need to learn to code more and build less. Was looking through the log, and realized I accidentally copied over something from the shooter that obviously won't work for us.
Any restrictions on the sub HW versions (eg Velocity, Vivid, etc)
jmone said:
Any restrictions on the sub HW versions (eg Velocity, Vivid, etc)
Click to expand...
Click to collapse
Once Test4 finishes building (if it boots), let me know! or just shoot me a logcat. I've only been able to test on vivid thus far. "adb logcat > logcattest.txt" is the command to run without the quotes to get a log sent to a text file (won't display anything while it's running), or copy past from adb logcat.
GOO-INSIDE.ME IS TAKING AGES TO UPDATE, SO I'M WORKING ON UPLOADING TO DROPBOX INSTEAD SINCE IT SEEMS TO UPDATE FASTER.
synergye said:
Damn, you beat me to the second post! After logcats, or suggestions from dev minded folks really, but currently building test4 due to issues with test3(test3 is the current build up as labeled).
This just seemed like the most efficient way to continue moving forward, and then by the end of my build day there will be a stable/functional beta labeled as such for the less adventurous.
Click to expand...
Click to collapse
Haha, sorry. Mods, feel free to delete my post. Looks like I signed into XDA at the wrong time
I've had quite a bit of experience with CM and what it's supposed to do. Just not the development side. I've got the Velocity 4G, so as long as I won't end up bricked I'll try anything you like. I'll have to wait until tonight to test though - gotta be careful downloading big files at work. Thanks for your hard work!
DallasJones said:
Haha, sorry. Mods, feel free to delete my post. Looks like I signed into XDA at the wrong time
I've had quite a bit of experience with CM and what it's supposed to do. Just not the development side. I've got the Velocity 4G, so as long as I won't end up bricked I'll try anything you like. I'll have to wait until tonight to test though - gotta be careful downloading big files at work. Thanks for your hard work!
Click to expand...
Click to collapse
If you're worried about bricking your device, then please don't test until I hear from someone else that the Velocity 4G is functional. Though it doubt it will occur, anything is possible, and I don't want to be blamed for anything.
synergye said:
If you're worried about bricking your device, then please don't test until I hear from someone else that the Velocity 4G is functional. Though it doubt it will occur, anything is possible, and I don't want to be blamed for anything.
Click to expand...
Click to collapse
I'm sure by the time work finishes in 8 hours, somebody will be here complaining that theirs is bricked if it's going to. Anyway, I'll stop clogging up your dev thread and do some work. Thanks again
DallasJones said:
I'm sure by the time work finishes in 8 hours, somebody will be here complaining that theirs is bricked if it's going to. Anyway, I'll stop clogging up your dev thread and do some work. Thanks again
Click to expand...
Click to collapse
Probably. Test3 didn't actually boot. Waiting for the mediafire verification on test3 to finish before I can upload test4...
Edit: Test4 uploaded. I need to run out for a few before I can test, but will be back in about half an hour.
synergye said:
Edit: And I need to learn to code more and build less.[/QUOTE
Take your time. Don't feel pressured to crank out builds. It's all about quality over quantity. lol
synergye said:
I accidentally copied over something from the shooter that obviously won't work for us.[/QUOTE
Was that an issue with Test3? Ha
Click to expand...
Click to collapse
Click to expand...
Click to collapse
synergye said:
Probably. Test3 didn't actually boot. Waiting for the mediafire verification on test3 to finish before I can upload test4...
Edit: Test4 uploaded. I need to run out for a few before I can test, but will be back in about half an hour.
Click to expand...
Click to collapse
I'll start testing
MisterSchnapps said:
synergye said:
Edit: And I need to learn to code more and build less.[/QUOTE
Take your time. Don't feel pressured to crank out builds. It's all about quality over quantity. lol
synergye said:
I accidentally copied over something from the shooter that obviously won't work for us.[/QUOTE
Was that an issue with Test3? Ha
Click to expand...
Click to collapse
Haha. Yeah. Threw in a 3d related graphics flag since we're no longer using custom graphics.
Sent from my Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IRC Channel to discuss findings?
i dont think beta4 boots up
come at me bro said:
i dont think beta4 boots up
Click to expand...
Click to collapse
I have also tried a couple of times with no luck
1987dram said:
I have also tried a couple of times with no luck
Click to expand...
Click to collapse
Same here
10char
haloXgod117 said:
Same here
10char
Click to expand...
Click to collapse
OK. I will get a logcat myself when I get back, taking a bit longer than expected. I said in OP quite a few of these won't boot, so please don't say a build doesnt boot without a logcat or anything helpful. That just takes up space.
Edit:grabbing dinner so will be a bit longer.
Sent from my Desire HD using XDA Premium HD app
synergye said:
OK. I will get a logcat myself when I get back, taking a bit longer than expected. I said in OP quite a few of these won't boot, so please don't say a build doesnt boot without a logcat or anything helpful. That just takes up space.
Edit:grabbing dinner so will be a bit longer.
Sent from my Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
honestly its not dumping for me its freezing up
Code:
C:\Users\steve\Desktop\adb>adb logcat > logcattest.txt
- waiting for device -
edit- it gave me this
http://depositfiles.com/files/zahajntzd
Update 2: You won't get a stable build from here, just treat this as a massive development thread now. Feel free to continue your great work.
Update: I have successfully built CyanogenMod 10 for you guys. I don't know if it'll boot or not, so please provide the logcat (adb logcat) and dmesg (adb shell dmesg)
You can download UNTESTED, EXPERIMENTAL builds here:
goo.im/devs/benjamingwynn/icong/CyanogenMod10
Original post: Feel free to discuss your thoughts on developing this for this device here, I don't have this device but I did say to BigBearEvo that I'll help him if I can. I will compile this ROM from source code.
I need help with this as I don't own the device (as I just said) but will make at least one build for it. I can't even promise this'll boot.
IF YOU WANT TO HELP MORE THEN PLEASE GATHER INFORMATION ABOUT YOUR DEVICE - TOUCHSCREEN TYPE, ETC IS HELPFUL. TELLING ME ITS A CERTAIN COLOUR ISNT!
Hope I'll get you folks a booting port soon.
- Benjamin
benjamingwynn said:
Feel free to discuss your thoughts on developing this for this device here, I don't have this device but I did say to BigBearEvo that I'll help him if I can. I will compile this ROM from source code.
I need help with this as I don't own the device (as I just said) but will make at least one build for it. I can't even promise this'll boot.
IF YOU WANT TO HELP MORE THEN PLEASE GATHER INFORMATION ABOUT YOUR DEVICE - TOUCHSCREEN TYPE, ETC IS HELPFUL. TELLING ME ITS A CERTAIN COLOUR ISNT!
Hope I'll get you folks a booting port soon.
- Benjamin
Click to expand...
Click to collapse
feel free. ill add it to the 2 that already boot up lol, i have been trying again with other kernels to experiment, all have failed again, most didn't boot, the one that did, again a non responsive screen same as others.
all I need is someone with some good knowledge of the kernel and tamper with it...
ill pull all the info i can from it.
BigBearEvo said:
feel free. ill add it to the 2 that already boot up lol, i have been trying again with other kernels to experiment, all have failed again, most didn't boot, the one that did, again a non responsive screen same as others.
all I need is someone with some good knowledge of the kernel and tamper with it...
ill pull all the info i can from it.
Click to expand...
Click to collapse
Hm, I'll boot into Linux and change some stuffs. I'm aiming to get jellybean running on this device.
Source: https://github.com/benjamingwynn/android_device_htc_icon_g
benjamingwynn said:
Hm, I'll boot into Linux and change some stuffs. I'm aiming to get jellybean running on this device.
Source: https://github.com/benjamingwynn/android_device_htc_icon_g
Click to expand...
Click to collapse
now that i would love to see.....basic cm7 would be nice too lol but maybe a tad outdated for you though lol
BigBearEvo said:
now that i would love to see.....basic cm7 would be nice too lol but maybe a tad outdated for you though lol
Click to expand...
Click to collapse
CM... 7?? lol, I think CM10 would run brilliantly on this device though I'll get CM10 working then work my way down lmao.
This is by far the best news ive read in this forum in a long time
I am also joining in this dev I'll help u BB
---------- Post added at 10:28 AM ---------- Previous post was at 10:26 AM ----------
The non booting kernels may have some library damage,which is associated with the screen
Second reason : in init.rc the bootclasspath must be changed it might be the link to an sense framework
---------- Post added at 10:40 AM ---------- Previous post was at 10:28 AM ----------
I saw ur github u can boot up but it would lag our touchscreens are weird to say
I think we could hack the chachas kernel tree, I'll contact Lucas now. I've worked with him on other projects for the chacha.
Sent from my Wildfire S A510e using xda app-developers app
benjamingwynn said:
I think we could hack the chachas kernel tree, I'll contact Lucas now. I've worked with him on other projects for the chacha.
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
BTW chachas screen resolution is half of ours and has a hardware keyboard"can remove the ime part"
I was gping to look into using the chacha kernel and other bits to see if it will boot. Just haven'thad tthe time yet.
BigBear is using Xparent Tapatalk Purple
BigBearEvo said:
I was gping to look into using the chacha kernel and other bits to see if it will boot. Just haven'thad tthe time yet.
BigBear is using Xparent Tapatalk Purple
Click to expand...
Click to collapse
Gwynn and bb why u guys ignore me
Sent from my HTC One X using xda app-developers app
Lol I'm not ignoring anybody
@BB well done on your RC status
I'm going to work on the device tree, if you folks know how to use github feel free to contribute stuffs as I can shift the stuff over to an organisation or just give you write permissions.
benjamingwynn said:
Lol I'm not ignoring anybody
@BB well done on your RC status
I'm going to work on the device tree, if you folks know how to use github feel free to contribute stuffs as I can shift the stuff over to an organisation or just give you write permissions.
Click to expand...
Click to collapse
currently i don't have a working Ubuntu.
My HDD crashed proper, lost it all lol.
Awaiting a new larger drive lol
other than that i can always send u what's required anyway lmao.
TY...im chuffed! :laugh:
@BB or whoever, you can find touchscreen stuff in the kernel.
benjamingwynn said:
@BB or whoever, you can find touchscreen stuff in the kernel.
Click to expand...
Click to collapse
nps will look into asap
I'll also need a user to run the following command with their device plugged in:
Code:
adb shell df -a
benjamingwynn said:
I'll also need a user to run the following command with their device plugged in:
Code:
adb shell df -a
Click to expand...
Click to collapse
that cmd gives me -a no such file or directory
but remove the -a and i get a whole list, will mail it you
....................................................................................................................................
mailed
Okay, I'm going to compile this and go to Judo because I can.
When I get back you might/might not see a build uploaded. If you don't then don't blame me.
but if you do then please do the following:
0) Set up ADB on your computer and backup stuff
1) Download it
2) Clear data as normal
3) Install it via Clockworkmod recovery (if possible)
4) Run the following...
adb dmesg > dmesg.txt
adb logcat > logcat.txt
at the same time to log everything your phone does.
Once this is done, please use logcat.miui.us, pastie.org or pastebin.com to report all the logs so I can read them later.
If it boots, screen cap it along with everything that's working. Please also include the recovery version you used too.
Click to expand...
Click to collapse
benjamingwynn said:
Okay, I'm going to compile this and go to Judo because I can.
When I get back you might/might not see a build uploaded. If you don't then don't blame me.
but if you do then please do the following:
Click to expand...
Click to collapse
tisnt there lol, but will wait for you laddie!
BigBearEvo said:
tisnt there lol, but will wait for you laddie!
Click to expand...
Click to collapse
Lol, its not there because repo was all being stubborn not syncing
Sent from my Wildfire S A510e using xda app-developers app
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Working:
Touch screen
ADB
Browser (Although no net access yet)
You can browse and get a feel of the entire OS, including the homescreen (unity desktop), multitasking (the cool new way to switch between apps), etc.
Since it is a preview, many apps are dummy apps.
Screenshots:
Check them out here
Video:
Here is a video of the fresh new OS in action on the O2x made by JordanRulz
Download links:
Ubuntu touch preview (raring ringtail)
Current build of Ubuntu-CM10.1 (old bootloader)
New bootloader build by delaya73:
cm-10.1-20130604-UNOFFICIAL-p990.zip
Older Ubuntu phone quantal image
older build 2 of Ubuntu-CM10.1 by delaya73
older build 1 of Ubuntu-CM10.1 by delaya73 for the new bootloader
TWRP latest version is recommended (CWM 6.x may work too)
Note:
The raring/quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
Source:
Ubuntu-cm10 source
Building instructions:
Building instructions are similar to building CM10 (refer Raum's guide) till repo sync (instead of official cm10 repo, use above source during repo init)
Dont forget to add device props in "local_manifests" (local_manifest.xml is deprecated). Add the following in local_manifests:
Code:
(Taken from Raum's guide, thanks to him)
After syncing the repo,
1. cd device/lge/p990, connect your device running cm10.1 with usb debugging on, and then ./extract-files.sh
2. In device/lge/p990/fstab.p990, remove "nosuid" from data partition
3. In kernel/lge/star/arch/arm/configs, in cyanogenmod_p990_defconfig, add the following:
Code:
CONFIG_SYSVIPC=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVTMPFS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_FSNOTIFY=y
CONFIG_SWAP=y
# CONFIG_ANDROID_PARANOID_NETWORK is not set
4. Go to ubuntu folder inside your source folder and do
Code:
bzr branch lp:phablet-extras/libhybris hybris
bzr branch lp:platform-api platform-api
If you didnt have bzr, get it first using
Code:
sudo apt-get install bzr
Now you can build. This build would be for the old bootloader. For the new one, make these changes said by pengus77 here
Flashing instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build and raring/quantal image
Then flash this afterflash.zip
3. Reboot
Credits:
Ubuntu dev team (Canonical)
Ricardo and the rest of the CM team
delaya73 for the new bootloader build
pengus77 for bringing cm10 to the new bootloader
Adam77Root for helping find the missing components stopping it from booting
All other contributors
AW: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
You rock man!
Gesendet von meinem LGP990 mit CM10.
Good luck with your job, Buddy, and Congratulations for all your interest/performance for our machines!
Regards.:good:
Thnx, I downloading, after a try, I will post some feedback
R: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Can i have some screenshot?
Sent from my LG-P990 using xda app-developers app
rugglez said:
"...If you think you can contribute, please do so ..."
Click to expand...
Click to collapse
I have not had time to install this ROM ... I have been testing other, but lack little longer to do so!
Once you have news post here the results.
Thank you all for the effort made
Thank you man you're doing a really good job
Very good job rugglez bro. cant wait for bootable version to test it on my self
Well, I tried to make some tests to see if he could complete the boot ... unfortunately without success after six or seven attempts.
Enough for today testing, hahahaha! ...
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
rugglez said:
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
For now, this is only for the new bootloader. If the project is successful, it would be made available on the old one as well
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Does not complete the boot yet
Download links:
Current build of Ubuntu-CM10.1
Ubuntu kernel for O2x
Ubuntu phone quantal image
TWRP latest version is recommended (CWM 6.x may work too)
Instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build, Ubuntu_kernel and quantal image
3. Reboot
Note:
The quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
To do:
There is no "logcat" in Ubuntu (may be some other way to debug), so need another way to look at what is preventing the boot
Credits:
Ubuntu dev team (Canonical)
CM team
All other contributors
Click to expand...
Click to collapse
have u tried dmsg/kmsg?
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
JordanRulz said:
have u tried dmsg/kmsg?
Click to expand...
Click to collapse
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
FettleifIsMyUserName said:
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Click to expand...
Click to collapse
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
Neefy said:
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Jishnu Sur said:
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
Click to expand...
Click to collapse
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
After watching some vids about this OS, it trully have a great potential. gonna watch this thread closely for progress
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
rugglez said:
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
Nice to know that the team is joining up and viewing to do great things
Great going guys
O2X with Magical ICS ROM and magnificent kernels from my buddies
rugglez said:
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
M always ready!!!!!!!!! =D
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
......and so on...!...
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
Ricardo is always a name in every project of the O2x, and he is a part of the CM team, in case you didnt know
But thanks for the reminder, I explicitly specified his name too now, deserves so much credit for bringing CM10 to our device.
Tonyp is a great contributor and we are thankful for all his work. But this is a ROM, and TWRP is a recovery used to flash a ROM, they have non-overlapping work. What I mean is, this ROM doesnt use TWRP's work, rather it can be flashed in TWRP or CWM6.
By your logic, Koushik Datta (developer of CWM and one of the best android devs) should be included in every ROM's credits here. Also, creators of USB, personal computers, internet, world wide web, which are also tools used in the process of flashing it.
(No offense meant to any of the above, they are all revolutionary people whom I greatly respect)
My point is, if I am using someone's work in this project/ROM, thats the person whose name goes in credits, not the one who is creating the tools to install it.
It's better if the discussion doesnt go further about this off-topic thing, if you find that I have used anyone's work in this ROM and not given credits, please let me know, thanks
Let's try to make Ubuntu Phone OS boot on our phone. Thats the priority here. Didn't get much time today, got college this week too, will see if I get time to work on it soon
THIS BUILD IS ONLY FOR PEOPLE WHO WAN'T TO POINT OUT BUGS AND OTHER ISSUES THAT I HAVE NOT MENTIONED PLEASE DON'T COMMENT AND SAY ZOMG WHY DOESN'T CALL WORK OR STUPID CRAP LIKE THAT! AGAIN TESTING ONLY!!
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
IMPORTANT INFORMATION
We'll not support users and answer questions from users which:
- are running a custom kernel
- have flashed mods
- modified system files
- didn't follow our intructions word by word
- are unfriendly
Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!
CHECK KNOWN ISSUES IN SECOND POST
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/
First time installing CyanogenMod 10.2 to your FIRST, or coming from another ROM:
- Read known issues ans FAQs
- Make sure you're running a proper working ClockworkMod-Recovery
- Copy GApps and CM10.2 ZIPs to your SDCard
- Boot into HBOOT (hold Volume Down at boot)
- Flash the boot.img
- Fastboot flash boot boot.img
- Reboot into recovery via the bootloader menu
- Flash CM10.2 zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
DOWNLOAD:
Google Apps:
http://goo.im/gapps
ClockworkMod Recovery:
If you're going to reuse our work, which we're doing for free, be fair and give proper credits.
This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.
Open-Source doesn't mean Out-of-Respect!!!
XDA:DevDB Information
CM 10.1 HTC FIRST, a ROM for the HTC First
Contributors
Lloir
ROM Firmware Required: A Brain
Based On: CyanogenMod
Version Information
Status: Testing
Created 2013-12-09
Last Updated 2013-12-28
At my discretion i may swap to CM10.1 to start with until i get my device (which should hopefully be soon)
THIS IS Work In Progress
NO ETA'S
NO ZOMG WHEN CAN WE HAZ THIZ
ANY OFF TOPIC WILL BE DEALT WITH BY THE MOD'S
NONE OF THAT CRAP
I do not tolerate fools lightly and i will berate you if you act like a complete idiot.
welcome to my thread
3rd
This is just awesome, installing now and will try to report logcats asap; It's really exciting to see a seriously minded dev on these boards. :victory:
just want to point out, this is a headstart for me, pending getting my device.
so as many logcats and kmsg's as possible. those are ULTRA important
Heh, well I might have the first brick. I couldn't boot past the Facebook logo and after reboot my charging indicator fails to show up.
this should be able to flash in twrp ? even though its 4.3 ? or should i switch over to cwm ? which is also outdated
SneakyGuyDavid said:
this should be able to flash in twrp ? even though its 4.3 ? or should i switch over to cwm ? which is also outdated
Click to expand...
Click to collapse
4.3 is fine to flash *sigh* recovery version only need's to be sorted for 4.4+
the issue last night was that i had compiled the build calling the device the operaul instead of the mystsomething or other
You have any words of advice on fixing the qhusb dload error? I really can't afford another phone.
xnerdx said:
You have any words of advice on fixing the qhusb dload error? I really can't afford another phone.
Click to expand...
Click to collapse
im like 9/10 sure that is a hard brick, just buy a broken htc first for like 40 bucks on ebay and swap the motherboard
SneakyGuyDavid said:
im like 9/10 sure that is a hard brick, just buy a broken htc first for like 40 bucks on ebay and swap the motherboard
Click to expand...
Click to collapse
Like I said, can't afford it right now.. It's the holidays and I'm a college student
xnerdx said:
Like I said, can't afford it right now.. It's the holidays and I'm a college student
Click to expand...
Click to collapse
im still unemployed and in high school lol, ask your aunt, uncle or... *cringes* parents?
SneakyGuyDavid said:
im still unemployed and in high school lol, ask your aunt, uncle or... *cringes* parents?
Click to expand...
Click to collapse
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
xnerdx said:
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
Click to expand...
Click to collapse
woah woah wait? the rom put your device into dload?
Lloir said:
woah woah wait? the rom put your device into dload?
Click to expand...
Click to collapse
Yes it did, I followed your instructions and wallah. Not my first time seeing a dload error on a phone either so...
xnerdx said:
Ha I wish I could ask somebody, I have enough to buy this phone new again but that ruins my plans with my significant other. I think I might as well buy a nexus.
Click to expand...
Click to collapse
thats what i mean dont spend a heap load, on a new First, keep most of the money for your plans and just try to buy a cheap First thats broken but has a fully functional mobo
xnerdx said:
Yes it did, I followed your instructions and wallah. Not my first time seeing a dload error on a phone either so...
Click to expand...
Click to collapse
jesus..... @jmz said the device bricked easily.....
SneakyGuyDavid said:
thats what i mean dont spend a heap load, on a new First, keep most of the money for your plans and just try to buy a cheap First thats broken but has a fully functional mobo
Click to expand...
Click to collapse
i'am so so sorry....I WILL try and make this up to you i promise
ALL MY BUILDS ARE HALTED UNTIL I GET MY DEVICE
NOTHING HAPPENS FROM MY END... I WILL NOT RISK ANYONE ELSE'S DEVICE
Lloir said:
jesus..... @jmz said the device bricked easily.....
Click to expand...
Click to collapse
Honestly I think it's an htc thing, I had this happen to my htc evita in a similar fashion.
xnerdx said:
Honestly I think it's an htc thing, I had this happen to my htc evita in a similar fashion.
Click to expand...
Click to collapse
it happened to my one v too, just talking to jmz, as he bricked both of his htc 1st's
AGAIN I'AM SO SO SO SORRY
This was unexpected nor did I anticipate this happening
i honestly feel so bad right now....
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
First thanks o.o
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Brawn_Sg said:
Why dont u use philz touch recovery or CWm for flashing
on cm and twrp recovery I also sometimes get those errors
Click to expand...
Click to collapse
Philz doesn't support --block flashing or the new method of flashing LP.our twrp has not properly implemented fstab for installation and I'm not able to make twrp with new fstab in cm-12.0 tree as it is throwing a lot of error messages and I currently don't have any kitkat based ROM tree due to my computer corruption few days ago.
I will be trying a clean build 2day.
ashwin007 said:
A couple of people were starting to work on CyanogenMod 12. Hopefully they are still interested in working on these projects. I am posting this as a place to share branches and collaborate if there is still interest in helping.My trees build perfectly.And the recovery baked from the cm-12 tree has display,touch working.But while installing zip I get a weird status-7 'failed to execute update binary.but since the Display,touch is working,it will be a pretty easy for working LP build.Please noobs stay away from asking weird questions.
At this point,I need support from any dev willing to work for this project.My trees are here.
https://github.com/ashwinr64/android_device_motorola_condor/
https://github.com/ashwinr64/android_kernel_motorola_msm8610
https://github.com/ashwinr64/android_vendor_motorola_condor
Btw,no hard feelings for anyone out there including @#buzz
I hope we can port LP very easily soon.
Click to expand...
Click to collapse
Which version of cwm recovery is in the build?
gud work
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
goutamniwas said:
@ashwin007 is it compiling ? (kernel source )
Edit :
This should help https://github.com/KonstaT/android_kernel_zte_msm8610/compare/cm-11.0...cm-12.0
check if some commits are missing
Click to expand...
Click to collapse
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
EDIT:Well @ace312 its no more cwm in cm tree.its cyanogen recovery made by cm
ashwin007 said:
Ya the kernel compiles perfectly.I have cherry-picked all those commits.and display and touch working.installation is the roadblock
Could you do me a favour?
Can you build twrp from kk tree using my fstab in
My device tree.and don't forget to add 'e2fsck' package to device.mk.thanks in advance!!!!!!
BTW I love your t2u.amazing!!!!
P.s:even my native place is Coimbatore.
Click to expand...
Click to collapse
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
goutamniwas said:
Coimbatorean gr8 , sorry but i dont have enough bandwidth for a cm sync :crying:
bw tat means u cant install it anyway ?
also thanks much for the complements
Click to expand...
Click to collapse
nevermind.i think i made a dirty build by replacing cmr with twrp without mka clean.so rebuilding now.hopefully it'll work.
Hey,
Why don't you flash system.img and boot.img with fastboot?
ace312 said:
Which version of cwm recovery is in the build?
Click to expand...
Click to collapse
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
GeekyDroid said:
Hey,
Why don't you flash system.img and boot.img with fastboot?
Click to expand...
Click to collapse
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
sw33ty4ppu said:
CWM/Philz is dead. CM has moved to CM Simple Recovery with CM12 and has ditched CWM. If you follow Gerrit, you'll know.
CM Simple Recovery is quite nascent ATM. TWRP is the recovery to beat, especially on Lollipop sources.
Sorry @ashwin007 for posting this on this thread while still being a n00b. I posted this to prevent further paranoid posts about the death of CWM. Apologies.
Click to expand...
Click to collapse
okay. it's been months I left ROM development. Sorry about that.
ashwin007 said:
Geekydroid.system.IMG is huge (700mb).but Motorola has that sparsechunk tech which separates system image into small part(you must be obviously knowing).so installing system.IMG makes it corrupt the /system partition.twrp 2.8.4.0 is working now.but i need to modify fstab for twrp which I forgot to do
Sw33ty4ppu not a problem.I think you have helped many of them.
Click to expand...
Click to collapse
Well, sorry I thought it is less than 215MB. I didn't think of it.
My last device was a motorola defy and developer @Quarx has a booting 5.0 lolipop build. perhaps he could enlighten us on how to make a booting build for out device.
Moto defy came with android 2.1 and kernel 2.6 so he should be able to help.
Now even moto e has received the "motorola update services app" update!! So maybe we are pretty close enough to get android L now!!! I think rather than rushing up things for condor cm12 and getting a buggy build after soo much hardwork wouldn't feel good!! Maybe we can wait a while for the android L to hit moto e ans then finally build cm12 which would be more stable too!!
•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•°•
see the attachment...
Lolipop is more closer...
This is a development thread.Refrain from posting those monotonous posts.I would like to keep this thread clean.
http://www.stjsgadgets-portal.com/2015/02/moto-e-users-start-getting-lollipop.html?m=1
I've received several reports for this thread in the past 2 days, so now it's time to issue a global warning here:
Let's keep this thread on topic, DEVELOPMENT, which is clearly stated in the title AND in the OP.
If you have a question, SEARCH FIRST, per the Forum Rules
1. Search before posting.
Use one of our search functions before posting or creating a new thread. Whether you have a question or just something new to share, it's very likely that someone has already asked that question or shared that news.
Click to expand...
Click to collapse