Trouble unlocking bootloader? try this! - Moto Z2 Force Guides, News, & Discussion

I will start by saying that i am no expert. I went to the website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a to unlock my bootloader. Even though my device is eligible, the website told me it wasn't. So I looked for a workaround.
I found this post.
https://forum.xda-developers.com/z2-force/how-to/tutorial-getting-unlock-code-to-wait-t4026031
Replacing the link below with Part1 part3 and part4 with my unlock data i got from my phone using [fastboot oem get_unlock_data] (refer to post for help). After Filling out the below HTML link with your info and copying and pasting it into the web browser and hitting go, it will either come back with an error or give you the bootloader unlock code right away.
https://support.motorola.com/us/en/api/mse/bootLoaderVerifyPhone?serialNo=[/url][[[Part 1 here]]]&secSerialNo =&processorUid=[[[Part 4] here]]&bootloaderHash=[[[Part 3]]]&info Only=N
Even though their website said my Device was ineligible through there little program, I used that trick and got a code for unlocking the bootloader.
Code Worked, Have had Zero Issues. Good Luck!!
Credit goes to rcmaehl. Thank you
Original Post is here - https://forum.xda-developers.com/z2-force/how-to/tutorial-getting-unlock-code-to-wait-t4026031

Post edited:
You have to remove the hashtags "#" from the code you get from the phone.
Remove the quotes "Part1" from the link below.
Code:
https://support.motorola.com/us/en/api/mse/bootLoaderVerifyPhone?serialNo="Part1"&secSerialNo=&processorUid="part4"&bootloaderHash="Part3"&infoOnly=N
The 1st part should be 16 characters long.
The 4th part should be 32 characters long.
The 3rd part should be 40 characters long.
So, a good unlock code will look like this. Mine is 19 characters long.
Code:
{"status_code":"0000","status_description":"Successful!","Boot_loader_unlock_code":"7*****************B"}
If it cannot be unlocked. It maybe something like.
Code:
{"status_code":"0020","status_description":"Either there are errors in input data or this device does not have bootloader lock code available yet.","Boot_loader_unlock_code":null}
if you see
Code:
{"status_code":"0003","status_description":"Processor UID cannot be empty!","Boot_loader_unlock_code":null}
the link is not correct, try creating the link again.
Original Post
@jbtumbleson
All I get is
Code:
{"status_code":"0003","status_description":"Processor UID cannot be empty!","Boot_loader_unlock_code":null}[Code][COLOR="Silver"]
[SIZE=1]---------- Post added at 01:52 PM ---------- Previous post was at 01:48 PM ----------[/SIZE]
[/COLOR]Is part 4 correct?
[[[Part 4] here]]
[Code]
https://support.motorola.com/us/en/api/mse/bootLoaderVerifyPhone?serialNo=[/url][[[Part 1 here]]]&secSerialNo =&processorUid=[[[Part 4] here]]&bootloaderHash=[[[Part 3]]]&info Only=N
---------- Post added at 01:58 PM ---------- Previous post was at 01:52 PM ----------
Never mind got it, you have to remove the hashtags "#"
Code:
https://support.motorola.com/us/en/api/mse/bootLoaderVerifyPhone?serialNo="Part1"&secSerialNo=&processorUid="part4"&bootloaderHash="Part3"&infoOnly=N

Related

[Q] adb install .apk works on and off

I'm looking for insight on why my "adb install" command sometimes works and sometimes does not. Again to be clear, I was able to use the command several times successfully, but not consistently.
This week I purchased the Nook Touch, and using the wiki I was able to root it successfully. With much patients and effort I was able to get all the apps loaded up, accept Button Savior Root ver. 1.1.1
As I have been doing this I have had problems with "adb install". Sometimes it will load the .apk file and sometimes it will not. I have tried renaming the .apk files, moving them to other directories.... and sometimes, these tricks will work.
Here is a sample error message I am getting. Any insights would be appreciated, my nook experience will be easier with Button Savior loaded.
*******COPIED FROM DOS COMMAND PROMPT ******
C:\Users\amy\Downloads>adb connect 10.0.0.6
connected to 10.0.0.6:5555
C:\Users\amy\Downloads>adb shell
# adb install com.smart.swkey-imported-apk [I enter this line]
adb install com.smart.swkey-imported-apk [System comes back with this]
adb: not found [System comes back with this]
#
***** Edited 3 minutes after I posted this **********
So right after I posted the above question, I thought I would try one more time to install the app.... and it worked. You can see from the log that I did nothing different. I'm still interested in anyone's ideas on why this sometimes works, and sometimes not.
----copied from dos command window -----
C:\Users\amy\Downloads>adb connect 10.0.0.6
connected to 10.0.0.6:5555
C:\Users\amy\Downloads>adb shell
# adb install com.smart.swkey-imported-apk
adb install com.smart.swkey-imported-apk
adb: not found
# exit
exit [It was right here that I posted the above commands, and then I tried it again below]
C:\Users\amy\Downloads>adb devices
List of devices attached
10.0.0.6:5555 device
C:\Users\amy\Downloads>dir *.apk
Volume in drive C is TI102618W0G
Volume Serial Number is 2A48-CCF8
Directory of C:\Users\amy\Downloads
06/17/2011 12:32 AM 1,657,343 133adw.apk
06/16/2011 09:47 PM 1,392,535 Amazon_Appstore-release.apk
06/18/2011 03:22 PM 624,675 button.apk
06/17/2011 02:23 AM 4,915,762 com.amazon.kindle.apk
06/17/2011 11:32 AM 1,844,811 com.android.vending.froyo.apk
06/17/2011 03:48 PM 1,844,811 com.android.vending_2.2.6.apk
06/17/2011 02:33 PM 13,241,537 com.opera.browser-1.apk
06/17/2011 02:35 PM 751,542 com.opera.mini.android.v6.0_update3.apk
06/18/2011 03:22 PM 624,675 com.smart.swkey-imported.apk
06/17/2011 12:06 AM 12,130 NookColorTools_0.2.apk
06/17/2011 10:15 AM 13,241,537 Opera_Mobile_11_Android.apk
11 File(s) 40,151,358 bytes
0 Dir(s) 196,977,213,440 bytes free
C:\Users\amy\Downloads>adb install button.apk
560 KB/s (624675 bytes in 1.088s)
pkg: /data/local/tmp/button.apk
Success
C:\Users\amy\Downloads>
The adb driver will sometimes just kick off for some reason. This happens on my nook and transformer. I will be doing something then it will stop responding. Then I just simply plug back the cable after I pull it out and it works fine. Frustrating as crap along with drivers not installed message even when I just used the damn thing connected to my computer a few seconds earlier. If I knew why it did that....I would be happy. What is worse is when you plug the tablet in and then it says device not found...
Perhaps it's a typo in your forum posting, but compare the following lines, 1st taken from your "log", 2nd taken from your directory listing:
com.smart.swkey-imported-apk (-apk)
com.smart.swkey-imported.apk (.apk)

Android Device Manager as Device Administrator

Is anybody else unable to activate Android Device Manager as a Device Administrator on the Note 4?
If you go into your security settings menu, device administrators, Android Device Manager is listed there with a checkbox next to it. I click on the checkbox, get a screen asking me if I want to activate it as a device administrator, and when I click activate, nothing happens, it remains unchecked. Without it as a device administrator, it won't be able to remotely wipe the device. I wonder if this is because Samsung wants us to use their service for that? If someone could check on this for me, I'd really appreciate it!
Same thing here
---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------
Go to the link below, find your device & enable it. That just worked for me.
https://www.google.com/android/devicemanager
That did it! Thanks larosa
What's up with this? Works fine on Nexus 5. Web link works as a fix.

[unofficial][linux3.4][native][tarchive][revised]ArchLinuxARM release for HP TouchPad

ArchLinuxARM for the tenderloin (HP TouchPad) - Native Boot with moboot
This is only tested on the Wi-Fi version. With a kernel swap, it should work on the tenderloin3g (LTE) tablet, though mobile data is highly unlikely to work. I also don't know if there exists a 3.4 kernel for the tenderloin3g, and you'd have to cherrypick many, many commits.
THIS REQUIRES A DATAMEDIA ROM.
Working:
3D Acceleration (OpenGL ES 2.0, Mesa) - can be unstable, however.
Wi-Fi (with NetworkManager)
Bluetooth
Audio (requires manual intervention)
Installation
MultiROM must already be installed, and you must already have a hardboot-capable kernel installed as well.
You will need a Terminal Emulator or ADB Shell to install.
This assumes that arch_tenderloin_20141210_root.tar.gz and uImage.Arch are already in the root of your internal storage (/data/media/0).
Code:
su
mkdir /data/local/arch
tar -C /data/local/arch -xpzvf /data/media/0/arch_tenderloin_20141210_root.tar.gz
mount -o remount,rw /boot
cp /data/local/uImage.Arch /boot/
mount -o remount,ro /boot
Booting
Select "Arch" on the moboot menu.
Read Me
If you WIPE DATA, it will also WIPE OUT THIS PORT, any applications installed with it, and all data saved under /home/arch!
Logging in
The username is "arch" and the password is "archlinux". Change the password ASAP.
For root, the username is "root" and the password is also "root". CHANGE THE PASSWORD ASAP!
You'll probably want to enable the On-Screen Keyboard (onboard) and set your Session to "MATE" up in the top right corner.
Making audio work after boot requires you to open a terminal, run alsamixer, set speaker_stereo_rx up by one, and then set PCM Playback Sink Rear up by one. The headphones are controlled by the mixer channel named Headphone. The speakers are controlled by the mixer channel named Output.
Downloads
datamedia install tarchive: https://drive.google.com/file/d/0B4WUjKii92l2RFZ6T2ptSjZZVWM/view?usp=sharing
uImage kernel: https://drive.google.com/file/d/0B4WUjKii92l2ZFlOYlFETzZyeG8/view?usp=sharing
Kernel Source: https://github.com/willcast/kernel_tenderloin branch: desktop_3.4
Also available for:
HTC HD2: http://forum.xda-developers.com/hd2-ubuntu/development/unofficial-archlinuxarm-htc-hd2-t2970483
Samsung Galaxy S III LTE: http://forum.xda-developers.com/gal...unofficial-port-archlinuxarm-release-t2969290
Nexus 7 2013: http://forum.xda-developers.com/nex...fficial-archlinuxarm-release-n7-2013-t2969301
Nexus 10: http://forum.xda-developers.com/nexus-10/general/unofficial-archlinuxarm-release-nexus-10-t2969450
Great job!!
Very nicely done!
I'm just wondering:
Why is the graphics so smooth in Android but not in X11?
Anyway, keep up the good work :good:
Frickin' SWEET! I was hoping someone would continue what the CrimsonRed dude started! I'm in process of trying this out! Will report back soon!
Cool. I'm assuming an otg usb keyboard/mouse would be required?
Thanks!
Okay so I want to try this out, but I need to clear out some space/partitions first. When running novacomd I get this:
[email protected] ~ $ /usr/local/webos/usr/sbin/novacomd
[2014/12/30 7:56:47] nice(-4) returned an unexpected value: -1
[2014/12/30 7:56:47] failed to open gadgetfs ep0 node - retry
[2014/12/30 7:56:48] failed to open gadgetfs ep0 node - retry
[2014/12/30 7:56:49] failed to open gadgetfs ep0 node - retry
[2014/12/30 7:56:50] failed to open gadgetfs ep0 node - retry
[2014/12/30 7:56:51] failed to open gadgetfs 5 times - giving up on usb
Can anyone help me straighten that out? Also how hard would it be to get Funtoo Linux running in this fashion? The last time I tried I could only get it running under a chroot on a 15GB partition...
hey, i exactly followed your steps, but it turned out to be emergency mode by default, i could do nothing without otg keyboard.
could you pls kindly help me out? bzw, i already have cm11 installed on my toouchpad.
MY BAD, the webos was uninstalled, now it's fixed, thanks a lot for this excellent work!!
I'm waiting for permission from the OP, but....
I'm working on setting up a weekly to bi montly rolling release with updated packages.
I won't be doing any kernel or driver work, but Just polishing up packages as well as including updates to my own themed Desktop Environment(Trying to make something more tablet friendly).
actzer said:
hey, i exactly followed your steps, but it turned out to be emergency mode by default, i could do nothing without otg keyboard.
could you pls kindly help me out? bzw, i already have cm11 installed on my toouchpad.
MY BAD, the webos was uninstalled, now it's fixed, thanks a lot for this excellent work!!
Click to expand...
Click to collapse
I'm having the same problem. So does webos need to be installed for this to work?
Unfortunately, even though web OS isn't required for any functionality (back in the TP ubuntu days it was needed for audio), I stupidly left /dev/store/root (web OS root) in the /etc/fstab file for this build.
Next build will include optional portable VSXu player, several emulators, newer Mesa GL, and an audio patch. I'll archive it as soon as I can slim it down.
GNOME 3 even sorta works, but don't actually use it because there are unrendered black squares and it's quite slow on this device.
castrwilliam said:
Unfortunately, even though web OS isn't required for any functionality (back in the TP ubuntu days it was needed for audio), I stupidly left /dev/store/root (web OS root) in the /etc/fstab file for this build.
Next build will include optional portable VSXu player, several emulators, newer Mesa GL, and an audio patch. I'll archive it as soon as I can slim it down.
GNOME 3 even sorta works, but don't actually use it because there are unrendered black squares and it's quite slow on this device.
Click to expand...
Click to collapse
Cant wait! My touchpad is awesome now. Arch ftw. :laugh:
This is awesome! Thanks a lot, castrwilliam! Nearly everything is working well for me, even KDE!
Chromium has very good touch support. You can enable pinch-to-zoom in chrome://flags . Extemsions, such as uMatrix, work fine. Finally, a good web browser on HP touchpad!
However, I do have a couple small questions.
In KDE, when I enable compositing in kwin_gles using opengl, the colors are reversed (blue is displayed as orange). Is there any way to fix this? When using xrender, it's ok, but I have to disable lots of effects to get decent performance. HW acceleration would be nice.
In future images, could you please include touchegg-gce from AUR? It's really helpful, and I'd imagine that pretty much anyone using this without hw keyboard and mouse would find it useful.
Stupid newbie question (Sorry, I'm new to Arch Linux): Speaking of AUR, is there an easy way to automatically set arch to 'armv7l' in PKGBUILDs in yaourt? It's kind of a pain to edit them every time.
castrwilliam said:
Unfortunately, even though web OS isn't required for any functionality (back in the TP ubuntu days it was needed for audio), I stupidly left /dev/store/root (web OS root) in the /etc/fstab file for this build.
Next build will include optional portable VSXu player, several emulators, newer Mesa GL, and an audio patch. I'll archive it as soon as I can slim it down.
GNOME 3 even sorta works, but don't actually use it because there are unrendered black squares and it's quite slow on this device.
Click to expand...
Click to collapse
Are you planning on reviving Ubuntu for the Touchpad?
Sent from my LG-ls990 using XDA Free mobile app
Started running this last night. But, it takes a little extra work. I run evervolv 5.0.2 dulaboot with webos. I also use twrp. With all those, /boot is too small to add. About .5Mb too small. My solution was to cut uImage.TWRP from boot and store a copy elsewhere until needed. That gave me the nesecarry room I needed. When I need TWRP again, I will temp move uImage.Arch and put twrp back in.
Is anyone still working on this? I'm what I hope is charging my TouchPad and I want to try this again.
Shiggity said:
Is anyone still working on this? I'm what I hope is charging my TouchPad and I want to try this again.
Click to expand...
Click to collapse
I started working on some stuff with it the other day.
blmvxer said:
I started working on some stuff with it the other day.
Click to expand...
Click to collapse
Cool. Are you around right now to help me get it installed? How would we talk about it? iRC via PMs?
---------- Post added at 02:59 PM ---------- Previous post was at 02:15 PM ----------
BTW, for my current attempt I'm basically using this https://github.com/crimsonredmk/ArchLinuxARM-TouchPad/blob/master/Installation.md but when it talks about the uImage and rootfs I'm using castrwilliam's. I'd ultimately like to use the latest rolling release available for ALARM, but I want to see what happens with that's currently available.
---------- Post added at 03:39 PM ---------- Previous post was at 02:59 PM ----------
Aaaannnnd I can't seem to get my root partition on /dev/store/arch-root to mount under the requested by kernel /local/arch without it kernel panicking first... >_>
Shiggity said:
Cool. Are you around right now to help me get it installed? How would we talk about it? iRC via PMs?
---------- Post added at 02:59 PM ---------- Previous post was at 02:15 PM ----------
BTW, for my current attempt I'm basically using this https://github.com/crimsonredmk/ArchLinuxARM-TouchPad/blob/master/Installation.md but when it talks about the uImage and rootfs I'm using castrwilliam's. I'd ultimately like to use the latest rolling release available for ALARM, but I want to see what happens with that's currently available.
---------- Post added at 03:39 PM ---------- Previous post was at 02:59 PM ----------
Aaaannnnd I can't seem to get my root partition on /dev/store/arch-root to mount under the requested by kernel /local/arch without it kernel panicking first... >_>
Click to expand...
Click to collapse
I'm working on making it work currently.
blmvxer said:
I'm working on making it work currently.
Click to expand...
Click to collapse
Sweet. Let me know when you have it working and I'll try it on my 32 GB TP.
---------- Post added at 06:21 PM ---------- Previous post was at 06:21 PM ----------
I also messaged you on your FB a few hours ago. @blmvxer
Shiggity said:
Sweet. Let me know when you have it working and I'll try it on my 32 GB TP.
---------- Post added at 06:21 PM ---------- Previous post was at 06:21 PM ----------
I also messaged you on your FB a few hours ago. @blmvxer
Click to expand...
Click to collapse
I have to charge my tablet up so I can reinstall webos, but from what I can see it should work with the link you have me.

OnePlus 3T Factory Restore Utility

I have the factory restore utility available for the 3T but not sure how to upload it or link to it since it exceeds the allowable upload size limit. It's a 1.2GB 7z file.
Split it up with WinRAR and then upload it to gdrive, Mega, mediafire... The server is up to you!
guisantes said:
I have the factory restore utility available for the 3T but not sure how to upload it or link to it since it exceeds the allowable upload size limit. It's a 1.2GB 7z file.
Click to expand...
Click to collapse
Please try the attached torrent file.
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
I'm trying it. It's just a matter of time before I need something like this ;
I'm ~30% done so should be downloaded for me in ~60-80 minutes+.
Thanks.
---------- Post added at 04:51 PM ---------- Previous post was at 04:09 PM ----------
hachamacha said:
I'm trying it. It's just a matter of time before I need something like this ;
I'm ~30% done so should be downloaded for me in ~60-80 minutes+.
Thanks.
Click to expand...
Click to collapse
I've got the file downloaded, unpacked, and am wondering if there's a README that came with it? I can see a lot of the usual ways to use the components via fastboot, etc, but thought this was meant to be a .. "utter disaster recovery tool" ;. Or am I missing something?
Yes, it is and utter disaster recovery tool.
You may need the qualcomm drivers - 64 bit windows driver is attached. I believe mine autoinstalled without needing the files
**** NOTE: This procedure will completely wipe your entire device ****
To use the recovery tool.
1. With the phone turned off, press and hold the volume up button while inserting the USB cable attached to your PC.
2. Windows will recognize the Qualcomm driver and if you're lucky will auto install the driver.
3. Run the MsmDownloadTool V3.0.exe file with administrator privileges (right click and run as administrator)
4. One of the lines in the window should show COMM or something that is not "No Device" when your phone is attached and recognized as the Qualcomm loader
5. Click on that line item, then select Start
6. The whole procedure should take about 5 minutes and the line item will turn green when completed.
guisantes said:
Yes, it is and utter disaster recovery tool.
You may need the qualcomm drivers. I believe these can be easily found but if not, then I can upload them as well.
**** NOTE: This procedure will completely wipe your entire device ****
To use the recovery tool.
1. With the phone turned off, press and hold the volume up button while inserting the USB cable attached to your PC.
2. Windows will recognize the Qualcomm driver and if you're lucky will auto install the driver.
3. Run the MsmDownloadTool V3.0.exe file with administrator privileges (right click and run as administrator)
4. One of the lines in the window should show COMM or something that is not "No Device" when your phone is attached and recognized as the Qualcomm loader
5. Click on that line item, then select Start
6. The whole procedure should take about 5 minutes and the line item will turn green when completed.
Click to expand...
Click to collapse
Thanks, that seems very useful. Thanks for making it available here.
hachamacha said:
Thanks, that seems very useful. Thanks for making it available here.
Click to expand...
Click to collapse
No problem.
I've used a very similar tool previously for my oneplus one which would not power up Hopefully I won't need it for my 3T !
Here are the missing Qualcomm 64 bit drivers.
Can we make this a sticky or mention in the OP the recovery procedure from post #5? I know this will become invaluable later on as the few devs that bought this phone start fully getting into test mode.
Delete fixed. Never mind.
You should place this in general with the guides in the op with some pictures , I think many will benefit rather than diving through the QnA section for it
if i restore factory mode.what's the next?
---------- Post added at 07:35 PM ---------- Previous post was at 07:29 PM ----------
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
when i restore, after reboot, have some error, it says: md5 checksum failed!
help me!
mgbotoe said:
You should place this in general with the guides in the op with some pictures , I think many will benefit rather than diving through the QnA section for it
Click to expand...
Click to collapse
I agree: Over on OP and here, I find myself recommending this guide and software nearly each day to someone that just "bricked" their phone. It's really good. As was just said, sticky it in "Guides" area. Thanks.
guisantes said:
Please try the attached torrent file.
Click to expand...
Click to collapse
Do you have the password from the OnePlus support?
FYI.. OP3T finally has an official section on the OP downloads page
http://downloads.oneplus.net/
martinklaus said:
Do you have the password from the OnePlus support?
Click to expand...
Click to collapse
There is no password on this archive.
mahonlee said:
if i restore factory mode.what's the next?
---------- Post added at 07:35 PM ---------- Previous post was at 07:29 PM ----------
when i restore, after reboot, have some error, it says: md5 checksum failed!
help me!
Click to expand...
Click to collapse
I used it without issue on my 3T. Are you still seeing the problem?
I uploaded it on megaNZ but I can't send links in here, so if you want it, send me a message. Btw: Thanks for the torrent, works perfectly!
guisantes said:
There is no password on this archive.
Click to expand...
Click to collapse
Yes, but on the original file from the support.
That's correct. I repackaged the files without a password after tech support extracted them via a remote session on my PC. Their archive password was very long with lots of non alpha-numeric characters.

Screen turning on by itself.

When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
antz_77 said:
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving.
Someone can help me please?
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
thesoupthief said:
Mine does this also when "Raise to wake" is on ( settings > lockscreen > raise to wake), but after switching this off I can wave the phone about all I like and the screen remains off
Have you tried restarting in safe mode? Just wondering if you might have an app which is keeping your phone from sleeping
Click to expand...
Click to collapse
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
antz_77 said:
I disabled raise to wake, but screen is turning on yet when moving (only when moving)
When the winds of change blow, some build walls, others build windmills
Click to expand...
Click to collapse
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
thesoupthief said:
Try toggling raise to wake of on on then off, then reboot the phone - sounds like something is stopping the setting taking effect
Clearly not normal behaviour
Nuclear option would be to reset to factory settings, but I'd be slow enough to do that
Why not just put pocket mode on and leave it at that?
Click to expand...
Click to collapse
I tried it, but nothing. Screen continue turning on whe moving the phone. I put pocket mode (even cover frontal cámara) and same result.
I have thinking about factory reset, but one user tried a factory reset ( another xiaomi forum ) , without results.
When the winds of change blow, some build walls, others build windmills
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
i have the same problem! thought im going crazy
i try update the system and will update afterwards
Mine has the same problem on global firmware but not on china firm
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
adb shell
settings put secure wake_gesture_enabled 0
Click to expand...
Click to collapse
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
thanks for the tip with adb it works perfectly
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
It works for me. Thank you.
When the winds of change blow, some build walls, others build windmills
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
thesoupthief said:
Not sure if it's relevant but I'm on the QJOEUXM build - so the EU ROM - 4gb, 128gb redmi note 9
You too?
If so it seems very odd that we're having such different experiences
Click to expand...
Click to collapse
Version here is QJOMIXM. Same problem.
arik100 said:
i think i got a permission error
how do i give permission?
merlin:/ $ settings put secure wake_gecture_enables 0
Security exception: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS
at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2050)
at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1570)
at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1530)
at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:437)
at android.content.ContentProvider.call(ContentProvider.java:2177)
at android.content.ContentProvider$Transport.call(ContentProvider.java:477)
at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375)
at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277)
at android.os.ShellCommand.exec(ShellCommand.java:104)
at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49)
at android.os.Binder.shellCommand(Binder.java:881)
at android.os.Binder.onTransact(Binder.java:765)
at android.os.Binder.execTransactInternal(Binder.java:1021)
at android.os.Binder.execTransact(Binder.java:994)
Click to expand...
Click to collapse
You must enable first these 2 options in developers menu
I'm stupid and I don't know how to do this and have the same issue, could someone walk me trough with how to get into ADB and use the commands
I have the same problem, I upgraded to MIUI12 and it didn't solve ... the solution would be only with adb ...
---------- Post added at 02:01 PM ---------- Previous post was at 01:25 PM ----------
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
...have a link that teaches "step by step" how to do this.....
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
Thanks! That did the trick!!
And after a proper cleanup my GF's brand new Note 9 is really a good buy!
Removal/disabling pre-installed 'crapware' is always a good start, regardless of brand!
Solved!
I created my xda accout just to say thanks, this worked perfectly.
Natedanver_99 said:
After a bit of searching i found the solution for this using adb.
All you have to do is run these 2 commands
Click to expand...
Click to collapse
logan3103 said:
I created my xda accout just to say thanks, this worked perfectly.
Click to expand...
Click to collapse
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Zah5 said:
thanks for the tip with adb it works perfectly
Click to expand...
Click to collapse
Pls help me how to perfom this trick..i have the same issue
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all. Your phone screen should stay locked when you move it at this point.
Hope this helps you.
Dadaonacsil09 said:
Pls help me how to perform this process i have the issue
---------- Post added at 01:47 AM ---------- Previous post was at 01:43 AM ----------
Pls help me how to perform this action i have the same issue redmi note 9 global
---------- Post added at 02:06 AM ---------- Previous post was at 01:47 AM ----------
Pls help me how to perfom this trick..i have the same issue
Click to expand...
Click to collapse

Categories

Resources