Database Info

Sony Arc S, unlocking bootloader, fastboot.exe fails

Hello, I want to root my phone and am trying to unlock my Arc S with Sony's official guide:
Instructions
First, you should confirm that it is possible to unlock the boot loader of your phone by checking the service menu. In your phone, open the dialler and enter *#*#7378423#*#* to access the service menu.
In your phone, tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
On your computer, click Continue at the bottom of this page to start the unlock boot loader process.
Read through the information in the pop up window and click Yes, I’m sure, if you are still confident you want to unlock the boot loader.
Read through and accept the legal terms. Click I Accept.
Enter your name, email address and the first 14 digits (remove the last digit) of your phone’s IMEI number. Click Submit. You can view the IMEI number by entering *#06# on your phone.
The unlock boot loader key is displayed. Write it down and save it for later use.
Download and install the latest Android SDK from developer.android.com.
Download and unzip this file. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony and Sony Ericsson devices. Make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. You can see current Google USB Driver package revision in the SDK Manager.
Place the unzipped file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. Accept to replace the old android_winusb.inf-file with the new file. If you can't find the usb_driver folder, please install the Google USB Driver Packager using the Android SDK manager.
Turn off your phone.
On your phone, push and hold the unlock button* at the same time as you connect the phone to the computer with a USB-cable. The unlock button may differ between different phone models. See the note in the bottom of this page for more information on what button use on your phone.
On your computer, you will be asked for drivers. Point to the usb_driver folder where you placed the android_winusb.inf-file, and select the Android Boot loader Interface-file.
Open a command window and go to the tools folder within the Android SDK folder.
Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your phone is connected properly.
Warning! If you perform this step, you will unlock the boot loader. This may void your warranty and/or any warranty from your operator. If you still want to unlock the boot loader of your phone, enter fastboot.exe -i 0x0fce oem unlock 0xKEY, where KEY is the unlock boot loader key you got in the beginning of this instruction. The boot loader should now be successfully unlocked.
Click to expand...
Click to collapse
I have done everything up till the second last part, where you confirm that the phone is connected properly with fastboot.exe. but when I try to run the getvar version command, it fails with
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce getvar version
getvar:version FAILED (command write failed (Unknown error))
I have made sure that my phone is in Fastboot mode, so I don't have any ideas.

Shotweb said:
Hello, I want to root my phone and am trying to unlock my Arc S with Sony's official guide:
I have done everything up till the second last part, where you confirm that the phone is connected properly with fastboot.exe. but when I try to run the getvar version command, it fails with
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot.exe -i 0x0fce getvar version
getvar:version FAILED (command write failed (Unknown error))
I have made sure that my phone is in Fastboot mode, so I don't have any ideas.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1527159&page=4
better off asking in here
Pvy.

Huh, for some reason it just worked, even though I didn't do anything different. Maybe it was because I read that post. Thanks anyways

How to lock bootloader after it was unlocked

This method was tested on P2a42 4/32 and P2c72 4/64 (both smartphones has 251 firmware installed).
Please, pay attention and read carefully:
You have a risk that P2 will go from EDL (9008) mode to 900E while you make a reconnect of connected to PC phone.
If you haven't successfully returned it by yourself into 9008 state - the only way is repair service. See details on 4Th step below the short instruction.
ADB and EDL (9008) drivers have to be pre-installed on your PC.​
For those, who faced with flashing firmware, gaining root, working with ADB and Fastboot commands, EDL mode on P2 and so on, here is the short instruction:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Wipe userdata via Fastboot: fastboot erase userdata .
4. P2 is connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
5. Flash 251 firmware as for unlocked device using START script .
6. Choose region ( ####682# ) and then make a reset ( ####7777# ).
7. That's all folks! Now you have locked P2 with a region that you want. So you can set the phone as you always do.
Below there is the same instruction, but detailed and with pictures.
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
Turn off P2.
Boot it into Fastboot mode - press and hold two buttons (Power And Volume -), on P2 screen you will see Fastboot mode: Screenshot 2.
View attachment 4358524
Connect P2 to PC (it is recommended not to use card readers; connect to USB which are situated on motherboard for PC, there is an exception for notebook (laptop)).
Press right mouse button and hold Shift on ADB folder, which is placed in the root of Disc C (С:\), choose "Open command line" - a CMD window will appear on the screen of PC.
In CMD window type fastboot erase secinfo and press Enter.
If all done properly, all drivers set properly, on the screen of your PC you will see: Screenshot 3.
View attachment 4358525
3. Wipe userdata via Fastboot: fastboot erase userdata .
Continue in CMD window. Type fastboot erase userdata and press Enter.
On the screen of your PC you will see: Screenshot 4.
View attachment 4358526
Close CMD window on PC.
4. P2 connected to PC in EDL (9008) mode, make a reset via launching blank-flash.bat from blankflash folder.
blankflash folder must be placed in the root of Disc C (С:\).
On PC you must hold opened window of "Device manager" with opened string "Ports (COM and LPT)".
Your P2 must be connected to PC in EDL (9008) mode.
Use P2 very carefully without further re-connections, because there is a high risk, that P2 can go to 900E mode.
P2 connected to PC, press and hold all three buttons (Power and both Volume).
Hold buttons (phone will be rebooted twice) until you will see "Qualcomm HS-USB QDLoader9008 (COM12)" in opened window of device manager in string "Ports (COM and LPT)".
You might get another number of port (not only 12Th), it doesn't matter.
The main aim is "Qualcomm HS-USB QDLoader9008..." string in device manager.
Please, be very careful, because even little re-press of button or re-connect of cable will send your P2 to 900E mode with constant vibration and blue LED.
Try to restore phone to EDL (9008) mode by pressing and holding three buttons.
If you have no luck (from 900E to EDL) - congrats, you've got a brick.
From this point you should ask for help in repair service.
Going further, if all is going right and P2 connected to PC in EDL (9008) mode.
In device manager window on PC you will see this: Screenshot 5.
View attachment 4358527
From blankflash folder launch (double click of left mouse button) blank-flash.bat: Screenshot 6.
View attachment 4358528
You will see a CMD window which shows you a reset process of your P2.
If all done properly (without any "ERROR False"), you will see: Screenshot 7.
View attachment 4358529
In the end of reset your P2 will automatically boots from EDL (9008) mode to Fastboot mode: Screenshot 8.
View attachment 4358530
I suppose that there is no need to speak about 5Th and 6Th steps, because it is a basic knowledge, that you should know, when you are going to lock bootloader on P2.
Important notice.
You have to use original or other cable that has been already successfully used in Fastboot mode with your Р2.
The simple way to check cable is to type fastboot oem config in CMD and look what info it will give to you.
For those, who have already locked bootloader, it is strictly recommended not to flash stock ROM via flashall.bat.
For flashing stock you should use method for unlocked device, so you need to use START script.
All will go right if you will flash via flashall.bat after bootloader was locked, without any errors, Р2 will be booted as usual - Wi-Fi, SIM-cards (with names of operators), IMEI's and Serial number - all will be OK ...
But!
Calling, SMS and Mobile data will not work, you will see crosses on antenna icons in Status bar (in the string of modem firmware in "About" you will see "X" instead of "R" (Screenshot 9, 10) as it was, modems region will be defective).
View attachment 4358708View attachment 4358709
You can switch on/of Mobile data from Notification drawer, but there will be no connection, only Wi-Fi will work.
I am searching for solution of this problem.
As soon as it will be ready, it will be posted here. See post #2.
ADB folder (download, unzip) - View attachment ADB.rar
blankflash folder (download, unzip) - View attachment blankflash.rar
All thanks addresses to https://forum.xda-developers.com/member.php?u=279908.
I've just translated it from Russian to English from 4PDA site
Good luck and have a nice day!
Remember ...backup rules.

Solution.
Your phone must be unlocked and you must already have TWRP-backups of modem (NON-HLOS) and EFS from Р2.
1. Unlock bootloader.
2. Install TWRP.
3. Restore modem (NON-HLOS) and EFS in TWRP - you will get working modem, but there might be no sound in telephony.
4. You should install modem image via TWRP for Android 6 or 7 to get back to a working telephony (for additional instructions see post #3).
Later, if there will be a method which will work without TWRP-backups and possibly without unlock of bootloader, it will be posted here.
Modem download links:
Android 6 (062): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75313
Android 7 (244): http://lenovo-forums.ru/applications/core/interface/file/attachment.php?id=75314

How to restore a modem.
Important notice - you need to use modem with the same OS version which is installed on your phone.
Look here:
Firmware 062 - this is Android 6.
Firmware 233 and higher - this is Android 7.
Flash this:
For Android 6 - Modem_P2_062_ROW.zip
For Android 7 - Modem_P2_244_ROW.zip
Flash modem via TWRP:
1. Download zip for OS that you need (do not unzip it, rename or choose extension).
2. Copy to the phone memory (or to external micro-SD card).
3. Boot to TWRP and act as it is shown on the screenshots ...
View attachment 4358546View attachment 4358547View attachment 4358548View attachment 4358549View attachment 4358550

EDIT: did the first step wrong, now it's Locked

Do you have data and calls working?
Enviado desde mi Lenovo P2a42 mediante Tapatalk

Is the warranty back if the bootloader is relocked?

Danoz88 said:
Is the warranty back if the bootloader is relocked?
Click to expand...
Click to collapse
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
Thanks I thought the same. But in this case why should we go back to locked bootloader

Danoz88 said:
why should we go back to locked bootloader
Click to expand...
Click to collapse
It is personal decision. May be someone don't like to see "UNLOCKED" state.

sergsinger said:
It is a difficult question.
I suppose, that official repair service can detect it.
Remember how you unlocked P2 at first time: you asked for unlock with internet connection and Lenovo ID, there is a possibility, that some data about it stored and can be used for different purposes.
Click to expand...
Click to collapse
I agree... But there are some reports on this forum suggesting otherwise.
One common report is the replacement of motherboard for bricked devices, that too for unlocked devices.

Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
Oh great. Is this all it have to be done or followed by previous page? Any problems or things to be aware of?

jitkr said:
Locked Boot-loader with just (3) steps:
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
2. Wipe secinfo via Fastboot: fastboot erase secinfo .
3. Flash fastboot images(Stock files).
* I was using Cardinal AOSP 8.0.0
*Blankflash not used
Thanks Locked
Click to expand...
Click to collapse
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp

Shuvamilu said:
I did not understand Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp
Click to expand...
Click to collapse
First post, first picture.

Danoz88 said:
First post, first picture.
Click to expand...
Click to collapse
I don't understand

Shuvamilu said:
I don't understand
Click to expand...
Click to collapse
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
sergsinger said:
From Unlocked to Locked state on P2.
1. Wipe sp if you have root: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp .
On this step you can use Total Commander with ADB plugin (YouTube will help you, there are tons of videos about it).
I prefer not to use PC, if there is another way.
What I've done:
Android Terminal Emulator installed and launched.
Gave it permission to root access.
In Emulator typed su and pressed Enter.
Sign $ will turned to # , which means that further commands will be under root access.
Type command: dd if=/dev/zero of=/dev/block/bootdevice/by-name/sp and press Enter.
If all done right, so you will see: Screenshot 1.
View attachment 4358523
Click to expand...
Click to collapse

Danoz88 said:
Every step which jitkr enumerated is explained by sergsinger who made this guide.
Read the complete first post of sergsinger. Also click on show content for full explanation.
If you farther understand nothing please clearly explain what exactly.
"I don't understand" does not help in any way.
Click to expand...
Click to collapse
Next process

If i unlcok bootloader, still recive system updates?

tapunger said:
If i unlcok bootloader, still recive system updates?
Click to expand...
Click to collapse
Yes, as long as you are on stock rom.

I lost my signal forever when I did a nandroid backup from another P2. I've tried it all, but nothing seems to work when it comes to restoring it.
I'm a bit confused by the first posts. OP talks about locking the bootloader and post #2 and #3 say you have to be unlocked to restore the modem? I'd have thought you wanted to lock it in order to flash the modem.

HTC U11 downgrade from Pie to Oreo

Hi Everybody!
Im hungarian man and sorry very small speak English. Google Translate helps me.
I have an HTC U11 Black Dual SIM CID34 (4/64) phone. I opened the bootloader and installed TWRP the phone is S-ON status.
Everything is fine so far.
I copy the ROM to SD card and start the phone Recovery mode.
I selected the ROM from this list:
Link: Removed by System
I wanted to install this ROM
2PZCIMG_OCEAN_DUGL_O80_SENSE90GP_MR_HTC_Europe_2.33.401.10_Radio_8998-002772-1711161638_release_signed.zip
Link: Removed by System
TWRP always writes in an invalid ZIP format.
Your phone is not loading Android now. It starts to load but stops at the boot screen. I can boot my phone into Bootloader, Recovery, Download mode.
Thank you for your help!
Please if you write simply to write or step by step how to fix the phone.
Best regards: Szabolcs

kovsza said:
Hi Everybody!
Im hungarian man and sorry very small speak English. Google Translate helps me.
I have an HTC U11 Black Dual SIM CID34 (4/64) phone. I opened the bootloader and installed TWRP the phone is S-ON status.
Everything is fine so far.
I copy the ROM to SD card and start the phone Recovery mode.
I selected the ROM from this list:
Link: Removed by System
I wanted to install this ROM
2PZCIMG_OCEAN_DUGL_O80_SENSE90GP_MR_HTC_Europe_2.33.401.10_Radio_8998-002772-1711161638_release_signed.zip
Link: Removed by System
TWRP always writes in an invalid ZIP format.
Your phone is not loading Android now. It starts to load but stops at the boot screen. I can boot my phone into Bootloader, Recovery, Download mode.
Thank you for your help!
Please if you write simply to write or step by step how to fix the phone.
Best regards: Szabolcs
Click to expand...
Click to collapse
Try renaming the zip file to 2pzcimg.zip,, and place it on the root of your sdcard and boot into downloader mode. Hth, this looks to be an ruu so it will put your phone back to stock and wipe all but the sd card.

hammered58 said:
Try renaming the zip file to 2pzcimg.zip,, and place it on the root of your sdcard and boot into downloader mode. Hth, this looks to be an ruu so it will put your phone back to stock and wipe all but the sd card.
Click to expand...
Click to collapse
I'll try and give you feedback.

I start the phone Downloaded mode. Phone autodetect the SD card ZIP file. I pressed VolUp buttons... and nothing.
Error message: FAIL12 RU_ZIP_ERROR
What's next?

Here you have some details, but are for downgrade from Oreo to nougat (maybe could it works??)
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481

kovsza said:
I'll try and give you feedback.
Click to expand...
Click to collapse
If you are on pie and trying to downgrade to oreo this cannot be done with out soff , and i do not think
Pie soff is supported,

hammered58 said:
If you are on pie and trying to downgrade to oreo this cannot be done with out soff , and i do not think
Pie soff is supported,
Click to expand...
Click to collapse
If this is the problem then is there an easy way to set it to S-OFF?

Pantumaca said:
Here you have some details, but are for downgrade from Oreo to nougat (maybe could it works??)
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
Click to expand...
Click to collapse
This is the description I read. Based on what I described, I got to the version change. The version change failed. But in another place I read that in Download mode you can easily reinstall the previous version.

kovsza said:
This is the description I read. Based on what I described, I got to the version change. The version change failed. But in another place I read that in Download mode you can easily reinstall the previous version.
Click to expand...
Click to collapse
I have used this procedure to downgrade from oreo to nougat, but have not used it to from pie to oreo,

hammered58 said:
I have used this procedure to downgrade from oreo to nougat, but have not used it to from pie to oreo,
Click to expand...
Click to collapse
Then even that solution won't work.

kovsza said:
Then even that solution won't work.
Click to expand...
Click to collapse
Like i said I have not tried it, as far as i know once you are on pie there is no going back unless someone else knows a solution

hammered58 said:
Like i said I have not tried it, as far as i know once you are on pie there is no going back unless someone else knows a solution
Click to expand...
Click to collapse
I see if somebody knows the solution or tried it.

Nobody?

If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. Download HTC Dev info tool from the below link
https://drive.google.com/file/d/1ubjDGNqCfIply-aRN8C7IQNb-YVkD4M7/view
3. Now connect your device to PC by turning on USB debugging in phone and open the info tool and click on GetDeviceInfo and it will show your device information in the tool.
4. If you want to change CID then follow this step otherwise skip to step 5. Change the CID to your desired CID and click on save.
5. Now change the misc version to the rom misc version which you downloaded for downgrade and click on save and apply changes.
6. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not and also check the version number is blanked out or not. If it doesn't then something wrong you have done, so again start from step 2.
7. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
8. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
9. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
10. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
11. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
12. Now open cmd and navigate to the com folder by using by using cd command.
13. Now cross-check whether you are in bootloader mode or not, if yes then proceed to next step otherwise reboot your phone to bootloader mode by typing "htc_fastboot reboot bootloader" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
14. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
15. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
16. Now the flashing process should start and wait for some time until it finishes.
17. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:

Ryü[email protected] said:
If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. This step is optional and this is only for those who wants to change the CID of their device if not skip to step 4. Just download "HTC dev infotool" turn on USB debugging in phone and connect your device to PC and open HTC dev info tool and click on Getdevice info and it will show you about your device information and from their change the CID of your device to your required CID by changing the CID field and hit save and click apply all changes.
3. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not. If it doesn't then something wrong you have done, so again start from step 2.
4. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
5. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
5. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
6. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
7. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
8. Now open cmd and navigate to the com folder by using by using cd command.
9. Now cross-check whether you are in download mode or not, if yes then proceed to next step otherwise reboot your phone to download mode by typing "htc_fastboot reboot-download" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
10. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
11. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
12. Now the flashing process should start and wait for some time until it finishes.
13. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
is it work on single sim devices to change cid??

filandry said:
is it work on single sim devices to change cid??
Click to expand...
Click to collapse
I think it works but always have a backup before doing anything because i tested it on my HTC dual sim 6/128GB dual sim variant and successfully changed CID from HTC__J15 to HTC__060 and downgraded from PIE to OREO

Ryü[email protected] said:
If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. This step is optional and this is only for those who wants to change the CID of their device if not skip to step 4. Just download "HTC dev infotool" turn on USB debugging in phone and connect your device to PC and open HTC dev info tool and click on Getdevice info and it will show you about your device information and from their change the CID of your device to your required CID by changing the CID field and hit save and click apply all changes.
3. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not. If it doesn't then something wrong you have done, so again start from step 2.
4. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
5. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
5. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
6. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
7. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
8. Now open cmd and navigate to the com folder by using by using cd command.
9. Now cross-check whether you are in download mode or not, if yes then proceed to next step otherwise reboot your phone to download mode by typing "htc_fastboot reboot-download" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
10. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
11. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
12. Now the flashing process should start and wait for some time until it finishes.
13. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It's not working.error sad you must change version number.
What is the best way for change version number?

Who to change cid and version number?

mehrdad_esmaeeli said:
It's not working.error sad you must change version number.
What is the best way for change version number?
Click to expand...
Click to collapse
Edited the post and forgot to add changing the version number check from step 2 again. If that too not work run this command "adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16" it will blank out misc version and follow the instructions i posted above.

Ryü[email protected] said:
Edited the post and forgot to add changing the version number check from step 2 again. If that too not work run this command "adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16" it will blank out misc version and follow the instructions i posted above.
Click to expand...
Click to collapse
Ok Finally I could
Tnx so much

[HOWTO] ULM bootloader unlock and root 20e (Pie) from Oreo

Here's a simple guide for those of you like me who bought a cheap ULM G7 that's actually cross flashed from something else (Sprint for my case).
I got mine with Oreo 11e on it. I'll just explain the steps to get to unlock with 20e (Pie) rooted. I'm not an expert, but I've been doing this stuff for a lot of years. I probably can't answer questions on why it's not working for your situation, so hopefully others can jump in when necessary.
These steps worked for me. Some may be unnecessary. Not sure.
DISCLAIMER: Don't blame me if something goes wrong. Again, this worked for me.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
https://lg-firmwares.com/downloads-file/17341/G710ULM11g_01_NAO_US_OP_1112
Install the patched LGUP (GUI one, not command line).
Flash 11g by doing a Partition DL, select the kdz in the bottom half (click on the first empty line).
After it's done and it reboots into the system. Let it boot, do the initial setup to get into options and enable OEM unlock and USB debugging.
Then do the unlock guide here:
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
You can follow the steps in there exactly. There is nothing different that needs to be done for the G7. You're basically using QFIL to flash the v35 eng boot to get a hacked fastboot.
You're now bootloader unlocked.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here: https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
Skip until you see "Skip to here".
* I was informed after that it's easier to just flash the 20e kdz, then use QFIL to extract the boot image instead of fooling around with kdztools. Leaving this for reference. *
Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
Use kdztools to unkdz, then undz:
Download the DEVEL branch: https://github.com/steadfasterX/kdztools/tree/develop
Install python. I'm using 3.8 x64 for Windows 10.
In a command prompt, run "pip install zstandard" which you need to unkdz.
In your extracted kdztools folder, run:
Code:
python unkdz.py -f <path to 20e kdz> -x
This extracts a .dz file.
Now run:
Code:
python undz.py -f <path to extracted dz file> -s 42
This extracts the boot image (you can see it's 42 if you do a -l instead of -s).
Now you have your clean/stock 20e boot image.
Go back into fastboot (if you're not still there) and BOOT the rooted 11g boot image: https://androidfilehost.com/?fid=1899786940962574205
Code:
fastboot boot 710ULM11g_rootedboot.img
It'll boot into the system and magisk is installed temporarily. Copy the clean 20e boot image onto your phone. Install Magisk Manager, then in Magisk Manager, click the first Install (top of the 2) and it'll pop up a window. Click Install again, then it'll show a menu with 4 options (honestly, the patch should be moved to the main menu imo). Click "Select and Patch a File". Find your 20e boot image and choose it. Magisk will now patch it and create a magisk_patched.img. This is your rooted 20e boot.
Skip to here.
Now we flash 20e to get Pie. Same as above, use LGUP to partition_dl the 20e kdz (select all).
Once it's done, it'll reboot. Wait for it to get to the initial setup (I don't like force rebooting while system is doing possibly important stuff). Get back into 9008 mode. Use QFIL to flash the patched boot img to "boot_a". Once that's done, just vol down + power for 15 seconds to force a reboot.
You're now 20e + root + bootloader unlocked.
I won't be monitoring this thread a lot, so don't expect quick responses, but there's enough details here for most people who are familiar with rooting to get to where I am.

I successfully rooted my crossflashed spring LG G7 using the guide you linked, and this verizon guide.
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
First of all, you'll want to flash to 11g, because we have a patched rooted boot image for it.
Click to expand...
Click to collapse
Other guides mention disabling/erasing certain partitions: the laf_a/boot_b according to this Lineage16 guide or laf_a/laf_b/boot_a & boot_b according to the 9008 guide, but I could be wrong
Code:
adb root
[In magisk make sure ‘Shell’ is granted super user access AFTER executing the following]
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf_a
adb shell su dd if=/dev/zero of=/dev/block/bootdevice/by-name/boot_b
This will get rid of download mode feature on your phone, rendering LGUP un-useable, you can use QFIL to restore your backed up laf_a/_b files.
There's a KDZ GUI extract tool here.
It found the following in 20e kdz file: boot.img_65286, boot.img_163830; both 64MB. If anyone knows what the bolded parts represent it would be appreciated. I assume the lower number corresponds to A and the higher, is B.
I'll likely use the twrp_june.img for both boot_a/_b.
Any time you want to flash something via twrp you will have to flash twrp via fastboot again (hence the non persistance), do your stuff in twrp, and then reflash the boot img (it will not boot if you dont do this or use josh1x's boot file). Just like steps 5-6 for gapps.
Click to expand...
Click to collapse
According to this guide.
Now, we want to get 20e rooted. Before we flash the 20e kdz, we need a patched boot image (Magisk). We have to create a patched boot image from the stock boot image. So, here are the steps for reference. If you want to skip this (trust me, you do), download my patched boot image here:
Click to expand...
Click to collapse
Assuming you already rooted the phone, there's a way to prevent, the KDZ from overwriting patched boot_a and boot_b in LGUP, as seen 7:00 and 7:25 of the following video.
I appreciate the guide though.

Stuck in fastboot mode, I forgot something..

Aztec_native said:
Stuck in fastboot mode, I forgot something..
Click to expand...
Click to collapse
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.

paxar331 said:
I never updated to 11g image. I manually patched the boot_a and boot_b image within Magisk GUI app, within the phone itself.
Click to expand...
Click to collapse
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.

strifej said:
Do you have download mode? If yes, you can also flash a kdz to start over. With 9008/qfil, almost all situations should be recoverable.
And what were you doing just before getting stuck in fastboot? Did you have a working system before going into fastboot? If you had trouble with the unlock process, you will have to ask in the V40 thread.
Click to expand...
Click to collapse
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?

strifej said:
Can you patch a boot image on a phone using magisk manager if it's not rooted? I assumed you needed to be rooted to be able to patch.
If you don't, then you can LGUP directly to 20e, pull the boot image using qfil, and patch with magisk manager right after. Saves a lot of steps and time if so.
Click to expand...
Click to collapse
No. I rooted with QFIL and V35eng.img → abl_a (after backing up abl_a). Then did fastboot oem unlock, re-inserted the backed up abl_a.img file, then did the magisk patch up to boot_a/_b.

Aztec_native said:
No download mode, I was trying to flash pie while on rooted Oreo.. it was fine before that. Half the fun, right?
Click to expand...
Click to collapse
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.

strifej said:
Maybe try a different LGUP? At worst, you can use the command line only one that bypasses checks and can force flash any kdz. But you have to be very careful to not flash the wrong firmware.
I'm not sure if QFIL can flash kdz, but you could research into that if it helps.
Click to expand...
Click to collapse
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.

Aztec_native said:
I flashed a firmware that I previously had flashed, ULM20e.
The phone is only recognized in fastboot as Android Bootloader Interface... Can't get anything to work, haha. However, I did get the 11g IMG to get a different screen..
Edit: The update to pie stopped at 91% and then gave an error.
Click to expand...
Click to collapse
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
The following post helped, in allowing me to regain access to download mode.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
If using LGUP 1.15, you'll come across google link by sarang on how to implement the 'common dll' patch. Forum won't let me link to the website.
Installed 11g after changing to LGUP's program files (x86) directory:
Code:
lgup_cmd.exe com[your com port # in windows device manager] "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "E:\HIS Documents\Computer guides\LG G7\Softwares\G710ULM11g_01_NAO_US_OP_1112.kdz"
I'm finally able to boot into Android 8.x now, and make magisk fully root.

paxar331 said:
Same here:
According to multiple google searches LGUP is not properly patched.
I then made the mistake of using an older version of LGUP, that doesn't give you the option to disable boot_a/_b partitions from being over written; which was a foolish mistake.
I'd like to add that Pie LG stock boot images have NO FASTBOOT support, DO NOT delete laf_a & laf_b files, doing so does away with 'download mode'. If you do delete it, you'll need QFIL to flash abl_a to v35eng.img; this will give fastboot enablement on the phone, and allow to transfer backed up files to phone using 'fastboot'.
QFIL does not allow overwriting of Pie files except abl_a, which is more than enough in this case.
I also patched Pie/20e boot_a/_b files with magisk, and the phone is stuck in a fastboot loop for me as well, this may explain why 11g is needed.
Click to expand...
Click to collapse
Qfil allows backing up files as well as overwriting almost any file. I do it all the time.
Bricking my phone along the way trying different things. Unlocking and relocking bootloader.
Most of the time when you patch boot imgs people patch and load the magisk patched image to the wrong slot.
I have crossflashed the Korean pie and updated to Android 10 and achieved root with Android 10 as well.
All with qfil and using the command line LGUP to crossflash.
I don't mind helping users with issues as well.

Does anyone know the cmd syntax to execute the following? I.e. 'partition dl' is selected, and every partition but boot_a/_b is selected for installation. LGUP 1.15 GUI asks for a login making it un-usable for most on here.
Edit: This post may correspond with using the right version of LGUP.
I googled parts of this video: https://www.youtube.com/watch?v=ylBSZk7EqcA
I was able to reach 100%.
Unfortunately there's a boot loop, it seems 710ULM11g_rootedboot.img must be flashed before transferring file with LGUP.
I'm stuck and totally confused. Flashed 710ULM11g_rootedboot.img before transferring G710ULM20e_00_NAO_US_OP_1010.kdz. I then pressed power and Vol Down, then tapped the power button, click No on the white screen background, and again, I'm stuck on the fastboot loop.
The fastboot menu looks different than that of the video
https://www.youtube.com/watch?v=ylBSZk7EqcA
The one in the video looks like it's from v35eng.img used in 9008 QFIL guide.

Go back to ULM11g and crossflash using lgup command line to 20e then root it.
I believe there is a rooted 20e boot img that you can load with qfil or if adb fastboot works.
Crossflashing:
https://forum.xda-developers.com/lg-g7-thinq/how-to/cross-flash-oreo-pie-firmwares-lg-g7-g7-t3915303
Using qfil to load rooted 20e img.
https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
The process in the second guide is the same when loading a rooted img to either boot a or b whatever slot your on.

I was able to solve it.
The magisk patched IMG file by this OP was flashed to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good:
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.

paxar331 said:
I was able to solve it.
The magisk patched IMG file by this OP was flashed it to both boot_a and boot_b, then executed 'fastboot reboot'; yeah boot_a and boot_b need to be flashed with an identical file.
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
The screen booted twice with the 'Red LG symbol" showing itself twice, before I could get in to the new user setup prompts.
The 20e patched file from the following thread was no good.
https://forum.xda-developers.com/lg-g7-thinq/development/magisk-18-0-boot-images-t3955096
The most important part of this upgrade is definitely making sure LGUP is setup properly, including not installing the stock 20e boot_a/_b partitions, as seen in my previous post, and don't delete the laf_a/_b partitions as a good precautionary measure.
Click to expand...
Click to collapse
Yes the boot imgs are identical they are labled a and b because of the dual slots. If you knew what slot you were in prior to flashing any magisk rooted image you would just need to flash that specific boot img slot.
I relocked my bootloader just for kicks.
If you can get into fast boot there is no need to erase laf partitions only if you need fast boot.

I tried it but didn't work in EAW and I lost serial number mac address how get them back??? Need urgent help please

mine was already bootloader unlocked,
but tutorial worked fine here I flashed 20e using LG up and rooted.
What I did:
MAKE SURE YOU ARE BOOTLOADER UNLOCKED. I am not responsible for any damage, it is only what I did.
1)Dowload the 20e firmware: https://lg-firmwares.com/downloads-file/21135/G710ULM20e_00_NAO_US_OP_1010
2) Download this: LGUP new version - https://drive.google.com/file/d/1dJZxrj7nteDDUcQpiJLpX9Mjumm5mtKp/view
3) Install the file you downloaded above (LGUP).
4) Download this: LGUP common.dll https://drive.google.com/file/d/1V8IF2vJed3bQBsBCHLNBJdnW4gRj2uo0/view
5) Open the file downloaded and you will see the folder common. Copy the folder common and paste inside the folder model of the folder of the installation of the LGUP. For example: C:\Program Files (x86)\LG Electronics\LGUP\model
6) You are doing great! Congratulations. Let's proceed with 7.
7) Get phone in hands. Turn off it. Press and hold volume up and connect the phone into notebook. once appears download mode panel you unhold volume up softly.
7.1) When you connect the phone in download mode LG device must show in Windows Device Manager under "Ports" as a LG Serial COM port. Check it.
8) check if you completed the download of the kdz file. Did you complete the download of the big KDZ? Put the KDZ file in C:\ localization of your computer.
9) Let's open a command prompt as administrator. Now, in the command prompt input, type:
cd <path of LGUP folder>
Example:
cd C:\Program Files (x86)\LG Electronics\LGUP
10) Is your phone com5? check in Device Manager under Ports. It is written COM and a number after. If the answer is yes, you only have to type this code and run in the command prompt:
lgup_cmd.exe com5 "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
11) Are you unsure if your phone is com5? just modify com5 to comX replacing X with the properly number. For my EMW worked with com5.
lgup_cmd.exe comX "C:\Program Files (x86)\LG Electronics\LGUP\model\common\LGUP_Common.dll" "C:\G710ULM20e_00_NAO_US_OP_1010.kdz"
12) Wait 5 minutes, less or more.
13) it is completed! Remove the plug of the device.
14) It is like a new phone you have to conclude the phone configuration.
15) install magisk from magisk website but dont update it.
16) Get developer options enabled in your phone.
17) Open command prompt as administrator, type this code:
cd <path of minimal adb and fastboot folder>
Example
cd C:\Android-FastBoot-Adb
Don't have adb and fastboot minimal folder? Research in google and download. If you don't know what is the folder, it contains fastboot.exe inside.
18) Type this code now: adb reboot bootloader
19) confirm in phone allow usb depuration in this device or the command wont work
20) Download in your windows this pre rooted file made for this PIE OS by the author of the thread
https://mega.nz/#!uqZFDKZQ!5dOCFKElmMOXnAMel7dSvyhGY5RkJjBsMwM-kH7eOGo
21) put the file inside the fastboot folder. the file name is g7_20ulm_20e_boot_magisk_patched.img
22) in command prompt (already in cd path of minimal fastboot folder) type this:
fastboot boot g7_20ulm_20e_boot_magisk_patched.img
23) phone will reboot.
24) now phone started, open magisk and update it and click to install directly when it asks.
25) magisk will ask to reboot, click to reboot you are now rooted.
good luck

Hi Just a lost soul passing thru Lol
I'm looking to shed some light on my g710pm, its been a few days since I've been searching to get on AOSP.
I cross flashed to ULM 11g stock and had root and unlocked bootloader, then flashed 21d ULM and now Enable OEM unlock is grayed-out (bootloader is already unlocked ) sub message. SO... I back flashed to ULM 11g with same issue.
I've been reading the forums and have a rough idea how to fix, some how re-flashing laf_a ?
would really appreciate the help
Thanks
Found FIX
1. PS C:\Program Files\platform-tools> adb devices
List of devices attached
LMG710ULM******** device
2. PS C:\Program Files\platform-tools> adb reboot bootloader
3. PS C:\Program Files\platform-tools> fastboot oem lock
(bootloader) Erasing userdata and cache OKAY [ 0.492s]
Finished. Total time: 0.592s
4. PS C:\Program Files\platform-tools> fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.004s
https://forum.xda-developers.com/lg-g7-thinq/how-to/verizon-lg-g710vm20f-t4057031

DOOGEE S59 pro unlocking bootloader issue

Hello.
I have a DOOGEE S59 pro phone and i tried a bunch of times to unlock its bootloader, but it didn't work.
I've already done these things:
I've installed the USB driver and the MediaTek driver from https://gsmusbdriver.com/
I've enabled "OEM unlocking" and "USB debugging" in the developper options
I've ran the CMD prompt in the platform-tools folder (which is placed in the C: drive) and run this code:
PS C:\Program Files\platform-tools> adb devices
List of devices attached
S59PROEEA0000026105 device
PS C:\Program Files\platform-tools> adb reboot bootloader (now the phone shows " =>FASTBOOT mode . . . ")
PS C:\Program Files\platform-tools> adb devices
List of devices attached
(My phone isn't listed anymore)
PS C:\Program Files\platform-tools> fastboot oem unlock
< waiting for any device >
And this is it. I can't do anything else. When I hold the power button + the volume up key I can return to normal mode, but what can I do to unlock the bootloader? I wanted to root my phone and flash some magisk modules after that, but the situation is like I said. Can somebody help me?

Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.

.

xinthenoob said:
Since the phone is using a MediaTek chipset you can try using MTKclient, after downloading the zip completely power off your phone and open a terminal inside the 2nd folder of the unzipped zip file, the run the command python mtk da seccfg unlock after you did that hold the button combination for fastboot mode so long until the screen goes fully black and mtkclient should try unlocking the bootloader. Tried and tested on my Xiaomi Redmi 9 because I didn't want to factory reset.
Click to expand...
Click to collapse
Thank you, I'll try that and I'll tell you if it works.

KakoFed said:
Thank you, I'll try that and I'll tell you if it works.
Click to expand...
Click to collapse
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt[
[/QUOTE]
Click to expand...
Click to collapse
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
I also tried to open a command prompt in the mtkclient folder itself, and it said that:
pip : The term 'pip' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the s
pelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ pip install -r requirements.txt
+ ~~~
+ CategoryInfo : ObjectNotFound: (pip:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

xinthenoob said:
I completely forgot 2 more things!
1. You need to have python installed (during the install when you see a button that says "Add to PATH" check it)
2. After opening the terminal run pip install -r requirements.txt
Click to expand...
Click to collapse
Alright, I don't know what have I done, but it totally worked! Thank you so much!

KakoFed said:
I've just installed python, but I don't see the "Add to PATH" button. When I try to type that command, it says 'pip' is not recognized as an internal or external command,
operable program or batch file.
What should I do?
And also, which version of python do I have to install?
Click to expand...
Click to collapse
It should be somewhere also don't use PowerShell, it's weird sometimes

xinthenoob said:
It should be somewhere also don't use PowerShell, it's weird sometimes
Click to expand...
Click to collapse
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help

KakoFed said:
Hi, it's me again.
I unlocked the bootloader successfully, but now I am trying to root my phone using magisk. I patched a boot.img file from the Doogee s59 pro firmware and I tried to flash it via ADB, but it didn't work. I went into the fastboot mode (it is saying "fastbootd" actually), and I typed
fastboot devices
That worked, my phone was listed, but after that I tried to flash the patched boot.img file using this command:
fastboot flash boot <the file directory>
And also
fastboot boot <the file directory>
And it didn't work, it said:
warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 33554432).
sending 'boot' (32768 kb) failed (write to device failed (no link)) fastboot: error: command failed
Something like this.
What am I doing wrong?
Please help
Click to expand...
Click to collapse
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix

xinthenoob said:
You can flash the boot using mtkclient once again, first back up boot and vbmeta using python mtk r boot,vbmeta boot.img,vbmeta.img then transfer the patched boot to your PC and rename it boot.patched after doing that you can flash it onto your phone using python mtk w boot,vbmeta boot.patched,vbmeta.img.empty. Making a backup of those two is VERY important Incase something goes wrong.
Also I think it's because your phone has a integrity check, if you really want to flash it using fastboot I could find a fix
Click to expand...
Click to collapse
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?

KakoFed said:
Thanks, I'll try it, but in case something goes wrong, how do I use the backup files?
And also, could I install magisk modules after that?
Click to expand...
Click to collapse
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Ok, thanks, I'll try everything of that later

.

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
Hi, I have a problem AGAIN. When I flashed the boot.patched file, it was almost ok, until I saw that my bluetooth and WiFi connections stoped working after the flash. There was this window opening again and again that the Bluetooth app still stops working. I had to flash the normal boot.img file for it to work.
How can I solve this problem? I still want to root my phone

xinthenoob said:
Same way you flashed the patched files, always include the vbmeta.img.empty if you're flashing anything but the vbmeta.
If everything goes as planned, absolutely! I'm using energize protection as an ad blocker and it's working great.
Click to expand...
Click to collapse
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me

KakoFed said:
ACTUALLY NEVER MIND
I found a solution myself, it was the boot.img file that I think was the problem. I patched the boot.img file again but this time I patched that one that I backuped with MTKclient.
Thank you so much for your help, you were really helpful for me
Click to expand...
Click to collapse
Sorry I caught the flu and was out for a while but I'm glad you found a way