Order of things to be done - unlocking/flashing etc - Xiaomi Mi 5 Questions & Answers

I intend to create a post with how to do things on this phone.
Just bought the 64GB Black.
So, trying to pull the order of things to be done.
Please help, this is for newbies.
When you receive it. What should be done first? (and how did you do it???)
(EDIT : I will update this as I find things out.)
Bootloader
Follow the guide found here : http://xiaomitips.com/guide/unlock-mi-5-bootloader/
You should do this in advance of getting your phone.
Recovery - TWRP
Guide here : http://en.miui.com/thread-245756-1-1.html
Which ROM to install?
CM alternative?
Gapps?
If you own the Mi5, how did you go about it? Any tips? What went wrong? How did you fix?

First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.

regnarox said:
First I unlocked my bootloader, which is essential to do first. Then I flashed TWRP using the ADB terminal thing on my computer via USB. After I had TWRP, I rooted my phone using SuperSU. But I was bored of MIUI so I flashed Cyanogenmod 13 in the thread in the MI 5 ROM forum. I have not changed anything since then really, I'm using the root that comes with CM now. It's all really good.
Edit: make sure you flash google apps at the SAME TIME as cyanogenmod! Without booting in between! Also the snapchat camera doesn't work right now for CM but if you use the app casper.io (not on play store, google it) you can use the phones camera app and then it works fine.
Click to expand...
Click to collapse
Which TWRP did you use (link?)
Which GApps did you use? (Nano, pico, stock etc) and presumably ARM64?

since there isn't a sdcard, are you able to do a full backup so you can revert back to if you have second thoughts. I guess you have to do a full wipe prior to flashing e.g CM13

Questions about rooting
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks

TWRP - https://www.androidfilehost.com/?fid=24533103863138514 (no touch screen issue which is present in other recoveries)
GApps - http://opengapps.org/ (ARM64) I used microG instead of gapps to save a lot of battery. (You can google it if you want)
It doesn't really matter what GApps do you use, although I'd go for nano/pico. I wouldn't want all the GApps to be my system apps.
---------- Post added at 11:11 AM ---------- Previous post was at 11:02 AM ----------
Sachuan said:
Hey I got a Mi5 64GB with unlocked bt and twrp installed.
Now I want to root the device but when I boot to twrp I can't flash files because the device is encrypted by default and in order to decrypt it I need to perform a full wipe or enter a password, I don't know the password because it's not a password I decided on, I don't really have a problem doing a full wipe I don't have any important data.
But here are my questions:
1. If I'll do a full wipe will I have to install MiUi and twrp again?
2. Right now if I connect my phone to my PC using USB when it's in recovery mode I can't use MTP and if I'll perform a full wipe the SuperSU.zip will get deleted from my device and I will have to get it back to the device somehow and I can't because I can't use MTP when I'm in recovery mode. So I thought maybe after the full wipe I will be able to use MTP on recovery maybe I can't because it's encrypted at the moment?
Thanks
Click to expand...
Click to collapse
1. You just need to format data, your system partition will not be wiped. You will just lose everything except the system.
2. You probably will be able to use MTP, although I'm not but other people are so you should too. If you don't, you'll need to go to advanced in TWRP, enter adb sideload and sideload the zip.

[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)

Sachuan said:
[I deleted your quote becasue it said I can't post outside links]
Ok, thank you!
(I don't need to install twrp again right?)
Click to expand...
Click to collapse
No, you don't

proag said:
No, you don't
Click to expand...
Click to collapse
Good thanks!
Sent from my MI 5 using XDA-Developers mobile app

Related

TWRP 3.2.3-1 for Pixel Devices

TLDR: It's here and it may eat your data, and you will lose SuperSU root if currently installed. READ the install instructions carefully!
Pixel XL
Pixel
DO NOT RESTORE DATA FROM alpha builds of TWRP using RC1. You will probably lose all data including internal storage. If you need to restore a data backup from an alpha build, reinstall the alpha and restore using the alpha and make a new backup using RC1.
Note: Do not use if you have multiple users (including a guest user)
File Based Encryption (FBE) can be a bit tricky. If a restore doesn't work correctly, it can trigger an automatic wipe of your data. Sometimes TWRP will fail to prompt you to enter your password or otherwise fail to set up decrypt properly. If this happens, reboot TWRP. It seems to be some kind of timing issue and I haven't had time to track it down yet.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted with SuperSU, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, grab the very latest SuperSU released on 2015-11-15 or later and install SuperSU.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
NOTE about 3.2.1-0: This version will decrypt Android 8.1, however the new image is built in Android 8.1 and may not be compatible with SuperSU and/or Magisk until they update their stuff. I have not tested. Good luck.
3.2.1-1 has working decrypt with the February security patch!
3.2.1-2 fixes some zip install errors
3.2.3-1 supports decrypting Android 9.0 Pie even with a pin / pattern / password set
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Amazing work sir! I think this is what we've all been waiting for! I mean I know I've been checking here frequently, hoping for this
Wow and so it begins, great work thanks!
Thanks
Sent from my Pixel using XDA-Developers mobile app
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Dees_Troy said:
Note: I am going to be very busy the next couple of weeks. I probably won't be able to answer your questions or fix things immediately.
Click to expand...
Click to collapse
the pixel installer.zip is corrupt. :crying:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
GeekMcLeod said:
Really looking forward to having this and SuperSU working together. After that, I just need things to flash. Been going crazy not being able to appeasey crack flashing addiction.
Click to expand...
Click to collapse
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
zaksimmermon said:
Do you happen to have a copy of the .zip? All the ones I download are corrupt...
Click to expand...
Click to collapse
No I haven't downloaded anything yet. Not going to until I can have supersu alongside twrp.
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Snowby123 said:
Why does installation of this remove SuperSU?
Aren't they supposed to be used side-by-side?
And it also warns not to install if expecting important calls.
Does it prevent the phone apps from operating or what?
I understand everything else.
Click to expand...
Click to collapse
"In other words, Chainfire's systemless root method modifies the same binary that TWRP needs to modify in order to get data decryption working. Therefore, when you flash TWRP you are overwriting the changes made to the init binary by Chainfire's systemless root method. While this is a minor setback, thanks to the dual partition nature of the Pixel (and future devices shipping with Nougat), TWRP has some nifty new capabilities."
I'm pretty sure he's just saying dont chance something going wrong like it bootlooping or wiping data if you need your phone for something important like a phone call. Tough to answer said phonecall in a boot loop.
zaksimmermon said:
has anyone got the zip installed? when i boot into twrp.img everything is encrypted? im 100% stock as well
Click to expand...
Click to collapse
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
rtthane said:
I get exactly the same. Even after several attempts at booting the img, i don't get prompted to enter the PIN / passphrase as stated in instructions hence why the data is encrypted i presume.
Click to expand...
Click to collapse
I finally got passed that issue. I had to flash factory images and erase everything to the point of being at setup screen. I didn't set anything up, no network or wifi, skipped Google sign in, no password and also no Google functions activated. This led to an unencrypted setup, so after turning on dev settings and Android debugging I booted up the image. Now my issue is the zip to install twrp for sailfish is corrupt and if you try to unzip it there are no files in it....I downloaded the marline zip and there are files when unzipped....
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
ne0ns4l4m4nder said:
Maybe I'm an asshole but I cNt for the life of me flash this I download the .IMG I even changed name to TWRP.img but it won't flash boot at all just an error hmmmmm maybe I'm just dumb?
Click to expand...
Click to collapse
Are you trying to fastboot flash or fastboot boot?
Sent from my Pixel using Tapatalk
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
fracman said:
Guys, check out super su and root in xl thread. New Super su posted by chain fire to work with twrp.
Click to expand...
Click to collapse
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
ej_424 said:
Posted on standard pixel SU thread as well. Now if only I could make sense on the steps I need to take. This dual partition issue is throwing me off
Click to expand...
Click to collapse
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
BakedTator said:
My phone won't be here till tomorrow but as I understand it you need to use these steps (someone correct me if I'm wrong)
Reboot bootloader
Fastboot boot (twrp).img
Reboot recovery
In recovery, flash the twrp flashable .zip file
Reboot recovery
Flash the SuperSU sr4.zip
Reboot
Profit????
Click to expand...
Click to collapse
OK thanks, wondering if root will work with November update or of I need to roll back first. Prior to SU update today Nov update didn't work with the auto cf root

I need help. My 3T has no OS and won't mount data partition in twrp.

I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Fastboot format userdata
flammenwurfer said:
I guess I wasn't paying close enough attention and I tried installing the 7.0 update from this thread.
I can now only get to TWRP recovery and fastboot. When I'm in TWRP my internal storage says 0MB and it won't let me mount the data partition. Flashing anything fails.
Click to expand...
Click to collapse
Flash the stock recovery through fastboot. You can use the toolkit found here on xda forums.
Also you can format data in TWRP and then it should work, but you lose everything in internal storage, pics, music, all your own stuff.
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
flammenwurfer said:
Thanks guys. I got the stock recovery installed and it wiped everything, which was fine. I already backed up important stuff. It seems the update went through because I have Nougat now. But I'm having trouble installing any other roms. It wants to decrypt but it doesn't work. I read on the TWRP post that you can set a boot password and it would update the crypto key type or something and it should work after that. Well I did that, but twrp still won't accept my password and let me flash anything.
Click to expand...
Click to collapse
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
kinfam said:
I had the same problem. I used the 3T toolkit to force decrypt (Option 14). This worked for me.
Click to expand...
Click to collapse
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Nobody121 said:
I just did this and it worked in TWRP: I was able to create a backup (which is not possbible in password-bugged state) and then I noticed I still was not able to mount the USB partition and thought I had to boot in to OOS once, so I did it, set up the bare minimum and then checked back at TWRP and voilà: Locked again.
The OOS said "encrypted" as well after I booted it.
I was (am) running 7.0, TWRP, non rooted (because I freaking can't)
Anynone can help here?
Click to expand...
Click to collapse
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
kinfam said:
Did you flash SuperSU before booting into OOS? Not sure what to tell you I did the Force Decrypt then went into TWRP and immediately flashed SuperSU.
Click to expand...
Click to collapse
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Nobody121 said:
I wanted to do so but was not able to because I was not able to mount the relevant partition, nvm though I think I`ll wait a day or two to see if TW releases a new build. Thanks anyways:good:
Click to expand...
Click to collapse
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
cultofluna said:
,Using the toolkit take the option 14....To push decryption..,
DONT boot to your ROM...With the toolkit push the SuperSU and then flash it...
Now you can boot to your ROM....
If you boot without SuperSU will reenforse encryption.....
Click to expand...
Click to collapse
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Nobody121 said:
Push with adb sideload? Because I was not able to get that going for me. ADB is installed on my PC. Also is there a way to backup my apps and data without root? I just set everything up. Thanks for the help
Click to expand...
Click to collapse
Options 1 and 2 on the toolkit is backup and restore apps and data..
cultofluna said:
Options 1 and 2 on the toolkit is backup and restore apps and data..
Click to expand...
Click to collapse
Nice haha, Ill try it later. Thank you really much
So there is currently no way to root and use TWRP without completely disabling encryption?
I'm having the same issues as the OP here. Whenever I go to use the toolkit it says "the system cannot find the path specified." Any ideas? I've tried within Android and in TWRP..
Sent from my ONEPLUS A3000 using Tapatalk

Stuck in Fastboot Mode / TWRP without OS

Hello people,
I have an OnePlus 3T, which does not start the OS. I can open Fastboot Mode or TWRP. I do not even know which OS is installed (I think stock rom, but do not know). When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted". When I boot into system, it stops at the black "Powered by android" Screen (very first screen).
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
So what Information do I have so far (with my amateur knowledge):
adb shell getprop ...
ro.build.version.release: 6.0.1
ro.build.version.sdk: 23
ro.build.display.id: omni_oneplus3-eng 6.0.1 MOB31K eng.jc.20170208.012427 test-keys
ro.modversion: OmniROM-6.0.1-20170208-oneplus3-HOMEMADE
ro.twrp.version: 3.0.4-1
When I start the bootloader:
Product_Name - msm8996
Variant - MTP UFS
Bootloader Version -
Baseband Version -
Serial Number - *****
Secure Boot - enabled
Device State - unlocked
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
I tried to flash the stock ROM => did not work (with this Error 7)
So my first question: Which OS do I have? Really Marshmallow 6.0.1?
Second: Do you need more infos?
Third and most important: How to repair this mess?
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Thank you very much for your help.
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
thes3usa said:
Use ADB Sideload to Sideload a ROM onto the phone since you have TWRP working. It's not a huge problem, and it's easily solvable.
*OR* you can use the Unbrick tool to solve your problem.
Click to expand...
Click to collapse
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
elchico92 said:
Thank you for your reply.
Okay so it is not important which system I run right now? And what about this kernel thing?
I can just flash it with sideload (e.g. https://forum.xda-developers.com/on...pment/rom-kernel-resurrectionremix-n-t3524715) and finished? Rooted and particularly working?
Sorry for the questions but I am a little nervous
Click to expand...
Click to collapse
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
elchico92 said:
So first this one (downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_21/), then this (androidfilehost.com/?w=files&flid=131965 - latest)?
Thanks again!
PS: Sorry I cannot post links yet.
Click to expand...
Click to collapse
Nope, that's the complete stock Zip. Unless you want to install OOS, that's not the one to Sideload.
Download the FW only from here: https://forum.xda-developers.com/oneplus-3t/how-to/firmware-beta-10-t3631166
And then Sideload it, reboot back to recovery, and then Sideload the ROM.
elchico92 said:
When I connect my phone to the PC and open the internal storage, it shows only the "TWRP" folder.
Click to expand...
Click to collapse
What is in the TWRP folder, anything? The TWRP folder would normally only be created, if a backup was created. You can possibly just boot TWRP, select the RESTORE option, select the backup from the TWRP folder, and get the phone up and running again.
Another possibility, if you aren't that up on adb commands (sideload, etc.), since you can access the internal storage, just download a ROM or fill stock ROM zip onto your PC, then just drag/copy to internal storage. Then boot TWRP, select INSTALL, pick the file, and flash it.
What is the background of the device, how do you not know the OS version? Did you receive it this way, or fixing it for a friend or something?
---------- Post added at 09:19 AM ---------- Previous post was at 09:12 AM ----------
elchico92 said:
When I boot into Fastboot, I get the dm-verity notification "Phone is unlocked and cannot be trusted".
I read that this unlocked-notification appears because I have the wrong kernel? Is that true? Which one do I need?
Click to expand...
Click to collapse
That isn't the dm-verity notification. The dm-verity notification screen is similar, but says "dm-verity is not started in enforcing mode".
What you described is the bootloader unlocked warning screen. The bootloader unlocked warning screen is expected and normal (in fact, unavoidable) if the bootloader is unlocked. And unlocked bootloader is required for TWRP, flashing custom ROMs, etc.
dm-verity warning screen is in fact normal, as well, if you have TWRP installed. That one can be disabled by a couple different methods. But it's only purpose is to notify a "average" user that the system has been modified. For XDA users that are intentionally modifying their phones (TWRP, root, etc.) the warning is pretty meaningless. Under certain conditions, dm-verity will prevent the phone from booting. But TWRP and root in themselves, will normally not do that.
Neither warning means you have the wrong kernel, necessarily. And unless you (or someone else) tried to flash a kernel, there really isn't any reason to believe that.
---------- Post added at 09:29 AM ---------- Previous post was at 09:19 AM ----------
elchico92 said:
I tried to reflash the original recovery => device did not start in recovery anymore => reflashed twrp
Click to expand...
Click to collapse
Flashing stock recovery will (by definition) replace TWRP with stock recovery. You probably have recovery, just the stock one (not TWRP) which is fairly useless in your case (can't flash custom ROMs, root, etc.).
elchico92 said:
I tried to flash the stock ROM => did not work (with this Error 7)
Click to expand...
Click to collapse
Can't really troubleshoot this, unless you tell us what file exactly (file name) and where you got it from. "Stock ROM" is far too vague, and can literally mean a dozen or more different things.
Also, what version TWRP?
Using a TWRP version which does not support Oreo is one reason for Error 7. Or you may have tried a file intended for the 3, not the 3T. So these details need to be provided, before we can figure out what went wrong.
elchico92 said:
What do I want: A stable, rooted ROM. It can be the stock ROM, but also a custom, I do not care right now.
Click to expand...
Click to collapse
You kind of need to decide which of those you want. Otherwise, there are just too many options for us to give.
Yet another option (in addition to those given) would be to flash the full stock OOS zip from here: https://forum.xda-developers.com/oneplus-3t/how-to/official-oxygenos-5-0-1-android-8-0-t3728119
Then before rebooting, flash Magisk to root, and you should be all set. The full zip will put you on a fully stock baseline (including firmware). Which, if you aren't sure if you want stock, beta or custom ROM, is not a bad place to be; you can see what the "stock" condition is, before messing with things like custom ROMs. But again, it's totally subjective and a matter of personal preference, and you really do need to decide for yourself what is best for you (as an individual) at this time.
thes3usa said:
You may want to Sideload the latest Firmware too, Open Beta 21 that is. And then Sideload a Nougat ROM. Don't sideload any GAPPs.
Click to expand...
Click to collapse
Why not just sideload stock ROM which includes the firmware? Make life easier
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Yeah, that is a good option, among many. As I mentioned, there are just too many options since the original poster hasn't even decided stock or custom ROM.
przemcio510 said:
Why not just sideload stock ROM which includes the firmware? Make life easier
Click to expand...
Click to collapse
Since OP hasn't mentioned whether he wants to use a stock or custom ROM. So I gave him the link for the latest FW, in case he wants to use a recently updated custom ROM without needing to download the whole Stock zip.
Done!
Thanks a lot. The phone is working again.
I have flashed with adb sideload the firmware and the ResurrectionRemix-Rom (Nougat) and then via TWRP the gapps.
So I hope, everthing will be fine now.
answers:
- TWRP-folder: yeah I created one because I thought, maybe to restore will fix anything
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
- background: it was the phone of a friend of mine => he never heard anything about ROMs etc
The thread can be closed.
elchico92 said:
- I tried to flash with TWRP a ROM, but it says "Error 7", which means: wrong ROM => but I am sure, it was the right one
Click to expand...
Click to collapse
I already offered to troubleshoot this error for your, but you never supplied the requested info. Don't assume it is the "right one" next time, but rather, give exact file names, version numbers, and let us verify. Mistakes happen, and it always is good to have another set of eyes look at the specifics.
---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------
elchico92 said:
The thread can be closed.
Click to expand...
Click to collapse
Threads on xda don't get closed, just because you solved your current issue. Others may have a similar problem, and may want to ask questions, etc.
I'm stuck in Fastboot Mode & TWRP without OS
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
slykereven said:
I everyone,
Like the title say I'm totally stuck, I don't know what to do ....
I've got a OnePlus 3T few years ago, and the first thing i did at the installation was to encrypt the phone with an option of oxygen OS, and after that i unlock the oem and add root access.
But when oneplus release a major update, there was issues with phone encrypted and unlock, for that I never could make an update of the OS, so I did try to install the lastest lineage os recently, and add an "error 7".
After reading a lot of stuff and try a lot of manupilations, i'm now totally stuck with only access to the fastboot, twrp, and the recovery of oneplus.
If someone here could help me, you will be very gratefull because i can't afford to buy a new phone for the moment... thank's
Click to expand...
Click to collapse
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Resolved
OK, that's a little crazy but it's working, i've got a one plus 3T A3003, but i had to install Stable9.0.3+Firmware+Modem_OnePlus3.zip and not the one for the 3T ..... then install the last lineage os 17, and everything seems to work for now !!!
---------- Post added at 09:13 AM ---------- Previous post was at 09:09 AM ----------
BillGoss said:
This should get you back to OOS:
In TWRP:
1. Do a factory reset
2. Flash OOS 9.0.6 full rom
3. Flash this modified firmware (to avoid the issue 9.0.6 with encrypted+unlocked) https://github.com/nvertigo/firmwar...3t/oxygenos-9.0.6-bl-km-5.0.8-firmware-3T.zip (see https://forum.xda-developers.com/on...5-0-8-firmware-barrier-t3941164/post79758055)
4. Reboot
This should leave you with a clean install of OOS 9.0.6 and an encrypted phone with the stock recovery (TWRP gets replaced when you boot stock OOS).
From that point you can do what you want.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Hi, thank's for your help, i didn't see your answer before and i have resolved the issue with other method

Mi 8 - recovery bootloop, help!?

Have my Mi 8 about a week, loving it BUT as the bootloader is unlocked I couldn't use Google Pay so I decided to install TWRP and get the Xiaomi.eu ROM.
I just installed TWRP and tried backing up the phone, but I got an error saying it Can not create the folder. I reinstalled TWRP, thinking maybe there was an issue with the first install but now it's stuck in a recovery boot loop. It loads to the MI screen with the unlocked icon but doesn't get to the powered by android, it goes straight into recovery.
The Rom is not on the device and I thought maybe could install it through the recovery but if I have the phone plugged into the laptop (Windows 10) and go into recovery, the touch screen on the phone doesn't work and the phone keeps rebooting itself.
I can also get into Fastboot and the device is detected by miFlash.
What should I do next, I don't trust my instincts. Any advice would be much appreciated. I'm currently downloading the Global Rom off Xiaomi (going to take a while on my 3mb broadband) and hoping I can flash that with miFlash tool, good or bad idea??
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
gm007 said:
U can use otg usb and put the rom on it.
Boot to twrp and wipe data (the one that ask you to say yes? Than install the rom(choose one for recovery flashing not fastboot)
Click to expand...
Click to collapse
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
cherbe.3 said:
Cheers for the reply! Unfortunately I don't have an adapter to put the rom on the phone. I'll order one now, always good to have for situations like this.
Any other way of getting the phone up and running sooner? If not, no problem, I'll just have to wait for the adapter.
Click to expand...
Click to collapse
Sure there must be a fastboot method but didn't tried it yet, i had this phone 3 days ago
Not sure if after formatting data and reboot to twrp you can copy the rom from pc to phone.
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Sent from my MI 8 using Tapatalk
Click to expand...
Click to collapse
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
gm007 said:
One more thing if you use fastboot method be sure not to relock the bootloader cause you may brick ur phone.
Click to expand...
Click to collapse
Oh yes, thank you for the reminder, that slipped my mind with this whole mess.
ariekumbang said:
If you want to install xiaomi.eu rom dont just wipe data but you have to format data then type yes. Reboot to twrp again. And at twrp recopy the xiaomi.eu rom.
Click to expand...
Click to collapse
Cheers for the advice, I'll make sure to format before installing. Only issue now is that I can't get the rom onto the phone to install it. Do you reckon if I format the data through TWRP it will then allow me to copy over the rom onto the device? Currently, unless in fastboot, the laptop doesn't recognise the device - constantly reboots the phone causing it to connect and disconnect.
SPOCK_VULKAN said:
Flash last MIUI global dev. Flash twrp. Wipe only data. Transfer Rom to phone. Flash Xiaomi eu Rom. Done
Click to expand...
Click to collapse
I like the sound of this solution but I have a few questions/need clarification as this mess has made me doubt myself (no issue flashing my previous phone mi5)
I downloaded the Global rom from here: http://en.miui.com/download-346.html#523 (just want clarification this is the official rom) I have the latest version of the miFlash. Am I right in thinking, put phone into fastboot, launch tool, locate unzipped rom folder, select 'Clean all' (and not save user data / clean all and lock (presume this means bootloader)) and click Flash??
And then do I start again, flash TWRP and hope it works?
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
If I do this (wipe data and format) will the laptop detect the device to allow me to move the rom onto the phone, currently it doesn't (well it loops between connecting and disconnecting when in TWRP, no issue detecting in fastboot)
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
deepblue2000 said:
the only right answer, all other are more or less useless.
you need to wipe data, then format data (confirm with yes)
after that, hold power+up to reboot in twrp again
(or go to mainmenu and choose reboot to recovery),
connect your Mi8 with Usb cable to PC and copy the xiaomi.eu rom to your mi8
and then flash it.
Click to expand...
Click to collapse
deepblue2000 said:
normally if twrp is launched, you can copy files as usual from pc to your Mi8
should be a stable connection.. (Win7/10 or any other Win)
if it keeps connecting/disconnecting you can try an other usb port.
do you use the right twrp ?
https://forum.xda-developers.com/mi-8/development/recovery-twrp-3-2-3-0-mi-8-t3837745
and you enabled usb debugging in settings before you flashed twrp ?
(I think without it will not work, even to flash twrp it is needed, so you did it)
Click to expand...
Click to collapse
I've tried several USB ports and different cables, no luck getting it to connect.
No the TWRP installed is 3.2.1-0611-XIAOMI8, yours uses the code name and seems to be a newer version and more legit, I'm going to flash that onto the phone. I presume do it the way I did it before - fastboot, shift right click to get to cmd line...etc.
I did indeed enable usb debugging when I installed it originally.
By the way, thanks so much for your help, I'm lost without my phone - it was love at first sight
Fastboot Flashing Code
Code:
Fastboot boot Twrp.img
Flash the recovery img again inside twrp and reboot to recovery again and it will stay.
If u are new to twrp, format data in twrp and reboot to recovery again and flash this file https://androidfilehost.com/?fid=3700668719832238534 after that u can flash the rom.
If u have already twrp installed, just flash the img in twrp
Click to expand...
Click to collapse
Actually I'm confused now, is this probably where I went wrong in the first place.
Boot the TWRP img and then flash it through TWRP, I've never done it this way before (have I been doing this worng all along?)
and whats the other file about? Disable_Dm-Verity_FEC_v1.1.zip
Sorry about all the questions
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
deepblue2000 said:
you can flash/update twrp inside twrp itself, but you dont need it.
I never used any tools or bat files, just normally installed adb,
and put the twrp.img in the same folder.
then open cmd:
fastboot flash recovery twrp.img
to boot into twrp again:
fastboot boot twrp.img
never heard from this fec1.1 zip, so ignore it.
you should go to the xiaomi.eu forum for help,
https://xiaomi.eu/community/threads...ing-xiaomi-eu-8-8-30.46378/page-2#post-444327
there are the steps posted what to do
Click to expand...
Click to collapse
Right, so I got TWRP 3.2.3 installed and seems to be working (not disconnecting and reconnecting) BUT the phone is still not recognsed - It says unspecified in the devices . I ran through the ADB set up, all installed including drivers but still no phone showing up. I hate windows 10 and drivers, can't get them to play nice (or it's me)
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
deepblue2000 said:
I had never any problems with Win10 x64,
I dnever installed any driver for my Mi5/6 and now 8,
win10 detects everything automatically, if you have installed any driver, maybe just
uninstall them and restart win10
Click to expand...
Click to collapse
AND WE'RE IN!!! THANK YOU, THANK YOU!! If you were here I'd hug you and get you a drink.
Forget my above nonsense and babble, PC wasn't happy with whatever was going on, once I got brave enough and actually followed your instructions in all fell into place!!
So conclusion -
I had the wrong TWRP (3.2.3 is needed)
PC didn't like whatever was happening without the OS
Wiped and formatted through TWRP - Phone was recognised
Dragged Xiaomi.eu rom over - copied perfectly
Flashed rom - successful and the wiped cache again to be safe
Rebooted and my smile came back the moment I saw the 'powered by android' icon
Went through set up and I'm back in.
Mi 8 - bootloop and locked device, no system, help?
Hi guys,
I did a pretty much bad thing on my phone, I've just bought it 2 weeks ago and I was loving the phone, my phone is unlocked but today I was rooting to install google camera with night sight and I don't know why my twpr was really weird, when pressing install all the folder that was showing was very different from youtube videos about mi 8 root and even compared to my old devices, it was showing folders like licence and others, but the weirdest was inside the sdcard folder that was showing a lot of unnamed folders(like this: 54u3hu6ijj4!ji5), the thing got worse when I've flashed magisk and the phone got stuck on bootloop, after that tried to flash a stock global rom from official Mi website on fastboot mode using Mi Flash Toll, what I did wrong is that I didn't see that the Lock option was ticked and than I pressed to flash, everything was going good when my device showed a message saying that the Miui wasn't compatible with my phone. After that I've tried to install TWPR again but my phone was locked by the Mi flash toll and know my device is without system and unlocked. I've also tried to unlock but is saying that my account is not bound to my device, so I have no idea what to do, I'm gonna never root any phone ever, worse thing I did.
Can Anybody know what I can do to unlock the phone?
Sorry about my English, that's not my native language.

How To Guide [TWRP] MI 11 (Pro/Ultra) (mars/star)

[TWRP] MI 11 (Pro/Ultra) (mars/star)​
WARNING : I do not know who made this TWRP and I am NOT taking credit for it. It was posted on eu site and I'm just sharing since there was no thread for twrp here on xda.
INSTRUCTIONS
1. Before starting the process, the bootloader must be unlocked.
2. Install Xiaomi USB drivers.
3. Enable Usb debugging from Settings - Additional settings - developer options.
4. Download TWRP for Mi 11 (Pro/Ultra) , and put it in your fastboot folder.
5. Put your phone into fastboot mode.
6. Rename downloaded file to "twrp.img".
7. Do the following command. It will automatically boot into TWRP.
Code:
fastboot boot twrp.img
8. If you get a screen asking for a pin, press 2nd option
and change language to English then enter phone pin.
9. Change language to English (press the 6th option).
10. Go to "Advanced" and select "Onekey inject TWRP".
11. Swipe to inject the TWRP. It might take a few minutes, so don't worry.
Note
1) Don't change the boot slot, currently (Slot A) for most or your device will not boot at all.
2) For user experiencing decrypt issue, you can try one of the methods below to enable decryption:
a. Remove all your security eg. fingerprint, face unlock, pattern and leave ONLY pin. Reboot to twrp and try again.
b. Reflash twrp.
c. LAST RESORT! Format data and factory reset your device then reflash twrp.
3. For user experiencing decrypt issue but just want to flash latest build:
a. Boot to twrp > mount > mount usb storage then transfer your rom.zip to data/media/0
b. Now go to install and look for rom.zip under data/media/0. Profit!
4. The decrypt issue was a bug on the Chinese twrp, no update since may so don't ask for an ETA.
CHANGELOGS
07/18/21
1) Additional instruction from scratch.
2) Additional note for people having decrypt issue.
CTTO: xiaomi.eu, hoangsang
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
skylerfly16 said:
Is the legit TWRP ?? Xiaomi.EU getting ready to push updates via TWRP? :'D
Click to expand...
Click to collapse
Yes, They just did the new stable in TWRP Format.
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
speedtripler said:
The Chinese exe worked for me this morning but after I installed it the phone didn't want to boot and I got stuck in twrp for awhile
Click to expand...
Click to collapse
Why did you install the Chinese exe?
skylerfly16 said:
Why did you install the Chinese exe?
Click to expand...
Click to collapse
The official one hadn't been released yet and I like a challenge sometimes
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
deleted post
I keep getting a " no such partician " fail msg , what am I doing wrong here?
speedtripler said:
I keep getting a " no such partician " fail msg , what am I doing wrong here?
Click to expand...
Click to collapse
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
heinhuiz said:
Your device is not connected, hence the empty list after adb devices.
Did you enable USB debugging in Developer options?
Click to expand...
Click to collapse
Thx It's ok,I got it after a few attempts
The language on twrp still opens on Chinese and it needs changed to English each time but apart from that it seems to work fine!
SanHelios said:
Hey, thx for bringing this to my attention, but i checked... root-access is gone... :/
Click to expand...
Click to collapse
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
innocence07 said:
mine was revoked after i flash the latest stable, just download magisk23.apk then rename it to magisk23.zip and flash thru twrp, got my root back that way, cheers
Click to expand...
Click to collapse
Is banking and payment apps still working?
Can you still pass safetynet check?
speedtripler said:
Is banking and payment apps still working?
Can you still pass safetynet check?
Click to expand...
Click to collapse
Yes and yes
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
sabrewulf said:
Thanks, it works for me.
But each time i boot on TWRP, go back to chinesse language.
Can we do backup ? (and what can we backup) in case of something wrong in the future
Click to expand...
Click to collapse
The recovery is fully functional as far as I can tell...
I did a complete backup successfully but I haven't tried to restore it yet
You click on everything ?
Hi,
after a long day of learning the hard way (got stuck in Fastboot Loop) I am now on stable EU 12.5.7 (MI11 Ultra, EU phone). So far so good, but I was wondering, how can I make TWRP stuck to the phone, meaning, when I push the power button to have an option like: Boot into TWRP. Is that possible or is there a "click this button with this... trick"?
ATM, I can only get TWRP to work, when I enable it via PC, which is not good.
I am asking, because I have an old Oneplus 6, which has this option. TWRP is installed and I can boot directly to it, if I want to.
Can you please help me out? Is there a trick or am I doing something wrong?
Greetings from Germany
Placebo
I believe you are on custom EU rom right? Just reboot into recovery, custom eu rom injects twrp as standard recovery
Hi, yes I am and I did that also. But still can't boot into TWRP from within the phone. Is there a trick after the injection?

Categories

Resources