Hi all, I was wondering if you know, after bootloader unlocking, why I can't access full fastboot commands as the one to remotely boot a recovery. "fastboot boot recovery.img" says "Failed: Command not allowed" and also does "fastboot oem ?" to list oem commands. OEM unlocking is permanently On , on the Dev Options and as I said before, bootloader is unlocked. But, I still can, I guess, flash boot, recovery etc. but I don't want to do it right now. I can tell it because so happened on my previous Huawei Phone and what's happening now on my P10 is the same thing. Thanks in advance.
Up, my ROM is VTR-L09C55B130 stock and I'm on Android 7.0
Related
So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.
jonrogers61 said:
So I bought this HTC One M7, the guy claims its soft bricked and hes not able to fix it because hes technically challenged. So I take it home boot it up, its stuck in a boot loop so I boot it into fastboot the bootloader is locked so I try to connect it to adb, no luck, there is no driver on this internet that I have found that will connect to adb. So I resort to fastboot, I "fastboot devices" and sure enough it connects (wicked), first I try to flash recovery, I try to boot recovery, I tried to update zip, no luck in flashing anything because I either get a signature fail or a "remote: not allowed" then I realize my bootloader is locked, I try to unlock it "fastboot oem unlock" and of course I get a "INFO [ERR] command error". I also tried to change my cid to 11111111 and no luck. I have actually tried everything I can think of I cant get s-off to work my recovery is stock as well so theres no possibility of OTG cable plus a usb. My fastboot will not flash anything in fastboot, I cant push any files to the phone, I cant connect to adb, I cant use my recovery. So what in the actual can I do? I think i'm f**ked.
Thank you in advance for anything you can help me with.
Click to expand...
Click to collapse
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked
donkeykong1 said:
You can't use adb unless you're booted to OS or custom recovery. Also you can't unlock bootloader with "fastboot oem unlock" unless your phone is GPE version. For Sense you need unlock token from htcdev. In order to flash anything, you need custom recovery, and you can flash it only if your bootloader is unlocked
Click to expand...
Click to collapse
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.
jonrogers61 said:
I unlocked my htc with the unlocktoken from htc dev but it still says locked in bootloader. I can flash the unlock_code.bin but it does not restart nor does it come up with a message that says I would like to unlock bootloader etc.
Click to expand...
Click to collapse
can you post the output of "fastboot getvar all" (remove your imei and serialno). Sometimes, reflashing the stock firmware can solve some bootloader unlock problem but I need to know you getvar all before I can tell you which one you should flash.
Short story: my phone bootloops (shows the Android One screen for 3 seconds, then reboots), and I cannot unlock the flash in fastboot. fastboot oem unlock fails, fastboot flashing unlock fails, fastboot flashing critical_unlock fails.
What can I do, is my phone definitely bricked?
Long story: I installed september OTA and then rooted with Magisk using the image patch method. Now I wanted to get October OTA, so uninstalled Magisk to recover the unpatched bootloader, but the OTA refused to install. So I tried the flash_all method, but it failed because I did not do the critical unlock. So I tried the fastboot flash critical_unlock, but it continuously refused to work.
So I decided to agan lock flash, and do the oem lock, to restart the unlock procedure from the beginning. But after locking, the phone does not boot anymore (and it was booting fine before!). On top of that, I cannot oem unlock anymore, fastboot oem unlock always fails.
Is there any way to recover the phone?
Try fastboot oem edl
then use mi flash
Thanks for help.
Unfortunately fastboot oem edl fails:
Code:
# fastboot oem edl
FAILED (remote: Device is already locked!)
Finished. Total time: 0.001s
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
doragasu said:
Thanks for help.
Unfortunately fastboot oem edl fails:
And as fastboot oem unlock also fails, I cannot unlock the bootloader.
Click to expand...
Click to collapse
I'll need more info than that
what's the error you get when using oem unlock or unlock_critical?
are you using minimal adb? If so, don't, use this instead https://developer.android.com/studio/releases/platform-tools
Are you using a usb 3.0 port? Switch to a usb 2.0 if you are
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
doragasu said:
I am working from Linux, and I have the full Android Studio installed. I cannot use adb, since I cannot boot the phone (and as far as I know, adb does not work on fastboot, but I might be wrong).
I will try with the one you linked and come back with the results.
Click to expand...
Click to collapse
Minimal adb includes fastboot, if you have minimal adb or you installed it from the repo then it's outdated, use the one I linked
Nothing was working for me, so finally I recovered the phone by opening it and using the deep flash method.
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/
I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone
Your fault that you locked bootloader on a modified system. Do a research next time
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
_08_ said:
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
Click to expand...
Click to collapse
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
shihabrumel said:
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
Click to expand...
Click to collapse
It won't let me. It says:
my command: fastboot oem unlock System: FAILED (remote "flashing unlock is not allowed")
Fastboot: error: command failed.
Same with the critical. I also had an error trying another command, it said, not allowed in lock mode.
Actually, I'm trying other commands and it's the same error with all comands.
My Mi A2 was not booting
My mi a2 last updated to 19/04/05 pie version, then i install the Google camera using below steps..
1. Turn on debugging mode/oem & turn off the phone
2. Then power button+vol dwn Fastboot mode & connect to pc (Pc already have the adb)
3. In pc>adb>folder>Cmd> type "fastboot oem unlock"
4. Then factory reset the phone and reboot again to fastboot mode
5. Then boot the patched image for phone
6. Then install the magisk and gcam work perfectly.
Simply i used these methods
the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
But then I tried to relock the bootloader, using below commands on cmd
1. "adb reboot-bootloader"
2."fastboot oem lock"
I tried these 2 commands 4 or 5 times
But phone is not power on with locked bootloader. Then I unlock again oem and try again,, But not working,
Then i unlock bootloader again and try these commands to lock it again,
1. "adb reboot-bootloader"
2."fastboot flashing lock"
3. "fastboot oem lock"
Unfortunately it is not work, also i can't give command "fastboot oem unlock", also i can't turn on my phone, Please help me... I want to restore my phone to working mode... Please help me, Quick, urgent :crying::crying::crying::crying:
i tried rooting my device but something went wrong after flashing the boot.img
now the device is stuck and i can only access fastboot.
i tried accessing the recovery but i get the same error msg.
i tried flashing every recovery img that exist for the red magic 3 but with no success
Flashing Unlock
Hey, make sure that you have first unlocked the bootloader with the fastboot command: "fastboot flashing unlock". Try it. It will erase all your data and do a reset factory and then you should be able to reboot your device normally. Also, it will let you flash the boot.img for root your device.
Perseo99 said:
Hey, make sure that you have first unlocked the bootloader with the fastboot command: "fastboot flashing unlock". Try it. It will erase all your data and do a reset factory and then you should be able to reboot your device normally. Also, it will let you flash the boot.img for root your device.
Click to expand...
Click to collapse
when i type "fastboot flashing unlock" in cmd it shows nothing .. just showing what commands i can do with fastboot
mashkalny said:
when i type "fastboot flashing unlock" in cmd it shows nothing .. just showing what commands i can do with fastboot
Click to expand...
Click to collapse
Did you let unlock bootloader and permitted the USB debbugin on the developers option before flash the boot.img?
Make sure you are using a USB 2.0 to connect your device to the PC. See if you PC recognizes the device into the fastboot menu with "fastboot devices", if doesn't, try reboot another phone with "adb rebbot bootloader", then enter "fastboot devices", your device should be listed into de the devices attached. Then try again entering "fastboot flashing unlock".
Perseo99 said:
Did you let unlock bootloader and permitted the USB debbugin on the developers option before flash the boot.img?
Make sure you are using a USB 2.0 to connect your device to the PC. See if you PC recognizes the device into the fastboot menu with "fastboot devices", if doesn't, try reboot another phone with "adb rebbot bootloader", then enter "fastboot devices", your device should be listed into de the devices attached. Then try again entering "fastboot flashing unlock".
Click to expand...
Click to collapse
i believe i forgot to unlock the bootloader when i tried to root. now i cant access anything in the fastboot mode.
mashkalny said:
i believe i forgot to unlock the bootloader when i tried to root. now i cant access anything in the fastboot mode.
Click to expand...
Click to collapse
Oh, that could be a problem. Try to use this tool. I hope you can get your phone working again. If this doesn't works, try to flash the original boot.img of your firmware version.
https://forum.xda-developers.com/re.../tool-nubia-red-magic-3-unbirck-tool-t3965044