I just restored my Nook tablet (16GB) to stock from CM10 and decided I wanted to run CM7. I installed it, all worked fine but then I turned my tablet off and it just kept booting into CWM which kept giving me errors about not being able to mount cache. It was Bricked. I went through multiple attempts to fix the tablet. I first tried AdamOutler's tutorial because it looked easiest (I didn't understand ADB 3 days ago and now I do). It stopped on the the part where it changes MLO to zeros. I'm not a hundrad precest sure what happened but along the way I also lost my serial number (I'm guessing this is the mmcblk0p5 partition) and I'm guessing it may have been this because it was all zeros. I then tried lavero.burgos tutoiral and I did all this manually though ADB. This guide didn't work at all for my problem sadly. I then tried so****e's Tutorial which kind of worked. It did fix the error I got when I boot into cwm. The problem now was that it did not boot out of clockwork mod. I then realized that this process fixed the partitions and that AdamOutler's Ubuntu total wipe would work, which it did! I was so happy, then I discovered after I turned off, and it tried a restore process, my tablet I got the "Contact customer service" error. I then thought that maybe if I did this again and then booted into cwm and replaced the partitions from lavero.burgos mmcblk files (just recovery and factory files). That didn't work. I then tried to boot from a MicroSD card with the CM7 on it and that worked surprisingly, but its way to slow. Any help would be very appreciated.
P.S. I did try the one with the repart.img and I never got the Check mark, it just said it was going to turn off in 5 seconds.
DaltonHeintz said:
I just restored my Nook tablet (16GB) to stock from CM10 and decided I wanted to run CM7. I installed it, all worked fine but then I turned my tablet off and it just kept booting into CWM which kept giving me errors about not being able to mount cache. It was Bricked. I went through multiple attempts to fix the tablet. I first tried AdamOutler's tutorial because it looked easiest (I didn't understand ADB 3 days ago and now I do). It stopped on the the part where it changes MLO to zeros. I'm not a hundrad precest sure what happened but along the way I also lost my serial number (I'm guessing this is the mmcblk0p5 partition) and I'm guessing it may have been this because it was all zeros. I then tried lavero.burgos tutoiral and I did all this manually though ADB. This guide didn't work at all for my problem sadly. I then tried so****e's Tutorial which kind of worked. It did fix the error I got when I boot into cwm. The problem now was that it did not boot out of clockwork mod. I then realized that this process fixed the partitions and that AdamOutler's Ubuntu total wipe would work, which it did! I was so happy, then I discovered after I turned off, and it tried a restore process, my tablet I got the "Contact customer service" error. I then thought that maybe if I did this again and then booted into cwm and replaced the partitions from lavero.burgos mmcblk files (just recovery and factory files). That didn't work. I then tried to boot from a MicroSD card with the CM7 on it and that worked surprisingly, but its way to slow. Any help would be very appreciated.
P.S. I did try the one with the repart.img and I never got the Check mark, it just said it was going to turn off in 5 seconds.
Click to expand...
Click to collapse
Can you tell me how you got it back to stock? I've tried a few things but nothing worked.
jaydeekay said:
Can you tell me how you got it back to stock? I've tried a few things but nothing worked.
Click to expand...
Click to collapse
I think It was the Total Wipe that did it but I wouldn't recommend it unless you have no other choice. It could wreck it (like erasing the serial number, freezing on MLO, etc...)
Related
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
i'm stuck in bootloop too.
I'm no expert, but just out of curiosity, have you tried to get back into CW and format your SD to 2048/256? Maybe the partition is hosed?
1st, try to FORMAT with this tools: http://forum.xda-developers.com/showthread.php?t=974422
you can change the image #9 with CW, once format done, when it reboot, you will have a message error in RED just power it off and on again, you will be in recovery mode, now follow the NVFLASH here:
http://forum.xda-developers.com/showthread.php?t=861950
also you can change image#9 to CW this will get you back to the base of stock VS rom
good luck
Wysdym said:
Sorry guys, this thread could go on and on for a long time explaining what all has happened so I'll put the current problem here and all the junk that led up to it below in case anyone wants to troubleshoot.
First of all my MOST thanks to Roebeet the best most patient person I have worked with. I wish I could give 1000 thanks at once.
The current problem is that I am stuck in a bootloop that not even nvflash will recover. No matter what I do even Vol+/Pwr just leads to big triangle exclamation. Because I nvflashed it back to stock and tried to (stock security wipe/factory). Viewsonic/Gtablet boot loop over and over. Vol-/Pwr allows access to APX mode works, but flashing nvflash, result bootloop.
How did I get here?
- March 10th z4root, vegan 5.1, perfect. No issues, great!
- March 15th got a bright idea to run ubuntu on it. Followed steps perfectly, no go.
Magic Value Mismatch. Panic (flashed with nv flash, got tnt 5.00)
- March 16th Worked great but wouldn't copy any apps to sd. Got titanium backup to
move user apps to sd. Titanium crashed and I lost all my user apps. Frustrated so
decided to flash nv again and go back to Vegan. No go.
- Tried several different ways to run nv, update to 3885, z4root, cw.08 no go
- Tried nv, stock, wipe, cw.08 no go
- Tried nv, 3885, no cw, pwr/vol+, bootloop permanent.
- Apx linux install successful, bootloop permanent
Click to expand...
Click to collapse
Can you get back to a state where you can at least get into CWM, even if it is still bootlooping? If so, go into the advanced settings and perform a fix partition (use the settings 2048 / 0). Please note, this will wipe any data you have on your /SDCARD folder (which is the flash card disk installed on your gtab, not the microSD card you may be using)
I agree with butch1326.
You can't move on to other roms until you know the G-Tablet is working right.
I would try to either nvflash or load the regular way CWM and just get CWM working right.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
Once that is done, then I would nvflash the bekit image as is described in a bunch of threads. That will get you all the way back to one of the old, stock setups.
If you get that far successfully, the get on wifi and the OTA should update you to
3588.
Once there, you can take a deep breath, do a bunch of studying on what has been working and what has not, and then move ahead.
Rev
P. S. --- Changing too much too fast is poison in the IT world.
butchconner said:
I agree with butch1326.
If CWM seems to be working right, then I would re-partition -- but to 2048 and 0 (not what was given above). Then I would do a factory data wipe.
QUOTE]
I was under the impression that 2048/256 was the default for the Gtab and that 2048/0 was used primarily for TnT Lite builds. Was I mistaken on this? I'd hate to be giving out the wrong suggestions.
Click to expand...
Click to collapse
From what I gather android in general is 2048 0. I believe stock gtab may have come with something else but never saw a reason why.
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
butchconner said:
I'm pretty sure what jasco13 said is right.
I think way back last year when we started it may have been the other -- but ever since I can remember, the standard advice has been 2048 and 0.
Rev
Click to expand...
Click to collapse
Damn....I must be getting old. 2048/0 it is. My apologies.
Ronin916,
No need for an apology. It was what it was and someone improved it and it is what it is.
Enjoy.
Rev
SOLVED
For the replies and more, No.. cwm was wiped out and did not exist any longer so that was not an option.
This took a LOT of doing. I'm talking about over 4 hours of nvflash, replacing parts of nvflash with other parts of cwm .8 and more. I was walked step by step through by a few devs. Because they tell me that mine had "other" issues, it would be specific to my machine alone and probably not help anyone else to post all of it. (However, I did find an IRC for the dev chat and that made all of the difference) Thank you to all of you Roebeet, EJ, Bad, and all the rest!
I was told that you haven't bricked it until you pitch it in the water, so keep your heads up.
Thank you to EVERYONE who replied to me.
You are a great community of helpful gents.
i have the same problem as you! I need help=(
Come on man you gotta close a thread like this out! It leaves everyone else stranded by not doing so. Glad you got this fixed though.
I'm STUCK in the same spot.. are you ablet to post your fix? PLLLLEEEAAASEEE
HELP!! HELP!! Stuck in bootloop for days!!
Hello all,
I have been stuck in boot loop for two days now!! I have nvflashed about 50 times (even used the format utility too in the mix) no luck!! I want to flash back to stock, then update to 3588 and use either Illuminate or Roebeets Honeycomb rom.
If some one has had this problem, can you help with some steps to fix??
Please please help!! I am ready to throw the G-tab out the window!!
THANKS!!
Anthony
Have you tried repartitioning?
Try installing clockworkmod and fixing permissions?
Sent from my Droid using XDA Premium App
I would love to be able to re-partition or install CWM, but I can't get by the boot screen.
Is there another method other than NVflash??
Thanks for responding!!
You need to nvflash...
1) Use bekit's 1105 nvflash image
2) replace part9.img with the recovery.img from clockworkmod install zip
3) type in the command to nvflash but hold down the volume up key on the tablet while you press the return key to start it. Continue holding the volume up while the nvflash starts.
4) When the flash ends you should enter CWM recovery mode. Repartition and wipe everything
5) swap part9.img back into the nvflash image and nvflash one more time.
If you are still looping after that you'll need to force the tablet to load a stock update. It will require a little more tinkering with nvflash. Let me know if you need the additional steps.
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
This has probably been covered here previously, but i searched fro several hours and tried several different things before giving up and just asking...
I have an 8gb NT, and i was running CM7 on it. I installed CM7 with Clockworkmod on an SD, but i had installed TWRP locally on the device. I was going to flash CM9 on to the device today, so i turned it off and went to boot into recovery mode, but i quickly noticed that there was something wrong with cyanoboot. It just boots in to recovery, there is no menu, just a loop. In TWRP, everything i try to load comes back with a "can't mount..." error. I read in several places to try certain rom installs through clockworkmod, so i booted to the SD card, but that doesn't work either. I think it is probably an error with the partition tables, but i was unable to find anything telling me how to repair that, though i found a lot of places and articles that said that it can be done. Does anyone know what might have happened here, and more importantly, how do i fix it? At this point i would be happy to go back to stock if i could...
Hi,
I think I might have bricked my Nook. A (hopefully) brief recap of what I did and have tried..
Tablet - 16gb
I was rooted and running CM10 internally. Decided to retore the factory image (I've done this before with no problems) and it worked fine. Restored, set up Nook with B&N, and re-rooted with zip file.
Check things out and decided to go back to the CM10 back-up I'd done via TWRP and this is where I think I screwed things up...I was on rooted stock 1.4.2 with CWM and restored the back-up from CWM.
Since then the internal set-up has been screwed up.
I tried to restore is back to stock again, it starts, tells me it's loading the software, I get the green check mark, pull out my SD-card, the tablet reboots and I get the wonderful red arrow telling me to restart and I get the arrow again to contact B&N support.
I've tried to flash the factory image, got TWRP up and running, tried to restore my back up and it says it runs except for an error: "E: Unable to mount '/data1.'
Also tried to install CM10 again and get the same error about unable to mount data.
Any suggestions anyone? I can work the Nook from the sd card (though it's interesting going back to CM7 again [will have to create a CM10 version]) but would love to fix this....
Thanks,
NikkieL
Try using Adam Outlet Ubuntu Total Re Flash method. It fixes most problems with bricked devices.
NikkieL said:
Hi,
I think I might have bricked my Nook. A (hopefully) brief recap of what I did and have tried..
Tablet - 16gb
I was rooted and running CM10 internally. Decided to retore the factory image (I've done this before with no problems) and it worked fine. Restored, set up Nook with B&N, and re-rooted with zip file.
Check things out and decided to go back to the CM10 back-up I'd done via TWRP and this is where I think I screwed things up...I was on rooted stock 1.4.2 with CWM and restored the back-up from CWM.
Since then the internal set-up has been screwed up.
I tried to restore is back to stock again, it starts, tells me it's loading the software, I get the green check mark, pull out my SD-card, the tablet reboots and I get the wonderful red arrow telling me to restart and I get the arrow again to contact B&N support.
I've tried to flash the factory image, got TWRP up and running, tried to restore my back up and it says it runs except for an error: "E: Unable to mount '/data1.'
Also tried to install CM10 again and get the same error about unable to mount data.
Any suggestions anyone? I can work the Nook from the sd card (though it's interesting going back to CM7 again [will have to create a CM10 version]) but would love to fix this....
Thanks,
NikkieL
Click to expand...
Click to collapse
I'd suggest that you try flashing afresh a CM10 or CM10.1 build using SDcard recovery, using a method such as described at http://forum.xda-developers.com/showthread.php?t=2056626.
In case you're considering using one of the so-called "unbricking" tools, read this post http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 first before you pick the wrong tool that would permanently wipe out your NT's individual device specific data like WiFi MAC address, security certificate, serial number, etc.
Thanks very much! Worked beautifully! Nook back working again!
NikkieL
So how messed up am I?
I was wiping my NT 16gb and thought hey, I'll start from scratch cause thats what it says to do. Sigh.
Went through and Formatted each individually (in CWM 6.0.4.5)
boot\
rom\
data\
cache\
And then wondered why after I flashed my ROM that the thing wouldn't boot into it and kept booting back to recovery
Partitions should be the same I didn't delete the whole thing (I hope), I followed the instructions @
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
I get the n on startup and at this point I get to the lady video but I can't get past that as the touch screen no longer functions.
I tried the instructions @
http://forum.xda-developers.com/showthread.php?t=2037368
Which got me to a recovery and into CM7 but once again my touchscreen didn't work
Now I'm back to the stock 1.4.2 (after following the un-brick site) looking at that lady looking at me with her cold dead unmoving eyes since I can't say play her video.
Is there any recourse? Can any point me to a thread or a website where I can attempt a fix. I'd like to say that I understand this stuff, but as an example I deleted the contents of all my partitions so I can't be that smart. The touchscreen worked fine before I caused the issue.
Okay so fixed it, just needed to make a CM10 boot rom, get into that and flash the touchscreen from there. Ah, good days.
Thanks to all the people who wrote all these threads that finally let me piece my fix together!