[ROM] Timing Power RK3188 Custom - Android Stick & Console RockChip based Computers

[ROM] Timing Power RK3188 Custom - Android Stick & Console RockChip based Computers

This is just an initial ROM for a project i'm starting with this device. This is the stock rom but cleaned up and tweaked a little. Removed all the junk from the rom and replaced the keyboards with Null Keyboard. Added a few apps for convenience. Keep an eye out, I will be updating frequently. Requests are welcome. Thanks for looking.
ADDED:
AdAway
ES File Explorer
Reboot App
Writer
Just flash with rockchip batch tool and enjoy!
can't post links so copy and paste in url box and remove the spaces:
h ttps://w ww.drop box. com/s/2x6qp0s56hqkyu3/timingpowercfw.img

nothing there
misk8er said:
This is just an initial ROM for a project i'm starting with this device. This is the stock rom but cleaned up and tweaked a little. Removed all the junk from the rom and replaced the keyboards with Null Keyboard. Added a few apps for convenience. Keep an eye out, I will be updating frequently. Requests are welcome. Thanks for looking.
ADDED:
AdAway
ES File Explorer
Reboot App
Writer
Just flash with rockchip batch tool and enjoy!
can't post links so copy and paste in url box and remove the spaces:
h ttps://w ww.drop box. com/s/2x6qp0s56hqkyu3/timingpowercfw.img
Click to expand...
Click to collapse
Please repost the ROM. When attempting to download it, this is what I get:
"Nothing Here
The file you're looking for has been deleted or moved."
Thanks!

As of now I'm using latest firmware 20131103.
I only use this device for Plex it's perfect for DTS, bluetooth audio/video is in perfect sync but MKV's with AC-3 stereo audio & video is out of sync big delay of some sort.
Anyone else experiencing this issue?
I can't try other ROMs because not sure which other ROMs can be flashed with this device. Any pointers or advice would be much appreciated.

Hello,
Just a curious question.
Does wireless display work on this ROM?
I have an CX-919 and flashed 4 different ROMS already (finless 15, 16b, kitkat, NZ something) and non off them work.
Wifi display is connected with my galaxy S4 or Asus ME302C tablet, but mirroring does not start.
It worked with my S4 one time with finless kitkat, but that was it.
I really want to get it working because i have all pictures etc. om my phone and tablet.
PS: if anyone reads this and has problems to get into flash mode, the solution is very simple.
Do not use the USB cable that comes with your stick.
Use an USB cable form your phone or tablet.
I use my Samsung USB cable and that works flawlesly, althoug the blue LED stays on (in opposite of what everyone says) after plugging it in the PC with the button held.
All flash tools i used see the stick everytime and no problems flashing whatsoever.

Related

[Q] Cant move apps to SD card

I just purchased an Elocity A7 and updated the firmware to 2.0134 and applied Dexter's Elocity 1.42 mod.
Everything seems to be working great, I can get to the marketplace etc. but for some reason none of the apps will go to the SD card that I have installed.
I can see the card mounted but when I go the the App to SD app the column to move to SD card (that I used in prior versions) is not on the screen.
Is this normal?, or am I doing something wrong?
Thanks in advance for your replies.
Demi

Your procedure isn't correct, first you have to load dexter 1.41Rom then add the patch 1.42, you cannot put 1.42 ontop of the factory firmware...

Elocity did not include the option, so you cannot move apps with stock firmware...
you need the CyanogenMod released, then you get the option to do it.

Thank both of you for the prompt replies.
Should I reinstall the elocity software again, over the Dexter mod?
What does CyanogenMod mean, and how do I install? it.
Sorry, I'm not very technical.\
Demi

demialbano said:
Thank both of you for the prompt replies.
What does CyanogenMod mean, and how do I install? it.
Sorry, I'm not very technical.\
Demi
Click to expand...
Click to collapse
Original Post by Dexter_nlb
I played around with a version of the CyanogenMod7 for tegra2, and now its in a acceptable state, so you can test it too.
I have used the latest Atrix4G 2.3.4 + vega / optimus 2X to put this version together, and its based on the original elocityA7 kernel and includes modules for cifs,nfs,ext3 and ext4 support.
So although its a Android Gingerbread 2.3.5 base, kernel is still just 2.6.32.9 based, so cpu,memory and kernel related optimizations are not here.
CyanogenMod7 offers a lot of customizable features, full multilanguage and latest enhancements found for our android comparing to original stock a7 rom, you get alot more features.
Fixes in Version3 (Cyanogen7RC1ModA7-3)
- Youtube HD video fixed
- VolumeUP/VolumeDown assigned to sound&search buttons
- DSP Manager is now working, it is really to loud for internal speaker if you go full power.
- GoogleTalk app update + crash fix. (still no video working)
- USB_OTG app updated, so changes take effect immediately when you swith HOST/DEVICE mode (used to connect tablet to pc with usb-a2usb-a cable)
- Real 1080p video out with HDMI (not sure how it affect playback, it seeems just upscaled)
What is found not working right now:
- Camera photo & video recording (photo stopped when avi got enabled)
- rotation sensor is 90 wrong (in gameloft games)
- bluetooth
What is working
- Netflix runs out of the box on this one, as i made build.prop changes so it thinks its a Xoom.
- wifi networking
- sdcard , usb host/device and USB stick support.
- all features of CM7
- mkv/avi/wma/wmv hardware acc. video playback (almost seems like more avi is supported than before?)
Download http://dext3r.komodin.org/Elocity-A7/Cyanogen7RC1ModA7-3.zip
to install after just as full update, but is a kernel only update. (extract Update.zip from this zipfile to root of sdcard)
Download http://dext3r.komodin.org/Elocity-A7/Cyanogen7RC1ModA7OCKernel.zip

Thanks,
I get an error message when I try to do this update. I am on Dexters Mod
Demi

The error message is cant find entry for META-INF/com/google/android/update-binary

demialbano said:
The error message is cant find entry for META-INF/com/google/android/update-binary
Click to expand...
Click to collapse
unzip the downloaded zip, and there is a zip inside named update.zip that needs to be extract and out on the root of your sd card

Thank You for the reply. It worked perfectly and now everything is up to date and working. I don't know how to press the thank you meter so here goes a double thank you...

How does the original question apply to the A7+?
I can't access card and I'm having memory issues... new thread has specifics

[FAQ] Common Issues and Solutions for SGT7.7, now with JB (12 May 2013+)

After seeing similar questions get asked and answered several time over, I thought this might be helpful (not least for myself). No particular order for now. Feel free to propose additional Q/A or edits--I'll credit accordingly. Thanks to our moderator (original_ganjaman) for making this a sticky.
This is meant to be a quick reference that either briefly answers a question or links to the answer--for issues with more or less known solutions. This is not the best place to post new, previously unanswered questions.
If you found this FAQ useful, do click on the "Thanks" button on the left.
* * * * * * * * *
JELLYBEAN (Added 12 May 2013+)
Q1: Can it be that the wait is over?
Indeed. Some ten months after the ICS update to our beloved SGT7.7 (and the release of JB into the wild), the Jelly Bean (Android 4.1.2) update has finally arrived. As of now, the ROM for Singapore, Indonesia, Thailand, Philippines, and Malaysia (PDA= P6800DXMD3, CSC = P6800OLBMD3) is available; and only for the P6800 (not the P6810). If you device came from the appropriate locations and have an appropriate stock ROM, you should be able to update via Kies. Else, download the file from Sammobile.com (search for "P6800").
The two main methods for flashing the ROM (not counting officially via Kies) are ODIN, and MobileODIN (requires a rooted device before flashing). Instructions for using both can be found here. Flashing with MobileODIN can be done preserving root, which is convenient. I have upgraded my SGT7.7 (Hong Kong model) with the Singapore ROM, using MobileODIN, wiping cache and data (thus losing my old apps, etc.), but preserving root--apparently, doing it this way can help avoid some potential wifi issues (reported in the forums), and battery life.
Q2: What languages are available in the SEA ROM (PDA = P6800DXMD3, CSC = P6800OLBMD3)?
As the ROM is meant for Southeast Asia (Singapore, Thailand, Vietnam, Philippines and Malaysia), the available languages are: English (UK), English (US), Bahasa Indonesia, Bahasa Malaysia, Tamil (?), Tieng Viet, Korean and Chinese (Simplified). A workaround for getting additional input languages is described in this post. Alternatively, you can also install swype (from Play Store), which has the option for downloading ton of additional input languages.
Developing...
* * * * * * * * *
ICE CREAM SANDWICH (Added 6 July 2012; edited 27 July 2012)
Q1: Whaa...?
As of the time of posting, the Android 4.0 ICS upgrade is only available via Kies for devices from Austria, and as more recently, Hong Kong. However, it is possible to download a copy of the respective ROMs from sammobile.com--search for "P6800" (3g/wifi version) or "P6810 (wifi only version). The .zip file is 590+MB. Be sure to get the correct ROM as the one for the P6800 will not work on the P6810 and vice versa. The ROMs do seem to work on devices from a variety of countries (not counting the Verizon 7.7). A list of languages supported in the Austria ROM can be found here. See here for discussion of the Hong Kong ROM.
The two main methods for flashing the ROM (not counting officially via Kies) are ODIN, and MobileODIN (requires a rooted device before flashing). Instructions for using both can be found here. Flashing with MobileODIN can be done preserving root, which is convenient. A detailed and guide using ODIN can also be found here.
It is also possible to flash with HEIMDALL--but just make sure that it is not Ver. 1.3.2 (1.3.1 works fine). The main bits: heimdall flash --cache cache.img --factoryfs factoryfs.img --hidden hidden.img --modem modem.bin --recovery recovery.img --secondary-boot Sbl.bin --kernel zImage; then CWM can be flashed with heimdall flash --recovery recovery.img (cgm999)
Flashing the ICS Rom over a STOCK Rom (both rooted and unrooted) preserves settings and most of the third-party apps, i.e., wiping is not required. (All told, this is also probably the safest way to proceed.) Mileage varies if flashing over non-stock Roms. (UPDATE--wintermute000 writes: "...doing a clear data/factory reset in locerra's Clockwork Recovery is 100% safe, the brick bug affects STOCK recovery.
More information on the brick bug and whether it affects ICS on the 7.7; also this.).
Some of the issues involving missing or non-functioning stock apps seems resolved if the a factory reset is done after flashing (settings>Back up and reset>Factory data reset; or when off, hold volume up and briefly press power to access option to factory reset). UPDATE--WildmanJoe writes: "...following a suggestion from another member on the board, I have found that it is not necessary to do a factory reset if your stock apps don't work. Just go to settings>applications and clear the data for the stock apps that don't work. It is tedious, however, it eliminates the factory reset brick risk..."
ALWAYS REMEMBER THAT YOU FLASH AT YOUR OWN RISK AS IT IS POSSIBLE TO BRICK YOUR DEVICE (see this discussion, and this.)
See here for a database of successful/unsuccessful upgrade configurations. (Do also contribute your own experience.)
Q2: What's it like?
As anticipated, the tab is way more responsive with ICS rather than Honeycomb. But having said that, ICS for the SGT7.7 does come with Samsung's 'enhancements', which means touchwiz (and no stock ICS Launcher). The Email, Contacts, Calendar ("S-Planner"), Messaging, Clock, etc. apps are also from Samsung. On the bright side, the unable-to-write-to-externalSD problem seems solved.
Q3: How do I modify the looks of it?
As with Honeycomb, an alternative launcher is still recommended (unless you have a special love for touchwiz). Possibilities include the old favorites ADW Launcher Ex, Go Launcher, LauncherPro, etc., but now also including those that only work with ICS and above: e.g., Nova and Apex. Furthermore, you can also install a status bar that looks (mostly) like stock ICS with this mod.
Q4: Can I install stock Google apps?
Search for "Android 4 ICS Calendar", "Android 4 ICS Messaging SMS" and "Android 4 ICS Launcher" by Tim Hutt in Play Store.
Q5: What about the Browser?
A Samsung tweaked version. You can always install Google Chrome (Play Store)--but this one does not work with flash--or Dolphin HD.
Q6: What about the keyboard(s)?
Comes with a Samsung keyboard, swype, and voice input. The version of Swype that comes with the Rom supports a limited number of languages, and there is no option to download more languages. If you want to use swype with other languages, go to the swype website, sign up for a free account, and follow the instructions to install swype beta. Swype beta can coexist with the version of swype that came with the Rom, and allows the possibility of installing additional languages (including Arabic, Korean, Chinese, etc.).
If what you want is the stock ICS keyboard, search for "IceCream Sandwich-ICS Keyboard" in the Play Store.
Q7: Can I root?
Yes and no. To be more precise: a rooted stock Honeycomb Rom can be upgraded to ICS via MobileODIN while preserving root. Update: here is a method to root the ICS rom.
* * * * *
HONEYCOMB (Older version of the FAQ)
Q1: Surely this thing with its speedy processor should feel more responsive?
A: First and foremost, this thing is very speedy and responsive (see e.g., this discussion). Ok, ok, the general consensus is that Honeycomb (Android 3.0) and Samsung Touchwiz (the default launcher) are holding back the otherwise stellar hardware a little. The only solution for the first is to wait for the upcoming Ice Cream Sandwish (Android 4.0) update, slated to be released July 2012.
What can--and arguably should--be done in the meantime is to change the launcher. ADW Launcher Ex*, Go Launcher, LauncherPro, and SPB all options. Apart from being much faster, more responsible and less of a resource hog, they are also much more customizable compared to Touchwiz (search in Market for various themes and icon packs). Some worry that since Touchwiz is not removed (it can't be on stock unrooted rom), it might still be in the background. If you are afraid that it is taking up valuable processor cycles, remove all homescreen widgets on Touchwiz to make yourself feel better, like I did.
*Jade Eyed Wolf has put up a very useful video tutorial on how to use ADW here (the thread is here). To get rid of the top statusbar in ADW, see this.
Q2: Is there a way to make the system font size larger without rooting?
There is an app for that; though this is probably be a better way for the those who have rooted their device (omarrabbat).
Q3: I am unable to write to the external sd card (from within Android) using anything other than the stock file manager; is there something wrong with me?
A: No, you're fine. That's how it is out of the box. The solution requires rooting (see Q4 below) the device and changing the permissions for the sd card. See here. (You can of course write to the sd card with Windows explorer after connecting the Tab to the PC via the USB cable.) Another method for solving the problem is available here; note that you will also need the device to be rooted, and have CWM Recovery installed, beforehand (lowem).
Q4: How do I get root access?
One guide is here; another (with instructions to unroot) is here.
Q5: Why can't I seem to change the lockscreen wallpaper?
Settings>Screen>Screen display>Lock screen. At which point you should be in Gallery (or if, like me, you have an alternative pic viewer--e.g., QuickPic--installed, the dialogue box should ask you to "select wallpaper from"...). Select photo of choice, but make sure to crop with Gallery, and presto. See discussion here.
Q6: How do I get movies and tv shows onto the tab?
See this discussion.
Q7: How do I connect my tab to my PC using a USB cable? Wireless?
Make sure that the appropriate drivers are installed on the PC (e.g., download and install Samsung Kies. When plugged in, Windows should recognize the tab as an MTP device, which allows one to browse both the internal storage and the external sd card in Explorer. The option to convert files as you copy to the device is not a good idea (see this). Best to do any conversion you want on the PC. It's safe to disconnect by simply pulling out the USB cable.
For wireless file transfers (and much more), try Airdroid, which works, and is free.
Q8: What's a good pdf reader for this baby?
There are several good choices: EBookDroid, Repligo, EzPDF, Mantano, Aldiko...
Additional input (for compiling this page) from: lousyfer, lowem, cgm999, Wildmanjoe, wintermute000

Reply from Samsung re: ICS for P6800
Dear XXXX,
Thank you for contacting Samsung Customer Care.
Unfortunately we do not have any details with regards to when an update will come for your device. Rest assured the development team are working on the next update and your issue has been noted .
If you have any further enquiries, please do not hesitate to contact Samsung Customer Care.
Thank you for contacting Samsung.
Kind regards,
XXXXXXXXXX
-------------------------------------------------------
Dear Samsung team member, can you please pressure the product team to release an upgrade to this device as the screen fonts are so small its very difficult to use.
I have read in a number of forums that customers are not happy with this problem and some believe that it will be fixed with the release of ICS for this device.
I bought the product with the intention of using it for work and its painfull to read. I really hope something can be done to fix this urgently.
Kind regards
XXXX
---------- Post added at 08:20 AM ---------- Previous post was at 08:05 AM ----------
Q3: I am unable to write to the external sd card using anything other than the stock file manager; is there something wrong with me?
A: No, you're fine. That's how it is out of the box. The solution requires rooting (see Q4 below) the device and changing the permissions for the sd card. See here.
I can rite to SD card and device with windows explorer. i did not root. I am using windows 7.

lousyfer said:
Q3: I am unable to write to the external sd card using anything other than the stock file manager; is there something wrong with me?
A: No, you're fine. That's how it is out of the box. The solution requires rooting (see Q4 below) the device and changing the permissions for the sd card. See here.
I can rite to SD card and device with windows explorer. i did not root. I am using windows 7.
Click to expand...
Click to collapse
Thanks for the Samsung info. I was referring to writing the external sd from within Android. (See the linked discussion in the FAQ.)

Thanks for this

Theory said:
Thanks for the Samsung info. I was referring to writing the external sd from within Android. (See the linked discussion in the FAQ.)
Click to expand...
Click to collapse
Thanks - i can write to SD card from within android using their stock file manager without any issues

Hi, a weird thing happened here. I paired my tab with two Bluetooth headsets and both work fine. Paired it with my laptop and another laptop, but it can't send or receive files from either. Any ideas?
P.s. thanks for the page!!
Sent from my GT-P6800 using xda premium

7.7 and kies
hey there.. i got my tab 7.7 yesterday in singapore, official samsung store. now i try to connect it to kies but he always say me: your model is not working with kies 2.0.
i use it with my galaxy s 2, no probs, and also kies air.. nope..
i use last kies version and win 7 pro
n.b.: even in wifi, kies doesnt work and my S2 is rooted..
i need to sync with outlook, thats why i need kies..
thanks guys for a quick solution..

deckensian said:
Hi, a weird thing happened here. I paired my tab with two Bluetooth headsets and both work fine. Paired it with my laptop and another laptop, but it can't send or receive files from either. Any ideas?
P.s. thanks for the page!!
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
I've used Bluetooth File Transfer app from the market on my SGS phone to send files to my paired GT-P6810. It works great. Remember though that BT is sloooow so use alternate, egWiFi, for large files.

FarmBoi said:
I've used Bluetooth File Transfer app from the market on my SGS phone to send files to my paired GT-P6810. It works great. Remember though that BT is sloooow so use alternate, egWiFi, for large files.
Click to expand...
Click to collapse
Thanks a lot for the info, will try it out.
Sent from my GT-P6800 using xda premium

occhiblughiaccio said:
hey there.. i got my tab 7.7 yesterday in singapore, official samsung store. now i try to connect it to kies but he always say me: your model is not working with kies 2.0.
i use it with my galaxy s 2, no probs, and also kies air.. nope..
i use last kies version and win 7 pro
n.b.: even in wifi, kies doesnt work and my S2 is rooted..
i need to sync with outlook, thats why i need kies..
thanks guys for a quick solution..
Click to expand...
Click to collapse
I can't offer a solution but would be keen to see if anyone can. I have the same problem. My 7.7 3G just won't connect to Kies. I'm running Vista, but will soon have a new PC with Win 7, so will try again then.
No probs with my SG2

scarytas said:
I can't offer a solution but would be keen to see if anyone can. I have the same problem. My 7.7 3G just won't connect to Kies. I'm running Vista, but will soon have a new PC with Win 7, so will try again then.
No probs with my SG2
Click to expand...
Click to collapse
Mine is running on kies with no problems. If useful I have win 7 and downloaded kies from Samsung website.
Sent from my GT-P6800 using xda premium

no way.. i tried everything.. he recognize kies air.. but no kies.. win 7 and last samsung kies..

Hi,
Had the same issue. Fixed it by deinstallimg Kies, make regclean, install Kies from scratch.
Worked fine for me ;-)

i did.. still same problem..

For Q3, found a slightly easier way via the "update.zip" method over at this thread : http://forum.xda-developers.com/showthread.php?t=1458021
It's under Tab 7 Plus forum but I've tried it and it works for Tab 7.7 as well.

lowem said:
For Q3, found a slightly easier way via the "update.zip" method over at this thread : http://forum.xda-developers.com/showthread.php?t=1458021
It's under Tab 7 Plus forum but I've tried it and it works for Tab 7.7 as well.
Click to expand...
Click to collapse
This is good. The original poster noted that the method "won't work for a device that doesn't have CWM Recovery installed." What about your own 7.7: was it rooted and did you have CWM Recovery installed when you use the update.zip?

Theory said:
This is good. The original poster noted that the method "won't work for a device that doesn't have CWM Recovery installed." What about your own 7.7: was it rooted and did you have CWM Recovery installed when you use the update.zip?
Click to expand...
Click to collapse
Yes, my Tab 7.7 is rooted, using the root.zip method discussed here. And yes also to the second, I installed the CWM Recovery 5.0.2.7 discussed here.

What is the LOST.DIR folder?
Can the folder itself or the files within them be removed?
Is there a safe way to remove the tablet from the connection a computer via USB?

uncle_buckman said:
What is the LOST.DIR folder?
Can the folder itself or the files within them be removed?
Is there a safe way to remove the tablet from the connection a computer via USB?
Click to expand...
Click to collapse
Not sure.
I've always just pulled my USB cable out. Doesn't seem to be any issue. I suppose it's more proper to effect it on the PC first.
Sent from my GT-P6800 using xda premium

Windows doesn't have an "eject" or "safely remove hardware" option for devices connected via MTP--at least, not one like it does for HDDs, flash drives, or other USB mass storage devices. As long as you're not using the connection it's fine to just unplug it.

New Finless ROM 1.7 for Measy u2c /B12/ Imito V2 (rooted)

Finless juste made a new rom (version 1.7) for these android stick:
Measy u2c / B12 / imito v2 (camera)
libstagefright inside
support and download here:
http://www.freaktab.com/showthread.php?4282-NEW-Measy-U2C-B12-Finless-ROM-1-7
my question.. Is he the only one who cook rom for android stick? cant find alternative here on xda...
anyway, a great Rom done by Bob!
Code:
Features in my Measy / B12 / Imito V2 ROM:
This is an entirely new system. This is not much from the original Measy/B12 ROM in this as fas as system goes.
Many features from my 1.6 ROM are of course in this along with new features.
BE SURE to check out the mouse wheel ZOOM function to enable google earth etc to zoom!!!!
Set it by going into settings>accessability> and turn on mouse zoom!
1) New "auto hide" status bar! To enable this go into settings>Display and turn it on.
Now anytime you run an APP it will automatically hide the status bar. Please note, some badly written APPs
can leave you in a stuck condition that you cannot exit the APP. You will need you keyoard exit key.
2) While you in settings>display there is another feature to force the settings menu icon in the status bar.
It is 3 dots vertically. NOw anytime you in a APP that has a settings capability, if you click that you get settings!
3) Lock screen is back friends! Now is settings>security you can
A) Disable the lock screen completely (default is slide)
b) Setup a pattern for lock screen
c) Setup a PIN for lock screen
d) Setup a password for lock screen
4) Sleep is back like a tablet!!!! Go into settings>display and you can turn on sleep!
Now understand how this works
a) If there is no wifi or ethernet connection, when it goes to sleep will power off.
b) If there is a connection, it will simple go into low power mode and turn the display off. Moving the mouse turns it back on again
5) I enabled location services. This is now in the settings menu. Tested and working with all APPs that use it.
remember to turn off GPS as we have no GPS.
6) New "grid" style launcher available as a choice of launcehrs.
Some people still want the Alternate launcher that comes with many TV sticks for EZ TV use.
I took this from the Neo X5 ROM as I liked it better than previous versions. This of course comes with the RK settings as well.
If you want to remove this just use ES File explorer and delete these files from /system/app
LauncherNEW.apk
AllApp.apk
RKSettings.apk
RKBasicsettings.apk
Now just reboot and all this will be gone.
7) Gameloft fix. This fixes Gameloft games from crashing to the desktop.
Many of them do not run and crash to the desktop. This is due to a license check based on the device.
Special thanks to Christian Troy for inventing this fix. I modded it for this ROM.
8) Build.prop edit to open up the Google Play store to APPs that normally say "not compatible".
I am spoofing a Samsung device that will show almost any APP as compatible.
YOur device will show up in google play as NOT a B12 device! Understand this please.
I also left the original buiild.prop in the ROM called build.orig.
If you want to go back, just use ES FIle Explorer or a root file explorer and rename build.prop to build.old
Then rename build.orig to build.prop.
Go into settings, apps, all and go into the Google Play app. Clear the cache and data.
Reboot! You should be back to showing up as a Minis Nexo X5.
9) Rockchip just released a updated libstagefright.so to try and fix HW decoding issues in XBMC.
Ihadd added this ot the ROM but have not fully tested it yet.
See info here regarding this new library.
http://forum.xbmc.org/showthread.php...756#pid1345756
10) As always, full init.d support! If you do not know what that is... ignore it. For geeks that want to use it. It is there!
11) RK Mirrioring is enabled. I have yet to figure it out or how to use it but if we ever do, its there.
I think we need a client on our tablets to use it. Hopefully more info will come from WiMo about this.
12) Remote Control using RK Remote APP is now fully supported!
In the ROM kit is a RKRemoteControl.apk.
You install this on your phone or tablet and now it can remotly control your TV player!
Just put the APK on sdcard or something and install it on your Android phone, tablet, etc.
ENJOY this one! I had a HARD TIME getting it to work!
13) I added a reboot APP that will allow optional reboot options like reboot to bootloader (flash mode).
14) As always I added the Xbox XPAD.KO module is now injected on boot. This was by request! Enjoy!
15) I added Xbox360 keylayout to fix some games and camera spin with xbox 360 controller. Per this post here:
http://forum.xda-developers.com/show....php?t=1792531
16) TUN.ko module is also added by request. (CIFS and MD4 are already in the latest kernel).
Be aware if you use another kernel other than whats in this ROM, you may have to manually insmod CIFS and MD4.
The files are in /system/lib/modules
This ROM has several options for you to choose from for flashing so please read carefully how to change these flash options.
I have provided 4 parameter files. These will increase APP space and decrease internal sdcard space.
1GB APP space (this is default setting for the flash tool).
2GB APP space.
4GB APP space.
6GB APP space! This is the max! This leave only 400MB of space for the internal SDcard.
___________________________
NOTE:
USB OTG port boot up:
Anytime the Measy/B12 is booted AND the OTG port is plugged into a PC, it will boot with USB storage turned on! What this means is on boot up you will not be able to see the internal SDcard or the External SDcard from within Android. On your PC you see the removable drives because on boot they are mounted to the PC not Android. Now you can this OFF once booted. Go into settings and USB. You will see PC connection is grayed out.
1) Click it and it will then put the check box in "conneted". Odd it is OFF by defualt even though it is really connected to the PC.
2) Now turn it off and it will unmount the SDcards from your PC and you can now see them in Android.
HOWEVER... Realize next reboot, it will be on again.
In my opinion this should not work this way but at least you can turn it off once booted.
The other work around is to always hook up the USB cable to the back micro USB port not the OTG port.
The back port ONLY powers the unit. There is no data connection on this port for PC.
This solves that issue. But remember the back port will NEVER connect to a PC or allow ROM flashes.
Only the OTG port allows that.

Can I install this ROM on MK809II?

ledzgio said:
Can I install this ROM on MK809II?
Click to expand...
Click to collapse
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...

g.b.a. said:
YES. And I think it's the best ROM for MK809 II. Try it and you'll see...
Click to expand...
Click to collapse
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...

ledzgio said:
Thank you! Is everything working with this ROM? even Wifi and bluetooth? I read that there are problems with them...
Click to expand...
Click to collapse
Yes. They are working fine with this ROM...
Enjoy!

Hi I am looking for cmw flashable zip for mk808 will this work ?

g.b.a. said:
Yes. They are working fine with this ROM...
Enjoy!
Click to expand...
Click to collapse
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks

ledzgio said:
I have heard that, with the MK809II because it doesn't have the reboot button, I have to open the device and do something inside...is it correct? do I have to do this operation even with this ROM?
thanks
Click to expand...
Click to collapse
Reboot?
If it is a normal reboot, you don't have to open the device.
There is a Reboot app included in the New Measy Finless 1.7 Rom.
Correct me if I am wrong but based on my understanding, you only have to open your device and do the "Shortcut" method when you are having
some problem in getting into recovery mode. or your small switch button is not working anymore...

Can I install this rom on my MK809III rk3188

are there some instructions/guide how to make rom for this little sticks on your own?

adiprince1 said:
Hi I am looking for cmw flashable zip for mk808 will this work ?
Click to expand...
Click to collapse
I would like to know this also.
Thanks
Sent from my SGH-T889 using xda premium

Z4L/Z4/Rockchip - Firmwares/ROMs/Root/TWRP & Performance Tweaks & Tricks

WARNING: I am not responsible if you use any of the following and for any troubles you may experience with your device.
{
"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"
}
I recently got a Z4L and wanted to do a few things with it. After many days and nights, I am ready to share. I also wanted to consolidate an area for us to easily get items. I will add things from others if pertinent or greatly desired. Much of this will also apply to the Z4 and to other Rockchip Android TV Boxes (to a lesser extent).
This first section will entail some information, firmwares, apps, and performance tweaks and tricks.
The second section will have information on flashing firmware, ROMs, and recoveries.
The third section will have all the available tools for Rockchip boxes.
Z4 vs. Z4L
The Z4 and Z4L are essentially the same Android TV Box with a few minor differences. The Z4 has dual band WiFi, while the Z4L only supports wireless b/g/n. This is because the Z4 uses an Ampak AP6335 chip, while the Z4L uses a Realtek RTL8723. Does it matter? Yes. I have found that many firmwares and ROMs will work on the Z4L, however, all WiFi and Bluetooth connectivity is lost. And even other Rockchip Android TV Box firmwares sharing the same chip have had problems (e.g. USB ports no longer work, partial loss of remote functionality).
Another difference on the Z4L is OTG capability. While the port works for flashing, it will not work for any external devices when in the Android OS...
A final, possible, difference is that I think the Z4L only comes with 8GB of storage, but I could be wrong.
Firmware
This is the stock firmware for the Z4L. It was quite difficult to find, and was the only one I have come across:
Z4L Stock Firmware
Custom Firmwares
This is the Z4L stock firmware with enhancements. I have made some performance tweaks to help make the Z4L run smoother. Apps have also been added (with the exception of FolderMount), which I will have available in a separate section below.
In the slim version, I have taken out several apps I found unnecessary (e.g. Gmail, Calculator, etc.). Things you would normally leave to a smartphone or PC. While the firmware will be the exact same size as the stock firmware, rest assured it is slightly lighter:
Z4L Slim
In the lug version, I have not taken out any of the preinstalled apps. Instead, I have just added the same ones placed in the slim version. This will be a larger file size due in part to the additional apps, and the extra space I left for possible future modification needs:
Z4L Lug
Apps
Kodi
Kodi 15.2 RC PL
This is the beta that comes with a lot of the Android TV Boxes. It is preloaded with official and non-official add-ons. While it is suggests it is a 15.2 Isengard Release Candidate, the app settings in Android (and at least one Kodi updater app) will state that it is version 15.1.
Kodi 15.2 PL
What I have found on the Z4L is that I cannot update it. The Play Store gives no update option. Update apps for Kodi will attempt to update and fail to install, as will a manual download from the Kodi site. The only way I could update to 16.0 was by uninstalling 15.2 RC and then installing 16.0. I would lose all add-ons, and even a backup from Kodi will disallow restoring unofficial add-ons. Even if manually adding unofficial channels, I had problems getting them to work...
Kodi 16.0 PL
This is the latest (Jarvis) Kodi, and I have gone ahead and preloaded it with all the same add-ons from the 15.2 RC version:
Kodi 16.0 PL
ZDMC 16.0 PL
This is a software built on Jarvis. I have inserted all the preloaded add-ons from the 15.2 RC version in it. I am unsure what the difference is with Kodi. They look virtually the same, except for the logos and branding (since Kodi does not allow others to use their IP).
ZDMC 16.0 PL
Stock Apps
The only other stock app I thought would be of interest is the launcher. I actually prefer it to any of the others available. It may or may not work fully with other Android TV Boxes:
MyLauncher
Apps in Custom Firmwares
These are all the apps that come in the custom firmwares I created:
Added
Other Apps
FolderMount is an app that can help when you have little storage space. The only reason I have it here is because it does not come with any of the custom firmwares and will be needed for one of the performance tweaks and tricks:
FolderMount
Performance Tweaks & Tricks
Some of these tweaks or tricks may be dependent upon root. The Z4L comes prerooted, but others may need to obtain root first.
Speed Up
One of the best fixes I can recommend to help with any sluggish performance is to speed up your CPU cores. Download an app like Kernel Adiutor to give you as much access as possible. If you download something like No-frills CPU Control, you will only have access to the "Little" cores of the RK3368.
Open your app of choice and find the area that allows you to set the minimum and maximum states of the CPU.
Ensure that the "Big" cores are set to 1.5GHz for the maximum state.
Change the minimum state to 1.5GHz.
Do the same for the "Little" cores, where the maximum state should be 1.2GHz.
You can leave the governor as Interactive or change it to Performance.
Leave the I/O scheduler as "cfq" for daily use, use "noop" for benchmarks.
I have not experienced any type of overheating from these settings.
Maximum GPU Performance
If you want to get a bit more out of the PowerVR Rogue G6110 GPU, you can downsize your resolution. I use a 1080p TV, so I changed the Android OS resolution to 720p. Download something like NOMone Resolution Changer, or equivalent. A few items will have some larger writing even after the DPI change, but nothing that should deter you from keeping the setting.
Open your app of choice.
Set the resolution to something like 1280x720.
Change the DPI to (or around) 151.
Apply.
Some apps will ask if you want to keep the settings, and prompt you if you need another message in case something happens. With NOMone, this does happen. It also gives you the ability to reset to default settings if need be.
With the two above tweaks, I was able to get the multi-thread score to outperform an iPhone 5S in GeekBench. And in GFXBench, I was able to outperform a LG G4.
Internal/External Storage Swap
The greatest drawback of the Z4L is the 8GB of storage space. It can fill up quickly if you want to play games, or have hefty apps. You will need to download SD Fix and FolderMount. I have tried other apps like Links2SD and Int2Ext, but they do not work.
Open SD Fix and follow the instructions.
Reboot.
Open FolderMount.
Analyze the apps and see which have Data or OBB files, and are not grayed out.
Select them and make a pair.
You can select a USB flash drive if you do not want to use a micro SD card, but either way, ensure the source and destination sources are properly chosen.
SD Booster
It is probable that your internal storage and micro SD card are not optimized. Download SD Booster to change this and speed up your I/O abilities. Red means that you are definitely not optimized, yellow means you are operating at substandard levels, green means your are at the perfect level, and purple means you are operating beyond the perfect level.
Open SD Booster.
Select the internal or external storage.
Change the original value to a different one (i.e. 512, 1024, 2048, 8096).
Use the green checkbox to confirm the changes.
Use the green checkbox on the main window to implement the changes.
The Z4L's internal storage is in the red when first opening this program, so this will help somewhat. You may not get a huge jump in read or write speeds, but every little bit helps.
Developer Options
The Z4L does not have the ability to enable Developer Options natively. The "Build" section is not present. Download and app for Developer Options, I recommend the one from Andev.
Open your app of choice.
Click whatever button(s) needed to access Developer Options.
The one I have mentioned is part of the custom firmwares I created. The only caveat is that it will require you to sign into your Google account before proceeding.
Xbox 360 Wireless Controller
If you want to use a Xbox 360 wireless controller instead of a wired one or Bluetooth gamepad, you can! You will need a Xbox 360 wireless gaming receiver. Download USB/BT Joystick Center.
Open USB/BT Joystick Center.
Plug in the wireless receiver.
Click the button on the wireless receiver for sync.
Click the middle button of your Xbox 360 wireless controller.
Click the sync button located on the top of the Xbox 360 wireless controller.
Select the option to search for controllers on USB/BT Joystick Center.
Once the controller is recognized, immediately begin testing the buttons and whatnot or you may lose connectivity.
This is a bit finnicky, but it does work. The first couple times I could not get the controller to stay synced. Once it did stick, I tried it with Dead Trigger 2 and found that almost everything worked but the D-pad. Of course, I still had to setup the buttons.
Misc. Issues
Apps Not Working
Some apps can be downloaded but will FC when trying to open them. For this, I do recommend downloading the APKs from somewhere reputable and installing them with the file explorer.
Stock File Explorer
The stock file explorer is actually good, but it will not let you go to root ("/"). For this you will require something like ES File Explorer File Manager or Root Explorer. I found that whenever I would go to the Data folder on ES File Explorer File Manager (after selecting show Hidden Files), it would show it as empty. Whereas, Root Explorer would show everything. However, I have not been able to access my USB flash drive through Root Explorer, but can do so with ES File Explorer File Manager.
Stock Media Player
The stock media player plays most everything, and has built-in 3D capabilities. However, when trying to play some x265 files, there were problems. I would recommend installing MX Player to help with H.265 or VP9 codecs.
10-Bit Video Files
8-bit video files for H.265 or VP9 have no problems playing on these boxes. But when trying to play something that is 10-bit, it has nothing but major frame stutter, audio skip or silence. Until these codecs are made to not utilize so much CPU power, I do not think anything other than actual PC's will be able to play them properly.
External Webcam
It may be possible to use an external webcam on these boxes, and some of the files I have looked at suggest this. I do not currently have an external webcam that I can try this out with, but if someone else does, please inform me and I will update the information here.
External 3G/4G
It may also be possible to use an external USB SIM Card Modem to get data to work on these boxes (if ever needed). I do not currently have any such device that I can try this out with, but if someone else does, please inform me and I will update the information here.
Thanks: XDA, Freaktab, 4PDA

This section only contains the TWRP files. Other necessary files are in the next section.
How To Get Into LOADER Mode
Loader mode is needed in order to flash ROMs. If you simply connect your Android TV Box with the a USB cable to your PC and power it on, you will only get ADB mode, which will not work.
Plug in the USB cable to a PC and the Android TV Box.
Press and hold the reset button. (On the Z4L/Z4 it will be located on the bottom of the box. On some others it will be in the A/V port, so use a toothpick or paperclip).
Plug in the power adapter while still holding the reset button.
4 seconds should pass before it is in Loader mode.
Let go of the reset button.
DO NOT TRY TO PUT A THIN OBJECT INTO THE Z4L/Z4! There is no back (at least on the Z4L), which means you can go straight into the area of the PCB and possibly destroy something or disconnect the antenna cable.
How To Flash Firmwares/ROMs
You can use either the Android Tool or the Batch Tool to flash IMG files. I prefer Android Tool since it provides more options, but I will explain how to use both.
Open the program of choice.
Switch to the "Upgrade Firmware" tab if using Android Tool.
Click the "Firmware" button (or the 3 dots button for "FW Path:" if using Batch Tool).
Navigate to your "update.img", or the IMG file for your firmware/ROM.
Select the IMG file.
Click "Open".
Click "Upgrade".
The Batch Tool can only do firmware/ROM IMG files, but Android Tool will allow you to flash BIN or entire extracted ROM files.
How To Flash Extracted Firmwares/ROMs
The Android Tool can be used to flash extracted firmwares and ROMs. You will notice that the software comes with a "rockdev" folder filled with IMG and other files. I have come across at least one ROM that was extracted and needed Android Tool in order to be flashed. For the purposes of this tutorial, ROM is interchangeable with firmware.
Open the "rockdev" file of Android Tool.
Go to the "Image" folder.
Replace all the files in the "Image" folder with the extracted IMG files from the ROMs "Image" folder.
Go back up one folder (into "rockdev").
Replace all the IMG files with the extracted IMG files from the ROMs root folder.
If you have any extra files from the ROM that are present in the "rockdev" folder, replace those as well.
For at least the Z4L, be sure that you have the Loader BIN file that is version 2.40!
Open Android Tool.
Put your Android TV Box into Loader mode.
The first tab will show you all the IMG, TXT, and BIN files that you should have from your ROM in the "rockdev" folder. The only file you may not have, but should already be in the folder, is "baseparamer.img". The one that comes with Android Tool will suffice.
Ensure all the check boxes for each IMG, TXT, and BIN file is checked.
Click "Run".
Note: NEVER FLASH AN EXTRACTED ROM ALONG WITH A TWRP RECOVERY! The box will boot immediately into TWRP, making it impossible to ever get to the ROM itself!
Once the process has completed, which should take no more than a few minutes, your Android TV Box will no longer state that is in Loader mode, and will either state no device is connected or "Found One ADB Device". If you see this, or at least that you were successful on the message prompt of Android Tool, then you can go ahead and disconnect everything and boot your box!
How To Flash TWRP Recovery
You will need the Android Tool for this. Download either Abdul's TWRP, Generic TWRP, or Specific TWRP. I have tested and used Abdul's TWRP on the Z4L, and it works without issue.
Change the name of the TWRP IMG to "recovery.img".
Go to "rockdev>Image" of the Android Tool folder.
Replace "recovery.img" with the renamed TWRP IMG.
Open Android Tool.
Uncheck every box except "Recovery".
Put your Android TV Box into Loader mode.
Click "Run".
TWRP is now installed. I am unsure for the other TWRP IMG files, but the Abdul variant will require a mouse in order to be used because the remote is not supported.
How To Root
If your Android TV Box is not prerooted, then you will need to use SuperSU. Download SuperSU from here. If you want to try the latest version, you can find it here. Ensure that you already have TWRP installed.
Place the SuperSU ZIP on your internal or external storage.
Boot into TWRP.
Click on Install.
Add a zip.
Find your SuperSU ZIP file.
Select it.
Flash the ZIP file.
You should now be rooted and can check with an app from the Play Store to verify. I have not tested this as I do not need it, so if any steps are different, please let me know and I will change accordingly.
How To Flash Firmwares/ROMs with a SD Card
You will need the Upgrade Disk Tool and a micro/SD card that is 4GB or more. For the purposes of this tutorial, ROM is interchangeable with firmware, and SD card is interchangeable with micro SD card.
Open the Upgrade Disk Tool (SD Firmware Tool).
Select your SD card from the dropdown menu.
Click the "Firmware" button.
Find your ROM's IMG file.
Select it.
Click "Open".
Click "Create".
Once done, ensure your Android TV Box is turned off.
Insert the SD card into your Android TV Box.
Power on the Android TV Box.
The process will take some time, but a notification of a successful completion will appear when done.
Turn off the Android TV Box.
Remove the SD card.
Power on the Android TV Box.
The Android TV Box should now be "upgraded" to the firmware or ROM you used.
I want to remind people that every time you flash a firmware or ROM, it will take around 10 minutes for the Android TV Box's initial boot into the Android OS.
I may also put some more information here about how to open the compiled IMG files and play around with the system IMG file inside, if people want to know (and I have time).

The Rockchip drivers needed for these tools can be found in Batch Tool v1.8 as "DriverAssitant" [sic].
Android Tool
This is the probably the best tool for flashing and dumping firmware or ROM files:
Android Tool v2.35
Batch Tool
This is a great tool for flashing firmware or ROM files. It is the easiest to use:
Batch Tool v1.8
Batch Tool v1.7
Again, v1.8 has the drivers needed to make all the Rockchip tools function.
Factory Tool
This is a tool that should allow you to change things like the boot animation, add or delete APKs, and even make system clones. However, this does not work with the Z4L. The latest version gets close to completing its initialization process, but fails at the end, keeping all the options grayed out...
Factory Tool v3.4
Factory Tool v4.0
Factory Tool v4.4
Factory Tool v5.0
I have changed a couple of the versions to default to English (or as much English as afforded by the program without too much modification). The others were already in English.
Dump Tool
This is a tool that is essentially Android Tool. I believe that the version of Android Tool I have linked will perform the same functions, but this was one specifically made for dumping stock IMG files. I have used it unsuccessfully, as I can dump all the IMG files, but I am unable to make them work together. However, the "system.img" file may or may not work for modification purposes, but I have yet to check...
Dump Tool v2.3
IMG Mod Tool
This is a great and useful tool for those who want to modify firmwares or ROMs. It allows you to open firmware or ROM IMG files and recompile them. And despite its name, it does work for RK3368 Android TV Boxes.
RK3066 IMG Mod Tool
Upgrade Disk Tool
This allows for "upgrading" your Android TV Box with a different firmware or ROM.
SD Firmware Tool
If I have missed any tools that do something different, have extra functions, or simplify procedures; let me know and I will add them here.

Reserved..

Reserved...

Great consolidated info for Z4 / Z4L RK3368.
Different ROMs being developed for this beast, mostly Z4. IMO best, fastest and stablest is @yablrar mod v1.2 A multi window one is also there. I believe MM 6 is releasing soon.
On a side note:
An easier way to get into recovery/bootloader mode is to use an App like Titanium or other to reboot. No need to tinker around with reset/power buttons.

I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02

Z4 Rockchip Bluetooth Issues
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks

WAIKIKI728 said:
I have this android tv...should your firmware work in it?¿?
http://www.leotec.com/index.asp?acc...LEOTEC&familiaweb=TV&CodigoArticulo=LETVBOX02
Click to expand...
Click to collapse
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
pimpurlid said:
I have the Z4 Rockchip , I have tried 3 different firmwares and I can't bluetooth past 4 feet ? It has 4.0 , is there a way to upgrade it ?
Thanks
Click to expand...
Click to collapse
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.

Heatshiver said:
It might work, yours looks like it does not have wireless AC, so there is a chance. Get a backup of your stock firmware, then try mine out. Be sure to check if your ports, WiFi, and Bluetooth work after flashing my firmware...
The hardware will be near impossible to upgrade, and not worth your time. If you really want to have it work past 4 feet, you would need to buy a Bluetooth signal booster. However, if you are just using a mouse or keyboard, I would try getting a USB 2.4GHz device instead. Those seem to work much better.
Click to expand...
Click to collapse
Thank - You .

Have you tried getting a version of Linux installed on one of these Z4's?
Other other people have got the 64 bit arm version running on devices that use the same chip (RK3386 chip).

how get loader mode
Please help ... I can't make that my pc find the Z4 rk3368 in loader mode, just the ADB mode.. to install you costum ROM Z4L slim..
tank you..

Hi, been trying to install custom roms, with rockchip batch tool and android tool, i am in loader mode and with org cable but all i get is test device fail. I can update stock firmware with usb just can't get custom roms to work. Thanks for any help.

Z4L
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?

Z4 ROM that should also work with the Z4L
d33pblu80 said:
Has anyone installed this rom, any feedback?
I have the Andoer Z4L and wanted to try this as I am experiencing some issues with audio via optical where it drops intermittently. Would any of the Z4 roms for RK3368 work on this device also?
Click to expand...
Click to collapse
My Z4 android TV (ATV) ROM should also work with the Z4L.
Just install my custom Z4 custom ROM available at freaktab. I'm a new user here at XDA so it's not allowed to me to post any external link. So just google for the name of my ROM. "[ROM] Z4 RK3368 - android TV (ATV) for Andoer Z4 - ENY EKB368 - Acemax AK838 - Tronfy X6"
Then just flash on top of that ROM the needed Z4L KRS files (resource & kernel) to activate the Z4L RTL8723bs WiFi chip (also described at my freaktab thread).
Good luck and much fun
-cOOLio-

In the end I gave up.
No one can tell me what is the most complete and working firmware.
All firmware always has something that does not work.
Now I still have the firmware 22.12.2015
It's not really a speed champion, but at least it works at all!

does anyone tell me how to get into recovery mode?
I would like to flash the supersu file, but I can not get into recovery

Nook Simple Touch - Resources?

Hi!
Theres lots of different packages and resources scattered around, and theres missing instructions and unclear details.
Would it be possible to compile a list, with instructions, on modding a rooted NST (/Glowlight)?
I have seen new kernels with USB Host/OTG, multitouch, upgrades, additional launchers etc, but no real details of how to use them, whats the most up to date etc
Thanks!

alexhorner said:
Hi!
Theres lots of different packages and resources scattered around, and theres missing instructions and unclear details.
Would it be possible to compile a list, with instructions, on modding a rooted NST (/Glowlight)?
I have seen new kernels with USB Host/OTG, multitouch, upgrades, additional launchers etc, but no real details of how to use them, whats the most up to date etc
Thanks!
Click to expand...
Click to collapse
Well, that will take a very long time. It's something I've thought about for this year, but it's a big effort.
Suppose you list what you'd like to do, and I'll try to point you in the right directions, in some kind of logical order.

Thanks for such a fast reply!
Referencing https://forum.xda-developers.com/t/share-your-setup-app-list.3143404/
I'd like to get the best kernel I can, with USB HOST and Sound drivers if possible
From that list I can also see of interest:
Extended Power Menu
AndroNook Settings
UsbMode
TuneIn Radio
QQPlayer
FastMode2
Opera Mini
AirDroid
adbWireless
Nook Clear Screen
Terminal Emulator
Stock Settings
Would you have any developers/stock experience and performance/featureset upgrade recommendations too?
Ideally I'd love to write up a page for everything I use with downloads and instructions where applicable
Thanks!
Edit: Tools like OpenSSH and BusyBox would be handy too, though I could probably build those from older sources if I need to

alexhorner said:
Thanks for such a fast reply!
Referencing https://forum.xda-developers.com/t/share-your-setup-app-list.3143404/
I'd like to get the best kernel I can, with USB HOST and Sound drivers if possible
From that list I can also see of interest:
Extended Power Menu
AndroNook Settings
UsbMode
TuneIn Radio
QQPlayer
FastMode2
Opera Mini
AirDroid
adbWireless
Nook Clear Screen
Terminal Emulator
Stock Settings
Would you have any developers/stock experience and performance/featureset upgrade recommendations too?
Ideally I'd love to write up a page for everything I use with downloads and instructions where applicable
Thanks!
Edit: Tools like OpenSSH and BusyBox would be handy too, though I could probably build those from older sources if I need to
Click to expand...
Click to collapse
Most of that list is apps. Give me a day to put something together.

nmyshkin said:
Most of that list is apps. Give me a day to put something together.
Click to expand...
Click to collapse
No rush! Thank you so much for your help

[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernels
The first kernel modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernel has included this change.
Now it gets a little confusing. For practical purposes, only kernels based on at least FW 1.2.1 are of use. Earlier kernels do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernels for the NST/G, one without support for USB Host and two with USB Host support.
Kernel 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernel modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernel modification and an app (link below). Kernel 166 is the only kernel that can run both display modes. Like all kernels that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernel that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernel 166 shows that it is) but only that there is no existing kernel that makes it possible.
The two kernels which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernel in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernel that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernel attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernel into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernel installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernel and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernel just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernel)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling. (or maybe it was SSHDroid?
If there is anything else, or something here is not clear, give a holler.

nmyshkin said:
[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernals
The first kernal modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernal has included this change.
Now it gets a little confusing. For practical purposes, only kernals based on at least FW 1.2.1 are of use. Earlier kernals do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernals for the NST/G, one without support for USB Host and two with USB Host support.
Kernal 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernal modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernal modification and an app (link below). Kernal 166 is the only kernal that can run both display modes. Like all kernals that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernal that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernal 166 shows that it is) but only that there is no existing kernal that makes it possible.
The two kernals which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernal in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernal that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernal attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernal into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernal installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernal and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernal just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernal)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling.
If there is anything else, or something here is not clear, give a holler.
Click to expand...
Click to collapse
Looking very complete, thank you for the awesome work! I'm quite busy but I shall dedicate a couple hours before next week to go through this entire process.
I do have a questions which I think I know the answer to, but wanted to confirm: With NookManager, does it run its own OS from the SD Card, or does the normal internal Flash Storage OS load and then NookManager takes over?
Same with CWM - Does the whole device (properly) boot off of the SD card and not internal flash?
If they do boot off of the card, due to the bootloader (I assume UBoot from what I read, nice!) then that leaves a lot of custom linuxy opportunities available for a really lightweight Linux OS, though drivers might be a painpoint.
Thanks!

alexhorner said:
Looking very complete, thank you for the awesome work! I'm quite busy but I shall dedicate a couple hours before next week to go through this entire process.
I do have a questions which I think I know the answer to, but wanted to confirm: With NookManager, does it run its own OS from the SD Card, or does the normal internal Flash Storage OS load and then NookManager takes over?
Same with CWM - Does the whole device (properly) boot off of the SD card and not internal flash?
If they do boot off of the card, due to the bootloader (I assume UBoot from what I read, nice!) then that leaves a lot of custom linuxy opportunities available for a really lightweight Linux OS, though drivers might be a painpoint.
Thanks!
Click to expand...
Click to collapse
According to my understanding, both NookManager and CWM boot directly from the sdcard. You can check the card contents, replete with its own uboot, mlo, etc. Similar set up as the CM 11 card.

nmyshkin said:
[I'm going to try to address your issues in this single post, but not all at once. I'll be adding things over the next few days. Since I don't know where in the process you are currently, just skip things you have already done]
Updating to FW 1.2.2
[Note: if you have a UK device, go to: https://forum.xda-developers.com/t/nst-g-dealing-with-non-us-aka-uk-devices-in-2021.4233411/ and return here to the "Kernals" section after completing option 3]
If your device is still on FW 1.2.1 you will need to do a manual update. In theory, you should be able to download the update zip from B&N (https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip), connect your NST/G to your PC via USB, copy the update zip to the "Nook" drive and wait. When the device sleeps, the update should be installed. If you come back later and look at the "Nook" drive and you don't see the update zip, it's done. You can check this by looking in the Settings app for the software version.
IF the theoretical procedure does not work for you, a deregistration might be in order. Since a device on FW 1.2.1 cannot deregister by contacting B&N servers (this is generally done via the Settings app), you will have to force a user data wipe. To do this, turn off the device. Power back on and as soon as you see the "Read Forever" screen, press and hold the two lower hardware buttons (page-turn buttons) until a prompt appears. Follow the on-screen directions. This will eventually leave you at the "Welcome" screen. Now attach the device to your PC via USB, drag the update zip onto the "Nook" drive and wait for the update to occur. Again, if you come back later and you don't see the update zip listed on the "Nook" drive, you're done. At this point you can continue and register your device.
IF the second method was unsuccessful, there might be something messed up with the resident FW. In that case, the best course is to initiate a factory re-write of the entire system. The eight-failed-boot attempts is painful and often very frustrating, but NookManager can do the job in the push of a button. So if you are still having issues updating, proceed to the "Rooting" section below and prepare a NookManager card. Then power down your device, insert the NookManager card and power up. Skip WiFi turn on. The "Restore Factory zip" option is found under "Rescue". Follow the directions and after a reboot you will be at the "Welcome" screen on some unknown FW. Attach the device to your PC via USB, drag the update zip to the "Nook" drive, and wait for the update to occur as described above. Once that has happened, continue on to registration.
Rooting
Go here: https://forum.xda-developers.com/t/nst-g-updating-nookmanager-for-fw-1-2-2.3873048/ and choose whichever version of NookManager seems like it will best meet your needs. I strongly suggest you make a FW 1.2.2 registered backup before rooting (NookManager can do this). When your device is rooted and you have done some configuration on the possible launchers and/or file managers, return here to the next section, "Kernals".
Note: regarding your question about ssh and busybox, the latter is installed during rooting with NookManager. I'm really not familiar with ssh but I note that you can supposedly use it with NookManager running. There is some info on the opening screen where the WiFi option is located.
Kernals
The first kernal modification was for multi-touch to enable pinch-zoom for those apps that would support it on the NST. Every subsequent kernal has included this change.
Now it gets a little confusing. For practical purposes, only kernals based on at least FW 1.2.1 are of use. Earlier kernals do not understand glowlight control (you can work around this, but why bother?). So there are more or less three "modern" kernals for the NST/G, one without support for USB Host and two with USB Host support.
Kernal 166 (see attachment below) does not support USB Host but it does support both augmented display modes, NoRefresh and FastMode (with the appropriate apps installed). NoRefresh is an augment for flicker-free reading when scrolling in an app (like a webpage, for example) or when moving around on a PDF image. Based on the original development thread, this appears not to require kernal modification, only the installation and configuration of an app (link below). FastMode is an augment for, well, I guess for playing with video. It presents a highly dithered image (lots of tiny dots) in an attempt to simulate greater grey-scale. Initially it seems like a good idea (impressive coding, anyway) but it's not good at all for reading and there is a lot of ghosting in video until the screen is finally filled with swirls of dots in various states of visibility. At least that was my experience. FastMode requires both kernal modification and an app (link below). Kernal 166 is the only kernal that can run both display modes. Like all kernals that support FastMode it is overclocked, supposedly up to 1100 Mz, although I never saw it indicated more than 1000 Mz. When running it you probably should have a CPU governor app installed (download below), perhaps trim the CPU down to 800 Mz to help with battery life.
NoRefresh and FastMode both require apps to activate the display augments (not simultaneously). But the point of all this (since you want USB Audio) is to try to make clear(?) that any other kernal that supports FastMode kills NoRefresh (somehow). So, if you want USB Host/Audio (and you do) then you have to choose which display augment you want because you can't have both. That is not to say it's impossible (clearly kernal 166 shows that it is) but only that there is no existing kernal that makes it possible.
The two kernals which support USB Host probably have numbers. Maybe one of them is 174. But probably nobody knows at this point. The kernal in the CWM zip for enabling USB Audio (with all the nifty drivers) is an overclocked kernal that supports FastMode. If you would prefer to have access to NoRefresh instead of FastMode, you can use the kernal attached below (can't find the original link, so...). Just open the CWM USB Audio zip in something like WinRAR and drag the new kernal into the "boot" folder, replacing the file already there. Be sure to not recompress the file. Use the "store" or similar option when dragging into the opened archive.
Kernal installation can be done via adb. The directions for that are here. But since you have the CWM zip available and want to install all the audio stuff as well, the easiest path is via CWM. That means you need a card.
Download one of the two sdcard options from here and burn a card (do NOT install CWM internally on the NSTG! It will replace the fail-safe factory image!!). Then copy the zip with the kernal and audio drivers to the card and boot your NSTG from the CWM card. Install from the zip and you're good to go after a reboot. If you change your mind later about the kernal just swap in the one you want in the zip file and flash the whole package again.
Two details on this CWM USB Audio package: microphone recording is not entirely/correctly implemented in the files as supplied. If that is not important to you, skip to the next stuff. If you want to get it done right and then forget about it, you need to replace one of the files in the zip with a corrected version and you also need to copy a patched version of framework.jar into /system/framework. The zip of patches below contains the framework.jar and a file called alsa.default.so. You can use a file manager to copy the framework.jar into /system/framework. Be sure the permissions are set the same as the original (you can rename original to framework.jar.bak first, if you want). Then reboot.
As for the little alsa file, open the CWM USBAudio zip and navigate inside to system/lib/hw. You'll see the original file there. Drag the replacement over and be sure not to recompress it (i.e., use "store" or similar). Now the zip is good to go for a complete USB Audio installation including both playback and recording. Whew!
USB Audio
Of course, it's not that simple. There's no headphone jack or speakers. How does the audio come out?! You need two pieces of hardware (three, if you count earbuds/headphones---or a cable to attach to the auxiliary jack of your sound system) and some software.
USB Host in general requires the use of an OTG cable stub. This seems to be a very critical part of the arrangement. My first cable fit poorly and I almost gave up on the whole enterprise. A second one fit in the slightly non-standard USB jack like a hand in a glove. Suddenly it all worked! I can't tell you which cable might work for you. They are cheap (that's part of the problem...) and you may need to try more than one. Amazon, ebay, etc. Some are straight-line, others 90 degrees. What's important is a good fit. I'm not saying the example in the link above is a good fit. I got mine so long ago I have no idea where it came from. Probably ebay. Long gone.
Since the NSTG has no sound hardware, you need a USB-C external sound card device (here's another link to the button/LED kind--expired, but you get the idea). These also are not very expensive and can be found on Amazon or ebay. There are two basic designs. One has a bunch of LEDs that just waste battery power. It may also have volume control and/or other buttons. The other one is more spartan, lacking LEDs and buttons. I have one of each and never use with one with the LEDs.
To initiate USB Host or Audio you need at least one app (each). @Renate has produced an app for USB Host and an additional one for USB Audio. They can be downloaded from her signature page. Both are used to activate USB Audio. They are great for diagnostics but I just never have any issues with USB Host (that perfect plug!) so I wanted something that would be simpler. Just one touch. I made two small apps, one for USB Host (does not activate audio stuff) and one for USB Audio (sets up host and activates audio). The latest version of the USB Audio app places volume control buttons on the screen when in use, so you really don't need a device with volume buttons. My apps are found here. These routines are also included as options in my QuickTiles app.
ADB
You didn't specifically mention ADB so perhaps you are already fixed for that or maybe don't think you'll want it. There are certainly some things that are really only possible with ADB when you start getting down and dirty with the device. But a good file manager and/or terminal app can also do a lot of stuff without ADB. Still, if you don't have it, the easiest way to get just ADB and not the entire Android SDK is to download and install Minimal ADB and Fastboot. This is for Windows. If you're using a Mac, you're on your own.
The apps in your list
I'm going to try not to editorialize too much here, but some things may not work as well as they sound and there might be better alternatives to others, so...based on my experiences (and prejudices...).
Extended Power Menu (caution, "reboot to recovery" option goes straight to factory re-image without any chance to say no! A possible alternative, my Alternate Power Menu app)
AndroNook Settings (I had trouble with this and the stock B&N system; some settings don't seem to work, some cause a reboot. A possible alternative my Nook Settings app--not as tidy but full-featured)
UsbMode (this is the kernal thing and/or maybe the activating app--already covered above)
TuneIn Radio (still works great, available in the package of apps linked in my signature)
QQPlayer (@pinguy1982 posted this copy--MX Player w/codec pkg also is great--again in my app pack)
FastMode2 (app already linked above; needed to activate FastMode with supporting kernal)
Opera Mini (installed with the updated NookManager packages. Direct link to Opera archive)
AirDroid (also, if you use ES File Explorer it has a "remote manager" capability. Creates an FTP address. You type in the address in the Windows Explorer address bar and voila, you can move files back and forth via WiFi. Hard to get to, though, buried in the app settings, so I made a little app to access directly. Also available as an option in my QuickTiles app.
adbWireless (ADB Konnect is installed by NookManager. One drawback: for long sessions you need to extend screen timeout since connection seems to drop when screen goes into sleep mode)
Nook Clear Screen (I found this not very useful; maybe I have a greater tolerance for little screen artifacts. Also available as an option in my QuickTiles app.
Terminal Emulator (couldn't track this one down in the forum so I uploaded a copy below)
Stock Settings (well, this is what's on the device out-of-the-box!)
I think (hope) that covers everything you mentioned. I did see a reference to an app called DroidSSH while I was tracking down some of this stuff, but no link. If that's something you might find useful, you'll need to do a lot of Googling. (or maybe it was SSHDroid?
If there is anything else, or something here is not clear, give a holler.
Click to expand...
Click to collapse
Kernel installed via CWM, USB audio working! Not a fan of FastMode and can't be bothered to mess with NoRefresh yet. Going to look at the OpenSSL stuff soon I think though.
Installing various apps from your list above and also your personal app list as linked in your signature, thank you once again!

Database Users

welcome