This post can unbrick any Nook Tablet as long as there is no hardware damage.
Introduction
Some of you might know that I've been working on getting Ubuntu 11.10 running on the Nook Tablet. Why Ubuntu 11.10? It's optimized for touchscreen. My work with Ubuntu is not totally ready yet. The touchscreen is totally wonkey and unusable for touch input.
...Well, without a 3.0 kernel tailored to our device, Ubuntu is quite unusable as a Graphical User Interface. I've tried to compile a few times without any real results to report. The best results I've come across use a 2.6 kernel based on the kernel used for our device by Android. Anyway, if anyone can help get us a operational 3.0, 3.2+ kernel with full support for our device, I can get Ubuntu running.
However, all is not lost. Ubuntu DOES boot on a 2.6 kernel and it WILL perform most tasks that do not require special device control, like wiping the disk and reflashing. I've come up with a total wipe and restore program for SDCard based on ubuntu.
So, as a result of my work, I would like to present the first ever Ubuntu Recovery. This will totally wipe your device. With the exception of the ROM Partition which contains serial information, every single partition will have zeros written to it then flashed with just enough to perform an initial factory reflash. Normally when you perform an update or flash of a device, it is simply formatted. A formatted device can be unformatted. A zeroed device cannot be unformatted. All information is overwritten with zeros.
This will also work if you've damaged the bootloaders or recovery partition.
how to create your own bootable Ubuntu Recovery SDCard
You will need:
A Class 4 SDCard with at least 4Gigs of space
6 gigs of free space (for downloading sdcard image and uncompressing)
The SDCard Image: http://ge.tt/9rVFXxC?c
Linux/Mac Instructions
Open a terminal in Ubuntu by typing "terminal" in the search bar then hit enter
uncompress the Downloaded SDCard Image
Code:
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
With the SDCard or reader removed from the computer, get a list of all disks
Code:
ls /dev/sd?
Insert your sdcard or usb sdcard reader, then press the up key and enter to repeat the last command. The new device will show up as sdb, sdc, sdd or sde. each new device gets a higher letter. Note this newly plugged in device.(ie. /dev/sdc)
Use the following command to make your new SDCard, where "sdc" is the name of your SDCard device.
Code:
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc bs=4096; sync
Wait 5-20 minutes (depending on SDCard speed) until the image burning completes.
Shove it in your nook and turn it on by inserting the USB cable(do touch the power button, just insert the usb cable). Your nook will boot Ubuntu and perform a total factory restore. The process will take 15 minutes to complete with a Class4 micro SDcard.
Pro-tip: to copy and paste easily in Ubuntu, highlight text in the browser, then press the middle mouse button on the terminal.
Pro-tip: The tab key will auto-complete filenames.
Windows Instructions
Thanks to cyberma007 for Windows instructions.
Extract AdamOutlerUbuntuRecoveryImage with Winrar
Rename the resulting file to Add the .img extension to the filename
Download and open Win32 Disk Imager. note: The open source project can be found here: https://launchpad.net/win32-image-writer
Choose the drive letter of your SD Card from Win32 Disk Imager
Click the Write button
Turn of your nook and put in the SD Card and turn it back on.
Your Microsoft®™ Windows©®℠ computer sucks at reading anything except Microsoft formats. It cannot read the Open Source Linux EXT4 format. You will only see one partition after creating the SDCard but it will work fine. If you want to inspect the contents, install a Linux distribution on your computer.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Theory of operation
how it works
When you insert the SDCard and turn on the device this is what happens.
The device boots from SDCard.
The Ubuntu GUI will load. Personally, I recommend that you do not touch anything
You will be presented with a 100 Second countdown
If you wish to stop, press and hold power for 10 seconds before flashing has started
You will be presented with a progress bar status update only. Closing this will not affect the process. the only way to stop is to turn the device off.
At this point, the flashing process will begin
Flashing Process
After Ubuntu has booted here is the procedure which takes place
MLO partition will be written with all zeros, then flashed
U-BOOT partition will be written with all zeros, then flashed
RECOVERY partition will be written with all zeros, then flashed
BOOT partition will be written with all zeros, then flashed
BOOTDATA partition will be written with all zeros, then flashed
BOOTDATA is mounted and a command is sent to factory reset the device upon next boot.
FACTORY partition will be written with all zeros, then flashed in two parts to work around a 120 second filesystem operation bug.
A sync operation takes place to ensure all data is written to the device
SYSTEM partition is wiped with all zeros
SYSTEM partition is recreated as a blank EXT4 filesystem
CACHE partition is wiped with all zeros
CACHE partition is recreated as a blank EXT4 filesystem
SDCARD partition is wiped with all zeros
SDCARD partition is recreated as a blank FAT32 filesystem
A sync operation takes place to ensure that all data is written
You are notified to press and hold power. When the screen goes black remove your SDCard
note: Using a Class4 SDCard, the screen timeout will be aproximately 30 seconds after the entire operation has completed. Do not confuse screen-timeout (blank screen) with turning off the device (black, unilluminated screen). Turn the device off and then remove the sdcard or risk corrupting the data on the sdcard.
It's my intention that this may help someone. This will at least be one more method for people to try before giving up on restoration to 1.4.0. I generally receive 5-10 PMs per week requesting support on the acclaim_update.zip. Hopefully this will reduce those and give people another option to try.
Ubuntu isn't ready for daily use yet, but this recovery tool is more thorough than any other recovery method out there. I need some help porting the 3.0 kernel to the Nook Tablet.
Note: to neuter recovery and just use ubuntu, remove the file called /root/recovery from the sdcard before loading into your Nook.
Which kernel branch did you try to build?
Kuzma30 said:
Which kernel branch did you try to build?
Click to expand...
Click to collapse
I've tried several. The problem is in configuration. I eventually settled for the stock 2.6 android_4430BN_defconfig. It seems to function best for this until we have a proper 3.0 kernel.
Thanks Adam very nice work. Question what if we want to revert to 1.4.0 or 1.4.0 is it possible or we will be stick it lol. Can this be supported for dual/multi boot?
~ Veronica
Sent from XDA premium using my Nook Tablet
Very good work Adam.
I have one trivial question... Why on all your projects do you use Ubuntu and not any other distro?
lavero.burgos said:
Thanks Adam very nice work. Question what if we want to revert to 1.4.0 or 1.4.0 is it possible or we will be stick it lol. Can this be supported for dual/multi boot?
~ Veronica
Sent from XDA premium using my Nook Tablet
Click to expand...
Click to collapse
Thats what this does. It reverts you to 1.4.0. It uses Ubuntu as a dedicated recovery. If you would like to dual boot, just remove the /root/recovery file. You can boot Ubuntu or normal by inserting and removing the sdcard. But like i said, the touchscreen is wonkey and there's no way to fix most of the problems without a 3.0 kernel.
ShadowReaperGR said:
Very good work Adam.
I have one trivial question... Why on all your projects do you use Ubuntu and not any other distro?
Click to expand...
Click to collapse
I use Ubuntu on my desktop. I like Ubuntu because it has a large user base and if i come across a problem, it is easier to correct or has generally at least been discussed. For a mobile device, it makes more sense than other Linux distributions because newer versions have been optimized for touchscreens. In general, i find Ubuntu supports more things than other Linux distributions.
Hoster: http://ge.tt/ or 4shared.com both max. upload 2Gb/file.
AdamOutler said:
Thats what this does. It reverts you to 1.4.0. It uses Ubuntu as a dedicated recovery. If you would like to dual boot, just remove the /root/recovery file. You can boot Ubuntu or normal by inserting and removing the sdcard. But like i said, the touchscreen is wonkey and there's no way to fix most of the problems without a 3.0 kernel.
Click to expand...
Click to collapse
Gotcha! thanks Adams, i'll wait until it gets a better kernel, i love the Ubuntu idea .
My 2 cents for host: http://minus.com/
Great work, will monitor this. Would be nice to have Ubuntu fully working on the Nook Tablet (or Nook Color, for that matter -- seems like development on that has died, shame as they are now $129 refurbished direct from B&N)
Hi Adam,
When you say the screen is wonky what do you mean? Is it sort of 90degrees out like our original CM7 build was?
CelticWebSolutions said:
Hi Adam,
When you say the screen is wonky what do you mean? Is it sort of 90degrees out like our original CM7 build was?
Click to expand...
Click to collapse
Yes. Also, none of the native tools to correct this work because of lack of proc and sys support.
Such a shame, I quite fancied a dual boot with android/ ubuntu
It was a simple fix in the build.prop on CM7
Oh well hopefully somebody will come up with a suitable 3.0 for you soon
AdamOutler said:
Note: If someone has web hosting for a 1.5Gig file and nearly unlimited bandwidth, the instructions above can be reduced to only a few simple steps... download, uncompress, run command in terminal to make a disk image, boot from SDCard. Team Komin's server bandwidth does not allow this.
Click to expand...
Click to collapse
If you're still interested in doing this let me know. I can find a place to host it. Who knows how many people "bricked" their NTs from the CM7 beta - this seems to be the only logical fix if ADB doesn't work in CWM (which I'm experiencing (even from the SD version of CWM)). I haven't gotten a chance to confirm if this works or not yet for that issue (I'm waiting on a new microSD -> SD adapter), but if it works this would make it a lot easier.
Bit of problem in the end of setting up the sd
Everything goes quite fine but in the end when it is supposed to automount and than to copy the files from the recovery it behaves strange. Im a windows user so i have been using linux for 10hr now. Ill post later what it says .
@scsione889 . If you have web hostin i think you should send a PM to AdamOutler because he is quite busy. Because that would help a lot a lot. In the future also if we brick it again would be easier to do it in shorter steps. Because this one takes long and is a bit complicated to.
Here is the rehosted file and new instructions. Let me know if there are any problems so I can redo the first post.
You will need:
A Class 4 SDCard with at least 4Gigs of space
Ubuntu installed on Disk, USB drive, Wubi, or CD: http://ubuntu.com/download
6 gigs of free space (for downloading sdcard image and uncompressing)
The SDCard Image: http://ge.tt/9rVFXxC?c
Instructions:
Open a terminal in Ubuntu by typing "terminal" in the search bar then hit enter
uncompress the Downloaded SDCard Image
Code:
cd ~/Downloads
tar -xvwzf ./AdamOutlerUbuntuTotalReFlash.tar.gz
type "ls" to get a file listing and locate the name of the new file. (ie AdamOutlerUbuntuTotalReFlash).
With the SDCard or reader removed from the computer, get a list of all disks
Code:
ls /dev/sd?
Insert your sdcard or usb sdcard reader, then press the up key and enter to repeat the last command. The new device will show up as sdb, sdc, sdd or sde. each new device gets a higher letter. Note this newly plugged in device.(ie. /dev/sdc)
Use the following command to make your new SDCard, where "AdamOutlerUbuntuTotalReFlash" is the name of the uncompressed file and "sdc" is the name of your SDCard device.
Code:
sudo dd if=./AdamOutlerUbuntuTotalReFlash of=/dev/sdc
Wait 5-45 minutes (depending on SDCard speed) until the image burning completes.
Shove it in your nook and turn it on. The process will take 15 minutes to complete with a Class4 micro SDcard
Pro-tip: to copy and paste easily in Ubuntu, highlight text in the browser, then press the middle mouse button on the terminal.
Pro-tip: The tab key will auto-complete filenames.
Fixed Nook
AdamOutler said:
Here is the rehosted file and new instructions. Let me know if there are any problems so I can redo the first post.
Click to expand...
Click to collapse
Works hurrey.
My nook was not just bricked but more than that heeheh. I have tried with adb, CWM, with the flashable zip but none of them dident work. I did lose my hope to fix it actually.
But this method worked just fine. And with the last post it was way easier to make it to .
Thanks a lot Adam i have been hiting your thanks booton and ill hit it for some more days too.
I can tell that now if you want you can replace the first post with this one. Of that's what you want.
Thanks once more.
Fatos said:
Works hurrey.
My nook was not just bricked but more than that heeheh. I have tried with adb, CWM, with the flashable zip but none of them dident work. I did lose my hope to fix it actually.
But this method worked just fine. And with the last post it was way easier to make it to .
Thanks a lot Adam i have been hiting your thanks booton and ill hit it for some more days too.
I can tell that now if you want you can replace the first post with this one. Of that's what you want.
Thanks once more.
Click to expand...
Click to collapse
Glad you accepted my suggestion and tried it, well worth it in the end then
You'd gone a little bit further than the others that had just formatted the xloader, you'd got carried away and done the lot lol
Enjoy you're CM7 NT and DON'T format anything on there ever again!!!!
CelticWebSolutions said:
Glad you accepted my suggestion and tried it, well worth it in the end then
You'd gone a little bit further than the others that had just formatted the xloader, you'd got carried away and done the lot lol
Enjoy you're CM7 NT and DON'T format anything on there ever again!!!!
Click to expand...
Click to collapse
Haha as they say learnig by doing. Heheh now i know.
Thanks for sharing your time.
Adam, will it ever be possible to get this on streak 7 ?
Related
Hello,
I have prepared a few update.zip's with kernels to boot linux:
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE.
1. Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==". http://ac100.gudinna.com/README/
2. Extract contents to a folder and follow instructions below.
copy the update.zip to a sdcard, and insert sdcard into folio.
Enter "Recovery menu" when folio is just turned on and press (POWER) once and (VOL up) next.
press (VOL up) Factory reset or system update.
press(VOL down) to continue to system update.
press (VOL up) to confirm system update.
during installation progress bar will show har far it is.
folio will reboot after installation.
insert the usb or flashdrive with the prepared filesystem into the folio and the tablet will boot automaticly from it
This sounds very interesting, might give it a try when im done playing with my new folio, ubuntu on it would be awesome
Does it boot to a full Ubuntu desktop or a bash prompt?
key combination to boot ubuntu
DerArtem said:
Hello,
I have prepared a few update.zip's with kernels to boot linux:
Please follow the instructions here to prepare your SD / USB Drive - start at "== Create a rootfs SD card ==".
Unzip the zip and then use the zip inside to update your kernel.
There are two different zips.
One to boot linux from a USB Flashdrive and the other from a SD card.
Click to expand...
Click to collapse
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
zoken4 said:
Does it boot to a full Ubuntu desktop or a bash prompt?
Click to expand...
Click to collapse
It depends on what you have put on your sd / usb flash.
Ivalex said:
Hi DerArtem,
once the media (SD) is setup, you need special key combo in order to let folio boot from the SD? thanks in advance.
Click to expand...
Click to collapse
I have updated the 1st post.
DerArtem said:
It depends on what you have put on your sd / usb flash.
I have updated the 1st post.
Click to expand...
Click to collapse
gorgeous!
got it, the first step, is exactly the same as uploading a mod. then the SD modified as per gudinna instr. will bring you to linux.
thanks again.
how fast/responsive is this? Can you benchmark it against the AC100 netbook running the same image - that had a noticeable lag at least on SD card access.
How prepare the SD?
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Shark17 said:
Thank you for your work!!!
I did all the process but I can't start linux.
The kernel boots but stop without start the desktop.
You can see when stops in this image:
ifisc.uib-csic.es/~edu/fotos_folio100/1.jpg
(Put the http:..., I can't put links because the system)
I prepared the filesystem in a SD card only decompressing the tar.gz, ¿Is necessary recompile the kernel or something like configure it?
Shark.
Click to expand...
Click to collapse
I have not tested it using a SD-Card. I will try it out when I have some time...
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
USB tried
I tried with the USB and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
Click to expand...
Click to collapse
I'm agree with your opinion.
I confirm that the method is not agressive for the tablet, restore android works for me.
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Hi,
eraph2 said:
I met the same problem : stuck at the "no console found" point, and this either with an sd-card or a usb key. I also tried wolfx's method (boot via fastboot), and had the same problem.
To me, it seems that this must come from the system we put on the sdcard/usb key.
DerArtem : could you tell us what distro you put on your usb-key ? (and maybe even with links for download ?)
Regards,
eRaph
Click to expand...
Click to collapse
I have used gentoo linux on a usb flash:
http://dev.gentoo.org/~armin76/arm/tegra2/install.xml
http://www.gentoo.org/doc/en/handbook/handbook-arm.xml
eraph2 said:
Actually, I just found what the problem was : on the image I uncompressed on the usb key (tegra-rootfs.tgz), the /dev directory was empty, and lacked a console and a null entry (see h**p://ubuntuforums.org/showthread.php?t=28550)
The folowing command solved the problem (to do on your sdcard/usbkey) :
cd dev
mknod -m 660 console c 5 1
mknod -m 660 null c 1 3
Click to expand...
Click to collapse
Yes, this files exists in the gentoo in the .tgz ....
I think that ubuntu might require a initrd...
And ubuntu works?
Can you start ubuntu fixing this?
Console
Creating the console in the dev..., ¿are you started ubuntu?
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
eraph2 said:
I successfully managed to boot the ac100 ubuntu image (tegra-rootfs.tgz) copied on my sdcard. X started well, and hooking a keyboard, I managed to create a user, edit his password, ...
Nevertheless, I did not manage yet to make both a keyboard and a mouse work at the same time (the usb hub does not seem to work), and unpluggin/replugging the keyboard did not work either.
So, the ac100 ubuntu image works somewhat (in text mode via ALT-F1, i managed to get root access), but seems to lack some hardware support (which is quite normal).
The first problem is probably that the boot.img I used was the one DerArtem provided with his modified sdmmc-update.zip archive, which contains a 2.6.32 kernel, whereas the ubuntu image uses a 2.6.29-ac100 kernel, hence no modules get loaded. I should find how to rebuild a boot.img with the good kernel (or better : add the good modules to the ubuntu image).
DerArtem : may I ask you how you did rebuild the boot.img in your various packages ?
Regards,
eRaph
Click to expand...
Click to collapse
Hi,
please search on the web how to rebuild the boot.img. This is not a problem. My zip also contains the config to rebuild the kernel. The sources of the kernel are also documented in the readme inside the zip. The initrd is just empty.
But running ubunu on the folio might be a bad idea. Ubuntu is compiled for NEON instruction set, but the Tegra 2 CPU does not support this, so a lot of applications can crash when they will try to execute more advanced code....
Debian (optimized for ARMv6 without NEON) or Gentoo are better for the Folio.
Then, if I want to install gentoo instead ubuntu, do I have to follow the same steps but changing the distro linux for the gentoo? Or is it necessary to do anything else?
Thanks
I tried to install gentoo in a USB, but it's a long process and it's not usual for me.
I'm very lost!
halu:
If you obtain a opetative distro image, can you upload in any place?
I'm thinking in write a howto with the results.
Bests
(Saludos desde Mallorca!! )
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.
After 3 days of tinkering I finally have my Webtop2SD working correctly with xfce and OpenOffice. The whole setup feels a little delicate, so wondering if there is any way to easily back up that partition? Should I just eject the card, place in my Ubuntu machine and do a "dd" on it or something?
Also, because I am still locked (until warranty is over) and can't use CWM backup to do a nandroid, where is the osh disk image stored so I can use root explorer to make a copy?
I apologize if these have been asked and answered. I did searches and did read the Webtop2SD posts from start to finish.
Cheers,
Thom
tjdmobile said:
After 3 days of tinkering I finally have my Webtop2SD working correctly with xfce and OpenOffice. The whole setup feels a little delicate, so wondering if there is any way to easily back up that partition? Should I just eject the card, place in my Ubuntu machine and do a "dd" on it or something?
Also, because I am still locked (until warranty is over) and can't use CWM backup to do a nandroid, where is the osh disk image stored so I can use root explorer to make a copy?
I apologize if these have been asked and answered. I did searches and did read the Webtop2SD posts from start to finish.
Cheers,
Thom
Click to expand...
Click to collapse
since your using webtop2sd your not using /osh
putting your sdcard in your ubuntu box and using dd should work.
I did want to come back to report that I backed up the partition with dd and then restored the image to another card (with similar partitioning). The other card, once popped into the Atrix, had a working full restore. Thrilled to have this backup.
For those who care enough to read this (because you need to know how it was done).
1. Powered down phone and removed MicroSD with my Webtop on it
2. Went to my Ubuntu box, inserted card reader, waited for it to come up.
3. Opened Gparted to identify the device name, in my case /dev/hdc
4. Figured out where to put the image. In my case /media/LinBackup
5. Entered a command: sudo dd if=/dev/hdc2 of=/media/LinBackup/OSHbackup1.img
6. Patiently waited for it to complete. It was only a 3 gig partition so didn't take long
For restore, it's basically the reverse. Identify your devices / mounts and partitions
1. Entered a command: sudo dd if=/media/LinBackup/OSHbackup1.img of=/dev/hdc2
Now I need to see if it's possible to do a dd from within the webtop. I don't know if it does a snapshot (allowing for open / locked files to be backed up). It would probably be an easier way to do the backups. I now have a spare 8-gig card already loaded with a working configuration in case the one in my Atrix went belly up.
I hope this helps someone. Having not a single "thanks" (shameful), do thank me if this helps.
tjdmobile said:
I did want to come back to report that I backed up the partition with dd and then restored the image to another card (with similar partitioning). The other card, once popped into the Atrix, had a working full restore. Thrilled to have this backup.
For those who care enough to read this (because you need to know how it was done).
1. Powered down phone and removed MicroSD with my Webtop on it
2. Went to my Ubuntu box, inserted card reader, waited for it to come up.
3. Opened Gparted to identify the device name, in my case /dev/hdc
4. Figured out where to put the image. In my case /media/LinBackup
5. Entered a command: sudo dd if=/dev/hdc2 of=/media/LinBackup/OSHbackup1.img
6. Patiently waited for it to complete. It was only a 3 gig partition so didn't take long
For restore, it's basically the reverse. Identify your devices / mounts and partitions
1. Entered a command: sudo dd if=/media/LinBackup/OSHbackup1.img of=/dev/hdc2
Now I need to see if it's possible to do a dd from within the webtop. I don't know if it does a snapshot (allowing for open / locked files to be backed up). It would probably be an easier way to do the backups. I now have a spare 8-gig card already loaded with a working configuration in case the one in my Atrix went belly up.
I hope this helps someone. Having not a single "thanks" (shameful), do thank me if this helps.
Click to expand...
Click to collapse
Thanks for the info!
Very interesting stuff and also very handy for us with Webtop2SD.
Happy Thanksgiving!
Sent from my Atrix using Tapatalk
Thanks for testing this out and coming back to give a report.
This will be very helpful for a lot of people.
So the next step is to place this .img file in an update.zip and it should work for reinstalling the webtop, correct?
would it be webtop.img or osh.img in the update.zip file?
I recently ordered an Onda obook10 dual booting tablet (Android 5.1 +Win10) from GearBest, and received it a week (and a half) ago. It is the V5 version (9th and 10th digits of S/N). Booted into Android at first, swiped around a little, and then left it alone for when I was free. Day before, I booted into Windows, and seeing that an account was already set up, hit the factory reset option (Options: remove all personal files, normal wipe (not thorough)). It rebooted, said it was resetting, then got stuck at 5% for a half hour. I then did a hard reboot, and it starting resetting again. I repeated this a few times, with different waiting periods, but it always got stuck at 5%. I wanted to see what was going on, so I opened the OS selector menu and tried to boot into Android, but that put the device into a bootloop, and it's stayed that way since. I downloaded the recovery WinPE from their website, and tried running it; all went well until the last step (installing the install.wim file), which succeeded, but when the batch file tried to set the boot options/flags, it threw an error about not being able to access D:, and failed. Tried making the recovery USB and installing multiple times, but it failed every time. I then tried Gandalf's WinPE image, which booted, and tried using imagex to install the .wim file to C: manually, as detailed here. This failed too.
I'm at my wits' end, honestly. I have no idea what else to try. There's another WinPE file available for download, but it's dated only a couple of weeks after the one I already have, so I'm hesitant to download it if there's any other option (I have very low bandwidth, it would take me at least two days). Also, it's hosted on Baidu, and the download times out after about an hour, and cannot resume. If anyone could give me any ideas, or point me towards a guide I haven't found yet (I've read all the relevant ones I could find on the Onda forums, but please post them anyway if you think they would be helpful), that would be great.
What would be perfect is if someone could upload, or point me toward a system dump/partition clone of at least the Windows partition and boot partition; I have the tools needed to flash those.
Thanks in advance.
EDIT: I managed to fix this a while ago, and have put the procedure somewhere in this thread, but since people keep popping up every now and then asking for it, I'm going to put this here so it's easier to find. Copied from later in the thread, here, and modified to be more general:
This uses slightly modified commands from the Onda firmware install script, and will result in a COMPLETE WIPE and reinstall of Windows - all the files on the Windows partition will be lost. This SHOULD work for anyone whose Android is working but Windows isn't, but I can't guarantee that. I can't even guarantee that this will work (though I am pretty sure it will) - I have not tested it completely. If you can, you should make a backup of anything files on the internal storage, just in case. As always, read the whole procedure before starting.
NOTE: If your Android isn't working, you need to install that first - get the Android file from the Onda Baidu page (look for the one for OBOOK 10 (not SE), with the appropriate V1, V2, V3, V5, or V7 code - you can find your code by checking the serial no. on the back of your device, the 9th and 10th characters), and follow the instructions in the document included in the zip - they are pretty straightforward, but you'll have to use Google Translate, as they're in Chinese. This MUST be done before the Windows procedure, because the Android installer wipes the entire disk.
If you want, you can make the procedure easier for yourself and save all the commands below to a text file, put it in the root folder of the USB before booting, and open it in Notepad by using:
Code:
notepad D:\textfile.txt
Or whatever name you give it. That way, you can copy paste them all easily.
Boot into the Windows installer, and when the command window appears, press Ctrl-C. After a few seconds, it will ask you if you want to terminate batch job, type 'y' and press enter. You now have a command prompt to work with.
You have to delete your Windows partitions first. The below partition numbers should be correct, but you should make sure first by running "list partition" and checking if it corresponds with the last 3 partitions, which should be your Windows partitions - their sizes are usually 128 MB, 35 GB, and around 800-1024 MB, and their types are Reserved, Primary, and Recovery (DO NOT delete the Primary partition at the beginning of the disk). DO NOT delete the Unknown partitions - those are Android's.
Code:
diskpart
sel disk 0
sel partition 14
delete partition
sel partition 13
delete partition
sel partition 12
delete partition
Your Windows partitions are now completely gone, so you'll have to recreate them first.
Change directory to the images folder.
Code:
cd D:\images
Get filesizes of .wim files to create partitions accordingly:
Code:
for %I in (Install.wim) do set INSTALL_SIZE=%~zI
set /a INSTALL_SIZE_MB=%INSTALL_SIZE:~0,-6%
for %I in (Winre.wim) do set RE_SIZE=%~zI
set /a RE_SIZE_MB=%RE_SIZE:~0,-6%
if %RE_SIZE_MB% LSS 430 (set /a RE_SIZE_MB=480
) else (
if %RE_SIZE_MB% GEQ 430 (
if %RE_SIZE_MB% LSS 680 (
set /a RE_SIZE_MB=%RE_SIZE_MB%+320
) else (
set /a RE_SIZE_MB=%RE_SIZE_MB%+1024
)
) )
Make sure to preserve all the spaces and brackets in the above code.
Enter diskpart, run the following:
Code:
sel disk 0
create partition msr size=128
create partition primary
shrink minimum=%RE_SIZE_MB%
format quick fs=ntfs label="Windows"
assign letter="W"
create partition primary
format quick fs=ntfs label="Recovery"
assign letter="R"
set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"
gpt attributes=0x8000000000000001
You should now have 14 partitions when you do "list partition".
Exit diskpart.
Now for the actual installation:
Code:
md w:\recycler
md R:\recovery\windowsre
DISM /Apply-Image /ImageFile:"D:\images\Install.wim" /ApplyDir:w: /Index:1 /Compact /ScratchDir:w:\recycler
xcopy D:\images\Winre.wim r:\recovery\windowsre /y
Create boot entry:
Code:
bcdboot w:\WINDOWS
If that doesn't work, then:
w:\WINDOWS\SYSTEM32\BCDBOOT w:\WINDOWS
Set recovery environment:
Code:
w:\windows\system32\reagentc.exe /SetREImage /Path R:\recovery\windowsre /target w:\windows
And that's it! You should have both OSes operational now.
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
EDIT: I've put the guide in the first post.
Flashing Help
SirVer said:
Update: I've managed to fix this problem. However, since the procedure is lengthy, and there doesn't seem to be anybody who needs a solution, I'm not going to the trouble of typing it out. If anyone does need to know how to save it, post here, and I'd be happy to help out.
Click to expand...
Click to collapse
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
[email protected] said:
I have an Onda Obook 10 and have a problem with aandroid side of it. The system UI crashes, all google apps have stopped.
I have the Rom for it but have no clue how to install it.
I have gone into recovery mode and cleared cache and done a factory reset but the errors still happen in Android. The Windows 10 side of things work fine.
Have you any advice or help you can offer,
Regards
Jon
Click to expand...
Click to collapse
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Widows swith icon
SirVer said:
Inside the ROM zip, there should be a Word document with instructions in Chinese on how to flash the ROM. It should basically say something like this:
1. Extract zip contents, put them in a USB drive.
2. Plug it in, and with a keyboard attached, hold down ESC and power on the device to enter BIOS.
3. Enter the Boot Manager, and select Internal EFI.
4. It should automatically start applying the ROM after a few seconds.
Be warned that this may wipe your Windows partition - this happened to me, but that may be because my partition table was somewhat messed up. Either way, be sure to take a disk image or backup of your MSR, C drive, and recovery partition (probably the last 3 partitions on the disk).
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
[email protected] said:
Hi Reinstalled android thanks for your help. the only thing missing is the icon to switch to windows. I think the partition is still there but there was an icon for switching but don't know where it's gone.
Any advice would be helpful.
Regards
Jon
Click to expand...
Click to collapse
Is the partition still there, or is that just free space you're seeing? For me, the partition was gone, with unallocated space in its place. If the partition is still there, then your job is relatively simple.
1. Make a WinPE recovery drive from another Windows machine, or just use a custom one (like Gandalf's WinPE, Google it).
2. Boot into it from the BIOS menu.
3. Load a command prompt.
4. Type "diskpart" (no quotes). Wait until you get a prompt like: DISKPART>
5. Enter the following commands:
a. select disk 0
b. list partition
c. select partition xx (where xx is the number of the Windows partition. If it's not labelled, it'll be the one about 36 gigs in size.
d. assign letter=c
e. exit
6. Now just run "bcdboot C:\Windows"
7. Reboot, and you should see Windows in your BIOS menu once more, and the button should pop up on Android as well.
If the Windows partition is not there, and it's just free space, things become more complicated. You'll need to get your hands on the Windows installer image. There is an older version on the Onda website (December 2015) that should do the job - or rather, there's a link to their Baidu account. You can find the more recent version in their account as well. The issue is that Baidu doesn't allow you to download files that large without installing their crapware. I got around it by registering an account and some URL-fu, but it's a PITA, especially if you have a slow connection. There's a Yandex mirror somewhere, but I'm not at home, so I don't have the link right now. I'll post it when I get back. EDIT: Here it is.
After you get the files, DON'T install it; it might wipe your Android install (did for me). There's an issue in their install script that made the command that hides the Android partitions from getting deleted not work. What I did was terminate the automatic install, and selectively apply the relevant portions of the script manually. You could probably do the same, but it could take you a while; took me two days and a bunch of background reading. If you're used to messing with Windows installs though, it'd probably be a cakewalk for you. I'd prepare some instructions for you, or even try and write a script myself using that one as a base, but I have exams right now, and I wouldn't have time for at least a week. If you haven't figured it out by then, just ask, and I'll do it.
Sent from my LG-D855 using Tapatalk
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Frezza said:
I have resetted my obook 10, it lock on 30% of restore for 2 hours, so i power off tablet. Now when i power on tablet it loop on Onda logo. If i power tablet with Power + Vol- I enter in Q2S menu and select Android that work fine.... I want restore Windows, If I power tablet with Power + down botton I don't enter in bios settings.... How can I fix problem?
Click to expand...
Click to collapse
You can enter the BIOS menu by connecting a keyboard and holding down ESC while booting up.
Sent from my LG-D855 using Tapatalk
Help
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
[email protected] said:
Hi
I have the Gandalf ISO file but need to understand from where do I go from the bios..like boot into the file?
regards
Jon
Click to expand...
Click to collapse
I don't remember exactly what it's called, but I think it was the second menu entry - Boot <Something>. In that menu, you should see your USB drive USB EFI device or something like that listed - it might also show the manufacturer name (it showed my USB as a Sandisk). If you don't see it, you may have made a mistake when making the bootable USB - try it again while reading the instructions on Gandalf's site carefully. If you used Rufus to make the bootable, maybe try Unetbootin this time - it worked fine for me.
P.S. In case you meant boot into the file - you can't. You have to write it to a USB drive first. Instructions are on the same site you downloaded it from.
Sent from my LG-D855 using Tapatalk
Can I install Windows 7 by Gandalf on this Tablet?
Frezza said:
Can I install Windows 7 by Gandalf on this Tablet?
Click to expand...
Click to collapse
Install? Maybe, but you wouldn't have any of the necessary drivers, so touch and WiFi and stuff wouldn't work. However, you can download the drivers and try installing them, which might work, though it probably won't since they're made for Windows 10.
Sent from my LG-D855 using Tapatalk
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Frezza said:
If there is this problem i install windows 10, I download img from link in last post, then i make a usb bootable ( with rufus) with img, then how can I start installation without delete android in other partition?
Click to expand...
Click to collapse
Depending on certain things, you may be able to just run the installer without doing anything extra. Are you able to boot into Android? Open a CMD window, and run the following commands:
1. diskpart
2. sel disk 0
3. list partition
Post the output of these here. A screenshot will also be OK.
Sent from my LG-D855 using Tapatalk
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
betsesv said:
Hi Have the same problem i'll follow your instructions
I download part1 and 2 from windows 10 folder.
My android install work perfect !
Click to expand...
Click to collapse
When you extract that, you'll get a bunch of files and a DOC in Chinese explaining the procedure to make the recovery disk. Once you've made that, a WARNING before you boot into it: it will automatically open a CMD and start a delay counter, after which it will start the install automatically. Since this might break the Android side, you'll have to cancel it with Control-C in that delay period, which will give you a normal CMD to work with. You can use this to run the commands from my last post. If you want to be extra safe, also download a different WinPE recovery file (like Gandalf - actually you should download this anyway, it has some useful tools you might need later on), and boot into that instead. Depending on the output of those commands, you may be able to just run the automatic installer without worries.
Sent from my LG-D855 using Tapatalk
obook20 crashed
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
alexander137 said:
hello all,
my obook10 is in black screen with word shell>> on it. it crashed from android, how i can restore it ? please help!!!
Click to expand...
Click to collapse
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
SirVer said:
You are probably in the internal EFI shell. Power off, connect a keyboard, and hold Fn+ESC while turning it on. This will get you the BIOS menu. Select Boot Manager. Normally, you'll see Android and Windows entries, and you could select one of them to boot, but in your case, you might only see Internal EFI Shell. If this is the case, follow the instructions from my earlier posts, and post the output of those commands. Depending on the result, it might be an easy fix, or a difficult fix. Hopefully, neither of you needs the difficult one, but if you do, I'll try and make a guide when I get time. In the meantime, post the output of the commands.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
alexander137 said:
thank you!! but i can't shutdown it, when i press powerbutton onda make new line with 'shell>>' , and powerbutton with volume down also don't reboot it. may be i do somthing wrong....
Click to expand...
Click to collapse
Just press it down for a long time, at least 10 seconds, that'll do it. For some reason it takes a really long time to force shutdown. If that doesn't work, then there might be an issue with your hardware. Also try typing the "exit" command - it should put you into the BIOS menu directly.
Sent from my LG-D855 using Tapatalk
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherryRook said:
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
View attachment 5713397
Click to expand...
Click to collapse
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
Click to expand...
Click to collapse
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?
Click to expand...
Click to collapse
P.S. my NT is 16GB version. Is your file work to my device?
CherryRook said:
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
Click to expand...
Click to collapse
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
nmyshkin said:
Lineage 14.1
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3262390066
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Flashed with emmc-based TWRP 3.0.2-0
Click to expand...
Click to collapse
For either of those ROMs you can use the sdcard version of TWRP:
nmyshkin said:
TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
Click to expand...
Click to collapse
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
nmyshkin said:
the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
nmyshkin said:
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
For either of those ROMs you can use the sdcard version of TWRP:
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
Click to expand...
Click to collapse
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
CherryRook said:
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
Click to expand...
Click to collapse
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
CherryRook said:
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
Click to expand...
Click to collapse
You may need to try another card, if you can get one. This is often the problem when the tablet won't boot (did you try booting by inserting the power cord?). It may take some trial and error, and as they say in the instructions, you may need to remake the card (reformat, re-write the image) to get it all to work.
I can't think of any other approach for where you are now. The device clearly can't get to either a recovery or an OS.
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Renate said:
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Click to expand...
Click to collapse
Unfortunately no. It has no reaction on mac and when I plug it to PC, windows shows me a announcement that there's a device which doesn't work properly
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That's weird. I followed the instructions on that page but still doesn't work. everytime I boot up, I got a quick N logo show screen then the familiar pixel glitch one.
Also I tried to change the partition ID to 0x0E FAT 16 LBA according from a thread in Chinese forum, but nothing changes
I was wondering if it's any kind of hardware issues?
CherryRook said:
Windows shows me a announcement that there's a device which doesn't work properly
Click to expand...
Click to collapse
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Renate said:
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Click to expand...
Click to collapse
I checked the device manager and found nothing. Literally, nothing there even after the weird announcement popped up.
I agree with your idea: maybe my emmc and system work fine, but something of bootloader or hardware has some problem so I got a pixel glitch screen. In my observation, the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
CherryRook said:
the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
Click to expand...
Click to collapse
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears.
The problem seems to be getting a boot from the sdcard. If you read through the now crippled forum, you will see that's not so uncommon. The most common solution is a different card or at least a complete re-write of the offending card.
It has been reported often that some NTs cannot boot from the sdcard unless they are connected to a power source (either the charging pack or the USB connection to a PC). I have not seen this with my two tablets, but it would not surprise me.
Even making the original cyanoboot sdcard is filled with traps. Everything has to be done just right or the card will fail to boot or--worse--wreak havoc on the system.
It occurs to me that one other approach to this situation is to prepare such a card as if you were going to flash a custom recovery and a ROM. These instruction shepherd you through the card preparation:
nmyshkin said:
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
Every single step is important, especially step 1. In step 2a the order in which the files are placed on the card seems to be important according to some guides. So every detail is important. No shortcuts. If you can prepare such a card and get your device to boot from it (try with the power cord), into the Cyanoboot menu, you should be able to flash a good emmc recovery and then......a ROM. But if the card won't boot, you can't do any of that.
Edit: Does this work on your tablet, or is it too far gone?
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" & "VOL+" & "VOL-" buttons simultaneously to reboot.
After reboot, release only the "PWR" & "∩" buttons after 2-3 seconds upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen while still maintaining to hold the "VOL+" & "VOL-" buttons.
The screen may blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue
I even accidentally let go of the "VOL+" & "VOL-" buttons once while testing this a few times but quickly pushed them back down again and was still given the factory reset screen so this method works even with a little goof like that. This worked since holding down the "VOL+" & "VOL-" buttons was found to be unnecessary.
nmyshkin said:
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears....
Click to expand...
Click to collapse
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
CherryRook said:
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Click to expand...
Click to collapse
So it was the card. Ta-da!
CherryRook said:
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Click to expand...
Click to collapse
The emmc version of TWRP (3.0.2.0) is full of little goofy "error" messages. Just ignore the bootdata messages. In general, TWRP is not going to wipe out /bootdata/ unless you try really hard. That's to prevent you from ending up with a brick.
CherryRook said:
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
Click to expand...
Click to collapse
This I cannot explain, but I hope that things will settle down as you begin flashing a ROM. Just bear in mind that the emmc TWRP has a poor touch interface. Always be sure items you have checked (or unchecked) are really that way. There should be no highlighting around a checked or unchecked item. If there is, it's not really what it looks like and you need to select (or deselect) again until you have a normal checkbox.
CherryRook said:
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
Click to expand...
Click to collapse
The emmc TWRP you have is the correct one for AOSP 7. Continue here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/ with step 2d. I do not recommend GApps, but it's in the instructions. If you want it, here is a link to the package I used. All the packages at OpenGApps seem to auto-expand with time until they are too large for our devices. If you don't want GApps, just skip any steps that refer to it.
Then proceed to step 3d since you have already flashed the emmc TWRP.
If you want full root access you'll need the superuser control apk. Here is a link.
I know the instructions are very tedious, with a lot of rebooting, but they are what worked for me reliably, over and over again. Detail counts in this kind of thing (and luck!).
nmyshkin said:
So it was the card. Ta-da!
Click to expand...
Click to collapse
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
CherryRook said:
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
Click to expand...
Click to collapse
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
If you completed the initial cyanoboot installation corrrectly, the device should boot into cyanoboot and then to the ROM (if installed) when turned on (without the card). If you leave the sdcard in and power up without selecting the "n" button to get to the boot menu, you will get an error about "boot magic", etc., and the device will just sit there on the cyanoboot screen.
So, yes (?) you need to remove the card to boot "normally" (i.e., into the ROM), although even there if you are quick you can intercept the boot with the "n" button and go into emmc recovery (from one of the boot menu options).
Is the problem that you don't have any OS? I wasn't clear whether that survived your first attempts with the bad card.
Edit: if you want to use an sdcard with the NT for storage it will have to be a different one than the one you prepared specially for flashing cyanoboot, etc.
nmyshkin said:
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
Click to expand...
Click to collapse
I restored the ID type of the sd card and now my NT can boot normally with the card inserted.
Tried the AOSP 7 you recommend and it's very good, thank you for it - but I think it would be better to have more custom settings, but Xposed and something like that are too heavy to NT with AOSP 7.
I tried to flash the lineage os 14.1 in your notredame folder but it can't boot. Looped at booting animation. Also, I tried a rom from AndroidFileHost, DrM-14.1-acclaim-Root-OC, but I got the status 7 error when flashing it, nomatter I use 3.0.2.0 TWRP on emmc or 2.8.4.0 one on the sd card. Any suggestion?