Related
I've literally tried every method on the internet to root the GSM Galaxy Nexus and I keep getting stuck at the very beginning: I can't get past the driver step and making sure the computer recognizes the phone as an ADB device. I've tried Samsung driver install, pdaNET drivers and just about any other method and I still can't get my computer to show that the device is a ADB device and therefore cannot root the phone.
Its a Play Store Galaxy Nexus running 4.0.4
all help is incredibly appreciated. I've been working on this problem since Friday.
I'm on a 64bit Windows 7 on a Dell XPS 15 computer
Jubakuba said:
If your Command Prompt displays the message "waiting for device" your driver wasn't successfully installed.
Close the Command Prompt window and open Device manager while your phone is still plugged in. (Search for it using the search option).
Right Click the "Android" option and select Update Driver. Choose to "Browse My Computer" and "Let Me Pick From A List." Pick the Samsung driver with the newest date and install it. Now retry the code above.
Click to expand...
Click to collapse
Try this.
I've tried updating via device manager. The problem is, it always says its up to date or when I manually select one it still doesn't work. Should I just not pick the newest driver? Pick an older version when selecting a new driver?
EDIT: also, another issue is that with Wug's when it searches for the adb device is searches in an odd folder that doesn't exist and I can't figure out how to change where it looks
Sent from my Galaxy Nexus using xda app-developers app
Or download the GNex Toolkit. Was having driver issues as well today (they were installed but for some strange reason Windows didn't recognize it anymore) and used the ones that come with this toolkit to reinstall through device manager. Of course as always with these things, use at your own risk, fiddling with drivers can be tricky .
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Cilraaz said:
What are you getting from your adb devices command? I had a problem with mine showing as consistantly offline. I had to change from a frontal USB port (usually a bad idea anyway) to a rear port. Some device/computer combinations make adb unhappy when using a USB hub, which most frontal USB ports essentially are.
Click to expand...
Click to collapse
When I use WugFresh and check for ADB it checks a nonexistent directory and returns an error. I found another method on google (I think the webpage was Foolproof method or something) and I check through command prompt and when I do it says List of Devices: then a blank line underneath
EDIT: just installed the GNex toolkit and drivers, plugged in, adb devices and it returned the blank line
EDIT 2.0: I just witnessed the most beautiful thing in the world. I plugged in again and it miraculously worked. I think I might tear up and cry a little
Yeah, for some reason the USB Driver in the Android SDK does NOT work. This was incredibly frustrating when I was trying to unlock my phone originally. I spent probably 30 minutes googling and trying different driver downloads.
I have attached the ones I used that DO work.
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Gunthy` said:
I've never rooted an already installed ROM for the Galaxy Nexus, but might I ask why you're not just installing a pre-rooted ROM from recovery? It'll save you a lot of headaches for sure. Even if you're not into custom builds, there's plenty of AOSP pre-rooted builds out there
Click to expand...
Click to collapse
I don't think the pre-rooted ROMs get OTAs, or do they? I've been trying to root on stock so I can still get OTAs and I like how stable it is. I've messed with other ROMs on other phones and I almost always go to stock or CM but I'd rather stick to stock on this for now
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
i actually delete any driver and use the pdanet works just fine, i had the same problem that you. is just mather of patience.
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Gunthy` said:
Okay I can understand that. However do realize that once you install an OTA, your root will probably be gone and you'll have to root manually once more ...
Click to expand...
Click to collapse
Maybe not. SuperSU has a feature to keep root when installing an OTA.
The 4th Derivative said:
Yea re-rooting is fine. I really only need root for a few days to get my phone set up but K really don't need root privileges in everyday use so losing root once I've done what I need is ok
Click to expand...
Click to collapse
Man.. as easy as this:
Go to bixie's jb rom thread, he has there linked a supersu+busybox cwm flashable zip, dl that and copy it to the device. Dl also a non-touch cwm image.
Unlock your bootloader, bla bla follow guides on how to set up/use fastboot, BOOT cwm (not flash it) with 'fastboot boot cwm.img', flash that supersu zip, reboot. Done, you rooted jb, install voodoo root keeper or something, back up root. Thats one way how to root a Nexus. You can even relock your bootloader after you finished customizing.
Sent from my i9250
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
The 4th Derivative said:
Sorry guys, forgot to post last night. I finally got root. Thanks to all who helped! You all made my life so much easier
Click to expand...
Click to collapse
hey, i have the same problem as you do on updating the usb driver. mind telling me how you do it? thanks!
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
The 4th Derivative said:
I put it in a different USB port (my sata+ if it matters) and found a method online. I cant remember where on mobile but I'll look it up once I'm home
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
its okay already. i have found the solution. thanks
The 4th Derivative said:
So here is the new story:
unlocked bootloader but it did not factory reset. It rebooted and my phone is as it was.
When I went to do fastboot boot boot.gsm.img, It says boot.img downloads and then it takes me to the google logo screen and gets stuck
Click to expand...
Click to collapse
EDIT
I currently rooted using the latest version of the Sons of Android ROM. Last night I made a back-up of it and flashed the Synergy ROM to test it for a friend. When I restored my back-up, I could no longer connect to the computer. I tried to reinstall the drivers through Kies and also direct from Samsung. The phone charges when connect to the USB port, but does not connect. I have tried two computer so I think it is the phone.
I search the forums and didnt find anything that help.
Does anyone have any suggestions?
Thank you!
Huskerjeff said:
I currently rooted using the latest version of the Sons of Android ROM. Last night I made a back-up of it and flashed the Synergy ROM to test it for a friend. When I restored my back-up, I could no longer connect to the computer. I tried to reinstall the drivers through Kies and also direct from Samsung. The phone charges when connect to the USB port, but does not connect. I have tried two computer so I think it is the phone.
I search the forums and didnt find anything that help.
Does anyone have any suggestions?
Thank you!
Click to expand...
Click to collapse
Make sure fast charge isn't selected.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
KorGuy123 said:
Make sure fast charge isn't selected.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I can not find any fast charge setting. I am starting to worry that I might have damaged the phone. I hope I just need to re-flash a driver or something.
Thank you!
make sure you're using the factory cable for the device.
try another USB port, preferably a port directly connected to the computers motherboard.
delete the current USB drivers for your phone on the computer. reboot it. in task manager, stop any kies background processes. reinstall drivers. reboot and see if that takes.
Huskerjeff said:
I currently rooted using the latest version of the Sons of Android ROM. Last night I made a back-up of it and flashed the Synergy ROM to test it for a friend. When I restored my back-up, I could no longer connect to the computer. I tried to reinstall the drivers through Kies and also direct from Samsung. The phone charges when connect to the USB port, but does not connect. I have tried two computer so I think it is the phone.
I search the forums and didnt find anything that help.
Does anyone have any suggestions?
Thank you!
Click to expand...
Click to collapse
Did you make a nandroid of the previous rom ? Flash back to that . Flashing any rom made for the NA version of the Galaxy s3 will NOT brick your phone. NO physical damage will happen in any way.
Yes check the cord to make sure its not that....samsung phones are picky....even with the same cord.
Fast charge is usually in the kernel settings menu. It will be something you would had to enable, I've never seen it come enabled on a rom. What kernel are you on ? I don't think you see that setting on TW based rom's anyway ( I assume you are on SoA right now?)
Have you tried to do a complete wipe and flash another rom ?
hednik said:
Did you make a nandroid of the previous rom ? Flash back to that . Flashing any rom made for the NA version of the Galaxy s3 will NOT brick your phone. NO physical damage will happen in any way.
Yes check the cord to make sure its not that....samsung phones are picky....even with the same cord.
Fast charge is usually in the kernel settings menu. It will be something you would had to enable, I've never seen it come enabled on a rom. What kernel are you on ? I don't think you see that setting on TW based rom's anyway ( I assume you are on SoA right now?)
Have you tried to do a complete wipe and flash another rom ?
Click to expand...
Click to collapse
I have a nandroid of my stock (after rooted) ROM, but it is on my computer now, not on the phone so I cant access it. I also had a nandroid of Sons of Android that was connecting just fine before I flashed Synergy ROM. I restored the Sons of Android ROM (nandroid) that was still on my external SD card and that didnt fix it.
I just did a complete wipe (Cache, Davlik Cache, System, Factory Reset, and Internal Memory), then installed the Wicked ROM with the stock kernel. It still doesnt work.
I tried two different cord on two different computers with no luck.
Thank you!
Is your usb debugging enabled?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Huskerjeff said:
I have a nandroid of my stock (after rooted) ROM, but it is on my computer now, not on the phone so I cant access it. I also had a nandroid of Sons of Android that was connecting just fine before I flashed Synergy ROM. I restored the Sons of Android ROM (nandroid) that was still on my external SD card and that didnt fix it.
I just did a complete wipe (Cache, Davlik Cache, System, Factory Reset, and Internal Memory), then installed the Wicked ROM with the stock kernel. It still doesnt work.
I tried two different cord on two different computers with no luck.
Thank you!
Click to expand...
Click to collapse
Completely remove the drivers on your PC and reinstall again. Also if you have kies remove that first.
Sent from my SAMSUNG-SGH-I747 using xda premium
Domoo said:
Is your usb debugging enabled?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
USB Debugging is currently enabled, but I have tried it both ways.
I also am noticing my data connection is really, really slow, much slower than normal. I looked under the Synergy ROM and there was some talk of needing to reflash modem and bluetooth when reverting to a stock kernel. Could this be the problem?
Thanks!
You could try mobile Odin and flash the rooted stock that way... Its a shot
You have to use a .tar file though
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
You could try mobile Odin and flash the rooted stock that way... Its a shot
You have to use a .tar file though
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Can you you give me some more info on Mobile Odin? I have never heard of it.
Last night I flashed the KT747 kernel because it has updated USB drivers, but it still didnt work.
I still have to believe that something went wrong when flashing the other night because that is when it stop work, but I am starting to think it is a hardware issue. It is very wierd!
Thank you!
Do you get any error when plugging it? I had a similar issue last week until I updated Windows.
BWolf56 said:
Do you get any error when plugging it? I had a similar issue last week until I updated Windows.
Click to expand...
Click to collapse
Nope, no error message. It just doesnt reconize it is there. I have tried three computers (Windows 7 - 64 Bit & (2) XP 32 Bit) and three different cords.
This sucks! Now I am hearting it from all the iPhone users.
Thanks!
Huskerjeff said:
Can you you give me some more info on Mobile Odin? I have never heard of it.
Last night I flashed the KT747 kernel because it has updated USB drivers, but it still didnt work.
I still have to believe that something went wrong when flashing the other night because that is when it stop work, but I am starting to think it is a hardware issue. It is very wierd!
Thank you!
Click to expand...
Click to collapse
Try this, same thing was happening to me on a rooted stock rom. The steps listed here helped me reconnect phone to PC.
http://blog.vacs.fr/index.php?post/...ot-detected-problem-on-Android-Samsung-phones
Huskerjeff said:
Nope, no error message. It just doesnt reconize it is there. I have tried three computers (Windows 7 - 64 Bit & (2) XP 32 Bit) and three different cords.
This sucks! Now I am hearting it from all the iPhone users.
Thanks!
Click to expand...
Click to collapse
Try wiping and flashing another ROM?
dratsablive said:
Try this, same thing was happening to me on a rooted stock rom. The steps listed here helped me reconnect phone to PC.
http://blog.vacs.fr/index.php?post/...ot-detected-problem-on-Android-Samsung-phones
Click to expand...
Click to collapse
I hope we are getting closer!
When is use the *#7284#, I get the UART section that is on PDA and I cant change it.
Under the USB section I have button that says "Qualcomm USB Settings" with a whole punch of options:
MTP
MTP + ADB
PTP
PTO + ADB
RNIS + DM + MODEM
RMNET + DM + MODEM
DM + MODEM + ADB
Should I use one of these settings?
Thank you!
Huskerjeff said:
I hope we are getting closer!
When is use the *#7284#, I get the UART section that is on PDA and I cant change it.
Under the USB section I have button that says "Qualcomm USB Settings" with a whole punch of options:
MTP
MTP + ADB
PTP
PTO + ADB
RNIS + DM + MODEM
RMNET + DM + MODEM
DM + MODEM + ADB
Should I use one of these settings?
Thank you!
Click to expand...
Click to collapse
You should have two options, MODEM and PDA. Mine is set to MODEM.
Still no luck! Very Frustrating!
I used Mobile Odin to flash back completely to stock, and the usb still would not connect. I do not know what else to do. I will have to remove the SD Card and use a card reader for now. I can flash back to stock when if I want to take it in and get it fixed or replaced.
Huskerjeff said:
Still no luck! Very Frustrating!
I used Mobile Odin to flash back completely to stock, and the usb still would not connect. I do not know what else to do. I will have to remove the SD Card and use a card reader for now. I can flash back to stock when if I want to take it in and get it fixed or replaced.
Click to expand...
Click to collapse
did u already try another cable, I had over 5 cables that suddenly stopped working for no reason, only charges but it doesn't connect to the pc..
so try another cable is my suggestion.
I need some help because I am puzzled on what to do. The other night, I tried to change roms on my Pixel XL. I'm used to being able to just flash everything once in whatever order and be fine (it was much simpler years ago when I got started with modding).
Anyways, I flashed FireHound rom and gapps, but forgot the vendor. I flashed twrp and that put me into a bootloop. It would reboot back into recovery each time. So I reflashed Pixel Dust, the rom I was on before, since I didn't have a backup. I forgot to make one. Lol.
Flashed the vendor, rom, and twrp. Rebooted to a clean rom. However, I'm not rooted. I attempt to go back to twrp - and I can't. It goes straight to Android recovery/ no command screen. I can't get back into twrp.
Since this, I downloaded the newest factory image so I could just reflash and start over and fix it. But I cannot connect to any computer. I've tried multiple cables, multiple computers, and each time I get a "USB device not recognized" error. Device manager shows my device as "Unknown USB device (device descriptor request failed)." I've attempted to reinstall/update the USB drivers, windows won't update it because it says it's already up to date. Windows 10 is what I'm using.
So I am stuck. Can anyone help me? Or did I completely screw everything up?
Thanks in advance,
Sam
Enable USB debugging in Developer Options.
Sent from my Pixel C using Tapatalk
Thanks, I tried that. Still nothing different.
Do you get any response on the phone when in bootloader and USB cable is plugged in?
Have you checked to make sure that your adb/fastboot programs are at the latest revision?
Sent from my Pixel C using Tapatalk
pkelly517 said:
Do you get any response on the phone when in bootloader and USB cable is plugged in?
Have you checked to make sure that your adb/fastboot programs are at the latest revision?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
I've updated the adb/fastboot versions from the sdk. I've updated the USB drivers. Or attempted to. And I get no response from the phone when in any mode.
Got any friends with a Linux machine? It's been ages since I used Windows to talk to my phone. I'll plug it in when I get home, though, to see if my phone is recognized.
Sent from my Pixel C using Tapatalk
pkelly517 said:
Got any friends with a Linux machine? It's been ages since I used Windows to talk to my phone. I'll plug it in when I get home, though, to see if my phone is recognized.
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No I don't. But I suppose I could set up a Linux virtual machine and try it that way. It's been a while since I've used Linux. You think it could work?
droidian1441 said:
You think it could work?
Click to expand...
Click to collapse
Yes
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb)
droidian1441 said:
You think it could work?
Click to expand...
Click to collapse
I'm not sure. I think a virtual box would still use the windows drivers. Good luck.
Sent from my Pixel XL using Tapatalk
droidian1441 said:
No I don't. But I suppose I could set up a Linux virtual machine and try it that way. It's been a while since I've used Linux. You think it could work?
Click to expand...
Click to collapse
DR3W5K1 said:
Yes
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb)
Click to expand...
Click to collapse
I was referring to Linux not a virtual machine. Sorry if I confused you.
DR3W5K1 said:
I was referring to Linux not a virtual machine. Sorry if I confused you.
Click to expand...
Click to collapse
No problem. Going to give Ubuntu alongside windows a shot. See if it works. Thanks for the idea!
hello did you find any solution >??
droidian1441 said:
I need some help because I am puzzled on what to do. The other night, I tried to change roms on my Pixel XL. I'm used to being able to just flash everything once in whatever order and be fine (it was much simpler years ago when I got started with modding).
Anyways, I flashed FireHound rom and gapps, but forgot the vendor. I flashed twrp and that put me into a bootloop. It would reboot back into recovery each time. So I reflashed Pixel Dust, the rom I was on before, since I didn't have a backup. I forgot to make one. Lol.
Flashed the vendor, rom, and twrp. Rebooted to a clean rom. However, I'm not rooted. I attempt to go back to twrp - and I can't. It goes straight to Android recovery/ no command screen. I can't get back into twrp.
Since this, I downloaded the newest factory image so I could just reflash and start over and fix it. But I cannot connect to any computer. I've tried multiple cables, multiple computers, and each time I get a "USB device not recognized" error. Device manager shows my device as "Unknown USB device (device descriptor request failed)." I've attempted to reinstall/update the USB drivers, windows won't update it because it says it's already up to date. Windows 10 is what I'm using.
So I am stuck. Can anyone help me? Or did I completely screw everything up?
Thanks in advance,
Sam
Click to expand...
Click to collapse
@Siddhantroyal
Did you try this solution: https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
Cheers...
5.1 said:
@Siddhantroyal
Did you try this solution: https://forum.xda-developers.com/pixel-xl/how-to/guide-fix-mtp-driver-windows-10-t3570625
Cheers...
Click to expand...
Click to collapse
hello thanks for responding.the issue is a little bit different with my phone.it is showing up as a usb device and not as a mobile/unknown device
Hey guys.
Yesterday, I swapped out my Oneplus 6T, and got a new Pixel 3 XL 64GB.
I managed to have no issues unlocking the bootloader, and I do have relative familiarity with adb tools.
I'm running a Dell XPS 13 which has a USB Type C port which I have been using for cmd through Windows 10 in the beginning much to my own success.
After unlocking the bootloader, I had opt'd in for the ota update for Android Q and downloaded without hesitation.
I booted into TWRP, and when attempting to flash through the USB OTG cable it failed. I do not recall, and didn't think to use the webcam on my PC at the time to screenshot the errors.
I can get into the bootloader, however now when I run adb devices nothing appears.
If I boot a TWRP img, go to advanced > adb sideload and run a session. I can then proceed to run adb devices and successfully it reports back my serial number of the device. ( can provide screenshots of this if it's of any assistance )
However, no way have I been able to flash the Factory images, from as early as September 2018 to the latest for Android 9.0, nor have I have been able to reflash the Android Q factory images using cmd and the flash-all.bat
I've also followed this guide step by step uninstalling every ADB and Android related driver prior to installing the "lastest google drivers" https://forum.xda-developers.com/pixel-3-xl/how-to/guide-progress-available-t3876849/page6
Sending sparse 'vendor_a' 2/2 (193888 KB) FAILED (Error reading sparse file) is where it hangs, and I'm absolutely at a stand still I wouldn't be posting if I hadn't searched and tried everything I could find any way related to it.
Also seems to be missing multiple sig files when running the flash-all.
If anyone can be of assistance it would be greatly appreciated I do not want to have to RMA to Google.
Thanks guys!
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
hatdrc said:
You can not adb sideload an ota in TWRP. It has to be the factory recovery.
When you are in the bootloader you need to do fastboot devices to see your device.
Did you get Q running? If you did I would download the factory image for it and edit the flash-all.bat to remove the -w.
Also make sure you have the latest platform-tools. I think they got updated when Q came out.
I've never had a problem but I know a lot of people have problems with C to C cables. May want to try an A to C cable if you can.
Click to expand...
Click to collapse
Sadly, I can't get to a USB A to C cable for 6 more days.
I did manage to get to Q, and I don't know what rushed me to thinking I could be flashing twrp on the beta.
I have been using factory images, I haven't sideloaded with adb, as I can't quite seem to figure out the flashing process for TWRP. Is there a method you could recommend we try?
I have the latest tools, and I'm 99.9% positive in one of the 20+ flashes I tried Today of various factory images, flashing the last factory with Q did not solve the trick with or without the -w.
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
As the other user has mentioned, I may be at a loss at being able to flash with TWRP after installing Q.
Gordietm said:
I think your using an old android Windows platform tools.
The newest version is r28.0.2, that should fix your problem.
Also in android Q with the pixel 3 xl, you can't flash anything with TWRP, the storage is not mounted.
Click to expand...
Click to collapse
Could you give me a detailed step by step, perhaps with the url's for the drivers & SDK tools.
I've used the links provided in the Soft Brick guide, and got the drivers direct from google themselves.
Although when I currently plug in my phone, it does install "Lemobile Android Drivers", the Google Drivers remove this but appear to be older drivers?
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Eudeferrer said:
If you are trying to flash from within TWRP, make sure everything is properly mounted.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Gordietm said:
Download from here the latest platform tools, then flash all the factory image.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Okay will do, please confirm if this is correct.
Extra Android platform-tools, and factory image to the same folder, then extract the zip file found within the folder itself with the zip found from the Factory Image
I erase system a & b, and boot a & b
Flash-All should work start to finish right?
What are the odd's I'm going to be stuck with a RMA?
I'm sure I've exhausted myself trying this exact process so many times yesterday.
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
This sounds identical to what I've be doing, which has been causing the vendor_a issue, but I will give it another run for you shortly here. Just woke up, and rather be fully awake before I go tackling this.
If you can think of any other method, or even an explanation why the vendor img doesn't seem to work that would be awesome.
Also, there is threads I found through google here on XDA with users have a similar issue hanging at vendor, but not due to the same mistake. I'll find you the URL's shortly here.
It's because you were using r28.0.1 before, download r28.0.2
Gordietm said:
Download platform tools, vr28.0.2
Extract it and put the contents in a folder you'll remember
Download the factory image and extract it.
Put the bootloader, radio, system image zip and flash all.bat files in the same folder as the platform tools.
Connect your phone and put in bootloader mode.
Double click flash all.
Click to expand...
Click to collapse
Gordietm said:
It's because you were using r28.0.1 before, download r28.0.2
Click to expand...
Click to collapse
I've been using r28.0.02 just confirmed by looking at everything I had downloaded for trying to fix this yesterday :/
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
I have access to another phone here, and can make a video of what I'm exactly doing?
Would this be of any use to troubleshoot, I really don't want to end up on the path to an RMA.
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Gordietm said:
Ok, go back and flash the march android p factory image. Let it boot up and setup. Enroll the q beta program and update to q with your phone. Try that.
Click to expand...
Click to collapse
Gordietm said:
At this point, you're probably best to talk to someone else who has more experience at this than I do.
Good luck!
Click to expand...
Click to collapse
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
XZeeWhy said:
Haha, well that's def not Google either, they straight up said RMA it.
Thanks for trying bro.
Click to expand...
Click to collapse
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
XZeeWhy said:
Was on the newest 9.0, updated through Q with the opt in, boot into twrp, flashed it, broke the phone ever since. That's the simplified issue, following the soft brick guide with updated tools & drivers using C to C cable no factory image has worked. All breaking at different points, closest an image got was the newest 9.0 failing at the Vendor img,
Click to expand...
Click to collapse
After failing on the Vendor image, you can sideload the OTA and that should get you back up and running......for some strange reason I always seem to fail there and sideload the OTA at that point has ALWAYS fixed me.
GL!!
hatdrc said:
The only other thing I can think of is wither the cable or the usb-c port on the computer. You said you can't get to an A to C cable but do you have another computer you could use?
Click to expand...
Click to collapse
There is another PC here, but it doesn't have a Type C port, and I don't have an adapter on hand either.
Certainly willing to give Windows a clean install or do a live boot or install of linux to see if a fresh install or another operating system may help resolve it.
So stock factory images can not be flashed via TWRP?
It does seem to change various images on the device when rebooting to bootloader after using Flash All so I feel like it's getting quite a large amount of the partial install.
If I have boot loader & TWRP, I mean there has got to be a way right?
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Slim2none4u said:
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Click to expand...
Click to collapse
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
I know you've already tried, but these two things are practically always the problem:
1) Using a new USB port on the computer. USB-C is particularly problematic.
2) Wrong drivers. The PC can use different drivers depending on whether the phone is in normal, bootloader or recovery mode. So you need to check your drivers while the phone is in recovery.
Arealhooman said:
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
Click to expand...
Click to collapse
Yeah not sure i really would mail it although it just a $50 toy and thats why i bought it...kind of a google fan boy and want the box set lol
Remote software would work and i would be willing as there is no sensative data on this PC.
But who would be willing?
Have you tried PixelFlasher
Arealhooman said:
Have you tried PixelFlasher
Click to expand...
Click to collapse
Only to flash stock and to root. Most roms are a sideload updates and i can't figure out how to use PF to do custom roms.
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
zpunout said:
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
Click to expand...
Click to collapse
I have a hub...may give that a try. Haven't touched the phone for a while now.