Hi all,
I have an issue where my device is not recognized by adb when in recovery.
it shows something like below when in recovery
adb devices
000000000 device
when is device is in fastboot
fastboot devices
it shows the serial number
but when i run command
fastboot reboot
rebooting...
finished. total time: 0.001s
and the device wont reboot,
also other fastboot commands like
fastboot flash recovery /(whatever path) will end up with some error
Please can any one help me out with this...
FYI: all commands in adb work fine with my Nexus one but these are the issues with HTC hero G2.
Wrong section, this should be on Q and A
If you are on linux try sudo adb kill-server and then sudo adb start-server
EDIT: Issue has been resolved
I managed to get the bootloader unlocked and root the phone before. But then i got a bit carried away and installed adAway incorrectly. Which got me into a bootloop.
I freaked out, and i ended up messing things up even further by trying to restore the phone.
I did perform a backup in TWRP. But this backup did not help at all.
Then i tried using fastboot to relock the bootloader. The reason for this would be so that i could use the eRecovery.
That did not work.
I have used both Minimal ADB and P8lite Multitool.
None of these tools detect my phone unless i put it into fastboot manually.
If i try to reboot through the tools, it will reboot, but only to the Huawei logo and stay there.
I have been able to flash the very latest rom from Sokkoban http://forum.xda-developers.com/p8lite/general/rom-emui-4-0-android-6-0-ale-t3505108
(thank you by the way for all the hard work)
But when i try to relock (with update.app in the dload folder) i keep getting errors.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb.exe reboot recovery
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock XXXXXXXXXXXX
< waiting for any device >
...
FAILED (remote: Command not allowed)
finished. total time: 0.019s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem relock XXXXXXXXXXXXX
...
FAILED (remote: root type is risk)
finished. total time: 0.901s
Click to expand...
Click to collapse
My stock buildnumber is (was?) ALE-L21C432B574. I still haven't found the proper stock rom.
I can see 2 IMEI numbers, so i guess this is a dual sim?
I have already got the phone replaced once. I don't know if i would be so lucky as to have it replaced once again, even though it is under warranty. Well technically it isn't. Nor was the other one.
I just wish to have this paperweight back in working order again.
TL;DR:
Power + Volume down = Fastboot
Power + Volume up = Nothing.
Volume up when in Fastboot = eRecovery. eRecovery will not download anything as the phone is rooted.
Reboot = Stuck in Huaweilogo.
Phone is not detected by HiSuite.
Edit: I did manage to find the stock rom (i think)
http://www.carbontesla.com/2016/07/download-huawei-p8-lite-b574-full-marshmallow-firmware-europe/
And i am back in business. The phone is no longer a brick, but it is not rooted.
Hi
I am trying to relock the BL for warranty.
I did a EDL-FULL-Nougat, then found out that Nougat does not boot into bootloader.
So I downloaded A2017G_NrollbackM from ZTE, which worked nicely. I'm in bootloader now and see
Code:
C:\>fastboot getvar unlocked
unlocked:
finished. total time: 0.008s
which was expected.
... just I don't understand, why I can't lock or get oem device-info
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
please help, thanks alex
did you enable 'oem unlock' on the developer settings?
yes, sorry forgot to add
lxlx said:
yes, sorry forgot to add
Click to expand...
Click to collapse
so i guess you have been able to lock it?
No, I mean I forgot to add that info in my first post.
I can not run device-info or lock, log posted.
Cheers :/
your Fastboot.exe is too old
Choose an username... said:
so i guess you have been able to lock it?
Click to expand...
Click to collapse
but you didn't even respond to my question
did you enable 'oem unlock' on the Developer settings?
skdubg said:
your Fastboot.exe is too old
Click to expand...
Click to collapse
that sounds promising, where to get the up-to-date fastboot.exe?
Choose an username... said:
but you didn't even respond to my question
Click to expand...
Click to collapse
I tried, but my non-native english failed apparently.
So to be clear:
Choose an username... said:
did you enable 'oem unlock' on the Developer settings?
Click to expand...
Click to collapse
yes I had oem unlock in dev-options enabled. Then I tried
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
Post deleted. Didn't notice you are on mm.
lxlx said:
that sounds promising, where to get the up-to-date fastboot.exe?
Click to expand...
Click to collapse
The 15 seconds ADB installer should install the newest fastboot available. But be sure to get rid of the old installation
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
lxlx said:
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
Click to expand...
Click to collapse
This hasn't got anything to do with the drivers. I mean, delete the fastboot.exe and adb.exe that you have, then download the "15 seconds ADB installer" and install it, and try again
OK, a bit more digging.
I have 15sec-adb installed systemwide in C:\adb>
Code:
C:\adb>dir /B
aboot.img
aboot_lock.img
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
strings.exe
as you can see, I put my aboot dumps there as well, and a strings-linux-like tool - after
reading this thread.
so, I got the ZTE driver to have my Axon7 visible to adb/fastboot (otherwise no device) ... and I have the latest 15sec adb here.
Code:
C:\adb>fastboot devices
823b48f5 fastboot
... but that's the only thing that works. not even easy things like this do
Code:
C:\adb>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.015s
quoting the other thread
What’s missing in this list are fastboot oem commands. These commands are specific to Android device manufacturers, and there is no comprehensive list or documentation anywhere for what fastboot oem commands are available.
Click to expand...
Click to collapse
so I'm not sure if my fastboot version is the problem. I rather think that the Nougat->MM stock thingy, overwrite my Axon7 aboot.img with only a small set of fastboot commands available.
in my backup I see
Code:
C:\adb>strings aboot* | findstr /i oem
C:\adb\aboot.img: 04 0004 OEM_ID1
C:\adb\aboot.img: oem unlock is not allowed
C:\adb\aboot.img: oem unlock
C:\adb\aboot.img: oem unlock-go
C:\adb\aboot.img: oem lock
C:\adb\aboot.img: oem device-info
C:\adb\aboot.img: is_oem_unlock_allowed
C:\adb\aboot_lock.img: 04 0004 OEM_ID1
C:\adb\aboot_lock.img: oem unlock is not allowed
C:\adb\aboot_lock.img: oem unlock
C:\adb\aboot_lock.img: oem unlock-go
C:\adb\aboot_lock.img: oem lock
C:\adb\aboot_lock.img: oem device-info
C:\adb\aboot_lock.img: is_oem_unlock_allowed
so in old and new aboot I had oem-commands available, back then...
I'm not an expert, but do you guys really know that my problem is related to the PC-config I have, and not to the device-config?
I can not check aboot on device, as I'm not root.
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
lxlx said:
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
Click to expand...
Click to collapse
Pretty sure miflash cannot lock your bl.
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
lxlx said:
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
Click to expand...
Click to collapse
I think it is still unlocked. I read something weird about the message not appearing after having a full stock system
But if you're gonna sell it/claim warranty, who cares?
update, ZTE repaired the display
lxlx said:
update, ZTE repaired the display
Click to expand...
Click to collapse
Did you lock the bootloader after all?
I guess they wouldn't even notice if the 5 sec screen didn't show up lol
BL still unlocked.
I sent it with MM-B10-FULL-EDL, where 5sec screen was not displayed.
And got it back with MM-B06 ... with 5sec screen
so I guess what happened:
- ZTE turns on, does not see 5sec, repairs display, does usual EDR 'update' which is actually a downgrade to MM-B06, then sees 5sec-warn and thinks of what to do now, but as screen is repaired, what else than return
OR
- ZTE repairs screen (VIP) although bootloader unlocked
either way, all good.
what I learned is
- fastboot parameters need to be in aboot.img
- I can't do getvar or oem-lock until I flash another aboot.
Anyone with A2017G and unlocked BL who needs to send back:
EDL to A2017G_B10_FULL_EDL.zip
and hope you also have hidden 5sec screen (BL still unlocked)
Hello,
I'm new to this forum, so please excuse me if this is not correct section to post.
I'm more used to Samsung and ODIN, first time i encounter this situation with Huawei
Here is the situation.:
Had to replace a LCD of a Huawei P10 Lite for a client. (WAS-LX1A model)
I did it, without issue...
Tested the replacement LCD (without glue it) display OK touchscreen OK
It went to the welcome screen asking for the PIN code to unlock the screen/
Ok so i turn it off.
Finish the replacement fix
Turning it back i got infinite loopboot ... showing HUAWEI logo , and rebooting all the times....
Trying to go to recovery mode holding VOL+ VOL- without success
The only key giving a reaction is VOL- going to FASTBOOT
This is the information i got the first time i went to FASTBOOT
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
( i did it but the phone is NOT detected in HiSuite,
but the phone is recognized on my Devices Manager of my Windows 10 laptop
under the name
KEDACOM USB DEVICE
> Android Bootloader Interface
so to continue what i had on my screen 1st time i went into Fastboot
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
Android reboot reason:
coldboot 16
NA
volumnkey_down_press_process_func
Phone Locked
FRP Lock
Click to expand...
Click to collapse
:'(
I don't understand why i get the FRP lock, usually its when you format and try to bypass the password of the google account (usually occuring when trying to ovveride this protection with stolen smartphones...) but here its not the case.
A few minutes before the smartphone asked me to encode the PIN code of unlocking screen (for my client its not a schema its a PIN code) i just tried 2 numbers and i even not validated my input i just turned off the phone ....
Well anyway, no when i go again in the fastboot the message is different and is always this one now
FASTBOOT&RESCUE MODE
Please Connect USB cable to your computer and open HiSuite
Android reboot reason:
AP_S_PMU 144
ocp_ldo17 ocp_ldo31
volumnkey_down_press_process_func
Phone Locked
FRP Lock
Click to expand...
Click to collapse
What have i tried already ?
i downloaded a TWRP image of 22 MB , installed " Minimal ADB and fastboot " SDK
with ADB i can't see the device
with FASTBOOT i can list the device
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
2XJ7N17406000665 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
but any other command (except fastboot reboot) fails,
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery_ramdisk p10twrp04.img
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (24954 KB)...
OKAY [ 0.736s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.748s
C:\Program Files (x86)\Minimal ADB and Fastboot>
....So what should i do next ?
Enabling the Developer Debbung USB option in the menu of the smartphone ?
How come ? the phone can't boot android so i can't access the options menu ..... :'(
Thanks in advance for you help
Try this - https://forum.xda-developers.com/p10-lite/development/service-rom-b362-c432-upgrade-o-o-n-o-t3813946
Same problem, I have changed LCD and the touch does not work if I restart, if I do it in hot it works.
Does anyone know any solution? Thanks
Guys, I need some help!
I've factory reset my Redmi Note 7, it was already rooted with TWRP recovery and unlocked bootloader. Then it got to TWRP GUI and I swiped to reboot the device and it says the system is destroyed.
MI Unlock tool and fastboot can't boot or flash:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.004s
MiFlash disconnects my device every time i click refresh
If I try fastboot boot recovery.img or twrp.img it says I cant flash because my phone is locked.
I can't boot the device to enable usb debug because is bricked and now it says it's locked and I can't flash nothing.
What should I do?
XablauSoares said:
Guys, I need some help!
I've factory reset my Redmi Note 7, it was already rooted with TWRP recovery and unlocked bootloader. Then it got to TWRP GUI and I swiped to reboot the device and it says the system is destroyed.
MI Unlock tool and fastboot can't boot or flash:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.004s
MiFlash disconnects my device every time i click refresh
If I try fastboot boot recovery.img or twrp.img it says I cant flash because my phone is locked.
I can't boot the device to enable usb debug because is bricked and now it says it's locked and I can't flash nothing.
What should I do?
Click to expand...
Click to collapse
I think u again locked ur BL from mi flash while flashing u forgeted to untick the option "flash all and lock" In mi flash. Try to flash recovery again from fastboot. Fastboot flash recovery recovery.img if it sayd device locked then unlock bl again by mi unlocker.