I messed up trying to root my phone but i found a way to fix by flashing to a newer firmware and the phone worked!
I tried to root again but this time i didnt enable developer option/usb debugging and now im stuck at bootloader screen
i cant enter recovery mode and i cant start the device.
im getting Slot _a is unbootable error message
i tried fastboot set_active _b but still getting same error..
fastboot flashing unlock doesnt work anymore because i dont have usb debugging ON
fastboot oem unlock -- getting this message
...
FAILED (remote: unknown command)
finished. total time: 0.004s
fastboot oem device-info ----------- (bootloader) Device unlocked: false
am i completely screwed?
sorry for the bad english
edit: im on version 1908,25 Global
EDIT: solved by this guide https://forum.xda-developers.com/rog-phone-2/how-to/guide-convert-cn-to-ww-rom-26-08-t3961042 THANK YOU SO MUCH
Related
Hi!
I'm trying to install TWRP on my P10. I've unlocked bootloader on Huawei website.
Whenever I'm typing in fastboot "flash recovery twrp.img" it goes through and everything says OK
But when i try to "fastboot boot twrp.img" I get FAILED (remote: command not allowed)
"fastboot oem device-info" gives me the same error too and "fastboot oem unlock" gives me already fastboot unlocked
What do you thing "fastboot boot twrp.img" should do? This command isn't allowed because it does not exist.
If you want to boot into your flashed TWRP recovery, you have to enter "fastboot reboot" and press volume up while booting - the USB cable has to be disconnected.
Instead of "fastboot oem device-info" try "fastboot Gevtvar unlocked".
or use adb when the phone is running.
"adb reboot recovery"
you can't go direct from fastboot to recovery simply by a command
Yeah, the command was wrong, sorry xD
Anyway I thinks it's fixed now and I'm able to boot manually to recovery from phone now!
jejeje i was coming here to tell you about wrong command
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
do you have instaled driver for P10, does computer recognice device like P10 ?
DiMeteo24 said:
I have the same problem with FAILED (remote: command not allowed). When I try to install or flash anything I see the info about FAILED (remote: command not allowed). I have FRP locked and I can't enable OEM developing option (it is inactive). I can't relock bootloader, can't instal TWRP, I have only simply erocevery where I can't wipe - only reboot and shutdown device.
I tried do update via dload, hwota - all with defeat
In ADB and Fastboot I can see my device connected.
Does anyone have any idea?
Click to expand...
Click to collapse
Any news? My p10+ it's in the same case
same problem im already unlock but the twr not install what is propper command
Hey guys, for all of you with "command not allowed" problem, you have to check OEM unlock setting on developer options but if you have a greyed out button, you need to flash again your stock room with a tool like dc-phoenix unlocker and bypass frp lock (on YouTube you will find tons of videos regarding this matter). Also, you can check if your Fastboot is protected (frp locked) on Fastboot screen...
There you go---> https://forum.xda-developers.com/hu...ution-bl-unlockedfrp-locked-fastboot-t3684302
PS READ the post to the END!! don't make mistakes it's really easy and fast. It works!
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Armand Bernard said:
Hi guys.
I know this thread is pretty old but I'm getting the exact same problem as the OP except on my P20 Pro: I can flash a recovery but not boot one from fastboot.
The biggest difference is that my bootloader is unlocked and I have FRP Unlock, so according to every post I've seen it SHOULD be working.
My fastboot log:
PS C:\adb> fastboot devices
LCL0218415002142 fastboot
PS C:\adb> fastboot boot twrp-3.2.1-0-charlotte.img
downloading 'boot.img'...
OKAY [ 0.187s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.187s
Click to expand...
Click to collapse
Have you try this command fasboot reboot recovery_ramdisk?
I get:
PS C:\adb> fastboot reboot recovery_ramdisk
fastboot: usage: unknown reboot target recovery_ramdisk
with "fastboot boot recovery_ramdisk" I get
error: cannot load 'recovery_ramdisk': No such file or directory
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Question
Armand Bernard said:
I sorted out my problem from a different angle so I no longer need to boot to TWRP from fastboot. Thanks for your help!
Click to expand...
Click to collapse
Could you please tell me how did u solve this problem. thx
darkdante13 said:
Could you please tell me how did u solve this problem. thx
Click to expand...
Click to collapse
This was quite some time back so I don't remember all that well, but I think I just used the built in Huawei recovery, erecovery, to restore my whole phone and then I was able to reinstall my custom recovery and boot to it normally. I can't guarantee this as I don't remember the whole context of this. Using erecovery I didn't lose my locally stored files, only my apps and app data. Hope this helps.
can anyone help me. my p9 stuck on Your Device Has been unlocked and can't be trusted.
cant go in twrp and won't power off only i can do is going in fastboot. but every time flash on fastboot it always failed (remote unknown command)
my phone status when fastboot is PHONE Unlocked FRP Lock. help me pls... thanks and sorry for my bad english
how to re-lock bootloader and unlock sir? and the problem is every time i flash stock recovery in fastboot FAILED (remote: command not allowed)
it always getting FAILED (remote: command not allowed)
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
lucmaas99 said:
what I have done is this:
Rooted phone
Installed TWRP
than I updated (stupid)
Lost root than I wanted to install Custom frimware what didnt work
Factory resetted phone, phone doesnt boot anymore now.
I can only access fastboot but I can not get fastboot to work on pc installed many different drivers just dont work.
Click to expand...
Click to collapse
Every two or three days people report here they bricked phones by forcing update or Factory reset (or relocking Bootloader) from custom or rooted phones (or by having TWRP) - one must first go back to the original stock firmware he had, before upgrading/resetting/relocking...
And this thread will also not help to somebody else -
since 'somebody' will not read (before bricking the phone) ;(
---
Do you still have TWRP - use HWOTA to flash stock
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
If you have no TWRP but Fastboot is showing Bootloader unlocked, you should be able to flash TWRP.
If Fastboot is showing Bootloader locked but FRP unlocked, you should be able to unlock Bootloader.
But if there is no more TWRP and Fastboot is showing FRP and Bootloader locked - maybe DC Phoenix can help you
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
lucmaas99 said:
I used this command in fastboot: fastboot oem device-info
But I get this error: FAILED (remote: Command not allowed)
On my phone it says: Phone: unlocked and FRP: Lock
Click to expand...
Click to collapse
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
lucmaas99 said:
I cannot get into to recovery but when I let the phone die and than it starts normally,
but everytime it turns off its get back stuck in bootloop I got my oem key when it booted back but now I tried unlocking it agian but it says this:
C:\adb>fastboot oem unlock <code>
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\adb>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.024s
Click to expand...
Click to collapse
I cannot flash anything because I cannnot enable USB debugging in developers options
zgfg said:
Yeah, this is not adb/fastboot drivers problem but a fact that you either did not keep OEM Unlocking or it locked due to your procedures. But you have no system to boot in and to unlock.
Is TWRP still on? Press and keep pressing Power until phone shuts down (from Fastboot).
Try to boot to recovery by keeping pressed Vol + and Power -- if it boots to TWRP proceed by HWOTA as above.
If it boots to eRecovery instead, maybe you can try Factory reset (although, I don't believe it will work)
If you don't have recovery anymore (and you have no system and FRP is locked) then you really bricked the phone, you should pay for DC Phoenix and try to unbrick
Click to expand...
Click to collapse
What can I do I can access phone but cannot unlock bootloader because cannot use remote commands and I can not get into any recovery menu I am out of idea's
lucmaas99 said:
I cannot flash anything because I cannnot enable USB debugging in developers options
Click to expand...
Click to collapse
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
zgfg said:
You can boot to system?
Which (full name) build it shows in About?
Can you enable Developer options - then why cannot you enable USB debugging?!
You must first enable Allow ADB debugging in charge... and only then USB debugging -otherwise USB debugging switches off
Click to expand...
Click to collapse
Modelnumber: EVA-L19
Build: NRD90M test-keys
I think I should not supposed to have test-keys doesnt seem correct?
So I got my phone to boot but everytime I want to do something in recovery or something else It wont boot anymore and than I need to make the battery run out of juice. are there anyfix without needing root recovery or fastboot.
ADB wont work because usb debugging wont turn on (tried many things), Fastboot kinda works but gives the error (remote command not allowed)
Cannot get into any Recovery I can boot to OS
** Nevermind, i found the command i needed.
fastboot oem asus-csc_lk
Hello, im having hardware problems and having to send my rog phone 2 back, but the bootloader is unlocked and i cant relock it. I've gone on google and tryed everything but i keep getting errors. Does anyone know how to relock it? Im kind of stressing out.
Fastboot can detect the phone but no matter what i do it just says "FAILED"
Commands:
fastboot flashing lock = FAILED (remote: 'permission denied')
fastboot oem lock = FAILED (remote: 'unknown command')
Thank you for your help.
Hi, i wanted to relock my Bootloader again. I deinstalled Magisk per app , did a factory reset and now i should be able to do Fastboot oem Lock in adb or not ? Cause i get failure every Time i try that its an unknown command. Can someone Help me mabye?
Edit like that, Reboot Bootloader work but then from there on not.
C:\adb2>adb reboot bootloader
C:\adb2>fastboot oem lock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
We used fastboot flashing unlock to unlock bootloader so I guess you need to use
Fastboot flashing lock
yes that was it thank you much