Hi,
I ran the MIUI unlock tool on my phone and it went through and ended in "success", however if I open root check or super su it reports its locked. Developer options says its unlocked as does trying to run my banking app it reports "cannot be used on rooted device" but anything that needs root reports its not rooted.
Anyone able to shed any light on this?
Root and bootloader unlock are 2 different things, flash twrp recovery and flash magisk if you want root, if I understand correctly
OK so I have fastboot working but ADB returns - error: no devices/emulators found. What I want to do is in this https://forum.xda-developers.com/poco-f1/how-to/guide-activate-vowifi-wlan-call-t3871263 but I can't get adb working and "su" on a terminal on the device returns command not found
Make sure you are connecting your PC to your fone using a usb 2 port. If the PC doesn't have usb 2 ports, connect via a usb 2 hub.
Related
Enabling USB Debugging through ADB? Im Stuck at Black Screen W/ "Unauthorized" in ADB
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Mcfinnipoop said:
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Click to expand...
Click to collapse
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
macstibs said:
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
Click to expand...
Click to collapse
No recovery if bootloader remains locked.
Davey126 said:
No recovery if bootloader remains locked.
Click to expand...
Click to collapse
Still a pretty nice tablet - sucks that there's seemingly no fix to this (especially after I paid $100 for a new lcd)...
Hello,
A friend of my asked me to install a new version on his iOcean X8 Mini.
After a few minutes into the process, I discovered that I couldn't modify anything at all.
Problems start occuring when I enter Fastboot via ADB (I power up the phone, connect it to PC, give it permission to use Android USB Debugging, then via 'adb rebeoot fastboot' I enter the Fastboot menu). Every command I enter here returns 3 dots just doing nothing. My command prompt is unusable after entering a command (for example 'fastboot oem unlock').
I've tried to push a ROM via ADB but this isn't working as well since it returns something like 'no permission' when trying to install, but I figured this was due to the locked bootloader.
Searched all over the internet for solutions, but so far nothing has really worked. What I somehow did mange to do is root the device (don't know if it was by default, I assume not), via RootGenius.
Anybody got any experience with this, and perhaps know some steps I can undertake to indeed unlock the bootloader of this phone?
Thanks in advance!
HELLO,
I have been trying to upgrade my Acer liquid e700/e39 from 4.4.2 kitkat to lollipop, so i have been trying to install philz touch recovery to my mac, which is running mac sierra.However whenever i get to the point that says 'this requires a working adb on your pc and a root shell on your mtk devices click ok, then it say's please wait a moment, then it says 'please connect your phone via usb, whenever i connect the phone and click okay it says "sorry adb root shell isn't working.But i enabled adb root on my phone via king root,and usb debugging is also enabled.I also followed some tutorials about installing adb and fastboot on mac x, and ran some commands via the terminal, but i still keep on getting 'sorry adb root shell isn't working with a yellow exclamation, and it then asks if i want to download some mtk tools which takes me to pdanet.I set up pdanet on the mac and on the phone from the instructions, but still nothing works.help!
thanks.
OEM unlocking and USB Debugging enabled.
ADB never finds the phone in my windows 10 install no matter what drivers I force it to use. - Tried USB 2 and 3.
Fastboot does find it if I manually start it in fastboot mode, but it can't do anything to it
Fails to write when doing oem unlock
Just sits there if I tell it to write the recovery image.
Phone functions fine, I just want root and a 3rd party rom to be rid of any built in spyware.
Any ideas? any way to root it without flashing then I can just have the twrp app flash it?
Nevermind, found a way around it. This dialpad command made it work
Personmans said:
Hope this will help someone with trouble getting ADB/Fastboot to work. I assume you have a similar environment to me: Windows 10, with working ADB drivers on another device (LG G4 in my case)
Set up LeMax2 in developer mode and enable USB debugging as usual.
Plug in usb and dial *#*#76937#*#* check the box that says "Enable AT Port"
The device should immediately give you the approval message for USB debugging.
Note: This will not stick after a reboot.
Once I had this working, I did an adb reboot recovery, but fastboot still did not work. With the device connected and at the stock recovery screen, I had to open device manager, delete the LeMax device, and allow it to detect again. Finally it appeared in fastboot devices and I was able to flash recovery.
Click to expand...
Click to collapse
I have Samsung Galaxy Tab S2 that I attempted to root earlier today. I used Odin and CF auto root method. Everything appeared to go fine, until it restarted itself after it was done. When it booted back up, the WiFi was not working. When I turn it on, it is simply stuck on "Turning on...." and nothing happens.
Problem 2: When I connect the tablet to a computer via USB cable, it does not recognize it. I'll hear a chime, so it detects it, but it does not show up in the file explorer. The tablet is set for a MTP USB configuration.
I tried a factory reset, but that did nothing.
I'm not sure what to do now. I do have a micro SD card, so I'm able to move it back and forth from the tablet to my PC to install APKs and other files. I'd like to try flashing a custom ROM to see if that fixes it, but now I'm not rooted. I used the SD card to install a couple of the one click root apps, but they were either unsuccessful, or require an internet connection to use.
I don't know if it's possible to actually install a custom ROM on a device that doesn't have internet access and can't use a USB cable.
If anyone has suggestions as to either of my problems, I'd love to hear it, because as of now I can't do anything with my tablet.
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
daphr said:
You can try to:
wipe data/cache from recovery and reboot it again to see if the wifi error still exists, or you can flash it again.
You can get and use adb/fastboot, if you haven't already, and check if fastboot (execute fastboot devices in cmd) recognizes your device after the chime sound. If you're lucky and your device is displayed, you can flash it again. All the best!
Click to expand...
Click to collapse
Thanks. Executing "fastboot devices" returns an empty list, however "ADB devices" returns some sort of serial number with "offline" next to it.
edit: I've been running adb kill-server and adb-start server commands, followed by adb devices, and that will switch the device status from "offline" to "unauthorized". I'm not sure how to fix that. I navigated to my .android folder on my PC and deleted the adbkey file but that didn't help.
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
daphr said:
In developer settings Enable USB debugging, revoke current USB debug authorizations and allow your PC's fingerprint. You can also enable OEM unlock in case you plan to play with the bootloader and custom ROMs.
Next in cmd after plugging the device in, check if it gets detected: adb devices
If you get the list you've mentioned, execute: adb reboot bootloader
This should boot your device into the fastboot mode where you have full access to your phone, so be careful what you're doing.
If you need more info on fastboot and adb, check out the forums.
Good luck!
Click to expand...
Click to collapse
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
Have you been asked for a new computer ID to accept after revoking old ones and plugging the device in again?
As long as you don't add new fingerprint of your computer to the device, your device will be unauthorized.
febtober said:
Unfortunately it's still showing the device as "unauthorized". I've toggled developer options and USB debugging on and, and repeatedly tried "Revoke USB debugging authorizations" but it hasn't help. I can't execute the adb reboot bootloader command while it's unauthorized.
Click to expand...
Click to collapse
You need to restock your tablet via odin (to put modem back aka Wifi)
After you restock Install Twrp and install magisk to root, instead of cf-root like you did (this will not breaking the safety net or knox even the modem)
(Note:before install magisk backup your "BOOT" via TWRP)