Related
I have a pretty big problem and need some guided help. My stock samsung usb charger sometimes charges the phone and sometimes does not. Tried multiple different chords and got the same results, sometimes works sometimes does not. So now I am assuming this is an internal hardware problem soo I decided I should flash stock images, unroot and relock the bootloader and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash stock images so I can return it to VZW....
Not sure what to do next.. any suggestions would be great...
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
mwalt2 said:
It sounds like you just don't have the drivers installed. Just install the Samsung drivers here.
Click to expand...
Click to collapse
I tried that. uninstalled the old ones (that worked for 3 months) reinstalled them again and still no luck..
Do you have any other Android processes running on your cpu? Droid Explorer or alike? Droid Ex **** blocks adb; I had a frustrating few minutes once when adb wouldn't connect to my device until I realized DE was running in the background.
Long shot, but just a thought.
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
chuckdz3 said:
and here comes the worst problem.... My device is NOT recognized when I connect it to my PC... therefor I can't access adb connection to flash
Click to expand...
Click to collapse
You mean fastboot
Melhouse said:
This is actually a common hardware error. See http://code.google.com/p/android/is...ary Stars&groupby=&sort=&id=23789#makechanges and http://forum.xda-developers.com/showthread.php?t=1427539
Basicly you need to buy a new USB charging board.
Click to expand...
Click to collapse
Yeah I believe that is what I am going to do, I just have to find the sch-i515 CDMA version because I am finding a lot of GSM versions out there right now.
bk201doesntexist said:
You mean fastboot
Click to expand...
Click to collapse
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
chuckdz3 said:
Sure. My adb command prompt does not recognize my device therefor I cannot execute any commands ei fastboot.
Click to expand...
Click to collapse
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
bk201doesntexist said:
fastboot doesnt have anything to do with adb; boot your device into bootloader
'fastboot devices'
do you see your device?
Click to expand...
Click to collapse
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
chuckdz3 said:
I am in the bootloader and don't see 'fastboot devices' or do I see my device. I see the product name, variant, bootloader version, baseband version, etc. Would that be considered 'my device' being recognized and I could actually flash the stock images?
Click to expand...
Click to collapse
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
mwalt2 said:
fastboot is like adb. You need to run it from a command line. You should have had to use it when you installed a custom recovery ('fastboot flash recovery customrecovery.img') or unlocked your phone (ie 'fastboot oem unlock'). fastboot is part of the android sdk (think it's in tools folder, but I moved mine so am not sure).
Click to expand...
Click to collapse
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
chuckdz3 said:
That's what my understanding of what it was too. I'm in the bootloader running a command prompt through windows and for the first time I think it recognized my devices. I ran 'fastboot devices' and a bunch of numbers on one line came up followed by fastboot. So I think my device is recognized and I can flash stock images?
Click to expand...
Click to collapse
yes, you can download the images for your device from google and flash them to your phone using fastboot if you want. I'm pretty sure that would put you back at stock with an unlocked bootloader.
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
bk201doesntexist said:
@op, next time read how to flash/get back to stock before flashing anything. there must be like a dozen of topics in xda about this ****.
Click to expand...
Click to collapse
I know how to. It was just your demeanor and wording/phrasing that had me confused.
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
brooklynite said:
I have the same problem, fastboot was working this morning, now after flashing Revolution HD, typing "fastboot devices" in CMD doesnt return anything anything, neither does adb push command which replies failed to copy .... As if the phone doesnt exist or its not attached. Does the phone need to be in clockwork mod? or just boot the phone normally?
Edit: This should do the trick, open CMD in Windows, navigate to your c:\android where you have fastboot and adb stored and type:
:cd %:h
adb kill-server
adb reboot bootloader
Click to expand...
Click to collapse
*facepalm*
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
mentose457 said:
Make sure USB debugging is turned on.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
*facepalm*
Melhouse said:
*facepalm*
Click to expand...
Click to collapse
Did I say something stupid?
mentose457 said:
Did I say something stupid?
Click to expand...
Click to collapse
debugging has nothing to do with it.
Windows XP absolutely HATES the samsung galaxy nexus.
The don't play along and it's almost impossible to get the drivers (especially MTP) installed correct.
Fortunately I have a W7 BEAST rig at home.. But the work XP pc can't handle the Nexus
Help! My Galaxy Nexus sudden going through BootLoop (Google logo kept coming back).
I have new born baby photos and video that I need to pull them out to my PC.
SO I read Mike 's Toolkit 7.8 and trying it.
I do not know what extract model and built is my phone. This is original phone so I bootloader is still LOCKED.
With Mike toolkit I followed up his Toolkit instuction #14.
Here is what I done.
1) In GNex TOOLKIT V7.8. I choose from 4.0.1 to 4.0.4 android build and model version (Yakju-Maguro since I am in Canada using Rogers/Fido as Carrier). Then I chose option#1 to install Nexus Window 7 drivers. This didn't work. My Window 7 did'nt regconize it.
2) During the installation of PDaNet. I hold Power On Buttom + Up Bottom (I think) Fastboot mode. I am able to get a page that shows me my "bootloader version", "Baseband version" etc...Only then PDaNet then installed Android driver successfully to my WIndow 7 Device Manager.
3) Go back to Toolkit V7.8 menu. Choose all 4.0.1 to 4.0.4 android build and model version.
I can now see my Serial Number on then top left side onw.
4) Then I chose #14 pull data from my phone.
It said the Device not found/regconized. Choose 4.0.1 to 4.0.4 android build and model
So I don't what I did wrong..
Please help..me..
I can only access to fastboot mode? Can I still files/photos pull?
Help me
Thank you very much! Your help is greatly appreciated!
step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9
Zepius said:
step 1) stop using a toolkit
step 2) http://forum.xda-developers.com/showpost.php?p=30772799&postcount=9
Click to expand...
Click to collapse
Thank you Zepius! Got few question..
My phone is in bootloop .so I can't go to android market and install Android SDK. I can't turn debugger mode on..
"assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager."
Installation of Android SDK to my window 7 pc?
Please tell me what I need to do. Much appreciated!
First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.
Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
This will not flash the custom recovery but it will boot it once. The adb command will copy your entire sdcard contents.
Sent from my Galaxy Nexus using Tapatalk 2
strumcat said:
First install 1wayjonny's drivers on your PC so it can communicate with your phone. See his thread in the dev section.
Then get adb (and fastboot) and unzip them somewhere on your PC. There's a link to a zip file containing those two commandline programs in one of efrant's threads. You don't need to install the whole SDK, just adb.
Then boot into recovery mode, since android mode bootloops.
Then follow the instructions in the link Zepius provided to use adb commands to pull your data from your phone to your PC.
Click to expand...
Click to collapse
Thank you for your help!
1wayjonny's driver is called "Universal Naked Driver 0.7"?
http://forum.xda-developers.com/showthread.php?t=1161769
Where can I find efrant's threads about adb + fastboot zip file(s)?
Sorry to keep bothering you.
Thank you!!
Petrovski80 said:
Since you can get into fastboot, I would :
- download a flashable custom recovery image such as clockworkmod
- boot into bootloader (fastboot)
- type: fastboot boot recovery nameofimage.img
- start adb
- type: adb pull /sdcard c:\somepathhere
Click to expand...
Click to collapse
Thank you!
My first and most priority is not to fix my bootloop issue but I need to get my phone photos+video backup.
So can I just make sure I get adb (Android SDK development and tools install) and adb my device?
then adb pull /sdcard c:\somepaththere?
I just want backup it first .. before I fix my phone or fastboot boot recovery nameofimage.img.
Thank you again.. I already lose some nights of sleeps because when I thought of photos that I took with my baby.
Gosh.. what a nightmare!
May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2
Duce HD2 said:
May I suggest to install either dropbox, box, Google drive and have it sync all your media, so if you ever have this happen again or worse the pics will be safe. Just saying..
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Yes. Once I get my photos and phone fix. I will.
Actually my coworker just said the same thing to me.
He has Samsung Nexus phone as well.
Thank you.
Someone please confirm me.
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
2) Install Android SDK with adb and fastboot commandline to my PC?
3) Boot my Nexus to bootloops (power buttom+volume)
4) Then connect my phone with USB and connect to my PC
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
jurassic98 said:
What is the property steps to backup my Photos+Video+ phone apps
Allow me to summarize.
Here is the steps that I understood.
1) Install Universal Naked Driver to my PC
Click to expand...
Click to collapse
Yep.
2) Install Android SDK with adb and fastboot commandline to my PC?
Click to expand...
Click to collapse
You don't need the entire SDK. You can if you want to, but unless you're planning on developing apps on Android, the SDK is overkill for just fastboot and adb. I suggest using the package efrant links to in his 101 & FAQ: http://forum.xda-developers.com/showthread.php?t=1812959
3) Boot my Nexus to bootloops (power buttom+volume)
Click to expand...
Click to collapse
Into bootloader: volume up+down+power.
4) Then connect my phone with USB and connect to my PC
Click to expand...
Click to collapse
Yes.
5) use "[GUIDE] Full Phone Backup without Unlock or Root" article from copkay
adb backup -all -f C:\backup.ab
Is this correct?
Click to expand...
Click to collapse
Almost. Adb won't work in when booted into bootloader. When you are in the bootloader, use the steps I mentioned earlier. In custom recovery, you do have the adb interface.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data? Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!
jurassic98 said:
Thank you efrant! I have been reading your article and Galaxy Nexus 101&FAQ.
My quick question is will step #6 fastboot boot recovery.img wipe all my photos/video/user data?
Click to expand...
Click to collapse
No, it won't wipe anything.
jurassic98 said:
Or this is like linux rescue disk? where you boot into a rescue environment?
Thank you again!
Click to expand...
Click to collapse
Yes, that's exactly like what it is.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
From my understanding you can't pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good
henno87 said:
From my understanding you can pass adb commands in fastboot. However if you're able to boot into recovery mode, you'll be good
Click to expand...
Click to collapse
Nope, you cannot. fastboot = fastboot, adb = adb. Different interfaces.
Try it.
efrant said:
This is what I would do:
1) Install the drivers (both for fastboot and ADB): http://forum.xda-developers.com/showthread.php?t=1379875
2) Download this to C:\Android and rename it to recovery.img: http://forum.xda-developers.com/showthread.php?t=1357642
3) Download and extract the contents of the attachment in the first post to C:\Android: http://forum.xda-developers.com/showthread.php?t=1626895
4) Open a command prompt in C:\Android
5) Turn off your phone and reboot into fastboot mode (vol up + vol down + power) and plug into PC
6) Type: fastboot boot recovery.img
7) Type: adb pull /sdcard
That will get all of your videos/photos/files/backups/etc.
As for your installed apps, you can re-install from the Play Store. For your installed apps data, you will have to use copkay's guide, but if your device is bootlooping, it may not work.
After your finished, you can read this: http://forum.xda-developers.com/showpost.php?p=29733879
Click to expand...
Click to collapse
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.
strumcat said:
Whew! efrant to the rescue. I really didn't want to look up a bunch of links.
I was just thinking that your instructions are so concise and organized that they're almost like a scripting language for "human virtual machines" that interface with Android.
Click to expand...
Click to collapse
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.
efrant said:
LOL, thanks! (Sorry, you are limited to 8 thanks per day)
The thing is, all of those links are in the 101 thread.
Click to expand...
Click to collapse
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!
jurassic98 said:
Help! me..
I run "fastboot boot recovery.img"
it says
c:\Android>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.680s]
booting...
FAILED (remote: Bootloader Locked - Use "fastboot oem unlock" to Unlock)
finished. total time: 0.690s
c:\Android>
In the bootloader , Lock state = Locked.
What do I do now? I need my photos and video.
Help me!
Click to expand...
Click to collapse
You said your bootloader was unlocked in the first post, no???
jurassic98 said:
[snip]
I do not know what extract model and built is my phone. This is original phone so I bootloader is still unlocked.
Click to expand...
Click to collapse
If your bootloader is locked, which it obviously is, you canNOT use what I had suggested. You need to try using ADB backup (use copkay's guide). However, as I mentioned before, given that you have a bootloop, it may not work...
This is a prefect example of why you should leave your bootloader unlocked -- if it was, you'd easily be able to recovery your data.
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Resolver1 said:
I'm a need of help here. I've been searching around the web and here to find the answer that for some reason I can't find. When I connect Kindle Fire 2 using a fastboot cable the device that comes up in Device Manager is otter2-prod-04. I've tried to install drivers manually using "Have a Disk" method but adb would not communicate with device (adb devices doesn't return a value). I don't know if the android_winusb.inf has to be edited (it only seems to be the case with first gen kindle) but I haven't found any guides that tell you to do it for Kindle Fire 2. Any help or proper direction is appreciated.
Click to expand...
Click to collapse
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
Hmm that did help. I should make a noob friendly guide because all of these guides are so vague when it comes to fastboot.
fast boot commands not functioning, adb works fine
onemeila said:
Have you ran a fastboot cmd? ADB and fastboot are totally separate from one another. Try running: fastboot -i 0x1949 getvar product
That will give you the product id while in fastboot.
Click to expand...
Click to collapse
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
lgweaver said:
when i issue this command all it does is sit with < waiting for device >
adb works fine, but not fastboot. fastboot devices returns nothing.
I have a factory cable that does boot it it fastboot screen.
Click to expand...
Click to collapse
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
onemeila said:
Then you have a driver issue. Get the device into fastboot and with it plugged in go to your device manager and right click the device that shows up(it will probably have a yellow triangle next to it. Then select update driver, then choose "browse my computer for device software", lastly choose "let me pick from a list of device drivers on my computer". Since you have adb working then you should have one that says "adb composite interface" or something like that. Once you install the driver you should be ok.
Click to expand...
Click to collapse
Found those steps. but that driver was already installed and said it was functioning. I risked it and attempted the root and install of jellybean without the fastboot command showing devices. apparently it works. my Kindle fire 2 is running cyanogen mod without issue now.
thanks for the response.
hello there, I'm currently using one plus 7 T, I don't know why , but after updating the last software update my device stuck in Boot loop, i can't able to turn it on, The boot reason says that : Init_user0_Failed . Unable to parse kernel log.Could you please help me to get out from this issue. As i'm outstation from the city, so i can't able to reach the service center. I need my data so i'm trusting you that you guys will sort out the issue, Thank you so much for reading this.
"fastboot set_active other" to switch slot
I'm facing the same problem. Please find a workable solution asap. I'll thank endlessly.
HueyT said:
"fastboot set_active other" to switch slot
Click to expand...
Click to collapse
How and where do I do this?
kiranlalge said:
How and where do I do this?
Click to expand...
Click to collapse
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
HueyT said:
In bootloader mode (check YouTube for how to boot into bootloader or fastboot mode for OnePlus 7t)
Click to expand...
Click to collapse
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
kiranlalge said:
"fastboot set_active other" to switch slot
It looks like the above needs to be typed in somewhere. Because I do not see any typing option on any of the screens the device shows in this situation.
Please help further. I'm not sure if the developer of the given ROM is reading my posts. I'm very hopeful on him to resolve my issue. Fingers crossed.
Click to expand...
Click to collapse
Plug phone into windows laptop with adb installed on laptop:
[Download] ADB Installer v1.4.3 - Drivers, ADB and Fastboot Tools
Install drivers, ADB and fastboot tools with one single installer.Advertisement What’s ADB Installer v1.4.3 This package includes all required drivers for Android: ADB drivers (Android Debug Bridge), Fastboot and Google USB-drivers. Very easy to install. Features: Small size. Fast installation...
xiaomifirmware.com
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Zesotar said:
Hi:
I'm with the same problem here, and i'm trying the "fastboot set_active other" command, but it returns me: "waiting for any device".
How can I proceed to make the phone recognized by the PC?
Click to expand...
Click to collapse
15 min adb fastboot drivers, OnePlus USB drivers, Qualcomm USB 9008 drivers (msmtool)
ashuetrx said:
I installed the ADB driver , now what ?? Will this erase my phone's data ?
Click to expand...
Click to collapse
Enable "USB debugging" in Dev.Options, Boot into fastboot mode on phone, type "fastboot devices" and it should give you a code--then your phone is ready for fastboot flashing files
Tried in another computer with Windows 10. It returns: "Slot change is not allowed in Lock State"
I get the a code with the fastboot devices, so it seems the phone is ready.
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Zesotar said:
Finally used MSM tool. I lost all my photoss but I recovered the phone.
Thanks for all the help!
Click to expand...
Click to collapse
how exactly did you do it with MSM tool?
cromedo7 said:
how exactly did you do it with MSM tool?
Click to expand...
Click to collapse
5 seconds with Google.
Fastboot method is much easier and without data loss.
Download
https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
Reboot to fastboot mode
Start minimal ADB and fastboot
Type: fastboot devices
If you see device and something like that:1S67gz everything's ok.
Now type: fastboot set_active other
Type reboot.
Done
I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me
And always blackscreen. Nothing show or display
Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Edit: I can see you have downloaded the Android SDK Platform-Tools on the desktop. Try to run the command under the correct path ( C:\Users\XXXX\Desktop\platform-tools_r33.0.2-windows\platform-tools>
RhapsodyK said:
Have you enabled USB debugging?
To enable USB debugging you need to enable Developer Options in your phone first. To do this: Go to Settings > About phone > Software info > and then tap the build number about 7 times.
Click to expand...
Click to collapse
How will he do this when he is in a boot loop?
CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Indeed. I have definitely lost my mind.
Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com
CRXed said:
How will he do this when he is in a boot loop?
Click to expand...
Click to collapse
Yes i have bootloader unlock. But totally blackscreen now. Any button do not work.
If ADB and Fastboot still work (and since your bootloader is unlocked), then @fil3s suggestion to use the Android Flash Tool is the best option to try.
fil3s said:
Use android flashtool. You can't downgrade on official a13 and I think you have to flash it to both slots or use flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Pc not recognize phone.
Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Guess I misunderstood. Do ADB and Fastboot still work, or don't they? If they don't, you might want to edit your OP.
Nordnord said:
Only adb devices and adb fastboot cmd work
Click to expand...
Click to collapse
Nordnord said:
Pc not recognize phone.
Click to expand...
Click to collapse
Do you have the latest drivers and Platform Tools installed? Try different cables and/or ports?
Here screenshot
Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.
Nordnord said:
Yes driver and platform toos installed. I tried different cable and port.
Abd/fastboot devices cmd works but next like adb reboot bootloader cmd not works.
Click to expand...
Click to collapse
Are you using A to C cable?
If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload
Nordnord said:
I got bootloop pixel 6 pro
Pc recognize it
Only adb devices and adb fastboot cmd work
Other cmd not work.
Can anyone help me
Click to expand...
Click to collapse
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?
Lughnasadh said:
Are you using A to C cable?
Click to expand...
Click to collapse
Yep
V0latyle said:
What were you trying to do, and at what point did this happen?
Is your phone recognized as a Android device, or is it showing up as something else?
Does holding down the Power button + Volume Down do anything?
Click to expand...
Click to collapse
Button combination not work
Not enter fastboot mode or recovery mode
fil3s said:
If fastboot devices works type
Code:
fastboot reboot bootloader
Or use adb sideload
Click to expand...
Click to collapse
Fastboot devices works
Adb reboot bootloader cmd not works
Nordnord said:
Fastboot devices works
Adb reboot bootloader cmd not works
Click to expand...
Click to collapse
Fastboot reboot bootloader cmd not works