Hi,
I read these threads about booting into ubuntu (http://forum.xda-developers.com/showthread.php?t=1392167&page=2) and implementing dual boot (http://forum.xda-developers.com/showthread.php?t=1578438).
As far as I could understand, in order to be able to multi boot into both images I need to use the zImage from the ubuntu kernel and initramfs file from the dual boot kernel.
The multiboot menu shows up when I'm turning the device on, but I can only boot into the ubuntu option.
When I try to use the stock (I was surpriesed to see this option) the device resets, and when I try choosing the rooted ICS I installed before, it seems like the menu is loading it (there's a bar at the bottom of the screen), but then theres only a black screen while the device is still activated.
I'm kind of new to this and I don't really understand the logic behind these matters - I just do as instructed, but if any of you can help I would really appreciate it!!
Related
Ever since CM9 went into its first Beta, I wiped and installed it in place of the CM9 Alpha builds I used previously on my Droid 3 XT862, a CDMA phone for which CM9 requires no patches to run as I understand it. Ever since the nightlies started rolling out, every attempt I've made to install them has left me with one of two situations. If I install a CM9 nightly and the latest corresponding GApps pack, without wiping it gets stuck at the "Upgrading Android" screen saying "Starting Applications" forever. If I wipe and install a CM9 nightly and the latest corresponding GApps pack, the phone never passes the Motorola "Dual Core Technology" screen. I end up flashing back to complete stock (requires activation and rooting) Motorola 2.3.4 GB rom every time it does this. I don't know how to get to CWM recovery if I can't boot into Android itself. Moto's menu Recovery mode option doesn't point to the 2nd init that CWM Recovery uses if I understand it correctly. I know an earlier version of the bootstrap used PB Tools to point to CWM Recovery. I think this is due in part to the fact that the D3 bootloader is still locked... I wish they would just unlock the dam thing...
I just want to know is there a way to get to recovery without booting into android if the key combo used during boot up doesn't work, (Power + X or M key for me)? In my case I can only get to Recovery by having CM9 reboot or using the BootStrap installer to do it. More often than not using rom manager or other recovery switch apps lead to the Android Exclamation screen.
I'm getting tired of the phone activation wait music every time I have to do this...
Also no one seems to mention this problem in Hashcode's CM9 DEV topic and I can't post there yet.
Jsonic said:
Ever since CM9 went into its first Beta, I wiped and installed it in place of the CM9 Alpha builds I used previously on my Droid 3 XT862, a CDMA phone for which CM9 requires no patches to run as I understand it. Ever since the nightlies started rolling out, every attempt I've made to install them has left me with one of two situations. If I install a CM9 nightly and the latest corresponding GApps pack, without wiping it gets stuck at the "Upgrading Android" screen saying "Starting Applications" forever. If I wipe and install a CM9 nightly and the latest corresponding GApps pack, the phone never passes the Motorola "Dual Core Technology" screen. I end up flashing back to complete stock (requires activation and rooting) Motorola 2.3.4 GB rom every time it does this. I don't know how to get to CWM recovery if I can't boot into Android itself. Moto's menu Recovery mode option doesn't point to the 2nd init that CWM Recovery uses if I understand it correctly. I know an earlier version of the bootstrap used PB Tools to point to CWM Recovery. I think this is due in part to the fact that the D3 bootloader is still locked... I wish they would just unlock the dam thing...
I just want to know is there a way to get to recovery without booting into android if the key combo used during boot up doesn't work, (Power + X or M key for me)? In my case I can only get to Recovery by having CM9 reboot or using the BootStrap installer to do it. More often than not using rom manager or other recovery switch apps lead to the Android Exclamation screen.
I'm getting tired of the phone activation wait music every time I have to do this...
Also no one seems to mention this problem in Hashcode's CM9 DEV topic and I can't post there yet.
Click to expand...
Click to collapse
I can't answer your question, but I know that CM9 is no longer working with recovery bootstrap... You have to use Safestrap. I had CM9 stuck at the dual core logo 3 times before I decided to google it and find this out. Hope that helps you.
Just wanting some advice (if any) to a white line issue I'm having with this tablet. I bought this tablet with Lollipop 5.0.1 already installed. I managed to get it downgraded, rooted, and currently have TWRP installed as well as CM12.1 nightly. The problem I have is that as soon as I install ANY custom recovery (TWRP or CWM recovery) it boots normally at first giving me the LG logo. Then, instead of getting the AT&T logo (or the CM custom boot animation), it gives me a series of white lines spamming from top to bottom of the screen. I know for a fact it has to be software related as when I return to stock KK everything boots fine, giving me the LG logo followed by the AT&T logo. I did NOT use the ADB method. Instead I downgraded using the LG Flash Tool, and a test KDZ file, which allowed me to install Flashify, then TWRP. My problem ONLY begins once I install ANY custom recovery. This process did not unlock my bootloader, however. Could this be my culprit, or would it be something else? Any help is greatly appreciated, and thanks in advance for any help/tips. More information is completely available upon request.
P.S. The white lines eventually disappear when the screen goes to sleep on it's own. I can then press the power button to wake the device which gives me the lock screen as normal. I just want to know if I can get the boot animation working. Everything else works fine.
You found cwm?
I followed a guide to dual boot my Linx7 tablet using the Cube iWork 7 download with Android and Windows 10. I got this working fine and over the last few weeks have setup both how i want them. However, at some point i seem to have lost the ability to choose which OS to boot. Normally I'd turn the tablet on, see the American Megatrends screen then it would boot to the EFI Shell/Bootloader?? which would give me the choice of booting Android or Windows. I get none now and it will just boot to the last used OS.
In Android i noticed an app that is called 'Boot to Windows' which works as expected, reboots into Windows. However when I was booting to Windows, to get back to Android i rebooted about 6 times and just hammered volume down which happened to work and boot it into Android. I'm not afraid to boot back into Windows in case i can't get back into Android.
Does anyone know what I've done, how i can fix it, ideally without having to reinstall both OS's again or is there a way of changing the OS to boot to without the menu (like volume down which i feel shouldn't have worked for me but did)
Any help would be really appreciated as I've searched for hours to find answers without any luck.
Hello,
I'm a long time browser of this forum and have had a lot of luck with ROMs in the past, however, in the spring I bricked my N8013 like something horrible. Long story short, I zeroed the internal SD card and had to rebuild the partition table from scratch as I couldn't find a working PIT at the time. FUN!
Anyway, once it was fixed I was able to get Lineage 14.1-20170305-unofficial-n8013 installed and working....mostly What a relief! MTP didn't work, but WiFi did. One thing I noticed right away was that the Boot Logo, when you first turned the tablet on seems to be referencing some trash space on the internal SD card as there is no logo, only noise or maybe a previous screen (i.e. if I go into download mode and reboot, then the download mode screen is now my boot logo). After the initial POST, the lineage boot screen shows fine, but that's some 10s later.
Regardless, the N8013 hardware does not run lineage very smoothly and Lineage is not optimized for the N8013 - aka **** battery life.
So, I decided to give Android HD Revolution 21 a shot. I used Odin and flashed "High On Android" recovery and installed Android HD Revolution 21 from my external SD card. Easy! Still doesn't resolve the boot image issue, but whatever.
Boot up and I discover that not only does MTP still not work, but neither does WiFi! Bluetooth works for some reason though. So, I took to the forums and tried to resolve the issue.
I tried flashing both sets of stock kernels from here and repeating the install process. Nothing. Additionally, I noticed in the Android Settings inside Android HD Rev. that it shows N8000, however, my tablet is the WiFi only model (N8013EA as stated on the back of the device).
So, TL;DR
-Welcome suggestions on how to resolve MTP and WiFi issues. Currently working in Android HD Revolution but I don't think it's limited to that ROM
-Welcome thoughts on how to fix the Boot Logo issue. I feel like this should be a simple fix, I just don't know where files like this would/should be stored since it exists somewhere in the partition table and now in the ROM.
Well, was able to resolve the WiFi issue by install the Boeffla Kernal from: https://www.boeffla.de/index.php/downloads/eol-kernel-versions
Still looking for help with MTP and the boot logo if anyone has ideas!
I was intrested for installing linux on my phone and found poshmarket os and i saw surface rt as an supported device so i tried to boot and it worked i think
I have made it to this screen, let the tablet sit all night, and it never progressed further. Do you have an update about how it went?
Same but I think the kernal is a problem
PostmarketOS for the Surface 2 is not really usable at the moment...
UPDATE I have been able to create a custom image with pmbootstrap.
However this inage also gets stuck on a with some commands and the last one is always "exiting boot services" different screen but i believe some tweaking in the pmbootstrap will resolve the issue