Database Users

[Q] Accidentally bought a demo unit, any way to fix it?

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:

[Q] Slider Disabled, Not recognizing gesture.... now what?

I am running CM
So I disabled the slider unlock, but it stopped recognizing my gesture for some reason and I cannot figure out how to login to my phone. Running stable build of CM7.1, not sure if I can change that setting somehow from ADP or do something from a terminal... Any ideas?
When I say gesture, I am not referring to the password based on the motion with the dots, I am saying the screen where the unlock / silent toggle was has been disabled and I cannot get passed there.
Your help is appreciated

Did u try unlock with menu button?
I remember that from cm7
Sent from my MB525 running 4.5.1-134 DFP 231 DEFY+ ROM...
using XDA App

No menu button doesn't do anything....
Do you know WHERE this "Slider Disabled" setting is stored? I could go in thru ADB and change it but I don't know where to look.
Here are the things I have tried already
----
Attempt 1:
$ ./adb -d shell
# cd data/data
# sqlite3 ./com.android.providers.settings/databases/settings.db
sqlite> update system set value=1 where name='lockscreen_disabled';
sqlite> .exit
# reboot
Attempt 2:
adb shell
input keyevent 82
---
Neither of these worked. I think the solution should be in the updating the settings.db, but maybe its a different row/record that contains "ENABLE slider"?
Help would be appreciated!

could deleting the the offending theme restore to normal?? Just thinking out loud here ^^
don't know much about adb

Okay. No help here, but I found a fix and I thought i would share it since I have seen that apparently other people have had this problem with no help as well other than "Wipe and reinstall rom"
This app fixed it!
https://market.android.com/details?id=se.curity.android.screenlockbypass
Just make sure you follow the instructions, you have to install the app, than install any other random app and BAM- unlocked phone! Sweet

Nexus 5 Jolla Store fix, warehouse install, and keyboard predictions

Found this answer deep in a Jolla thread and it worked like a charm, so I thought I would bring it to light for anyone trying to enable/fix these features on their Nexus 5 running Sailfish OS:
All credit to @5pik3
Download the newest version on your Jolla device here: https://openrepos.net/content/basil/warehouse-sailfishos
Go to terminal (or dev SSH access)
Acquire root permissions with
Code:
devel-su
Type in the password from the developer options panel in the settings app
Now execute this code, line by line
Code:
ssu dr home
ssu dr adaptation0
zypper refresh
If you get a prompt here, type yes (you may have to do it 2 times)
Code:
pkcon install-local /home/nemo/Downloads/harbour-warehouse-[version].armv7hl.rpm
(Replace '[version]' with the version you are installing)
Code:
pkcon install store-client jolla-xt9 jolla-xt9-cp
And that is it! Jolla store should work, Warehouse should be installed, and after a reboot, you will have keyboard predictions!
OP:
5pik3 said:
If you want to install warehouse app download from here https://openrepos.net/content/basil/warehouse-sailfishos
Now open your terminal app or use the ssh access.
You need to have root permissions with 'devel-su'. Enter your password (the one in the developper options in the settings app).
Now you have to disable some repos : enter 'ssu dr home' and 'ssu dr adaptation0'.
Try a litle 'zypper refresh' and you will see no more authentication errors
And you can install the warehouse app with 'pkcon install-local /home/nemo/Downloads/harbour-warehouse-0.3-20.armv7hl.rpm'
And finally you type 'pkcon install store-client jolla-xt9 jolla-xt9-cp'
You can now have the keyboard prediction's and have both warehouse and jolla store to work
Click to expand...
Click to collapse

pkcon install store works fine on nexus 7 grouper but installing things from within the store gives an error to me

same issue with nexus7
Having same problem using sailfishos-grouper-release-1.0.8.19-alpha1.zip on nexus 7 grouper.
Any tips?

help
why i can't type the password on terminal??

chandradcp said:
why i can't type the password on terminal??
Click to expand...
Click to collapse
You are typing it in, it is just not showing up (this is a security feature for every linux distro). So, type the password in (even though it is not showing up) and hit enter, it will work.

vman411gamer said:
You are typing it in, it is just not showing up (this is a security feature for every linux distro). So, type the password in (even though it is not showing up) and hit enter, it will work.
Click to expand...
Click to collapse
thx... it works:good:

Fresh installs of Sailfish OS 2.0.5.6 give an error when running the final command.
Code:
[[email protected] Downloads]# pkcon install store-client jolla-xt9 jolla-xt9-cp
Command failed: This tool could not find any available package: could not find jolla-xt9
Any idea how to fix this?

Guide to avoid registering a new GSF android_id at each clean install

As you may noticed since last week google wants us, the custom rom users to manually register our android_id to the link https://www.google.com/android/uncertified/
It looks simple isn't it?
But there's a catch. Each google account can register up to 100 ids. So if you keep registering new ids after every clean install you'll more likely to hit that 100 ids limit soon. That's even worse for fhe rom developers as they may flash up to 20-30 roms a day.
I'm figuring out that in a different way though. The procedure I'm following is:
A. BEFORE ANYTHING
If you're doing this first time:
1) Copy this database from /data/data/com.google.android.gsf/databases/gservices.db
2.1) Open the database with a sql editor or from adb shell or a terminal emulator in sqlite3, see android_id with this sql command:
SELECT *
FROM main
WHERE name="android_id";
2.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "SELECT * FROM main WHERE name = \"android_id\";"'
3) Then save the value you're seeing to somewhere else, and register to your account at https://www.google.com/android/uncertified/
B. THEN FOR EVERY CLEAN INSTALL
1) Backups and wipes.
2) Flash rom (pt roms with vendors have the firmware included).
3) Flash gapps.
4) Optionally flash a custom kernel.
5) Reboot and configure your device.
6) Flash magisk, reboot.
THEN THIS PART IS IMPORTANT:
7.1) Again copy this database /data/data/com.google.android.gsf/databases/gservices.db and open in a sql editor (or with sqlite3 in terminal emulator, or adb shell) and execute this sql command:
UPDATE main
SET value=XXXXXXXXXXXXXXXXXXX
WHERE name="android_id";
7.2) OR from adb shell:
$ adb root
$ adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db "UPDATE main SET value=XXXXXXXXXXXXXXXXXXX WHERE name = \"android_id\";"'
Note: XXXXXXXXXXXXXXXXXXX is your android_id as you've learned and registered to your account before (You can see the android_id s you've registered at the same google link).

I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.

Deleted

Deleted

muff99 said:
I just registered my IMEI, that one stays the same across factory resets.
Also, Titanium backup has an option to restore a previously used android ID.
Click to expand...
Click to collapse
Yes that works too but this is the manual method for the gsf android_id. Wifi only devices doesn't have IMEI for example.

https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/

G4B33 said:
https://www.xda-developers.com/google-removes-100-device-registration-limit-uncertified-device-page/
Click to expand...
Click to collapse
Yes so now we don't have to do that much of hacky-wacky stuff just to get gsf certified status anymore. #YayGoogle? ?

What if you don't do that?

seems not working. After rebooting, it went back to previous id

You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/

ccelik97 said:
You know I've just realized that doing exactly what's written on Google's page (that I've shared link of it) doesn't change my status too. My id is exactly what I've registered on the id registration page but no it stays uncertified so you can ignore this post too... I hope we can find a solution soon :/
Click to expand...
Click to collapse
I think the display will always stay on "not certified", but you are atill able to use the Google services (which unregistered custom ROM users are not any more, if I understood correctly).
This is just a guess on my side, I have not tested this (and I can't since I added all kinds of IDs to that registration page ...).
All in all the information flow from Google on this topic has been spectacularly bad, imho.

When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.

image45 said:
When I register my GSF id, its not saved or a different number is display, see my correct I'd in the enter field vs ones registered.
Click to expand...
Click to collapse
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.

muff99 said:
That's because you entered it in hex format, it gets converted into decimal.
Also, don't post your id here ... Not sure what happens if other people register your id with their Google account.
Click to expand...
Click to collapse
Do I need to convert it or is that an accepted way to submit the information please?
If I try to resubmit it advises already registered.

[Guide][nonroot] Fix AndroidQ no UI sound bugs

Since I originally wrote this I have found an even easier way that works 100% without root using Setting database editor so I've updated this guide to the better method.
as a few of us 2XL owners will know Google derped sounds on the factory image of Q and our nice charging sound has been replaced with a horrible Error sound (Google Bug tracker.)
after a few weeks of waiting & trying to fix the issue myself I have finally managed to figure it out...
turns out they're trying to access sounds from the WRONG location
UI sounds on factory Q image seem to trigger from /product/media/audio/ui but this directory only has boot animations, no audio as these files are actually located in /system/media/audio/ui
it's probably why upgrading from 9 to 10 keeps the audio settings but factory flashing doesn't.
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the settings database editor (link above)
Code:
open a terminal app and type(or copy paste) the line below;
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
or using adb:
Code:
adb shell
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
using setedit go to the global tab and look for each of the UI audio settings, switch /product/media/audio*.* to /system/media/audio/*.*
Restart your phone to apply the settings.
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Minor notes:
I'm unsure why the charging sound is dictated by wireless_charging setting.
I've had a report that settings revert after a few reboots, I've not had this myself and I've rebooted a lot but if it happens just reapply the changes in setedit.
You can also change the sounds to files on your system, I've not had luck pinpointing my sdcard folder but I have been able to change Lock.ogg to Dock.ogg as a test.
(/Sdcard/download didn't work)
_________( Old method )_________
This is my first write up so please bear with me
please note I'm not responsible for any messups you make doing this
it can be done on a terminal emulator, I prefer ADB shell
in order to sucessfully do this you will need HiddenSettings magisk module
Thank you skittles9823
I'm unsure if you need busybox but the module certainly looks for it
Code:
[B][COLOR="red"]adb shell[/COLOR][/B] or launch your [I]TerminalApp[/I]
taimen:/ $[B][COLOR="red"]su[/COLOR][/B]
taimen:/ [I]#[/I] [B][COLOR="red"]hidden[/COLOR][/B]
4 - All settings
[CHOICE]:[B][COLOR="red"]4[/COLOR][/B]
3 - Modify settings
[CHOICE]:[B][COLOR="red"]3[/COLOR][/B]
===== Modify Settings =====
[Search?]:[B][COLOR="Red"]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/COLOR][/B]
press enter & reboot your phone.
That is pretty much it, hopfully the android team fix this next patch.
I'll add some notes from what I have found through tinkering
you must reboot after modifying EACH setting.
you can see the "=" is not added when changing the settings wireless_charging_started_sound=/system/media/audio/ui/ChargingStarted.ogg (wrong)
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg (Right)
Here are all the settings i can find
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg (this causes an error on my phone)
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg

Awesome job figuring this out. Hopefully Google will fix this in the November system images since You've done all the work for them.

Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update

Nightf0x_007 said:
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Click to expand...
Click to collapse
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that

co4 said:
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
Click to expand...
Click to collapse
Does settings revert back after multiple reboots ? Cause this happened to me

Nightf0x_007 said:
Does settings revert back after multiple reboots ? Cause this happened to me
Click to expand...
Click to collapse
I've yet to have anything revert yet if it does happen I'll post, I guess you can reapply the settings? Or once they revert can they be re changed?

Awesome it worked I have all my sounds back!!!!

krolla03 said:
Awesome it worked I have all my sounds back!!!!
Click to expand...
Click to collapse
I'll add that it's been reported that setting may revert and reapplying will fix it again

co4 said:
I'll add that it's been reported that setting may revert and reapplying will fix it again
Click to expand...
Click to collapse
so far so good

Thank you SOOO much! :highfive: It works on my Pixel 2. Had to reset it to factory after the December update killed my Pixel launcher app. After the reset I faced this horrible charging sound and the lack of lock sounds, too.

God this was driving me crazy on a warranty replacement Pixel 2. 3rd replacement and finally it boots and the battery is decent.
I don't know if I would have noticed but for having 2 phones side by side. After that, I couldn't un-hear it.

What about Effect_tick.ogg? Is there any way to set this custom sound?

Hi,
I've tried the first method, but I couldn't grant permissions in the Terminal app, it fails!
I don't have root.
Can anyone help?
Thank you so much

All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.

Mandrutz said:
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Click to expand...
Click to collapse
I have this also on my pixel 2 does anyone know the ADB script for that?