Database Info

error for rooting ICS

Upgraded to ICS 4.0.4 following Jim's instruction. Got stuck on the rooting step. In windows, the driver could be installed without USB debug turned on. And I can see the phone is mounted. Only when I turned on usb debugging, the driver couldn't not be installed properly and rooting script would freeze at damon started (something like that)
Tried it under Mac too. The phone can't even be recognized. Tried factory reset/reinstall newest driver/reboot millions of times, it just didn't help. The phone still can be seen using adb devices command. But I got the following errors while running the rooting script:
Unable to chmod /data/local/12m/debugfs^M: No such file or directory
Unable to chmod /data/local/12m/su^M: No such file or directory
Unable to chmod /data/local/12m/cmds^M: No such file or directory
failed on '/data/local/12m/batch' - No such file or directory
...
I can still log on to my phone by adb -s command and it turned out I don't have permission to write or list all the phone folders including data. No wonder. There is noway of changing the permission with chmod either since sudo does not work.
I came very close to fxz back to 2.3.6 because of the frustration, but still wanted to give it a final shot. Does anyone have any idea how to get my phone rooted in this case?

Questions should be posted in Q&A (Questions & Answers) Section.
I assume you're running the script as Administrator? Also, I'm not sure what you're getting at with the drivers not being able to install if the phone is in debugging mode. It has nothing to do with the phone, you just download the latest drivers and install to your PC, then enable debugging on the phone, connect via USB, and run the script as Administrator...
Sent from my fingers to your peepers

[Q] ADB Error closed please help me.

hello, i'm new and sorry for my english, i have a chinaphone with android 4.2.2 e don't have the name of this model, so i can't find any roms or firmware for this phone.
The problem is that i installed chianfire3d and after install driver and reboot my phone is blocked in bootloop.
I FIND some tread for uninstal chinefire driver fro adb usind adb shell command.
When i write adb devices i can see my phone number, but when i use ab shell or usb or reboot or other return a message with "error closed"
I can only access to cwm 3.0 and i can't run usb debug mode.
Can someone help me with adb shell? why this happened?

help me please:good:

[Completed] Frustrated. ADB Device unauthorized. No solutions work

Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!

Follow_and_Feel said:
Hello xda-members,
I've been searching for 4 hours now and every time I try to use ADB along with my device I get the "unauthorized" message and can't use it.
I've been searching for answers all across the internet and tried nearly everything I could find, e.g.:
1. In windows cmd:
Code:
adb kill-server
Code:
abd start-server
2. Unplug phone
3. Reinstall drivers
4. Reboot phone / PC
5. Disable and Enable USB-Debugging-Mode
I read in several threads on other sites, that the adb key is the problem (there's no "authorization"-pop-up appearing on my phone, when connecting it via usb, furthermore I can't revoke debug permissions in developer settings), so I tried also:
1. delete .android. folder on my PC (C://User/me/.android.)
2. Copy the adb_key file to my phone (/data/misc/adb)
None of that worked. None.
I'm really desperate since I need ADB for several important reasons (to me important). I don't know when this problem occured first. When I bought the phone ADB worked fine. I don't know what to do anymore.
Technical information:
- Windows 10 PC
- Latest LG drivers, latest adb version
Phone:
- LG G4 H815 V20C (Marshmallow)
- Rooted, TWRP installed, SuperSU working without problems
So please, if anybody out there has had the same problems help me!!!
Click to expand...
Click to collapse
Greetings,
Please read the sticky threads for this forum. XDA Assist is for helping NEW members find their way, not a help desk for Senior members who should know where to ask for help.
Thread closed.

Having Problems using ADB after a reboot

Hello, I hope that this topic can be opened here, if not please move it or let me know and I will delete it.
In adb I am getting the error "failed to check server version: protocol fault (couldn't read status): No error" and I cannot see my device when I use the command "adb devices". Moreover, it seems like my phone is not letting me authorize my laptop for USB debugging despite trying different options to getting it to work. I have tried different trouble shooting methods that I have found online, but nothing has worked so far. If anyone has any ideas, it would be greatly appreciated.
I am using a POCO F2 Pro that has had its bootloader unlocked and I am running Xiaomi.eu version 12.0.4 (stable) and using a Windows 10 machine to connect with my phone. I did not have much problems with the flashing off TWRP, using ADB commands, or flashing the ROM when I did all of these things last month.
Now, however, I have been having some problems. I believe it started when I tries to update the System FW a few days ago in the phone instead of flashing it manually. Because it was the stable version, and because the option existed in my system settings, I thought that I would be able to update it without going through those steps. The update downloaded and I got the correct file, but when I hit install, I did not get the new FW, despite the phone rebooting. I've been having problems with adb since this time, I believe.

Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.

Saratoga79 said:
Try restarting adb server:
Code:
adb -d kill-server
adb -d start-server
Try re-enabling USB debug stuff in Dev Options too.
Click to expand...
Click to collapse
Hello, thanks for your reply. I tried that yesterday, but I gave it another try today. This was the error that I received when I ran the command in Powershell:
Program 'adb' failed to run: No application is associated with the specified file for this operationAt line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ adb -d kill-server
+ ~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ResourceUnavailable: ) [], ApplicationFailedException
+ FullyQualifiedErrorId : NativeCommandFailed
When I ran the command in Command Prompt, I got the error "failed to read response from server".
Trying to start the server also lead to an error "protocol fault (couldn't read status): No error
---------
Part of my issues may be coming from the fact that I no longer get the authorize USB debugging on my phone, even after I have revoked the authorizations. I've tried different ports, different USB cables, and even factory resetting my phone, to no luck.

Try using the latest platform tools from Google.

batuken said:
Try using the latest platform tools from Google.
Click to expand...
Click to collapse
From what I know, I am using the latest SDK platform tools. I initially downloaded from that site either in late July or early August, and yesterday I deleted the old files and re-installed them from the website. Is there an additional step that I might have missed in removing the old files from my computer?
Additionally, the .android folder in my user profile is now empty (no adb_key file(s) inside).

Op7pro not responding to fastboot commands

Hey, im having trouble finding working ways to root my op7pro GM1913 (OOS 11.0.4.1 GM21BA)
Ive been trying this https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Currently trying to unlock bootloader. (Step 2)
I can connect via adb but when i go to bootloader/fastboot i lose connection to the phone.
Ive tried regular adb command tools and "TOOL ALL IN ONE" When the phone is on it responds to adb commands but when i need fastboot commands its not working and i can see the device id dissapear from the all in one tool.
I have tried multiple usb ports (2.0 and 3.0) and multiple usb C cords (Op oem + Samsung) Tried removing Windows signature verification and installing oneplus usb drivers, but it gets stuck at "Execute the commands..." (99% or so) When i try again it finds some installation files. When im in bootloader, Windows device manager still shows a generic android phone. Oem unlocking and usb debugging is on, also set default usb configuration to file transfer. No help.
I want to keep Oxygen os, but i want to be rooted and have magisk, preferably TWRP too but im open to other ways.
Windows 10 20H2 if that matters. (Latest update for me)
Oneplus 7pro GM1913 (Eu nordic)
Oxygen os 11.0.4.1 GM21BA

Download a Linux distro and install adb and fastboot like this: https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/
Just download adb and fastboot tools package from Google, extract it,open command prompt inside where you extract it and enter these in terminal:
sudo install adb dmtracedump e2fsdroid etc1tool fastboot hprof-conv make_f2fs mke2fs mke2fs.conf sload_f2fs sqlite3 /usr/local/bin
sudo mkdir -p /usr/local/lib64
sudo install lib64/libc++.so /usr/local/lib64
Then adb --version (enter) fastboot --version (enter) like Nathan says in guide. Super easy and I guarantee you if you go this route you won't have any hiccups. Sounds like stupid windblows driver issues or outdated adb/fastboot tools. One of the two. Are you flipping on dev options and check marking little box that pops up on your phone to allow it to communicate with PC? A simple : adb devices (enter) should make it appear on phone screen. You don't even have to install Linux, you can boot it off a live USB. Takes about one minute to make one. If you make one you can boot the live USB , download adb and fastboot, and install as Nathan's guide says then reboot when you are done and your back in windblows. IDK why anyone wouldn't want Linux installed though. Best decision I ever made was switching from windows to Linux about 9 years ago. It really makes anything you do to your devices MUCH easier to do!! This may sound stupid but have you rebooted your PC? Because you will definitely need to , probably more than once on windblows to get it to work.

Thank you for the reply. No stupid questions, yes i tried rebooting pc/phone. Ill try your way and report in a couple days.

Solution is simple. From Android 11 on, OnePlus (and Android phones in general) uses the universal drivers, you just need to install them in Windows in order to use fastboot commands. See my answer in this post.

There are a few things you can try if your OP7 Pro is not responding to fastboot commands:
1. Make sure you have the latest drivers installed for your phone.
2. Try using a different USB cable.
3. If you're using Windows, try running the fastboot commands from a command prompt with administrator privileges.
4. Try booting your phone into recovery mode and running the fastboot commands.