Hey, I'm having a problem with updating my MiA1 using TWRP since january patch. Here's is, more or less, what's happening. AOSP Pie with december security patch is working flawless. I can reinstall this .zip with TWRP whenever I can.
But since january ROM, I'm having the same problem: if I install january/february patch, everytime I boot the phone, with or without gapps installed, the phone continues with a black screen after the Mi logo and nothing happens. Actually, if I double press the power button, the phone vibrates (as if the camera was opening) and if I single press it, the nav bar acts like im locking;unlocking the phone.
What I did:
-Checked with MD5
-Downloaded boot.img from the latest stock ROM from Xiaomi oficial site (same patch as AOSP).
-Installed boot.img without gapps: the screen works
-Boot.img before AND after installing gapps: bootloop.
-February update done with a clean install and over december patch: black screen as well
Can someone please help me? I don't know what I'm missing and don't want to get stuck with an older update
Try flashing latest pie via miflash, and then custom roms
Related
Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
NiteFlame1003 said:
Hello,
hopefully someone could help me solve my issue.
i've installed the latest nightly of cm 12.1 today overwriting my previous installation of cm11 with a build from january.
the recovery i used so far was twrp.
after upgrading cm to 12.1 i can no longer access the recovery. the phone shows a black screen and reboots when i press the power button.
i've tried reflashing current and older (2.7) versions of twrp with odin but with no success.
Click to expand...
Click to collapse
You should have flashed official lollipop first, to get the latest bootloader. And you should begin there. And then flash twrp for your rom and cm12.1 using twrp.
Use a cm12.1 rom from development forums instead. E.g temaseks.
so just to make it clear for the dummy kind of user which i seem to be the necessary steps are:
1. getting a stock lp rom and flash this
2. flashing a custom recovery
3. flashing custom rom (e.g. temaseks or standard cm12.1)
Does the Phone have to be rooted for these steps? It looks like it has lost its root status with the update to 12.1 or when i tried to re-flash the broken recovery partition.
thanks for your patience.
I am on g900f.
I flashed the lastest RR rom:
https://forum.xda-developers.com/ga...opment/rom-resurrection-remix-n-klte-t3510376
, then opengapps and then magisk ... it freezes on boot.. I get the bootanimation and after a while the logo freezes...
tried 2 flashes (one with magisk flashing and one without) and tried another version.
Also tried https://forum.xda-developers.com/ga...m-cyanogenmod-14-0-galaxy-s5-android-t3476433 LineageOS and same behaviour.
Never had such an issue before... is there a specific baseband or radio to flash?
I am actually having the same issue. upon updating it locks up completely while first boot animation plays. I had to revert to the march 29th rom and update magisk. I also have a lock screen blue screen lockup issue that I cant seem to get fixed. Very troubling.....
I flashed the latest version of TWRP and it is now working fine
I am glad yours works now, I am running philz touch recovery, could you please either link me to what you flashed or tell me the name and version?
Got it updated to the newest version and all seems good for now. Thank you very much!
ok good to hear
was going to post the guide I used to install TWRP; I was actually on philz recovery too before:
http://www.droidviews.com/install-twrp-recovery-samsung-galaxy-s5/
i have flashed the FireHound-v4.1.1 [Angler] rom and gapps and i was on 8.1.0 (OPM5.171019.015, Feb 2018) so i didn't flash vandor image in first time and got error in firstboot lockscreen that i have to flash the opm 3.17 . By using twrp image flash option i flash opm 3.17 vandor then again after advance wipe FireHound rom flashed. Now device not booting up after lock screen of firehound it goes back to twrp after 2 hrs of waiting to device to bootup i flash stock 8.1.0 (OPM5.171019.015, Feb 2018) again.Now my device is keep on restarting it not even going to recovery i can go to bootloader only. I have unlocked bootloader and fastboot flash method enabled. Please help me as its my beloved device. i have already made my backup of all data.
Got any solution ?? I have the same problem.
I had a similar issue but it was on nougat 7.1.2 . Anyway i flashed the factory image and the first time it bootlooped but on reflashing the same factory image around 3rd time the phone booted up. So try that and see if you can fix it.
I want to have a Samsung Stock based ROM and a LOS/AOSP ROM on my phone and switch between them, but I can't get it working. I always end up on a bootloop at the S7 Edge logo.
My bootloader and modem is updated to latest version. I wanted to install Hyper ROM and LOS 16.
So I first installed Hyper ROM, downloaded the latest version of Dual Boot Patcher, open it, allow root access, go to ROMs in the app, select my System to set the kernel. Then I go to patcher section, add the LOS-zip, gapps-zip and magisk-zip (does magisk even work with this? have tried without but also no luck) and patch them as secondary. I reboot into recovery, flash patched LOS and gapps, reboot aaaand... I'm stuck at a bootloop.
This seems to happen no matter what I try, how I switch them around, also if I patch the Hyper ROM zip as primary first. Nothing seems to help. Am I doing something wrong here?
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.
Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...