I have tested all ports of ubuntu in both sections of of the work in progress,and "easy ubuntu".
from what i see the ports are almost usless i tryed to update the os and it worked i got all the way to 11.04 but i could never get it stable,i tryed with all the meger skills i have to update and make it more stable,and as a result i broke the img when i tryed to go to 11.10.i hope we can get some more intensive testing and more devs to bring us a good tegra port that will give a true ubuntu.img that will work.
ps:all devs working on this issue im a tester from android forums ive worked on the lg esteem cwm and many more roms,kernal,themes ect.if you need me hit me up im ready to test away.
Related
maybe someone more linux savvy can check into this.
a search on our kernel version 2.6.27 thats on the moment brings up a website with a program for a local root vulnerability.
http://www.milw0rm.com/exploits/9545
not sure if it can be compiled for android... Just trying to help
I compiled it, and i am trying to get it to work but its running me into a brick wall. Its weird cause it works on my computer(full linux)... so Ill keep trying
Intresting indeed. I wish i could figure it out, but i dont know anything about linux.
there is some additional info over at ppc geeks here
http://forum.ppcgeeks.com/showthread.php?t=96237
Have you rewritten the x86 assembly instructions for ARM assembly? Also, I tried one of the milw0rm exploits on my Moment...seems they patched the kernel before the release.
I managed to discover a root exploit but its not the same as we are used to thanks to Samsungs stupid RFS aka FAT16 rom file system.
I'm nor knowledgable to make a rom, but hopefully this can be used to redo the rom in yffs2 so that it will work with existing apps, because even if we COULD keep root, stuff doesnt work, like nandroid, or Root Explorer.
http://www.samsungmomentforum.com/how-to/root-access-(finally-achieved!)/
I know many devs frequent xda and with zefie's root expliot maybe someone with the knowledge can create a rom for it in yffs2 using the source code samsung released.
Link: http://phandroid.com/2009/11/24/sprints-moment-open-source-released-by-samsung/
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
natediggler said:
I was wondering how hard it would be to alter the patches in the update.zip found here to work with the leon. I know the two phones are almost identical as seen here. as of right now there is only an update for the sprint/boost/virgin g-stylo's but there is supposed to be one coming for the t-mobile/mpcs one soon. i've taken the source and started tinkering with it. I've compiled the kernel changing TARGET_PRODUCT=g4stylusds_global_com to TARGET_PRODUCT=c50_mpcs_us but leaving the config as g4stylusds_global_com_defconfig and get far enough to get the zImage, but not the ko files. I have not yet compiled the rom, and it was about this point i started thinking about the update.zip DominicGresham was kind enough to provide us and maybe it would be easier than editing the source. any input would be appreciated. I like 6.x and would like to have it on my daily driver, and help everyone else that wants it for our device. i'm going to keep tinkering away until i get something besides a bootloop, and will attach the zimage i got after this test compile again on the kernel with the mpcs gstylo defconfig. i guess i should go ahead and try to compile the rom also and see how that goes. https://www.dropbox.com/sh/04pab4lbxncd7rr/AAA_GesYl74E35ikF4weaw1ca?dl=0
Click to expand...
Click to collapse
Hey are you still working on this rom? i would like to know because i can try to help in any way if needed
### check update notes. anywhere in this thred I have placed ### is a update
Original post is in ()
((Ok so here's the low down. I have the SM-G530T1. am trying to root the stock, deknox, deodex, debloat but leave the MyMetro app and the hotspot app other mods you name it.. but those are for starters. I have not found a stable way to pull this off yet as the only rooting methods I found that lets me use supersu is CF-Autoroot..... but... it is for the SM-G530T not the T1 so even though it works it still messes up which is why I am here.
I am hungry for learning and becoming a dev one day so I'd like to learn my way around the Kitchen but so far the windows kitchens are just bootlooping me.. Bad batches roms... I have tried many many ways and no success yet because the stock rom is such a pain to mess with unless you have root access. I thought about trying to use king root just to get a stock rom pull but im not sure if that idea will workout for me in the end seeing how kingroot is such a dbag and doesn't let you use supersu. I Need all the help I can get I'd really love to get a working rom for my dumb little phone so I can use that as a base to learn from.
The T1 and the T dont have much in differences so if one of you awesome people could maybe check out the stock metro pcs version for me and help me get something stable I'd appreciate that a lot. I am trying to help a few people out with this same phone as well so all credit will go to those who helped make this possible. I have windows 7 64bit that barely works and is not mine so I am limited to what I can do. I think my biggest issue is I am not able to use linux and ubuntu because this laptop is really old and barely works. VM doesn't even register the 64bit on this laptop. really sucks.:silly:
###### UPDATE as of 8/25/16, With the help of @ASSAYYED and his awesome kitchen made for windows. I have been able to at least get proper root access now.. but still need a recovery. I am trying to make one from stock but really need help for my device. Here are the specs.. All I need is either some one to be awesome and make me a quick one or tell me hw to make one for a qcom device like I have please..
my phone info if that helps http://www.4shared.com/photo/ZaSM2d9rce/Screenshot_2016-08-25-07-08-53.html
http://www.4shared.com/photo/G4zmKEw9ce/Screenshot_2016-08-25-07-08-41.html
http://www.4shared.com/photo/Eb7gXgLace/Screenshot_2016-08-25-07-07-00.html
@ASSAYYED , for helping me thus far and providing a awesome windows kitchen to cook in.
here is link to his thread and tool info, http://forum.xda-developers.com/che...-android-roms-editor-assayyedkitchen-t3410545 ####
I recently bought a FLIR ONE thermal imaging camera. Unfortunately, the device is not detected on my D802 using any marshmallow ROM.
I was using Resurrection Remix rom, but also tried Paranoid, XOSP, Dirty Unicorns, AICP, .... with no luck. Also, flashing Dorimanx and Lambda kernel didn't help.
When I run Chainfire USB Host Diagnostics, it says the kernel supports it, but OS does not.
On Lollipop (stock-based) roms, there is no issue, and the device is detected.
Can someone explain why the marshmallow ROMs miss this support. Is there any way to get this working ? I'm now running a LP rom again, just to be able to use the cam, but it really feels like a downgrade.
Same here, did you manage to fix it?
tehsYs said:
Same here, did you manage to fix it?
Click to expand...
Click to collapse
No fix other than going to stock based ROM or other phone.
All mm/aosp/caf roms are using a generic otg driver that breaks support for usb host intent filters. In other words, the phone won't broadcast to applications the a usb otg device has been plugged in.
It's not just your device in question, any device other than flash storage doesn't get detected. A developer could probably fix this but as it is broken in all non-stock roms it would probably be challenging to fix.
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
computerfreek274 said:
I do android development Mostly for the droid turbo, apps and tweaks. I think i may be able to help out here.
I did manage to get flir one working on none stock rom last night. It worked fine on stock. Then i seen this post installed cm and no joy. So after a bit of tweaking i did get it to work. I will see if i can come up with some kind of Universal patch for all users.
I will try and post a how to video to get it working on non stock roms. I am going to pull out some other phones to see if the patch works on all phones.
Keep an eye on my youtube channel http://www.youtube.com/iphostway/videos
I will work on a Universal fix starting today.
Click to expand...
Click to collapse
That would be really cool
If I can help testing your fix, please let me know.
Dear fellow developers and users of this great device,
I'm working on mainline support for the p4note device family, I started with the N8010 but this is usable on all the other N80XX devices as well as they are technically all the same aside from the modem.
The current status is that an initial device tree will land in 5.11 with some components still missing but its a good start. I'm working on the rest and also I'm working on Android 11 on top of that.
This post will not be updated any longer, you can find my mainline progress here.
There is also a blog which I'll probably woefully neglect as I'm way too busy with everything in life.
Cheers
An update for my mainline progress, there is kernel logs on the display now! I'm currently working on the touch screen config.
Oh Nice to see.
But i think not many people read the General forum anymore ^^
You might want to mention this in the Dev thread.
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
fldc said:
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
Click to expand...
Click to collapse
Hey, great to hear that you want to tinker with it. Remember that I currently work on rev 6 of the hardware, the version info can be found in the atags of the kernel log. You may run into issues with other revisions but it should be fine.
For the wifi settings, you need the correct nvram file. I'm not yet sure whether you can determine it by the version of the hardware, the current way is a macloader in the current hardware repo.
I extracted the touchscreen firmware from the sources and put them in my buildroot repo. The driver will look for a file called maxtouch.fw on boot.
I hope this helps.
Thank you very much for the pointers, I haven't t really been into kernel development since Samsung Galaxy S2 (9100), but getting a proper Linux installation on this device would fit me perfectly so I would happily try things on my side, keep us posted.