[GUIDE] Flash 'fastboot ROMs' for Lenovo Z6 Pro - Lenovo Z6 Pro Guides, News, & Discussion

Disclaim
All steps described here have been many times tested and proved to be safe but, you may know that sometimes in life unexpected things happen. I'm not responsible for any damage in your devices, do things at your own risk.
Introduction
Thanks to xda user @alexeei we can install almost every Z6 Pro stock ROMs using the Fastboot Mode. You always should check the package content and the installation script(s) to be sure that you know exactly what is gonna be installed. You can find all the ROMs listed and linked in this index.
Let's go with the guide.
0. Pre-requirements
- The Bootloader must be unlocked.
- Lenovo drivers installed in your computer. You can download them here . Thanks @benjieb
1. Download and extract the ROM
You cand find many of them here. Extract the downloaded file and a folder will be created with these contents:
- All the files required for the installation in Fastboot Mode.
- The ROM files.
- The .bat file(s) which contain(s) all the actions that will be performed during the installation.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You always should check the content of the .bat file(s). Read post #2 to get more info about this.
2. Reboot your device in Fastboot Mode
Shut down your device and boot it holding pressed both Volume Down + Power buttons until the Fastboot Mode menu appears. You can navigate in the Fastboot Mode menu with volume buttons to choose the options and the Power button to confirm, but at this point you don't need to do any action in this menu.
3. Connect the device to the computer with USB cable
4. Execute the .bat file
Just execute the .bat file with a double click and a CMD window will be opened and the installation will start. Only a few lines will appear at the beginning and then nothing will happen, it will seem to be stopped but actually it's not, just be patient because this screen could last around ten minutes. So despite of the 'Invalid sparse file format at header magic", keep the faith and don't do anything but wait.
The device will reboot once the installation is done.
5. Errors in the log. No voice in calls.
Some errors may appear in the CMD window during the installation, this is because some partitions are 'critical' and we're not allowed to modify them via fastboot. Usually this is not a problem because these "small partitions" don't prevent the new ROM to work normally, except if you're installing Android 10 from Android 9. If you change Android version with this method you will find that your micro doesn't work in calls. You can fix it installing these "small partitions" from TWRP.
Any correction, info or advise about this post will be very welcome.

About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.

descarao81 said:
About the .bat file(s):
You always should check the content of these files before doing any installation, specially with recent fastboot installers including several .bat files for diferent uses. Just open the .bat file with right click and select Edit to view the actions included in the file.
None of Alexei's fastboot installers have never included any command to erase Data, but I'd say it's mandatory to check twice the .bat file to be sure that you're not going to affect an undesired partition. In case e.g. the .bat file includes the line 'fastboot flash system system.img' but you don't want System partition to be installed, just delete this line from the file and Save before closing it.
Maybe you want to edit the file to include in the batch any other thing, a custom recovery for instance. Just drop your custom recovery file in the rom folder (the fastboot installer folder) and make sure that the line in the .bat file regarding the recovery matchs with your recovery file name.
Also you can notice that recent fastboot installers include more than one .bat file. They are named in a descriptive way like "UpdateZUI.bat" or "UpsateAOSP", but you should check them anyways. Let's say you're using any of the Q aosp-based custom ROMs (they include Boot and System partitions) and you want to update the vendor and/or the firmware. You should check the .bat files to find which of them suits better with your needs.
Click to expand...
Click to collapse
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom

hilary trump said:
Thanks for your instruction. Will this method work on other lenovo devices. I have a lenovo tablet running android 10 chinese stock rom, now I would like to flash global stock rom
Click to expand...
Click to collapse
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
Thanks. The rom has not released yet. I just pre-ordered a chinese variant tablet P11 pro TB-J706F

descarao81 said:
It depends on the rom package. The packages made to be installed using fastboot are usually very similar, but you should check the .bat files. I could take a look if you provide a link.
Click to expand...
Click to collapse
I found the link as follows
mirrors.lolinet.com/firmware/lenovo/ Tab_P11_Pro/TB-J706F/TB-J706F_S210002_201015_ROW.zip
But inside the package there is no BAT file though

Related

[HOW TO][LTE] Revert to original 4.0.1 STOCK on Windows

Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Thanks, this worked for me. However, it does not re-lock the bootloader. You can tell by when the Google logo is on the screen while booting up, if there is an unlocked lock on the bottom then it is unlocked. To fix this, type in:
flashboot oem lock
Click to expand...
Click to collapse
After that you should be good to go again and be stock.
Why not use the 4.0.2 image? Makes more sense to use the latest version:
https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Zzim said:
I get a "Missing adbwinapi.dll" error when trying to use your .bat? How do I ensure ADB is installed correctly?
Click to expand...
Click to collapse
If you've got the SDK installed put the fastboot files in the sdk\tools or sdk\platform folder where adb is located. The adbwinapi.dll should be located in there.
Or just copy adbwinapi.dll into the same folder where you have the "restore kit" files downloaded from the OP.
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
error
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
djeddieone said:
confirmed working bailed me out on a bootloop when trying to root my CDMA Verizon Galaxy Nexus
Click to expand...
Click to collapse
cerotes have galaxy nexuses? hrm
mikedfromaz said:
i have the flash.all file in my platform tools but i got an error device not recognnized message?
how do i get this file in zip form?
https://dl.google.com/android/aosp/m...y-516b56c2.tgz
Click to expand...
Click to collapse
Winzip.. unzip it twice...
Sent from my Galaxy Nexus using XDA App
edit: got it thanks
Thank you for the script..i know it will come in handy one day or another!
Sent from my Galaxy Nexus using xda premium
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
bigeric828 said:
whenever i try to extract the files using winzip it says it can't read the header etc etc. Any ideas?
Click to expand...
Click to collapse
It was zipped with WinRAR as a standard zip file. Should be able to be opened on just about anything... Have you tried redownloading?
oops already posted this but i put it in the wrong thread but here it is again sorry.
does anyone know how i can get this working? whenever i run it i just get an error: device not found
waiting for bootloader...
flashing bootloader...
error cannot load "bootloader-toro-primek10.img"
<waiting fo device>
anyone suggestion? ive tried reinstalling the drivers and its still not working
any help is appreciated thanks
so.....how do we run the script? with fastboot? with what commmands? it's late, i'm tired and i just want to start from scratch on my GNex...had Wallet running, then loaded BB, lost Wallet, now wallet won't run on ANY rom i have, even rebuilt to 4.0.2, but need to get back to 4.0.1...i posted a question in the Q&A section if there was an ODIN of 4.0.1 lying around somewhere....hopefully i'll get some help either way...
thanks.
EDIT...got it, double click the bat file...the original post did not say that.....thanks for the last post for mentioning it
|Jason8| said:
Hello, I did some searching and didn't see anything like this for Windows.
** NOTE: This requires the ADB and bootloader drivers to be installed already **
Google released the original 4.0.1 firmware (including radios and bootloader) in a compressed .tgz file. You can get that here:
https://dl.google.com/android/aosp/mysid-itl41d-factory-516b56c2.tgz
Extract the file into a working directory. Then... extract this (attached) into that directory as well.
Either reboot to bootloader manually or turn on USB Debugging, then run flash-all.bat and everything should go from there!
This is just a modified version of the script Google sent along with the package, so there shouldn't be any issues.
Tested the script on my own phone, and it completed twice. So it should be safe. But as always, you assume the risk!
Click to expand...
Click to collapse
Having seen the Nexus S sticky for factory firmware etc., I think its time we see this or another post evolve into the same sort of thing including full restores for 4.0.1, 4.0.2 and the eventual 4.0.3(lte) radio's etc.,
Here's a modified script that will allow you to choose between 4.0.1 and 4.0.2. (as long as you have either image or both) It also has the option to re-lock the bootloader.
I'll also update it when the official 4.0.3 images are released.
I don't take no credit for what was already done, I just modified it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Instructions:
=========
1- Extract folder with contents of this package.
2- You will need the Google Factory image for the version you want to restore, or both if you want.
3- Extract the image files to the same folder in step one. Image files should not be in a seperate folder!
So you should have, in one folder, the above files contained in this package plus:
image-mysid-xxxxxx.zip (xxxxxx= pertains to what version)
radio-tor-i515.xxxx.img
radio-cdma-tor-i515.xxxx.img
flash-all.sh
bootloader-tor-primexxxx.img
4- Dbl click on GNexRestore.bat and follow the prompts.
Optionally, if you do have the Android SDK installed, just copy the image files and GNexRestore.bat to the platform-tools folder.
fastboot.exe will also be needed, if you don't have it already, just copy the one in this package to the same location.
Then run GNexRestore.bat
when you extraxt the factory image i get one file and the icon looks like a blank piece of paper. is that how it is suppose to be
When you extract the image, you should see a folder with the files you need.
e.g. this is from 4.0.2

[root] mk3 4.3

WARNING!
Warranty may be void of your device if you follow the procedures given on this page!
You only are responsible for your device. I won’t be liable if any damage occurs to your device and/or its components.
BEFORE YOU BEGIN..
You must do this pre-installation stuff before attempting to root your device in order to avoid any complications later, and have a smooth and successful process.
BACK UP YOUR DEVICE
Back up important data and stuff before you start playing around here as there are chances you might lose your apps and app-data (app settings, game progress, etc.), and in rare case, files on sd card, too.
For help on Backup and Restore, check out our exclusive page on that linked right below.
ANDROID BACK UP AND RESTORE GUIDE: APPS AND TIPS
INSTALL DRIVER
You must have proper and working driver installed on your windows computer to be able to successfully root your device using Universal Root de la Vega script . In case you’re not sure, follow the link below for a definitive guide for installing driver for your Samsung Galaxy device on your computer.
Samsung Drivers
CHARGE YOUR DEVICES
If your android device, or PC, powers off due to lack of battery while the process is underway, it could damage the device. So,make sure both of them are adequately charged and that no power interruption takes place when the process is undergoing — at least 50% battery of the device and laptop is what we would recommend.
OTHER THINGS TO TAKE CARE OF:
└ Use original USB cable to connect your phone to PC.
└ Do not use the procedures given below on Mac (using VMWare) as it works best on proper Windows PC only.
DOWNLOAD FIRMWARE
Download the firmware you want to root. You can get the firmware from either SamMobile’s samsung firmwares directory or just Google the firmware you want to download to get the download link.
Once you’re done downloading the firmware make sure it’s a .tar/tar.md5/.exe file. If in case it’s in .zip format than extract the zip file to obtain either the .tar/.tar.md5/.exe file..
MK3 Firmware
STEP-BY-STEP GUIDE
Once you’ve downloaded all the required files given above, proceed with the instructions given below to get a knox-free root for your firmware using the URDLV (Universal Root de la Vega) script.
PART 1: Cook the firmware file using URDLV script
We’ll first cook your firmware file to make it compatible with the root scripts we’ll use in further parts of this guides. For this, we’re going to use URDLV script first
Extract the Universal-RDLV.zip file to a separate folder on your computer
└ If you have a anti-virus program installed, and it’s trying to delete some of the extracted files, then disable it for a while and re-extract the Universal-RDLV.zip file again, making sure nothing gets deleted.
Open a command prompt window inside the folder where you extracted the Universal-RDLV.zip file. Press “Shift + Right click” on any empty white space inside the folder and then select “Open command window here” option from the context menu
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can either create a FULL modified firmware file or just a CSC file from the firmware you want to root. In this guide we’ll be creating a FULL modified firmware as we believe it to be more reliable than creating a CSC file. Input the command given below in command prompt window and hit ‘Enter‘ to start building your modified firmware file
urdlv full C:\I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME.tar.md5
└ The command above is only for illustration purpose. After “urdlv full”, you must insert the path to location of the firmware file saved on your PC. It can be in either .tar, .tar.md5 or .exe format. To get the path to firmware file, you may drag n drop the file in command prompt window and it’ll automagically pickup the file’s path
Right after hitting enter, you’ll see another command window showing you progress of the file creation, which may take time, so be patient here!
You’ll see a similar window (like below) once the file is successfully created
Your modified firmware file is now created with ‘_VEGA’ added to the end of file name, I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_VEGA.tar.md5. The file is saved under “Output” folder inside the folder where you extracted files in Step 1
PART 2: Flash the modified firmware using Odin
Extract the ‘odin3.09.zip‘ file that we downloaded from the downloads section above. You’ll get the ‘Odin3 v3.09.exe‘ file
Boot your device into Download Mode:
Power Off your device first. Wait for 6-7 seconds after display is off
Now, press these 3 keys together until you see warning screen: Volume DOWN + Power + Home
Press Volume Up to continue to Download Mode
Start/Run the ‘Odin3 v3.09.exe‘ file that we extracted in Step 1
Connect your device to PC. Odin window will show an Added!! message in bottom left box.
└ If you don’t get the Added! message, then make sure you installed driver as given above, if yes, then uninstall and re-install driver again.
Also, try another USB port on your PC and make sure you use good quality cable, preferably that came with the phone. Reboot phone and PC and try again.
Click on AP button in Odin and select the firmware file we created in Step 5 of Part 1, I9505XXUEMJ5_I9505OXAEMJ5_I9505XXUEMJ5_HOME_VEGA.tar.md5
In the “Option” section of Odin, keep only the “Auto Reboot” and “F. Reset Time” boxes checked. All other boxes in the “Option” section should be kept unchecked
Double check the above two steps carefully. You must not make any mistake with the steps above or else you may brick your device. Your Odin’s screen should look like the screenshot below:
Click the ‘Start‘ button on Odin to start flashing the firmware file, and wait until you see ‘PASS!’ message on Odin’s top left box
When you get PASS! message, your phone will restart automatically. You can then disconnect your phone from PC.
└ If you see FAIL instead of PASS in Odin’s top left box, disconnect device from PC, close Odin, remove phone’s battery and put it back in 3-4 seconds, open Odin and then repeat PART 2 and PART 3 of this guide again
PART 3: Root your device
Extract the root_de_la_vega_sdcard.zip file to get these (one file and one folder):
root_de_la_vega.sh (file)
root_files (folder)
Important! Remove the external SD Card from your device, if connected
Connect your phone to PC and Copy the file (root_de_la_vega.sh) and folder (root_files) to the root of internal SD card on your device
└ It’s very important that you transfer the file and folder to the root on your device’s internal SD card.
Now, restart your device
Once it has restarted, delete file and folder you copied to SD Card in Step 3 above. Yes, delete the file (root_de_la_vega.sh) and folder (root_files), both of them
Important! Now, after you’ve deleted the files, restart your device again.
Once your device has rebooted, Root Access should be there. You can now insert your external SD Card back if you have one
└ Put the external SD card back only after rebooting the device (as instructed in step 6)
CONFIRM ROOT ACCESS
You must have a new app installed now: SuperSU. Check it in app drawer. Also, to check whether you got root access or not, use this simple made-for-this-purpose app, Root Checker.
Note: this will trip knox use it at your own risk
respective owner and all credits go to the people HERE
If you're saying that this may still trip Knox, the easiest and fastest way to root still remains just flashing a custom recovery with Odin and then flashing root.
Much simpler and much less time consuming than patching an entire tar and then flashing that huge file with Odin.
i understand cnexus but this was requested by a member of the community ive heard some people having problems with cf auto root i myself had problems with cf autoroot and a few other root ways so im just giving this to the community if all else fails for them like myself

[GUIDE][BR][LP]Complete guide for unlock bootloader and flash TWRP in H442F DUAL SIM

Hello folks!
It's been a while since last time I spent in this forum section (when the method for flashing Poland MM KDZ was published), but suddenly I decided to check the current development and it was great do discover that developers found a way to unlock bootloader! Then, I tried to do the procedures, found some adversities around the path, flashed stock KDZ for my device A LOT and finally managed to obtain a fully working LP stock with root and TWRP for my model: H442F (Dual SIM) ("LG Volt 4G" in Brazil).
The thing is: although a lot was done regarding the Spirit LTE, I found near zero information specifically for my device variant. Since I tried a lot of paths and eventually achieved an interesting result, I decided to write a full tutorial, with a lot of instructions and pictures for "novices" who desire learn all the steps but gives up at the high learning curve. Finally, I also wrote this tutorial in Brazilian Portuguese, which I believe will help at least some comrades (you can download the PDF in portuguese HERE).
Needed files:
LG Drivers (remove old ones if already instaled)
LG Flash Tool 2014 (credits to @quangnhut123 from this thread)
Brazilian H442F10a Firmware (this is a low speed server, I can upload to a better one if someone asks)
Android SDK Tools (for Windows users; Linux ones just install the package android-tools-adb)
Kingroot (or download here: www.kingroot.net)
Latin America Patched Aboot (credits to @pvineeth97 , for more info check this thread)
TWRP (or download here: https://twrp.me/lg/lgspiritlte.html)
Flashfy (or download here: https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en)
SuperSU (or download here: http://www.supersu.com/)
Finally, if you prefer, you can download a full pack in this link (except for KDZ), however, I did prefer to keep isolated links for better credits and referrals
Step-by-step
Download all needed files
Install drivers, SDK and unpack Flash Tool
Save all files in the same folder, but keep KDZ file inside Flash Tool folder
Put your phone in download mode (power off, hold vol+, plug usb in pc, keep holding until download icon appears)
Wait a little for Windows completely detects device and load all drivers
Verify in Device Manager if your pc detects phone as "LG Mobile USB Serial Port (COM#)"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open LG Flash Tool as admin
Select KDZ file
Choose the downloaded H442F10a_03.kdz file
Choose CSE Flash
Click START
Then, "Clear phone software update registry"
You'll see a warning
Then, OK (no need to change country)
Another app will open for the flashing. If you are offline, it is possible to show just a "?" character. Wait patiently...
In about 5min it will finish
After some reboots, you'll see the phone starter screen. Just move forward (no need to configure anything right now, maybe wifi, but not google account)
Enable Developer Options going to Settings/General/Common/Software Information and tap some simes in Build Number until the "You are a developer" message appears
Go back to Settings/Developer Options and turn on USB Debugging
With Debugging on, choose MTP (for Windows) or PTP (Linux), and when asked, allow the computer
Now, make sure you installed (and know how to use, since I will cover just a few commands here) the Android Debugging Bridge (adb). It will be essential for some steps, as well for entering Recovery Mode (I will show some Linux screenshots because I do not use Windows - for this tutorial, just for KDZ flash - but with a working adb the commands are the same)
Open a command prompt (Windows: right click in start menu) or a terminal (Linux) and run "adb devices" to see if the device was detected. If not, run again and check if phone are asking permissions (and grant it)
Go (cd) to the folder with all downloaded files and write the commands (some names may be different if you downloaded individual files from official links)
adb push aboot_5120_patched.bin /sdcard/
adb push twrp-3.2.1.0-cn70n.img /sdcard/
adb push SuperSU-v2.82-201705271722.zip /sdcard/
adb install Flashify_1.9.2.apk
adb install KingrootV5.3.1.apk
At whit point, make sure your internet is fully working (3-4G or WIfi), then, open Kingroot and root the device
After a well successful root, go back to adb and run "adb shell" and then "su". The phone will ask root permission. Grant it and in adb again run "cd /sdcard"
Now we arrived a critical step. Make sure to type the command as is show, because an error may result brick. We will copy the modified aboot into the respective phone partition (check code, check picture, and double check!)
If everything occurs all right, will appear this message
Great! Now you have an unlocked bootloader! What we have to do now is fhash a custom recovery (in this case, TWRP).
Open Flashify, give root rights, then go into Flash/Recovery Image/Choose a file/File explorer/sdcard/[downloaded file]. When asked to flash click "YUP!" and then "Flash More" (as we do not want the phone to reboot right now)
An extra step I prefer to do is remove Kingroot, since it installs a lot of services and keep device substantially slow. If you prefer Kingroot over SuperSU, you are DONE!
Case you prefer SuperSU... Open Kingroot/.../Settings/Uninstall Kingroot
It will prompt if you are sure. Just click Continue/OK
Go back to prompt/terminal and run "adb reboot recovery"
Phone will enter TWRP!
Now, just a few steps!
Go to Install and flash SuperSU
Go to Wipe and do a Factory Reset
Go to Settings and disable TWRP app installer (optional)
And finally go to Reboot and choose System
DONE!!!
Now you have a phone with an unlocked bootloader, a recovery capable of doing a lot of stuff (sideload, wipe cache, backups), and rooted as well.
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Korelev said:
A really good job, I'm sure a lot of your fellow countryman will find this very useful!
Click to expand...
Click to collapse
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Valeeeu dms irmao, ajudou dmss
Ninloth said:
Thanks man! Today I finally added a link with portuguese-br instructions. Hope more Brazilian users will have the chance to perform these operations!
Click to expand...
Click to collapse
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Hi!
Well, unfortunately I don't know. I made the procedure, wrote the tutorial, and 2 months later changed my phone for a new one. Can't test anymore.
Mrkblo said:
Thanks for the instructions. After unlocking its bootloader, wil it be compatible with any H440 custom rom (single sim operation, of course)? Or the only custom rom we get is Cm12?
Click to expand...
Click to collapse
Yes, it should be compatible with any custom rom as long as your phone is Lg spirit LTE( snapdragon variant ).

[Bootloader Unlock] [TWRP] [A7010a48] [Noob]

Overview​
Many people asked me on telegram how they can unlock their bootloader and flash TWRP, as obvious I helped them but then again few people asked me... I was wondering telling entire steps again and again will waste a lot of time so I decided why not on xda-developers?
So here it is presenting a "Noob way to unlock boot-loader, flash recovery" :laugh:
Disclaimer​
]Of course there is a risk of doing anything so I won't take any responsibly of fixing it !! Please do some research if you are not aware of anything. Warranty will be voilà so you won't be able to claim any service repairs for free. Please proceed at your own risk :angel: However, if you follow everything carefully you won't be able to stick into anything.
Click to expand...
Click to collapse
Downloads​1. ADB Driver 1
2. ADB Driver 2
3. Windows 10 Updater
4. ADB Toolkit
5. TWRP ​​
Installations​Now it's not hard but still like a manual, I have added this. To install the drivers first and most important is to update Windows to its latest release. Extract .rar/.zip files downloaded from the above download section and go to the ADB Driver 1 & 2 folder and look if there is an executable file like .exe/.bat if yes then run it as admin and all set if there isn't then you may see a setup information well simple look for a file ends with .inf extension. If you find such a file then simply open device manager and click on your PC name for e.g my PC name is MINIX and then click on action tab select add hardware legacy --> Next --> Search and install automatically --> Next --> Show all --> Next --> Have Disk --> Browse and then go to the folder where the .inf/setup information file is located click on it --> Next and then it may pop up something like driver signature verification failed for it just move HERE All set ! But I would suggest to do a windows update check again for proper installing of drivers and then restart.
Process​Now it's not rocket science! Let's begin!
* Update your phone to latest firmware S232 (Necessary)
* Open ADB Folder
* Copy Downloaded TWRP to ADB folder
* Rename TWRP image to recovery.img
* Move to your mobile turn on USB debugging and OEM unlocking (These options are there in developer option)
* Connect USB (Will pop up some prompt, allow for this pc if still not then revoke USB permission and check back! )
* Run .bat file called as unlock_recovery.bat
----------(Your Phone will reboot into fast boot mode and will start Unlocking process just hit volume up key on your phone when you see a prompt written in small letters)---------
* Now open the cmd/PowerShell in ADB folder itself for that hold shift key and right click will see a prompt with PowerShell/cmd click on that if still confused the go-to address bar and type cmd there. That's its!
* Type the commands one by one has listed :
Code:
fastboot devices
fast boot flash recovery
Now its important that you reboot into recovery for the first time just after recovery flash or else you will need to do entire process again … Now to boot into recovery you will have to hold power key & both volume keys at a time until you see Lenovo logo, then release the power key and volume keys. After the TWRP logo, it will take some time! So wait, but if not boot into recovery do all the process again !
Cheers :good: you have successfully installed TWRP now ! If still not then don't worry drop a replay below so that we can assist you I don't want to make money from this so no donations but still if you want to appreciate my work just hit the small button of :good: That's more than enough for me
Q/A​
Q.1 My TWRP is removed after I booted back into the system, now what can I do?
A.1 Well, This is a normal thing caused due to a backup made by system of stock recover and you will have to delete it in order to fully use TWRP for that process is simple to download Aroma File Manager Flash this zip into TWRP recovery and you will see a file manager locate to system folder and in that look for a file called as recovery-from-boot.p and delete this file only /-
Q.2 My device is rebooting into TWRP only, what to do?
A.2 Now answer is not that simple you will have to download the stock ROM and flash it via SP Flash Tool that's the only option. We are looking into the issue and will find the resolution ASAP.
For more Q/A just drop a comment below and we will try to solve it! And if the issue is common we will add it to this post
We know how important it is for you to get your issue fixed but there are certain rules you will have to follow, please read them so we can assist you further!
1. Don't use bad words
2. There is a pattern you will have to follow so that we can fix it or else it may get neglected
ROM: XYZ
Root Status: N/A
Recovery Version: XYZ
Issue: XYZ (Please use a short and effective description of your problem, Don't make it too long also before you post make sure it's not there in Q/A post.)
Click to expand...
Click to collapse
For more better rectification you can add a screenshot of your issue/error.
For additional help you can reach us at :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Telegram Group​
Hello folks, for redwolf recovery process remains the same, thread
But yea, the name of recovery is redwolf.img whereas for twrp its something else so just use this code
Code:
fastboot flash recovery redwolf.img
@reserved
link is broken
Hello everyone I need a favor from a person who has unlocked bootloader can you help
---------- Post added at 04:21 AM ---------- Previous post was at 04:19 AM ----------
I need some files from you pls please please please please

How To Guide Simple Guide How To Root

Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "fastboot reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Saved
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can't find my Downlaods folder. Idk what that is.
Gytole said:
View attachment 5574243
I can't find my Downlaods folder. Idk what that is.
Click to expand...
Click to collapse
Fixed lol
vassosman said:
Alright so a lot of people seem to have issues with rooting their device and creating a lot of spam on this forum because they don't know how to read.
This guide is for Windows PCs and will be for the people who don't want to read complicated guides.
What you Need:
A Device that has an unlocked Bootloader
The Factory Image of the ROM you are using or updating to Download Here
The Latest STABLE Magisk Download Here, if you are opting for a Beta/Canary then have fun.
7-zip or similar file extractor
ADB and Fastboot, I use Minimal ADB and Fastboot but this Script Here will download the latest version and add it to your PATH.
Way to Transfer Files to Phone (USB Cable?)
Steps:
Update to the Latest ROM. This can be done via Sideloading (personal preference) or OTA
Confirm you are on the same version as the factory image. Current is SP2A.220305.013 aka March 2022 Update
Extract the Zip File to a Folder. Current filename is raven-sp2a.220305.013.a3-factory-87b3bf0a.zip
Go in to the folder and extract the Image ZIP into a Folder. Current Name is image-raven-sp21.220305.003.zip
Find the Boot.img and transfer it to your device.
Install the Magisk Manager APK on the Device
Open Magisk and press Install.
Select "Select and Patch a File" and select the Boot.img you transferred to your device.
Magisk will patch the file and place the new .img file in your downloads. The filename will look like "magisk_patched-24300_abcde.img".
Transfer the patched file from your Downloads folder to your PC.
Reboot your phone to Fastboot mode Youtube Tutorial
Locate the patched .img file and press SHIFT+RightClick, click the option "Copy as Path"
On your PC open Command Prompt. If you dont know how to do this, you shouldn't be rooting your device.
In command prompt type "fastboot flash boot" and then paste the location of your patched .img file.
The whole command should look like "fastboot flash boot "C:\Users\Admin\Downloads\magisk_patched-24300_abcde.img"
Reboot the phone with the command "adb reboot"
Once the device is booted up, go to Magisk and see if you are rooted.
If there is enough demand, I can provide photos to help.
If I messed up along the way, let me know and I can change the guide.
Click to expand...
Click to collapse
It should be fastboot reboot
fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Good call, I was writing this on the fly and wasn't actually doing it as I was writing the guide.
fil3s said:
It should be fastboot reboot
Click to expand...
Click to collapse
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
EdBurger l said:
Rather than saying they don't know how to read", it might be that they don't understand the "meta-language" of any given discussion or explanation!
Click to expand...
Click to collapse
Goodo bruh.
vassosman said:
Saved
Click to expand...
Click to collapse
Do you really think this guide is too hard to follow? It's thoughtful that you typed out the steps but is it really less confusing or difficult?
[GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
.
dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
They are not required to change if you plan on running Magisk 24.3. I did not change anything when I updated my P6P (bought in Feb) and rooted it.
dmarden said:
Is the whole vbmeta / boot verification thing no longer necessary?
I tuned out from all the root stuff because I only unlocked in the beginning and didn't want to wipe.
Click to expand...
Click to collapse
not needed anymore with latest magisk
That's great news, I've been missing it.
I am going to do this on S3B1.220218.006 (QPR3 Beta 1.1). Fingers crossed!
Worked perfectly, the only thing I might add is a link to the Google USB Drivers (since they must've updated). I had them installed originally (to have unlocked my device in the first place) but needed to update them.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Thanks a ton! I would've never noticed that the wipe step was no longer needed.
I recognize I am replying a lot, haha... sorry about that.
Presumably the update method for this should work exactly like past Pixel devices, yeah?
For me, this method was as follows:
1. Download the full image and edit the script to remove the "-w"
2. Install the modified image
3. Boot up once
4. Then basically follow the original procedure from this thread again
I know on OnePlus devices I was always able to uninstall Magisk root via the Magisk app, take the OTA, then reinstall Magist root via the Magisk app before rebooting, but that never seemed to work on Pixel devices (at least for me).
Just to share...
I decided to give the Magisk restore images, OTA, install again before reboot method a try and it worked perfectly going from QPR 1.1 to 2.
Thank you for this post. I would like to root my phone. I am a noob and it’s a little intimidating. If you would add pictures, I for one, would really appreciate that. Thanks again!

Categories

Resources