Partitioning SD card in u8150 - Android Q&A, Help & Troubleshooting

I partitioned my SD card in huawei u8150 everything for me is ok but when I look in cyanogenmod settings then application the check box in the expanded internal expanded storage is not clickable please help
ROM: CYANOGENMOD 7.2 STABLE
Sent from my U8150 using xda app-developers app

Don't know the specific device but when running into similar issues I usually do the following
1 back up everything
2 back those backups up somewhere other than the SD
3 reformat the SD with the device you intend to use it for
4 check if re-partitioning is needed
4a if not then; skip to 5
4b if so then; re-partition and go to 5
5 check that things seem ok, try moving an app to SD, try reading/writing/deleting a few junk files
6 if all is ok then move backed up data back to SD card and chock it up to the oddness of electronics, if all is not ok then perhaps your ROM or kernel or device has something sooooo check for bug reports on the sites that you get those from and or check the lists of features.
Currently I run cm 7 on my HTC device and have a multi-partition set up on the SD card, no issues other than Android only seeing the first one in the list.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey

S0AndS0 said:
Don't know the specific device but when running into similar issues I usually do the following
1 back up everything
2 back those backups up somewhere other than the SD
3 reformat the SD with the device you intend to use it for
4 check if re-partitioning is needed
4a if not then; skip to 5
4b if so then; re-partition and go to 5
5 check that things seem ok, try moving an app to SD, try reading/writing/deleting a few junk files
6 if all is ok then move backed up data back to SD card and chock it up to the oddness of electronics, if all is not ok then perhaps your ROM or kernel or device has something sooooo check for bug reports on the sites that you get those from and or check the lists of features.
Click to expand...
Click to collapse
I can move applications but the sd card partition does not increase my internal memory which is 163 mb by the way thanks bro for your help in advance

bonsoljoshua said:
I can move applications but the sd card partition does not increase my internal memory which is 163 mb by the way thanks bro for your help in advance
Click to expand...
Click to collapse
I mean that if i can move the full application in that partitioned aprt of the sd card that would increase my memory

I've written a few guides here and there, if you search hard enough you'll find one about
Folders plug
http://forum.xda-developers.com/showthread.php?t=1502893
that I wrote once about that app... I think so anyways if not then here is a quickey to save time for all readers that stumble across this work around
1. Get some warnings out of the way
~ this app is in beta (currently)
~ requires root
~ use at your own risk
~ don't use on system apps (like your phone or contacts)
~ don't use on apps that you rely on (anti theft apps for example)
~ I'm not the dev of the app just a supporter
~ make a backup (nandroid style) then back all that up and what ever you value on you sdcard somewhere else
~ I've done some hard testing with this app and put two devices into boot loops / simi-bricked states. So know how to recover from this and be careful.
~ I have yet to fully brick any device ever, even with this app, so it might be safe when used properly.
2. Provided the warnings don't bother you, then download and install the above app
3. Open the app and be presented with a few options
~ under menu + Preferences = Mount on boot
~~ I would not use this until playing with the other options first and seeing how your device responds
~ under menu + Edit = a screen that will say something like "no mount points selected"
~~ this is where the magic happens, move to step 4
4. Under 'menu + Edit'
4a~ now press menu and then "Insert"
~ this is where things may be confusing
4b~ For source folder you may want to make a new folder on your sdcard with an app like root browser (hint this app comes bundeled with ROM Toolbox; another fantastic app) I put mine under '/sdcard/Adev/Internal_Spoof/' and then make a new folder path per app from there
4c~ For Target folder things get a bit complex; you've got to find the folder on the device's internal folder structure (root browser for the win on this again) that contains the apps data.
... be back to edit the rest in in a sec, just posting to ensure you know I'm still here
5. Before finalizing any links you should probably back up the app data somewhere else too. For example '/sdcard/Adev/Internal_Spoof/backups/'
6. So you've got a good target for both now there are more options.
6a~ you can press accept and then press and hold on the connection you've just made and then select mount
6b~ or after setting a bunch up the main screen with the red plug icon can be pressed like a button to activate all the ones in the list that have a green check box next to it at once.
7. Once you've tested this... for example I used;
~ for Source I used '/sdcard/Adev/Internal_Spoof/download
~ for Target I used '/data/download'
And kinda get what's going on here and know where you app data is saved (hint I think mine is under '/data/data' but yours maybe different) it's time to make it useful for your quest for more space to install apps (among other things too maybe?)
7b~ so if an app like Pandora is under 'data/data/com.pandora' and you map it like so--
~ source '/sdcard/Adev/Internal_Spoof/Pandora'
~ target 'data/data/com.pandora'
-- and back the data from '*/com.pandora' to '*/Internal_Spoof/Pandora' and then activate the link... then nothing will look different... except when you view the available space that its
8. Rinse and repeat for each app and don't forget to copy the data (otherwise it'll brake the app till you un-link and copy the data ) and remember not to do it to certain apps.
9. Once you've verified that it's all good and your apps run with ok levels of lag you can try testing the "mount on boot" option that I told you not to use yet. If it works after a reboot then opening and interacting with the affected apps, then rebooting again and interacting again and rebooting again, then it's time to do something dangerous...
10. Provided that your with me so far and things are good on your device its time to do the risky bit; deleting the data from 'data/data/com.pandora' and running it strait from sdcard and re-testing for broken apps with a reboot.
This will effectively open real system memory back up for other tasks but like I said use at your own risk.
final edit before seeing any feedback- this work around may seem a bit complex at first but once you've got a list of apps that work when short-cutted like this it can make a big difference in how much available space can be accessed, however, this may cause force closures on some apps, and may degrade the life of your sdcard. Furthermore in some usage scenarios I had better battery life but that's for another guide on another day
I'll be linking in a google doc version of this guide when I get it shairable and maybe link in screen shots or screen casts for better guidance. If I've really helped then consider hitting the thanks button and happy hacking and modding.
Sent from either my SPH-D700 or myTouch3Gs
Debian Kit/QEMU Linux Install guide for all android devices that I'm writing:
http://forum.xda-developers.com/showthread.php?t=2240397
Now have working Installers for ARM Java 7 JDK + Maptools + jMonkey

Related

[ZIP][DEV][ROM] Nookie Froyo 0.6.8 (02/15) CWM flashable!

Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!

[APP][02/26] Nook Color USB Mass Storage utility - Mount any partition to your PC

I've compiled a simple app to be able to easily mount to your PC any given partition.
Feel free to donate if this app is of any use to you. Much appreciated.
Please note that changes to the drive will not be saved if you do not properly unmount/eject the drive from PC (in Ubuntu: right click, unmount. In Windows, eject.).
For those using stock browser, apk files often fail to download.. You can install Astro explorer and activate downloads in settings (last option). Then you should be able to download this file.
Dolphin should work without issues..
This is a Beta release.
This requires a working root (su). By that I mean your nook must be rooted. Regarding HC, see j4mm3r's thread.
This can be used, for example, to open your SD or internal data on your PC..
You can mount pretty much any partition to your computer with this app:
- SD
- Media (internal drive for your media and documents...)
- SD Partitions (up to 4)
- Internal storage - BE VERY CAREFUL WITH THIS!!
There are two "mount points" on the nook (lun0 and lun1)
So you can simultanously mount two partitons.
As an example, you can mount SD on 1st and MEDIA on the 2nd.
Each mount point has it's own tab.
Please try it out and post feedback.
Thank you.
EDIT (13.02.2011):
This has been tested on HoneyComb and Froyo (not in Eclair 1.0>1.1).
In Froyo: USB Mass Storage (Notification bar) should be turned off.
Compatibility mode will need to be disabled in Spare parts (reboot required).
If this doesn't work for you, try entering manually in ADB while NC plugged in to your PC:
Code:
adb shell
echo /dev/block/mmcblk0p8 > /sys/devices/platform/usb_mass_storage/lun0/file
And post result here.
Sam
----------------
UPDATES:
13-02-2011: 0.2b => minor bugs and made app scrollable for Froyo Landscape
26-02-2011: 0.3b:
- Changed 'settings' label (mistake) to system.
- Added a "Make sure you properly unmount/eject drive from PC when finished" message when mounting.
- Added dual boot system and data (p9 and p10).
- Changed 'Confirm mounting' to 'Confirm', as poster suggested. Thanks.
--------------
Hmm can't quite seen to get it to work right. The app does nothing for me when I select a partition to mount. I can get the SD card mounted via android's USB connected notification. I've tried the app with it turned on and off. It's got super user, so that's not it. By the way, I'm running Froyo 6.7 off the eMMC. Let me know what to try.
EDIT: Got it to work after running the ADB command in 1st post. Awesome app, thanks.
Sam,
Thank You, you program made my day. It works great, I have been messing with vold.fstab for days and I could only mount the boot of my sdcard. So, I went with manually pushing file to /sys/devices/platform/usb_mass_storage/luno/file which worked but your app make the process much better.
Again Thank you for everything you have done.
Biz
Could this work as a Xbox media storage? I want to get a new demo, and I got no Hard Drive
Works great!
this is great! i was thinking (since your help in the other thread) about trying to cobble something like this together myself in android app creator suite but didnt know if i could manage or not. Now i dont need to even try! thank!
EDIT: 2 things, one, is it possible to have this setting survive a reboot? and secondly, is the display supposed to be tiny? it only fills like a third of the screen and is centered at the top. this is on emmc froyo 0.6.7 the screen is scrollable as you said so just have to scroll down for the confirmed button
Does it unmount them on the nook when they are attached to the PC? I was playing with the echo command and it seems that the nook is unable to see any changes to the filesystem. I wrote a script that unmount them then runs the echo statement. Then another script that remount them once they are disconnected.
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
samuelhalff said:
Good question. As I said, this is beta. I'm open to any suggestion. From what I tested, changes did actually occur even when mounted on android..
Unchecked compatibility mode in spare parts and reboot for fullscreen..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
you did say that huh... sorry
This provided an easier way to fix root (SU binary) to make SuperUser work again on HC.
Glad it helped.
Over 100 downloads and very few feedbacks...
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
Over 100 downloads and very few feedbacks...
Click to expand...
Click to collapse
Interesting. I did see that if you try to download / install directly from the HC browser it doesn't work. Perhaps people do this instead of trying with their computer and assume it doesn't work? Downloads don't equal successful installs.
For Windows users, it (currently) provides the only way to mount the 4th partition of my HC SD card. Am I mistaken? Perhaps others don't realize what this is or are put off by the UI?
Keep it up. This is a much needed utility ATM.
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB..
Sam
Sent from my HTC Desire using XDA App
samuelhalff said:
The UI isn't THAT awful, is it?
Anyway, this can help a lot of people, especially the ones not too familiar with ADB.
Click to expand...
Click to collapse
To a person familar with partitions and the android file system it's fine. To those expecting a more fruity / friendly UI, it's far from it. However, you can't please everyone and it might be a waste of your energy to try. It's practical / functional and that's all I need it to be.
Indeed it can, much preferred over ADB even though I can use it just fine. You might want to make it more clear in the OP that users that have problems may need to type "adb shell" before the echo command. Not everyone will know this.
You app works well Sam! I can finally access my media partition via USB. I am looking forward to updates. Perhaps retaining setting after a reboot? Great work man!
Works great! I downloaded it with dolphin browser (running froyo on emmc) Then used root explorer to navigate to downloads and just clicked to install. Doesn't get any easier than that!
Would it be possible to have it mount media partitions? Like if I have dual boot setup would it be possible to mount the extra partitions to edit them?
Which media partitions?
Right, forgot about dual booters.. I'll implement that in 0.3..
Thanks.
Sent from my HTC Desire using XDA App
I want to thank you so much for this samuelhalff. I mean it. Something like this that may seem trivial to someone who can just do it means a WORLD to someone like me and i truly truly appreciate it. The devs/peeps here have made my little wanna be ereader ((hehe)) a great honeycomb tablet. I think its great for someone that cant afford the next great thing **xoom** to be able to join in the tech fun. You all have made me very happy with my little tablet.
Jamie.
Love the app!!!! but i got a issue now... There is no way for me to browse the media partition on the device... so I can not access my pictures that I placed on the internal storage...any insight?
Working great for me, HC on eMMC. Appreciate it!

[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta

[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!

[Q] Desperately trying to increase the memory...

Hi there!
First of all excuse my bad English. I learned this language several years ago. But let me have a try to tell you about my problems:
I’m a proud owner of a Samsung Galaxy Ace 5830i. Before using this device I’ve been a real Apple nerd (shame on me) but now I’m proselytized completely.
However I’m facing a difficulty now. I tried to increase my internal memory, but it doesn’t work.
I’m actually running this custom firmware:
http://forum.xda-developers.com/showthread.php?t=2778000&nocache=1
And I‘ve tried all the solutions mentioned here:
http://www.droidthunder.com/increase-internal-memory-android-phone/
All of them are causing error messages – as a sample the Terminal Emulator App is telling me „a2SD“ is not found. And Link2SD seems to be working – but after receiving about 15 messages the device tells me the storage is full.
I’ve installed SuperUser and Clockwork Recovery for sure…
As I know myself as a little dopey, I’m sure it’s my own failure –but I can’t find it. So please help me!
I’m absolutely certain you need further information –so just let me please know what you exactly need.
Stollentrolle said:
Hi there!
First of all excuse my bad English. I learned this language several years ago. But let me have a try to tell you about my problems:
I’m a proud owner of a Samsung Galaxy Ace 5830i. Before using this device I’ve been a real Apple nerd (shame on me) but now I’m proselytized completely.
However I’m facing a difficulty now. I tried to increase my internal memory, but it doesn’t work.
I’m actually running this custom firmware:
http://forum.xda-developers.com/showthread.php?t=2778000&nocache=1
And I‘ve tried all the solutions mentioned here:
http://www.droidthunder.com/increase-internal-memory-android-phone/
All of them are causing error messages – as a sample the Terminal Emulator App is telling me „a2SD“ is not found. And Link2SD seems to be working – but after receiving about 15 messages the device tells me the storage is full.
I’ve installed SuperUser and Clockwork Recovery for sure…
As I know myself as a little dopey, I’m sure it’s my own failure –but I can’t find it. So please help me!
I’m absolutely certain you need further information –so just let me please know what you exactly need.
Click to expand...
Click to collapse
First of all do please explain all of the instruction(s) you did take from step one , rather than directing us to some general external links method .
Your custom rom comes pre-rooted with su app as i gathered and binary update installed , so i didn't get the part about installing stuff and please clarify the process you went through for play store an Gapps installation as com.android.vending-5.2.13-80321300-minAPI9.apk was omitted from system/app of your TWR v2.5 . ( post #270 my comment )
If you got any root explorer installed please give me what you see under /system/etc/init.d folder of your device ( you can also install terminal emulator and give me the following output command is generated >> "ls -l etc/init* " & type "su" to get elevated and then type " df" for now and FYI there are two method for increasing your internal space : 1-link2sd free version from play store and 2'; universal script method which is a bit complicated but does not require app linking method such as link2sd app .
On the side note though , If I am not mistaken TWR v 2.5 is heavily customized , therefore few MB of space will be remained under /System partition . You need to re-partition your external device through clock work mod and install link2sd app from play store to increase internal memory space , or use cronmod script which is a bit complicated . ( upon re-partitioning , all of your external SD card data will be erased , so back up your critical data ) . I need those output i requested to be any assistance to your cause , but this is a general guideline anyway :
Link2sd instructions :
1- Uninstall any new app you have downloaded through your built -in application manager or from play store/my app section ( before that unlinked then through link2sd , if you created link2sd connections ) . Delete any .apk file leftover within your Download folder , accessible through your built-in file manager ( root explorer /es file explorer will do).
2. assuming you are familiar with your custom recovery console ( a.k.a : CWM ) , turn off your phone and push the hardware combo key to get to your CWM :
3. Go to advanced>partition SD card>choose size ( 1024mb)
4. After that( ext4 or ext2 will be created upon entering 1024 Value , depend oc the CWM version and kernel you are using ), then choose 0mb as swap partition and continue .
5. After this is done go to mount and storage and format sd-ext there (back up your sensitive data as you will loose them ).
6, Reboot your device .
7. open up your internet browser and search for " free link2sd app from play store " , if you can't find it directly over play store search function and install the app.
8. Open up the app , you will asked to choose your sd-ext partition format : pick ext4 or ext2 ; if you got any script error , then from top left corner menu , choose recreate mount script and pick ext2 , if ext4 generated mount error .
9. from top right corner menu , choose multi-select > push on the option on toolbar or select your apps > push on three vertical dots from top right again and this time choose link to sd card > all of the app selected by link2sd or hand picked by you will be transferred to /sd-ext partition plus some other technical stuff .
10. now back to the first page and from top left menu , choose storage info : you must see something like :
Internal
SD card
SD Card 2nd part
System
Cache
spaces , from now on , your limited internal will remain at the fixed ratio and your /mnt/sdcard and /data/sdext2/4 will be involved with apk data and library and app cache
Soft rebooted from top left corner menu of link2sd in order to become effective .

[HOW-TO] Installing AOSP Android 7.0 "Nougat" Internally on the 16 GB Nook Tablet

[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?

Categories

Resources