Hi,
I'm after some advice, how do I place the Moto G5 in Qualcomm mode or EDL mode.
I have entered the bootloader by holding down and turning the phone on, this allows me to use fastboot.
From there I can scroll down to QCOM, but when I press the power button it boots into the normal system instead of EDL mode.
I have also attempted from within fastboot to use:
fastboot oem edl
fastboot oem qcom-on
fastboot reboot emergency
and
fastboot reboot-edl
Although non of these have been sucessful.
I also have access to an EDL cable, although, when I plug the phone in, then flick the switch 10 seconds later, it does not enter EDL mode, it just charges.
The phone sometimes shows as File Storage Linux USB Gadget in device manager, although it is inaccessible, I have updated the laptop to use the qualcomm drivers, although I don't think it will ever recognise it if I can't put the phone into qualcomm mode to begin with.
Any help would be much appreciated.
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
TheFixItMan said:
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
Click to expand...
Click to collapse
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
jameswstubbs said:
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
Click to expand...
Click to collapse
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
TheFixItMan said:
Sounds dodgy to me - sounds like your trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
It's not dodgy, but I fully understand.
Thank you anyway.
try fastboot -i 0x2b4c oem reboot-edl (it's working for LENOVO ZUK Z1 and ZUK Z2)
You can try (if you can/have the TWRP image) to flash TWRP and in reboot options select EDL.
In case the bootloader isn't unlocked you can also use fastboot boot [TWRP image name] to boot directly into TWRP without flashing and then repeat, go into reboot options and select edl.
Not sure if it works for you, if it does let me know that I have helped!
TheFixItMan said:
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
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
What happened was that I tried to update via Mi Suite
Everything completed nicely but it just wont boot at all
Is there anyway to wipe data without waiting for the unlocking procedure from xiaomi?
There's no recovery menu apparently
Edit: Managed to solved it by booting into EDL mode
How did you boot it in EDL mode? Just curious... I've tried couple of methods but it wouldn't enter EDL.
nijel8 said:
How did you boot it in EDL mode? Just curious... I've tried couple of methods but it wouldn't enter EDL.
Click to expand...
Click to collapse
Power off or restart
press both vol+ and vol-
insert usb while pressing
should viberate at this point
then it should request to install qualcomm drivers
with the current setup of Max, you cannot boot into EDL from adb? or maybe you are doing it wrong.
what i did was to boot on fastboot mode, then issue the command
Code:
reboot oem edl
the command is different for Mi Max.
I have exactly the same problem. But I'm not experienced on Fastboot, as my second phone is a S3 which is way easier to unlock.
Could you describe in more detail how you have accessed the EDL mode? The only thing I can use is "The Fastboot-Bunny" which does not help at all.
When I use the Vol+/- method my screen stays black and my phone connects to the pc. But how did you continue now?
Could you provide a link to the software?
Thank you very much in advance.
(Can not use my phone since update, exactly the same situation...)
When I do as you told, my phone shows a black screen. I don't know whether the phone is really on or off. I hear the "connect-sound" of windows, it seems to be connected as I can see it as "Qualcomm HS-USB QDloader 9008 (COM10),
but what do I have to do now??
Survivor1990 said:
I have exactly the same problem. But I'm not experienced on Fastboot, as my second phone is a S3 which is way easier to unlock.
Could you describe in more detail how you have accessed the EDL mode? The only thing I can use is "The Fastboot-Bunny" which does not help at all.
When I use the Vol+/- method my screen stays black and my phone connects to the pc. But how did you continue now?
Could you provide a link to the software?
Thank you very much in advance.
(Can not use my phone since update, exactly the same situation...)
When I do as you told, my phone shows a black screen. I don't know whether the phone is really on or off. I hear the "connect-sound" of windows, it seems to be connected as I can see it as "Qualcomm HS-USB QDloader 9008 (COM10),
but what do I have to do now??
Click to expand...
Click to collapse
If you see Qualcomm HS-USB QDloader 9008 (COM10), run Mi Flash and flash the ROM again.
MiFlash won't work due to locked bootloader. I already tried it. Flashing Rom with MiSuite does not help too.
Ooopps no way you can do it yourself. The only chance is the unlocked bootloader. From there you can install twrp then supersu(newer super su fixes the boot for my case)
We have the same problem. But mine is unlocked bootloader.
What i did is boot to fastboot. Flash the rom with miflash. Then i turned it off because its still useless if i wait it still stock at mi logo so i boot fastboot again and flash twrp. from there adb i reboot to twrp then flash supersu. I wait like 10 mins only and yes it boot to normal
You can install TWRP on it follow this guide even if the bootloader is locked:
http://forum.xda-developers.com/mi-max/how-to/installing-twrp-locked-bootloader-t3406501
Survivor1990 said:
MiFlash won't work due to locked bootloader.
Click to expand...
Click to collapse
MiFlash can work both in FastBoot or EDL modes. In FastBoot mode, locked bootloader prevents FastBoot server to execute "flash" command. But in EDL mode, MiFlash works with any bootloader state.
Anyone can help me?
My phone was dead, no fastboot no edl mode. My pc just show me hs-usb diagnostic 900e instead of the qloader.
Maybe any solution please
did you tried test point ?
http://en.miui.com/thread-308092-1-1.html
abhye_x said:
Anyone can help me?
My phone was dead, no fastboot no edl mode. My pc just show me hs-usb diagnostic 900e instead of the qloader.
Maybe any solution please
Click to expand...
Click to collapse
Its driver problem i faced same issue then i tried it on another pc it worked
emuzychenko said:
MiFlash can work both in FastBoot or EDL modes. In FastBoot mode, locked bootloader prevents FastBoot server to execute "flash" command. But in EDL mode, MiFlash works with any bootloader state.
Click to expand...
Click to collapse
So in EDL mode with a locked bootloader will it unlock the bootloader? I am confused abt whether this is the case if I choose "delete all" which will prob incl data & bootloader.
It also seems in fastboot mode, mi flash can only work with unlock bootloader. Any reasons why unlocking is required?
Rgds
I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone
M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.
So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.
hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
jonas.sj said:
Hello, I'm having some serious trouble bootloading my Kyocera DuraXV Extreme (AOSP)
I've went into developer options and activated USB debugging and allowed OEM unlocking.
But I get stuck on rebooting into bootloader mode. I've tried different approaches:
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
2. adb reboot bootloader command
Both options reboot the phone without going into bootloader mode.
Seems Kyocera decided to somehow lock the bootloader mode. Anyone know of a workaround here?
Click to expand...
Click to collapse
My comments below are based on the belief that you are trying to unlock the bootloader.
I am not familiar with this phone but generally the two steps mentioned by you are not enough to unlock the bootloader. After those steps, you'll have to issue a command via adb to unlock the bootloader and if successful, then you can boot into it for further operations. The command will vary between devices, so search and profit.
Thanks, this cleared it up a bit, you are right, I'm trying to unlock it.
I'm trying the command fastboot flashing unlock but only getting the message < waiting for any device >. I read somewhere that I might need some USB drivers but I don't know where to find them. I have the latest version of the standard USB drivers for the phone, but as I understand it I need special drivers for this?
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
jonas.sj said:
I'm trying to follow the steps here: https://www.ifixit.com/Guide/How+to+unlock+the+bootloader+of+an+Android+Phone/152629#s317298
I get stuck on the step:
Enter the command adb reboot bootloader
Wait a couple seconds until your device rebooted into the bootloader, then enter the command fastboot flashing unlock
My phone isn't "rebooted into the bootloader", it just reboots. It gives the message "< waiting for any device >" when I write fastboot flashing unlock
Click to expand...
Click to collapse
It should be a driver issue. When the phone is on and you connect it to the PC/laptop and send the command 'adb devices', does it show an alphanumeric value? Likewise, when you are booted into the bootloader by key combination and send the command, 'fastboot devices', does it show the same alphanumeric response? If so, the drivers are installed properly. If not, either you don't have the correct drivers or they are not installed properly. Try installing the drivers again after disabling driver signing in Windows on your PC (search for it on Google).
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
jonas.sj said:
Hello, can you clarify what you mean by "booted into the bootloader by key combination"?
My problem is I cannot boot into bootloader at all.
Any attempt at doing so results in a normal boot of the device.
Click to expand...
Click to collapse
Are you sure that the key combination for booting into bootloader is what you described in the first post?
1. Starting up phone while holding volume up and down buttons. Then select "reboot to bootloader".
Click to expand...
Click to collapse
I see Power plus Volume Up as the suggested one from a Google search. Try that.
If you can't even boot into the bootloader with the correct key combination, I don't know how to help you further since we are starting to go in circles. I am sorry.
Hello, thank you so much for trying to help me. It seems I can't boot into bootloader. Volume up + power gives the same result as what I did before.: It opens a "Recovery" menu where I can choose reboot to bootloader, but this option just reboots the phone.
I've been in contact with Kyocera and they say:
Thanks for contacting the Kyocera Customer Support. We will be more than happy to assist you with your concern
In this case allow us to inform you that since this device is a basic phone , it doesn't have the option to activate fastboot mode. By installing something that will change the way the phone works , that will void the warranty that came with the phone. We as manufacture can not help you to modify the software that came with the phone.
So the phone's fastboot mode has been deactivated. But since it's an android I guess it should still be possible with some workaround. I just don't know whee to start, I've been researching for a week with no result.
Something interesting ehre, maybe someone with more coding knowledge can tell what's going on.
I found the source code for the phone and located a file called recovery.c which I guess handles the menu I see when I press volume up + power button. Maybe some clue to why the phone isn't going into fastboot mode?