Razer bootloader unlock - Razer Phone Guides, News, & Discussion

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

Related

Unlocking Bootloader: "command write failed" after most fastboot commands.

So 10 hours ago I decided I wanted to root my phone to install some apps and maybe even a cool ROM.
I read that the first step is to unlock the bootloader. I have trying my hardest to do this first step for 10 hours.
I've read 4-5 different tutorials twice on xda.
My phone is:
HTC One A9(hiae), bought in Sweden
hTc download mode
*** LOCKED ***
htc_hiaeuhl PVT S-ON
LK-1.0.0.000
[email protected]
OpenDSP-7.8.2.00197-8952_1228
OS-1.56.401.70
Jan 22 2016....
I have tried the normal way through htcdev.com even had the Unlock_code.bin at one point. But I had to reinstall all drivers twice to get it.
I have tried using the WinDroid Toolkit, no better than the manual way.
I got my hard earned token ID through both ways.
I find that every time I want to use fasstboot to send over a file i.e. "fastboot flash recovery twrp.img" hTc download mode is stuck at Start download, like I need to confirm it but can't because the command failed. The same goes for the Unlock_code.bin, can't send it over.
Code:
C:\adb>fastboot devices
HT5AVBE04449 fastboot
C:\adb>fastboot flash unlocktoken Unlock_code.bin
target didn't report max-download-size
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.003s
I can get past this next problem temporarily by reinstalling all drivers, tedious.
Code:
C:\adb>fastboot oem get_identifier_token
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Possible problems:
hTc download mode: I need to accept the download before fastboot give up, instant.
Win10: Bad OS for this?
USB connectors: Not enough power? Some other USB devices don't work here normally.
HTC Sync Manager: I've not bother installing the software.
Solution
I've made it;
I'm not sure if I was in the real download mode at the time, but that might have been it.
Also this time I redid everything, deleted all the drivers correctly and installed via Universal Naked Drivers
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
ouioui01 said:
Hello,
Did you check OEM unlocking to allow the bootloader to be unlocked in Settings/Developper options (hidden by default, appears when you tap Build number 10x in Setting/About/ Software information/More/ Build number) ?
Click to expand...
Click to collapse
For my phone it is 8 taps and yes. Every time I start a new Android I do a OEM unlock.
But I might be correct to change USB connector.

Cant boot into recovery, fastboot cant unlock oem

Hello Guys, I am new to the forum. I read a lot of threads, but no one i found had the solution or the exact same problem i have.
I bought a new Xiaomi Redmi 4X and wanted to install the los 14.1 Version I found here in XDA (https://forum.xda-developers.com/android/development/rom-2017-08-07lineage-14-1-t3653016). (I have installed custom roms a few times before and also faced some problems)
I flashed twrp via the fastboot mode using my linux laptop. I installed the los zip file and booted into it, but it was stuck in a boot loop. I wanted to go back into twrp, but it did not work, so i tried it with the fastboot again. Then I saw that oem is locked.
As root user i tried to unlock it with
Code:
# fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
but it doesnt work.
So I am stuck now without any ROM and Recovery, I can only access to the bootloader.
I am happy for any help.

Bootloop Mi4C please help

Hi all,
I really need some help. I was trying to update my Mi4c to MIUI 10, but something went wrong and now I it is in bootloop. It is locked and I can't unlock it anymore.
Since Fastboot is working I tried to enter EDL mode via ADB but it says this
PS C:\fastboot> .\fastboot devices
ecc1a647 fastboot
PS C:\fastboot> .\fastboot oem edl
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Please help,
Thank you
why not you try to flash the miui rom using fastboot mode instead of going to EDL.
You can get the rom file from this url https://mifirm.net/model/libra.ttt

Help please: adb devices no u11 listed? tried many times..

reboot to bootloader mode, tried lots of way to fix it but still no device listed, tried: drivers defferent, checked tcp port 5037, kill-server, start-server, restart many times, tried with diferent windows 10 OS, and diferent computer/laptops, device ID / VID loaded to .android folder as well,
as my u11 seemed encrypted you can see my previous post:
My u11 encrypted? lost wifi and mobile signal, after restore rom, it bricked
Please check the pictures: short story first: after reset the ROM with recovery mode, the u11 can go through the encrypting screen, then it will loop and stuck in the setup screen. I didn't really encrypt my phone ever, I only had a simple...
forum.xda-developers.com
But when I use command: adb devices
nothing listed, this what is look like:
-------------------------------------------------------------------------
C:\Windows\system32>adb devices
* daemon not running; starting now at tcp:5037
* daemon started successfully
List of devices attached
--------------------------------------------------------------
Can I actually use adb with bootloader mode of u11? As I cannot boot into my android OS which stuck in setup screen with no wifi no mobile signal and I cannot switch android to debug mode, the only thing I can do: boot to bootloader/fast boot mode, but adb devices cannot find it. I want to keep my original ROM
Do you see you phone with fastboot devices ?
Thank you so much! sure I can see the device now with fastboot!
but i got this now: (should I unlock u11?)
C:\Windows\system32>htc-fastboot erase persist
erasing 'persist'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
Thank you so much! sure I can see the device now with fastboot!
but i got this now: (should I unlock u11?)
C:\Windows\system32>htc-fastboot erase persist
erasing 'persist'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
------------------------------------------------------
My u11 is encrypted by some reason, no wifi no mobile signal, stuck in setup mode,
do you still have chance to get the original rom back or i have to flash a downloaded rom now?
thanks

Unlocking Bootloader AGM M5

I've been trying for awhile now to unlock the bootloader on my AGM M5. It is running on a simplified Android 8.1. I've enabled USB debugging and have enabled Bootloader Unlocking in settings. ADB works fine but I cannot get the bootloader to unlock when I run the following commands.
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\platform-tools>fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: -0.000s
I've tried running them from several different devices. Windows 7, Windows 10, and Raspberry Pi. But they all gave me very similar results.
If someone could give me some help it would be great. I'll mention right here that my ending goal is to install Postmarket OS. So if this is totally an unnecessary step please let me know. The reason for this step was I was trying to get a boot.img from the device and I wanted to install TWRP. But I was running up against every direction it tried and all my research was yielding very little as it seems that my M5 is not a very popular device.

Categories

Resources