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?
Related
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
Is it an easy process? Ive been rooting since 2011 so i can't imagine rooting a chrome book would be too hard?
Sent from my LG-H811 using XDA Free mobile app
I don't think it's that hard but I've only tried it when testing it for a netbook. You will have to search that model as it varies. Usually called developer mode and dual booting with another Linux distribution.
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
kibmikey1 said:
Yes. You just need to enable developer mode, install Arch Linux, disable software verification settings, and obtain adb/fastboot via command prompt (although the versions may or may not be outdated).
Click to expand...
Click to collapse
Hi, I'm trying to flash Marshmallow on my Nexus 7 using my Dell Chromebook. I'm almost there but my N7 says I have to update my ADB to 1.0.32. Unfortunately Ubuntu hasn't updated their repositories so any idea how I can update ADB on my chromebook?
thanks
Sent from my D6503 using Tapatalk
mrme73 said:
Technically yes but you will have to root the Chromebook first to gain access to the Linux command line to install the adb software as root
Click to expand...
Click to collapse
if i do this will it "root" my phone so I can get apps that require root?
Also, I have a galaxy j3 eclipse, will this work on my phone
rickyiswhite said:
I was looking at a toshiba chromebook 2 but was wondering if you can root a phone on it as i wanted to root my G4.
Sent from my LG-H811 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can root a phone on a chromebook just put it in developer mode and use your crosh shell to run adb and fastboot.
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
phone not connecting
What do i do if phone does not connect?
how do i put the TWRP.img file into the same folder where the fastboot and adb files are? or how do i type the command to flash it to my oneplus 7 pro in my crosh shell window.
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
lonnie89 said:
I am able to unlock my boot-loader via adb and and fastboot but cant find away to access the Chromebooks file system to flash twrp and and custom roms. help!!! Im attempting to convert the Moto G7 to a more secure linux rom.
Click to expand...
Click to collapse
On my pixelbook with the beta Linux installed copy the downloadet twrp.img file to the linux folder that's located in the files app. Should then show up in your home Linux directory.
How do I get access to that file system in croots and flash it to the phone.
How do I get access to the file and move to the phone in croots what are the commands. It's my my downloads folder.
garretts228 said:
There is a lack of information and a bit of misinformation here. You don't "root" your chromebook and you don't have to install Arch Linux. So here is the breakdown. If you want to root your phone you can do so by using ADB. To do this you have to do a few things:
1. Enable Developer mode on your chromebook (this requires a powerwash which will delete data and reset your chromebook)
2. Open Crosh by pressing Ctrl + Alt + T
3. Type "shell" and press enter.
4. Update ADB and move the binaries to their appropriate location by typing:
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
5. Make sure ADB is working by typing "adb --version" and pressing enter. This will tell you the version of ADB that is installed, which the current version is 1.0.40 Typing "adb --version" will also tell you where ADB has been installed to. This should say: /usr/local/bin
6. Enable Developer Mode on your phone and enable USB Debugging within the Developer settings.
7. Test that you can communicate with your phone by typing "adb devices" with your phone connected to your chromebook. If your device shows up make sure that you can send data to your phone by typing "adb reboot recovery". This should reboot your device into recovery.
8. If you were able to successfully reboot your phone into recovery using ADB then you have everything you need to root your phone using your chromebook. Just look up how to root your phone using ADB and you will be good to go. This is the method I used to unlock my Bootloader, install a Custom Recovery and the method I used to root my OnePlus 6T with Magisk.
Click to expand...
Click to collapse
Hi. Thanks for a working method. I have tried each step and Crosh gave me error:
bash: /usr/local/bin/adb: cannot execute binary file: Exec format error
One question - do i have to be on "developer channel" in Chromebook?
Coz then i will have to reinstall Chromebook.
Best Regards
Nick
{
"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"
}
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
eurovive said:
Finally yes - i need to be in Developer mode for ADB.
Full article is here - how to and what is what.
How to Use ADB and Fastboot on a Chromebook
For a long time, Chromebook users who also need access to the Android Debug Utility (ADB) and Fastboot for Android devices were left with one option: Crouton. Now, however, both ADB and Fastboot are included in Chrome OS. Here’s how to access them.
www.howtogeek.com
Click to expand...
Click to collapse
Sorry I didn't leave that detail behind for you, but yes that method does indeed require dev mode. However there are other methods that don't require it now using Linux. I have not done them so I am only forwarding this information:
https://www.reddit.com/r/chromeos/comments/dtwfpm
Thats a nice suggestion too. As someone says Chromebook should be Intel-ready to run Android apps, thats why i was thinking whats wrong. I have Arm based Tegra K1 with saying some how limited support of updates, therefore having support for Crostini feature. Will try later.
If you want to repost this guide to other websites, please let me know before you repost.
For Chinese users: 中文版教程将会在dospy发布。
Click to expand...
Click to collapse
So after you unlock the bootloader successfully, you definitely want to install custom ROM, or at least root the phone, right?
Here's the guide about rooting Nokia 3.2 / 4.2.
This guide could probably work on Nokia 6.2 / 7.2 in the future.
Step 1: Unlock the bootloader
https://forum.xda-developers.com/nokia-4-2/how-to/guide-how-to-unlock-bootloader-nokia-4-2-t3962402
For Nokia 3.2, you'll need to read this as well: https://forum.xda-developers.com/nokia-3-2/how-to/guide-how-to-trigger-nokia-3-2-to-edl-t3962841
Step 2: Acknowledge current slot
You have two methods.
Method 1: After USB debugging enabled, execute this command:
Code:
adb shell getprop ro.boot.slot_suffix
Method 2: Under fastboot mode, execute this command:
Code:
fastboot getvar current-slot
We assume the current slot is b.
Step 3: Trigger the phone to EDL mode again
There's a hidden command in aboot known as "fastboot reboot-emergency".
However, normal fastboot binary doesn't have that command at all, so we need to compile a binary or hack the binary.
For Windows users, I've provided the fastboot binary that can use this command, and I renamed it to edl-fastboot.exe. You can download it on the attachment below.
For macOS/Linux distro users, I'm afraid you have to fork the source code, edit related content and compile yourself.
So with this special version of fastboot binary, we can boot the phone to EDL mode directly:
Code:
edl-fastboot.exe reboot-emergency
But wait, why didn't you mention this command when you released bootloader unlock guide?
That's because, if you attempt to use this command under locked bootloader, bootloader will response "Permission denied, auth needed. " and refuse to proceed the command.
I don't know how the authentication is done yet, but it's definitely not something that average developers can access to.
Click to expand...
Click to collapse
Step 4: Use partition manager to dump the partition
If you've came so far when unlocking the bootloader, you have already know the great partition manager.
Still, we assume the COM port number is 8 (COM8).
When the partition list appears, find "boot_b" (or boot_a if the current slot is a), right click on it, choose "Manage Partition Data" and click "Read Data". Then fh_loader binary will dump the boot image to your PC.
For Windows users, it's located at
Code:
%AppData%\Qualcomm\QFIL\COMPORT_8
Where %AppData% is actually C:\Users\your_user_name\AppData\Roaming .
The filename looks like this: ReadData_emmc_Lun0_0x3a000_Len65536_DT_07_09_2019_13_55_54.bin
Now close the partition manager, your phone will exit EDL mode and boot normally.
If you're interested in dumping full eMMC storage, you may want to read this: https://forum.xda-developers.com/android/general/guide-how-to-dump-write-storage-t3949588
Step 5: Install Magisk Manager and patch the boot image you dumped
I think everyone who reading this guide knows where to download Magisk Manager.
Copy the boot image you dumped with QFIL to Download directory in your phone's internal storage, and rename it to boot.img for your convenience.
In case you don't know how to patch, read this guide: https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Step 6: Flash patched boot image and reinstall Magisk for ensurance
After you pulled patched boot image from your phone, reboot your phone to fastboot mode, then execute these commands:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Note, temporarily boot method introduced back for old A/B devices like Nokia 7 Plus no longer works on Nokia 3.2 / 4.2 - it will boot your phone to Qualcomm 900E mode.
Once your phone booted to normal OS, open Magisk Manager, and reinstall Magisk and required runtime to make the root much more effective.
You may want to read this guide if you want to inherit root along with OTA update: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Extra info about custom rom:
I've tested PHH-Treble GSI on Nokia 4.2 and it made me disappointed.
The vendor compatibility is worse than FIH made Android Phones.
You may want to read this for more details: https://github.com/phhusson/treble_experimentations/wiki/Nokia-4.2
Next preview: Stock firmware reinstallation guide. Note, Nokia 3.2 / 4.2 are not made by FIH, so OST LA no longer works on both devices.
Special thanks:
@topjohnwu for Magisk
Wingtech for leaking prototype units
Reserved
not detected
my pc doesn't detect the phone when its in edl mode. before people start asking I unlocked the bootloader by enabling oem unlock in the phone settings.
I have a TA-1156 (a 3.2 variant) that has a different mainboard layout. For quite a while, I tried in vain to bring it into EDL mode - until I just tried the fastboot command "flash unlock" which worked.
I guess I should have tried that right away as I did have the OEM unlocking option in the developer setup.
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
I can enter EDL mode easily now with the patched fastboot exe. The correct driver is active and QFIL detects the phone. However, as soon as I follow the instructions by setting the programmer, and then try to start the partition manager, the phone stops responding.
After a while, I get a "sahara" error about no reply from the phone.
I wonder if someone has a stock boot.img of the Nokia 3.2 (build 00EEA) lying around ...
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
{
"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"
}
JFDee said:
Anyway, now I'm unlocked but can't access the partitions with the QFIL partition manager. I suspect the phone expects a different programmer than prog_emmc_firehose_8937_ddr.
Click to expand...
Click to collapse
My guess was right. Now I'm able to reply to myself with a solution.
I tried a different prog_emmc_firehose_8937_ddr than the one provided by @hikari_calyx in the unlock thread
There is a programmer with the same name in this firmware:
sprout-015B-0-00WW-B01 .rar
It's provided by @bouyhy01 in his rooting thread.
The size of the programmer file is slightly different:
Code:
hikari_calyx: 428,936 bytes
Firmware: 428,944 bytes
Long story short: the different programmer worked in QFIL, so the partition manager worked as well, I got my own boot image, patched, flashed and had root - finally ... Thanks for all the research work, hikari_calyx and bouyhy01 !
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment prog_emmc_firehose_8937_ddr_from_fw.zip
.
JFDee said:
Here is someone else's photo of the mainboard (I just realized that it's actually from hikari_calyx!) but on mine, the right one of the test points you marked in your 3.2 variant does not exist, so I edited it out in the photo:
View attachment 4867461
Click to expand...
Click to collapse
I guess the only point can be connected to the ground, for example, the RF shield is grounded.
JFDee said:
Attached is the working programmer file, in case anyone else stumbles upon the same problem. By the way, my phone has the October security patch installed which is currently the latest available.
View attachment 4869373
.
Click to expand...
Click to collapse
Thanks for info. Mine Nokia 3.2 is a prototype unit, so I don't know the situation of other versions of Nokia 3.2.
Hello, I have tried this manual for rooting Nokia 4.2 with last security update of 5th of November. After 5 step (flashing patched boot image) my phone try to reboot and then asked for factory reset (Can't load android system - Your data may be corrupt). After making factory reset there were no root at all.
What can i do next ?
PS. It's strange enough when i download boot_b image it was 63.4 Mb snd when i have patched it by Magisk manager - the size od magisk_patched.img became 10.2 Mb
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).
Yesterday my phone offered me to update ColorOS to PEUM00_11_a_12 (about 400 MB)
I did not noticed any change. Still based on Android 11.
Removed chinese software has not been reinstalled afterwards.
Changelog (translated via Google)
system
[Optimization] System stability
[Fix] In the system clone scene, the problem that the live wallpaper disappears after one-click cleaning
[Fix] In some scenarios, there is a low probability that the sound cannot be heard during a call
[Fix] The screen move button disappears when launching some game apps in compatibility mode
[Updated] Android security patch to February 2022 to improve system security
Screen
[Optimization] Bright screen response speed after large screen is expanded
[Optimization] The animation of golden peacock wallpaper shows fluency
Input
[Fix] When the input method is set to the handwriting keyboard, the handwriting keyboard cannot be called up with low probability
[Fix] The problem that the input method cannot be called when the search box on the right side of CCTV is used
camera
[Fix] In some scenarios, the camera crashes with a low probability after being turned on
[Fix] In some scenes, there is a low probability of noise in video recording
To view more content and participate in discussions, please log in:
OPPO社区
www.oppo.cn
Precautions
1. To reduce the risk of version upgrade, it is recommended to back up personal data before upgrading.
2. During the software upgrade process, the temperature of the mobile phone may increase slightly for a short time, and it will quickly return to normal after the upgrade is completed, which is a normal phenomenon.
3. If you encounter any problems during use, please contact the official customer service for feedback or consultation.
The "Rotation" app no longer works for me since this update. Does anyone else have this problem?
Can you elaborate on ""Rotation"?
No more wifi calling option
It seems that after the update, wifi calling is gone. I installed android studio and tried to enable it through the below adb commands, but couldn't get the device to be recognized in recovery mode. Its showing unauthorized in recovery mode.
1) Enable developer options in the phone and enable debugging mode, change to MTP connection
2) adb devices -＞its showing the device named attached
3) adb reboot fastboot -＞ phone is rebooted and shows the language option
4) fastboot reboot recovery -＞ rebooting into recovery, finished
5) adb devices -> showing unauthorized
Does anyone know how to enter the recovery mode in this phone?
trojan1111 said:
It seems that after the update, wifi calling is gone. I installed android studio and tried to enable it through the below adb commands, but couldn't get the device to be recognized in recovery mode. Its showing unauthorized in recovery mode.
1) Enable developer options in the phone and enable debugging mode, change to MTP connection
2) adb devices -＞its showing the device named attached
3) adb reboot fastboot -＞ phone is rebooted and shows the language option
4) fastboot reboot recovery -＞ rebooting into recovery, finished
5) adb devices -> showing unauthorized
Does anyone know how to enter the recovery mode in this phone?
Click to expand...
Click to collapse
Once phone is completely powered off hold the volume down button and power button until phone has started in recovery mode
{
"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"
}
Thanks, Tim-2.0. However, if I use that way to enter recovery mode, I cannot get my device shown up in adb commands.
Using the adb commands to reboot the device and triggered the recovery mode, adb devices show "unauthorized", so I cannot proceed to do the adb shell command.
Tim-2.0 said:
Once phone is completely powered off hold the volume down button and power button until phone has started in recovery mode
View attachment 5556199
Click to expand...
Click to collapse
Yes and to be known because the delete option in the menu isn't working
trojan1111 said:
Thanks, Tim-2.0. However, if I use that way to enter recovery mode, I cannot get my device shown up in adb commands.
View attachment 5556235
Using the adb commands to reboot the device and triggered the recovery mode, adb devices show "unauthorized", so I cannot proceed to do the adb shell command.
View attachment 5556239
Click to expand...
Click to collapse
Uh I see, fair enough..
It seems you were able to boot into fastboot? I cannot even do that. It very briefly does before restarting itself and powering on normally. This flashes up on the screen for about a second but that's it:
Tim-2.0 said:
Uh I see, fair enough..
It seems you were able to boot into fastboot? I cannot even do that. It very briefly does before restarting itself and powering on normally. This flashes up on the screen for about a second but that's it:
View attachment 5557135
View attachment 5557137
Click to expand...
Click to collapse
Yes, I was able to boot into fastboot through the adb command. I have never seen that screen before. Weird, I thought all Oppo Find N phones are the same because there is only one version - CN one.
trojan1111 said:
Yes, I was able to boot into fastboot through the adb command. I have never seen that screen before. Weird, I thought all Oppo Find N phones are the same because there is only one version - CN one.
Click to expand...
Click to collapse
Yeah I figured it out, I was using the wrong adb command
Also, I have solved your device not showing up in fastboot problem! It did the same to me.. Folllow this guide and update the fastboot driver
Actually scrap that, I have just remembered that it was an adb / recovery issue. Have you resolved this yet trojan1111?
Tim-2.0 said:
Actually scrap that, I have just remembered that it was an adb / recovery issue. Have you resolved this yet trojan1111?
Click to expand...
Click to collapse
No, i still haven't been able to solve the problem.
If its happen after update OTA, then you need flash the phone with full file.
PS : You may try factory reset
AzimBahar said:
If its happen after update OTA, then you need flash the phone with full file.
PS : You may try factory reset
Click to expand...
Click to collapse
I tried factory reset already and it didn’t work. I guess there is nothing that can be done because there is nowhere to download the firmware for this phone. Hopefully, the next update will fix this issue.
I’ve seen Firmware is available on ROMdevelopers. BUT it’s required official login to flash.
(Login can get from service Center guy or guy who do remotely)
On another thread, someone was able to download a firmware for the phone.
Find N root
Given the pain of trying to make this phone somewhat functional and something that resembles the level of customisation that I am used to I am thinking I might attempt to root my device. I am pretty sure by doing so I can get Android Auto...
forum.xda-developers.com
Maybe you can take a look on it and download the firmware.
Is there any way to bring wifi calling and volte back ????
I lost them since I updated my device.
Any advice??
z06forever said:
Any advice??
Click to expand...
Click to collapse
No way, also in Japan many of provider lost VoLTE call.
you may try to downgrade to the firmware below, but I haven't heard who tried, so not sure.
Oppo Find N 5G PEUM00 Stock Firmware ROM (Flash File)
Download the official Oppo Find N 5G PEUM00 Stock Firmware ROM (Flash File) for your Oppo Mobile. We also provide all other Oppo Stock Firmware for free.
firmwarefile.com
So I have a Infinix Note 12 pro 4g x676b. The manufacturer of this model has another model with the same name which is more popular. Now let me get to the point. I wanted to root this phone with magisk. its android 12. I tried a few tutorials for it but i realised i need twrp, but this phone model dosent have a twrp img. So i tried the method of fastboot and adb. i patched my boot.img using magisk and then try to patch it to my mobile using my pc. The adb device gets detected and i get it into fastboot. But in fastboot the device does not get recognized. I tried installing all the drivers but the manufacturer does not provide any. I got every unnofical driver installed but still it dosent detect. And also my phone does not get detected in device manager either in other devices or portable devices. What do i do now?
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
xXx yYy said:
May be this guide is useful:
How to get into fastboot and How to exit fastboot INFINIX Note 12 (2023)? - HardReset.info
The Fastboot Tutorial will show you the easiest way to access the hidden model called fastboot. Check out the secret combination of keys that will boot your device into fastboot.
www.hardreset.info
Click to expand...
Click to collapse
that is not my question tho. My phone does not get recognised on my windows pc
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is getting recognised as Unknown device?
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
{
"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"
}
Take note that a phone's Android is rooted if SU is present in Android's filesystem.
xXx yYy said:
A PC-connection isn't required at all, you can run ADB and/or Fastboot commands from phone, too. Note: Android must got rooted.
Click to expand...
Click to collapse
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
potatosil said:
that is not my question tho. My phone does not get recognised on my windows pc
Click to expand...
Click to collapse
It is a driver related problem.
You may be able to get your work done using wireless adb, although flashing stuff wirelessly is very risky (if the connection breaks whilst the flashing is still going on).
mvikrant97 said:
It is getting recognised as Unknown device?
Click to expand...
Click to collapse
not even an unknown device just nothing is there
potatosil said:
i am asking my question to get my phone rooted. If it was already rooted i wouldnt have made a thread
Click to expand...
Click to collapse
To root a phone's Android Fastboot isn't needed as you suppose : ADB is the correct tool.
Most people instead of adb.exe what comes with Android SDK use adbLink2 app what provides a link between your Android device and your computer.
adbLink2 features:
Install Programs without Android SDK
ADB/Fastboot enabled command-line
Busybox for root and non-root
Built-in WIFI/USB remote
Manage devices via USB or IP address
Root-aware File Manager for Android devices
Install/Uninstall Apps
Connect to devices ad hoc
Manage multiple devices from one PC
Edit XML and other files on your devices
Log file viewer for adbLink2
Hyperlinked HTML Help
adbLink2 is available for Windows, macOS and Linux/ChromeOS
BTW to clarify things, you obviously don't know of:
1.
Before I define root, it's important to understand why it exists and how it works. It's because Android uses permissions ( Linux-based permissions, to be exact ) in the file structure. Every file, every folder and every partition has a set of permissions. These permissions decide who can read a file ( look at or access the contents without changing them ), write to a file ( be able to change the contents of that file, or create a new file inside a folder or partition ) and execute a file ( run the file if it's a type that can run, like an app ). This is done based on users and permissions - certain users have access, while users who don't have the right permissions are blocked from having access.
When you first set up your phone and turn it on for the first time, you are assigned a user ID. If another user logs in via Google, they are assigned a different user ID. When an app is installed on your phone, it's also assigned a user ID of its own. The system itself is a user and other processes that need to run on your phone may have their own user ID. Everything that can do anything to any files on your Android is a user.
2.
To get elevated permissions ( root access ) you place the SU binary ( SubstituteUser ) in a spot that it can run when it's called to run - that's called a PATH - e.g /data/local/tmp. If any app is in user ID's PATH it will run without telling the system exactly where it is. You also need to make sure the SU binary is in a spot that your user ID has permission to execute ( run ) files. Any other app ( Google Play has plenty of apps that need root permissions ) will also need the same access. When you use a method to root your phone, all this is sorted out by the folks who built the root method.
3.
This is where root comes in. The SU binary uses flags when it's run to tell the system what user ID you want to switch to. For example, if I run the SU binary on my Google Pixel phone like this "su Jim -c 'mount - o rw,remount -t auto /system'" I will run the mount command as the user Jim ( after supplying Jim's password ). If I run the SU binary with no flags or arguments, it switches me to the root user. Normally you would need to supply a password, but since "root" is an unused user on Android it has no password. Running the command "su" will switch you to the user root, and assign you the user ID of 0, and put you in the root group. You are now the Super User.
4.
As the Super User you can do anything to any file, folder or partition on your Android. By anything, I mean literally anything. You can remove bloatware apps and you can also remove essential system files that break your phone. You can also do things to the hardware like change the CPU frequency and ruin your phone forever.