New Users - Read First ! ! ! - Barnes & Noble Nook Tablet

( moderator please consider pinning this post )
You can mess up your tablet "IF" you do some wrong steps. Wish to list terse ( one line ) bullets to make it direct. There are other post that lay out the details.
The forum has a VERY nice search function. It is silly not to take advantage of it.
==================================================
1) Do not put cm7.2 'internal' upgrade on the 8GB units ! Fixed ! ! ! !
2) Do not load Chainfire3D drivers on your cm7.2 . . . . . this one killed me !
3) Using cm7.2 'external' on 8GB and 16GB units will not touch the nook's original os.
4) Using the 'Ubuntu - total wipe & re-flash' will erase your 'serial number' and 'deviceID'. Fixed ! !
5) Recoveries can and will FAIL if you have a damaged partition table.
6) Some sd card's brands ( Lexar ) and classes ( 10 ) will work poorly ( or not at all ! ) in your nook as your external os.
7) Always flash on a full battery.
8) Always format your sd card ( first ) with fat32. . . . . ( sdformatter v3.0 )
9) Side loading will not work until you turn 'on' unknown sources in settings \ applications.
10) Display is easily the #1 battery drain... Want it to last longer, dim the display.
11) Loading in 100+ apps will only take away one third of your ( app ) storage. . . . . typically, your mileage may vary
12) Your nook will not charge if turned 'on' and using your phone's charger.
13) Key app in GingerBread / cm7.2 - app2sd is not available / usable in ICS / cm9.
14) OTA stands for 'Over The Air' - B&N is sending your ( stock ) unit an update.
15) The devs need to fix tough problems, so please don't post in their area.
16) Rooting your stock NT does NOT block OTA's.
17) Take note of apps with "HD" in their title. They require h/w accelleration ( which we do not have working yet )
18) If its 'off' but the back lite is still 'on' then it is hung.
19) One possible way to get it out of a hang is to: press and hold the 'N' button and the 'Volume Up'. Now in addition, press and hold the power for a count of ten and let go.
20) Always backup before trying something ( anything ! )
21) Turn 'off' unknown sources when you don't need it. New virus uses unknown sources to infect your tablet.
22) CM9 is in 'alpha' for 16 and 8GB units. Please don't load unless you understand the risk and know how to back it out.
23) Ad-hoc tethering works ! Must apply a wpa_supplicant fix via adb to your rooted nook
24) Use a partition manager to resize your booting sd and regain the unused space on the card. ALERT ! Danger ahead !
25) Windoze 7 people have to remember to 'right click' and then 'run as administrator' .
26) cm9 will quit working on purpose. http://forum.xda-developers.com/showpost.php?p=25478233&postcount=446
27) the b&n usb cable is "special" and plugs "deeper", which is required for charging.
28) the microphone is NOT working for a lot of people with cm7 & cm9. devs will fix... soon...
29) if your stock nook says software version 1.0.0 ... it is not OTA blocked. ... Heads up !
30) Connecting useful items to usb is called "usb hosting", which is NOT working yet.
31) Never trust a big download. ( especially if its slow ) Use md5 crc checksum to validate the integrity.
32) You can clean up your 'Dalvik cache' in Titanium Backup, goto menu / more.
33) if you're ONLY interest is reading books then the 'rooted' stock 'os' is best. do not install cm7 / cm9 ( yet ! )
34) when given the choice between App Installer, and Packaging Installer, always choose the second.
35) for cm7, an error has been reported in the build.prop file that results in emmc not mounting when connected to a PC
36) want to see what's going on with your memory/partitions ? get 'free' app "Storage Analyzer" to see internal and external !
37) asked to make a logcat/dmesg report ? get/use free app, 'Voodoo Report'. you can reboot and mail it to yourself.
38) turbo prop tweak : http://forum.xda-developers.com/showthread.php?t=1684997

Yeah good idea i have think about doing this because im really getting tired of repeat things over and over again but you beat me to it . You get my thanks.
~ Veronica
Sent from my Nook Tablet using xda premium

old_fart said:
( moderator please consider pinning this post )
You can mess up your tablet "IF" you do some wrong steps. Wish to list terse ( one line ) bullets to make it direct. There are other post that lay out the details.
==================================================
1) Do not put cm7.2 'internal' upgrade on the 8GB units.
2) Do not load Chainfire3D drivers on your cm7.2 . . . . . this one killed me !
3) Using cm7.2 'external' on 8GB and 16GB units will not touch the nook's original os.
4) Using the 'Ubuntu - total wipe & re-flash' will erase your 'serial number' and 'deviceID'.
5) Recoveries can and will FAIL if you have a damaged partition table.
6) Some sd card's brands ( * ) and classes ( 10 ) will work poorly ( or not at all ! ) in your nook as your external os.
7) Always flash on a full battery.
8) Always format your sd card ( first ) with fat32. . . . . ( sdformatter v3.0 )
9) Side loading will not work until you turn 'on' unknown sources in settings \ applications.
10) Display is easily the #1 battery drain... Want it to last longer, dim the display.
11) Loading in 100+ apps will only take away one third of your ( app ) storage. . . . . typically, your mileage may vary
12) Your nook will not charge if turned 'on' and using your phone's charger.
Click to expand...
Click to collapse
My mileage differs on #4. If you boot recovery afterwards your sn, deviceid, mac address, etc return. I have used this numerous times and still have all my stock info as when I took it out of box.
Maybe whatever happened that caused you to use this restore method caused you to loose your info or maybe I'm just lucky!

Hey old_fart or anyone with 8GB version NT,
Since I don't have an 8GB version, can you test something for me?
meghd00t told me this, MLO and u-boot are the only ones that will pass the correct cmdline to the kernel to tell it about the 512 RAM on the 8GB units.
I want to see if flashing the MLO and u-boot from 1.4.2 fix this problem.
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Click on flash_u-boot_and_MLO.zip, view raw to download the zip and flash it. Then flash CM7 Alpha Final and see if it work. If not, my pre-built rom.
You can't brick your NT by doing this since it's the same files from BN update.

succulent said:
Since I don't have an 8GB version, can you test something for me?
Click to expand...
Click to collapse
sorry, i too have the original 16GB model.
.
ahh, what's an MLO ? ( x-loader ? )

old_fart said:
sorry, i too have the original 16GB model.
.
ahh, what's an MLO ? ( x-loader ? )
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://omappedia.org/wiki/Bootloader_Project
MLO is signed x-loader that load the bootloader (u-boot).

bump, new stuff learned and so added to the list...

old_fart said:
bump, new stuff learned and so added to the list...
Click to expand...
Click to collapse
ditto

added a couple new ones.

Changes to reflect the "NEW" cm7 beta compiled by CelticWebSolutions. It's really great that he has ( once again ) donated his expertise and did the hard work for the benefit of the group. Bravo Zulu !
.
Now let's clobber the cm9. Beat it into submission...

Great info. Thanks.

It was posts like this one that helped me to learn enough about the NT to allow me to root, add CM7, modify the build prop, etc. We noobs really do read these posts and we appreciate them. Thank you.:good:

I got a deal for the 8 gig for 80 bucks, I also see on frys they have the 16 gig for 105 shipped... what's the better deal and bargain? I just want to throw ICS on it and have a decent cheap tablet.

better late than never and for all those asking the same question
sah0724 said:
I got a deal for the 8 gig for 80 bucks, I also see on frys they have the 16 gig for 105 shipped... what's the better deal and bargain? I just want to throw ICS on it and have a decent cheap tablet.
Click to expand...
Click to collapse
Well the difference there would be the ram the 8gb has 512 Mb of RAM and the 16 gig has 1024 Mb of RAM. I have used both, owning the 8gb and working on my friends 16gb and the real difference is the 16gb loads a little faster, maybe 10 secs faster at most over the 8 gb and also I hate to say it but a little smoother gameplay. if it were me, at those prices I would spend the extra $25, see I was one didn't want to wait and went and bought it at B&N, regrettably.
As for putting ICS on it, there are ways for both tablets, most are compatible with each other, but just double check to make sure as you can severely mess things up if you do not use proper avenues of approach. Not to worry though, if you do, once again there are many way out there to fix it if you do. Well HoPe this helps any and all who wonder!

I recently picked up a Nook Tablet 8gb version second hand. I have been toying with the idea of rooting and adding CM10 to try to get more out of it. I was wondering how hard this process is and if its really worth it.

TheAndroidN00BIE said:
I recently picked up a Nook Tablet 8gb version second hand. I have been toying with the idea of rooting and adding CM10 to try to get more out of it. I was wondering how hard this process is and if its really worth it.
Click to expand...
Click to collapse
It's not that hard and is absolutely worth it. See http://forum.xda-developers.com/showthread.php?t=2575489 for info/pointers.

Related

[DISCONTINUED][RAM] darkstone SuperRAM FroYo v1.5 [kernel: Hastarin custom]

leepriestenator said:
MODERATOR WARNING!
All of us here are ecstatic that DS is back. This new Build marks the next level in Android Development for WinMo phones. It's a very exciting time but there are a few things we all need to keep in mind.
1) No THANK YOU Posts. Anyone found doing so on high volume threads will be given as infraction. We have implemented a new THANKS button here at XDA. Use that to convey your gratitude.
2) The first few pages of this thread have already informed us of this build being incredibly fast. Everyone knows it now which means NO more "This is so FAST!" posts.
3) There are several issues with this build, which have come to light over the last 30 pages. Check to see if your problem has been listed (Chances are that 999 out of 1000 are already listed). If it is, then you are not allowed to post asking for a solution to the same problem.
4) STRICTLY NO REQUESTS!
Any discussions in this thread have to be limited to the build provided here. No discussions and arguments about the pros and cons of Sense Builds.
5) NO asking for ETA of the next build.
Any deviation from the above will result in an Infraction.
Click to expand...
Click to collapse
---------------------------------------------------------------------------
------------------------------------------------------------
SuperRAM FroYo by darkstone1337
Version 1.5
Release: 18-December-2010
Thread: http://forum.xda-developers.com/showthread.php?t=870518[/SIZE][/U][/B]
------------------------------------------------------------
Click to expand...
Click to collapse
------------------------------------------------------------
If you don't know anything, SEARCH GOOGLE FIRST.
------------------------------------------------------------
What is SuperRAM FroYo?
- It is an AOSP rom with some modifications added, but kept as close to stock as possible. The only thing that is modified is the keyboard, some menu options and the launcher.
What is special about this build?
- What is special about this build is that the entire Android O/S filesystem is stored in RAM before it is booted.
What does this mean?
- Well, RAM is faster than NAND(ROM) and SD Card which in turn will make the build superfast too! Very fast. Very very fast!
I don't understand what NAND(ROM) or RAM is!
- NAND is a slower memory type (ROM) which is designed to hold data even after the phone is turned off. This is where your Windows Mobile operating system is stored.
- RAM is a much faster memory type which is designed to hold information on a temporary basis. After your phone is turned off, the data in RAM is lost.
- Running Android on your HD2 does not touch your ROM in any way! So when you turn off the phone and turn it back on, Windows Mobile will be loaded. No changes are made to ROM.
Does this mean I'm going to lose the stuff that I put in Android when my phone goes off or crashes?!
- NO. Only the operating system files for this build will be stored in RAM. User data and downloads will be saved to your SD card in a special file called data.img
- Remember if your phone crashes in Android, nothing will affect your Windows Mobile operating system since this build runs off RAM.
What other advantages does this build have?
- Unlike normal builds which are ran from the SD card, this build will not stress your SD card nearly as much. This will allow faster transfer speeds and less chance of data corruption.
- Battery usage will be less than SD card based builds as the operating systems files will be accessed from RAM instead of the SD card.
- Quick android boot!
Something isn't working properly!
- First of all check the build thread by SEARCHING FIRST to see if there is a solution to your problem or if it is already listed as a known issue. If there is no solution and the problem has not been posted by someone else, ONLY THEN should you post here: http://forum.xda-developers.com/showthread.php?t=870518
- Please include details about the issue, such as how to replicate the problem.
Click to expand...
Click to collapse
------------------------------------------------------------
Installation and Setup:
Make sure that you do not have another Android folder on your SD card. If you do, then either rename the folder or back it up to another location and delete the folder.
Copy the folders named Android and media to the ROOT of your SD card. If you don't know what the root of the SD card is, look here: http://uk.answers.yahoo.com/question/index?qid=20080521052942AAMW3kA
On your HTC HD2, use file explorer to browse to the Android folder on your SD card. Run the program CLRCAD.EXE (nothing is supposed to show up when you run this program.). Then run haret.exe.
You will now see a green HTC logo on a black background for a couple of seconds, then you will see nothing but a blank screen for a couple of seconds.
After this, you will see the android unlock screen. Unlock the lock screen and go through the setup wizard. After this is done, import your SIM contacts if you have any.
To do this, open the Phone app, press the Contacts tab, then press the Windows hardware button on your HD2 and select Import/Export. Select Import from SIM card. From here, press the Windows button again and select Import All.
If you do not see your SIM contacts then follow the instructions below:
*****************************************************************************
If you are using an existing data.img then you will need to delete the one that you are currently using, and copy over a fresh data.img that is included with this build. If this is your first time booting this build, then this does not apply to you.
- Open the phone app and dial this code in: *#*#4636#*#*
- You should now see a list of menus, choose the one named Phone information.
- Scroll down to the bottom of the page and press the 'Turn off radio' button. Wait for your signal to drop.
- Now press the 'Turn on radio'. Wait for your signal to be restored.
- Now change 'Set Preferred Network Type' to GSM/CDMA auto (PRL).
After doing this, return to the home screen (press the Home hardware button on your HD2) then open the phone app again and follow the instructions on how to import your contacts as described earlier.
YOU CAN ONLY DO THIS ON YOUR FIRST BOOT. YOU MUST KEEP THIS IN MIND.
*****************************************************************************
- After importing your contacts, you MUST reboot your phone. If you do not do this, then your data connection will not be enabled.
- Hold down the end call hardware button and select Reboot.
- You will now boot back into Windows Mobile. Run CLRCAD.EXE and haret.exe as described earlier to load Android.
After this, the installation is fully complete and you can now start using Android.
Click to expand...
Click to collapse
------------------------------------------------------------
Notes:
- I have included a 256MB data.img, however you can use any size that you wish if you have your own data.img.
- I highly recommend starting with a new data.img regardless of whether you have used this build previously. There is some changes that may conflict with your current image.
- If you wish to make changes to the build, use the file structure in Android/root/ on your SD card to put your modified files in. They will be copied upon boot. Do not worry if they are not deleted, this is normal.
- After your first boot, make sure to delete the DATA folder on your SD card. It is stored under Android/root/data.
- If you plan to reinstall the build again, make sure to copy back this folder from the ZIP file.
- Robot voice issue may occur when in a call. If this happens, during the call press the LOUDSPEAKER button then END THE CALL. Do this exactly and every call after will no longer have this issue.
- You are left with around 280MB+ free RAM after booting the build. This is enough memory for anything!
- Build.prop is easy to modify, I have included a copy in /Android/root/system on the SD card. Modify this as you with and your changes will be copied over upon the boot of Android. If you mess something up, just delete the file and the changes won't be applied upon next boot. This goes for any file you put in the Android/root/ folder.
- I'm not going to be like other chefs and say "THE BATTERY LIFE IS EXCELLENT I PROMISE" etc. Everyone's setup is different, just test the build for yourself!
- Forget quadrant scores! If you're judging this build by quadrant scores then I pity you. This type of build is different from other builds, yes the quadrant scores may not be in the 2000+ range, but honestly, can you actually say to me that this build is slower than other builds that have a higher score? I sure hope not.
- To delete LauncherPro just uninstall it from the Application Manager! Before you do this, make sure you install another launcher such and ADW Launcher or Gingerbread launcher which can be found from the Market free of charge.
- If you want to remove ads, this is very easy.
- Download this adfree hosts file: http://gamesquare.co.uk/hosts.zip (COPY AND PASTE THIS LINK IN YOUR BROWSER.)
- Unzip this file to the /Android/root/system/etc folder on your SD card. Boot into Android and there will be no more ads.
Click to expand...
Click to collapse
- The base rom is from AdamG's OxygeN Desire rom which has been modified by myself.
- The initrd and CSSync updates is based on that from cedesmith. However, I've modified the initrd for my own build.
- The PPP wrapper update is from LeTama's thread, version 0.7
- The HaRet loader is custom made by NetRipper, thanks to him for helping me increase the initial ramdisk size limitation!
For developers only:
- The kernel included is hastarin's r8.6 eb_oldcam kernel, this has been modified for my build!
- Kernel source: http://www.gitorious.com/~hastarin/linux-on-wince-htc/hastarins-linux_on_wince_htc
- Patch: http://pastebin.com/6qjkb4Hh
Click to expand...
Click to collapse
------------------------------------------------------------
Bugs Fixed in version 1.5:
- Data corruption fixed (framework force close)
- App compatibility increased (skype, drocap2, other apps should now work)
- SIM contacts fix (read above on how to get SIM contacts on your phone if you do not see your contacts)
- Camera app force close on settings now fixed
- Wifi tethering now working (use the Wireless Tether app included)
- Unable to remove LauncherPro is now fixed, I've moved the launcher to /data (read above on how to change launcher)
- UI sounds should now work for everyone
Bugs Remaining:
- Notification LED's only blink once
- SetCPU unable to change CPU speed (not that I think that theres much need to do this anyway)
- Possible PPP data issues for some people
New Features:
- Gingerbread keyboard now has a multi-language auto-complete dictionary (access this in keyboard settings and choose your language)
- Added RTL support (thanks to Ambious for his modified framework file!)
- Updated to Google Maps v5
- Added Astro file manager
Click to expand...
Click to collapse
------------------------------------------------------------
Thanks to everyone at #htc-linux, #htc-linux-chat and at xda-developers for your help, guidance and support!
Thanks to my beta testers! Thanks to Hastarin for pointing out the toolchain issue which cases high power usage in sleep!
The first boot will take under a minute, subsequent boots will take much less time.
I am running HTC HD2 Stock rom 3.14.405.2.
My radio is 2.15.50.14, I have NO robot noise issue with the combination.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
^ Home screen - Keyboard ^
^You^
Download here: http://www.multiupload.com/01Q9CDT76Y
UPDATE:
Apply this patch to prevent data corruption. If you already using this build, use a new data.img (any size) after you apply this patch.
crawlingcity said:
http://www.mediafire.com/?ebwijry3m9k6p3u
posting this initrd on darkstone's behalf. fixed corruption. rename it to newinitrd.gz
Click to expand...
Click to collapse
UPDATE:
Follow these instructions if you have higher battery drain!
DarkStone1337 said:
Lets see how many people will ignore this...
To fix high power drain / usage in standby (60mA or 70mA) disable 'Use wireless networks' in Settings>Location menu. You will now get 7mA or less constantly. I discovered this as the main culprit last night. Also works in other builds.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Code:
V1.2 Beta - old
http://www.multiupload.com/IO59N57MG0
Kernel update: http://www.multiupload.com/2G8LKSNZF6
V1 - old
[URL]http://www.gamesquare.co.uk/?p=478[/URL]
MIRROR: [URL]http://hamid29.s73.rapidbaz.com/premium/49b2df8acc9fae5467b31e3814faf34d/4d05db44/s73.eu./8523299?SuperRAM_Froyo_v1.7z[/URL]
​
New Darkstone build is beating 28sec on boot, and 2100 on quadrant without any tweat!
the super hero is back, and much strong!
thank you sir!
renna1992 said:
is this build multi language?
Click to expand...
Click to collapse
Yes it is!
Oh my god... it's really unbelievable fast!! really thunderbolt!!
Many thans darkstone for your hard job. Nice to test any new build from you.
to go to your site i have to fill out a survey first or play a game on a website riddled with viruses? really?
Since its aosp its sense-free? (hoping) anyway ..this must be a must have!! Will try soon and do some testing . Oh and darkstone..welcome back
As said on IRC: build works awesome. Quadrant scores even get higher after you boot for the second time. Keep it up!
molesaied88 said:
to go to your site i have to fill out a survey first or play a game on a website riddled with viruses? really?
Click to expand...
Click to collapse
Viruses, surveys? I've just put ads up to cover server costs
I never put up any virus or survey
But if you're loading entire file system in RAM, it would reduce free RAM that we get after boot? How much free ram we get with it in compare to normal builds? How big entire system for android is?
Download size is 78mb, so I assume it would take about 78mb out from RAM?
Great Work !
will see if you able to put the amazing cedesmith desirehd rom away from my phone.
molesaied88 said:
to go to your site i have to fill out a survey first or play a game on a website riddled with viruses? really?
Click to expand...
Click to collapse
Yeah - just like you said, straight away got a full screen pop-up ans when I tried to click out of it my AV kicked in immediately with a security warning. Not a very friendly ad provider
Like he says, it boots insanely quickly after the initial boot.
Very nice AOSP build.
chrisnash said:
Yeah - just like you said, straight away got a full screen pop-up ans when I tried to click out of it my AV kicked in immediately with a security warning. Not a very friendly ad provider
Click to expand...
Click to collapse
OK! Ad removed, sorry about that, I'll need to have a word with my ad provider
I'll add screenshots soon folks!
Thanks Darkstone,
This build is fast, very fast indeed.
Boot time is the fastest thing i've seen so far.
However i do get robot voice and i can't seem to get rid of it.
Using OzDROID ROM 2.00 with 2.15 radio
few questions:
how much ram is left for running applications ?
is there all of changes made by me in system (install apps, changing settings) will save anywhere ?
is this build for normal daily use good ? Or keeping android in ram making some limitations ?
DavidX_07 said:
few questions:
how much ram is left for running applications ?
is there all of changes made by me in system (install apps, changing settings) will save anywhere ?
is this build for normal daily use good ? Or keeping android in ram making some limitations ?
Click to expand...
Click to collapse
Ram is usually 240mb+ available after boot, don't worry about that, it's plenty!
Changes to /system won't be saved since android is loaded into ram. If you want to make permenant changes, you can either modify the system file in linux and rebuild the file. Or you can can create a file structure in the Android folder on your sd card and create the folders named Root, Update.
Insert the files you want changing in there and create an update script. The changes will be made upon every boot as long as you have the files stored on your SD card
Your settings and apps are stored to SD card, so all your changed made in Android via normal usage will be saved
Don't mean to be pushy..but are there any plans of a sense version of this build
I don't like stock froyo much and if yes, I will hold out till its released
jan-willem3 said:
The real advantage of this is the boot speed.
The rest of the speed is produced by the intret.gz from cedesmith or am I wrong.
Click to expand...
Click to collapse
No not only boot speed, the build is faster overall as it is stored in ram and not on the SD card. Therefore, your SD card will be less stressed, will have more speed available to be used when reading/writing files.
I have HSPL 2.08 and 3.14 ROM, well this gives some problems with low RAM(?) or something. Does that mean that this android rom will run slow(er) as well?
hey im glad you are back Darkstone... but can you display more information about the build...like....
-how to install it
-whats working
-whats not working
-battery life?
-put pictures
-does it have Widgets?
and some other information??
thanks!!

[DISCONTINUED][RAM] darkstone SuperRAM Sense v0.1 [kernel: Hastarin EB]

leepriestenator said:
MODERATOR WARNING!
All of us here are ecstatic that DS is back. This new Build marks the next level in Android Development for WinMo phones. It's a very exciting time but there are a few things we all need to keep in mind.
1) No THANK YOU Posts. Anyone found doing so on high volume threads will be given as infraction. We have implemented a new THANKS button here at XDA. Use that to convey your gratitude.
2) The first few pages of this thread have already informed us of this build being incredibly fast. Everyone knows it now which means NO more "This is so FAST!" posts.
3) There are several issues with this build, which have come to light over the last 30 pages. Check to see if your problem has been listed (Chances are that 999 out of 1000 are already listed). If it is, then you are not allowed to post asking for a solution to the same problem.
4) STRICTLY NO REQUESTS!
Any discussions in this thread have to be limited to the build provided here. No discussions and arguments about the pros and cons of Sense Builds.
5) NO asking for ETA of the next build.
Any deviation from the above will result in an Infraction.
Click to expand...
Click to collapse
---------------------------------------------------------------------------
------------------------------------------------------------
SuperRAM Sense by darkstone1337
Version 0.1
Release: 30-December-2010
Thread: http://forum.xda-developers.com/showthread.php?p=10180198[/SIZE][/U][/B]
------------------------------------------------------------
Click to expand...
Click to collapse
------------------------------------------------------------
If you don't know anything, SEARCH GOOGLE FIRST.
------------------------------------------------------------
What is SuperRAM Sense?
- It is a Sense rom with some modifications added, but kept as close to stock as possible. The only thing that is modified is the keyboard, camera and some icons.
What is special about this build?
- What is special about this build is parts of the Android O/S filesystem are stored in RAM before it is booted.
What does this mean?
- Well, RAM is faster than NAND(ROM) and SD Card which in turn will make the build superfast too! Very fast. Very very fast!
I don't understand what NAND(ROM) or RAM is!
- NAND is a slower memory type (ROM) which is designed to hold data even after the phone is turned off. This is where your Windows Mobile operating system is stored.
- RAM is a much faster memory type which is designed to hold information on a temporary basis. After your phone is turned off, the data in RAM is lost.
- Running Android on your HD2 does not touch your ROM in any way! So when you turn off the phone and turn it back on, Windows Mobile will be loaded. No changes are made to ROM.
Does this mean I'm going to lose the stuff that I put in Android when my phone goes off or crashes?!
- NO. Only the operating system files for this build will be stored in RAM. User data and downloads will be saved to your SD card in a special file called data.img
- Remember if your phone crashes in Android, nothing will affect your Windows Mobile operating system since this build runs off RAM.
What other advantages does this build have?
- Unlike normal builds which are ran from the SD card, this build will not stress your SD card nearly as much. This will allow faster transfer speeds and less chance of data corruption.
- Battery usage will be less than SD card based builds as the operating systems files will be accessed from RAM instead of the SD card.
- Quick android boot!
Something isn't working properly!
- First of all check the build thread by SEARCHING FIRST to see if there is a solution to your problem or if it is already listed as a known issue. If there is no solution and the problem has not been posted by someone else, ONLY THEN should you post here: http://forum.xda-developers.com/showthread.php?p=10180198
- Please include details about the issue, such as how to replicate the problem.
Click to expand...
Click to collapse
------------------------------------------------------------
Installation and Setup:
Make sure that you do not have another Android folder on your SD card. If you do, then either rename the folder or back it up to another location and delete the folder.
Copy the folders named Android and media to the ROOT of your SD card. If you don't know what the root of the SD card is, look here: http://uk.answers.yahoo.com/question/index?qid=20080521052942AAMW3kA
On your HTC HD2, use file explorer to browse to the Android folder on your SD card. Run the program CLRCAD.EXE (nothing is supposed to show up when you run this program.). Then run haret.exe.
You will now see a green HTC logo on a black background for a couple of seconds, then you will see nothing but a blank screen for a couple of seconds.
After this, you will see the HTC Sense unlock screen.
Click to expand...
Click to collapse
------------------------------------------------------------
Notes:
- My own personal thought. I don't know if Sense was worth putting into RAM, I guess I like challanges so I gave it a go. I'm not promising amazing speed with this build.
- Upon booting, your HTC Sense launcher will contain no widgets or icons. It is up to yourself to add widget and icons.
- I have included a 1GB data.img, however you can use any size that you wish if you have your own data.img.
- I highly recommend starting with a new data.img regardless of whether you have used this build previously. There are some changes that may conflict with your current image.
- If you wish to make changes to the build, use the file structure in Android/root/ on your SD card to put your modified files in. They will be copied upon boot. Do not worry if they are not deleted, this is normal.
- Robot voice issue may occur when in a call. If this happens, during the call ENABLE THE LOUDSPEAKER, then DISABLE THE LOUDSPEAKER then END THE CALL. Do this exactly and every call after will no longer have this issue.
- You are left with around 250MB+ free RAM after booting the build. This is enough memory for anything!
- Build.prop is easy to modify, I have included a copy in /Android/root/system on the SD card. Modify this as you with and your changes will be copied over upon the boot of Android. If you mess something up, just delete the file and the changes won't be applied upon next boot. This goes for any file you put in the Android/root/ folder.
- I'm not going to be like other chefs and say "THE BATTERY LIFE IS EXCELLENT I PROMISE" etc. Everyone's setup is different, just test the build for yourself!
- Forget quadrant scores! If you're judging this build by quadrant scores then I pity you. This type of build is different from other builds, yes the quadrant scores may not be in the 2000+ range, but honestly, can you actually say to me that this build is slower than other builds that have a higher score? I sure hope not.
- The base rom is from Lambros Custom Rom r4 Desire rom which has been modified by myself: http://forum.xda-developers.com/showthread.php?t=745447
- The initrd and CSSync updates is based on that from cedesmith. However, I've modified the initrd for my own build.
- The PPP wrapper update is from LeTama's thread, version 0.7
- The HaRet loader is custom made by NetRipper, thanks to him for helping me increase the initial ramdisk size limitation!
- The HTC EVO keyboard is from motoman234 : http://forum.xda-developers.com/showthread.php?t=810338
- The modified HTC EVO Camera is from iamgpc : http://forum.xda-developers.com/showthread.php?t=829534
- Thanks to LeTama for providing a way to create my own htcleo.acdb file!
For developers only:
- The kernel included is hastarin's r8.6 eb kernel, taken from here: http://forum.xda-developers.com/showthread.php?t=787588
- Kernel source: http://www.gitorious.com/~hastarin/linux-on-wince-htc/hastarins-linux_on_wince_htc
Click to expand...
Click to collapse
------------------------------------------------------------
Bugs Fixed in version 0.1:
- No more data corruption. I have enabled sync in initrd.
- Robot voice is very rare now during calls. It should only happen once when you boot for the first time.
- No more high battery drain during sleep! Refer to my post here: http://forum.xda-developers.com/showpost.php?p=10179562&postcount=2293
Bugs Remaining:
- Notification LED's only blink once, use LED me know from market if you want LED notifications. Be warned, power consumption will rise with this.
- Rare robot voice bug
- PPP data should now work correctly for EVERYONE [UPDATE, turns out it's not...]. Thanks to MAsterokki and DutchDanny for pointing out the issue! Take a look here and see if there is a solution to your data problem: http://forum.xda-developers.com/showthread.php?t=892079
------------------------------------------------------------
Thanks to everyone at #htc-linux, #htc-linux-chat and at xda-developers for your help, guidance and support!
Thanks to my beta testers! Thanks to Hastarin for pointing out the toolchain issue which cases high power usage in sleep!
The first boot will take under a minute, subsequent boots will take much less time.
I am running HTC HD2 Stock rom 3.14.405.2.
My radio is 2.15.50.14, I have NO robot noise issue with the combination.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Download: http://www.multiupload.com/UA7FCEFW5T​
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
1st time ever being 1st!!!!!!!!!! woot woot partayy nice job
Good news............
woooooo... waited for this .... thanks darkstone ....
Screenhots would be sweet I love the continuing development, but I'm gonna stick to the non-Sense build of DS.
Still, thx for the effort.
Making a good thing even better, greaatt work Darkstone
Can you guys not read, it says big as day no thank you posts
Cool thx good News. I hope the roms for sd card works on cottullas bootloader.
I Hope darkstone has quick internet so this get uploaded quickly cause i can't wait, This is going to be best android build thanks a million for your amazing work and for returning. since i been using your builds from the start.
Edit opps sorry for the "thank you" post just really excited.
what is the defference to SuperRAM_Froyo_1.5?
Patiently waiting for the upload of Awesome Rom on paper..
dratengon said:
what is the defference to SuperRAM_Froyo_1.5?
Click to expand...
Click to collapse
there's a section that says "Bugs Fixed in version 0.1" under that are the changes
dratengon said:
what is the defference to SuperRAM_Froyo_1.5?
Click to expand...
Click to collapse
HTC Sense is included with this build
monx® said:
HTC Sense is included with this build
Click to expand...
Click to collapse
lol the box of worms you've opened will be plentyful
This one come with "SENSE"
dratengon said:
what is the defference to SuperRAM_Froyo_1.5?
Click to expand...
Click to collapse
I think we said that Sense would never be possible? May I ask why it is possible now? Is this a stripped version of sense? What changed?
Lets all wait for to try the build before posting a bunch of nonsense (pun intended). This is supposed to be for feedback and the DL link is not even up so lets not have 5 pages of fluff posts....please...pretty please.
Ok...Except from Sense.... everything should be similair to SuperRAM_Froyo_1.5....right?
Sorry folk... tried so many diff rom.... a bit confuse... maybe too much turkey, ham....
DarkStone1337 said:
which in turn will make the build superfast too! Very fast. Very very fast!
Click to expand...
Click to collapse
DarkStone1337 said:
I'm not promising amazing speed with this build.
Click to expand...
Click to collapse
Haha, I love a guy with a sense of humor. You never cease to entertain (and of course your builds never cease to amaze).
It's interesting you opted to stick with hastarin's EB. That specific (old) driver invariably shuts down my phone at about 9% battery remaining (despite numerous attempts to calibrate and erase entrained charge data), so I was wondering if this build, like many others, can withstand a simple zimage swap with the non-EB kernel. Since this particular thread and build are both so new, I thought it a prime time to ask before ruining something and coming back to complain or whatnot.

Bootloader cracked and next steps

So now that we have found the leaking crack in the bootloader and proved it's usefulness fat-tire and others are going to start work on a couple of key projects that I could use a little help on.
This will also keep conspiracy theorists at bay who call me "extremely low IQ male rooster with social development issues" (Also I have no pies)
Here is how i see the next steps:
Strip down uboot (or other bootloader) and teach it boot from it's own partition.
For example install 2nduboot in /boot, hijacking the signature check and then setting a 1MB offset to look for the real, unsigned boot.img. Repeat for recovery.
This is the real hold up and why there is nothing to "flash" as of yet. (still no pies)
Finish CWM. 100% done.
Completed. See recovery.img here: http://forum.xda-developers.com/showthread.php?t=1440645
Work on CM9 for both SDcard and internal booting
See Below
So instead of insulting me. I am looking for some people to help work on these things. We are going to be doing this is private respostories and a private irc channel due to the stupid reward that is out there.
If you are wanting to work with me. The reward (if we get done by the 22nd) goes to Doctors Without Borders. This is where we should all be donating. No negotiating.
So PM me or come to #nook-tablet @ freenode
Reserved
Bootstrap-loader (Goal #1)
Here is some more details on my thoughts on bootstrapping /boot and /recovery to boot unsigned images.
Today we are only bootstrapping with a 2nduboot on the sdcard. This would allow custom kernels and ramdisks on emmc for things like easier root, overclocking, CM9, CWM, etc
So my thoughts were to bundle together a bootstrap bootloader (uboot obviously will work, but another project that was used for CM on the touchpad called, moboot, may be a nice option to get menus and such) and the unsigned kernel+ramdisk into one binary blob. The unsigned boot.img will be at a well known offset. This will allow us to act as "stock" as possible and do things like. Replace just the kernel with an OC one. Replace just the ramdisk with ro.secure=0, etc.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This would also allow us to completely replace recovery with CWM.
Current Status: Fattire working on a meny for SD booting. Still discussing best way to do internal booting although using bauwks bootstrap uboots will work for now for emmc but incorporating a possible menu is being looked into. Low Priority
CM9 (Goal #2) Inprogress
There is a lot here and I am going to go at it pretty methodically adding one feature at a time. So graphics first, then key/touchscreen, usb gadget, etc.
There is a number of kernel changes that need to be done:
Find the closest git repo/branch/revision from omap zoom to apply B&N changes as a patch.
This will allow us to a) have revision history b) allow merging up to 3.0 easier
This is pretty important and if anyone is handy with git and knows of an easy way. Let me know
Backport key changes (fattire probably has this already done)
Backport usb gadget
Backport a hwrenderer compatable sgx drives (maybe move to a 3.x kernel at this point instead)
Backport
Current Status:
Teasers:
Wow. Thanks nemith for all the info. I will work with you and 100% will give the donation to them (verbal and writen agreement). From when I was building CWM on the GNex I remeber having to change one of the values in the .mk file to allow for adb.
Hi nemith,
That is a nice plan which aligned with my plan for modding u-boot to boot off the internal partitions .
I pushed some changes into my git repository on github which looks like #1 on your list. git://github.com/bauwks/Nook-Tablet.git
So for example, to build a 2nd u-boot that will install to the internal flash partition "recovery" and try to load the next stage at offset 256K of the internal "recovery" partition one would do:
(cd to u-boot directory and switch to second-uboot branch first, then)
PATH=/usr/local/arm-2010q1/bin:$PATH
make nt2ndboot_irecovery
make
./tools/build_nt_2ndboot_img.py -f -o irecovery.img u-boot.bin
dd if=/dev/zero of=irecovery.img bs=1 seek=262143 count=1 # pads to 256K size
Then, you can cat your irecovery.img and your real recovery.img together and blast them onto the recovery partition.
There is also a nt2ndboot_iboot config that will do the same, but is used on the "boot" partition.
I have only done minimal testing with the recovery partition 2nd uboot. I'm about to write a full image onto my recovery partition and see what happens
Update:
I flashed my recovery partition with irecovery.img + a random twrp2 image I had and it boots solely from internal flash! No more SD card needed, no more USB connection needed, just holding down power+N
nemith said:
So now that we have found the leaking crack in the bootloader and proved it's usefulness fat-tire and others are going to start work on a couple of key projects that I could use a little help on.
This will also keep conspiracy theorists at bay who call me "extremely low IQ male rooster with social development issues" (Also I have no pies)
Here is how i see the next steps:
Strip down uboot (or other bootloader) and teach it boot from it's own partition.
For example install 2nduboot in /boot, hijacking the signature check and then setting a 1MB offset to look for the real, unsigned boot.img. Repeat for recovery.
This is the real hold up and why there is nothing to "flash" as of yet. (still no pies)
Finish CWM. 100% done.
Completed. See recovery.img here: http://forum.xda-developers.com/showthread.php?t=1440645
Work on CM9 for both SDcard and internal booting
Started on this one as well. I can boot but haven't got adb working and no graphics (expected at this point)
So instead of insulting me. I am looking for some people to help work on these things. We are going to be doing this is private respostories and a private irc channel due to the stupid reward that is out there.
If you are wanting to work with me. The reward (if we get done by the 22nd) goes to Doctors Without Borders. This is where we should all be donating. No negotiating.
So PM me or come to #nook-tablet @ freenode
Click to expand...
Click to collapse
A bit on UI, cleanup, and various boot scenarios
Bauwks.. cool, glad emmc is is a go.
Current Status: Fattire working on a menu for SD booting. Still discussing best way to do internal booting although using bauwks bootstrap uboots will work for now for emmc but incorporating a possible menu is being looked into
Click to expand...
Click to collapse
UB2 update from me: A fruitful night with lots of fun enhancements, some modest UI feedback, and a sprinkling of safety/sanity fixes and other tweaks. SD and emmc options should be more convenient/consistent now, with recovery selection effectively handled by UB2 not UB1 (though power+n will remain an option obviously). I'll let nemith elucidate.
Also, bauwks, nemith suggested, and I thought it wasn't a bad idea, to expand to 512K instead of 256K as a partition buffer just to be on the safe side. I think he said the partitions are 16MB in all, so a little extra padding for possible future bloat is probably not a bad thing to have-- especially if there's gonna be a 2nd-bootloader "standard" (ie, so that any UB2 or menu will work in the future...) now's the time to decide- what do you think? Is 512 reasonable? Adding a single new .rle pushes you over. (We actually can eliminate two .rles right now, as the "charging" and "plugin" ones are effectively useless. I got rid of them, then added two more for feedback so I'm back to even, though eventually I'll probably get rid of them too.) What are your thoughts?
Considering I don't have an NT and I'm working blind here with nemith testing... I think this could wind up pretty nifty.
bauwks said:
Update:
I flashed my recovery partition with irecovery.img + a random twrp2 image I had and it boots solely from internal flash! No more SD card needed, no more USB connection needed, just holding down power+N
Click to expand...
Click to collapse
Nice!!!!
I was loathing the idea of having to keep a bootable sdcard in the thing forever. From my understanding of this, this hardware is now "cured", and just needs a special blob appended to the front of the boot and recovery partitions, eh?
dhkr234 said:
Nice!!!!
I was loathing the idea of having to keep a bootable sdcard in the thing forever. From my understanding of this, this hardware is now "cured", and just needs a special blob appended to the front of the boot and recovery partitions, eh?
Click to expand...
Click to collapse
Yeah. Or more specifically, everything in those partitions will need to be shoved over by a set amount to make room for UB2.
fattire said:
Also, bauwks, nemith suggested, and I thought it wasn't a bad idea, to expand to 512K instead of 256K as a partition buffer just to be on the safe side. I think he said the partitions are 16MB in all, so a little extra padding for possible future bloat is probably not a bad thing to have-- especially if there's gonna be a 2nd-bootloader "standard" (ie, so that any UB2 or menu will work in the future...) now's the time to decide- what do you think? Is 512 reasonable? Adding a single new .rle pushes you over. (We actually can eliminate two .rles right now, as the "charging" and "plugin" ones are effectively useless. I got rid of them, then added two more for feedback so I'm back to even, though eventually I'll probably get rid of them too.) What are your thoughts?
Click to expand...
Click to collapse
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
I can't really offer much as I am no android developer. I can modify basics and work thinsg out through educated trial and error but most of what you guys have been on about has been way out of my league. If it makes any difference I have 2 NTs one of which is brand new in a sealed box just sat waiting for the correct time to bother getting it out to play.
I'm quite happy to do testing, tweak things and do what I can where required.
Not sure what happened about the reward thing but as has been said before I think giving it to a good cause is a very decent and honest thing to do.
Doing it and donating the 'winnings' to a good cause is a far better idea and I commend you for following that route. Those that do it solely for the money aren't doing it for the reasons that I think XDA exists and from what I've seen before often get their money out of blatantly using other members hard work to make themselves look good, there always seems to be a lot of sitting on the fence then diving in at the last second and releasing something as their own when most of it isn't.
Anyway, enough babbling from me! Keep up the good work and when you think I can be of any help I will be more than happy to chip in where required.
bauwks said:
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
Click to expand...
Click to collapse
Presumably, the partition table is write protected along with the xloader and bootloader partitions, right? Now I guess that would be by power-on-write-protect rather than permanent write protect (which would obviously lock even THEM out of it...). Stupid question, but has anyone checked if the eMMC reset pin is connected to a test point on the board or on some gpio we can manipulate? I'm just wondering if we can pull something like a gfree on this sucker, especially since the eMMC is practically identical to the one on VISION/GLACIER/ACE, just larger. Bounce that reset pin and reinitialize the eMMC with write protect disabled, replace xloader and uboot with proper uncrippled ones, and BE GOD.
Progress on CM9 from @AndroidNemith http://twitpic.com/86hx6m - Twitter
dhkr234 said:
Presumably, the partition table is write protected along with the xloader and bootloader partitions, right?
Click to expand...
Click to collapse
Nope.
dhkr234 said:
Now I guess that would be by power-on-write-protect rather than permanent write protect (which would obviously lock even THEM out of it...)
Click to expand...
Click to collapse
Nope.
dhkr234 said:
Stupid question, but has anyone checked if the eMMC reset pin is connected to a test point on the board or on some gpio we can manipulate? I'm just wondering if we can pull something like a gfree on this sucker, especially since the eMMC is practically identical to the one on VISION/GLACIER/ACE, just larger. Bounce that reset pin and reinitialize the eMMC with write protect disabled, replace xloader and uboot with proper uncrippled ones, and BE GOD.
Click to expand...
Click to collapse
This is not the g2. It's not a write-protected emmc and a power cycle of the emmc will do nothing. I appreciate the enthusiasm, but you're coming to this very late.
More rambling...
If I'm not mistaken, the way you're suggesting is UB2 would be a prepended portion of the boot and recovery images as part of a "package", and this is how we were already discussing doing it in the cm9 build system-- this also matches in effect how Nook Color CM7 distros work-- the bootloader is actually re-installed with every update.zip (to enforce compatibility as newer versions of Android require newer u-boot).
However, I was considering that some people want to swap various u-boots in and out of existing boot or recovery partitions without necessarily having to push aside the rest of the image to make room. So if they're thought of as a unit, it makes total sense to do it as you suggest- but if UB2 is something that can be replaced (or updated) independently, then maybe a standard "buffer" size would be more appropriate.
We've talked about a few ideas- if a simpler boot menu is used to replace UB2, or a redirection to "see other partition for bootloader"... then it could be 512K (or whatever) mostly wasted... which may not be a big deal either.
Anyway, just typin' out loud. Lots of options, and no "right" way to do it.
bauwks said:
Hi fattire,
I guess it depends on how you look at it. I was looking at it like: an "image" is a concatenation of a 2nduboot and an Android kernel/ramdisk. To install, one would just dd the "image" to a partition. Then the 2nduboot wouldn't have to have a fixed max size that is predefined, if it needs to be increased you would just modify the partition offset in the bootcmd to load the stuff after the new size. It would also make updating the 2nduboot easier because it's part of the "image".
But, I have not worked with Android before so I do not have expertise in how images are typically deployed. If you always want the real image to be at a fixed offset then increasing to 512K makes a lot of sense. You are free to use the solution that best fits your problem.
By the way, the offset of the real image doesn't have to be a power of 2, it only has to be a multiple of the MMC sector size (512 bytes).
Click to expand...
Click to collapse
aversion of single-point-of-failure
I'd like to recommend, to avert the Single Point of Failure, a manditory and automatic backup of the /ROM/ partition. Since you're developing the first custom kernel, there will be a lot of work based upon yours for this device.
This can be handled in the init scripts. after /ROM/, /system/ and /sdcard/ mount. If the /ROM/ folder is available and there is no backup, make one. This simple step can save alot of grief in the future in case of damage.
Untested code:
Code:
#! /bin/sh
ROMBACKUPDIR="/sdcard/backup/ROM/";
BACKUPFILE=$ROMBACKUPDIR"ROMPARTITION.img";
TESTFILE="/ROM/NAMEOFANYFILE";
ROMPARTITION="/dev/block/***";
busybox test ! -e $ROMBACKUPDIR && mkdir --parents $ROMBACKUPDIR;
#no backup detected, so make one.
busybox test -f /ROM/$TESTFILE && busybox test ! -f $BACKUPFILE && busybox dd if=$ROMPARTITION of=$BACKUPFILE;
where ***=the ROM partition on your kernel and NAMEOFANYFILE=the name of any file on the /ROM/ folder
Whomever is building the AOSP!!!
Be careful with the ICS 4.0.3. There are alot of issues with the way the AOSP market place is working with it. The 4.4.3 Market has a tendancy to crash continually. Might be worth building ICS 4.0.2, and using that to elimitate all the problems whe can.
I have a mac g5 on public ip space and a NT that I can plug in if any dev's want to use that.
other than that, I'm another tester for y'all.
Loglud said:
Adam,
I own the nooktabletdev.org wiki, I will add all of those into it, or allow you an admin account. Then we can just point to there.
Click to expand...
Click to collapse
I've begun said post here: http://forum.xda-developers.com/showthread.php?p=21371828
Congrats to everyone who cracked it finally
I can say with 90% surity that You can recover a junked ROM partition or for that matter a fully junked eMMC, for the simple fact that it gives other pheriperals a chance before booting into eMMC (cannt say 100 % by myself immidiately now, because have been busy with other stuff at work over the last week, so my memory FIFO wrt my experiments on NookTab is bit blurry now).
AdamOutler said:
I've begun said post here: http://forum.xda-developers.com/showthread.php?p=21371828
Click to expand...
Click to collapse
Ahhhh, documentation!!!!
But seriously, thanks very much for that.
And FYI: Probably the best place to keep documentation is right here: http://forum.xda-developers.com/wiki/BN_Nook_Tablet -- in the xda device wiki.
Hey guys this just made you famous on the interwebz...
http://www.engadget.com/2012/01/14/nook-tablet-bootloader-bypassed-android-4-0-takes-its-first-ste
Good jorb!

Install and Configure a2sdgui on ROM's CyanogenMod

Install and Configure a2sdgui ROM's CyanogenMod
Hello fellow good here I leave this tutorial hos to use a2sdgui based on CyanogenMod ROMs, as these ROMs do not include this system and its installation is different from a stock rom; a2sdgui is an app that allows us to extend the internal memory the mobile to have more space to install apps, this is accomplished by configuring two aspects: SD memory partition and installing a script called darktremor a2sdgui, well initiate:
THE WHOLE PROCESS IS DONE AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKS IN MOBILE IF YOU DO EVERYTHING AS SHOWN TO WORK ALL YOU ASSURE THAT CORRECTLY
RECOMMENDED TO DO BEFORE INSTALLING THE MOBILE APPS
Requirements:
- ROM based CyanogenMod 7.1 or 7.2
- Install a2sdgui (DOWNLOAD FROM THE MARKET)
- Script darktremor a2sdgui 2.7.5.3 Beta 04 (Download)
- SD card partitioned
Instructions:
1. - Install a2sdgui
2. - MicroSD Memory Partitioning:
First download the MiniTool Partition Wizard.
http://download.cnet.com/Partition-W...=dl&tag=button
Once installed, we put our SD on the PC (with a reader, adapter or anything like that) and open the program.
If you already have some partitions it is recommended that if we start from 0 erase all as shown.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After deleting all now begin creating them.
We give and we get this Edit menu and the first is FAT32.
We have to make FAT32 and Primary, we assign space is relative, I having 8GB (class 6) I put all but 1.5 will be for ext4 and swap.
Now for the ext4 partition, select PRIMARY. Now the partition type is relative, it is recommended that if your card is less than 6 class partition is ext2. If Class 6 or more ext4. That and I leave to your judgment, in my case I assign 1 GB will be to host the apps as if they were in the internal memory.
Now we use the remaining space for the swap partition (PRIMARY), in my case 500 Mb RAM With this more of our ACE will have 800 MB of Ram (the swap partition is a partition that is used like RAM, it is so important!)
APPLY Now we give and we get this message should accept and the thing to end as you see in the two screenshots below.
Partitions that I recommend are:
3. - Restart the phone in recovery mode
4. - Scroll to and select mounts & storage mount / data and mount / system
5. - Made the above should be unmount / data and unmount / system
6. - Now return to the main menu of recovery
7. - Enter to install zip from sdcard> choose zip from sdcard>-2.7.5.3-beta04 dtapps2sd-signed.zip
8. - Restart the phone, when you start DO NOT OPEN OR ANYTHING IN THE MOBILE, the mobile just restart again, it is NORMAL not alarmed.
9. After reboot, enter A2SDGUI. On the menu that appears in the display of APPS on SD are expected to be active and SWAP may also, in case this is not no more to give up and active. At the end of the menu is the VALUE SET 0-100, I got 100 and I gave the side.
10. - Now we turn to LowMen directly and I have chosen this, to me is the one that best suits me. The option below elijais leave more free memory, it is better but in my case having 800 mb is fine for me up there.
11. - Now let's Dalvik-Cache and choose it and click Move & Rebuild and phone will reboot.
AND THIS IS WHAT WE HAVE TO END MUCH MEMORY FREE AND ESPECIALLY A lot of RAM! ENJOY!
Link2sd is better ..and s2e is better heavenly
Sent from my SGA rocking CM7.2 by vo-1 + all-in-one script
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
ayush29k said:
@tazlooney89, thanks for sharing this tutorial.
Could you please explain the difference between link2sd, s2e and app2sdgui??
there are so many methods, gets pretty confusing which to use.
Click to expand...
Click to collapse
Robbang said:
Yeah, Im pretty confused on this too.
What are the differences and cons/pros of each?
Thanks in advance
Click to expand...
Click to collapse
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
raymanlololo said:
I haven't used s2e, so i can't give you a description of, but i can say that the main difference between links2sd and app2sdgui is that meanwhile the first only moves the apps to the sd (even those that aren't allowed to by the os), app2sdgui "cheat" Android to "think" that it have more internal memory, but really it's just part of your sdcard.
Hope you'd understood me
Click to expand...
Click to collapse
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Robbang said:
Ok. Thanks. So what do you use? app2sdgui? I have used Link2Sd for a week or so now. I think it is really good. it gets the job done nicely.
Click to expand...
Click to collapse
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
try this
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
raymanlololo said:
No one, 'cause I've installed the stocklite and,I don't know why, app2sdgui doesn't run on it (to me at least).
Click to expand...
Click to collapse
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
ps1max said:
did u see this thread http://forum.xda-developers.com/showthread.php?t=1485470
Click to expand...
Click to collapse
ambujpriyadarshi1991 said:
DTaaps2sd doesnt work on stock rom .. as it need supported kernel.... ext4 sd-ext partition....
and stock provides with rfs system type....so running app2sdgui is not possible..
refer the link here...
DT A2SD thread on xda : http://forum.xda-developers.com/showthread.php?t=715940
this one is my try on explaing DTA2sd--
http://forum.xda-developers.com/showthread.php?t=1530270
Click to expand...
Click to collapse
I think you guys didn't understood me; I'm on the stocklite v3, and it's a custom rom with DT scripts installed. Anyway I'll take a look over that threads ;-)
EDIT:
Haha, i've messed it up!
I don't know why or how, but now i have the app2sdgui running, but....also i had runngin link2sd, and several apps linked. Now i have a lot of "andro-boxes" (linked apps that are, seems, not readable) in my phone, a sdcard partitioned and a lot of information blocked.
I'm trying to create the mount scripts on link2sd to unmake the links, and start using app2sdgui, but link2sd can't because "device or resource busy"
Good, i'm the best! XD
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
If you use Swype beta you need authenticate them, but u can use a altenative, a swype modify, i dont know if i can post the link here, because i dont know if this is a warez... ?? but put in the google and search for DA SWYPE. In this web site you have many options of colors of swype.
myshowbiz said:
I can't activate de Swap.
When I pres the button to activate the swap, appears "Changing setings..." after that "Reading setings...", some buttons appears in background but after 1 sec disappear.
how to fix that ? thx before...
Click to expand...
Click to collapse
Same goes here...cant activate the swap

[ROM] Unofficial Xylon Acclaim 2.1.1 [XYAOSP 4.2.2] [Nook Tablet][06MAR2013]

DO THIS AT YOUR OWN RISK.
I AM NOT RESPONSIBLE IF YOU BRICKED YOUR DEVICE.
Do research and reading if you are uncertain about this rom.
Do not PM me about the ROM.
WHAT IS IT?
Xylon is fully transformed distribution for Android Devices. It is designed to take full advantage of the device’s hardware and to provide the user pure Android experience.
The team is constantly working on making things better for the users and is happy to do so. We, the team, believe that for one to experience the pure taste of Android, he/she should be provided with something which is fast, intuitive and fluid – That’s where we come in – To provide you that.
Xylon started as a part of the Fruits & Veggies (FNV) project, a community ROM for the Galaxy Nexus and is now set up individually but its roots are based on FNV. Remicks, the founder of the FNV – inspired Daniel MM (Daxmax, founder of Xylon) to build something that would make users love what they use. In Daniel’s words – “This is an FNV based ROM, not FNV. But it has the winds of FNV, and it has more spacious features around the Android world.”
-http://xylon.androidvenue.com/about
FEATURES:
Phone, Phablet, and Tablet UI
Customized Trebuchet Launcher
A lot of customization
Compiled with Google’s GCC 4.7 toolchain.
Linaro's compiler flags, O3 and Linaro string routine)
Kernel 3.0.66+
CWM 6.0.28
SuperSU
QUESTIONS AND ANSWERS
CHANGELOGS:
Look at XYAOSP source history for further changes, I will not post them.
02/27 – Repo synced, Initial build so there could be many bugs.
03/06 – Repo synced, kernel updated to 3.0.68 with new lowmemorykiller, font size increased a little in statusbar and Trebuchet, you can increase icon size to 120% in Trebuchet, gesture control in Trebuchet, new SuperUser (Koush's).
IMPORTANT NOTES: If you noticed null icons (no action icons) on the NavBar then you need to go to Settings > XY Tools > Navigation Bar > Menu (The vertical three dots) and Reset navbar icons/targets. For Navigation Ring to work, you need to clear data/data1 if you are on previous build.
TO DO LIST:
Lots of things
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
INSTRUCTIONS:
You need to do a full wipe (factory reset and wipe cache) if you are on a different ROM.
You need to wipe data1 and cache if you are SD booting.
You need to reinstall GAPPS after each ROM installation.
In the case you booted and all you see is black screen for a couple minutes, reboot to see if it's fix.
Initial booting can take several minutes.
Copy ROM/GAPPS into your Internal Storage on the device.
Reboot into recovery and install ROM from Internal Storage.
Full wipe can be done before or after installing ROM/GAPPS.
For SD booting, you need to make bootable SDCard first.
There are plenty of guides around.
INTERNAL ROM:
86b333d03739180e428e5cbb2cb9d706 *xylon_acclaim_2.1.1_06MAR2013_16_HD.zip
84ca9aeb88fad3ddcd127a216a34557a *xylon_acclaim_2.1.1_28FEB2013_01_HD.zip
SDCARD ROM: (Single boot) BOOT partition contents, boot.zip
134e175b18da509b37cf0897294214a6 *xylon_acclaim_2.1.1_06MAR2013_HD_SDC.zip
3b46595484586b0e0e99ca856fbb5ad7*xylon_acclaim_2.1.1_28FEB2013_HD_SDC.zip
INTERNAL GAPPS: *Might need to go to advance > fix permission in CWM before flashing GAPPS
4493696a11733e4e2a15d0026211963e *gapps-jb-20130301-signed.zip
c4a07a24e11448824b84e314600cd357 *gapps-jb-20121212-signed.zip
EXTERNAL GAPPS:
e2a80b77153a6bacd3df785742487ea3 *gapps-jb-20130301-signed-SDC.zip
36e9081e0dd29b67193d2db9441683c3 *cm-10.1-20121212-gapps-SDC.zip
RECOVERY: (TWRP 2.4.3.0 + CWM 6.0.2.8)
THANKS TO (CREDITS):
bauwks - Bootloader exploits
CYANOGENMOD
Source - https://github.com/CyanogenMod
Web - http://CyanogenMod.org
CM G+ - https://plus.google.com/+CyanogenMod
XYLON
Source - https://github.com/xyaosp
Web - http://xylon.androidvenue.com/
XYE G+ - https://plus.google.com/communities/102617491638136644864
Members:
Alex (AlexForTomorrow)
Arz Bhatia (arzbhatia)
Bluewall
Daniel MM (DaXmax)
David Vidal (Dorilife)
Varun Verma (D00mSlayer)
NOOK TABLET
Source - https://github.com/CMNookTablet, https://github.com/Kuzma30
Members:
Brandon Bennett (nemith)
Chris (chrmhoffmann)
fat-tire
Hashcode
Kuzemko Alexsandr (Kuzma30)
Kyrylo Mikos (mik9)
Rebell
KINDLE FIRE
Source - https://github.com/loosethisskin, https://github.com/KFire-Android
Members:
Aaron Davis (icemank121)
Andrew Dodd (Entropy512)
Hashcode
IngCr3at1on
JackpotClavin
Jacob (drkhd)
John Craig (x0xhellx0x)
Loosethisskin (twa_priv)
Markus Cisler (bl1nk)
Raymond Jay Golo (intersectRaven)
Scott Brady (sbradymobile)
Shujun
SGT7
Source - https://github.com/sgt7/android_packages_apps_Trebuchet
Members:
Angel666
Chirayu Desai (chirayudesai)
eaut
Humberto Borba (humberos)
jt1134
Koudai Aono (koxudaxi)
pulser
redrebel696
Scott Brady (sbradymobile)
techomancer
COMPILER
Source - https://github.com/succulent
Web - http://iamafanof.wordpress.com
HD (Succulent)
Questions and Answers
Want to clear cache manually?
Delete the dalvik-cache folder inside cache folder with root access & restart.
Is Jellybean running slow on your NT? It might be your SDCard.
microSD Card Benchmark Comparison — CrystalDiskMark
Why do I have to wipe data/factory reset?
Dirty installation can slow the OS and causes side effects due to residue files still on system.
Want to swap your internal storage (EMMC) to SDCARD?
Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
My converted MP4/M4v isn’t working?
Use Handbrake 9.4. The current ducati firmware is outdated and doesn’t support newer MP4 codec.
How do I edit system files?
Use FileManager, settings>change access to root access, & click on lock icon, change to RO>RW
How do I take screenshot?
Hold power button + volume down
Where’s Developer options & Performance?
Click Build number several times.
Want to save battery?
Rename system/apps/phone.apk to phone.apk.bk
Change CPU performance to 800 MHz max feq. and use conservative, click set on boot
For better standby battery, go to Wifi Advanced settings > Keep Wi-Fi on during sleep > Only when plugged in
Where’s bluetooth/OTG/USB Host?
…
Do I need to install GAPPS?
Only when updating as the image comes with GAPPS
Yes, you do need to reinstall GAPPS after each update.
Don’t like Media Transfer Protocol (MTP) and want USB Mass Storage (UMS)?
Edit /system/build.prop, change persist.sys.usb.config=mtp,adb to mass_storage,adb
Older Mac might need http://www.android.com/filetransfer/
How to I view sdcard1 (SD card) with FileManager?
Go to Settings and change Access Mode to Prompt or Root.
Google Voice crashes?
Update Google Search
Don’t see folders or files when clicked on Internal Storage or SD card?
Refresh
Do I need to root the device for CM ROM?
Rooting is the ability to use superuser for root permission on a system.
Mainly for stock Android with no superuser.
All CM ROM come with superuser access.
How do I block OTA updates from BN?
You don’t need to. You are running CM software not BN.
How do I wipe data on sdcard?
The latest recovery (Orange theme) has an option “Wipe data1 on sdcard”, that is wipe P3 on sdcard.
It’s similar to factory reset, only that wipe data partition on the internal memory.
Boot animation is messed up?
Yes, for now.
What about tethering?
It’s removed since CM7, I couldn’t get to work with all the outdated patches.
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
http://forum.xda-developers.com/showthread.php?t=1369817
I am stuck in a recovery boot loop?
Flash this, flashable_fix_bootloop.zip, File>Download
GAPPS, stuck at Wi-Fi Connecting…?
Patient. Just wait up to a couple minutes.
Hulu Plus not working?
You need a cracked Hulu APK so search for it on XDA. Hulu works on stock ROM.
How do I increase animation speed?
In the developer options, change animation scale to none or 0.5x.
Succulent, this is awesome. I'll test it out myself
Re: [ROM] Unofficial Xylon Acclaim 2.1.1 [XYAOSP 4.2.2] [Nook Tablet]
Amazing!
Sent from my NookTablet using xda app-developers app
Imma test it out also. Fantastic!!
---------- Post added at 02:46 AM ---------- Previous post was at 02:45 AM ----------
After testing for about an hour, I can name a few problems I came across. First thing I noticed was the text and the icons. They were blurry and was an eye strain for me. Second minor problem but the Nav icons are smaller than on the other builds. I tried youtube and the first video I tried didnt work. Just show's play button.
Keep up the great work!!
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
postulio said:
I'll try this out, thanks.
Just to be clear, only the top link is for the actual rom right? The source links are just for reference? I assume.
Anyone try it yet?
Click to expand...
Click to collapse
The download link is under Internal ROM towards the middle of the post.
Used this ROM for a day, not bad.
Love the customization. To me though, it feels a little laggy. Also i have been having tons of trouble playing youtube videos on it, both on the website and through the app. they either dont start at all or crash (and i still hear the audio, lol). sometimes they simply wont load.
another observation is that pretty much all the 4.2 ROMs i've tried have pretty bad battery life when compared to 2.3. This is unfortunate but doesnt render the tablet unusable. I'd say if you charge it every night, it is fine. Leave the tablet overnight, without charging, with wifi on (although i know it goes into sleep) the battery drops from 85 to 35 in about 8-9 hours, which is awful.
Personally I am going back to PA 3.1 for now, but will check back if development progresses.
I tried out Xylon: for a first build it works really well and is very responsive (even though I am running it off SD). The couple of problems I ran across are the same one I recently encountered on some other ROMs: e.g., MX Player out-of-control when playing some video in HW mode (even when the Player is force-stopped the audio still keeps going), System-UI crashes when switching to Tablet-UI.
I think this ROM has a lot of potential and is really fun to use.
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
bingoz said:
Whenever I adb devices from my PC to NT, it says devices offline, how can I connect my PC & NT? I found some other threat about new adb on 4.2.2 but they didn't help.
Click to expand...
Click to collapse
You might find some helpful pointers at http://forum.xda-developers.com/showthread.php?p=35971559#post35971559.
Also, make sure that you do have the latest update of ADB (see http://forum.xda-developers.com/showpost.php?p=38118551&postcount=9).
FWIW, I re-flashed Xylon ROM with cm-10.1-20121212-gapps-SDC.zip — not only does Google auto-restore now works but also I no longer have the problem of “System-UI has stopped” when switching to Tablet-UI.
been using this for 4 or 5 days now, seems pretty good to me, battery life is a lil suspect, but ive just uopdated to 6th march version, so will see how this goes
CWM Backups
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Looks cool Im going to try flashing this rom today. Thanks for all the work you put into it.
RhinoNelson said:
It may be I am using a dated CWM but my 6.0.2.8 version does not correctly calculate the MD5 sums. Anyone able to successfully do backups with MD5 sums ti help me know if the issue is mine or the ROMS?
Click to expand...
Click to collapse
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
CWM backups
digixmax said:
6.0.2.8 is a very recent if not the latest version of CWM.
How do you determine that "6.0.2.8 version does not correctly calculate the MD5 sums"?
Click to expand...
Click to collapse
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
RhinoNelson said:
When I run the backup, the last step performs the MD5 sum and it gives an error. I had this with a backup with a different ROM as well yesterday. I didn't retry so it could have been circumstantial. I don't have this ROM installed any longer so I can't attempt another backup of it.
Click to expand...
Click to collapse
FWIW, the couple of times I encountered "MD5 errors" in doing backup using recovery were when I had insufficient space in the sdcard's first partition ("/boot") to accommodate the size of the needed backup.
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
succulent said:
....
Want to swap your internal storage (EMMC) to SDCARD?
[*]Edit /system/build.prop, persist.sys.vold.switchexternal=0 to 1
jamesgg said:
The Rom seems to think that /sdcard directory is in the external sd card, So I can't download files from the internet (web browser) with out a microsd, it gives me an error "says no such directory." Is this normal for the Nook Tablet, any way to get around that?
Click to expand...
Click to collapse
Did you try this?
Sent from my ST27i
Click to expand...
Click to collapse

Categories

Resources