Hi !
It's quite a shame I can't post that question directly on the good thread, but well, it's how this forum is done.
So, I'd like to know what became of the u-boot bootloader that sp3dev did try some months ago:
http://forum.xda-developers.com/showpost.php?p=23004214&postcount=53
Is it part of the V3 bootloader ? Has it been abandoned ? Does it actually work ?
The goal would be to be able to boot a simple Linux kernel from USB, and from there to try various Linux "products": Mer/Nemo, PlasmaActive, etc. All of that, without losing the possibility to have a custom Android recovery + Android installed on eMMC.
Is there some kind of hack you can use on any phone to boot into either one ROM or another at startup? I have MultiROM on my Nexus 7 that allows me to boot to many different ROMS off internal and external sources. Is something like this possible on the Sprint LG G2?
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.
I'm trying to figure out if I can flash a different variant ROM to my G530AZ. Being that there aren't any rom's available for my phone.
There are a few factors involved in this.
First, if you consider doing this, you'll want to get the ROM for the device that matches the specifications of yours as closely as possible.
The second is, it's likely that the sizes of system partitions will differ between variants of the same device, so there would be a possibility of messing up the partitions on your device if you flashed the image. You should be aware of this risk, and should be prepared either to:
Manually resize the system image to fit your device, then flash it.
Just flash it anyways and hope for the best.
You can always try porting the device yourself to a custom OS for yourself, or put in a request for that in any appropriate forums.
I can say yes or no, because like what vince2678 said, it would mess up your partition, but even if you succeed it, you'll have more problems, such as some functions won't work due to differences between libs from the rom you just flashed and the libs that your device need for working functionalities
Does anyone know how or where I can find info on building a custom rom for this phone?
You can look at the AOSP, Omni and CM wikis. They have good documentation on how to get started on the whole process of building a custom rom.
Hi.. Im new here with this device i read almost every single post here but there are quite a few things that I don't get it..
What is bootloader? Should i unlock it before rooting the device? And recovery here is in Chinese so shall i get TWRP instead? Also about the flashing Roms issue that erase imei and SN.. why would that happen? And How can i take a backup for these in case i lose them.. Some people mentioned SN writing tools but some people says its not working so im abit confused.. And has anyone noticed that the flashlight of the mobile is actually yellow that affects camera's captures? I would be really grateful if someone helps
1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..
Krishnas096 said:
1. What is a Bootloader?
Hboot, or we may call it Boot-loader, is like BIOS to windows. It is the first thing that runs when you boot up your Android device. It packages the instructions to boot operating system kernel and most of them are specifically designed to run their own debugging or modification environment.
Every Android phone has a boot-loader that instructs the operating system kernel to boot normally. But you need to understand one thing here that as Android OS is an open source OS and is available on a variety of different hardware, every manufacturer has their own version of bootloader specific for the hardware present in it’s environment.
2. Should you unlock it before rooting the device?
It solely depends on you whether you want to unlock it or not. Unlocking bootloader will give you access to installing custom recoveries on your phone and also you can use custom kernels to boost up phone's performance or simply get more battery juice. Since our K4 note doesn't have any custom kernels so good luck with that.
Warning: Unlocking Boot-loader voids phone's warranty
3. Why does IMEI/SN erases while flashing ROM's
People don't read the tutorial properly. They blame the OP instead when they do something wrong and loose their IMEI/SN.
What basically happens is, when flashing ROM's through SP flash tools, They should flash it in "DOWNLOAD" mode only and not in "Format ALL" mode. People who all lost their IMEI basically did this mistake.
4. How to Backup and Restore your IMEI/SN (NVRAM)
All the device specific details such as IMEI, SN, MAC addresses are stored in a partition called as NVRAM. So backing it up will indirectly be referring to backing up your IMEI/SN. Here is how you can do it.. LINK
5. How to install Recovery?
if you are on Marshmallow then you will be able to install recovery through this thread. LINK
6. Yellow Flashilight problem?
This bug is introduced in Android V6.0 that is marshmallow. Actually this is not truly a bug. Unlike on Lollipop which had only one LED light enabled during Camera operations, Lenovo decided to enable both of the LED's (That is white and yellow) to give the images a more true LIVELY appeal.
But terming this as bug here because nobody liked it and users were pissed off straightaway. Hopefully, Lenovo will fix it soon.
Hit Thanks if i helped..
Click to expand...
Click to collapse
Ahaaaaa Thanks Alot now it get it all.. Hope they fix that soon.. And i read that some devs here is willing to make a custom kernel i guess.. thanks again and sorry for wasting ur time.. Btw have u noticed that the sound on headset and Bluetooth is also abit lower than other devices?
Lenovo A7010 - CM13.0 Android 6.0 on lenovo-forums.ru