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 .
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
stygianblizzard said:
Hi All,
I know I have messed up, but want to know is there any remote possible way to do this?
I tried to flash and it failed and on top of that I used
Code:
fastboot oem lock
which has made it even more miserable. I am not able to recover anything now. This what I have tried to unlock OEM -
Code:
C:\>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.014s
C:\>fastboot oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.029s]
finished. total time: 0.031s
I tried to install Google Stock by pressing on flash-all -
Code:
error: cannot load 'bootloader-shamu-moto-apq8084-71.08.img'
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: cannot load 'radio-shamu-d4.0-9625-02.95.img'
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
error: failed to load 'image-shamu-lmy47i.zip': No such file or directory
Press any key to exit...
Screens have been attached
Is there any remote possibility on what can be done?
What I learned is when new stuffs arrive study it properly before messing with it around :laugh:
Click to expand...
Click to collapse
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
gee2012 said:
If you don`t have TWRP installed you`re screwed and you have to send it in for repair .....
Click to expand...
Click to collapse
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
stygianblizzard said:
Ya its there... I switch to TWRP or bootloader and trying to experiment more to get out of it. Thing is I am not able to flash anything. I tried pushing google stock files using ADB commands but when I am trying to install them its failing.
Click to expand...
Click to collapse
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
TWRP cannot flash the stock images. Only flash able zips. The modified zips linked by @gee2012 should work
gee2012 said:
Try this: Reboot to bootloader, select recovery mode, enter TWRP, mount MTP and push/sideload and flash a flashable image from here http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052.
Click to expand...
Click to collapse
Just few mins got img downloaded. That was bloody awesome. I dont know how to thank you :laugh::laugh::laugh::good:
Superb
Its working again!!!!!
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.
I have unlocked my phone, and i tried to reinstalling but there was an error:
Code:
E:\Minimal ADB and Fastboot>fastboot flash recovey "E:\DOWNLOAD\twrp-3.4.0-0-xmsirius (1).img"
target didn't report max-download-size
sending 'recovey' (33576 KB)...
FAILED (command write failed (No error))
finished. total time: 0.036s
Anyone gotten any ideas on what could be going on here? Please help me!!:crying::crying::crying:
If you have an usb hub or an old computer use them.
Or enter the command then connect your phone.
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
warmachine20 said:
c:\adb>fastboot devices
7XVKYLNZROBAIVFQ fastboot
c:\adb>fastboot oem unlock
FAILED (remote: 'unknown command')
Finished. Total time: 0.009s
Click to expand...
Click to collapse
I have the same device, the same issue.
i have 5033F
the same issue
fastboot flashing unlock_critical
FAILED (remote: 'not allowed in locked state')
Finished. Total time: 0.003s
OEM Unlock enabled in developers option