Database Info

[Q] Fuhu Nabi 2 - Root and Removing Monarch

I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?

theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
Go into the settings of ES file explorer and check everything under root settings. The only folder you want to get rid of is the Apps in the vendor folder. Anything else can harm the system. I just used the cut feature on the apps folder and pasted it to my sd card to make sure it worked first. Good Luck!

That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.

theonyxphoenix said:
. then switch to boot in parent mode, .
Click to expand...
Click to collapse
how ?

theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
Guess I missed something and should've read better, how did you set it to boot only into parent mode.
Sent from my SAMSUNG-SGH-I957 using xda premium

theonyxphoenix said:
That worked great, thanks. I had to make sure to change it to always boot in parent mode or else it tried to boot the monarch interface on a cold start and, not having the necessary files any longer, just ended up with a blank screen. I had to restore a unit to factory and then switch to boot in parent mode, then remove the apps folder. Works like a charm now.
Click to expand...
Click to collapse
How do you set it to boot into parent mode?

byohaserd said:
How do you set it to boot into parent mode?
Click to expand...
Click to collapse
Did you try going to settings -Security - put a TIC in " Set Parent Mode as default mode " ?
---------- Post added at 07:15 AM ---------- Previous post was at 07:07 AM ----------
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
---------- Post added at 07:28 AM ---------- Previous post was at 07:15 AM ----------
theonyxphoenix said:
I have managed to follow the instruction to root and install the google play store from this http://forum.xda-developers.com/showthread.php?t=1905674 but it also mentions the ability to remove the Monarch kids interface and make it a regular ICS tablet. I am unable to find the system/vendor files to remove them. I have root permissions since it allowed me to run Titanium Backup.
I used ES File Explorer and wasn't able to find the necessary folders to remove Monarch. Any advice?
Click to expand...
Click to collapse
I used TWRP to do anything - rooted or unrooted you can make change as you wish .
when you are in TWRP mount system then use advanced and file manager
hope this helps

I did not see that until you mentioned it...thanks
I was able to get it to work by going into a startup manager and freezing kidsmode2 and nabimode. I erased the apps folder though cause I wanted the space freed up.
Sent from my NABI2-NV7A using xda app-developers app

I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?

Rest to Factory setting
mikewhit001 said:
I deleted some files I shouldn't have. My nabi 2 keeps rebooting. It goes from the start up screen to "Android is upgrading..." Then back to the start up screen, then again. When I try to go to "Recovery Kernel" I get the Android laying down with the Red triangle over his chest..any suggestions?
Click to expand...
Click to collapse
1-switch off.
2-press power button & vol + together.
3-press vol - to go to recovery kernel and press vol + to select it.
3-android model should come lying down with red triangle!.
4-press vol - & vol + together.
5-select the system reset and press power button.
6-after that switch off and on with all new factory settings.
Best Regards.

Eric Karz said:
ALSO
I found no need to delete the vender/apps folder as it can be used to help get rid of "Android is upgrading ' message after each boot up that seem to come when you install apps from play store
Click to expand...
Click to collapse
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1

Nabi 2 Charge/Reboot problem
t499user said:
I created a new gapps package that does away with the upgrading message on every boot.
http://forum.xda-developers.com/showpost.php?p=35887804&postcount=1
Click to expand...
Click to collapse
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!

I flashed your package but the android upgrading still shows up for me,only for a few secs and it seems as if no programs get upgraded...what are your thoughts on this? How can I find the stray files that are causeing this?
Sent from my NABI2-NV7A using xda app-developers app

stuck in TWRP
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.

mikewhit001 said:
My tablet only boots in TWRP v2.2.2.1
I've flashed at least 5 different images in fastboot using at least 5 different methods. Every time I think I make any progress, I reboot my nabi2 and it reboots directly to TWRP. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.

ALD3 said:
Are you trying to flash a backup of 1.9.37 or just a program thru install? I know that if you wipe system and then flash another backup, if the backup is no good, twrp will not boot system but go right back to twrp. That is a safety setting, cause if it booted with no system installed you would most likely have a bricked device. That happened in the early days of Twrp, so they added the safety setting. If you flashed a backup, how long did it take, a good backup or image will take 10+ minutes, a bad 1 will say done in 1-2 minutes or less.
Might help if we had a little information about what you where doing.
Click to expand...
Click to collapse
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.

mikewhit001 said:
I tried flashing multiple backups and they all go to twrp. The backups only took a minute or 2.
Click to expand...
Click to collapse
Ok your backups are all bad, that's why it finishes so quick and won't boot out of TWRP recovery. You will have to download a image file and get it into the TWRP folder on your sdcard. You will have to download it on your computer unrar it and name the folder something like unrooted 1.9.37 and transfer it to your micro sdcard. Then put micro sdcard back in tablet. In TWRP recovery, you will have to go into Advanced>File Manager. In file Manager, you will have to click on external sdcard and copy the file from there back to sdcard>TWRP>backups>serial#>unrooted 1.9.37 it doesn't matter what the folder name is that you put in the serial# folder but the all the others are as named and your new folder HAS TO BE IN THE SERIAL# FOLDER, or Restore will not see it. When that is done go back to main menu and Restore, you should see your new folder, choose it and swipe to restore. This should take 10+ minutes. You should be able to reboot to system then.
Unrooted1.9.37 file to download
https://www.box.com/shared/ew0jcmch2ohvr43ubjqe
This thread can help you a lot quicker.
http://forum.xda-developers.com/showthread.php?t=1905674
If you have problems, PM me and I will send you my email so we can work quicker and won't trash up this thread.

I'm having the same issue since the gapps update, where the Nabi shuts itself down while charging. Sometimes it can be a real pain to reboot after it does this.
Funhog51 said:
Completed the OTA to 1.9.37, root, and gapps install - had the upgrading message on every boot but fixed that with the new gapps package (thanks a lot to all the great developers on this forum!)
However I still have a problem since the root process that I haven't seen addressed so far after searching the forums.
After my putting the Nabi 2 to sleep and plugging in the charger, it will fully charge and turn the battery light green as it should, shortly after that the device then powers off and requires a reboot/cold start vs. just a quick click of the power button to return from sleep mode. It does reboot fine and has a full charge - all other operations are normal.
Any suggestions on how to eliminate this power down/reboot after charging?
Thanks!
Click to expand...
Click to collapse

i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???

streetglide13 said:
i cant delete /vendor/apps always tells me (app can not be deleted) thats in es file explorer the others say its deleted but its still there???
Click to expand...
Click to collapse
In es go to the menu where you turn on root explorer and tap the words 'root explorer' then a menu will pop up, tap mount r/w and then set /system to rw. You then should be able to delete the files. After you're done deleting set system back to read-only.

[CWM/ROOT/UNKNOWN SOURCES] HD/HDplus Stock Root/other Mods - via CWM flashable zips

Update 09/10/13. This thread is being updated to reflect many new developments with the HD/HD+. Alternate ROMs are now plentiful and B&N has added Google Play Store and gapps to stock. And now the biggest change for stock is verygreen has broken the file protection scheme that B&N implemented that had made it very difficult to modify stock. The complicated methods developers had to implement to root and modify stock are now gone. So I am modifying this thread to reflect that. It still will be focused on stock and the use of CWM to modify it, but will have a few other mods to other ROMs as well.
What verygreen has developed is a new boot.img file that removes the file protection that prevented users from modifying /system. After that modified boot.img is flashed to internal memory, those /system files can be modified without danger of the device resetting. Also, one added benefit is that with the new boot.img installed on your device, any B&N update will fail. So that means once you have installed the boot.img it will stay there until the user flashes a complete new rom themselves.
The only way users can modify the /system files is to be rooted or to use zip files flashed by CWM. This thread provides zips to root using his boot.img and other zips to make other mods, like enabling Unknown Sources so apps can be sideloaded without using Play Store or the B&N Store.
Verygreen has published his boot.img zips that remove the file protection here. If you use his latest versions of recovery to flash his zip, they will ask if you want to root. It does root and it works very well. But that version of root does not include busybox or superuser which some users like.
I have updated my Universal Root zip to rev3 to include his boot.img and adds superuser and busybox. Just flash that zip with either his or my recovery and you will have root. And with this version of root, there is no danger of being reset by B&N. If you used my earlier versions of Universal Root, I recommend you use my Disable Root zip before flashing this new version.
I also have full rooted 2.1.1 stock zips in item 6 below.
WARNINGs. The CWM recovery in this thread is used to install the zips below to internal memory which are mainly to modify stock. But it can also be used to install a Cyanogenmod (CM) ROM on internal memory as described in the Dummies Guide to installing CM to internal memory here, as well as to modify CM once installed.
Be sure to use CWM to nandroid backup your existing ROM before you try to install anything here. That way if something goes wrong and your system messes up, you can boot to the CWM SD and restore your ROM exactly the way it was before you did anything.
Some of the newer HDplus devices are very difficult to get to boot to an SD. They should eventually boot but many users, including me, have had difficulty. Look at this thread (in particular, look at this post within that thread).
Click to expand...
Click to collapse
If you have questions or comments on this post, reply to this thread. If you are a new user and cannot post here, post on my HD/HD+ tips thread here. Please do not send me private messages or emails. By posting in the forums others get a chance to help you and if I answer your question in the forum, others can see my response and it may help them too.
1. Clockworkmod (CWM) Recovery - READ THIS SECTION FIRST, IT HAS EVERYTHING YOU NEED TO GET STARTED!
CWM recovery is a tool that you can use to install modifications to your stock that you ordinarily could not do without already being rooted. And it has lots of other features like making an exact backup of your stock so you can restore it later if you want. And you should do that before you ever start installing anything else. But the feature that is most useful here is the ability to install (flash) the zips I have here on this thread.
A summary of the below section for those looking for steps is as follows:
a. Make the CWM SD.
b. Copy the installation zips to the CWM SD.
c. Insert the CWM SD to the device and boot to it.
d. Use the CWM commands to backup your device and install the zips.
e. Remove the CWM SD and boot to your modified device.
a. Make the CWM SD.
Before you can install the modifications here you must make a bootable CWM SD. To make one, you will need a spare SD that you are willing to dedicate to use as a permanent CWM card, a card reader for your PC, and burning software.
EDIT (5/22/13) - There is a new procedure brought to my attention by another user (thanks fanoush) which lets you make the CWM SD without burning the image. It seems the OMAP4 devices are a little more liberal on the booting requirements than previous OMAP devices. This makes it easier to install on any size SD. Follow this new procedure as the old procedure sometimes is difficult to acheive:
New procedure:
Format (fat32) any size card with SDFormatter (free on web).
Use partitioning software (Mini-Tool Partition Wizard or EaseUS Partition Manager, both free) to set the first (and only) partition as "active". Don't repartition, just set active. I have read that some versions of Windows will let you set the first partition active without having to use partitioning software, but I only use XP and it does not have that feature.
Unarchive the appropriate set of BOOTFILES for your device (HD or HD+) from my .rar file attached below and copy them to the SD. There should be five files. Make sure you copy the MLO file first before you copy the other four. DO NOT INSERT THE SD INTO YOUR NOOK UNTIL TOLD TO DO SO IN SECTION 1c BELOW!
Move on to item b below to copy the installation zips.
Click to expand...
Click to collapse
Old procedure: Click on Show Contents.
To make a CWM card you must use a process where software copies (burns) an image file to an SD. I recommend using Win32DiskImager. Download and extract the image file for your device (HD or HD+) attached below and burn that to your SD. For detailed instructions, click on the Show Content button.
Attached at the bottom of this post you can get the CWM image zips that I have modified to work on stock. I have versions for HDplus and for the HD. You must use the version for your device, they are not interchangeable. And you must use the CWM image zips from this thread if you want them to work on stock. Download the appropriate 4GB CWM image zip for your device and extract it. You will end up with an approximate 3.7GB .img file. Burn that image to your 4GB or larger SD using Win32diskimager in Windows or use the dd command in Linux or OSX (Mac).
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first). With this 4GB image it will take a while. If you get an error message about access denied it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
When burning is complete, temporarily remove the card and re-insert again so the PC recognizes the new image.
If you do not have a 4GB or larger SD, you can use my small version of the image, also attached below. It only requires 120MB of space on the SD. And it has all the same features as it's bigger 4GB brother, it is just smaller. But there is not room to put backups on the card. If you use a small card, see item 11 below for workarounds on making backups.
You can use partitioning software, like Mini-Tool Partition Wizard or EaseUS Partition Manager (both free), to can expand the partition to the full size of the SD you burned it to. But I recommend you not use a really large SD to put CWM on. Certainly no larger that 8GB. It is a waste of a big card to use it for stock CWM.
To burn using Linux or Mac, you are on your own. A user, (jfever311) just added some Linux instructions here. And recently cdaters just added some Mac instructions here.
b. Copy the installation zips to the CWM SD.
With the card still in the PC, copy to the SD card those zips (keep them as zips) that you want to install to the Nook. I recommend the Enable Unknown Sources zip, and, if you want root, the Universal Root zip as discussed in the sections below.
c. Insert the CWM SD to the device and boot to it
Remove the card from the PC and insert into your POWERED OFF Nook and power back on. CWM should appear. If it does not and boots to stock instead, power off and try again. You can tell when it is going to boot to CWM when the 'cyanoboot' logo shows. If it still does not boot after several retries, first make sure you have the right version of the image/files to match your device (HD or HD+). Some of the newer HD+ devices a very resistant to booting to SD. My new device boots to SD maybe once in ten tries. I think it is hardware related. HD's seem to boot to SD very reliably.
d. Use the CWM commands to backup your device and install the zips.
Once CWM appears, use the volume up/down keys to move the cursor and highlight "backup and restore". Then use the n key to activate it. The power key is the back button. Pick backup and it will take several minutes to backup your system. That way if something messes up you can later restore that backup. Keep the backups for future needs, don't delete them.
Then use the power key to move back to the main screen and select "install zip from SD". Pick the zip you want from the list of zips that you put on the SD earlier and select install. Do them one at a time in any order you want. You do not have to do any wiping.
e. Remove the CWM SD and boot to your modified device.
After you finish, remove the CWM card and tell CWM to reboot. Sometimes you get a message saying that it is set to flash a new recovery and do you want to fix that? It makes no difference what answer you choose, so I just say no. It should boot to stock with your changes installed.
Most of the below zips can be flashed (installed) on any version of stock HD-HDplus ROM as long as you have booted the Nook into stock at least once and registered. All of the zips below can be installed and work without the Universal Root if you don't want to be rooted. Just copy any additional zips to the SD while it is inserted in the PC, remove from the PC, insert into the Nook again and boot to the CWM and install per the previous paragraph.
There is an alternative to downloading on your PC and copying the zip to the SD card for flashing. You can download the zip on your device and store it on internal media memory. Then, when you boot to CWM to flash it, select "install zip from SD/choose zip from internal memory" and install from there.
One additional thing. Since the device is very sensitive to the apps you install later (the device will try to reset itself if you install an app that writes to /system), it is probably a good idea to back up with CWM periodically so that if you do have to restore, you won't have to repeat a lot of the changes you made since the last backup.
If you do get into the 8 failed boot process because something got inadvertently added to /system, you can recover from the reset by turning off the device before the 8th reboot and inserting your CWM card. The next boot will boot to CWM and you can restore your last back up to get back to where you were.
Be sure to keep your CWM SD for future use.
EDIT (9/18/13) I don't like or use TWRP recovery but many users have asked for a bootable SD that uses it. So I extracted the files from verygreen's internal TWRP and made bootable SD versions for each device and added them to the list of attachments below. I have both the BOOTFILES version (which I recommend using) and a burnable 4GB image version. The image version is compressed to 7z format to make it small enough to attach to this post.
You are on your own for how to use TWRP, don't ask me, I don't use it.
2. Universal Root for Stock (rev3 - 09/10/13 )and Disable Root (rev2 - 2/3/2013)
Adding Root to stock is an important step in making your device better. It gives you access to files and locations that you are ordinarily not allowed to see or modify. Many further mods to your device depend on being rooted.
This zip will detect which device you have and will root your stock no matter what version of the software (even 2.1.1). The zip is very small and is attached to this post. I added a couple of small apps to help users. Zeam is an alternate launcher to help you see sideloaded apps and AnyCut lets you put a stock Home shortcut on the zeam screen. If you do not want these apps, just go to settings and uninstall them.
This version of root also changes how the boot sequence looks. It briefly shows the original Nook logo, followed by the Cyanoboot logo, followed by the normal stock boot up sequence. After the first boot when the stock home screen comes up, press the n key and a dialog box pops up asking which launcher you want to use. Click default and select zeam. To put a stock home shortcut on zeam, long press the zeam screen, choose shortcut, choose AnyCut, choose activity and scroll to home and select it Then press OK. There will now be a shortcut installed to get back to the stock home screen. An alternative way to switch back and forth between stock home and zeam is described by natefish here.
I also added another zip to disable root if you already rooted your device. It is only to be used if you rooted using rev2 or older of the Universal Root. It will leave all the other things installed by the zips below, just root will be gone. And you can always add root later again if you want by flashing the Universal Root zip. It will not work on rev3. If you want to remove the rev3 root, just go to item 6 below and flash one of my plain stock ROMs. It will take everything back to plain stock including removing the Cyanoboot loader and the root files (and CWM or TWRP if you installed them to internal memory). This is handy if you need to return it to B&N under warranty. But it will leave the Unknown Sources setting enabled if you had flashed that zip.
If you prefer not to be rooted, all of the other below zips can be installed and work without having root.
If you have a previous version of root and get updated by B&N despite setting OTA to manual per item 7 below, just flash this root zip again and your root should be back. Breaking root will not effect your installed apps unless those apps specifically required root. One of the side benefits of the rev3 root is it causes any B&N update to fail, so the root sticks.
3. Enabling Unknown Sources - (rev0 - 09/08/2013) (formerly the Extras zip)
I have a new stand alone Enable Unknown Sources zip and attached it below. It replaces the former Extras zip that is now obsolete. This zip changes a hidden setting in stock to allow apps to be installed from other sources besides the Nook Store or Play Store. You will need to have booted and set up stock before flashing this zip. But you do not need to be rooted.
And I now have a version of the old Extras zip (which included enabling Unknown Sources) for 'Stock installed on SD' by verygreen. Get it here (WARNING! This version of the extras zip is only for users running stock installed on an SD, NOT for users running original stock installed on internal memory. Do not install it on stock on internal, it will do nothing.)
4. Swapping "sdcard" and "ext_sdcard"
Many users have complained that on the HD/HD+, like many phones, the internal media is named "sdcard" so that apps can store their files there. Some users would like them stored on their external SD. This mod will swap "sdcard" and "ext_sdcard" so that apps will store their files on the external SD. The external SD will show as "sdcard" and the internal media will show as "ext_sdcard". And it shows swapped using MTP also. It can be a little confusing since we cannot control the names, but they are swapped. If you don't have an external SD in the slot, both sdcard and ext_sdcard will display the internal media.
I have two zips attached below, one to install the swap feature and one to remove the feature. Just flash the one you want and on the next boot it will become effective. These are for stock only.
I also now have a version for the official CM10.1/CM10.2 on emmc for the HD+ and HD.
WARNINGs This swap is kind of a kludge, so some things are troublesome. For these swap zips to work, your SD must be formatted to fat32. And the settings, storage option in CM does not provide accurate information. In fact, it may hang your device if you try to view it. If it hangs, just reboot. Also another issue is you cannot install apk files from the new sdcard. You must move the apk to internal media memory before installing.
5. New CWM (v6036) for internal memory (emmc) and Restoring stock recovery to emmc (HD/HD+)
Now that verygreen has made available his native CM10.1 ROM and has matching native CWM and TWRP recoveries that can be put on internal memory (emmc), I have made three more zips. The first two are my versions of a repackaged verygreen CWM (v6036) for internal memory for HD (here or here) and HD+ (here or here) that work on both stock and internally installed CM. If you are already on the newer CWM for CM11 (v6045 or newer) that cannot flash older zips and you want to go back so you can, I have modified this zip (rev2) to be flashable with the newer CWM. That way you can go back to v6036 to be able to flash older zips.
The third is a zip to return the stock recovery to internal memory should users want to return their devices to pure stock. A nandroid restore of an earlier stock backup will restore everything except the stock recovery. So if you have installed verygreen's or my recovery to emmc and you want to go back to pure stock, flash my HD+ zip here or here and my HD zip here or here. Both are also attached below.
6. Plain Stock HD/HDplus 2.1.0/2.1.1/2.2.0/2.2.1, Full 2.1.1 Stock with Root (latest 03/05/15)
Warning! All of the zips in this section must be flashed with CWM v6036 or earlier. v6045 or later will cause the installation to abort with assert errors.
I have plain unrooted factory 2.1.0, 2.1.1 and 2.2.0 zips for each device. They will take you back to stock with no root (and with file protection) so you can let B&N update you to the latest ROM version if you want. They also restore the recovery to stock in case you had previously installed CWM or TWRP to internal memory. The plain stock 2.1.0 for HD is here or here, and the HD+ here or here. Plain stock 2.1.1 for HD here or here and HD+ here or here. The plain stock 2.2.0 for HD is here or here and the plain stock 2.2.0 for HD+ is here or here. The plain stock 2.2.1 for HD is here or here and the plain stock 2.2.1 for the HD+ is here and here. If you are flashing these so you can return a device to B&N, be sure to also factory reset/wipe data with recovery (CWM or TWRP). Also an added warning if you are using TWRP and flashing these plain stock zips. After flashing and telling it to reboot, it detects that the plain stock is not rooted and asks if you want to install SuperSU. Tell it to not install as that will cause the plain stock to reset itself.
I also have full stock 2.1.1 rooted ROM zips. They can be flashed with the CWM above and have the verygreen boot.img that removes the /system file protection. They also are rooted and have superuser and busybox. Get the HD version of the rooted stock here or here and the HD+ version here or here. They can be flashed over whatever version you have. You can do it without any wiping so your installed apps and settings will remain intact. This version does not include Enable Unknown Sources, but if you had previously flashed the new Enable Unknown Sources zip, that is a setting and should stick and not need flashing again. The ROM zips will replace your entire /system so any other zips you flashed here like Extras or swaps will be gone. After flashing this ROM, you will need to reflash any mods you want from this thread (except the new Enable Unknown Sources if you had flashed it earlier).
These zips are quite large (over 400MB) so expect long downloads.
7. New OTA (Over the Air) update block
Another user (thanks greenya!) has come up with a new method to block OTA updates from B&N that seems to work. I have tested it with AdAway. I tried to manually update my 2.0.5 system in settings. It says there is an update available but does nothing when I push download. I removed the block and hit download and it began downloading immediately. So it does block them.
If you are rooted, you can do this yourself with AdAway. I have a description in my HD/HD+ Tips thread linked in my signature, here. See item 4.
Another possible block would be to put CWM or TWRP on internal memory per item 5 above. I don't think updates will install without stock recovery installed. They usually fail with CWM or TWRP.
Edit: I just did some testing and if the new boot.img has been installed, the B&N updates fail and abort. See my post here.
8. The Importance of doing Backups
Some users have not made backups because they have installed CWM to a relatively small SD. You need to have backups with these devices because they can and will reset themselves, especially if rooted.
Save your CWM card and the backups because you WILL need them again. I recommend you make a backup of the device before any modifications and another when you think you have it the way you want it. Keep both backups because you may someday need to get back to pure stock so you can update. Some of my mods interfere with updates.
Also, being rooted adds the danger of being reset by some app that modifies /system. So, if you are rooted and you want to install a new app that requires root, make a backup of your device just before installing the app in case it causes a reset.
To restore, go to the backup and restore menu and select restore. That will restore the whole device if you are recovering from a system reset. Or can go to the advanced restore menu to just restore /system if you caught the reset before it completed. There are other times you might want to just restore /data, like just after a clean device update.
9. Modifications to verygreen's New SD Scheme
With bokbokan's help, I modified bokbokan's Cyanoboot to work on verygreen's New SD so the menu works. It is now easy to boot back and forth between stock and CM10.1 with verygreen's New SD Scheme. Just flash the NookHDplus-verygreen-New-SD-add-bokbokan-Cyanoboot zip attached below.
The second zip allows stock to see his emulated media SD partition as ext_sdcard in stock. Just flash the NookHDplus-verygreen-New-SD-fix-stock-to-use-New-SD-Media zip attached below.
Both zips can only be flashed with verygreen's New SD CWM (early 7.1).
10. Recovery Bootloops - (Device boots only to CWM or TWRP recovery)
Occasionally the /rom partition (p5) will get corrupted. That partition contains vital information necessary to operate your device. When that happens it tries to boot to stock recovery so that it can repair itself. But since many users have replaced stock recovery with CWM or TWRP, it boots to one of them and does nothing. Rebooting again does the same thing. So you end up in a recovery bootloop. And restoring your original stock backup does not help since it does not restore the stock recovery nor repair the /rom partition.
To fix it you need to restore the stock recovery by either flashing one of my stock recovery zips attached below or flash a whole plain stock zip from item 6. Then when it reboots, it can repair itself.
Obsolete zips have been moved to the next post.
Current attachments:
XDA:DevDB Information
[CWM/ROOT/UNKNOWN SOURCES] HD/HDplus Stock Root/other Mods - via CWM flashable zips, ROM for the Barnes & Noble Nook HD, HD
Contributors
leapinlar
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-10-11
Last Updated 2015-03-05

Change Log
Change Log
03/05/15 - added plain stock 2.2.1 zips for both devices to item 6
12/23/13 - added plain stock 2.2.0 zips for both devices to item 6
11/12/13 - added item 10 Recovery Bootloops
09/22/13 - updated internal CWM to v6036
09/15/13 - added bootable SD versions of TWRP recovery for emmc for each device
09/10/13 - reworked entire post for new Universal Root rev3 and full rooted 2.1.1 stock ROMs.
09/08/13 - Created stand alone enable Unknown Sources for stock and added reference to verygreen's new boot file zip
09/04/13 - updated Swap SD for CM10.1/CM10.2 on emmc to rev6 to fix assert error on HD
08/22/13 - updated Swap SD to apply to the official HD/HD+ CM10.1/CM10.2 on emmc
07/29/13 - fixed broken HD/HD+ CM10.1 emmc swap SD zip (rev4 now works properly on HD)
07/21/13 - added HD version of Restore Stock Recovery zip to item 5
06/29/13 - added link to Extras for stock on SD, item 3
06/16/13 - fixed another typo in SD Swap zip to rev2
06/16/13 - revised SD Swap zip for verygreen's emmc CM10.1 to rev1 to fix an issue where the userinit.d folder was not created.
06/15/13 - added SD Swap zip for verygreen's emmc CM10.1
06/06/13 - added two zips to help with verygreen's New SD scheme (item 9)
05/24/13 - added zip to install my custom CWM (v6028) to internal memory to item 5
05/24/13 - rearranged and renumbered sections to move obsolete items to bottom and added warning about newer HDplus booting from SD
05/22/13 - added alternate procedure for making bootable CWM SDs
05/16/13 - removed item 5, Voice Search and added new item 5, Restore Stock Recovery
05/15/13 - updated HD+ CWM images to rev4, which adds recovery partition backup (v6028)
05/06/13 - modified Extras zip to remove old OTA block (which no longer worked) and add GPS permissions to improve Play Store compatiblity
05/03/13 - added full plain unrooted ROM version 2.1.0 for both devices to section 9 (now 6) and edited other sections accordingly
03/29/13 - added Section 11 (now 8), The Importance of doing Backups, and updated OTA to rev2
03/25/13 - added rev1 of location services to add gps permissions to allow more apps to show as compatible in Play Store
03/17/13 - even further editing to make it look less intimidating
03/04/13 - general editing of text to improve readability
02/24/13 - minor change to new OTA block (rev1)
02/23/13 - added new OTA block method and zips
02/18/13 - added revised HD+ stock CWM compatible with new HD+ Hybrid CM SD
02/04/13 - added modified Update to 2.06 zips for all ROM versions. Numbered sections and put dates on revisions and files
02/03/13 - revised CWM images - HD+ with larger fonts and HD made compatible with the new HD Hybrid CM SD.
02/02/13 - added rev2 of Universal Root, Disable Root, Extras and Gapps + Extras
01/31/13 - added white-on-white repair for version 2.0.6 and plain stock 2.0.0 zips so your system can update to the latest stock version
01/12/13 - added rev1 of Gapps + Extras to correct minor issues and to add zeam and AnyCut for those not wanting to root
01/10/13 - added Location Services
01/06/13 - added SDSwap
01/05/13 - added HD versions of 2.0.0 rooted ROM and white-on-white repair zips
01/04/13 - restored HD+ 2.0.0 rooted ROM link
01/03/13 - added warnings about Voice Search and about the danger of being rooted on these devices, added disable root zip and rev1 of Universal Root
01/02/13 - added small CWM image files and instructions
01/01/13 - added tip about doing periodic backups, interrupting 8 failed boot reset, added Voice Search and updated the HD CWM image to rev2
12/31/12 - re-arranged post and reworked instructions
12/30/12 - temporarily disabled HD+ 2.0.0 rooted ROM link
12/27/12 - added HD CWM and re-labeled zips that work on HD
12/25/12 - added Universal Root and other zips.
12/23/12 - original post for HD+ CWM and HD+ 2.0.0 rooted stock ROM
Obsolete Zips
If you want to see these items, click on Show Content below
a. Gapps/Play Store + Extras (rev2 - 2/3/2013) - No longer necessary for version 2.1.0.
This zip adds Play Store and a few other extras. This is the zip that most will want to install since it gives you a lot of flexibility to install new apps. And if you install it without the Universal Root there is no danger of getting reset.
You can download my NookHD-HDplus-Gapps+Extras-for-stock-rev2.zip here. Rev1 included a few minor fixes and added zeam and AnyCut. Rev 2 adds Terminal Emulator, Root Browser and Userinit. It is approximately 24MB. It can be flashed as long as you have booted and set up (registered) the Nook first. After you install the zip, remove the SD and reboot. You will see "Updating Apps" during boot. That is the system setting up the gapps. Then you should see Play Store in the zeam launcher and you can open it and register with Google. Warning! This version of the gapps zip is for stock only. Do not try to install this version to CM10 on SD.
If you did not install the Universal Root and set up zeam as described in the Universal Root section, you need to do it now.
Many users complain that Play Store lists many common apps as incompatible with your device. Just because Play Store says it is incompatible does not mean it will not run on your device. It just means Play Store will not let you install it. The solution is to find and install the app from somewhere else like the Amazon Store, the 1Mobile Store or from another device. I have found most apps that Play Store says is incompatible actually do work.
b. White-on-White repair for HD/HDplus (latest - 1/31/2013) - No longer necessary for version 2.1.0.
This mod changes some text colors so that most third party apps no longer display white text on a white background. The choice of the text colors was a compromise since the same text colors are used on white backgrounds and grey backgrounds. If too dark they will not show on grey and if too light they will not show on white. Thanks to someone0 for help in selecting the colors and making this mod.
Some people do not like the effect of this mod, so be sure you have made a backup of your system as I recommended earlier before you install this mod so you can easily revert back to stock colors.
Also be sure to install the correct version for your device and software version. If you install the wrong version for your device, it will either not install or get stuck at 99% when it boots. If it does not install or gets stuck, just install the correct version or restore your backup.
You can get the version for HDplus 2.0.0 here and HDplus 2.0.2/2.0.4/2.0.5 here. And the version for HD 2.0.0 here and HD 2.0.2/2.0.4/2.0.5 here. I just added versions for 2.0.6 for both devices. HDplus here and HD here. Since this mod interferes with future updates, I have included two zips to take them back to the 2.0.6 stock settings so that it can update without failing. Get the rev1 of revert to stock settings for HDplus here and HD here.

Leapinlar, shouldn't this thread be in the Nook Hd+ forum?

Yes, I will see if I can get it moved. Thank you for catching that.

Thx so much. I will try it.

Moved.

Wow, thank you very much for this. Flashable CWM? Another road to custom ROMs. Thank you.
Once I get my new setup, I'll see if I can get back on Android development. I've only worked on the Samsung Galaxy 5/Europa for Android development before.
Sorry for the bother, please may I ask; after installing the ROM, will it keep the 8-bootup-failure-reset intact? I know it sounds like a stupid question, haha but I'm curious; since it is overwriting the default ROM. Thank you.

TYVM, I was told I was going to get on HD+ for Christmas and wanted to use it stock for ebooks (I have a BN account and a dieing nook 3G with bought books I want to keep) but the new 2.0.5 update would leave me to choose no tablet stuff (until CM10/cyanoboot gets up) or no BN access.
Does this have the White on White Text fix in or will I need to do that myself?

I don't think he did.

The Old One said:
TYVM, I was told I was going to get on HD+ for Christmas and wanted to use it stock for ebooks (I have a BN account and a dieing nook 3G with bought books I want to keep) but the new 2.0.5 update would leave me to choose no tablet stuff (until CM10/cyanoboot gets up) or no BN access.
Does this have the White on White Text fix in or will I need to do that myself?
Click to expand...
Click to collapse
I'm working on it. Soon. Ok, see OP for links, one for 2.0.0 and one for 2.0.2/2.0.4.
Sent from my HD+ rooted stock using Tapatalk

I believe there is a fault with my dad's HD+, would it be possible to get any version of the stock ROM back? Sorry for the bother.
The pre-rooted ROM (modified 2.0.0 in this thread) loads up sideways, and freezes at 99% upon second boot.

Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?

dbh369 said:
Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?
Click to expand...
Click to collapse
That's exactly what I'm thinking. I can't seem to register, that could be my device fault though. I'm going to test with version 2.0.5, and see if I can register. I'll edit with the result.
EDIT: I can't seem to register with version 2.0.5 either, must be a tablet fault. I'll have to get it replaced. So, I'm assuming you can register the modified ROM in this htread, since leapinlar did state it can be activated right?

dbh369 said:
Just checking, you will have the ability to use your B&N account with this, right? You aren't skipping OOBE and becoming "test", right?
Click to expand...
Click to collapse
Right, go ahead and register. It is just like when it came out of the box, except it is rooted. But you can skip it if you want.
Sent from my HD+ rooted stock using Tapatalk

HiddenG said:
I believe there is a fault with my dad's HD+, would it be possible to get any version of the stock ROM back? Sorry for the bother.
The pre-rooted ROM (modified 2.0.0 in this thread) loads up sideways, and freezes at 99% upon second boot.
Click to expand...
Click to collapse
How did you flash it? And what files did you use? Did you wipe /data first? It will freeze at 99% if you flashed the wrong white-on-white file.
Sent from my HD+ rooted stock using Tapatalk

leapinlar said:
How did you flash it? And what files did you use? Did you wipe /data first? It will freeze at 99% if you flashed the wrong white-on-white file.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
Thank you for your response.
I'm using CWM on a SanDisk 4GB Class 4 SD Card, I went into "Mounts and storage" > format /data > Yes. Then, "install zip from SD" and selected "NookHD+factory-2.0.0-rooted.zip". After that I waited, rebooted the device, took the SD card out before reboot, and it all worked fine. I'm currently having problems with registration, probably a device fault, therefore I rebooted to solve the issue, then the loading loaded sideways (i.e. landscape mode) even when the tablet is held straight. It also gets stuck/freezes at 99%. I have not installed GAPPS yet, or even downloaded/installed the white-on-white file yet. This problem only occurs on a second reboot, and if you reboot it again after the second time, the same problem occurs.
To get out of the problem, I flashed the ROM again. Now I'm back to stock ROM after 8 failed boots.
Thank you for your response once again. I hope I'm the only one with this problem, and no one else, haha.

HiddenG said:
Thank you for your response.
I'm using CWM on a SanDisk 4GB Class 4 SD Card, I went into "Mounts and storage" > format /data > Yes. Then, "install zip from SD" and selected "NookHD+factory-2.0.0-rooted.zip". After that I waited, rebooted the device, took the SD card out before reboot, and it all worked fine. I'm currently having problems with registration, probably a device fault, therefore I rebooted to solve the issue, then the loading loaded sideways (i.e. landscape mode) even when the tablet is held straight. It also gets stuck/freezes at 99%. I have not installed GAPPS yet, or even downloaded/installed the white-on-white file yet. This problem only occurs on a second reboot, and if you reboot it again after the second time, the same problem occurs.
To get out of the problem, I flashed the ROM again. Now I'm back to stock ROM after 8 failed boots.
Thank you for your response once again. I hope I'm the only one with this problem, and no one else, haha.
Click to expand...
Click to collapse
When you rebooted again after interupting registration, you probably messed up /data again. You probably should have wiped it again and reflashed. You could have a problem with registration if you have a corrupt /rom partition. Stock will automatically repair that if it can. But one of the things I did to help prevent automatic updates was to interfer with that process. Were you able to register once you did the 8 failed boot reset?
Sent from my HD+ rooted stock using Tapatalk

I'm an experienced flasher of many Android devices and I have followed all of the instructions in this thread.
I have:
-- in CWM wiped /data /system
-- then also did the 8 time failed boot to restore stock
... and this ROM will *not* register. After typing in a valid user name and password, registration fails with a "contact customer support".
Ideas guys?

scoopman said:
I'm an experienced flasher of many Android devices and I have followed all of the instructions in this thread.
I have:
-- in CWM wiped /data /system
-- then also did the 8 time failed boot to restore stock
... and this ROM will *not* register. After typing in a valid user name and password, registration fails with a "contact customer support".
Ideas guys?
Click to expand...
Click to collapse
Was that a brand new registration or just reusing the same screenname/ password you used before? I had not problem resigning in with the same credentials as before. I wonder if there was something in my factory zip that identified that rom for my device? I will follow up that with my second device.
EDIT: I was able to flash and B&N register my second device which is on a completely different account. And I could see nothing in my zip that identified anything other than saying it was a US device. It did take what I considered a long time to respond to putting in my credentials. It churned for a while, but eventually responded.
Sent from my HD+ rooted stock using Tapatalk

leapinlar said:
Was that a brand new registration or just reusing the same screenname/ password you used before? I had not problem resigning in with the same credentials as before. I wonder if there was something in my factory zip that identified that rom for my device? I will follow up that with my second device.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
Interesting you ask as I've now tried both using an account that was on 2.05 as well as formatting stuff again, reflashing, then trying a new account.
BOTH fail with the same message.
I'm hypothesizing that there could be something on their server that's identifying your ROM as something that should be rejected...

[SC-02C] Any Rom Patcher by Simmo [Updated : 2013/06/16]

Simmo's SC-02C Any Rom Patcher
with special thanks to wjchen0 for the ntt gps kernel module
Tested and working with ICS and JB 4.1.x
JB 4.2 works, but requires a Siyah based kernel or a kernel designed specificially for the SC-02C, such as KBC.
Please press the Thanks button if it works for you.
Code:
Modem: SC02C-OMLPL
Apps: ClockworkMod SuperUser
Busybox
Tweaks: Set NTP server (jp.pool.ntp.org)
Free tethering (tether_dun_required=0)
NTT GPS & compass fix
Facebook ContactsProvider database patch (is_restricted=0)
Black camera viewfinder fix for the Docomo rom
CyanogenMod APN xml (with spmode)
Samsung JellyBean fonts (incl. Japanese)
SP-Mode Mail with Push & Docomo Account Authenticator
Docomo emoji library
How to get a working JellyBean rom.
Root your phone and install a custom kernel. Reboot into CWM.
Download a custom rom. I recommend WanamLite or NeatRom.
Download my tweaker.
Install the rom first, then my tweaker.
Reboot, then you're done.
Note : You must install the tweaker every time you do a full wipe.
If you are running Jelly Bean then you can install CommuniCase by Docomo, instead of using SP-Mode Mail.
Changes:
2013/06/16
Updated the DcomoAccountAuthenticator to work with Docomo CommuniCase.
Added support for Docomo emojis in keyboard that use it.
Reverted to the OMLPL modem, as I found it works better.
2013/02/04
Updated the system modules and modem from the latest OMMP4 rom.
2013/01/28
The gps module has a bug that cuases the system to hang at the docomo logo.
You must install this new update to stop it happening.
If you already have the "stuck at docomo logo" problem, download the new tweaker and install on top. It deletes the corrupted file.

reserved

reserved

reserved

reserved

SimmoF said:
reserved
Click to expand...
Click to collapse
which update file you mean?
I　ｄｏｗｎｌｏａｄ　ｔｈｅ　ｌａｔｅｓｔ　ｔｗｅａｋ　ｆｏｒ　ａｎｙ　ｒｏｍ
ａｎｄ　ｓｔｉｌｌ　ｓｔｕｃｋ　ａｔ　ｄｏｃｏｍｏ　ｌｏｇ／．．．．
---------- Post added at 01:33 PM ---------- Previous post was at 01:16 PM ----------
ａｎｄ　ｉ　ｃａｎ　ｎｏｔ　ｆｉｎｄ　ｔｈｅ　ｆｉｌｅ　ｔｏ　ｄｅｌｅｔｅ．．．

wendac said:
which update file you mean?
I　ｄｏｗｎｌｏａｄ　ｔｈｅ　ｌａｔｅｓｔ　ｔｗｅａｋ　ｆｏｒ　ａｎｙ　ｒｏｍ
ａｎｄ　ｓｔｉｌｌ　ｓｔｕｃｋ　ａｔ　ｄｏｃｏｍｏ　ｌｏｇ／．．．．
---------- Post added at 01:33 PM ---------- Previous post was at 01:16 PM ----------
ａｎｄ　ｉ　ｃａｎ　ｎｏｔ　ｆｉｎｄ　ｔｈｅ　ｆｉｌｅ　ｔｏ　ｄｅｌｅｔｅ．．．
Click to expand...
Click to collapse
I just updated again.
You can download "Simmo's SC-02C Any-Rom Tweaker 20130128b.zip"
Install this and it deletes the file for you.
Please post if it fixes it.

SimmoF said:
I just updated again.
You can download "Simmo's SC-02C Any-Rom Tweaker 20130128b.zip"
Install this and it deletes the file for you.
Please post if it fixes it.
Click to expand...
Click to collapse
it does not work for me.....

wendac said:
it does not work for me.....
Click to expand...
Click to collapse
please mount /data first in the mounts and storage menu in philz recovery menu

Works great
Great tweak. Working for me so far and I had a few issues myself. I will say that in order to get the ROM (I'm using Wanamlite 14.0 and the 23 Toggles) and the tweaker working properly I did have to do a full wipe.
I will just recommend that anyone who wants this to work BACKUP - BACKUP - BACKUP.
I also used Titanium Backup (correctly - Thanks Simmo :silly: ) to backup all user apps. Don't worry about the system apps - the ROM takes care of them.
My order of installation -
1 - BACKUP your current ROM - again - BACKUP your current ROM
2 - Use Titanium Backup (use this guide) to back up your user apps so you can get them back afterwards. When using Titanium Backup for the first time on a new ROM, you may get the message about using the phone's original ID, ignore it, let it use the new one.
3 - Follow SimmoF's instructions in the first post
4 - Reboot and enjoy.
Thanks again to SimmoF - buy him a beer.

rushter said:
Great tweak. Working for me so far and I had a few issues myself. I will say that in order to get the ROM (I'm using Wanamlite 14.0 and the 23 Toggles) and the tweaker working properly I did have to do a full wipe.
I will just recommend that anyone who wants this to work BACKUP - BACKUP - BACKUP.
I also used Titanium Backup (correctly - Thanks Simmo :silly: ) to backup all user apps. Don't worry about the system apps - the ROM takes care of them.
My order of installation -
1 - BACKUP your current ROM - again - BACKUP your current ROM
2 - Use Titanium Backup (use this guide) to back up your user apps so you can get them back afterwards. When using Titanium Backup for the first time on a new ROM, you may get the message about using the phone's original ID, ignore it, let it use the new one.
3 - Follow SimmoF's instructions in the first post
4 - Reboot and enjoy.
Thanks again to SimmoF - buy him a beer.
Click to expand...
Click to collapse
i fully wipe and follow simmon's way to install the rom
it is ok
but after i restore my app by titanium back up
it stuck at the docomo logo again...

wendac said:
i fully wipe and follow simmon's way to install the rom
it is ok
but after i restore my app by titanium back up
it stuck at the docomo logo again...
Click to expand...
Click to collapse
Then it obviously appears that it is not the ROM or the tweaker causing the problem. Please be sure that you have the right Tweaker B version and boot into recovery and run it through again.
If not, I would say try again but after the ROM installs let it reboot before installing everything else. Run through the google setup stuff, don't do the samsung stuff, skip it.
Then go in and only restore user apps. I always thought I knew Titanium Backup well, but, as Simmo pointed out to me, I was wrong. Go ahead and JUST RESTORE YOUR USER APPS - NO SYSTEM APPS OR DATA. You may also have to go in and set your apn to the spmode.ne.jp .
This is what worked for me. After you have done that and just the ROM and your restoration works, test with a few reboots. Then go and get the tweaker file again. Just to be safe.
I know that, myself, if I let everything settle and check for running operation, then install the 23 toggles, tweaks and sp push files, it works.
If you get stuck at the boot logo AND you have downloaded the Tweaker B version of the file before wiping again - try to boot into recovery and just run the tweaker file as suggested.
DON'T GIVE UP!!!
It's a very smooth ROM. So far...

Re: [SC-02C] Any Rom Patcher by Simmo [Updated : 2013/01/28]
Finally set up everything.
Trick is not to use titanium back up to restore data.
Btw how can I use other kernel ?
And any suggestion for battery
Now on wanamlite Rom with simmon tweak.
Sent from my GT-I9100 using Tapatalk 2

Thanks Simmo's
I have tried the two Roms; and this issues have been persist
- The SD card can't read.
- Can't read the memoir or the SD card via the computer
- Can't instal any APK.

Re: [SC-02C] Any Rom Patcher by Simmo [Updated : 2013/01/28]
[email protected] said:
Thanks Simmo's
I have tried the two Roms; and this issues have been persist
- The SD card can't read.
- Can't read the memoir or the SD card via the computer
- Can't instal any APK.
Click to expand...
Click to collapse
Run a disk checker.
If on windows. Mount as USB device.
Open a command window on the PX.
Run the command "chkdsk driveletter: /f"
That should fix it. If it says partition type is RAW, then something strange happened and it needs to be formatted.
If your internal /data partition is damaged, you need to do something different. Tell me a If that fixes your problem.
Sent from my GT-I9100 using Tapatalk 2

SimmoF said:
Run a disk checker.
If on windows. Mount as USB device.
Open a command window on the PX.
Run the command "chkdsk driveletter: /f"
That should fix it. If it says partition type is RAW, then something strange happened and it needs to be formatted.
If your internal /data partition is damaged, you need to do something different. Tell me a If that fixes your problem.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
- The SD can't read via the device, but with computer it's work
- The internal memoir appear just with 2 gb
- When i try to instal any APK from internet (ex Google play) it doesn't work.

rushter said:
Then it obviously appears that it is not the ROM or the tweaker causing the problem. Please be sure that you have the right Tweaker B version and boot into recovery and run it through again.
If not, I would say try again but after the ROM installs let it reboot before installing everything else. Run through the google setup stuff, don't do the samsung stuff, skip it.
Then go in and only restore user apps. I always thought I knew Titanium Backup well, but, as Simmo pointed out to me, I was wrong. Go ahead and JUST RESTORE YOUR USER APPS - NO SYSTEM APPS OR DATA. You may also have to go in and set your apn to the spmode.ne.jp .
This is what worked for me. After you have done that and just the ROM and your restoration works, test with a few reboots. Then go and get the tweaker file again. Just to be safe.
I know that, myself, if I let everything settle and check for running operation, then install the 23 toggles, tweaks and sp push files, it works.
If you get stuck at the boot logo AND you have downloaded the Tweaker B version of the file before wiping again - try to boot into recovery and just run the tweaker file as suggested.
DON'T GIVE UP!!!
It's a very smooth ROM. So far...
Click to expand...
Click to collapse
how is your battery consumption\ for wanamlite?
I know this rom is great but the battery really decrease too fast. Even I close the mobile data and wifi. It drops around 5% per hr. compared to cm9, it is far too high

XXLS8 has issues. the XXLSJ leak is much better actually.
I recommend going back to the leak or going to cm10.1
I am playing around with cm10.1 at the moment.
XXLS8 sucks.

Re: [SC-02C] Any Rom Patcher by Simmo [Updated : 2013/02/04]
I've been trying to download your tweaker on and off now for about two weeks. Tried different combinations with different browsers to no avail.
Every time I click on the file, it just opens up and shows the files in the zip. Its pretty to look at but .....
Can you not just upload to xda???
(Direct download)
Sent from my GT-I9100 using xda premium

Can't download zip from Google Drive on phone
E43JAP said:
I've been trying to download your tweaker on and off now for about two weeks. Tried different combinations with different browsers to no avail.
Every time I click on the file, it just opens up and shows the files in the zip. Its pretty to look at but .....
Can you not just upload to xda???
(Direct download)
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I had the same problem. It's not the zip file that is a problem - it's google drive
First, I am assuming that you are doing this from the phone itself.
I used Firefox and this is what you need to do -
1-Click the link to download the file and once you are in the directory where you see the zip click on it.
2-It will open and show you the contents of the zip - don't worry
3-Click the menu key on your phone and one of the choices listed will be show as desktop or something like that - click it
4-Let page reload
5-Now at the top of where the zip file is shown, you will see some menu choices - File Edit, etc.......
6-Click File and I think the bottom choice is download. Click that and it should download the zip file.
It will give it a random name but you should be able to get things figured out from here.
Please thank me below and make sure you get simon (or Me - haha) a beer.

need help - how to copy TWRP nandroid backup to device?

how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.

Latest TWRP has MTP mode.

but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB

You'll need to give us more information.
Why did it fail? Why did your phone stop booting?

1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop

gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.

how can you copy using twrp while in recovery? are you able to access your PC from recovery?

gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.

ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??

Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty

No. Do a full flash of userdata.img

Please explain
What would I achieve by flashing it?

gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.

Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working

gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.

I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5

gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup

How get emojies back after Twrp/rooting?

No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3

bythelaw said:
No matter what TWRP version I use as my recovery, OOS loses all the emojis. I want to stay stock and rooted. I achieved root via magisk, but the OS is impossible to use without graphical symbols with square boxes instead of them. Please help me. I'm on oos 10.3.3
Click to expand...
Click to collapse
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:

Mr.FREE_Bird said:
So what's basically happening is that you somehow like many others don't have the Reserve partition which includes Emojis, Fonts and some OnePlus Apps.
There are a couple of things that you can try to fix it.
You can try to install OOS through local upgrade without wiping anything. This may work or not. From my experience it never worked but for some it did so it's worth to give a try.
If the first method doesn't work you can give this Magisk module a try, it contains everything that's included in the Reserve partition. Just install it via Magisk and reboot.
https://androidfilehost.com/?fid=1899786940962618515
For both methods you may need to wipe the app data and cache of your keyboard app for the emoji's to reappear.
If both methods don't work for you, you probably need to do a complete reinstall of OOS. You could try to clean flash OOS via TWRP or restore your device with the MSM Download Tool.
Good luck! :good:
Click to expand...
Click to collapse
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?

bythelaw said:
I tried the first method, didn't work. I'll try the second method and reply here.
After installing "Reserve_V1" via magisk, do I have to data-reset via twrp? Wipe internal storage? Or anything else?
Or
Just reboot after flashing the zip, and hopefully emojies are back?
Click to expand...
Click to collapse
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.

Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Awesome, thank you so much. I'll try it and reply

Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
It seems I didn't pay attention before, but now I see that after twrp and root, my internal storage is not working properly. No apps are installing, can't download anything either.

Mr.FREE_Bird said:
Doesn't surprise me, never worked for me too...
No wipes needed, just install the Magisk module via Magisk and reboot. You may need to wipe the app data and cache of the keyboard app you are using like I mentioned but that's it.
Click to expand...
Click to collapse
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.

Im planning to root my op6, how do i not mess up the reserve partition??

bythelaw said:
Reserve magisk worked wonderfully.
Thank you so much. Hopefully others can find this thread as well and root.
Click to expand...
Click to collapse
Great to hear, glad that the Magisk module I shared was helpful. :good:
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
Antieco said:
Im planning to root my op6, how do i not mess up the reserve partition??
Click to expand...
Click to collapse
I'm actually not quite sure what causes the reserve partition to go missing. But from my own experience it seems that wiping the /data partition after a clean install of OOS with he MSM Download Tool causes this to happen. But I am not 100% sure this is correct.

The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps

Mr.Hunk said:
The Reserve zip file worked very well. Thanks to the zip creator and guy refering to the zip file.
Now with everything fixed I wanted to use the font changer magisk module which I couldn't due to the above module blocking/overwriting it.
Reserve file containing all the fonts and emojis in system/fonts folder. Surprisingly almost all the files were already present in the phones system folder but containing 0kb data, which was the problem.
Extracted the Reserve zip file, copied files from system/fonts and replaced them in the phones system/fonts folder via file manager. Rebooted and everything was working. Now all the fonts and emojis are working as well as I'm able to change fonts using font changer module. Hope this helps
Click to expand...
Click to collapse
Absolutely not a problem! Glad it was somewhat helpful.
Great solution and tip for others who might run into the same issue. I'm sure that will be helpful for others who might run into this thread. :good: