Hi everyone!!
IMPORTANT:NEVER SELECT ERASE OR FORMAT PARTITIONS IN LGUP. IT WILL MESS WITH YOUR IMEI
Im making a new guide to unlock your bootloader/root your device. Its easier to do a little bit risker but if you do it slowly you wont mess up your phone and in the event you do you can always recover it. Remember to FOLLOW ALL THE STEPS or you may end up messing up your phone, The best thing is, you dont need to downgrade to even unlock the bootloader!!
DISCLAIMER: I AM NOT RESPONSIBLE IF YOUR PHONE BRICKS! YOU ARE FOLLOWING THIS GUIDE AND ITS YOUR CHOICE TO DO IT OR NOT TO DO IT AND YOURE THE ONE DOING IT. I JUST WANT TO HELP OTHERS OUT.
If you cant for some reason access fastboot even flashing the v35 file, use this guide: https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031 it says verizon but i think most of the models of the g7 cant acess fastboot so you can try this.
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
--The LG FIrehose file
- QPST/QFIL
-9008 drivers FOLLOW THIS GUIDE!! To install drivers properly IF WINDOWS DOESNT INSTALL THEM AUTOMATICALLY!!
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Steps.
Download the V35 abl,LG Fire house file, download and install qppst and install the 9008 drivers (WUNDOWS 10 should automatically do it for you) If not, download it and install them.
Boot into edl mode via connecting your phone to the pc then turning it off. Hold Vo- and power and keep pushing the vol+ button multiple times when it turns off.
Go into device manager and check if its detected. to check open up device manager and check Ports and it should say Some port 9009 Qualcomm or something like that (IF theres a question mark, exclamation mark or it says qhusb bulk even after you install the drivers, make sure you disable driver signature enforcment on windows and install the drivers again. Theres multiple ways to do it just google on how to disable driver signature enforcment windows 10. Same with windows 7/8,)
Run as administrator qfil and select flat build,.
--Programmer Type: Load the firehose file
-- On the top go to configuration and where it says Device type, make sure you change it to ufs.
-- Click ok to save and exit
At this point qfil should be detecting your port . If not there should be a select port button next to it on top.
Go to Tools then Partition Manager
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
Search for abl_a and right click on it. First do Read Data, it should take only a couple of seconds Then Load Image and load the v35 image. It should say GPT Finished or something like that at the log with no errors.
Reboot holding volume - and power for like 20-30 seconds until the lg logo comes up Then hold the down button to boot into fastboot or it will automatically boot into fastboot depending on what version of android you are on.
Open the folder where your adb tools are, then hold shift +Right Click in the folder and open powershell. Type and enter CMD
Enter: Fastboot oem unlock it should output with OKAY, If it gives you unknown command, try a USB 2.0 port and then turn off your phone and while its booting up enter the command before you boot into fastboot. Once thats done dont close the window yet!!
Once thats done you can now restore your other abl so you can boot back into android. To do that run %appdata% in the search bar or in the run window by holding the windows button and pressing the R button. Then you should be in C:\Users\{YOUR USERNAME}\AppData\Roaming
Open up the Qualcomm folder --> QFIL --> COMPORT#
There should be a ReadData Blah blah.bin in there. Drag and drop that in the folder where your adb tools are
then go back to the window i told you not to close (The powershell/cmd window) then do fastboot flash abl_a (The file name with ReadData) without the ( ).
Now you can turn off the phone vial holding volume - and power and then reboot into android!! You should get a bootloader unlocked or a cannot be checked for courrption message! Congrats your bootloader is unlocked!!
To root: Just back up your boot image via and then find it in %Appdata% put it in your phone then use magisk manager to patch the boot file and then take that boot file and then flash it to boot_a via edl.
I tried my best to write this guide and sorry for my grammatical mistakes. Ill be helping people unlock/root their bootloaders for free during this covid time as well. If you want to donate you can always tell me but its not necessary.
Ill try making a video as soon as i can.
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks ?
nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Should be in theory
nyolai said:
Nice guide,
Will I able to use this guide to root my G7 verizon version ? (G710VM)
Thanks
Click to expand...
Click to collapse
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
netookska05 said:
Yes and no. Yes it will unlock the bootloader but the problem with verizon there is no fastboot unless you erase the laf imgs.
Which is why in my guide I use the crossflashed ULM11g it has fastboot and the oem unlock enable button which makes it easier to issue the "fastboot oem unlock" command.
Give it a try and if your not good at doing this with qfil will brick your device. If you run into issues try my guide.
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031
Click to expand...
Click to collapse
Ill add your link to my thread.
Awesomeslayerg said:
Requirments:
-A PC
-USB Cable to connect your phone of course
- V35 ABL
-The LG FIrehose file
- QPST/QFIL
-9008 drivers
-ADB PLATFORM or someway to access fastboot via cmd
-PATIENCE!!
Click to expand...
Click to collapse
All the links to files redirect to "Unbrick G7" file.
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
TigerV said:
I m stuck in this step
A window should pop up with all the partitions. If you get a shara failed error, make sure your drivers are installed correctly and try rebooting into edl again once more. To do that just hold vol - and power until the lg logo comes up and then keep holding vol - and power again and once it turns off again just do the edl combination again.
always got Shara failed error.
Has windows 10 and tried all possibilities.
The driver not detected automatically so installed manually. Please Help
Click to expand...
Click to collapse
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Awesomeslayerg said:
Do you have ELF File for the programmer> The one included in the zip file? Sorry i didnt include the ABL Ill update the zip soon Do you get an exclmation mark or something on the ports in devnice manager?
Click to expand...
Click to collapse
Thanks for your update.
Yes I m using the same ELF file from zip.
The driver not installed automatically so I have installed it manually via device manager and thn no exclamation mark. But somehow its not work. Tried many time but the same issue
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
TigerV said:
Can you please update the link of 9008 driver and guide? Its not working (may be bad link)
Click to expand...
Click to collapse
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
****.. Unlocked bootloader. Lost Widewine L1. Relocked bootloader again. but Widewine L3 is available. Anyway to get it back to L1. I remember My pixel and Op6 could get back Widewine L1 after relocking bootloader again.
Awesomeslayerg said:
Fixed it. Make sure whenever you close qfil or everythime you get that error just reboot into edl mode again.
Click to expand...
Click to collapse
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
TigerV said:
Thanks somehow I manged for get edl and flashed the image.
Now getting another issue. when I do "Fastboot oem unlock" its say
FAILED (remote: unknown command)
finished. total time: 0.002s
tried will all method with different PC, Different USB and all as mentioned in the main post, but no luck.
Click to expand...
Click to collapse
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Hey op or whomever can help point me in the right direction: when looking at used/refurbished g7's which models should I ask sellers about or steer away from like the LMG710R (I know the LMG710TM is a no go, what about the Sprint unlocked for GSM and what's there code if I want to avoid them?)?
Thanks.
the v35abl file is not avaliable
wente said:
the v35abl file is not avaliable
Click to expand...
Click to collapse
here is the same link from main post (that link has some hyperlink issue)
https://androidfilehost.com/?fid=1899786940962574206
Would this work on LG710N (korean) ??
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Awesomeslayerg said:
From ecperince just keep doing that. Nut before entering fastboot put the command in and press enter then reboot directly into fastboot. Kerp doing it unt you see the orsnge unlocked bootloader on your g7 screen
Click to expand...
Click to collapse
have tried many many time and all possible way but no luck
---------- Post added at 06:25 PM ---------- Previous post was at 06:23 PM ----------
coolrevi said:
Once the bootloader is unlocked with this method DRM is lost forever. Even relocking the bootloader will not bring Widewine certification to L1. I am back to stock with locked bootloader. Widewine is at L3.
Click to expand...
Click to collapse
re-lock and stock flash also not in bring back to L1? I can not even unlock my boot-loader. stuck at "fastboot oem unlock" and its not working, tried all possible way
Related
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
Hlw all.
Sorry for late to write this post. I will write this post in several parts. So Don't angry if i am late.
PART 1:
HOW TO UNLOCK BOOTLOADER
Click to expand...
Click to collapse
First add a xiaomi account on your device.
Now
1. Go settings
2. My Devices
3. All Specs
4.Miui Version
Tap 5 times to activate Developer Option.
Now return settings menu
And Scroll down
Go
1. Additional Settings
2. Developer option
3.OEM Unlocking [ On This]
Now turn on your phone's internet connection through personal data pack.
Now go Mi unlock status and press add account .
Your Device will be added successfully.
You have to wait 10 days for unlock your bootloader.
Xiaomi privacy policy
Click to expand...
Click to collapse
Now Go xiaomi website and Download xiaomi unlock tool .
You will need a pc or laptop with internet connection for this process.
Extract that zip and open Xiaomi unlock.exe
Login your Xiaomi account.
Backup important Documents on your phone.
Click to expand...
Click to collapse
Power off your Phone
Press "Power button + Volume down"
for fastboot mod .
Connect your phone through usb cable
Now press unlock
When it will complete 100%, Your device will unlocked and Reseted.
PART 2:
INSTALL TWRP
Click to expand...
Click to collapse
First you have to Download TWRP. Official twrp is not release. So you have to download unofficial twrp. it is safe and 100% well for Mi cc9. Because i am using this.
Download this from here:
https://androidfilehost.com/?fid=6006931924117916679
And Also download
adb usb driver version 1.4.3.exe
Install this software .
Next you have to enable usb debugging in your device.
Connect via usb cable to your pc or laptop.
Now unzip the twrp file and go that folder .
See many cmd command file in this zip inside.
Just open last one
Now write
adb devices
Click to expand...
Click to collapse
Screen on your phone and Ok the demon they ask.
Next write
adb reboot bootloader
Click to expand...
Click to collapse
Now write
fastboot flash recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
fastboot boot recovery (copy full name of twrp and paste here).img
Click to expand...
Click to collapse
Twrp will install successfully. just disconnect your phone and press power button + volume up.
Twrp will appear which one you install.
Any help you need just comments here if you failed.
Thats all for today.
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
dragokanev said:
Hi, I unlocked the Boot Loader but now I get a screeen in chinese which I am assuming is asking for my Mi account,phone number or email but every time I type any of those a red messege showes under the box which I am assuming meanes that something is wrong. Does anyone had the same problem and solution because I am pretty sure I know my Mi account and my phone number and they are tiped in correct.
Click to expand...
Click to collapse
Use those phone number and password which one you sing in for unlock bootloader.you need internet connection to complete this process.
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
Yes. You have to write:
fastboot boot recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img
easier to rename the file to twrp.img .....
Please help to restore CC 9
Please help me bring my Xiaomi CC 9 back to life. I updated it with MIUI 11.3.3.0.PFGEUXM and my device does not boot normally. My bootloader is locked and an account is not installed in the developer settings. Does anyone know what to do ???
I got error -1 on my smartphone when I added account and device in the '' mi unlock status '' menu.
How to solve
--
Edit:
resolved: I logged out and logged into the Mi account on the device and gave no error
I have to wait 168H to unlock
Tks
GSI's are quite good. I have good SOT with ArrowOS GSI: 12h - 13 h. I think it's more interesting to use Pie GSI's for now.
Where can I get this ArrowOs GSI rom?
Unlock tool stops at 50%
What should I do when the Unlock Tool stops at 50% and reports: couldn't verify the device. Is it because I haven't waited the 10 days yet?
You have to wait to unlock bootloader.
majigs said:
im stuck at "fastboot boot recovery (copy full name of twrp and paste here).img"
is it the same file "recovery-TWRP-3.3.1-0709-XIAOMI_CC9-CN-wzsx150.img"?
Click to expand...
Click to collapse
you dont have to boot the image if you flashed it first, if you did 'fastboot flash recovery recoveryname.img', no reason to do the boot part, just do fastboot reboot-recovery
if you dont want to flash twrp over your stock recovery, then use the fastboot boot recoveryname.img and then mess around with twrp, backup everything and flash a new rom and reboot, next time you reboot to recovery, stock will still be there
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
axlina said:
Hello. I'm having problems unlocking my new phone. When i open Mi unlock tool, unlock option is greyed out.
I installed drivers through unlock app and option "install drivers" Also installed adb drivers that I got with ulock app through device manager - add legacy hardware
But something is wrong. Someone please help me.
Click to expand...
Click to collapse
In this unlock tool folder ( Install Drider) one file exist.
You must install it. Then your device will connect.
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
axlina said:
someone please help me. I unlocked bootloader and trying to install TWRP but everytime I try it's stuck at sending recovery. I've waited for 10 minutes and then I qut. What am I doing wrong?
Commands adb devices and fastboot devices recognize my phone.
Click to expand...
Click to collapse
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
TelumLetiferum said:
Unfortunately I can't help you with that but I have a question did you wait 10 days or not cause my phone just refuses to cooperate with the unlock tool. Sometimes the fastboot logo just disapears and it says press any button to shutdown.
Edit: Just to clarify the flash tool does not say anything about the waiting period. If someone can help me or clarify the situation I would greatly appreciate it.
Alright so it appears to either be a USB gen limitation or just my plain ass stupidity for not installing adb drivers. Hell if I know but either way now it says how many days I have to wait so nice.
Click to expand...
Click to collapse
Download 15 seconds adb installer and answer question with three yyy.
I waited 43 hours to unlock bootloader.
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
kingofmb said:
I have performed all the steps successfully, but unable to boot into twrp by pressing power + vol up, still booting in stock one, anybody facing the same issue?
Click to expand...
Click to collapse
It's power button +volume down... Try again
Hi guys, I need some help. I flashed 1.6 in edl EU firmware with MiFlash. Now when I load the phone it comes up saying that the bootloader is unlocked and press power to continue. This stops me from holding down power and volume to get into fastboot. I have also tried going into recovery and reboot into bootloader but still no fastboot. Just bootloader is unlocked and press power to continue as I have mentioned before.
Please help! ? As need fast boot to install recovery!
ztxaxonjay said:
Hi guys, I need some help. I flashed 1.6 in edl EU firmware with MiFlash. Now when I load the phone it comes up saying that the bootloader is unlocked and press power to continue. This stops me from holding down power and volume to get into fastboot. I have also tried going into recovery and reboot into bootloader but still no fastboot. Just bootloader is unlocked and press power to continue as I have mentioned before.
Please help! ? As need fast boot to install recovery!
Click to expand...
Click to collapse
What does it say in developer options?
In development options it says bootloader is unlocked under OEM unlocking
also I turned on USB debugging
ztxaxonjay said:
In development options it says bootloader is unlocked under OEM unlocking
also I turned on USB debugging
Click to expand...
Click to collapse
Plug in your phone to your cable to your PC. Reboot the phone and soon as it turns off, hit the sound up & sound down button along with the power button. Hold these down until your PC sounds and verifies you are in EDL mode. Once in EDL, start the app on PC using admin privileges. Once the program has started, run unlock bootloader (option 4) again. Once it's complete, reboot the phone to the OS. Reboot holding power & volume up. This will take you to recovery. Now go to reboot to bootloader. When in fastboot follow the directions to install TWRP. Do not skip any steps! Apparently, steps are being skipped.
jim262 said:
Plug in your phone to your cable to your PC. Reboot the phone and soon as it turns off, hit the sound up & sound down button along with the power button. Hold these down until your PC sounds and verifies you are in EDL mode. Once in EDL, start the app on PC using admin privileges. Once the program has started, run unlock bootloader (option 4) again. Once it's complete, reboot the phone to the OS. Reboot holding power & volume up. This will take you to recovery. Now go to reboot to bootloader. When in fastboot follow the directions to install TWRP. Do not skip any steps! Apparently, steps are being skipped.
Click to expand...
Click to collapse
Hi Jim so I've followed your instructions and that has managed to get me into fastboot thank you but still not able to flash recovery it's just saying no partition and when I use the unlock boot tool it failed on the last bit for fastboot I've add photos
ztxaxonjay said:
Hi Jim so I've followed your instructions and that has managed to get me into fastboot thank you but still not able to flash recovery it's just saying no partition and when I use the unlock boot tool it failed on the last bit for fastboot I've add photos
Click to expand...
Click to collapse
I said you need to follow directions. In the directions to run <fastboot boot TWRP.img>, not flash. Then flash the installer if you wish to make it permanent, but I wouldn't recommend making it permanent to allow OTAs to work properly.
Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well
ztxaxonjay said:
Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well
Click to expand...
Click to collapse
Go into fastboot, connect to your PC and run <fastboot boot TWRP.img> then flash Magisk. Do not flash the recovery. Boot TWRP using the above command. Flashing the recovery will not work. If you read the directions, it tells you that. I have told you everything step by step. If you can access fastboot, you are done with the EDL tool, just go into fastboot and boot TWRP using the ADB command <fastboot boot TWRP. img>
---------- Post added at 06:19 AM ---------- Previous post was at 06:06 AM ----------
ztxaxonjay said:
Sorry I'm not sure where I've gone wrong here I followed your instructions but when I run the axon edl tool it managed to unlock the bootloader and give me back fast boot with out any stop's on boot up but when I run the axon edl tool I got the error at the end which I posted in the picture so then after that didn't work I put it into fastboot and tried to flash the recovery myself and That didn't work either that's why I posted a photo of that as well
Click to expand...
Click to collapse
Go into fastboot, connect to your PC and run <fastboot boot TWRP.img> then flash Magisk. Do not flash the recovery. Boot TWRP using the above command. Flashing the recovery will not work. If you read the directions, it tells you that. BTW, I don't think you read the directions. Go back and look at my previous post. You only use the EDL tool to unlock the bootloader. After you have unlocked reboot to the stock recovery and select reboot to fastboot. Then boot TWRP.
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
lostneedfound said:
Been trying to fix my phone for two days. first time rooting and it was kind of a success besides the wifi not working so i wanted to undo the root. tried many things and apparently messed up many things. The phone will not go into recovery mode. It wont turn on. if i try to flash anything i get many different errors(even twrp). And yes ive made sure everything is for my phones version(s). Oneplus 8t tmobile. so basically the phone can turn off and go into fastboot and the only thing inbetween that is it shows the 1+ logo for a split second.
"fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable."
"unknown partition"
"FAILED (remote: 'Flashing is not allowed for Critical Partitions" btw bootloader is unlocked so dont understand how this is happening unless im misunderstanding the meaning
msm will not detect my phone also. even updated the qualcomm drivers and still nothing. however can't really find a sure fire way to determine if the phone is in edl mode besides it connecting in msm. which i haven't been able to do even at the start of yesterday when the phone could atleast flash twrp and boot edl from there. Pls help
Click to expand...
Click to collapse
WiFi not working because the boot.img you flash is not match your system version.
ULTRAJC said:
If you have to use online source patched boot.img, don't flash, only do "fastboot boot boot.img", if it can successfully boot into the system, then use magisk patch current system boot.img and reboot.
Click to expand...
Click to collapse
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
Some_Random_Username said:
Go to device manager and make sure your phone shows up as QDLOADER 9008.
If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ) and install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you downloaded CAB file.
MSM tool is stuck on "Param pre-processing"
Ensure you're using the Qualcomm drivers linked above.
Click to expand...
Click to collapse
Some_Random_Username said:
Why is my device getting in Qualcomm crashdump mode in spite of a successful download?
Your unit was most likely manufactured after March 9th 2021, see https://forum.xda-developers.com/t/...ice-to-oxygenos.4180837/page-14#post-84789741 for reference. You therefore need to use HydrogenOS 11.0.7.12 MSM to recover your device linked at https://www.oneplusbbs.com/thread-5886794-1.html (mirrored at https://mega.nz/file/O8UySbgR#cXGlHkdA_7CYEhKIrek9zzAEwJ7Vx1D5BZdemnPlvGE by @pikatenor ). Getting new OxygenOS MSM tools is nowadays impossible unless you own the device it is meant for, so OP will not be updated to add new OxygenOS MSM tools allowing to workaround this issue. Feel however free to reach out to me in DM if you would like to get told how to maximise your chances to obtain one.
Click to expand...
Click to collapse
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
ULTRAJC said:
WiFi not working because the boot.img you flash is not match your system version.
You can use command "fastboot oem edl".
EDL mode(usually a full black screen) will timeout in few seconds if not receive any command from MSM, so you can start MSM flash frist then put phone to EDL.
Two possible situations need attention:
If MSM just not work or you not using Windows, you can follow:
[GUIDE] Unbrick or restore to OOS using only fastboot
This guide will only work up to OOS 11. This guide is for users that can't or just don't want to download MsmDownloadTool. Linux users especially, since the tool is not available for linux. All you need is a recent version of android tools with...
forum.xda-developers.com
Click to expand...
Click to collapse
fastboot oem edl results in FAILED (remote: unknown command). tried it in minimal adb and fastboot and platformtools.
and that is the guide ive been following. however i keep getting partition issues.
lostneedfound said:
and that is the guide ive been following. however i keep getting partition issues.
Click to expand...
Click to collapse
Fastboot unbrick guide didn't work for you?
Maybe continue to try the key combination, open device manager, if you see devices name: …QDLoader 9008(driver installed) or …QHUSB_BULK(driver not install). That's EDL mode.
Some guide suggest this two command may work:
"fastboot reboot edl"
"fastboot reboot-edl"
Also can try "fastboot boot recovery that have adb.img" then use command "adb reboot edl".
okay so i none of that worked just continues to say unknown command or unknown partition. with the qual com i dont see anything otherthan android device for phone related stuff in the device manager. is there something ican do to get these partition errors to go away? last night i wasn't having any trouble with them and now they are everywhere and i really dont understand why becuase i hardly flashed anything last night. today i started flashing stuff from the guide you recommended/the one ive been using all this time and thats when the partition errors started and now im seeing them everywhere and i followed the guide down to the dime.
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
lostneedfound said:
solved out of pure rage i restored my pc to factory and when it started back up i redownload msm and phone connected perfectly. also correctly rooted by adb pulling my own boot.img. ty for your help
Click to expand...
Click to collapse
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
nujackk said:
That was one way to go, but for others. The problem was your adb/fastboot was old. Should no longer use the minimal adb it's outdated. Always use the latest platform tools.
Click to expand...
Click to collapse
Exactly @nujackk ,
I have found the most likely reason for an "unknown command" message to a newer fastboot command is an old fastboot.exe version.
Hey guys, I need help flashing my Google pixel 2. It was off for a couple of months and now when I am trying to start it, its not booting without putting it on charge and even then it only shows the battery icon then the google icon and restarts (So a bootloop). But when I press and hold the power button and volume down key, it goes in the fastboot mode ( the one where all device information is shown with an Android Logo) (Pic att).
If I select Download mode, it just shows operation denied and if I select recovery mode then it goes to bootloop again. Also as far as I remember when I last used the phone, the usb debugging was turned off so please suggest what to do from here.
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Alekos said:
If you have USB debugging disabled with OEM unlocking off there's not much you can do. That's why I usually suggest if you're going to relock your bootloader keep oem unlocking enabled so you can flash the factory image if you run into problems. this has saved me a few times.
try downloading the platform tools and usb driver and running the unlock command, what message do you get? The first command you want to run is ADB devices to make sure that your device appears in the list and the command prompt. second command to run is fastboot reboot bootloader , If your phone restarts back into bootloader then you know you have the driver and fastboot /ADB installed and working properly. then go to the Android developer page and find the proper unlock fast boot command I think there's a different one for the Pixel 2.
Click to expand...
Click to collapse
Hey thanks for the update man. I know I should have kept atleast oem unlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
mayankggrwl said:
Hey thanks for the update man. I know I should have nlocking enabled. My fault.
Now I followed your instructions and the phone only shows under fastboot devices. But when I run ADB devices it comes as blank under list of devices attached. I still tried the fastboot reboot bootloader command but the phone just restarts with the battery charging icon flashing on screen and then going back into the fastboot mode. (pic of which I attached in the original post).
Any other ideas would be appreciated, else ill just take it to a service centre.
Click to expand...
Click to collapse
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Alekos said:
Mine shows blank also when running the devices command.
If you can run commands like "fastboot reboot bootloader" or "fastboot reboot recovery" etc and the device restarts, then platform-tools and driver is installed. I mean make sure you have the latest versions of both or else there's no point on going any further. An older version platform-tools will cause a bunch off issues so update that for sure.
what happens when you run any of these commands when your in the bootlaoder menu (where it says Fastboot and device state: locked) (after you've updated platform-tools, check the version by typing the command " fastboot --version" - 31.0.3 is the latest version)
fastboot flashing unlock
fastboot flashing unlock_critical
fastboot oem unlock
If you can unlock your device, you can flash recovery/bootloader image and go from there. But it doesn't look good.
Click to expand...
Click to collapse
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
mayankggrwl said:
Hey man, Thanks for the update.
Unfortunately none of these commands are working and yes I have the latest platform tools and drivers installed. Attaching image of the same.
Click to expand...
Click to collapse
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Alekos said:
yeah, it means the oem unlocking option is disabled in developer options. damn.
can you try logging into recover menu at all so you can update both boot slots A/B with the ota using adb update option in the recovery menu.
What about running a few fastboot commands to delete userdata and even switch boot slots. that Fastboot screen will show what slot you are booted in (either a or b). try switching slots and booting then?
fastboot --set-active=a (if you are in Slot-B)
fastboot --set-active=b (if you are in Slot-A)
After swithing slots, hit restart device and as soon as you see the Google Logo, hold volume down. If you can boot into Android, enable oem unlocking as soon as you can, don't even connect to wifi or whatever. Or try accessing Recovery mode after switching slots. Main goal is to try to access recovery to update ota and/or access Android to enable oem unlocking.
have you looked on xda for other fastboot commands to try? There's a few Unbrick posts on the Pixel subs - worth a try?
edit-- sorry, I deleted some of my comment by mistake, had to rewrite it/
Click to expand...
Click to collapse
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
mayankggrwl said:
Okay so I tried switching slots. Currently active slot is A but it again shows error that slot chage is not allowed in locked state. Well was worth a try.
I tried almost everything to get into recovery menu as per my knowledge but cant. It just restarts back into the fastboot state or goes into bootloop.
I did a bit of searching before creating this thread but didnt found anything. Ill try again and see if someone has something similar.
Click to expand...
Click to collapse
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how the op in that thread above fixed his Pixel 2 with Skipsoft tool. His Device state said Locked in his screenshot on his post.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
edit--try these commands
fastboot erase system
fastboot erase data
fastboot erase cache
Alekos said:
this thread is interesting:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
specifically this comment:
{Solved} Pixel 2 Bricked, need help.
Hey Guys. I'm new to the Pixel 2 and have found myself stuck and not sure what to do. I'm stuck at this screen and keep getting getting an error message staying "Slot Unbootable: Load Error". I am not able to get into fastboot to flash the...
forum.xda-developers.com
download the full factory image (not ota) and extract it, and move the radio and bootloader images into platform tools folder and try flashing? But don't think you can.
Also, maybe try installing Skipsoft and see what commands you can execute from there? https://skipsoft.net/download/unified-android-toolkit-v1-7-2/
it supports the Pixel 2.
Not sure how those users in the thread flashed the bootloader image since I didn't think you could if the device state is locked, but worth a try.
Also try draining the battery and see if it will boot into Recovery Mode at all. And check the other Pixel threads (like Pixel 3 XL) there's a few unbrick posts there also.
Click to expand...
Click to collapse
Okay great !! Thanks for these. Ill go through that thread and will see if any of the listed methods work. Will also try that software. In a rush so will try these later on and then ill update you.