I can't unlock bootloader in my my phone.
I've also on usb debugging mode and ome unlock, and use the adb driver and write the proper command but it shows waiting for device.
Any one have any ideas..
Plz help me..
do you really have adb and fastboot drivers installed?
connect phone to pc via cable.
in adb console write- adb devices
if you have the correct adb drivers you should see your device id as connected
write adb reboot bootloader
it will boot to fastboot, write fastboot devices
if it shows your phone id everything should be fine, unlock your OEM via command
Heyyo, for me using the developer options in EUI ROM and unlocking bootloader in there worked. Please try that and see if it helps
I tried in a few ways and did not unlock the bootloader even though everything was going well. Finally, the phone returned to its previous state. previously, I had Lenko zuk with 2 - without any problem, I unlocked it using Tool all in one.
mirmad56 said:
I tried in a few ways and did not unlock the bootloader even though everything was going well. Finally, the phone returned to its previous state. previously, I had Lenko zuk with 2 - without any problem, I unlocked it using Tool all in one.
Click to expand...
Click to collapse
Either your phone is not in bootloader mode or you have no drivers installed. Since I never use Windows, I can't help though.
Connect your phone to the PC. Then type in a console "adb devices" if it shows your device just type "adb reboot bootloader" . When the phone restarts type "fastboot oem unlock" (I think this was the command) and you're done. If you see "offline" or nothing after "adb devices" check the driver's if they're installed. If so check the cable and don't use any usb external hubs.
It did not do anything. Everything is fine for the reboot and does not see the device after restarting.
mirmad56 said:
It did not do anything. Everything is fine for the reboot and does not see the device after restarting.
Click to expand...
Click to collapse
what about when you connect phone to pc, open adb console and write- adb devices?
do you get something like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately, I am not doing something wrong
mirmad56 said:
Unfortunately, I am not doing something wrong
Click to expand...
Click to collapse
Does it says that the phone is in fastboot mode?
no
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
shows error or no device
mirmad56 said:
no
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
shows error or no device
Click to expand...
Click to collapse
Can you provide a little bit more info?
What error are you getting and what exactly are you doing?
in the command window I entered the adb reboot bootloader. answer, no device found, no emulator.
mirmad56 said:
in the command window I entered the adb reboot bootloader. answer, no device found, no emulator.
Click to expand...
Click to collapse
Are you sure that you have enabled adb on your phone. If yes then there's a problem with the cable.
I went through the entire TWRP installation procedure successfully (?), But the phone is just like before the app came in; OFFICIAL TWRP APP. What's next ? can anyone help?
mirmad56 said:
I went through the entire TWRP installation procedure successfully (?), But the phone is just like before the app came in; OFFICIAL TWRP APP. What's next ? can anyone help?
Click to expand...
Click to collapse
You're done. Install some custom ROMs if you want to and do whatever you want.
I installed TWRP using TOOL ALL IN ONE.
Deb Sankar said:
I can't unlock bootloader in my my phone.
I've also on usb debugging mode and ome unlock, and use the adb driver and write the proper command but it shows waiting for device.
Any one have any ideas..
Plz help me..
Click to expand...
Click to collapse
I'm dealing with the same problem
Related
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
bhushan46 said:
Hello devs,
here i will write what my friend did with his phone htc one x plus
1.unlocked bootloader successfully
2.flashed recovery, some uncompatible kernel , img files Without rooting.
After this, phone was not booting , now recovery is also not working.
Even phone is not accepting the adb fastboot commands.
1. whenever i boot in HBoot it search for a file .zip from sd card (for what i dont know)(while connected to computer)
2.it shows the "fastboot usb" but computer says device not found. Drivers are installed. Checked with other htc device so they are working fine
3.Is there any way to take to stock via RUU installations.
please guide me with tutorials.
please help me with this problem.
thanks in advance.
Click to expand...
Click to collapse
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Ghand0ur said:
S-ON = No Brick.
Recovery and "img files" Don't need root.
Nothing is called adb fastboot
Connect phone in fastboot mode (Power + Volume Down > Fastboot)
Then use the "fastboot devices" command.
Flash twrp 2.8.6 http://dl.twrp.me/enrc2b/twrp-2.8.6.0-enrc2b.img
Flash a compatible kernel.
Device should be "fixed"
Search for "RUU enrc2b" . RUU depends on your CID.
Click to expand...
Click to collapse
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
see that image.
bhushan46 said:
First of all thank you so much for your reply.
Yeah thats great, i have S-on .
But Fastboot mode is not working .
When i connect phone to computer it shows fastboot usb but no command works.View attachment 3256147
see that image.
Click to expand...
Click to collapse
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Lloir said:
Useful reading
http://forum.xda-developers.com/showthread.php?t=2277112
http://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
http://androidforums.com/threads/list-of-fastboot-command.714676/
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=how+to+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=what+is+fastboot
https://www.google.co.uk/webhp?sourceid=chrome-instant&ion=1&espv=2&ie=UTF-8#q=adb+and+fastboot
Click to expand...
Click to collapse
Hahaahahhaa Perfect description.
@OP:
ADB and Fastboot are two different things.
You DO NOT NEED ADB.
DO NOT WRITE ADB
Write "fastboot devices" directly, and your device will show up.
And please do read all the links lloir provided.
Thank you so much guys.. @Lloir nd @Ghandour
OK, so i am really lost at this point. I have been trying for the past couple of days with no luck.
I used Minimal adb and fastboot, downloaded Lg drivers (LGMobileDriver_WHQL_Ver_4.0.3), sdk google drivers and looked at many comments to figure this out.
i type adb device and my phone shows, I type fastboot device and last couple of my phone shows. I used Mininimal adb and fasboot to unclock the the bootloader and i followed all the commands but when i get to fastboot flash recovery twrpxxxx.img, it tells me cannot load twrpxxxx.img. Also, when i type in adb reboot bootloader in brings me the an LG screen with powered by android at the bottom instead of the correct screen.
So, i tried the other way. Power phone off, hold down the volume down button and plug in usb and bootloader/fastboot opens up ( the screen with the line in the top left, with a blank page). it shows unlocked, few lines in white, and then few lines in red. I type fasboot devices and my phone shows up displaying last couple of the phone sn#. but when i go to type fasboot flash recovery twrpxxxx.img, i get the same message cannot load twrpxxxx.img. and on the phone is shows fastboot getvar partition recovery.
Any idea on what this is and how can i solve this?
Thanks in advance.
Rename it to recovery.img and try again.
I renamed it and I still get the same error. Cannot load recovery.img
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Elu_sama said:
Make sure the image is in the same folder that you are running adb from; it doesnt scan your whole computer for the file. ��
Click to expand...
Click to collapse
It is in the same folder.
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Figured it out.
papatoon3 said:
I renamed it and I still get the same error. Cannot load recovery.img
Click to expand...
Click to collapse
I suggest you remove and reinstall sdk or install nexus root tools and run a cmd within the updated tools. Make sure you installed the right drivers, delete all others, reinstall, although your error seems more a problem with the tools, permissions perhaps, did you run cmd as admin?
Unable to load tells me it can't find your file.. Perhaps it has a hidden extension? Recovery.img.txt
Whats the complete exact command you're typing?
"fastboot flash recovery recovery.img"
http://androiding.how/how-to-install-twrp-recovery-via-fastboot/
Sounds like this is not enabled
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk
papatoon3 said:
Does it make any difference that my phone is unlocked from T-Mobile via unlocked code? That should not have anything to do with it thought. I am just tying to figure it out.
Click to expand...
Click to collapse
SIM unlocked (tmo has no code, its an app) and bootloader unlocked isnt the same thing.
Never mind got it
papatoon3 said:
Figured it out.
Click to expand...
Click to collapse
What was the solution i need it please and thanks
tanked89 said:
Never mind got it
What was the solution i need it please and thanks
Click to expand...
Click to collapse
When your phone is turned on and plugged in, type command adb devices, Does it show?
Put phone in fastboot mode, type command fastboot devices, does it show?
I figured it out. I had to install motorola and g4 drivers to get fast boot to read when I only had one or the other it was only reading adb when I had both on pc it read and adb & fastboot and worked. Thank you.
Hi sir I am facing a problem I rooted my v10 first I unlocked bootloader and then I rooted it by using fwul I hard reset it but when I turned it on a twrp recovery menu appeared please help that how it fix
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
@lost101, Need your expert advice on this. Others, please do help.
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
lost101 said:
'USB Debugging' most likely does not need to be enabled with Condor handsets in order to unlock Bootloader. That is a security feature that only appeared with later devices.
The USB issue seems obviously driver-related. The easiest solution would be to boot into a Linux Live CD (such as Ubuntu), and gain fastboot access that way - drivers are not needed in Linux. Then fastboot flash the latest XT1022 factory firmware image.
*Note: In linux, use the 'sudo' command prefix:
sudo fastboot devices
Click to expand...
Click to collapse
Live booted uBuntu Raring Ringtail 13. Added the necessary repositories first ;
sudo add-apt-repository ppa: phablet-team/tools && sudo apt-get update
Click to expand...
Click to collapse
. Further installed the ADB & Fastboot ;
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
. Got success messages.
Further using the terminal, used two commands ;
sudo adb devices
Click to expand...
Click to collapse
sudo fastboot devices
Click to expand...
Click to collapse
The result was exactly the same which i get in Windows command prompt. The list of devices shows a blank. I've installed the drivers and rechecked them, the device is listed as "Motorola ADB Interface" under Device Manager :
and; shows as Fastboot condor S in hardware eject box.
I fail to understand why it isn't showing as connected only in the fastboot menu. Fastboot reason is given as "fall through from not charger boot mode". The device shows only the fastboot screen by default. If any other option like recovery etc is selected, it throws the error message as bootup failed. Scenario is exactly of the same pic which was posted in #1.
Please suggest the next step.
@BBThumbHealer - Starting to look like Bootloader corruption. An unbrick method could be applied to potentially restore a functional Bootloader. One exists for Falcon 5.1 - unsure about Condor at this time.
I would try to eliminate the USB cable as the problem by trying alternatives.
BBThumbHealer said:
Hello Guys,
Laid my hands on a spare XT1022 from my friend that was supposedly junk for him because of the following reason. The phone starts of directly in fastboot mode and there's no sign of a normal startup. Although i've connected the USB cable and it shows up as "Motorola ADB Device" under Device Manager, still the fastboot shows Connect USB Cable error. The exact scenario is depicted in a similar pic below :
.
The phone is fully stock and was treated to this message upon a random reboot. I can get this back to life by flashing TWRP & Custom ROM's but for that first of all need to unlock the bootloader, for which the data cable needs to be shown as connected. USB Debugging wasn't enabled.
Would be highly obliged if someone could shed some light in the right direction and help out on this
Regards.
Click to expand...
Click to collapse
I was stucked in the same problem yesterday. I succeeded and recovered my Moto E to live again.
As in the screenshot you posted. Your bootloader is locked. You need to unloack the bootloader. To do so follow the steps in the link given below :
https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Login or create your Moto ID and follow the steps as described.
After that you'll have to flash the firmware again. hope this helps.
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
Hello guys can someone help me on my redmi note 10,
So basically my problem is adb can detect my phone when its power on but when my phone switches to fastboot adb cannot detect it anymore. I also try the adb reboot bootloader command, it work and it go to fastboot but after that it didnt detected anymore.
Please help me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
missingN said:
I'm not sure, but it looks like you need install usb/device drivers from MiFlash.
And after, try enable/allow usb debugging
Click to expand...
Click to collapse
i already tried that still the same
@ibanezred16 May be you missing add Environment Variables path?
Adb-fastboot PE guide
ibanezred16 said:
...when my phone switches to fastboot adb cannot detect it anymore. ...
Click to expand...
Click to collapse
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Mthw said:
This is intended behavior, if your phone is in fastboot mode it can only be detected by fastboot (try command 'fastboot devices'). Devices can only be detected by adb in recovery when sideload is enabled or in OS with debugging on.
Click to expand...
Click to collapse
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
ibanezred16 said:
sorry im new here, can you tell me a way to flash the twrp? because the regular method don't work with me
Click to expand...
Click to collapse
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Mthw said:
What do you mean by regular method? This should work: 'fastboot boot twrp.img' and once it boots up go to Advanced and there is an option called 'flash current recovery'.
Click to expand...
Click to collapse
that's also one of my problem when it boots to twrp the touch screen is not working can't touch or click anything when im in twrp
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Mthw said:
Are you using this one? https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4268563/ Either way you should probably ask there.
Click to expand...
Click to collapse
yes, thank you very much for your help
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
yeah im trying to install Evox
Mthw said:
Were you successful? I am guessing you are trying to install a ROM, depending on the rom you could also use a different recovery.
Click to expand...
Click to collapse
Im succesfully installed twrp I used mouse via otg connector to touch the screen