Hello everyone
Before rooting adb was recognizing my device but after I root it no longer shows it.
It's works fine when I load CM12 but once I boot the bootloader it won't appear. I install the the necessary drives but no luck
Related
I'll try to make this brief and to the point as I realize how many people come here seeking help.
I've rooted many android devices (my first was an htc incredible) so I'm not exactly "new" per say, but don't really fully understand what I'm doing either long story short.
Got my nexus 7 today, tested some things with the screen when I first got it (just playing videos to see how bright it is)
I Followed a video suggested (somewhere) on the forums (video here (but I can't post urls))
-Sat down, got the usb drivers from here - Can't post link
-got adb fast boot tools - can't post link
-Downloaded SuperSU
-Enabled usb debugging in settings
-Booted into recovery
-Updated Driver when prompted
-allowed usb debugging after entering adb devices command
-used adb reboot bootloader command
-used fastboot oem unlock command (worked succesfully)
-used flash recovery openrecovery-twrp-2.6.0.0-flo (personally I think it didn't flash correctly because I don't know how to explain issues I will detail below
- (unless this is where I went wrong) rebooted to get into os so I could place supersu.zip on internal storage for rooting
- sticks at glowing X
ADB won't recognize the nexus 7 in recovery or bootloader
Windows only sees the nexus 7 as either
QHSUSB_DLOAD
MTP USB Device
flo
I've tried wiping from recovery, it fails.
I DO seem to be able to get adb to recognize the tablet when it is in recovery mode now.
Adb lists
06d9e78e Recovery
I've tried reflashing Twrp, still can't wipe, Is it possible for me to just install kitkat from recovry straight from adb or fastboot? It's been a while but I was thinking if I could just reset the os it might work. I have razor-krt16s-factory-7235eb0d.tgz ready to go I just don't know how to put it on the tablet without an sd card to transfer with
I have also installed Wugs Nexus Root Kit but since I have no idea what build of 4.3 my n7 is running...it really isn't doing me any good -_-.
any help would be appreciated, I'm stumped but will be continuing to dig for answers.
Thanks
I am trying to adb sideload custom rom but adb devices is not recognizing my nexus 6p. Does anyone know of a solution? I have deleted my internal storage, I have no os, am I screwed? My computer recognizes that my phone is connected, adb recognizes my phone is attached when not in recovery. The only time my phone is not attached is when in twrp recovery, when in recovery my phone shows up in device manager with an exclamation point and the message that the drivers are not installed but adb is installed.
Thank you.
blopez805 said:
I am trying to adb sideload custom rom but adb devices is not recognizing my nexus 6p. Does anyone know of a solution? I have deleted my internal storage, I have no os, am I screwed? My computer recognizes that my phone is connected, adb recognizes my phone is attached when not in recovery. The only time my phone is not attached is when in twrp recovery, when in recovery my phone shows up in device manager with an exclamation point and the message that the drivers are not installed but adb is installed.
Thank you.
Click to expand...
Click to collapse
I'm assuming you're bootloader is unlocked. If so, just flash factory images.
Sent from my Nexus 6P using Tapatalk
I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.
Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?
I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.
Hello everyone,
I've wasted my Christmas days to - unsuccessfully - re-root a Shield (16GB; 2015) after upgrading to Software 7.2.1. I need to use more than one USB mass storage device and to be able to copy from one to another, so I want to re-enable Stickmount.
The device was rooted before (which means the bootloader was already unlocked, too), and enabling USB debug, finding the device on my PC via "adb devices" was no problem, either. Issuing "adb reboot bootloader" went fine, too, the device could now be seen via "fastboot devices".
So, I flashed the TWRP image (I actually tried three different versions, 3.0.2, 3.1.1, and the most recent 3.2.3). All seemed to load fine (it spewed out two time values followed by OKAY, took about one second), but the reboot that follows only shows the NVIDIA logo forever without anything else happening (the longest I waited was 20 minutes) - according to the docs I could find (and had used before), TWRP should appear after about 15 seconds.
So, I'm stuck. I cannot get TWRP to start which prevents me from sideloading SuperSU, which means I can't use Stickmount.
Is there anything I did wrong? Is there any other way to get Stickmount installed onto my Shield? Any help is appreciated.
Cheers, Pit.
You'll need to wait until TWRP gets updated to get around the new android security measures. So keep checking TWRP website periodically to see when a new version is released.
You could have found this out if you went to Nvidia Shields Android TV forum and read some posts.
I was reading here, as well as at the nvidiashieldzone, where the tutorials are up, plus I was googling for the errors I was getting to no avail. Sorry for not finding every post on every forum on the internet, and thanks for giving the right pointer.
That means there is currently no way whatsoever to get the Shield rooted on 7.2.1., right?
Not just now, there's a guide to root 7.2 - using a developer image, and there's a chance of bricking - best to wait until TWRP is updated - also you don't need to root to use stickmount.
You only need to do something like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb shell
pm install -i "com.android.vending" -r /sdcard/Download/stickmount.apk
adb reboot
That way you can use your apk without being rooted - and your device will still be secure, and you can use widevine etc for netflix and other apps that check to see if your device is rooted.
Or you can just push the driver files stickmount uses like this:
adb reboot bootloader
fastboot boot twrp-3.2.3-0-foster.img
#in twrp - mount/system - select storage - internal storage
adb push hosts /system/etc/hosts (example file)
adb shell "chmod -R 644 /system/etc/hosts"
adb reboot
Thanks for the info - if I understand this correctly, I can install apks with root-like permissions using TWRP without rooting the whole device, right?
I will try that out once TWRP is working again.
I hope someone in here can help me with the following problem:
I had an old Android version on my X720, which I wanted to update/install LineAge custom ROM with Android 10 on. Since the old Android was acting weird and USB debugging couldnt be enabled for some reason, I decided to wipe the System/Cache on it using TWRP recovery BECAUSE the device wasnt found on Windows 7 when plugging in via USB. Previously I installed ADB drivers and everything needed, but still Windows couldnt find the device and I was unable to move the Lineage ROM (plus GApps) to the device to be able to install it via TWRP. Anyway, now there is no OS installed and I can only boot into TWRP. I tried to ADB sideload the Lineage ROM via TWRP (via connected USB to my Notebook), but after typing "adb devices" and "adb sideload path...." etc. in Windows Terminal as Admin I always get "no devices found". So, when connecting the device to my Notebook, nothing is shown and the device doesnt appear under "Device Manager" and I think that's the main problem.
Does anyone have any solution or idea? Thanks a lot in advance!
try reading this useful thread:
https://forum.xda-developers.com/le-pro3/how-to/unbrick-leeco-phones-leeco-variants-t3847220
good luck!