Fix: How to fix "broken recovery" NT's - Barnes & Noble Nook Tablet

First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this. (You need to goto this thread to install the sdcard version and follow instructions.
First of all, make sure your drivers are setup properly as this is a windows script to fix everything since you can only fix it from a computer. (I CANNOT EMPHASIZE THAT ENOUGH!)
Then you just download this zip, it check's md5 sum on the image before flashing so no worries, and then it flashes. It will reboot when it's finished.
I am in NO way responsible should anything happen, it was your fault for not checking the app's md5 in the first place so if this works for you, openly admit that you could have been better with handling the app's flashing. <-- Required.
I'm having a seperate thread so I can actively update this with anything that may arise since it would make my app's thread cluttered.

Read the whole thread or enjoy a broken Ntab, it's your choice.

Just wanted to say thanks for the dedication to those of us not smart enough to figure things out on our own.
Sent from my BNTV250 using Tapatalk

is this for those nt cannot use sd card recovery or 8 times boot break to restore the originally rom?

Dumb Question
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.

Benblanko81 said:
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Click to expand...
Click to collapse
Means that you must have your nook drivers installed and working, if you ever rooted then you should have your drivers working properly.
~ Veronica

Can't get this to work
I have verified that I have the proper drivers (thanks Veronica). I unzip the fix and run the batch file, but the window closes almost instantly. I am using an XP machine, because of installing the drivers when I rooted. I can not for the life of me figure why it wont run. I am booted into the sd card version of CWM. Do I need to mount it some way or just at the home CWM recovery screen. I have been looking for help without asking and bothering, but can't figure it out. Not a noob but totally confused. Any help would be appreciated. Thanks.

Oops! I managed to set the wrong error levels on it, I meant to do 0 and 1, I instead did 1 and 2. Anyway, uploading now.

Still no go.
I got the batch file to run but it does not finish. It starts the Deamon successfully, and it just stays at Deamon Started Succesfully. It has been there for about 45 minutes. Should I wait or can I kill it and start over. Thanks again.

Kill it reboot your machine and start over
Sent from XDA premium using my Nook Tablet

No Go
Thanks Veronica, but the reboot still does the same thing. I just started the Nook&Zergy and the device shows up so I know the drivers are proper, it just stays stuck in Deamon Started Successfully for the fix. I am out of ideas, I fear I have just bricked my first device. I have doing this since the G1, this is sad.

No no, just do:
adb push cwm_internal.img /sdcard/cwm_internal.img
adb shell
then type:
dd if=/sdcard/cwm_internal.img of=/dev/block/mmcblk0p3

First off great work Indirect. This is exactly what I was hoping that image creator would be used for, just working on other things and got preoccupied. I think you might have to do some explaining though.
One thing to note though is that CWM should not be used for any other then rooting your device. As it stands right now there is no reason to flash it to an internal partition, you will only risk messing something up, as it has no gains.
Overview:​In the Nook Tablet world there is a locked bootloader, which requires that there be a Secure Chain from u-boot, to the recovery. With the exploit that bauwks discovered and designed, we are able to flash custom recoveries on to the device. However a recovery must be packed.
Packing Structure:​​There are two ways that we have been able to go about getting around the boot loader, the internal method requires that we use the second U-Boot, with a 256k buffer and then attache the recovery after the buffer.
(0-m bytes) ------> (m-256k bytes) ------> (256k-n bytes)
Bauwks ntBoot Buffer nemiths CWM
The trick is that that 256kth byte must contain the header for the CWM, and this is vital. If that is lost, or something on Bauwks didnt get flashed right, you will enter a boot loop.
FAQ:​
What Is a 'broken recovery' NT?
A broken recovery Nook Tablet is one where either the NT's internal recovery structure was not writen correctly or one where the NT's internal recovery structure is missing bauwks boot.
How can I tell if I have a 'broken recovery'?
Assuming you have not messed with any other partitions if you do either the N + pwr method, or the 8 false boots, you should see it open the BN recovery. If your device constantly turns on and off after one of these two methods, then you have a broken recovery partition.
My Nook just continues to boot into the recovery whats this?
Aha now that is not a 'broken recovery' and is actually quite fixable. In the nook Tablet there are two files that relate to the booting structure, aka the selection of where to boot from. These lie on a partition called bootdata, and are named BCB and BootCnt. If you are running stock on your internal partition, just let the stock recovery run, and it will solve your problem. If you are running CWM, you will have to use the following commands,
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
Aaa this is confusing can't I just put the stock recovery on my NT?
Sure. Hopefully indirect will make a script soon, or I will make one tonight that will put the default recovery img back. If you are feeling lucky you can do the following while on CMW.
NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU CAUSE TO YOUR DEVICE. One false move and you will brick your device. HIGHLY UNRECOMMENDED
Code:
adb push recovery.img /data (this is the recovery from the 1.4.0 or 1.4.1 update zip)
adb dd if=/data/recovery.img /dev/block/mmcblk0p3 (THIS LINE IS [COLOR="Red"]EXTREMELY DANGEROUS[/COLOR]. It should only be done as a last resort, and you should only do it if you are willing to take full responsibility.)

Dead End.
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.

Benblanko81 said:
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Click to expand...
Click to collapse
Oh well you should had started your first post by saying im using SDK and you will have it fixed faster. SDK is not needed in windows, leave that for devs all the necessary stuff that you needed to root is provided in indirects permanent root thread including drivers.
Glad it worked!
~ Veronica

Please help
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.

lehite said:
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
Click to expand...
Click to collapse
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica

lavero.burgos said:
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
Click to expand...
Click to collapse
Sorry if I was not clear. Here is the entire process:
1. I have a rooted Nook Tablet.
2. I installed Indirect's One Click App to install CWM
3. I used that app to install CWM.
4. I attempted to boot into CWM, but it flashes the box and then shuts off
5. I came to this thread and began following the instructions to fix it, but the fist set of instructions "First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this.(You need to goto this thread to install the sdcard version and follow instructions.)
6. I followed those instructions, but I still get the box image then shut down.
7. I can't boot normally or into CWM.
Let me know if you need any other information and I greatly appreciate your help.

What I really need to know is how to create the CWM sdcard on a mac. i.e. I don't have a linux machine with gparted and I can't figure out how to get something like Disk Utility to enable boot and lda flags.
Thanks!

bootable sd card with osx
Lehite, I was having the same problem, i.e. disk utility in osx couldn't do the job for me. I ended up using this method.
Download the “size agnostic” CM7 SD card installer image (v1.3 in my case), then write it to your microSD following the instructions on the before mentioned page. The writing takes a little bit without terminal telling you the progress, after 1-2 minutes it should be done.
After succesfully writing the image to your SD card copy the files from Goncezilla's SD Boot thread (here) to your SD card overwriting files if necessary and follow his further instructions.
On a reboot with the boot SD inside your nook you should get to the CWM menu after seeing the cardboard box. good luck!
I myself am also stuck at the black screen after the box and need to figure out how to get the ADB working on osx to be able to do Loglud's commands...
UPDATE: to get ADB working on osx I used this method. Since I'm not a developer I didn't download the whole SDK package from google but rather just the ADB tools from here.
I then connected the Nook to the mac while in CWM, checked if it was properly recognized but typing adb devices, and applied Loglud's adb commands. BAM! worked! Am back in android Many thanks to all for directions, especially Loglud.
Now a question to Indirect, I downloaded your package just today, while using it it verified the MD5 positively and continued flashing. Why did I get the black screen, and not the CWM?
cheers

Related

How I unbricked by Nook Tablet seconds before I gave up all hope

I busted my Nook Tablet, tried a hundred different things to fix it, and was about to give up, when I finally found the solution. This is my story.
Seriously, though, this forum has been a huge help to me, and I'm posting this in the hope that it will help someone.
First, a little background on me. I'm a software developer, and I've even contributed a bit to the development of the gingerbread-based CM7 for the Droid X. So I know a bit about Android, but I don't pretend to understand everything, especially on the Nook Tablet. That will become clear as you read the rest of this because I can't really explain some of the things I experienced.
Using several of the helpful guides here, I successfully booted ClockwordMod Recovery off an SD card, rooted my tablet, and installed the CM7 alpha (http://forum.xda-developers.com/showthread.php?t=1481826). Since booting CWM off the SD worked so well, I didn't feel the need to install it internally. It was a beautiful thing.
By the way, in order to boot CWM from an SD card your tablet must be plugged into USB! At least that has been my experience, and it hasn't always been made 100% clear.
Then, I bought a new SD card - the one I used originally was borrowed from another device. The new one was 16 gig. I wanted to make sure I could still use it to boot into CWM, so I started out as before by writing the image found at
http://forum.xda-developers.com/showthread.php?t=1488035 to my SD card using Win32DiskImager.exe, which I acquired from http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14. But this repartitioned my 16 gig SD card down to 2 gig, so I used gparted in a Ubuntu VM to resize the partition to 16 gig.
I had all sorts of trouble getting into CWM with this new SD card. I don't really know why. Maybe the partition resizing was an issue, I'm not sure. But after lots of attempts, including plenty of failed boots, I started getting the dreaded black screen saying, "Please restart your device and try again. If you encounter the same issue, please contact customer service or visit: nook.com/tablet/support." I couldn't boot up CM7 anymore.
At this point I switched back to my previous SD card, plugged in the USB cable, and was thankfully able to boot into CWM. I tried the usually stuff. Reset data. Reinstalled CM7. Restored the backup of the factory ROM before I installed CM7. Nothing worked, I always got the "please restart" screen. Then I tried the 8 failed boots method to restore the factory state. It wouldn't go into the restore mode, just the same garbage again. At this point I figured I had really and truly bricked my device. This thread (http://forum.xda-developers.com/showthread.php?t=1397262) describing a similar problem didn't give my any confidence.
But since I could get into CWM, I realized I should at least be able to get into a shell via ADB and have a look around. Getting ADB working was a challenge, but eventually this post (http://forum.xda-developers.com/showthread.php?t=1363652), installing the USB driver attached to this one (http://forum.xda-developers.com/showthread.php?t=1354487), and adding the necessary line to adb_usb.ini (see the runmefirst.bat in the previous link) got me up and running with an adb shell.
I suspected my problem had something to do with triggering factory reset mode with so many failed boots, and somehow that factory reset mode was broken. With that in mind, I eventually stumbled upon this post (http://forum.xda-developers.com/showthread.php?t=1444630). I use CWM to mount /bootdata, logged in from my computer with "adb shell", and issued the dd commands the post described to reset the BootCnt and BCB files. I had to remount the bootdata partition read/write with "mount -o rw,remount /bootdata". If you do this once and still get a "Read-only file system" error when you do the dd command, just try the mount command again. I don't pretend to totally understand why that would be necessary, but it seemed to be necessary for me.
The first time I tried this and rebooted, I still got the same "Please restart your device error." It took me a couple of tries to figure out that I had to issue these commands and then remove the SD card before rebooting. It seemed as if booting from the SD card somehow re-poisoned the device so that even once I removed it I was still in a bad state.
Once I did this my device booted back into CM7. I shut it down, used the 8 failed boots method, and was able to reset to factory successfully. So apparently I was in some sort of badd BootCnt/BCB state, but it wasn't just the regular 8 failed boots state. I'd love to hear an explanation of why this might be, if anyone knows.
TL;DR: if you get a "Please restart your device and try again" error and nothing seems to fix it, try this:
1. Boot into CWM off an SD card
2. Mount /bootdata via CWM
3. Log in from your computer using "adb shell"
4. mount -o rw,remount /bootdata
5. dd if=/dev/zero of=/bootdata/BootCnt bs=1 count=4
6. dd if=/dev/zero of=/bootdata/BCB bs=1 count=1088
7. Remove SD card
8. Reboot
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
tien_ttm said:
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
Click to expand...
Click to collapse
Can you copy/paste the exact command-line you used? It sounds like you might have a space somewhere it doesn't belong, or something like that.
Yes, i copied command-line from your first post. I don't understand my nook tablet. It'll lost all the data and program that i have installed after i reboot it. It keep the data and program 2 months ago. I have copied some mp3 songs to internal card, after reboot it, all of songs disappear. I bought it from internet so i can't know what happened to it.
tien_ttm said:
Thanks Kring789 so much, i have a same problem like you. I do step by step as you wrote, but at step 4, i have a error message from adb shell "remount /bootdata
/sbin/sh: remount: not found". And i can't reset my nook to factory default, it still display "Please restart your device and try again". Help me!
Sorry for my bad English, i'm vietnamese
Click to expand...
Click to collapse
If I am reading your comment correctly, it looks like you're using the wrong command: typing 'remount' instead of 'mount', is that correct?
Yes, "mount -o rw,remount /bootdata" is one command, not two commands separated by a comma.
kring789 said:
Yes, "mount -o rw,remount /bootdata" is one command, not two commands separated by a comma.
Click to expand...
Click to collapse
I fixed this command-line. Adb shell did not show error, but NT still display "Please restart...". Hix, what's wrong with my NT
tien_ttm said:
I fixed this command-line. Adb shell did not show error, but NT still display "Please restart...". Hix, what's wrong with my NT
Click to expand...
Click to collapse
Paste your entire adb shell session in here and let me take a look. Also, did you remember to remove your SD card before rebooting?
NT8 will not boot except via SD
Thank you so much for posting this.
I have the 8gb model NT and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how it would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the warnings that you mention - or even a flash of light. No matter how I try to boot it (with or without cable, with or without the Nook button) or how long I hold the buttons down, it still remains with a BLACK SCREEN.
However, the SDCard will boot properly. I followed your instructions in the O.P. precisely and I did NOT receive any errors. However, it still will not boot internally.
I then tried Veronica's process to flash CM9 to the internal (which is supposed to work on NT8). The flash process (via SD/CWM) went properly and I did not receive any errors. However, I still cannot get anything to boot (except my SDCards).
If I put my CM7a (bootable) SDCard into the NT8, it boots and runs great! Likewise meghd00t's recovery/CWM sdcard boots and runs properly.
I can do ADB & FASTBOOT and I have even done the dd to download my partitions (for backup) and then dd copies from online. Still no joy.
However, even after dd'ing p5, ADB still reports my TRUE serial number? It seems that the dd to part5 did not take?
The only other thing that I have found, that seems significant, is the fact that when I am in CWM, I cannot mount the EMMC. I can ADB/shell into the device but that did not allow me to mount the emmc either.
Any ideas? How can I force the device to mount the emmc?
Unbrick & return NT8 to STOCK
This process did NOT clear my Nook Tablet (8GB). Neither did any of the other (previously existing) methods clear it. It was bricked and would ONLY boot with a bootable SDCard. Otherwise, it remained totally black.
However, Meghd00t's recovery SDCard did the trick. It should work for either NT8 or NT16 devices and restores the Nook to Stock configuration. I did NOT lose my serial number.
Find Meghd00t's thread here: http://forum.xda-developers.com/showthread.php?t=1562130
video
Kringle789, i can't understand your instruction... could you make videoinstruction?
P.S. please, help me. It's the brand new device for me and I'm very sad that I can't use it.
P.P.S. I can turn on CM7 from SD.
xstranger said:
Kringle789, i can't understand your instruction... could you make videoinstruction?
P.S. please, help me. It's the brand new device for me and I'm very sad that I can't use it.
P.P.S. I can turn on CM7 from SD.
Click to expand...
Click to collapse
I have... http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ the video is embedded.
Sent from my Nook Tablet using xda premium
videoinsruction
Thank you raywaldo, but this video about how to unbrick NT when there is no message "Please restart your device and try again..." (I have this message)
Thats why I need videoinstruction for unbricking by kring789
Sorry for my English and please help.
xstranger said:
Thank you raywaldo, but this video about how to unbrick NT when there is no message "Please restart your device and try again..." (I have this message)
Thats why I need videoinstruction for unbricking by kring789
Sorry for my English and please help.
Click to expand...
Click to collapse
Sorry but I haven't seen that message. Have you tried the obvious ... restart and try again. I suspect that you have. Don't have any other ideas.
Sent from my Nook Tablet using xda premium
restart
Yes. I have tried. Maybe...=)
Could you tell me how to restart device?
I want to do it again. Maybe I have done something wrong.
Restart
xstranger said:
Yes. I have tried. Maybe...=)
Could you tell me how to restart device?
I want to do it again. Maybe I have done something wrong.
Click to expand...
Click to collapse
To restart:
Hold the power button for 30 seconds to power off.
Release & then press the power button again until the "n" screen appears.
raywaldo
It doesn't work.
Thank you.
xstranger said:
raywaldo
It doesn't work.
Thank you.
Click to expand...
Click to collapse
is the back lite "on" ? what is you hold down the 'power' and the 'N' at the same time ?
old_fart said:
is the back lite "on" ? what is you hold down the 'power' and the 'N' at the same time ?
Click to expand...
Click to collapse
nothing had happend. It's still the same problem.
I suppose, I have damaged the booting section/s.
And I don't know what to do...(
Maybe that
I can't download CWM on SD. Can anybody help me? Please, give me some instruction.

[Q] Asus Prime bricked (Type 3): Donation if you can help me

Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?

Help Brick Help Anyone

Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!

At wits end with bricked 16gb Tablet

I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!

[Q] NT 16GB always boot to Recovery Mode only

Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
- I tried press Power and N button or 8 times fail reboots but it still boot into recovery
- I tried flash new ROM from sd card, and the status is shown Installing Update.... and then it shown Install from sd card completed!!! There was no any notification more (as usual). And after "completed" by this way, reboot and still went into recovery mode again
- I also tried flash new cwm version 6.0.x, wipe data, format system, data,.... and flash ROM again from sdcard but still didnt work.
- I also tried reset to factory default http://forum.xda-developers.com/showthread.php?t=1663836 but it still boot into CWM again and again.
- and follow many topics on google search but still no luck
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
I want to flash a new ROM, a fresh tablet to make a gift for my dad on father's day, but it is brick :crying::crying::crying:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
DavDoc said:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
Click to expand...
Click to collapse
I have adb set up, but it doesn't recognize my NT , it always boot to recovery mode
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
DavDoc said:
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
Click to expand...
Click to collapse
Hello DavDic,
Thank you for your help,
I follow your link and I success to boot from SD card, and CWM version is 5.0.5, then I success install the update.zip too, unfortunately after removing the sd card and reboot, it still boot to CWM version 6.0.2.9 - this is the version that I flash from ROM Manager before my NT is bricked (I flashed wrong device when I choose Nook Color in Rom Manager)
So I try to reboot again from sdcard, cwm version 5.0.5, then flash new CM10.1 ROM, and reboot and still go to CWM 6.0.2.9
and again, I boot from sdcard, cwm version 5.0.5, flash to new cwm version 6.0.2.9, flash new ROM and still boot to CWM screen
So, I can create and boot from a Sdcard, But can not boot to OS, always go to cwm 6.0.2.9 screen (that I think the wrong file since I flash from Nook Color file ). Thank you!
h a l t said:
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
...
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
...
Click to expand...
Click to collapse
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
digixmax said:
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
Thank you, I did but no luck still boot to recovery mode
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
DavDoc said:
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
Click to expand...
Click to collapse
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
h a l t said:
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
Click to expand...
Click to collapse
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
DavDoc said:
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
Click to expand...
Click to collapse
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
h a l t said:
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
Click to expand...
Click to collapse
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
DavDoc said:
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
Click to expand...
Click to collapse
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
h a l t said:
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
Click to expand...
Click to collapse
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
F5, F5, ..... I see the light at the end of the tunnel,... God, what is the adb, shell command to help me escape this trouble :angel::angel:
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
These two files are in the /bootdata partition (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for a list of the NT partitions and their content).
But if OP's flashing Succulent's flashable_fix_bootloop.zip (which basically re-install a fresh copy of these two files) didn't fix the problem then he might have wiped out some other critical components of the system.
I follow Adam's guide, unbrick my NT, and then flash new CM10.1 ROM perfectly.
Thank you again DavDoc and digixmax for helping me so much! :good:
Glad you got it working again
Sent with my Dinc4G

Categories

Resources