Hey guys,
Back May when dp3 came out, I went ahead and installed it. Now I'm stuck without a working twerp because I'm encrypted. Problem is I can get dab to work when the phone is on but cant connect to it from bootloader. I'm using the same pc from when I first rooted it...so I know that end is ok. Here's what I've done so far.....I've uninstalled all other drivers and have installed and checked with googles usb driver and clockwork mod universal drivers. I've used usbdeviw to make sure I had no conflicts there. I've tried all usb ports and different cables. I'm using win10, sdk is system wide, everything is up-to-date.
jaysway said:
Hey guys,
Back May when dp3 came out, I went ahead and installed it. Now I'm stuck without a working twerp because I'm encrypted. Problem is I can get dab to work when the phone is on but cant connect to it from bootloader. I'm using the same pc from when I first rooted it...so I know that end is ok. Here's what I've done so far.....I've uninstalled all other drivers and have installed and checked with googles usb driver and clockwork mod universal drivers. I've used usbdeviw to make sure I had no conflicts there. I've tried all usb ports and different cables. I'm using win10, sdk is system wide, everything is up-to-date.
Click to expand...
Click to collapse
One more way to confirm is by connecting your device to another PC, and check if fastboot works while your device is in bootloader mode, and adb, when your device is booted in the operating system.
DJBhardwaj said:
One more way to confirm is by connecting your device to another PC, and check if fastboot works while your device is in bootloader mode, and adb, when your device is booted in the operating system.
Click to expand...
Click to collapse
It wont work on my desktop either...same story. I have not done any of the steps i listed though either. Did all that on my laptop and no dice.
jaysway said:
It wont work on my desktop either...same story. I have not done any of the steps i listed though either. Did all that on my laptop and no dice.
Click to expand...
Click to collapse
While it is booted in the operating system, can you get it connect through MTP?
DJBhardwaj said:
While it is booted in the operating system, can you get it connect through MTP?
Click to expand...
Click to collapse
Yes
jaysway said:
Yes
Click to expand...
Click to collapse
Weird. Did you try switching to a different cable?
DJBhardwaj said:
Weird. Did you try switching to a different cable?
Click to expand...
Click to collapse
Yep....still no dice. I feel as if I've exhausted all my known options. Not sure where to go from here.
jaysway said:
Yep....still no dice. I feel as if I've exhausted all my known options. Not sure where to go from here.
Click to expand...
Click to collapse
So while in operating system, and USB debugging enabled, you cannot detect it through the "adb devices" command?
DJBhardwaj said:
So while in operating system, and USB debugging enabled, you cannot detect it through the "adb devices" command?
Click to expand...
Click to collapse
Yes I can
This is while phone is on, usb debug enabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And while in bootloader
xx
jaysway said:
This is while phone is on, usb debug enabled.
And while in bootloader
Click to expand...
Click to collapse
ADB doesn't work in the bootloader, only in recovery and booted in Android. You must use "fastboot" <command>, like "fastboot devices" while in the bootloader.
Sent from my Nexus 5X using Tapatalk
jaysway said:
This is while phone is on, usb debug enabled.
And while in bootloader
Click to expand...
Click to collapse
Mate you are doing it wrong here. ADB only operates when Android is loaded into the operating system or when sideloading. While in the bootloader, you need to operate over fastboot. So the right command command would be:
Code:
fastboot devices
Ya just realized. I'm a dumb ass.
jaysway said:
Ya just realized. I'm a dumb ass.
Click to expand...
Click to collapse
No one is. It's a phase we all have gone through. :good:
Related
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you install the samsung usb drivers on your pc?
fmf.post said:
Hello All,
I've been trying to root my device following this thread:
http://forum.xda-developers.com/showthread.php?t=1957002
However once I reboot the device pressing the volume down, I don't get the ID:COM to light up in yellow.
If I plug the device in while its on, I do get the ID:COM to light up, so I'm guessing the drivers are correctly installed.
I have no idea what to do...
The reason for using this specific method, is because its supposed to be good for beginners.
I cant seem to find much additional information about what else to do.
Honestly I'm clueless and been searching around for a while online.
Any help would be appreciated.
Click to expand...
Click to collapse
This method is easy and works .
Download Mode .
Put file to PDA in Odin .
Connect cable .
Flash .
http://forum.xda-developers.com/showthread.php?t=1831173
jje
I did...
conan1600 said:
Did you install the samsung usb drivers on your pc?
Click to expand...
Click to collapse
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Thanks All
fmf.post said:
Yes, I installed kies as per instructions.
And I see the com port and tablet detected when I plug it in without being in download mode.
Thanks for the suggestion
Click to expand...
Click to collapse
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
fmf.post said:
Ok... so guess what?
I was just being an idiot.
Instead of power and volume down, I was doing volume up.
Now it worked perfectly.
Thanks to all for comments.
Click to expand...
Click to collapse
Is this after doing the JB update your using this root?
Yes
domethiuos said:
Is this after doing the JB update your using this root?
Click to expand...
Click to collapse
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
fmf.post said:
Yes, after the update.
It works perfectly.
Really easy and straight forward.
Took about 15 seconds.
Click to expand...
Click to collapse
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
no. ..
domethiuos said:
You didnt any files specific to 4.2.1 just the ones in his zip?
Sent from my GT-N8013 using Tapatalk HD
Click to expand...
Click to collapse
The third post in that thread contains the specific files for our tablet.
Make sure you use the correct one.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The first file on the first post only contains the software needed on your pc.
Let me know if you need any more help, i was really clueless the first time.
Hi, I tried to push the 4.3 update and unroot my device through Wugfresh kit and all went well. But when it initially booted, I had this constant popup saying that "Bluetooth Share has stopped working" making the device unusable as it was stuck on the welcome screen. So, I rebooted into bootloader and tried to use the "Unroot + Stock" option saying my device had a soft brick and flash 4.2.2. But now nothing starts, it stays on the Google screen and that's it. I am however able to boot into recovery. I've checked the manual way of doing it but it says my USB debugging needs to be turned on (but I can't boot into the OS to do that)... To top it up, my computer isn't recognizing my device. I've used mskip's toolkit as well, no go. Are there any solutions or is my table gone for good?
Thanks
Oh yeah I tried again with Wugfresh it says this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to install this to use ADB in recovery.
Thanks, I've downloaded those drivers and followed the instruction for windows 8 but still adb doesn't recognize my device and I cannot boot into the device to change it to debugging mode as I cannot go past the Google screen =\ any other ways to make it recognize my device?
my brother has a nexus 7 do you guys think if I deleted all the drivers and put his into debugging mode it'll install drivers for mine too?
What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.
Username invalid said:
What you installed is needed to use ADB while in recovery. Here is the latest Android Composite ADB Interface Driver from SDK that you need for use of ADB while booted and fastboot in bootloader.
http://d-h.st/kDu
You do not need USB debugging to use ADB while in recovery or fastboot.
Click to expand...
Click to collapse
Hi, thanks again. However, I have no idea what to do with those files (the drivers) with ADB
Install or update through device manager.
I had a similar issue. My pc went to BSOD in the middle of writing system. To made it worse, fastboot stopped working altogether. My solution was to do the flashing from my Linux partiton. I know it's a crazy advice, but linux commands never fail, and you won't need drivers at all.
Still, try to use the "flash-all.bat" from the factory image, and stay away from toolkits.
When I plug in my nexus in (while in bootloader) on my device manager this pops up but then I try to update the drivers it says it can't update unknown device
You may have to disable Window's Driver Signature Enforcement.
I do not have a linux partition I'm using a windows 8 and I have 2 other PCs with win7 and xp. My windows 8 digital signature checking is disabled.
EDIT: plugging my bro's nexus did not make mine get recognized by the PC. I am installing linux on my other PC just to see if it works + i've never used linux so a new experience
running it on ubuntu 12.04 did not help either =\ while in bootloader in terminal I type in adb devices and not devices are listed under "List of devices attached"
When you are in boot loader mode you need to use fastboot instead of adb, I.e. try:
fastboot devices
(I suppose you have the latest SDK installed ...)
Sent from my Nexus 7 using xda app-developers app
Well guys, I've been doing this for about 12 hours straight lol and I'VE FINALLY DONE IT THROUGH UBUNTU OMG I LOVE UBUNTU! YES!!! Thank you all for the amazing support and advice! Much appreciated. Thank you ALL! :highfive:
It's not as if your device was bricked in the first place
Installing the drivers in Ubuntu is very easy using "sudo apt-get install android-tools".
Hi all,
I'm really desperate because my LG stuck in a boot loop and it can only get in the download mode.
I've read the thread about using fastboot command to restore to stock but my condition seems to be a little bit difference
First
i've got these command while plug my phone in
[860]fastboot mode started
[1070]-reset-
[1080]-portchange-
[1150] fastbootrocessing commands
Normally there would be a [910]udc_start() in the second line but i don't have it
Second
my command such as fastboot reboot or fastboot erase all stuck. When i unplug the usb cable it appear the too many link line like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is there any other way for me to return to stock or i can't use my phone anymore?
Note: i've tried to change the usb cable, usb port and even another computer and all of them stuck at the command line.
lordgon said:
Hi all,
I'm really desperate because my LG stuck in a boot loop and it can only get in the download mode.
I've read the thread about using fastboot command to restore to stock but my condition seems to be a little bit difference
First
i've got these command while plug my phone in
[860]fastboot mode started
[1070]-reset-
[1080]-portchange-
[1150] fastbootrocessing commands
Normally there would be a [910]udc_start() in the second line but i don't have it
Second
my command such as fastboot reboot or fastboot erase all stuck. When i unplug the usb cable it appear the too many link line like this
Is there any other way for me to return to stock or i can't use my phone anymore?
Note: i've tried to change the usb cable, usb port and even another computer and all of them stuck at the command line.
Click to expand...
Click to collapse
Try Skt tool and fix fastboot.
xmayhemreturnsx said:
Try Skt tool and fix fastboot.
Click to expand...
Click to collapse
can you be more specific about what i have to do , i really don't understand.
Guys, please help me :crying:. I feel so hopeless
lordgon said:
can you be more specific about what i have to do , i really don't understand.
Guys, please help me :crying:. I feel so hopeless
Click to expand...
Click to collapse
I'm sorry but I meant to say Srk Tool. you can find it here http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 . Once you download the tool open it up and go to fixed utility (4) and then press fix fastboot.
xmayhemreturnsx said:
I'm sorry but I meant to say Srk Tool. you can find it here http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076 . Once you download the tool open it up and go to fixed utility (4) and then press fix fastboot.
Click to expand...
Click to collapse
Thank you so much. May i asked if its worked for an lg without usb debugging ( i stuck in the bootloop so i can not enable it) and i havent rooted my device yet?
lordgon said:
Thank you so much. May i asked if its worked for an lg without usb debugging ( i stuck in the bootloop so i can not enable it) and i havent rooted my device yet?
Click to expand...
Click to collapse
It should work just fine.
Help Me Anyone Guys, I'm In Extreme Problem.
Unfortunately, I Did Something With TWRP Backups, And Then TWRP Is Not Opening, It Just Restarts, And When Connected To PC, adb Shows Device Unauthorized And Doesn't Show Any Authorisation Pop UP On Mobile. What Should I Do?
I Can't Even Factory Reset From Settings As It Makes A Reboot And Does Nothing.
Help Would Be Extremely Appreciated.
Thanks In Advance.
Reinstall drivers properly, mostly don't try in win 10, 10 is **** causes bugs, use win 7 or 8 or 8.1 also enable oem unlocking from settings and enable USB debugging
Sent from my Moto G4 Plus using Tapatalk
Krsambhav16 said:
Help Me Anyone Guys, I'm In Extreme Problem.
Unfortunately, I Did Something With TWRP Backups, And Then TWRP Is Not Opening, It Just Restarts, And When Connected To PC, adb Shows Device Unauthorized And Doesn't Show Any Authorisation Pop UP On Mobile. What Should I Do?
I Can't Even Factory Reset From Settings As It Makes A Reboot And Does Nothing.
Help Would Be Extremely Appreciated.
Thanks In Advance.
Click to expand...
Click to collapse
Need a little more details to help (Which ROM, what exactly did you do, which version of TWRP, etc)
Have you tried the 'Revoke USB Debugging Authorisation' option? It worked for me when my phone wasn't recognised.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure if it's a W10 issue as I've been doing everything with W10 since then beginning with no issues.
⌲ from my Moto G⁴ Plus / Tapatalk
1chrome said:
Need a little more details to help (Which ROM, what exactly did you do, which version of TWRP, etc)
Have you tried the 'Revoke USB Debugging Authorisation' option? It worked for me when my phone wasn't recognised.
I'm not sure if it's a W10 issue as I've been doing everything with W10 since then beginning with no issues.
⌲ from my Moto G⁴ Plus / Tapatalk
Click to expand...
Click to collapse
Hello Brother, Meeting U After Many Days.
First, I Have Moto Stock ROM, And That **** Doesn't Has Revoke Option.
Last, Yes I Was Using Windows 10 And It Detects The Device But Doesn't Gets Authorized By Phone Due To No Pop Up.
Thanks
EDIT : TWRP 3.0.2-2 r2 I Think.
EDIT 2 : I Restored My Old Backup And Unfortunately I Forgot To Wipe Partitions And Then Got This Problem.
I am not what exactly went wrong. Boot into fastboot mode and If you're PC is detecting fastboot, try booting into TWRP using an image and see if you can restore a backup.
Or if you have your personal files backed up, just flash the Stock Nougat ROM via fastboot.
That will clear up everything. Or if you want a more flexible ROM, just go for a custom one
⌲ from my Moto G⁴ Plus / Tapatalk
1chrome said:
I am not what exactly went wrong. Boot into fastboot mode and If you're PC is detecting fastboot, try booting into TWRP using an image and see if you can restore a backup.
Or if you have your personal files backed up, just flash the Stock Nougat ROM via fastboot.
That will clear up everything. Or if you want a more flexible ROM, just go for a custom one
⌲ from my Moto G⁴ Plus / Tapatalk
Click to expand...
Click to collapse
But adb Is Showing Unauthorized So How Do I Use Fastboot?
Krsambhav16 said:
But adb Is Showing Unauthorized So How Do I Use Fastboot?
Click to expand...
Click to collapse
Did you tried other computer/laptop, or change the port you are using, try to change the data cable as these are the basic steps we do in these cases.
If problem continue persist try to use the Windows 7 for flashing via abd, also try to boot into safe mode and then try the adb may help you.
avirk said:
Did you tried other computer/laptop, or change the port you are using, try to change the data cable as these are the basic steps we do in these cases.
If problem continue persist try to use the Windows 7 for flashing via abd, also try to boot into safe mode and then try the adb may help you.
Click to expand...
Click to collapse
OK I Will Try On Friends pc. Thanks
I have not touched this phone in a year, so forgive me if im rusty.
I embarked on a project of compiling slimroms 7.1.2 for this device a year ago, and made a rom that made it onto the device. Now, Here is my mistake. At the time when i built the rom, the nougat bootloader for this device was not out yet(i think, as my bootloader is on a0.4d aka dated 2016-11-30) Giddy that i had finally built a custom rom that worked, i hurriedly flashed the device through the recovery(twrp at the time) and thats when the issues happened. The device will not charge past 1 percent, and in an effort to fix, without knowing that my outdated bootloader was the issue, i decided that installing stock recovery was the best option. BIG MISTAKE. as i now cannot flash anything in recovery. i keep getting signature verification failures and what not.
With that backstory out of the way, here is my issue. I cannot flash anything in fastboot, because when i connect the device to windows i get
Code:
Windows has stopped this device because it has reported problems. (Code 43)
A request for the USB device descriptor failed.
Yes i have updated the drivers and when i install the motorola drivers manually i get this:
Code:
This device cannot start. (Code 10)
A request for the USB device descriptor failed.
this is the single most thing that is keeping me from reviving this device. I have tried using linux, but the device just doesnt show up. I have tried multiple usb cables. so i know thats not the issue. any help would be very appreciated.
UPDATE: i have done some digging around and no loader files are working. (using a 32gig class 10 microsd). Also, It is on stock recovery so i cannot flash anything other than stock images, which if i am correct, none are recovery flashable, only the otas are. When i try to flash an ota it doesnt work because it is expecting stock apps in system, which are not there since i am on a slimrom rom.
TLDR: i have stock bootloader and recovery, (24.49-18-8/4) but have a non rooted slimrom 7.1.2 which shows up in windows as get device descriptor failed(unknown device). if there was a way to root slimrom 7.1 without usb and with stock recovery that would help alot.
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
mr_5kool said:
Have you tried the method to revive the phone in Qualcom mode (error 9008)?
Click to expand...
Click to collapse
Can you link me to a thread that has that info please?
When I am in bootloader and hit the power button on the qcom option my phone just boots into the slimroms option with no change in the USB side
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
mr_5kool said:
Here you are
https://forum.xda-developers.com/moto-x-style/help/solved-hard-brick-moto-x-style-xt1572-t3693860
Click to expand...
Click to collapse
So my issue is worse than that. It shows up on the computer as "device descriptor get failed" so I am unableble to use that method unless I can force it into qdloader mode
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
When i try to install this driver, it says that it is incompatable for my device
I will try again when i get home tomorrow though
mr_5kool said:
Here is the Qualcom driver if you don't have
https://drive.google.com/folderview?id=0Bx2X76GhQpwDVXg5ZXZYNFo0MzA
Click to expand...
Click to collapse
Alright, When i try to install this driver i get this
View attachment 4594365
And this is the error i have on any machine
View attachment 4594369
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
mr_5kool said:
I don't know what happened to your PC. But it is successfully installed here. The worst problem we (mosy of us) had met was error 9008. If your phone cannot be solved by this way, I'm sorry that I can't help much!
Click to expand...
Click to collapse
its quite alright. i think that i bricked the phone while trying to use an unsupported bootloader, therefore bricking the mainboard
Its noones fault but my own, so i will chalk this one up to a loss lol