Database Info

[Q] Unlock Bootloader for HTC one X+...waiting for device!

hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!

quantum94 said:
hello there, i am trying to root my htc one x+
But while typing "fastboot oem get_identifier_token" to unlock the bootloader, i get the response "waiting for device" forever!
on the phone,it is showing "fastboot usb" and also the cell is being detected on normally being connected to the pc!
I even checked the device manager, all the drivers are proper, no exclamation mark near the htc device.
I downloaded the fastboot files from htcdev and ran it. Also downloaded and installed Android SDK as mentioned on htcdev.Also downloaded AdbWinApi.dll and Adb.exe from here:
http://adbshell.com/download/download-adb-for-windows.html
Placed all of them in a separate folder &ran the above command.
Also i copied adbwinapi.dll and adbwinusb.dll in win\system32 just in case.
i also ran the adb.exe
Also turned off the fastboot option on the device
Also restarted the pc and left it overnight just in case....
I have no idea what's going wrong! Any help!
Click to expand...
Click to collapse
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.

root-expert said:
Hello first run
Code:
fastboot devices
if you can see your device the procceed with your command. If you can't see it something is wrong with the fastboot configuration.
Click to expand...
Click to collapse
nopes...on typing "fastboot code", it redirects me to the current directory:
{
"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"
}
what to do?

Are you sure you are in fastboot mode?

root-expert said:
Are you sure you are in fastboot mode?
Click to expand...
Click to collapse
pretty sure...u can see the pic at:
What now!? :crying:

quantum94 said:
pretty sure...u can see the pic at:
What now!? :crying:
Click to expand...
Click to collapse
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.

root-expert said:
First of all download and install the official andorid sdk from google and then try to run fasyboot from there.
Follow these instruction to install the complete sdk tools.
If this doesn't help try reinstalling your device drivers.
Click to expand...
Click to collapse
sorry for the late reply....
I tried the same thing on different pc and it worked!
But i have another problem!
I installed cm11 nightly for my on my x plus from here:
http://get.cm/get/qG0
After that my imei has gone blank along with the baseband version.
I did a bit of research and found that by using ruu, u can get the imei back.
So for that i needed turn my s-on to s-off by the foll commands:
adb reboot
if i am not mistaken, while the phone is rebooting i am supposed to put the 2nd command:
adb wait-for-device push firewater /data/local/tmp
The problem here that I think is the phone reboots so fast that i guess the command fails to execute and i get an error saying :
error protocol fault (no status)
So, how to turn off fastboot or quickboot in cm11? There is absolutely no option in the phone. I tried battery settings,power settings, everything!
is there a way to disable fastboot/quickboot in bootloader mode?
plz help!

help root

Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses

Bencaill said:
Hi everyone,
I tried the method given by @DallasCZ but I have an issue.
All the files are in the same folder but I have this message: "cannot load: 'boot.img': No such file or directory"
Please help me !
Thanks in advance.
Kisses
Click to expand...
Click to collapse
Hello, are you sure you have the boot.img also in the direcotry?

DallasCZ said:
Hello, are you sure you have the boot.img also in the direcotry?
Click to expand...
Click to collapse
yes, I am sure I have it

Bencaill said:
yes, I am sure I have it
Click to expand...
Click to collapse
i tried it again and it works well for me.
can you post a creen of the folder where you extracted the files?

{
"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"
}

you have to run the root.bat file, you cannot dir the boot.img

I know I have to run the bat file but you asked me a screen of the folder

I have this message:

strange... idunno for me its working well (windows 7 pro) and the boot.img is in the same directory... do you have some antivirus, anti spam apps running?

A other member of Frandroid forum has exactly the same issue. But he is running W8.1
That is really strange.

I am running win 8.1 as well

POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)

The problem seems to be resolved by using Windows 7 instead.
http://forum.frandroid.com/topic/223905-tuto-root-de-l-idol-3-55/?p=3417628

using win 7 is not a solution... there have to be a way how to do it, because there are thousands of users with win 8.1 who using fastboot and adb commands...

Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?

is your bootloader unlocked?

And I take it you've enabled Developer Options and USB Debugging?

After all my talk about the ease of communicating with Android devices from a Mac, I'm now unable to successfully issue fastboot commands when in the bootloader. I've tried using sudo, making sure to include arguments that address the device, etc. I can execute adb commands when the phone's system is booted, though. But fastboot commands either get me a "waiting for device" or nothing at all. I thought I was able to do this successfully yesterday, when I was just testing it out. Today, I was going to root by booting into TWRP and flashing SuperSU.

maigre said:
Is it a drivers issue? Does "adb devices" return anything? Or "fastboot devices" if you're in the bootloader? If you don't get a device listed after executing that command, the OS isn't fully recognizing the Icon 3.
I've all but abandoned using Windows for interaction with my Android devices. The driver issues are too big a pain in the butt. With Mac, and no need for installing drivers, the only issue is the occasional usb cable that doesn't work well. I don't mean that as a Mac is better than Windows thing. I use both and am not into these kinds of battles. But it is easier on Mac in this case.
OP, have you tried this with a different USB cable?
Click to expand...
Click to collapse
If it was a driver issue, my phone would not restart with the command, every drivers are OK

ractar28 said:
POThe only thing I can suggest is to change the line
fastboot -i 0x1bbb boot boot.img
to (in your specific case)
c:\users\user\desktop\idol3_6045_root\fastboot -i 0x1bbb boot c:\users\user\desktop\idol3_6045_root\boot.img
and see what occurs.
I'm thinking you may have fastboot somewhere else on your computer as well and that somehow, it's looking in the local directory of that fastboot. While that goes against everything logical (local directory should always be checked first), I'd give that a shot.
If that still doesn't work, open the cmd.exe with elevated permissions (right click "command prompt" in start menu, and run as administrator)
Click to expand...
Click to collapse
Your method worked !!!!!!!!!!!!!!! THX !!!!!

adb android not support on security

Hello, when im trying to change charge mode with command "fastboot oem off-mode-charge" i got message
Minimal ADB and Fastboot>fastboot oem off-mode-charge disable
...
FAILED (remote: not support on security)
finished. total time: 0.013s
Phone is unlocked (checked in fastboot getvar all unlocked: yes)
Phone is Alcatel 1x 2019 with android 6.0
Anyone can help me with it?

I also have the same problem with Hotwav (wheatek) H1 device. Unlocked the bootloader, but when trying to disable off-mode-charge I get the same error. Maybe there is some security setting that needs to be disabled first?

You both are speaking of FASTBOOT, and not of ADB as cited in this theads header.

Yes, but this is changed in fastboot, no? It should work, bu doesn't

I get the same error. And when I enter "adb devices" I get "1023456789ABCDEF unautorized". "fastboot devices" does not show anything

To fix this "unauthorized" error you
1. Revoke USB Debugging on phone
If the device is shown as unauthorized, go to the developer options on the phone and click "Revoke USB debugging authorization" .
2. Restart ADB Server:
Then restarted adb server
Code:
adb kill-server
adb start-server
3. Reconnect the device
The device will ask if you are agree to connect the computer id. You need to confirm it.
It is now authorized!

Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
{
"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"
}

time2fly said:
Doesn't change the original problem. The device appears as "0123456789ABCDEF", and setting "boot on charge" fails with cryptic error message "remote: not support on security". Typical chinese error message.
I am stuck. Can anyone help me? I bought this phone (Soyes XS12) to use it as a GPS car tracker, but what use is it if it doesn't automatically boot when charged.
View attachment 5899259
Click to expand...
Click to collapse
First of all: The command fastboot is for fastboot. The command adb is for adb. When booting into fastboot then adb doesn't work.
To use it in your car as GPS tracker. With an additionally mobile connection? Or only pure GPS? Where is the phone? Somewhere outside the car on the top or well hidden inside the glove box?
Let's assume your phone is able to get a GPS signal. How to track it?

Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.

Looking at it, this seems intentional from manufacturer's side. They can enable it and you updated firmware if you pay a large sum of money. I've tried all the tricks and hacks mentioned in this forum – nothing helped. I don't know why these Chinese phones are so "secured". Trying to force businesses to pay when they discover that something rarely used by ordinary people but essential for some business project is disabled in the stock firmware?

Well, I don't consider "boot on charge" as rarely needed. Everyone who goes to bed at night and uses his phone as an alarmclock needs this. It's not understandable that this is not an option in the settings. And we're talking about Android 9 here!

0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.

time2fly said:
Forget all the GPS info. I just want the phone to boot when I connect it to the charger. I know of the difference between adb and fastboot. I was just experimenting which tool could detect my device. While adb can, fastboot can't, because "0123456789ABCDEF" is obviouslly not a valid device id.
Click to expand...
Click to collapse
Try fastboot oem help to see the available options/features. Maybe there is another corresponding option that needs to be enabled.

alecxs said:
0123456789ABCDEF instead of serialno indicates that is either a fake/clone device or someone has tinkered with that device already. most likely usual fastboot commands won't work. if you have possibility to root that device you can modify the para partition and set off-mode-charge manually.
Click to expand...
Click to collapse
Yes, that was my backup strategy. But how do I root it? There is no TWRP version for the Soyes XS12, and I have no other knowledge of how to root phones. I can seem to send adb commands, but not fastboot.

either with WwR MTK v2.51 beta + SP Flash Tool or with mtkclient. your first goal: dump the para partition or the ROM/boot.img off the phone while in preloader mode. once you have it, you can modify it or root the phone.
mtk-su could also work.

There is nothing you can do even if you root the phone. The system partitions cannot be mounted in r/w mode.

don't need to mount system rw on systemless-root.

Is the Alcatel 9029W rootable?

I just got this tablet a few days ago so I was wondering if it was possible to root it as I already have a primary phone that I use.

Search the WEB for "root any MTK device"

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
Will the method still work even though it's not a MTK device? On CPU-Z it says it's a ARM Cortex device.

ARM Cortex is a processor technology,, what in your case is used by MediaTek when they developed and produced the chipset for your phone.

That seems to make sense. I'll try the method when my laptop charges back up. Thanks for the help

jwoegerbauer said:
Search the WEB for "root any MTK device"
Click to expand...
Click to collapse
The method doesn't seem to work because after doing
adb reboot bootloader
The device just reboots and when I do
fastboot oem unlock, it gets stuck on waiting

What's the method you always are referring to?

jwoegerbauer said:
What's the method you always are referring to?
Click to expand...
Click to collapse
The mtk one you told me about

I was following this to be more specific

The steps to prepare programmatically unlocking a phone's bootloader by means of fastboot what most people do - me included - are
Code:
adb devices <- your phone must be listed here
adb shell "getprop ro.oem_unlock_supported" <- The return value must be 1, if not then don't proceed
adb reboot fastboot <- or: fastboot reboot bootloader
fastboot devices <- your phone must be listed here
to verify the phone is succesfully connected and acting in fastboot ( aka bootloader ) mode.
If phone isn't shown then a fastboot connection doesn't got established.

adb devices - works
adb shell "getprop ro.oem_unlock_supported" - I get a 1
adb reboot fastboot - device just reboots normally
fastboot reboot bootloader - says <waiting for any device>
fastboot devices - just shows a empty line of text

{
"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"
}

You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.

jwoegerbauer said:
You simply confirmed that fastboot isn't working.
Hints:
1. Install its latest version ( -> see my signature )
2. Additionally install the "Android USB Driver" suitable to your phone: with regards to some phones this driver is also needed to make fastboot working - may be your phone is one of these.
Click to expand...
Click to collapse
I've finished doing 1 and 2. Do I retry going into fastboot again?

Oskii said:
I've finished doing 1 and 2. Do I retry going into fastboot again?
Click to expand...
Click to collapse
Do what you think is right ...

It seems that the device is still unable to go into fastboot mode.

I will double check to make sure

In @Oskii 's defense, I've had some Alcatel devices that somehow seemed to have fastboot disabled (namely the Alcatel 1 / Orange Rise 54, IIRC), I don't know how though. It's just impossible to boot into any bootloader/fastboot mode (or at least I never found out how).
I *did* manage to (sort of) root them using a method I don't remember (sorry ; it was an obscure app), but it was unreliable : root wouldn't always "get applied/stick" after boot and I had to reboot and cross my fingers to make it work again.
I know it's not of much help, but still…

It's still not working :v

It cannot without booting to fastboot mode.

fastbbot flash failed <waiting for any device>

I purchased a nice Willeyfox Swift in very good condition with Android 7.1.2. , wanted to install LineageOS + MicroG via ADB.
OEM unlock and USB Debugging Mode enabled, drivers installed, the device was perfectly recognized, bootloader unlocked ("DEVICE STATE- unlocked"),
but then problems started:
When I wanted to flash TWRP via platform-tools, „< waiting for any device >“ appeared. This happened using Windows 10 as well as Mac OS (so I guess, drivers aren’t the problem).
TWRP -package is: „twrp-3.5.0_9-0-crackling,img“
{
"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"
}
Has anyone any idea?
Thanks for help!

ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices

jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Thanks a lot - I skipped "adb reboot bootloader"
Now it works.
Just with a problem often posted along with Wileyfox:
After successfully having installed TWRP, the device only reboots into bootloader, not to system.
But I'll follow this problem on other threads (or do you have an answer?)

finally, I managed it: Thanks to wowi63 , I first intalled Cyanogen, before installing lineageOS. Thank you again for reminding me not to forget <adb reboot bootloader> (I did it before with another device, even had it on my list of procedures, but was just to blind to see...)

I'd like to close this thread

jwoegerbauer said:
ADB and Fastboot are 2 completely different softwares: ADB deals with device's Android OS whereas Fastboot deals with device's bootloader.
To successfully run Fastboot commands you have to establish a Fastboot connection as 1st thing of all things:
Code:
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
I logged into XDA just to thank you very much!
Cant belive I failed something so elementary.
Finally after 2 days I am able to fix my device.
Thanks.