Flash factory image without pc - Google Pixel XL Questions & Answers

Hello,
I have this strange issue that occurred after I flashed one of the many custom roms floating around.
The USB connection menu in the phone is greyed out and technically I cannot transfer anything over the cable from a computer and with this obviously I cannot use any adb command so I can flash the stock.
The phone is only charging when being plugged in nothing else
Prior to be flashing the rom I have booted TWRP tethered so I could flash it but now since my usb settings are greyed out I cannot boot TWRP anymore nor I can boot from the phone as I didn't make TWRP permanent.
Is there any way at this point that I can flash TWRP, any rom or even stock image considering that I cannot see the phone over the USB ?
Appreciate any input

...why don't you just reboot into bootloader and boot twrp again and this time flash it in recovery? Are you saying you no longer have a usb connection to your phone, as in it's broken?

Related

[Q] Trying to restore One X to Stock

I've been running Cyanogenmod 9 for a couple of months, but decided to restore to stock so I can try out ICS and the new version of sense. I tried this a while ago but got stuck when when phone wasn't recognised via USB when connected to my laptop. Fastboot would change to Fastboot USB when plugged in, but the phone wasn't picked up. However, on this occasion I was able to restore Cyanogenmod without problems.
I tried this again yesterday with the same result regarding the USB connection, but when I restored Cyanogenmod it now just hangs on the boot screen and won't go further. Prior to this, when I ran the restore function in Clockworkmod, the phone would hang on the HTC splash screen with the beats audio logo on it. I did manage to get the phone to boot into recovery, but rather than the usual menu option I had a message something like "checking SD card..." and then nothing.
I am not sure where to go from here. The only thing I am wondering is if I tried to do this with the battery being too low, and the installation has failed because of this. I do want to go back to the stock OS, but not sure how to go about resolving the USB issue.
UPDATE
Partially solved the problem, in that I've managed to reinstall the cyanogenmod. Still stuck with lack of USB connectivity though.
Wrong section.....
Do you have the Fastboot files all in the same folder and do you have the HTC Sync drivers installed? You need that set up correctly to get a fastboot USB connection.
My suggestion is to simply "fastboot oem lock"
Then flash corresponding RUU to your current HBOOT. You can find out which RUU you need by typing "fastboot getvar version-main"

[Q] Urgent help needed. Fastboot usb not working

I was running resurrection remix, when i saw the 4.4.3 based slimkat. So naturally, i had the urge of flashing it. i was on TWRP 2.7.0.0, i flashed the 2.7.1.0 version of twrp, flashed the rom, gapps, and rebooted, but my phone wont boot up. later, after a series of flashes and wipes, when i failed to boot the rom, i tried to install some other rom. but my phone wont connect to pc in recovery. i flashed the TWRP 2.7.0.0, then CWM 6 but no luck. finally, i flashed phillz along with the kernel from viperx and the phone mounted. copied viperx, flashed, rebooted. now the phone wont pick up my sim card. i thought this might be the issue with the kernel. went back to fastboot to flash the kernel, everything was working fine but as soon as i connected the usb cable, and phone was in fastboot usb mode, my volume buttons and power key stopped working,windows said that a device has malfunctioned, tried to flash but it would just say <waiting for device> and as soon as i removed the usb cable, my phones hardware keys started working again. if booted in hboot with usb connected, it would get stuck on checking sd card for update. Now i am stuck and need urgent help, coz i might miss some important calls if this continues and i am unable to flash.
Some other information that might be useful.
Rom: ViperX
Windows: 7 ultimate.
only HTC usb drivers installed, nothing else.
To flash i usually use Hasoon`s tool as it is very handy

Cant access USB debugging or any of the bootloader after replacing screen.

I recently replaced my Cracked Screen on a Verizon m8. I was on a custom rom with twrp installed. After the initial boot, I was having problems with a speaker and went to try to boot to the bootloader to do a RUU, when I noticed that I can no longer access the bootloader screen. It was then when I noticed that not even my computer was recognizing the phone no more. It's as if the phone won't debug no more. I can still access my TWRP by rebooting straight to recovery thru a app or the apm it has on the custom rom im using. I've tried to flash other roms with no success to get access to these two things. I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms. Or if anyone has had this problem before or if any suggestions im open to anything to try and get to the bootloader screen. It also doesn't even boot the two or 3 second boot up screen until you get to the roms boot up screen. It also doesn't goto the bootloader screeen when it try's to access the bootloader. Even when booting straight to recovery stays black until twrp actually shows up. So it's as if bootloader is completely being bypassed. You cant use the volume keys to access the recovery cause everything is blank. Although on first attempt to access bootloader screen when I was stuck there in black. I had to figit the keys a bunch of times to reboot, hoping that I didn't activated something in that screen that caused the phone not to debug. Any suggestions is more then welcome and if someone has a stock twrp of recent stock rom 4.605.9 I believe it is would be more then great. Cant find one other then in zip or exe version. Hoping maybe that might reactivate those two things. Thanks for taking the time to read my problem.
Debugging or adb works within OS, and its not a mode in itself. I think you mean you can't access bootloader-fastboot mode.
Casetheace said:
I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms.
Click to expand...
Click to collapse
You mean stock recovery. TWRP is a specific custom recovery, therefore always a custom one.
I don't think stock recovery will change anything. Bootloader is on a completely different partition.
Its odd that you can't access bootloader. It must still abe intact, otherwise the phone would not work at all.
Did you try (in OS): adb reboot-bootloader
Are you s-off or s-on?
The phone is S off. I was able to get the phone to USB debug. I took it out of the shell and plugged in the USB cord and it debug instantly . So I'm guessing with that I had to damage something when I either took the phone out of the shell originally or when I replaced the screen. Cause you literally have to take every piece of the phone off and then reasamble the phone from scratch. Once i put the phone back in shell, i couldnt get it to usb debug no more. But I still can't access the bootlader, nor is the first boot screen on power up before the main boot up screen starts. Also has no display if I reboot to recovery using a app from the phone. You don't see the screen where the red text would show up saying rebooting to recovery, display starts when it begins to show twrp on display. But when I had the shell off, and was able to access USB debug, I was able to use adb commands from my computer from fastboot mode , but phone had no display. Was able to run a RUU, was able to use adb to reboot to boot loader, then was able to fastboot get varall command. Even flashed a twrp recovery install in fastboot under command prompt . So that tells me that the boot loader is operational. That it has to be some sort of power failure in booting that nots powering the display on initial boot for 2 to 3 seconds , no power on bootliader display, no power rebooting to boot loader or rebooting to recovery until it boots recovery. Any ideas what would cause this failure of power of display during boot loader processes? By the way , have twrp 2.87 . Its a Verizon build, but I'm on a T-Mobile sim.
I've installed live boot and attached a log. If anyone can help or maybe know why this might happen. Believe there is two boots, each with a separate power. Main boot is the initial power up last two or three seconds, and then system boot.. Believe main boot is sending power off display and then power on display on system boot.

Bootloader problems on Tate (Fastboot screen)

Tried to update the Kindle 7" Tate to MM tonight.
Flashed the ROM no problem but when it came to GAPPs philz recovery was blocking it for some reason.
No problem i thought i'll downgrade the ROM and use flashify to flash the TWRP bootloader.
Now i'm stuck on Fastboot splash screen whenever i turn on, tried the quick pull reboot but because i've messed the bootloader that was pretty unhopeful.
Worse problem is that i cant seem to find my fastboot cable.
Ive reinstalled minimal adb and fastboot and ive got the boot img ready to flash but i cant seem to get the device to be recognised with fastboot -i9 0x1949 getvar
Wish i'd just left the stupid device on lollipop now.
Any advice would be gratefully recieved.
p.s. As i hunt for my fastboot cable - am i looking for a cable with a micro usb or mini usb connector on? If im looking at the ports - which connector does it go in?
:crying:

Sorta/Kinda Brick After Attempted TWRP Install - Moto G7 Play 1952-4

Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Did you flash the copy-partitions.zip while in TWRP?
Maybe you could borrow some ideas from the official install instructions for LineageOS.
Install LineageOS on channel | LineageOS Wiki
wiki.lineageos.org
I had some strange intermittent USB connectivity issues with a few Moto G7 Plus devices with my main laptop, but was fine connecting on a 12 year old desktop computer. So perhaps you could check to see if adb connects on another machine. Only other idea I have is to somehow flash back to stock again with fastboot.
[Guide][Channel][Stock]Moto g7 play Factory Firmware Images
Moto g7 play Android 9 and 10 Factory Firmware Stock Images Info Updated on 23-11-2020 Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download...
forum.xda-developers.com
zpunout,
Thank you for your response.
zpunout said:
Did you flash the copy-partitions.zip while in TWRP?
Click to expand...
Click to collapse
No, I didn't know I needed to; nothing about that is mentioned by TWRP.me.
This is unknown territory for me, but your question sparks a thought for me. I wonder if 1) The stock recovery is in the "other" slot, and 2) there is some way to boot from it. That could be a way to sidestep the ADB devices problem I'm having?
zpunout said:
So perhaps you could check to see if adb connects on another machine.
Click to expand...
Click to collapse
At the moment, I have no way to do that. I don't think the USB connection is the culprit, ADB "sees" the phone just fine while the phone is in the stock OS, just not in recovery (EDL?.
zpunout said:
Only other idea I have is to somehow flash back to stock again with fastboot.
Click to expand...
Click to collapse
That's my current plan, but FASTBOOT won't flash anything while ADB devices won't/can't see the phone. I'm hoping someone has a workaround of some sort for that.
Tenaya
Hi, first of all lets set some things straight, you are experiencing a Boot Loop, in other words a software brick. (Soft Brick) now luckily these are fairly simple to fix. Sorry to break it to you but the N/A Screen won't disappear, that used to be the Blue/Yellow Motorola Splash Screen, but since you unlocked your phone it'll only show N/A but thats okay there are tools that can help you customize this and change it later on.
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in. But worry not, try to get into your bootloader, and try to connect adb through there.
Tenaya43 said:
Ok, so I’ve run myself off the road into a deep hole and am hoping someone can help me climb out and get back onto the correct path.
I have a Motorola Moto G7 Play 1952-4 (channel). My goal is to install TWRP, and LineageOS 18.1 with GAPPS. Root is not important at the moment.
Here’s what I did:
After successfully unlocking the bootloader (thank you Motorola), I downloaded TWRP for Chanel from the TWRP.me site. My plan was to first install TWRP, then use TWRP’s install feature for LoS 18.1 and the GAPPS.
To install TWRP recovery, I followed the instructions on the TWRP site. After starting the ADB server on my Windows 10 PC and booting the phone into the stock recovery, I used “adb boot twrp-3.5.2_10-0-channel.img” to temporarily boot into TWRP recovery. I then used ADB to push TWRP.zip onto the internal SDCARD. I used TWRP’s install feature to install "twrp-installer-3.5.2_10-0-channel.zip", presumably to both slots. To the best of my memory, everything completed correctly.
BUT . . . when I powered down the phone and attempted to boot into recovery, all I got was a black screen with a small N/A in the upper left corner instead of the familiar TWRP screens. After a while, the phone booted itself into the stock U.S. Cellular Android 10 (Hell Oh - Moe Toe). I've done several power-off/power-on cycles to no avail. I am able to get to and use the stock OS.
So, like TWRP.me suggests, I figured I’d just flash it back to stock and start over. Um, nope. I can Vol-DN/Power to the bootloader menu, but “adb devices” doesn’t see the phone, preventing me from flashing anything. USB Debugging is enabled and the phone says "USB Transfer Mode: Connected". “adb devices” sees the phone while Android 10 is running, but as soon as I boot into recovery, the phone “disappears” from ADB.
The only other thing I could think to do was to use the “Rescue” function in the Lenovo/Motorola Smart Assistant. While ADB can’t see the phone, LMSC sees it just fine and I was able to rescue/reinstall the stock OS successfully, or so LMSC said. Unfortunately, LMSC doesn’t seem to fix whatever is wrong with the recovery. Interestingly, “N/A” no longer appears after Vol-DN/Power and select Recovery Mode, the black screen now says “bad key”, followed a little while later by the Android logo with a “!” in the middle of the screen and “No command” below it.
And that’s the hole I now reside in. Despite considerable searching/reading here at XDA, I'm at a total loss for what to do next.
SOOOO, I’m hoping someone can help me:
1. Fix the N/A black screen
2. Get into a mode that ADB can see
3. Properly install TWRP
Thank you in advance,
Tenaya
Click to expand...
Click to collapse
HellxDo,
Thanks for the reply.
After I used LSMC to "rescue" the phone, it stopped displaying N/A" and began showing "Bad key". Different, but not better.
HellxDo said:
Now why is it on a boot loop you may ask, well that is because there is no more operating system to load in.
Click to expand...
Click to collapse
Hmmm . . . The phone currently boots into the stock rom (U.S. Cellular Android 10) if I wait a while after "Bad key" displays. If there's no more OS to load in, how do it do dat?
HellxDo said:
But worry not, try to get into your bootloader, and try to connect adb through there.
Click to expand...
Click to collapse
My (limited) understanding is that the only way to "get into" my bootloader was with the Vol-DN/PWR button combination. When I do that , I get the bootloader menu, but ADB doesn't/can't see the phone - nothing is listed when I run ADB devices and fastboot won't/can't flash anything.
Is there a different/better way to get into my bootloader?
Tenaya
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Tenaya43 said:
And the adventure continues. Here's some more information.
While continuing to research this, I was wondering if there was another way to boot the phone into EDL mode and Google found some instructions at thecustomdroid.com for using ADB to boot the phone into EDL. I booted the phone to the stock OS and used the command adb reboot edl. The phone immediately went blank, followed shortly by the "bad key" message. After a while it again booted into the stock rom.
I still cannot use fastboot because it doesn't/can't see the phone.
I have also discovered that if i use VOL-UP/PWR, the phone boots directly to "bad key", followed by the stock rom. Another dead end.
I also used LMSC to "Rescue" the phone again and learned several things:
While LMSC is running, it boots the phone into the bootloader menu and begins to flash. If I do adb devices while LMSC is flashing, the phone STILL doesn't appear in the list.
LMSC definitely flashed the stock OS - when the phone rebooted, it was back to the stock OS Android start screen as if it had never been configured.
There is still no recovery and I still can't flash anything.
LMSC is somehow able to flash without a recovery present.
Anyone have any other ideas?
Tenaya
Click to expand...
Click to collapse
If "fastboot devices" can't see your device while in bootloader mode, that could be the same issue I had relating to your USB compatibility with your computer. Try to borrow someone else's computer, install "platform-tools" to see if the "fastboot devices" command works.
If that works, next see if the command "fastboot getvar all" works. You should get many lines of info come up. If it gets stuck after a couple of lines, then the symptoms are the same as what I had. I have a bunch of really old laptops and a desktop sitting around with platform-tools just for this issue. I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly, but I haven't had success yet.
OK, some progress.
I found this:
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
kenzo has graciously hacked fastboot.exe to force the phone into EDL mode. Using that, the phone booted into EDL and fastboot devices can now "see" the phone. Thank you kenzo.
BTW, kenzo's fastboot-edl isn't G7 Play specific, it was originally for the Xiaomi Redme Note 3 and seems to work for some other Android phones as well.
I'm still working on getting TWRP and LoS installed, but at least fastboot can talk to the phone.
zpunout said:
I have heard others say that plugging the phone in via a USB hub sometimes gets fastboot to connect properly
Click to expand...
Click to collapse
I also had no luck with a USB hub.
I haven't tried another computer yet; I'm going to see what I can accomplish with fastboot-edl.
Tenaya
fastboot oem blankflash

Categories

Resources