Maze has finally published the Alpha Stock-Rom.
Download Link: https://goo.gl/9kCJiv :fingers-crossed:
The system.img file is incorrectly downloaded as a system 002.img file. It must be renamed. And then copy it to the folder "3. Maze_Alpha_V05_20170816 Official ROM".
Thanks!
Hope anyone can root this phone.
Hi!
I am in need of a new phone, and this one looks quite good at the price.. But what do you think can i expect from custom ROM scene here for it? I am a Xiaomi Fan, and my Mi4 was and is one of the best supported phones still. Do you think there will be a subforum for this device, custom ROMs (preferreable Lineage OS, or other close to AOSP ROMs? OFC nobody can know now, i understand, but what tells your experience of other new phones from new companys? It has created quite a buzz, so i think there will be a demand for sure..
Just am 2 afraid to get a phone without good custom ROM. Never had an Android in last 5 years with stock ROM. Total nightmare for me now to have to go back.
Root + TWRP 3.2.1
3 Methods to root MAZE Alpha
Note: Method II is the most universal and must works with almost any official ROM
I- Method 1 : flashing modified Magisk boot.img
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v14
7. Voila
I have used this Magisk guide to create it
I used old manual guide :
Code:
adb shell "rm -rf /data/local/tmp/*"
adb push META-INF/com/google/android/update-binary common magisk_inject boot.img /data/local/tmp
adb shell "cd /data/local/tmp/magisk_inject; mv ../common/* .; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/busybox busybox"
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "rm -rf /data/local/tmp/*"
II- Method 2 : using TWRP and Magisk.zip (External SDCARD or USB OTG cable needed)
1. reboot int bootloader mode : adb reboot bootloader
2. unzip and flash the the attached TWRP recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
3. In TWRP choose first "change language" then press the "cancel" button while asking you for decryption password for data
4. In your PC download the Magisk-v15.3.zip and put it in a USB key, or an SDCARD
5. Use an usb otg cable to connect the USB key to your phone running TWRP and install the Magisk-v14.zip from Usb-otg (or SDCARD)
6. bonus: do a complete backup of your phone : all partitions except cache and data to your Usb-otg (or SDCARD)
7. reboot and install the MagiskManager apk v14
III- Method 3 : using the phhusson modified boot image
1- flash the attached boot image, using fasboot (fastboot flash boot boot-super-bootimg-output-su-eng-r318.img) or SPFlashTools using the attached scatter, if you do not want to unlock your bootloader
2- reboot to Android then install from google play the phhsusson superuser
3- Voila
Important Notes:
1- In all case you can use SPFlashTools to flash boot image without unlocking bootloader.
2- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Some useful tips
1- manual install of busybox :
a- root you phone with method II if not already done
b- stay in TWRP (or boot TWRP as in method II) then in advance->sideload slide the slider to confirm and after cancel that (we will not sideloading any thing, just to activate adb)
c- unzip and copy the attached busybox : adb push busybox /external_sd/
d- mount the system partition with the TWRP mount button
e- copy the busybox binary to /system/xbin : adb shell --> cp /external_sd/busybox /system/xbin/
f- make executable busybox and create links (the point at the end is a part of the command) : cd /system/xbin/; chmod 755 busybox; ./busybox --install -s .
g- umount the system partition in TWRP and reboot
2- manually install the OTA update.zip :
a- Google and download those 3 tools BlockImageUpdate, simg2img and img2simg.
b- In a terminal of your Linux PC do :
Code:
simg2img system.img system.raw.img # convert the sparse image to a normal raw (ext4) image
BlockImageUpdate system.raw.img system.transfer.list system.new.dat system.patch.dat # patch the newly created raw image
img2simg system.raw.img system.img # convert the patched raw image to a flashable sparse image
- system.img: you old system image (from 20170816 official rom)
- system.transfer.list, system.new.dat and system.patch.dat : inside the OTA update.zip
c- After that the original system.img will be patched and you will have an updated system.img.
d- Flash this patched system.img and also all .bin and .img files inside the update.zip (just replace old ones in the original 20170816 rom by those) and you will have the new official rom
3- Using supersu as root manager :
The last update at this time of supersu zip (2.82 SR5) works well, even it cannot update the su binary.
Credits to Magisk Devs, Phhusson and Jemmini
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
If I root my phone with this method, will I get further OTA Updates from Maze?
Following to see where this goes.
Cheers
CrashCrash123 said:
If I root my phone with this method, will I get further OTA Updates from Maze?
Click to expand...
Click to collapse
Yes.
You will only lost the root.
If the new update have the same kernel, the same methode with the same boot image can be used to root it again, othewise, we can follow the Magisk guide to create a new one.
I have tried this method. But it only works until the reboot. Then the root access is gone again.
SomeOneX said:
I have tried this method. But it only works until the reboot. Then the root access is gone again.
Click to expand...
Click to collapse
The root is permanent.
If you lost it, perhaps the first time we unlock the bootloader, the phone do a reset, and we lost the root (I suppose).
Just re-flash the new boot again, and it will be permanent : fastboot flash boot new-boot.img
Hi . I have locked the OEM lock but I can not install it through fastboot (remote: not allowed in lock state)
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
alfymon22 said:
can we expect VOLTE on this device ?
and is there any chance of custom rom development for this device?
Click to expand...
Click to collapse
It seems (take with a pinch of salt) that VoLTE is supported, but then most sites that announce that also make mistakes on other specs, so...)
As for custom ROMs, so far the square root of bugger all, but the consumer phones are just filtering in, so give it time.
dreambo said:
Here how to root this phone.
1. make sure to have already installed the version 20170816
2. reboot the phone in fastboot mode (phone off -> Vol Up + Power or "adb reboot bootloader")
3. unlock the bootloader if not already done : fastboot flashing unlock (if not works, in android development setting set the unlock bootloader and then retry)
4. unzip and then flash the attached boot image : fastboot flash boot new-boot.img
5. reboot your phone: fastboot reboot
6. install the MagiskManager apk v13.6
7. Voila
I have used this Magisk guide to create it
Credits to Magisk Devs.
Click to expand...
Click to collapse
it worked, but i have cts fail on safetynet check. how you fixed this?
PrimateaEu said:
it worked, but i have cts fail on safetynet check. how you fixed this?
Click to expand...
Click to collapse
install the universal safety net fix
Hey guys, does this root method wipe the data partition?
KilljoyTDA said:
Hey guys, does this root method wipe the data partition?
Click to expand...
Click to collapse
The flash of the boot image does not wipe the data, but unlocking the bootloader reset the phone and wipe the data.
If you phone is already unlocked, you will not loss the data, otherwise do a backup before.
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
KilljoyTDA said:
Well, I don't remember unlocking it, unless Kingo's windows app does it without telling even when rooting fails, so I guess I'd better back up.
Thanks for the info
Click to expand...
Click to collapse
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Thank you @dreambo for this method, but for me "fastboot flashing unlock" not work, "fastboot oem unlock" working for me, all ok
ps:excusez moi pour mon anglais
dreambo said:
It is easy to know if your phone is locked or not : enter fastboot mode and then do : "fastboot getvar all".
Read the last lines of the output and you will know.
Click to expand...
Click to collapse
Well I failed to back up for some reason anyways, so since I had almost nothing vital on the internal memory, I rooted (sucessfully) and now I'm reinstalling/reconfiguring my apps. Thanks anyways
Related
Heisenberg's How-To Guide For Beginners
Nexus 6P
{
"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"
}
Intro
This thread will serve as a location for basic how-to guides for the Nexus 6P. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
If you're unsure about something please read the FAQ section in post #3 before creating a post to ask a question.
Prerequisites
Always update your phone to the latest build available before starting the unlocking/rooting process. This guide is always current/correct as per the requirements of the most recent build available.
You'll need a working adb/fastboot environment on your PC to get through some of these guides.
Google have finally decided to allow us to install adb & fastboot without needing to install the entire Android SDK. Hurrah! What does this mean for you? Much less mucking around. Grab the appropriate version for your OS:
Platform tools for Windows | Google USB driver for Windows
Platform tools for Linux
Platform tools for Mac
Main Page
Simply download and extract the archive (and follow the linked instructions for the Google USB Driver for Windows). Once you've extracted the download you should have a platform-tools folder, within that folder you should see fastboot and adb. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Please see older method for installing adb/fastboot here:
You must have Java installed and up to date in order to use the SDK Manager, please ensure that this is taken care of before installing the SDK.
Please do not install adb/fastboot via any means other than the Android SDK, using other tools (like Minimal adb & fastboot) can lead to an outdated setup and various problems with flashing. You've been warned, other tools will not be supported in this thread.
Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library, Google USB Driver
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into the bootloader (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Quick Tips
How to boot into the bootloader:
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
adb reboot bootloader
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
How to boot into recovery:
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
adb reboot recovery
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
Index
Post #1
1. How To Unlock Your Bootloader
2. How To Install A Custom Recovery On Your Device
3. How To Decrypt Your Data Partition
4. How To Make A Nandroid Backup With TWRP Recovery
5. How To Make An EFS Backup With TWRP Recovery
6. How To Root
Post #2
7. How To Install A ROM with TWRP Recovery
8. How To Install A Custom Kernel With TWRP Recovery
9. How To Update To A New Build Of The Stock ROM
10. How To Flash The Factory Images (Return To Stock)
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
12. How To ADB Sideload an incremental OTA update package.
13. How To ADB Sideload a full OTA update package.
14. How To Update To Android 7.0 Nougat
FAQ can be found in post #3!
1. How To Unlock Your Bootloader
Go into Settings/About Phone, scroll down and click on “build number†continuously until you see a toast notification telling you that you've enabled Developer Options. Go back to your Settings menu and enter Developer Options, scroll down and click on the “Enable OEM Unlock†checkbox, also make sure you enable USB Debugging while you're in the Developer Options menu.
Power off your phone then boot into the bootloader (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.
Once you've confirmed your fastboot connection issue the unlock command:
Code:
fastboot flashing unlock
This will erase all user data from the device!
You should now see a screen on your phone asking you to confirm this action, use the volume keys to scroll and the power key to confirm if you're sure you want to go ahead.
Allow the process to complete and then issue this command:
Code:
fastboot reboot
Allow everything to go ahead and once finished you can disconnect your usb cable.
Note: After unlocking your bootloader, each time your phone boots up you'll be greeted with a warning that says "Your device software can't be checked for corruption. Please lock the bootloader". This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is unlocked it will stay there.
Important: do not relock your bootloader unless your phone is fully stock. You must flash the factory images first in order to remove root and custom recovery (if you have them), if this precaution isn't taken you may end up with a brick. Please see section 10 of this guide for full instructions on how to return to stock.
2. How To Install A Custom Recovery On Your Device
Prerequisites: unlocked bootloader (section 1).
Download the latest TWRP Recovery.
Make sure you check the md5 of the file to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Boot into the bootloader. Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot flash recovery <filename>.img
(The recovery filename in the command will change depending on which recovery you're flashing)
Use the volume keys to scroll and power key to select the Reboot Bootloader option. Once the phone has booted back into the bootloader you can use the volume keys to scroll and the power key to boot into your newly flashed recovery. It's now safe to disconnect your usb cable.
When TWRP boots up you'll be asked whether you want to allow system modifications or to keep it read-only, choose to allow system modifications, there's no benefit to keeping it read-only.
On Nougat you need to flash SuperSU after booting into TWRP otherwise TWRP won't stick (see section 6).
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this.
3. How To Decrypt Your Data Partition
This is no longer necessary as long as you use TWRP 2.8.7.1 or newer, unless you are using the Android N developer preview, in which case you must decrypt.
Prerequisites: unlocked bootloader (section 1).
TWRP recovery cannot decrypt your data partition at this stage. In order for TWRP to be able to read/write on your data partition (to root or create a nandroid backup) you will need to format it, a format will remove encryption.
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter this command:
Code:
fastboot format userdata
Please note: this will erase all user data from the device!
Once the process has completed you can either reboot normally:
Code:
fastboot reboot
Or you can reboot back to the bootloader in order to undertake another task:
Code:
fastboot reboot-bootloader
4. How To Make A Nandroid Backup With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Warning: before you make a backup with TWRP you must remove all lockscreen security. If you do not do this you will not be able to unlock your device after restoring your backup (entering your pin will result in an "incorrect pin" message), you'll be forced to perform a factory reset to boot into Android. To remove lockscreen security go to Settings>Security>Screen Lock and set it to swipe/none.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, check the system/data/boor boxes, and swipe to backup. The process will take a few minutes.
Note: If you happened to forget to remove lockscreen security (PIN/Pattern/Fingerprint) before creating your backup, and you cannot get into your OS after restoring, you can do the following to fix the issue. Boot into TWRP and use the built in file manager to delete /data/sytem/locksettings.db. This should be enough to get you into your OS again. If it isn't you can also try deleting /data/system/locksettings.db-shm and /data/system/locksettings.db-wal. If this still doesn't fix your issue you can delete /data/system/gatekeeper.password.key and /data/system/gatekeeper.pattern.key.
5. How To Make An EFS Backup With TWRP Recovery
An EFS backup is very important to have, if your EFS partition becomes corrupt you will have no IMEI, and therefore will not be able to use the phone as a phone. Making an EFS backup is insurance against this catastrophic event. Without a backup, restoring your EFS can be extremely difficult or impossible. The backup you create can be easily restored using the restore tool in TWRP recovery.
Boot into TWRP and select the backup option from the TWRP home screen, make sure only the EFS box is selected, and swipe to backup. The process will take a few seconds. Keep a copy of the backup on your phone and also keep another copy somewhere safe.
6. How To Root
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Download the latest root version (Magisk, SuperSU) of your choosing to your phone:
Magisk Stable
Magisk Beta
SuperSU Stable
SuperSU Beta
Boot into TWRP recovery and enter the install menu.
Navigate to where you have the root zip stored on your internal storage and select it.
Swipe to install.
Once the zip has installed you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
Do not flash the version of SuperSU that TWRP offers to flash for you in order to give you root, it is not compatible and will cause problems. When you attempt to reboot out of TWRP it will tell you that it's detecting that you don't have root and it will offer to root for you, skip past this. You do have root, ignore this every time it comes up.
FAQ can be found in post #3!
Donate To Me
FAQ can be found in post #3!
7. How To Install A ROM with TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device. You'll also need to find out what build your ROM is based on and download the vendor image for that build, you'll find the latest in my index here.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your internal storage and select it. You can hit the "add more zips" button now to queue up your gapps package to be flashed after the ROM zip.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.
Hit the home button once everything has finished installing.
Install the appropriate vendor image.
Select the install option from the TWRP home screen.
Click the "install image" button in the bottom-right corner.
Navigate to where you have the vendor image stored on your internal storage and select it.
You'll now be asked which partition to flash the image to, select vendor.
Swipe to install.
Once you've installed all necessary zips/images you'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button and you'll boot into your new ROM.
8. How To Install A Custom Kernel With TWRP Recovery
Prerequisites: unlocked bootloader (section 1), TWRP recovery (section 2).
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system, hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
9. How To Update To A New Build Of The Stock ROM
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the latest build via the appropriate factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
Once all operations are complete you can reboot the device.
You'll have to flash SuperSU again now, plus add any mods that you previously had.
10. How To Flash The Factory Images (And Return To Stock)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box. This will wipe everything from the phone. If you wish to flash the factory images without wiping your personal data from the internal storage please move on to the next section.
Go to Settings/Backup & Reset and perform a factory data reset. This will remove all of your user data from the device (apps, settings, photos, music, etc).
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
If you wish to you can also relock the bootloader with this command:
Code:
fastboot flashing lock
(This command will wipe all user data from the device)
Important: do not lock the bootloader unless you have first flashed the stock images. Locking the bootloader while you have a custom recovery installed can result in a brick. Please also note that the locking procedure will wipe all user data from the device.
Once all operations are complete you can reboot the device.
11. How To Flash The Factory Images (Return To Stock But Leaving Internal Storage Intact)
Prerequisites: unlocked bootloader (section 1).
This section will explain how to return the phone to be like it was when it came out of the box, except it will not wipe any of your personal data (photos, music, etc) from the internak storage.
Download the appropriate factory images for your model here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img (not present on Android 7.1.2 and above)
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into TWRP recovery and enter the wipe menu, select advanced wipe, check only the data box and swipe to wipe.
Go to the TWRP main menu and enter the reboot menu, select bootloader. The phone will now boot into the bootloader, once it has you can connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
On 7.1.2 and above you'll also need to boot into TWRP recovery and wipe cache and dalvik cache.
12. How To ADB Sideload an incremental OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the appropriate OTA zip from my index. OTA updates must be taken in order so you must select the right zip. For example, if you're currently on the MMB29Q build you must select the MMB29Q --> MHC19I zip. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "ota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload ota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
13. How To ADB Sideload a full OTA update package.
Prerequisites: Completely stock setup (the only modification allowed on the phone is the unlocked bootloader).
Download the OTA zip that you want to upgrade to from my index. You don't need to be on any specific build prior to flashing a full OTA package. You can only move to a higher build though. The filename will be quite long so to make things easier you can rename it to something easier. For the purposes of this guide let's say we'll rename it to "fullota.zip". Place the file in your fastboot folder on your PC.
Boot into the bootloader, use the volume buttons to scroll the options and use the power button to select recovery mode.
Once the phone has booted into the stock recovery (you should see Andy Android with an exclamation mark) hold power and tap volume up to get into the recovery menu. Use the volume buttons to scroll and use the power button (you might need to hold it) to select "apply update from adb".
On your PC navigate to your fastboot folder, hold shift and right-click your mouse, select "open command prompt here". Issue the following command:
Code:
adb sideload fullota.zip
Wait for the operation to complete (it'll tell you once it's finished) and once it's all done you can reboot your phone, the first boot might take a while.
14. How To Update To Android 7.0 Nougat
Prerequisites: unlocked bootloader (section 1).
This method does not wipe your data, so you will keep your apps and settings. You should have no problems, however, if you experience problems you may need to perform a factory reset and flash again. Make a backup first and transfer it to your PC.
Download the Nougat factory images for your model (Nexus 6P/Angler) here.
Unzip the angler-xxxxxx-factory-xxxxxxxx (x's replace variables) into a directory on your PC (for this guide we'll use C:\angler\).
Once unzipped you should have a folder named angler-xxxxxx (x's replace variables). Open it and move the following files to a new directory named C:\angler\images\:
bootloader-angler-angler-xx.xx.img
radio-angler-angler-xx.xx.img
(Please note that radio and bootloader naming changes from build to build so the filenames and below commands will change with them)
Within C:\angler\angler-xxxxxx\ you'll see another zip archive named image-angler-xxxxxx, unzip the contents of that zip into the C:\angler\images\ folder we created before. Now within C:\angler\images\ you should have the following files:
android-info.txt
boot.img
bootloader-angler-angler-xx.xx.img
cache.img
radio-angler-angler-xx.xx.img
recovery.img
system.img
userdata.img
vendor.img
Boot into the bootloader and connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here), enter these commands to flash:
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
You can skip flashing the recovery if you wish, but even if you do the stock recovery may be patched on the first boot anyway. So you'll need to flash TWRP and SuperSU again if you need/want those, as well as any other system modifications you may have had.
Note: Do not flash the userdata.img
Once all commands/flashes are complete you can reboot the device:
Code:
fastboot reboot
You'll have to flash SuperSU again now, plus add any mods that you previously had.
FAQ can be found in post #3!
Donate To Me
Frequently Asked Questions
1. How do I boot into the bootloader?
Power off your device. Once it's powered off hold power + volume down and the phone will boot into the bootloader. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot bootloader[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the bootloader directly from Android (root required).
2. How do I boot into recovery?
Boot into the bootloader (see above), use the volume keys to scroll through the options and use the power button to select the recovery mode option. You can also use the following adb command:
Code:
[/INDENT]
[INDENT]adb reboot recovery[/INDENT]
[INDENT]
You can also use an app called Quick Boot to boot into the recovery directly from Android (root required).
3. When issuing the fastboot flashing unlock command it doesn't work, I only get a list of possible commands. What's going on?
This is usually due to having an outdated adb/fastboot setup. If you installed adb/fastboot by any means other than via the Android SDK this is probably the cause. Visit the prerequisites section in the beginning of this guide to properly install adb/fastboot and ensure that it's up to date.
4. After unlocking the bootloader I get a message that says "Your device software can't be checked for corruption. Please lock the bootloader". What's going on? Can I get rid of it?
This is nothing to worry about, it's normal to see this when you have an unlocked bootloader. You can't remove it, as long as your bootloader is locked it will stay there.
5. How do I take an OTA or update if I have root or other system modifications on the stock ROM?
You can't take an OTA update while you have root or any system modifications. You'd need to use fastboot to flash the system, boot, and recovery images. It's much easier to just flash the newer build with fastboot, see section 9 of this guide for full instructions.
6. Does taking an OTA update wipe my user data?
No, it doesn't.
7. Do I need to make an EFS backup?
Yes. Absolutely yes. An EFS backup is extremely important, if your EFS partition becomes corrupt your IMEI will disappear and you will not be able to use the phone as a phone. Without a backup it can be extremely difficult (or impossible) to restore your EFS.
8. Do I need to flash the userdata.img from the factory images?
You should never flash the userdata image. It doesn't take into consideration the storage capacity of the device and always allocates 32gb of storage. This is ok for the 32gb model, but for the 64gb and 128gb models you'll end up with much less storage capacity than you should have. If you wish to wipe your internal storage you'd use the following command instead:
Code:
[/INDENT]
[INDENT]fastboot format userdata[/INDENT]
[INDENT]
Reserved
Reserved
Reserved
Reserved
thanks
works great
The_android_Modder said:
works great
Click to expand...
Click to collapse
Lol, how?
Heisenberg said:
Lol, how?
Click to expand...
Click to collapse
Magic
tyvar1 said:
Magic
Click to expand...
Click to collapse
xxtruplayaxx16 said:
lmao
Click to expand...
Click to collapse
He must be from the future...
The_android_Modder said:
works great
Click to expand...
Click to collapse
thank you for the morning lolz
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
tf2manu994 said:
If we wanted, could we just go to step 4, and not do the rest? I.e just root stock and leave it as is?
Is that safe?
If it is, can I flash a rom on later?
Thanks
(I know the device isn't out yet, just getting prepared for it.)
Click to expand...
Click to collapse
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Heisenberg said:
No, because you need a custom recovery in order to flash SuperSU, and you need an unlocked bootloader to flash a custom recovery. Why not just unlock the bootloader?
Click to expand...
Click to collapse
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
tf2manu994 said:
Ah you misunderstood me, I mean like do all steps upto 4, and then not do the rest?
Sorry for misunderstanding
Click to expand...
Click to collapse
Ahh ok, now I understand. Yes of course, they're not actually steps that all need to be completed, they're just numbered sections. So if all you want to achieve is to root your stock ROM then you only need to follow steps 1-4.
Hemm sorry but are we talking about a phone that doesn't exist?
Fentadroid said:
Hemm sorry but are we talking about a phone that doesn't exist?
Click to expand...
Click to collapse
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Heisenberg said:
It certainly does exist, it just hasn't been released yet. And as it says in the OP these processes remain virtually unchanged from model to model in the Nexus line.
Click to expand...
Click to collapse
I hope that too!!!
Great Job
Thanks for your Hardwork:good:
Hello.
Probably You knot that. I can't find it.
I am looking for an information (instruction) how to root Le 2 Max. And I can't.
I rooted one year ago Huawei P6, it was easy. But I don't remember many details and can't find an instruction "step by step": do X, then Y, press Z and so on.
Can You paste a link?
(I know, my english isn't perfect.)
MoRiA Cheo said:
Hello.
Probably You knot that. I can't find it.
I am looking for an information (instruction) how to root Le 2 Max. And I can't.
I rooted one year ago Huawei P6, it was easy. But I don't remember many details and can't find an instruction "step by step": do X, then Y, press Z and so on.
Can You paste a link?
(I know, my english isn't perfect.)
Click to expand...
Click to collapse
Rooting Le Max 2 is the simplest. I am assuming that you are on 15s or 16s stock ROMs (They can be any... Indian, Chinese or US versions)
Power off your Le Max 2.
Boot to fastboot or bootloader: Power + Vol Down
1. Download 15s TeamSpain recovery. link
2. Download and install Minimal adb and fastboot from here
3. Make sure the recovery img file is placed in the same folder where fastboot.exe and adb.exe are located.
Go in that folder, press shift button and right click -> Open command window here.
fastboot twrp flashing command: just copy and paste the below command in the dos window with your phone connected in fastboot mode.
Code:
fastboot flash recovery TWRP5.8TeaMSpaiN.img
4. Boot to recovery: Power + Vol Up
When booting into TWRP, ignore your phone is encrypted messages and go through those warnings to reach TWRP's main menu.
Erase the data partition (Some ROMs are encrypted eg. IN or US Roms are encrypted) Wipe -> Advanced wipe -> Tick Data option and -> Swipe to wipe
5. Reboot again in recovery to get access to data partition. (Do not boot to system or EUI will over write the TWRP with stock recovery.
6. Flash SuperSU 2.76 (Whichever is latest) using adb sideload command. link
7. Sometimes you may have to flash SuperSU zip twice.
8. Reboot to system and you will have a rooted phone. Make sure you Swipe to disable replacing TWRP.
It can't get any more clear than this.
OK, thank You.
There is "step by step". But for sure:
1. Link: there is a recovery (=TWRP) for this custom ROM, right?
1A. Fastboot = Power + Vol Down?
1B. Any file's name? Any path?
2. Boot into recovery = Power + Vol Up?
2A. Erase ALL data?
Many question yet.
Is this a similar instruction to EXACTLY THE SAME ROM?
http://revolutionlemax2.blogspot.com.es/search?updated-max=2016-05-29T03:11:00-07:00&max-results=7
Now I see You wrote more. Thank You. Now is my fight.
MoRiA Cheo said:
Now I see You wrote more. Thank You. Now is my fight.
Click to expand...
Click to collapse
I was editing my post. Now refresh and see.
Hello again.
You helped me very much. I know more but still have a problem. But first:
1. I have EUI version 5.8.015S (Stable) and number of compilation: FEXCNFN5801507014S. Not sure if 14S if 15S.
2. I had off "debugging". I turned it on. Then I installed some drivers.
3. I installed the downloaded application (.exe file) and paste ".img" file into Program File (not on desktop or "downloaded"). Correct? I think so: only in Program Files are fastboot.exe and adb.exe.
4. I did something else: left Shift + left Ctrl + Right Click -> console and I paste "fastboot oem unlock". There was an info "success".
5. And then was a problem. Shift or Ctrl+Shift (I tried both) and paste "fastboot flash recovery TWRP5.8TeaMSpaiN.img" (no quotations) gave me such info: error: cannot load 'TWRP5.8TeaMSpaiN.img'
And over and over.
I got stuck.
Do You have any idea?
MoRiA Cheo said:
Hello again.
You helped me very much. I know more but still have a problem. But first:
1. I have EUI version 5.8.015S (Stable) and number of compilation: FEXCNFN5801507014S. Not sure if 14S if 15S.
2. I had off "debugging". I turned it on. Then I installed some drivers.
3. I installed the downloaded application (.exe file) and paste ".img" file into Program File (not on desktop or "downloaded"). Correct? I think so: only in Program Files are fastboot.exe and adb.exe.
4. I did something else: left Shift + left Ctrl + Right Click -> console and I paste "fastboot oem unlock". There was an info "success".
5. And then was a problem. Shift or Ctrl+Shift (I tried both) and paste "fastboot flash recovery TWRP5.8TeaMSpaiN.img" (no quotations) gave me such info: error: cannot load 'TWRP5.8TeaMSpaiN.img'
And over and over.
I got stuck.
Do You have any idea?
Click to expand...
Click to collapse
Why are you messing around with USB debugging? I have not mentioned about it in my guide. Copy the recovery img file to the place where adb.exe and fastboot.exe are installed on your computer. I cannot know what path you used to install it. Check if it is C:\Program Files (x86)\Minimal Adb and Fastboot
I cannot help you further if you don't know where you have installed the fastboot program. You shouldn't even be rooting your phone alone. Get some Android expert friend to help you out.
You was right. I made a big mess.
But finally I did it! I rooted the device and I have this ROM: http://forum.xda-developers.com/le-max-2/development/cm13-lemax-2-teamspain-revolution-t3404634
Thank You so much. Someone has to tell me: **** up and listen. You did it.
Respect for You.
confusion:
sanke1 said:
Rooting Le Max 2 is the simplest. I am assuming that you are on 15s or 16s stock ROMs (They can be any... Indian, Chinese or US versions)
Power off your Le Max 2.
Boot to fastboot or bootloader: Power + Vol Down
1. Download 15s TeamSpain recovery.
2. Download and install Minimal adb and fastboot from
3. Make sure the recovery img file is placed in the same folder where fastboot.exe and adb.exe are located.
Go in that folder, press shift button and right click -> Open command window here.
fastboot twrp flashing command: just copy and paste the below command in the dos window with your phone connected in fastboot mode.
Code:
fastboot flash recovery TWRP5.8TeaMSpaiN.img
4. Boot to recovery: Power + Vol Up
When booting into TWRP, ignore your phone is encrypted messages and go through those warnings to reach TWRP's main menu.
Erase the data partition (Some ROMs are encrypted eg. IN or US Roms are encrypted) Wipe -> Advanced wipe -> Tick Data option and -> Swipe to wipe
5. Reboot again in recovery to get access to data partition. (Do not boot to system or EUI will over write the TWRP with stock recovery.
6. Flash SuperSU 2.76 (Whichever is latest) using adb sideload command.
7. Sometimes you may have to flash SuperSU zip twice.
8. Reboot to system and you will have a rooted phone. Make sure you Swipe to disable replacing TWRP.
It can't get any more clear than this.
Click to expand...
Click to collapse
2. Download and install Minimal adb and fastboot from here ___
There are a number of files, and none called lemax 2. What file should i use?
This TWRP & TWRP Installer is Unofficial.
Official TWRP Can find on following link : https://forum.xda-developers.com/one-power/how-to/official-twrp-motorola-one-power-t3848354
NOTE:- Decryption support available now for TWRP in Fastboot mode only (TWRP installer currently not support for decryption)
Credit & Thanks
@erfanoabdi for bringing officeal TWRP for MOTO one Power
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Warning:-
I am not responsible for bricked devices.
Your warranty will void now. Do it at your own Risk.
Requirement:-
1. Unlock Bootloader Link By @rushiranpise :- https://forum.xda-developers.com/one-power/how-to/guide-motorola-one-power-unlock-relock-t3858797
2. Minimal adb & fastboot install on pc :- https://forum.xda-developers.com/showthread.php?t=2317790
Note: - As google introduce the partation AB for android one devices so there is no recovery partation sepereatly .
We need to patch recovery into Boot.img.
Guide:-
1. Download Twrp recovery.img & TWRP Installer. keep TWRP_recovery.img in adb folder and copy twrp insatller to sd card of phone
2. go to settings/about phone/build number (tap build no for 7 time now developer option available in settings)
3. go to developer option turn on usb debugging .
4. then go to pc download and extract and copy adb fastboot driver folder in Drive C. (or install form net.)
5. Go in fastboot folder which is copied to C. press and hold shift key on your key board and click right key on your mouse . it will show option open cmd here or open power shell window here.
6. Click it, A cmd window will open. or you can open CMD in pc as admin and use cd cmd to adb minimul folder.
type "adb devices" - it show some no of your device in cmd window on pc if not just revoke adb from your phone developer setting and give permission from your phone screen)
type "adb reboot bootloader" your phone reboot in bootloader mode.
Now Type in CMD :-1. fastboot devices (a device no. will show in cmd window on pc) if not means fastboot not installed properly reinstall it.
2. fastboot boot TWRP_recovery.img (phone will boot in twrp temporary)
(Now if you want to read your internal storage in twrp then you need to wipe by select format data option at bottem right of twrp. Beware it will erase all data from your phone ) if you not want then skip this
3. select install option and select sd card from select storage option from twrp.
4. select twrp installer which you copied into sd card and install.
Done TWRP now installed into boot. reboot to recovery and then reboot to system.
Note:- you need to flash this installer after every rom flashing or boot flashing to patch boot again because now twrp is inside the boot itself
New Link TWRP3.3.1 (update)- https://drive.google.com/open?id=1iRpOyUA-FleNwiWO7Rmu5kEeWjgmDBox (decryption support)
Link TWRP3.3.0 (update)- https://drive.google.com/open?id=1k5nZ3AfAd8GEkbPN3ntPj7c922VbqqfZ (decryption support)
As in TWRP 3.3.0 there is no need of twrp installer zip, in advance function of twrp there is option to install ramdisk into boot. this option is available but not working for us . it is installing but stuck on teamwin logo so use only as boot in twrp don't install it.
OLD LINKS : TWRP Installer :-https://drive.google.com/open?id=1mTlm2DRrIfOTeSpB4YnVLKCVcKtPjgF7
TWRP recovery :-https://drive.google.com/open?id=1xzg-TpDOska_w9aExyKVflKBCA8TRD6O
TWRP Decryption Supported Recovery:- https://drive.google.com/open?id=1iYOk0OdddPuylfl0TRI73d9zSYigllwV
How to Take Nandroid Backup and Restore (Only for Decryption support twrp)
1. boot into twrp via fastboot and enter your pin or password to decrypt.
2. Most important - go to backup and unselect oem and system and vendor. (there are two system and vendor unselect one and only select system image and vendor image to take backup)
3. now select storage where to take backup either internal or external or usb otg.
4. take backup.
5. For restore select restore and do.
6. step 2 is most improtant never use these partition to take backup or restore.
Note:- if after restore phone not boot properly or any issue don't panic restore stock rom(which backup you have) & boot and do process again to resotre. always better to restore only boot, system image and vendor image and data only.
Version-4
added all official support in this
Removed MTP & fix bugs for wiping partition
Removed Toybox & included busybox
advance versoin then official TWRP(Compiled with PIE source)
Decryption Working now (Not in installer)
thx.
I get this error, someone knows how to solve it ?
colorist said:
thx.
Click to expand...
Click to collapse
HTML:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot boot TWRP_recovery.img
downloading 'boot.img'...
OKAY [ 0.615s]
booting...
FAILED (remote failure)
finished. total time: 1.522s
I have my bootloader unlocked , and I'm trying to install TWRP in my moto one
I get this error, someone knows how to solve it ?
angelogiuseppe said:
HTML:
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot boot TWRP_recovery.img
downloading 'boot.img'...
OKAY [ 0.615s]
booting...
FAILED (remote failure)
finished. total time: 1.522s
I have my bootloader unlocked , and I'm trying to install TWRP in my moto one
I get this error, someone knows how to solve it ?
Click to expand...
Click to collapse
same here, any help ???
Amaterasus said:
same here, any help ???
Click to expand...
Click to collapse
try transferring the .img file to sd card first and then try the same command
maybe it will help
you can try these methods too:
i) check if the bootloader is getting lock again
ii) you've turned on oem unlocking in develeper options
iii) check the partiton isn't corrupted
and if these does not help you try factory resetting your device.
good luck
we have to flash installer after boot into recovery?
ZeroVirus said:
we have to flash installer after boot into recovery?
Click to expand...
Click to collapse
yes bro
and you'll have to flash it everytime you install a custom rom
---------- Post added at 05:27 PM ---------- Previous post was at 05:24 PM ----------
Amaterasus said:
same here, any help ???
Click to expand...
Click to collapse
if you are still getting this error
I find a way to get through it
just enter the command and press enter without connecting your phone
it will show that its waiting for device
then get into the bootloader by holding down power and volume down button
then connect the phone to pc
it should do the work
Does the latest twrp 3.3.0 works with the flash command or I can only boot it?
I am currently using the old version with the twrp installer.
Wanted to know if the latest twrp is working with flashing recovery partition.
Plz port multi rom twrp for one power
Not working
nerdfail said:
Does the latest twrp 3.3.0 works with the flash command or I can only boot it?
I am currently using the old version with the twrp installer.
Wanted to know if the latest twrp is working with flashing recovery partition.
Click to expand...
Click to collapse
Yes same question here ??
P30 Note?
Hello,
will it work with Motorola P30 Note (XT1942-1)? Basically the same phone, but without LTE B20.
TWRP not decrypt internal memory.
Hi sir.
I am using TWRP recovery 3.2.3 on my Motorola one Power.
I am facing problem internal memory are showing incrypted.
How can I fix this.?
I also used it new updates. They are not working.
When I flashed this twrp-3.3.1-1-chef.img internal file was decrypt but twrp shows devices unrooted.
Can you help me out sir.
I'm trying to install twrp latest version 3.6 plus but after boot it's not open stuck at the twrp logo after reboot
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3/development/twrp-3-2-3-0-pixel-3-t3861622
Download: https://dl.twrp.me/blueline/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
GitHub: https://github.com/topjohnwu/Magisk/releases
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
Was my misunderstanding. I thought you were implying people should go back to stock recovery to flash ota. You are talking about flashing ota in twrp. You might clear that up a little bit in that section.
Great post.
Unfortunately, if you are writing a process, then writing everything out is a requirement. Especially with item numbers or using an outline format. Not everyone understands shortcuts taken or abbreviated words, unless they are spelled out in the beginning. IMO, wrote and read too many processes. Including software requirement documentation.
Hi,
thanks for the thread :good:
wangdaning said:
Number 3 in "Applying OTA via ADB sideload" should be flash stock boot.img I think.
Click to expand...
Click to collapse
Yes, I think so too.
rczrider said:
I wrote it like that because the file isn't actually called "boot.img", but rather "bootloader-blueline-blahblahblah.img" where "blahblahblah" is the release. Since it changes, I figured just calling it the "bootloader IMG" would make more sense.
Click to expand...
Click to collapse
The boot.img is into "image.zip"
Then I suggest to flash into a and b (or both)
Code:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
or
fastboot flash boot --slot all boot.img
Edit
be careful here: Factory reset via ADB sideload (can also do this without wiping data)
bootloader is bootloader, boot is boot, bootloader.img isn't boot.img
so, maybe better to write:
fastboot flash bootloader nameofbootloader.img or if simply renamed fastboot flash bootloader bootloader.img
deleted, bug.
trouble flashing files
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
wangdaning said:
Please read the instructions carefully. You cannot flash twrp directly. "fastboot boot twrp.img" then when twrp boots you can use it or make it permanent by flashing the install zip or the internal twrp option. I go with the install zip as it seems more stable to me (placebo I suppose).
Click to expand...
Click to collapse
Thanks, but still no luck.
fyrmd said:
When I try to flash twrp.img or boot.img this is what I get back " FAILED (Write to device failed in Send Buffer() (Too many links)) fastboot: error: Command failed.
Any thoughts?
Click to expand...
Click to collapse
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
fyrmd said:
Turns out it was the cable, it is an expensive one from Amazon so not sure what I should be purchasing for next time.
Click to expand...
Click to collapse
I always buy Anker cables and chargers. All have been good so far.
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
Are you able to get into recovery? If so, download the full ota to your pc and side load it with adb.
xiaowei666 said:
Now,my pixel 3 can not work,the bootload is locked.when I select recovery by fastboot,The phone noticed me can not find vaild operating system,the device will not start.
Click to expand...
Click to collapse
i same issue
rczrider said:
[*]Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Click to expand...
Click to collapse
why not copy all files?
---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------
fyrmd said:
Thanks, but still no luck.
Click to expand...
Click to collapse
boot to the twrp.img and flash the twrp.zip, unless you are on android 10 you should have no problem unless you are doing it wrong. not exactly hard to do.
How to enable oem unlock in this case?
pedro5148 said:
How to enable oem unlock in this case?
Click to expand...
Click to collapse
There are a few suggestions at https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
However, if the network carrier has locked the bootloader, you cannot unlock it. In the U.S., Verizon and AT&T phones generally cannot be unlocked due to locked bootloaders.
Hi, first of all, I'm not a dev or else just user who had difficulties to flash GSI on my phone... Was 7 years with a samsung galaxy Note 3, with twrp....So easy to flash....
with the help of @gr0ndpa, thanks to him.....
FLASH GSI
Now I will explain how to flash easily with files attached
1/ first of all you need a phone and drivers installed, use xiaomi pc suite, unzip and install it
2/ you need to activate USB debug in dev options.
3/ dl adb folder unzip it and put in C
4/ run command and type
Code:
cd /adb
5/ then
Code:
adb devices
to check if phone recognised
6/
Code:
adb reboot bootloader
once in fast boot
7/
Code:
fastboot flash vbmeta vbmeta.img
wait finished type to enter in fastbootD
8/
Code:
fastboot reboot fastboot
9/
Code:
fastboot flash system
LiR 313.XXX.img
you will have a system error, but wait the flash begin in few seconds
at the end wait ok then
10/
Code:
fastboot reboot recovery
on stock recover
11/ wipe data and reboot with +/- and PWR
and you're done...
In case you want to flash custom kernel or patched boot image to root with magisk, you have to
12/
Code:
adb reboot bootloader
Copy kernel boot image to C drive and rename kernel boot image to boot.img.
13/
Code:
fastboot flash boot c:\boot.img
14/
Code:
fastboot reboot
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
Downloads for : Xiaomi Mi 11 Lite 5G | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
You can check what I ve done on tuto ss...
if you have some comments, don't hesitate...
I flashed LiR 18.1 rom and very happy with it.....
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++==================================================================================================================================================================================================================++
Flash ROM
This now how to flash ROM on your device, it's convenient for all roms like LOS, corvus, awaken...
First you need all the proper drivers installed and unlocked bootloader, USB debugging all of that stuff.
Now open up a cmd/terminal , and put the files i sent and the ROM file in the folder from where you're opening the cmd/terminal and connect the phone (you may need to put ./ as an suffix for all the commands if you're on linux)
Type
Code:
adb reboot bootloader
Then type
Code:
fastboot devices
to see if everything is ok
Then type
Code:
fastboot flash boot_ab boot.img
(you can drag and drop the file instead of typing it)
After that's done type
Code:
fastboot flash vendor_boot_ab vendor_boot.img
(you can drag and drop this too if you want)
Code:
fastboot flash dtbo dtbo.img
(you can drag and drop this too if you want)
After that's done type
Code:
fastboot reboot recovery
This will boot you into a recovery and now you need to go to wipe and format data
After that go to apply update then adb sideload then
In the cmd type
Code:
adb sideload rom.zip
for example (you put the ROM zip here you can drag and drop it)
Wait for that to finish it will go to 47% and on the phone it will show step 1/2 then step 2/2
and when it's done it's gonna show an error
adb: failed to read command: No error
Then you can reboot to system
Hello thank your for the short HowTo. Unfortunately im stuck on invalid sparse error. Could you pls post a fix to solve this? Would appreciate your help.
hardshell said:
Hello thank your for the short HowTo. Unfortunately im stuck on invalid sparse error. Could you pls post a fix to solve this? Would appreciate your help.
Click to expand...
Click to collapse
You have to wait at least 30 sec after the error appear...
Are you sure you are on fastbootD???
tuto modified and completed to also root device with magisk and patch boot.img
when i restart into fastboot, it is frozen.
dy2592 said:
when i restart into fastboot, it is frozen.
Click to expand...
Click to collapse
normal, nothing happens on fastboot....when you flash, only thing is on your computer, not on screen..
cant seem to get this installed =(
rayman95 said:
8/
Code:
fastboot reboot fastboot
Click to expand...
Click to collapse
After I enter this, it just stays on waiting for any device.
Update: I was able to figure it out. My device had no drivers so I went search through updates on windows and installed a LeMobile Android driver os it shows up properly in device manager.
How does one install gapps?
dy2592 said:
After I enter this, it just stays on waiting for any device.
View attachment 5419437
Update: I was able to figure it out. My device had no drivers so I went search through updates on windows and installed a LeMobile Android driver os it shows up properly in device manager.
Click to expand...
Click to collapse
because you don't have xiaomi drivers installed...install xiaomi pc suite and you will have drivers installed...
duplicate
rayman95 said:
In step 14, I encountered the error "fastboot: error: ANDROID_PRODUCT_OUT not set" after executing the fastboot flash system command. what do I need to do?
Click to expand...
Click to collapse
Did you insert the img at the end?
Fastboot flash system LIRxxxxxxxxxxxx.img
you have to put your rom to adb folder and dont forget to add .img at the end
rayman95 said:
you have to put your rom to adb folder and dont forget to add .img at the end
Click to expand...
Click to collapse
1.img is your rom Is there anything else missing?
dy2592 said:
Did you insert the img at the end?
Fastboot flash system LIRxxxxxxxxxxxx.img
Click to expand...
Click to collapse
yaha your right thank you so much
rayman95 said:
you have to put your rom to adb folder and dont forget to add .img at the end
Click to expand...
Click to collapse
thank I solved my problem. Now I have another problem, how to install GAPPs
Patrick Star_ said:
thank I solved my problem. Now I have another problem, how to install GAPPs
Click to expand...
Click to collapse
run twrp, it's explain in 1st post or maybe try with magisk...I can install minimicroG nogoolag with it..
rayman95 said:
run twrp, it's explain in 1st post or maybe try with magisk...I can install minimicroG nogoolag with it..
Click to expand...
Click to collapse
I tried to use twrp to brush into GAPP, but the error is 70. How can I solve it? I don't know if there is a problem with my twrp. Can you send a tutorial on xiaomi11 Lite 5g installing twrp? Thank you very much
Patrick Star_ said:
I tried to use twrp to brush into GAPP, but the error is 70. How can I solve it? I don't know if there is a problem with my twrp. Can you send a tutorial on xiaomi11 Lite 5g installing twrp? Thank you very much
Click to expand...
Click to collapse
In case you want to flash twrp put the file to adb folder and type in fastboot
15/
Code:
fastboot boot twrp.img
And twrp link is in post 1..maybe you choose bad gapps variant