Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
akram0010 said:
Hi there everyone, i want to know, how can i take a backup of stock rom of my device.
Do i need to root my device before taking a backup? If not then is there any other way to take backup of Stock Rom (i.e boot.img etc) with the help of PC (here Ubuntu Linux in my case) via using ADB, Fastboot and not using custom recoveries like TWRP, Orange Fox, SHRP.
Also do i have to root my device before installing any custom recovery in it?
I am very sorry for any inconveniences, as i am a newbie please accept my apologies.
Click to expand...
Click to collapse
Assuming that the bootloader is unlocked.
aIecxs said:
as already mentioned in other thread one can't do anything on locked bootloader, therefore backup is impossible
https://forum.xda-developers.com/t/a-question-from-a-newbie.4407343
Click to expand...
Click to collapse
Sorry i forgot to mention, but still unlocking bootloader doesn't root device.
I think the question is still valid
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Is root needed
aIecxs said:
if your bootloader is unlocked just boot into TWRP and create backup, no root required
Code:
fastboot boot recovery.img
edit: or just download MIUI according to your current properties
Code:
adb shell getprop ro.build.fingerprint
the only other method would be MTK secure boot authentification exploit
https://github.com/francescotescari/XiaoMiToolV2
https://github.com/bkerler/mtkclient
https://forum.xda-developers.com/t/mod-dev-mediatek-mtk-auth-bypass-sla-daa-utility.4232377
Click to expand...
Click to collapse
Can you please tell me what is this recovery.img, and where would i get it (in Fastboot rom or recovery rom).
As i said earlier i am a newbie in this field and very much confused with these terms.
no root required click on the first link above and download TWRP for your device (TWRP-3.4.2.b_lancelot.zip)
I assume you are running windows?
extract zip file and place recovery.img on your PC in platform-tools directory. connect phone in fastboot mode, install android_winusb.inf "Android Bootloader Interface" drivers and from cmd.exe check fastboot devices
if you can see device serialno you are ready to boot TWRP from fastboot with above first command.
for linux just install android-tools-fastboot
As i am using Ubuntu i installed ADB, FASTBOOT using the APT :
Code:
sudo apt install android-tools-adb android-tools-fastboot
.
Therefore i don't have the platform-tools directory.
Also I am unable to quote reply, its showing error (Oops, we broke the Matrix, someone call Neo)
yes that's right. it doesn't matter which directory files are placed. that way you installed fastboot binary is already in PATH. linux is far more easier and doesn't require additional drivers. it might require additional udev rules to make fastboot work, but you can simply by-pass with sudo fastboot for now...
Related
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
Hello, I have a H-901 v-10 That I've successfully unlocked the bootloader and am ready to flash TWRP recovery but every time I try to open the file my computer wants to burn it to a cd/disc.
What am I doing wrong?
hank1948 said:
Hello, I have a H-901 v-10 That I've successfully unlocked the bootloader and am ready to flash TWRP recovery but every time I try to open the file my computer wants to burn it to a cd/disc.
What am I doing wrong?
Click to expand...
Click to collapse
Stop trying to OPEN the image file. You should be on a command line using the fastboot flash command to flash the .img file directly to the recovery partition. You need to do some more reading because it sounds to me like you haven't yet installed the android developers kit which contains the adb and fastboot commands you will need to communicate with your phone.
Start by doing what you should have tried first...a google search for "How do I install TWRP on my phone?"...the first result is https://www.howtogeek.com/240047/how-to-flash-twrp-recovery-on-your-android-phone/
I've setup adb and fastboot, opened the twrp folder and have opened a command prompt window by typing shift + right click and entered fastboot flashing recovery recovery image then it showed some code on the command prompt but it didn't flash the twrp what do I do
Hi,
this is a small tutorial to show you how to flash the recovery, also eRecovery, via command line / adb shell within Android.
Flashify and other apps never worked for me, so I used commands to flash it without the need of fastboot.
It's a small tutorial for those who never worked with commands like this.
Please notify me if something went wrong or if you found any other issues.
I wanted to make a small script but I stopped it because of the lack of available commands in Android.
DISCLAIMER:
Read this tutorial first.
Never flash custom recovery to eRecovery.
Never flash recoveries from different devices.
Don't try to flash other partitions with this commands if you don't want to risk a brick.
Requirements:
- Oreo / EMUI 8 installed, Nougat hast other partition names. Pie isn't supported by me until final release.
- working root access
- terminal emulator app (I recommend Termius, it's easy to use and has nice features, it's free to use)
> or a PC, and USB cable and working ADB, also USB Debugging enabled in developer settings
- recovery img files on your phone, I recommend it to put them into your user root /data/media/0/ (internal memory)
NOTE: All commands are case sensitive!
Now open your terminal app or open the adb shell.
Type following command to enable root access:
Code:
su
SuperSU will ask you for root access, grant it.
Following command is needed to figure out, which type of memory your phone has:
Code:
ls /dev/block/platform
There are two possible outputs:
If you've a device with the faster UFS memory, it's ff3b0000.ufs, if eMMC it's hi_mci.0.
From now I'll write MEMORY instead of ff3b0000.ufs or hi_mci.0.
For flashing the recovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/RECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/recovery_ramdisk_a
Example: dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk_a
The output should look like this:
Code:
65536+0 records in
65536+0 records out
33554432 bytes transferred in 0.247 secs (135847902 bytes/sec)
If not, check your command and file paths.
For flashin the eRecovery fire up following command:
Code:
dd if=/PATH/TO/YOUR/ERECOVERY.IMG of=/dev/block/platform/MEMORY/by-name/erecovery_ramdisk_a
Example: dd if=/data/media/0/ERECOVERY_RAMDI.IMG of=/dev/block/platform/ff3b0000.ufs/by-name/erecovery_ramdisk_a
IMPORTANT NOTE: DO NOT INSTALL TWRP IN THIS! Flash only stock eRecovery!
The dd command won't give you any progress output, so be a bit patient. It should be done in a few second, but don't close the terminal app or connection before you got any output.
Unix systems like Android will give an output if something went wrong, always.
I use this to flash new TWRP versions or to flash stock recovery before I update.
If you recently updated your phone, you still need to flash via fastboot, because you lost root during the update.
The dd commands also work with fastboot. Mostly you'll use "fastboot flash recovery_ramdisk", but if you need to flash eRecovery, you can use the dd command.
23. February 2019:
Pie should also work, but you have to remove the "_a" after the partition name.
Example:
dd if=/data/media/0/twrp_3.2.1.img of=/dev/block/platform/ff3b0000.ufs/by-name/recovery_ramdisk
Please report if it's working or not.
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
fr3ker said:
How to know the path to the recovery_ramdisk?? Is all devices the same?? I didn't get it right the 1st time .. it shows path is invalid
Sent from my VTR-L29 using Tapatalk
Click to expand...
Click to collapse
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Jannomag said:
Should be the same on every device. Remember, case sensitive and use _ and not -.
Maybe it's different on non UFS devices, which one do you have?
Are you able to post a screenshot of your command and output?
Click to expand...
Click to collapse
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
M1chiel said:
Maybe @fr3ker is not on Oreo? The recovery_ramdisk partition is only for Oreo. In Nougat it is just called recovery. I don't know how the Pie partitions are called.
Click to expand...
Click to collapse
Also my thought, I wanted to add this to the requirements when I created this post but apparently I forgot this. Now it's added as first point.
Hi.
I have a hard bricked p10. When I connect to laptop it's says USB SER. It doesn't not turn on I can't access recovery with power + vol. I can't get into fastboot. Anyway I can access fastboot to flash kernel and erecovery?
Jannomag said:
I use this to flash new TWRP versions or to flash stock recovery before I update.
Click to expand...
Click to collapse
Is it mandatory to flash stock recovery before update? Is it applies only to ota update or ff method?
Yes, FF or OTA are using stock recovery to flash the update. With TWRP it won't work.
Updated?
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Blümchen Blau said:
@ Jannomag:
Have you checked this for Pie meanwhile?
I currently have the problem, not being able to enter fastboot with:
Code:
sudo adb reboot bootloader
Additionally, there's something I do not understand. For the dd-command for flashing, why is the input-file (if=) the file in "/dev/block/platform/..." and the output on the sd-card? Wouldn't mean flashing an img to the device, that if= on the sd (or connected PC) and of= the path to the device (phone)?
Click to expand...
Click to collapse
WTF....Why didn't I notice this terrible mistake! Thank you for reading my post completely, you're 100% correct, I'll correct this directly after I submit this post.
Huawei did also a small change at naming the recovery partition, which I'll update, too.
I had also the problem that I wasn't able to boot into fastboot by command before I fried my phone - I couldn't figure out the reason for this.
Again, thank you!
Jannomag said:
Again, thank you!
Click to expand...
Click to collapse
Your'e welcome! I did update now, but didn't need your (correct ) way to fastboot, because the method described by borgerapper did the trick for me to get into fastboot and flash the needed original recovery.
Thanks anyway!
Download link: https://drive.google.com/file/d/1gLshzM9zYEvR0Cknl4eh6KI32nEZbL5O/view?usp=sharing
I tried backing up the userdata.img, but that kept filling up my device storage. It was going beyond 19GB in size. So I cancelled the operation.
Enjoy these files, they will be useful for ROM porting, system restore, or system downgrade.
Editing these files can lead to a brick or a non booting state. So be careful.
I pulled all of these files from my device's system partitions.
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
turtleletortue said:
What did you do to dump these? Did you use dd to dump them or any other method? I dumped a few partitions from my BNTV460 a while back, but I'm unsure if I did it properly, so I was curious of how you dumped it from your BNTV650.
Click to expand...
Click to collapse
I temp rooted the Nook. Then I pulled the firmware files with ADB.
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
I did make a TWRP for this device.
tgp1994 said:
I saw that global MediaTek root tool posted earlier, I was just going to dump the partitions myself. Thank you for posting these OP! Does anyone know if there's a TWRP image for our devices? There's one posted for a "Barnes & Nobel Nook Tablet", but I haven't a clue if it's for the BNTV650.
Click to expand...
Click to collapse
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
secretwolf98 said:
How to unlock the bootloader:
1) allow OEM unlocking in developer options in the device settings
2) download ADB onto your computer https://developer.android.com/studio/releases/platform-tools.html
3) cd to the directory in CMD
4) enter this command: adb reboot bootloader
5) once the device is in fastboot mode, do: fastboot oem unlock
How to flash the stock OEM recovery:
1) fastboot flash recovery STOCK_recovery.img
How to flash the tested buggy TWRP recovery:
1) fastboot flash recovery TESTED_recovery.img
How to flash the untested TWRP recovery:
1) fastboot flash recovery UNTESTED_recovery.img
How to reboot back into the OS:
1) fastboot reboot
Downloads:
- Stock: https://drive.google.com/file/d/1Z7AJH6fSbeOkLLWt2JVwsCKiwxt0vlYK/view?usp=sharing
- Tested: https://drive.google.com/file/d/1R4ph5Z5mofsac0Qd352H_BEEz9JS4wBA/view?usp=sharing
- Untested: https://drive.google.com/file/d/1zP81MuR5LLvdYuDvYQHPVCJlgCOUBPlt/view?usp=sharing
Click to expand...
Click to collapse
Oh, there are recoveries? Thanks! What's wrong with the buggy version?
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
secretwolf98 said:
I will try to update this thread soon with the latest software update. If I can remember how I pulled the system files.
Click to expand...
Click to collapse
Did B&N release a software update?
tgp1994 said:
Did B&N release a software update?
Click to expand...
Click to collapse
Yep. It is v1.0.21. With the build date of June 2020. And with the security patch of May 5, 2020.
so there is no twrp or custom rooted rom for this device?
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