Hi,
I'v got used Razer phone today with Oreo 8.1, tried to unlock boot but it failed. Commands I've ran so far (debug and oem unlock both on)
adb reboot bootloader
got the download mode
android bootloader interface version 11 driver from google.
fastboot -i 0x1532 devices
xxx40xxxx fastboot (xx are numbers)
then
fastboot -i 0x1532 flashing unlock
...
FAILED (command write failed (No error))
finished. total time: 0.004s
on the phone download mode words disappeared and no driver appear in the PC
also tried another root method with posted here in XDA for Oreo but still not working.
Please I need help as I bought the phone to root and enjoy it
Majed
NeverMind, used another laptop and i was able to do it... I think AMD has some usb filters or something
My Honor 6 was bricked after a stock OEM installing. I was tried to use fastboot to install a new recovery, but it shows
Code:
FAILED (remote: Command not allowed)
, however my phone says it is UNLOCKED.
Please help.
Thanks
A hawe a Huawei Mate 10 wich after hard brick (COM1) 6 mounth ago wake up himself!!!
Fastboot is works
Bootloader locked
eRecovery works
Stock recovery works
But DC Phoenix not flash any update.app or board.dgtks file (DC gives evrytime ERROR... device not supported, flashing incomplet). Flashing stops befor DC phoenix can open backdoor.
In fastboot works only one command, that is FASTBOOT DEVICES, and result is 123456789ABCDEF
I can*t flash nothing in fastboot vommand line: gives me error for example:
FASTBOOT FLASH OEMINFO OEMINFO.IMG
sending `oeminfo` 378kb...
OKAY
Writing `oeminfo`...
FAILED remote: Command not allowed
Any fastboot command ends with that error
eRecovery get errors after try flash WIFI DNS firmware finder.
Device lost all: oeminfo, vendor, IMEI, model
And only founded information by DC/HCU/fastboot is device name 0123456789ABCDEF
What i can to do to fix that?
Thanks
Hello, I wanted to go back to the initial system that was on my U11 but there was a very big problem because I can not lock the bootloader or install recovery because it shows the error: FAILED (remote: '4 RU_BATTERY_LOW please connect charger (0% <30%)'). And I will add that the battery is 100%
I don't have a answer for you but you can check out this thread for ideas,, hth,
[help] FAILED (remote: 4 RU_BATTERY_LOW please connect charger (0% < 30%))
I try to downgrade form Pie to Oreo but It's not work. Now I can't install any thing (RUU exe firmware, TWRP), message error: FAILED (remote: 4 RU_BATTERY_LOW please connect charger (0% < 30%)). I charge my phone 100%. But anything change. I...
forum.xda-developers.com
Hurray: D I fixed error: "Recovery" FAILED error (remote: "Not allowed on PRODUCTION device").
Guide to the incomprehensible
1. Download the original firmware from (https://4pda.ru/forum/index.php?showtopic=830013) (the firmware information can be read in the download mode. Example: radio-8998-002772-1711161638)
2. Download RUU-Decrypt-Tool (https://forum.xda-developers.com/t/...sal-htc-ruu-rom-decryption-tool-3-6-8.3382928) I extract the system (extraction guide is described in the link)
3. From the extracted system, copy the file (hosd_signed.img) to the adb folder on the computer, then turn on the phone in bootloader mode and enter the command: fastboot flash hosd hosd_signed.img
4. Our described bug has just been fixed. Now you can install TWRP without any problems. Good luck
wksawery71 said:
Hurray: D I fixed error: "Recovery" FAILED error (remote: "Not allowed on PRODUCTION device").
Guide to the incomprehensible
1. Download the original firmware from (https://4pda.ru/forum/index.php?showtopic=830013) (the firmware information can be read in the download mode. Example: radio-8998-002772-1711161638)
2. Download RUU-Decrypt-Tool (https://forum.xda-developers.com/t/...sal-htc-ruu-rom-decryption-tool-3-6-8.3382928) I extract the system (extraction guide is described in the link)
3. From the extracted system, copy the file (hosd_signed.img) to the adb folder on the computer, then turn on the phone in bootloader mode and enter the command: fastboot flash hosd hosd_signed.img
4. Our described bug has just been fixed. Now you can install TWRP without any problems. Good luck
Click to expand...
Click to collapse
Hi. Can you help me with this one? I've downloaded "2PZCIMG_OCEAN_DUGL_P90_SENSE10GP_MR_HTC_Europe_3.31.401.1_Radio_8998-200321-1905141529_release_540931_signed.zip" and after that i did " RUU_Decrypt_Tool.exe 2PZCIMG_OCEAN_DUGL_P90_SENSE10GP_MR_HTC_Europe_3.31.401.1_Radio_8998-200321-1905141529_release_540931_signed.zip -f" and in the end i've rebooted my HTC U11 in bootloader menu. And from the PC after i have connected my phone to it , i have run the command : "fastboot flash hosd hosd_signed.img" and rebooted the phone again in bootloader mode and trying to install recovery image with fastboot command but i am still getting the error that you having .
Please advise !
Hello, friends. So I am here following this exact tutorial :
How to Restore OnePlus Nord Back to Stock OxygenOS Software - A Complete Guide
In this guide, we will show you how to restore the stock OxygenOS software on the OnePlus Nord by flashing the factory image/Fastboot ROM. Things like custom ROMs, TWRP, and Magisk root are pretty…
www.thecustomdroid.com
I currently am stuck there
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flash abl abl.img
target reported max download size of 805306368 bytes
sending 'abl' (1996 KB)...
OKAY [ 0.055s]
writing 'abl'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.057s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock_critical
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot flashing unlock
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.000s
Click to expand...
Click to collapse
I just simply do not understand what could be wrong here.
In fastoot mode I get "device - State unlocked"
As you already saw, it seems the device is completely unlocked. What could be wrong ?
Also, some steps before, I get that :
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
I suspect switching to the automated in Windows won't change much.
It is strange because I am able to perform these steps without problems, ones the ones after seem to not work :
./fastboot flash boot boot.img
./fastboot flash dtbo dtbo.img
./fastboot flash modem modem.img
./fastboot flash recovery recovery.img
./fastboot --disable-verity flash vbmeta vbmeta.img
./fastboot --disable-verity flash vbmeta_system vbmeta_system.img
Click to expand...
Click to collapse
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
My phone is a Oneplus Nord and I am using the advised Oxygen OS ROM provided in the tutorial I linked at the beginning of my message.
I hope you'll be able to get me out of this as I unfortunately can't figure out how to solve this problem on my own.
Best regards
krakard said:
I might be doing something wrong ? Be located in the wrong folder or something ? For instance, when I type these commands it does not work if I write the "./" before fastboot, it tells me
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ ./fastboot flash boot boot.img
bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Yes, that makes sense.
Fastboot should be located at /usr/bin/fastboot. Since you're not in that directory, ./fastboot won't work. (This ./ means: "Look at the current working directory for the command fastboot." If it cannot find fastboot there or it isn't a shell command, it will throw an error.)
However, since you didn't install fastboot globaly, you have to address its exact path inside your platform-tools folder. If fastboot is not in Partition-image folder, ./ won't work.
Can't help you with your main issue though.
Edit: You seem to have fastboot installed globally though:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
So my first explaination is valid.
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
krakard said:
Thank you for clarifying that. I understand the issue there. Which is a non-issue indeed since I already installed it globally. But well, it at least teaches me how Linux work.
Of course however, the main issue remains that's for sure.
Click to expand...
Click to collapse
You're welcome.
BTW:
krakard said:
@pop-os:~/Desktop/platform-tools_r31.0.2-linux/platform-tools/Partition-image$ fastboot reboot fastboot
fastboot: usage: unknown reboot target fastboot
Click to expand...
Click to collapse
There is no "fastboot" to boot into. Instead, type
Code:
fastboot reboot bootloader
I didn't mention that yesterday for some reason.
Guys, here is where I am at now. Still struggling but I feel I am very near ! Some help maybe ?
https://forum.xda-developers.com/t/...your-device-to-oxygenos.4148415/post-85022511
best regards
SOLVED
krakard said:
SOLVED
Click to expand...
Click to collapse
How did you fixed this? I'm currently stuck at the same point as you with a oneplus 8
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
mbootsman1 said:
Same here, how did you managed to solve the "Flashing is not allowed for Critical Partitions: error with the fastboot ROM batch file?
Click to expand...
Click to collapse
I found the solution, you have to do fastboot reboot fastboot which reboots you to fastbootd instead of fastboot. There you can flash critical partitions without issue.
Hi,
As the command recommanded everywhere :
Code:
fastboot flashing unlock_critical
had never worked for me in the bootloader environment,
I have to reboot i my rom embedded recovery in order to flash the file (apply update menu) through the :
fastbootD
To sum up :
#From Android (while having all prerequisite done ie bootloader unlocked...)
Code:
adb reboot bootloader
#From the bootloader I choose to boot to recovery and I get to the rom custom recovery
#In the custom recovery, I choose the menu "apply update" that will lead me to the fastbootD mode
#I type the appropriate command to flash the persist partition
Code:
fastboot flash persist "c:\your_path_to_your_persist_file\persist.img"
#Then I simply reboot the phone
Code:
fastboot reboot
PS : Initially flash the OxygenOS (OOS) 11, then apply the CRdroid Android v8 custom rom (based on Android 12)
I did it similar like solid-snake:
In my case I also had no access to fastbootD
The solution came randomly when I flashed back the first part from my lineageOS package:dtbo.img, vbmeta.img and the recovery.img --> after that my phone naturally booted in a fastbootD mode from the lineageOS package.
I modified the flash-all.bat from the stock ROM fastboot flash package:
I removed the line with the reboot command, because I'm already in the fastbootD mode.
Then I ran the modified flash-all.bat and everything went well.
If anyone else struggles (like I did) to get the phone in EDL mode, or the "Flashing is not allowed for Critical Partitions" error ,even if the "fastboot flashing unlock_critical" cmd was executed, here are some hints that might help.
I tried forever on a Linux computer without any luck, so I ended up installing Windows 10 on actual hardware to finally unbrick my One Plus Nord (Avicii). Here are the most important steps, YMMV, execute at own risk:
bcdedit.exe /set nointegritychecks off run this cmd as admin in terminal, toggle to "on"
then install edl drivers as admin, This is where I struggled the most, I finally found an .exe file(QDLoader HS-USB Driver_64bit_Setup.exe) that I just installed and then phone showed up as it should in device manager. ("Qualcomm HS-USB QDLoader 9008," not "QUSB_BULK")
install adb and fastboot. (platform-tools)
install MSM-Download-Tool
download stock OS for use in MSM-Download-Tool program
open msm tool, if phone is not recognised try turning on and holding power pluss both volume, or just one of the volumes.
uncheck the "sha hash check" box
flash
if you get the "Sahara Communication Failed", just try again, it worked for me.
wipe
erase Windows 10 and replace with any Linux distro, tell your PC it will never happen again.
enjoy
Here are link to the EDL-drivers that worked for me. Or just do a web-search for "QDLoader HS-USB Driver_64bit_Setup.exe"
The flashing process will take over 300 seconds, be patient.