I've got a stock Nook 3 that I've installed RelaunchX and Ankidroid on. It boots to RelaunchX.
The Android status bar does not run until I open the Nook ereader app, but then the machine is so overworked that Ankidroid has trouble running. How might I start the Android Status Bar without opening the Nook ereader app? The machine is not rooted but I'll root it if necessary.
Thanks.
This post seems to indicate that from `adb` I could probably start the status bar with something like this (doesn't work):
Code:
$ am start -n com.nook.partner
1. What would be the correct command?
2. How might I start the status bar without `adb`?
https://forum.xda-developers.com/showpost.php?p=71938111&postcount=434
Related
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
Try this:
1. turn it off completely
2. press at the same time the power button (back side) and the two lower side buttons (bottom left and bottom right page)
3. it should start the recovery and restore your device to stock
Link: http://forum.xda-developers.com/showthread.php?t=1137967
Let us know if it works.
hi,
now i don't have the Nook available (i'm at office), but yesterday i was playing with ADB and having a look at nook system folders; i remember seeing a property file in which there is a property like demoMode=enable/disable or something like that (i'm not sure, but if i remember well this file should be in the same folder where also other device specific properties like serial number, mac address, etc.. are stored).
Until reading your message i didn't even know such a mode existed. But now i think that maybe it could be possible to edit that file and enable the "regular" mode on your Nook.
Of course, even if that is possible, you would need to get root and ADB access to to that, and there is the risk of bricking the unit (even though if you can create a backup image to be on the safe side).
When i'll be back home, i will try to find further info about the above mentioned file.
Regards
hi,
i don't know if you already solved, in any case i had a better look at the system folders of Nook, and it seems to me that the Demo Mode is managed by a dedicated application (/system/app/DemoMode.apk). Baksmaling the source code of this app, it seems that it is activated on any Nook unit after boot, but in case the value of setting "demo_mode" is not set to "on", it just exits without doing anything; on contrary, the demo mode is activated (i.e. the continuous loop through a set of images).
So, to get rid of demo mode is activated, you could launch a script to change the relevant value of the setting "demo_mode", to set it to "off"; and then reboot the Nook:
Code:
echo *************************
echo * Setting Demo-Mode off *
echo *************************
adb shell mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
adb pull /data/data/com.android.providers.settings/databases/settings.db settings.db
sqlite3 settings.db "update secure set value='off' where name='demo_mode';"
adb push settings.db /data/data/com.android.providers.settings/databases/settings.db
del settings.db
Of course, to be able to launch it, you need to have your Nook already rooted, so that ADB is enabled.
The script is inspired from similar scripts present in the batch file "xe-autoroot.bat" from user xboxexpert of this forum. Therefore, in case you still don't have rooted your Nook, i suggest you to use its script to get it (link to the thread). In this case, you can easily launch the script to disable demo mode from the same folder where you have xe-autoroot.bat, since yu already have all the needed software (sqlite3).
Another possible solution could be just to remove DemoMode.apk from /system/app folder (but i'm not 100% sure this would have side effect).
In any case, not having a demo mode Nook unit, i cannot be sure these methods would work.
Hope this help
That doesn't work
When I have tried to root it I can't because I can not get to the menu to setup the wifi it won't let me get away from the screen saver my mom ordered one of these off ebay for like $40
Figured it out
If it is on an older version you can just drop the official firmware on your nook let it update and it worked like a charm
https://www.barnesandnoble.com/u/Software-Updates-NOOK-Simple-Touch/379003175/
how to disable DEMO mode on Nook simple touch
couchlife said:
I bought the NST online from a forum and the punk sent me a demo unit. It just scrolls through the various promotional screens. I've tried doing the software update and factory reset but neither of them work. Is there any way I can "unlock" everything?
Click to expand...
Click to collapse
a lot of time passed since other guys had a problem of demo mode on nook. i got my nook (simple touch) as secondhand, unfortunately locked to demo mode.
below is step-by-step how to switch it back to 'normal' mode >>>>>>
--- turn your Nook ON
--- go to Settings - Screen - on Screen window press-and-hold top-right button AND same time keep tapping the "Screen" caption (on a top of display)
--- Demo Mode will pop up on your display
--- undo 'Toggle the demo mode'
--- now to activate "normal" mode switch off-and-on your Nook !
that's It :good:
Hey,
I'm having a rooted Nook Simple Touch (FW 1.2.1) and want to add a shortcut (to launcher 8) for powering off the device. Unfortunately every tried command (adb reboot -p, several java shutdown methods) results in an immediate shutdown of the device and it looks like the device is frozen. After pressing the power button, you can see the usual "device is powering on" screen.
Does anybody know how I can power off my device, with showing the "Your NOOK has turned off completely" screen? Already tried some sendevent commands for simulating touch events, but with no success.
Thanks in advanced.
I always just hold the power button.
Do you want it to shutdown without even the confirm menu?
It's trivial, it's just an Intent, android.intent.action.ACTION_REQUEST_SHUTDOWN
Oh, but you just can't just:
Code:
# am start -a android.intent.action.ACTION_REQUEST_SHUTDOWN
Starting: Intent { act=android.intent.action.ACTION_REQUEST_SHUTDOWN }
[i]blah, blah, blah[/i] requires android.permission.SHUTDOWN
Unfortunately (or fortunately for security) android.permission.SHUTDOWN can only be obtained by a system app.
The solution? Write an app, put the permission in AndroidManifest.xml and sign it with the system signature.
This is only possible if you have re-signed your entire system.
It works fine on my Nook.
Yes, I want it without the confirm menu.
I tried your suggestion with the intent, transferred the app to with su to system app, but with no results. Do I have to generate a key by myself and sign the app to get the shutdown permission from android?
After a deeper system scan, I found the images which are shown if the device is shutdown or restarting under /system/assets. So I wrote an App set the image cold_boot_screen.png as background and shutting down the device with reboot -p. So this is working for me.
black-lord said:
I tried your suggestion with the intent, transferred the app to with su to system app, but with no results.
Click to expand...
Click to collapse
You should have seen "Not granting permission android.permission.SHUTDOWN" in logcat when installing.
You should have seen java.lang.SecurityException in logcat when attempting to run.
black-lord said:
So this is working for me.
Click to expand...
Click to collapse
True.
Still, that's really a Linux shutdown and not the kinder, gentler Android shutdown.
Or maybe not?
Maybe zygote gets a signal to shutdown and shuts down everything gracefully?
I don't know.
Re-signing your system does not have to be a big deal.
Moreover, if you want to go modifying some of the Nook's framework or Reader you'll have to do that anyway.
Dear Sirs
It has been almost 2 years since I got my Nexus 6P, and I always disable the navigation bar for a better usage. Before Oreo I added 'qemu.hw.mainkeys = 1' on Build Pro file via root file explorer. But it no longer worked, If I did, the system will collapse and I have to reflash the system. So is there any new way to disable the navigation entirely on Oreo.
Many thanks.
Best Regards
ChaoChao
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
So sad. thanks for your help though.
dratsablive said:
I am interested in auto hiding the nav keys. I had a method that worked, but had phone replaced last week, and the upgrade to OREO. I had tried using the adb command:
adb shell settings put global policy_control immersive.navigation=*
But this command returns an error about Failed executing settings. ''
I have tried Tiles, but that has some annoying lag.
Click to expand...
Click to collapse
Try issuing the command
adb shell settings list global
to see if that setting still exists.
stevemw said:
Try issuing the command
adb shell settings list global
to see if that setting still exists.
Click to expand...
Click to collapse
I was trying to execute the command
adb shell settings put global policy_control immersive.navigation=*
from a terminal on the phone, but executing this command on my laptop while connected to phone worked
Anyone can please help..!!!!
In android 8.0 (oreo),i am unable to hide soft keys using "qemu.hw.mainkeys=1".since after this my phone starts doing data factory reset,next time it boots.
I tried immersive mode but soft keys alwayas pops up while using keyboard.
Also tried themer.zip from some xda link,it does hide the soft keys but swipe at bottom where softkeys are seems laggy while performing swipe action in LMT launcher.
There's an app called custom navigation bar, you can try it out, after you did your setup you can even uninstall it.
i install custom navigation bar app,but it failed compatibilty test,what to do now???
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
lemonspeakers said:
I dont want to hide the nav bar. I want to completely disable it so it wont pop up at all anywhere. I'll be using swipe navigation.
Click to expand...
Click to collapse
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
phedoreanu said:
I want to disable it as well. Pie Control is great.
Any solution yet to disable the navigation bar on Oreo 8.x?
Click to expand...
Click to collapse
If you are rooted stock Feb update you can flash this. A restore zip should be created in a folder called ozop on your sdcard.
I have NST with firmware 1.2.1 and this kernel and (pre-installed) Nook Touch Mod Manager (modified jars: server.jar = mod-0.4.0, anrdoid(sic!).policy.jar = mod-0.2.0) and checking in Hide screensaver banner in Configure Mod Options doesn't hide banner. Furthermore I can change banner text but if I set blank string the stock banners appears. So in effect I can't hide this banner. It's either stock or one-character at best. What can I do with this?
ingramsmith said:
I have NST with firmware 1.2.1 and this kernel and (pre-installed) Nook Touch Mod Manager (modified jars: server.jar = mod-0.4.0, anrdoid(sic!).policy.jar = mod-0.2.0) and checking in Hide screensaver banner in Configure Mod Options doesn't hide banner. Furthermore I can change banner text but if I set blank string the stock banners appears. So in effect I can't hide this banner. It's either stock or one-character at best. What can I do with this?
Click to expand...
Click to collapse
Not sure about this, but I had a similar issue with NTMM not too long ago when I was doing a lot of rooting on fresh/updated firmwares. At one point I could not re-enable the slide-to-unlock, which appears to be default de-selected in NTMM. Whether I had it checked or unchecked, it was not there. I never was able to figure it out but the behavior disappeared on a subsequent rooting so I'm guessing there were a few electrons misplaced at some point. Since NookManager can be run repeatedly, you could always try re-rooting to see if that clears up the problem.
Alternatively, you could extract the modded jars from your NookManager card and apply them yourself, as described in the standalone for NTMM: https://forum.xda-developers.com/showthread.php?t=1991048
Hey together,
I just tried to get started with the Fire Toolbox 9.1 on Windows 7.
Problem is: In the Toolbox the menue items are not shown. Where normally the menue buttons are (like ADB Shell, Custom Launcher etc.) there are only white boxes with no text readable. The only text i can read is the headline "main menu".
Does anyone have got an idea how to solve it?
firet_AndY said:
Hey together,
I just tried to get started with the Fire Toolbox 9.1 on Windows 7.
Problem is: In the Toolbox the menue items are not shown. Where normally the menue buttons are (like ADB Shell, Custom Launcher etc.) there are only white boxes with no text readable. The only text i can read is the headline "main menu".
Does anyone have got an idea how to solve it?
Click to expand...
Click to collapse
You recommended to upgrade your PC to Windows 10. You have to report your bugs to @Datastream33 instead.
Windows 7 is End of Life so I don't think the developer is going to support the OS. Just upgrade the PC to Windows 10.
Well, thats not very helpful - you guys should be rather ashamed of yourselves - you could suggest a Win10 upgrade rather than belittling the user for having an older OS.
Or, you could just give them the answer they need....
Try changing the windows themes - I find that High Contrast #2 often works fine.....its just a display issue.....
You can download Windows 10 from the Microsoft website
Download Windows 10
www.microsoft.com