I installed twrp and then it asked for a password to mount the internal storage. I looked up how to bypass this and it said on the MIUI forums to format data. I did that and rebooted the device and it hasn't left the mi loading screen for like an hour now. Please help
Also, I can't go into EDL (holding down both volume buttons + power) for some reason. It restarts I see a red LED flash and then it goes straight back to the MIUI logo.
Fastboot Flash Stock miui Rom. Instructions on the MIUI homepage.
h0LLe said:
Fastboot Flash Stock miui Rom. Instructions on the MIUI homepage.
Click to expand...
Click to collapse
I can't go into fastboot
EDIT: Okay I'm in fastboot but it isn't showing up on my computer as a device and I can't use commands. How do I flash something when I can't open twrp?
Figured it out. Using the xiaomiflasher tool and downloading latest global dev rom from here: http://en.miui.com/a-234.html
h0LLe said:
Fastboot Flash Stock miui Rom. Instructions on the MIUI homepage.
Click to expand...
Click to collapse
Okay, I re-flashed the stock MIUI and then booted up TWRP again. Rebooted from inside twrp i didnt even install anything just backed up my stuff and then it froze again on the loading screen. wtf?
Vaet said:
Okay, I re-flashed the stock MIUI and then booted up TWRP again. Rebooted from inside twrp i didnt even install anything just backed up my stuff and then it froze again on the loading screen. wtf?
Click to expand...
Click to collapse
Bootloader locked?
When you flash original MIUI you won't have trwp recovery.... You did something wrong
Okay, an update on the situation. I flashed MIUI global dev latest version with miflash through fastboot and then just remounted twrp and installed cm firmware, cm13, lazy flasher, SuperSU and Gapps and everything is running perfectly. All features are working and it's as smooth as butter. Thread can be locked now
Thread closed at OPs request
Related
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
dvaibhavd said:
I am using TWRP 3.0.2.0 It is giving me problems as shown in images below.
I tried flashing new recovery but it also couldn't get flashed. While flashing new CM 13/CM14.1 ROMs it is giving errors, but it flashes older CM 13 ROMs fine.
Click to expand...
Click to collapse
Bro wait....!!!
Is this real?
You are using too old recovery(as your ss says 2.8.7)+old boot loader..you need some work on your phone to be able to flash new cm 13/14.1.
Just head over to general thread and find how to upgrade boot loader and install latest twrp.
After that you can flash all latest available ROM.
Boot logo Problem
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Same
utkhirodka said:
Hey I have used this method http://forum.xda-developers.com/one...update-bootloader-firmware-to-t3478917/page20 and updated the BL.However after flashing CM14 I am stuck on 1+ logo.
I was able to flash stock Oxygen Rom .I want to flash CM 14 please help
Click to expand...
Click to collapse
Same here with the TZ issues. As for the recovery, the TWRP version 3.0.2-0 is the most latest one that I can flash & boot into successfully. If I flash anything newer than 3.0.0-1 my OPX is stuck on OP logo as well.
My phone is stuck at one plus boot logo when i tried to go into recovery mode or tried to start it the oneplus logo popped and goes out again and again and when i tried to flash twrp through fastboot mode it say the device is locked cant change or erase the recovery what should i do please guide me
The only recovery that will flash on mine is 3.0.2-0. I've tried flashing through Fastboot. I've even tried to use the dd command for both 3.0.3-0 official and blu sparkz v41 and it gets stuck at the OnePlus logo.
Phone still boots into OOS just fine and 3.0.2-0 flashes through the old JMZ TWRP app just fine. It's just any other method that doesn't work.
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Exodusche said:
The latest recoverys for new bootloader is 3.0.3, bluesparks 3.0.2-1 V41 or Sultans updated TWRP. 3.0.2 and under us for old bootloader.
Click to expand...
Click to collapse
Again, I tried flashing 3.0.3 and it wouldn't stick.
blackknightavalon said:
Again, I tried flashing 3.0.3 and it wouldn't stick.
Click to expand...
Click to collapse
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Exodusche said:
After flashing recovery you have to boot right into it with fastboot command then swipe to allow modifications?
Click to expand...
Click to collapse
As stated above, all it does is hang at the OnePlus logo.
Also...
fastboot boot drive:\path\to\twrp-3.0.3-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.507s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.540s
Click to expand...
Click to collapse
blackknightavalon said:
As stated above, all it does is hang at the OnePlus logo.
Click to expand...
Click to collapse
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Exodusche said:
Ok sorry what I did was keep it simple. Reflash original stock recovery, flash 2.2.3 then flash 3.1.4 and boot. Just skip everything and reboot back to bootloader mode. Now you can flash latest TWRP and should boot latest ROMs without any issues.
Click to expand...
Click to collapse
2.2.3 flashed successfully. I already know 3.1.4 will work. I'll post again if your plan completely works.
...and I'm still getting the same errors after flashing 3.1.4 through stock recovery. o.0
I'm going to start from the earliest firmware available and flash progressively from there and see if that works.
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
Go into developer options and enable OEM unlocking
---------- Post added at 02:26 AM ---------- Previous post was at 02:17 AM ----------
funkyhunky said:
Obtained phone with buggy touchscreen. Flashed CM to see if it fixed it. Didn't. Trying to go back to full stock for return
Recovered stock device via TWRP then installed what I thought was a stock recovery.img, except it wasn't - it was a CM recovery
The CM recovery only lets me boot to recovery or the bootloader - no other options are functional
In the bootloader the FRP is locked and doesn't let me flash TWRP or stock recovery
What should I do to replace the CM recovery with TWRP or stock when the FRP is locked?
THanks
Click to expand...
Click to collapse
I have just now read your post thoroughly you said that the touchscreenis buggy,is it twrp or in the system
If it's twrp don't worry I too have the same problem in the version I tried eg. 3.0.2.0,3.0.1.0,3.0.0.0
But if it's in system try factory resetting
And change smart power saving mode to performance
But to unlock frp(i suppose you have already unlocked your bootloader) just go into developer options and enable OEM unlocking option
Ok I got the stock recovery back:
I booted into the bootloader and used the local command window to fastboot boot a twrp image from my computer
With TWRP booted (but not installed) on my phone I put in a sd card with a stock recovery image, and used the booted TWRP to install the stock recovery
Unfortunately, I have not figured out how to relock the boot loader, but hopefully they overlook/don't care about that for a return - I did not root the phone
U can relock bootloader in honor5x
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
cyrusalmighty said:
I think I have a similar problem. I bought new KIW-L24, I unlocked bootloader, flashed twrp to go to RR Nougat ROM. When I started Twrp to install ROM it said "Comparing tarz 2.2 to 2.5" so I read that I had update to MM.
I went to settings>updater and started update to M331 EMUI 4.0 ROM on the twrp recovery instead of stock recovery. I have M331 ROM now but I can't fastboot the TWRP recovery anymore. It sat twrp installed successful but the EMUI Stock recovery opens up when hitting Vol. + and Power instead of Twrp.
I noticed fastboot menu shows Phone unlocked but it does not say FRP Unlocked anymore. Does that prevent me from installing custom recovery now? Please...any help is appreciated.
Click to expand...
Click to collapse
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
gopinaidu77 said:
Just delete the google account in your phone and do a factory reset. Later reboot but skip adding gmail . This will unlock frp .
Click to expand...
Click to collapse
Can the frp relocking stop me from flahing twrp? Or is it this stock rom I am on? Do you know if other people have problems flashing twrp on L24 B311 MM update? Could I have caused my issue when I updated to the official rom using the twrp? I didn't think the update would work without stock recovery but it did. I did factory resets but I still can't install install any custom recovery. Can I go back to earlier stock rom?
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
cyrusalmighty said:
I followed your instructions and deleted Google accounts and factory restored. I go to bootloader and it says Phone Unlocked but does not say FRP unlocked anywhere. I flshed twrp anyways and although cmd window shows it flashed OK when I reboot the stock EMUI Recovery opens again.
Edit: Now I use adb and mfastboot.exe to open twrp and do a backup. I don't know if I install a different rom if I will able to finally install twrp. I wonder if this 331 stock rom is the problem or FRP is issue here. Never had this problem with my Gold Honor 5X.
Click to expand...
Click to collapse
Plz boot recovery first and install recovery from twrp . This may do some help
gopinaidu77 said:
Plz boot recovery first and install recovery from twrp . This may do some help
Click to expand...
Click to collapse
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
cyrusalmighty said:
Ok. Ive never done this this way. When installing Twrp image it asks where to install? Select Partition to Flash image: Boot, OEMinfo, or Recovery. Do I just press Recovery only?
Click to expand...
Click to collapse
Select only recovery
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
cyrusalmighty said:
ok I installed image, chose recovery, and installed superSU_2.46.zip but it still only boots up EMUI Stock recovery. Unfortunately its stuck in bootloop now so now I cant even adb/fastboot into twrp anymore. Now my only option is holding vol +- and Power to install update from sd card (dload folder). I just dont kmow what FW file to use.
Click to expand...
Click to collapse
Fastboot boot recovery.img dint helped?
gopinaidu77 said:
Fastboot boot recovery.img dint helped?
Click to expand...
Click to collapse
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
cyrusalmighty said:
I ended up trying everything. I held volume - and Power to force Fastboot&Rescue Mode. I did fastboot boot twrp_kiwi.IMG. When in Twrp I install twrp_kiwi.IMG (For permanent Install) but EMUi recovery still stays.
I believe the custom recovery is installing but NOT where it needs to install.(Probably a different partition). I noticed a erecovery when I extracted an update file with HuaweiExtractor with does program. I DID get out of Bootloop by applying update from SD card (Force Update Volume - and Plug in USB cable). I rolled the FW back to B130 Emui 3.1 Firmware. I still need to fash Twrp and update this phone now.
Click to expand...
Click to collapse
So the frp lock still exists is it?
gopinaidu77 said:
So the frp lock still exists is it?
Click to expand...
Click to collapse
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
cyrusalmighty said:
Yes I think the FRP Lock is on. It only says: Phone Unlocked. Before it used to say hone Unlocked and FRP unlocked.
Click to expand...
Click to collapse
Have u removed gmail account ?
gopinaidu77 said:
Have u removed gmail account ?
Click to expand...
Click to collapse
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
cyrusalmighty said:
Yes I had removed gmail account. I went to settings>accounts and deleted Google and all other accounts. Does FRP Unlock when you unlock Bootloader?
Click to expand...
Click to collapse
U can try that
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Do following, instead of flashing your recovery.
Use this method boot and flash Magisk. Reboot back to your system and install Flashify and install your choosen Recovery with it
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
in stock rom you need to flash magisk right after flashing twrp else it will get replaced by stock
jonske said:
Hi peeps
New Pocophone owner here. I got my bootloader unlocked earlier today and now trying to flash the official TWRP 3.3.0.0 recovery from twrp.me, simply following the fastboot instructions on the device guide.
However every time I reboot the device, the recovery always reverts to the stock MIUI recovery?
What am I doing wrong here?
I just got the phone and have upgraded it to MIUI 10.3.6 as well. I am wanting to flash pixel experience onto it.
Click to expand...
Click to collapse
What the post above says is correct. However, if you don't want Magisk, after flashing TWRP, reboot into recovery and then into system. You may retain TWRP. However, this doesn't work for everyone.
Hi all, I fixed the issue by completely wiping my phone via TWRP and clean flashing pixel experience ROM. After rebooting on pixel rom TWRP persists.
It appears that MIUI rom has something that keeps reverting it to stock MI-recovery.
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP once more. That's it! You have just overwritten the stock recovery and are now on TWRP!! Now you can reboot to system and TWRP will remain on your device. There's no need to flash Magisk etc if you want just TWRP and nothing else.
Rowdyy Ronnie said:
If you are on MIUI and flashing TWRP, once the recovery is up for the first time, you need to head on to reboot>recovery again in order to overwrite MIUI stock recovery. So the whole process would be like this;
i) Fastboot flash recovery twrp.img (or whatever the name of the image)
ii) Fastboot boot recovery
iii) Once TWRP is up, Swipe to allow modification and then go to Reboot>Recovery and reboot into TWRP again. That's it! You have just overwritten the stock recovery and are now on TWRP!! There's no need to flash Magisk etc if you just want TWRP and nothing else.
Click to expand...
Click to collapse
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
jonske said:
I did those exact steps and it didn't work. It ALWAYS kept getting overwritten.
Click to expand...
Click to collapse
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Rowdyy Ronnie said:
Did you follow step 3? You can't boot into system right after twrp is up for the first time. You need to reboot into twrp twice before you boot into system. This is what I do whenever I flash twrp and it never failed me yet.
Click to expand...
Click to collapse
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
jonske said:
Yes, I even flashed the recovery image from within TWRP and rebooted to recovery again. Still didn't work.
Note this was on the new 10.3.6 stable MIUI release that got rolled out recently. Not sure if it has new detection or anything that rolls it back.
Anyway I have resolved my issue now all is good.
Click to expand...
Click to collapse
How did you fix it?
I should have been more careful before updating coz after the update i realized that twrp won't work on miui 13. I can fastboot recovery but the internal storage is encrypted and it shows 0 MB. I need root, so i am thinking of downgrading to 12.5 again. Can i do that without loosing data? Also how can i downgrade? Should i just download fastboot version of the rom and update it?
lakshmish said:
I should have been more careful before updating coz after the update i realized that twrp won't work on miui 13. I can fastboot recovery but the internal storage is encrypted and it shows 0 MB. I need root, so i am thinking of downgrading to 12.5 again. Can i do that without loosing data? Also how can i downgrade? Should i just download fastboot version of the rom and update it?
Click to expand...
Click to collapse
you can't update from 13 to 12.5 you need to erase all your data , it's mandatory...
Just flash the fastboot rom with Mi Flash and tick "Clean All" so after MIUI boot you can flash twrp and other ROM again
Already messed it up :-( Can you please tell me which fastboot rom i should flash... I was using eu rom but even after flashing it phone boots to mi recovery.
Hey, yesterday I flashed xiaomi eu stable MIUI 13.0.3 by their script.
To do it,
1) put the phone in fastboot mode
2) just run the script by double clicking on it, however you need the file with data_format on the end.
If your phone does bootloop and go back to MIUI Recovery 5.0 like mine did yesterday, you can fix it by wiping all data in this recovery it boots up to and then restarting the phone. It worked for me and my friend.
lakshmish said:
Already messed it up :-( Can you please tell me which fastboot rom i should flash... I was using eu rom but even after flashing it phone boots to mi recovery.
Click to expand...
Click to collapse
miui 13 is not worth to try , is just miui 12.5 with more bugs , nothing changed so flash fastboot rom with mi flash
Global v12.5.4 : https://xiaomifirmwareupdater.com/miui/mojito/stable/V12.5.4.0.RKGMIXM/
lakshmish said:
I should have been more careful before updating coz after the update i realized that twrp won't work on miui 13. I can fastboot recovery but the internal storage is encrypted and it shows 0 MB. I need root, so i am thinking of downgrading to 12.5 again. Can i do that without loosing data? Also how can i downgrade? Should i just download fastboot version of the rom and update it?
Click to expand...
Click to collapse
Just so you know if you ever need this again.
You dont need recovery at all to get root.
Just fastboot pached boot image.
DominPL421 said:
Hey, yesterday I flashed xiaomi eu stable MIUI 13.0.3 by their script.
To do it,
1) put the phone in fastboot mode
2) just run the script by double clicking on it, however you need the file with data_format on the end.
If your phone does bootloop and go back to MIUI Recovery 5.0 like mine did yesterday, you can fix it by wiping all data in this recovery it boots up to and then restarting the phone. It worked for me and my friend.
Click to expand...
Click to collapse
Oh! I think i havent wiped all data. I will try this tonight. Thanks a lot
alonsoj636 said:
miui 13 is not worth to try , is just miui 12.5 with more bugs , nothing changed so flash fastboot rom with mi flash
Global v12.5.4 : https://xiaomifirmwareupdater.com/miui/mojito/stable/V12.5.4.0.RKGMIXM/
Click to expand...
Click to collapse
Actually i was happy with 12.5 but got too excited with MIUI 13... I should have done my research. Will again flash this. Thanks for the link.
slickw said:
Just so you know if you ever need this again.
You dont need recovery at all to get root.
Just fastboot pached boot image.
Click to expand...
Click to collapse
I didnt know this.. I won't go to MIUI 13 again coz there are no recoveries for it and it cant be decrypted for now but its good to know that i dont need recovery for root. Thank you!
I installed today CherishOS A12. Tbh cool rom, doesn't work that bad. A lot better than miui though. Animations are nice and long, plus the phone is fast.
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img