hi
While working with the device, it reset without prior warning, and since it trying to start and when the Google logo disappears and the animation stage arrives, 3 seconds later it turns himself off.
I entered into the Recovery mode and cleaned Cash - did not help
I thought to take out the battery in case something might be stuck in my memory but I still have not done it because when I dismantled the small panel (on the part of the camera) I accidentally turned on the device and it showed me that it upgrades the apps, which was a good sign for me so I closed the panel and waited for it to finish The 147 applications. At the end he turned himself off
I did not proceed with the matter of dismantling the battery.
I have the default recovery, I did not install recovery applications that expand the possibilities in the recovery mode.
and i don't remember if i turned on the USB debugging.
I decided to transfer the files (pic's, whtsapp) by ADB befor i try the factory reset
but I get sideload instead of recovery
C: \ adb> adb devices
List of devices attached
R ********** sideload (I changed the stereo to asterisks)
and every command I try to run I get
error: closed
Does anyone have an idea of how to copy files or repair the system ?
thanks
You should be able to bring it to fastboot mode by powering it off, then holding Power, Volume up an Volume down until the robot appears.
From there you should see the device with "fastboot devices". You might need to install some drivers at that point.
When in fastboot you should be able to start TWRP with "fastboot boot twrp-3.1.1-0-manta.img". When in TWRP you can see /sdcard in Windows or you can start Advanced > File Manager and copy your data to a USB stick.
thanks bornheim2
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night
so my guess is that my battery is bad.
can i use usb a male to usb a male adapter
or Hittime smart 3 in 1 Micro USB OTG/Sync/Charging cable
( i can't put links )
to connect the device with OTG to the computer for power and for transfer data to the computer ?
thanks
[email protected] said:
i succeeded to load the TWRP
but when i unplug the USB for plugin the OTG the screen start blinking and the devices turned off.
i have charge the device all night so my guess is that my battery is bad.
Click to expand...
Click to collapse
You should see the device in Windows when TWRP is running (and the device is charged by the PC). That should be enough to save your files.
i don't see it on windows (computer)
[email protected] said:
i don't see it on windows (computer)
Click to expand...
Click to collapse
That might be a driver problem. Do you see it in Device Manager on Windows? Probably with a yellow triangle?
it's good in the devices manager "Android Bootloader Interface"
but after the TWRP it upload, the devices no longer appears in the device manager
and the screen is still blinking
when i run the "fastboot boot twrp-3.1.1-0-manta.img"
it turn in the device manager to "Android ADB recovery interface" and after 1 sec is disconnect
Related
So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
ldunn said:
So, last night I decided to install ali ba's CM 7 build. After a few false starts, I ended up with a boot loop. Since then I reverted with fastboot using a LEGEIMG.zip, and I can't mount my microSD card via my phone anymore. USB Debugging is all but gone, I can access it for maybe a minute and then it dies.
To be clear, the icon on my phone indicating that USB Debugging is active, but `adb devices` stops showing it after a minute or so.
When I plug in the phone, Windows tells me "USB Device Not Recognised". I've tried removing and re-installing HTC Sync.
I'm lost for where to go right now, suggestions?
Thanks
Click to expand...
Click to collapse
I had the same problem. I'm not sure how to get ADB back, but I can help you with the MicroSD mount problem. Go into Fastboot on your phone, with it plugged into your computer. In the cmd prompt navigate to the folder where adb devices is and type fastboot oem enableqxdm 0
Let me know if you figure out the adb bit. I'm still trying to fix it.
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p.
this situation is the same when I connect the phone when it is alive.
I have installed adb and fastboot with this software
https://forum.xda-developers.com/showthread.php?t=2588979
with the 1.4.3 version it shows in the end of the process "0 files copied" and then I tried the 1.3 version and it showed that 4 files were copied but it also showed an error.
I have also downloaded ADB from google site but it does not work either.
When I try to open the powershell in a folder where I have downloaded an img and type in a fastboot command the computer doens't recognize any type of command.
So if anyone can help me ill be glad.
Thanks in advance,
Matan.
matan4442 said:
Hi everybody,
ill try to make it short:
My 6p has entered into the bootlooping mode.
I have never unlocked the bootloader/changed ROM/kernal.
After I let it bootloop until the battery is dead it's changing from bootlooping into blinking red dot. Then when I charge it for a couple of minutes it comes back to life after 10~ min it's bootlooping again - so I have a window of possibilities to play with the setting. In that window I have used the "OEM unlocking" option.
In the bootlooping state when I boot into the bootloader and connect it into the PC the device doesn't recognize that it has been connected and a PC ,and the PC recognize a entry of new device but doesn't recognize it is a Nexus 6p. Matan.
Click to expand...
Click to collapse
What is the new device identified as....Qualcomm HS-USB QDLoader 9008? Your phone may be stuck in EDL mode. If that is the case you need to search XDA and attempt solutions for that problem first.
Did you previously have your PC setup properly with the correct USB drivers and it was working OK, or just now trying to get your dead phone to communicate? If the former it may be the EDL issue above. If it was the latter, the communication problem may just be the drivers were never set up in the first place. Have you tried a different cable or port on your PC, or another PC?
With no access to the OS you will be unable unlock the bootloader or access to ADB because those have to be enabled FIRST in the OS, so there's no helping you here until you can actually boot into the OS. Do you have access to Recovery mode? Tried a factory reset? If you don't have recovery, that was a major omission.
Messing around with my Z3 compact, which was already rooted and I'm sure the bootloader was already unlocked when I first rooted it. Anyways I tried to install Magisk for testing purposes, now I have a non-functional phone. Now I can't boot into recovery mode (I had TWRP) or into the regular mode.
I can boot into fastboot mode (plug in USB + hold Power & Volume UP --> 3 Vibrations --> Blue LED Notification). I checked using flashtoolx64 and it does detect the phone is in fastboot mode.
However when i try to flash the stock firmware, where I have to restart the phone in flashmode (Power off --> hold Volume Down --> Plug in USB), Windows says there is an error recognizing the device. and when I check device manager, it says the USB Device entry is: Unknown USB Device (Configuration Descriptor Request Failed). Could this be a driver issue?
I couldn't find any other solutions for restoring the system without going into flashmode, because it looks like i can't even get that working. I would appreciate any solutions that utilize fastboot mode, since that is the only mode I can get into with the computer recognizing it.
-Edit 1-
Silly me, it turns out I was able to get into flashmode afterall (Power Off > Volume Down > Plug in USB).
After double checking and re-installing the Sony Xperia USB drivers, I thought the phone was done. I tried plugging in the phone using the back USB ports instead of the front and voila flashtools can push the stock firmware. My guess is that the "Configuration Descriptor Request" error I saw in the Device Manager was because I was using the front USB ports on my PC.
-Edit 2-
Apologies, clicked on the wrong forum when it should have been posted in the troubleshooting forum. This thread can be closed/deleted since I figured out what's wrong (see edit 1)
I try update my nvidia shield tv 2017 but now the System bootloop on Android circles animation (dont start box).
- I try fastboot with Controller but dont work (many, many times)
- I try conect to pc but dont connect device with fastboot
bricked bootloader??
I dont have solutions.... please help.
Sorry my english
Try un plugging the power then plug a USB keyboard in and hold the A and B key and then plug the power back in.
same problem for 3 days, can not enter fastboot mode. my shield is in bootloop
Shot in the dark, but have you tried different USB ports on the computer? I know in my case, some otherwise working ports will not work with the shield. Seems to be very fussy when it comes to which ports I choose. None of my front ports work on this desktop, I have to plug into rear ports in order for my computer and shield to see each other.
Also be sure to use the original cable that came with the shield.
Also make sure USB debugging is on.
Any fix ? Same problem
Have you tried "adb reboot bootloader" in command prompt when the android logo is looping?
I have no Android logo i have no os just twrp and twrp with no access adb and fastboot command dont work on NVIDIA logo
If you put lineage os on a usb stick can twrp read the usb stick? If so, you can install the zip file of lineage with gapps...once that's installed and booted up, you can enable usb debugging in the developers options and fastboot and adb should work again.