Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....
Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.
oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX
Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..
Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.
Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!
I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.
Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
I'm having the same problem.
basically when i am on slot b, I can't use any fastboot commands and ive also not installed twrp.
those same commands worked when i was on slot a.
now i am stuck in slot b. don't know any fix.
ZuNNN said:
Hello everyone, so recently i decided to update my mi a2 to android Q, since my OTA updates werent updating (i had root with magisk, and no twrp), so i decided to erase all my data, and i tried from 0, instaling twrp first so i can switch from custom roms and whatnot. when i tried to install twrp it started to give me some errors on my device when i typed commands on my computer, saying "press any key to shutdown", basically i think i bricked my phone, i cannot use a single fastboot command, im getting desperate, i can provide more information as we go on...
[EDIT] when i try a command, for example: "fastboot flashing unlock_critical" it gave me an error like "FAILED (command write failed (no such file or directory))" or "fastboot erase ddr
erasing 'ddr'... FAILED (remote: unknown command)" these were the last commands i had here
[EDIT 2] when i try to use MiFlash and flash the original rom, it still gives me the same error on my device like (press any key to shutdown), it goes all black with this small message....
Click to expand...
Click to collapse
Use Windows PC (preferably 7 with Intel and USB 2.0), latest platform tools and try again. I generally do not install TWRP, rather boot it (use the latest one) and carry out the tasks since I use Stock ROM.
I had that problem before.
Things that solved:
Use another usb-c cable
Run fastboot on linux
Use an usb 2.0 HUB (the ones that have 3 or 4 ports)
did u check usb debug box,and OEM as well?
and if you did all of that , did unlock bootloader?
hi guys, after the really buggy android 10 update from xiaomi i decided to install a custom rom on my device, i hadn't installed a custom rom in ages and never on an a/b device so it was new to me, i was kinda stumbling but managed to install twrp, install pixel experience rom and then switched to slot a and it booted
but now my device does not accept most fastboot commands! fastboot getvar all only works 1/3 of the time, most of the time it either fails with FAILED (remote: 'unknown command')) or FAILED (Write to device failed (Unknown error)) which boots me to the same black screen as OP. fastboot boot twrp.img always fails. the phone boots successfully but im unable to switch slots or boot to recovery when everything was working perfectly before switching slots. ive tried 2 cables with 3 usb ports on my laptop.
Hi, I'm trying to get TWRP flashed onto my device (model number G8441), but when I try to flash it with fastboot it spits out an error:
> fastboot flash recovery twrp.img
Sending 'recovery' (33688 KB) OKAY [ 0.885s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
I'm using https://twrp.me/sony/sonyxperiaxz1compact.html (if it helps, I wanted to flash https://forum.xda-developers.com/t/rom-havoc-os-4-6-official-r.4225905/ and I use Arch Linux (I don't have a Windows device available))
I have enabled USB Debugging and OEM Unlocking. I have the US model.
I'll try to be able to send more information if needed.
Sorry about the terrible formatting, its my first time using XDA forums.
Sneexy said:
Hi, I'm trying to get TWRP flashed onto my device (model number G8441), but when I try to flash it with fastboot it spits out an error:
> fastboot flash recovery twrp.img
Sending 'recovery' (33688 KB) OKAY [ 0.885s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
I'm using https://twrp.me/sony/sonyxperiaxz1compact.html (if it helps, I wanted to flash https://forum.xda-developers.com/t/rom-havoc-os-4-6-official-r.4225905/ and I use Arch Linux (I don't have a Windows device available))
I have enabled USB Debugging and OEM Unlocking. I have the US model.
I'll try to be able to send more information if needed.
Sorry about the terrible formatting, its my first time using XDA forums.
Click to expand...
Click to collapse
You enabled OEM unlocking but did you actually unlock the device? Toggling the switch in the Dev options is one thing but to properly unlock the bootloader, you must have an unlock key from Sony.
More info here:
How To Unlock Bootloader on Xperia XZ1 and XZ1 Compact
Good News for all Sony Xperia XZ1 and XZ1 Compact users. Now you can Unlock Bootloader on Xperia XZ1 and XZ1 Compact, Read all the instruction carefully.
www.getdroidtips.com
AlexKarimov said:
You enabled OEM unlocking but did you actually unlock the device? Toggling the switch in the Dev options is one thing but to properly unlock the bootloader, you must have an unlock key from Sony.
More info here:
How To Unlock Bootloader on Xperia XZ1 and XZ1 Compact
Good News for all Sony Xperia XZ1 and XZ1 Compact users. Now you can Unlock Bootloader on Xperia XZ1 and XZ1 Compact, Read all the instruction carefully.
www.getdroidtips.com
Click to expand...
Click to collapse
I actually didn't, I thought it was already unlocked, silly me. Going to try that now.
Got the code and such, but when I run the command to unlock the bootloader, fastboot complains fastboot: invalid option -- 'i'
Is there another/newer command or tutorial I'm supposed to check?
EDIT: Checked Sony's site and it had the updated command, Thanks for your help!
Sneexy said:
Got the code and such, but when I run the command to unlock the bootloader, fastboot complains fastboot: invalid option -- 'i'
Is there another/newer command or tutorial I'm supposed to check?
EDIT: Checked Sony's site and it had the updated command, Thanks for your help!
Click to expand...
Click to collapse
You're welcome
Does that mean you unlocked the bootloader on PIE? When I did it, the only known way was to downgrade to OREO, temp root, back up TA partition, unlock bootloader, restore TA and then upgrade back to PIE.
AlexKarimov said:
You're welcome
Does that mean you unlocked the bootloader on PIE? When I did it, the only known way was to downgrade to OREO, temp root, back up TA partition, unlock bootloader, restore TA and then upgrade back to PIE.
Click to expand...
Click to collapse
Yep, I unlocked it on Pie.
I'm having, a similar (sort of) problem. I've unlocked the bootloader following Sony's steps. Fastboot sends recovery "okay", writes it "okay" as well. But it doesn't boot into recovery. Instead, the phone briefly shows an opened lock image with the text "Your device software can't be checked for corruption. Please lock the bootloader", and it proceeds to booting up into the OS.
suquet.paul said:
I'm having, a similar (sort of) problem. I've unlocked the bootloader following Sony's steps. Fastboot sends recovery "okay", writes it "okay" as well. But it doesn't boot into recovery. Instead, the phone briefly shows an opened lock image with the text "Your device software can't be checked for corruption. Please lock the bootloader", and it proceeds to booting up into the OS.
Click to expand...
Click to collapse
I'll try and help but I need a little info:
First: Do you have USB debugging enabled?
How did you flash recovery? Could you give your steps?
How are you booting into recovery?
AlexKarimov said:
I'll try and help but I need a little info:
First: Do you have USB debugging enabled?
How did you flash recovery? Could you give your steps?
How are you booting into recovery?
Click to expand...
Click to collapse
Hey Alex! After a few hours I managed to figure out what was wrong.
I had to force reboot (after flashing the OS, via fastboot reboot) and press Sony's recovery hardware combination buttons which Sony themselves had misrepresented as being VOL DOWN + Power. Turns out, it's VOL UP + PWR.
So, I'm all good! I was able to boot into twrp and give it all the accesses and permissions it needed.
Facing the same issue here with my Vivo Y21,when I run fastboot flash recovery of the img file it says
Sending 'recovery' (32700 KB) OKAY [ 0.781s]
Writing 'recovery' FAILED (remote: 'Verify state locked')
fastboot: error: Command failed
can anyone help please
Hello. Is there a way to unlock the Bootloader without having to do it from the same phone settings??
I am not able to enter the phone because of the security it has and I am unable to flash it again because it has the Bootloader blocked =(
I have the same issue with VIVO Y16
Sending 'boot' (32768 KB)
FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
did anyone face the same issue? please help
hi,
i was trying to root a oneplus 10T 5g phone but somehow it got stuck at fastboot mode, device is oem unlocked.
i see following error while manually loading.
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
thanks in advance.
Sounds like your bootloader isn't unlocked.
It says boot loader is unlocked.
shahidmjd said:
It says boot loader is unlocked.
Click to expand...
Click to collapse
What model do you have?
It is one plus 10 T 5G 2417 model
I never had to do this but you could try.
fastboot flashing unlock
then
fastboot flashing unlock_critical
I did use unlock critical command but it says device is already unlocked.
Also bare in mind this is the 10 pro forum.. you'd be best making a thread in the 10T section..
They are a little different, I've not witnessed anyone have this issue before.
shahidmjd said:
I did use unlock critical command but it says device is already unlocked.
Click to expand...
Click to collapse
That's odd.. I've no idea buddy, ask in your actual forum..
shahidmjd said:
hi,
i was trying to root a oneplus 10T 5g phone but somehow it got stuck at fastboot mode, device is oem unlocked.
i see following error while manually loading.
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
FAILED (remote: 'Flashing is not allowed for Critical Partitions.
thanks in advance.
Click to expand...
Click to collapse
reflash stock
Downloads\platform-tools_r33.0.3-windows\platform-tools>fastboot flash abl abl.img
Sending 'abl' (179 KB) OKAY [ 0.006s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
Try booting into fastbootd before running those commands, run.. fastboot reboot fastboot
EDIT: Some Oneplus phones do not allow flashing partitions that would be seen as critical within the usual fastboot mode, only fastbootd.. Maybe this is the case for the 10T
platform-tools_r33.0.3-windows\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
shahidmjd said:
platform-tools_r33.0.3-windows\platform-tools>fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Click to expand...
Click to collapse
I hate to say this, but I think your phone might be bricked.. I would suggest trying to flash the stock boot.img, and also the none critical files for your device within the bootloader / normal fastboot if it allows you to and then try to rerun - fastboot reboot fastboot, to boot into fastbootd.. My 10T is currently fully bricked.. The Whole EDL nonsense is ridiculous.. The OnePlus Chat Support said remote support could be available for me.. Which is usually unheard of.. Especially seeing as they want to keep their EDL tool and files from prying eyes.. I just want my device back, nothing else.. I would even be willing to leave the room, while they do their work.. They will probably blank my screen until the restore is successful.. They will probably reply to me in a year from now knowing OnePlus..
Just remember to make sure that you only flash the boot.img and none critical files for your current firmware and region... Otherwise.. It could end badly..
I understand I am encouraging something and engaging in something that is off-topic for this device section.. However I hope what I have said can possibly help you.. Not having a phone really sucks.. And I have gone the entire day without one..