Google services and apps are not working - Xiaomi Redmi Note 5 Pro Questions & Answers

I am on MIUI 9.6.3 GLOBAL stable rom.
I have unlocked my bootloader and twrp is installed.
I took a full back up of my current miui rom (including data) from twrp.
I was using Pixel Experience rom.
Now i want to come back to miui, so i have restored from the backup that i took including data.
But the Google services have stopped working.
Even some third aaps are also not working properly.
I tried restoring from the backup without data but then the ph setup itself is getting stuck, as Google services are not working.
Please help.

/data parition is corrupt
flash miui again by
1. Format /data , (change /data partition filesystem to exFAT and then back to ext4)
2. wipe system , vendor
flash MIUI again!
don't flash lazyflasher! or magisk now! and don't flash any custom kernel at this point!
reboot! setup accounts, update google play services and update all apps
now reboot in to revoer and flash lazyflasher and magisk!
orr flash custom kernel and magisk!
reboot

YasuHamed said:
/data parition is corrupt
flash miui again by
1. Format /data , (change /data partition filesystem to exFAT and then back to ext4)
2. wipe system , vendor
flash MIUI again!
don't flash lazyflasher! or magisk now! and don't flash any custom kernel at this point!
reboot! setup accounts, update google play services and update all apps
now reboot in to revoer and flash lazyflasher and magisk!
orr flash custom kernel and magisk!
reboot
Click to expand...
Click to collapse
Can you please help me on point 1, like how the change filesystem to exFAT and then back to ext4 ?
Just want to ask, if i flash the same version of full miui rom(i downloaded it from miui forum) through some flasher tool, will it fix the issue..?

YasuHamed said:
/data parition is corrupt
flash miui again by
1. Format /data , (change /data partition filesystem to exFAT and then back to ext4)
2. wipe system , vendor
flash MIUI again!
don't flash lazyflasher! or magisk now! and don't flash any custom kernel at this point!
reboot! setup accounts, update google play services and update all apps
now reboot in to revoer and flash lazyflasher and magisk!
orr flash custom kernel and magisk!
reboot
Click to expand...
Click to collapse
tamalnag said:
Can you please help me on point 1, like how the change filesystem to exFAT and then back to ext4 ?
Just want to ask, if i flash the same version of full miui rom(i downloaded it from miui forum) through some flasher tool, will it fix the issue..?
Click to expand...
Click to collapse
1. connect device in fb mode , keep ORANGFOX recovery on desktop. (8.3)
2. open ADB / fastboot command prompt, test connection to device , Fastboot devices and enter... if it show some hex code, this mean yourr device is connected
3. type fastboot boot ..... and DRAG DROP orangfox recovery from Desktop to cmd window and press enter! you device will boot in to OF recovery!
4. goto WIPE > ADVANCE WIPE > select DATA click PARTITION OPTIONS > click exFAT > click OK > it may give ERROR, but its oK,,, > click WIPE again > goto ADVANCE WIPE >select DATA click PARTITION OPTION > now select ext4 > click OK.
5. again goto WIPE, click FORMAT DATA> type YES and proceed
6. AGAIN goto WIPE now, select partitions /system /overlays / data / delvik cache , /cache and OK.....
7. once done. , click power off and power off device
now do the STEP ONE again! and boot into recovery. flash custom rom or MIUI and it would be ok!
1. make sure you have MIUI downloaded from proper location and the rom is COMPLETE. broken file may brick your device
2. NO you cannot just FLASH recovery rom of MIUI using flasher! , FLASHER supports Fastboot ROM and yes! it will FIX everything! .... BUT
3. in flash there is BOTTOM RIGHT BUTTON mentions , WIPE ALL & LOCK... you MUST NOT SELECT this! or else miFLASHER will FLASH ROM and will LOCK your bootloader !!!!! so becareful
4. I never flashed RN5pro using FLasher! but my OLD redmi3s, i always used miflasher to flash FB version of MIUI ROM in EDL mode! now RN5pro can only be connected in EDL MODE if you REMOVE BACK PANEL and touch two test point with Tweezer! & connect usb wire SIMULTANEOUSLY. this will finally connect your RN5pro in EDL MODE and (qualcomm loader8 will APPEAR in windows DEVICE MANAGER window) ... BUT still to FLASH RN5pro in EDL mode using miFLASHER,, you must have your AUTHORIZED ACCOUNT by MIUI (which i don't know how to get ) ... but for such fones! there is speciall tutoria on XDA , how to FLASH RN5pro in EDL mode (bricked fone) and BY PASSING the AUTHORIZED ACCOUNT VERIFICATION by MiFLASHER
so i hope you fix your /data partition bootloops easily!!!
remember!!!!!!
for me! MIUI10.0.0 worked perfect
when i flashed MIUI10.0.2 and flashed magisk! i got serious bootloops! and i couldnt come out of it! i wiped data partitions many times! using TWRP,,,, it was only ORANGEFOX recovery who did the magic!! I extracted the PERSIST.img file from FASTBOOT ROM of miui9.6.7 rom (2.1gb file) and I flashed PERSIST.img on PERSIST partition (orange fox recover allows to do that) and then i did the /data partition thing! and finally i flashed AOSIP8.1 (custom rom and i came out of bootloops)
My guess is that MIUI10.0.2 has some bugs!
now MIUI10.0.4 is out!
TRY THAT ONE!!! don't flash MIUI10.0.2 !!!

YasuHamed said:
1. connect device in fb mode , keep ORANGFOX recovery on desktop. (8.3)
2. open ADB / fastboot command prompt, test connection to device , Fastboot devices and enter... if it show some hex code, this mean yourr device is connected
3. type fastboot boot ..... and DRAG DROP orangfox recovery from Desktop to cmd window and press enter! you device will boot in to OF recovery!
4. goto WIPE > ADVANCE WIPE > select DATA click PARTITION OPTIONS > click exFAT > click OK > it may give ERROR, but its oK,,, > click WIPE again > goto ADVANCE WIPE >select DATA click PARTITION OPTION > now select ext4 > click OK.
5. again goto WIPE, click FORMAT DATA> type YES and proceed
6. AGAIN goto WIPE now, select partitions /system /overlays / data / delvik cache , /cache and OK.....
7. once done. , click power off and power off device
now do the STEP ONE again! and boot into recovery. flash custom rom or MIUI and it would be ok!
1. make sure you have MIUI downloaded from proper location and the rom is COMPLETE. broken file may brick your device
2. NO you cannot just FLASH recovery rom of MIUI using flasher! , FLASHER supports Fastboot ROM and yes! it will FIX everything! .... BUT
3. in flash there is BOTTOM RIGHT BUTTON mentions , WIPE ALL & LOCK... you MUST NOT SELECT this! or else miFLASHER will FLASH ROM and will LOCK your bootloader !!!!! so becareful
4. I never flashed RN5pro using FLasher! but my OLD redmi3s, i always used miflasher to flash FB version of MIUI ROM in EDL mode! now RN5pro can only be connected in EDL MODE if you REMOVE BACK PANEL and touch two test point with Tweezer! & connect usb wire SIMULTANEOUSLY. this will finally connect your RN5pro in EDL MODE and (qualcomm loader8 will APPEAR in windows DEVICE MANAGER window) ... BUT still to FLASH RN5pro in EDL mode using miFLASHER,, you must have your AUTHORIZED ACCOUNT by MIUI (which i don't know how to get ) ... but for such fones! there is speciall tutoria on XDA , how to FLASH RN5pro in EDL mode (bricked fone) and BY PASSING the AUTHORIZED ACCOUNT VERIFICATION by MiFLASHER
so i hope you fix your /data partition bootloops easily!!!
remember!!!!!!
for me! MIUI10.0.0 worked perfect
when i flashed MIUI10.0.2 and flashed magisk! i got serious bootloops! and i couldnt come out of it! i wiped data partitions many times! using TWRP,,,, it was only ORANGEFOX recovery who did the magic!! I extracted the PERSIST.img file from FASTBOOT ROM of miui9.6.7 rom (2.1gb file) and I flashed PERSIST.img on PERSIST partition (orange fox recover allows to do that) and then i did the /data partition thing! and finally i flashed AOSIP8.1 (custom rom and i came out of bootloops)
My guess is that MIUI10.0.2 has some bugs!
now MIUI10.0.4 is out!
TRY THAT ONE!!! don't flash MIUI10.0.2 !!!
Click to expand...
Click to collapse
Thank you very much for such a detailed explanation.
I will try this out.

YasuHamed said:
1. connect device in fb mode , keep ORANGFOX recovery on desktop. (8.3)
2. open ADB / fastboot command prompt, test connection to device , Fastboot devices and enter... if it show some hex code, this mean yourr device is connected
3. type fastboot boot ..... and DRAG DROP orangfox recovery from Desktop to cmd window and press enter! you device will boot in to OF recovery!
4. goto WIPE > ADVANCE WIPE > select DATA click PARTITION OPTIONS > click exFAT > click OK > it may give ERROR, but its oK,,, > click WIPE again > goto ADVANCE WIPE >select DATA click PARTITION OPTION > now select ext4 > click OK.
5. again goto WIPE, click FORMAT DATA> type YES and proceed
6. AGAIN goto WIPE now, select partitions /system /overlays / data / delvik cache , /cache and OK.....
7. once done. , click power off and power off device
now do the STEP ONE again! and boot into recovery. flash custom rom or MIUI and it would be ok!
1. make sure you have MIUI downloaded from proper location and the rom is COMPLETE. broken file may brick your device
2. NO you cannot just FLASH recovery rom of MIUI using flasher! , FLASHER supports Fastboot ROM and yes! it will FIX everything! .... BUT
3. in flash there is BOTTOM RIGHT BUTTON mentions , WIPE ALL & LOCK... you MUST NOT SELECT this! or else miFLASHER will FLASH ROM and will LOCK your bootloader !!!!! so becareful
4. I never flashed RN5pro using FLasher! but my OLD redmi3s, i always used miflasher to flash FB version of MIUI ROM in EDL mode! now RN5pro can only be connected in EDL MODE if you REMOVE BACK PANEL and touch two test point with Tweezer! & connect usb wire SIMULTANEOUSLY. this will finally connect your RN5pro in EDL MODE and (qualcomm loader8 will APPEAR in windows DEVICE MANAGER window) ... BUT still to FLASH RN5pro in EDL mode using miFLASHER,, you must have your AUTHORIZED ACCOUNT by MIUI (which i don't know how to get ) ... but for such fones! there is speciall tutoria on XDA , how to FLASH RN5pro in EDL mode (bricked fone) and BY PASSING the AUTHORIZED ACCOUNT VERIFICATION by MiFLASHER
so i hope you fix your /data partition bootloops easily!!!
remember!!!!!!
for me! MIUI10.0.0 worked perfect
when i flashed MIUI10.0.2 and flashed magisk! i got serious bootloops! and i couldnt come out of it! i wiped data partitions many times! using TWRP,,,, it was only ORANGEFOX recovery who did the magic!! I extracted the PERSIST.img file from FASTBOOT ROM of miui9.6.7 rom (2.1gb file) and I flashed PERSIST.img on PERSIST partition (orange fox recover allows to do that) and then i did the /data partition thing! and finally i flashed AOSIP8.1 (custom rom and i came out of bootloops)
My guess is that MIUI10.0.2 has some bugs!
now MIUI10.0.4 is out!
TRY THAT ONE!!! don't flash MIUI10.0.2 !!!
Click to expand...
Click to collapse
Thanks for your help.
It worked successfully.!

Related

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
I have the same problem
Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???
I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.
Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.
karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.
sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

Encryption issues on Nougat firmware

Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
You could try with other TWRP versions? Say 3.0.2-22
It's a known issue
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Simone98RC said:
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
Click to expand...
Click to collapse
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Password I hope can be managed with the new modified TWRP mentioned below by @abhibnl but I am more concerned with the dm verity message not going...
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
now i am sideloading os from twrp
mnishamk said:
You could try with other TWRP versions? Say 3.0.2-22
Click to expand...
Click to collapse
It's not working, because modded TWRP from .18 to .23 are designed for Marshmallow community builds.
dbabaev21 said:
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Click to expand...
Click to collapse
What I've said above (tried .19 too with same unsuccessful result).
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Probably it would be risolutive, however I want to stay on latest Community Build.
I can say that sideload won't work with Open Beta 10: it can be flashed only via recovery (both TWRP and stock).
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
That would be easy! The hoped behaviour
Obviously I've just tried with unsuccessful result.
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @abhibnl solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
badmaash said:
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Click to expand...
Click to collapse
The recovery should be linked in the official OB10 download page @ oneplus.net
Simone98RC said:
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @atulclassic solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
Click to expand...
Click to collapse
Yes i was referring to that recovery. 1 user has responded that it worked fine on his f2fs encrypted storage, so i believe it's worth trying. I am not on f2fs so i personally can't test it for you. But i would advise you to atleast give it a try. You never know when you by mistake boot right after a fresh stock rom install with stock kernel, and it will immediately encrypt your storage. So, you can't always just keep formatting internal memory. A proper TWRP recovery is indeed required for both ext4 and f2fs. All i am waiting for is updated kernel sources for recovery devs to work on.
For the many having issues, here's a step by step:
step by step install for OOS 4.0 and twrp-3.0.2-1.28-op3.img
Have OOS stock recovery installed on your phone. You must also have adb installed on your computer.
connect your phone to your computer via usb and open a dos command session on your computer.
On your phone, reboot into fastboot (bootloader).
From adb command on computer, type fastboot boot twrp-3.0.2-1.28-op3.img.
First make a backup and copy it to a safe location.
Now wipe everything - Internal, system, data, cache.
Reboot to Recovery. This is the stock OOS recovery!
Go to install from USB and then enter sideload mode.
On your computer dos prompt, type adb sideload (path)OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Allow the long and slow process to complete and reboot.
Upon reboot, it is encrypting the data partition as EMMC.
Upon bootup, enter setup and go through it quickly as you will have to enter it again so do not waste time configuring it.
Once setup is complete, reboot into fastboot.
From DOS command, enter adb and type command fastboot boot twrp-3.0.2-1.28-op3.img.
TWRP will boot up asking for encryption password. Hit cancel and then swipe to allow modifications.
Go into mount. Only the system and cache will appear. Back out and select WIPE.
select ADVANCED WIPE and data partition only.
Modify the data parition by selecting Repair or Change file system.
It will list the current mount point as emmc. Select Change File System.
Select F2FS and swipe.
This will wipe current data partition and reformat it.
Once you have done this, while in TWRP, select the ADVANCED button on the main menu.
Now select ADB SIDELOAD and swip to start sideload.
On your computer in ADB, type command adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip.
Now reboot system and go through the usual setup and your done.
TWRP v11: the definitive solution
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
FINAL UPDATE: the specified recovery is working with Open Beta 10 decryption.
Thanks all for answering :good:

Xiaomi Max 3 stuck on boot after Unlock + TWRP Format Data

So here's what I did to cause my phone to get stuck on the logo screen:
1. Unlocked my phone using the Mi Unlock
2. Used ADB to install twrp-3.3.1-0-nitrogen
3. I couldn't mount my Data or SD Card folders due to encryption, so someone told me to use TWRP to format data, which I did. It didn't boot up after that.
I've tried the following fixes:
1. TWRP > Advanced Wipe > Cache / Data / Internal Storage / System
2. TWRP > Install > MIUI 11 V11.0.2.0.PEDCNXM
3. TWRP > Install > MIUI 11 V11.0.3.0.PEDCNXM
4. TWRP > Install > Magisk-v20.4
No luck, still stuck on boot. Anyone kind enough to please help?
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
irinho said:
I had the same problem when I backed up the global rom with OrangeFox and restarted the system without installing anything.
The following procedure worked for me.
User the latest version of TWRP 3.3.1 do not use OrangeFox
1. First you must remove the encryption, Wipe> Format Data, confirm by typing "yes"
2. Advanced Wipe and clean Dalvik, Cache, Data, System and Vendor.
3. Then proceed with the installation.
In my case I installed xiaomi.eu_multi_MIMAX3_V11.0.2.0.QEDCNXM_v11-10
Hope this helps!
Click to expand...
Click to collapse
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Hadron001 said:
Thanks a lot for the reply!
I somehow managed to get it working with OrangeFox, so I'm going to try it for awhile till it breaks. But I can't seem to pass the SafetyNet Check in Magisk, so I might have to your tips eventually.
What I did was:
1. Use the MI Flash tool + 11.03 CN Fastboot ROM to get out of the boot loop.
2. Loaded OrangeFox-R10.1-stable-nitrogen and Magisk-v20.4 on an SD Card
3. ADB + Fastboot to install twrp-3.3.1-0-nitrogen, then installed OrangeFox
4. Using OrangeFox, installed Magisk-v20.4
Click to expand...
Click to collapse
I have not yet rooted with magisk on xiaomi.eu so I have no way of giving an opinion on what may have gone wrong in your case.
But did you install the most current magisk from magisk.me and clear the cache?
maybe this video can help you. shows a Brazilian installing orangefox and rooting with magisk in the global rom and everything works, Magisk passes the SafetyNet test. https://youtu.be/O5bq1HMFREI?t=328

Question Cannot flash TWRP from Fastboot, TWRP reboot shows Slot A/B, dont know what to do

Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Start fresh by flashing stock MIUI rom through fastboot and proceed from there
1 Boot once into MIUI and reboot into fastboot
2 fastboot boot twrp.img (from platform tools folder)
3 Flash custom rom like ArrowsOS with inject twrp option checked
4 Reboot recovery
5 Format Data by typing "yes"
6 Reboot to system
7 Done
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Use "fastboot boot TWRP.img" to temporarily boot TWRP.
You can install TWRP by using "Install to Ramdisk" inside TWRP and selecting TWRP.img
Cvenda said:
Ive already flashed a few phones, but this is the first time that Ive got CMD error "FAILED (remote: (recovery_a) No such partition)". So I booted twrp.img, falshed ArrowOS and TWRP from within TWRP and it said something about Slot A and B, which I dont understand ... some guide also said to Format Data, which I did, and then I just could boot into TWRP in Slot A, and no OS on Slot B, which rebooted me into Slot A. I couldnt find any info about this and I dont know what to do. Anybody knows how to properly flash TWRP and custom ROMs please ?
Click to expand...
Click to collapse
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
pedrowood said:
Did you manage to fix it? I got into the same problem, I could only fix it downloading the most updated version of adb/fastboot. I don't remember where I downloaded it, but it was what solved this problem for me.
Click to expand...
Click to collapse
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Cvenda said:
well Iam still confused about that Slot A/B thing, but since Ive probably bricked my phone, I flashed the fastboot ROM through MiFlasher and I havent tried flashing TWRP or custom ROM since, there are some things I really like about MIUI so Iam gonna see which ROM Iam gonna choose in the future
Click to expand...
Click to collapse
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Milan-XDA said:
Slot A and B refer to Project Treble, where there are 2 separate partitions. 1 for OEM like Samsung and other for core Android OS. That way Google can update the OS partition with security updates without having to wait for Samsung to implement those security update into their version of Android, as was the case before Galaxy S9. Needless to say, this way security updates get pushed out way faster, because there is no need to wait an entire year (I'm looking at you Samsung) for OEM to finally implement it. Hope this clears things up for you.
Click to expand...
Click to collapse
reason for slots
Robert314 said:
Follow the TWRP install instructions by fastboot boot TWRP.img
advanced, install TWRP
It should then reboot and TWRP will be installed
Then proceed as above by flashing a ROM e.g ArrowOS with TWRP inject.
Then reboot TWRP and wipe data
Click to expand...
Click to collapse
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
EDIT: after sideloading ArrowOS and booting TWRP using "fastboot boot twrp.img", I can access internal storage, so I uploaded twrp.img into /sdcard/Download folder, installed it into ramdisk, rebooted to Recovery and now successfully flashing CrDroid ROM that I uploaded to /sdcard/Download
Cvenda said:
there is a slight problem with this ... I cannot upload any file to the phone, because I have wiped Data, so there is no folder that I can access from the PC, so I can only sideload .zip files, and most of the .zip files just doesnt work for some reason, only ArrowOS, but not the PixelExtended, nor CrDroid ... I cannot even sideload TWRP.img to install it into ramdisk
Click to expand...
Click to collapse
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Robert314 said:
You can adb transfer files in TWRP. You could also use a USB stick connected via OTG cable
Click to expand...
Click to collapse
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Cvenda said:
its behaving so randomly ... I often get error kInstallDeviceOpenError, even tho I successfully installed that ROM at least one time ... I dont know which slot (A/B) to use and when ... now I have ArrowOS in slot A and CrDroid ins lot B, and I cannot flash anything from booted TWRP.img ... Iam gonna try to install TWRP into ramdisk again from USB OTG
Click to expand...
Click to collapse
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Robert314 said:
In order to wipe the super partition (both A/B and data) flash Xiaomi.eu and then wipe data
Click to expand...
Click to collapse
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Cvenda said:
how exactly should I proceed ? flash fastboot stock ROM with MiFlasher, boot into bootloader, boot twrp.img, wipe data, and then what ? which slot do I choose ? should I install TWRP into ramdisk, reboot into recovery and then flash custom ROM ?
Click to expand...
Click to collapse
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
dreamytom said:
ROM: xiaomifirmwareupdater.com/archive/miui/alioth/
Mi Flash: xiaomiflashtool.com
ADB & Fastboot: developer.android.com/studio/releases/platform-tools
TWRP: https://forum.xda-developers.com/f/xiaomi-poco-f3-xiaomi-mi-11x-redmi-k40.12161/?prefix_id=33
Clean Install of Xiaomi.eu ROM:
Flash Stock ROM with Mi Flash
Boot System once (to create /data)
Boot TWRP from Nebrassy or @Vasishoth
Flash Xiaomi.eu ROM
Format Data & Dalvik Cache
Click to expand...
Click to collapse
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Cvenda said:
in case of flashing custom ROM, are the steps same ? just instead of Xiaomi.eu ROM I flash PE, or CrDroid ? and should I format data and dalvik also or wipe data (that option where I need to type YES) ? Ive found official guide for flashing CrDroid, but Iam stuck st booting animation for 30 minutes
Click to expand...
Click to collapse
Go into TWRP and press wipe then format data (type yes).
regedit12345 said:
Go into TWRP and press wipe then format data (type yes).
Click to expand...
Click to collapse
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Cvenda said:
I have stock rom in slot A (bootable and working) and custom rom in slot B (stuck at booting animation), and I should format data while being in slot A right ?
Click to expand...
Click to collapse
Doesn't matter. Just select format data > yes > reboot to system
regedit12345 said:
Doesn't matter. Just select format data > yes > reboot to system
Click to expand...
Click to collapse
sooo what seemes to work for me now is, that I formated data, then flashed PE ROM from OTG and booted into it without any problems

Question MI 12X system partition Corrupted/deleted Need Urgent Help Please. ??

my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.
ajoy25 said:
my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.
Click to expand...
Click to collapse
Check here that everything has been done correctly
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
ajoy25 said:
my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.
Click to expand...
Click to collapse
How did you install twrp? Did you flash the twrp to boot partition? If yes, you need to find out which system you had installed and then flash the suiting boot.img.
Background: In A/B partition scheme, recovery is part of boot.img. Boot.img needs to be patched by twrp. So normally you need to boot twrp by typing "fastboot boot twrp.img" and then, when twrp is booted, go to advanced and press "flash current twrp"
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
ajoy25 said:
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
Click to expand...
Click to collapse
Ok, you already deleted data. Try to format data via fastboot. Use "fastboot -w" and retry!
ajoy25 said:
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
Click to expand...
Click to collapse
Maybe start one thing at a time.
Problem with twrp
Try flashing this Fastboot rom
Download the rom/extract it/open the folder /use first install.bat with the phone in Fastboot mode
https://sourceforge.net/projects/xi...13.0.5.0.SLDCNXM_v13-12-fastboot.zip/download
then install the TWRP and update the rom via OTA (do not put any security on the lock screen).
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img​
then in Twrp go to Advanced -> flash current TWRP->reboot TWRP
If that doesn't work/see post https://forum.xda-developers.com/t/...need-urgent-help-please.4491461/post-87424405
NOSS8 said:
Maybe start one thing at a time.
Problem with twrp
Try flashing this Fastboot rom
Download the rom/extract it/open the folder /use first install.bat with the phone in Fastboot mode
https://sourceforge.net/projects/xi...13.0.5.0.SLDCNXM_v13-12-fastboot.zip/download
then install the TWRP and update the rom via OTA (do not put any security on the lock screen).
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img​
then in Twrp go to Advanced -> flash current TWRP->reboot TWRP
If that doesn't work/see post https://forum.xda-developers.com/t/...need-urgent-help-please.4491461/post-87424405
Click to expand...
Click to collapse
Thank you for ur kind support. I have managed to flash it with mi flasher & rooted it with masgisk.

Categories

Resources