[Q] can't update - Nook Color Q&A, Help & Troubleshooting

Hi,
I installed cm7 with the stable build 7.0.3 and for some reason couldn't get gapps to work. the n I tried to update to 7.1.0 rc but I can't for some reason. I tried reboot into recovery and install from SD on ROM manger but it wouldn't work. can someone please help me?

What kind of error messages do you get? Does it reboot and fail? Or does the install fail? Elaborate please. Or, if you don't want to answer those question but take forever to install, here goes the El Guide:
0.5: Go into settings>applications. Tick Nonmarket installs and usb debugging.
1. Backup all your data. Simple. Do this on a computer with ADB:
Code:
mkdir Backup
and
Code:
adb pull /data/app/ app/
lastly:
Code:
adb pull /data/data/ data/
2. Download CM7. Pick your version. Nightly, RC, stable. Download it to the sd card. Also google "gapps" and download the universal version, for all devices. Put that on the sd card. Also download any other things to have flashed (OC kernel, Keysmod) and put it in the sd card.
3. Boot into ClockWork Mod. (Rom Manager > Reboot into recovery) Using the volume button to navigate, go to mounts + storage, and format system, data, and cache. Go into advanced and formate dalvik cache.
4. Now hit the power button, select Install zip from sd card, choose zip from sd card, then find the cm_encore_xx_xx.zip. Select Yes to flash.
4.5: Do the same step to get to selecting the zip, but this time pick gapps. Then also flash any other things you need too. (OC Kernel, keysmod)
5: Power button> reboot device
6. Boot into CM7. Set up the installation. Now plug into the computer.
7. Make sure the nook is setup on cm7 and is at the home screen, NO OTHER ACTIVITY GOING ON.
8. Run these commands from the computer using ADB:
Code:
cd Backup
Code:
adb push app/ /data/app/
(wait, it depends how long on the amount of apps you had.)
Code:
adb push data/ /data/data/
Code:
adb reboot
System should reboot, with data & apps restored. If all you get is a bunch of force closes on boot or launching an app, redo steps 2-7 but then do this:
-begin steps for desperate people-
Go into settings>applications. Tick Non-market installs and usb debugging.
Download File Expert from the market.
Run on the computer:
Code:
adb push app/ /sdcard/install/app/
Code:
adb push data/ /sdcard/install/data/
Make sure before that there is enough space on the sd card to hold those two folders.
Now run file expert, go into the install folder, press+hold on the app folder, and select "Install all APK Packages" Now just select install for each file. Now run this adb command:
Code:
adb push data/ /data/data/
Now reboot. BAM! Apps restored. And app data too.
-end desperate people instructions-
There you have it. A [long post to type in the quick reply form] guide to install cm7 latest. Note that for most future releases, these steps won't be necessary. The only thing will be to flash cm7, gapps, and other packages. This process of backuping and stuff was becaus (for me) upgrading to a major release caused issues.

To elaborate, it does nothing. I follow verygreens method to install a new build. I put it on the SD card( file is a zipped one) and then put it in my nook color and power on. Then I reboot in recovery. It just doesn't do anything. same for gapps. I thing I may be doing it wrong. I also tried going to install from SD ( in ROM manager) and I found the build and choose it. It then shows me reboot options and I pick wipe Dalvik cache and back up existing ROM. It then reboots and does nothing.
P.S. I don't have any data on my nook color that I can't install again.

Related

[Walkthrough] From stock (1.5) to rooted 2.1 (update - new link)

Introduction:
This walkthrough will take you through rooting a stock 1.5 Eris. After following the walkthrough, you will have a rooted 2.1 Eris.
Unfortunately, this will NOT help people who upgraded to the Leaked 2.1 ROM. For now, there is no way to fix your issue.
CREDITS:
GrdLock for his walkthrough in androidforums - it inspired this one and much of the info came from his walkthrough
caboose for finding the rooted dev ROM
amon_ra for the recovery console
ivanmmj for rooting the 2.1 ROM
Warning:
Neither I, nor xda-developers.com, is responsible if this process bricks your phone. Sometimes, the unforeseeable will happen. Sometimes, you will make a mistake. Although this process is relatively safe, if your phone becomes bricked, we do not and will not provide support or replacements for your bricked phone.
Index:
I: Gaining root: an unlocked hboot
II: Prerequisites: Tools to flash
III: Flashing a rooted/modded recovery
IV: Flashing a custom ROM (rooted version of leaked 2.1 ROM)
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
II: Prerequisites - Android SDK - These instructions are for Windows XP. You must adapt them to your version of Windows.
First we must install the Android SDK as it has the tools we need for both this walkthrough as well as to make your life in the Android world easier.
1. Visit the Android SDK site.
2. Visit the Java site and download the latest Java JDK.
3. Extract the Android SDK zip file unto c:\AndroidSDK\
4. Double click on SDK Setup.exe
5. Many times, you will need to click on Settings and check the box to force HTTP instead of HTTPS.
6. Choose to download the USB drivers package. Nothing else is required.
7. Enable your phone's USB debugging mode: Settings > Applications > Development > check USB Debugging
8. Connect your phone via USB to your PC.
9. Right-click My Computer > Properties, click on Hardware, and go to Device Manager. You should see a device with a yellow exclamation next to it, this is your phone (if you don't see it you probably forgot to enable USB debugging mode)
10. Right-click the device, select Update Driver. Browse to your Android SDK directory, and you should see a "USB Driver" folder in it now. If you don't, you forgot to download the USB Driver package when in "SDK Setup.exe". Select the driver in that folder.
11. To make life easier, lets add a global path to the android SDK tools. Right-click My Computer > Properties, click on Advanced, then click on Environment Variables. Doubleclick on PATH, then at the end of the Variable value, add a semi colon ";" and then c:\AndroidSDK\tools
III: Flashing a Custom Recovery
Flashing a custom recovery will make your life easier when flashing ROMs in the future.
1. Download this file: Recovery.zip
2. Extract file contents to your \tools\ directory of your Android SDK.
3. Open up a command prompt and go to your tools directory, and execute these commands:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
4. Success! You now have a recovery partition installed on your phone. You can access it by running "adb shell reboot recovery" or by powering off your phone, holding "Volume Up + Power On"
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
CONGRATULATIONS! You now have a rooted 2.1 phone!

No OS but only CWM recovery

I want to flash a rom but i can't save the zip files to my storage. What do i do?
I have no os but only cwm. Please help, thanks.
dicksonjoe said:
I want to flash a rom but i can't save the zip files to my storage. What do i do?
I have no os but only cwm. Please help, thanks.
Click to expand...
Click to collapse
ADB Sideload
1. Connect your phone make sure it's actually connected. No errors in Device Manager
2. Rename the downloaded ROM you want to flash to something basic, like rom.zip (Names can get rather long)
3. Open CMD (command prompt), & navigate it to the folder you placed the ROM in. or just press shift and right click on the folder where the rom is and select open command prompt here
4. Boot to recovery on your phone and enable the ADB sideload function. Under Advanced in TWRP...not sure about CWM
5. in CMD type adb sideload rom.zip or what ever the name of the .zip is
6. Let TWRP or CWM flash the zip and prompt for reboot.
7. Reboot and be happy, your phone is fixed!
You can then transfer the gapps to your internal storage and flash the normal way through your reecovery or just go through the same process for the gapps after you flash the rom.
I am having trouble installing the adb file.
I don't know what mode my phone needs to be on in order to install adb file.
dicksonjoe said:
I am having trouble installing the adb file.
I don't know what mode my phone needs to be on in order to install adb file.
Click to expand...
Click to collapse
Installing adb doesnt have to do with what mode your phone is in.

help please

i format my Nexus 4 on twrp recovery using advance wipe and i checked all the box there, and when i rebooted its stuck on google logo, what should i do?
Well why would you do that? If you selected everything under advanced in twrp, that means that you have also wiped the system partition so there is no rom to boot into, hence why you are stuck at the google logo. You will need to use adb to copy a rom onto your phone, and then flash it via twrp. Instructions:
1. Setup adb: http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
2. Install Koush's universal adb driver (google this for the download)
3. Put the phone into twrp
4. Download a rom on your pc and move it to your desktop. Rename it to "rom.zip".
5. Open a command prompt window and run the following commands:
Code:
adb devices
If your phones serial number shows up, continue. If not, reinstall drivers.
Code:
cd Desktop
adb push rom.zip /sdcard/
6. After its finished pushing, go to install within twrp and flash it.
when i typed in cd desktop it says "The system cannot find the path specified". and when i continue to adb push rom.zip /sdcard/ it says "cannot stat rom.zip: no such file or directory"
it worked, thanks for your help.
I hope you realized when you checked all the boxes, you checked to wipe the internal storage which holds all your personal data.
And you checked to wipe /system partition which house the operating system, of course there wouldn't be anything to boot into.
sent from xda premium app

Edited build.prop & Phone won't boot

I have a N9005 which has the stock Samsung ROM, the only modification made is that it's rooted with the Odin method.
I edited the build.prop file, and the system is stuck in a bootloop (just blank screen after the animated Samsung Logo).
I made a backup of the build.prop file on the extSdCard.
What's the best way to get the phone recovered? (hopefully without doing a factory reset).
I tried using ADB but it doesn't recognise the phone (even with Samsung Drivers installed). When I boot into recovery mode the options are:
1) Reboot System Now
2) Apply Update from ADB
3) Apply Update from External Storage
4) Wipe Data/Factory Reset
5) Wipe Cache Partition
6) Apply Update from Cache
Thanks in advance for any help!
Install twrp. Mount system. Copy those build.prop from extsd into system using file manager. Then set permission as as chmod 744. Just play around in the twrp, all of the options(mount/file manager/permission) are in there.
Or flash stock rom with odin.
Sent from my SM-N920C
Is there a way to install TWRP without being in the phone? Most of the tutorials for installing TWRP requires you to install an app from the Play Store
Ok TWRP is installed, how do I go about copying the build.prop file from the backup to the /system directory
In twrp select mount. In select partition to mount list, tick system
Go back to main menu. Select advanced>file manager. Browse to the build.prop in your externalsd. Select the file. You'll be prompted with several options. Choose copy file.
Navigate to system. There is a select button. Press on it. Automatically it will prompt to copy the file.
Back to main menu. Choose permission. Navigate to system/build.prop. select it. You'll be prompted with a few options. Choose chmod 755
Reboot
Sent from my SM-N920C

How to install a rom with TWRP (for NOOBS)

Download Revolution Rom 5.8_15s for Le Max2 onto your c:\ drive of your PC. Reboot your device into fastboot mode (make sure you have your USB cable attached and the drivers loaded on your PC for ADB). Next make sure you have the twrp.img downloaded and copy it to your ADB folder. Then open up a command prompt session. Change the directory to your ADB directory. Type <adb devices>, this this will start the server and return info from your phone (provided you have installed the drivers). Verify that you can see your device in Windows File Explorer. If you can see the device and its' internal storage proceed to wipe everything. That means Dalvick, cache, system, data and internal storage. That is a clean install. Once it is all wiped, go back to your pc and copy the rom from you c: drive to your internal storage. Once the copy is complete you should still be in TWRP on your device. Simply go to <INSTALL> and flash the rom. If you have done everything properly upon completion of the install, reboot into system. All should be good.
Before you react to a problem, most of the time you can find the answer on this site. Therefore, you should always do a search first. More than likely, your problem has already been answered. Always check first!

Categories

Resources