Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
fastboot getvar rescue_version
fastboot getvar rescue_phoneinfo
fastboot oem get-product-model
fastboot oem get-psid (if this has personal information please replace it with X or something.)
fastboot getvar vendorcountry
and let me know what they return.
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works.
Thanks!
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
gnasher666 said:
Hi,
Here's the results from mine:
D:\Mate-8>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B160
finished. total time: 0.016s
D:\Mate-8>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.078s
Click to expand...
Click to collapse
Thank you for checking that!
I'm getting closer to successfully tricking HiSuite into wanting to recover my phone.
Can you please run these commands?
fastboot oem get-product-model
fastboot oem get-psid
fastboot getvar vendorcountry
I think oem get-psid might output personal information. If it does, don't post it obviously. I think the most important one is getvar vendorcountry, potentially, because mine just fails on that. When you post, please post any leading spaces, etc before the text so I have an exact replication of the command.
Thank you!
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
gnasher666 said:
The getvar command didn't work, neither did getvar all.
D:\Mate-8>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L29
OKAY [ -0.000s]
finished. total time: -0.000s
D:\Mate-8>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
D:\Mate-8>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.021s
D:\Mate-8>fastboot oem get-psid
...
(bootloader) SN:23Q7Nxxx
(bootloader) IMEI:xxx
IMEI:xxx
OKAY [ 0.022s]
finished. total time: 0.022s
Click to expand...
Click to collapse
Thank you very much for trying that.
It's strange. It looks like HiSuite sends all of those commands to my phone, the last one is vendorcountry which fails, then tells me my phone isn't supported (even though it lists NXT-AL10 as supported for recovery.)
Would you mind trying the System Recovery option in HiSuite and see what happens for you?
Also, if anyone with NXT-AL10 could please check if HiSuite is able to do recovery when it's in fastboot mode, this would potentially help me discover a universal unbrick method, so please let me know!
Here are the results from my AL10 with international L29C900B133 rom :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.069s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-C900B133
finished. total time: 0.000s
C:\adb>fastboot oem get-product-model
...
(bootloader) NEXT
OKAY [ -0.000s]
finished. total time: -0.000s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5TXXXXXXXXXXX
(bootloader) IMEI:XXXXXXXXXXXXXXX
IMEI:XXXXXXXXXXXXXXX
OKAY [ 0.000s]
finished. total time: 0.016s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.008s
As you can see, getvar didn't work for me neither.
And it seems that HiSuite isn't able to do recovery when it's in fastboot mode, because it doesn't see my phone in this mode...
Hi.
Here are the results of my AL10 with chinese ROM AL10C00B156 :
C:\adb>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.068s
C:\adb>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-AL10C00B156
finished. total time: 0.006s
C:\adb>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-AL10
OKAY [ 0.006s]
finished. total time: 0.008s
C:\adb>fastboot oem get-psid
...
(bootloader) SN:VKN5T15C24012455
(bootloader) IMEI:869906027864873
IMEI:869906027429222
OKAY [ 0.011s]
finished. total time: 0.012s
C:\adb>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.011s
I'll try HiSuite asap...
EDIT : HiSuite (4.0.4.301) recovery doesn't work for me neither : when I click on "Recover system" in the "Entered system recovery mode" screen, it says "Your device does not take care of the recoveries system"...
Thank you very much. So I guess NXT-AL10 is not supported with HiSuite, even though it says it is... Very strange!
It also looks like it's likely there's no way to recover my phone, unfortunately. I might soon give up on trying to find a way to fix it myself (even though I have fastboot...) and send phone to China to see if they can fix it under warranty.
I hope you'll find a solution !
Good luck.
Return from a NXT-L09
duraaraa said:
Hello all,
I'm hoping you guys could help me out. I have a bricked Mate 8 and am trying to fix it.
I'm hoping anyone with a Mate 8 (any and every model) could run these commands for me:
(first please boot to fastboot mode.)
Also, could you let me know if you run HiSuite and choose System Recovery with the device in fastboot, whether you get a 'phone not supported' screen or whether it works."
Click to expand...
Click to collapse
This is what I got:
:\sdk\platform-tools>fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.063s
C:\sdk\platform-tools>fastboot getvar rescue_phoneinfo
rescue_phoneinfo: NXT-L09C212B120
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-product-model
...
(bootloader) HUAWEI NXT-L09
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot oem get-psid
...
(bootloader) SN:AXXXXXXXXXXXXX
(bootloader) IMEI:8XXXXXXXXXXXX
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk\platform-tools>fastboot getvar vendorcountry
getvar:vendorcountry FAILED (remote: Command not allowed)
finished. total time: 0.016s
On the hisuite, I get a message that says my device is not supported, also wifi recovery does not work, Im guessing that happens because I have unloocked the bootloader?
I was able to get an input when running fastboot vendor country. Mine is bricked at least for the moment as well. No go with hisuite to restore.
C:\Users\Malekowsky>fastboot getvar vendorcountry
vendorcountry: dualcu/cn
finished. total time: 0.005s
fastboot oem get-psid
...
FAILED (remote: Command not allowed)
can't get imei info, wich command i can use?
Related
Trying to unlock the boot-loader to install custom recovery in order to flash a new rom
i have the Verizon version , is this possible ?
i keep getting errors from basic commands so i am not sure what i am doing wrong
C:\Android>adb reboot bootloader
C:\Android>fastboot oem unlock
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: -0.000s
C:\Android>fastboot oem unlock UNIQUE_KEY
...
(bootloader) fastboot oem unlock disabled!
FAILED (remote: )
finished. total time: 0.001s
C:\Android>fastboot oem get_unlock_data
...
FAILED (remote: unsupported command)
finished. total time: 0.000s
I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
reynierpm said:
I recently acquire a Moto G GPE, I read several post and also try with this https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and none works. See output:
Code:
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
D:\>cd d:\Software\Android\ADT\sdk\platform-tools\
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem unlock_data
...
(bootloader) 'unlock_data' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.011s
d:\Software\Android\ADT\sdk\platform-tools>fastboot.exe oem get_unlock_data
...
(bootloader) This command is not needed to unlock. Run fastboot oem
(bootloader) unlock directly.
OKAY [ 0.012s]
finished. total time: 0.012s
Any help?
Click to expand...
Click to collapse
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Z-WolF said:
When you are in fastboot mode, what does the seventh line says?
"Device is ******. Status Code: *"
Also, have you tried this code?
Code:
fastboot oem unlock
Click to expand...
Click to collapse
Thanks it was LOCKED but after run the command you suggest me and follow the instructions now I have my device UNLOCKED. Now I'm trying to install this recovery but I can't because I don't know how to install from ZIP, any guide or help?
Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery
xgisse said:
Hi
I'm trying to fix a Moto E that won't boot up, it's stuck on the bootanimation.
I managed to get into fastboot and unlock the bootloader but when I tried to flash TWRP i get this:
C:\Users\Gise\Desktop\fastboot>mfastboot flash recovery twrp-2.8.6.0-condor.img
target max-sparse-size: 256MB
sending 'recovery' (8652 KB)...
OKAY [ 0.297s]
writing 'recovery'...
(bootloader) Battery Low!!
FAILED (remote failure)
finished. total time: 0.328s
I can't flash it because of the low battery and it won't charge because once I exit fastboot it gets on a booting loop
So I tried using this script
@ECHO off
:start
mfastboot getvar battery-voltage
mfastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
and I get this:
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 1.980s]
finished. total time: 1.980s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.008s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.016s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
< waiting for device >
(bootloader) battery-voltage: not found
getvar:battery-voltage FAILED (remote failure)
finished. total time: 0.010s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.006s
and so on...
Somebody help please, i don't even know if the script is working because it won't give me the voltage of the battery
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
Your thread will be moved to Moto E Q&A,Help and Troubleshooting.
Are you able to charge with the device turned off?
___
v7
XDA Assist
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando
velocity86 said:
My mate 9 mha-l29 after a failed update from hisuite (the cell reboot during the update) remains stuck in the screen as show in the image below. no access to recovery emui.
Inviato dal mio SNE-LX1 utilizzando Tapatalk
View attachment 4942543
Click to expand...
Click to collapse
Cannot open the attachment. Anyway, did you resolve - if not, do you remember what was your firmware version and to which version you were trying to upgrade?
Do you have ADB/Fastboot tools installed to PC - if not, you can find on XDA Minimal ADB and Fastboot
Boot the phone to Fastboot (switch the phone off, connect by USB to PC, press and keep pressing Vol- and boot by Pow).
In Fastboot screen, does it show at the bottom that Phone (Bootloader) is locked (in green) or unlocked (red), also does it show that FRP (OEM) is locked or unlocked (you can also attach a photo)
Execute the following Fastboot commands and provide the results back (not from the first command - it's just to check if PC is connected to the phone)
Code:
fastboot devices
PAUSE
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
Thanks for the help. I hope to resolve the problem
C:\ADB>fastboot devices
AHK7N16B02001730 fastboot
C:\ADB>fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.000s]
finished. total time: 0.000s
C:\ADB>fastboot oem get-product-model
(bootloader) MHA-L29
OKAY [ 0.017s]
finished. total time: 0.017s
C:\ADB>fastboot oem get-build-number
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot oem oeminforead-SYSTEM_VERSION
(bootloader) :MHA-L29 8.0.0.379(C432)
OKAY [ 0.016s]
finished. total time: 0.016s
C:\ADB>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
hi,
I tried to use the unlock.cmd in command promt via fastboot, half of it worked it only unlocked my frp but it said "failed: Unknown Command !". Please help, is there any other way I can unlock my bootloader? My max pro m1 won't boot and doesn't have access to recovery mode. Thanks
C:\adb>C:\adb\unlock.bat.cmd
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is user
target reported max download size of 536870912 bytes
sending 'IMAUOvZqcpug' (0 KB)...
OKAY [ 0.002s]
writing 'IMAUOvZqcpug'...
(bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.005s]
finished. total time: 0.009s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.003s
All is download
Maybe update your adb/fastboot