Burn a SD and don't boot yet.
Erase uImage from the boot partition
Put the uimage from inside the eclair overclcock zip into boot
Success
Sent from my SPH-D700 using XDA App
Related
I used to use pre-rooted BN 1.1.0 and can use CWR without problem. Now I installed a stock BN 1.1.0 and rooted it with auto-nooter 3.0.0 and once I reboot into CWR to flash 1.1GHz OC kernel I can not get out anymore. It will just reboot into CWR again and again. I tried to flash stock kernel but no luck.
Any suggestions?
Thanks!
Create a Monster Root pack bootable CWR SD (from monster root pack thread). Then find CW-Removal.zip in this forum and copy to the sdcard. Boot the SD, which will load CWR from the bootable SD and flash the CW-removal.zip file. This will restore stock recovery on the device and make it boot again.
I couldn't get CWR to work from the device with 1.1.0. So I just use the bootable SD instead. Hope this helps!
Sent from my Nexus S using XDA App
Hey Guys,
So I am working on installing Kang-o-rama 1.2 beta 1 and trying to set it up with Dark Tremor Apps2sd (Apps2ext).
I am using ClockworkMod Recovery 3.0.0.5. So before flashing the ROM, I followed these instructions on how to set up the ext partition for apps2sd. I formatted the ext for 512mb and swap for 0mb. After that finished, I copied the contents of the sd card back to the sd card through the recovery. Then I wiped the cache, dalvik-cache, and data/factory reset. After that, I proceeded to install the ROM. It was fine until it hit the part where it said it was installing applications. It froze and just sat there. I had to do a battery pull. The I tried re-formatting the cache and upon trying to format the sd-ext it froze. This is happening everytime now and preventing me from installing Kang-o-Rama.
Any ideas or help with this would be much appreciated.
Thanks!
My digestion would be to use Clockwork 2.x or Amon Ra...
Sent from my Nexus One using XDA App
danger-rat said:
My digestion would be to use Clockwork 2.x or Amon Ra...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
+1
I had all kinds of partitioning issues when I first tried clockwork. Switched to amon and haven't had any problems since.
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
mathfeel said:
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
Click to expand...
Click to collapse
BOOM Wining.
http://forum.xda-developers.com/showthread.php?t=932145
therealguppy said:
BOOM Wining.
Click to expand...
Click to collapse
LOL. Thanks.
My current ROM is phiremod nook V4.1. After flashing this and reboot. The Nook U picture flashes, then it's flashing "A N D R O I D _" prompt at the lower left and nothing...
There are three of us currently stuck on that damned android_ screen right now. As I posted in the other one if you get out of this please post your steps!
I reflashed phiremod nook V4.1. That boots pass ANDROID_.
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
I already did that. Right now as I turn it on, it displays the "Touch the Future of Reading" line instead of the "Loading..." line from CWR. Or do you think this is not sufficient?
There is message when installing repartition-boot-with-stock.zip:
"This will install stock boot 1.0.1 Eclaire --- This won't boot with Froyo!"
Can this the issue too?
EDIT: During the 5 minutes delay b/t post, I installed repartition-boot-with-stock.zip and Nook Color-v1.1.0-r2.zip, now it boots and stucked at the Nook icon with the "Contain Reader Mobile by Adobe" line.
Okay, so I restore stock image, albeit 1.0.1 using images form this page:
http://forum.xda-developers.com/showthread.php?t=919353
Steps:
1. download/extract boot.img and system.img to bootable sdcard (with CWRv3.0.0.6)
2. boot using sdcard, mount /sdcards
3. use adb to dd the image as described in article.
4. repeat failed boot to force recovery.
I thought this would restore /system and /boot ext3 again, but it doesn't...still getting stuck at "ANDROID_" prompt after reflashing the Nook Color v1.1 above. I am going back to CM7...sigh...
EDIT: Actually, it DID work! My problem was when I reflashed Nook Color v1.1-r2.zip, I wiped system and data, which I shouldn't have.
therealguppy said:
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
Click to expand...
Click to collapse
FYI I've been in the same boat as you a couple of times now with my Nook not wanting to boot. And it seems it gets to different points each time before locking up and not booting. I'm starting to think the same thing as your comments here. This whole ext4 stuff is what seems to be causing issues for a lot of folks specially when wanting to go back to a different ROM or stock. To further compound it is the fact the newest CWR is 3.0.1.0 and all bootable sdcard files are still 3.0.0.6 or 3.0.0.5. With that said I can tell you making a backup using the 3.0.1.0 CWR that is on the internal mem and then getting stuck booting is no good. Reason being from wha tI've found so far is if you take your 3.0.1.0 backup and put it on a bootable sdcard that has 3.0.0.6 so you can restore, it does not work right from what I've found. The only way I've found to fix it easily so far is to first flash the " Remove CWR * .zip from the link posted here. After that then flash the repartition-boot-with-stock.zip file. Once I've flash those 2 files I'm able to flash a new ROM and have it boot like it should.
Another way I've got around it was to power the device on into recovery with no sdcard in the device. Once it booted into recovery ( ie CWR 3.0.1.0 ) I put the sdcard in the device that had my 3.0.1.0 CWR backup. I restored that backup using the actual 3.0.1.0 recovery from internal mem. Once finished tried to boot and it got stuck. When it did I then powered it down and fire it back up but this time booting to the sdcard and then I flashed the repartition-boot-with-stock.zip and it would finally boot up like it should.
Bottom line IMO at least is it seems to be hit or miss on what is the best way to get it back up and running after the boot partition gets hosed. And that can make it a bit frustrating.
Sorry I don't have time to read all of this. Just keep in mind that > 3.0.0.6 formats to ext4 (ie CM). For stock and froyo, use 3.0.0.5 to format to ext2 and 3..
System, data and cache need formatting before flashing a new rom.
Repartitioning boot is only useful if your NC doesn't boot.
Sent from my HTC Desire using XDA App
thought 3.0.1.0 was supposed to work for everything.
Simple question......if i have already flashed Honeycomb onto the nook internal memory..and if i would like to instead flahs CM7 to the internal memory can i just load my CM7.zip file onto my ClockWorkRecovery SD and then install from zip using that? or do i have to restore back to stock and then reroot and start the process all over?
let me know if you need any clarification on my jibber jabber
Just wipe from recovery, then flash the zip and compatible gapps...
Sent from my NookColor using Tapatalk
danger-rat said:
Just wipe from recovery, then flash the zip and compatible gapps...
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
wipe from recovery? Does this mean simply drag the zip file out of my sd card using my computer or put my CWR sd into the nook wipe it there, take the sd card back out of the nook drag and drop the cm7 zip onto my sd card and then install from zip using the CWR
I believe he means you need to boot CWM and use the menu to format areas like data/system/cache and then install CM7. I'm not sure which areas need to be formatted if you installed HC though.
Depends on which version of HC you installed.
If you installed the v2 with ext4 filesystem, you should be able to just wipe system/data/cache and then install cm7.
If it was one of the older HC releases that you had to format the boot partition to install, im not sure what to do.
i had to format boot for HC not cache and i believe with cm7 i have to format cache
I wiped the boot partition when installing Honeycomb on my NookColor. Once I got GingerBread back on the Nook, I installed Clockworks but, no matter what I press at boot time, I am no longer able to get into recovery. Does anyone know the magic to this or have the original boot partition that I can load on to my NookColor.
Thank you so much, in advance.
David
First thing I'd try is the 8 failed boot attempts to restore to stock... this should fix you file system.
DizzyDen said:
First thing I'd try is the 8 failed boot attempts to restore to stock... this should fix you file system.
Click to expand...
Click to collapse
Since I have CM7 on the Nook, it wouldn't. That is only if you have a root B&N image. I broke it installing HoneyComb and went to CM7 after.
I did find the recovery boot fix image in the forums and installed it. I am hoping that it fixes the problem. I haven't tested it yet.
As far as I know... if you don't have CWR installed on eMMC then the 8 failed should work... the zip file it uses is not overwritten by any of the ROM's.
If you installed CWR on eMMC, you can use CWR uSD and the remove-cwr.zip file to restore the 8 failed boot abilities.
If you adb into the nook... mount /dev/block/mmcblk0p3 /tmp
you can see if the factory.zip is still there.
U-boot is the problem. Flash either boot repartiton or recovery repair. Recover repair is better!
Sam
Sent from my Desire HD using XDA App
Thanks Sam... I forgot the obvious... typical, huh.
No worries..
Sent from my Desire HD using XDA App