Related
heard that NT may have BL lock, it really is a bad news.
i'm wondering whether NT support normal apk downloaded from other places?
like installing with other markets and use these markets to install apks?
and could someone tell me the influence if we can't crack this lock?
can we reformat the partitions?can we root the device?
thank you!
Check some of the other threads. Much progress has been made, and its very easy to side load apks.
While no one has rooted it yet, it's still very early. Give it time.
Sent from my SPH-M820-BST using XDA App
yeah, i saw many guys said they sideload the apps, but i don't understand what is sideload
Sideload = loading apk onto an sd card. You can then put sd card into NT and install app that way.
You will need to first enable apps for unknown sources, you can find how to do this in a number of threads.
ms2003 said:
yeah, i saw many guys said they sideload the apps, but i don't understand what is sideload
Click to expand...
Click to collapse
Sideloading is the installation of an app from a non-approved source. This can involve installing via downloaded or transferred APKs, installing from a sd card, pushing via ADB, etc.
i got it, this means if i have 3rd party market or apk files, i can install applications in NT
ms2003 said:
i got it, this means if i have 3rd party market or apk files, i can install applications in NT
Click to expand...
Click to collapse
As a rule, it appears that you can install most apps by sideloading. This post gives the basics. Read the whole thread and follow it. If you have any questions, just ask them (search first). The XDA community is the kindest that I know of on the internet, people want to help you.
Hope this question is in the right place.
After downloading ANY apk., after clicking on it, a window pops up that reads:
Install Blocked: For security your phone is set to block installation of applications not obtained from Android Market
Below that is "OK" as my only option.
I've visited and revisited the recent rooting threads and other similar sources and found that most if not all arrive at a different option that offers "Settings" that can be changed. Even when I go directly to Settings>Device Settings, I have NO options to alter and allow "Unknown Sources"
Device: 1st Nook - purchased Nov 2011/ firmware 1.2
2nd Nook - purchased approx April 2011/ firmware 1.3
Both units respond the same way. What are my options here. Thanks for any and all help.
W8ing4Pre3 said:
Hope this question is in the right place.
After downloading ANY apk., after clicking on it, a window pops up that reads:
Install Blocked: For security your phone is set to block installation of applications not obtained from Android Market
Below that is "OK" as my only option.
I've visited and revisited the recent rooting threads and other similar sources and found that most if not all arrive at a different option that offers "Settings" that can be changed. Even when I go directly to Settings>Device Settings, I have NO options to alter and allow "Unknown Sources"
Device: 1st Nook - purchased Nov 2011/ firmware 1.2
2nd Nook - purchased approx April 2011/ firmware 1.3
Both units respond the same way. What are my options here. Thanks for any and all help.
Click to expand...
Click to collapse
You need tgps_launcher. There are several posts about it.
http://forum.xda-developers.com/showthread.php?t=1349891
jreed012 said:
You need tgps_launcher. There are several posts about it.
http://forum.xda-developers.com/showthread.php?t=1349891
Click to expand...
Click to collapse
Thanks for your reply. However (unless Im misunderstanding something) I have tried the launchers recommended here and other sources. Each time I continue to hit the same dead end after I choose Package Installer........"Install Blocked"
Sorry if Ive misunderstood you. Im really tying to get this and trust those that have walked this path. Thanks
W8ing4Pre3 said:
Thanks for your reply. However (unless Im misunderstanding something) I have tried the launchers recommended here and other sources. Each time I continue to hit the same dead end after I choose Package Installer........"Install Blocked"
Sorry if Ive misunderstood you. Im really tying to get this and trust those that have walked this path. Thanks
Click to expand...
Click to collapse
You need to allow installation of non-market applications first. To get to that menu, you can use tgps launcher.
http://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1354487&v=1&libid=1322962789511&out=http%3A%2F%2Fli362-167.members.linode.com%2Fgapps%2Fnon_google%2Ftgps_launcher.apk&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D1397&title=Full%20root%20for%20Nook%20Tablet.%20%5B11%2F20%2F11%5D%20%5BYes%20this%20is%20a%20permanent%20root!%5D%20-%20xda-developers&txt=http%3A%2F%2Fli362-167.members.linode.com%2F...s_launcher.apk&jsonp=vglnk_jsonp_13229630191137
Use the nook browser to open the link above. It will give you the option to enable usb debugging (under development) as well as install non-market apps.
Further instructions can be found on the "How to Root" sticky.
THIS IS FOR 1.4.1, 1.4.2, and 1.4.3 ONLY - Please don't quote the first post.
As of October 31 2013, the Nook Color with Froyo is dead in the water, as far as the Google Play store is concerned. Google updated to Google Play Services 4.0, and with it killed off the API support for Android 2.2 Froyo. That means that almost all apps being produced or updated since then will not support Froyo. If you look up Angry Birds on the Play Store website, you will see that the minimum system requirements are Android 2.3 and up.
What it does:
Permanently Enable ADB via uRamdisk
Installs adbWireless
Installs su and Superuser.apk
Installs Busybox
Installs Softkeys
Installs Zeam Launcher
Installs B&N HomeLauncher
Installs HomeCatcher
Installs NookColor Tools (To Enable Non-Market Installs)
Installs Live Wallpapers
Installs Custom Boot Animation
Fix to Allow update to Adobe Flash and Air
App Auto Install (Open up manualnooter-5.xx.xx.zip from sdcard drop in /data/app)
System Files that get Modified:
uRamdisk - Enable permanent ADB Access
/system/build.prop - Fingerprint change
download.db - Fixes Market "Download Unsuccessful" issues
services.jar - Fixes apps2sd
Changes:
August 20, 2012 -
Updated Adobe Flash to version 11.1.111.10
Moved Adobe Air from the Data partition, to the System partition. This is to fix the "Read-To-Me" playback error.
Fixed the missing text in the "NookColor Tools" app
Introduced versions that disable B&N updates, by utilizing the SQLite method
Introduced incremental updates, so that you can flash only the changes that were made in the upgrade
manualnooter-5.08.20.incremental.zip - This will make the changes from manualnooter-5.02.19 to manualnooter-5.08.20. It doesn't block B&N updates.
manualnooter-5.08.20.incremental_block_updates.zip - This will make the changes from manualnooter-5.02-19 to manualnooter-5.08.20. It will Block B&N updates
February 19, 2012 - Fixed script that deleted the kernel image, and left you stuck at "Read Forever"
February 12, 2012 - Initial release
Before you begin:
You must do a complete wipe before installing this package.
If you want to update to 1.4.3 - Instructions HERE
You must already have a registered Nook Color
YOU MUST DOWNLOAD ALL YOUR B&N CONTENT BEFORE YOU CONTINUE, OR YOU RUN THE RISK OF LOSING ALL ACCESS TO B&N CONTENT
You must have a Google Account, for Gmail, Market, Etc. IF you used a Gmail account for B&N Registration use that one for this process.
You must have a bootable ClockWorkMod version 3.2.0.1 SD card: HERE - Use Win32DiskImager to flash this image to your SD card LINK
OR emmc CWM Recovery Installed
You must have enough intelligence to follow instructions.
If you don't have enough posts to post in the development section, please go post in the Q&A section, and post with "MN5" in the heading. I don't read every post on this board, so I can get to you a little easier if you follow these guidelines.
Let's get started:
If you're running a previous MN 5, you do not need to do a complete wipe.
Download one of the Following ManualNooter 5 files based on your needs:
manualnooter-5.08.20.basic.zip - It doesn't include apps2sd support, and doesn't block B&N updates. Doesn't replace any system files
manualnooter-5.08.20.basic.block_updates.zip - It doesn't include apps2sd support, but has B&N updates blocked. Doesn't replace any system files
manualnooter-5.08.20.apps2sd.zip - Includes apps2sd support, but doesn't block B&N updates. It will replace a system file, making it firmware version specific
manualnooter-5.08.20.apps2sd.block_updates.zip - Includes apps2sd support, and has B&N updates blocked. It will replace a system file, making it firmware version specific.
If you will be flashing with apps2sd support, you will also need to download one of the following kernel images to fully utilize apps2sd support.
Dalingrin OC kernel - Dalingrin 090111 OC kernel
OR Stock kernel - Stock. kernel with apps2sd support
Copy above file(s) onto your bootable CWM SD card using Windows Explorer, OS X Finder, etc.
DO NOT extract the zip file. It MUST be left as-is
DO NOT copy the zip file into a folder. Leave it at the top directory of your card.
Unplug your Nook Color from computer. (If plugged in)
Turn off your Nook Color. (If turned on)
Insert bootable CWM SD card with ManualNooter into your Nook Color.
Turn on your Nook Color
If using bootable CWM SD card this should boot you directly into recovery
If using emmc CWM Recovery instead of SD card CWM Recovery, boot to recovery.
When CWM boots select:
install zip from sdcard (Volume down 4 times, then n)
choose zip from sdcard (Volume down 1 time, then n)
manualnooter-5.xx.xx.zip (Hit volume up until you get to it, then n)
Confirm that you really want to run the update
Selecting this indicates that you take responsibility for your own actions.
Wait patiently and follow onscreen directions
If you flashed apps2sd file, now would be the time to flash the kernel for full support.
Remove bootable CWM card from Nook Color and select reboot
If you get "Install Failed" after rebooting out of CWM this can be normal. Just reboot again.
After reboot and unlocking your device select Zeam Launcher.
Open up Market and Accept Terms and Service/Sign In.
Exit out of the market, wait a couple minutes for Gapps to sync everything up, and market to update
When the market icon has changes, open it again to accept terms of conditions again for the updated market.
You may not have to Accept Terms and Service or Sign In if you're updating from a previous MN version.
If you made it this far your nook should be successfully Rooted.
Enable Non-Market Installs by running the Nook Color Tools App.
Uncheck the top box, then recheck the box again
(OPTIONAL) To restore the SD card to a "usable" state
Insert bootable CWM card into Nook Color
Go to Settings > Device Info > SD card > UnMount > Format
This will wipe your SD card of all MN/CWM bootable abilities. If you use this you will have to reflash the SD card for future MN releases if you don't flash CWM to your emmc.
If you are upgrading from manualnooter-5.01.21, or earlier:
You need to perform the market limited visibility steps found below
If the market dies on you after performing those steps:
Go into manage applications
Select Market
Uninstall updates
Open market and accept user agreement
Exit market to let it update itself
Open market and accept user agreement
How-To Video
Known issues without solutions:
Network Location isn't enabled -
Signature Issue -
News and Weather app/widget -
Reliant on network location -
Known issues and solutions:
Google Search widget crashes - This is an issue with the NC network location
Start the Google Search app
Press the "Menu" button
Select "Search settings"
Uncheck the box next to "Use My Location"
Read-To-Me playback problem -
If you have upgraded to manualnooter-5.08.20
Open Manage Applications
Select "All"
Locate and select "Adobe AIR"
Select "Uninstall Updates" from the upper right corner
Exit back to the launcher, and select the "Play Store"
Search for "Adobe AIR"
Uncheck the "Allow automatic updating" box
If you have not upgraded to manualnooter-5.08.20
Flash one of the incremental update files with CWM to update to manualnooter-5.08.20
Open the "Play Store"
Search for "Adobe AIR"
Uncheck the "Allow automatic updating" box
ROM Manager file selection -
After selecting "Install ROM from SD Card" you can't select a file to flash
Open "Manage Application"
Select "All"
Locate "ROM Manager"
Select "Uninstall Updates" from the upper right corner
Exit back to your launcher, and select "Play Store"
Search for "ROM Manager"
Uncheck the "Allow automatic updating"
YouTube won't play HD files
Older versions of YouTube allowed you to select "HQ" High Quality playback
Open "Manage Application"
Select "All"
Locate "YouTube"
Select "Uninstall Updates" from the upper right corner
Exit back to your launcher, and select "Play Store"
Search for "YouTube"
Uncheck the "Allow automatic updating"
IMEI Force Close -
There is no randomly generated IMEI in this version - This can be fixed by using the IMEI Generator HERE
Calendar sync -
Calendar does not sync properly with multiple calenders linked to your google account. Simply use one of the many free alternative calendar apps.
Market has limited visibility - This is a known tablet issue, not just a Nook Color one.
Start Nook Color Tools
Select the "All Settings" button
Unplug your Nook Color from computer. (If Plugged in.)
Choose "Manage Applications" from the list
Select the "All" tab
Scroll down to "Market" and select it
Tap "Force stop"
Tap "Clear cache"
Tap the back button if you have SoftKeys running, else swipe right to left on the status bar at the bottom of the screen (from the clock to the book icon)
Scroll up to "Google Services Framework" and select it
Tap "Clear data"
Tap "OK"
Tap "Force stop"
Press the n button to return to your launcher
Start Market
At the "An error has occurred" message, tap "OK"
Hold your power button to turn off your Nook Color from the menu
Turn your Nook Color back on and give it a moment to find your WiFi connection
Start Market again, and the problem is resolved
Complete Wipe:
Flash back to clean stock rom
This will not work if you're using emmc ClockWorkMod Recovery
You must do both parts to completely wipe clean your Nook Color
Thanks To:
thespotlite from Android Creative Syndicate - How-To Video
bpk - SoftKeys
MrSiir - adbWireless
Gojimi - HomeCatcher
Suteru - Boot Animation
Ben74 - NookColor Tools
HamNCheese - B&N HomeLauncher
Michael Bentz - Zeam Launcher
pokey9000 - Original Nooter that started the AutoNooter and ManualNooter projects.
GabrialDestruir - Borrowed install instructions
Dalingrin - OC kernel
Please Note: If I'm using your app within ManualNooter or AutoNooter and you'd like it removed please send me a PM stating so and I will do so for future versions.
Frequently Asked Questions:
Can i update Adobe Flash and Air -
Yes, the Adobe boot loop fix is applied with MN 5
Does this block OTA updates -
Starting with ManualNooter-5.08.20 you now have the option to flash a package that will block B&N updates by using the SQLite method
update_disable.zip - You can also download, and flash this using CWM at any time to block B&N updates.
update_enable.zip - If you need to unblock B&N updates at any time, you can flash this file using CWM to restore the update function.
Can I change the stock keyboard -
Yes, some of the best known keyboard apps have all been tested to work. Just follow these directions to install the keyboard.
If you don't have the paid app "Root Explorer," you can download the free app "ES File Explorer." Once you open "ES File Explorer," you will need to go into settings to set root access, mount file system, and change the home directory to "/"
Download/Install the keyboard that you want to use from the market or Amazon Appstore
Open your explorer app, and navigate to /data/app
Locate the apk file for the keyboard that you just installed
Examples: com.touchtype.swiftkey-1.apk or com.swype.android.inputmethod-1.apk
Long press on the apk file, and select "Move" or "Cut"
Navigate to /system/app
If using Root Explorer, select "Mount R/W"
Now select paste to move the apk file into the /system/app folder
Exit your explorer app, and reboot the device
After the device reboots, open the app "NookColor Tools"
Select "Choose Keyboard" and select the keyboard that you just installed
If installing Swiftkey or Swype, you can now open the app to finish the install process
I did this mod from a request in another thread, LINK. It is a port of “revcompgeek’s” work under the Nook tablet section, HERE. The mod removes the QuickNav bar when you presss the n button, making it like a standard home button, and makes the back and menu buttons permanent.
I did not include it in the MN package because I am not sure how many people would want it, and it has not been tested long enough. Just simply flash the Statusbar_mod.zip file with CWM, it will take about 5 minutes to boot back up after flashing since it is a framework file. You will need to use the app “AnyCut” or “BetterCut” to create a link to the “Shop” and “Library.” If you don’t like it, simply flash the Statusbar_stock.zip file to return to stock. If you flash a new version of MN 5 after applying the Statusbar_mod.zip, you will need to reapply the Statusbar_mod.zip file again to regain it.
*UPDATE*
I noticed that "AnyCut" is currently missing from the market, and since the app was free in the market, I have attached it below.
Great!
Are there any of the limitations I've read about (read-to-me, free in-store reading) with regards to rooting 1.4.1, or are those now worked around?
MassiveAttack said:
Great!
Are there any of the limitations I've read about (read-to-me, free in-store reading) with regards to rooting 1.4.1, or are those now worked around?
Click to expand...
Click to collapse
Around 4,000 people have kindly tested different versions over the last two months, and everything should be working properly. The key step to follow in the directions, is step 4 under “Before you begin,” You must download all your B&N content before you continue, or you run the risk of losing all access to B&N content.
I don’t remember there ever being an issue with read-to-me, I remember there being touchscreen issues with kids books in the early versions of MN 4. A handful of people did test the in-store reading function, and reported that it worked fine.
Absolutly amazing! Thank you!
Dalingrin 090111 OC kernel with manualnooter-5.02.12.zip
I don't need apps2sd. Can I use manualnooter-5.02.12.zip and then install Dalingrin 090111 OC kernel?
fpga_guy said:
I don't need apps2sd. Can I use manualnooter-5.02.12.zip and then install Dalingrin 090111 OC kernel?
Click to expand...
Click to collapse
That should work fine, it's what I had before the apps2sd release.
MassiveAttack said:
[...] Are there any of the limitations I've read about (read-to-me, free in-store reading) with regards to rooting 1.4.1, or are those now worked around?
Click to expand...
Click to collapse
I haven't tried read-to-me, but free in-store reading works fine.
MassiveAttack said:
Great!
Are there any of the limitations I've read about (read-to-me, free in-store reading) with regards to rooting 1.4.1, or are those now worked around?
Click to expand...
Click to collapse
I tested read to me this morning using Tales of Peter Rabbit. It worked just fine.
success!
This is how I got 1.4.1 going from BN1.3 with MN:
I am running BN1.3 with MN4.6.16. I have CWM 3.0.2.8 on a bootable sd and have made a backup.
Instead of restoring to stock and then upgrading to 1.4.1, I I used the 1.4.1 image from
http://forum.xda-developers.com/showpost.php?p=21203895&postcount=129 and then apply MN5.02.12
Before install 1.4.1, I wipe/data and /cache then install 1.4.1.
Did another wipe/data.
Since I have an old NC with the 5gb partition, I can continue to use CWM 3.0.2.8.
After rooting BN1.4.1, if I am unhappy, I can just restore my old BN1.3 backup.
GMPOWER said:
Around 4,000 people have kindly tested different versions over the last two months, and everything should be working properly. The key step to follow in the directions, is step 4 under “Before you begin,” You must download all your B&N content before you continue, or you run the risk of losing all access to B&N content.
I don’t remember there ever being an issue with read-to-me, I remember there being touchscreen issues with kids books in the early versions of MN 4. A handful of people did test the in-store reading function, and reported that it worked fine.
Click to expand...
Click to collapse
I had been following the thread about the 1.3 firmware, and I saw the pre-releases for the 1.4.1 firmware had some issues. I'm thrilled this will work--maybe my wife will let me "borrow" her nook now
fpga_guy said:
So let see if I have this correct:
I am running BN1.3 with MN4.6.16. I have CWM 3.0.2.8 on a bootable sd and have made a backup.
Instead of restoring to stock and then upgrading to 1.4.1, I want to use the 1.4.1 image from
http://forum.xda-developers.com/showpost.php?p=21203895&postcount=129 and then apply MN5.02.12
Since I have an old NC with the 16gb partition, I assume that I can continue to use CWM 3.0.2.8.
After rooting BN1.4.1, if I am unhappy, I can just restore my old BN1.3 backup. Do I have everything correct?
Click to expand...
Click to collapse
Probably want to get the multiupload mirror in this post instead... rapidshare has gone horrible as of late... IMHO of course.
Works like a charm!! Thanks very much! Question for you guys: In your opinion what is the best way to block OTA updates?
iraqmilner said:
Works like a charm!! Thanks very much! Question for you guys: In your opinion what is the best way to block OTA updates?
Click to expand...
Click to collapse
I'm not a guy, but here's what I used. I should add, I used it to stay on 1.3. It tells whoever is looking that you're on 1.4.1. I guess it'll have to be updated if B & N comes out with another update.
Market Not Loading
Everything went perfectly with the MN'ing, but when I try to go to Market, Gmail, Talk, etc, the NC tries to open Market or Google service but then immediately closes. Many attempts yield same results. Any ideas are welcomed.
iraqmilner said:
Works like a charm!! Thanks very much! Question for you guys: In your opinion what is the best way to block OTA updates?
Click to expand...
Click to collapse
To block OTA updates, I used SQLite Editor with the instructions below from "Mark"
I can't find this post anywhere and have no idea where I got it, if you are Mark..THANK YOU! and post a link to the original so we can find you! <G>
Worked perfectly for me. I've attached the text file so you can save it instead of trying to read the forum, it takes a bit but not as much time as you'd think.
The $3 is well worth it!
:::This is a one-time thing, and doesn't require revising it as new updates come out, as some other methods do (e.g., pushing modified build.props files down). Those are completely free, but a fair bit more complicated, and have to be redone every time a new update is released by B&N.
1) Go to Extras, open the Android Market, tap on the magnifying glass, and search for SQLite Editor. It will cost you <$3.
You don't need the companion product, Root Explorer, at all, that others have mentioned, so you can save some $$$ if you want (4 bucks, I think). It's actually quicker not to even use Root Explorer.
2) Buy and install SQLite. If you're running auto-nootered, you'll need to shut your Nook off and restart it afterwards. That's because the Extras screen info is cached, and not updated dynamically, so you'll never see any newly loaded Apps until you reboot.
3) After powering back up, go to Extras and click on SQLite. It will scan your entire Nook and find every SQL database file there. Even the hidden ones. It only takes ~10 seconds.
4) Scroll down to DeviceManagerService, and tap on it. Then tap on devicemanager.db.
5) Tap on the "registry" entry. It's easier now if you rotate to landscape, so you can see more of the fields in each entry.
6) All the entries in this table start with "com.bn.device....". Look for the one that's labeled '...fota.mode" at the end.
7) In the far right Value column, you'll see "Auto". Tap on that to select it. Then go down to the Status Bar at the bottom, and tap the Menu button (3 horizontal lines), and pick Edit Field.
8) You'll then see a black screen with one entry, the field editing form. You should see the field name of "value" there, and its contents will be "auto". If it turned out that your selection picked some other field (they are pretty small!), don't panic! :smileywink: Just go back and retry until you get the right one.
9) Tap on "auto" and the keyboard will come up. Backspace to delete the current contents, and enter "manual" in its place. Then tap Done. Then tap Save. Until you tap Save, you've changed nothing, so poking about is fairly safe. You may see a message about granting super-user permissions, which is normal.
10) You can now exit out of SQLite if you like (it's not necessary), but you're not quite done yet, so don't enable WiFi immediately. To make sure that the system is using the settings you just modified, you need to force it to reload and "see" them. So just power you Nook off and back on. After it reboots, it will use your new settings from then on. That's it.
Walla! You're all set. Auto-updates will no longer be pushed down to your Nook. However, updates you manually sideload wll still work. If you decide at some point you'd like auto-updating to work again, just go back in and re-enable it by changing "manual" to "auto".
~~
While the length and detail of the instructions above may make this look like it's more complicated than it really is, I'd rather err of the side of accuracy than leave something "obvious" out. It really doesn't take more than 2 minutes to do, and most could probably figure it out on their own, if they really needed to. The one thing they might overlook is the need to reboot afterwards, which isn't necessarily obvious.
- Mark
free sql editor
There is an open source free sql editor. The link is posted in
http://forum.xda-developers.com/showpost.php?p=11038175&postcount=23
Very easy to use.
iraqmilner said:
Works like a charm!! Thanks very much! Question for you guys: In your opinion what is the best way to block OTA updates?
Click to expand...
Click to collapse
I flashed CWM to internal memory once I had everything to my liking.
From past experience this will block the OTA update.
It is a minor issue to flash back to stock in order to upgrade the next time B&N does an update.
This may not be the right way, but it is easy, a lot easier than other methods IMHO.
i upgraded to 1.4.1 but after i run manualnooter 5.02.12 i am just stuck at read forever screen on reboot.
Watching ABC.com show problems
Running BN1.4.1 with MN5 latest. The show NCIS comes through fine. But the ABC shows (eg Castle) causes the browser Dolphin HD to FC.
Any idea what is causing it?
I have rooted with no problem, but now I have 3 questions.
1) I can't get any .apk files to load. I get an error saying "This NOOK cannot read this file..."
2) in NT Settings, I can't get the unknown sources box to stay checked
3) Is there any way to put the android market apps on the home screen?
Thanks for any help!
I believe sideloading apks was blocked in 1.4.1.
Sent from my Xoom using Tapatalk
That sucks! What about putting android market apps on the main screen of the NT?
There is a Nook Color app in the Android Market that does exactly that.
dcfootqb said:
I have rooted with no problem, but now I have 3 questions.
1) I can't get any .apk files to load. I get an error saying "This NOOK cannot read this file..."
2) in NT Settings, I can't get the unknown sources box to stay checked
3) Is there any way to put the android market apps on the home screen?
Thanks for any help!
Click to expand...
Click to collapse
Most of this stuff is explained elsewhere in the forums . . . I know everybody says that, but believe me, it's true!
To get you started - - you can sideload apps on any rooted Nook:
(1) Get the NT Hidden Settings app (which you have)
(2) Goto "Hacks" - - tap "Unknown Sources Hack" Hit "Back"
(3) Goto "Application Settings" - - toggle "unknown sources"
(4) reboot the Nook
(5) Check in "NT Hidden Settings" . . "Applications Settings" . . to see if "Unknown Sources" is still checked. If not, repeat the steps above.
It's not unusual for people to have to do this 2 or 3 times to get the hack to "stick". Some people swear by toggling each setting on and off a couple times before rebooting. I know it's a PIA, but as far as I know everybody eventually get's it to 'stick' after a number of repeats.
Good news is, once you get Unknown Sources to stick, you won't have to mess with it again unless your restore to stock & re-root.
The "Nook Color Applications" app works well on the Nook Tablet, as noted above. You might also want to look at Go Launcher or ADW Launcher - they give you a new desktop with multiple home screens and other features, but still let you use the stock book reader, Netflix, etc. While some people here are using CM7 or CM9, a lot of people have really tricked-out the stock NT ROM with a 3rd-party launcher. I run mine like that, and I've actually liked it better than CM7.
But I'll switch to CM9 immediately once it's a bit more stable. ;-)
Best of luck!
awesome! I will try tonight. Right now, my two year old wont let me play with "his" nook. lol
Thanks, this forum is the best!
Hey there,
I've been having a similar problem. I recently rooted (using http://forum.xda-developers.com/showthread.php?t=1529553 method), and have been able to access the market and download apps that way, but I'm unable to sideload them. When I try to open any app it says "Unable to install. This application was not able to install onto your device. Please "Archive" and then "Unarchive" the application to try again." I have an SD card inserted, and this error comes up with the Amazon market, and the HomeCatcher app. My unknown sources box is checked though! Any help would be greatly appreciated!
-DRA
i rooted with http://forum.xda-developers.com/showthread.php?t=1439630
but having hard time installing the CM 7 veronica did one stop CM7 ...
mezozon said:
i rooted with http://forum.xda-developers.com/showthread.php?t=1439630
but having hard time installing the CM 7 veronica did one stop CM7 ...
Click to expand...
Click to collapse
I believe veronica is currently recommending the "new" beta ( internal only for now ) made by CelticWebSolutions.
http://forum.xda-developers.com/showpost.php?p=22199348&postcount=1
timpilcher said:
Most of this stuff is explained elsewhere in the forums . . . I know everybody says that, but believe me, it's true!
To get you started - - you can sideload apps on any rooted Nook:
(1) Get the NT Hidden Settings app (which you have)
(2) Goto "Hacks" - - tap "Unknown Sources Hack" Hit "Back"
(3) Goto "Application Settings" - - toggle "unknown sources"
(4) reboot the Nook
(5) Check in "NT Hidden Settings" . . "Applications Settings" . . to see if "Unknown Sources" is still checked. If not, repeat the steps above.
It's not unusual for people to have to do this 2 or 3 times to get the hack to "stick". Some people swear by toggling each setting on and off a couple times before rebooting. I know it's a PIA, but as far as I know everybody eventually get's it to 'stick' after a number of repeats.
Good news is, once you get Unknown Sources to stick, you won't have to mess with it again unless your restore to stock & re-root.
The "Nook Color Applications" app works well on the Nook Tablet, as noted above. You might also want to look at Go Launcher or ADW Launcher - they give you a new desktop with multiple home screens and other features, but still let you use the stock book reader, Netflix, etc. While some people here are using CM7 or CM9, a lot of people have really tricked-out the stock NT ROM with a 3rd-party launcher. I run mine like that, and I've actually liked it better than CM7.
But I'll switch to CM9 immediately once it's a bit more stable.
Best of luck!
Click to expand...
Click to collapse
When a rebooted like 5 times it still the same thing unchecked.
To make sure How Do Your reboot?
miguelnook said:
When a rebooted like 5 times it still the same thing unchecked.
To make sure How Do Your reboot?
Click to expand...
Click to collapse
If you want to have Google play installed the easiest process to do now is to make a boot able cm SD card. CM10+ is the most recent so I recommend using it. There are also SDC versions of cm7 and 9. These don't affect your internal storage at all so the level of caution for bricking is low.
If you want to look into these SDC ROMs head over to the iamafanof site. There are links to the ROms and further instructions on how to create the cards.
I'm posting this here in the hopes that someone has come across this issue. I'm trying to compile some of the fully-native Android SDK examples (native-activity, native-plasma) and then install them on my Tegra 2 device running CM7. Well, everything goes fine until I try to install the APK. It installs, but always crashes upon launch. Now, let me explain that I am fairly certain that there's nothing wrong with the APK. It installs and runs fine under both the emulator and other real devices (e.g. I have a Nook Color running CM9 that does not have this problem).
Specifically, the .so included in the APK at lib/armeabi/libnative-activity.so does not get copied to /data/data/com.example.native_activity/lib. So obviously, because the file is not copied, the app can't find its .so and won't run.
The interesting thing is that if I long-press the app after it's installed, I can "Move to SD card" and it works! And after doing this, if I move it back to the phone, it works as well. Is this a problem with CM7? I can also choose in Cyanogenmod Settings to always install apps to "external storage," but I can't be guaranteed that every user running CM7 will have this option selected.
Any help is appreciated!
Updated and revised, 11-29-20
In this post I am presenting a way to slightly extend the practical range of the 8 gb Nook Tablet by using microG for Google Services Framework spoofing rather than the resource-hogging GApps. Although I have tested these ROMs thoroughly on the BNTV250a, they would all likely run just fine with GApps on the 16 gb model (I currently run AOSP 7.0 with microG on my 16 gb tablet), while only CM 11 runs acceptably on the 8 gb model with GApps. Let's get that simple setup out of the way first.
I selected the unofficial CM 11 ROM with the final security patches by Chris Hoffmann [https://www.mediafire.com/?gq1y21uz11lr1c0]. It is serviceable for me. The main drawback is the old WebView (which cannot be updated) resulting in the inability of browsers to display many sites properly, including the current default skin for XDA. Despite this, I've come to feel that it's perhaps the best option, with or without GApps. Installing this ROM is easy. Flash with the recovery listed in post #2, reboot, then flash a pico GApps package from Open GApps. To run the ROM without GApps, read on.
I made a quick tour of CM 12.1, CM 13, AOSP 6.0 and AOSP 7.0, and Lineage 14.1. In the following post I'll lay out some pros, cons and hints based on my experiences. I flashed each ROM several times, trying different things, building the system from scratch each time rather than restoring apps from backup. That gave me a chance to work with each OS and see how it would perform not only during setup, but also during a shakedown/tweaking phase. What I can say about all of these ROMs is that GApps effectively kills each and every one on the BNTV250a.
Life without GApps
I, of course, tried side-loading apps without GApps. Easy, right? I thought so until I came to a few that whined about requiring Google Play Services to run. Even mundane things like the NPR News app, my local newspaper and MX Player are "GSF dependent" (Google Services Framework). Then I tried another app that would not install at all. Turns out it did a license verification check (it's free!) and saw no Google anything, so forget it. This was sort of news to me I suppose because even my lowly NST had GApps installed once upon a time, so I never encountered this issue before. You can hunt around for apps elsewhere but if you pick up an app that happens to be featured in the PlayStore, you may be out of luck no matter where you got it from. Or maybe not.
There is a project called microG by XDA member @MaR-V-iN. It consists of a lightweight set of apps (two at minimum, a third if you want location services) which provide the needed authentication to Google servers and/or inquisitive apps. There is a catch: the ROM must support "signature spoofing".
These ROMs do not have that option. You can Google "signature spoofing" to read the pros and cons. This is just information. Caveat emptor, etc. There is an Xposed module called FakeGapps which enables signature spoofing. I tried this on a few ROMs and found it worked fine. At the time I started this there was no official Xposed update for Android 7.0 and as that was one of my targets, I started looking for something else [note: Xposed has since been updated to include Android 7.0 and beyond]. That led me to Tingle by XDA member @ale5000. This is a Python/ADB based method of automatically patching framework.jar to enable signature spoofing. This seemed to me a more direct and elegant approach. Although I was intimidated by it at first, I eventually just dove in. The only thing I didn't already have was Python and that was easy enough to install. The process is basically automatic once it gets going. Unfortunately it does not work for ROMs that are odexed or deodexed. The AOSP 7.0 ROM turned out to fall in that category. Xposed must be used there.
OK, what can all this do for you? It can get you a spoof of Google Services Framework without GApps. Period. There are a few simple additions to allow for location services. It used to be that you could also enable Calendar and Contacts syncing. No more. As for PlayStore access, this is possible running microG with CM 11, but not beyond. It's just too resource intensive. For ROMs beyond CM 11 I found the Aurora Store (F-Droid) to work OK, although not always in the same way. On some ROMs you can use the anonymous Aurora Store login, on others you need to supply a Google account (email). Trial and error.
The General Process
If you have never "flashed" anything before that you can talk about at work, then you need some basic instructions for creating an SD card that will allow you to try out these procedures. The excellent instructions by @digixmax here will get you started with the SD card. You need to follow steps 1-2 to prepare the card, although the version of TWRP you use will depend on the ROM you want to try out (see second post for links). Also, the ROM itself will vary (see second post for links) and you will not want GApps (unless you are just installing CM 11 with GApps). The remainder of the steps (3-10, skipping 9) also describe the general process of flashing a ROM (or other "flashable" files like Xposed, etc.) using the SD card.
1. Flash the ROM using an appropriate recovery (I have listed the ones I used in the following post)
2. First boot, enable root, USB debugging and ADB
EITHER
3. Connect tablet to PC via USB and access via ADB ("adb devices"--some of these ROMs require that you approve PC access to the tablet via ADB, so check the tablet screen to approve that option if needed)
4. Open a command window on the PC and navigate to your Python installation directory. Because I was not sure what I was doing I just dumped the entire contents of Tingle into the Python directory. That simplified path issues for me. Type "python main.py" and select option 1. Wait for the "all done", hit CTRL-c and kill ADB server. Disconnect tablet from USB and reboot.
OR
3. Flash appropriate Xposed for the OS; reboot
4. Install Xposed installer app and FakeGApps.apk; use Xposed installer app to enable FakeGapps (signature spoofing); reboot
5. Install root file manager of choice if desired (the CM stock file managers are totally capable of the following operations if given root access; the stock file explorers of the AOSP and Lineage ROMs may allow the same, although I have had mixed results. You can always install a root file manager via ADB before continuing if all else fails) A copy of ES File Explorer is attached below.
for CM 11 without GApps but with the PlayStore:
6. Move Phonesky.apk--i.e. the PlayStore-- (old, lightweight version from a KitKat ROM: http://www.mediafire.com/file/1c2f0n3k3cwsln7/Phonesky.apk/file) into /system/priv-app; set apk file permissions to rwx-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given; set to enable Google device registration; add an account. This process can be slow. Be patient. If you end up at a black screen, reboot and try again or see if the account is already established.
10. Open the PlayStore. Do some searching. You want to give it time to auto-update (this process may be completely silent). Exit. Check Settings>Apps>Downloaded to see if PlayStore has shown up there. If it has, then it may be updated. You can check yourself to see if the version number is higher. If there is no update, access the PlayStore again and check again. Once you have an update, you're good to go.
OR, for ROMs beyond CM 11:
6. Use root file manager to create the folder "Phonesky" in /system/priv-app. Set folder permissions to rwx-rx-rx. Use root file manager to move "FakeStore" apk into /system/priv-app/Phonesky and set apk file permissions to rw-r-r.
7. Move microG component apks into /system/priv-app; set apk file permissions to rw-r-r (you need a minimum of Services Core, Services Framework Proxy for this step)
8. Reboot
9. Check microG Settings to be sure spoofing is enabled and other permissions are given.
It's a lot, but if I could do it many times over you could do it once
In the end you'll have a tablet spoofing Google Services Framework so most apps will run without whining, but without the crushing weight of the PlayStore or the full GApps.
Contacts and Location
Life without GApps doesn't mean you have to give up these services. Just keep in mind that running background services can compromise a system that is already on the edge.
I tested the instructions that follow on a BNTV250a, using the stock Contacts and Calendar apps.
1. Contacts
There are some places in "on-line land" that describe a method for enabling contacts sync. I have not found the various methods to work any longer. It is possible to sync Contacts using DavDroid. There is only one version that will run on CM 11 and the same app will run on the other ROMs as well (attached below). However, you are adding more overhead to a device that is already pushing the limits. In the end I opted to export my contacts in vcard format and read them in as a local file. The more socially active may find this unacceptable, but it works for me.
2. Location
To enable location you will need to install an app which coordinates WiFi triangulation (something usually handled by GApps). There are two possibilities. You can get a Unified NLP apk from the microG download page. After installing the app you can check your microG settings to see if everything is OK. Then you can check Settings>Location and set it up the way you want.
If you want to use Maps you will also need to flash a maps.zip file from microG. This contains a couple of library files for Maps. As far as the Maps app itself, I have never had good performance from any version of Google Maps on my devices--until now. That's because I went fishing for an older, less bloated version that would run on the BNTV250a. It works beautifully on all my devices from KitKat to Nougat and allows pre-cache of map areas which don't expire. I've attached a copy of the apk file below.
Email
The stock Email client works great (at least for GMail accounts) and looks a lot like GMail (no surprise there). If you have your heart set on GMail, version 4.5.2--from GApps for Jellybean--seems to run just fine with a footprint of about 11 MB. I've attached a copy below.
The ROMs
Updated and revised 2-5-23
Generally I disabled any stock stuff I could that I would not use. Anything past CM 11 has a maddening issue I call "peek-a-boo keyboard", most noticeable when using the browsers. The keyboard drops out while you are typing or simply refuses to open without a struggle. You can solve this problem in CM 12 and minimize it in CM 13 by installing Simple Keyboard.
CM 11 is beginning to show expired certificates and SSL issues. You can try replacing or adding new certificates, but it's not easy and you're left with warning artifacts in the status bar. Ditto with CM 12 and CM 13, but they are not nearly as bad--for now. The stock browsers, fortunately, allow you to "ignore" security warnings which makes browsing more pleasant. You may not feel that's a great idea, but the reality is that browsing is the Achilles Heel for all these ROMS, and it's worse the higher you go. The stock browsers may give the best overall performance, whatever their shortcomings.
Because of the SSL issues, I don't recommend CM 11 any longer unless you are not going to do much in the way of internet stuff.
Note: I have noticed that both my Nook Tablets (8 and 16 GB) run better if they've been on for a bit. If yours is cranky when it gets up in the morning, pouring coffee on it won't help, but a little siesta after boot may be just the thing
CM 11 (but with issues as described above)
https://www.mediafire.com/?gq1y21uz11lr1c0
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
This is arguably the best choice for the BNTV250a if you want something other than the stock B&N ROM. It runs smoothly enough that you could even keep the PlayStore app on it and it would still behave reasonably. It's even better without it. The only drawback with this ROM is that Android Webview cannot be updated. This means that some websites will not display properly or may simply crash, regardless of what browser you choose to use. I found the antique stock browser to be surprisingly good, but Via also works well. Also, the SSL is in need of updating, so you will run into issues with some websites and apps like OverDrive.
The lesson that this ROM taught me is that these tablets are for casual use. You can't just load them up with apps and expect them to run well. Think about what you really would like to use the tablet for. Consider older versions of apps that will probably still have more features than you will ever want but are less taxing to the system. You can see from the attached screenshot how I eventually pared my choices down. I should probably pare it down even more. Most of the apps are older versions and I've kept the total count low, certainly less than on my 16 GB tablet and other devices. You don't want to exceed about half of the internal storage capacity.
CM 12.1 (potential WiFi issue as described below)
http://www.mediafire.com/file/7zxc2e...K6-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Edit 9-30-22: I recently booted this up to find that it would no longer connect to my fairly new ATT router. Puzzled, I took the tablet to my local library and had no difficulty connecting there (open network, though). Next I started restoring backups of each of the other ROMs in this list and each one had no trouble with WiFi at home. I installed a fresh copy of the CM 12.1 ROM. It also refused to connect to the router. I scrounged around the web and found two more versions of CM 12.1. Neither would connect to my router. So...I'm not sure if there is some additional security ATT has built into their WPA2 authentication or what, but I mention this just to alert you that this might be a problem. I was even able to connect to a mobile hotspot generated by my Windows 10 machine (password needed). Why this new(?) problem for the 12.1 ROM only, I have no idea.
Before you start installing apps the behavior is sprightly, even on the BNTV250a. As the internal space decreases and RAM use increases, it becomes a little less so. Even so, when running well I think it comes close to CM 11 (with GApps), albeit with more lag.
The stock browser seems like the best bet (I tried many), though it can be slow.
For me this ROM has two major issues. When it is unhappy, it will simply shut down the tablet, literally turning it off. This used to sometimes happen when I ran it on my 16 GB model, so it's not the fault of the BNTV250a. The other issue is problems for apps writing to the external SD card. For a tablet with precious little internal space, you just don't want apps downloading into internal space or storing lots of data there. There is an edit to the file /system/etc/permissions/platform.xml which corrects this issue for some apps. Find the section of platform.xml below and add the last line:
Code:
<permission name=”android.permission.WRITE_EXTERNAL_STORAGE” >
<group gid=”sdcard_r” />
<group gid=”sdcard_rw” />
<group gid=”media_rw” />
This change enabled OverDrive and Kodi, for example, to download files to the external SD card. It might work for others.
Not as fluid as CM 11, but WebView issues are gone and you can access most up-to-date content (if slowly).
CM 13
https://archive.org/download/cmarchive_snapshots/cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-acclaim.zip
Flashed with SD-based TWRP 2.8.6.0, enabled signature spoofing with Tingle
Never having tried this ROM on my 16 GB tablet, I was actually pleasantly surprised by its behavior on the BNTV250a. There's a funny WiFi thing where if you leave WiFi on when you shut down and then boot up again, it will not automatically connect (unless the lockscreen has come on, which is pretty fast after booting, so no biggie). Otherwise it's pretty much like CM 12 although maybe a little more stable--if you don't overdo it. The Sound Recorder app is somehow broken on the CM 13 ROM. If this is something you'd like, you can replace the broken version in /system/app/SoundRecorder with the one attached below. Make sure the permissions are rw-r-r and reboot.
Some apps can't write to the SD card (as portable storage). Kodi is an example, I'm sorry to say. I've tried many "solutions" to this problem but the only one that worked for me is to edit /data/system/packages.xml, adding the permission for each specific app you want. This is a long file and I did this using the editor from the CM File Manager. There are probably easier ways. After locating the app you want in the xml file, add this line anywhere between the <perms> and </perms> tags:
Code:
<item name="android.permission.WRITE_MEDIA_STORAGE" granted="true" flags="0" />
This change will be overwritten if the app updates, so you might want to keep that in mind.
This is the ROM I've settled on for my BNTV250a (screenshot of home screen below)
AOSP 6.01 "Marshmallow"
Box
notredame.app.box.com
(you want aosp_acclaim-ota-MOB30Z.160820.zip)
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is one of the ROMs built by @amaces. The AOSP builds are very lean compared to CM ROMs so I was hoping this might perform somewhat better than CM 13. But I don't think it does.
The first big hurdle is enabling root. My thanks to @digixmax for pointing out the right tool. After first boot (or maybe even before, but I did it after) you need to flash UPDATE-SuperSU-v2.46.zip. Works perfectly.
The stock launcher is, well, funky. I replaced it with Nova Launcher but after installing a few other apps it was clear the system was under great stress. Lots of black screens and crashes. Not a good option for the BNTV250a.
AOSP 7.0
https://www.mediafire.com/?5vcw8l603d3r5sc
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Xposed
This is another ROM by @amaces and what I run on my 16 GB tablet. On that device it is virtually flawless. I really wanted to say the same for the BNTV250a, but I can't.
Enabling root for the ROM is achieved with Magisk.
The ROM appears to be odexed to Tingle and so you must flash the correct Xposed (for 7.0 and Magisk) and install the installer app along with the FakeGapps app as described in the previous post.
The stock launcher is pitiful and you need to install a root file manager to get anything done. The system is laggy and video is not smooth. Not even a potential option for the BNTV250a.
Lineage 14.1
Box
notredame.app.box.com
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Edit 2-5-23: Well...no, it does not have the classic shut-down bug (tablet reboots right after it "shuts down"). Instead, it often shuts down just fine, but occasionally locks up during shut down and has to be forced off with the power button.
Flashed with emmc-based TWRP 3.0.2-0, enabled signature spoofing with Tingle
This is a third ROM built by @amaces (his most recent for the NT). I didn't have much hope for this because if 7.0 was an issue, I didn't expect 7.1 to perform well.
The only native root capability is for ADB. To enable full root, you need to flash addonsu-14.1-arm.zip (attached below). I did that after first boot but perhaps it can be done along with the ROM.
Not surprisingly the ROM has the feel of CM. There appears to be a file manager but it is only a partial reflection of the native file explorer and is useless for the manipulations that need to be done, so you need to adb install a root file manager as described in the previous post.
The stock browser is complete rubbish. It looks to be Gello(?) but it is the most infuriating collection of electrons I have ever encountered. There are no navigational buttons, no bookmark button--no buttons at all! I really tried. I used gestures (some rude), I tried magic words (many of which do not appear in children's books). Nada. When I finally managed to reach my test site it was like wading through, well, Jello! So....attached below is the nice lightweight stock browser from AOSP 7.0. Navigate to /system/app/Browser and there you will find Browser2.apk. Rename it to something else and copy in the Browser2.apk attached below, setting file permissions to rwx-r-r. Reboot. If you are successful, you can delete the old, useless browser apk. To enable bookmarks, navigate to /system/app/BookmarkProvider and inside you will find the apk file. Tap to install. I don't know why this needs to be done, but it does even on AOSP 7.0. Reboot and you've got a functioning browser (rife with "peek-a-boo keyboard")
The ROM hates Kodi, crashing constantly. Video from other apps is not smooth. Not a viable choice for the BNTV250a.
For a lark I tried it on the 16 GB model and it's actually not bad, but then I saw that embedded browser videos (like YouTube, for example) were funky colors, so... It may be that later versions corrected this, but those likely have the shut-down bug. In any event, a terrible choice for the 8 GB model.
Took a bit of trial and error to get the perfect version of playstore to not give an error, but I got it working. Thank you a lot for this write-up!
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
denmalley said:
Yes I am breathing life back into a BN Nook in 2020 (quarantine will do funny things to a guy). Thanks for the comprehensive guide. I had installed CM11 years ago and it kinda sucks as is, so looking forward to seeing how this shakes out. I have to re-educate myself on all the various steps like adb, installing root file manager etc, it has been a long while since I played around with android's innards!
Click to expand...
Click to collapse
While you're becoming familiar again with the procedures, give me a day or two to update the post. I recently redid my BNTV250a with CM 13 to try some things and then finally went back to CM 11 using the MicroG components rather than GApps. I'm really happy with it, but I have to say that the tablet (just like my BNTV250 with AOSP 7) behaves better if it's been on for awhile. It can be really cranky if you try to start using it right after boot.
So I'll update the post title to include CM 11 and add some details about CM 11 to the second post in a few days.
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
denmalley said:
Hey thanks for keeping up with this thread! I installed CM11 as suggested but hitting a snag with tingle. I just dumped the tingl directory into the python folder as you did and ran main.py. This was the output.
C:\Python27>python main.py
MENU
1 - Patch file from a device (adb)
2 - Patch file from the input folder
> 1 adb
ERROR: Missing adb => ['adb']
NOTE: Only one binary per type is required
ERROR CODE: 65
Not sure what I'm doing wrong
Click to expand...
Click to collapse
I don't remember seeing the "adb" after "> 1", but I may just not remember. So, just in case and to be really clear (in case I wasn't before):
1. I assume you have adb working on your PC or you wouldn't have gotten to the Python step. Did you ever set the PATH for adb? I confess I never bothered until I tried this procedure. But you have to be able to access adb from the Python folder for this to work. If you're not sure, just cd to the Python folder and try starting adb. If it doesn't work then the PATH needs to be set. Here's a good description for Windows (scroll down to "Step 2"): https://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
2. When I said I dumped the contents of Tingle into the Python folder, I meant that literally. There is no "Tingle" folder in my Python folder,but there are a bunch of extra files that are "Tingle". Just want to be sure.
Those are my only ideas at present. I hope one of them does the trick!
Ah yes path variable did the trick! On to the next steps, I'll keep you posted!
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
denmalley said:
Ok, now i am at the play store step - keep getting error "unfortunately google play store has stopped." Over and over again when attempting to open. After reboot too.
Click to expand...
Click to collapse
Did you
1. Check microG settings to be sure everything is OK?
2. Sign in to your Google account from the microG settings (add account)?
3. Then try the PlayStore (check permissions on Phonesky folder and app)
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
denmalley said:
One part I'm not clear on. I placed all of the apks where you say to (steps 6-8), once I reboot, is play store supposed to just appear? When I do self-check in microg everything is checked except playstore and the bottom two (location). I got the impression from your instructions that I'm supposed to wait for some background processes to appear.
Click to expand...
Click to collapse
Yes, the PlayStore icon should appear--admittedly a very old and funky one with this old version.
The Playstore automatically updates. I wish it did not, but there is no way to stop it. But to have that happen you have to access the Playstore at least once, maybe even download an app, and leave wifi on awhile.
On my main microG settings screen I show Google device registration ON. On the self-check screen, everything is checked except the last box. I have the location stuff installed.
So if PlayStore is unchecked, something is not right. Perhaps the app got corrupted when I uploaded it. I am shut down right now but can reup tomorrow. Or you can just get another app from Apkpure or similar. I used to use something around 8.02 to get started.
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
denmalley said:
I am very much stuck at this point (unless I guess I continue with regular gapps which goes against the whole point of this approach). I tried nuking and redoing the whole process with the same result. Attached screenshots of all relevant screens to show permissions/settings/etc.
Also I can't find a "phonesky.apk" anywhere, only full-blown google store apks which are much larger than the phonesky.apk you provided and so I must assume are not the correct thing.
Click to expand...
Click to collapse
Phonesky=PlayStore, just renamed--microG expects to see Phonesky
Something is not right with the app. I have to run, but here is a link to v. 8.02 which I have used in the past:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-8-0-23-release/
Rename to Phonesky before using. It will be a little more cranky but it will work to get you going. I hope.
Edit: or, if you prefer, go to OpenGapps and download a KitKat pico GApps. Extract from that zip the Phonesky app and use it.
Edit, Edit: yeah, I tried reupping a copy of the Phonesky app but when I downloaded it the file size did not match. So I changed the first post and inserted a link to a copy on my mediafire account. That downloads with the right file size.
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
edit
The only other thing I haven't yet tried is redownloading everything and maybe even using a different PC. Ah heck who am I kidding, like I've got anything better to do. I'll keep cracking at it.
denmalley said:
Well, I think I'm giving up. I've redone the process three times now. I used your new Phonesky.apk this last time and I still can't get the play store to show up. Only other thing I can think to ask - if I add a google account through microg settings, is it supposed to change to indicate that account is now added? Because if I go in there it will still say "add acount" even though I can see in the regular settings under accounts that a google account is present.
Click to expand...
Click to collapse
I'm really baffled by this behavior. When you add a Google account via microG nothing changes on the microG settings page, but the account should show up in the CM11 settings under "accounts".
When you prepare the system for flashing, do you do an Advanced Wipe? I'm a little AR about this sort of thing, especially as my devices have been flashed with different OS's many times. I start with an Advanced Wipe, clearing out everything except, of course, the microSD card, and then I follow that by a regular wipe. Then I start flashing.
If you are still having trouble, let me know and I'll wipe my current system (I have a backup) and start again from scratch, downloading copies of the files I have posted to see if I can duplicate what is happening to you. Maybe Google has changed something in the time since I did my newest configuration and the microG folks have not caught up with it yet. This appears to be true for Contacts because I cannot get them to sync up or even see my Google contacts. This was not the case in the past. There is chatter about it on the microG site, but none of the "solutions" go anything beyond what I have already related and some of the conclusions are like "and it just started working..."
I did not do the advanced wipe, so let me try that. I'm also going to redownload everything and give it another go. No need to wipe your device just yet - you've already done WAY more than I expected to help! I will do this over the next few days and keep you posted.
Well I tried six different ways, full wipe, change the "group" set for the group permissions to "root" (it had been set to sdcard), redownloaded every last bit of software used in this process, used a different computer, etc etc etc. Nothing is working. Still no play store. Everything else seems to be fine except that.
So anyway, I finally just did a full wipe, flashed the CM11 unofficial that you provided in second post, and grabbed a kk gapps package and flashed that. Switched from trebuchet to nova and I've got a tablet I can live with! Working much better then the cm10 rom I had on there before (like swipe to unlock screen, wait 5 seconds....touch app drawer, wait 5-10 seconds....touch an app, wait 30 seconds....slooooooow).
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
denmalley said:
Thanks for pushing me along in this direction, before I started back into this process I had completely forgotten all the little intricacies which would have gotten me hung up and possibly bricked. And all the of the other guides out there have broken links, outdated info, etc. So I'm happy with where I landed and very much appreciate the help, even if we didn't quite get there with your proposed improvements! I now have a capable e-book, backup songbook for gigs, and a spare digital mixer controller that I can clean up the personal stuff from and hand off to an assistant.
Click to expand...
Click to collapse
I'm glad you reached a point where you feel good about the outcome but sorry that you had to waste so much time.
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
nmyshkin said:
I will run through the procedure again in the next few days. Maybe there's something that got garbled in the updating of the post. In any case I'd feel better if my instructions actually achieved the intended result.
Click to expand...
Click to collapse
Well.....I'm not sure how the error crept in, but it looks like the creation of the Phonesky folder was the issue. This is needed for ROMs beyond CM11, but there are no folders in /system/app or /system/priv-app for CM11. Thus for CM11 only, the files like Phonesky.apk are simply dropped into /system/priv-app and the permissions set as described, Then everything works as it should.
I've corrected the instructions. My apologies.