TWRP 3.0.0-0 - Wileyfox Swift

Hi,
PLEASE VISIT THE CORRECT AND OFFICIAL THREAD HERE. THIS THREAD WILL NO LONGER BE UPDATED.
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
{
"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"
}
-Jev

Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?

jevtheboss said:
Hi,
As some of you may know, @beroid has a TWRP 3.0.0-0 which he released on his Unofficial CM13 thread. I was unaware of this but lukily (thanks to @yasteellutch) I was told about this new TWRP. So, if you are looking for it, or are unaware of it because you dont look through the original thread, well here it is and now you know!
Installing
Go the download link here and you will be presented with two files.
FOR CURRENT TWRP USERS:
Download the zip file and flash it within TWRP. Your device should reboot automaticly into the new TWRP.
FOR NEW USERS:
Download the img file and place it in your platform-tools folder on your pc. Then reboot your device in fastboot. Then, open a command window in that folder and run commands:
Code:
fastboot -i 0x2970 erase recovery
- IF YOU GET WAITING FOR (ANY) DEVICE SKIP TO NEXT PART
Then enter
Code:
fastboot -i 0x2970 flash recovery recovery.img
Disconnect the device from your computer. Then remove the battery. Then replace the battery and press VOLUME DOWN and POWER to rebbot in to recovery mode to verify the installation. IF YOU DONT, IT WONT WORK!
IF YOU GET WAITING FOR DEVICE:
Do the same commands but without the vendor id eg.
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
Credits to:
@beroid for making this. IT IS ALL @beroid's WORK!
So, now you know about TWRP 3.0.0-0!
SCREENSHOTS:
-Jev
Click to expand...
Click to collapse
Not sure if -i 0x2970 is needed for fastboot think its only for fastboot oem
No need for battery removal there is a fastboot command ........fastboot reboot......... that does the same thing

dnahc said:
Hello,
Thank you, I have used it since few weeks without problem. But your TWRP build doesn't seem to include encryption support. TWRP asks for the password but it can't decrypt data partition. Is there some kind of missing module or this is not officially support by TWRP 3 ?
Click to expand...
Click to collapse
Hi,
Please could you visit the thread here and ask the question there. I think TWRP 3.0.1 will fix the issue. :good: If not, on the TWRP website, 3.0.2 has been released which is supposed to fix some decryption issues so please wait for the thread (the one I linked to earlier) to be updated

Related

[GUIDE] How to flash " .IMG " files [HOW TO]

So,
I searched the forums for about an hour but i was not able to find a proper guide on how to flash .img files. Mostly, people have problems flashing recovery files.
This might be pretty easy but,...Still,it might help someone.
Here are some simple steps on how to flash .img files onto your Galaxy Nexus.
Let's Get Started
• First of all download this great toolkit by WugFresh from his website.
• Setup the toolkit by installing the Samsung drivers(you must have already installed them).
• Now enable USB debugging on your device by Setting>Developer Options>Android Debugging > [check enable].
• Download ClockworkMod Recovery from here.
• Now Click on Launch (Advance Utilities) at the bottom left corner on the toolkit.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
___________________________________________________________
• Now check ' Flash (Permanent) ' .
___________________________________________________________
• Click 'Recovery'
___________________________________________________________
• Now, Select the .img recovery file you've downloaded or you can search the file path given below(in the image) for recovery.img files included in the toolkit.
___________________________________________________________
• Select OK and then your'e Done !.
looks good.. here are the steps for mskips toolkit if you wanna add them
download .img file
place the .img file in mskips toolkits "put img file here to flash here" folder
boot gnex to fastboot mode and connect to pc
open mskips toolkit
choose model number
choose option 11 "boot or flash .img file to device"
at first look i thinked you write the steps for flash a .img..but in fastboot..not in a toolkit.i think that flash in a toolkit is so easy also for a total-noob..because they are made for that!instead of do this type of installation,i'd preferred to see the standard fastboot mode,to encourage people to do it manually ( 30 sec)
sometimes **** happens and with the use of toolkit it's more difficult trace problems,anyways that for the guide!
EDIT at this point,i think this is not bad
to flash a .img files from fastboot,download and do an md5 of the file,copy it in the fastboot folder and in a command terminal from windows after going to the directory of fastboot where you downloaded the file digit: (yours phone has to be in fastboot-mode and with usb-debug ON)
FOR A RECOVERY .img
fastboot flash name_of_file.img
FOR A BOOTLOADER .img
fastboot flash bootloader name_of_file.img
FOR A BOOT .img (kernel+ramdisk)
fastboot flash boot name_of_the_file.img
1.some in the fastboot directory have the file inside nomined fastboot-windows..if it's the case,you have to write always fastboot-windows instead of fastboot in commands..or you can rename it that's more quick.
2.when you have to do with a recovery,if you want to only trying that,you can instead of -fastboot flash- do -fastboot boot-..in this case the phone boots with that recovery but after a reset it reloads the previous
EDIT 2
you can add in yours poll the voice "i don't use toolkit".i think in the end will have lots of vote!
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+1 fastboot is a lot safer and easier.
Nice. I had my recovery installed via cwm by the way.
thegtfusion said:
Great, but learn how to do it via fastboot. Its safer and its impossible to brick your device if you know fastboot.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
this.
if you are going to teach people how to flash .img files, do it right, not through a root toolkit. oh, and in no way does this belong in development.
Guides like this are best in General or Themes
Please read rule 15 for a better description of what should be posted where
Thank you for your cooperation
Thread moved
FNM
lawl.
fastboot flash recovery nameofrecovery.img is so hard.
Jesus! What thread have I stepped into!
Beamed from my Grouper.
Zepius said:
lawl.
fastboot flash recovery nameofrecovery.img is so hard.
Click to expand...
Click to collapse
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery
adrynalyne said:
We had someone in IRC when the Gnex first came out flash recovery to the boot kernel.
For those confused,
fastboot flash boot recovery.img
The user couldn't figure out why it only booted to recovery
Click to expand...
Click to collapse
Lol!
Beamed from my Grouper.

Fastbooting android whose recovery is not opening.

While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
{
"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"
}
akshat2119 said:
While trying to root my redmi 1s, i accidentally pressed a wrong button due to which it seemed like if recovery is no longer functioning.
The mobile is getting struck at mi logo and is not proceeding forward.
Pressing volume down+power button successfully opens fastboot screen. Earlier when I was connecting it to mi suite on pc, i was able to flash. But due to incomplete charged battery, flashing procedure stopped. After the recent windows update, mi pc suite is recognizing the android but is not able to flash it. It pops out a dialogue box saying "cant flash the device". Any idea what can i do now?
Click to expand...
Click to collapse
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
vicky romero said:
If your phone boots into fastboot, then try installing twrp recovery and then flash the rom you wish.
Click to expand...
Click to collapse
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
akshat2119 said:
but how to flash twrp via fastboot. i.e. which software would recognize fastbooting android?
Click to expand...
Click to collapse
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Thank you
vicky romero said:
Flashing twrp is done by fastboot using adb tools. First install the USB drivers of your phone. You can simply google them. Then go to this link https://drive.google.com/open?id=0B_43Fi9T_yqvUy1jOWk0cnJyZEk
and download the four files in the adb folder. Now download the latest twrp image i.e, twrp 3.0.0-0 from this link
https://dl.twrp.me/armani/
keep the adb tools i.e, the four files you had downloaded and the twrp image in the same folder. Rename the twrp 3.0.0-0 to recovery.img. Now hold shift key and press right click on your mouse. From there select open command window here. Now open fastboot and connect your phone through Usb and type this code
Code:
fastboot devices
This is to check wheather your device is connected or not. If it's connected then it will show some code. After that type this code
Code:
fastboot flash recovery recovery.img
That's it twrp will be flashed right away. Then you can flash MIUI or any other custom rom.
Click to expand...
Click to collapse
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
akshat2119 said:
A big thank you. I owe you for helping out. By the way after installing recovery I tried downloading rom(both armani which was earlier working and miui official). The script gets sideloaded successfully but again the operating system is not loading. ie mobile is still struck in bootloader
Click to expand...
Click to collapse
Flash this firmware before installing the rom. It'll fix the bootloops.
https://www.androidfilehost.com/?fid=24052804347850305
Thanks @fefifofum for this flashable zip.

i need help to flash twrp recovery on RN5 pro

i just need to flash twrp recovery on my redmi note 5 last miui 11.0.3 android version is 9
i just follow the steps but i didnt flash to twrp recovery when i write the command in adb//
some peoples telling me that the last twrp img recovery contain password or something like this any one can help me
Unlock bootloader first
Re: @wickednight
TWRP is a custom recovery. Flash it need an unlocked bootloader.
If your bootloader is locked, go to https://en.miui.com/unlock/ to apply for unlocking permissions. Download Mi Unlock Tool and proceed to unlock. A waiting period and instruction will then be displayed in Mi Unlock Tool. Use your phone actively during the waiting period.
More information about unlocking: https://c.mi.com/thread-2262302-1-0.html
Once you successfully unlocked the bootloader, in theory, you can flash any file as you want. However, Xiaomi has enabled ANTI_ROLLBACK feature on the Redmi Note 5 (whyred). Check the anti level first so you can choose the right flashing method.
Install all drivers needed on your computer and connect your phone to PC. Hold POWER and VOLUME DOWN for about 11s to enter fastboot mode. Open a command prompt window in the adb tool folder, type this command to check the anti level of your phone:
fastboot getvar anti
Look for the number after "anti:" in output imformation in order to know about the anti level of your phone. The flashing steps is a little different for anti3 devices and anti4 devices.
If the anti level is 3 or lower, you can flash the twrp recovery img file using fastboot command directly. Make sure the twrp img file has been placed in the adb tool folder, and has been renamed to "twrp.img".Type this following command to flash twrp recovery easily:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
If the anti level is 4 or higher, the steps is more complicated. You must bypass the ARB first. Download the whyred-arbpass.img and flash it to antirbpass partition or the ARB will block all your flashing commands. All needed files I will put their links at the end of the post. Type this command to bypass the ARB for one time. You need to use the whyred-arbpass.img to bypass the ARB everytime you want to flash. Make sure the whyred-arbpass.img is placed in the adb tool folder.
Command to bypass ARB and allow you to flash the recovery:
fastboot flash antirbpass whyred-arbpass.img
Check the output, make sure "sending antirbpass" and "writing antirbpass" are all OK. Now you can flash the recovery like anti3's devices:
fastboot flash recovery twrp.img
Check the output, make sure "sending recovery" and "writing recovery" are all OK. Now the recovery on your phone is TWRP recovery. Hold POWER and VOLUME UP to force the phone reboot into twrp recovery.
All needed files:
1. TWRP recovery img files for whyred:
https://dl.twrp.me/whyred/
2. ANTI_ROLLBACK bypasser file (need to flash it to antirbpass partition):
https://drive.google.com/open?id=1cbHeULrh62R0COSD-RU9OwsWFR2zyfmc
MD5:
{
"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"
}
If you find it useful, please click thanks.

Question Booting GSI's

hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
stevendeb25 said:
hey been out of the android modding scene for quite a few years now, been playing around with some GSI's, all bootloop at bootanimation... (Stock/Kirisakura patched via magisk) boot to animation, non patched kernels bootloops at google screen, cant flash permissiver, any other tricks i can try? adb aint active neither in any kernel
Cheers
Click to expand...
Click to collapse
I really don't know much about GSI's, but don't you have to disable AVB before flashing one? Basically disabling vbmeta verification and verity (which would require a factory reset afterwards)? Not sure if you've done or tried this, so just throwing it out there.
{
"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"
}
Generic System Images (GSIs) | Platform | Android Developers
developer.android.com
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Morgrain said:
Some more information would be helpful. What did you do exactly? Best tell us every step, every file you used and when.
You say that ADB isn't active. Does that mean that you can neither boot into recovery/your PC does not recognize the phone/ you can't use fastboot? You say that your device bootloops, that means it boots up at least, so your bootloader is still intact/working?
These two websites here are your first go to in that case:
Google Pixel - Update and Software Repair
&
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
The bootloader has nothing to do with the bootanimation. If you see the bootanimation, the bootloader has done it's work ages before.
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Nothing data corrupted
Rebooted back to bootloader
Fastboot reboot recovery
Data reset
=Google logo
Fastboot reboot bootloader
Fastboot flash boot magisk_patched.img
Fastboot reboot
=Bootanimation
ADB ain't enabled in boot.imgs so can't pull logcats to try to see why no boot.
Tried lineage, octativeos, LeOS, phusson, same with all GSI's
P.s phone is intact and easily put back to stock
stevendeb25 said:
From stock
Fastboot reboot bootloader
Fastboot reboot fastboot
Fastboot erase system
Fastboot flash system gsi.img
Fastboot reboot
Click to expand...
Click to collapse
As @Lughnasadh said, it looks like you're missing the disabling of AVB by flashing Google's custom vbmeta.img before installing the GSI image.
Note: If your device has adopted Android Verified Boot (AVB), download and flash the following image to disable AVB before flashing a GSI: vbmeta.img
Click to expand...
Click to collapse
As above, see here: https://developer.android.com/topic/generic-system-image#flash-gsi (blue box).
hi thanks for that, flash vbmeta
still stuck on bootanimation.
i have tried a number of gsi's does this error matter when flashing gsi? "Invalid sparse file format at header magic" still installs fine

Question My phone has became brick(cannot enter the recovery mode), after installed boot.img

After 168 hours bought. I've unlocked my Xiaomi 11 lite 5G NE.
I follow the offical guide to install the latest Lineageos. https://wiki.lineageos.org/devices/lisa/install
here is my operations:
Enable devleoper mode and USB debugging on my device.
adb devices shows OK, it can list my device.
enter the fastboot mode, type `fastboot devices` shows ok, it can list my device.
I've download all files from this page: https://download.lineageos.org/devices/lisa/builds
lineage-19.1-20230325-nightly-lisa-signed.zip
boot.img
dtbo.img
super_empty.img
vbmeta.img
vendor_boot.img
then I enter the fastboot mode in my phone and connected to my computer(adb, fastboot, usb drivers was installed).
I follow the Lineageos instructions and type the following command.
fastboot flash dtbo <dtbo>.img //dtbo.img listed above
fastboot flash vendor_boot <vendor_boot>.img //vendor_boot.img listed above
fastboot flash boot <recovery_filename>.img //boot.img listed above
then the guide let me enter the recovery mode(hold power + volumn up), my phone shows this image:
{
"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"
}
It can not enter the recovery mode like the guide says.
Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?
newbie_or_not_newbie said:
Hello,
don't know if it could be a reason, but was official miui 13 or 14 (Android 12 or 13) ?
Click to expand...
Click to collapse
I don't know which version of miui installed in my phone. I didn't check my phone's default miui version. I've just brought this phone a week.
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
I think that's the really problem. I will recovery the offical miui and try again.
it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way
Trismo said:
it cold possibile a problem with usb driver or cable problems
i think you only flash dtbo.img , boot and vendor_boot did not get on the device
start you lisa device with fastboot (power + Vol down)
fastboot flash boot_ab .\path to boot.img all files in the same folder
Code:
PS C:\lisa\lineageos19\> .\fastboot.exe flash boot boot.img
press enter,
than connect the cable after its finish unplug the cable
an do it with dtbo and vender_boot the same way
Click to expand...
Click to collapse
It doesn't work. I've tried.
newbie_or_not_newbie said:
In lineage OS flash instructions, it says this :
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
Don't know if it can softbrick your phone if it's android 13.
Click to expand...
Click to collapse
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.
treelu said:
It doesn't work. I've tried.
No, I've tried to recovery Miui. And ensuring my Miui to equal android 12. It is still not work.
Click to expand...
Click to collapse
And Miui Start ?
Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased
Nillesse said:
Hi
Bro no worry
Flash the the latest xiaomi.eu rom for lisa
Via fastboot and it will boot normaly
Ps all data will be erased
Click to expand...
Click to collapse
Thanks. I am not worry. My phone can still work with Miui.

Categories

Resources