Related
I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.
Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.
Try it with another computer, another USB cable...
I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...
Try Moborobo
Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk
Hi guys. I think I need your help because I soft bricked my E975, and after leaving PANIC MODE I think I'm also out of options.
I've tried to list everything I've done - probably idiotic mistakes so you have all the information to what could be wrong.
Here is what I've done so far that led to bricking it and what I've made to make it worse(?):
rooted the phone - that seems to be the only thing I've done correctly (4.1.2 android)
installed FreeGee and Rom Manager
FreeGee backup efs
Rom Manager flash CMWR
Turn off the phone - try to access the recovery menu
neither Vol UP + Power nor Vol Down + Power - doesnt' work - that should made me stop
back to Android I FreeGee flash TWRP
Turn off the phone - try to access the recovery menu
neither Vol UP + Power nor Vol Down + Power - doesnt' work - that should made me stop
back to Android I finaly access the recovery menu by launching it from Rom Manager
TWRP runs smoothly
I backup current rom
Here I confuse myself and switch between Recovery and Android a few times not doing any changes
use Rom Manager to get back to Recovery (as the volume+power combination doesn't seem to work - all get is bzzz wibration and nothing ever happens)
wipe the system (I think I didn't do full wipe which might be part of the coming problems)
install MIUI rom (4.4 android)
reboot
rom partialy works - that means I can access the system and internet through wifi, SIM doesnt work, nor download manager
as I try to install Rom Manager to access the recovery (the power+volume combo doesn't work) It comes out that I also cannot install any apps
I install Android SDK on Windows and access recovery through adb
TWRP doesn't seem to run correctly, it's completely unresponsive and touch seems to stop working afer a few seconds
after a few unsuccesful tries I'm making things (supposedly worse) by following this thread: http://forum.xda-developers.com/showthread.php?t=2667398
I use KDZ and now the phone is on bootloop
The vol+power combos still don't allow me to access recovery, and as I can't access the Android itself it seems I lost a way to go into recovery
I try to use the TeenyBin method http://forum.xda-developers.com/showthread.php?t=2249500
LGNPST installed but I cannot enter the download mode
I reread the instructions a million times and I still cannot enter download mode (both volumes+usb in or both volumes+power+usb in) similary to not being able to enter recovery (vol+power)
the only thing that happens here (sometimes) is that windows tries to discover the Android Phone and fails to install drivers (I have the latest, and they worked before) - and sometimes the battery icon shows and starts charging
I can see the logo on bootloop
So this is what I've done (f**ked) so far - what are my options doctor?
Oh right oh right boys!
So... Still cannot enter Download Mode nor Recovery with power/volume buttons but...
After the phone went to bootloop I just connected it to PC through usb and went into recovery by adb reboot recovery and wiped the phone clean and installed a CM I had on sd. And everything seems to be working fine. Still the inability to enter Recovery/Download through keys seems strange. If anyone has answer to that pls reply
Hi guys,
my wiley fox swift gets stuck in a continual optimising apps cycle. I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted) it worked fine yesterday and today i can't get it to work.
It's always optimising apps, if it's finished then i see the cyanogen logo and it starts optimising again shortly after.
I removed the battery and did wait about 15 minutes before putting it back in, i tried waiting (after 2 hours+ of it optimising i gave up),
i does not get recognised when i connect it to the pc (although i only used it to put stuff on the sd-card before) maybe a driver would fix this but i'm not sure which one.
I'm pretty clueless right now and i would be happy if someone can help me.
Saw the same thing on a friend's device today, used fastboot to factory reset the device. Insert USB in a powered-off device while holding vol+ then using fastboot do a "fastboot -w" to factory reset and recreate the (probably corrupted) data partitions.
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
dajohre said:
i installed the minimal adb and fastboot connected my phone with my pc started it and tried it.
it doesn't recognize my phone and is stuck "waiting for any devices".
what can i do now? i'm not very experienced with android phones and fastboot.
Click to expand...
Click to collapse
ADB needs debugging to be enabled in developer options
FASTBOOT will only work if the phone is in bootloader mode
I already said in my first post:
dajohre said:
I can't enter recovery mode, when i press power+volume up it enters fastboot
(only see the black fastboot screen can't do anything). I did not change anything on my phone (not rooted)
Click to expand...
Click to collapse
since i never changed anything in my phone I haven't enabled debugging in developer options, if I could access the bootloader mode I could reset my phone but like i said,
it enters fastboot and not the bootloader from which i could enter recovery mode
under these circumstances, can i do anything?
see here https://wiki.lineageos.org/devices/crackling/
Note they call bootloader mode Download
Ok i can access recovery mode now (it was explained wrong here)
i tried to factory reset but the problem still persits.
in recovery mode i did go to ->Wipe data/factory reset then i had the options (No/No/Yes -- delete all User data/No)
i choose the third option and it did load a short while. after a reboot it still wants to optimise apps.
what's the best option now? i can choose (Apply update\ Wipe data/factory reset\Wipe cache partition\wipe media\reboot to bootloader\View recovery logs)
Fix
Hi,
I had the same issue and wrote the Wileyfox customer support.
They provided me the following instructions to fix the issue:
Download:
* 1 - ZNH0EAS2NH
* 2 - ZNH2KAS7EB
* 3 - TOS111B
Repeat for File X in [1, 2,3] :
* Goto Recovery
* Update your phone using File X
Since this is my first post I am not allowed to post links.
Find the full document including file links here: h t t p s : / / we . tl / B1IpUP6wtB
Already after running the first update my phone booted again.
Only thing I noticed is that the UI feels a little laggy / slower than before.
Regards
Nexus 5X lost lock pattern (fastboot found, adb not found), recovery "no command"
Hello !
So, I've had the same pattern to unlock my screen AND boot my phone for months.
This morning, I can't unlock : I do not remember it, I try to connect the dot "as usual" and then start to think, and now I've got my muscle memory mixed with me trying to figure out what is the pattern! So I try different combination that I think are close.
Then I reboot...
Then... there's this lock on boot time also, I tried a few different combination, and I have only 5 tries left before device WIPE !
- I have installed Android studio, the USB Driver (which I think is the right one)
- I can either boot my phone in normal mode (stuck in the dot patern lock), either in fastboot mode
- From fasboot mode, I can go to recovery, but it says "No command"
- With the SDK tools, I can list my device with "fastboot devices" (and reboot it for example), but I can't have it to appear with "adb devices"
I'll try one or two other time later when I'm tired my patern, to see if i can do it without thinking...
BUT, Can't I remove the lockscreen somehow? I'd preferably backup some files and apps data before wiping it
What do you suggest!?
Thanks in advance
I finally had to wipe / factory reset.
On reboot, he asked me to unlock the phone WITH MY GOOGLE ACCOUNT.
So ... I had to wipe everything, then unlock it. Why, oh why, the boot screen does not have this option!?
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