I have been using VEGAn-Tab Ginger Edition for about 2 weeks and it was nearly perfect. THEN, yesterday I started the Tab and it only made it to the "G-TABDEVs" screen and stayed there.
I turned it off and every start gave the same response.
I applied the NVflash and only got past the Viewsonic bird screen then the Gtablet screen got stuck...same.
I applied the NVflash with the CWmod in part 9 and was the same, but now I can access the CWmod screen.
I tried to partition (2048, 0) and it gets stuck every time (have to power down)
It seems that the partition table or something is lost or corrupted.
I can not perform any of the CWmod commands, it just freezes and I have to power down.
Is there any other way to set partitions or does this seem like another issue.
I have looked tirelessly among all the great information here to no avail.
Thank you in advance!!
nevermind........ didnt read carefully and my answer was not going to be helpful so I deleted it
Ditto for me.. except
Except that my tablet will eventually run CWM, but everything is SSSSLLLOOOWWW............................................. as in 5 minutes to wipe cache, plus the 10 minutes and errors about "Can't mount /dev/block/mtdblock4 (Not a directory)" before I even get a menu in CWM.
All of this happened after flashing Clemsyn's latest PIMP kernel (and wiping appropriate areas, cache and Dalvik)... obviously the two incidents seem related, but I see reports of folks on the forums running this combination all the time and my tablet booted three times with no problem before it experienced terminal slowdown...
So why the "nevermind"... how was this fixed?
Not fixed yet.... Don't know what the "nevermind" was about...
Oh, OK, sorry. possibly a mis-post... I am currently backing up my internal SD card and preparing to NVFlash, repartition and reformat my internal SD card and load everything new. I am hoping that the issues are filesystem related and that a total clean out will fix it. I will most likely not use Titanium Backup to restore my apps, as that has been mentioned as a source of issues with the GB Vegan ROM - especially boot issues. Long process ahead - I have over 350 apps to sift and sort through manually - not looking forward to it...
I will post here if this fixes the problems in the chance that our issues are related.
heliav8r said:
I have been using VEGAn-Tab Ginger Edition for about 2 weeks and it was nearly perfect. THEN, yesterday I started the Tab and it only made it to the "G-TABDEVs" screen and stayed there.
I turned it off and every start gave the same response.
I applied the NVflash and only got past the Viewsonic bird screen then the Gtablet screen got stuck...same.
I applied the NVflash with the CWmod in part 9 and was the same, but now I can access the CWmod screen.
I tried to partition (2048, 0) and it gets stuck every time (have to power down)
It seems that the partition table or something is lost or corrupted.
I can not perform any of the CWmod commands, it just freezes and I have to power down.
Is there any other way to set partitions or does this seem like another issue.
I have looked tirelessly among all the great information here to no avail.
Thank you in advance!!
Click to expand...
Click to collapse
Little more info.... Using ClockworkMod v2.5.1.1 Bekit 0.8
no problem accessing APX mode and applying NVflash.
After a full NVflash and reload, not restoring anything from Titanium Backup, i am running again. I am also booting faster... <1 minute. Not the simplest fix but it worked.
huntar said:
After a full NVflash and reload, not restoring anything from Titanium Backup, i am running again. I am also booting faster... <1 minute. Not the simplest fix but it worked.
Click to expand...
Click to collapse
This happened to me as well. I had vegan ginger rc1 running for a couple of weeks and then I chose to reboot the gtab because I couldn't get an app to work when I was trying to open it. Upon reboot, I got stuck in a boot loop. It would make it to the flashing vegan ginger screen and would just keep looping. I nvflashed and then got stuck at the gtablet screen like yourself. I had to nvflash with cwm built in to get back into cwm. It was a real pain and I thought my gtab was toast. I'm back running and haven't had a problem yet (knock on wood). But a few weeks have gone by and it is running stable.
heliav8r said:
Little more info.... Using ClockworkMod v2.5.1.1 Bekit 0.8
no problem accessing APX mode and applying NVflash.
Click to expand...
Click to collapse
Hi,
I'm having a very similar issue. I can NVFlash till I'm blue in the face bug I can't repartition the SDCARD; just hangs or spits an error (1.1 or 1.2). I notice that NVFlash only ever starts flashing at part4.img; wondering why it doesn't do the ealrier part2 etc.
How can I get the partitions fixed without CWMod as it ain't working for me. I've disco'd the battery also, no luck. All the flashing with and without CWMod works but I hit the bootloop or stuck on gtab logo (after birds). I'm really leaning toward "It's dead Jim"
Seems I have to repartition but can't do with CWMod of any flavour; also tried format.zip image; no joy.
HELP ME PLEASE!!!
jroger0707 said:
Hi,
I'm having a very similar issue. I can NVFlash till I'm blue in the face bug I can't repartition the SDCARD; just hangs or spits an error (1.1 or 1.2)
Click to expand...
Click to collapse
nvflash cannot fix your SD-card partition problems. See this post for why. You have to either use ClockworkMod or the system commands available in recovery mode to re-partition your SD cards.
If you can get a working adb set up, I can walk you through the steps to manually repartition the internal SD card.
WhyDidI
rajeevvp said:
nvflash cannot fix your SD-card partition problems. See this post for why. You have to either use ClockworkMod or the system commands available in recovery mode to re-partition your SD cards.
If you can get a working adb set up, I can walk you through the steps to manually repartition the internal SD card.
Click to expand...
Click to collapse
Thanks for the reply. I've got adb installed and working and have been trying to do it with parted and sdparted. I've tried sdparted -es 2048 -ss 0; it just sits there forever checking requirements. Parted can't seem to find anything. I don't have /dev/block/mmcblkXXX shown only mtd and loop (for current state at least)
I also tried mknod b 179 XX based on my good gtab to try to recreate but I'm a little over my head there so may be doing something wrong or missing additional steps.
For s+g I've uploaded dmesg for my good gtab and badtab. Some notable diffs including version; likely because one is Vegan 5.1.1 based and the other is 4349 based and the Warning and backtrace info. later in init.
This should help someone who knows what to look for.
Still trying and looking for help!
This is the kind of problem report that we'd like to see on the board, ie., one with log files and pertinent information.
Let's look at the important differences between the kernel messages. Lines prefixed with a '- ' are from the good kernel, and those prefixed with a '+ ' are from the bad kernel.
$ diff -u <(cut -d] -f2- JR_dmesg_GoodGtab.txt) <(cut -d] -f2- JR_dmesg_BadGtab.txt) | less
--- /dev/fd/63 2011-06-12 00:30:26.863474335 +0530
+++ /dev/fd/62 2011-06-12 00:30:26.943474334 +0530
@@ -1,6 +1,5 @@
- Initializing cgroup subsys cpu
- Linux version 2.6.32.9-00000-10.8.2-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #9 SMP PREEMPT Thu Oct 21 12:40:01 EDT 2010
- CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c53c7f
+ Linux version 2.6.32.9-00001-g0e0c333-dirty ([email protected]) (gcc version 4.4.0 (GCC) ) #1 SMP PREEMPT Fri Jan 28 14:45:21 EST 2011
+ CPU: ARMv7 Processor [411fc090] revision 0 (ARMv7), cr=10c5387f
Click to expand...
Click to collapse
The good kernel was compiled in Oct 2010, and the bad one in Jan 2011 by the same person.
- Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 btmac=95abe7131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](bootbmp),[email protected](logodata)
+ Kernel command line: [email protected] [email protected] vmalloc=192M video=tegrafb console=ttyS0,115200n8 usbcore.old_scheme_first=1 cpuid=200102 devicetype=1002 bspversion=0202100907 btmac=9c5ed6131a00 tegraboot=nand mtdparts=tegra_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](bootbmp),[email protected](logodata) recoverykey=1
Click to expand...
Click to collapse
This is where it gets interesting. I've formatted the differences in the NAND flash partitioning schemes for better readability:
Good gTablet:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=95abe7131a00
tegraboot=nand
mtdparts=tegra_nand
16384K @ 7424K (misc)
4096K @ 24320K (bootbmp)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
204800K @ 96000K (system)
222464K @ 301312K (cache)
Click to expand...
Click to collapse
Bad gTablet:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=9c5ed6131a00
tegraboot=nand
mtdparts=tegra_nand
4096K @ 7424K (bootbmp)
16384K @ 12032K (misc)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
253696K @ 96000K (system)
173568K @ 350208K (cache)
recoverykey=1
bspversion=0202100907
Click to expand...
Click to collapse
1. The second message fragment indicates that the bad gTablet is one of the non-standard (because newer?) ones with the swapped (misc) and (bootbmp) partitions. Mine is the same, and as a consequence I have to be careful about which nvflash files I use. For this gTablet, make sure you use the nvflash zip file which has a '46_2010112600' in its name, instead of this version: 'nvflash_gtablet_2010110500'. This latter you can use on your good gTablet.
2. Here's my gTablet's NAND flash partition structure:
Kernel command line:
[email protected]
[email protected]
vmalloc=192M
video=tegrafb
console=ttyS0,115200n8
usbcore.old_scheme_first=1
cpuid=200102
devicetype=1002
btmac=9c5ed6131a00
tegraboot=nand
mtdparts=tegra_nand
4096K @ 7424K (bootbmp)
16384K @ 12032K (misc)
32768K @ 28928K (logodata)
16384K @ 62208K (recovery)
16384K @ 79104K (boot)
204800K @ 96000K (system)
222464K @ 301312K (cache)
androidboot.hardware=harmony
Click to expand...
Click to collapse
and you can see that there are differences compared to yours. Your system partition has been expanded in favour of the cache partition following it.
Q: Did you try to install Honeycomb on the bad gTablet? That would account for the size differences.
- 0x000005dc0000-0x0000125c0000 : "system"
- 0x000012640000-0x00001ff80000 : "cache"
- tegra_nand tegra_nand: Block 0x97c is bad [chip=0,offset=0x12f80000]
- tegra_nand tegra_nand: Block 0xe52 is bad [chip=0,offset=0x1ca40000]
- 0x0000017c0000-0x000001bc0000 : "bootbmp"
+ 0x000005dc0000-0x000015580000 : "system"
+ 0x000015600000-0x00001ff80000 : "cache"
+ tegra_nand tegra_nand: Block 0xd25 is bad [chip=0,offset=0x1a4a0000]
+ 0x000000740000-0x000000b40000 : "bootbmp"
0x000001c40000-0x000003c40000 : "logodata"
Click to expand...
Click to collapse
Looks like you have bad blocks on both gTablets affecting the cache partition in both cases. This is not unusual for this hardware--I've got a couple in my system partition.
Next. From the good kernel:
Open SDIO2
- tegra-sdhci tegra-sdhci.2: request en gpio failed
mmc1: Invalid maximum block size, assuming 512 bytes
mmc1: SDHCI controller on tegra-sdhci.2 [tegra-sdhci.2] using ADMA
tegra-sdhci tegra-sdhci.2: probe complete
-
- tegra_sdhci_probe complete
-
- tegra_sdhci_probe
Click to expand...
Click to collapse
I'm not sure what this is, but the SD card controller seems to finish ok.
Now, we get to the problem message:
- mmc2: new high speed MMC card at address 0001
- mmcblk3: mmc2:0001 MAG4EM 14.9 GiB
- mmcblk3: p1 p2
- mmc_rescan out
+ mmc2: error -110 whilst initialising SD card
Click to expand...
Click to collapse
The bad gTablet is unable to initialize the internal SD card (mmcblk3) for some reason. The -110 is actually a -ETIMEDOUT error, meaning, "Card took too long to respond" to a command.
This could either be a kernel problem (you have an old kernel) or a SD card hardware fault. Get pershoot's latest Froyo kernel and see if installing it fixes the problem. boot-cm_2632.41-oc-uv-xtra-vfpv3_fp-060311.zip for the 1.1 bootloader or boot-cm_2632.41_newbl-oc-uv-xtra-vfp_fp-060311.zip if you have the 1.2 bootloader.
If an updated kernel does not fix the problem, you can
a) either send the tablet back for replacement, or,
b) open that gTab up and replace the internal SD card--if it's in a removable socket--with another similar capacity (16GB) SDHC card. You could also try removing the card and cleaning the contact points.
rajeevvp said:
This is the kind of problem report that we'd like to see on the board, ie., one with log files and pertinent information.
Let's look at the important differences between the kernel messages. Lines prefixed with a '- ' are from the good kernel, and those prefixed with a '+ ' are from the bad kernel.
The good kernel was compiled in Oct 2010, and the bad one in Jan 2011 by the same person.
This is where it gets interesting. I've formatted the differences in the NAND flash partitioning schemes for better readability:
Good gTablet:
Bad gTablet:
1. The second message fragment indicates that the bad gTablet is one of the non-standard (because newer?) ones with the swapped (misc) and (bootbmp) partitions. Mine is the same, and as a consequence I have to be careful about which nvflash files I use. For this gTablet, make sure you use the nvflash zip file which has a '46_2010112600' in its name, instead of this version: 'nvflash_gtablet_2010110500'. This latter you can use on your good gTablet.
2. Here's my gTablet's NAND flash partition structure:
and you can see that there are differences compared to yours. Your system partition has been expanded in favour of the cache partition following it.
Q: Did you try to install Honeycomb on the bad gTablet? That would account for the size differences.
Looks like you have bad blocks on both gTablets affecting the cache partition in both cases. This is not unusual for this hardware--I've got a couple in my system partition.
Next. From the good kernel:
I'm not sure what this is, but the SD card controller seems to finish ok.
Now, we get to the problem message:
The bad gTablet is unable to initialize the internal SD card (mmcblk3) for some reason. The -110 is actually a -ETIMEDOUT error, meaning, "Card took too long to respond" to a command.
This could either be a kernel problem (you have an old kernel) or a SD card hardware fault. Get pershoot's latest Froyo kernel and see if installing it fixes the problem. boot-cm_2632.41-oc-uv-xtra-vfpv3_fp-060311.zip for the 1.1 bootloader or boot-cm_2632.41_newbl-oc-uv-xtra-vfp_fp-060311.zip if you have the 1.2 bootloader.
If an updated kernel does not fix the problem, you can
a) either send the tablet back for replacement, or,
b) open that gTab up and replace the internal SD card--if it's in a removable socket--with another similar capacity (16GB) SDHC card. You could also try removing the card and cleaning the contact points.
Click to expand...
Click to collapse
Thanks alot; you seem to have a handle on this stuff. Ya, I've tried the 46 route. I end up in what appears to be an APX loop in that case; although I did try it as you suggested.. and this time I did it fresh in linux (typically in windows). My tab could very well be newer. I got it fresh last month from tigerdirect and it came with 4349. I can give you the s/n if that might help. Damn, if I knew the SDCARD could be in a socket I would have paid more attention when I had it open. So, now I'm back to Roebeet's 4349 stock w/CWMOD. Not sure I can mount SD-EXT anymore (been a while since I tried) but if I can does it make sense for me to update the kernel with the one you suggest (I have it now). I assume I just put it on SD-EXT as update.zip and then use CWMOD to navigate to it... Any suggestion as to why I end up in APX loop with 46 and not the others; doesn't that mean that the non-46 is my 'mapping'? If you can help further I would appreciate it; just let me know what to try and what logs, captures etc. I was thinking to dump my entire good gtab and put that on the bad one; but I don't know if that makes sense nor how to do it completely. I know of the dump_flash etc. commands but that's only a piece. HELP STILL!!
how can i tell if I have one of the non std gtablets?
I have mount /dev/block/mmcblk0p2 file exists error when wiping dalvic. I dont have any of the other issues.
tjsooley said:
how can i tell if I have one of the non std gtablets?
Click to expand...
Click to collapse
1. Check the kernel messages.
2. Or, use nvflash to get your partitioning scheme.
I have mount /dev/block/mmcblk0p2 file exists error when wiping dalvic. I dont have any of the other issues.
Click to expand...
Click to collapse
That's a harmless diagnostic. See this post.
And, BTW, that is not the correct error message string. For any sort of troubleshooting, it would help if you supplied the exact error messages in your posts.
rajeevvp said:
1. Check the kernel messages.
2. Or, use nvflash to get your partitioning scheme.
That's a harmless diagnostic. See this post.
And, BTW, that is not the correct error message string. For any sort of troubleshooting, it would help if you supplied the exact error messages in your posts.
Click to expand...
Click to collapse
I get this "E:Can't mount /dev/block/mmcblk2p2
(File exists)" when trying to wipe Dalvik Cache.
How do I fix it.
I see the link and the information is helpfull but how do i fix it?
Same error when I remove the external microsd card and try to wipe Dalvik
jroger0707 said:
I assume I just put it on SD-EXT as update.zip and then use CWMOD to navigate to it...
Click to expand...
Click to collapse
Correct.
Any suggestion as to why I end up in APX loop with 46 and not the others; doesn't that mean that the non-46 is my 'mapping'?
Click to expand...
Click to collapse
I'm not a nvflash expert--I've never needed to do a full nvflash--but, I suspect it is because your gTablet came installed with the newer 1.2 bootloader and the newer NAND-flash partitioning scheme. Roebeet, who's probably seen more gTabs than the rest of us ever have, can comment on this.
For your SD card problems, try the latest pershoot kernel. If that doesn't work, I can compile a custom kernel for you. While trawling through the MMC device driver source in the kernel I saw an option, which, if enabled, might fix the detection of your SD card. The option is only there to support marginal and quirky MMC SD cards and so it's normally left disabled.
Note that if the custom kernel fixes your probem, it won't be a permanent solution, as you'll have to come to me every time you decide to upgrade the kernel (or you'll have to compile one yourself from pershoot's or clemsyn's sources).
tjsooley said:
How do I fix it.
I see the link and the information is helpfull but how do i fix it?
Click to expand...
Click to collapse
1. Hardware fix: Always have an SD card with 2 partitions in the external SD card slot.
2. Software fix : Modify the ClockworkMod source so it doesn't print an error message if the second partition does not exist on the external SD card (or there is no SD card in the external slot).
3. User fix: Just ignore it.
rajeevvp said:
1. Hardware fix: Always have an SD card with 2 partitions in the external SD card slot.
2. Software fix : Modify the ClockworkMod source so it doesn't print an error message if the second partition does not exist on the external SD card (or there is no SD card in the external slot).
3. User fix: Just ignore it.
Click to expand...
Click to collapse
Thanks, Why would it come up one? it did not before.
I have a 16gb micro sd in the ext slot.
tjsooley said:
I have a 16gb micro sd in the ext slot.
Click to expand...
Click to collapse
Does it have 2 partitions on it? The first one a VFAT partition and the second an ext3 partition?
Related
[This method is now obsolete. I've created flashable zips for setting up dual boot. And flashable dual boot Nookie Froyo and Honeycomb ROMs. See my other post.]
I've successfully dual boot B&N stock eclair and nookie froyo, both from internal eMMC. Here are the steps to use my script,
1. Download attached dualboot.zip. Create a folder called 'dualboot' on your NC's SD card. Unzip dualboot.zip into this folder.
2. Download Nookie Froyo 5.9 base image from http://edencomputing.com/nookcolor/nookie-froyo-base-0.5.9.tar.gz and copy into the same 'dualboot' folder on SD.
3. Check you have these 3 files in SD's 'dualboot' folder,
dual-boot-files.tar.gz
dual-boot.sh
nookie-froyo-base-0.5.9.tar.gz
4. Make sure /sdcard and /media are mounted in NC. If they are visible on your host PC, umount if you are running Linux, or 'safely remove' if you are on Windows, or 'eject' in Mac.
5. From your host PC, run 'adb shell' to go into your NC.
6. At adb shell, run the following commands.
cd /sdcard/dualboot
busybox sh dual-boot.sh
7. After a few minutes and a lot of messages scrolling by, you should see a message says ">>>>>>>>>>>>>>>>>>>>Done". At this point, you can reboot the NC. Normal boot will go to stock eclair. Hold 'n' button during boot to go to froyo.
p.s. I've also modified the recovery boot keycombo (stock is Power + n) in u-boot.bin. Hold both Vol+ and Vol- during boot to go into recovery. Keep holding them till you are in recovery, no need to worry about how long to hold.
If you want to remove dual boot
1. follow steps in this post http://forum.xda-developers.com/showpost.php?p=11001928&postcount=66 to restore media partition to stock configuration. Note you need to make your own backup of media partition before trying this.
2. follow steps in this post http://forum.xda-developers.com/showpost.php?p=11014734&postcount=88 to restore stock u-boot.
Original steps kept below if you are interested to know what the script does
Here is how I have done it,
1. In stock rom partition 8 of internal eMMC is mounted as media. We can use a partition tool to shrink this partition to make enough room to create 2 more partitions, 1 for froyo system partition (mmcblk0p9) and 1 for froyo data partition (mmcblk0p10). The partition tool I used is GNU parted which comes with Koush's clockwork mod. You can download a pre-compiled copy from his git tree. It can be run on the NC itself.
2. Copy all files from nookie froyo's system partition into mmcblk0p9, and data into mmcblk0p10.
2. Copy nookie froyo's uImage into mmcblk0p1. The file name should be changed to uFImg, so that it can co-exist with stock eclair's uImage on the same partition.
3. Modify nookie froyo's init.rc in the ramdisk, to mount mmcblk0p9 as system, and mmcblk0p10 as data. Pack the ramdisk image, and copy into mmcblk0p1 as uFRam. Again we use a different name so it can co-exist with stock eclair's uRamdisk.
4. I've modified B&N's u-boot tool to detect whether 'N' button is pressed during boot. If it's pressed, boot using uFImg and uFRam. Otherwise boot using stock uImage and uRamdisk. Attached is my modified u-boot. Copy the u-boot.bin into mmcblk0p1 to overwrite stock u-boot.bin.
With this setup, if no button is touched during boot, NC will boot into stock eclair. If you hold 'N' button during boot, it will boot into nookie froyo.
One problem I've found is with the modified partition layout, when booting into stock eclair, media partition does not get automatically mounted. But I'm able to manually mount it.
Played around with the partition layout a bit. It seems if media (partition 8) is at the end of eMMC, it will be automounted in stock eclair. So my final partition layout looks like this,
Code:
Model: MMC SEM08G (sd/mmc)
Disk /dev/block/mmcblk0: 7944MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 32.3kB 74.0MB 74.0MB primary fat32 boot, lba
2 74.0MB 148MB 74.0MB primary fat32 lba
3 148MB 461MB 313MB primary ext2
4 461MB 7691MB 7230MB extended
5 461MB 938MB 477MB logical ext2
6 938MB 1941MB 1003MB logical ext3
7 1941MB 2311MB 370MB logical ext3
9 2311MB 2681MB 370MB logical ext2
10 2681MB 3692MB 1011MB logical ext3
8 3692MB 7691MB 3999MB logical fat32 lba
< standard disclaimers - I'm not responsible for whatever damage you did to your NC >
Very nice work. Will have a look.
Thanks.
Nice work. However, I have a concern. As we may have experienced, NC would sometimes randomly reboot itself. So there will be chances that first I boot my NC with nookie froyo, then it reboot and become 2.1 again...
Until a permanent solution is found, this dual boot will not be as effective as it should...
lazinase said:
Nice work. However, I have a concern. As we may have experienced, NC would sometimes randomly reboot itself. So there will be chances that first I boot my NC with nookie froyo, then it reboot and become 2.1 again...
Until a permanent solution is found, this dual boot will not be as effective as it should...
Click to expand...
Click to collapse
I think the problem is over-exaggerated. Since changing the stock governor to ondemand, i have never had a 2.1 reset. Additionally, i have NEVER had a NF (2.2) reset.
Anyway, thanks for the guide OP.. i am actually itching to do this myself...
Divine_Madcat said:
I think the problem is over-exaggerated. Since changing the stock governor to ondemand, i have never had a 2.1 reset. Additionally, i have NEVER had a NF (2.2) reset.
Anyway, thanks for the guide OP.. i am actually itching to do this myself...
Click to expand...
Click to collapse
I agree. the random reboot has only happened to me while on eclair, nookie froyo hasn't given me a single one.
Congratz to the OP for getting dual boot to work.
Does this affect Clockwork Recovery at all?
Can you still use the stock e-reader stuff if you put Nookie Froyo on it or do you have to dual boot in order for it to work? I mean the being able to read magazines and books and all that good stuff. Thanks
Maybe someone here can give me a hint.
I've managed to get a stable version of NF on eMMC. But I can't manage to mount sdcard. And if I mount media, it's corrupts my boot partition, as if it mounted on mmcblk0p1, which is maybe the case...
Any advice on how to edit my init.rc?
Thank you
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
It's not always just the JVM crash "reboots". I've had actual reboots. Sometimes, it's just JVM. Other times, it's an actual device reboot. I took care of the device reboot by using the Settings Profile method.
BugsBunny891 said:
I agree. the random reboot has only happened to me while on eclair, nookie froyo hasn't given me a single one.
Click to expand...
Click to collapse
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Click to expand...
Click to collapse
Once i put the wifi sleep policy back to Default my reboots stopped. I recommend people use waketimer to keep wifi alive while the screen is off. It was mentioned in the wiki.
Great job on the dual booting!
rookie1 said:
I've successfully dual boot B&N stock eclair and nookie froyo, both from internal eMMC. Here is how I have done it,
1. In stock rom partition 8 of internal eMMC is mounted as media. We can use a partition tool to shrink this partition to make enough room to create 2 more partitions, 1 for froyo system partition (mmcblk0p9) and 1 for froyo data partition (mmcblk0p10). The partition tool I used is GNU parted which comes with Koush's clockwork mod. You can download a pre-compiled copy from his git tree. It can be run on the NC itself.
2. Copy all files from nookie froyo's system partition into mmcblk0p9, and data into mmcblk0p10.
2. Copy nookie froyo's uImage into mmcblk0p1. The file name should be changed to uFImg, so that it can co-exist with stock eclair's uImage on the same partition.
3. Modify nookie froyo's init.rc in the ramdisk, to mount mmcblk0p9 as system, and mmcblk0p10 as data. Pack the ramdisk image, and copy into mmcblk0p1 as uFRam. Again we use a different name so it can co-exist with stock eclair's uRamdisk.
4. I've modified B&N's u-boot tool to detect whether 'N' button is pressed during boot. If it's pressed, boot using uFImg and uFRam. Otherwise boot using stock uImage and uRamdisk. Attached is my modified u-boot. Copy the u-boot.bin into mmcblk0p1 to overwrite stock u-boot.bin.
With this setup, if no button is touched during boot, NC will boot into stock eclair. If you hold 'N' button during boot, it will boot into nookie froyo.
One problem I've found is with the modified partition layout, when booting into stock eclair, media partition does not get automatically mounted. But I'm able to manually mount it.
< standard disclaimers - I'm not responsible for whatever damage you did to your NC >
Click to expand...
Click to collapse
Excellent work. How large did you make the mmcblk0p9 and 0p10 partitions and could you provde a link to android gparted? Thanks much.
runhopskipjump said:
Once i put the wifi sleep policy back to Default my reboots stopped. I recommend people use waketimer to keep wifi alive while the screen is off. It was mentioned in the wiki.
Great job on the dual booting!
Click to expand...
Click to collapse
^This.
solution worked for me as well.
BugmanXDA said:
Another thread claimed that the reboots people were having were the Java run time service rebooting, not an actual OS reboot.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Nope, I've never seen my NC have a Java VM halt, it's full OS reboots. My phone's ROM cook says that's generally a kernel panic, but I've never gotten any logs from the event.
If anyone is interested, I've managed to get NF on eMMC with mounting uSD.
Thought you should know.
Sam
Now that there is a stable o/c kernel for Froyo, I would like to do a dual boot installation; but the instructions (especially the packing ramdisk part) are still a little over my head. That probably means I shouldn't attempt it, but if anyone has any more tips, I'd appreciate them!
I'm creating a script to do the installation. Will update the 1st post once I tested it.
That would be great!
Sent from my LogicPD Zoom2 using XDA App
rookie1 said:
I'm creating a script to do the installation. Will update the 1st post once I tested it.
Click to expand...
Click to collapse
Wow fascinating work. Will this still work with clockwork recovery installed ?
What about with eclair 1.1?
Will both nookie and eclair be able to read from the sd card?
Sent from my Nook Color
The script does not touch recovery, besides changing the keycombo. So it will work with CWR installed. But CWR is not aware of the additional partitions (9 and 10), so I guess it won't backup and restore them.
Both eclair and froyo can access the sd card. In froyo /media is not automatically mounted. Not sure whether this is a nookie 5.9 bug.
Long missive below, so fair warning – I have put in as much detail as I can remember to help out troubleshooting and I have read every thread on APX mode I can find both on this board and others.
I’ve gone and done it now, my GTab formerly running VEGAn-Tab 5.1.1 is stuck booting only to APX mode. So what did I do, and what have I tried?
* Immediately after purchase, I loaded ClockworkMod .8, then VEGAn 5.1.1. Absolutely no issues.
* Started looking into the various kernels, decided to try Clemsyn’s since it seemed to support VPN’s without any hassle (I don’t have any Linux experience, so to me moving module files around is a hassle). It worked great, my VPN to home worked. I successfully upgraded several times to his Version5 without any problems.
* Loaded a ton of apps, the vast majority worked just fine. I loaded App2SD, and moved most of the larger apps to the SD card. I also I think moved LauncherPro to the SD Card, which caused minor problems later.
* Inserted a 512MB USB stick. It worked. However when the GTab rebooted with it in, I received a ton of FC’s for apps loaded to the SD Card that load on startup, including LauncherPro. I can’t remember what exactly I did to fix that, I remember somehow getting the regular launcher to load, then uninstalling LauncherPro and a ton of other apps. Reloaded those but didn’t move them to the SD Card. Everything back to normal.
* Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
* Yesterday I inserted a 4GB USB stick. It didn’t work. Rather stupidly based on my earlier experience with the 512, but confident I could fix anything that broke, I rebooted the machine with the stick still inserted. As expected, a ton of FC’s, this time though the apps were not loaded on the SD Card. Not good. I also could not get into the regular launcher to uninstall things. No problem, I was planning to switch to the Gingerbread edition of VEGAn anyway. I force rebooted (held the power button down about 10 seconds).
* The GTab came back to life in APX mode. Not good, but not fatal either. I downloaded NVFlash and the Win7 x64 drivers, I had no problem connecting the GTab and my laptop. Now feeling a little better, but still annoyed.
* Read the “[STICKY][ROM] nvflash FULL restore, using bekit's original image (Instructions)” thread on recovery backward and forwards twice to make sure I understood what I was doing. Came to the conclusion that all I needed to do at this point is unzip the two files (one with NVFlash, the other with the stock images) into one subdirectory, and run the .bat file. I did that, watched NVFlash create and format about 10 subdirectories, then load the images to them. NVFlash reported success, and my GTab rebooted into stock TnT. The usual FC’s on bootup, after chasing those away, I enabled WIfi, and let it download the latest firmware – 3588. It asked to install, I said yes. It asked to reboot I said yes. It rebooted into APX mode.
* Now I am really annoyed, this isn’t supposed to happen, though I did find I think 2 guys that are stuck in APX mode, looks like one returned his, the other leaves it on a dock and does not touch it. I don’t have the dock, I don’t like the stock TnT, and since I ordered the custom carbon fiber backing sticker and the “android eating the apple” sticker and they look great on the back I am not in favor of returning it at this time.
* So I spent another couple of hours on the web reading. I read the “[UTILITY] G-Tablet Format” thread on formatting the device, I downloaded that zip file, it looks much like the regular NVFlash recovery process. Actually exactly the same, but it looks like the .img files are different and the NVFlash file is different. It ran, and said it was successful. The GTab rebooted, and said I think “Magic number mismatch”. I rebooted again, expecting to see a magic number error, which would give me the greenlight to go into NVFlash Recovery mode, but failure - right back into APX mode. I wanted to do try the format and then restore to stock process back to back, but it seems that the machine has to reboot after any NVFlash action. Right back to APX mode, NVFlash to stock worked the same as before, loaded then APX mode on reboot.
* I tried using NVFlash to stock but adding CWM .8 on partition 9. No difference, right back to APX mode, no chance to get CWM to load. I read that using a single command to push only CWM to partition 9, then while holding down the plus sign pushing the image. That actually worked, it rebooted into CWM. Everything seemed to work as expected, I could mount the system and data directories, format them, reformat the SDCard, change it’s size to 2048/0. I tried wiping the DELVIK cache, it returned an error saying a file existed but then said it was successful. I don’t remember what it said when I did that the very first time when loading VEGAn 5.1.1, so that might be the expected behavior. Either way, I rebooted and right back to APX mode.
* I read somewhere that flashing CWM to partition 10 worked. I swapped around .img files so that it was pushed to 10 instead of 9. Upon reboot, it went straight to CWM. I had the same experience as before, upon reboot after that it went to APX mode instead of back to CWM.
* I popped the back off and tried booting while shorting out the 4 pins, no change, though I could get to APX mode anyway so I wasn’t expecting a miracle. The button next to those 4 pins didn’t make a difference either.
* I tried booting while holding down the vol- button, and again with both the vol- and + being held down. Neither worked.
* I downloaded the SDK to try ADB mode. It made me download the Java DK, no problem. The SDK does not see the JDK, but I didn’t reboot the laptop, since I was still in #Tegratab (thanks BadFrog for your help). I will do that when I get home and get ADB to work, but I don’t know what to do when I get that done. ADB works, I needed to load the 32 bit version of the JDK, even though I have an x64 machine. ADB works, so I am happy. Now to see if that helps the overall problem.
* I did after booting into CWM load VEGAn Gingerbread and Clemsyn’s GB Beta 2 kernel. After next rebooting into APX mode, I pushed CWM to partition 9, and it tried booting into GB but never got past the animated GB screen. I will try that again later today with 5.1.1 and the Ver5 kernel and see if it makes any difference. I can probably live with it booting into APX mode if I can push CWM to Par9 and get it to boot back into 5.1.1 when needed. z4root didn't help either.
* So in conclusion, I am stuck in APX mode no matter what I tried. I think it is partition related, because of the problems after inserting the USB sticks, and since it will reboot after NVFlash into whatever seems to be in partition 10. In the DOS world that is easy to fix, especially when doing a system wipe and rebuild. I tried using NVFlash to say partition 10 is the boot partition, that didn’t work, NVFlash actually didn’t seem to do anything and I had to do a CTRL-C to end it.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
* 1725CET 26 Mar 11 - Unit RMA'd to Amazon - I was on day 30 so off it went, the replacement just shipped so they will cross in the mail.
Bump for more visibility
Very nice detailed post - you certainly did your homework. With that in mind I don't think I have much to add.
Yes, I remember one user who would reboot into APX mode all the time. I think there was one other person who would reboot into Fastboot all the time. And I don't think those problems were ever resolved.
Question: What is the model # on your device? I want to make sure it's it's not a 320, as at least one user on this board got a 320 and not a 300 (he got it from SEARS online). A 320 is a 1GB "v2" Malata device and those nvflash files might not work with them.
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Yep, mine is stuck in APX mode and the only way to "boot" it is to nvflash it.
I've set it up with VEGAn 5.1.1 and another kernel and my wife uses it. It sits on the dock (charging) when she's not using it and is never turned off/rebooted. If it does go off, I just nvflash it to boot (using the --format_partition 2 command) and once it boots the bootloader and formats partition 2 it proceeds to run.
I gave up (and also since my wife is using it I can't test other methods to make it work) and will later probably get myself one of the newer tablets (Samsung or Motorola or Toshiba...who knows) and pass my fully functional Gtablet to my wife.
roebeet said:
Here's another suggestion before you give up. Since nvflash seems to be the problem, maybe try another nvflash such as the Adam. The Adam nvflash DOES work on the GTAB. Maybe it will "jump-start" something for you.
Adam nvflash (Windows): http://api.notionink.com/fix/windows/LCD.zip
Adam nvflash (Linux): http://api.notionink.com/fix/linux/LCD.zip
Normally I wouldn't suggest this, but you are ready to return so there's not much to lose. You can always re-flash back to 1105 bekit, before you return it. These files will alter the booloader to that of an Adam, but again you can undo with the GTAB nvflash if needed.
Click to expand...
Click to collapse
Good sugestion, but unfortunately the nvflash in the adam recovery rom is the same as the one in the FORMAT images (151K), it seem to be better under windows since it list partition in text, the other when asked for a list of partition output a binary files.
As for the bekit1105 I usually do (when trying other rom or tnt5) NVFLASH FORMAT IMG, THEN NVFLASH the 1105 with the partition #9 replacing the clockwork .8 alway worked for me.
If it was me I would try to re-partition under windows the flash section, I am not sure how to do it with adb but if possible I would do it there.
I also notived the unit seem to be making sure the flash is partitioned in 2 section (2GB/16GB) inside system/etc/inandop.sh maybe that would be a couple of command to run by hand in adb, I know partition of flash can be tricky at time and it may be the reason the unit is falling to apx..
Would be a good idea to extract the partition list to confirm all their size a legit too.. either way don't give up I am quite sure someone will figure out a way of those half bricked unit...
michaeljwestii said:
*
Decided I wanted a boot screen other than the birds, so I made one following the instructions in that thread. Like everyone else, my graphic failed on partition 6 but worked on partition 7. No problems after that.
Any suggestions, other than peel my stickers off and mail it back to Amazon.com?
* 1239CET 25 Mar 11 - Edited, I tried z4root, it didn't help my problem.
* 1345CET 25 Mar 11 - ADB now working. Win7x64 Ult.
Click to expand...
Click to collapse
I really think something is wrong there, the correct partition for the bmp is definitely #6 in my tablet,
however in the other recovery (nvflash_gtablet_46_2010112600.zip) in roebeet's dropbox the #6 and #7 are inverted... 16MB vs 4MB but their .cfg is correct
So if you flashed the bird on 7 it's a surprise for me that it worked...
also I am wondering did you change the size if the partition in the .cfg files prior to flashing ??? or did you simply swapped the files? I noticed a few post where people where changing the recovery partition without adjusting the size in the .cfg file...
I would really like to see the list of your partition...
sound like the geek way to ask a girl for a show
read this... http://forum.xda-developers.com/showthread.php?t=934023
your boot configuration table may be bad... so maybe another rom like roebeet suggested would help...
Actually it's bekit's dropbox.
Some of the newer gTAB's have partitions 6 and 7 reversed:
Code:
[partition]
name=BLO
id=6
type=data
allocation_policy=sequential
filesystem_type=basic
size=4194304
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
filename=part6.img
[partition]
name=MSC
id=7
type=data
allocation_policy=sequential
filesystem_type=yaffs2
size=16777216
file_system_attribute=0
partition_attribute=0
allocation_attribute=0x10
percent_reserved=0
filename=part7.img
My first gTAB (the one I currently own) was setup this way, but one dev unit I got in December had them reversed, and bekit had one that was reversed as well. I actually flashed the 1105 bekit image and it had worked for me, at the time.
I do not think the image can be the cause of this problem (as long as the size in the cfg is correct), however I think something is wrong in the early boot process in his case...
The guy in this toshiba forum are playing quite a lot with their partition with nvflash...
http://tosh-ac100.wetpaint.com/page/Repartition+Internal+Storage
Interestingly, reading my partition 11 on my tab end with an error...
Z:\>nvflash -r --read 11 part-11.img
Nvflash started
[resume mode]
receiving file: part-11.img, expected size: 209715200 bytes
/ 209584128/209715200 bytes receiveddata receive failure NvError 0x120000
command failure: read failed
like if the partition was not the correct size by a few bytes...
Roebeet...
I was looking at the ADAM recovery and I think it may explain why some tablet are boot looping or bricked...
the file name they use for the .bct files tell us something...
LCD\harmony_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_2K8Nand_HY27UF084G2B-TP.bct
They specify their FLASH (HY27UF084G2B) number in their boot config, this is probably due to the fact that they change their IC from time to time (flash are often on high allocation so manufacture often have more than one supplier) and those change seem to be important enough that they use it as their boot config... (bct probably need to match the memory... or even configure memory speed etc)
This mean that flashing with a BCT that is not specific to the type of memory installed may be bad... but there's no proof that viewsonic had unit with different memory, unless it's one of the difference between the 300 and 320 unit you where mentioning..
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
michael...
Did you try in nvflash to set the boot partition ?
--setboot N
sets the boot partition to partition N
roebeet said:
Interesting. One thing about the Adam and the VEGA that I always liked is that we have at least on vendor-based nvflash config from them. Even the Viewpad10s has one. But we never got an official one for the gTablet - bekit's version is fantastic and still the defacto standard, but it's not the vendor's.
I keep wondering if the latest holdout on their stock release is because they want to deploy an nvflash version. It's not in the realm of impossibility, given that the Viewpad10s already has one. And it would certainly be a good way to give users a backout in case the update.zip fails (Viewsonic, you reading this?). A vendor-based nvflash config would be a wonderful thing, if they offered it. Well, we can hope....
Click to expand...
Click to collapse
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
P00r said:
I think it would better and safer if people would do a capture of their unit rom instead of using a generic one as a backup.
Would be nice to see one from Viewsonic as well, I hope they hear you!
I tried to locate that viewpad recovery with no sucess, ca you point me in the right direction ? tnx
Click to expand...
Click to collapse
Well, it WAS here:
http://ap.viewsonic.com/in/downloads/
But now it seems to have been pulled. Weird. Maybe check back in a day or two. I already looked at their firmware and it's very similar to the Advent Vega 1.0.9 firmware (sister devices).
I have downloaded the VEGA image restore, they left inside the utility used to create the .BCT files
the help for this utility confirm the bct is linked to the flash chips
as well as to the image (not sure which...)
Usage: buildbct [options] Configfile ImageFilename ChipName
options:
-h, --help, -? Display this message.
-d, --debug Output debugging information.
Configfile File with configuration information
ImageFilename Output image Filename
ChipName Name of the chip, currently valid --ap15
This mean using a generic bct may be risky if viewsonic have more than 1 type of hardware tablet with the same name...
Makes a lot of sense, to me. I honestly think we've been very lucky so far (most of us). Bekit and I must have the same device as his backup has never failed me. And, as you can imagine, I have flashed my device a LOT.
We don't know the hardware differences - why are some of the newer devices shipped with switched partitions? Why is it that at least one XDA user got a 320, when they paid for a 300? And if those Woot devices really are new, who's to say that the hardware inside isn't slightly different. Maybe our mods won't work on them regardless of what we do.
The other problems are that 1) Viewsonic isn't telling us and 2) we aren't keeping any metrics on this. We had this issue with the Pandigital Novel, but it was only two boards - eventually we could find ways to distinguish between the two (we called them "v1" and "v2" boards. I even opened them up and could tell that way. But, so far, we don't know if this is the case with the GTablet.
This 320 series will be interesting to watch
I do not think the order of the partition should have any impact, looking at other device they are all organised diferently, only their descriptor and file system seem to matter (YAFFS for the user accesible section) but it does show they played with it
Thanks for the comments and help
Thanks everyone for the comments and help. I checked Amazon and since I was on day 30, I did an online RMA and sent it back, so I didn't try the Adam idea. I did confirm it is not a model 320 though.
P00r - I did try the Setboot N command, pointing it at partition 10, since when I put the CWM image there it booted to it. NVFlash hung and I CTRL-C'd it after about 3 minutes.
When I swapped partition 6 & 7, I did swap the config info also, so the partition size and file system were correct per the cfg file normally.
The bad GTab and new replacement will cross in the mail, hopefully Gojimi's GB is out of experimental and into Beta by then
The whole BCT is still a mystery (to me at least). I've posted about that, and if I recall, responded to official viewsonic suggesting they provide info on that plus partition table, etc. I have yet to find any info on what the BCT actually is, but have seen from posts on wetpaint that messing with it or changing it can bork your device.
That's one of the reasons I'm still stock. Don't want to get into a situation where nvflash is the only resort.
The other reason I haven't tried to flash using nvflash is the bad blocks I mentioned awhile ago, and not being able to nvflash/read all my partitions. Figured that if it can't read all partitions, it probably won't be able to write them either .
Just ordered a 2nd Gtab from the woot deal, so I'm curious if that'll show bad blocks in dmesg, and if I'll be able to read all partitions w nvfash w the new one...
Jim
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
michaeljwestii said:
When the new tablet comes in, I'll pull the partition list and post it. Is there any other info from a bone-stock machine anyone would think is useful?
Click to expand...
Click to collapse
Happy to hear you cane exchange it!
Can you try extracting all the partition, I got an error on my partition 11, and I think Jim is right about the bct also used to map bad block in the flash...
I am just curious to see if this error is there on a virgin unit!
I can send you a batch files for the command
Gtablet specs:
Model number: Mountain Laurel
Android OS version: 2.2
Tap UI version: Mountain Laurel 1.0.0
Kernel Version: 2.6.31.9-00001-g0e0c333-dirtyhudson at tapntapsvn #1
Build number: FRF91
Problem: I got my gtablet in the mail and everything worked fine with stock on there. (besides for stock being, well, stock). I rooted and installed Mountain Laurel and proceeded to download and install many apps. That worked fine for a few days, and now recently, most (in all practicality all apps) apps force close and will not run. I would love to hear suggestions on how to fix this, or even be pointed in the right direction of where to find the answer. Many thanks.
P.S. I believe the build I had before Mt. Laurel was. 4349 (or whatever that build was if I missed a number or two)
creece09 said:
I would love to hear suggestions on how to fix this, or even be pointed in the right direction of where to find the answer.
...
P.S. I believe the build I had before Mt. Laurel was. 4349
Click to expand...
Click to collapse
This could be the root cause of your problems. Follow the instructions in the first post to repartition your internal SD card.
And, if you need to install ClockworkMod recovery, use the 1.2 version of ClockworkMod instead of the one suggested in that thread.
Thanks for your response!
Once I reparition the sdcard, and reset back to factory, that will make my gtab back to factory settings like I just opened it, correct? Then I can go back in and install my custom rom of choice along with reinstalling all of my apps. Is there really a need to do a clockwork recovery? Does all that do is reinstall all my apps and user data? If that's the case, I can just go back and install the apps, I'm a college student home for the summer, time is like problems with the government, theres an abundance.
Thanks again for the help.
creece09 said:
Once I reparition the sdcard, and reset back to factory, that will make my gtab back to factory settings like I just opened it, correct?
Click to expand...
Click to collapse
It won't be factory settings. For that you'll have to nvflash or reinstall ViewSonic's original 1.2-4349 firmware. It'll be like a fresh install of Mountain Laurel, though.
Then I can go back in and install my custom rom of choice along with reinstalling all of my apps.
Click to expand...
Click to collapse
Yes, you can install whatever custom ROM you want after this--provided it is 1.2 bootloader-based. Doing a factory reset is anyway recommended when switching ROMs.
Is there really a need to do a clockwork recovery?
Click to expand...
Click to collapse
If your current recovery image lets you repartition the internal SD card and lets you do a factory reset, then there is no need to install ClockworkMod Recovery.
If that's the case, I can just go back and install the apps, I'm a college student home for the summer, time is like problems with the government, theres an abundance.
Click to expand...
Click to collapse
Good luck.
rajeevvp said:
. . . And, if you need to install ClockworkMod recovery, use the [url=http://forum.xda-developers.com/showthread.php?t=1165502]1.2 version of ClockworkMod instead of the one suggested in that thread.
Click to expand...
Click to collapse
Hi rajeevvp, which one are you talking about ? Download link ?
The above mentioned thread provided a link to CWM_3.0.2.8_rev5.rar which is the same that I've been using for a while. It does everything fine, except that it does not clean up all data from the internal sd card like the the old cwm 08 did after the repartition 2048/0.
With the old cwm 08, after the repartition, and after being connected to a pc, the pc shows a blank drive.
With the CWM_3.0.2.8_rev5, after the repartition, and after being connected to a pc, the pc shows all data there like nothing ever happened.
Would you enlighten us on this subject and/or is there a sure way to clean everything.
Thanks
Dave,
mydave1 said:
With the CWM_3.0.2.8_rev5, after the repartition, and after being connected to a pc, the pc shows all data there like nothing ever happened.
Click to expand...
Click to collapse
Are you also having a "Groundhog Day" problem?
Would you enlighten us on this subject and/or is there a sure way to clean everything.
Click to expand...
Click to collapse
If it isn't Groundhog Day, then this will wipe everything. You will have to repartition the appropriate SD card--or reformat the partition you wiped--afterwards.
Boot the tablet into ClockworkMod recovery, then type on PC:
Code:
C:\> [B]adb shell[/B]
~ # [B]ls -l /dev/block/mmcblk*[/B] [I]Find out what SD cards the kernel detected[/I]
brw------- root root 179, 24 2011-07-17 23:42 mmcblk3
brw------- root root 179, 25 2011-07-17 23:42 mmcblk3p1
brw------- root root 179, 26 2011-07-17 23:42 mmcblk3p2
~ # [B]dd if=/dev/zero of=/dev/block/mmcblk3 bs=64k[/B] [I]Wipe entire internal SD card[/I]
[I]If you have an external SD card[/I]
~ # [B]dd if=/dev/zero of=/dev/block/mmcblk2 bs=64k[/B] [I]Wipe entire external SD card[/I]
[I]Or, you can wipe selected partitions. Use the output of the
[B]ls -l[/B] command above as a guide to select partitions[/I]
~ # [B]dd if=/dev/zero of=/dev/block/mmcblk3p2 bs=64k[/B] [I]Wipe 2nd partition (/data) of internal SD card[/I]
Be warned that the dd command will take a long time to complete depending on the size of the SD card/partition. To shorten the time taken, you can add a count=n (where n is a number) parameter to the dd command line. But, this requires you to know some esoteric filesystem details for the wipe to be done effectively.
WARNING: Do not use dd on devices which don't exist! You must only use the /dev/block/mmcblk* devices listed in the ls output. Otherwise, dd will create a new file and fill up your recovery partition in short order and you will have to reboot to escape.
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
I believe I narrowed down my problem to needing to format the different mmcblk’s so I can get one of the different recoveries to restore the image. As to what I have tried and have not keep reading.
So one day decided to try cm7 via SD Card, and it looked impressive. However It said something about issues with the sd card. I had no Idea what it would do to the nook ( I should've read the the instructions more thoroughly)
So I reboot only to find the nook looping back to cwm recovery (it was rooted).
After some searching I try the Ubuntu restore. It got stuck at the MLO part, I decided maybe it takes a while and i guess it Zeroed out mmcblk5 (I guess i'm not sure of anything at this point). The only issue later I find is that Ubuntu doesn't do any formatting, it just blanks out the partition and reloads it. After that failed attempt CWM just freezes at the cardboard box
I gave this a try
http://forum.xda-developers.com/showthread.php?t=1663836
but it spends a while with 1 red x and then reboots into locked recovery.
Giving it another try, I start apply the method described in:
http://forum.xda-developers.com/showthread.php?t=1605664
but “scripts” zip file gives a 404 error at Drop box.... the other files worked like a charm. It did get me pretty close and gave me this state (3 drives formatted in ext, I just need the others to format and restore). Thanks meghd00t!
List of devices attached
0000000000000000 recovery
~ # parted /dev/block/mmcblk0
parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: MMC MAG4FB (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 16.3MB 15.7MB recovery
4 16.3MB 33.6MB 17.3MB boot
5 33.6MB 83.9MB 50.3MB rom
6 83.9MB 134MB 50.3MB bootdata
7 134MB 522MB 388MB factory
8 522MB 1164MB 642MB ext4 system
9 1164MB 1611MB 447MB ext4 cache
10 1611MB 14.5GB 12.9GB media
11 14.5GB 15.6GB 1139MB ext4 userdata
So now I am trying
http://forum.xda-developers.com/showthread.php?t=1545766
See post#2. However I am no linux guru and I am stuck at the step that says
Copy device and vendor folder from Nook-Tablet to ~/android/system/
I followed the instructions on
http://forum.xda-developers.com/showthread.php?t=1570022
To setup ubuntu on the vm box. I can connect to the nook via adb on windows 7 but it refuses to work from Ubuntu, it just wont show (I added the adb_usb.ini and launched adb via sudo). I tried to pull from windows but it doesn't look right and think it would be best if I pull it from Ubuntu.
P.S.
Oh also, since I reason that my partitions are pretty much gone I tried to pull it from the cm7 sd image. unless someone knows how for me to mount the mmcblk’s and extract the needed files from there.
Fixed Somewhat ...
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Please restart...
Riddler9884 said:
Well I found the missing files to get this method to work.
http://forum.xda-developers.com/showthread.php?t=1605664
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/showthread.php?t=1470910
However the nook just boots then it says: Please restart your device and try again, and powers down...
For some reason I cant get the acclaim_update.zip to work. Can anyone please help or send me in a new direction?
Click to expand...
Click to collapse
That is the notice that the Nook is trying to load Recovery but there is not a recovery.img
I note in the op that you tried Megd00t's repart. It is absolutely solid in my opinion. I even intentionally bricked my nt8 to film the video that shows how to make it work.
If you try it again, you should be able to use an SDCard version of Clockworkmod to flash any *.zip to the device. See my series of videos here: http://www.youtube.com/playlist?list=PL676779C4F7BE8FEB&feature=mh_lolz
PM me if you have questions. I have not yet finished the accompanying articles describing the processes.
I am stumped
I performed this again
http://forum.xda-developers.com/show....php?t=1605664
with the added lines from the DD recovery
for blocks 7, 8 and 9
No go - It boot loops the stock recovery
Then I applied the Ubuntu recovery.
http://forum.xda-developers.com/show....php?t=1470910
Same result - It boot loops the stock recovery
by what I read both of these are supposed usually do the trick but it still doesn't do it. I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Stock cannot be flashed without mod
Riddler9884 said:
I followed the advice that cwm should be able to apply any zip
but the stock bn update zip doesnt work
acclaim update fails
heck the ribbon rom fails
it gave a status one. What am I overlooking?
Click to expand...
Click to collapse
My error. (Sorry) The B&N update file (the BN acclaim update is the same) cannot be flashed without modification. Meghd00t posted a "howto" I believe but I don't have a link right now.
However, you SHOULD be able to flash the Ribbon Root and other custom ROMs using CWM. I don't know where you should go now...
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
Riddler9884 said:
Would there be a way to make a disk image of the entire nook with all the sub partitions defined?
It would have blocks 1-9 with their stock info and the rest of the partitions zeroed out. So they loaded with info when you boot to recovery?
Click to expand...
Click to collapse
I believe that is Albert Wertz's process. You might want to check it out. His file is a CWM "Backup" image that you should be able to "Restore" (with CWM). Might be worth a try...
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Riddler9884 said:
Well I am not sure but I believe what fixed it was:
repartitioning the Nook using: http://forum.xda-developers.com/showthread.php?t=1605664
Then Using: SD_R3NT16or8gbV4_7
http://forum.xda-developers.com/showthread.php?t=1528625
I flashed flash-restore-stock.zip from:
http://forum.xda-developers.com/showthread.php?t=1545766
followed up by using the restore feature in SD_R3NT16or8gbV4_7
to complete the missing info
I almost got my nook back. Now I just need to work out how to get my sn back.
Click to expand...
Click to collapse
Hey sounds like you are almost there.
The sn is under the SDCard door. I saw a post somewhere on XDA about a process for manually putting it back in the device memory. Search here and Google.
Sent from my NookTablet using XDA
I tried
http://forum.xda-developers.com/showthread.php?t=1610069
I guess it works depending on how much you have cleared from the nooks internal memory in the process of restoring the nook.
I kind of put this together based on what I saw here
http://nookdevs.com/NookColor_Fix_Boot_Loops
Look at the section that says
echo -n -e "\x08\x00\x00\x00" > /mnt/devconf/BootCnt
i did a little research
Their method didn't work form me, but it gave me insight. I worked out the chmod by what was said here
http://forum.xda-developers.com/showthread.php?t=1586281
~ # echo -n -e "20201700########" > /rom/devconf/SerialNumber
~ # echo -n -e "20201700########" > /rom/devconf/DeviceID
~ #echo -n -e "5867########" > /rom/devconf/MACAddress
~ # cd /rom/devconf
/rom/devconf # chmod 440 MACAddress
/rom/devconf # chmod 440 DeviceID
/rom/devconf # chmod 440 SerialNumber
Update - It Couldn't Register but I did find this out by chance:
When I originally got my tablet and rooted the google play store saw this under My Devices:
(From a pc, Log in, all the way at the bottom, My Devices tab)
Maker-> Barnes&Noble
Model-> BNTV250
I went back in recently after restoring and got this:
Maker-> Bn
Model-> Nook Tablet
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
repart.img
Riddler9884 said:
Maybe one of the restores was messing with changing the name for Compatibility? I used so many things I cant tell where the above came from.
Click to expand...
Click to collapse
What is the ID that is displayed when you connect with ADB? In all of my (3 months) trial of being "bricked", I did not stop getting my serial number as the id when I connected with adb. But, nothing else on the internal memory worked. The only way I could use the Nook was with an external SD-based ROM (I used CM7a).
What I suggest is (repeat this after each different attempt to fix your issues): Try Meghd00t's repart.img again. Let it clear everything and restore back to stock. You might be pleasantly surprised! I sure was.
Here is a link to my step-by-step guide. http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Restore serial number on Nook
Riddler9884 said:
Nope no more, re-imaging the nook for this test. My wife will kill me if I keep ignoring her to tinker with the nook, Especially since it was for her to read her novels.
After loading albertwertz image and having access to android market and the amazon store has her happy.
Registering the B&N would just be a plus.... I need a tablet I will just get a Samsung 7 inch tablet.
Click to expand...
Click to collapse
I found this on one of Succulent's posts:
- To get your serial number back, you need to perform factory restore (8 failed boot method)
- The one that prompt,
Clearing data…
A reset is being performed.
This may take a few minutes
Click to expand...
Click to collapse
Here is a link to the thread: http://forum.xda-developers.com/showthread.php?t=1545766