Hi,
I've quite a problem with setting up ubuntu on MultiROM. I've got the required kernel installed. The roms are installing properly. Just when I want to boot it, there shows the google icon twice and then goes back to MultiRom. I tried to install ubuntu desktop (newest) and ubuntu touch, always with the same result.... Any idea how to solve this?
I believe that's rather MultiROM problem because I have the same problem with BodhiLinux... Can previous using linuxonandroid affect MultiROM?
Are you sure you are using the correct kernel and flashed Ubuntu through the correct modified recovery?
I'm not sure, what was wrong... I installed everything twice again (first time it didn't work) and ubuntu installed and booting (still not working correctly, but that is always something ) Anyway, thank you for your answer without it I wouldn't have motivation to do it the second time.
Lol you're welcome
Related
hey guys, i am having a problem getting the dualboot app to start when i actually boot my tilt 2
yes, i already have android installed and working
yes, gen.y dualboot works if i manually start it and it will boot linux and then android
but, my problem is that i want it to start how its supposed to (when i boot the phone)
i haven't found anything about anyone having problems getting the dualboot app to boot, but only problems with getting the dualboot app to boot android, which is not my problem, so could someone help me?
its probably something obvious to someone else, but i can't figure it out
and i know that i don't "need" to have it start when i boot the phone, but then what would be the point of the app?
nicc51591 said:
hey guys, i am having a problem getting the dualboot app to start when i actually boot my tilt 2
yes, i already have android installed and working
yes, gen.y dualboot works if i manually start it and it will boot linux and then android
but, my problem is that i want it to start how its supposed to (when i boot the phone)
i haven't found anything about anyone having problems getting the dualboot app to boot, but only problems with getting the dualboot app to boot android, which is not my problem, so could someone help me?
its probably something obvious to someone else, but i can't figure it out
and i know that i don't "need" to have it start when i boot the phone, but then what would be the point of the app?
Click to expand...
Click to collapse
Probably don't have it installed correctly on the phone if it's not in your main memory but on your memory stick it wont interrupt the boot sequence.
help
i have mine installed but the volume doesn't work
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
destructo322 said:
Hello XDA,
First time posting so I have to ask in Q&A rather than the thread for MultiROM itself. I've been to these forums quite a few times for rooting and unlocking other's devices, but now that I have a Nexus 7 myself, it's time to start messing around with it.
So the situation for my problem is that I have successfully installed MultiROM and was able to boot up my stock image fine, but when I installed Cyanogenmod 10.0.0, the screen automatically goes to the boot screen for Cyanogenmod rather than asking which ROM to boot and then just hangs on that boot screen forever.
I have not used the kexec hardboot patches for anything yet so it can be that I should be using those somewhere along in the process.
Also, how do I go about uninstalling MultiROM so that I can start all over again? Do I just go into TWRP and hit "install" and choose the stock image for 4.2.1?
Click to expand...
Click to collapse
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Mac of York said:
It's overwriting the kernel with one of its own... that's the only thing I can think of. Flash a kernel that has MultiROM support like m or motley.
Click to expand...
Click to collapse
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
destructo322 said:
Does this mean that I should find a version of CM that has one of those kernels? Or do i simply flash the kernel by itself and that would overwrite the CM kernel so that the problem would be resolved?
Also I tried installing Kaos Droid and chose the option to install the M kernel before CM actually and I remember that it also would just boot to a completely black screen and nothing past that. So i'm not sure if it's the kernel. But i did just successfully go back to stock and rooted again so that I will try out your suggestions tomorrow. Thanks.
Click to expand...
Click to collapse
You can flash the kernel separately and it'll be fine.
Sent from my Nexus 7 using Tapatalk HD
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
hecksagon said:
I had flashed CM10 but forgot to reboot into fastboot and boot the CM10 kernel. As the thing was bootlooping, I was able to successfully do an adb reboot recovery, completely skipping using a USB keyboard and pressing Ctrl - Print Screen - I key combination normally used to get to recovery. Apparently at some point, even if the rom isn't booting, the kernel somehow starts adb. Anybody else have any luck with this or know any reason why this even worked? If this is the normal way for android to boot, maybe it would be possible to still get into recovery even if we flash a different kernel.
Click to expand...
Click to collapse
Interesting I wonder if its repeatable? I guess its will be hard to test unless you already messed up, nobodys gonna mess up on purpose just to try this out without a hardware recovery option but maybe someone who messes up on accident will report back here on what they found out.
Wasn't able to repeat it on the Ouya kernel with CM ROM installed but it seems to work all the time if you get a boot loop in CM10 kernel and CM ROM. I'm still not feeling safe enough to actually flash the CM kernel, so I am still using fast boot to boot the kernel from a laptop.
On a side note, I do have xbmc set up as my launcher and have list of working skins that can launch android apps from. Once I figure out how to get the crazy CPU usage I am getting worked out I plan to make a guide for a full media center.
Hey all, I was installing MultiRom so that I could try out different roms with the primary purpose of getting GameCih working on my Nexus 7 (1st Gen). I went through the first steps but got the "Kernel: doesn't have kexec-hardboot patch!" message. So following the guide at http://forum.xda-developers.com/showthread.php?t=2457063, I went ahead to patch that kernel. However, when I hit install, I realized it said it was a 4.1 stock kernel. The install ran and when the boot started, it just sat on the colorful X for 10-15 minutes. I booted into recovery and tried to figure out a way to get the proper kernel on the device and install that, but had no luck. Unfortunately, I backed up using the Wugs Nexus Toolkit and forgot to do it within the recovery on the device. So are my only options to wipe the device and start over or can I install the proper kernel, or is there another solution? Thanks so much for your help.
Sorry for the double post, but I waited several days to reply. I ended up going ahead and doing a wipe. It kept the rom, but did seem to fix the issue. I also tried installing the AOSP 4.2.2 ROM in MultiRom, but that one isn't working. And once I did that, several of the apps stopped working in the PAC Rom. It doesn't look like I'm going to get much help here, but I thought I'd at least respond to my original post
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
krkeco said:
Hi, I wanted to reply in the multirom thread but can't because I am still too newb. Hopefully someone here can point me in the right direction? I've tried everything I know how to do. I really appreciate any help I can get!
So here is my problem. I downloaded multirom for my n4, then I updated. I reopened, and noticed I had the red line of text saying I was missing a kernal or something, so I clicked that and install (so instead of just updating the app I updated my kernal? and I also clicked update recovery). I needed to finish in recovery mode so it rebooted. Then it soft bricked. It goes to the load screen (with countdown timer) and then just black screens indefinitely tmk (5+ minutes of adhd agony). I had already downloaded cm 10.2 and gapps on the device in preparation for multirom, so I rebooted into recovery again, launched multirom and added cm 10.2 with gapps. I first tried with sharing kernal because I don't have my laptop to install 4.3 .tar, but that failed, so I installed ROM without sharing kernal. It runs fine, except I can't use bluetooth or wifi... so it really doesn't run fine =/ everything else seems okay though.
All my data is already backed up on my hdd so no worries on losing that, but I would like my phone functioning sooner than later.
I'm on vacation and don't have laptop with me, any ideas on how I can fix this? I have my Nexus 7 too, so I can download stuff, but I don't know how to:
a) install 4.3 so I can get cm 10.2 fully running?
b) reinstall 4.4.2 to stock (I tried factory reset but it didn't do anything either)
I think the biggest problem is lack of laptop because I could easily just reset the phone with that and run my nandroid (which is on laptop too.... ftl) but if there is a solution please let me know! Thanks!!!
Click to expand...
Click to collapse
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Thanks for the quick reply, is that the 27 or the 33 / 84 download?
sites.google.com/site/bpearuploads/
Or does it not matter?
opssemnik said:
WHY DID THE ERROR HAPPENED?:Because multirom app sets the default kernel to 4.2.2 one, since you werent on 4.2.2 it soft bricked.
DO I NEED TO REINSTALL STOCK TO GET CM FULLY WORKING?: Nope, just search in the general section of our device, for the hybrid modem thread, download the hybrid .84 and flash on recovery
PS: I think you will need OTG to pass the file from your n7 to your n4 since no bluetooh,no data and no wifi....
Or search like crazy around google to see if there is a way to pass files thru nfc
Click to expand...
Click to collapse
Got it figured out thanks to your help!