i recently tried to update my huawei p8 lite to android marshmallow 6.0
i unrooted and my bootloader is unlocked.
as the phone rebooted to finalize the installation it rebooted immediatly at 0% and kept rebooting and showing "huawei software installing 0%".
i managed to boot it in fastbootmode but everytime i try to reflash or do anything with it i get the error "remote:command not allowed"
every time i reboot or drain the battery it just goes to the "huawei software installing 0%" screen and starts the loop anew.
how to fix this? or should i just return it to them?
Try this post, start with 1 that should be enough :
http://forum.xda-developers.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
You can also download the file from this post and try installing the stock recovery:
http://forum.xda-developers.com/p8lite/help/upgrade-android-5-1-1-b008-ale-21-t3285993
olrak said:
Try this post, start with 1 that should be enough :
http://forum.xda-developers.com/p8lite/general/huawei-p8-lite-android-6-0-marshmallow-t3309796
You can also download the file from this post and try installing the stock recovery:
http://forum.xda-developers.com/p8lite/help/upgrade-android-5-1-1-b008-ale-21-t3285993
Click to expand...
Click to collapse
i cant do anything with fastboot. everytime i try to flash or even view something it says (remote:command not allowed)
Try reinstalling your drivers from your computer.
Remove the driver for the fastboot device and try to reinstall them. Use a good resource for the drivers. Like google or huawei etc.
You can also try to download HiSuite 4.04.301 en try system recovery.
olrak said:
Try reinstalling your drivers from your computer.
Remove the driver for the fastboot device and try to reinstall them. Use a good resource for the drivers. Like google or huawei etc.
You can also try to download HiSuite 4.04.301 en try system recovery.
Click to expand...
Click to collapse
i cant use hisuite because my phone is in a bootloop and i cant install new drivers because it says (remote:command not allowed) everytime i try to do something even remotely related to my phone in fastboot
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
olrak said:
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
Click to expand...
Click to collapse
installed new drivers still cant issue any commands
olrak said:
hisuite, oké
install new drivers = on your computer, not on your phone.
when you are in fastboot, go to your computer settings and remove the fastboot device or update the drivers for that device.
Click to expand...
Click to collapse
i think usb debugging is disabled does that have any impact on the situation?
That's not an issue, usb debugging is only necessary when you can startup to android. Try googling, whill do that too.
xileftrepur said:
i recently tried to update my huawei p8 lite to android marshmallow 6.0
i unrooted and my bootloader is unlocked.
as the phone rebooted to finalize the installation it rebooted immediatly at 0% and kept rebooting and showing "huawei software installing 0%".
i managed to boot it in fastbootmode but everytime i try to reflash or do anything with it i get the error "remote:command not allowed"
every time i reboot or drain the battery it just goes to the "huawei software installing 0%" screen and starts the loop anew.
how to fix this? or should i just return it to them?
Click to expand...
Click to collapse
Is the bootloader unlocked?
If not, you'll need to unlock it first in Fastboot (you can use DCUnlocker for it, if you don't want to wait the 14 days for Huawei to do it).
Same Problem.
Exactly the same problem.
I've already posted into the other topic, but I post it here as well.
daviddosa said:
Looks like you've used the KingRoot method to root your phone.
Flashing via fastboot requires the fastboot to be unlocked.
The message "FAILED (remote: Command not allowed)" indicates, that the script tried to execute the command, but because the bootloader is still locked, it cannot do such thing.
There are 2 solutions:
Download the original firmware and try to update to it via the "dload" method. (sdCard>dload>UPDATE.APP)
Try to unlock the bootloader. But for unlocking, you'll need the Product ID, which as of now, only obtainable, when the phone is able to boot up.
I really recommend trying to download the firmware, and give the "dload" method a shot, because without an unlocked bootloader, nothing you can do at home.
Right, it's almost nothing. There's this site called DC-Unlocker, and with a fast runthrough, it should be able to unlock the bootloader, but I haven't tried, or tested it in any way. Still an interesting program, though.
Edit:
Just saw your post under the other similar topic.
You should try to do a Factory Reset, by hand, via fastboot, and then updating with the "dload" method again.
The commands are:
fastboot erase cache
fastboot erase userdata
Maybe this helps.
Click to expand...
Click to collapse
Hi I am Rupesh from India and I have lenovo a3000H and I am using it from past three years and I am bored with it and so I have downloaded cm 5.1.1 from your site.
I have tried a lot to root the device at first I have installed framaroot and after that I have installed superuser app which gave error as their is no su binary installed.
In order to unlock the bootloader I have installed android studio and USB drivers provided by the device vendor. When I connect the tab to Windows 8.1 system I am able to see an entry named lenovo a3000 under portable devices in device manager.
When I issue the command adb devices on command prompt of my pc I am able to see a serial number followed by the word device. When I issue the command adb reboot bootloader instead of entering into fastboot mode my tab is restarting itself after that when I issue the command fastboot devices I am unable to see no output.
Previously I have tried to backup my tab storage from PC using adb and my tab asked for confirmation but no backup was performed.
I think that fastboot is unable to detect the device.
I am unable to root my tab with using PC or without using PC.
Please suggest how to root my tab properly.
Regards,
Rupesh.
Before performing the above I have enabled USB debugging and became developer by tapping 7 times build number in about phone.
Hello,
I have a problem with my Huawei P9 Lite. Build number is: VNS-L31C900B161
Whenever I try to flash twrp using adb I get the message
"writing 'recovery'...
FAILED (remote: Command not allowed)"
My bootloader is unlocked and I just flashed a new firmware. My main goal to to switch to yet another firmware since the one I'm on right now doesn't allow me to open the Play store.
I want to switch to C432 in order to be able to update through the stock recovery (C900 firmwares are nowhere to be found) and I read in another thread that I need to flash oem info using TWRP. If anyone knows another way I'd appreciate some directions.
Oem unlock aswell as USB debugging are enabled.
I'd greatly appreciate any help.
Hello! I have a very similar problem with my P8. Unfortunately so far no one has ever been able to help me. Previously I had 2x Huawei P8 and one P9.I modified all the different methods. I've had some time to learn but this case is beyond my skill.
In my case also the bootloader - unlocked (all known methods for verifying bootloader status show that it is unlocked). Because my phone is connected to a computer running Windows 10 64b tried the methods without the driver signatures (quieter I do not think that is the problem in this because other P8 unlocked on the same computer, the same ADB drivers etc ...) I've tried adb over wifi and even these dubious methods without using a PC. Nothing. The only response: "Command not allowed ". Maybe I will add that dedicated tools type SRK Tools , HWMultitool, WinDroid ToolKit They perform a normal TWRP boot procedure and show that the procedure was successful (!!!) .... and nothing. Black magic. So far in 3 different sites they could not explain it to me.Finally, I will add that this particular P8 is a copy that I got under warranty (previous P8 unfortunately fell but honestly gave me a whole new ... But without any box, Without anything, the phone itself ... Any such blockade made in Huawei?
me2
Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10
I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.
Can't anybody help us?
Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me
Format data?
What your twrp version ? your twrp version must be version support 11.
You cant flash Magisk via TWRP. It doesn't work, Install the magisk App
Wrong place to ask this stuff