TWRP / Encryption / Mount issue when trying to root [OP3T] - OnePlus 3T Questions & Answers

Hi All. Complete newbie to the forum here......in search of advice!
I've just got my new OnePlus 3T, so wanted to get it all set up and rooted before switching over from my Galaxy S5.
After reading several guides I followed the below steps:
Completed the OTA update to OOS 4.0.2
Unlocked the boot loader
Flashed TWRP 3.0.3
Booted into Recovery and TWRP asked for the encryption password (which was the same pattern I used in normal mode)
Internal memory was accessible so I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip. (I couldn't tell if they flashed successfully).
Rebooted
When the phone tries to reboot, I eventually get a screen saying 'Encryption Unsuccessful' and suggests I need to factory Reset.
When I select to reset, it boots back in to TWRP, but there is no request for the encryption pattern this time, and internal memory doesn't seem to mount. (showing as 0mb).
I'm wondering what my next step should be?
Should I try to flash the latest TWRP (3.0.4) via ADB?
Or would I be better off trying to flash back on stock recovery and the stock OOS 4.02 rom, and then wait for a newer TWRP before trying to get root access again?
.......Or will none of the above work?!
All I was really looking to do was root the phone. I'm not planning on changing from the stock OOS rom. I also don't mind if its encrypted or not encrypted.
I have had a look through some of the threads, but cant find examples of this scenario. Any help appreciated!

Which SuperSU file did you flashed?

The-Wexican said:
I proceeded to flash no-verity-opt-encrypt zip and SuperSu.zip.
Click to expand...
Click to collapse
I hope you didn't flash in that exact order. That could possibly be the reason for your issue. Also, you don't need the verity zip if you're flashing SuperSU.

Thanks for the feedback. Below is a link to the guide I followed on the Oneplus forums:
[GUIDE] OnePlus 3T: How to Unlock Bootloader | Flash TWRP | Root | Nandroid & EFS Backup and More !! (It wont let me link the thread as I'm a new user, but Google will show it!
That suggested to flash them in that order, I think.
SuperSU-v2.79-201612051815.zip was the SuperSU I used.

All, just to add, I don't need to recover any data or anything like that. I'm just looking for the best way to get out of this bot loop (of sorts).
I'm kinda thinking that because TWRP Recoveryseems to load OK, I could maybe flash back on the stock recovery and then side load the stock rom?
Any thoughts?
Or is it worth a shot at updating to the latest TWRP first (3.0.4)?

Below is the message I see when I try to boot the phone normally now (not in recovery)........
{
"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"
}

The-Wexican said:
Below is the message I see when I try to boot the phone normally now (not in recovery)........
Click to expand...
Click to collapse
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success

stephlal said:
I did what you did 2 days ago with success.
I recommend you flash back to stock and do the following:
-New devices boot
-Received OTA 7.0, 4.0.2 OOS
-fastboot oem unlock routine
-Flashed TWRP 3.0.4-0 - follow every step of: https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391 - read this 5 times, step 11 only requires you pick A) OR B), do not flash both
-Flash UPDATE-SuperSU-v2.79-20161211114519.zip (if you picked Step 11 A), that's what I did).
-Reboot
-Success
Click to expand...
Click to collapse
Awesome!
That worked. Thanks for your help!
Now running OP3T with OOS 4.0.2, TWRP recovery, rooted with SuperSU, and I even cleared the DM-Verity nag screen by booting into bootloader and running:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Very happy now!

Related

[ROM] Oxygen OS 3.2.5 untouched system.img + boot.img (twrp + fastboot)

If someone wants to make mirrors or a flashable zip, feel free to contact me and I will update thread
I've got my new OP3 today and what I've noticed that it runs with Oxygen OS 3.2.5. So I have looked around and saw that nobody backed up their 3.2.5 und uploaded it so I decided to do it.
Here is the download link: https://mega.nz/#!PJhzRDyL!wX12zmq9ptiu8gNbtfQfypB2Q6wGdu3IfNFFwi9acQk
The only requirement is an unlocked bootloader as fastboot doesn't allow to flash on locked devices
How to install:
via twrp:
- boot into twrp recovery
- press "install"
- press "install image" on the bottom right
- select the image and confirm on which partition it should flash
(not recommended) via fastboot:
- boot into fastboot
- use these commands to flash it:
ignore the little warning message and pe patient because it can take a while till you get a response from cmd because fastboot splits the image into 6 parts
Code:
fastboot flash boot boot.img
fastboot flash system system.img
Note: if your phone isn't booting, flash supersu and it should boot.
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"
}
Fastboot flashing is not working.
Can you comment on the LTE reception and performance? It was the only issue i had with 3.2.4
Anyone tried looks tempting
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
TWRP is working, fastboot not.
Im on 3.2.5 now so yes its working, but only with TWRP
*Extracted fine with newest winrar*
Error on my end, sorry, thank you!
Chronzy said:
@hellcat50 zip is corrupt, "unexpected end of archive" when I tried to extract the img's. Downloaded it twice. Don't recommend wiping and trying to install at this time.
Would love to have this though, would you mind repacking?
---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------
you were able to extract the imgs? I downloaded it twice and got corrupt zip both times.
Click to expand...
Click to collapse
It did extract without any issues on my end.
I downloaded and extracted the file on my PC with the latest winrar.
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
So, I will not lose my data, right?
No, but you should still do a backup in TWRP.
AcmE85 said:
No, but you should still do a backup in TWRP.
Click to expand...
Click to collapse
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Andrea224 said:
Sorry, but I haven't installed TWRP. I'm completely on stock (system and recovery)
Click to expand...
Click to collapse
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
AcmE85 said:
Then there is probably no way to install this to your device, as a user already said that using fastboot does not work.
I also think that your bootloader should be unlocked for this to work.
Click to expand...
Click to collapse
Mmh...ok, thanks anyway.
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Reconfigured said:
So basically you should have unlocked bootloader, supersued, and TWRP'ed
Click to expand...
Click to collapse
SuperSU is not needed, why should it be? With this you overwrite the whole System partition, thus removing all mods including SuperSU and Xposed.
waiting for someone to confirm the LTE issue resolution.. if it's resolved, I'll flash this ASAP..
AcmE85 said:
EDIT:
Worked as described in the first post.
I flashed both files, followed by the latest SuperSU 2.78 and Xposed,
then did a reboot.
All works well!
Click to expand...
Click to collapse
Pick your brain for a moment if you don't mind...
Still having issues with both methods... in TWRP, at the install image screen i'm only getting boot and recovery partition options, supposed to have system too right?
Fastboot it hangs for a moment at an error of something about invalid sparsing but continues to flash, apparently successfully, but when i reboot system it just boots back to recovery.
Chronzy said:
Pick your brain for a moment if you don't mind...
Click to expand...
Click to collapse
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
Can we directly flash it over 3.2.4 in twrp ?
Any differences with the previous version guys?3.2.4....Tnx!!
AcmE85 said:
I am using this recovery
http://forum.xda-developers.com/oneplus-3/development/recovery-twrp-3-0-2-0-touch-recovery-t3402999
After switching to image install, I simply picked the system.img and was able to pick between system, boot and recovery.
Repeated for boot.img as boot...
Click to expand...
Click to collapse
I was on an older recovery, should have known... that did it, Thanks! :good:

Mi 9 unlocked flashed TWRP can't copy ROM

Hi all!
I bougth my Mi 9 in China. Have it unlocked. Flashed general TWRP 3.3.0 cepheus from miui.eu link.
When I boot in recovery and go to sdcard I don't see my regular file folder structure anymore. There are folders with numbers and letters only. Is it encrypted now?!
Then when I was tinkering with new TWRP, the phone just got stuck in the loop. It boots in loop to recovery. I can access fastboot
But I cannot copy files thru recovery when data is mounted. Neither uploading ROM works with adb.
What can I do now?
I din't wipe anything. Just reflashed the TWRP and it got stuck in loop and loads recovery.
Cheshire_Puss said:
Hi all!
I bougth my Mi 9 in China. Have it unlocked. Flashed general TWRP 3.3.0 cepheus from miui.eu link.
When I boot in recovery and go to sdcard I don't see my regular file folder structure anymore. There are folders with numbers and letters only. Is it encrypted now?!
Then when I was tinkering with new TWRP, the phone just got stuck in the loop. It boots in loop to recovery. I can access fastboot
But I cannot copy files thru recovery when data is mounted. Neither uploading ROM works with adb.
What can I do now?
I din't wipe anything. Just reflashed the TWRP and it got stuck in loop and loads recovery.
Click to expand...
Click to collapse
You can try format data and reboot to recovery and try once more to copy files
P.S Sorry for my bad english
P.S.S i am using twrp by manuforio
Cheshire_Puss said:
Hi all!
I bougth my Mi 9 in China. Have it unlocked. Flashed general TWRP 3.3.0 cepheus from miui.eu link.
When I boot in recovery and go to sdcard I don't see my regular file folder structure anymore. There are folders with numbers and letters only. Is it encrypted now?!
Then when I was tinkering with new TWRP, the phone just got stuck in the loop. It boots in loop to recovery. I can access fastboot
But I cannot copy files thru recovery when data is mounted. Neither uploading ROM works with adb.
What can I do now?
I din't wipe anything. Just reflashed the TWRP and it got stuck in loop and loads recovery.
Click to expand...
Click to collapse
I had the same pain in the butt
You are facing two issues:
1. You must have the correct TWRP
2. You must follow the correct steps
See my post here:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79905261#post79905261
I am curently on RevolutionOS for MIUI.
I like it because it keeps the Fingerprint Reader and the AI Button working.
Also all the nice features of MIUI are retained but it adds more useful features.
Feel free to ask me for help if you have further trouble or if you run into problems with the GPS - I have a fix for that.
You can possibly use these instructions, but I have not testet them:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79924068#post79924068
In case you "soft-brick" it, use the MIUI Flash Tool: https://www.xiaomiflash.com/
But then you need to download and extract a rom that has a ".tgz" ending from here: http://en.miui.com/a-234.html
Let me know how it goes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I formatted the data partition. Also wiped delvic cache. And phone reboots into Mi-Recovery 3.0. What the heck?! No sign of TWRP left! Then I choose to reboot and it installs me new ROM. I am very puzzled with Xiaomi. Never been so hard before. Anyone can suggest? How to wipe and install clean ROM? I can install TWRP again but when the phone reboots it automatically overwrites and uses Mi-Recovery...
ChingghisKhan said:
I had the same pain in the butt
You are facing two issues:
1. You must have the correct TWRP
2. You must follow the correct steps
See my post here:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79905261#post79905261
I am curently on RevolutionOS for MIUI.
I like it because it keeps the Fingerprint Reader and the AI Button working.
Also all the nice features of MIUI are retained but it adds more useful features.
Feel free to ask me for help if you have further trouble or if you run into problems with the GPS - I have a fix for that.
You can possibly use these instructions, but I have not testet them:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79924068#post79924068
In case you "soft-brick" it, use the MIUI Flash Tool: https://www.xiaomiflash.com/
But then you need to download and extract a rom that has a ".tgz" ending from here: http://en.miui.com/a-234.html
Let me know how it goes
Click to expand...
Click to collapse
Okay, let me try. Come back to you.
ChingghisKhan said:
I had the same pain in the butt
You are facing two issues:
1. You must have the correct TWRP
2. You must follow the correct steps
See my post here:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79905261#post79905261
I am curently on RevolutionOS for MIUI.
I like it because it keeps the Fingerprint Reader and the AI Button working.
Also all the nice features of MIUI are retained but it adds more useful features.
Feel free to ask me for help if you have further trouble or if you run into problems with the GPS - I have a fix for that.
You can possibly use these instructions, but I have not testet them:
https://forum.xda-developers.com/Mi...iaomi-mi-9-t3905825/post79924068#post79924068
In case you "soft-brick" it, use the MIUI Flash Tool: https://www.xiaomiflash.com/
But then you need to download and extract a rom that has a ".tgz" ending from here: http://en.miui.com/a-234.html
Let me know how it goes
Click to expand...
Click to collapse
Hi!
Thanks a lot for the advice. I reinstalled unoficial TWRP. Cleared cache and internal memeory. ANd flashed the system from the MIUI eu. So far it works.
Appreciate!

Bricked Huawei P smart 2018 FIG-LX1 stuck in ERROR MODE

EDIT: I could fix this, if you have a device that works with HuRUpdater just download an update.zip, put that and the HuRUpdater zip in a new folder and it updates the recovery through TWRP so that's how I fixed it.
So I'm stuck in ERROR MODE. The only mode that works for me is Fastboot. I tried to reinstall recovery_ramdisk, system, cust and userdata but still in the same error. Before the brick EMUI 9.1 was installed. I've tried to install LineageOS 16 on my phone with TWRP, but I got error 7. First I've restored the nanddroid backup and I went stuck at a bootloop. I've entered eRecovery and downloaded the lastest version available on server and got this error. Any solutions for it? And the bootloader is unlocked, same with FRP. The error that shows in the screen
{
"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"
}
is Func. NO: 11 (recovery image) and Error NO: 2 (load failed). Would be appreciated if someone answers.
Here is how Fastboot looks like...
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Another_Alchemist said:
I've had a similar situation which I got out of using advice from this forum. Basically, I erased data from fastboot, flashed the stock 9.1 recovery (which I found a link for in one of the P Smart ROM threads) and lineage boot.img.
I MAY also have powered on with BOTH volume keys pressed.
You do have fastboot access, so I'd guess you will eventually be able to recover via the stock recovery.
Click to expand...
Click to collapse
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
LucastheBowser said:
Thanks for the help but forget this, I could fix it, I'm gonna modify the thread to inform that I could solve it. I finally could access twrp via the 3 button update method and used HuRUpdater to update the recovery and could fix the phone with an EMUI 8 rom and recovery that I flashed with HuRUpdater. Also, I could install LineageOS without ERROR 7 by modifying a text file in the ROM zip. Thanks anyway.
Click to expand...
Click to collapse
Hello! It seems Im having a same problem, since this device is somewhat discontinued by huawei, I cannot update it to any version, and cannot downgrade it either, using the "classic" sdcard method. Could you tell me how you used HuRupdater to flash the rom on yours?
The Solution for me->
Full package->
Software.rar
drive.google.com
Put your device on Testpoint mode:
Disconect the batery, join the point to gnd and conect usb cable on your pc.
and ..
and later you can update by SD

After update security pixel 4xl " your device corrupt"

{
"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"
}
Well, without more information about the actual error message... my suggestion would be to flash a full image from Google without the wipe command flag. (You remove the "-w" from the flash-all.bat)
You can try using the browser based flash tool if downloading platform tools/ADB is too much for you. It's supposedly easier, but I've never used it before. It also might wipe your device by default, so be careful?
MBenzKH said:
Help!
Click to expand...
Click to collapse
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.
v12xke said:
Being bootloader locked, about the only thing you can do is flash a FULL OTA IMAGE available from Google's website and flash it from recovery using ADB. This procedure has also been called a "rescue ota". You cannot flash a full image via fastboot (because you are locked) but you can flash the OTA from recovery. There are instructions on Google's download page. Just pick the newest OTA image available. The most important thing is to get adb/fastboot set up correctly on your PC. Always easier to learn when your phone is working properly, but still not that difficult to accomplish and verify proper installation. Start with the very latest (February 2021) adb/fastboot binaries. Drop those files (and the image) into a folder and add that folder to your path statement. ADB only works in recovery NOT in fastboot mode like your screenshot. If you have questions or need more info, PM me.
Click to expand...
Click to collapse
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?
jljtgr said:
I've not had a locked boot loader for longer than 7 days in the past decade, so my experience is poor... but I always thought that the locked bootloader would deny usage of foriegn images like a Magisk patched boot.img or something else. It's surprising to me that you would not be able to flash a full Google image directly with Fastboot. Am I wrong?
Click to expand...
Click to collapse
From the screenshot provided, OP's bootloader is locked, so he cannot fastboot flash ANYTHING. Within the stock recovery there is an option to flash a full OTA image via ADB from a laptop or PC. A recovery OTA is the only way forward in this case, and is dependent on whether he has a working recovery. I've seen this method save many bootloader locked phones. Hopefully OP will come back and let us know he was successful.

How To Guide Guide to Flash Miui_VILIGlobal_V13.0.1.0.SKDMIXM_e7e8f0ef90_12 and use Magisk

Hello All,
Quick and dirty guide.
Warning!
I'm not responsible for any damage to you, to your device or to your data. Do this at your OWN RISK! If you don't know what you are doing, STOP now!
Steps to flash the ROM using TWRP:
Be on Android 11 (MIUI 12.5) and flash TWRP. There is a guide here on how to do it, so i'm not posting that.
Obviously, you'll need unlocked bootloader so if it's not unlocked, your case is lost
Download the ROM in the title from here and copy it to your phone
Reboot to TWRP
If you want, i guess you can wipe data - i haven't done this
Flash the ROM like you would any other (install and select the zip you copied over from the above link)
At the end, it'll give you mounting error but it's all good, reboot
Wait for the ROM to settle if you wish - you can stop here
For Magisk, follow the below steps
Enable developer settings and USB debugging
Install the Magisk Manager app (latest version 24.1 at the time of writing this little guide)
Turn off the phone and boot it into fastboot mode
Start the fastboot app of your choice from your pc and connect your phone via USB (I'm using Minimal ADB and Fastboot, you can find it on XDA)
issue the following commands in the same order:
Code:
fastboot devices
if you don't get as a response a few digits of your device ID with the fastboot text next to it, you'll doing something wrong (driver might be or you are not in fastboot mode)
Code:
fastboot flash boot_a patched_boot.img
if the command completes you'll get a finished message
Code:
fastboot flash boot_b patched_boot.img
patched_boot.img is the full path of the patched boot.img file
Code:
fastboot reboot
wait for the device to boot.
Patched boot.img is attached but if you wish, you can extract it from the rom yourself using payload dumper and patch it on your phone with Magisk. The attached boot.img is patched with Magisk 24.1, this is what you'll need as well - this is the current version. You need to unzip the attached file of course!
Enjoy.
{
"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"
}
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Pichulec said:
Just flashed by TWRP and reset to the factory. So far there is no fastboot image, only recovery one, and normal way it is not possible to flash it as it is only for Mi Pilot people.
Click to expand...
Click to collapse
what do you mean with "no fastboot image"?
There are two types of images - recovery and fastboot.
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Yuditkiichi said:
Hello, im trying your guide but my phone stuck on fastboot mode and when im try to enter twrp, it stuck on frozen screen i cant swipe to unlock twrp....any idea?(
Click to expand...
Click to collapse
Hi, if TWRP worked before, it should as well now.
donjamal said:
Hi, if TWRP worked before, it should as well now.
Click to expand...
Click to collapse
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
I would probably relfash twrp as long as I'm still on 12.5.
Yesterday received OTA update for my 11t pro. I'm not in Pilot Programm..
Yuditkiichi said:
Any idea how to solved my twrp problem? Or should i reflash it with pc?
Click to expand...
Click to collapse
for now twrp not working for a12.
wait for update
All can download rom here https://xiaomifirmwareupdater.com/miui/vili/stable beta/V13.0.1.0.SKDMIXM/
and use updater to update it.. that dont need any mi pilot.. i just installing it.. yeeah!

Categories

Resources