Hi all,
I'm on MIUI EU rom with bootloader unlocked (no modifications, no root) and would like to report a strange issue. I can only use SHRP instead of TWRP-grus.
If I use current TWRP-grus the phone will aways boot into bootloader. With SHRP everythis is fine, but recovery has to be flashed first and boot to it from bootloader. Power / Vol up won't work.
I still flashed VBmeta and wiped/format data partition. The problem is that I can't boot into SHRP or TWRP using power/vol+. The phone will aways boot into bootloader. It seems that SHRP or TWRP can't be flashed permanently. I will have to use fastboot commands to flash SHRP first and afterwards boot into SHRP from bootloader. Otherwise I can't boot into recovery.
Can anybode help me please? Feel free to ask if anything is unclear.
any idea?
It's a common issue for grus. These issues were the only reason for me to switch back to stock.
Still hoping they will be ironed out some day so I can go back to Xiaomi.eu but not yet...
As of the latest Xiaomi.EU update (21.3.3) , updates for MI9SE are SUSPENDED which doesn't give me much hope.
Related
Today I have faced a strange situation, I installed TWRP (after unlocking the bootloader) on my OP3 as soon as I received the device then I flashed custom ROM by @Grarak http://forum.xda-developers.com/oneplus-3/development/rom-unofficial-cyanogenmod-13-t3399089.
After using for some days I decided to give Oxygen OS another try, so I wiped the cache,data,system and Flashed full OTA provided by @namanbhalla https://forums.oneplus.net/threads/...ficial-oxygen-os-roms-and-ota-updates.450783/
Every thing went smooth but after starting up I wasn't able to goto twrp, for some strange reason twrp was automatically replaced with stock recovery. OK, I decided to reflash twrp, but bang! after so many flashing I wasn't able to boot into twrp, still there was stock recovery.
Solution:
1) fastboot oem unlock (re run even if it says already unlocked)
2) fastboot flash recovery twrp-3.0.2-0-oneplus3.img
now TWRP is installed.
I not Android Developer and cant guarantee above will work and wont harm your device. Try at your own risk.
that is all not needed, i have had this happen to me multiple times reflashing Stock and Stock recovery replaces TWRP, all u have to do is boot up to fastboot mode and flash TWRP, do not reboot, use Power + Vol + and when the Unlocked bootloader screen comes up press the VOL key and click recovery and TWRP is back. no need to do the unlock bootloader again, unless u unchecked it, just make sure it is checked when flashing the Stock rom again or u can just use flashify if u rooted stock before the recovery got replaced somehow, i have even had this happen on FreedomOS 3.2.1
Hi,
i have a Helium 128G and got some problems with the radio. Currently i was on 8.1.5 following the guide
http://forum.xda-developers.com/mi-max/how-to/guide-install-global-miui8-root-t3435594
and i also officially unlocked the bootloader after this.
So i thought - to flash a new radio - it would be fine to just flash the 8.1.9 over the updater method. Unfortunately the phone rebooted in TWRP and flashed something. After this the reboot took >10 Minutes so i rebooted into TWRP and found the internal storage is encrypted now. So all data lost. Great!
Nevertheless i tried to flash 8.1.9 via Mi Flash. This worked and the phone booted but after i flashed TWRP it won't boot anymore. What is this? Is it even possible to run 8.1.9 rooted with twrp?
Thanks for your suggestions, i'm really pissed at the moment
EDIT: My TWRP Backup with 8.1.5 worked and now i have the radio from 8.1.9 and the rom 8.1.5. Nevertheless i would like to have 8.1.9 rooted with twrp
Hi! I've also experience your problem, did your phone entered recovery mode after flashing TWRP? if not try flashing the 8.1.2 ROM through EDL (power+vol up+vol down) then after letting the first boot finish flash TWRP. Hope this help
I'm not sure but at one point i saw the xiaomi recovery picture!? Now it works with my 8.1.5 backup again but is it really that heavy to just install a current version when on twrp and root!? i'm officially unlocked for that.
I wanted to install Lineage OS and was curious if I could install it without having TWRP flashed into recovery. I mean, I'll still use fastboot boot twrp, ill just won't have it in my recovery.
I'm asking because when I tried to do fastboot flash recovery twrp it said failed antirollback check. Would like some help if possible
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
corkiejp said:
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
Click to expand...
Click to collapse
Thanks for your help !
Anti rollback is such a pain in the ass.
Hi guys,
after flashing china stable MIUI 12 and wanting to root again with custom recovery and magisk i got the problem as follows:
Device was blank, flashed TWRP through fastboot, then updated to SHRP.
With SHRP i flashed the china stable ROM MIUI 12 as zip file.
Booted once, system is fine, enabled developer options and debloated.
Moving magisk on the device and rebooting into recovery gave me stock recovery, so no flash of magisk possible hm.
Thought well, on stable Chines ROM now just flash TWRP once more, did like always, flashed vbmeta, flashed twrp, fastboot reboot and instant power + volume up to reboot TWRP, worked.
Now reboot leads in lost ROM, TWRP loop.
Where is the error please?
Just flashing china stable MIUI 12 once more and waiting for next step to safely root device.
so far I think, you should flash vbmeta before flashing AOSP rom, I don't know if your problem was solved or not. share your experience here so that others can be benefitted.
This is my first thread, I apologize for any mistakes or core aspects left out.
Intro/Formatting KeyBefore I start, I want to give a quick thanks to those contributing to these forums/threads, as it got me through my first custom ROM install ever! Knowing too much information is better than too little, and my want to not waste anyone's time, I'm going to share most of my experience installing the custom recovery and ROM. I will explain what I mean by custom recovery dying at The Dead Recovery. Italics will be used as commands entered in SDK tools. Bold will be used as outputs from cmd.
Phone SpecsPhone: Oneplus 7T HD1905 running Android 11 OOS
Custom Recovery: Chinese TWRP from this youtube video
Custom ROM: Derpfest R for hotdogb found here
My Install ProcessBesides needing to turning off driver signature reinforcement, the bootloader unlock was a normal process. Issues started occurring when I wanted to flash the custom recovery. fastboot reboot fastboot would not give me any feedback on the cmd prompt as it would say <waiting for devices> even though my phone was in fastbootd mode. After reading another thread, I hail married the flash using fastboot flash recovery twrp_best.img. All was great! My phone booted into TWRP, wiped the old stuff, flashed Derpfest, and rebooted. Derpfest works pretty well! (a little buggy but what do you expect from a beta build?).
The Dead RecoveryI notice the safety net with this ROM was broken, so I wanted to install Magisk to fix that issue (I wanted to use Gpay). I download the apk, do my renames for .zip and unintall.zip, and attempt to boot to recovery, but I just get a black screen! Using PWR+VOLUP allows me to reboot into the ROM just fine at least, so I didn't brick my phone. From here, I don't know what I should do to mitigate this issue. Here are my main concerns/questions.
Questions/Concerns1. Will flashing a new recovery allow me to still boot into my phone?
2. Should I use a different image?
3. Should I maybe use flashboot flash recovery_a twrp_best.img flashboot flash recovery_b twrp_best.img to flash the recovery?
Thank you in advance!