Database Develop

Adding root to a custom build.. devs, a little help please?

So, I'm messing about with building android from the source, just as a learning process and for my own personal satisfaction at this point.
I've come most of the way under my own steam.. got a build up and running from the donut-plus-aosp branch, all google apps included and working.. but I don't actually know how to include root access in the build.. I know this is probably an embarrasingly simple question for a dev, and I feel suitably stupid for having to ask.
Also.. now you're here.. apps2sd.. do I need to compile anything special for that or is it just a bunch of symlinks in init.rc?
Muchos gracias.

I believe the root access is located in the kernel (boot.img)
You would also want to include the SU binaries and busybox.
For the apps2sd, the apps2sd script is run from the init.rc IIRC
Do not hold me up on this because I have not even looked at Android yet, but this is what I gather from reading the forums. I'm hoping it may give you a little direction while someone who has actually built from the source steps in

Thanks. I've already included the su binary and superuser apk but couldn't launch them, so I thought I must be missing something either in the kernel or init.rc.
I was hoping not to have to build the kernel manually just yet.. walk before you can fly and all that, but maybe it's time to grow some wings.

You should just compile cyanogen's kernel. he has it on his github. btw.. did you add busybox? i think apps2sd requires it but im not sure.(check logcat on startup, see what errors its throwing)

I've just added busybox in, but I can't do anything with apps2sd until I get root sorted.
I'm sticking with the 2.6.29-donut kernel for now.. cyan's includes loads of patches that I don't understand yet.. I'll compile it and see what happens purely as an experiment but I reckon it'll give me problems...

Just looking at the configuration options for cyan's kernel makes me feel like a dad trying to program a vcr

This post was infected with retardation. Please ignore.

goldenarmZ said:
This post was infected with retardation. Please ignore.
Click to expand...
Click to collapse
LOL
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
I know I hate looking at kernels. Liquefies my mind

B-man007 said:
btw if your building from ASOP, it should already have root. I think you only need to add it to T-mobile OTA's
Click to expand...
Click to collapse
It's not working for me.. I just get "permission denied"

Well I've got root by running chmod 4777 on /bin/sh, but this leaves root access wide open to everything and bypasses the confirmation check from superuser.apk... Come on devs, I could really do with a few tips here!

I think I've got it now... thanks to all the devs, you were a real help here.

goldenarmZ said:
I think I've got it now... thanks to all the devs, you were a real help here.
Click to expand...
Click to collapse
XD
i know, they are so helpful right?
Actually they never come by here anymore because of the supernoob questions
I suggest you try to pm,twitter, or website the devs. many of them are very helpful, but cannot stand noobs. as long as you do your research (like u did) you should get help

Hmmm, as I'm also building AOSP from scratch, I would have liked you to have at least posted the conclusion. I feel like several pages were ripped out of my copy of the story.

Looking for MIUI4DX testers

NOTE: If you do not know how to SBF or have problems SBFing please do not post about it here. This is a research thread
A while ago TreyM started development on MIUI4DX. Unfortunately he does not own a Droid X. And due to personal reasons he may not be returning to the scene for some time. If he was here I would ask to take over development, but because of the circumstances I've decided to head development. (If anyone has an issue with this please contact me.)
I'd use the other thread created by TreyM for this, but I feel due to this being very unstable and being in a place where there are other device developers, I may be able to get some more input. Also this is an older build of MIUI,
Here comes the hot stuff!
Instructions:
These are in update.zip form. Just install as a zip through ClockworkMod
To grab a logcat you must have the ADB. Open a terminal (Command Prompt) and input the following:
Code:
adb devices
adb -d logcat > MIUI4DX-logcat.txt
I also need dmesg output.
Code:
adb devices
adb shell
dmesg
Go to pastebin.com and post a link to logcats and dmesg output here.
Test builds, and changelogs.
Here is test #9. It is basically the Defy MIUI ported to the Droid X
http://tetradsoftware.com/android/i...ile=miuiandroid_DroidX-1.7.10_pre-alpha-9.zip
Does not get to the bootanimation
LOGCAT: http://pastebin.com/SLy6TSqh
DMESG: http://pastebin.com/kc4N34cy
This is test #10. It's basicly the Defy apps, and framework-res.apk forted to CM7:
http://tetradsoftware.com/android/index.php?dir=DroidX/MIUI4DX/&file=MIUI-Alpha-10.zip
This actually gets to the bootanimation
LOGCAT: http://logcat.miui.us/285002
DMESG: http://pastebin.com/0wAFVXKs
Please, please, please look over the logcats, and dmesg for both of them. I can't decided which to go from.
Follow me on Twitter @ghostlypickel

are we suppose to just install one of the given zip's or do we have to use the commands first. Some detailed instructions would be extremely helpful

reannimated said:
are we suppose to just install one of the given zip's or do we have to use the commands first. Some detailed instructions would be extremely helpful
Click to expand...
Click to collapse
Install then run the commands. The test logs and changelogs are at the bottom for organizational reasons, since it's being constantly updated.

Downloading now flashing and logging when I arrive home in about an hour or so.
Just flashed the new miui port for the nook color. Wip but great Tom nonetheless.
Sent from my DROIDX using XDA Premium App
Edit: took a bit longer getting home then expected. Redownloading now previous went south.

OP updated with important info. Please look at BOTH builds logcats/dmesg. I cannot decide which to go from.

Still looking for testers?

cyberhern said:
Still looking for testers?
Click to expand...
Click to collapse
I dont think he is since the real release is coming out tonight for the DX and D2.

bigshotrob22 said:
i dont think he is since the real release is coming out tonight for the dx and d2.
Click to expand...
Click to collapse
i hope that's true

cyberhern said:
i hope that's true
Click to expand...
Click to collapse
It is. It's supposed to be released on miui, xda, and on rootzwiki.
Sent from my DROIDX using XDA App

bigshotrob22 said:
It is. It's supposed to be released on miui, xda, and on rootzwiki.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
THANKS for the heads up...
Guess I know what I'll be doing this weekend.
!-)

sweet! i will have to try this tomorrow but definitely keeping an eye out on this thread

*Bootloader Unlock Research* Cheesecake Clarification

10 charact

..........

Also reserved please

This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium

ROB281 said:
This sounds like something that can kill a lot if time while I'm in the office.
What are we looking for when doing this?
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
Well, I'll get to the point soon. still modifying the post. but basically the gist of it is to check ALL of motorola's update servers for updates, not just the one that comes programmed into the device. If we're lucky and we find a hidden update, we may be able to get an unlocked bootloader (or other goodies?), which will allow us to use our device as we please (new kernels, better mods, etc)

Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App

karthakon said:
Thanks for writing this up, I've been hesitant to try it since some of the paths/files in other posts did not exist on the Bionic.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Well, I was bold and basically just created the files. When I ran the *#*#4636#*#* test, I found that it did indeed change my could update server.
also the com.motorola.blur.setup was in /data/data/ and not the system/etc/motorola.

Thank you.
Sent from my ADR6400L using xda premium

Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.

K.AuthoR said:
Thank you for this. The previous directions were based on the Atrix so there were a lot of files listed that I never saw so I felt unsafe just making them up and moving things around. I'll get on this sometime in the very near future.
Click to expand...
Click to collapse
I actually have been testing some methods that may not even req a wipe in between or possible before
Sent from my DROID BIONIC using Tapatalk

Apparently someone found an update somewhere. Good sign. I'm going to check it out in an hour or two. Don't have my hands on it yet.
Sent from my DROID BIONIC using Tapatalk

Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!

kennethpenn said:
Looking at these right now. I'll go ahead and update the main thread with your corrections. Thank you for figuring it out!!!!
Click to expand...
Click to collapse
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update

phydo said:
when I hit the server, it says it's a 5.5.886 -> 5.5.891 update
Click to expand...
Click to collapse
Just so everyone can see it: the update label will always be for the build ID that the zip is supposed to be installed over. That means if you've got an update:
Blur_Version.1.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "1."
Blur_Version.5.5.886.XT875.Verizon.en.US.zip --> This means the zip should be installed over devices running Build number "5.5.886."

Was anyone ballsy enough to attempt to install the update? It doesn't have a bootloader inside, but it may still be dangerous.

P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!

cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.

jimmydafish said:
So I decided that I just couldn't sleep not knowing if the root patch had been fixed. So I decided to flash the update.zip. And what I expected to happen, happened, it zapped the local.prop exploit.
So here I sit on the new build unrooted and stock. I'm fairly certain that if I try to revert back to the OG build I will have a paper weight on my desk until a full xml fastboot file can be found. I would suggest you all wait and don't flash this yet.
Click to expand...
Click to collapse
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!

Enzopreme said:
thats what i call takin one for the team!!! thanks bro!!! You'll be rooted again in no time, maybe even s-off!!!
Click to expand...
Click to collapse
S-off doesn't apply to Moto products...
Sent from my DROID BIONIC using xda premium

cellzealot said:
P3 flashed it and it does absolutely contain a bootloader update.
The critical pieces are the mbm.bin, mbmloader_hs.bin and mbmloader_ns.bin.
HS and NS refer to Hardware Secure and Non Secure parts and both are included in these updates because both types of hardware are present in the test groups or whomever is the intended recipient of these files.
There is not an unlock, per se, but both secured and unsecured mbmloaders are present and the updater script has a check for the ro.secure status and loads the appropriate file for the target device.
The D3 update and assumedly this file as well cannot be reverted to stock release version, so this file must be regarded very carefully and assessed before any decision to flash or not is made.
There is a LOT more discussion we need to have about these files and OMAP SoCs I think regarding the differences between them and the Tegra II SoCs and fuse arrays!
Edit: This breaks the djrbliss root method using the tcmd exploit. We need to look further and discuss with him other possibilities for root. Reverting has not been established yet and may brick since we dont have a complete XML.zip.
WARNING!!!! This is a very dangerous file to flash at this stage!!! Please do not rush into testing it yet!!!
Thanks to those who got the file and thanks to P3Droid for guinea pigging.
Oh and I have to add that clarified cheescake is an oxymoron...you garnish cheesecake with wonderful things!
Click to expand...
Click to collapse
I suppose I was looking for the wrong things. On other devices, "ap20bl.img" was responsible for bringing such goodies as an unlock capability.

[DEV]Ultimate AOSP ICS Testing Arena [Always Updating]

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

CM 7/9/10 Dev discussion

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