FORUMS
Remove All Ads from XDA
Honor View 10
Win an Honor 7X!

 View Poll Results: Would you dare to try a beta port of Ubuntu Touch on your HOX?

Never! Too risky or I am not interested at all.
 
0 Vote(s)
0%
Maybe, depends on how stable it would be.
 
0 Vote(s)
0%
I would take a look as soon as it works a bit.
 
4 Vote(s)
100.00%

Ubuntu Touch for HOX: A new experiment on an old device

55 posts
Thanks Meter: 7
 
By Flohack, Member on 8th September 2016, 01:47 PM
Post Reply Email Thread
Hello all,
I´m picking up this thread again.
Meanwhile long time has passed, but I see that the time is now much better for a working port. There is ubports project, which has a working tree based on CM12.1 and there are some custom ROMs which have ported 12.1 also.
So its hopefully just a matter of combining the right things.

What I got already:

- Tree that is compiling
- Recovery image that is booting and adb enabled

UPDATE 2016-09-18:
- Kernel is booting and no panic
- Start screen shows up with animation (but blurred, see picture) HTC One X with Ubuntu Touch, first sign of life

UPDATE 2016-10-07:
- lxc-container for android confirmed to be started, but with errors - see http://pastebin.com/RCcBULBy
- Further boot is stuck
- ADB is working finally reliable!

Looking for interested porters/developers to work on this port!

BR Florian
The Following User Says Thank You to Flohack For This Useful Post: [ View ] Gift Flohack Ad-Free
 
 
8th September 2016, 02:00 PM |#2  
Senior Member
Thanks Meter: 356
 
More
Im ready to help. BTW for the adb you have to goto mount and click disable mtp and enable it again the USB config of hox is not right I would look to that later
The Following User Says Thank You to DevUt For This Useful Post: [ View ] Gift DevUt Ad-Free
8th September 2016, 05:59 PM |#3  
OP Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by DevUt

Im ready to help. BTW for the adb you have to goto mount and click disable mtp and enable it again the USB config of hox is not right I would look to that later

Sounds great, especially when you are the guy who already provides the device repos - I will look into the ADB stuff in a few minutes or so...

BR Florian
9th September 2016, 07:59 AM |#4  
Senior Member
Thanks Meter: 356
 
More
Quote:
Originally Posted by Flohack

Sounds great, especially when you are the guy who already provides the device repos - I will look into the ADB stuff in a few minutes or so...

BR Florian

Im experimenting with the kernel at this time so dont use the MM branch instead use the cm12.1 branch or head to github.com/htc-one-x/android_kernel_htc_endeavoru

And use the cm12.1 or lp5.1 branch

And im always for help so please keep us updated with the status
9th September 2016, 06:07 PM |#5  
OP Member
Thanks Meter: 7
 
More
Hi,
First test with recovery failed, got boot loop this time. But will try with correct kernel config later today...
With CM 11 from cm server I got a working recovery. Will be interesting to see differences
9th September 2016, 06:15 PM |#6  
Senior Member
Thanks Meter: 356
 
More
Quote:
Originally Posted by Flohack

Hi,
First test with recovery failed, got boot loop this time. But will try with correct kernel config later today...
With CM 11 from cm server I got a working recovery. Will be interesting to see differences

Use the htc-one-x kernel and paste the /proc/last_kmsg on paste.omnirom.org so i can have a look
9th September 2016, 08:02 PM |#7  
OP Member
Thanks Meter: 7
 
More
How to get that if recovery has bootloop xD
10th September 2016, 06:12 AM |#8  
Senior Member
Thanks Meter: 356
 
More
Quote:
Originally Posted by Flohack

How to get that if recovery has bootloop xD

You let the recovery bootloop once then when it boots the second time you force reboot it by holding the power button then you boot into normal android then
Code:
 
adb shell su -c "/proc/last_kmsg"
10th September 2016, 09:02 AM |#9  
OP Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by DevUt

You let the recovery bootloop once then when it boots the second time you force reboot it by holding the power button then you boot into normal android then

Code:
 
adb shell su -c "/proc/last_kmsg"

Ok my recovery is stable now after applying kernel config for Ubuntu. But now again, no ADB is possible. But USB port seems to be up:

Bus 002 Device 013: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt (Charge Mode)

And this is the screen I get: http://imgur.com/gallery/Epwp0
Why am I in charge mode? Smth wrong with the recovery options?

BR
10th September 2016, 12:19 PM |#10  
Senior Member
Thanks Meter: 356
 
More
Quote:
Originally Posted by Flohack

You let the recovery bootloop once then when it boots the second time you force reboot it by holding the power button then you boot into normal android then


Ok my recovery is stable now after applying kernel config for Ubuntu. But now again, no ADB is possible. But USB port seems to be up:

Bus 002 Device 013: ID 0bb4:0ff9 HTC (High Tech Computer Corp.) Desire / Desire HD / Hero / Thunderbolt (Charge Mode)

And this is the screen I get: http://imgur.com/gallery/Epwp0
Why am I in charge mode? Smth wrong with the recovery options?

BR

First step :: Remove cyanogen recovery and add TWRP
10th September 2016, 10:01 PM |#11  
OP Member
Thanks Meter: 7
 
More
Quote:
Originally Posted by DevUt

First step :: Remove cyanogen recovery and add TWRP

[In reply to Florian Leeber]
Won't work. You need to build an Ubuntu recovery for your device. It handles the unpacking differently the android recoverys

Thats the problem with Ubuntu Touch, I need to get their recovery working

BR
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread