I'm trying to root my tablet for a couple days now. It became kind of a challenge now to root it.
So here are the things I've tried:
Most famous one click root applications - KingoRoot (also the pc version), OneClickRoot, Framaroot, Zhuanhou (or something like that) , Baidu, Universal Androot, and a couple more. All failed. KingoRoot I tried a couple of times (maybe 10), all failed. First I was trying with a locked bootloader, then I unlcoked it, tried most of the things again, no success.
I tried following this thread to root it manually https://forum.xda-developers.com/showthread.php?t=2684210
Everything went well untill the part when I needed to access the files from nautilus in download mode. I tried both in an ubuntu on a virtual machine, and on a kali linux running on a live usb, but I couldn't see the files in nautilus. I tried fastboot mode also after I unlocked the bootloader, I also tried ADB sideload mode, no success.
I can see my device when I type adb devices when its on, can't see when its in recovery mode, I can see it when I type fastboot devices when it's in fastboot mode, both in windows and linux(es). I can't see it in sideload mode in adb devices (I don't know if it's supposed to be that way)
When I plug it into the PC in MTP mode, I can't see it in Windows and Ubuntu running on a VM (VMWare player), windows fails to install the driver (corrupted inf file or something), in Kali it shows up in MTP mode. I can see it in camera mode though, and it is listed in adb devices. I can connect to it's shell normaly, push files, etc. Can't switch to adb root.
I couldn't find CWM or TWRP recoveries for it either...
In the manufacturer website there are some files to download, including a reflashing manual in polish , a driver, that's actually just CWM universal driver, and their stock os image files, with sp flashing tool.
XDA Visitor said:
I'm trying to root my tablet for a couple days now. It became kind of a challenge now to root it.
So here are the things I've tried:
Most famous one click root applications - KingoRoot (also the pc version), OneClickRoot, Framaroot, Zhuanhou (or something like that) , Baidu, Universal Androot, and a couple more. All failed. KingoRoot I tried a couple of times (maybe 10), all failed. First I was trying with a locked bootloader, then I unlcoked it, tried most of the things again, no success.
I tried following this thread to root it manually https://forum.xda-developers.com/showthread.php?t=2684210
Everything went well untill the part when I needed to access the files from nautilus in download mode. I tried both in an ubuntu on a virtual machine, and on a kali linux running on a live usb, but I couldn't see the files in nautilus. I tried fastboot mode also after I unlocked the bootloader, I also tried ADB sideload mode, no success.
I can see my device when I type adb devices when its on, can't see when its in recovery mode, I can see it when I type fastboot devices when it's in fastboot mode, both in windows and linux(es). I can't see it in sideload mode in adb devices (I don't know if it's supposed to be that way)
When I plug it into the PC in MTP mode, I can't see it in Windows and Ubuntu running on a VM (VMWare player), windows fails to install the driver (corrupted inf file or something), in Kali it shows up in MTP mode. I can see it in camera mode though, and it is listed in adb devices. I can connect to it's shell normaly, push files, etc. Can't switch to adb root.
I couldn't find CWM or TWRP recoveries for it either...
In the manufacturer website there are some files to download, including a reflashing manual in polish , a driver, that's actually just CWM universal driver, and their stock os image files, with sp flashing tool.
Click to expand...
Click to collapse
Greetings and welcome to assist. Unfortunately you have already tried all the methods I would have suggested, you could try this as a last resort
https://forum.xda-developers.com/showthread.php?t=2684210
Good Luck
Sawdoctor
Related
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
zomgitsanoob said:
ADB, but not Fastboot, can see my phone. I have followed the same steps as with Windows 7, yet I can't get fastboot to see my device on this new machine. I see threads for other phones, but didn't see one for this for our phone. I need to reflash my recovery because this new CWN can't mount the sd card and I need to reflash root and busybox after OTA update (ota survival failed)
Click to expand...
Click to collapse
OTA survival failed?
Did you pay for superSU pro?
It's worked for me since ICS
And about the fastboot on Windows 8.1......Good luck
EDIT#
annoyingduck said:
After the upgrade, all drivers are wiped. Hooking up N7 to cpu triggers an auto setup that does not work correctly. In device manager what shows is and android device with an adb composite interface driver, but no actual N7...its hidden. This is how I got it to work:
I had already reinstalled SDK/platform tools/etc (if you haven't done this, just download the google drivers themselves from google). Connect device with debugging enabled and allow the auto setup. Turn off debugging, and again allow the auto set up. On my computer, both with debugging on/off the N7 did not show up in the devices list. While debugging is off, open the control panel, go to hardware+sound/view devices. Here the N7 will show. Right click it/properties/hardware/click the driver/properties/change settings/driver/change settings/update driver/manually search/choose MTP. Reboot, enable debugging/hook up/right click start/device manager/android/android adb composite driver/right click/update driver/manual search/type in path to the google drivers/install.
After that your N7 will read in the device list as an N7, files will show in the file manager (MTP), and ADB will work....
Click to expand...
Click to collapse
TRY THIS
Windows has determined the driver software for your device is up to date.
I worked just fine on a Windows 7 machine
One more reason 8 is a POS
OTA survival was a partial success. Some apps can still get root, apparently, but others fail and
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed. (when in fastboot)
Is it possible? I tried a couple of methods but it always ended up with the "error: device not found". My solution was to put it in the sdcard and spare it from any kind of wipe but i'm a curious person and i'd like to hear more opinions. Long story short is it possible to run a .zip file from the bootloader/recovery without booting the Phone first to enable the USB debugging?
It's possible in recovery on Linux. I've done it in Ubuntu. I can't do it in WinXP, but maybe it's possible in newer versions of Windows.
My logic is: you can always use fastboot commands when in bootloader. But adb commands in recovery require the device to be recognized. This is a bit of a pain in the *ss because mostly Windows doesn't install the drivers correctly when you are in recovery mode. In your device tree it is recognized as a unknown device and you have to install the motorola drivers manually. Then you can use adb to push pull files i guess.
I've confirmed ADB push works in TWRP Recovery (probably others), on a PC running Windows 7.
I was trying to install a couple of different custom roms on my phone. I have TWRP as the recovery tool. I tried a rom called ATT Buckeye and it seems to have bricked the phone. I don't have any other roms copied to the internal storage to try to flash them. I can reset to factory defaults both through holding the volume and power down and through TWRP, but I'm not able to start into a system. The only thing I can do is boot into TWRP 2.7.0.0
I saw that I can copy files using ADB, but it says "device not found" when I am connected and run adb shell. I have the drivers from LG's website installed, but there is a yellow exclamation mark on it in device manager. I found a thread where it says that I should be able to get the drivers from the Android developer SDK. I also found the individual download for Google USB drivers. In both cases, Windows isn't able to find any drivers in the USB drivers folder. I'm not sure what else I can do to revive my phone. At this point, I'd like to just get it working again any way possible.
I used this to fix my phone http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Then I was able to load Cloudy G2 http://forum.xda-developers.com/showthread.php?t=2783192
Good to go
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Chrisp3 said:
Hi guys
First things first: yes I have searched and tried various things to fix this problem before asking.
USB debugging and OEM unlock is activated, of course.
When I connect my Pixel 3a (in regular Android mode) via USB to a PC, I can see the device via adb and run commands such as adb reboot bootloader. Once the device enters fastboot mode, the connection is gone. adb devices -l and fastboot devices both come back with an empty list.
I've tried with Windows 10 and Ubuntu 20LTS, on 2 different computers and with different cables. The Pixel runs on Android 12 beta.
What I'm ultimately trying to archieve is installing GrapheneOS on it.
Any ideas?
Thanks a ton in advance!
Christian
Update: ok, after trying several things I've got it running on Linux. apt-get update + upgrade did the job. Thought my system was already up to date, but not up to date enough obviously.
Click to expand...
Click to collapse
On Windows, make sure your phone is connected and you can run ADB commands. Enter Device Manager in Windows and verify that there is a listing for Android ADB Interface.
I just connected to a new computer and I could do ADB but not Fastboot. Discovered that instead of ADB Interface in Device Manager, it just said "Pixel 3a."
If this is the same for you, go install the Android USB drivers.
KaptinBoxxi said:
You don't use ADB for communication in fastboot, you use fastboot
for example
adb devices will see the device with USB Debugging and powered on fully
fastboot devices shows devices connected in fastboot mode
Download Google Chrome and use Graphene's on-site installer rather than downloading the ZIP. Way easier for those who don't generally flash stuff day to day
Click to expand...
Click to collapse
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Chrisp3 said:
Yop, tried fastboot as well and didnt work either. Installation via Chrome is a good point. Finally did that and agree that its far more comfortable!
Click to expand...
Click to collapse
The issue with the fastboot method (realized this when I upgraded to Win11 Beta) is the ADB Quick Installs are missing some stuff, and cause certain flash methods to not work via flash-all.bat's from Google or Graphene or others.
When I install ADB System Wide, I also download the platform-tools from Google, and over-write everything in the c:\adb folder, also adding the stuff missing. Idk why the adb quick installers don't just download from google directly, would save a lot of headaches