Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog:
• Updated sources to latest
• Almost Everything working fine.
Only for MIUI 13 Android 11
Creator: @Aghora7
Download
Installation instructions
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
lurchiii said:
whats is with data encrypten? is it working or problems with: "cant decrypt fbev2 partition"?
Click to expand...
Click to collapse
I can't answer to this question, because it depends on you made any mistakes during the installation or not
Its support for A12 miui 13.0.4
Does it support A12 eea europe rom ?
xristos1925 said:
Does it support A12 eea europe rom ?
Click to expand...
Click to collapse
it supports a11
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
sanjibukai said:
It seems Poco M4 Pro is not supported by TWRP and OrangeFox and that this unofficial TWRP is only for Android 11..
In my case I rooted (with magisk) from the latest ROM with Android 12..
And then installed LineageOS (Android 13). Everything works fine..
But I want to have a custom recovery for installing e.g. Gapps...
How can I do that?
Or do I need to rollback to previous ROM, install this TWRP then root with magisk and then go and install Lineage OS (and in that case I will still have TWRP and rooted)?
Thanks for any details..
Click to expand...
Click to collapse
Once you have lineageos installed, you must to flash twrp via fastboot and then flash Gapps
1. Flash system ( when it's done, don't reboot phone, just flash twrp
2. If you already are on twrp flash your Google apps
3. When you're done with flashing gapps, restart phone to system (twrp will be gone after reboot)
4. You have installed Gapps
i don't know how to flash twrp permanently, if you want further informations about this recovery, then join fleur telegram development channel
BloxetPL said:
1. Flash system ( when it's done, don't reboot phone, just flash twrp
Click to expand...
Click to collapse
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
sanjibukai said:
Hello and thanks for the reply..
Currently when I'm installing LineageOS I do the following:
Code:
# SMINORI SCRIPT
fastboot flash system system.img
fastboot reboot fastboot
fastboot getvar is-userspace
fastboot erase system
fastboot delete-logical-partition product_a
fastboot flash system system.img
# <- here?
fastboot reboot recovery
Do you mean that after installing LineageOS above, I need to run:
Code:
fastboot flash boot twrp.img
fastboot boot twrp.img
# Booting in TWRP despite the error
adb sideload gapps_file.zip
And then just install Gapps using the TWRP GUI?
Click to expand...
Click to collapse
Remove "fastboot reboot recovery" from SMINORI tool and instead of this type "fastboot flash boot twrp.img
fastboot boot twrp.img"
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
globalfandemic said:
I currently have MIUI13 and Android 11.
Tried to install TWRP with the instructions given but my phone will keep on bootloop.
TWRP interface shows for a few seconds but it shuts down after.
Im looking everywhere for answers but couldnt find any
Click to expand...
Click to collapse
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
BloxetPL said:
I saw that your question on telegram, as they said do "fastboot reboot recovery" no "fastboot boot twrp.img"
Click to expand...
Click to collapse
Already tried, still same issue.
Tried using a couple new commands too with no result:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot_a twrp.img
fastboot flash boot_b twrp.img
fastboot reboot recovery
Also tried using only the commands you gave:
fastboot flash boot twrp.img
fastboot reboot recovery
Related
Hey everyone, I just flashed my Moto G5S with a custom ROM (8.1 Pixel Experience).
Everytime I start it, it just goes into TWRP recovery mode. If I hold the Power+Volume buttons, and then select "Start", then it will boot into the Android OS. But if I leave it alone, then it just boots into TWRP Recovery mode.
How do I resolve this? it sounds like the boot order is not correct... but I don't know how to fix this.
EDIT: I have tried running the commands below in TWRP Terminal. They did not help
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Thank you all so much.
Same problem
I'm having exactly the same problem.
I've tried every single thing I can think of so far, including reverting everything back to stock.
Even when I revert the recovery img back to stock, it still tries to boot into recovery and just has a screen with the android logo and one word: "error".
I think that we need the moto G5 plus equivalent of "blank flash". EDIT: I'm not allowed to post links, so replace DOT with . here: cloudDOTEvache-androidDOTcom/Moto/potter/blankflash/
I'll try flashing this and see if it works.
Solved!!
I was finally able to solved this with the following steps:
Download the latest stock rom and firmware. There are lots of links around (sorry, I still can't post links). I used the Feb 2018 version.
Extract the zip file to the same places as fastboot. Boot into the bootloader.
1: Check your device is connected in fastboot mode
Code:
fastboot devices
If your device is listed then proceed.
2. flash bootloader
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
This might be enough - I didn't test it but you could try booting back into twrp and reinstalling your custom ROM here.
2. flash stock ROM ( and everything else)
I got a couple of error messages about signing with bad keys here, just ignore them.
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
4: Optional: relock bootloader
Code:
fastboot oem lock
5: Reboot and rejoice! (hopefully)
Code:
fastboot reboot
6: Reflash TWRP and then sideload Magisk for root
Reboot back into bootloader.
Download lastest TWRP for Moto G5S plus. Mine is called twrp-sanders-r16.im
g:
Code:
fastboot flash recovery twrp-sanders-r16.img
Get the latest Magisk from their website. Mine is v16.0.
In TWRP go to advanced -> sideload. Then:
Code:
adb sideload Magisk-v16.0.zip[CODE]
And you are done! Good luck :D
Thank you. I will give this a shot when I have a moment. At least I can still use my phone and it's not a brick. I'll come back with an update!
Success!
The previous suggestion worked... thank you so much!
I don't want erase my user data... I'm good with pixel experience rom.. no major bugs.
Help with twrp bootloop.. I use twrp r20 for Sanders unofficial
Hi,
I got the same issue. Can load fine with Start from Bootloader, but after next Restart, it's stuck on TWRP bootloop again.
I installed Pixel Experience, TWRP 3.2.1 r20 and Magisk 17.1
I used fastboot to load each file as you suggested, but still don't work.
Any idea where it might be wrong?
Thanks!
Fix bootloop in twrp MOTO G5 PLUS, works too in G5 s Plus
kevinm2738 said:
Hey everyone, I just flashed my Moto G5S with a custom ROM (8.1 Pixel Experience).
Everytime I start it, it just goes into TWRP recovery mode. If I hold the Power+Volume buttons, and then select "Start", then it will boot into the Android OS. But if I leave it alone, then it just boots into TWRP Recovery mode.
How do I resolve this? it sounds like the boot order is not correct... but I don't know how to fix this.
EDIT: I have tried running the commands below in TWRP Terminal. They did not help
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/sdcard/fota-backup.img
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Thank you all so much.
Click to expand...
Click to collapse
Here the solution: search in youtube "Solucion al Reinicio en Twrp Moto G5 Plus y seguramente todos" i cant upload links because i am a newbbie.
Sorry bad english.
---------- Post added at 12:41 AM ---------- Previous post was at 12:11 AM ----------
stevenhw8 said:
Hi,
I got the same issue. Can load fine with Start from Bootloader, but after next Restart, it's stuck on TWRP bootloop again.
I installed Pixel Experience, TWRP 3.2.1 r20 and Magisk 17.1
I used fastboot to load each file as you suggested, but still don't work.
Any idea where it might be wrong?
Thanks!
Click to expand...
Click to collapse
Here the solution: search in youtube "Solucion al Reinicio en Twrp Moto G5 Plus y seguramente todos" i cant upload links because i am a newbbie.
Sorry bad english.
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Reserved
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
buschris said:
is there a reason why this phone won't flash TWRP or ROMS directly from TWRP?
Click to expand...
Click to collapse
It actually does that
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems. Normally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Skippy12359 said:
Question on which partitions to backup in twrp. I'm on stock pie Moto g6 xt1925-6 and want to be able to flash back to it with no problems.lNormally I would backup boot, data, system. If I want to try out a gsi however it's is a system image and that's not normally backed up in twrp. I guess I'm asking which partitions should I backup that allows moving between gsi images, stock rom and custom roms.? Thanks
Click to expand...
Click to collapse
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
madbat99 said:
System.img is just the format the ROM (GSI) comes in. A regular system backup will restore just fine. The only difference is you can flash and backup system as an image if you want with TWRP now (boot and recovery too).
Data backups only work if you unencrypted your data. So restoring stock without root isn't possible (because of DM verity and forced encryption).
But restoring system and boot should work either way between GSI's. But unencrypted GSI backups of system and data should restore either way. You can make the backups as images if you want.
Click to expand...
Click to collapse
Really great feedback madbat99 and very much appreciated. Cheers
Nice to see, especially since Best Buy is running a sale on the G6 Unlocked (all of $150USD) - their cheapest Universal Unlocked handset during the current sale; at this price, even cheapskates like my Mom and her fiance could bite. (Further, at this price, we could even buy three - and I could run Lineage OS again - since Tracfone does not care if I don't run stock.)
the roms never start on my moto g6 . except the descendant.
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
What other roms did you try?
tiagoneo said:
the roms never start on my moto g6 . except the descendant.
Click to expand...
Click to collapse
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase
fastboot oem fb_mode_clear
fastboot reboot
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
yurais said:
am having this issue with stock pie.
I run the flashing commands, some gives few errors as Key siganuteres or something. and finally doesnt boot.
I use same commands but with Oreo Stock Rom and phone starts working.
here is code I used
I ask to myself If I will take same luck with the custom roms.
maybe am a bit offtopic...
Click to expand...
Click to collapse
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Thanks, didnt know the important stuff was inside the XML, will check...
Enviado desde mi SM-G930F mediante Tapatalk
---------- Post added at 10:02 AM ---------- Previous post was at 09:33 AM ----------
madbat99 said:
You can't use the exact same commands. Open the XML file in the zip and see what the flash commands are
Click to expand...
Click to collapse
Ok. I checked the xml, compared with bat file and there were significant changes.
Vendor partition was not beeing flashed
There was no erase ddr command
And the order of commands is slightly different.
I CORRECTED, flashed, again saw the strange warning or error while flashing recovery and boot which read: Image signed with key bad key
But system booted this time... even though digitizer still doesnt work, my main purpose of uograding, as it stopped working when I flashed the previous running oreo version...another story, offtopic here
Thanks
Enviado desde mi SM-G930F mediante Tapatalk
I had tested the RR, AEX, HAVOC OS, LINEAGE. now it only starts if I install the stock from scratch, and put the gsi system image. but does not pick up with gapps
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
dmilz said:
CRN-TWRP 3.2.1
Download here,
https://mega.nz/#!9gV0RQ7C!tcxUtoJisxdQbGWh62Te69TnKYXlUXv-L1p8_kknxS4\
!!unlocked bootloader
Yes, it does support GSI roms.\
Tested PIE roms. (not tested oreo)
- AEX
-Descendant
-RR
-Viper
-Lineage
To flash
1 Reboot to bootloader mode (volume down + power button)
2 fastboot flash recovery "recovery name plus extension or just drag recovery on cmd) then hit enter
3. Reboot to recovery
4 Profit:good:
Bugs
-Decryption password fails
Want to disable dm verity and force encryption?
Follow link
1 Format data
2. Reboot to recovery
3 Flash force encryption disabler
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
++Base recovery, Lenovo A6000
Click to expand...
Click to collapse
qual é a chave de decodificação?
UPHtx said:
qual é a chave de decodificação?
Click to expand...
Click to collapse
[TWRP][UNOFFICIAL] TWRP [64 Bit][3.7.0]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
# I assume you are confident with ADB and Fastboot commands and you know what you are doing. #
# If you don't, search on Google before messing with your device. #
# I am not responsible for...you know what I mean. On the other hand, please feel free to point out any error in this guide. #
# Lots of useful information can be found on Telegram Group for Mi 9 SE #
# If you already unlocked your bootloader and flashed TWRP, go directly to part 2 of this guide #
PART 1 - UNLOCK DEVICE AND FLASH TWRP
# Before starting, be sure that you can unlock your bootloader and you have these files: #
- Mi Unlock tool (http://en.miui.com/unlock/)
- Minimal ADB & Fastboot 1.4.3 (https://forum.xda-developers.com/showthread.php?t=2317790)
- TWRP recovery for your device (please check the development section).
Install ADB and Fastboot drivers on your PC, if you don't have them already.
- enable developer options on device, allow OEM unlock and ADB debug.
- install Minimal ADB & Fastboot tool and run a command window. PLEASE DON'T USE WINDOWS 10 POWER SHELL. Double click on "cmdhere.dll" in root folder instead.
- move twrp image in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename twrp file as "twrp" only.
- connect your device to your PC USB port, pair it with PC then reboot it to bootloader (power + volume down combo).
Unlock bootloader using Mi Unlock tool (full unlocking guide at https://c.mi.com/thread-1635834-1-1.html)
Unlocking bootloader will erase all of your data, including storage.
Once you unlocked:
- reboot and setup device
- enable developer options again
- double check bootloader status and allow ADB debug
- connect to USB port and pair device with PC for ADB debug bridge then type in command window:
Code:
adb devices
Code:
adb reboot bootloader
once in bootloader screen code:
Code:
fastboot devices
Code:
fastboot flash recovery twrp.img
- don't give fastboot command "fastboot boot recovery twrp" or "fastboot reboot recovery twrp". Just press and hold power+volume up for about 10 seconds to reboot to recovery.
- swipe to allow twrp modifications.
- I would suggest to NOT format data to get rid of encryption unless you actually need it. Encryption does not slow down your device or harm your battery life.
- I would also suggest to NOT wipe system and reboot to recovery because it could lead to a fastboot bootloop.
PART 2 - HOW TO FLASH A GSI ROM
# IMPORTANT #
When flashing a GSI ROM, it is recommended to use a Stable firmware as base.
If device is running different builds, flash latest Global or China Stable before starting using MiFlash tool.
Beware that device could have the anti-rollback enabled, so be careful when flashing another firmware.
Mi 9 SE is a system-as-root device, so you must flash A/B type GSI ROMs.
You will need these files:
- GSI A/B ROM (FlokoROM at https://treble.andro.plus/ or choose one at https://forum.xda-developers.com/project-treble/trebleenabled-device-development)
- vbmeta.img (https://androidfilehost.com/?fid=818070582850505317)
- gapps for Google services (https://opengapps.org/) - select ARM64 - 9.0 - I would suggest nano or pico package.
- magisk for root and modules (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445)
- MiFlash flashable STABLE stock firmware (http://en.miui.com/download or https://mirom.ezbox.idv.tw/en/phone/grus/)
- MiFlash tool (https://www.xiaomiflash.com/)
If you are already running a Stable firmware start from here, if you don't, flash a Stable firmware.
- move GSI and vbmeta images in the same folder where Minimal ADB & Fastboot is installed.
- for your convenience, rename GSI file as "system" only.
- reboot device to bootloader, ensure you are connected with your PC properly
- to double check it, run a command window and type:
Code:
fastboot devices
once you get the device recognized type:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
this command will disable dm-verity and AVB on device. PLEASE DON'T USE WINDOWS 10 POWER SHELL to disable vbmeta or you will get an error feedback. Double click on "cmdhere.dll" in root folder instead.
then:
Code:
fastboot flash system system.img
this command will flash system.img
Code:
fastboot -w
this command will wipe data on device
Reboot your device in recovery using button combo and resize system partition to install Gapps.
From TWRP Wipe menu > advanced wipe > system > repair or change file system > resize system > swipe to resize
- move magisk and gapps from PC to device
- go to mount menu and tick mount system
- go back to install menu and flash gapps
- once you flashed gapps unmount system
- go to install and flash magisk
- go to wipe menu and swipe for factory reset
- reboot
once rebooted, complete the device setup.
be aware that some GSI could bootloop or not boot at all even if you followed the guide properly.
in case rely on GSI devs for assistance or fixes.
Of course you can flash a GSI ROM using TWRP.
The only fastboot command you need to perform is to disable dm-verity and AVB.
If you already disabled it while flashing TWRP for the first time, you can follow these steps to flash a GSI using TWRP:
- Tap on advanced Wipe menu and wipe cache, dalvik, data and system
- Tap on Install > Install Image > select image and flash it to system
- Install Gapps with the same process shown above.
- Swipe for factory reset and reboot.
-----------------------------------------------------------------------------------------------------------------------------------------------
If updating GSIs builds from the same branch (e.g. Floko 060219 to Floko 060919) you are not required to wipe data. You can update flashing system.img on TWRP and Gapps time by time.
If you are moving from unofficial builds to official, or if you are moving between branches (e.g. Floko to Havoc), you need to wipe data as well.
@pengus77 provided for a very useful Magisk Module that will fix adaptive brightness, battery stats and in-call BT. You will find it here: https://forum.xda-developers.com/showpost.php?p=79762257&postcount=242
If you flashed a GSI ROM, you are basically using a system.img flashed on top of your stock firmware so, unless you performed modifications to vendor or boot partition, you can revert to stock using fastboot or TWRP.
You need to extract system.img (and boot and vendor, if needed) from the stock firmware.
You will need the vbmeta file as well to re-enable AVB and dm-verity otherwise the device will reboot in fastboot mode only.
Beware: you must flash EXACTLY the same system.img of the firmware you were running before flashing a GSI
Once you have both files, you can follow these steps to go back to stock using fastboot:
- place the files on Minimal ADB & Fastboot root folder
- reboot bootloader
- start a command window from Minimal ADB and type: fastboot devices
once your device has been recognized type the following commands:
- fastboot -w
- fastboot flash system system.img
- (optional) fastboot flash vendor vendor.img
- (optional) fastboot flash boot boot.img
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
You can also revert to stock using TWRP, by the way you will still need fastboot to flash vbmeta partition.
These are the steps to follow if you are using TWRP:
- place system.img on your device and vbmeta.img in Minimal ADB & Fastboot root folder.
- reboot to twrp and wipe dalvik, cache and data
- flash system.img to system partition
- (optional) flash vendor.img to vendor partition
- (optional) flash boot.img to boot partition
- reboot to bootloader
Start a command window in Minimal ADB & Fastboot, then type:
- fastboot devices
- fastboot flash vbmeta vbmeta.img
- fastboot reboot
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Moh3n.B said:
Thansk for your work.
Does TWRP backup work?For getting back to stock?
Click to expand...
Click to collapse
I hope it is helpful
Backup worked for me on the TWRP I mentioned above.
If you want revert to stock you can flash again stock firmware using MiTool (fastboot ROM) or twrp (Recovery ROM).
Good thread! Might be confusing if there's no guide to install TWRP and GSI ?
Great guide. It will help a lot of people to flash and test roms. And us by extension to find the best rom for our device !
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
scorpionredblack said:
Today I had some time and I tried to install the latest Havoc Gsi, unfortunately the result was negative, I ran the guide both from xda and from here, my basic rom was 10.2.3.0, arrived at the command fastboot -w performs the various wipes, but then it does not allow me to go into recovery, it always and only goes in fastboot, and the only way to make the smartphone work is to use miflash and put the official version back.
Click to expand...
Click to collapse
Try to flash vbmeta.
For me is not necesary.
Try like this from twrp:
- Wipe cache, dalvik cache, system, data
- Flash latest weekly eu firmware as base xiaomi.eu_multi_MI9SE_9.6.5_v10-9.zip
- Than flash havoc as system
Optional: flash magisk and custom kernel
Just stuck on bootloader unlocking.
Got this error "current account is not bound to this device"
I added device from mi unlock status too.
Moh3n.B said:
Just stuck on bootloader unlocking.
Click to expand...
Click to collapse
Search on Google. It looks like to be a common issue. If needed, follow the unlocking guide I linked on OP.
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Is there way to enable DC dimming (anti-pwm)?
I am using Havoc OS and my eyes are hurting..
sky104hk said:
successfully flash Foloko ROM to Mi9 se, run very well!
just a small queastion, is DT2W is not working in all GSI rom?
Anyone try it yet?
Click to expand...
Click to collapse
For now all gsi have same problem.
how to flash gapps ... i got error 70
raber111 said:
how to flash gapps ... i got error 70
Click to expand...
Click to collapse
Read carefully post n.2
Before I flash this, I world like to know from those already using this rom: How is the camera quality and finger print unlock response /speed?
I'm pissed at the frequent snow down of the miui system because I run vpn all day on my phone.
Sent from my Mi 9 SE using Tapatalk
krispuniq said:
Before I flash this...
Click to expand...
Click to collapse
Generally speaking, all the GSIs ROMs are based on Phhusson AOSP GSI ROM, so they have more or less the same performance and bugs.
At he moment FOD is not working well. You cannot unblock the device while on screen off or while on AOD.
For camera, you can install BSG Google Camera mod, that is working quite good.
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Vsider said:
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Click to expand...
Click to collapse
Flash the boot.img of your current firmware version in twrp to both slots and flash twrp installer.zip afterwards then reboot. Now you will be able to boot as normal and have twrp installed also
Vsider said:
Hello I'm stuck at fastboot loop with my Mi A3 after flashing TWRP
Here is what I did:
1. unlocked bootloader
2. downloaded TWRP from here: dl. twrp. me/ laurel_sprout/twrp-3.3.1-0-laurel_sprout.img.html (cant post links, sorry)
3. installed it with fastboot flash boot twrp-3.3.1-0-laurel_sprout.img
After that the reboot is always goes into fastboot
I found the advice to change the partition - it was B and I set it to A and it could load the stock recovery, so I tried to flash TWRP again and it went to Fastboot loop again, on both partitions. No I don't know what to do.
command 'fastboot devices' - shows the device.
but I cannot boot into recovery, I tried holding power and volume up buttons many times, it always boots into Fastboot (screen with bunny and robot)
Please help!
Click to expand...
Click to collapse
Don't use twrp
It'll break userdata partition
Use shrp recovery
For Android 9
https://sourceforge.net/projects/mi...RP_P-v2.2-laurel_sprout-official.img/download
For Android 10
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download
Shrp installer Flashable zip after flashing ROM
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Rajendran Rasa said:
Don't use twrp
It'll break userdata partition
Use shrp recovery
For Android 9
https://sourceforge.net/projects/mi...RP_P-v2.2-laurel_sprout-official.img/download
For Android 10
https://sourceforge.net/projects/mi...HR_Q-v2.2-laurel_sprout-official.img/download
Shrp installer Flashable zip after flashing ROM
https://sourceforge.net/projects/mi...ller-v2.2-laurel_sprout-official.zip/download
Click to expand...
Click to collapse
TWRP breaks down? ? Man!! Everyone using it.
All the youtubers.
There is a stable twrp for a3
Hi, I'm trying to flash OOS rom on my phone, Curtana. But I got an error when flash it.
The Terminal facing System: (REMOTE: Partition not found).
And I'm stuck at fastboot, can't not boot system or to recovery.
Thanks for your help.
nhokloz105 said:
Hi, I'm trying to flash OOS rom on my phone, Curtana. But I got an error when flash it.
The Terminal facing System: (REMOTE: Partition not found).
And I'm stuck at fastboot, can't not boot system or to recovery.
Thanks for your help.
Click to expand...
Click to collapse
OOS ?!?!? is there OxygenOS for curtana?
where did you get it?
can i have a link or adress please...
javidman said:
OOS ?!?!? is there OxygenOS for curtana?
where did you get it?
can i have a link or adress please...
Click to expand...
Click to collapse
You can get here https://t.me/curtanacloud/472
I have found a solution. I flashed stock rom via MiFlash to have fastbootd (not fastboot). Then reboot to Bootloader and type 'fastboot reboot fastboot' to boot to fastbootd. Then I can flash any system.img I want.
Another method, but I've try yet.
1. Unlock bootloader
2. Flash LOS recovery
3. Boot bootloader
In CMD
4. Enter: 'fastboot reboot fastboot'
5. Then you will see 'fastbootd', enter 'fastboot flash system system.img' (system.img = gsi img)
6. enter 'fastboot reboot recovery'
In recovery
7. go to factory reset
8. select format data/factory reset then format data
9. then select reboot system