This issue was resolved by Meghd00t's new REPART.IMG file. See this post on that thread: http://forum.xda-developers.com/showpost.php?p=26060323&postcount=151cool:
I have the 8gb model Nook Tablet and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how the internal flash version would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the stock "reset" warnings - 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 the instructions on this thread ( http://forum.xda-developers.com/showthread.php?t=1515788) precisely to reset the BootData. I did NOT receive any errors. However, it still will not boot internally.
I then tried sigmabeta's process to flash CM9 (http://forum.xda-developers.com/showthread.php?p=25661314) to the internal emmc (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 (http://forum.xda-developers.com/showthread.php?t=1481826) 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 onto the device's partitions. Still no joy.
However, even after dd'ing a downloaded copy of p5 to the device, 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 I can get this thing to boot internally? How can I force the device to mount the emmc?
Click to expand...
Click to collapse
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Final "fix"
lavero.burgos said:
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Click to expand...
Click to collapse
Not sure that I have tried ALL of them, that is why I am still searching. Also, people come up with new ideas that have not previously been published.
Thanks for all YOUR help. Especially the dd to fix bootdata.
Sure wish someone would come up with a solution for this problem. There seems to be quite a few of us who are looking for answers.
Sent from my Nook Tablet using XDA
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Existing solutions
succulent said:
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Click to expand...
Click to collapse
Thanks for the info. I do appreciate it and I will be trying some of your suggestions later today when I get home.
One problem (that seems to be easing up a bit) is the fact that few posters distinguish WHICH version of the NT that they are working with. The NT16 "solutions" became the NT8 "problems." It would be great if everyone posted WHICH version they have.
The other issue is (as you stated) when you follow a guide to fix an issue, it CAN mess up your device even worse that it was. Then, you have TWO issues to deal with - rather than just one as before. I am afraid that is where I am now.
One question: You mention "compiling" CWM. Are you referring to the technical term of compiling code into an executible? Or, are you simply referring to the process of putting a working image onto an SDCard? I can do the latter without issue but I have never compiled code.
I do use Ubuntu Linux so many of the Windows driver issues are moot for me. However, I do have a dual boot with XP in on the other side - just in case I need to do some Windows-only stuff.
I really appreciate the help. I am no novice but I am not a developer either. I can usually search, read, try, and work out the problems that I (and other less technical users) experience. That is what my website is all about - translating the really "tech" jargon into everyday language for non-techies to follow. But this one has stumped me (and at least a few others) for the past couple of months.
succulent said:
I have learned that many people like to format things apparently.
Click to expand...
Click to collapse
Sent from my NookTablet using Tapatalk
I've noticed this as well. People really need to do more reading before randomly selecting/flashing things.
Related
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
I've seen a number of requests for this functionality and recently it became necessary for one user who had a disabled Home Key to clear cache and data without the use of ClockworkMod. I have reserached two methods to address this issue. These instructions require some familiarity of android, computer and tablet terminology and usage. Feel free to ask for clarifications in comments. Here we go...
Method I - Stock Recovery Command File
Technical: Stock Recovery command file can be used to perform a few additional functions as well as to alter the path to update files. These commands will execute with all privileges available to recovery mode.
Advantages: Very easy to use. Very little technical knowledge required. No third party software is required for use.
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Prepare a text file named "command" (no file extension) with one of the following commands on a single line. The wipe data command will wipe both data and cache. Wipe cache will wipe cache only.
--wipe_data
--wipe_cache
2) Place the file in a folder named "recovery" in the root directory of your MicroSD card.
3) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
4) Allow the command to execute completely then the tablet should reboot (this may not occur automatically depending on firmware installed).
Method II - Updater Script
Technical: The attached "Updater Scripts" perform delete commands (recursively if necessary) on the named directory or file(s). The directories are mounted automatically by the system before the script executes but it could be easily revised to include that step if necessary. The partitioning, formatting and directory structure are left untouched. Only files are deleted.
Advantages: No third party software is necessary for execution. Relatively easy to modify for more surgical precision (i.e. leaving installed apps but clearing possibly corrupted system data). Included example: "Clear Battery Stats"
Prerequisites: You will need a MicroSD card formatted FAT32 and a method for transferring files from your computer to the MicroSD.
Usage:
1) Download the attached archive (ClearData.zip) to your computer.
2) Extract the files to your computer. You should then have a folder named "recovery" (which contains a file named "command") and an additional archive named "update.zip"
3) Place the recovery folder and the update.zip in the root directory of the MicroSD card.
4) From a powered down state, insert the MicroSD card into your tablet and boot into recovery by powering it on while holding down the Volume Up key.
5) Allow the script to execute completely then reboot the tablet (this may occur automatically depending on firmware installed).
This will become handy someday.
Thanks for sharing your knowledge.
You're welcome. One quick note... the new stock recovery adds a menu simiilar to ClockworkMod. These methods will still work since the recovery folder/command file are checked first but it really isn't as necessary any more.
Need Help
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Me too
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
lrgche said:
Tried both methods above but either way I get to the viewsonic splash with the message "Booting recovery kernel image" in the upper left and it just stays there, stuck there, I left it for a long time to see and it never leaves that screen.
Any ideas?
Click to expand...
Click to collapse
That's an indication that you may have more serious problems. nvflash will be required. http://forum.xda-developers.com/showthread.php?t=861950
Once done you will likely need to install ClockworkMod and repartition your internal storage.
Loukoebel said:
I can't get into clockworkmod either. My machine is running faster. I almost hate to mess it more.
Click to expand...
Click to collapse
If your tablet boots properly but you can't get into CWM then it probably isn't installed properly (or at all). http://forum.xda-developers.com/showthread.php?t=865245
Keep in mind that CWM is NOT compatible with all ROMs. Make sure the developer for your chosen ROM recommends it before installing it.
Does your method in opening post have to be run from external micro sdcard?
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
K J Rad said:
Both methods are performed with an external MicroSD card. They will work from internal also but it is a little more difficult to get the files in place if your tablet is not booting properly.
Click to expand...
Click to collapse
so your method is a simple way to replace one of the main uses of Clockword MOD?--Plus you stay stock more or less.
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
K J Rad said:
That is correct. Method II can also be modified to be less intrusive (leave user apps installed) or embedded into update scripts to perform a wipe during new ROM installs.
Click to expand...
Click to collapse
Wipe data does what--remove the apps installed?
And the partitions?
Your post is very interesting. It implies that you have a knowledge of the g-tabs partition structure. I have played with Linux off and on for the last 10+ years. When I began, I used Slackware and when you set it up you had to manually create partition tables using fdisk. You were only required to create two - the data partition and a swap partition but it was often recommended that you create several others - one to contain the home directory to prevent users from using all the disk space (in the days of small disks) for example. It appears that there are a lot of partition on the g-tab. Up to now, I have used various wiping tools like clockwork or calkulins wipe all on faith. I would really like to know what all the partitions are and what is in them. I have used terminal to get to the root folder and tried to do an fdisk to display the partitions but try as I might everything remains hidden. It would seem that a script like yours could be adapted to do many things but I would certainly want to understand the structure a little better before I did anything. I have searched and been unable to find that information. Can you point a way for the curious to learn more about the partition structure on the g-tab?
Wish I had a direction I could point you in. What I've found so far has mostly been stumbled upon while looking for something else. What I can tell you is this...
1) When using fdisk in Android you must specify the device to look at. Try something like: fdisk /dev/block/mccblk3 That should list the current partitions as defined by CWM or whatever was used originally.
2) Within one of those partitions in the list generated above are sub-partitions holding the bootloader, system, data, etc partitions. You can see how they're described in the .cfg files in the nvflash restores that are lying about.
lsu205 said:
Wipe data does what--remove the apps installed?
Click to expand...
Click to collapse
Removes user apps and their associated data as well as system related data and settings.
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
CodeNamePapa said:
K J Rad - any idea if the partition size can be set with these methods (2048 & 0) in case I can't get clockwork installed?
Click to expand...
Click to collapse
I'm looking for a solution to that problem. Unfortunately these methods still require the ability to get into recovery mode which likely won't work if you're having trouble getting CWM installed.
If, however, you can get into recovery... then it is theoretically possible to create a script that would accomplish that. As soon as I have one I'll be adding it to the mix ;-)
Edit: I've found something I think will work. Will do some testing tonight. It will still require access to recovery.
I wasn't sure if you saw my other post but I am seeing no partition 0 when I NVFlash with a verifypartition.
http://forum.xda-developers.com/showpost.php?p=13059520&postcount=57
I haven't yet but I will. Let's try to keep this thread on topic. Thanks.
More thoughts:
because I went w/ cyan7 is it possible i have a "bad" kernel and that the stock bekit-1105 or the roebeet-3588 files are crashing w/ the kernel in place already?
I know custom ROMs can have a custom kernel applied separately, but I have no idea whether cyan7 loads it's own kernel...
I have yet to try the nvflash_gtablet_46 version, as I see the img files w/in are different from the original 1105 .zip
Also:
read on another thread that part 2 and part 3 aren't loading for other users when doing nvflash - I did notice that it pauses, runs some stuff, then starts loading part 4 through to the last part, then success. - do part 2 and 3 run for you?
edit: I see a 4349 downgrade.zip in another thread for those who got the OTA update but want to go back to stock 3588 prior to jumping off somewhere else - I can't expect that would help me as I can't do squat w/ recovery yet, but could that possibly "reset" any bad kernel problems? - again, I'm just thinking out loud.
This is well outside the scope of this thread but I find some of what you mention interesting so I'll address it and then end any further off topic discussions.
I did not build nor have I ever used Cyan7 so I have no basis for an opinion on the matter other than this... Each ROM comes with a kernel installed so if properly done an nvflash should overwrite any "bad" kernel.
Part2 and Part3 do indeed load, they are just displayed differently than the other Parts. Just minutes ago I flashed down from Mountain Laurel (4349 based with the new bootloader and recovery) with absolutely no trouble. I can, and have, read back those partitions after an nvflash to prove that point.
The 4349 downgrade will only work for you if recovery is working. Having never used it I don't know that it would "reset" the kernel but any subsequent flashing of a new ROM image would.
I am working on a stock recovery solution for partitioning but it isn't likely to help anyone who is stuck in an APX loop. I do have some ideas on what might help for that condition but I haven't been able to get my hands on one for testing and trying to help people here is like being a consulting mechanic for a car repair that's in someone else's shop having work done on it that you're not being told about.
I'll be happy to address any further comments or questions regarding your specific issue in an appropriate thread or via PM. Thanks.
I am having a rather challenging issue. I moved from branch 1.1 and Vegan GE-7.0.0.0 RC1 to 1.2 NVflash 20110508 CWM5504 and flashed the TeamDRH-AOSP-Preview-1F-LDPI. So the issue is that I cannot write to, wipe, reformat or partition my internal sdcard. I had to flash the ICS ROM from my external sdcard and reboot system, but the screen locks on the TeamDRH title graphic page after loading all of the apps. I tried different releases of CWM55XX, but no difference.
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
I can get into APX and CWM. I can mount the USB port and view the internal drive. I can move, add and delete files and windows explorer shows that each action is completed. I renamed the old Update.zip to Update-Old.zip and it changes in explorer. But as soon as I unmount USB the changes are lost. When I go into CWM and try to install the zips, the only zip files showing are the update.zip and Vegan…zip. I tried to go back to Vegan, but it boot loops.
I tried rr5678’s G-Tablet Format utility that completely erases all traces of anything in the G-Tablet's ROM storage space. It showed all of the steps as completed. I got the red letter message at power on, immediately flashed the 1.2 NVflash/CWM and it functioned perfectly. But, still, no change or effect on the old files on the internal sdcard.
At this point, after way too many hours researching, reading and rereading, it may be that either I have a corrupt config file, (which is beyond my limited expertise to determine) or a bad microdrive.
I would appreciate any thoughts or ideas on resolving this. I want my GTab back!!! (It would be extra nice to have ICS, as well!)
Cheers,
Geary
galyons said:
Running CWM, I have re-partitioned to 4096/0, then 2048/0, formatted/cleared/wiped every partition, run the keycheck and tried pretty much every function CW has but nothing can touch the files on the drive!
Click to expand...
Click to collapse
This is a known problem that sometimes develops on some gTabs with a non-standard kind (compared to the majority of gTabs) of internal SD card.
There is no known "fix" for the problem. There is a workaround on page 5 of that thread, though.
But, first, I'd like you to get me the output of a dmesg command and then run through a set of tests (see posts #88 and #66) and get me their exact output.
Ok, I will read enough to see if i can figure out how to get the test results. Gonna take me a couple of days. Thank you for the guidance!
Cheers,
Geary
Well, I downloaded the Knoppix image, burned a bootable CD, booted Knoppix, hassled through getting connected to the internet, reread the threads and gave it a "go". Got buried in abd...dmesg and bailed. I would love to provide all of the diagnostic messages, but quite honestly, do not want to invest more time to become marginally able to do so.
So...RMA and boxed off to US Merchants. Hopefully you can discover a fix, rather than a work around for this issue. But the work around is infinitely better than an ever boot looping tablet!!
Thanks again for your help to me and others!!
Cheers,
Geary
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!
Hi,
I'm pretty interested in learning a bit about android, but for the moment i have this tablet that i have royally screwed up during my learning curve It's a PORTO 10.1 chinese tablet.
It would freeze up at the boot logo, but after some searchin, a forum member on the internet kindly sent me some .img files that he used to fix the same brand/model of tablet. They are flashed with the Rockchip tool. It's a RK3066 based tablet.
Prior to receiving the files i was trying other ROM's because it was becoming clear that there wasn't a full dump available for this tablet. None of them worked, and the tablet ended up being completely dead as a result. Being completely stupid once more, i formatted the tablet in the Rockchip tool, before realizing and learning that the ROMS don't come with .img files for partitions like userdata or cache etc? So any chances of recovery even if i did find a partial ROM, may have gone. Yes, i am an idiot Well you have to read a lot and make mistakes to learn, right? I've certainly learnt how to backup all of my partitions now in Rockchip tool since then!
Anyway the jist of it is, the tablet is 100%low level erased as far as i know. I've flashed the files that i was given from a guy on gsmforums, and the tablet turns on again, displays the manufacturer logo and then the android boot animation...but thats it. It gets stuck on the android logo animation.
The partitions i know have been flashed and should exist now are:
misc
boot
kernel
recovery
system
backup
The parameters of these partitions do match what they should be for this tablet. The one thing i did do before screwing the thing up was backup the parameter data. It's a shame i didn't backup anything else!
Obviously there are partitions i am missing, such as userdata, cache and maybe some more from what I've read. My main questions are these:
1. Will android hang like this at the logo if it cannot find/mount a userdata partition? or might i see a terminal/errors instead?
2. If i could get into Recovery (which i can't) does a factory reset just quick format the userdata partition, or would it obliterate it and recreate the partition over again and format it?
3. Are there any ways i may be able to recreate my missing partitions, assuming that it the reason why android is now stuck at the logo?
I did attempt to flash a copy of the cache and userdata partitions from another very similar tablet, but it didn't make any difference.
I know a little about what each partition is there for and what they do, i use a linux pc regularly although i am still working my way up from semi-newbie
Knowing how android should react to having no userdata/cache partitions might help me figure out what i need to do to fix this tablet? I am willing to read and learn if someone can tell me where to begin or give me some hints that might answer some of my questions.
Many thanks,
James.