Related
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
Backup TA for Sony Xperia™ (Mac OS X version)
With this app you can backup and restore the TA partition of your device.
This can be useful, for example, when you want to unlock your bootloader and not lose your DRM keys and most importantly, your warranty. Before unlocking your bootloader, backup your TA with this app and you will be able to restore it to a factory state (locked bootloader, DRM keys intact, etc).
The app is based on TA Backup v9.10 by DevShaft (thanks !), which can be found here.
View attachment 2573685
Downloads
Frequently asked questions
Source code
Issues
Thanks a lot for bringing this to Mac OS X and make it open source as well! Will have a look at the source and your work at a later time.
Stuck on requesting root on the first try, successful in the second time.
stanley321 said:
Stuck on requesting root on the first try, successful in the second time.
Click to expand...
Click to collapse
Did SuperSU ask you to grant permissions to "shell" when it hanged ?
limiter121 said:
Did SuperSU ask you to grant permissions to "shell" when it hanged ?
Click to expand...
Click to collapse
I have granted SU permission to shell, so it won't prompt anyway.
The app is then not responding and I have to force close it.
stanley321 said:
I have granted SU permission to shell, so it won't prompt anyway.
The app is then not responding and I have to force close it.
Click to expand...
Click to collapse
Yeah, the app will appear to hang but it actually waits for adb to work it's magic.
Is there any chance you could send me a copy of the system log ?
To do so, open the Console app, enter "Backup TA" in the search field in the top right corner (to filter the logs) and make sure that "All Messages" is selected in the Log list (sidebar) on the left side of the window. At this point there should be lots of messages from Backup TA shown. You can now go to File -> Save a copy as... and send that file to me so I can look at what went wrong.
Thanks :fingers-crossed: !
limiter121 said:
Yeah, the app will appear to hang but it actually waits for adb to work it's magic.
Is there any chance you could send me a copy of the system log ?
To do so, open the Console app, enter "Backup TA" in the search field in the top right corner (to filter the logs) and make sure that "All Messages" is selected in the Log list (sidebar) on the left side of the window. At this point there should be lots of messages from Backup TA shown. You can now go to File -> Save a copy as... and send that file to me so I can look at what went wrong.
Thanks :fingers-crossed: !
Click to expand...
Click to collapse
Tried but nothing show up after the search!?
So I think it is just a case that I'm too hurry to check the app and closed it earlier than I should while it is working.
stanley321 said:
Tried but nothing show up after the search!?
So I think it is just a case that I'm too hurry to check the app and closed it earlier than I should while it is working.
Click to expand...
Click to collapse
Try selecting system.log in the sidebar and then search for Backup TA, it should work.
Anyway, I'll implement a better way to get logs from the app soon
limiter121 said:
Try selecting system.log in the sidebar and then search for Backup TA, it should work.
Anyway, I'll implement a better way to get logs from the app soon
Click to expand...
Click to collapse
I find it but can't get it up here...
We are sorry, your post was flagged by our system and was blocked from submitting. If you believe this was in error, please contact an admin to report this.
Looking at it, I think I just closed it too early. Nothing wrong with your part!
stanley321 said:
I find it but can't get it up here...
We are sorry, your post was flagged by our system and was blocked from submitting. If you believe this was in error, please contact an admin to report this.
Looking at it, I think I just closed it too early. Nothing wrong with your part!
Click to expand...
Click to collapse
Too bad about the log, but thanks a lot for testing and helping
limiter121 said:
Too bad about the log, but thanks a lot for testing and helping
Click to expand...
Click to collapse
Checking the timestamp, maybe you should add a message to ask the user to wait for at least a minute to prevent nervous users like me from closing it too early.
Sorry for being new to this TA thing, I don't know how long I should expect.
stanley321 said:
Checking the timestamp, maybe you should add a message to ask the user to wait for at least a minute to prevent nervous users like me from closing it too early.
Sorry for being new to this TA thing, I don't know how long I should expect.
Click to expand...
Click to collapse
No problem, will add it in the next version
Thanks for bringing this in a simple form to MacOS
Already backup up, but did another backup and did the test; all seemed well.
New version 1.1 (2) available !
Download it here.
Changelog :
Added better log handling. You can now see the log files using Help -> Open logs folder
UI does not lock (beachball) anymore during lengthy backup/restore operations
limiter121 said:
New version 1.1 (2) available !
Download it here.
Changelog :
Added better log handling. You can now see the log files using Help -> Open logs folder
UI does not lock (beachball) anymore during lengthy backup/restore operations
Click to expand...
Click to collapse
make it for linux please :angel:
thanks
imen27 said:
make it for linux please :angel:
thanks
Click to expand...
Click to collapse
I will take a look, but don't get your hopes up
limiter121 said:
I will take a look, but don't get your hopes up
Click to expand...
Click to collapse
sounds great,many thanks
New version available
New version 1.1.1 (3) available !
Download it here.
Changelog:
Enabled verbose logging (for tracking down issues)
Big update
New version 1.2 (4) available !
Download it here.
Changelog:
Added auto-update support
Improved reliability (by using bundled BusyBox commands)
Bug fixes
limiter121 said:
New version 1.2 (4) available !
Download it here.
Changelog:
Added auto-update support
Improved reliability (by using bundled BusyBox commands)
Bug fixes
Click to expand...
Click to collapse
Thanks, mate. I think it worked. Just one question: is it normal that a 2MB TA partition gets zipped into few KB? Something like 77KB. Are those sizes (for both TA partition and zip file) normal?
Hello, I just bought a new motoactv.. But I now see, that because of the fact they shut down Motoact, I cant create an ID. and therefor I cant use the watch as it is. I could root it, but I dont think it will give me the functionality (advanced interval for running) as it can now.
so..is there anyone who can give me their login as they dont use Motoactv.com anymore?
Would be highly appreciated!!
muish002 said:
Hello, I just bought a new motoactv.. But I now see, that because of the fact they shut down Motoact, I cant create an ID. and therefor I cant use the watch as it is. I could root it, but I dont think it will give me the functionality (advanced interval for running) as it can now.
so..is there anyone who can give me their login as they dont use Motoactv.com anymore?
Would be highly appreciated!!
Click to expand...
Click to collapse
Just register new account from your watch.
VjFill said:
Just register new account from your watch.
Click to expand...
Click to collapse
Yeah, but since the pc doesnt recougnise the watch as a USB storage device, and WIFI cant be installed, I never get to create an account. I now have the account details of the person where I bought it from, but I suppose I can as well throw it away, Motorola doesnt give support either.
muish002 said:
Yeah, but since the pc doesnt recougnise the watch as a USB storage device
Click to expand...
Click to collapse
Stop adbd shell in your watch.
Easiest way - via MotoACTV Root Tool from http://www.cleardroidroms.com/motoactv.php
muish002 said:
WIFI cant be installed, I never get to create an account.
Click to expand...
Click to collapse
Go to 'Settings' screen -> Wireless -> Wifi -> Add network
VjFill said:
Stop adbd shell in your watch.
Easiest way - via MotoACTV Root Tool from http://www.cleardroidroms.com/motoactv.php
Since the watch is not recougnised as storage device, I cant see it in explorer either. So I cant, unfortunality, root it either.
Go to 'Settings' screen -> Wireless -> Wifi -> Add network
Click to expand...
Click to collapse
No, it then sais, add a new network with your pc.
I hope you have THE tip..I tried everything, but sofar nothing worked.
muish002 said:
No, it then sais, add a new network with your pc.
I hope you have THE tip..I tried everything, but sofar nothing worked.
Click to expand...
Click to collapse
Again. Disable adbd - then you will be able to connect Motoactv as a USB storage.
muish002 said:
it then sais, add a new network with your pc.
Click to expand...
Click to collapse
Looks like a custom firmware.
Go to Settings -> General -> Motoactv status -> Software version.
Post it here.
VjFill said:
Again. Disable adbd - then you will be able to connect Motoactv as a USB storage.
Oh, I completely overlooked this last time. Great, that worked
Looks like a custom firmware.
Go to Settings -> General -> Motoactv status -> Software version.
Post it here.
Click to expand...
Click to collapse
It sais 4.54.50
I am goimg to try and root it!
muish002 said:
It sais 4.54.50
I am goimg to try and root it!
Click to expand...
Click to collapse
This is initial release or first maintenance version. A really old software.
Update your Motoactv to latest and root only after that.
Keep in mind that versions for 8Gb and 16Gb are different. Choose firmware only for your device.
OR
Install Motorola Device Manager from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Plug in your Motoactv.
MDM has to check it and upgrade to latest (but I have no idea, will it be correct as I have never seen such old firmware like yours)
'Advanced functionality' won't be enabled with root.
Interval training can be enabled/planned via Motoactv portal.
So, upgrade your watch, add new wifi from settings -> wireless, then register new account, go to http://motoactv.com
Voila.
VjFill said:
This is initial release or first maintenance version. A really old software.
Update your Motoactv to latest and root only after that.
Keep in mind that versions for 8Gb and 16Gb are different. Choose firmware only for your device.
OR
Install Motorola Device Manager from here https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Plug in your Motoactv.
MDM has to check it and upgrade to latest (but I have no idea, will it be correct as I have never seen such old firmware like yours)
'Advanced functionality' won't be enabled with root.
Interval training can be enabled/planned via Motoactv portal.
So, upgrade your watch, add new wifi from settings -> wireless, then register new account, go to http://motoactv.com
Voila.
Click to expand...
Click to collapse
I already rooted it I think.
Problem is, when I run motorola device manager, it only says, no updates and at device it says "N/a"? So no clue how to get the latest software on it.
muish002 said:
Problem is, when I run motorola device manager, it only says, no updates and at device it says "N/a"? So no clue how to get the latest software on it.
Click to expand...
Click to collapse
Uninstall Motorola Device Manager.
Install this version - https://drive.google.com/file/d/0B9ZhejL5ANmGQjdreG5jR3YybTg/edit
2.4.5 definitely had correct drivers.
Check that battery on your watch is fully charged.
MDM has to detect your Motoactv correctly, search for software and upgrade it,
If it won't - look here http://forum.xda-developers.com/showthread.php?t=1534073
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Click to expand...
Click to collapse
Links are in the first post.
at the end, I got it working. Even wifi, although that was on ly a few times, since then I cant login anymore. I am about to sell the watch, as its realy bad in GPS for running (as it was bought as running watch), so I will just sell it as smart watch. But then I do need some apps installed on it. But when you install one app, its full, now trying to get it to install on the SD memory, but again.. not so easy!
In the process of trying out an app for dealing with MediaScan (which seems to have screwed with my NST, so don't ask), I caught a fleeting glimpse of the developer options settings screen! It may be that things there (like USB debugging) don't generally work, but I have to ask: does anyone know how this hidden section can be accessed on the (rooted)NST?
The typical "tap 7 times on the build number in About" doesn't work because there is no build number and nothing else there responds to 7 taps.
So?
@nmyshkin,
Yes, there are two main ways to access Develoment Settings. Number one is through a shell, ADB or local:
Code:
am start -n com.android.settings/.DevelopmentSetting
You can also install my one of my alternate Settings.apk files, in which Development Settings is accessible from the regular Settings screen. The original development project can be found here: AndroNook Settings.
Hope this helps!
ИΘΘK¡€ said:
@nmyshkin,
Yes, there are two main ways to access Develoment Settings. Number one is through a shell, ADB or local:
Code:
am start -n com.android.settings/.DevelopmentSetting
You can also install my one of my alternate Settings.apk files, in which Development Settings is accessible from the regular Settings screen. The original development project can be found here: AndroNook Settings.
Hope this helps!
Click to expand...
Click to collapse
I assume the ADB access does not actually make the menu option appear but instead simply gives direct access to a known command?
I did look at the AndroNook settings but don't have a ROM in place that is compatible.
nmyshkin said:
I assume the ADB access does not actually make the menu option appear but instead simply gives direct access to a known command?
I did look at the AndroNook settings but don't have a ROM in place that is compatible.
Click to expand...
Click to collapse
That is correct, the command launches the activity directly.
What ROM do you have installed? I have made a compatible version for every ROM I know of for the Nook Touch (stock rooted, 1337, and Tweaked Modded), so I don't know how you aren't compatible.
ИΘΘK¡€ said:
That is correct, the command launches the activity directly.
What ROM do you have installed? I have made a compatible version for every ROM I know of for the Nook Touch (stock rooted, 1337, and Tweaked Modded), so I don't know how you aren't compatible.
Click to expand...
Click to collapse
I'm using--I guess--the stock rooted(?) and I suppose that the kernal changes don't affect that, based on your question? (I'm using the kernal that pinguy most recently packaged with the USB Host/audio stuff).
nmyshkin said:
I'm using--I guess--the stock rooted(?) and I suppose that the kernal changes don't affect that, based on your question? (I'm using the kernal that pinguy most recently packaged with the USB Host/audio stuff).
Click to expand...
Click to collapse
Stock rooted would be if you rooted your Nook with a rooting tool (like, say, NookManager), but didn't flash one of the two available ROMs afterwards.
And yes, none of the UsbToCom/UsbSound kernel stuff affects Settings.apk at all, so you're good to go.
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for options 3 or 4 it does not matter as much because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Nook" logo screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there are only two working reader apps besides the stock Reader that can handle Adobe DRM protected epubs: Mantano 2.2.3 Premium (activated or not), and Aldiko 2.0
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions. Since the site seems to be down, here is a link for the image zip.
b. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
c. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Eject the device from the USB connection and tap the power button to put it to sleep. If you hang around you may see the device wake up and the update commence. Otherwise come back awhile later. If the update zip is no longer visible on the Nook drive when it is reconnected to your PC via USB then the update has been done.
d. Register your device. Remember you don't need to use a credit card, just an email address.
e. If you wish to root the device select one of the updated versions of NookManager for FW 1.2.2 that are given here.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
4. Try out my unofficial UK FW 1.2.2 update.
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
pkk11 said:
Hello nmyshkin, so glad I found your post! I resurrected one NST glowlight that had problems just now. Thanks a lot!! I followed your instructions, changed region to US, updated to 1.2.2, then used Nook Manager to root. A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
Yes, it is possible but there are some special issues surrounding the Glowlight model.
The definitive DIY summary for USB Audio by @Renate NST is buried deep in the original USB Host development thread: https://forum.xda-developers.com/t/wip-usb-host-support-working.1457971/page-19#post-43281985
I recollect that there is a minor path error somewhere in the description, but I will have to search around to find that.
For those who would rather not get their hands quite so dirty (or who don't trust their hands...), there is a CWM-flashable zip prepared by @pinguy1982: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/. This is what I have used since my first initial set up following the DIY directions, although I swapped in a different kernal. More on that later. The advantage (beyond the obvious) is that the zip contains a tweaked set of audio drivers.
Here, too, there were a few minor issues which I corrected in my own copy, although clearly the package works as it was originally posted.
The issue with the Glowlight revolves around the choice of USB Host-enabled kernals. The one referenced by @Renate NST is for FW 1.1.5. It also enables multi-touch and allows you to run NoRefresh display mode if you desire. However, FW 1.1.5 was written when the concept of the Glowlight was just a glimmer in some developer's eye. Consequently it behaves poorly with the Glowlight control, in essence separating the actual light function from the light icon in the status bar. I use this kernal with my Glowlight because I also run my QuickTiles app and it controls both the light and status bar icon, bypassing the system controls. The reason I chose this kernal is because it allows the use of NoRefresh which I feel is superior to FastMode for text reading.
As far as I know all of the other USB Host-enabled kernals are over-clocked kernals that were designed to allow the usage of the FastMode display mode. This is true of the kernal included in the CWM zip created by @pinguy1982. None of these kernals, to my knowledge, will also work with NoRefresh. There is only one kernal that allows you to use both NoRefresh and FastMode (not at the same time, of course) and that is kernal 166--but for some reason this was not the base for adding USB Host to a 1.2.x kernal. Maybe there is an essential incompatibility. It's way beyond my pay grade.
I've meant to look at this more closely and get some definitive information. This will take a few days and involves backing up my device and trying the various kernals. There is one that claims to support the Glowlight function, USB Host, and NoRefresh but I suspect the author of that post was being sloppy in describing the screen refresh mode.
Anyway, that and tracking down the other minor issues I mentioned above will likely take a few days.
Yeah, I didn't have anything to do with the kernel mods on the NST for USB host mode.
There is one patch for audio sample rates on the page for MergeSmali (in sig).
The current UsbMode-2.2.apk supports NST and Glows (although the Glows need the injectd daemon also).
pkk11 said:
A follow up question I had was with regards to enabling sound through the micro USB - I found that in the past it was possible here, however, I am not sure how to go about this, as it seems that its another launcher and not Nook Manager. Could you please let me know if this is possible?
Many thanks in advance!
Click to expand...
Click to collapse
OK, so I'm glad you asked this question because it prompted me to look more closely at the kernal issue and I found that there is an appropriate kernal for the Glowlight!
CAUTION: before you do this, use NookManager to make a backup of your device.
For audio playback:
You will need a CWM card to flash the zip. You can make a card from one of the two files at: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. There is a "2 gb" file and one for "128 gb". The card you choose should have at least the capacity mentioned in the file name. Download the file, unzip and burn the image to an SDcard. DO NOT try to install CWM directly onto your device. This will destroy the one fail-safe that makes the NST so hard to kill: the factory image.
Next, download the CWM-flashable USB Audio zip from here: https://forum.xda-developers.com/t/cwm-usb-audio-enabler.3139603/
The kernal in this zip is based on 1.2.x so it will work with a Glowlight. It includes multitouch, enables FastMode (with the appropriate app), and USBHost. It is overclocked, so you may want to install some kind of CPU regulator to calm it down. It will not work with the NoRefresh app.
If you would prefer a kernal that is not overclocked and works with NoRefresh (but not FastMode), you can download the zips here: https://forum.xda-developers.com/t/nstg-kernel-multitouch-usb-host-kernel.2846867/#post-54803848. Unzip the files. Open (not unzip) the CWM-flashable USB Audio zip and inspect the contents (WinRAR allows this kind of thing, not sure about other archiving software). In the "boot" folder you will find the two kernal files. Drag the replacement files you downloaded into this folder (within the archive) and set the overwrite to "storage" or "store". You don't want any more compression going on. Then close the archive.
Once you have the CWM-flashable zip set up the way you want it, copy it to the CWM card. Power down the NSTG, insert the CWM card, power up and wait for completion of boot. This is the button function layout for CWM:
Button layout:
Both Buttons on the left: BACK
Upper button on the right: UP
Lower button on the right: DOWN
n button: SELECT
Power button: TOGGLE DISPLAY
Once you've flashed the zip, you'll need to reboot. If there is a message about possibly losing root, etc., just say no. I've been down that road before.... By attempting to fix a non-existent problem it will create that very problem. So don't let it "fix" nothing.
You need some hardware to make all of these changes actually do something. Also a little software. As far as the hardware, you need an OTG cable (e.g. https://www.ebay.com/itm/Micro-USB-...48?hash=item365c5af32c:g:LmEAAOSwa6heLwTo)and a USB-C audio thingy (e.g. https://www.ebay.com/p/94253551?iid=383621510193 or https://www.ebay.com/itm/Sabrent-Us...259335?hash=item42166fae07:g:v~kAAOSwG5ZekgAB). Both are available on ebay or Amazon and are not expensive. Some audio gizmos include volume control buttons, some don't. I have one of each, but don't use the one with the buttons because it's full of LEDs and the whole USB Host thing drains power anyway, so who needs a bunch of lights?
Some people have had issues with USB Host. I suspect it's because of the OTG cables. The first one I got just did not work. The USB socket on the NSTG is not exactly an industry standard and the cheap OTG cables are not precision instruments. I finally got one that fits well but I have another (right-angle model) which sticks out half-way when fully inserted. It works, but it's worrisome. Also, do not let the cable and audio gizmo dangle. Everything should be on a flat surface. If you put stress on the USB jack and make it unhappy, you're going to have trouble doing something very important: charging. I speak from experience.
Now the software. To activate USB Host (and Audio) you need one or two apps. @Renate NST has a USB Host app as well as an Audio Control app. Both are needed for Audio and are useful if you need to troubleshoot. They can be downloaded from her signature link.
I have found that with a good OTG cable I never have initialization issues with USB Host (on all three devices I own). So I wrote a little one-touch toggle app to turn USB Audio on and off. There are screen prompts to tell you when to connect and disconnect things. Version 4 of the app displays on-screen volume controls as well. You can find that here: https://forum.xda-developers.com/t/app-nst-g-usb-one-touch-toggles.3172213/. The same functionality is also built in to my QuickTiles app, although with nicer screen prompts
If you get this working and are interested in audio recording with the NSTG, there are a few more things to do, but we'll leave that alone for now.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
alexhorner said:
Heads up, this link https://sites.google.com/site/xcdguides/nook/nookregion on option 3 no longer works but it is archived at https://web.archive.org/web/20210821235751/https://sites.google.com/site/xcdguides/nook/nookregion and the dropbox download on that page works fine still and is https://www.dropbox.com/s/nwtz0wi6kpb1d3u/nook_region_changer.zip
Click to expand...
Click to collapse
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
nmyshkin said:
Thanks. I noticed the site was down just today whilst trying to help another UK individual. Fortunately I had archived the image zip some time ago against a day such as this. And I, too, referred him to the Wayback machine archive, but I didn't think to test the direct dropbox link. That was clever.
Good grief. Is nothing sacred?!
Click to expand...
Click to collapse
Self host FTW!
alexhorner said:
Self host FTW!
Click to expand...
Click to collapse
yah....my Mediafire account is almost full now with all the NST and Nook Tablet stuff I'm trying to save from oblivion. Hope there's room for this one more.
nmyshkin said:
Wow...I seem to spend a lot of time trying to help people get going with their NST only to find out half-way through the process that they have a non-US device. This changes a great deal. There are advice and hints scattered all over in various threads and it seems like maybe it would be a good idea to get it all in one place. Here.
When B&N abandoned UK devices the current firmware was 1.2.1 but this is not the same as the 1.2.1 firmware on the US version of the device. The main difference is that the URLs used to contact B&N servers were different, the default dictionary was Oxford, and the Settings had actual localization options (or perhaps I should say "localisation") for various countries/languages. This allowed the user to see familiar language in the on-screen system.
The problem
Someone who gets a used non-US device will probably get it reset or want to reset it before doing anything else. And then you are stuck because you can't get past much before it gives an error since it can't contact non-existent URLs. You can't update to FW 1.2.2 because non-US devices will not accept the update.
B&N's "answer" to this dilemma has been reported joyfully on the Mobilread forum. They suggest you skip registration altogether (known as "Skip OOBE") and use the device for reading side-loaded books. What they don't tell you is that skipping registration results in a device with markedly shortened battery charge life. A logcat of such a device shows that the system is constantly churning away, trying to figure out why it can't contact B&N.
Options
I'm not saying that what I present here is exhaustive. There are probably people a lot more clever than I who have come up with other approaches. Still, in order from least good to most good:
Note: if you cannot get to the "Welcome" screen or are stuck on some other screen such as "Network error", you will need to do a "soft reset" before pursuing options 1 or 2 (for option 3 it does not matter because you will be booting from various cards). To perform a soft reset, power down, then power up again but as soon as you see the "Read Forever" screen, press and hold the two lower hardware (page-turn) buttons until a prompt appears. Follow the screen directions. This will eventually leave you at the "Welcome" screen.
1. Take B&N's advice. To skip OOBE:
a. Turn on the device and let it boot to the "welcome" screen.
b. Hold down the top right hardware button on the front of the device and slide your finger from left to right across the top of the screen. A "Factory" button should appear in the top left corner of the screen. Tap it.
c. Once again, hold down the top right hardware button and tap the bottom right corner of the screen.
d. A "Skip OOBE" button should appear. Tap it and the device will complete initialization.
e. If you wish to root the device (which is presumably running FW 1.2.1), you can use the updated Nook Manager package which will still work with FW 1.2.1
Note: this configuration may give errors when you attempt to connect to a WiFi source and you will experience a shorter usable charge time.
2. Improve on B&N's advice.
If you follow these steps you will eliminate the inordinate power drain caused by skipping registration--but at a cost: the "guts" of the B&N system. This means you will need to select and install a reader app, dictionary, file manager and launcher of your own. I have done this and it works fine, but it does involve a little tinkering.
a. Follow steps in #1 above (including rooting).
b. Install (side-load via your SD card or use ADB) apps for a reader, dictionary (if wanted), file manager and launcher. There are many choices, but these were mine: AlReader, ColorDict3, ES File Explorer, ADW Launcher.
c. Use NookManager to remove all B&N apps (one of the options). Note that the original NookManager package does not do a proper job of this, so be sure you are using one of the updated versions.
Note: to my knowledge there is only one working reader app besides the stock Reader that can handle Adobe DRM protected epubs. Mantano 2.2.3 Premium (activated or not)
3. Convert your device to US firmware and update to FW 1.2.2
a. Go here and follow the directions.
b. Select one of the updated versions of NookManager for FW 1.2.2 that are given here.
c. Download the FW 1.2.2 update from B&N: https://su.barnesandnoble.com/nook/nook2/1.2.2/351e26527e80156183e74be2da2ce89f/nook_1_2_update.zip
d. Power on the device and at the "welcome" screen connect it via USB to your PC. Drag the update zip to the "Nook" drive that you will see. Allow the device to sleep. Come back awhile later. If the update zip is no longer visible on the Nook drive then the update has been done.
e. Register your device. Remember you don't need to use a credit card, just an email address.
f. Use the updated NookManager card to root and perhaps customize your device.
Note: it has been reported that you will not be able to purchase books from B&N. Also, you will have a Merriam-Webster US-English dictionary instead of the Oxford dictionary. And....localization is locked in the Settings app to "US", with no other options.
g. If you prefer the Oxford dictionary, you can download a copy of the UK 1.2.1 update zip at the bottom of the region changer page.
The dictionary files are located in /system/media/reference/ . Compare what's there with what's on your device and replace. Be sure the file permissions are set the same as what was there before. Reboot.
h. You will need ADB access (either via USB or WiFi) to see the complete localization menu. Connect to the device via ADB and type:
adb shell
am start -n com.android.settings/.LocalePicker --ez hideDevLanguages false
Select the language you prefer. This may cause a reboot.
If you don't have/want ADB, you can install my Nook Settings app. It gives full access to the LocalePicker. If you don't want the app, you can uninstall it after making the Locale change.
Click to expand...
Click to collapse
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
alexhorner said:
How would you recommend I copy and replace the dictionaries from the original 1.2.1 firmware file? It does not appear to be a zip file even though it is labelled as such
Click to expand...
Click to collapse
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
nmyshkin said:
I have a vague recollection that it can't be cracked by simply Windows. I believe WinRAR or 7zip will work. I'm downloading a copy from my archive as I type and will give it a shot. I know it can be/has been done.
Yep, WinRAR. I'll just extract the dictionary file and attach it here. Or not. Mmm....too big.
So....you'll need either WinRAR or 7zip to do the job.
Click to expand...
Click to collapse
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
alexhorner said:
Had some trouble with 7Zip too, but after opening 7Zip on its own and manually selecting the file, it extracted.
I took the ox_en_GB.db file (the only one in there) and placed it in /system.media/references and 644'd it which is what the other files in that directory were. Nothing to replace, just add. No idea if it works or how to test it, but at least the file is there if I ever wish to use it.
Managed to get the system locale changed fine with NookSettings too, so now thats all good!
Click to expand...
Click to collapse
The only way to test the dictionary is to load up an ebook, long-press on a word, select "Look up" and see what happens.