Database Develop

Le2: No recovery with MIUI 8

Hi guys,
I installed MIUI 8 through TWRP, but didn't quiet like it, so I decided to try out other ROM's like Lineage OS, but none of them would install. When I tried to reboot using MIUI which was still installed, I couldn't use the keyboard anymore, so I decided to go back to TWRP and install the SuperUser Version of EUI I have already used for quiet a while. It installed correctly, but when I rebooted my phone, MIUI somehow tried to boot again. I went back to TWRP, installed EUI, but when I rebooted, MIUI tried to boot again. The big issue is that MIUI can't really start up which means that the start screens just keeps rotating, but nothing else happens. Does anybody have an idea how to solve that problem? I never experienced such an issue. Thanks!

I solved it by just trying it multiple times. I didn't really reach my target, but at least my device is usable again.

It is not available

Beta 10 to 4.1.6 Rollback Nightmare. Help!

When I tried reinstalling Stable OxygenOS 4.1.6, the phone locks up upon install and setup screen. This goes for previous OS versions, as well. It takes force quits, restarts, and numerous install attempts and the phone still locks up. I tried stock recovery, old and new TWRP versions, all of which are clean installs, Nothing. LineageOS and other Hydrogen based roms still lock up, either at the setup screen, or when I try and activate developer options. Every Rom I tried after activating developer options, it doesn't leave the gear icon in the menu, either. It takes a restart (force quit) for it to show up. Also, WiFi doesn't work. Sometimes when I try and install OxygenOS either by sideloading, or through TWRP, the phone locks up at the wifi setup screen. This goes for every version of OxygenOS I tried. Your advice is appreciated. Thanks.

I had some problems last night while switching back and forth between Beta and stable. I could try to help but I'm not a guru at this, so wait for confirmation if you are not sure.
First I think you need the right TWRP version. 3.1.1-2 is the latest one, but I'm using 3.0.4-1 (flashed stableOOS with it) and everything is back to normal for me.
Try a clean flash of stableOOS. TWRP > Advanced wipe, select dalvik,cache,data,system and swipe.
Then install the OS. Don't reboot yet, and instead boot into recovery after going back. I read that this ensures you keep TWRP.
It may say No OS installed, but go ahead. Then boot into system again. This worked for me and I restored my backups

I just went from beta 10 to 4.1.6 and have no issues at all.
I followed the basic procedure, in TWRP (recommend to use the latest bluesparks one from his kernel thread - just TWRP no need for his kernel), I did a factory reset, (in TWRP just swipe to Factory reset from the WIPE screen where it says 'Most of the time this is all you need'), its correct nothing else needed, then flashed the full v416 file, then flashed Magisk 13.2, rebooted to system, that was all. TWRP was not lost with this method.
System booted to stable v4.1.6 and no issues.

Check what format are your partitions fornatted in. Make sure they are f2fs. Otherwise try the debrick tutorial. It helped me fix a lot of bugs on my 3T.

I tried all of the above, and I'm certain under the right circumstances, your advice would work. In the end, I used the unbrick tool which brought it back to it's original locked state, and I'm still running into issues. I wonder if there's a hardware issue somewhere that was the result of using Beta. The OS boots up and I'm finally able to access developer options, but no WiFi and the phone still refuses to restart or power off unless I do a hard shutdown. I've never seen anything like it. Numerous ROMS, recoveries, and sideload installs using the One Plus Recovery, and it still doesn't work.
Thanks for everyone's input, but I feel like this phone is done.

Stock OS taking too long too boot! Maybe Bootloop

I was in the middle of changing from Havoc OS 2.0 to Stock OOS 5.0.8 .
I flashed a new twrp version 3.2.3.1 and then flashed OOS zip file, when I booted into system it took too long to start the setup screen and never eventually did.
I suddenly recalled that i read somewhere that twrp 3.2.3.1 is being giving some encryption issues, so I thought that this might be the issue so I forced restarted the booting process (pressing power button for a while),went back into recovery , then to bootloader and changed to twrp 3.2.3.0 and then flashed the rom again.
But this time too had no success and still the boot animation (oneplus's) is going on but 3T not starting.
I had given an ample amount of time ( around 30 mins) and have even repeated the process of flashing about 3 times
(including wiping everything) but still no luck
I am worried because i know my device never took so much time to boot any rom. Please Help
Note: I still can access recovery and everything so might not be the case of bootloop ( i don't know really)
Edit: After Some Fiddling around i decided to try some other rom and surprisingly Havoc OS flashed Perfectly Without Any Problem.

Stuck in TWRP Bootloop

I tried to install the weekly xiaomi.eu rom and so far everything worked. at least that's what I thought.
When I start the phone, the mi logo is briefly displayed, turned off, then immediately showing the mi logo again and shortly afterwards the recovery starts.
I have no idea what i could have done wrong.
this is how I proceeded:
1. Device unlocked using the official unlook tools (the device is more than 30 days old and has been linked to my account)
2. ADB driver installed on my pc (also worked fine)
3. TWRP installed using ADB with CMD. (did not seem to have worked the first time because the xiaomi recovery was started but after another time with a different download of twrp it worked)
4. Copy The current weekly rom to the internal stroage.
5. Installed using TWRP.
I have no idea if I have forgotten something and have already tried to reinstall the rom several times. (even over OTG) every time it is shown to me that everything has worked fine and is done.
I also reinstalled twrp several times because I read that it may be because of it.
(the only thing that looks wrong is "E:Unable to decrypt FBE device" at the beginning when flashing or wiping)

did you format data ( type yes ) before install weekly rom ?

It's normal for twrp not to take right away.
I normally flash it like 3 times right in a row with fast boot.
I've had it reboot back to the mi recovery several times like that.
But as the last person said. Formatting data should fix the bootloop.
You should only have to do that once, then you can use the miui.eu updater within the rom from here on out.

[SOLVED] Very hard to reflash reboot

Hello everyone,
First I would like to mention i tried almost everything i can think of but a while back I lost root via incorect ota update from magisk (i guess i accidentally rebooted)
And cant seem to get it back ever since.
I tried reflashing 10.14 from orangefox, and it boots but as soon as i turn off or reboot it is stuck on splash screen. I heard that Xiaomi did botch several security updates so people tried full roms, not incremental and solved their problems, so i flashed 10.17 same story, boots and on shoutdown stuck on splash screen on the next boot
Problem is it wont even boot if i do a full recovery.zip install, only if i flash the OTA right after fastboot boot, i presumed i messed something in A/B partitions, so i installed recovery to ramdisk, twrp recommends doing a recovery bootloop fix after, which i cannot do since i get ERROR 1 something hex kernel
Also it seems to be a problem that i can flash from fastboot, but not miflash since error appears that the critical partition is locked, which i am sure i unlocked before, after all i couldn' tb
I would really like to fix it and not lose data of apps. I tried flashing 10.17 from orange fox, and doing a magisk flash from the fox addons, and again it gets stuck on splash. If I could just somehow get into te os while root so i can backup app data and run over to a Rom away from emmc bugs and the like. Really a shame that they abandoned this beautiful looking phone with mid range specs, even in its prime.
I would also like to patch boot.img from 10.17, but it seems it is not needed since i did that with 10.14, which also stuck on android welcome screen when i flashed magisk. In addition it seems boot.img is not modified at all since all files are date of creation 2008. for all firmware on that phone
Please, any suggestions, I need to do more clearer scans (which Gcams allow), and after even touching fastboot i am getting software errors all over (i am really hoping those are user errors)
Thank you for reading.

Somehow it solved itself. I know I should explain what I did but i really don't know.
Edl over adb or fastboot wasn't working so i entered it in https://androidfilehost.com/?fid=24591000424940129
the script worked, but it was not made for Xiaomi mi a2.
Then i did a miflash, but it did an infinite flashing which after 1000 seconds i aborted, then i trid it and it booted.
Few notes it wont boot when connected to a usb, and it sometimes gets into fastboot splashscreen combo if i hold fastboot while on flashscreen, after that it booted.
Maybe it is a trick for soft brick i dont know, after that i was able to reflash magisk.
I now it isn't much, but hopefully it helps someone, i was hanging onto threads, searching one error after another.