Instruction:
Download Image Here
Code:
MD5 6c1a472b37b41216067a365cc113c473
Copy image to sdcard using WinImage. The sdcard has to be at least 1 GB. Under the disk menu, choose your sdcard then under disk menu again choose restore. If the disk is in use, you will not be able to copy the image to the card. Eject the card then try again. Avoid opening or automounting the card because winimage will see the card as being in use again.
Shutdown the Nook Color
Put sdcard in the Nook Color and press the power button
Press the volume down button so you highlight the "- apply update from sdcard"
Press the "N" physical button to selected the highlighted option
Press the volume down button so you highlight the "- Yes - Install /sdcard/update.zip"
Press the "N" physical button to selected the highlighted option
At this point, it will apply the sideload_update to your device
Use the volume down button to highlight "- mounts and storage"
Press the "N" physical button to selected the highlighted option
Use the volume down button to highlight "- format data"
Press the "N" physical button to selected the highlighted option
Use the volume down button to highlight "- Yes - Format"
Use the volume down button to highlight "- format cache"
Press the "N" physical button to selected the highlighted option
Use the volume down button to highlight "- Yes - Format"
Press the button button to return to main menu
Take out sdcard
Press the "N" physical button to select "- reboot system now"
After it has been reboot you will get an "Install Failed" message. Shutdown and reboot one more time and you are back to stock
---------- Older Image that uses dd ----------
Older Stock 1.1.0 (Use the link above) <--- This deploys dd images of /system and /boot.
Curses just used the stock 1.0.1 img an sideloading 1.1 as we speak -_-
This will be sooo much nice-er then having to set nook drivers back from adb to drag the update over.
Would it be plausible to cut /boot out of this (or something?) and flash it from the CWR on the eMMC?
This image is a life saver!!! Very nice. Kodos to all the parties that put this together.
Nice one, I'm grabbing this for when I start experimenting with stuff on eMMC
Process went well. During the first boot, got the rectangle with message failed to install but was fine after another reboot. About the disk capacity, i'm not sure why I only have 3.7 gig left? prior to running this image, I used to have the dual boot (regular 2.1 and the nokiefroyo). Any thoughts? Again thanks for this image.
Torrent for stock-1.1.0-CWR.zip
I created a torrent for stock-1.1.0-CWR.zip. With enough seeders this should be much faster than multiupload. Also, here's an MD5 checksum for the file brianf21 put on multiupload.com:
Code:
MD5 (stock-1.1.0-CWR.zip) = ea5ca2acc5067edfed49e694149d0e9e
If you have already downloaded the file and your MD5 checksum matches, please seed the torrent.
brianf21 said:
Instruction:
Download image
Burn to sdcard
Boot Nook using sdcard
Flash internal memory using the zip on the sdcard
Format data and cache from "mounts and storage"
Remove sdcard
Reboot
This is NOT rooted. Post any problems!
http://www.multiupload.com/8ODDMTYPIY
Click to expand...
Click to collapse
Quick question on this...is this the full update? I.E. if I have CWR installed in my recovery partition, will this replace it with stock recovery and system? Just wondering if this restores fully stock so that eight boot failures will reset the system again.
I know there are other posts on how to do this, but this seems the most convenient.
aschneid said:
Quick question on this...is this the full update? I.E. if I have CWR installed in my recovery partition, will this replace it with stock recovery and system? Just wondering if this restores fully stock so that eight boot failures will reset the system again.
I know there are other posts on how to do this, but this seems the most convenient.
Click to expand...
Click to collapse
The eight failed boots should start the recovery procedure. I am not sure if it will work with your setup though.
Vid. said:
I created a torrent for stock-1.1.0-CWR.zip. With enough seeders this should be much faster than multiupload. Also, here's an MD5 checksum for the file brianf21 put on multiupload.com:
Code:
MD5 (stock-1.1.0-CWR.zip) = ea5ca2acc5067edfed49e694149d0e9e
If you have already downloaded the file and your MD5 checksum matches, please seed the torrent.
Click to expand...
Click to collapse
I will start seeding as well. Thanks!
Worked great! I had flashed my NC with Nookie Froyo. Everything was working well until one day when it just wouldn't turn on. The only way I could get it to boot was from an SD card. Threw this guy in and restored everyting back.
Thanks!
I was having constant problems with mine. It worked fine for several weeks after rooting, then one day it wouldn't boot past the n screen. After repeated attempts with some other stock roms I got it back to 1.0.1, updated to 1.1, then after rooting again I got stuck with it only booting to CWR. Pretty soon it was completely messed up again and wouldn't boot, and no amount of flashing seemed to help. I found this thread, and the second rom worked perfectly on the first try. Thanks so much.
brianf21 said:
Stock 1.1.0 <--- This copies /system and /boot and will preserve custom partitions. Preferred!
Stock 1.1.0 <--- This deploys dd images of /system and /boot.
Click to expand...
Click to collapse
the first file... initiates a download for 1.0.1 is the zip file just named incorrectly?
pleasehelpnoob said:
the first file... initiates a download for 1.0.1 is the zip file just named incorrectly?
Click to expand...
Click to collapse
No, it installs 1.1.0 directly. I forgot to change the file name.
thanks brian,, nice build
brianf21 said:
No, it installs 1.1.0 directly. I forgot to change the file name.
Click to expand...
Click to collapse
thanks for the response
pleasehelpnoob said:
thanks for the response
Click to expand...
Click to collapse
I just fixed the name. Thanks for pointing it out.
I will be bringing back my nook color to barnes and noble for a return. Currently I have rooted nookie 0.6.8. will flashing the first file in this thread bring it back to stock sufficiently for a return?
can i flash this with my EXT4 Compatible Bootable Clockwork SD Card and get back to stock?
wethead4 said:
I will be bringing back my nook color to barnes and noble for a return. Currently I have rooted nookie 0.6.8. will flashing the first file in this thread bring it back to stock sufficiently for a return?
Click to expand...
Click to collapse
Don't forget to wipe user data. That way when they power it on, it will go to the OOBE. Nevermind... I reread the OP, that is already in there.
Homer
Related
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
First a word of thanks to rookie1 for putting this idea in my head and get me cracking on the code. (checkout his thread: [ADV](multi)u-boot v0.1). The idea is to present a boot menu of options to select the boot order for the NC.
I have implemented a set of custom console management functions (see sources below) which can be used to display any text based interface, there is support for Portrait/Landscape orientation and two font sizes are supported (Warning! Large font sizes look extremely ugly so I haven't compiled the binary with large fonts, if anyone needs it PM, me and I can send it to you via email)
Presented here is a compiled version of the u-boot.bin binary which has default font scaling and Portrait mode selected.
Installation
Simply use the u-boot.bin from the zip file attached with the post and follow rookie1's installation instructions from the his post linked above.
Important: Backup the original u-boot.bin in case you need to restore it in the future
Usage
To get to the boot menu, simply press any key within 5 seconds when the prompt appears.
There are two options to select and each one of them has alternatives to chose from:
- Boot Device
Select between: eMMC and SD
- Boot Mode
Select between: normal, recovery and alternative
Click to expand...
Click to collapse
Boot device enables the selection of the boot device. For the NC, there are just two options i.e eMMC (internal) or SD card.
Boot mode allows the selection of the kernel + ramdisk combo, which is then booted off from the selected Boot device:
- normal mode: kernel image file is "uImage" and ramdisk file is "uRamDisk"
- recovery mode: kernel image file is "uRecImg" and ramdisk file is "uRecRam"
- alternate mode: kernel image file is "uAltImg" and ramdisk file is "uAltRam"
Click to expand...
Click to collapse
This allows for the creation of dual boot setups where uAltImg + uAltRam files can be created to support a second OS or maybe overclocked kernels. Follow your favorite method for creating these as I'm not going to expand into the topic of dual boot setups here.
Follow the on-screen key usage guide to navigate the boot menu.
Default Behavior
When no key is pressed and the NC is powered up normally, the boot behavior is to boot into the normal (files: uImage + uRamdisk) found on the boot device, hence:
- When u-boot.bin is installed on the eMMC, the uImage + uRamdisk files are from eMMC
- When u-boot.bin is installed on the SD card, the uImage + uRamdisk files are from SD card.
Setting default Boot Device
A file named "u-boot.device" can be created at the same location where u-boot.bin is installed to control the default boot device. The contents of this file determine the boot device selected at boot.
The value of "0" means SD card and "1" means eMMC. So for example if installing u-boot.bin on the SD card, one wants to set the default boot device to be eMMC instead of the SD card, then the following can setup the u-boot.device file:
Code:
# echo -n "1" > /media/SDCARD/u-boot.device
This is similar to the file u-boot.order as mentioned in rookie1's original post, but it only takes 1 byte instead of 2 in that case.
This is useful in case when you want to lend your nook to your girlfriend and have the stock BN Eclair installed on eMMC and HC on the SD card. This way you can setup u-boot.bin on the SD card along with the u-boot.device file pointing to eMMC and have the NC boot into stock even with the SD card inserted. Whenever you want to boot into HC, simply get into the boot menu and select SD + normal!!
Think of these choices as selecting the appropriate kernel + ramdisk images from either the eMMC (internal memory of the NC) or the SD card. Other exotic options like for example selecting uImage from eMMC and uRamdisk from the SD card are currently not supported.
Files
u-boot.bin_v0.4.zip - contains the u-boot.bin
Sources
(updated with v0.4 changes)
https://github.com/j4mm3r/bn_nc_u-boot/tree/boot_menu
Changelog
v0.4:
Now uses Portrait orientation for display
Implemented custom console functions that support:
Font scaling (default or double size)
Portait/Landscape mode
Added support for Portrait/Landscape mode
Changed keys to suit Portrait orientation
v0.3:
Cleaned up sources, misc fixes
Missed the power key (Press any key?)
v0.2:
Improved lcd console display
Supports alternate boot mode
Supports setting up a default boot device
v0.1:
Initial release
I'm lazy...
Make CWR installable zip (SD and eMMC versions)
A few words of caution: Please don't use this if you don't understand what you are doing and remember all the usual disclaimers and warnings apply here as well.
Furthermore, I target this thread towards developers and advanced users so I have deliberately left out user friendly instructions. Feel free to incorporate it into your own custom ROM/CWR release.
Enjoy!
reserved
Reserved for future updates
This is going right on my nook...
would it be possible to update this so we could choose the emmc or the media position? what I mean is could this work with dual boot.
Not exactly sure what you mean, this is just the second stage boot loader. AFIAK, hardware limitations allow us to boot only from the eMMC or the SD card.
If you by any chance you meant the location of the /media mount after booting into Android, then I'm afraid that it is not under boot-loader control. Thats the job of init.rc loaded from the ram disk or depends upon the configuration for vold.
Novarider said:
would it be possible to update this so we could choose the emmc or the media position? what I mean is could this work with dual boot.
Click to expand...
Click to collapse
Sorry to waste space, but I had to say THANK YOU! The explanation of what each option boots, made the light bulb come on... I finally understand uRamdisk, uImage, etc.
Thanks! Nice options to have!
Recovery
This is a great idea that should be worked into a recovery as current recoveries are wiping eMMC when flashing new rom zip. I see some great things with this.
Would it be possible to alter this to allow boot into the "alternate" ROMs allowed by rookie1's dual-boot code? For example, I could set up dual-boot Eclair/Honeycomb on my eMMC using his code, then put CM7 on my SD card (and maybe even Froyo as well?), and choose between them?
Like this:
eMMC Normal
eMMC Alternate
SD Normal
SD Alternate
And you could include the recovery options you listed as well...
Socrguru said:
Would it be possible to alter this to allow boot into the "alternate" ROMs allowed by rookie1's dual-boot code? For example, I could set up dual-boot Eclair/Honeycomb on my eMMC using his code, then put CM7 on my SD card (and maybe even Froyo as well?), and choose between them?
Like this:
eMMC Normal
eMMC Alternate
SD Normal
SD Alternate
And you could include the recovery options you listed as well...
Click to expand...
Click to collapse
what he said!
As I am working on a major document about recovery and restoring procedures, can you please update your OP instructions to include how you would UN-do this feature?
I image just creating backup copy of the uboot.bin, but want to make sure.
j4mm3r said:
First a word of thanks to rookie1 for putting this idea in my head and get me cracking on the code. (checkout his thread: [ADV](multi)u-boot v0.1).
The idea is to present a boot menu of options to select the boot order for the NC.
Installation
Simply use the u-boot.bin from the zip file attached with the post and follow rookie1's installation instructions from the post linked above.
Instructions
To get to the boot menu, press and hold the "n" key while powering on the NC and keep pressing both the "n" key and power key till the words "Entering boot menu..." appear on the screen. Now release both the keys and, the boot menu will present itself.
There are four options to chose from:
- eMMC boot, normal
This boots from the internal eMMC in the normal mode. Which means the that uImage kernel is loaded from the eMMC boot partition and uRamdisk is the ramdisk.
- eMMC boot, recovery
This boots from the internal eMMC into recovery mode. Which means that the uRecImage kernel is loaded from the eMMC boot partition and uRecRam is the ramdisk
- SD boot, normal
This boots from SD card, in the normal mode. uImage and uRamdisk are loaded from the SD card boot partition.
- SD boot, recovery
This boots from the SD card, into recovery mode. uRecImg and uRecRam are loaded from the SD card boot partition.
Vol+/Vol- keys can be used to select between on-screen options.
Pressing the Home key (or the "n" key) then starts the boot process.
Think of these choices as selecting the appropriate kernel + ramdisk images from either the eMMC (internal memory of the NC) or the SD card. Other exotic options like for example selecting uImage from eMMC and uRamdisk from the SD card are currently not supported. Although it should be simple enough to expand the options to include lets say, an alternate normal boot overclocked kernel etc.
I'll post the sources on github very soon, but please feel to follow the patch details included here and expand the possibilities.
Files
u-boot.bin_v0.1.zip - contains the u-boot.bin
boot-menu.txt - source code patch details
Changelog
Initial release
A few words of caution: Please don't use this if you don't understand what you are doing and remember all the usual disclaimers and warnings apply here as well.
Enjoy!
Click to expand...
Click to collapse
next version, config file just like GRUB? kidding....
great work! U are real man!
You are correct.
Yea, just back up the u-boot.bin before replacing and it can be restored when needed.
Remember, the boot menu is the only new thing added which hijacks the recovery boot procedure (Power + "n") to get into action. Not pressing anything will result in a normal boot.
faceman66 said:
As I am working on a major document about recovery and restoring procedures, can you please update your OP instructions to include how you would UN-do this feature?
I image just creating backup copy of the uboot.bin, but want to make sure.
Click to expand...
Click to collapse
j4mm3r said:
Yea, just back up the u-boot.bin before replacing and it can be restored when needed.
Remember, the boot menu is the only new thing added which hijacks the recovery boot procedure (Power + "n") to get into action. Not pressing anything will result in a normal boot.
Click to expand...
Click to collapse
...and to be extra clear, "normal boot" would be the same as the OP's:
- eMMC boot, normal
Click to expand...
Click to collapse
Is it possible to change the way the options are displayed? I'm not complaining it works the way it is but if it could be updated to look better that would be great. Maybe have it look kinda like cwm recovery where you can see all of the choices and select one.
I already dual boot. Do I need to do everything again or just flash the file in OP.
Sent from my PC36100 using XDA App
This version is quite different than rookie1's dual boot. It does not use the extra file to determine the boot order nor does it have the option to boot alternate kernel + ramdisk.
Consider this as a replacement for the stock u-boot.bin that can show up a menu and let you choose from the provided options.
donniezazen said:
I already dual boot. Do I need to do everything again or just flash the file in OP.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ok Thanks.
j4mm3r said:
This version is quite different than rookie1's dual boot. It does not use the extra file to determine the boot order nor does it have the option to boot alternate kernel + ramdisk.
Consider this as a replacement for the stock u-boot.bin that can show up a menu and let you choose from the provided options.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Released a new version of the boot-menu. See OP for details.
Will test out the new version later. Thank you for this app its extremely useful
Nice
Sent from my Captivate using XDA app
I've tried about a million times now and can not get my Gtab into clockwork recovery. I downloaded the internal version of clockworkmod and hooked my gtab up to the computer and placed the clockworkmod zip in the recovery folder and unzipped it. Then I turned my device off and held down the power button + vol + it then says "Recovery key detected" and acts like its installing. Then It reboots and I turn it off again and it just keeps doing the same thing saying "
recovery key detected" and won't boot into clockwork!!!! Advice please?? And I know this is a noob question, I do. I tried following the instructions on the stickies but they're vague as to which clockwork zip I am to download??? Please help. Thanks!!!
From what I gather, after you download the internal zip you unzip that so you see the update.zip file & recovery folder. You move both of those to the root of the g-tab which would be /sdcard. I haven't done it yet since mine is charging right now.
Trying it now
GOLDEN....Finally! Thank you sir!
peurifoyd said:
I've tried about a million times now and can not get my Gtab into clockwork recovery. I downloaded the internal version of clockworkmod and hooked my gtab up to the computer and placed the clockworkmod zip in the recovery folder and unzipped it. Then I turned my device off and held down the power button + vol + it then says "Recovery key detected" and acts like its installing. Then It reboots and I turn it off again and it just keeps doing the same thing saying "
recovery key detected" and won't boot into clockwork!!!! Advice please?? And I know this is a noob question, I do. I tried following the instructions on the stickies but they're vague as to which clockwork zip I am to download??? Please help. Thanks!!!
Click to expand...
Click to collapse
Hmm?.. I think the issue you are having is moving the update zip into the recovery folder.
when you extract the files from the zip file extract them to the main directory "/SCARD" and thats it.
After you extract it you should see (in that directory) a folder that says "Recovery" , within that folder there should be a file named "Command" and thats it, no more files in there.
Also in that main directory you should see an "update.zip" file, leave it there. DON'T MOVE IT into the recovery folder.
from there follow directions to boot into recovery mode.
1) Power down
2) Press and Hold down volume up + rocker
3) Press and hold Power Button
4) when device powers on you will see "Recovery Key Detected"
5) release buttons
6) recovery will install and reboot as normal.
7) Power down and follow steps 1 through 5 again.
8) You should be in recovery mode now.
Edit:
Took too long to make this post!! LOL
my noob questions...what version did you use and can you post a link to it?? i am getting my g tab today!!
thx...
Follow the instructions on this link.
http://forum.xda-developers.com/showthread.php?t=865245&highlight=clockwork
Rumbleweed said:
Follow the instructions on this link.
http://forum.xda-developers.com/showthread.php?t=865245&highlight=clockwork
Click to expand...
Click to collapse
thx. i'm up n runnin vegan 5....
Tekrhino, I feel stupid but I have to ask for your help re: this same issue. It seems so clear on what to do from your instructions but I still can't get clockwork recovery to load. I'm having the exact same issue of not getting into clockwork recovery so I must be doing something wrong.
Maybe by telling my steps you can get me on the right path.
1. Downloaded clockwork mod to desktop.
2. extracted update.zip now I have a file that says update unzipped.
3. attached gtab to usb, recognized by computer as removable disk.
4. click on "open folder to view files and see list of different files on gtab
5. copy and paste recovery and update unzipped to this window and disconnect gtab from computer and then try to do the above mentioned steps to get into recovery. get the recovery key is detected message but can't get into clockwork recovery.
I must be doing something wrong but can't figure out what! Any suggestions that can point out the error of my process will be very much appreciated.
GGGwhatever!!
You don't need to unzip update.zip. You just put it in the /sdcard directory and the reboot to CWM and take the CWM options to run it.
Rev
Download CWM to your computer.
Uncompress it get two files (recovery and update.zip) Do not unzip update.zip
put these two files in your root directory on your Gtab ( SDCARD)
Hold Vol+ button turn on.
Sit back and watch
GGGTABBB! said:
Tekrhino, I feel stupid but I have to ask for your help re: this same issue. It seems so clear on what to do from your instructions but I still can't get clockwork recovery to load. I'm having the exact same issue of not getting into clockwork recovery so I must be doing something wrong.
Maybe by telling my steps you can get me on the right path.
1. Downloaded clockwork mod to desktop.
2. extracted update.zip now I have a file that says update unzipped.
3. attached gtab to usb, recognized by computer as removable disk.
4. click on "open folder to view files and see list of different files on gtab
5. copy and paste recovery and update unzipped to this window and disconnect gtab from computer and then try to do the above mentioned steps to get into recovery. get the recovery key is detected message but can't get into clockwork recovery.
I must be doing something wrong but can't figure out what! Any suggestions that can point out the error of my process will be very much appreciated.
Click to expand...
Click to collapse
I just got my tablet today and am still playing around with the stock, but from what I read I think your mistake is unzipping the "update.zip" file.
You only unzip the clockwork mod file you downloaded. Then you have two files: 'update.zip' and 'recovery' (folder). Leave the update.zip alone, don't unzip it and put these two files onto your gtab. Either internal storage (sdcard) or microsd card (sdcard2), depending on which clockwork file you have.
Thanks Rev! I know it is something simple but it was what I needed to get started.
Now I can play!
Newbie possible screwup
Help, followed install for Cwd and all get is the recovery reconized and it just stays on theviewsonic open page. Willnot go any further it is stuck.
I messed up the G Tablet soon after receiving it.
Here are two links with information on how to get it restored.
Viewsonic GTablet For Dummies
Guide - Restore G Tablet after a failed Recovery Mode update
Hope this helps.
djab67
(If I have helped, please hit the "Thanks" button)
Hello.
This question may have been repeatedly asked, but I have not found a complete answer.
I want to make a backup for Huawei Mediapad - or rather, the myself firmware version.
Most try to have the new modified version of the firmware with root access or just official.
The most stable, in my opinion, is C170B008. But annoying that every time I have to do a lot of action to modify a set of programs after reflash.
I tried to modify the contents of /system (system.img.ext4) and /cust (cust.img.ext4).
#mount filename.img.ext4 foldername
Actions with MC (delete/insert any files, set's permissions)
#umount filename....
Click to expand...
Click to collapse
After unmounting and packaging it into update.zip - try to install it on a MediaPad, "settings-...-install from SD" only - and getting error at the beginning of the process. --> reboot to old OS.
Please, write this - what I'm doing wrong.
Or, (the best action), add this full manual for working with MediaPad images, archive.
you have to put the update.zip in the 'dload' folder on your sdcard. Deactivate Quickstart in the Settings, Power off the device and start it with Power + Volume+. This should do the trick.
Rumbi said:
you have to put the update.zip in the 'dload' folder on your sdcard. Deactivate Quickstart in the Settings, Power off the device and start it with Power + Volume+. This should do the trick.
Click to expand...
Click to collapse
this method = my method of flashing, not?
when flashing started:
1. on the screen shows a green robot and the progress bar
2. is 5 seconds
3. on the screen shows a red message "Failed to flash"
It means:
- I tried the wrong way to work with partition
- I tried to pack the archive without a signature or whatever...
Hm this issue is weird. Here's how I do it.
- Ubuntu 10.04 VM
- http://forum.xda-developers.com/showthread.php?t=1373814
- After unmounting the Image I copy it to my Windows 7 Desktop
- Open an unmodified update.zip with 7-Zip and just move the system.img.ext4 into the 7-Zip-Window.
- It starts repacking and after that I can use it without any problems on my Mediapad
Then I try the "mount" command with the "loop" option.
May be, this is the reason for flash failure
alexdrakea said:
Then I try the "mount" command with the "loop" option.
May be, this is the reason for flash failure
Click to expand...
Click to collapse
Did you try to flash using fastboot, this is how I revived my machine the first time I messed up
CarpeNoctem said:
Did you try to flash using fastboot, this is how I revived my machine the first time I messed up
Click to expand...
Click to collapse
Fastboot mode works good.
I'll wait, still think that there can be done. Now Ubuntu is taken a great interest for work on tablet.
something strange just happened
on my rooted nook tablet i can't access to google play store
it say "you must add an account to the device to continue. do u want to add an account now"
and when i click on YES it closes everything and goes back on the main screen
and also Gallery - Email - Talk have the same icons with the android logo
is this related to the fact that the software has been updated to the new version 1.4.3?
should i root it again?
thanks a lot
WhiterabbitITA said:
is this related to the fact that the software has been updated to the new version 1.4.3?
Click to expand...
Click to collapse
Yep. Reroot using the sdcard method and everything should go back to normal. A system update breaks root as it modifies the /system/apps/ directory which is where superuser/google play are stored when rooting.
helpppppp
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
I think I'm having this same problem.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
simple answer for avoising breaking root is to install a custom rom
Sent from my Nook Tablet CM7 BETA using xda premium app
RooterBooter said:
Hopefully, someone can help me with this, as I seem to be having a similar problem. I am familiar with how to root the nook tablet, and have done so already, but since then, I believe the firmware updated, breaking my root. I am afraid to do it again, because when I first rooted the tablet, a game on it didn't work properly, and only worked properly after the update. Will this new root process cause any existing games to stop working? And how do I then prevent future firmware updates from breaking my root, again?
Click to expand...
Click to collapse
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
How do I tell if I'm using stock recovery or custom recovery?
tobdaryl said:
or install custom recovery (cwm) if you wish to continue to use stock
without stock recovery B&N can't send you updates
Click to expand...
Click to collapse
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
deleted because of multiple posts linked.
I have now booted into mac instead of ubuntu in an attempt to fix.
Looks as if I got caught in xda update!
It's still not correct but better now.
WhiterabbitITA said:
i was trying to reboot using that method
http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
i need help because something went wrong
Instructions:
Download the packages listed in the download folder, and extract them to your desktop.
extract ALL the files from the single zip.
NOTE: Do not extract the .zip with superuser and su.
Open the image flasher .exe, and browse for the .img that you extracted from the same zip
Put your SD Card into your nook or reader, and select the drive letter from the drop down on the right.
Press write, and wait
Once it has completed open the SD Card from the Windows browser and place the .zip in the root of the SD card.
Turn your Nook off.
Turn your Nook on while holding both the N+Power button. Your device will turn on, and then turn off after holding it.
NOTE: Do not let go of either button until your device has powered on and off again.
Put the SD Card into your nook.
NOTE: If it is already in there eject it and then put it back in.
Power your Nook on normally.
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
Select flash update.zip.nothing like that on the menu
i have rebbot system, install zip from sd card and selecting YES goes to Installation aborted
what to do?
Select Select from SD card.
Select your .zip
Reboot device
NOTE: Remove the SD card after your device reboots as if you don't it will continue to boot from the SD card.
Click to expand...
Click to collapse
From main menu (first screen after cardboard box)
select - install zip from sdcard
next -
select - apply /sdcard/update.zip
next -
N down and select YES
---------- Post added 15th August 2012 at 12:16 AM ---------- Previous post was 14th August 2012 at 11:36 PM ----------
RooterBooter said:
I used Albert Wertz's method for rooting using an sd card, and had no problems, except that I didn't go as far as to block the OTA updates. Is it possible to have a custom recovery and stock recovery on the same device? How do I tell, and how do I safely install cwm, without being able to use Titanium Backup (since my root is now broken)?
Click to expand...
Click to collapse
No, there is one partition designated for recovery. You can run cwm from sdcard when you wish and keep stock recovery internal, but custom recovery is the only way I have seen that absolutely blocks otas (otas are blocked with custom rom also) if that is your concern. To tell about your recovery the only thing I can think of is the power and N key into recovery. If you read what is presented on the screen when it appears and refuse a reset you are safe, that takes care of stock, if you are nervous reread and take your time. For cwm if that is installed you will see a cardboard box flash and then a menu with the first item to reboot, that is also safe.
To get into either recovery (for looking) from power off press and hold power and N, after two seconds release power, after one or two more seconds release N also. That should do it.
If you wish to have absolutely what to click when you get stock recovery just wait a while and I'll come back and edit this post to reflect that info. At the moment have something else going on (NT) I can't stop.
Stock recovery shows Factory reset
do you want to reset your device to the factory default?
Press POWER key to exit
Press Home key to continue
press power and you are out and safe
Installing CWM recovery! There are now two apps(they require root) here on xda for that purpose, one is 16gig only (Nook Tab Recovery Flasher) by indirect the other is 8gig and I don't know who did it.
There are also flash zips for each and a flash zip that is both 8gig and 16gig. If you are 8gig make sure you choose one for 8gig
CWM sdcard with a flash zip does not require root.