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
Related
Alright, Ive had my nexus 7 for a while and I want to unlock it and root it. I havent decided what rom to use yet. (Would love input on good ones, 4.2.x) I plan on using the Motley kernel, but I was wondering in what order should I flash them in, should I flash the rom and gapps then let it boot up and settle in, and then flash the kernel? Or the opposite? (Kernel first, then rom). Just looking for an answer to the flashing order and feedback on good 4.2.x roms, I was thinking either Paranoid 2.99 Beta or CM10 Nightlies
ROM goes first; otherwise your custom kernel will be overwritten.
Sent from my Nexus 7 using Tapatalk HD
Alright thank you, now Im just wondering about a good 4.2.x rom
Ok Ive unlocked and root my nexus, and I try installing a custom recovery (TWRP) and then when I go to the reboot recovery option in Nexus toolkit, it boots to a droid with a red triangle, and wont do anything, I have to hold down the button till it restarts..
I went through most of the the Nakasig Tilapia ROMs (Nexus 7 3G) here on XDA and decided on this one from my signature (temasek's).
Also, tried some kernels (faux, motley) and decided on the franco one (based on the Battery Saving skills I saw in a study-type post).
Why this temasek's? I was searching and didn't find a ROM more flexible than the CyanogenMod at the moment. I may be mistaking (this is my oppinion).
It has a lot of options and customization you can do, BUT, this temasek's ROM has all of these and also his own features ( Tethering and portable hotspot was what I was seeking, you can also check the rest out).
Hope that helped. :silly:
Purevulcan0 said:
Ok Ive unlocked and root my nexus, and I try installing a custom recovery (TWRP) and then when I go to the reboot recovery option in Nexus toolkit, it boots to a droid with a red triangle, and wont do anything, I have to hold down the button till it restarts..
Click to expand...
Click to collapse
Sounds like you didn't actually flash a recovery.
Sent from my Nexus 7 using Tapatalk HD
I was wondering if it did, Im using Nexus Toolkit and it acts like it does something but it didnt seem to do anything and I still get the red triangle, what can I do?
Purevulcan0 said:
I was wondering if it did, Im using Nexus Toolkit and it acts like it does something but it didnt seem to do anything and I still get the red triangle, what can I do?
Click to expand...
Click to collapse
Ditch the toolkit first of all. The best way would be to use fastboot, but Goomanager and ROM Manager can flash them from within Android.
Sent from my Nexus 7 using Tapatalk HD
if running stock, just with root, you have to rename or delete the recovery-from-boot.p file. or the stock recovery will replace your custom recovery after every boot, every time.
from twrps' site.. http://www.teamw.in/project/twrp2/103
The stock ROM*will automatically replace TWRP with the stock recovery.* To prevent the stock ROM*from replacing TWRP, boot TWRP, go to the mount menu and mount system, press the home button, then press Advanced ->*File Manager.* Browse to /system and select the file named recovery-from-boot.p then choose to rename the file to recovery-from-boot.bak.
Click to expand...
Click to collapse
I grabbed ROM Manager from the play store and flashed it, Its working thanks and whats sideload, I saw that as an option
Purevulcan0 said:
I grabbed ROM Manager from the play store and flashed it, Its working thanks and whats sideload, I saw that as an option
Click to expand...
Click to collapse
to transfer from one device to another, computer to nexus 7.
Thank all of you so much, all probably just stay stock for a few days but I'm might switch, do you guys have any recommendation of kernels and Roms?
I'd like to recommend u to see the following thread to select your 1st ROM and Kernel.
[INDEX]All In One Nexus 7 Index Thread *JAN 3rd 2013
http://forum.xda-developers.com/showthread.php?t=2070419
Regarding ROM, personally I love ParanoidAndroid because of its customizability. But as your 1st choice, how about CM10?
About Kernel, I love Franco #25 for 4.1 and #31 for 4.2. To select Kernel, pls refer to the following thread.
[GUIDE] *NEW* 4.2.1 RESULTS! N7 'Best' Kernel? (Performance & Battery Tests)
http://forum.xda-developers.com/showthread.php?p=31620793
enjoy
Ok Ive been running Motley kernel for around a day now and its amazing, but I was thinking about testing cm 10.1, but I was wondering when I factory reset and clear the data, will it erase my Nandroid backup?
Purevulcan0 said:
Ok Ive been running Motley kernel for around a day now and its amazing, but I was thinking about testing cm 10.1, but I was wondering when I factory reset and clear the data, will it erase my Nandroid backup?
Click to expand...
Click to collapse
Just do a factory reset don't erase data or however it's worded. All the same it's never a bad idea to have a Nandroid on your PC or a USB drive.
davisac said:
Just do a factory reset don't erase data or however it's worded. All the same it's never a bad idea to have a Nandroid on your PC or a USB drive.
Click to expand...
Click to collapse
How do you access the backup on the device from the computer, I didn't think you could see root directory natively
Purevulcan0 said:
How do you access the backup on the device from the computer, I didn't think you could see root directory natively
Click to expand...
Click to collapse
TWRP saves the backup to the /SD/ and I thought CWM did as well. Even if it doesn't, copy the backup from the root to the /SD/ with your tablet then transfer to the computer.
Alright cool, I just flashed CM 10.1, what kernels work with it?
Purevulcan0 said:
Alright cool, I just flashed CM 10.1, what kernels work with it?
Click to expand...
Click to collapse
In other words Im wondering if I can flash Motley Kernel, the one I had before because I really liked it
Purevulcan0 said:
In other words Im wondering if I can flash Motley Kernel, the one I had before because I really liked it
Click to expand...
Click to collapse
Disregard all of that lol, I flashed over motley on Cm10.1 and it performs beautifully
I've been using multirom without problems for the past week (even loaded webOS and Ubuntu on it). However, today I flashed Franco r47 kernel and after rebooting, the rom selection screen would not display anymore. And instead, it would boot the internal rom immediately after the Google logo.
Checking TWRP, it still has the multirom option under Advanced.
Has anyone else experienced this or knows what I can do?
no one? can't really post this in the multirom thread
I have got the same question, any other solutions?
thunderbolt.dash said:
I have got the same question, any other solutions?
Click to expand...
Click to collapse
I've flashed multirom_v8_n7-signed.zip again and it seems to have fixed the issue. :good:
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
[Q] How can I remove custom recovery? Ran into some problems and want to "start over"
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.
_tyler_ said:
So I recently rooted my VZW G2 thanks to wyrdtrtle on IRC (HUGE thanks, btw). I had lots of issues and he helped me out for about 3ish hours. It ended off with me asking him which recovery I should use (CWM vs TWRP) and he said he uses TWRP for it's touch interface, so I went ahead and installed it via FreeGee. Fast forward to yesterday night, I decide to flash CM 10.2 (I'd prefer starting out on a guaranteed stable build instead of a nightly since I've been on Android since January and know very little). I find and watch a tutorial (can't link since i am a new user) and proceed to download the CM10.2 zip and the gapps. After a few seconds, it fails. I try looking for more tutorials, specifically for G2 and CM and it still fails. I then tried installing CWM (maybe TWRP was the problem?) via FreeGee and again, flashing failed. I thought it might be CM and I was going to try ParanoidAndroid or Mahdi (think that's the name) and see if that works but I now want to remove both recoveries and "restart" as if I had just rooted my phone. Decided to post here before I potentially brick my phone. Sorry for wall of text, but any help is appreciated.
Click to expand...
Click to collapse
how'd you root your phone first? through what?
MuzakaTheBeast said:
how'd you root your phone first? through what?
Click to expand...
Click to collapse
I followed the IORoot22 instructions along with clarification from wyrdtrtle on IRC
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Oh, right, I remember reading that Loki bypasses locked Bootloaders (which somehow led me to think only CWM had Loki support and would work when TWRP didn't). I'm gonna try this now.
spinninbsod said:
Try patching cm10.2 with freegee in the menu with three lines and you should see something called update Loki in zip tap that and go to where you placed cm and tap cm and it will take a couple minutes to patch if it fails try to redownload cm but do not skip previous steps it will softbrick your phone.
I DO NOT take responsibility for bricks soft/hard bricks when you root,flash ROMs you risk bricking your device
Happy modding welcome to the world of android
Sent from my LG-VS980 using Tapatalk
Click to expand...
Click to collapse
Didn't work. Still get an error saying it failed
_tyler_ said:
Didn't work. Still get an error saying it failed
Click to expand...
Click to collapse
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying
spinninbsod said:
did you try redownloading cm 10.2 downloads get corrupted sometimes it is very annoying
Click to expand...
Click to collapse
apparently the 10.2 rom i was trying to flash wasn't compatible with my phone (not too sure on the specifics) but I tried the latest nightly for cm11 and I've been running it since last night.
Hey guys,
I've known about this whole modding thingy going on for android phones, and i've decided to give it a shot myself.
I took a backup of everything (copied everything.. didn't use any app for that. not too smart of me..)
Anyway,
I looked around and decided to install Hells Core kernel on my phone, along with Cyanogen Mod.
So after installing the SDK on my computer, unlocking the phone, rooting the phone with SuperSU and Clockwork Mod,
I got to installing the kernel.
I put it on my phone, rebooted into recovery mode, reset all data (dalvik cache and all..)
then I installed the kernel from a zip file I put on the phone, and it all went smoothly.
However, when I reboot my phone - it's all messed up!
The screen is all half yellow, and half is just black - not even text.
In the yellow part, you can hardly tell that it's the first welcome screen - because the text is too big to fit the screen.
Anyway, the whole phone is fk3d up.
I just wanna put it back to the original stock kernel and rom...
How do I do that now?
Thanks a lot guys..
This is urgent >_<
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
jd1639 said:
Just flash cm again without doing any wipes. It'll get rid of the kernel
Sent from my Nexus 5
Click to expand...
Click to collapse
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
capzul said:
I haven't got CM on my phone,
and I can't connect it to the computer because it needs get past the welcome screen - which I can't click on any buttons!
****EDIT ****
nvm, I managed to do it
I used android toolkit, and now the computer can access the phone's internal memory.
Thanks!
***** EDIT #2 ******
Nop, doesn't work yet...
when I copy the other kernels zip's, everything seems okay
but when I reboot my nexus to install from the recovery mode, the zip are corrupted - and when I access from my computer it shows they're 0 bytes.
as if nothing was copied..
What can I do ???
***** EDIT #3 ******
Well, managed to get the phone to work!
Not getting anywhere near Hellscore now..
What I did was run 'install zip from sideload', and then from the pc I used 'adb sideload <FRANCOROCKS>.zip', and that worked
Phone's now up and running, installing my apps again.. lol
Scared to change the ROM though.. after all this >_<
Click to expand...
Click to collapse
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
hassi4042 said:
Because you did all this the wrong way. Learn and study before flashing anything, it's not about some simple zip flash. that simple zip file can brick your phone if flashed without knowledge.
hells core kernal is not a CM based kernal that's why you got broken screen. there is a separate thread for cm based kernals. do flash a custom rom like Mahdi slimkat etc they offer great features but only after fully understanding what you are doing
Click to expand...
Click to collapse
Well, I flashed the kernel before I put the ROM, so this happened with HC kernel on stock ROM.
:X
you probably flashed the wrong version of the kernel
You did get the CM Version of Hells Core, right?
This happens to me all the time, just reflash the Roms .zip and you'll be fine.
Sorry to say that, but from your comments it's obvious that you messed up with wrong kernel's version and is not a fault of this specific kernel.
Also the zero kb downloads show bad downloads on your side again.
Sent from my ONDA A9 Core4
capzul said:
Hey guys,
I've known about this whole modding thingy going on for android phones,
Click to expand...
Click to collapse
Lol
Sent from my Nexus 4 using Tapatalk