Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Nice find!
No DRM crap or anything that would cause some features to be lost (stopped working) after unlocking bootloader?
I'm Sony user btw and had already lost DRM and some of its features, including camera that didn't work on older ROM version XD
Thanks, I just ordered the phone because of this post.... Though I should probably have waited for the U20
Still, ive been jonesing for an HTC fix . I need this.
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Doesn't work for me... (Solution)
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Know it's working!
Don't use fastmode/Fastmoded Mode, it has to be done with CMD and bootloader startet!
Hello, friends on the fifth floor
Before using FastBoot flash unlock, you need to open OEM lock in developer mode now. You can try my way and give me a reply on how to unlock normally. I am looking forward to your reply
Mick_Rinelander said:
Doesn't work for me.
C:\Users\User\Downloads\platform-tools>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Any suggestions?
Click to expand...
Click to collapse
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
wpride77 said:
Start CMD: adb reboot bootloader
then run
fastboot flashing unlock (for devices above 2015 y.)
If you still have this error, make sure if you have Correctly driver installed (must be Android bootloader interface) !!!!!!!!!!
Enjoy!!!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Were you able to flash any GSI roms on your unlocked HTC Desire 20 Pro?
i have one and im thinking of unlocking it
C:\Users\mypc>fastboot flashing unlock
FAILED (remote: 'Not implemet.')
fastboot: error: Command failed
Getting this error on my Itel A48 (L6006) running on android Q.......fastboot and adb drivers are installed and fastboot recognize my device
is this will work
HTCdev - HTC Kernel Source Code and Binaries
www.htcdev.com
can we find boot.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader can now be easily unlocked.Older get_identifier_token command is no more needed.
Instructions
Download HTC_Driver_v4.17.0.001 and install the package.
Download Google USB Driver. ( For installation information, read Install a USB Driver) .
To install the Android USB driver on Windows 10/11 for the first time, do the following:
Connect your Android device to your computer's USB port.
From Windows Explorer ( Search ), open Computer Management.
In the Computer Management left pane, select Device Manager.
In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
Right-click the name of the device you connected, and then select Update Driver Software.
In the Hardware Update wizard, select Browse my computer for driver software and click Next.
Click Browse and then locate the Google USB driver folder.
Click to expand...
Click to collapse
Connect your device to your computer and Backup device
( Get a complete backup of your contacts, messages, apps, and internal storage. Now usually, Enabling OEM unlock won’t erase the data on the device. But obviously, the eventual step after OEM unlock is bootloader unlocking, and that will wipe away everything on your device )
Download ADB. ( How to Install ADB on Windows, macOS, and Linux )
Enable OEM Unlocking
Open the settings on your phone.
Find the section that says “Developer options” and tap on it.
Scroll down till you find the option “OEM unlock”
Tap on it to turn the toggle on, and you are done.
Then simply run below command.
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
elimiriel said:
D:\android\Bat\com>fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
I've experienced error messages like this. OEM is unlocked in the developer mode, and the device is in bootloader also. Am I missed something?
Click to expand...
Click to collapse
Yes you have problems with fastboot on your PC.
Btw OEM unlock wiped my data just to heads up.
otack said:
Bootloader can now be easily unlocked as same as Pixel devices.
Older get_identifier_token command is no more needed.
Instructions
Connect your device and PC, then simply run below command.
Code:
fastboot flashing unlock
Select "UNLOCK THE BOOTLODER" by volume key and press power button.
Done!
Cheers!
Click to expand...
Click to collapse
Thanks mate!
I can confirm same strategy for the new Desire 21 pro 5G.
ToM
how unlock bootloader spd 9863a Android ver.11 realme c11
Hello, I need HELP! When I get to the "Google USB Driver" section I cannot proceed any further. When I open the update hardware wizard, I choose the folder that the Google drivers are in, and sadly, the drivers do not get installed to the device. The error reads "The best drivers for your device are already installed", preventing it from getting installed. I am using a Samsung Galaxy S21 that has an IMEI of a bunch of zeros (0).
Related
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Juice Jones said:
Hello,
I need the help of the XDA community. I'm very new to Android and Ive gotten myself in quite a bit of trouble.
I rooted my phone recently and decided to unroot the phone in order to trade with another user. In the process, my phone is wiped clean, and attempting to use RUU has left me relocked with S-On. I currently have no OS on the device. Attempting to run RUU gets no results, as I am met with Error 155 before I get any progress when the phone starts the "Sending" process. My phone will go into bootloader and it is recognized as a fastboot device by my PC, but not as an ADB device. I have the info from my bootloader menu below.
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
OS-5.12.502.2
My phone is an AT&T HTC ONE M7, 32 GB. I am at a loss and I've tried researching. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
majmoz said:
My guess you tried to run a RUU of a lower version than what is on your phone that is why you got the error 155. ADB does not work if there is no OS because it needs USB Debugging enabled in the OS but it works with a custom recovery like TWRP. Download the Guru Reset 5.12.502.2 and push it to your phone with the following procedure:
Click to expand...
Click to collapse
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Juice Jones said:
So I attempted to follow your instructions, got my bootloader unlocked and TWRP installed. Got the Guru Reset pushed onto my phone storage. Now I'm getting an error when trying to install. "Error Flashing zip" "E: Unable to mount '/cache' " "E: Unable to mount '/data/ " "E:Unable to mount storage. "
Not sure where to go from here.
Click to expand...
Click to collapse
Are you using TWRP 2.6.3.3? If not, flash it first.
In TWRP under Wipe, there’s an Advanced Wipe menu. Go there and select Data, format the partition. Downside you will have to push the Guru Reset back to the phone.
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
EDIT - I sort of solved it myself in post #7
sminki said:
I've been trying to relock my bootloader all afternoon...
fastboot oem relock 1234567890987654
Why? I was on B121 with unlocked bootloader, TWRP and SU. My intention was to flash stock recovery, relock and update to B140.
After a lot of experimenting, flashing, re-flashing, wiping etc. I cannot relock the bootloader. Even with a complete system flash and wipe of data. It fails with
Code:
FAILED (remote: root type is risk)
Does anyone know if there's a tamper flag, or similar
Click to expand...
Click to collapse
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
piskr said:
I think that the command is: fastboot oem lock.
from your description I don't see the rationale on locking bootloader. Be very careful, with unlocked bootloader you can make almost any mistake and find the solution but playing with locked bootloader is a totally different ball game.
Click to expand...
Click to collapse
Not on these. That the first thing I tried. That gives
Code:
FAILED (remote: Command not allowed)
Which is essentially "command not found", as you can pass it any garbage and that's what it gives back.
As I see it, you can't install updates with an unlocked bootloader (unless I'm wrong, or there is something desperately wrong with my phone). With no custom roms (at the moment) this is all we have
EDIT:
Looks like I was wrong about updates on unlocked bootloader. I went back to B100 (UK) then back up to B121
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
t-ph said:
Have you succeed to relock bootloader? In case of warranty need locked bootloader is a must thing?
Click to expand...
Click to collapse
I haven't retried yet. I was still in my 14 day return period and was undecided if I was going to keep the phone
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried it on B100?
Have you tried it on B140?
Have you tried "oem lock" instead of "oem relock"?
Note: Always mention your model number in your thread title and description. Not all different models behave the same and not all updates give the same error message.
Thank you for opening this thread. We hope to read your answers on the above questions to help you.
kenshiwara said:
Questions:
What model of Huawei Honor 7 do you have? (Settings -> About Phone -> Model Number)
Have you tried "oem lock" instead of "oem relock"?
Click to expand...
Click to collapse
I have the EU Version PLK-L01 16GB
..and yes I had, see my second post - lock doesn't seem to be a valid Huawei boot-loader command.
I've had a busy and incredibly boring time trying to sort this out.. Somehow, I re-locked :victory:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unfortunately from the point of view of returning the device to Huawei, Re-locked is not the same as Locked, but it's all I have found.
After TWRP format:
Code:
sudo fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: images signature check fail)[/COLOR][/B]
finished. total time: 1.048s
After B100 Downgrade:
Code:
fastboot oem relock 1111111111111111
...
[B][COLOR="Red"]FAILED (remote: root type is risk)[/COLOR][/B]
finished. total time: 0.970s
I re-flashed the UserData image from B100, after booting up I got this:
After UserDate Wipe:
Code:
fastboot oem relock 1111111111111111
...
OKAY [ 1.985s]
finished. total time: 1.985s
fastboot oem get-bootinfo
...
(bootloader) [COLOR="Green"]relocked[/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
So basically, I re-locked with a completely fresh, untouched system and a "factory" wiped data partition.
Obviously I have unlocked again and gone back to B140. If someone else want to experiment, feel free to post your results. I'm done with this :silly:
Re-lock your bootloader successfully
Re-lock your Honor 7(PLK-L01)'s bootloader successfully
No matter on which version you are and on which recovery, follow the steps:
1. Extract the B100 "UPDATE.APP" using this tool. Credit goes to its maker. If you wanna make flashable zip from "UPDATE.APP" then use the attached "Profiles.xml" file for HuaweiUpdate Extractor, me and @kenshiwara has added Honor 7 in the list.
2. Now flash "boot.img", "recovery.img", "cache.img", "cust.img", "system.img", "userdata.img" from the extracted B100 "UPDATE.APP" by executing following commands in "Command Prompt"
Make sure you are in the same folder where all these files are then "Right click" inside the folder by holding down "Shift", then select "Open command window here".
For "boot.img"
Code:
fastboot flash boot boot.img
For "recovery.img"
Code:
fastboot flash recovery recovery.img
For "system.img"
Code:
fastboot flash system system.img
For "cache.img"
Code:
fastboot flash cache cache.img
For "cust.img"
Code:
fastboot flash cust cust.img
For "userdata.img"
Code:
fastboot flash userdata userdata.img
Now reboot your device by executing this command
Code:
fastboot reboot
3. Setup your device, then place B100's "UPDATE.APP" in your external SDCARD in "/dload" folder.
4. Now, switch off your device and press the three button combo to flash the B100 "UPDATE.APP", the three button combo is "Vol. Up", "Vol. Down" and "Power Button" press these three simultaneously to flash the B100 "UPDATE.APP".
5. After your device reboots and after you are done setting it up, go to "Settings > Backup & Reset", then select "Factory data reset", tick "Internal Storage" and press "Reset Phone".
6. Again after rebooting, switch off your device then by pressing "Vol. Down" button connect your device with PC.
7. Now, you'll be in "Fastboot&RescueMode" and your device status will be "Phone Unlocked".
8. Execute the following command to relock your device.
Code:
fastboot oem relock *16 digit unlock code*
9. Now, you'll see that your device status is changed to "Phone relocked".
So, you just relocked your Honor 7.
So basically what I said then
sminki said:
So basically what I said then
Click to expand...
Click to collapse
I think you just flashed "userdata.img" of B100 which is not good as it broke your "/userdata" partition, but yea basically that
DigiGoon said:
8. Execute the following command to relock your device.
Code:
fastboot relock *16 digit unlock code*
Click to expand...
Click to collapse
are you sure? i thaught it was
Code:
fastboot [B]oem[/B] relock *16 digit unlock code*
non-toxic said:
are you sure? i thaught it was
Code:
fastboot relock [B]oem[/B] *16 digit unlock code*
Click to expand...
Click to collapse
Thank you for pointing that out.
speaking as the man who has, you're both incorrect
Code:
fastboot oem relock *16 digit unlock code*
sminki said:
speaking as the man who has, you're both incorrect [emoji14]
Code:
fastboot oem relock *16 digit unlock code*
Click to expand...
Click to collapse
You should've checked my answer before stating that I'm incorrect too. And yeah check its last edit too, its not edited after your reply.
Sent from my PLK-L01 using Tapatalk
i'm not well
my humble apologies @DigiGoon
I have try "fastboot oem relock *my code*" and it works. But i had changed nothing on my phone. it was just unlocked.
no root; no TWRP; no other updates
maybe this was the reason why.
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Hello,
i can`t relocked my phone.
FAILED (remote: root type is risk).
My Honor 7 has the Firmware B330.
I think i tried everything but i always have the same error.
What can is the newest solution?
what's the point of relocking the bootloader?
hachuwaka said:
what's the point of relocking the bootloader?
Click to expand...
Click to collapse
I want to know too. Is there any risk to keep unlocked the bootloader on non rooted device?? Except guarantee
---------- Post added at 05:46 PM ---------- Previous post was at 05:43 PM ----------
Sandnes74 said:
I have unlocked my phone.
I'm now on B140.
With a unlocked phone, do I still get updates from Huawei anymore?
Click to expand...
Click to collapse
You will receive updates but do not install them!!!! If you don't listen to me your device will be caught in bootloop
Sent from my PLK-L01 using XDA-Developers mobile app
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
2: Returning to Stock
If for any reason your phone is no longer functioning properly such as a bootloop (the phone is restarting itself over and over), "Can't Load Android System," "Startup Failed", or any such error you can fix this by flashing the stock firmware using fastboot.
I have taken stock firmware version OPW27.113-89 and packaged it with a few extras. XDA Member luiz_neto has provided a modified logo.bin that removes the unlocked bootloader warning during boot. A special thanks to XDA Member lohanbarth for providing the stock firmware. I have included the fastboot file for Windows, Linux and Mac users. Windows users can run the .bat file to execute all the necessary commands. For Linux and Mac users, I have included a bash script. You will need access to a PC and connect your phone via a USB cable.
*Downloads:
Modified Stock Firmware OPW27.113-89: (Download)
MD5: 3a1d984a8a3d0c57fb21931a8004eb27
Instructions:
*On your phone:
2A. With the phone powered off(even if for just a moment between the phone rebooting) hold the Power button and the Volume Down(Vol -) at the same time. You should boot into what is called the bootloader. It should display information on the screen and state "AP Fastboot Flash Mode" in orange lettering.
*On your PC:
2B: Extract the firmware which is in tar.xz container/file extension. Windows user probably need to use Winrar, 7Zip or PeaZip to extract the file.
2C: Using Windows Explorer, navigate to the folder EVERT_OPW27.113-89_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml and click on it to open it.
2D: Hold the Shift Key on your Keyboard. While holding Shift, Right Click in the window(not on the file). Depending on your windows version you should see either "Open PowerShell Window here" or "Open Command Window here." Select which ever one applies.
2E: You will see a black and white screen or a blue and white screen. The steps are the same no matter which screen you see. Simply type(or copy and paste) the following command:
Windows:
Code:
flash_rom.bat
For Linux and Mac you need to make the script file executable. It will make the fastboot binary executable for you. From a terminal run these 2 commands one at a time:
Linux:
Code:
chmod a+x flash_rom.sh
./flash_rom.sh
Mac:
Code:
chmod a+x flash_rom_mac.sh
./flash_rom_mac.sh
Your phone should reboot on it's own. If for some reason it doesn't try tapping the enter key on your keyboard or use the volume keys to make sure “Start” is selected on the right side of the phone and pres the power key on the phone. It should successfully boot the stock firmware.
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
carlosgeraldo said:
Xplorer4x4 Hello good afternoon is on is corrupted When it unzips it says that header is corrupted! @Xplorer4x4
Click to expand...
Click to collapse
Did you try to download the package again?
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Mara-X said:
Does anyone know whether It's possible to remove the "Your device has loaded a different operating system." after flashing stock rom through fastboot and relocking bootloader? I was looking to sell the phone...
Click to expand...
Click to collapse
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Flash the stock firmware in my op.
Sent from my Moto G6 Plus using XDA Labs
Click to expand...
Click to collapse
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
I have never relocked my bootloader so I can't say for sure but this sounds out of the ordinary. Did it boot fine with an unlocked bootloader?
Sent from my Phh-Treble vanilla using Tapatalk
weazie said:
Did you try to download the package again?
Click to expand...
Click to collapse
I found the error: it was in my PC I started a program to fix the registry and after that unzipped the file normally!
Mara-X said:
No, I'm not talking about the unlocked bootloader warning, but the message that appears after you lock the bootloader. "Your device has loaded a different operating system"
Click to expand...
Click to collapse
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
MrMatnenko said:
Hi! have you succeed with your issue flashing this stock firmware ?
Does this stock firmware helps to remove warnings "This device has loaded a different operating system", and "Verity mode disabled" during boot?
And the worst thing is the message "System integrity compromized" and hens - GooglePay disabled and no software updates., when bootloader is re-locked?
Click to expand...
Click to collapse
Same problem here. I hate this messages
<bootloader> flash permission denied
friends, any command I give appeared this, someone knows how to solve?
Failed anything I've tried... Can you help @Xplorer4x4 ?
andreym_costa said:
Failed anything I've tried... Can you help @Xplorer4x4 ?
Click to expand...
Click to collapse
Shows the message "Failed Remote ' ' and "Flash permission denied"
andreym_costa said:
Shows the message "Failed Remote ' ' and "Flash permission denied"
Click to expand...
Click to collapse
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
WoKoschekk said:
You MUST provide MORE information! Screenshots, a detailed error description and not only a piece of your error.
Click to expand...
Click to collapse
I'm trying again... And now seeing this, can you help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
andreym_costa said:
I'm trying again... And now seeing this, can you help?
Click to expand...
Click to collapse
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
WoKoschekk said:
Please follow my guide below. That would be much easier I think, because it seems you are doing several things wrong.
1. download ADB/Fastboot tools from here and extract the downloaded zip to 'C:\' to create the path 'C:\platform-tools'
2. download your current firmware build here.
You use 116-16-22 but the latest build is 11-16-29 for RETBR.
3. extract the firmware.zip to 'C:\platform-tools'
Watch out to extract only single files and images to that path and do not create a subfolder => see screenshot attached
4. extract attached flashfile.zip to 'C:\platform-tools'
5. open 'C:\platform-tools' in Explorer and type 'cmd' in the address bar and hit 'Enter'
=> opens a new cmd window
View attachment 5654883
6. boot your Moto into fastboot mode, connect it to your PC and run 'fastboot devices'
=> output: <SERIAL-NO> fastboot
7. execute 'flashfile.bat' and start flashing
Click to expand...
Click to collapse
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
andreym_costa said:
I tried again and now these errors occur. I thought it might be a locked bootloader, but apparently everything is ok, at startup it has an unlocked bootloader warning. And really thank you to helping me.
Click to expand...
Click to collapse
No, your bootloader isn't unlocked. The OEM-Unlock toggle would be inactive (greyed out) in case of an unlocked bootloader.
Hi there,
I recently bought a LG K40s and wanted to unlock the bootloader in order to root this phone. But I could't find any instructions on how to do this nor a fastboot mode for that phone.
Does anyone know how I can get root access on this phone?
Thanks in advance,
Oebbler1
Fastboot: switch off the smartphone by holding the Power button for a couple of seconds. Then connect the Type C USB cable with your PC or laptop. Now push Volume Down and connect this cable with your device. When
hi. I try to root this device but when I use ADB this don´t go to bootloader, the device reboot in normal mode. I look TWRP web and this device isn´t in the list
Any method to root this device?
Regards
Help
we need to create a post to get help to root and install twrp on LG K40s
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next step is to install the USB-driver matching your device
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Any news?
Any news on how to root this device?
solve ?
renanflores85 said:
Any news on how to root this device?
Click to expand...
Click to collapse
there is an apk that search for what program can root the current android, and the only it show was stumproot, idk if is safe, i never saw it before, but searching for it, it show that is a root program for lg
jwoegerbauer said:
@jessepinheiro50
To root Android as 1st thing of all things these requirements must be achieved
Next step is to install the
Then check you can access phone from PC via USB
Code:
adb devices
and that boot-loader can get unlocked
Code:
adb shell "getprop ro.oem_unlock_supported"
and if returned value=1 verify that you can deal with phone's boot-loader
Code:
adb reboot bootloader
fastboot devices
Next step is to boot into phone's boot-loader, and unlock it WHAT WILL ERASE ALL DATA ON YOUR PHONE
Code:
fastboot OEM unlock
fastboot reboot
At last step you flash the software that will add root to Android
Code:
adb devices
adb sideload <ROOTING-SOFTWARE-ZIP>
adb reboot
Click to expand...
Click to collapse
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
letsbrick said:
this don't worked, it just reboot the phone, and it show 1 when it check if is possible to use boot-loader
Click to expand...
Click to collapse
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
jwoegerbauer said:
Try
Code:
fastboot flashing unlock
instead of
Code:
fastboot OEM unlock
Click to expand...
Click to collapse
That's not work for me. adb don't identify the device and only wait.
wallrony said:
That's not work for me. adb don't identify the device and only wait.
Click to expand...
Click to collapse
yeah is waiting for any device
So... The problem is that "adb reboot bootloader" doesn't init smartphone in bootloader, but in normal boot process. it's feasible to think about how to "unlock" the "boot of bootloader", since LG may have blocked in this device.
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
indestructible master said:
we should create guides in XDA how to install drivers on PC
as this is common hardship for many.
most preferably some autoinstaller of all drivers, for all devices (taken from manufacturers)
Click to expand...
Click to collapse
No, that's not the problem. Fastboot commands run only when the device's in bootloader device.
So, i solved to persist and search many ways to see something. And that, i got in recovery menu (with Restart System, Wipe, Start ADB sideload - but without connection with PC, as a not connected device, the connection isn't stablished because adbd is a not found command from device shell, in the log returns that, and system wait more or less of 5 minutes to back to recovery menu). In that, i could see the recovery logs, and the last is the normal procedure of a factory reset, i think. In that i encountered some properties that are defined by default:
Code:
ro.boot.flash.locked=1
ro.treble.enabled=true
ro.bootloader=unknown
ro.product.name=mmh551m_f
And by peace of mind, i run
Code:
adb shell "getprop ro.bootloader"
on PC terminal with adb and that returns me the "unknown" that i see in the log. Running
Code:
adb shell "getprop"
returns all prop of the system, so that can be examined to make something. So... I tried to change property using setprop, like ro.boot.flash.locked to 0, or ro.bootloader to any value, but no success.
And to finalize, in contact with LG support whatsapp, the ChatBot returns me a message saying that the bootloader function isn't available by secure reasons.
I think that the value was simply hided from the original value to not access the bootloader, but it's in device ... But with no permission to change the value and not know what value set in the prop.
There are a guide to unlock the boot-loader, but not yet to root.
Root LG K41S + SafetynetAPI pass
Disclaimer These kind of modifications are not for the faint of heart!!! Flash/modify at your own risk!!! I will not be responsible for bricked phones, Dead batteries, world war 3, yada yada yada..... you Know the Rest. :sneaky: Introduction...
forum.xda-developers.com
I followed this process and it doesn't go past the [ fastboot OEM unlock ] step.
I just get < waiting for any device >
However, when I try to use Google Pay and other such apps, I am faced with a security issue.
The question is: Is the bootloader unlocked or not ?
If so, how to relock it ?
Have a device of this wich has a problem with the screen apparently, after changing the screen it wont boot, no battery animation when charger is connected, only a red light and a smooth periodical vibration. If i hold power on and any vol buttons it seems to try boot showing lg logo but fail quicly and keeps off.
Something happened when i repaired it was that side buttons flex got broken so had to order a new one, it passed a lot of time to receive it but i believe that day with broken flex when testing the new screen i think i've seen the battery animation... Im not sure.
But seem its a common issue in this model. So is there something i can do to fix the mainboard?
Solution below.
For those with the same device, I was able to successfully root + pass safetynet, without TWRP or custom recovery. Since this device isn't yet on the forums I thought I should share my findings.
At the time of rooting, I was currently updated to the newest version available (10) and did this through the regular OTA updates.
Preparations
1. Download Magisk Manager Beta from https://magiskmanager.com/magisk-beta/
2. Download the stock firmware for your tablet from https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
3. Download kdrag0n's SafetyNet Fix from: https://github.com/kdrag0n/safetynet-fix/releases
Edit: looks like I missed a step, thanks for the feedback! Point 4 has been corrected to include instructions on how to unlock the bootloader specifically.
4. Unlock your bootloader, instructions on how to enable USB debugging which is needed, can be found here: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html, from there you can open your command prompt, navigate to the directory where you have your fastboot and ADB stored, and type "adb devices" to confirm your device is found (a serial number will display on success) - next type "adb reboot bootloader" to force your tablet to restart into it, finally type "fastboot oem unlock-go" to unlock the bootloader. This voids your warranty.
-- end of edit.
5. Enable USB debugging through developer options (go to settings->about->find build # and tap a handful of times until it says you are a developer.
6. Plug the tablet into your PC, and set the default option to Charge only, or go to file transfer mode and enable USB debugging over file transfer.
Steps
1. Unzip the firmware, there should be a folder called Maincode, in it contains "boot.img" as well as adb/fastboot.
2. Copy the boot.img and Magisk apk to the tablet.
3. Install Magisk
4. Tap on "Install" or "Update" beside Magisk in the app and follow the prompts.
5. You will be asked to select a file, select the boot.img you copied earlier.
6. This will generate a file (it will tell you the path) of a patched boot image.
7. Reboot, and copy the patched boot image to the "Maincode" folder from the tablet.
8. In command prompt, type adb devices and make sure your serial number is shown. If not, review the preparations.
9. Type adb reboot bootloader and you'll see a cute little Tux (penguin)
10. Type fastboot devices and ensure your device is shown, if not then it could be bad drivers on your PC or a crappy USB cable. Check device manager on your computer and make sure you see Lenovo ADB. You may have to force it to install it, or you may see a yellow exclaimation mark - right click on the device and force it to install the Lenovo Bootloader option.
11. Next, in the "Maincode" folder where you put the patched image, rename the old "boot.img" to "stock_boot.img" and the patched version to "boot.img"
12. Back in the command prompt, type fastboot flash boot boot.img
13. Reboot by typing fastboot reboot.
Magisk should now be installed, and your tablet should be rooted. Next, you'll want to go into Magisk and do the following:
Steps:
1. Click on the modules button (bottom of the screen, far right option) and at the top you're given an option to install from storage.
2. Navigate to the SafetyNet Fix zip file and select it, then proceed.
3. You will be given the option to reboot - do this. The first time it may go into recovery, but rebooting brings you back to the home screen.
4. Go back to Magisk, click on the gear at the top right - there is an option to hide Magisk from the system, do this and name it whatever you'd like (just not Magisk) - wait a moment, as the app will restart after it installs.
You can check to make sure you pass SafetyNet in the Magisk (now renamed) app, and root status by downloading one of the countless root checking apps on Google Play Store.
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Bobmat34 said:
Could you let me know a clear way to unlock the bootloader on the Yoga Tab YT-X705F? The instructions you've provided don't point to anything helpful beyond activating USB Debugging.
"4. Unlock your bootloader, instructions: https://www.shizhub.com/2018/12/how-to-enable-disable-usb-debugging.html - do not proceed beyond where it starts talking about TWRP."
I'm looking to root my tablet but cannot as trying to find info on unlocking the bootloader is proving difficult.
Thanks in advance
Click to expand...
Click to collapse
Thanks for pointing that out! - I've updated my notes above, but if your familiar with fastboot the command is simply "fastboot oem unlock-go", no unlock code needed for these guys. It will wipe your device and void your warranty though, in case you're not already aware.
Cheers!
Thanks for this rooting guide! I was able to root my YT-X705F
Here some comments/hints:
- At first make sure your downloading the right stock firmware. I've tried a different one which results into a boot loop. One way to find out the right version is to start into the recovery mode. In the header you will find the right version. In my case it was YT-X705F_S001130_210508_ROW
- Make sure you have actually unlocked the boot loader. "fastboot flash x y.img" worked, so I didn't recognized that the boot loader was not unlocked. This was reason for "fastboot boot y.img" shows errors "FAILED (status read failed (Too many links))".
- The extracted stock firmware have no "Mainfolder". All files, including boot.img and recovery.img, contained in the root directory of the ZIP file.
- After installing Magisk app (v23.0) it shows me: Installed: N/A, Ramdisk: No, A/B: No, SAR: Yes. According to this Magisk installation guide you have to patch the recovery image instead of the boot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Patching the recovery image was fine with Magisk. No errors was shown. Please note I used the recovery.img
After this I was able to boot the patched image without flashing it:
After "fastboot boot patched_recovery.img" nothing happens. The tablet keeps showing me the Linux Tux image. I have to disconnect the USB cable and then I booted into system.
*Upd. never mind, I download the official rom file from lenovo\
Crap. I patched the boot image with Magisk, and by the time I flashed it - the system got updated from S001133 to S001135, and I'm getting a bootloop. Can someone maybe upload original boot img from S001135?
Or what else can I do? the update isn't on the mirror server yet https://mirrors.lolinet.com/firmware/lenovo/Yoga_Smart_Tab/YT-X705F/
Rooting was successful! Thanks for the guide. Since I cannot find any section in the forum for the YT-x705 tablet, I thought I can have a follow up question in here. The reason I rooted was because alexa app keeps getting removed after each reboot. I rooted as I wanted to convert it into a system app.
So far, I've been unsuccessful . I have tried with the systemizer module and titanium backup. Anyone have any idea how we can retain alexa app after a reboot? Interestingly enough, titanium backup shows alexa as frozen after I install alexa from playstore, despite it appearing in my app launcher. I am unable to unfreeze it. Alexa is then removed after I reboot.
Quick question: What do i do if i don't have a "MainCode" folder, on the tablet or in the extracted folder.
or is that just the folder with the maincode, in it?
Thanks, looks like a good guide!
Jim
you're just going into the zip file from step 2 where the boot.img file is. I just followed all these instructions and got my yoga rooted.
ugh...I don't have a device that I can root for a couple of years... and it feels like I'm a complete noob, now!
when i try to flash the boot image I'm getting: FAILED (remote: Partition flashing is not allowed)
When i run fastboot oem device-info i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Finished. Total time: 0.010s
So i don't think i am unlocked. even after following the steps. I've got Developer options, Debugging is obviously working, OEM Unlocking is toggled on.
I feel like on my phones we had to run an adb or fastboot command, and then the device would reboot and reset it and it would then be unlocked.
Am i missing something?
Thanks again!!
Jim
p.s. and once i get it working, what roms can i flash? any of the "yoga" roms? or do i need to look at something specific like the 3 or 4?
answered my own question!
i had to run: fastboot oem unlock-go
the device rebooted and reset
now i get this:
PS C:\Users\Jim\Downloads\YT-X705F_S001135_210909_ROW (1)> ./fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.007s]
Now on to the next step!
So anyone know what ROMs i should use and how best to install them, i don't think we have a working TWRP, do we?
... after crash of my booting Android 10 system last stock rom my yt-x705F 210909 can't be rooted anymore!
i use some app and this app ask for busybox .... so crash !!!
i reset tablet by system recovery .
"wipe data/ factory reset"
after restart my tablet is working again.
Bootloader is still open
also develover mode is working USB Debugging etc.
but no rooting alowed by patching root img .. see next
now i try to install stock rom NEW but some error
"apply update from external storage " get error
same is from "Apply update from ADB" abd sideload file.img
are this zip files from this server corrupt? mirros lolinet ?
i use magisk 25.2 i try all option with hook on recovery also vbmeta
patch both boot.img and recovery.img
after patch one of these img device runs into the bootloader , tux start up.
if i patch stock boot.img device booting normal but NO ROOT
also twrp can't no flash only option "fastboot boot twrp.img"
"fastboot boot flash recovery twrp.img" not working
if i use twrp by "fastboot boot twrp.img" zip stockrom makes also error
someone knows about RESCUE and SMART ASSISTENT" LMSA Tool ?
any suggestion
how is this working ?
go on settings > about tablet > push a view times on Hardware-Version
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
looserintheend said:
NEW Firmware update YT_X705F_S001137_220721_ROW for yoga
what's new?
Click to expand...
Click to collapse
Know where can I find this firmware?