After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
I've been trying other things with no success.
I've installed windows on a VM and rebooted the phone into fastboot mode. When I try to list devices in fastboot I get the '?' answer as if the phone wasn't recognised.
Device drivers seem to be installed as no missing drivers appear in the device manager.
How can I fix this?
Thanks in advance!
UPDATE: Added some more info
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot.exe getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.017s
antoniovazquezblanco said:
After installing B126 in my rooted P7 I'm unable to use fastboot although the phone shows unlocked bootloader in the screen.
Code:
$ sudo adb reboot bootloader
$ sudo fastboot devices
???????????? fastboot
The device seems unrecognised and when I try to flash or boot anything I get the following error:
Code:
FAILED (remote: Command not allowed)
On the other hand I'm able to reboot via fastboot command.
I'm using linux and running fastboot and adb as root in order to ensure I have permissions to access to de device although this shouldn't be necesary.
Why could this be happening?
Thanks in advance.
Click to expand...
Click to collapse
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
g4b3rm4n said:
Did you make the
Code:
/etc/udev/rules.d/51-android.rules
file? It is necessary to create it with the correct information to make ADB work on Linux.
If you don't have the file, read this: http://askubuntu.com/questions/213874/how-to-configure-adb-access-for-android-devices
The first answer explains how to create the file. You don't need to be root to use ADB by the way.
Click to expand...
Click to collapse
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
antoniovazquezblanco said:
Thank you very much for your time and patience!
AFAIK changing udev rules only lets you use the USB devices with your regular user avoiding the need of elevated permissions. Anyway, because I had nothing to loose I've tryed the solution you adviced. Here are the results...
After creting the udev rules for my user I no longer need to use the sudo command for getting results with adb or fastboot, which was expected, but I keep getting the "Command not allowed" with fastboot.
Code:
$ fastboot oem ?
...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.000s]
finished. total time: 0.000s
$ fastboot getvar ?
getvar:? FAILED (remote: Command not allowed)
finished. total time: 0.000s
$ fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
On the other hand, fastboot devices now returns something interesting...
Code:
$ fastboot devices
0123456789ABCDEF fastboot
Any other hint?
Thanks in advance!
Click to expand...
Click to collapse
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
g4b3rm4n said:
Well, the bootloader seems to be fine and the fastboot ID "0123456789ABCDEF" seems to be also OK (according to this thread it means "the device is in fastboot mode"). My guess is a permission problem - is the device rooted? Also, this thread's resolution for this error message was turning debugging mode on - so you might want to check that too
Click to expand...
Click to collapse
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
antoniovazquezblanco said:
My device is in B609 not rooted because the method used still not very convincing to me... Could it be this?
Debugging is enabled...
Thank you very much!
Click to expand...
Click to collapse
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
g4b3rm4n said:
If think yes, it might be. It surely looks like a permission problem, and since you are not rooted, it could be that those commands can't be used.
Rooting B609 was pretty hard for me - I flashed the bootloader of B608, then used CWM to flash SU, and then I was 100 percent rooted. If you don't want to root your phone, I'll try tomorrow (or later today - it's 0:50 here and see if fastboot commands work properly when rooted. What commands should I try?
Click to expand...
Click to collapse
Is this also happening to you?
I would like to be able to use fastboot boot for some kernel testing... It seems there's source code for kernel building both from Huawei and the comunity and it would be nice to have a free kernel as a base for cm devel...
It is also 00:50 here (Spain)... Tomorrow will be another day, no hurry
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Kostyan_nsk said:
1. After editing udev rules, fastboot recognizes your device correctly ('fastboot devices' returns your device's SN).
2. Presence of su doesn't affect on work of fastboot anyhow.
3. You can't use 'fastboot boot' command because it's not supported. Huawei's bootloader supports very limited set of commands.
Click to expand...
Click to collapse
Thank you Kostyan_nsk! I really appreciate you sharing your knowledge .
About 2 I thought the same but I was not sure... so why not trying...
About 3 do you know what are the supported commands or where to find that information? It would be nice to have a post in the developers section with some documentation for those who want to perform tests with the device .
I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
ravi_buz said:
I had unlocked, installed dual recovery and rooted my phone with LP. This latest update (270) removed my root and locked my bootloader (Service meuu says unlock allowed = Yes) . I tried to unlock it again using flash tool and adb cmd and both seem to fail. In flashtool it keeps saying that my code is wrong (I created a folder in custom folder with ulcode name and a txt file with the ulcode) still din work. In adb cmd i am getting
version: 0.5
finished. total time: 0.003s
FAILED (remote: Command did not succeed)
finished. total time: 0.021s
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
I have installed all drivers in my system too. Any help?
Click to expand...
Click to collapse
Try unlocking from Sony's site ( official method ) http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
Good Luck :fingers-crossed:
Found the solution
Please check my post here http://forum.xda-developers.com/showpost.php?p=61450689&postcount=390
I recently discovered that my phone had already lost its DRM keys (purchased the phone second hand). So I decided I wanted to unlock the bootloader to install the DRM fix to see if that improves my camera quality.
I have followed all of the guides I can find and have attempted to troubleshot it, however nothing seems to be working.
This is the error I am getting:
Code:
C:\Flashtool\x10flasher_lib>fastboot -i 0x0fce oem unlock 0xKEYHIDDEN
...
FAILED (remote: Command did not succeed)
finished. total time: 0.022s
C:\Flashtool\x10flasher_lib>fastboot -i 0x0fce oem unlock 0xKEYHIDDEN
...
FAILED (remote: Device is already rooted)
finished. total time: 0.004s
C:\Flashtool\x10flasher_lib>
I have tried creating a folder in the flashtool folder with my device id and ulcode.txt with the unlock code in it, same result.
Any suggestions on what I could be doing wrong?
So I realized what I was doing wrong today.
When I was creating the folder in flashtool with my device id and unlock code, I was creating a file named ulcode.txt.txt instead of ulcode.txt. When creating a txt document, it is not necessary to add the file extension.
Silly mistake, however I thought I would post it just in case anyone else encountered this "issue".
I'm trying to allow bootloader unlock but keep getting the error above. I've seen various posts on this in the past but am still stumped after doing the following :
- the phone is an xperia Z3 compact
- enabled Developer options
- enabled USB debugging
- allowed installation of apps from unknown sources
- set 'Install software' with USB Connectivity
- unlocked sim (network unlocked)
- received unlock code from Sony
- running software on Ubuntu linux
Commands I've run
=================
fastboot -i 0x0fce oem unlock 0xB9D9999DF99BDB9A
...
FAILED (remote: Command not allowed)
finished. total time: 0.003s
[email protected]:~# fastboot getvar version
version: 0.5
finished. total time: 0.002s
[email protected]:~# fastboot devices
YT9110A9BX fastboot
Anybody got any other ideas ? Thanks in advance.
I think the problem is that the setting of "Bootloader unlock allowed: No" can't be unset other than by Sony. I have contacted them but I'm not holding my breath.
Hi frend.
What do I have!
HTC 626G is written in the phone and on the box.
HTC 626ph on the phone cover.
626G and 626ph = from one box at purchase
CPU MTK6592
Android 4.4.2
build 1.78.401.100 and 1.79.401.100
When you enter commands: fastboot
fastboot: getvar version
fastboot out: getvar:version FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar version-bootloader
fastboot out: getvar:version-bootloader FAILED (remote: not support on security)
finished. total time: 0.003s
fastboot: getvar version-main
fastboot out: getvar:version-main FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar serialno
fastboot out: getvar:serialno FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar product
fastboot out: getvarroduct FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar modelid
fastboot out: getvar:modelid FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar cidnum
fastboot out: getvar:cidnum FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar build-mode
fastboot out: getvar:build-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar boot-mode
fastboot out: getvar:boot-mode FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar security
fastboot out: getvar:security FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: getvar imei
fastboot out: getvar:imei FAILED (remote: not support on security)
finished. total time: 0.002s
fastboot: oem get_identifier_token
fastboot out: ...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem get_identifier_token - error!
$ fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.003s
Click to expand...
Click to collapse
fastboot oem unlock - error! Unlocked, perhaps?
$ fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7000
)
finished. total time: 110.541s
Click to expand...
Click to collapse
I made backups
Backup HTC 626G 1.79.401.100 (for SP Flash Tool)
Backup HTC 626G 1.78.401.100 (for SP Flash Tool)
Backup HTC 626G 1.72.401.101 (for SP Flash Tool)
Instructions such!
If their upload to the phone via SP_Flash_Tool_v5.1348.01_SEC + download_agent MTK_AllInOne_DA.bin, phone is loaded. but there is no picture on the display (LСD), only backlight.
I have even copied preloader! by command dd if=/dev/preloader of=/mnt/sdcard/preloader.bin count=262144 bs=1 When copying he 256 KB. STOCK 1.79-1.78 Preloader
if it is open WinHEX and to edit the original 114kb (as in 0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4) and downloaded into the phone, it does not start. Not respond to the button.
Upload preloader in Backup HTC 626G 1.03.707.1 (для SP Flash Tool) (0PM1100_A32MG_DUG_K44_SENSE53_htc_asia_1.03.707.1_Radio_MOLY_WR8_W1315_MD_WG_MP_V62_P4)
Phone is turned on. No image, just backlighting. but it works.
There are still a similar patient. After loading TWRP recovery, It hangs on the splash screen HTC and reboots (bootloop). When downloading files from a backup of the original, nothing changes. (bootloop)
I can not understand why I can not get them to work. What else can be done?
Three weeks I can not understand.
I recommend to view a selection of photos on my topic.