Related
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 now making post that there really shouldn't be any need for, because all that's in here is already covered elsewhere. 100% Apparently not easy enough to find for newcomers, so I'm making an attempt to help info collection.
NOTHING here is my work! All I’ve done is trying to make easy to follow instructions to other people’s hard work. Those people deserve your thanks, not me!
I’m a newbie myself and that’s why I can say that this really is very easy! If I can do it without problems, so can you! I try not to chat away too much in the instructions. Make regular searches, here or Google for more info. I found it, so surely you can too! Any questions? Well, being a noob myself I probably can't answer. Google is a very good friend of mine though...
Please do not ask questions through pm. It's better if people that know more than I do get a chance to answer them in the thread instead!
You need to know how to burn an sd image. Separate instructions to that after the other instructions if you don’t.
Step 1: Establish what it is you want to do! Choose A, B or C
A: You do not want to touch the internals of your NT but want to try CM10 anyway
B: You want to stay in the BN environment but would like to be able to install apps from elsewhere (for example Google Play Store)
C: You want to get rid of BN and install CM10 instead.
A: Run CM10 from sd card – no root required
This should work on 8GB Tablet as well as 16GB
When you boot into the card you’re running Android ICS. Remove the card and you’ll boot to internal BN operating system. (Or keep the card in, boot to Cyanoboot Menu and choose “internal boot”)
Ready-made card image download links to be found here: http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
It’s a large download (around 500 MB), but it is a ready-made sd card image. As it says in the instructions there, you’ll more than likely want to expand the user partition to take full advantage of the card, but that’s covered in his instructions.
There are other, more manual ways to make these cards as well. Also covered both in that blog and here at XDA! Go search!
B: Root the Tablet
This works on both 8GB and 16 GB Tablet.
“Rooting” is like unlocking your device, giving you access and control over it. You’re still running BN operating system though. Several excellent root guides here on XDA.
For example: http://forum.xda-developers.com/showthread.php?t=1488035
Or http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
The first one (Brian’s) require a 2 GB card the other one (Albert’s) just needs a very small card. (I think 128 MB would do, but I don’t have any that small to try)
Both give good instructions in their topics.
Both install gApps.
If you want to block OTA updates from BN, go to Play Store and find NT Hidden Settings. Even if it got installed with the root it’s probably not latest version and doesn’t have the Block OTA function.
C: Installing CM10 internally
***8GB owners must make sure to use ROM that works with their device!***
Since I’m a noob I look for easy way, and this is very easy and needs very little know-how!
***Warning! CWM is a very powerful tool. Do not "wander around" and "experiment" with stuff without doing proper research! Seriously! DON'T!***
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/showthread.php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
3. Boot into the sd-card and it should take you to CWM 5.x.x. environment.
I guess a backup of you current system would be a good thing (even though I admit to skipping that myself). To backup you'll probably need another card if you're using "The Albert Card" now, because I doubt it's enough room on that.
You navigate with the volume rocker, go back to previous menu with “power” and confirm choices with “n”
Choose “install zip from card” – “choose zip from card” – your CWM zip
See warning above!
4. Power off and prepare your sd card for ROM flashing. (If you’re working with just one card you will need to format it with SD Format or similar to get it back to full capacity.) Put your CM10 ROM zip and the appropriate gApps zip on the card.( It doesn’t matter if there’s other stuff on the card, so you don’t have to format it because of that!). I will not link to a specific ROM. Make your own choice but be sure it works for your model and also make sure you use the right gApps!
5. Reboot into Cyanoboot. This took me a couple of attempts to get right.
From powered down device, press power and right after that press and hold "n", You should boot into Cyanoboot and get the boot menu. Choose "Internal recovery" and you should get into new CWM
6. I don’t know how much clearing is needed, but I prefer to clear pretty much everything to make sure of a clean install. Cache and Dalvik I always clear.
***DO NOT format anything unless you knwo what you're doing! *** (See Satan's posts below)
7. Flash ROM and gApps same way as you flashed the CWM 6.x.x (install zip from card – choose zip from card) reboot and go!
How to burn an sd-image:
I use Win32Diskimager. Download link in Albert’s root topic (and numerous other places!!)
Unzip into a folder.
(I also copy my various img files to that folder to have them easily available)
No need to install, just run by doubleclicking the EXE in the folder.
Make sure the device letter really is your sd card.
Click on the blue folder and navigate to your img file, choose it and “write”.
It will take some time if it’s a large img, but that’s what the progress bar is there for, isn’t it?!
Nice work ,
But you should add 'do not format any partition ' warning. Android users coming from other devices might do this by default during flashing rom.
Almost every one with bricked tablets has tried formatting partitions.
Sent from my ST21a
Thanks Satan! I did not know that! Will do!
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
satan89 said:
but looks like some people missed it.
Click to expand...
Click to collapse
It looks like a lot of people miss a lot of things...
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
+1000
Do not format especially the rom partition and, most critically, the factory partition which respectively contain a set of small files with device-specific unique data (not only Serial No. but also MAC address, public/private key certificates, etc.) and the backup archive copy of the same data files (/factory/romdata.zip).
Unfortunately, I've seen some "unbricking" tools (including some that are very frequently cited/recommended on these NT forums) reformat/zero-out and flash over these 2 partitions. The end result being, even in the event the "bricked" NT gets "restored to stock", depending on the specific tool used it could be carrying device-specific data of someone else's (e.g., tool developer's) NT.
EXACTLY!
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
I think this is exactly what happened to my NT. Took me weeks of researching (I don't have a lot of free time) to figure out how to restore my 16GB NT.
Help
Im trying to single boot CM10 from sd card without touching nook os. I am using guide (CM10.0 Jellybean SDCard IMG for Nook Tablet (12/31) FINAL)
I have tried for hours using different methods also and cant even get it to boot to CM, no CM logo at all. I have a BNTV250 NT on 1.4.3. I have tried multiple sd cards, I am using a Sandisk 8gb class 6.
In a nutshell all I should have to do is
-Format the card with SD formatter,
-Extract the (Extract cm10_xxxxxx_sd_hd.img from cm10_xxxxxx_sd_hd.7z/rar)
-Use Winimage to write the image to the SD card, correct??
The Nook still refuses to boot into Cyanogen, just boots up normal every time!
same with every procedure i have tried,
Any pointers????
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
asawi said:
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
Click to expand...
Click to collapse
No, I have not, will try now.........ty
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
HOLY ****!!!! I LOVE YYOU!!:laugh::laugh::laugh::laugh::highfive::victory:
That worked, I cant believe it. Why is this not written anywhere??
LOL! :laugh: Glad you got it working!! :good:
Any clue of how to get rid of booting that way? I'm not always with a USB cable witj me.
Enviado desde mi Nexus 4 usando Tapatalk 2
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
asawi said:
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Tried doping that with no luck. After 8 or 10 attempts magically boots todo cm. Thanks.
Enviado desde mi Nexus 4 usando Tapatalk 2
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
ThePhantom97 said:
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
Click to expand...
Click to collapse
Thank you very much for putting this together, it was very helpful!
I POSTED EARLIER BUT IT NEVER SHOWED UP SO IM REPOSTING. sry for caps.
rooted my nook color and everything was fine. then i tried to root my nook tablet. searched all over the net for comprehensive instructions to do so and i found this
The first thing you need to do is extract the contents of file #1 and write the extracted img file to a Micro SD. If you are using Microsoft Windows then click the file named Win32DiskImager.exe, select the NT16or8gbV47SDimagefile.img, select your drive letter for your SD card.
If you are using Linux, then open up the terminal and CD into the directory where NT16or8gbV47SDimagefile.img is located. Once in the correct directory issue this command to write the .img to the Micro SD:
sudo dd if=NT16or8gbV47SDimagefile.img of=/dev/sdX
You must replace the X in sdX with the appropriate letter for your SD slot. There are many ways to get the correct letter but I use the program Gparted.
Ok, so now you have an SD card that will root your Nook Tablet. Let's boot into Recovey. Turn off your Nook if it is on, and connect the USB wire to your computer. Your Nook will now turn on and enter into ClockwordMod Recovery. Using the Volume Keys to move up and down and the N key to select, click on Install zip from SD. You will now see a zip file called Root_8gb-or-16gb-NTV4_7.zip. Highlight that file and press the N.
If all goes well, the operation will complete. You are now rooted. Press the Power button to go back to main Recovery menus and select Reboot and press the N key. Your Nook will appear normal. It is not. Press the N key and you will see a new option for Home screen. Clicking the new Home icon will take you to an Android looking desktop. Yay! We are not done yet.
Now, install ES File Explorer from the Play Store. Open the app and browse your Micro SD card. Look for a folder called Apps. In this folder you will see a file named Nook Recovery Flasher.apk. Click this file to install it. Once installed, click on Flash CWM Recovery. Now you do not need the SD card you made earlier to boot into Recovery. It is now part of the system.
Remove the SD card and connect it your computer and format it so that it is empty.
Copy the files #2, #3, and #4 that you downloaded from above to the SD card and insert it back into the Nook Tablet.
Remember how to boot your Nook into Recovery mode? Do it.
Select Install zip from SD again and install ONLY CWM_v6.2.7_emmc.zip. This will upgrade your recovery. Without upgrading, you will not be able to flash CyanogenMod. Once the operation is complete, use the power button go back to reboot the Nook. Boot it to Recovery one more time.
Now you can select the latest CyanogenMod file you downloaded to install it. After that, select the latest Gapps you downloaded. Reboot the Nook and you are good to go!!!
. i folowed all the instructions to the dot. but when i got the this step, "Remember how to boot your Nook into Recovery mode? Do it." and i did it. but when i rebooted it immediately tried to boot into recovery but got stuck on the cardboard box screen and it flickered none stop and would not proceed to recovery (CWM) menu. I tried everything i could think of and i found that if i reformatted my sd card with the CWM sd root img and put sd card into NT and boot up it successfully brings up CWM. from this i tried both normal cache wipe and advanced menu cache wipe and also tried wipe to factory settings and wipe battery stats, rebooted and it still gets stuck on the flickering cardboard box screen..........anyone have any ideas? i cant seem to boot it up at all past this screen. maybe i shud format system through sd-card cwm? but then i would have no OS, so how would i proceed with this. is it totally broke or wut? god i hope not:crying::crying::crying::crying::crying::crying:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
wut ive got so far
digixmax said:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
Click to expand...
Click to collapse
well i think wut u gave me is exactly wut i need. followed the custom rom tutorial and it worked fine to the point to where i first get to cyanoboot menu where i would have proceded to install cm10 and gapps. but i accidentally put the wrong cwm on the sd card and it said bad boot. (note it also said it disabled charging) so i go the right cwm boot img for it. but the fact that it disabled my charger i cannot get back into the cyanboot menu. anyone kno how i can reactivate charging? if not then im completely screwed because once it dies i wont be able to charge it again and it will be flippin useless. even worse than before.........sigh fml someone shoot me in the dome
The "charging disabled" message on the Cyanoboot screen does not mean what you think it means (i.e., charging is turned off on for good until you somehow turn it on again). If you're stuck on that boot screen, just hold down power button for 20-30 sec to turn it off and start over with the SD card with the right CWM.
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
YAY!
Temetka said:
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
Click to expand...
Click to collapse
YAY! i figured out how to get past the bad boot part. just be sure to be vigilant and press "n" asap when the screen boots up in cyanoboot......and i mean like THE second it pops up. that solved all my problems.......
but i dont understand the piece of advice part with the 5 point/ 10 point touch installer deal. ill do alil research on it to see wut it is and wut i got to do. if you care to send a link explaining it that would be super flippin awesome. and btw thx sooooooooooooooooo much. this forum has been the most helpful place. quick responses and accurate information. everyone i talk to rocks. i appreciate it so much. :victory:
The 5point and 10point touch is just that.
So you know how your screen responds to your touch input? And let's say you use to fingers to zoom in on a picture. That would be an example of 2 touch. Expand from there for more finger interaction.
Here's an XDA thread on the topic:
http://forum.xda-developers.com/showthread.php?t=769932
and nice Wikipedia article on how multi-touch works:
http://en.wikipedia.org/wiki/Multi-touch
Glad you are up and running.
[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet
Edit 2-5-23: I recently revisited my installation and found it had become sluggish to the point of being more or less useless. Google Play service updates had taken their toll. So I decided to start over and use microG instead. I also found that the original rooting method no longer worked for some unknown reason, so I resorted to Magisk. Seems like a good time for an update to the instructions!
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Using microG to spoof Google Services Framework signature frees you from the relentless pressure of GApps as Play Services are always updating and always expanding. I originally used a pico GApps package on my first install. At the time the package was 77 MB. The current package as of this editing is 184 MB--too much for the device. You can start with my original package but it won't stay that size. Still, some people will want to try so I have provided instructions for both microG and GApps.
If you have a bootable SD card made for installing CM 10.x-13.x, you can skip to step 2b.
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
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from https://www.mediafire.com/?5vcw8l603d3r5sc or https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8 [this ROM is no longer in the repository maintained by @amaces] (alternate link provided by @mikeataol)
e. Magisk for the Nook Tablet: https://forum.xda-developers.com/attachments/magisk-v16-0_patched2-zip.4427362/ (credits to member @fddm)
OPTIONAL:
f. the zip file of the GApps package (corresponding to Android 7.0): https://www.mediafire.com/file/po12x99lg47p4oj/open_gapps-arm-7.0-pico-20170310.zip/file
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install magisk-v16-0_patched2-zip
OPTIONAL:
k. Reboot to internal (emmc) recovery as in 3d.
l. Select Install. From the external SD card install appropriate opengapps zip
Continue here from either step j or step l
m. Remove SD card and select reboot.
For GApps
n. Wait for first boot to complete and sign in.
After first boot and the usual stuff, check Magisk Manager to see if root is enabled. You will be asked to update Magisk Manager. You can say "yes" ONCE. It will ask every time you open the app, but don't say "yes" again. The next update will render it inoperable., you'll lose root, curse me, etc. You've been warned.
Done!
[Don't you want to make a baseline backup right now?]
microG (for those skipping GApps)
Spoiler
You've skipped GApps if you're looking at this. There are all kinds of packages available for Magisk to do all the microG stuff in one fell swoop. But there's a lot of contradictory information out there and many of the packages include other stuff you may not want. Also, this old version of Magisk may not work with some of the packages. In the end I decided to try setting up microG the way I learned to do it: manually. It's not that difficult and you get only what you want.
To work, microG requires that signature spoofing be enabled on the ROM. On this ROM you need to use Xposed for that. So let's get started!
4.
a. Download the Xposed installer zip for Magisk and SDK 24 (Android 7.0): https://www.mediafire.com/file/v6zkpj4n3rbi11t/xposed-sdk24-topjohnwu.zip/file. Copy the file to the bootable SD card you used for the ROM installation.
OPTIONAL
b. Download the flashable maps zip file and copy it to the SD card (you only want this if you wish to use Location services or might want to run Tasker): https://www.mediafire.com/file/7y8cmr4obydo35d/mapsv1.flashable.zip/file
c. You'll need some kind of root file manager for this process (you could use adb, but it's cumbersome). I've attached an old version of ES File Explorer that I like. You'll have to adb install that since the meager sort of "file manager" in the ROM doesn't work with the package installer.
d. You'll also need the Xposed installer app and the Fake GApps module which enables signature spoofing. I've attached both below.
e. Finally, you need the microG component apps. You can get them here: https://microg.org/download.html. You want Services Core, Services Framework Proxy, and Store. If you want to use Location services, you will also need the UnifiedNLP app.
The tools are now assembled!
f. Shut down your tablet and place the bootable SD card in the slot. Power up.
g. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery
h. Select Install. From the external SD card install xposed-sdk24-topjohnwu.zip
OPTIONAL
i. If you want to use Location services, also install mapsv1.flashable.zip
j. Remove the SD card and reboot. The process may take a little longer due to the new Xposed framework (first time only).
k. Transfer the apps you collected in steps d and e above to the internal Download folder. Use the root file manager you installed to install the Xposed installer app and the Fake GApps app. Open the installer app and check anything that needs checking then reboot. Check the installer app once more to see that the Fake GApps app has been installed and enabled.
l. Using the root file manager create the folder /system/priv-app/Phonesky. Set folder permissions to rwx-rx-rx. Use the root file manager to move fake "Store" app (com.android.vending-16.apk) into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
m. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core and Services Framework Proxy for this step). Reboot.
n. Check microG Settings to be sure spoofing is enabled and other permissions are granted. You don't need to enable any of the other Google stuff at this point unless you want to.
OPTIONAL
o. If you want Location services install the UnifiedNLP app then return to microG settings to configure (check regular settings for "Location" also--you'll see that the microG settings have been inserted into the general Settings app)
OK, you now have microG running at its lowest service level. Without doing anything else it should provide signature spoofing for apps that are looking for Google Services Framework. If you want higher levels of service (say, an actual Google account) you can make those selections in the settings. Generally, apps that require a Google account will call up microG to initiate a Google login (slow, but it works).
It is theoretically possible to run the PlayStore with the right configuration, but I would not recommend it. The Aurora Store (F-droid) runs really well on the device and can provide you with PlayStore access without GApps (or more demanding levels of microG service). You can use the anonymous login.
Calendar and Contacts will not sync with Google using microG. There's a lot of old stuff online about this working and how to set it up, but it does not work any more, so don't waste your time. If you MUST have synced contacts and calendar, you can use DavX (F-droid) (configuration--start with Calendar!) . Otherwise you can export a vcard file (*.vcf) of your contacts and load them in as a local set on the tablet. For a contacts app I extracted the Contacts.apk from a CM 13 ROM and placed it in /system/app/Contacts (permissions rw-r-r). Likewise the Calendar.apk in /system/app/Calendar. I've attached these apps below.
For email I tried using the AOSP client from a CM 13 ROM. The system recognized it but crashed on opening. Eventually I settled on an older version of K-9 mail (6.20). I had problems with Google 2-factor verification with the more current versions.
I've attached a screenshot of my system below. More discussion on individual apps and issues in the following post.
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues and app options.
Updated 2-16-23
Issues and Apps
Every custom (and stock) ROM has some issues. This one seems to have very few and they are easily addressed.
1. The stock browser is "broken", at least to the extent that it cannot save bookmarks.
Here's a fix for the bookmark issue. Use a root file manager to navigate to /system/app/BookmarkProvider. In that folder you will find an apk file of the same name. Tap to install (actually update, I guess). Then reboot.
A good alternative browser that works well with this ROM is Via.
2. The stock launcher is pretty basic. After a lot of fooling around with display and font size in Settings I found no combination that significantly affected the rather large (for my taste) icon size without otherwise distorting the display in some way.
I ended up restoring the display to defaults and installing Nova Launcher.
3. There's no Gallery?! Yep. For awhile I was using a Gallery from my old CM 10.2.1 install, but it didn't work very well. Then I discovered that @theportal2 had worked up a Lineage Gallery app with the necessary libraries for install on other ROMs. It works great and includes a ton of features, even photo editing. You can get it here: https://forum.xda-developers.com/an...lineage-os-gallery-apk-photo-editing-t3664460
4. The MTP file transfer setting in Settings>Developer options>Networking>Select USB Configuration is not effective and selecting it in Settings seems to encourage the MTP host to whine with system messages occasionally.
Leave setting on "charging" (default) and when you connect via USB, use the pull-down notification to select MTP transfer for that session.
Better yet, you can disable the MTP Host app with no apparent repercussions. Just go into Settings>Apps (show system) and disable it. I was sort of surprised that this had no effect on file transfer protocol.
5. The swipe-to-unlock screen is tenacious and its use may result in repetitive motion injury.
OK, so maybe this is a "feature?". If you touch anywhere on the swipe-to-unlock screen the little "Swipe to unlock" bounces up from the bottom. With that visible, the screen swipes effortlessly. Who knew?
6. The system throws up two notifications when you connect to USB (if you have debugging enabled). Just a minor annoyance. If you don't like seeing those two "N"s either, you can see just one (for the connection type: charge, transfer, etc.) with a simple addition to /system/build.prop:
Code:
persist.adb.notify=0
7. Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I recommend off-loading a copy and editing with something like Notepad++. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
Replace the file on the device with the edited version and reboot. This change will be overwritten if the app updates, so you might want to keep that in mind.
8. I am partial to the version of ES File Explorer which is attached to the first post. It's not too bloated and works well with the device, the package installer, etc.
9. Generally speaking I would gravitate toward older versions of apps which may be easier on the system. As an example, I'm using version 1.8.6 of MX Player, long before all the streaming nonsense took over. TuneIn Radio and Pandora are so old they will run on Android 2.1! Sometimes enough is just right.
Apps that don't work
1. The NPR News app currently in the PlayStore at this writing crashes repeatedly just after starting.
Version 2.6.1 works fine. Interestingly, when the PlayStore version installs, the icon background color is black. On another Nook Tablet (HD) running CM 11, the same version installs with a white icon background and runs fine. Version 2.6.1 also installs on this AOSP ROM with a white icon background. Hmm.
Xposed
Oh yes, even I eventually missed a feature or two from my last CM install The good news is that the Nougat version of Xposed runs well on this ROM, at least to the extent of using Gravity Box (I just had to have the extended power menu back.....)
Alternative apps for microG
I've included some of the more common ones (Contacts, Calendar, Email) in the previous post. If you've set up Location service you might want Maps. I've not had much luck with newer versions of Maps on my various devices. Too greedy for system resources. But I have found an older version of the app which still runs, includes Places, and allows you to cache map areas which do not expire.
YouTube is another real resource hog. I'm not a big YouTube fan, but there are times when I want something and a browser like Via or the stock one is so-so (it works, but you have to be patient). I looked around and decided NewPipe would meet most of my needs. It's not perfect. The full-screen player crashes on all the custom ROMs I've tried. However, you can set it to use an external player (like MX Player) and that works fine with full screen. I really like the ability to download videos (or just the audio) in a recognizable format--and even to the SD card!
And don't forget the Aurora Store (F-Droid) for PlayStore access.
nmyshkin said:
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Adding a pico Google Apps package keeps the ROM mean and lean while giving you PlayStore access to add just what you want.
If you have a bootable SD card made for installing CM 10.x-12.x, you can skip to step 2b.
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
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from my Dropbox: https://www.dropbox.com/s/b7zc8d56z2gl69m/aosp_acclaim-ota-NBD90Z.161020.zip?dl=0 (alternative link provided by @mikeataol: https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8) [this ROM is no longer in the repository maintained by @amaces]
e. the zip file of the Gapps package (corresponding to Android 7.0) from http://opengapps.org/
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install appropriate opengapps zip
k. Remove SD card and select reboot.
Wait for first boot to complete and sign in. To fully enable root access for ADB and apps you must install the opensource version of the SU interface from the PlayStore: https://play.google.com/store/search?q=phh superuser&c=apps. Search for "phh superuser".
Done!
[Don't you want to make a baseline backup right now?]
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues.
Click to expand...
Click to collapse
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
ehtisham ali said:
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
Click to expand...
Click to collapse
You can try, but I think you'll need to update the internal TWRP at least.
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
nsfgp said:
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
Click to expand...
Click to collapse
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
mikeataol said:
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
Click to expand...
Click to collapse
Thank you Mike!!! It is the /system mounting .... I never thought it would have to be mounted .... since it complaint not enough space instead of not found/mounted. But anyway .... I mounted /system in TWRP after ROM install+reboot into recovery. Now I can see stuff inside /system.
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Do I really need those stuff in /system/media and have to copy it back?? If no use I want to keep it lean.
Thanks again!!! (I am using the exact LNOS ROM in A's experimental folder as you mentioned)
Just a heads-up that I don't actually have the hardware, so everything that I upload for acclaim is not really tested, but I try to not to break things.
nsfgp said:
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Click to expand...
Click to collapse
I'll put something like this on the list, so a larger /system (upstream Lineage, or via REPIT) is usable with these builds (Lineage/AOSP would still need manual resize).
So far this build (7.0) works much better than 6.0. Thanks!
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
killerkalmah said:
Hi, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
killerkalmah said:
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
mikeataol said:
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
Click to expand...
Click to collapse
That's they way I've tried, inserting the USB cable, the sd is class 4 indeed, so I don't know what it could be.
nmyshkin said:
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
Click to expand...
Click to collapse
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
killerkalmah said:
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
Click to expand...
Click to collapse
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
nmyshkin said:
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
Click to expand...
Click to collapse
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
killerkalmah said:
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
Click to expand...
Click to collapse
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
nmyshkin said:
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
Click to expand...
Click to collapse
Alright! I found 3 sd cards each of them with a 2gb capacity, that should the incompatibilty, each three are different brands, and I found a better SD adapter, I will re-do all the steps in building the SD and if that does not work will download the files again with jdownloader to avoid menace pop outs, and if that doesn't do I will check the MD5 :fingers-crossed: I will update here, and thank you again!.
Update: it was the SD, I manage to do all the steps except for the gapps file, I couldn't install it, which you will recomend to download, I download the ARM android 7.0 mini, and more importantly my tablet loops on the "android" screen, with or without the SD inside, am I missing something? I did not installed supersu even though I got asked a few times during tutorial, any suggestion?
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
nosborm said:
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
Click to expand...
Click to collapse
I'm a little bit lose regarding memory space on this tablet, I reinstall the OS that was in this tutorial and finally booted to menu, but I can't connect to wifi, I don't know why, I might install another OS, which gapps file you reccomend to download? the stock, full version or mini?
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?