Hi all!
I just updated my Nook from an old Phiremod build to MIUI 1.8.5, and I love it! However I see (because of the CyanogenMod logo, and the subsequent menu) that the new advanced boot menu was baked into the ROM. Now this seems to be a lot more awesome than the old-fashioned multi-uBoot, and I can boot into Normal and Recovery just fine... however my other ROM on the eMMC won't boot. I've actually done this to two NCs, my mothers and my own. My mother's had Stock 1.1 rooted on the alt partition. Mine had a build of Honeycomb. Both hang whenever I select Boot Alt then Reboot!
Is there any way to recover these old partitions? If not, that's not a big deal. it would just be nice.
More important however:
How can I, using the new Boot Menu, have my Normal boot be CM/MIUI/Whatever, and my ALT boot be (preferably rooted and OC'd) Stock 1.2? Please help, I'm going back to school and would love to have Stock for studying... and as of this point, my mother's under the impression that I broke her Nook Color, so I'm in hot water!
Please!
Thanks!
EDIT: found this: http://forum.xda-developers.com/showthread.php?t=1156909 This MAY be the solution to my problem. Going to try it and see where it leads. Silly me only looking for the solution in the Android Development section, not the General section. Will post back soon, for now, IGNORE ME!
Yeah this totally looks like the solution to my problems. It seems to be using Multi-uBoot 0.4 as opposed to the boot menu, but I'm just going to do what I do best: blindly follow instructions and pray that all will be well. I strongly believe it will be. Should I run into any problems, I'll just rewrite this thread and go from there. Happy Nooking everyone!
Related
ok - i have a G1 ... fully functional etc
anyway - i started looking into putting SenseUI on it - and then about 15mins ago came across the cyanogen thread and became very intrigured....
i have a couple questions
1. with the latest release of the ROM, is the phone fully functional?? - no restrictions etc? tmo doesnt mind or restrict you etc? - i still want all features working
2. is there a step by step on installing the rom? - i looked around a bit but found multiple conflicting instructions/recommendations -
3. WORST case scenario, can i always go right back to where im at now? - official tmo/google release, fully functional, normal g1? - or am i stuck
my biggest concern is ruining the phone - im just getting in to G1 editing etc - ive always been too nervous because its my main phone and only phone - but i used to do all kinds of crazy things with my old blackberry - beta releases from overseas etc etc - just havent gotten the balls to mess with my g1
but ill be honest, i hate the iphone (not sure why) - but im getting kind of fed up with the G1 - i love it, dont get me wrong - but the add-ons/functions i read in cyans rom intrigured me a lot
so with all this being said - please answer my questions listed above
i dont care so much about the files/apps - i can always re-download the apps i use etc... and the pics/vids i can back up to my pc
thanks in advance!!!!
the current stable release of cyanogen's rom in 4.0.1 and it is very stable and much faster than stock cupcake. the only thing missing as far as i can tell is the myfaves app. but i do not care bc i can update that online. everything in market works. plus many extras from donut.
are you rooted? if not, go to the market.
search for recovery flasher.
download it.
then go to cyanogen's thread and download 4.0.1.
put it on the root of your sdcard (upmost folder).
use the recovery flasher app to apply cyanogen's recovery image 1.4 on your phone.
power off your phone.
hold home and power to boot into recovery.
it should have a green android with text in front of it.
go to flash any .zip.
select the 4.0.1 file you put on your sdcard from above.
hit home to apply it.
after it finishes and tells you to reboot the phone then select reboot phone on the menu.
let the phone boot up.
may take 5 to 10 minutes.
then look into partitioning your sdcard for apps2sd and a linux-swap partition if you want those options.
yes you can easily revert the phone to stock rom like you never rooted it.
when you boot the phone up the first time, if you get a lot of force closes then boot into recovery.
go to the recovery console
hit enter
type fix_permissions
then type reboot
if that does not work then you will have to wipe the phone from the recovery menu and re-flash the rom
any other questions
trying it now - (crosses fingers)
its been on the NEW adroid splash screen ( the one with the android on a skateboard) for a while now... it stops highlighting once in a while and flashes off - then starts again... its been about 7-8mins i think..... is this normal?
got it!
thanks!!!
your welcome. did you have root or did you use the recovery flasher app? because if you used the recovery flasher app there is a quick question i have
i didnt have root at all prior to me trying this tonight
something i would try. power your phone down. hold the camera button and power button (this boots up into bootloader) if you get a rainbow screen then you will want to flash the hard spl(androids on skateboards with a white background). so you can you use fastboot. here is where you can get the hard spl. just boot into recovery and flash it. i do not know if flashing the hard spl will wipe your phone like flashing haykuro's spl will, but you would much rather have the hard spl than not having it so the pros far outweigh the cons. welcome to your newly rooted phone. if you have any questions feel free to pm me and i will do my best to answer them.
david1171 said:
something i would try. power your phone down. hold the camera button and power button (this boots up into bootloader) if you get a rainbow screen then you will want to flash the hard spl(androids on skateboards with a white background). so you can you use fastboot. here is where you can get the hard spl. just boot into recovery and flash it. i do not know if flashing the hard spl will wipe your phone like flashing haykuro's spl will, but you would much rather have the hard spl than not having it so the pros far outweigh the cons. welcome to your newly rooted phone. if you have any questions feel free to pm me and i will do my best to answer them.
Click to expand...
Click to collapse
Thanks for the step by step guide David...
I would like to ask a question on ROM types. I am currently using JF's 1.51. I have no problem with this (occasional force closes, which I suspect is from the SetCPU app). I have hearing lots of updates from CyanogenMod's ROM. What are the main differences? From your experience, what do you think are the disadvantages of CyanogenMod's ROM versus JF's 1.51? Would appreciate any help you can give. Thanks
erlern said:
From your experience, what do you think are the disadvantages of CyanogenMod's ROM versus JF's 1.51? Would appreciate any help you can give. Thanks
Click to expand...
Click to collapse
sorry i almost cried when i saw disadvantages lol.
1 you do not have to overclock bc the phone is set up to overclock when it needs it and to underclock when it doesn't need it.
2 apps2sd is automatic if you have a second partition. there's a great guide for easily partition your phone with cyanogen's 1.31+ recovery image.
3 many cool things from donut.
4 a lot of themes are made for cm roms
5 a lot of stuff too much for me to list
if you really want to try it just get his latest recovery image. download 4.0.1 or whatever the latest stable release is. make a nandroid back up. flash the rom, and if you don't like it, or want to go back to JF then you can easily
David, Thanks for this. Just for kicks. If i want to reset to the factory defaults all I need to select is the "wipe data/factory reset" from recovery?
I think my post just disappeared...anyway... David, Just for kicks, If I need the phone back to original settings, I need to select the "wipe data/factory default" option in recovery? This will keep the new recovery method, just deletes the rom?
You will keep the recovery image. Yes it will just clear you data and stuff off the phone. Things like recovery image, SPL, and radio do not get wiped. If you do wipe just reflash a rom and you will be good to go.
PHP:
david1171 said:
sorry i almost cried when i saw disadvantages lol.
1 you do not have to overclock bc the phone is set up to overclock when it needs it and to underclock when it doesn't need it.
2 apps2sd is automatic if you have a second partition. there's a great guide for easily partition your phone with cyanogen's 1.31+ recovery image.
3 many cool things from donut.
4 a lot of themes are made for cm roms
5 a lot of stuff too much for me to list
if you really want to try it just get his latest recovery image. download 4.0.1 or whatever the latest stable release is. make a nandroid back up. flash the rom, and if you don't like it, or want to go back to JF then you can easily
Click to expand...
Click to collapse
I like your SPL on your signiture. Im guessing its the danger SPL
Yeah it references the danger spl lol. I think thats the feeling that anyone gets when flashing it. I know i was like i really hope this works or i'm going to be sad.
Original question(s) seem to be solved.
Closing thread
I got the NC from overstock for a good deal. I am pretty savvy technically and have rooted phones, returned to stock from a bricked android phone, etc.
So I got a blue dot 1.2 NC. I was initially planning to do a repartition and then install CM7. Thats how I started. I created a bootable CWM 3.08 uSD card. Ran the repartitioning script (from here). That went well.
Then I was reading about rooting and saw the Manual Nooter thread: this one
On a whim I ran the manual Nooter install, which ran well too ( I later realised that this was for STOCK 1.2 )
Then I installed CM7, gapps and OC kernel in that order which completed successfully too.
Now, when I start the NC, I am stuck at the n COLOR animation. Tried clearing data, cache, etc but nothing works.
How do I get out of this pickle? I am itching to use my first android tablet! Thanks for your help..
pspTP said:
I got the NC from overstock for a good deal. I am pretty savvy technically and have rooted phones, returned to stock from a bricked android phone, etc.
So I got a blue dot 1.2 NC. I was initially planning to do a repartition and then install CM7. Thats how I started. I created a bootable CWM 3.08 uSD card. Ran the repartitioning script (from here). That went well.
Then I was reading about rooting and saw the Manual Nooter thread: this one
On a whim I ran the manual Nooter install, which ran well too ( I later realised that this was for STOCK 1.2 )
Then I installed CM7, gapps and OC kernel in that order which completed successfully too.
Now, when I start the NC, I am stuck at the n COLOR animation. Tried clearing data, cache, etc but nothing works.
How do I get out of this pickle? I am itching to use my first android tablet! Thanks for your help..
Click to expand...
Click to collapse
Since you are working with the blue dot, you need to upgrade your bootable CWM to version 3.2.0.1. That versions is designed with support for the blue bot. I would then rerun the repartitioning, since most likely it did not work right with the old CWM. At that point you should be able to wipe the system and install CM7, gapps, and OC.
GMPOWER said:
Since you are working with the blue dot, you need to upgrade your bootable CWM to version 3.2.0.1. That versions is designed with support for the blue bot. I would then rerun the repartitioning, since most likely it did not work right with the old CWM. At that point you should be able to wipe the system and install CM7, gapps, and OC.
Click to expand...
Click to collapse
Thanks I will give that a try tonight and report back.
Newby Thoughts
What's a blue dot?
I'm a newby at this but why not start with a factory reset then build up to what you want. Sounds from your posts that you've just been throwing different things at it and somehow expecting things to work. Like I say, newby thoughts but the factory reset and step by step has worked for me--and apparently many others. Let us know if you try and how it works.
OTC
GMPOWER said:
Since you are working with the blue dot, you need to upgrade your bootable CWM to version 3.2.0.1. That versions is designed with support for the blue bot. I would then rerun the repartitioning, since most likely it did not work right with the old CWM. At that point you should be able to wipe the system and install CM7, gapps, and OC.
Click to expand...
Click to collapse
Thanks gmpower. That seemed to do the trick. I used CWM 321 and also made sure I did a data system and cache format before I installed CM7. The NC booted into CM7 and everything looks great now
Appreciate your help!
The blue dot is a sign on a box that the new nook is with a new partition setup , rather than what was originally provided with the nook.
Cuhulin said:
The blue dot is a sign on a box that the new nook is with a new partition setup , rather than what was originally provided with the nook.
Click to expand...
Click to collapse
if you want to swap partitions back to 'old' setup,
which i did, DeanGibson's thread is good
http://forum.xda-developers.com/showthread.php?t=1094371
now have 5 gb for storage - music, books, etc.
quick question, didn't the nook from overstock come with 1.2 stock?
i rooted my overstock blue dot one and am having weird power issues, so i was curious if it was a hardware failure or something with manual nooter?
thanks!
Cuhulin said:
The blue dot is a sign on a box that the new nook is with a new partition setup , rather than what was originally provided with the nook.
Click to expand...
Click to collapse
does anyone know when these models became pervasive on the market? I have a friend who got a nook after me (mine was March, his in April I guess) and we had trouble following the process with his (which worked great for mine) and I'm just now realizing he may have the new one...
dag16 said:
quick question, didn't the nook from overstock come with 1.2 stock?
i rooted my overstock blue dot one and am having weird power issues, so i was curious if it was a hardware failure or something with manual nooter?
thanks!
Click to expand...
Click to collapse
Yes I think my nook from OS came with 1.2 stock. It had the blue dot on the box. I initially turned it on and registered the device on the BN network. Following which I tried the whole rooting and custom ROM thing.
In my case I think using CWM 3.0.8 caused the issues I was having. Switching to 3.2.1 I was good to go.
What are these weird power issues that you are having?
pspTP said:
Yes I think my nook from OS came with 1.2 stock. It had the blue dot on the box. I initially turned it on and registered the device on the BN network. Following which I tried the whole rooting and custom ROM thing.
In my case I think using CWM 3.0.8 caused the issues I was having. Switching to 3.2.1 I was good to go.
What are these weird power issues that you are having?
Click to expand...
Click to collapse
Thanks for the info.
Mine kept powering off randomly and constantly. I unrooted and restored stock, and it still persisted, so warranty replacement on the way!
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
grins1 said:
Phone: HTC Hero, CDMA
Carrier: Sprint
While others have reported of this problem, the solutions that worked for them dont work for me. Im really stuck.
I know, its an old and slow phone, but I was hoping to go to CM7 to get better performance out of it. Well, I must have done something wrong in the process. My current android version is 2.1-update1. I used z4root to root it and used the clockworkmod ROM manager to install a recent nightly after backing-up my current ROM. Installing the nightly failed, something to do with the zip, but my phone had already been wiped and rebooted in default factory mode. I tried doing the install again with the same nightly and a more recent one, but it kept failing due to a problem with the zips. After one of the reboots, the OS just wouldnt load; seems to be looping on the 'HTC quietly brilliant' screen. I am able to boot in recovery mode, but cant figure out how to get past this looping issue.
Ive tried booting using the back-up I created with no luck. Ive even tried going through the RUU process (cant post a link cause Im a new member here), which results in an error message stating that theres an incorrect bootloader.
I did figure out that I was trying to install CM7 using the wrong zip; had the GSM version. Ive tried installing CM7 with the correct zip, but, after reboot, it loops at the animation with the android on the skateboard and the blue arrow around it. Not sure what it means that the two different OSs loop at, what looks like, the same points.
I probably did something wrong, but Im hoping somebody with a better understanding of all thats involved can let me know if there is any way for me to fix this. Thanks in advance for the help.
Click to expand...
Click to collapse
I *think* your error, in general, was using a bunch of "easy" one click methods and not properly learning (READING) about what the proper steps are. Here is my advice (assuming you are still rooted) -
1.boot into recovery (power off phone, hold home button, press power)
2.wipe data/factory reset
3.mounts/storage - wipe system and boot
4.restore nand backup OR flash ROM/gapps (from the same thread)
5.reboot, and be patient, bootup could take 5-10 minutes.
Good Luck.
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
grins1 said:
You are the man (or woman)! I believe the formatting of system and boot is what did it. Really appreciate the help.
Click to expand...
Click to collapse
It is important, as Il Duce said, that you definitely do a good amount of reading when you want to get involved in rooting your phone. You are opening yourself up to some great innovation and fun, but you can also cause yourself a lot of headaches.
Recovery is your friend. If you can get into that, at least you know things are ok. I like to wipe (or format) system, data, cache, and boot 3x just to make sure that clockwork recovery cleaned everything and there are no dingleberries from the last rom I was using.
Flashing the correct type of rom is even more important. Don't flash a gsm rom to a cdma phone and NEVER flash a gsm radio to a cdma phone. Once you delve into the reading aspect of XDA, you will see that is the sure way to brick your phone.
Some roms take longer than others to boot up. Let it run its course. Sometimes it will reboot right after installing. At some point, you might want to make a nandroid of the new rom you are running and go back to your stock (2.1 update 1) and update your PRL, baseband, etc. (if you haven't done an update in a while).
Have fun, that is the most important part and we seem to have a lot of it here in HeroC XDA land.
You know, I put in a fair share of reading about how to update the ROM on my phone and I was under the impression that it would be fairly simple. I figured that since this has been done for quite a while and all these tools have been developed, I wouldnt need to know what happens on the back end during a root or ROM install.
But I did get myself into a bind that I wasnt able to figure out on my own. And with the help of this forum, I was able to get past my problem. Im glad to say I now have a phone that is functioning very smoothly with CM7 and the apps I need.
Next step for me is figuring out how to save my apps to the SD card so that I can install from there if/when I update my ROM in the future.
Thanks again for the help!
Get titanium backup FTW.
BANG! from my shooter...
Ok so i recently bought a dell streak 7 and have had it rooted and such. i installed cwm 6.0.1.0 for su.
now heres my problem:
i tried out DJ_steves ics build just for kicks but went back to stock, now im looking at the other roms, and i wanted to put honeystreak HD7. they all looked dated and like there isnt much development going into them, but i figgured id grab the one with the lattest date on it. (november 4) but when i flashed the zip through cwm 6.0.1.0 i reboot and i am boot looping. (after the green twisty light up android text) so i nvflashed back to streak droid hd7-2-wifi only. which works but theres no oc and it feels laggy in my hands...
sorry for the nooby question i feel stupid ive never had this much trouble with a device but all the roms and dates are confusing me..
thank you for the help..
What version did you use? R8? After you flash R2, you need to make an install.txt with some settings on it, described on TabletRoms.com, then you can flash R8.
HD7 is over and long gone, after the break up of XDA and DJ_Steve.
Ok ill look over at tabletroms. guess you guys have got some sort of history going down here huh? lol thank you.
Hi,
Firstly ought to say thanks to verygreen et al. for the awesome cyanogen mod, have 10.1.3 up and running on a nook hd+ mand it's great.
I'm trying to get: h-t-t-p-s://play.google.com/store/apps/details?id=com.bskyb.skygotablet&hl=en_GB to work on the nook hd+ with cyanogenmod, they have some pretty extreme protection measures against rooted devices. I've read just about the whole 292 pages of the thread on Sky Go (The mobile version) to work out how I might go about getting it to work.
I've tried manually moving su, and OTA rootkeeper, and changing ro.tags to "release-keys" in build.prop, I'm just taking a backup now to try changing ro.secure to 1 in default.prop in initrd.gz. (I couldn't figure out another way to get hold of the boot image, am I missing something obvious?).
Basically wanted to know if I'm fighting a losing battle here - or if there some way to actually unroot cyanogenmod that I'm not aware of. Don't really want to have to go back to stock to get this working, but the tablet is for the Mrs and I think she'd really like Sky Go.....
I know in the previous version people had some success running with a stock kernel - does anyone know if it's possible to replace the Cyanogenmod kernel with the stock nook one?
Cheers