Hi all, trying to install CM on Nextbit Robin and I'm having trouble getting the TWRP recovery img flashed. I have working Fastboot & ADB tools installed. Robin driver is installed on PC. Device IS responding to Fastboot and ADB commands. Have unlocked Bootloader and in Fastboot mode now trying to flash recovery (TWRP) img. Have latest TWRP file etc but CMD screen on PC returns a "cannot load file" message. TWRP file located in same directory as Fastboot etc. (I'm working from Windows 10 environment.) Debugging enabled etc. on device. I've flashed CM many times on other Android devices - haven't encountered this issue before. Only issue I've noticed is that the command ADB Devices returns "List of devices" but nothing is listed - HOWEVER device IS responding to ADB commands and Fastboot commands. Thanks in advance for any help you can provide!
I have the exact same problem,
Related
So I'm in the process of trying to Root my ZTE Smarttab 10 on firmware v03b.
Ive been following instructions on the following pages:
http://forum.xda-developers.com/showthread.php?t=1629630
http://forum.xda-developers.com/showthread.php?t=1473555
The instructions are spread out across those threads and my problem starts kind of early in the process.
My goal is to use ADB to boot in to the Bootloader and then use a recovery rom to use TWRP to install a rom.
What i have done:
I have installed the ZTE Drivers
I have installed the SDK tools and updated it.
Now when the tablet is running normally I can see it in ADB and is able to run the command.
ADB Reboot Bootloader
This reboots the devices to a black screen (I assume this is the bootloader) and windows recognizes that a device is there.
The problem is that when I try to see this from ADB i cannot see the device when running ADB Devices.
This makes the next step impossible as I need to use ADB to boot a recovery rom.
So I would have posted in the development treads listed above but as I dont have 10 posts (this being my first post) I cannot post in the threads above.
I'm confident that this is a driver problem and I have uninstalled and re-installed all the drivers related to this including SDK.
But no luck yet.
Where other people say they have succeeded is when in the device manager they have ADB interface and ZTE Handset ADB interface listed.
This is the state where I'm at but I still cannot see the device in ADB.
Anyone have any insight on this kind of problem and can offer any help for a solution or direction to get to the solution.
Thank you for your help and attention!
//Nagarutu
Vodafone (ZTE) SmartTab10 3.2 HoneyComb
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
matt4321 said:
You can't use adb in bootloader mode, you want fastboot. So when you do 'adb reboot bootloader'. It reboots to the black screen (that is the bootloader). Try typing 'fastboot devices' and see if you're device comes up. It should if you have all drivers installed correctly and fastboot on your system. Then you'll be able to do 'fastboot flash recovery recovery.img' to install the custom recovery, then a 'fastboot reboot' and lastly an 'adb reboot recovery' will get you into your custom recovery to flash a new rom. Don't forget to make a backup.
Click to expand...
Click to collapse
Thank you for the help ! it cleared things up for me.
Now the trouble's continue.
With the firmware im on (v03b) you cannot use the fastboot flash method but only fastboot.
And they way it is supposed to be done is that you run
fastboot boot recovery.img (recovery being a twrp recovery for my device)
When its booted to TWRP i should be able to see it in ADB to be able to run the following commands to it:
--> adb remount
--> adb shell
--> ln -s /system/xbin/su /system/bin/su
However I cannot get it to show in ADB (or fastboot) when its booted in to TWRP.
Any ideas?
I managed to solve the last bit to.
Now it was actually a driver problem, so i just updated the driver in device manager and located the ADB driver from ZTE and it worked to boot in to TWRP and then to flash the device.
Now I have CM10 installed and is smiling!
Took me 4 days but damn it its done!
Thanks for the help!
Glad you've figured it out
1a
2a
3a
4a
5a
Hello Everyone, this is one of my first posts so go easy on me.
I used the method in this thread to flash JB onto my TF201, and now i cannot boot to recovery (get the android on his back/side with the red exclamation) and fastboot shows up as a device in device manager in windows, but when i run the "fastboot devices" command with the up to date SDK nothing is listed. ADB works, but for osme reason superuser was installed as a system process and will not uninstall, and will not issue any sort of root command to anything, including ADB. any ideas?
Hello,
Since a few years, I have root, TWRP recovery and XPOSED framework on my device.
I thought It's time to go further and try out new ROM, but to do it I need to unlock a bootloader.
Unfortunately, when I'm entering a fastboot mode (notification LED is blue) the adb "fastboot devices" command does not show anything.
I'm working on Windows 10.
What am I doing wrong?
Is a twrp somehow blocking the access? Or maybe I can do it directly from TWRP recovery.
PS. Drivers are OK, because I'm entering the fast boot mode by "adb reboot bootloader" command.
Im fairly certain its driver on the pc side.
Try it on a different pc.
Adb needs different drivers from fastboot. You havent installes fastboot drivers from the driver package.
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Have you tried with another cable or diffrent USB port?
I did but same result. Any other advice I can follow?
TSKXDA said:
I am trying to put a custom Rom on my phone but can't at the moment.
I have used adb-setup-1.4.3 for adb and fastboot.
Whenever in using "adb devices" command, it shows my device name and when I boot into bootloader it does show my device name as well when I use "fastboot devices". It lets me flash recovery but whenever I try to use adb push I get error: device '(null)' not found.
I have tried to enter recovery and to use MTP or adb sideload but my phone is not recognized there i.e. no device shown when I use "adb devices".
After many tries and and installing/ reinstalling drivers, I did a clean install on my laptop (Win 10).
Installed adb 1.4.3 <Only adb and fastboot>
Installed Xiaomi drivers using Mi Flash Tool.
Still facing the same issue.
Strangely I have Mi Mix 2 as well and it shows up in recovery under adb devices.
What am I doing wrong?
Click to expand...
Click to collapse
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
MobyDuhFreak said:
You don't need to use asb push
After u flash the recovery
Boot Into the recovery using "fastboot boot "recovery file"" and then flash the zip file from the recovery
You can flash from internal storage or sd card so it's best to put the files in the SD card and flash from there
Click to expand...
Click to collapse
If I try to fastboot into recovery I still get the same error.
TSKXDA said:
If I try to fastboot into recovery I still get the same error.
Click to expand...
Click to collapse
Is your phone a redmi 5(codename Rosy) or a redmi 5 plus or a redmi note 5 in India (codename Vince)?
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!