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 just currently opened my box fresh out and installed z4root to root it... Sucess!
Now im trying to downgrade as i am "supposed" to according to this thread.
http://forum.xda-developers.com/showthread.php?t=1036956
This is what is in my about screen under settings so you know what version ect i have http://img546.imageshack.us/img546/1476/20110427032325.jpg
from the aforementioned thread i downloaded the 4349_Downgrade.zip and placed it on my sd card... Renamed it update.zip and closed usb connection, and then powered off and powered up first pressing and holding the "+" on the volume rocker on the top of the tab. and then pressing power.. When i say "+" i mean Volume + witch is on the top left of the tab closest to the right in the direction of the search home menu and back keys...
When im holding this combo of buttons the screen boots up after a second or two says recovery key detected or whatever in the top left for a few seconds and then goes to the g tablet white screen... THen it shows a box with a downarrow on it and a progress bar for a few moments and then shuts off and reboots into the homescreen.......
I read in this forum a topic how the guy experienced the same results but turned out he was holding the Volume - key... I made certian i wasent doing what he did and literally just held the Volume + key on the right edge with the tip of my nail and held power... Same results..
I have tried with the program root explorer going into the file manager... (Why is there a file called sdcard2?? never seen that before) i go into /sdcard find the update.zip i put from the renamed 4349 file and then back up to the "/" dir and mount as r/w and paste the update.zip in there then mount as r/o back out to home power off.. i repeate the aforementioned process and still the excat same thing...
The origonal update that was put on there when i first put in my newly formated fat32 sd card i deleted.. i have searched and search and have no idea what is wrong or how to fix this... Certianly i couldnt be the only one with this issue?
Please help, im just killing time sitting here waiting for help lol.... Thanks..
My end result is im trying to get CWM 08 on there and a great and stable rom witch i choose that RC1 of vegan.. Unless u know of a better one. And once this is all done is there a good kernal i should be flashing? Why and how do i do it.?
Thank you in advance..
1) The downgrade is only necessary if you were on 4349 to begin with.
2) what you described is exactly what should happen in stock recovery for 3588 and older.
3) No... it is not exactly what others have said about holding the wrong volume key because when you do hold the wrong one the screen goes black after a few seconds.
4) SDCARD is your internal storage. SDCARD2 is the mount point for your external (MicroSD Card) storage.
5) It sounds like nothing is wrong...
6) Install CWM... http://forum.xda-developers.com/showthread.php?t=865245
Ooook
The thread i mentioned in my first post the first link if u click it the title of tje topic reads
[STICKY] [ATTENTION] - 3991 and 4349+ VIEWSONIC-LOCKED BOOTLOADER INFO here
Also it has a link to a pic of my about phone so cant u tell from that?
I am lost i did excatly to a T as described in the tutorial in step 6 in your reply and im getting the same thing i hold down volume + it says recovery key detected for a few secs in goes to gtablet screen and flashes to that down with a down arrow.....
What am i missing? Surely i dont have the only tablet with this problem..
Yes, I can... Your TAP UI version is 3391... LOWER than what you are trying to downgrade to. So you don't need to. You are seeing exactly what is supposed to happen with the version you have. This is the normal behavior for that version.
The only thing you are missing is the knowledge that nothing is wrong...
http://forum.xda-developers.com/showthread.php?t=892090
There is nothing wrong with your tablet.....[mod edit]
K J Rad said:
Yes, I can... Your TAP UI version is 3391... LOWER than what you are trying to downgrade to. So you don't need to. You are seeing exactly what is supposed to happen with the version you have. This is the normal behavior for that version.
The only thing you are missing is the knowledge that nothing is wrong...
Click to expand...
Click to collapse
Then why can i not flash CWM? I went to your link tried both internal and sd files mounting on "/" and on "/sdcard" /update.zip or /recovery.zip in either folder and im still getting the same issue when i hold Volume + and power...
I cannot get CWM and a Rom on there.
thebadfrog said:
http://forum.xda-developers.com/showthread.php?t=892090
There is nothing wrong with your tablet.....just your knowledge
Click to expand...
Click to collapse
From what i gather from that link is that i am to take the files insides cwmod_microsd.zip witch are update.zip and recovery folder that houses command and physically take the microsd card out and mount on my computer witch is technicly SDCARD2 and place those files in that root directly... and then the power down insert card and vol up and power.....
I am getting the same issue same box and same nothing.
Most likely because you aren't following the directions. Take some time to learn at least the basics about your tablet. Then read the instructions again.
you can do it on either the internal or external. It depends on what the line in the command file says. Once you boot once whether sucessful or not the command file is deleted. Your making this harder than it is
Then what am i missing? I got this tablet yesterday at 2 pm and stayed up till 3 am trying to get CWM on it!
I cant imagine what im missing, ive read dozens of posts tried atleast 15 times putting either the downgrade or cwm sdcard update files in the internet "/" or "/sdcard" or "/sdcard2"
And yes i noticed that it deletes the update and recovery folder if i drop it in /sdcard2 or "/", ill put the files there either directly to sd card from the computer or thru root explorer and when i hit vol + and power it does the same thing.
This has to be the most frustrating tablet/ android device ever!
The last time i had something this hard was when i bricked my iphone in early 09 and figured out i had to reload the ipw file via a brand new install of itunes from a virgin computer (that computer turned out to be me using the librarys lol)
so i just got both the internal and external cwm files from this post
http://forum.xda-developers.com/showthread.php?t=865245
and put them in both /sdcard and /sdcard 2 for some reason when i used root explorer i noticed that for somereason in /sdcard2 there was a recovery/recovery/command so i pulles recovery to /sdcard2/recovery and pasted it there and deleted the other recovery folder.. re did the whole process and low and behold i was lookin at a CWMN screen! so... i have no idea, but if i ever meet the man who created the Vewsonic g tab ill kick him in the nuts.
Now i followed this guide
http://forum.xda-developers.com/showthread.php?t=865245
and i mounted the usb put the Vegan Rc1 rom in the ROMS folder and choose zip from sd and installed... and im just stuck at the view sonic screen, so i powered off did a wipe data factory reset and wipe cache and then went to advanced and fix permissions... Then to choose install from sd card choose my vegan rom and installed then backed out to home and hit restart and again its been ten mins or so and im still staring at a viewsoniv screen still..... Is this normal or any more suggestions?
There is a fix but as much trouble as you had installing clockwork I'm suggesting you avoid that fix so I'm not even saying the name. Stick with froyo roms
Thats not very helpfull... Just please tell me what it is i can ifgure it out on my own, i obviously did with the CWM now i just cant get the rom installed for some reason i have a tablet that just boots to the view sonic screen at the moment
Just to update...
I fixed it. THanks for your help and no thanks for your sarcasim.
Was stuck at the viewsonic birds screen
So i did so more, searching... its now 5 am and figured out what nvflash is and
via this thread http://forum.xda-developers.com/showthread.php?t=861950
and making sure u extract EVERYTHING in all the zip files with the exception to the USB folder u drop in the nvflash folder as directed, because if u dont u will get a error when u run nvflash_gtablet.bat
Once that is complete follow this thread
http://forum.xda-developers.com/showthread.php?t=865245
Word for word to install Vegan from stock... It may save a lot of confusion to just nvflash from stock and then drop the CWM recovery and update on the sd card and go that route..
Hope this helps and newbs...
See...the search function does work
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.
This guide was created for people who are not as familiar with the world of Switch exploits.
NOTE: This is not the official ROM thread! DO NOT ask questions about using, troubleshooting, etc. the ROM here. I will not be able to help you and it splits discussion. Please ask questions, tips, etc, in the official thread! This post is purely to guide users in setting up their PC and such for installing this on their Switch.
DISCLAIMER: Everything is done at your own risk. Use common sense.
What you will need:
An RCM exploitable Switch console. Check here to see if your device is exploitable. If you have a newer device an exploit may be possible on older firmwares, but if you haven't already set it up you probably updated to a too new version already. Read more here. (for non-RCM exploitable devices)
A jig or other method of triggering RCM. Here's a few methods. Premade jigs can be found online.
A computer. (Assuming a Windows PC for the purposes of this guide)
A good USB-C cable that can connect to your PC and Switch.
A high quality, high speed microSD card of at least 16GB.
A way to read microSD cards on your PC.
Required downloads:
The ROM, find it in the Downloads section of the first post. Select the SD Card size that matches yours. Read through the post as well for latest information.
If desired (but not required), the shield-ifier.zip and/or the Reboot2Payload zipfile also in the ROM downloads section. Shieldifier should allow you to download games meant for the NVIDIA Shield. Reboot2Payload means you'll reboot to Android when you hit "reboot" within Android (or Hekate if you choose reboot to bootloader). Without it you'll reboot to the default OS.
GApps, AKA Google Apps. This will install the Play Store and other Google services. Not required but 95% of people will want this. Select ARM64, 8.1, and then any on the right (Nano is recommended). Hover your mouse over each option for descriptions. If you're not sure just choose Nano.
TegraRcmGUI. This program will push the exploit to your Switch. Grab the latest .msi installer and install it.
balenaEtcher. This program will write the ROM to your SD card.
Hekate. This is the "bootloader" if you will. Once you get to RCM with your jig (or whatever method) this is the payload we'll be sending over. The ROM developer recommends using version 5.0 exactly, and I'll recommend that. Version 5.2+ however does include support for partitioning your SD card so you can use one SD card for Horizon (Switch's default OS) and Android, though I have not been able to figure it out.
I recommend putting the ROM, GApps, shieldifier, Reboot2Payload, and Hekate files all in one folder so your Downloads folder doesn't get cluttered.
Steps:
Insert your SD card into your PC. Backup anything you need to because all data on the card will be wiped.
Open balenaEtcher. Select the "android-XXgb.img.gz" file you downloaded. In the middle make ABSOLUTELY sure the device selected is the SD card you want to use. You don't want to accidentally destroy some other drive you have attached. Click "flash". This can take a while (30mins-hours depending on SD card speed and size!), especially on larger cards. The progress bar will jump around, and get stuck at like 99%. Don't worry, that's fine.
Once it's complete you can close balenaEtcher. You should be able to see two new drives in Windows explorer. One will give an error if clicked (Don't click format when Windows asks!) and another is a 2gb partition Windows can read. If these don't appear then reinsert your SD card into your PC. Mine mounted the unreadable partition as D:\ and the readable one as S:\. EDIT:Redoing this months later it only shows the one drive for me.
Place the GApps .zip (and shieldifier/Reboot2Payload .zip) file(s) in the root of the 2gb partition. Don't unzip them.
Eject the SD Card from your PC and place it in your Switch.
Use your preferred method of booting into RCM. I posted a link with many methods in the "What you need" list up top. You'll know you're in RCM when the Switch screen stays black and doesn't boot as normal when you hold Power+Vol Up.
Launch TegraRcmGUI. Go to the settings tab and select "Install driver". Go back to the payload tab and select the Hekate .bin file as your payload. Connect your Switch. It should say "RCM OK" in TegraRcmGUI. Now select "Inject Payload". Once you see the GUI on your Switch then you can disconnect it.
Tap "More Configs" and then hold down Vol Up and tap "Switchroot Android". Continue holding Vol Up until you get to the TWRP menu.
Tap "Keep Read Only" on the first screen.
Tap "Mount" and check "System" and "Vendor". Then tap the home button at the bottom. (If they don't appear, move your finger up and down in the middle and it should refresh, try that every time it looks like things are missing in TWRP.)
Tap "Install", then "Select Storage", then "Micro SD card" and "OK". Tap the GApps zip, uncheck "Reboot after installation is complete" and slide the slider to the right. Optionally do the same for shieldifier and Reboot2Payload (press back after GAPPS flash to go back). Once finished with all zips wipe the Dalvik cache (it will prompt you). NOTE: If you want GAPPS you MUST install GAPPS before you first boot up Android, so if you accidentally booted into Android, reflash your SD card and restart the guide (you may be able to wipe data and caches through TWRP to fix it, I haven't tested).
Select "Do not install" if it asks to install the TWRP app. Reboot the device (you may have to hold the power button), enter RCM again, and re-inject hekate from your PC. Boot Android again but this time don't hold any buttons. Your screen may be black for a minute, don't panic. First boot takes a while.
Your device should boot into android. Congratulations. Update the NVIDIA Shield app through the Play Store if you installed it. For setting up anything else, or for questions you may have, use the official thread.
NOTE: This is not the official ROM thread! DO NOT ask questions about using, troubleshooting, etc. the ROM here. I will not be able to help you and it splits discussion. Please ask questions, tips, etc, in the official thread! This post is purely to guide users in setting up their PC and such for installing this on their Switch.
You are missing the step where you mount the SD card first before installing GApps. GApps install will fail if you do not mount the SD in TWRP first.
weirdingway said:
You are missing the step where you mount the SD card first before installing GApps. GApps install will fail if you do not mount the SD in TWRP first.
Click to expand...
Click to collapse
Tap "Install", then "Select Storage" (If the dialog box is blank just slide your finger up and down to scroll and it should refresh), then "Micro SD card".
Click to expand...
Click to collapse
That seems to do it for me.
gorei23 said:
That seems to do it for me.
Click to expand...
Click to collapse
That works for me AFTER I mount the SD card "System" in TWRP
EDIT: You even said it yourself but missed adding it to your guide. Just trying to help
https://forum.xda-developers.com/ni...ageos-15-1-t3951389/post79971072#post79971072
Paper clip
I need a step by step. Cause that parts so confusing...
weirdingway said:
That works for me AFTER I mount the SD card "System" in TWRP
EDIT: You even said it yourself but missed adding it to your guide. Just trying to help
https://forum.xda-developers.com/ni...ageos-15-1-t3951389/post79971072#post79971072
Click to expand...
Click to collapse
Ohhhhh you mean mount the /System partition? I think we had a miscommunication. The "sdcard" is automatically mounted, as shown in the YouTube video I hastily made...
I believe the part about mounting the /System partition is only needed sometimes, depending on what you told TWRP to do with the /System partition on first boot. Got ya.
sSHARPZz said:
I need a step by step. Cause that parts so confusing...
Click to expand...
Click to collapse
Not much to it. Short pin 9 & 10 and hold down power and vol up. If you can't manage it look into buying a premade jig that does it easily and reliably.
So one side of the paper clip directly on pin 9,10 and the other near a conductive metal? Also there are several options on amazon. (Quickest shopping method) any chance you can point me to the correct one?
sSHARPZz said:
So one side of the paper clip directly on pin 9,10 and the other near a conductive metal? Also there are several options on amazon. (Quickest shopping method) any chance you can point me to the correct one?
Click to expand...
Click to collapse
Just shorting 9&10 should do it. They're just plastic with a tiny piece of metal inside. Just find one with good reviews.
What's the best way to boot into recovery, this is my first time trying to do anything in relation to modding my switch, any help will be highly appreciated!
everything is working but my joycons wont connect any ideas?
One thing that isn't on here that was required for me was to wipe the dalvic and the cache right after flashing GAPPS. It wouldn't boot aftr that, might be a good addition to your guide. Thanks for the guide though, it was absolutely amazing and got be Android!
Does it cleans the data on switch or just clear the sd card?
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Does this process make any changes to the Switch? Normally I use SX OS and would rather not mess with it just to try Android.
Will the switch boot android automatically, or do you need to inject hekate from a PC or phone every time you want to boot it?
bottmint said:
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Click to expand...
Click to collapse
Yea get an RCM jig from Ebay. Well worth it with no hassle.
Sent from my SM-G955U using Tapatalk
Clip
bottmint said:
Please don't advise people to shove a paperclip into their rails. The pins are susceptible to damage. Advise them to purchase a proper jig, instead.
Click to expand...
Click to collapse
We asked, he answered. What’s it to you?
Atmosphere and Android
This is awesome news, by chance I had just ordered a hackable Switch today.
Might be a silly question, but I was planning to follow the NH Server instructions to install the Atmosphere CFW
I have ordered a 512GB Micro SD Card for homebrew stuff
The instructions here (Thanks, very clear) suggest that an entirely new / dedicated SD card will be needed for Android.
Anyone planning / see a way to partition and have Atmosphere apps AND Android off of 1 SD card?
Thanks
After injecting payload, screen stays black. Anybody having this issue?
See screenshot showing payload was successfully injected.
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?