NativeSD WM #1 Introduction
Posts:
#1 Introduction
#2 Setup Partition
#3 Install Recovery
#4 Install Native SD
#5 Applications (Run Backup Restore Delete)
#6 Updating
#7 FAQ
#8 Links to Other OS
#9 Reserved for Learning Never Ends teams
The HTC HD2 was a Windows Mobile Phone. However it can run different phone operating systems including Android. Originally the choice was to run a single version of Android instead of Windows Mobile (using MAGLDR) or to boot from Windows Mobile to Android running on the SD card (for example using Portadroid) by executing CLRCAD.exe and HaRET.exe (Handheld Reverse Engineering Tool) bootloader. The problem with running both Windows Mobile and Android on the same phone is that EXT4 had to be held as a file on the SD card (using FAT32) which is slower. With NativeSD, your SD card is partitioned, or split, into two with the first partition being the FAT32 and the second partition as EXT4. The advantages are, you can still run Windows Mobile and use the FAT32 partition, Android runs much better (faster, with fewer problems and lower battery consumption), you can have as many different versions of Android as you have space on your card and all the operating systems can use the same data in the FAT32 partition. As you keep your original data and Windows Mobile programs on the existing FAT32 partition it is very easy to try NativeSD, including different Android ROMs, but still keep Windows Mobile always available to run any legacy programs that you must have.
This thread is about installing, running and maintaining NativeSD from Windows Mobile (WM6.5). If you are running a different operating system, please visit the appropriate thread listed in one of the posts below or the main NativeSD Rom Boot Script for HD2 forum:
Forum > HTC Leo: HD2 > HD2 Android > HD2 Android SD Development >
[DEV] NativeSD Rom Boot Script for HD2
http://forum.xda-developers.com/showthread.php?t=1869673
More details can also be found in the XDA Wiki:
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD
To get started, please see the next post for the first step:
Setup Partition
NativeSD WM #2 Setup Partition
NativeSD WM #2 Setup Partition
Requirements: To get started you need an HTC HD2 phone (either European or T-Mobile US), and SD card – which you presumably have if you are reading this – and ideally a personal computer. You will need to download a “Recovery” program to run on your mobile – 4EXT is recommended. Since you will be changing your SD Card you are strongly advised to back it up first. The next step is to partition or split your SD card into two which can be done using a Windows program Mini Tool Partition Wizard Home Edition. (Apparently the partition can be done with 4EXT Recovery on the phone but the PC is easier). Of course you will also need to choose a NativeSD ROM from the XDA website.
HTC HD2 Windows Mobile 6.5 Requirements
In order to run Android, your HTC HD2 will need to have:
Radio: 2.08 or higher - download from [RADIO] The HTC HD2 Master Radio Thread
The following three somewhat old threads have more information about Android on HD2:
[REF] The Definitve Guide To Android On HTC HD2
[REF] A Brief guide to Installing and Maintaining Android [SD/RAM] on HD2
[HSPL/HSPL2] HowTo flash everything
Bear in mind that they do not refer to NativeSD.
The steps to take on your PC are:
A) Backup your SD Card - for example copy all of it to your PC or use a new SD card. This step is optional but strongly advised.
B) Format your SD Card to make sure it is in good shape and has a primary FAT32 partition. Cards that are larger than 32 GB will not necessarily have a FAT32 format. For example a 64 GB card will usually be formatted to have an "exFat" partition and needs to be reformatted to FAT32. At the same time you can also choose a cluster size but the default should be fine for now. See the thread [GUIDE] [INFO] All about SD CARDS - which one, why and how!. If you format your SD Card, then restore the data from the backup. These steps are optional but strongly advised. Recommended Windows program for formatting your SD Card as it does not format the "Protected Area":
https://www.sdcard.org/downloads/formatter_3/
C) Create an EXT4 partition on your SD card. There are two methods.
i) On your PC using MiniTool Partition Wizard Home Edition (MTPW)
This is a video showing how to use the program but note that we need EXT4 NOT EXT2 shown in the video: http://www.youtube.com/watch?v=Cygl0qZnbaM
Note that you can use other partition managers but Minitool Partition Wizard works and is the method recommended by Xylograph
ii) On your HD2 using the 4EXT Recovery Classic program by madmaxx82 mentioned in the next post #3 Install Recovery. Check in the thread for your chosen NativeSD ROM to see if it supports automatic creation of EXT4 partition using Recovery. If it does, then install 4EXT Recovery, copy the unzipped Android Native SD build to this folder and execute CLRCAD.exe and HaRET.exe from the recovery folder and the card will be partitioned and the Native SD will be installed automatically. Caution though as these ROMs may not install to NativeSD folder and as a result you may not be able to use some of the other items in this guide. Always backup your SD card before trying this.
D) The size of the EXT4 partition is up to you. The minimum is probably 500 kb but 1 GB is advised and it does depend on the size of ROM you are using. If you have a larger SD card then 2 GB is recommended. Larger than 2 GB may be difficult to backup in one go. A rule of thumb is 0.5GB for NativeSD and 0.5 GB for each ROM you want to have available in EXT4. So the minimum advised is 1 GB. Another rule of thumb could be no more than 25% (one quarter) of your SD Card for EXT4. I only use half of the FAT32, leaving half the card free to backup either FAT32 or EXT4. For example I have a 32 GB card with 24 GB for FAT32 and 8 GB for EXT4 with 14 ROMs (14 * 0.5 = 7GB +0.5).
D) Double check that the first FAT32 and second EXT4 partitions are both 'primary' and that FAT32 is first and EXT4 last partition.
More details can also be found in the XDA Wiki:
forum.xda-developers.com/wiki/HTC_HD2/NativeSD#Format_EXT4_Partition
Please see the next post for the next step which is done on the mobile phone. This is a good time to check that Windows Mobile still works properly for you:
Recovery
Native SD #3 Install Recovery
Native SD #3 Install Recovery
In order to install a NativeSD on your Windows Mobile (WM 6.5) you will need to put a "Recovery" program onto the SD card of your phone. For Windows Mobile the recommended Recovery programme is 4EXT Recovery Classic. This can be downloaded from the link provided by Xylograph on the NativeSD thread
[http://goo.im/devs/Xylograph/Various/Recoveries Download 4EXT Recovery from here]
Although Xylograph provides several different recoveries, the one you want for Windows Mobile is in home » devs » Xylograph » Various » Recoveries » SD >> recovery_4EXT2.2.7_leo_sd.zip
Size: 5.53 MB
MD5: 142c324022b7ea77c3a7ca8d2fcabb70
Link: http://goo.im/devs/Xylograph/Various/Recoveries/SD/recovery_4EXT2.2.7_leo_sd.zip
Download this to either your mobile phone or computer. Create a folder on the SD card of your mobile phone called "4EXTRecovery". (Although you can name the folder anything you want, it is useful to use the same name as the win android program listed below). The 4EXTR.zip file contains five files which should be unzipped into the 4EXT recovery folder. These files include CLRCAD.exe and HaRET.exe. In order to run recovery, from Windows Mobile, you open the recovery folder using a file manager and then press HaRET.exe. (Note to load a ROM you would normally press CLRCAD.exe first but this is not required for and does not impact Recovery). The recovery programme will launch.
As this is a text based recovery programme (in other words, you do not touch the screen), there are a few keys that you need to know in order to navigate around the screen.
Volume up + to move cursor up
Volume down - (or Windows key) to move cursor down
Left call phone button to select
Back button to go back
Windows menu key to move cursor down or quit AROMA Installer
Edit; The above text in Magenta, and a bit below refer to 4ext_recovery_SD which is no longer available on Xylograph's Goo repository. There are other SD recoveries there, give them a go. The instructions given above should be similar.
Note also that if you rename the folder which the files (HaRET etc) are in, you also need to edit the startup.txt file (rel_path="Whatever_you_renamed_it_to"), so probably best to keep the original folder name and put it to the root of your SDcard.
The first action is to format the EXT4 partition (created by Minitool Partition Wizard) using the recovery tool. Even though Minitool Partition Wizard creates the 4EXT partition, some people have experienced problems until they reformat EXT4.
a) Scroll down to ext3-4ext-ext4
b) Scroll to wipe / format
c) Format sd-ext
d) Exit recovery and then restart it to be safe.
More details can also be found in the XDA Wiki:
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD#Format_EXT4_Partition
Please see the next post for the next step which is also done on the mobile phone, using Recovery. This is a good time to check that Windows Mobile still works properly for you:
Install Native SD
Native SD WM #4 Install Native SD
Native SD WM #4 Install Native SD
Requirements: Your Windows Mobile (WM6.5) phone should now have an SD card that has been partitioned into two with the FAT32 partition first followed by EXT4 with both set as primary. The FAT32 partition should have been formatted as FAT32 and the EXT4 partition reformatted as EXT4 using recovery. You should be running Windows Mobile and be able to run recovery. This is covered in the preceding posts.
You will also need to choose a NativeSD ROM from the XDA website. Gingerbread (GB - CM7), Ice Cream Sandwich (ICS - CM9) and JellyBean (JB - CM10) ROMs are supported. GB tends to be more stable and JB is more cutting edge (possibly not as stable). ROMs will state NativeSD in the thread title or in the first post - try searching HD2 Android for "NativeSD". They can be found in either:
HD2 Android NAND Development [http://forum.xda-developers.com/forumdisplay.php?f=928]
HD2 Android SD Development [http://forum.xda-developers.com/forumdisplay.php?f=735]
The Native ROMs are downloaded and saved to your SD Card in zip format. Usually the file name will include "NativeSD". Recommend that you save them in a folder on your SD Card called "Download" as that is where most Android programs will save them. Do not unzip the file.
In order to run recovery, from Windows Mobile, you open the recovery folder using a file manager and then press HaRET.exe. (Note to load a ROM you would normally press CLRCAD.exe first but this is not required for and does not impact Recovery). The recovery programme will launch. Some people refer to the following steps as "flashing" a ROM.
Using 4EXT Recovery:
Select install from SD card.
Select choose zip from SD card.
Choose a zip to apply for example a NativeSD.zip from your Download folder.
Continue install? THIS CAN NOT BE UNDONE. Yes.
Press next to Continue the installation...
Choose Install to SD-EXT.
Select Default Connection - leave this unchecked for PPP connection (default).
Depending on the ROM's AROMA script there may be other choices.
Click next to start the installation
Installing ROM please wait...
Installation complete... please reboot...
Windows Mobile will boot.
Open the NativeSD folder in your SD Card.
Press CLRCAD.exe then HaRET.exe in the NativeSD folder to load Android NativeSD ROM.
More details can also be found in the XDA Wiki:
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD#Install_NativeSD_using_Recovery
When you reboot from Android, you phone will load Windows Mobile. To run your NativeSD at any time, open the NativeSD folder in your SD Card. Press CLRCAD.exe then HaRET.exe in the NativeSD folder to load Android NativeSD ROM.
Please see the next post for applications that can make it easier to run NativeSD:
Applications
NativeSD WM #5 Applications (Run Backup Restore Delete)
NativeSD WM #5 Applications (Run Backup Restore Delete)
Windows Mobile 6 programs
CLRCAD and HaRet
CLRCAD.exe needs to be run in Windows Mobile to enable sound for HD2 Android. See post by DarkStone1337 who comments "Don't worry if nothing happens, this is normal." HaRET (Handhelds Reverse Engineering Tool) is used to boot Linux from within Windows Mobile. More information is available in this thread Linux and Android on the HD2. Both executables are provided in the above link #3 Install Recovery
There are a number of Windows Mobile 6 programs that will automate the task of running CLRCAD.exe and then HaRET.exe from the correct folder in order to load Android on your HTC HD2 Leo. A list can be found in the XDA Wiki:
http://forum.xda-developers.com/wiki/HTC_HD2/Android_Loader
Notable is the WM .exe file created by o82239 called "Multiple Android-Starter (WinMo 6.5 + NativeSD-Android)" that allows you to select which NativeSD Rom you want to run from WM (assuming you have more than one ROM stored in a sub-directory of "NativeSD") or to run any one of 4 different Recovery programs (assuming you put them in the directory "4EXTRecovery", "twrp2", "twrp2.3.3.0.ex" or "recoverytytungbackup").
http://forum.xda-developers.com/showthread.php?t=1951897
Recovery scripts
Tytung has written a "NativeSD Touch Recovery" [http://forum.xda-developers.com/showthread.php?p=33668198#post33668198] tool that runs in Recovery to allow you to Backup, Restore or Delete a NativeSD ROM. It saves the backup to your SD Card in /sdcard/NativeSD/Backup/
https://sites.google.com/site/nativesdtouchrecovery/
It works perfectly for Windows Mobile WM6.5 users who boot 4EXT Recovery from SD using the 4EXT Recovery. To use it, from Recovery, flash NativeSD_Touch_Recovery_v1.0.zip. More details can also be found in the XDA Wiki:
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD#NativeSD_Touch_Recovery
Tytung Softkeys_Switcher_for_NAND_and_NativeSD works for all kinds of ICS/JB NAND/NativeSD ROMs. Use Recovery to Flash Softkeys_Switcher_for_NAND_and_NativeSD.zip to enable/disable the virtual softkeys after installation. See his post #11593.
TWRP Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery that now has Extended Features including Built-in NativeSD manager. See [RECOVERY] Team Win Recovery Project (TWRP) | Extended
kokotas Extended TWRP is touchscreen and supports NativeSD. See Extended TWRP
Android Apps
datagr has created an Android app for "nativeSDMultiBoot" that allows you to choose which NativeSD ROM you will boot next. He has expanded it to include backup and restore running from within Android. Search for his posts on the main NativeSD thread:
http://forum.xda-developers.com/showpost.php?p=31110691&postcount=1
c1cl0n has written an Android app "CM9 NIGHTLY Port Manager" for his [NIGHTLY] CyanogenMod 9 [tytung HWA R3.5] [SD/NativeSD] thread. Using this manager you can change your system values of DPI & make Softkeys visible. It works on most NativeSD ROMS, not just CM9. After making the changes, you have to reboot.
Titanium Backup root is one of the most popular Android Apps (free or paid) as it allows you to backup apps and data from one NativeSD ROM and restore them to another NativeSD ROM. Unfortunately it is not easy to restore the icons on your Android Desktop and care should be taken when restoring Apps from one version of Android to another. This wiki may be helpful:
http://forum.xda-developers.com/wiki/Android_ROM_Update
One of the main reasons for running Android on your Windows Mobile HTC HD2 is the apps that are available from the Google Play Store https://play.google.com/store/apps - to get you started, a few favourites include:
XDA-Developers https://play.google.com/store/apps/details?id=com.quoord.tapatalkxda.activity
gReader (Google Reader | RSS) https://play.google.com/store/apps/details?id=com.noinnion.android.greader.reader
Opera Mobile web browser https://play.google.com/store/apps/details?id=com.opera.browser amongst others such as Dolphin and FireFox
Navigation apps (paid including TomTom and Sygic https://play.google.com/store/search?q=tomtom&c=apps) including free programs such as Google Maps and Waze
Google Apps https://play.google.com/store/apps/developer?id=Google+Inc
Games include the ubiquitous Angry Birds https://play.google.com/store/search?q=angry+birds&c=apps
Social Apps include the inevitable Facebook, WhatsApp Messenger, & Twitter https://play.google.com/store/search?q=social+apps&c=apps&sort=0
but watch out for battery eating synchronization.
BetterBatteryStats will help to identify and guide you how to stop applications that eat your battery when your phone should be sleeping. http://forum.xda-developers.com/showthread.php?t=1179809
Most of these have free and paid versions.
Please see the next post for information on NativeSD:
Updating
NativeSD WM #6 Updating
NativeSD WM #6 Updating
One of the great advantages of the new technique of NativeSD on the HTC HD2 is that all users can benefit from ROM development. So a ROM developed for NAND, implemented using NativeSD, can usually be used by CLK, Windows Phone and Windows Mobile users. Basically the Loader runs an AROMA Installer script http://forum.xda-developers.com/showthread.php?t=1461712 that allows you to choose which version of the ROM you wish to install. The basic components are the same but individual parts are required for different operating systems. You choose which options you wish to install. As AROMA is a Touch and Customizable ROM Installer, it does not matter if you use a Text based loader. Once AROMA is launched, you select options by touching the screen. Recommendation is to accept the defaults the first time.
Files are extracted from the NativeSD.zip file and copied to both the FAT32 partition and the EXT4 partition on your SD card. They are stored in folder with the same name as the ROM (for example NativeSD\CM10). The FAT32 partition, which you can read in Windows Mobile, has only two files: initrd.gz and zImage for each ROM. initrd.gz is a Linux initial ramdisk that has been compressed using Gzip and zImage is similarly a compressed kernel image file. The way you chose which NativeSD to run is by copying initrd.gz and zImage from the ROM sub-folder into the NativeSD folder. This can be done using file manager (overwriting the ones in the NativeSD folder) or more easily using one of the applications shown in the post above. From Android use "nativeSDMultiBoot" and from Windows Mobile use "Multiple Android-Starter" - both of these copy the files for you. In the NativeSD folder, you run the common set of files CLRCAD.exe and then HaRET.exe to boot the NativeSD using the parameters specified in startup.txt. (These are the first tiny letters you see when the ROM starts booting). This can be automated using some of the above applications. In the EXT4 partition the subfolders of NativeSD for each ROM contain data and system files. With all these files being unzipped and copied during the flash and boot, occasionally things go wrong.
Fixing problems
First thing to check is that the NativeSD.zip ROM file was downloaded correctly by checking the Hash checksum. A good Dev will provide this, for example Xylograph recovery_4EXT2.2.7_leo_sd.zip has an MD5: 142c324022b7ea77c3a7ca8d2fcabb70
If your ROM does not boot correctly the first time (after say 15 minutes), you should try and reboot it again. Alternatively you can simply try to flash the ROM again using Recovery. This will keep your data and settings and may correct any problems that have occurred. Search the thread for the ROM to see if other users are experiencing the same problems. Recommend that you look for a post by one of the Learning Never Ends team to say they have flashed the ROM using Windows Mobile successfully.
Updating to new version
When updating to a new version of the same ROM, you can often simply flash the new version on top of the old using Recovery. Conversely, if the new ROM does not suit, you can usually flash the older version again using Recovery. As the different versions of the same ROM are stored in folders with the name of the ROM, this flashing simply overwrites the previous System files, hopefully leaving the data. In some case, the Op will advise a new or fresh install. In that case you should backup the ROM (see above post), delete the existing old ROM (see above post) and flash the new version as if it was a new ROM. You may be able to restore data using either Titanium Backup (or similar app) or data.ext4.tar from Tytung backup.
OTA Update
Over The Air (OTA) Update is supported by some ROMs and allows you to receive push notification of new updates so that you can easily download the updated version of a ROM. This is saved to a folder on your SD card called sdcard/OTA-Updater/download. Using OTA is the same as downloading from the home page but possibly more convenient as it is automated amd you do not have to visit the thread. You do have to use Recovery to Choose a zip to apply - for example the one saved in sdcard/OTA-Updater/download.
Resize EXT4 Partition
Resizing your EXT4 partition can be done in Linux using GParted or from Windows. First recommendation is to Backup all of your NativeSD ROMS to FAT32 using either one of the methods detailed in the above post and then back up your FAT32 Partition to your PC. From Windows, you can then use MiniTool Partition Wizard Home Edition 7.6 to
a) Delete EXT4 Partition
b) Extend/shrink FAT32 to free up the new EXT4 size you want
c) Create a new EXT4 partition with the size you want
d) Format EXT4 Partition again using 4EXT recovery
e) Restore your NativeSD ROMS to EXT4 (following whichever method above that you used to backup)
Please see the next post for:
FAQ
NativeSD WM #7 FAQ
NativeSD WM #7 FAQ
Please see xda Wiki for
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD
XDA University has A New User’s Guide to Android and an Android Dictionary.
Several ROMs now have separate Question and Troubleshooting [Q&T] Threads that should be used to post general questions instead of the development related forums. They are located in the forum > HTC Leo: HD2 > HD2 Android > HD2 Android Q&A, Help & Troubleshooting and General and include threads for:
[Questions/Troubleshooting][ROM Sea_JB and Sea_PA}]
[Questions/Troubleshooting ROM TouchWizMOD
Q&T for [Pixeldroid Jelly Bean 4.2.2][XYECMAO][Monster Sound][NOS Injected] Rom
[Q&T][ROM][4.2.2][720p] NexusHD2-JellyBean-CM10.1 V2.0 [NativeSD]
You should also read the above posts and search this thread before posting. Please see HD2 Forum Rules. You may will find it helpful to read this [GUIDE] - XDA New User Guide - Getting started on XDA. Questions about NativeSD for Windows Mobile are welcome here but only users with 10 posts (or more) will be allowed to post to any development-related forum. Before you try Android NativeSD we would expect you to have used your HD2 and made 10 posts, for example, by helping answer questions in the HD2 Windows Mobile 6.5 Q&A and General forum.
Please see the next post for:
Links to Other OS
NativeSD WM #8 Links to Other OS
NativeSD WM #8 Links to Other OS
This thread is a GUIDE to NativeSD for Windows Mobile (WM6.5) New Users
If you use another Operating System, although much of the information here is relevant, you should read and post in the appropriate one of these threads:
MAGLDR NativeSD Installation
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD#MAGLDR_NativeSD_Installation
Forum > HTC Leo: HD2 > HD2 Android > HD2 Android Q&A and General >
NativeSD Rom+EXT4 for New Users with peechurs
http://forum.xda-developers.com/showthread.php?t=1881205
The first post has pictures ("peechurs") showing how to partition SD Card and "flash" ROM using 4EXT Recovery.
Windows Phone (WP7) Installation
http://forum.xda-developers.com/wiki/HTC_HD2/NativeSD#Windows_Phone_.28WP7.29_Installation
Forum > HTC Leo: HD2 > HD2 General >
Step by Step:: How To Set up WP7 and Android with NATIVESD
http://forum.xda-developers.com/showthread.php?t=1880905
There is useful information for Windows Mobile Users in the above threads and in the main NativeSD Rom Boot Script for HD2 thread.
Forum > HTC Leo: HD2 > HD2 Android > HD2 Android SD Development >
[DEV]NativeSD Rom Boot Script for HD2
http://forum.xda-developers.com/showthread.php?t=1869673
Please post questions specifically about NativeSD for Windows Mobile (WM6.5) in this thread here.
http://forum.xda-developers.com/showthread.php?t=1986437
1. Introduction
2. Setup Partition
3. Install Recovery
4. Install Native SD
5. Applications (Run Backup Restore Delete)
6. Updating
7. FAQ
8. Links to Other OS
9. Reserved for Learning Never Ends teams
Reseved for Learning Never Ends team
If you find this thread helpful then do not forget to
Rate: *****
Submit thread as News Tip
If you find a particular post is helpful, please click on the :good: Thanks button.
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
The Learning Never Ends team is a very small group of a few HTC HD2 Android enthusiasts who have been inspired by our dear friend and LNE team member Kuzibri to remember that Learning Never Ends and share our learning with you. I suggest that you do not send PM to the team as they may take a long time to be answered (if at all - particularly those that start with the subject "I want"!) Remember that all of us volunteer our free time.
Cheers
Tom
Szczepanik said:
If you find this thread helpful then do not forget to
Rate: *****
Submit thread as News Tip
If you find a particular post is helpful, please click on the :good: Thanks button.
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks
The Learning Never Ends team is a very small group of a few HTC HD2 Android enthusiasts who have been inspired by our dear friend Kuzibri to remember that Learning Never Ends and share our learning with you. I suggest that you do not send PM to the team as they may take a long time to be answered (if at all - particularly those that start with the subject "I want"!) Remember that all of us volunteer our free time.
Cheers
Tom
Click to expand...
Click to collapse
Hi Tom,
thanks my very dear friend for the credits :highfive:. I will try my utter best to be of help on this thread too. Members can ask me all kind of questions related to WinMo 6.5.5 and/or Android Native SD. Regarding the Native Android SD, your posts are as clear as possible and can IMO hardly lead to a lot of questions, so I will focus on the software side of it. , i.e. which ROM to use, how to solve problems with Android, etc, etc. I would like to suggest that it's, in my personal case, allowed for members to send me a PM if necessary, cause, for well known reasons, I have the time to answer and I'm used to always answer my PM's ASAP.
very best regards and good luck with this new thread, Kuzibri
I would like to say a BIG HELLO to the latest member of the LNE TEAM, kuzibri:thumbup:
Its an honour to have you on board
Sent from my GT-I9100 using Tapatalk 2
wis1152 said:
I would like to say a BIG HELLO to the latest member of the LNE TEAM, kuzibri:thumbup:
Its an honour to have you on board
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks very much my very dear friend, highly appreciated and much honoured to be part of your team now!!!!!!
very best regards, Kuzibri
P.S. Edit your signature!!!!I I changed mine, so you can change it too, the learning never ends is back!!:victory:
I haven't say thank you to people for a long time, but this time I have to say: Thank you, LNE Team.
Will try it later.
700
Wow, 700 Thanks for a non-porter or developer, but just somebody who likes to help people when they have problems!! Many, many thanks to all of you who pushed the thanks button for me!!!! Taking into account that the thanks button was introduced when I already had 2500 posts, this means that 1 of 4 of my posts is rewarded with a thanks!!!!! This is great and very encouraging! Many, many thanks.
very best regards, Kuzibri
First: Thank you VERY much for this Guide, i just startet to "learn" about Android NativeSD with WM 6.5 and it was hard to get information together for absolute beginners.
Second: Questions!
Requirements, i have a HD2 (Europe version) with the lastest original WM 6.5 ROM from my Provider,
do i have to flash a Hard SPL or upgrade the Radio to later version to use Android NativeSD?
Wuehli said:
First: Thank you VERY much for this Guide, i just startet to "learn" about Android NativeSD with WM 6.5 and it was hard to get information together for absolute beginners.
Second: Questions!
Requirements, i have a HD2 (Europe version) with the lastest original WM 6.5 ROM from my Provider,
do i have to flash a Hard SPL or upgrade the Radio to later version to use Android NativeSD?
Click to expand...
Click to collapse
Hi,
First of all: welcome to this thread!!!
if you have the latest ROM version from your provider, which is HTC's 3.14 ROM, you already have SPL 3.03 and Radio 2.15. The SPL version you can check on your tricolor bootscreen and the radio version in settings-software. If you have these versions, there is no need to flash a Hard SPL,
best regards, Kuzibri
Now there is a guide i just had to try it out. Everything worked fine till i tried to start Android after flashing by first executing clrcad.exe.
I received the Message: Application not signed,..blablabla.
From this point, a lot of other applications from WM6.5 wont work any longer to :crying:
But i found a solution here:
http://forum.xda-developers.com/showthread.php?t=858348
maybe you can add this to the guide, or make it a step to change settings befor starting to flash because its very hard for a normal beginner to
change Regkeys when most apps wont work any longer.
After changing the RegKeys Android starts and iam very happy to use it and can always switch back to WM6.5!
Thanks again!!
(sorry 4 bad english :laugh
Wuehli said:
Now there is a guide i just had to try it out. Everything worked fine till i tried to start Android after flashing by first executing clrcad.exe.
I received the Message: Application not signed,..blablabla.
From this point, a lot of other applications from WM6.5 wont work any longer to :crying:
But i found a solution here:
http://forum.xda-developers.com/showthread.php?t=858348
maybe you can add this to the guide, or make it a step to change settings befor starting to flash because its very hard for a normal beginner to
change Regkeys when most apps wont work any longer.
After changing the RegKeys Android starts and iam very happy to use it and can always switch back to WM6.5!
Thanks again!!
(sorry 4 bad english :laugh
Click to expand...
Click to collapse
Hi my friend,
First of all: after pressing clrcad, you have to press haret.exe!!
maybe something went wrong with the partitioning of your SD card for the .EXT4 partition, therefore I would like to advise you to use another program for partitioning your SD card. Have very good experiences with that one. See attached file. Backup your SD card to PC, unzip this file and copy it to the root of your SD Card . Then download the Native SD Android build of your choice and put it unzipped in this recovery folder and press clrcad and thereafter haret.exe and your Native SD Android will be installed without ruining the WinMo apps and/or changing reg keys because they are at this moment not on your SD Card. .After installing the Native Andoid build, copy your WinMo progs back to the SD Card and they will be copied in the FAT32 partition of your SD Card.
very best regards, Kuzibri
Learning Never Ends team said:
NativeSD WM #2 Setup Partition
C) Create an EXT4 partition on your SD card using Minitool Partition Wizard Home Edition.
This is a video showing how to use the program but note that we need EXT4 NOT EXT2 shown in the video: http://www.youtube.com/watch?v=Cygl0qZnbaM
/QUOTE]
Hi my dear fellow LNE friends,
maybe you can add this program to the C guide to make an EXT4 partition on the SD card: Recovery - see attached file. Format SD Card, unzip this file to the root of your SD .card and copy the unzipped Android Native SD build to this folder and execute clrcad and haret from the recovery folder and the Native SD will be installed automatically. It works perfectly for me and is very fast !!!!! IMO it's the simplest/easiest way for beginners. It's really only called Recovery.7z. Do not know exactly where I "grabbed" it anymore , but it works fabulously!!
very best regards, Kuzibri
Click to expand...
Click to collapse
Thank you very much for your post.
Class 10 or Class 4 micro Sd better for Native SD Android roms.?
Before i used Class 10 micro sd for Sd Android roms.
But it is very slow and with a lot of problems when SD rom starting.
Related
This is meant to be a basic guide to installing and maintaining Android (SD CARD/RAM) on your HD2
NOTE: This guide is not meant for NAND versions of Android installation !!
I want to thank all the XDA forum developers who have made it possible to put Android on the HD2. This is my attempt to make a simple guide for what can be confusing and somewhat scary process (It certainly felt like that to me!!).
For detailed information guide and FAQ please read this thread by mskip
For clear explanation of how things work in Android on HD2 these two threads have excellent detailed information:
http://forum.xda-developers.com/showthread.php?t=813434
http://forum.xda-developers.com/showthread.php?t=790095
Click to expand...
Click to collapse
Before you start you need this Info
Windows ROM version > All Ship ROMs are compatible
Radio Version > Radio needs to be 2.08.50.xx or more (x.xx.51.xx are not compatible)
SPL
Click to expand...
Click to collapse
How to get the Info
For items 1,2 in WinMo look under Settings>About Phone>Software information
This info is also displayed on the bottom left corner (the numbers after the alphabets R,D,G) of your initial boot up white screen with green HTC logo
For item 3 >> Turn phone off > Press and hold Volume down button >briefly press release power button >SPL version is displayed on bootloader screen (Red/Green/White)
Click to expand...
Click to collapse
For those with Radio > 2.08.50.xx you can install Android >> GO TO STEP B
Click to expand...
Click to collapse
For those with Radio < 2.08.xx.xx you cannot install Android without upgrading your Radio (Flashing a new Radio) >> GO TO STEP A then STEP B
Click to expand...
Click to collapse
STEP A (Flashing a new Radio)
If you do not have a compatible Radio version follow the steps below:
Upgrading to the newest HTC stock ROM: This process will upgrade your Radio version anyway (The latest 3.14 ROM has Radio version 2.14.50.4 which is compatible with Android installation): LINK HERE
If you don't want to / or can't upgrade to the latest HTC stock ROM you are going to have a slightly more complicated way
If SPL is 2.10.xxxx or below then use HSPL method. Click here
If SPL is more than 2.10.xxxx you have 2 choices (since HSPL does not work)
Use SSPL method click here
Downgrade your SPL and then use HSPL method click here
Note:
>>Please check the radio version recommended by the Android Build maker>>
>> Click here if you want to download Radio versions
Click to expand...
Click to collapse
STEP B (Installing Android)
If your Radio is compatible (>2.08.50.xx) then here is how to install Android on your HD2
1) Micro SDHC card
Should be atleast 4 Gb, Class 2/4/6/8/10
Formatted clean with 32 or 64 Kb cluster size
2) Install automatic boot loader on WinMo :
This allows you to choose between booting into Windows or Android on start up. From 2nd Android bootup onwards these programs will make it easier to load Windows/Android at startup and you can even specify autoboot into Android if you wish.
Download this as a cab file and install in the phone memory (not in SD card)
Android Loader v6.0 Final for HD2
Exceller bootloader
You can of course manually always boot up Android anytime from Windows File Explorer by running CLRCAD and then HaRET files included in the Android build (see below).
3) Android Build :
Download your chosen Android build on your computer.
Extract / Unzip the folder on the computer
Now copy into the Root of your SD card.
Folder should be labelled "Android"
Once copied into SD card you will see 2 files: CLRCAD.exe and HaRET.exe which have to be run to boot into Android.
There will also be other folders / files (Android Apps, initrd.gz, system.ext2, rootfs.img, zimage, startup.txt, ts-calibration) please leave them as they are.
There are many choices in builds available, such as - MDJ, Darkstone, MIUI,. Please search the forum to look at the different features. I can't advise you on what clothes to buy. The same reasoning applies to advising on Android builds, you have to find out what is right for you...Try the build, if you dont like it, just go for another build..copy and paste your new android folder over the old one and its done.....
4) Data.img :
Your build may have a ready-made one included in the build folder or available to download separately. Size of data image is upto you, 256Mb/512Mb/1Gb (or more). This determines the Size of your Android operating system space for settings and downloaded apps etc. Bigger size allows you to keep more apps etc.
>> At start up if you have a ready-made data.img file, booting up in Android is much faster (5-10 min). (You can choose the image size yourself with this option)
>> If you boot up without a ready-made data.img (Clean Install), then this is created by Android system at first bootup which takes longer (up to 30 min) Here the system will choose its own set default image size depending on startup commands in the build. Its not easy to change this size once its created (although it is possible)
5) First Android Boot
Once you have reached this step you are all set. It really is that simple!
These steps are performed with the phone booted in WinMo
Charge your phone to 100%. This ensures proper battery calibration.
In your File Explorer open the Android folder on the SD card
Run CLRCAD - Nothing seems to happens - This is normal. !!!
Run HARET - Small pop up window with grey progress bar appears with message HaRET LINUX BOOTING - You should then see some text lines in the top left corner of the screen and then a Splashscreen (blank screen with a HTC logo) Please be patient and allow time for the initial bootup.
If Android loads successfully, then (depending on your build )another Splashscreen will appear and then the Lockscreen for Android is launched.
Set up your phone for first use as per onscreen instructions and let all account finish syncing before doing anything else
Click to expand...
Click to collapse
Once you are up and running here are some of my own tips to maintain your system.
1) Always back up of your data.img file on to your pc/mac (weekly)
This is better done in WinMo. This will mean that you can always have a failsafe arrangement for troubleshooting.
2) Troubleshooting (If you start getting data corruption errors or force closes .
> Make another Clean Install of the build -Boot into Android- Reboot in WinMo - Connect to Computer - Copy backedup data.img file into the New (compatible) Android folder.
DONE! you are back where you started. All apps, settings, contacts,emails, messages are saved as they were at the time of backup.
You can also use a backup programme like Titanium Pro. This is useful when going over to a completely different chef build as you cannot (usually) take your old data.img file across.
3) Changing kernels
Follow instructions on the relevant thread.
For MDJ / Hastarin Kernels the following steps work
Boot up in windows - copy 'zimage' and 'Root' folder (which has modules) from the new kernel and paste into your /Android folder on SD card (i.e replace zimage of old kernel).-
Boot up android - check for successful upgrade under Settings>About phone>Software>Kernel ... the new kernel should be listed.
On boot up android will copy the contents of the /Android/Root folder to the relevant place.
If upgrade is successful then while in Android use a File explorer (with root permissions) to delete the 'Root' folder within Android folder, as this is no longer needed.
Note: Some kernels require the Modules (wifi,bt,lights etc) to be copied manually using Root File explorer while booted in Android. Please check the relevant posts for correct steps.
4) Upgrading Android Builds
I always do a clean install i.e let the Android build its own data.img with a clean formatted SD card.
Once this is done then copy your old backed up data.img and overwrite the newly created data.img to get all your info and settings as they were.
Caution: data.img is usually not compatible across different chef builds and its best to start a clean install if you are going to use a completely different build altogether. You can get you settings back by using a backup programme such as Titanium. Google sync will get your Contacts and Calendar back anyway if you have synced it previously to Gmail account.
5) Improving Battery Life
Having read through a lot of forums and trying out various techniques here are tips that have worked for me.
Charge your phone in WinMo to 100% (Green LED) While still connected to charger boot to Android and wait for the LED to go green. Then disconnect from charger.
Autoboot before launching into windows/sense fully, I use Exceller autoboot in 3 sec.
Rebooting Android 2-3 times after initial install and letting it 'settle' for a 1-2 days
Turn off any functions not required e.g BT, WiFi, GPS, Autosync
Turn down screen brightness to minimum
Use a battery current widget to monitor drain
Conditioning of battery: Boot into windows when battery is @ 5%, Discharge the battery fully and let the phone turn off> charge fully to green LED while phone off >> Boot up in Android and continue charging till LED green>> One cycle every 2 weeks
Recalibration: In Android with File explorer (e.g ES Explorer), Choose settings, enable root access and then in Root delete ... /data/system/batterystats.bin . This should be done when 100% charged, Now disable root access in file explorer and close, Run the battery down fully and follow the step above...
Fully conditioned battery should show about 4.2 - 4.3 V charge at 100% (Free app Battery Indicator)
Dataswitch (free app) allows switching mobile data when phone is not in use such as during night time etc
I keep Airplane mode in windows as default before first boot in Android (Not sure if this really helps)
For me greatest battery drain seems to be when i am in area of poor phone signal> switching to 2G helps using Dataswitch app
Things that don't work:
Task killers are not really very useful according to Hastarin
For more detailed information regarding battery life issues have a look at this post
Click to expand...
Click to collapse
Have fun and enjoy your HD2 with Android
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Noob question
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Proz00 said:
"Radio Version > Radio needs to be 2.08.50.xx or more"
more correct
Click to expand...
Click to collapse
Updated, Thanks for that.
loni90 said:
Hi!
ive done all this last summer, and it all works fine.
but i wonder if android will work if you have the original WM6.5 insted of Chucky, and other costum ROM?
i mean, the customs are really ugly, and i never use them on dual boot - but i would use WM6.5 if i had the original one, with sense and everything.
the dual boot would be more useful. now i only use android.
Click to expand...
Click to collapse
I agree with you on that. The stock ROM work fine (check my sig) and to be honest I tried the custom ROMs but felt more comfortable with the Stock ROM. It means less messing around with your phone!
Its most important however that your Radio is compatible though. If its not then there is no choice but to Flash a new Radio ROM.
Seems to be well explained, thanks
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Ahh i just told mate at work copy android to sd card run cllr then haret.
Worked fine lol
omershahab said:
What is the advantage of letting the Android build create its own data.img first and then overwriting it with your previous data.img?
Click to expand...
Click to collapse
This only applies for Upgrading and not a New install. For a new install its always better to let the system create a data image or use the 'empty' image supplied with the build. Most builds have codes to create a default size image. If thats not to your liking then you can choose a supplied image of desired size and do the first boot up...
For upgrading purposes this method has advantages
1) it ensures a clean trouble free installation first time (makes sense to avoid any conflicts with the old data image on boot up.)
2) If there are any problems with the build then at least you can identify them before you transfer the old data image.
solid.snake said:
Seems to be well explained, thanks
Click to expand...
Click to collapse
Your welcome
Difficult to express how easier you made this process for me, with all info provided.
In my name, and the name of all the rest,that will use this thread to start with Android on HD2...... txs
Updated
updated info on maintanence and battery life
despy1989 said:
updated info on maintanence and battery life
Click to expand...
Click to collapse
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
KrewsialNL said:
I just added a link to your thread in my signature if you don't mind. Hoping it will provide easy access for all users
Click to expand...
Click to collapse
Not at all Reminds me I have to do the same on my signature too
Hey, would doing this void my warranty/contract insurance?
Im on virgin media UK, if that helps.
Thanks for the great tutorial anyway
Unless u install a HSPL my understanding is that there is no reason to void your warranty. But I m no expert in these matters. Having said that my old hd2 touchscreen was freezing and I had hspl on it but managed to reinstall the original SPL back and returned it to virgin and this one is the replacement..they didn't complain ..
Sent from my HTC HD2 using XDA App
I have radio 2.07.51,22_2 and spl 1.42
Does that mean the only way I can do this is the HSPL method?
Great guide m8 good job well explained, but I dont know if this helps anyone but I always un-mount my SD card before a reboot or shutdown, on some builds it can reduce corruption to your data image (ie cedesmiths builds)
JR
@ samdeath . Have u considered upgrading your HTC stock ROM? The new 3.14 ROM also upgrades ur radio. In that case there is no messing with HSPL. The other option is SSPL which does not change ur original SPL.
@ JR . In theory if u umnount the SD Card in Android, it only delinks the the SD card portion outside of your data image? If u umnount the whole SD card then android would crash.
Sent from my HTC HD2 using XDA App
I cant upgrade the stock rom, there isnt a virgin media rom on the htc website, and the normal one says my device is not eligible for it. However, ive installed HSPl now, and followed all the steps, changed the radio to 2.15 etc, However now ive just "installed" android for the first time and its been on the htc spash screen for like an hour. I did not use a data file, is this normal?
Using froyo hd v4.6 btw
Hello again fellow nookie lovers....
DISCLAIMER: If you do not know what the following information does, means, or could result in if not performed correctly, please stop now and go no further. I hold no liability for how you use the following information or if you brick, bork or f&*k up your device.
Now with that, let's continue.....
I decided to post up a modified .IMG file I was able to throw together after getting my hands on a honeycomb preview. The original IMG was provided to me by a good friend (Thanks J and Thanks to the creator of the IMG) and then honeycomb come shortly after.
Using WinImage or a similar program to burn the IMG to a SD card, 1G or larger, will give you a bootable SD allowing you to boot directly into clockwork recovery and install the following:
B&N Original Firmware 1.0.1
Nookie Froyo
Nookie Honeycomb (SN:Overclocks to 1100 default)
Google Apps
Before installing any of the 2 Android systems, remember to visit "Mounts and Storage" and format the Data, System, and Boot partitions. Save Boot for last as it will lock up the nook and require a restart of the device. Once these areas are formatted, continue to install your preferred system of choice. Once that is completed, be sure to install the Google Apps zip to give you the market.
As of this time, the IMG file is approx 978 MB. As I modify I am sure it will grow to require a 2 GB SD.
For my next project, I will be including an image with some of the most important apps a Droid user needs, ie:
ADBWireless
Applanet
BetterTerm
SetCPU
etc
If there are any good apps that I might overlook, hit me up here and let me know.
Nookie-Installer - http://www.megaupload.com/?d=PLNQ9QYZ
~Exile~
"When All Else Fails, Try Linux"
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!
Hi all,
Sorry, posting here because no access yet to dev sub forum. Admin, can you move it in dev subforum ?
Long time reader of xda forum, this is my first contribution. Long Post ... read carefully before starting.
This modded TWRP recovery program open the ability to boot any roms or recovery roms from external storage or even internal storage ( but not a lot of place there...).
It can be very usefull to :- test a new released custom ROM without erasing your current one
- use any recovery ROMS
- run multiple instance of same ROM : example CM11/Dalvik and CM11/ART runtime ( thank's to excellent porting of CM11 from sbrissen ! )
- Save your internal flash by writing only to external card.
- test kernel/initrd without flashing them
- bypass 8M limit of boot/recovery devices size Limitations :- fully supported internal roms ( located in /data/media/0/roms )
- fully support FAT32 (vfat), EXTx on external sdcard roms
- Partially supported Exfat filesystems ( >= Android 4.3, or any android 4.x with latest Civato kernel http://forum.xda-developers.com/showthread.php?t=2287802 )
- Not supported NTFS until now ( just because I never used it... )
- Sizes of filesystem hardcoded in this version ( check /sbin/create_rom.sh if you want to change default sizes )
- multiboot only from recovery program ( I did that on purpose just because did'nt want to change boot.img )
- Not all internal block devices "protected" from OTA and/or APPS - 5 blocks are protected ( boot, efs, cache, system, data ). Maybe modem and preload will be added next time...Some time ago, I started to try to add multiboot fonctionnality to our Galaxy Note 8.
My starting point was to port kexec-harboot patch created by mkasic in this post http://forum.xda-developers.com/showthread.php?t=1266827 and explained also by Tassadar in http://forum.xda-developers.com/showthread.php?t=2104706
Unfortunaltely this method could not be fully completed, mainly because one of the very lasts operations of kexec (disabling mmu) did not work on our cpu - exynos4412.
Then I tried another method derivated from kexec-hardboot method which finally worked very well.
I will explain in another post the details of the method and kernel patch/userspace tool. I think this method is not as elegant as KE-HB method but is easier to implement and i think it can be applied easily on almost all Android devices.
At this step, I was able to boot any kernel/initrd from android. Next step was to be able to boot a full custom rom from another location than the inernal flash.
I looked at excellent multirom project sources from Tassadar wich gave me good knowledge of the method applied ( if I understood well : first stage ke-hb kernel/initrd acting as bootloader and new init injected on the fly in target inird, new init that is
able to mount/load appropriate filesystems ).
My goals was to make something easier to code and to use the features directly provided by original targeted init. I wanted also to use exactly the same recovery tools to manage an external rom or the internal rom.
The method is quite simple :
- creating img files formatted as ext4 devices ( for cache, system, data, efs, and boot)
- associating those img files to loop devices
- force linking the loop devices to the original internal blockdevices (mmcblk0pxx) in /dev filesystem
Step 3 is very important because all recovery programs and installation programs use them to mount/unmount/format/install operations.
When the 3 steps are applied, we can use all recovery programs to install a rom directly in the new locations. We apply also the same method to install any recovery images
Even if all recovery programs are able to support this method, I choose TWRP to add new management functions ( create/delete roms and recovery roms ) mostly because it was very easy to modify ui.xml to add custom pages and to add functions ( as shell scripts )
Note that the same method is also applied for booting a new rom. In this case, we use native fonctions in init.rc to mount the appropiate img files ( mount [email protected]/to/img/file ... ).
You can look shell programs in /sbin and files in /injector dir to check methods.
Instructions :
Important Note : Use this program as is, I am not responsible if something goes wrong and erase your data, so BACKUP all your data before using this program.
Also I recommand end-users to wait few time for feedbacks from developpers and powerusers before trying it.
Please read carefully all instructions.
If you install a ROM on vfat, exfat linux filesystems the ROM size will take about 7GB on your media card, so verify first remaining space before installing.- cache : 1.5G
- system : 2.5G
- data : 3G
- boot : 8M
- efs : 20MIf you install on EXT fs, same size will be reported but as img files are sparsed, real size used will be far less (only real size of all objects installed)
Install to internal flash ONLY if you are sure to have always 7GB free.
For your first installation, I recommand that you use an external sdcard formated in vfat. If you have an external sdcard in ext4, it will be better. For recovery ROMS, no recommandations, it will work well everywhere.
If you have ~7G available internally, go for instern install, installation will be very fast and ROM will be as fast as real rom.
Typical new rom installation : follow this steps for first time try.
Choose for example Cyanogenmod (10.2 or 11) for first try.
1 ) "ROMs Management" -> "Create New ROM" -> Press Storage, choose "external Card" ( even if it is already chosen ) -> "ROM Name" -> enter name "test" (no space in the name !) --> "Swipe to Create ROM"
-> wait ~20mn ( if external ) or ~1 mn ( if internal ) In console output, you will see :
Creating ROM...
....
ROM creation complete. Press "Back" to go back to main menu
At the end of this step, all empty img files are created ( will be filesystems and boot images )2 ) "set ROMs" -> Press Storage, choose "external Card" -> press on ROM name that you previously created --> "Swipe to Swap ROM"
-> wait ~5 seconds
In console output, you will see :
Swaping ROM...
...
Command succeded
Swap ROM complete Press Back => In main menu you will see in red color "CURRENT ROM : <name>
At this step you can now Install a ROM as usual3 ) Install ROM, GAPS, PROGRAMs as usual, this will be installed externally.
At the end of installs, DON'T REBOOT, go to main menu4 ) Go back to internal ROM : "Set ROM" -> "Reset to Internal" -> "Swipe to confirm switch" -> "Back"
5 ) "Multiboot" -> "Boot ROM" -> choose your newly created ROM -> "Swipe" -> "Reboot New Rom"
Use same procedure to install recovery ROMs.
Notes :Be patient on first boot....
If first boot does not work try another time ( reboot to recovery ). If still does not work, you can let a message here.
Active "Advanced reboot" in CM Roms to be able to reboot to recovery.
I let roms and recoroms directories opened. Play with img files only if you know what you are doing.References / Credits :
mkasic : kexec-hardboot creator
Tassadar : multirom creator - bbootimg included in this release for boot.img extraction
sbrissen : cm port on Galaxy notes
Civato : ROMs and Kernels ( native exfat very usefull )
TWRP Team
All Roms creators : Without all of you, this project will be useless !Philippe,
Great progress. Hope it will reach functionality of Nexus 4 MultiROM. It will be good if we can install additional ROMs on stock ROM without allocating that much space. Also NTFS support can be added.
Thanks.
Hello. On another XDA forum, the Note 2 forums, there's a developer who has dual boot working on the Note 2s (same specs as the konawifi). I'll post links for you to look over and possibly contact the dev.
Link to Note 2 N7100/N7105 thread for the mentioned above
http://forum.xda-developers.com/showthread.php?t=2239453
Link to github referring to dualboot recovery
https://github.com/Hellybean/android_bootable_recovery
EDIT: another link to the kernel with dual boot capabilities:
https://github.com/Hellybean/android_kernel_samsung_smdk4412/tree/dualboot
idk if these are any help for your efforts, but thank you sir. can't wait to see the final project.
Great work!
Been using this for a week now... I love it.. I'm using stock 4.2.2 internally and testing all the others externally.
good
thanks! it worked perfectly
Got it working after figuring need to install a 4.4 rom then go about my merry way!
[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet
Edit 2-5-23: I recently revisited my installation and found it had become sluggish to the point of being more or less useless. Google Play service updates had taken their toll. So I decided to start over and use microG instead. I also found that the original rooting method no longer worked for some unknown reason, so I resorted to Magisk. Seems like a good time for an update to the instructions!
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Using microG to spoof Google Services Framework signature frees you from the relentless pressure of GApps as Play Services are always updating and always expanding. I originally used a pico GApps package on my first install. At the time the package was 77 MB. The current package as of this editing is 184 MB--too much for the device. You can start with my original package but it won't stay that size. Still, some people will want to try so I have provided instructions for both microG and GApps.
If you have a bootable SD card made for installing CM 10.x-13.x, you can skip to step 2b.
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from https://www.mediafire.com/?5vcw8l603d3r5sc or https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8 [this ROM is no longer in the repository maintained by @amaces] (alternate link provided by @mikeataol)
e. Magisk for the Nook Tablet: https://forum.xda-developers.com/attachments/magisk-v16-0_patched2-zip.4427362/ (credits to member @fddm)
OPTIONAL:
f. the zip file of the GApps package (corresponding to Android 7.0): https://www.mediafire.com/file/po12x99lg47p4oj/open_gapps-arm-7.0-pico-20170310.zip/file
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install magisk-v16-0_patched2-zip
OPTIONAL:
k. Reboot to internal (emmc) recovery as in 3d.
l. Select Install. From the external SD card install appropriate opengapps zip
Continue here from either step j or step l
m. Remove SD card and select reboot.
For GApps
n. Wait for first boot to complete and sign in.
After first boot and the usual stuff, check Magisk Manager to see if root is enabled. You will be asked to update Magisk Manager. You can say "yes" ONCE. It will ask every time you open the app, but don't say "yes" again. The next update will render it inoperable., you'll lose root, curse me, etc. You've been warned.
Done!
[Don't you want to make a baseline backup right now?]
microG (for those skipping GApps)
Spoiler
You've skipped GApps if you're looking at this. There are all kinds of packages available for Magisk to do all the microG stuff in one fell swoop. But there's a lot of contradictory information out there and many of the packages include other stuff you may not want. Also, this old version of Magisk may not work with some of the packages. In the end I decided to try setting up microG the way I learned to do it: manually. It's not that difficult and you get only what you want.
To work, microG requires that signature spoofing be enabled on the ROM. On this ROM you need to use Xposed for that. So let's get started!
4.
a. Download the Xposed installer zip for Magisk and SDK 24 (Android 7.0): https://www.mediafire.com/file/v6zkpj4n3rbi11t/xposed-sdk24-topjohnwu.zip/file. Copy the file to the bootable SD card you used for the ROM installation.
OPTIONAL
b. Download the flashable maps zip file and copy it to the SD card (you only want this if you wish to use Location services or might want to run Tasker): https://www.mediafire.com/file/7y8cmr4obydo35d/mapsv1.flashable.zip/file
c. You'll need some kind of root file manager for this process (you could use adb, but it's cumbersome). I've attached an old version of ES File Explorer that I like. You'll have to adb install that since the meager sort of "file manager" in the ROM doesn't work with the package installer.
d. You'll also need the Xposed installer app and the Fake GApps module which enables signature spoofing. I've attached both below.
e. Finally, you need the microG component apps. You can get them here: https://microg.org/download.html. You want Services Core, Services Framework Proxy, and Store. If you want to use Location services, you will also need the UnifiedNLP app.
The tools are now assembled!
f. Shut down your tablet and place the bootable SD card in the slot. Power up.
g. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery
h. Select Install. From the external SD card install xposed-sdk24-topjohnwu.zip
OPTIONAL
i. If you want to use Location services, also install mapsv1.flashable.zip
j. Remove the SD card and reboot. The process may take a little longer due to the new Xposed framework (first time only).
k. Transfer the apps you collected in steps d and e above to the internal Download folder. Use the root file manager you installed to install the Xposed installer app and the Fake GApps app. Open the installer app and check anything that needs checking then reboot. Check the installer app once more to see that the Fake GApps app has been installed and enabled.
l. Using the root file manager create the folder /system/priv-app/Phonesky. Set folder permissions to rwx-rx-rx. Use the root file manager to move fake "Store" app (com.android.vending-16.apk) into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
m. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core and Services Framework Proxy for this step). Reboot.
n. Check microG Settings to be sure spoofing is enabled and other permissions are granted. You don't need to enable any of the other Google stuff at this point unless you want to.
OPTIONAL
o. If you want Location services install the UnifiedNLP app then return to microG settings to configure (check regular settings for "Location" also--you'll see that the microG settings have been inserted into the general Settings app)
OK, you now have microG running at its lowest service level. Without doing anything else it should provide signature spoofing for apps that are looking for Google Services Framework. If you want higher levels of service (say, an actual Google account) you can make those selections in the settings. Generally, apps that require a Google account will call up microG to initiate a Google login (slow, but it works).
It is theoretically possible to run the PlayStore with the right configuration, but I would not recommend it. The Aurora Store (F-droid) runs really well on the device and can provide you with PlayStore access without GApps (or more demanding levels of microG service). You can use the anonymous login.
Calendar and Contacts will not sync with Google using microG. There's a lot of old stuff online about this working and how to set it up, but it does not work any more, so don't waste your time. If you MUST have synced contacts and calendar, you can use DavX (F-droid) (configuration--start with Calendar!) . Otherwise you can export a vcard file (*.vcf) of your contacts and load them in as a local set on the tablet. For a contacts app I extracted the Contacts.apk from a CM 13 ROM and placed it in /system/app/Contacts (permissions rw-r-r). Likewise the Calendar.apk in /system/app/Calendar. I've attached these apps below.
For email I tried using the AOSP client from a CM 13 ROM. The system recognized it but crashed on opening. Eventually I settled on an older version of K-9 mail (6.20). I had problems with Google 2-factor verification with the more current versions.
I've attached a screenshot of my system below. More discussion on individual apps and issues in the following post.
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues and app options.
Updated 2-16-23
Issues and Apps
Every custom (and stock) ROM has some issues. This one seems to have very few and they are easily addressed.
1. The stock browser is "broken", at least to the extent that it cannot save bookmarks.
Here's a fix for the bookmark issue. Use a root file manager to navigate to /system/app/BookmarkProvider. In that folder you will find an apk file of the same name. Tap to install (actually update, I guess). Then reboot.
A good alternative browser that works well with this ROM is Via.
2. The stock launcher is pretty basic. After a lot of fooling around with display and font size in Settings I found no combination that significantly affected the rather large (for my taste) icon size without otherwise distorting the display in some way.
I ended up restoring the display to defaults and installing Nova Launcher.
3. There's no Gallery?! Yep. For awhile I was using a Gallery from my old CM 10.2.1 install, but it didn't work very well. Then I discovered that @theportal2 had worked up a Lineage Gallery app with the necessary libraries for install on other ROMs. It works great and includes a ton of features, even photo editing. You can get it here: https://forum.xda-developers.com/an...lineage-os-gallery-apk-photo-editing-t3664460
4. The MTP file transfer setting in Settings>Developer options>Networking>Select USB Configuration is not effective and selecting it in Settings seems to encourage the MTP host to whine with system messages occasionally.
Leave setting on "charging" (default) and when you connect via USB, use the pull-down notification to select MTP transfer for that session.
Better yet, you can disable the MTP Host app with no apparent repercussions. Just go into Settings>Apps (show system) and disable it. I was sort of surprised that this had no effect on file transfer protocol.
5. The swipe-to-unlock screen is tenacious and its use may result in repetitive motion injury.
OK, so maybe this is a "feature?". If you touch anywhere on the swipe-to-unlock screen the little "Swipe to unlock" bounces up from the bottom. With that visible, the screen swipes effortlessly. Who knew?
6. The system throws up two notifications when you connect to USB (if you have debugging enabled). Just a minor annoyance. If you don't like seeing those two "N"s either, you can see just one (for the connection type: charge, transfer, etc.) with a simple addition to /system/build.prop:
Code:
persist.adb.notify=0
7. Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I recommend off-loading a copy and editing with something like Notepad++. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
Replace the file on the device with the edited version and reboot. This change will be overwritten if the app updates, so you might want to keep that in mind.
8. I am partial to the version of ES File Explorer which is attached to the first post. It's not too bloated and works well with the device, the package installer, etc.
9. Generally speaking I would gravitate toward older versions of apps which may be easier on the system. As an example, I'm using version 1.8.6 of MX Player, long before all the streaming nonsense took over. TuneIn Radio and Pandora are so old they will run on Android 2.1! Sometimes enough is just right.
Apps that don't work
1. The NPR News app currently in the PlayStore at this writing crashes repeatedly just after starting.
Version 2.6.1 works fine. Interestingly, when the PlayStore version installs, the icon background color is black. On another Nook Tablet (HD) running CM 11, the same version installs with a white icon background and runs fine. Version 2.6.1 also installs on this AOSP ROM with a white icon background. Hmm.
Xposed
Oh yes, even I eventually missed a feature or two from my last CM install The good news is that the Nougat version of Xposed runs well on this ROM, at least to the extent of using Gravity Box (I just had to have the extended power menu back.....)
Alternative apps for microG
I've included some of the more common ones (Contacts, Calendar, Email) in the previous post. If you've set up Location service you might want Maps. I've not had much luck with newer versions of Maps on my various devices. Too greedy for system resources. But I have found an older version of the app which still runs, includes Places, and allows you to cache map areas which do not expire.
YouTube is another real resource hog. I'm not a big YouTube fan, but there are times when I want something and a browser like Via or the stock one is so-so (it works, but you have to be patient). I looked around and decided NewPipe would meet most of my needs. It's not perfect. The full-screen player crashes on all the custom ROMs I've tried. However, you can set it to use an external player (like MX Player) and that works fine with full screen. I really like the ability to download videos (or just the audio) in a recognizable format--and even to the SD card!
And don't forget the Aurora Store (F-Droid) for PlayStore access.
nmyshkin said:
[shamelessly adapted from peerless instructions for other NT installs by @digixmax, and information from @mikeataol that is scattered through the CM 13.0 thread.]
Disclaimer: Neither I nor any other user mentioned here, real or imaginary, is responsible if you brick your device following these instructions. The only stupid question is the one you didn't ask right before you ruined your tablet.
By following these instructions you can install an AOSP Android 7.0 ROM from @amaces internally (into emmc) on a 16 GB Nook Tablet running either stock, CM 10.x, CM 11.x, CM 12.x, or CM 13.x, assuming you have done no special repartitioning (it may also work if you have done special repartitioning, but I do not know). If you have previously installed CM 14.x and have repartitioned, you can return to those installation instructions where there may be a description of how to revert to the regular partitioning. This ROM does not require any special partitioning.
The AOSP ROM is a bare-bones, very responsive build. It runs rings around my former CM 12.1 install without any freezes or shutdowns. Adding a pico Google Apps package keeps the ROM mean and lean while giving you PlayStore access to add just what you want.
If you have a bootable SD card made for installing CM 10.x-12.x, you can skip to step 2b.
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, set the partition ID type for the partition to 0x0C FAT32 LBA, and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
d. the zip file of the AOSP Android 7.0 ROM by @amaces, i.e., aosp_acclaim-ota-NBD90Z.161020.zip from my Dropbox: https://www.dropbox.com/s/b7zc8d56z2gl69m/aosp_acclaim-ota-NBD90Z.161020.zip?dl=0 (alternative link provided by @mikeataol: https://mega.nz/#!nQwiEILS!dm7i-4AOUzYW5yP0LaqcZ5EAUsxeh-Qr8DULB4BGYZ8) [this ROM is no longer in the repository maintained by @amaces]
e. the zip file of the Gapps package (corresponding to Android 7.0) from http://opengapps.org/
3. Put the SD card into the NT and boot from its power off by inserting a powered USB cable. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display.
a. Select SDC Recovery.
b. [Optional step but highly recommended] Select Backup to backup your NT current ROM config (/boot, /recovery, /system, and /data).
c. Return to TWRP opening screen and select Install. From the external SD card install flashable_TWRP_3.0.2-0.zip
(my experience with TWRP is that it is very cranky, at least on my tablet; if you have trouble with it not recognizing the external SD card, try rebooting into recovery again....or again....)
d. Reboot. Press and hold the "n" button as soon as CyanoBoot comes up to get the boot menu to display. Select Internal (emmc) Recovery (note that from here on all installation is done using the internal TWRP 3.0.2-0)
e. Select Wipe (data & factory reset) OR, using Advanced Wipe, wipe system, data, cache, dalvik.
f. [Optional] Select Advanced Wipe, Repair or Change file system; select "data" (only) and change file system from ext4s to f2fs (supposedly a faster format--if you decide to undo all this, you should probably reformat "data" to ext4s)
g. Reboot to internal (emmc) recovery as in 3d. (ignore warnings about "no system" if you see any)
h. Select Install. From the external SD card install aosp_acclaim-ota-NBD90Z.161020.zip (ignore E: unknown command errors)
i. Reboot to internal (emmc) recovery as in 3d.
j. Select Install. From the external SD card install appropriate opengapps zip
k. Remove SD card and select reboot.
Wait for first boot to complete and sign in. To fully enable root access for ADB and apps you must install the opensource version of the SU interface from the PlayStore: https://play.google.com/store/search?q=phh superuser&c=apps. Search for "phh superuser".
Done!
[Don't you want to make a baseline backup right now?]
My thanks to @digixmax for his many, many excellent how-to's and for the help he has given me in the past. He is also responsible for providing the flashable TWRP that avoids the need for fastboot in this install. I'm grateful to @mikeataol for his patient responses to my probably lame questions in the CM 13.0 thread concerning this ROM and, of course, really thankful that @amaces turned out this excellent version of AOSP Android 7.0 for our devices.
See post immediately below for a discussion of known issues.
Click to expand...
Click to collapse
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
ehtisham ali said:
I have cm 11 installed with 12 gb system and 1 gb media partition . and twrp 2.8.6... Installed . can i flash rom and g apps straight away ? Without foolowing other instructions
Click to expand...
Click to collapse
You can try, but I think you'll need to update the internal TWRP at least.
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
nsfgp said:
Is anyone able to install any of the recent AOSP/LNOS builds of Amaces on a 16G NT that still uses the original partition format PLUS any recent opengapps TOGETHER successfully???
For me any builds from Amaces since 2017 can install successfully ... BUT ran out of /system space after that and cannot install OpenGapps. I use/tried PICO opengapps only always.
When I open file manager from TWRP 3100 there is nothing inside /system .... so was not able to clean up anything inside ....
Amaces: If you see this can you please help?? I know your focus is on the Ovation (I use it too) but I really want to try your LNOS for the NT on my original partitioned one.
Just FYI on the 16G NT that has the newer CM14.1 repartitioned format -> None of Amaces' ROM for Acclaim can install. Can only use dmarble's new LNOS builds or the old remaining CM14.1 builds on those.
If anyone has a good and easy solution to get around the /system out of space issue to install Gapps please share. I want to keep one acclaim on the original partition format. My other acclaim is running dmarble's ROM happily.
Click to expand...
Click to collapse
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
mikeataol said:
Yes, have done many times.
make sure you have mounted /system in TWRP
Try a reboot after ROM install, and before gapps install.
The latest LNOS in experimental (lnos_acclaim-ota-N2G47E.170416) installs a fresh pico gapps of about 80MB with no manipulation.
in the past if I have had to make room, I copy and delete /system/media to /emmc before gapps install, and copy it back after
Click to expand...
Click to collapse
Thank you Mike!!! It is the /system mounting .... I never thought it would have to be mounted .... since it complaint not enough space instead of not found/mounted. But anyway .... I mounted /system in TWRP after ROM install+reboot into recovery. Now I can see stuff inside /system.
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Do I really need those stuff in /system/media and have to copy it back?? If no use I want to keep it lean.
Thanks again!!! (I am using the exact LNOS ROM in A's experimental folder as you mentioned)
Just a heads-up that I don't actually have the hardware, so everything that I upload for acclaim is not really tested, but I try to not to break things.
nsfgp said:
But it still complaint about not enough /system space and cannot install Gapps. I just copied off /system/media and deleted it. And now the Gapps installed ok. I am rebooting into LNOS now.
Click to expand...
Click to collapse
I'll put something like this on the list, so a larger /system (upstream Lineage, or via REPIT) is usable with these builds (Lineage/AOSP would still need manual resize).
So far this build (7.0) works much better than 6.0. Thanks!
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
killerkalmah said:
Hi, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
killerkalmah said:
Hi, thank you very much for the tutorial, I have followed the guide step by step but I can't get the tablet to boot the cyanoboot, I turned off and plug the power cable from the adapter and it boots normally, my tablet model is BNTV250 16 GB version, runing stock OS and it has not been rooted before or anything, I have tried flash the sd with older methods in order to root it and haven't had any success, that's how I ended up here, I'm using an 8GB trascend sd card, the Tablet detect the sd card since I can see the files in the tablet browser but I can't get it to boot the cyanoboot or anything else, can someone assist me? thank you very much in anticipation.
Click to expand...
Click to collapse
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
mikeataol said:
there is a certain percentage of Nook tablets that wont boot from a card unless you power down, insert the card, then power up by inserting the USB cable, not by pressing the on/off switch. (about 15% of nooks I've seen are like this)
if even that doesn't work, you should make another card . Class 4 is best, faster isn't better in this case.
Click to expand...
Click to collapse
That's they way I've tried, inserting the USB cable, the sd is class 4 indeed, so I don't know what it could be.
nmyshkin said:
If the tablet won't boot from the SD card it's likely that there is either something wrong with the boot files, i.e., those files first placed on the card in step 2a, or with the formatting of the card (step 1). You might want to download a fresh set of files and try making the card again. Corrupt files will make this task impossible.
It's also possible that your particular SD card just won't do it. It's been known to happen.
Click to expand...
Click to collapse
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
killerkalmah said:
Is it possible that the SD card can be read it, explorer and formated from the tablet and unable to do the boot? cuz the tablet appear to recognize evrything on the SD
Click to expand...
Click to collapse
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
nmyshkin said:
Unfortunately, yes. I'm not saying your card is defective but this whole business of booting from the card contains a minor but distinct element of voodoo
So....download those files from step 2a again, reformat the card (again....), and prepare it as before (again....). If it still does not work, I'd look for a different card to try this process. Don't be discouraged. I did a lot of "again..." when I first did anything like this. It will work for you.
Click to expand...
Click to collapse
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
killerkalmah said:
I downloaded those files again, re-do the sd card and prepare it again, it still don't boot lol
This is the link I'm following for the TWRP image; https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img, i don't know if I have to use that or the one that comes in the suculent boot folder?
Another thing is that I've been using an SD card adapter and have tried trough the nook too, and also downloaded the mini gaaps file for android 7 ARM, but I'm pretty sure that has nothing to do with the boot stuff, so I'm gonna fallow your suggestion and try with an old 1 gb or 2 gb card, and see what happens, everything related on formating the SD via partition tool mini has done correctly, my Internet security blocks a menace while I attemp to download the files from media fire, you think that could be corrupting the files? I get the download and the menace blocked by Iinternet Security so I'm not sure, if you have any other suggestion I will be glad to read, meanwhile I will search for those damn cards, and I can't thank you enough for you time helping a noob here! thanks!!
Click to expand...
Click to collapse
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
nmyshkin said:
You are downloading the correct TWRP. The other one is too old. I don't know about any warnings from MediaFire. I just downloaded the succulent_boot.zip myself and saw no warnings, but that may be browser/configuration dependent. I'm using Firefox with a double layer of ad-blocking.
Generally speaking you want to download the files on your PC, then insert the SD card into the adapter, into the SDHC slot, and do all the work on the PC before inserting the card into the tablet.
If you have a way to verify the MD5 checksums of your boot files (winmd5free), this is what I get:
MLO: 979fa71c9ee33ca9690df809c71e1991
u-boot.bin: 1070cd90b3d57a47cdc8c22b00243ff7
flashing_boot.img: 3a626c102ef4324a163d54751ef680f1
I think you might run into size issues with the mini GApps.
Click to expand...
Click to collapse
Alright! I found 3 sd cards each of them with a 2gb capacity, that should the incompatibilty, each three are different brands, and I found a better SD adapter, I will re-do all the steps in building the SD and if that does not work will download the files again with jdownloader to avoid menace pop outs, and if that doesn't do I will check the MD5 :fingers-crossed: I will update here, and thank you again!.
Update: it was the SD, I manage to do all the steps except for the gapps file, I couldn't install it, which you will recomend to download, I download the ARM android 7.0 mini, and more importantly my tablet loops on the "android" screen, with or without the SD inside, am I missing something? I did not installed supersu even though I got asked a few times during tutorial, any suggestion?
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
nosborm said:
Have you tried clearing the cache? That worked for me the first time I did this.
Also, which OS image are you using? When I tried to reinstall a newer version mine would not boot after copying gapps over, presumably due to space.
Click to expand...
Click to collapse
I'm a little bit lose regarding memory space on this tablet, I reinstall the OS that was in this tutorial and finally booted to menu, but I can't connect to wifi, I don't know why, I might install another OS, which gapps file you reccomend to download? the stock, full version or mini?