I rooted my HTC EVO, then wanted a new kernel for better battery, wanted the new gingerbread ROM too but after I rooted, I deleted a few unwanted, stock apps. After I did this, I started to get a lot of force close messages. Certain apps won't even open. So I tried to unzip a new kernel and I wiped all my data from the hboot. Now it starts up, will go to locked home screen. I try to unlock it, it's the white htc screen then loads into the set up (i.e. keyboard usage, etc) and in the last step a force close message pops up then goes through the whole scenario again. Now I want to just put a whole new system on so I can have my evo back. HELP?
emiliah310 said:
I rooted my HTC EVO, then wanted a new kernel for better battery, wanted the new gingerbread ROM too but after I rooted, I deleted a few unwanted, stock apps. After I did this, I started to get a lot of force close messages. Certain apps won't even open. So I tried to unzip a new kernel and I wiped all my data from the hboot. Now it starts up, will go to locked home screen. I try to unlock it, it's the white htc screen then loads into the set up (i.e. keyboard usage, etc) and in the last step a force close message pops up then goes through the whole scenario again. Now I want to just put a whole new system on so I can have my evo back. HELP?
Click to expand...
Click to collapse
Download the rom, kernel, and Gapps (http://www.goo-inside.me/gapps/latest/7/) on your computer. Boot into recovery. I don't use Clockwork, and I'm assuming you rooted with Unrevoked, so that's probably the recovery you have, but try to find the option to mount your SD card via USB, and move the files to your SD card. Do not unzip them. They must be .zip files. Unmount your SD card, wipe your data, wipe your cache, wipe your Dalvik cache, repeat all the wipes at least one more time, then flash the .zips in this order: 1. ROM 2. Gapps 3. kernel. Then reboot, and you should have a working system.
If you use ROM Manager and created a backup then you could flash (install) the OTA ROM Sprint sent out a few months back. This OTA ROM will be for the Rooted evo, so you won't lose root. Go to youtube.com and search this, "How to install new Sprint Htc Evo OTA 3.29.651.5 and keep root." In his comments he'll provide the link to that zip file and you can flash it from the recovery mode. Make sure you wipe the dalvik/cache and then flash zip file from sd card. It will appear to look like your initial problem but it will get passed the white htc screen. You could turn it off and turn it on again if HTC screen stays longer than 10 min. Once the ROM kicks in, you'll notice its stripped of all your cusomizations. If you used rom manager to back up your ROM then redownload ROM manager from market and the superuser app that came with the OTA zip file will allow ROM manager to run. At that point select manager and restore backups from ROM manager and select your backup and it should put you back to where you were prior to the problem.
Sorry so long, but I'm very detailed and don't want to assume you know what I'm talking about.
P.S. similar situation happened to me yesterday I fixed my issue like described above.
Another Thing haha, don't delete your stock apps just freeze them using Titanium backup. Freezing does the same thing for battery life. You wont see them in app drawer and they wont run in background.
This thread is dedicated to hacking and development of the Sharp SH7218u. This is an Android phone with a somewhat unique clamshell form-factor.
Before proceeding, please note that all of the usual warnings apply. The software and techniques described here have the potential to break your device and make it unusable. By using the software and following these techniques you run the risk of bricking your phone. I take no responsibility if this happens - proceed at your own risk.
First, some credits for the work of others:
Z4root:
Developed by xda member RyanZA.
http://forum.xda-developers.com/showthread.php?t=833953
SH7218u Clockworkmod Recovery:
Clockworkmod original developer is Koushik Dutta:
www.clockworkmod.com
Dialer2:
Original developer of now open source dialer is dnaq Productions:
http://dnaq.tumblr.com/
Initial hacking and development work:
Gigi Tse is credited for early and ongoing work for the SH7218u:
http://gigitse.com/
http://www.msharp.cn/forum/t390991/page1/
Now on the instructions....
-------------------
Rooting Your Phone, Installing Clockworkmod Recovery, and Installing Google Apps
Gather the Required Files:
1. Go to the z4root xda thread, login in and download z4root.1.3.0.apk:
http://forum.xda-developers.com/showthread.php?t=833953
2. Download SH7218u_recovery.apk:
(attached below)
3. Download the Clockworkmod recovery flashable Google Apps file from the following site:
http://goo-inside.me/gapps
In the table, you want to select the HDPI, CyanogenMod 6 version. The file that you download should be
called 'gapps-hdpi-20101114-signed.zip'
4. Place these three files on your micro-SD card and insert the card into your phone.
Root Your Phone
1. Boot up your phone and skip the system setup wizard. Go to the app drawer and run 'Settings'.
2. Select 'Applications', and enable 'Unknown sources'.
3. Select 'Development', and enable 'USB debugging'.
4. Exit back out to your home screen launcher, then go to the app drawer and run 'ES File Explorer'.
5. The file explorer should show you the contents of your sd card. Tap on the file 'z4root.1.3.0.apk'.
6. Confirm installation of z4root, and when this is complete select 'Open' to run the app.
7. From within z4root, press the 'Permanent Root' button.
8. Wait until this process is complete, and the phone will reboot by itself. It can take 30 seconds or so for this to happen, so be patient. You are now rooted.
Flash Clockworkmod Recovery Image
You must be rooted for this to work. Do this after you have successfully completed the rooting process above. Also please note that this is not the CWM recovery image developed by Gigi Tse. Her image contains CWM version 3.0.2.4. This is my recovery image and contains CWM version 5.0.2.8.
1. Open the app drawer and run 'ES File Explorer'.
2. Tap on the file 'SH7218u_recovery.apk'.
3. Confirm installation and run the application by selecting 'Open' once installation is complete.
4. On startup, the application will request Superuser privleges - press 'Accept' to allow this.
5. Press the 'Flash Clockworkmod Recovery' button.
6. Wait a few seconds until you see the confirmation message 'Recovery Flash Complete'.
7. Exit out of the application. You now have Clockworkmod as your recovery. You can uninstall the SH7218u_recovery app if you wish as you have no further use of it.
Note for users of Link2SD: This version of Clockworkmod recovery will perform backup and restore operations on the secondary SD card partition used by Link2SD. However, that partition must be formatted in the ext3 filesystem for this to work. Formatting the partition in any other filesystem (e.g. ext2, fat32, ext4, etc.), will result in failure to mount and backup the partition. An SD card can be prepared for use with Link2SD from within this version of Clockworkmod recovery by using the 'Partition SD Card' feature within the 'Advanced' menu.
Install Google Apps
1. Boot into Clockworkmod Recovery. This is done by powering down your phone, then turning it back on by pressing and holding down the number 3 and 6 buttons together, then pressing and releasing the power button. Continue to hold the number 3 and 6 buttons until you see the Clockworkmod screen.
2. Select 'install zip from sdcard' from the menu.
3. Select 'choose zip from sdcard' from the next menu.
4. The next menu will be the contents of your sdcard. Select the Google Apps file - 'gapps-hdpi-20101114-signed.zip'.
5. Confirm the installation and wait until it is complete.
6. Press the back button once to get back to the main screen and select 'reboot system now'. You now have Google Apps installed.
When you reboot the device, you will be taken through the Google account setup. Please note that in order for contacts applications to work with Google synchronization, you will need to install a modified contact editor. The stock firmware on this phone is not intended to sync with the Google servers as it was intended for Chinese users. The modified contact editor fixes this issue. It is free and available from the Market. Look for 'Contact Editor Free' by a developer named 'dmfs'.
Deleted
Deleted
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
TabletGuru said:
Thank you! Very good job!
No ideas how to get the phone to answer a call when you open?
Click to expand...
Click to collapse
Hey someone read my thread!!
Sorry, no posts on this thread yet and it has been up for a while. I think most people who have this phone stick to Howard forums or other such sites that cater to the phone type and its region of origin.
As for your question, no...but I have tried. That would require a modification of the phone app or a change to the OS itself as the phone app is the active app when the phone is ringing and the device is opened. If I had the source code for the stock phone app, this would be a fairly easy thing to do. Unfortunately, I have been unable to find the source for the stock device firmware anywhere. I tried compiling a generic Froyo phone app from the Google source, but of course this did not work. This is a somewhat special app that needs to interface with several parts of the device's hardware, so a generic version just doesn't work. Unless Sharp releases the full source code for the stock firmware, I don't think this is going to be possible....at least not from someone with my somewhat limited development abilities.
Sent from my MB855 using xda premium
Google Play
Hey xdajunkman, amazing work you are doing here.
Have you considered adding Google Play to the mix? I was able to get the latest version working just fine on my SH7218u.
How hard would it be to hack the light notifications area of the phone, to make some of the notifications last for 1-2 seconds longer?
I should also add that my phone is giving some really flaky GPS information. It is putting me somewhere in the ocean near China unless I use wifi only. Do you have any experience with this?
EDIT: I don't know why, but the dialer is not working for me with regard to the long-press of the delete key and silent (#) key. No idea why...
EDIT2: It is because I had another keyboard installed; which must do something funky... switching back to a default keyboard and then trying seemed to work!
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
johnny8384 said:
Thanks for your guide! Do you have got new version Rom? 2.3 or 2.3.5?
Click to expand...
Click to collapse
Not likely to come. This would mean building something like CM7 for a new device from scratch. This kind of task takes dozens of man-hours for an expert developer, and that assumes that they have access to the original source for the release build. We do not have the original source, and there is no such developer working on this device. We will be stuck with Froyo.
Thank you so much for taking the time to write a guide xdajunkman!
I received my SH7218u today and did everything. The instructions were clear and the whole process took no more than 30 minutes.
Surprisingly, my SH7218u accepts 64 microsd card (after you format it).
Is it ok to have 2 partitions?
One is a ext2, and the other I just created using clockwork mod ext3...
I'm wanting to use that custom rom..
EDIT: clockwork mod Repartitioned my ext2 to ext3 now ಠ_ಠ
and all my apps are "installed"
Going to make a backup rom now.. and then Install xdajunkman's custom rom >__<
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
delpan said:
My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps ( don't remember exactly) what i've to do now? plz help me
P/S: My english sucks, sorry for that
Click to expand...
Click to collapse
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
sirjoe1 said:
EDIT: Ok succesfully installed the Custom rom It looks great I might say awesome work xdajunkman
Ok the question is now.. how to I get back all my previous apps and stuff?
I followed the guide and made a backup already
Click to expand...
Click to collapse
It is usually just easier if you wait until you have the new ROM installed before you try and install your apps. There is no reliable way from within CWM to restore your installed apps.
However, because the new ROM is just a modified version of the stock ROM, it should be possible to flash the new ROM without wiping the existing user data and keeping your installed apps. Restore your backup that has all of your apps installed. Then, flash the modified ROM but skip the step in the instructions that tells you to wipe existing user data. Instead of wiping the user data, do the following:
1. In the 'mounts and storage' menu of CWM recovery, select to format both '/system' and '/cache'
2. In the 'advanced' menu of CWM, select 'Wipe Dalvik cache'
Now proceed with installing the ROM as per the instructions. This should result in the modified ROM being installed, but all of your installed apps should be protected.
If this does not work, then you will just have to re-installed the modified ROM according to the instructions (including wiping the existing user data), then re-install all of your apps. For future reference, a great app called Titanium Backup will allow you to backup your apps and restore them after changing the ROM.
sirjoe1 said:
-->My 7218u stuck at Sharp logo when boot because i've uninstalled a system apps
-->( don't remember exactly) what i've to do now? plz help me
Boot into clockwork mod by pressing 3and 6 and the power on button, (assuming you have that installed)
Reinstall the rom.. http://forum.xda-developers.com/showthread.php?p=22106340#post22106340
Click to expand...
Click to collapse
Agree with sirjoe1. Hopefully you flashed CWM as your recovery before you did this. However, if not then booting into recovery mode as described above should trigger a factory reset from the stock recovery partition. I have not attempted this myself with the stock recovery, but usually what this will do is simply return your device to it's stock state. You can then start over using the instructions in the OP....but without deleting critical system apps this time.
Hello again, I've a question, has anyone successfully Overclocked the cpu frequency on this phone using setcpu or similar apps?
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
xdajunkman said:
Overclocking not possible without either a custom kernel or a kernel module of some sort. As the source for the stock kernel was never released, such a thing would be a HUGE undertaking. Very unlikely to ever happen.
Click to expand...
Click to collapse
Oh darn, that's such a downer..
These sh7218u threads are so dead nowadays :/
I might have messed up my phone -_- (again)
I went into the /data/sdext2/dalvik-cache and deleted everything and now a few apps have gone missing, and some won't work, they just give me a force close error >___<
I also lost my go launcher ex settings..
and to make things worse.... my internal memory went to 0% free... deleted a few things to clear up 8mb..
Any Ideas how to fix this ? @[email protected]
[Can you guys play 480p videos?
I can't.. 360p runs fine though..]
I am hoping to get this device this week.
Thanks for your tutorial, and I will let you know if it runs out just fine
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...
With a lot of help from dottat, Dees Troy, and Darth, both in existing posts and in my process, here's a compiled tip guide to how I upgraded my Verizon HTC One M8 from S-off, rooted, KK 4.4.4 with TWRP installed to stock LP 5.0.1, reinstalled the new TWRP, regained root, and reset my preferences for battery life without losing my data, reinstalling apps, etc. It's essentially a workaround to reverting to stock KK 4.4.4 with stock restore before taking the OTA patches. Instead, this method upgrades the firmware and replaces the system, rather than patching.
1. If you haven't already fixed access to your external SD card, please do that. HERE
2. Load the latest TWRP by your method of choice (I recommend fastboot) and make a full nandroid backup to your external SD. HERE (Also, set aside the right copy to install on the upgraded unit)
3. Download dotatt's DOTTAT_VZWM8_S_ON_5.0.1_RUU.exe pack (I know it says S-on. It won't change your S-off status) from this thread. HERE
4. Download dotatt's "Tweaks zip to unlock tether/disable max password wipe/enable music channel" (optional, but recommended) from the bottom of OP. HERE (Also note the instructions toward the top for flashing the L hboot to get out of hangs; I didn't need it, but I was glad it was there.)
5. Download SuperSU per the instructions HERE.
NOW YOU'RE READY TO START THE UPGRADE.
6. Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the EXE version and it did a great job upgrading the hboot/firmware, then upgrading the stystem. Most importantly, it did NOT wipe my data. I also use the htc_fastboot.exe in it's extraction directory for all of my subsequent fastboot operations. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
7. Follow this guide to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described. (AND, fix your SD card access again - see Step 1)
8. Optional - Review your battery usage. There has been a lot of chatter about lower battery life on LP, and I experienced it myself in the first several hours. This guide was helpful in reminding me of things I had done to tweak my phone before. HERE (I know it's a Nexus forum. It's applicable) - It appears that new Google services were turned on in the accounts-sync categories. I recommend looking through Settings-accounts-Google and adjusting your sync preferences on EACH account to the way, or back to the way, you prefer them.
That's the guide. I hope it helps shorten your reading and searching by an hour or two.
For the few people that asked about apps closing when trying to input text after this update path, please see this thread for the fix. HERE