Ubuntu Install - Nexus 10 Q&A, Help & Troubleshooting

So i am having a slight issue getting ubuntu installed on my nexus 10.
I followed the instructions here.
http://developer.ubuntu.com/start/ubuntu-for-devices/installing-ubuntu-for-devices/
I am on 14.04 on my PC so some of this doesnt directly follow but i added the packages
So i run the ubuntu-device-flash --channel=stable --bootstrap
When i do this all seems well, then the nexus pops up with a ubuntu touch CWM based recovery. I tell it to reboot and it just goes back to standard old android. Has anyone else ran into this? Any ideas on how to get the latestest version of ubuntu touch running on my device?

Related

[Q] Dual Boot TPT 183**

I have a nexus 7 and was able to get a Dual Boot installed which was able to let me keep android o/s and also install the ubuntu o/s.
Yeah the screen is way too small on the nexus 7 but wanted to try it and see if it could be done.
Now I want to get this TPT to do the same think being that it has a larger screen and the folio kb with it.
Has anyone seen any dual boot installers out there? I've searched and only came across someone just doing a install of ubuntu only.(taking out the android o/s)

adb sideload won't work (bricked my n10) HELP

Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
parakalien said:
Background, I've done this many times, I currently have the latest CWM installd on my manta and I change ROMS and Kernels pretty frequently (I just like trying new things).
Recently I tried the preview build of Ubuntu Tablet and I can't get it to boot. Problem is I don't have any other zips on my internal storage to flash back to.
No problem I thought, I'll just side load using adb and the sideload function of CWM.
I've done it before and it worked perfectly but now I'm getting an error.
I do have my rom .zip in the correct foler (platform-tools) and I am running my command prompt from the right place.
If I do adb devices I do see my tablet serial number and it says sideload, just like it should.
But when I use the adb sideload MYROMNAME.zip I get an error that reads, *Can't read `sideload`*
If I try to use adb push MYROMNAME.zip /sdcard/ it says error:closed.
I tried completely removing my ADT bundle and redownloading the latest version and reinstalling everything including the google usb driver but I get the exact same error... I'm using win 7 32 bit.
Any ideas??? My tablet currently is bricked until I find a solution.
Click to expand...
Click to collapse
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
newellj79 said:
Grab one of the many toolkits from the development sections and flash the factory image. Then u can just start over. I've had to do this myself, thanks to the first release of Ubuntu for our tablets.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Thank you very much!! This fixed it and was super easy.
Appreciate your help getting me out of a sticky situation!

Switch b/w Ubuntu / Android and Dual Boot

Hello,
Running i9250 on stock 4.2 android.
Want to try the Ubuntu stable build on it. I can see the Ubuntu Installation steps on Ubuntu website.
However just want to know what would be the way back to android. Would I be able to keep CWM recovery partition and restore an old nandroid backup. ?
Secondly is it possible to run Android and Ubuntu in a dual boot mode..
Thanks for your replies.
HyperEscape said:
Hello,
Running i9250 on stock 4.2 android.
Want to try the Ubuntu stable build on it. I can see the Ubuntu Installation steps on Ubuntu website.
However just want to know what would be the way back to android. Would I be able to keep CWM recovery partition and restore an old nandroid backup. ?
Secondly is it possible to run Android and Ubuntu in a dual boot mode..
Thanks for your replies.
Click to expand...
Click to collapse
Hello,
at least for 2012 Sony Xperias (S, Acro S and ION) there exists a dual boot tool by @letama, which can be found here and is verified to run the Ubuntu OS as one of the two roms (or both, whatever sense that should make...).
Of course this specific minikernel will not help you directly, but maybe it'll point you in the right direction to continue your search. Maybe you can find out, whether a similar tool can be made / exists for your device in the thread mentioned.
HyperEscape said:
Hello,
Running i9250 on stock 4.2 android.
Want to try the Ubuntu stable build on it. I can see the Ubuntu Installation steps on Ubuntu website.
However just want to know what would be the way back to android. Would I be able to keep CWM recovery partition and restore an old nandroid backup. ?
Secondly is it possible to run Android and Ubuntu in a dual boot mode..
Thanks for your replies.
Click to expand...
Click to collapse
I installed the stable version on my I9250. I'm not sure about the dual boot as this was not my daily driver.
From my experience after installing I could not go back to a CWM ot TWRP back up.
I had to do a reinstall a fresh 4.2.2 and then re-root.
I tried to restore back up from TWRP, but for some reason I had issues with a complete restore.
it was no biggie for me, since it was not my daily driver, but I made sure to back up the data I had on it just in case.
My experience.

[Looking For] Ployer Momo8w Dual Boot Win10 Drivers

As title says, I'm looking for the Windows 10 Drivers for the Ployer Momo8W Dual Boot Tablet.
While updating the Windows 10 version of my tablet an error occured during the installation of the new version. I managed to do a clean install of windows 10 from an USB stick but now I have several "unknown devices" in the device manager, the touch display doesn't respond and screen rotation doesn't work either (everything is upside down as in 180° distorted)
I have found a thread with Ployer Momo7w drivers here on xda, but I'm not sure if they would work on my momo8w though. I hope someone can help me.
Hey buddy.
I'm going through similar with my Momo9w, while playing around trying to make it dual boot I messed it up, removed recovery to accidentally.
Finally managed to get a clean install of Windows 10 on it, then had another go today and now need to go through it all again! Worth a go.
Anyway I wanted to say the Momo7w drivers posted seem to work with my 9W, so I'm sure they will with your 8w.
The only issue I had on win 10 was the touch screen calibration not working right, the touch point was off from where I was touching it. However there is a Chuwi topic on here I've jist been reading with similar problems and fixes, so when I am back to win 10 I will try those.
Ian
centuryheli said:
The only issue I had on win 10 was the touch screen calibration not working right, the touch point was off from where I was touching it.
Click to expand...
Click to collapse
I've got the same issue here. Did you manage to solve that problem?
20qwertz12 said:
I've got the same issue here. Did you manage to solve that problem?
Click to expand...
Click to collapse
Hey Buddy.
Ah, I'm still struggling to be honest.
Originally I installed Windows 8.1 and got the touch screen working fine after a few tries, then it updated to Windows 10 and there was no problem. Then in my stupidity I tried installing a dual boot with Android again and now I'm back to the beginning with Win 8.1 beside me and trying to fix the calibration again!
From the time before it is something to do with the touch screen driver and the Windows driver it installs for the screen, I've read the touch drivers need to be installed after in this case.
I'm currently sat beside the tablet trying to get the touch screen working on Win 8.1 again.
Ian
Thx for the tip with the chuwi thread, managed to install the touch screen drivers and it's now working again
I hope you can solve that problem of yours too
Hi all. Ehhh... Not very closely related, but you guys here appear to be the best experts on the topic on the whole wide internet, so I hope you can help me out.
Just bought a Ployer momo8w dual boot for my daughter, but the accelerometer won't work in Android.
My unit came with a new firmware, Android 5.1.1 and Windows 10. The accelerometer does work in W10, but would not even show up in Cpu-z or sensorbox in Android. Is there any way to 'hack it', or any way to downgrade the firmware to Android 4.4/W8.1 or whatever exact version these used to be shipped with? I could not even google anyone else having this problem, but I have two devices (two daughters) and they both have this issue.
ME TOO HOW INSTALL win10 driver ?
I do a backup using powershell like i found around here... and uploaded to mega.
Here's the link:
Drivers:
hXXps://mega.nz/#!SsdVnSjJ!XPHRqwMmOHVye7XxVoD1qdu95jy7bkV_5BVBBDR-rVE
And for a touchscreen 100% working you need to copy SileadTouch.fw to System32\Drivers folder and reboot.
SileadTouch:
hXXps://mega.nz/#!qgdBhSwS!pF0y7NfyC6UHVIGgDFfcwdnTemya7wUZe4Dt_o2htC0
And for fully working Video, i used Intel Driver Update Utility, downloaded from intel's site, here:
hXXXs://downloadcenter.intel.com/download/25977/Intel-Graphics-Driver-for-Windows-10-and-Windows-7-8-1-15-33-
but you can download the driver from here:
XxXxs://mega.nz/#!W5NUTYZI!sBaGoJhJl0NZvALsBpCMOmvgqdIOTvOVJwabioVBIdc
The only thing that it's not working for me i'ts the mSD Card Reader
i downloaded the first link, but which folder do i put it in? please help im struggeling with the touch
I know this thread is quite old... but I managed to get some drivers at least.
For Bluetooth you can download the official Realtek drivers here:
realtek.com/en/component/zoo/category/rtl8723bs-software
For audio I found this (lenovo website):
support.lenovo.com/us/en/downloads/ds040044
But for touch I still have no clue! The SileadTouch file didn´t work for me.

Looking for a group of Ubuntu Touch devs to join

Hi,
I have some free time and would like to join a group of Ubuntu Touch devs. Is this a good place to ask or should I re-post on Canonical?
You can attempt to re-post on Canonical's forums, but the Ubuntu Touch Google+ Community is pretty active with both developers that work on Ubuntu Touch and consumers. I know I've seen Canonical's Michael Hall post in there as well as a couple others at some points.
https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)
kidhudi said:
https://ubports.com
This might be the place for you. They are asking for devs.
Good luck. I hope you start with the shamu (Nexus 6)
Click to expand...
Click to collapse
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.
Matrixians 14 said:
I have a Nexus 5 and I want to dual boot Ubuntu with Android. There are 2 instructions on ubports.com but the one using MultiROM(to dual boot) has no link! I followed other guides with MultiROM but Ubuntu won't boot. Android's still working fine, though.
Click to expand...
Click to collapse
You will likely need to look into the official Ubuntu Dualboot solution and adapt that for the hammerhead. Ubports ROMs are intended to be installed via the ubuntu-device-flash commands only and are likely not supported under MultiROM easily.
That said, if you have an UBports system image installed via MultiROM, and it appears via multirom, you can always check /proc/last_kmsg after a failed Ubuntu Boot (while in multirom's boot manager) to see where the boot went bad, you could also open the ROM under MultiROM's recovery and hit Patch init and see if that helps.
Other than that, I'm afraid the only supported installation method for the community ports are the instructions listed on the page. You may also have some luck looking for KDE Plasma Mobile tutorials (which use a standard Ubuntu Touch image for their basic installation, not sure if they do the same thing as ubuntu-device-flash though).
One last thought, have you tried MultiROM manager? It may have images for your system (I recommend going no further than rc-proposed, devel does not run many apps from the Store and is based off Xenial, sp there's some library incompatibilities with apps installed from the Ubuntu Store. Devel branches are also not guaranteed to boot, however rc-proposed and stable should at least boot for you unless their builds are fundamentally broken, in which case, you should bring it up with the maintainer)
Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.
Matrixians 14 said:
Thanks, but now Ubuntu Touch worked. I installed the dual boot app and added the channels for hammerhead. But now Everytime I boot into Ubuntu it removes my custom recovery. Instead of booting into the recovery, it boots into Ubuntu Touch, and it only happens if I reboot into Ubuntu Touch, so I basically have to reinstall recovery after using Ubuntu, which is very inconvenient.
Click to expand...
Click to collapse
I replied on the G+ page too, but figured I'd post here as well so others may benefit if I'm right here. -SNIP-
Edit: I just realized how the dualboot utility works.. It is likely the application overwriting your recovery image. If you want to keep MultiROM, I'm afraid you'll need to reinstall Ubuntu with MultiROM manager as the dualboot utility writes Ubuntu's boot.img to the recovery partition to boot Ubuntu.
Yeah, thanks, but it only works with the dual boot utility. I have my issues with MultiROM if you've read the first post on G+. But now I restored my system to a previous state when there was no dual boot utility so I don't want Ubuntu Touch anymore. Linux Deploy would do the trick, but now even IT has problems installing trusty. After the installation, I reconfigured it from the Linux Deploy menu and when I start it, it failed to start the VNC server and I don't know why. Is it the architecture of Trusty that i chose?
I did see your post, my apologies that MultiROM isn't booting for you, I ran into this weird issue myself on the Flo, normally it can be solved from trying other revision numbers in either the stable or rc-proposed channel. Sadly, through the Dualboot installer, there's no way around this (bar writing an /etc/init.d script for Android that automatically flashes the TWRP image when Android boots back up)
It may very well be the architecture of trusty. I would recommend trying vivid, saucy, wily or xenial. (any of the more recent versions, trusty is rather old at this point and you would've been getting Vivid [15.04] via Ubuntu Touch)
That said, you'll get much more performance using XServer XSDL from the Play Store and setting Linux Deploy to use it (X Server -> Use XServer XSDL), it also allows you to use any X application remotely or locally (on a remote machine you'd do export DISPLAY=[Tablet IP]:0)
As for Ubuntu Touch, if you go back through and attempt MultiROM again, start with the latest revision (I recommend staying far away from devel and devel-proposed unless you are purposely wanting to develop applications for Xenial, most applications targeting Vivid here don't work.) and then if the latest fails to boot, try the next one down the line. Another issue here could be a kernel that doesn't properly support KEXEC, have you tried MultiROM with a different KEXEC compatible kernel? I honestly can only recommend two different configurations, the singluar installation (Ubuntu being the only OS, gives you the most storage space) or MultiROM :\ I don't have much experience with the Dualboot app.

Categories

Resources