Related
Okay guys, so here's a weird one.
My g-tablet was working great. Was running VEGAn-Tab Build, BETA 5.1.1, no reason to update it, because it did everything I needed. I finally had it to where I wanted it, then it all kind of started falling apart. Here's how.
I power it on and notice my home screen got all messed up for some reason (using launcher pro). All of the settings defaulted to the original. I tweaked it back to more or less how I wanted it, and when I had it back to normal, thought nothing better of it. Must have glitched out some how.
Then I notice a bunch of things starting to force close, specfically android market, amazon market, titanium backup, google services framework, launcher pro, etc. Odd thing is it would do it one at a time, but otherwise my tablet would carry on as normal.
I go ahead and restart the tablet, to see if that helps at all, and what do you know, the homescreen is messed up again! I thought launcher pro might have been the culprit, so I un-installed the app and rebooted... And launcher pro is still there.
I go ahead and delete it again and start deleting other apps, restarting the tablet, and no matter what I do, everything stays the same. time for some clockwork mod action. I go into clockwork mod, and try to do the factory reset option, thinking what the hey, I'll try anything right now. Hit it, mourn the loss of my user data, and reboot the system... and again, everything is still the same.
I hook up my tablet to the computer via usb, and it looks like I'm able to at least delete misc. files that way. But when I return to good old Tabatha (my nickname for Gtab) everything is stuck just the way it is.
Needless to say, it feels like I'm stuck in the twilight zone.
I know I should have researched it by now, but I'm going to finally look it up to see if I can recover with NVFlash (I know I know, very noobish of me, using strange roms and not knowing any of the basics).... but I'm increasingly worried I've got some kind of a hardware malfunction on my hands. Could it be the memory? The internal SD card?
Oddly enough, my tablet still functions... I can browse the web, hook it up to my computer, etc etc, but no matter what I do I can't alter the data I already have on my tablet. Can't delete things, can't change settings, update apps, etc. etc. Which makes it pretty much useless for what I wanted to use it for.
I finally realized what this is like. The movie groundhog day, and I'm stuck in the same day, over and over again.
Any help or input that might get me out of this mess would be greatly appreciated.
Phil: "I was in the Virgin Islands once. I met a girl. We ate lobster, drank piña coladas. At sunset, we made love like sea otters. *That* was a pretty good day. Why couldn't I get *that* day over, and over, and over..."
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
rajeevvp said:
This is now the second time that I've seen this exact same problem. I was in the process of troubleshooting the original one when the user returned his gTablet for replacement. If you can stand the deja vu, read this thread.
Do not nvflash your tablet--nvflash cannot fix SD-card related problems. Read this post for why not.
Instead, do this for me: Reboot the gTablet, then open a Terminal, or, use adb and run this command:
Code:
$ dmesg > /mnt/sdcard/dmesg.txt
Attach that dmesg.txt which will contain messages from the kernel to your next post.
I'll check this thread in the evening.
Click to expand...
Click to collapse
Thanks for the direction, at least I know it isn't an isolated incident. It's 1:45 AM where I am right now, and I have to wake up for work in about 5 hours... So I probably won't be able to get in depth with the follow up on this stuff untill after work tomorrow night (so long as the wife doesn't hog the computer )
Again thanks for the quick response, I appreciate you pointing me into some sort of direction. Can't wait to try to get this sorted out!
Currently trying to figure out how to get ADB going.... pretty intimidating, but I'm trying. I got the Java JDK installed, installing the SDK, but can't find the "SDK Setup.exe" file or even a USB driver folder in the SDK directory. Got a good resource for getting ADB set up?
Save yourself some trouble. Got to http://www.knoppix.org/ and download the latest Knoppix live CD image.
Burn it, boot it, then use the adb executable from this post. For simple things like just running adb, you don't need the entire Android SDK.
Get me a dmesg while inside ClockworkMod:
Code:
$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
ADB commands documentation
Thanks, I'll try it out sometime this weekend!
Well, I really screwed myself now. I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive. [Do I need to load the OS onto a flash drive instead?]
So I started messing with some stuff in clockwork mod. I apparently really goofed it, and I got a "Magic Value Mismatch" error everytime I tried to boot it up.
I looked up Magic Value Mismatch, and from there it pointed to using NVFlash to try to fix that problem. So tried that. After I flashed it, I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
I looked up this issue and apparently the key is to get into clockwork mod and do factory reset, reset cache, and partition the SD card to 2048 and 0, which I did... (per post #4 on this thread: http://www.slatedroid.com/topic/17501-helpstuck-in-bootloop/ ) but still no dice.
Not sure where to go from here, or if I can even get it to interface with ADB in its current state. Looks like I'm done for
Thanks for trying though
On second thought, I may have had a breakthrough, at least in getting ADB to see my tablet!!! Woohoo! It finally sees the device and has a serial number. Was following the device on this thread:
http://www.androidtablets.net/forum/viewsonic-gtablet-technical/5377-adb-g-tab-step-step.html
7. under the "[Google.NTx86]" section, paste the following:
Code:
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
save the file and exit.
But I have a 64 bit machine, so I finally figured it out and plopped that into the 64 bit portion of the .inf file. DOH!
So now let me see what I can drum up through the previous commands above.... though the parameters have changed now to be sure... Due to my haste things may have taken a turn for the worse.
To recap, now my tablet is stuck in a boot loop after having done NV Flash, after having screwed up some settings in clockwork mod trying to fix a "Magic Value Mismatch" error.
Tried:
$ dmesg > /mnt/sdcard/dmesg.txt
I just run this in the cmd prompt at my platform-tools directory where the adb is correct?
All it says is, "The system cannot find the path specified."
Am I doing something wrong, or is my tablet that messed up?
Okay, this is slightly weird. So I was browsing around in clockwork mod, and lo and behold, the original zip flies for vegan tab are all STILL THERE. So I reloaded them... And My tablet zips back to exactly the way I had it before!
Only this time, so far no force closes. This looks way too good to be true after what I've been through. I'm going to try modifying some files and settings and restart my tablet to see what it does. I'm pretty sure I can't be out of the woods yet. Allthough it is 3:33 AM as this is happening... magic hour. I may be going insane.
EDIT: Nope, was definitely way too good to be true. All my data is as stuck as it was ever was. But at least now I can get into it again. But now we're back to square one. Lemme figure out this dmesg business and get back to you. X(
So I would try issuing the following exactly in the command line at the adb platform tools folder:
$ dmesg > /mnt/sdcard/dmesg.txt
Is that code supposed to be copy and paste in? I don't seem to be getting anything. I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file. And you want me to do that while the g tablet is in recovery, correct?
FYI, trying to do it through Windows 7. Would that command only operate in the linux environment via knoppix?
Thanks
titobetlogs said:
I can do the following command and get the info to pop into the command interface:
adb shell dmesg
But I can't figure out how to save that to a text file.
Click to expand...
Click to collapse
Redirect the output to a file:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
titobetlogs said:
I got the Linux distro loaded but still couldn't figure out how to get ADB to work. For whatever reason, When I boot from the DVD, I can't download the zip from within linux (get errors) and I could not open the ADB command by navigating to where I have it extracted in my hard drive.
Click to expand...
Click to collapse
I suggested using Knoppix just because it is so easy to use adb in Linux. Broken-down steps for future reference:
1. Download and burn the latest Knoppix Live CD iso image. Check the downloaded file size. The .iso file should be ~700MB in size. Also, test the CD by booting it and then typing at the boot prompt: knoppix testcd
2. Boot Live CD and skip the creation of any partition or file to store user data. After all, we just want to run adb.
3. After Knoppix has booted into the desktop, run a browser, right click on the adb.zip attachment in this post, then select "Save Link As..." and save the zip file into /tmp.
4. Connect the gTablet to the PC via the USB cable.
5. Open a terminal window, then type in it:
Code:
hostpc$ [B]cd /tmp[/B] [I]Change to the dir. where adb.zip was saved[/I]
hostpc$ [B]unzip adb.zip[/B] [I]Unzip zip file[/I]
hostpc$ [B]ls -l adb[/B] [I]Check if the adb program was extracted OK[/I]
-rwx------ 1 rvp rvp 159620 Dec 1 22:23 adb
hostpc$ [B]chmod 555 adb[/B] [I]Make adb executable.[/I]
hostpc$ [B]sudo ./adb shell dmesg > dmesg.txt[/B]
Note 1: do not type in the shell prompt, 'hostpc$'. It is only there to show you what the screen should (roughly) look like.
Note 2: If adb says something like "device not found", just unplug the USB cable from the PC, wait a few moments, then re-plug the cable and re-run the adb command again.
6. Go back into the browser and attach the dmesg.txt file that is there in /tmp. You will have to tell the Noscript plugin to allow scripts from xda-developers to enable attachments. Right click on the page, then select the Noscript menu item, then choose "Temporarily allow xda-developers.com".
I thought for sure I finally had it back to stock, as the intro screen started to show the tap n tap logo... but i basically got stuck in a boot loop, tap n tap, then "n", then tap n tap, then "n", etc, until it dies.
Click to expand...
Click to collapse
I'm not surprised. If the files on the internal SD card cannot be modified then that boot loop behaviour is to be expected. Here's why:
Android requires certain partitions to exist on the system. These partitions can be either on the flash or on SD cards. The partitions are:
/system: This is where the binaries and system apps that come with the firmware are stored. This partition is usually mounted read-only to protect it. On the gTablet, this partition is on the 512MB built-in NAND flash chip.
/cache: As the name indicates, this is the partition used to speed up the execution of the Java apps. Temporary files are also created here. This partition too is on the built-in NAND flash chip.
/data: This is where user-downloaded apps are stored by default, and also where Android stores its system configuration data. This partition, on the gTablet, is on the internal SD card.
/sdcard: This is where user content like media files, books, and the apps moved to SD card are stored. This partition too is on the internal SD card.
The first 3 partitions are critical and Android won't come up without them being present (or, if there are any errors on them). Among these 3, only /system needs to be correctly populated (When you install a ROM, new stuff is copied here). The other 2 partitions, /data and /cache can be empty and the system will boot up fine--with defaults. In fact, when you select "wipe data/factory reset" in CWM, /cache and /data are re-formatted--effectively, wiped clean.
(There are 2 other important partitions on the NAND flash chip, but, these are not mounted because they don't contain a proper filesystem. You have to use special tools to create the contents of these 2 partitions.
The first of these is the "boot" partition. This one and "system" are re-written when you install a new ROM. The "boot" partition holds the Android Linux kernel. If you install a new kernel, only the "boot" partition is rewritten.
The second is the "recovery" partition. This contains a separate, and usually different (and safe), Linux kernel and a mini filesystem image. This is a fail-safe partition. Stock recovery and ClockworkMod sit here.)
In your case, nothing on the internal SD card can be modified, so the stuff in /data will still be from your old ROM. (nvflash also cannot modify SD card contents, as I mentioned before.) When the stock firmware boots up, it will find incompatible stuff in /data. Critical apps will then die. Android will restart them, they will die again. This is your boot loop.
Get me the dmesg output and then we'll run a few tests using CWM, but, judging from your previous posts, I don't think your internal SD card can be fixed. You have 2 options:
1. Return the tablet for a replacement.
2. If you can't return it, I can switch the internal and external SD cards on your ROM so that you can boot and use the system (almost) normally. But, this is a custom solution and you will need to have an external SD card in its slot always. Read through this thread.
Wow, you really know you're stuff! I'll see what I can get you later on in the day with regard to the dmesg, I'm currently still at work.
I had suspected a hardware error... bummer. I'll definitely be interested in seeing if I can just use the external micro sd slot to sub out for the internal sd card. I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Do you know if this thing takes 32 gb micro sd cards? That would be pretty awesome, I at least wouldn't feel too limited on space.
By the way, thanks for all your help on this, I know I'm a huge noob. I greatly appreciate your patience and taking the time to break everything down for me. I have absolutely zero background in programming or anything computer related, though I do find this stuff extremely fascinating! If I could rewind the clock and study this stuff in school, I would do it in a heartbeat.
Again, thanks so much, can't thank you enough.
titobetlogs said:
I would at least like this thing to be functional again, though I suppose I'll never be able to try any of the honeycomb roms when those get past alpha. Oh well.
Click to expand...
Click to collapse
No, you should be able to run whatever ROM you want. I'll send you an installable zip file, in a few days, which should get you going again on Vegan-Tab, at least. You'll just need to remember to flash this zip file right after you've flashed the ROM (of your choice).
Right now, I don't know if I need one zip file for each kind of ROM in existence for the gTablet, or, if I can use some scripting and do the internal/external SD card switch using just a single installable zip file. I'll look into this on the weekend.
Do you know if this thing takes 32 gb micro sd cards?
Click to expand...
Click to collapse
Yes, it does.
By the way, thanks for all your help on this, I know I'm a huge noob...
Click to expand...
Click to collapse
I was a complete noob to Android myself back in April of this year. I've picked all of this up in just a few months. I'm pretty sure you can do it too, with a bit of poking around in the system. Of course, having a background in Unix/Linux helps a lot.
In your honor, below are some inspiring lyrics from the Karate Kid soundtrack:
You’re the best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you down
You’re the Best!
Around!
Nothing’s gonna ever keep you dow-ow-ow-ho-how-ho-own
INSPIRING GUITAR SOLO
Dude! you're embarrassing me -- I haven't send you the zip file yet... and, you haven't sent that dmesg output I wanted.
I know I've been stuck at work and family functions every day this week so far. Hopefully I'll get to it soon
Finally got to this! Here you go! Thanks again!
titobetlogs said:
Finally got to this! Here you go!
Click to expand...
Click to collapse
Can't see any problems in that dmesg output. Time for some tests on the internal SD card.
Boot into CWM, then run on PC (on Linux run: sudo ./adb shell):
Code:
C:\SOME\PATH> [B]adb shell[/B]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I] Mount internal SD card partition[/I]
~ # [B]mkdir -p /sdcard/a/b/c[/B] [I]Make a directory tree[/I]
~ # [B]echo test > /sdcard/a/b/c/test.txt[/B] [I]Create a file[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Read it back again[/I]
test [I]Correct[/I]
~ # [B]echo 3 > /proc/sys/vm/drop_caches[/B] Flush kernel caches
~ # [B]cat /sdcard/a/b/c/test.txt[/B] Read it back again
test Correct
~ # [B]umount /sdcard[/B] [I]Unmount[/I]
~ # [B]mount /dev/block/mmcblk3p1 /sdcard[/B] [I]Remount /sdcard[/I]
~ # [B]cat /sdcard/a/b/c/test.txt[/B] [I]Reread file[/I]
test [I]You should see "test" here[/I]
~ # [B]umount /sdcard[/B]
You should see "test" after the kernel flush and the remount.
Next, reboot the tablet--back into CWM, then run the cat command again. `cat' should output "test", again, if the SD card is OK.
Here's a screen of the commands I entered and what I got back. Did I do anything wrong? Looks like something's a bit off.
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
This is the Q&A topic for [thread="20962941"]GTabCombOver[/thread].
Does flash player work on this rom?
I think only opera browser
Best HC Yet
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Flash
AeroToxin said:
Does flash player work on this rom?
Click to expand...
Click to collapse
Flash works for me in Opera, but it can be a bit touchy.
What version of opera and flash are you using? I downloaded opera mobile 11.1 because 11.5.3 gives me problems, I'll put in a url, push enter, and whatever I type goes away it tries to load the page and just stops (like I pushed cancel on loading the page). Then I was gonna download flash 10.3 and opera started acting up made the tablet slow and had to reboot.
USB and Wifi
markmac said:
I really like this ROM. Couple of items of note that i have seen. My Wifi started to error out. I have tried fixing it, but it still just reports error. I am going to try pershoots kernel. I had issues before with Clems HC kernel. Second I tried inserting a USB disk, and the status bar says USBDisk2 inserted, but it does not appear to be mounted.
Click to expand...
Click to collapse
Does turning it off and on fix the wifi?
I'll look into using a usb disk soon.
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
markmac said:
No just keeps going into an error state. It seems to be after modifying the WPA_Supplicant with Root Explorer, is when it errors. For work, my company uses LEAP and this is the only way i know of to get it to work. I have done it a hundred times with different ROMs. For some reason unless i leave the wpa_supplicant unmodified, it goes into error. I have double checked and re-checked to see i haven't made any mistakes.
Click to expand...
Click to collapse
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Let me know if there is anything i could test for you. This is the only thing holding me back from finally being happy with an HC ROM.
markmac said:
Sure. Basically I was adding the network, from the Settings applet to use 802.x. I would then modify the supplication to look like the following with Root Explorer:
Network={
ssid=”<networkname>”
scan_ssid=1
key_mgmt=IEEE8021X
auth_alg=LEAP
eap=PEAP
identity=”<domain>\<username>”
password=”<password>”
phase2=”auth=MSCHAPV2”
}
Only after i modified it did it error. Before i modified, the entry was still there, but in the default form which didn't work.
Click to expand...
Click to collapse
Is that the entirety of your wpa_supplicant.conf file or only a fragment? Because, there are other parameters missing, and it says "Network=..." instead of "network=...". Not sure if case matters in the wpa_supplicant.conf file, but, it is something to check.
A detailed debug output would help in troubleshooting your problem. Get it by doing this in CWM:
Code:
$ [B]adb remount[/B]
$ [B]adb shell mv /system/bin/wpa_supplicant /system/bin/wpa_supplicant.bin[/B]
$ [B]adb push wpa_supplicant /system/bin/wpa_supplicant[/B]
$ [B]adb shell chown root.system /system/bin/wpa_supplicant[/B]
$ [B]adb shell chmod 755 /system/bin/wpa_supplicant[/B]
Use this shell script as the wpa_supplicant to push:
Code:
#!/system/bin/sh
exec /system/bin/wpa_supplicant.bin -ddd "[email protected]"
Collect the logs like this:
1. Power off gTab.
2. Connect USB cable.
3. Run "adb logcat -v time > logcat.txt" in a CMD.exe window.
4. Power on gTab.
5. Kill the adb logcat or shutdown tablet after WiFi has errored out.
This will collect all the logs right from the beginning.
That was just the section I edited. I don't have my cable with me so i can't run ADB right now. I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
heapsize
What app can I use to change the heapsize? Also, dumb question.... What app should I use to adjust the overclocking?
markmac said:
I did just do the same thing on Flashback and it worked, but I prefer to run GtabCombOver.
Click to expand...
Click to collapse
Try using the wpa_supplicant binary from Flashback, then...
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cgingermany said:
What app can I use to change the heapsize?
Click to expand...
Click to collapse
Just edit /system/build.prop and change dalvik.vm.heapsize.
awesome, thank you! I'll give that a shot. On the dev page someone there said switching those up a little was helping with overall performance so I'll give it a shot and let you guys know. Thanks again.
gtabcombover said:
That would probably be the reason. GTabComb has a different wpa_supplicant from most ROMs, so it might not be compatible with the modification you are using. Can you give me more details on what you are doing to modify it?
Click to expand...
Click to collapse
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
dagwud said:
Actually, I'm having the same problem, and I haven't made any changes to wpa_supplicant.
The only way to get WiFi functioning again is to reboot the device. I can't turn off WiFi, because it just keeps saying "Error." I even tried going into airplane mode, but it made no difference.
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in." I don't remember having this problem prior to making that change.
I've changed it back to "Never" and will report on whether the problem persists.
Click to expand...
Click to collapse
Mine wont connect at all....... What am I doing wrong?
dagwud said:
In my case, the problem seems to be related to the fact that I've changed the setting for the wifi disconnect policy to "Never when plugged in."
Click to expand...
Click to collapse
Very unlikely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Code:
C:\> [B]adb shell dmesg > dmesg.txt[/B]
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
cgingermany said:
Mine wont connect at all....... What am I doing wrong?
Click to expand...
Click to collapse
Do a basic check. Look at the wpa_supplicant.conf file and see if it looks OK. As a minimum, for home networks, check that the ssid= and psk= values are correct:
Code:
C:\> [B]adb shell cat /data/misc/wifi/wpa_supplicant.conf[/B]
Again, will need to look at logs to find out what's wrong.
rajeevvp said:
Very likely.
Will need to look at logs to determine the actual cause of your problem. See post #12. Also get the kernel messages using:
Click to expand...
Click to collapse
I haven't had time to do as you've requested. However, restoring the setting to the "default" has alleviated the problem. The device appears to be turning off WiFi after a period of time, since it's often had to reconnect after I turn the screen back on.
I'll get to the logs when I'm at my computer and have the time to wait for the wifi error.
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.
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!