Boot Loader for ROM's??? - Droid Eris Android Development

Would it be possible to make a boot loader GUI for the eris to easily select between a few ROM's. Does something like this already exist?

have you seen this?
http://forum.xda-developers.com/showthread.php?t=661413
it will probably do what you are looking for

Kinda... I searched but seemed to have missed that. I'm thinking of something more like a GUI that prompts you when you turn your phone on without booting into recovery. It would then give you the option to choose what ROM you wanted to boot. All this without having to navigate through a recovery boot screen.

rkymtnbum said:
Kinda... I searched but seemed to have missed that. I'm thinking of something more like a GUI that prompts you when you turn your phone on without booting into recovery. It would then give you the option to choose what ROM you wanted to boot. All this without having to navigate through a recovery boot screen.
Click to expand...
Click to collapse
You are referring to a "dual-boot" setup which is highly improbable on the Eris. The Eris is short on internal memory to start with, but to add a dual-boot you would need to partition off the space even more. There just isn't enough space to do that effectively. IMO
Just get comfortable with Recovery and the options are there. You could have nand backups of every rom available and switch them that way if you really wanted.

The problem is, you wouldn't be able to have multiple roms loaded on the phone at the same time (well, at least not easily). There wouldn't be enough space on the phone. The only way I could see doing it would be to create the current back up/restore steps, but that seems like it'd be terribly slow.

FunkyFender said:
The problem is, you wouldn't be able to have multiple roms loaded on the phone at the same time (well, at least not easily). There wouldn't be enough space on the phone. The only way I could see doing it would be to create the current back up/restore steps, but that seems like it'd be terribly slow.
Click to expand...
Click to collapse
I figured that might have been the case. Nand backups would take more time than I would want at boot. Internal space is a little too limited... your right.. I overlooked that. It would have been cool though haha.

Related

just rooted hero and tried some roms but wanting stock back?

I rooted my hero and tried out a few roms but non seem to polished yet so was wanting to finda stock rom while keeping root of course, Id mainly like the stock one with the ability to run apps from sd card.
have you tried fresh 1.0 its pretty close to stock. If you want you can just return to your nandroid that you did after you rooted but before u installed any ROMs and thats basically a rooted Stock ROM
yeah im gonna try that because now I cant do anything, I hope I didnt mess up my phone, no matter the update I apply(and I try wiping to) it just sits at the htc screen.
How do you apply the nandroid backup?
I just basically have the folder with everything in it on desktop
boot into recovery mode and go down to the listing that says Nandroid Restore.
also when you install a new ROM it isnt rare for it to take up to 10 minutes to boot.
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Nandroid Restore. I assume you did make a nandroid right after you successfully rooted correct?
yeah its doing the nand. restore now. hopefully all is well. just waiting for it to finish restore.
ive never had a problem rooting, my g1 always worked fine.
ah phew, thankfully I had a backup. and i was thinking, is their honestly any reason to go to a rom atm? I mean for my g1 I used one because it was faster, quicker, more features, and had apps2sd.
but atm for hero atm doesnt look like a top notch one yet?
also can the stock rom with root do apps2sd?
and easiest way?
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
samrozzi said:
yeah i mean id wait 30-even 45 mins, it just sits at the htc screen, and sometimes the lock screen will even appear, i jsut kept getting errors for force close
and id get to a permission screen, itd say like overclock at the top and ask for permission?
any idea what that is and what todo?
Click to expand...
Click to collapse
obelisk79 said:
firstboot scripts can keep your phone at the htc boot animation for 5-10 minutes. I don't know if you waited that long or not but generally I have seen that first boot with a custom rom take a little while to get things setup right.
Click to expand...
Click to collapse
He already stated he waited way more than 10 mins....
Fresh 1.0 makes your phone quicker, I wasn't going to ROM until a really customized and polished one came along but after trying Fresh, I'd highly recommend it.

[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.

Quick boot question

I'm sure this has been covered before, but I'm not having luck digging through thousands of threads to find my answer. Its quick and easy for someone who knows more then I do.
I have a T-Mobile US HD2. I've flashed a custom rom of windows (latest version of Core) and I'm trying to run the latest version of Core Droid.
I've been able to install and boot up into Android just fine.....just once though. After the install process when it boots into Android, if I shut off the phone, restart it....blah blah blah it will automatically go back into Windows....and then I have to delete all the Android files and start new.
I've tried using this boot loader http://forum.xda-developers.com/showthread.php?t=733752
My options are set to have Android as the default, 30 second delay to let me have a chance to get into Windows incase I ever wanted too, and I have /android set as the Android folder. When I orignally copied all the files to my flash card, I put them in a folder on root called Android. As well, I've done all this on a freshly formatted SD card.
I've tried this several times with a few different WinMO Roms. I've tried a couple different distros of Android but without any better luck. Core seems to be the only one I can actually get to boot.
Please, any help would be great. I know I'm just missing something quick and simple here, but since this is something that I don't know much about I'm kind of stuck
EDIT :
I should also add that I've tried installing the boot loader both before and after my Android install. It doesn't make a difference either way.
Why do you have to delete Android and start again? Booting back into Windows is correct, of course, but you've not explained what actually goes wrong.
Sent from my HTC HD2 using XDA App
It seems like Droid wants to go through the whole install process again. It will sit there and do absolutely nothing (I left it sitting overnight on the black HTC screen that shows up when first putting on droid).... The only way I can get back into droid is if I format the SD card and start from scratch. Then if I turn off the phone or reboot it I have to do everything all over again.
I'm trying to just boot into Droid when I turn on my phone without having to worry about Windows. I don't mind a dual boot option. I just don't want to use Windows anymore
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
johncmolyneux said:
The only thing I can suggest is trying a different Android build. Just get one running and then reset your phone to make sure you can restart Android again. Worry about the bootloader later.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
It seems to be working OK now. I re-flashed Windows and did everything from scratch. Set up the boot loader again and things seem to be ok.
What would you suggest as far as what build to use. I know this is kinda a touchy subject, but can you give me me pros/cons of the big ones?
I've NEVER used Android before so I'm pretty new to this
Dude, there is plenty of threads, even recent ones that already exhaust that question to the full, all you need to do is read them.

[Q] Little help here.....

Phone shut down, will only boot to MAGLDR screen now and errors out when you try to get to android. The error is:
"sd kernel open failed"
Any ideas on where I should go from here?
Thanks
Wood
Was it successfully running Android before it shut down?
NAND or SD?
What ROM?
What did you do before it shut down, that got you to this point?
As much information about the events and circumstances leading up to your current situation will help others to help you, it's probably something simple why it's not working, but you have to be specific and as detailed as possible to let everyone know exactly whats going on with your phone
huggs said:
Was it successfully running Android before it shut down?
NAND or SD?
What ROM?
What did you do before it shut down, that got you to this point?
As much information about the events and circumstances leading up to your current situation will help others to help you, it's probably something simple why it's not working, but you have to be specific and as detailed as possible to let everyone know exactly whats going on with your phone
Click to expand...
Click to collapse
Yes it was running, NAND , recovery 400M. Just turned screen on to make a call and it was on MAGLDR screen.
In MAGLDR, go down to services, click on it, choose boot settings, choose boot source, choose Android from NAND, and then choose boot AD NAND from MAGLDR's main menu. It sounds like it's trying to boot Android from the sd card, maybe your pocket changed the settings in the MAGLDR menu.
get error "NAND kernel open failed"
Can you load Clockwork Recovery?
If so, you can restore a backup if you have one, or flash a new kernel and see if that helps. Maybe it is a problem with the kernel, although I doubt it. Here's a kernel you can flash which works well for me:
http://forum.xda-developers.com/showthread.php?t=940823
If the new kernel doesn't get it going again, and you don't have a CWM backup made, then it looks like you're screwed and will have to start over with a fresh ROM. But fortunately Android is pretty easy so set up, so in the worst case scenario, you can be up and running with a new ROM set up fairly quickly.
Always make a full backup in CWM at least once every week or two, so that if something goes bad like this, you can easily restore everything back to the state it was in at the time of the backup.

[Q] Can you help a brother out?

I will post the long version here, mainly because I have nothing better to do.
Here is the situation. I bought a NC about 6 months ago. I rooted it using Auto Nooter. I have no idea what ROM I installed to be honest. I'm very much a novice at this. And I'm quite stupid to boot, I might add. It has worked relatively ok since then. The ROM seemed a bit buggy and I had some initial troubles with constant reboots, in addition to some basic things not working and way bogging the thing down, but in general it was ok. I haven't used it much since unless I was traveling.
Today....I was traveling. Traveling to BFE. As such, I decided to bust out my trusty NC and download a new book while I was waiting for my flight. I did so, and something went a bit haywire. It seems that somehow, without prompting, the device has restored itself to the stock B&N ROM (1.1 maybe?). Yet - the Android OS is still there. For example I can click on my task manager app in the lower left corner of the homescreen and it shows that all of my apps are running and I can even switch to them. But my homescreen is defaulted to the B&N one showing my eBooks and I can't figure out how to get my Android launcher back. I have tried to reboot and it does the Droid boot up but reverts to the same B&N home screen.
I was thinking about trying to update to a new ROM since it had been awhile and I figured there must be something better/more stable out there now - Honeycomb or whatever. I guess this is the kick in the ass that I needed.
So now here I sit in a hotel room in BFE. There are no restaurants open past 9. There are no bars. There IS a Super Wal Mart but I think I'm gonna pass on that.
I figured I would look into this. Where to start? Should I re-set this thing to stock and then just pick a new ROM and re-root? Can I do any of this without having a SD card slot in my laptop - just using a USB cable? Will I lose any eBooks that I downloaded?
I await your sage advice.
rooting actually means gaining super user access to the current android rom. B&N, i believe is Froyo, so you did not install any rom so to speak. you were probably just rooted.
I think the issue is with the launcher and not that it is back to stock. What happens when you long press on the home screen?
If you plan to do anything, you will definitely need an sd card reader.
If you autonootered, then you were running stock, but rooted. With a custom launcher replacing the stock launcher, it sounds like.
At any rate, you were probably hit with the automatic update to B&N 1.2 (which is Android 2.2, iirc.) You almost certainly aren't rooted anymore, but it may allow you to run any apps that you already had downloaded, just from the stock app launcher.
When you get an SD card reader, you can check out Manual Nootering. It's basically the same as the old Auto Nooter, but for B&N 1.2. If you change the rom entirely (install CM7) or just run a different rom from an SD card, you'll avoid having B&N overwrite your root access in the future.
Thanks for the responses. I believe that you are correct. I actually was running 1.0.0. I used auto-nooter to root the thing and had it working with a custom launcher. I don't think it updated to 1.2. In fact I know that it didn't update to 1.2. I am trying to get it to do that right now.
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
I could Super Wal Mart tonight for a SD card reader if I'm feeling frisky.
I've got all kinds of problems.
I went to update to 1.2 from 1.0. I removed my SD card and erased and deregistered device. I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Any advice?
I'd do a full factory reset, then try the update to 1.2 again.
A couple of things about the 1.2 update -- do not unzip the update file or rename it. Just drop it as-is into the nook. And make sure to eject the nook from your computer and unplug it.
Thank you aka. I got it to take. I am now at 1.2. Now back to square 1(.2). Any help on this?
Baboontyme said:
I would like to install a new ROM or root or do something after it updates to 1.2 so that I have access to the Android market. What is my best way to do this? Should I just root again from 1.2? Should I install this CM7?
Can you help me understand the differences? Thanks again.
Click to expand...
Click to collapse
Baboontyme said:
I booted it back up and it thinks it's a phone. I put the 1.2 file in the root drive via USB, as I have read over and over that the thing should recognize the 1.2 file and reboot itself. It's not working. I erased and deregistered again. same deal.
Click to expand...
Click to collapse
ETA: lol, congratulations! I guess just skip to that link at the end.
I'd agree with akaCat that you should do a factory reset, BUT you can only do that if you still have the stock recovery utility, and it seems possible that you do not. Try to get the NC to reset by interrupting the boot 8 times. If it doesn't work, you may have installed ClockworkMod Recovery on your Nook Color in place of the stock recovery utility. You may have done so while rooting, or later from the ROM Manager app, perhaps even by accident.
Have you attempted to boot to recovery by holding down "n" while you power on the device, and continuing to hold power + n for about six seconds (1-one-thousand, 2-one-thousand, etc), then releasing both? If so, do you get a factory reset dialog (series of yes/no options) or a longer menu including items like "mounting and storage" and "flash zip from sd card?" If you get the longer menu, then that's ClockworkMod Recovery, and neither the 8-failed-boots-reset nor the automatic update are going to work.
If you do have ClockworkMod Recovery, don't do anything yet. Hopefully somewhere on the screen it tells you the version number, in the format 3.0.x.x. Just let us know that version number and power off the NC.
If you still have the stock recovery utility, then do the factory reset, boot into the stock OS, connect USB, drop the update file straight on the Nook (not in any folders), safely remove the NC from your PC, and let it sit. Hopefully it will reboot itself.
If not, the next step is probably going to involve preparing a bootable ClockworkMod SD and manually installing a CWM-compatible version of the update, or of a different ROM. This article may help you wrap your head around the different options: http://quinxy.com/guides/how-to-pick-your-nook-color-operating-system-and-install-options/
ETA: lol, congratulations! I guess just skip to that link at the end.
Thank you, Tao. I seem to be a bit stuck, though.
I'm at 1.2 stock. I was able to reformat and erase my sd card. I went to load the .gz image onto the card (for CM7, per instructions here http://forum.xda-developers.com/showthread.php?t=1000957) and I also loaded the nightly build. Then inserted card into NC and booted. Nothing.
Any idea what I'm doing wrong? Should I unzip either file?
One thing that might/might not matter....when I went to eject the SD card from my PC, I wasn't given that option so I just pulled it.
One more thing.....the instructions at the link above instruct you to "write the image to your SD card" but then go on to say "eject the SD card" and then further "insert the uSD card into your computer"
Huh?? Isn't it all on the same card? Why do I need two different cards? What am I missing?
This blog breaks down the same process a little more step-by-step, with videos: http://www.anamardoll.com/2011/04/ereader-running-cm7-firmware-on-nook.html
You can skip the long preamble down to "Ready? Let's get started."
You do need to unzip the disk image, and write it to the SD using a program like Win32DiskImager or WinImage. It's also definitely a good idea to safely eject the SD card from your PC.
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Can someone also tell me how to access the book I just purchased and was in the middle of reading? Do I have to go somewhere and re-download?
Baboontyme said:
Hi Tao and others. Thanks again for all of your help. I'm almost there!
I followed this Ana chick's directions and I have CM7 booting up. I am now at the stage where I am trying to boot up in recovery mode so I can get the google apps and wifi thing going. I can't get it to work! I am holding down the "n"/home button and then the power button and it keeps booting up with CM7. I've tried it probably 20 times. Any help? Thanks!
Click to expand...
Click to collapse
I should add that though I can get CM7 to boot, I never get "The Power of Reading". It's just kind of a flash.
That's all normal--verygreen had to make a new uboot, which no longer shows "The Power of Reading" and also flies through a recovery boot so fast you could miss it. If gapps didn't install, just make sure the .zip is still in the boot partition and keep trying. I'm pretty sure holding power > reboot > recovery boot works now from within CM7, but I would go into Settings>Accounts and try to sign in to Google before assuming it didn't install.
If the book was a B&N purchase, once you have the market working, just install the Nook app and sign into your account, and you should be able to re-d/l the book, possibly even still synced to where you left off.
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
btw, you can also boot into recovery through rom manager, its easier.
Baboontyme said:
Thank you so much Tao and others. Up and running with CM7. Any additional mods I should be messing with?
Click to expand...
Click to collapse
You can overclock: http://forum.xda-developers.com/showthread.php?t=925451
Just make sure you grab the version for SD, and install it just like gapps, then set clock speed via CyanogenMod Settings>Performance>CPU
boxcar8028 said:
btw, you can also boot into recovery through rom manager, its easier.
Click to expand...
Click to collapse
Easier than holding power a sec, poking "Reboot," then "Reboot to Recovery?"
Really, it's about the same either way, depending how handy ROM manager is on your system.

Categories

Resources