[Q] How do you boot multiple roms on Nexus 10 - Nexus 10 Q&A, Help & Troubleshooting

On my other android devices I can use bootmanager but not for the Nexus 10. How can I boot multiple roms on Nexus 10 without losing data from another rom.

bnichs5 said:
On my other android devices I can use bootmanager but not for the Nexus 10. How can I boot multiple roms on Nexus 10 without losing data from another rom.
Click to expand...
Click to collapse
If you develop a boot manager for the Nexus 10, you can use that :good:
Currently though, it doesn't look like a boot manager exists.

bnichs5 said:
On my other android devices I can use bootmanager but not for the Nexus 10. How can I boot multiple roms on Nexus 10 without losing data from another rom.
Click to expand...
Click to collapse
The closest to multiboot on the Nexus 10 is to use the backup/restore features of a recovery program such as TWRP. I've used this to boot between custom ROMs and even the Ubuntu Phone OS. The Nexus 10 is great for using this method as its I/O speeds are so fast. The recovery backup includes all your data and settings.
In practice I've found this to be a very workable substitute for the real thing.

Related

[Q] dual booting

I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App
The short answer is: no.
mysteryemotionz said:
I know the winmo phones can dual boot winmo and android. They boor android from the sdcard.
Im wondering if we can get are phones to dual boot so we can have are working rom ect.... And we can dual boot into the secondary android from the sd card to test are mods
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?
muyoso said:
They can dual boot because Android is an open OS and is free. It would be illegal to put Winmo on our devices without paying for the proper license.
Also, for what possible reason would you even want to do this? To use as a reminder of how primitive Winmo looks and was compared to Android?
Click to expand...
Click to collapse
I wanna dual boot with 2 separate sets of android for testing purposes
Sent from my Emotionless Beast of an Epic using the XDA App
I think yes, it would be possible. I wouldn't know how, but its been done on android before, and there is an alpha version being worked on already for the Sammy Moment at SDX and Samdroid.
And if this could be achieved it would be a great to help to developers.
I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.
RKight said:
I think I would like it just for the purpose of trying out new roms without having to give up my current rom, in case I don't like the new one.
Click to expand...
Click to collapse
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I'm aware of that process but if I'm just wanting to tinker with a new rom, I really don't want to go through all that trouble. If I want to try a new Linux distro on my PC, I'm not going to ghost it, install the new distro, then restore the old image later. I'm going to throw the new distro on a second hard drive and dual boot while I decide if I like it. That way, I have a known stable OS, configured the way I want, just a reboot away.
mysteryemotionz said:
Certain themes with the battery percentage mode will cause boot problems from recovery
Sent from my Emotionless Beast of an Epic using the XDA App
Click to expand...
Click to collapse
I have noticed this as well, and a flash with odin plus reinstalling clockworkmod is the only thing that prevents it from corrupting your backups for future use.
daddymikey1975 said:
if you do a full backup, flash a new ROM, restore data (only) and you don't like the new ROM, you can go back into recovery, restore full backup and voila.. you're back to the ROM you just backed up.
takes 3 minutes to do all this.
no need for dual boot IMO
Click to expand...
Click to collapse
I don't know. That's fine if you just want to try out a ROM one time, and quickly, or if you can do without your main ROM for a long time. I had a windows phone before I switched to Android. Having the "dual boot" was key to my switching to Android. I was able to install Android, set it up the way I wanted to (which took lots of time) and "play" with it whenever I had time, but at other times I needed to be able to switch back to my main phone. I'd switch a couple times a day sometimes (just a single click to go either way). After a couple of weeks of being able to work with Android I knew I'd be happy switching.
You could do something like this with backups and restores, but I honestly think it would get overly cumbersome. You'd have to backup your main ROM and then the second ROM. Every time you changed a setting or moved something around in either ROM you'd have to remember to make a new backup, or the next time you switched into that ROM all of your changes would be reverted back.
In any case, I don't know how possible it is to have dual boot, but I can certainly see a lot of advantages for some people.
HARET is what makes the WinMo android boot possible and is based on work done with soft/hard SPL. No Android equiv to HARET exists yet. However, a lot of work is happening with HBOOT due to the Vision G2 eMMC situation. I wouldn't be too far off if I were to speculate that an android HARET may be in our future.
Go check out this thread from the Eris forums. - Dual boot recovery hack
As I'm not intimately familiar with the inner workings of Clockwork, I don't know how plausible it is on the DX. It could either be really easy to port since we're already bootstrapped, or nearly impossible. That's a problem for a dev much smarter than me to conquer.
I will say that I tried it out on my Eris. The stock class 2 card was unbearably slow, a class 4 was tolerable, and a class 6 (which cost a small fortune) ran as if it was installed internally. Kinda neat, but not terribly practical for daily use.

Weirdest way to brick?

So I have a 32GB Nexus 7 on Rom SBean. (4.2.1) I installed Chainfire and was reading through the supported devices, and I thought nexus 7 was supported so I installed it. It then rebooted my Nexus 7 and was on a bootloop. I thought hmm, Time to flash a clean rom. So I turned off the nexus and was trying to boot to rom with my button keys. I held them for a good long 1 minute and nothing. Did I screw up? or can I fix this issue?
help is very much appreciated.
macmac49 said:
So I have a 32GB Nexus 7 on Rom SBean. (4.2.1) I installed Chainfire and was reading through the supported devices, and I thought nexus 7 was supported so I installed it. It then rebooted my Nexus 7 and was on a bootloop. I thought hmm, Time to flash a clean rom. So I turned off the nexus and was trying to boot to rom with my button keys. I held them for a good long 1 minute and nothing. Did I screw up? or can I fix this issue?
help is very much appreciated.
Click to expand...
Click to collapse
boot into your bootloader, then into recovery, wipe your data(factory reset), then reflash your rom. why would you want to use chainfire on your nexus 7, its a quad core device? you dont need to make these apps/games think that you have another device.
simms22 said:
boot into your bootloader, then into recovery, wipe your data(factory reset), then reflash your rom. why would you want to use chainfire on your nexus 7, its a quad core device? you dont need to make these apps/games think that you have another device.
Click to expand...
Click to collapse
Alright, I got it all done. I was trying to increase performance with my kindle because it was very laggy. I have no clue why, but it was. Thanks for your help.
macmac49 said:
Alright, I got it all done. I was trying to increase performance with my kindle because it was very laggy. I have no clue why, but it was. Thanks for your help.
Click to expand...
Click to collapse
wait, are we talking about a kindle or a n7

[Q] Rom and Kernel Questions

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

My Custom Mod Misadventure

Okay, I gave this a shot.
I used the Nexus Root Toolkit and rooting the thing went pretty well. I downloaded a Cyanogenmod rom, actually 2, and that was the start of my issues I think. I accidentally loaded the nightly instead of the stable.
I also didn't realize that adb would not boot anymore with 4.2.2 so I was stuck. I checked in the settings of the Nexus and it loaded up various roms you could use. I would select them and it would start to load, but then show the error message with the little android on his back.
I followed the tutorial "Root and Install CWM On Nexus 7 Running JB 4.2.2" in an attempt to get some control back and it went well until I was supposed to find the zip on the device. I had copied it over, separate from any folder, but I could not find it while in bootloader.
I ended up manually putting it in bootloader and using the Nexus Root Toolkit to restore the stock rom.
I liked certain things about the custom rom, but it was a pain not having the Google Apps, and I could not get the Gapps to install either.
Obviously I knew just enough to get halfway there. I am not sure when I will try this again, although I would like to learn more. I guess I better read some more tutorials on here.
Why didn't you just flash gapps in recovery?
Sent from my Nexus 7 using Tapatalk
Well first off there isn't Android 4.2.2 for the new Nexus 7, you must have followed a tutorial for the old one.
I used the nexus 7 toolkit.... There lies your problem
You used a toolkit not knowing what you're actually doing. Or what any of the terms mean / how and what they're used for etc.
Adb doesn't boot... Um what. Fastboot couldn't flash cm11...um what 4.2.2 um what

Nexus 10 stock rom

Hello, I got cyanogenmod installed on my nexus 10 atm, it came with it, when I bought it second hand, but now I want to install the newest stock rom(5.1), how can I do that, do I install it from recovery like a custom rom, or via pc?
braien334 said:
Hello, I got cyanogenmod installed on my nexus 10 atm, it came with it, when I bought it second hand, but now I want to install the newest stock rom(5.1), how can I do that, do I install it from recovery like a custom rom, or via pc?
Click to expand...
Click to collapse
Follow Method 2 in the OP from this thread: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, all steps are the same for all the Nexus devices. Just make sure you have the correct factory image for the N10. Not sure if you have to wipe userdata when going from CM to stock, but I probably would just to start fresh and make sure there are no issues down the road.

Categories

Resources