Database Users

[Q] Recovery Error

When i tried to Boot from recovery mode i got Error message with no command.. none of those option in recovery mode working. My phone is UN rooted running on official 4.3 Jellybean. Is this only i m getting? or because my phone is unrooted its locked?
Some Assist would be nice thank You

try using ADB commands:-
connect your phone using usb cable (with usb debugging enabled in developer options)
open command prompt (windows)
if you have ADB as environmental path then just type "adb reboot recovery"
else you need to navigate to the adb.exe and then type the upper command.
it worked for me

can u link where can i download ADB tool

i've attached the latest ADB version 1.0.31 (don't use older versions as they wont work on our device)

No wifi after downgrade to MK3

Hello, I downgraded to MK3 to root my device and succeeded. However, I no longer have any networking that works. The guide here says to put in this cmd code to fix it, but doesnt tell you where to do it. I tried with my device connected on CMD but it won't work at all. He gives no instructions on how to do it. http://forum.xda-developers.com/showthread.php?t=2663545
Could someone please help me with this?

Laemon said:
Hello, I downgraded to MK3 to root my device and succeeded. However, I no longer have any networking that works. The guide here says to put in this cmd code to fix it, but doesnt tell you where to do it. I tried with my device connected on CMD but it won't work at all. He gives no instructions on how to do it. http://forum.xda-developers.com/showthread.php?t=2663545
Could someone please help me with this?
Click to expand...
Click to collapse
There are 3 methods posted there? Didnt you try at least method 2?
Ensure that "adb devices" in CMD detects your phone being connected.
Code:
adb push bypasslkm /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm

jmjoyas said:
There are 3 methods posted there? Didnt you try at least method 2?
Ensure that "adb devices" in CMD detects your phone being connected.
Code:
adb push bypasslkm /data/local/tmp
adb shell
cd /data/local/tmp
chmod 755 bypasslkm
./bypasslkm
Click to expand...
Click to collapse
I used the second method and got it working, didnt realize they were talking about different methods. However, now my sim card isn't working. No networks besides wifi.

Laemon said:
Hello, I downgraded to MK3 to root my device and succeeded. However, I no longer have any networking that works. The guide here says to put in this cmd code to fix it, but doesnt tell you where to do it. I tried with my device connected on CMD but it won't work at all. He gives no instructions on how to do it. http://forum.xda-developers.com/showthread.php?t=2663545
Could someone please help me with this?
Click to expand...
Click to collapse
You phone must be previously NB1 and you need to root so you downgrade to MK2, root, and instal safestrap.
Your post appears that you finished steps 1 through 7..
Your bootloader is in NB1 but your modem and kernel is in MK2 so your wifi would not work.
To fix it , either you go back to NB1 or use the bypass exploit.
if you had made a NB1 backup before you odin you can restore that back up. That is for the step 8.
If you want to go back to NB1 use the file in the post #2 and follow the instruction on post #3.
if you want to stay in MK2 you can use adb (android debug bridge) to fix the wifi problem . That is for the step 9.
Search adb on the net and get the adb files. go to command mode with admin, start the adb connect your phone and check your device is listed in the adb.
Then enter the codes that mentioned on the page step by step.
If you had never use the adb before I would go back to NB1.

I've decided to give up, having too many problems and been at it for 5 hours to 6 hours. Updated back to 4.4.2 and will simply look to root before installing updates on the next device I buy.

[Q] dumpsys batterystats working only via adb

Hey all,
in terminal emulator when i try to do dumpsys batterystats as normal user, i get a permission denied error. So far so good but when i execute the command as root, it says that dumpsys didnt find the service 'batterystats'
But when executing this from adb shell on my computer, it works without complaints?!!
I tried doing this because i noticed wakelock detector not showing any data so i went to supersu log to look what command the app tried to execute and it was dumpsys batterystats
P.s. i tried su'ing to [email protected] as well hoping that it would work but i get the same response as with root
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery

Okay i just updated supersu and it is working now ?
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery

Device boots into Bootloader

I tried all the methods mentioned in the threads already present in the forum, but none of the methods seems to work for me. " no space left on the device " this is the error i get when i execute command "dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc" .

That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run
Code:
#cd /dev/block/platform/soc
#find . -name misc
to verify 7824900.sdhci is correct address.

[email protected] said:
That command is if you are stuck in bootloop that boots to recovery, not bootloader. Also, if you meant it boots to recovery, your path to misc. may be different, 7824900.sdhci is for moto g5 plus xt1687. May be for others also, but to be sure, run to verify 7824900.sdhci is correct address.
Click to expand...
Click to collapse
I posted this query earlier and all of them stated this solution to the problem. My problem is my device never reboots itself it reboots into bootloader and from there i have to manually press start to boot into rom and also my device is XT1686

As I posted, run the commands to be sure your misc. address is 7824900. If it returns something different, modify the
Code:
dd if=/dev/zero of=/dev/block/platform/soc/7824900.sdhci/by-name/misc
command to reflect your misc. address. Also I believe those commands need to executed as root.

I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.

JohnSmith8786 said:
I had the same issue after upgrading the stock firmware to Oreo. Running the command via terminal wouldn't work either, I had to connect to a PC and run the command via ADB while in twrp. Worth a shot if you hadn't tried it.
Click to expand...
Click to collapse
Yes, ADB/Fastboot is always preferred, terminal is where you must run as root with su commands, and you must be rooted with Majisk .

[Moto G6 Plus] developer option OEM unclock is disabeld (gray, not switchable enable)

Hi,
I have had a MotoG6 plus from a friend, but after upgrade it from 8.0 to 9.0 begans problems. The phone goes on crash and restart many time during usage of lots of Apps. I Tried a factory reset + reinstall alot of app, but nothing changed. The phone crash as well with same frequency. I decide to broke it and i tried to install a LineageOS16_9Pie. Unfortunatly during the Custom install, even if i followed a guide, unloking the bootloader, i really broke it, the bootloader and recovery partition. I have started the image of TWRP via fastboot to obtained a motoG6plus working (even without a proper bootloader) with LineageOS16_9Pie. To do it i've got the code from motorola site, to unlock the G6plus, after eneable USB debug + OEM Unlock from OS. With theLineageOS i have unlocked and locked oem many times using the OS without any problems . I have used the LineageOS for a week, after that, It started agan the same crashs i had with the stock rom 9.
I decided to reinstall the 8.0 version Evert , to remove the boot errors and because with the 8.0 was stable. After i installed the stock rom 8.0 evert i cant' unlock oem again . Into the developer option, the option "OEM unclock" is gray , disabeld not switchable . Even if i tried to unclock again from fastboot command , it say that i have to switch and anable "OEM Unlock" from the OS but i can't.
Is there a way to unclock byassing the OS or re-enable that option?

Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Thanks WoKoschekk, but i surely ' loaded a wrong rom, because the Moto G6plus don't have Wifi and connectivity via SIMs working, so I can't download any app. I am going to try to copy an app via apk on the SD. The good news is that the bootloader initial stop has disapeared, (but i still do not have any recovery)

Nothing to do with "install app unknown" o similar (sorry, my phone is in Italian). Even if i do have the apk terminal emulator, i Can't install because of the few app in list that i can unable to install unknown sources. In this list there isn't "File manager" .. i still have the error of parsing the package

If you downgrade from Pie to Oreo you will lost all connections. To get them back you must flash a Pie version of any Rom.
First of all flash the right and latest firmware.

I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.

Reggians said:
I Would like to reburn another rom, but i can't because the option "Unlock OEM" is in "gray" not switchable, so for be is a bit hard. I am stuck..
Thanks anyway for your interest. I appreciated it.
Click to expand...
Click to collapse
Flash the latest Magisk.zip to enable OEM unlock option.

WoKoschekk said:
Try this command in terminal app:
Code:
:/ $ su
:/ # service call oem_lock 1 s16 allowed
The output should be:
Code:
Result: Parcel(00000000 '....')
Click to expand...
Click to collapse
Hi
I finally copy a term.apk and installed with success ! (i have no root permissions on the device)
when i give
Code:
evert_n:/ $ su
the answer is:
Code:
/system/bin/sh: su: not found
127|evert_n:/
if send the command with #
Code:
:/ $ # service call oem_lock 1 s16 allowed
i get null
Code:
127|evert_n:/
if i send the command without # (probably it is the cli after su level) like this
Code:
:/ $ service call oem_lock 1 s16 allowed
the answer is
Code:
service: Service oem_lock does not exist

WoKoschekk said:
Flash the latest Magisk.zip to enable OEM unlock option.
Click to expand...
Click to collapse
I have installed Magistik7.3.4.apk via filesystem but, i don't have connectivity and i can't install it via TWRP because i have the device locked so i can't even try to load TWRP via fastboot , so Magistik is not fully working unfortunatly..

Are you able to start the device in fastboot mode?
What is the error message when booting in TWRP?
For the "service oem_lock" command you need super user rights...

if you haven't solved it yet, use this to enable internet connection to your phone and you will be able to unlock the bootloader
https://github.com/Genymobile/gnirehtet

Has anyone solved this? Do I need to wait the 7 days to unlock it again?
I saw a thread where someone said they skipped the 7 days by changing the date of the device and rebooting, but that didn't work for me.