Hello @ all,
i flashed CM13 latest firmware
reboot recovery,
flash latest MM aicp + open gapps + supersu + xposed + goodix_fp_8 (for fingerprint) + Agni kernel 2.0r4
this combination gives me a bootloop. unless i dont flash goodix. then it boots.
can anyone tell me what i do wrong? it worked once to flash but it simply doesnt boots up. stucks somehow at bootscreen...
edit:!!! solved it. flashing cm13 radios as last zip and it boits!
Related
Hello @xda
I ran into some ussues lately with TWRP and M5 kernel made by @Myself5
Until last week I have been using M5-kernel with Validus ROM, and it has all been running smooth. I have been able to open TWRP during boot with volume keys and all was joy. Then I decided to try MultiROM and I got that working with the app.
This monday I decided to get rid of it and cleaned my phone.
Then the issues started. I replaced MultiROM TWRP with TWRP and flashed boot.img from validus zip. No problems entering recovery and I successfully flashed the zip and gapps for it. I used his latest version with M5 included. Booting into the ROM was not a issue and it all worked fine until I was trying to get into TWRP.
As I always do before I backup my phone, I shut it down. Then I booted it and tried to enter recovery, the purple light came on, but nothing happened when pressing any keys...
To enter the recovery i had to boot the ROM and reboot to recovery, witch I did not have to do before. I tried all possible solutions, in the end I decided to try with the kernel from a earlier Validus version, and guess what, it opened TWRP.
Is there someone that can tell me WTH I'm doing wrong??
I always do a
<fastboot flash recovery twrp.img and <fastboot flash boot boot.img
My previous thread is
http://forum.xda-developers.com/redmi-note-3/help/help-phone-reboot-5-10-kenzo-t3376650/
That's why I use CM based ROM
I had follow the instruction from : here
but I got stuck in mi logo
and the other problem is, when I flash the ROM it can't enter to TWRP recovery
to able to enter TWRP it needs to be re-unlocked and go back to MIUI via MiFlash and re-flash TWRP again
I tried to re-unlock and flash TWRP only without go back to MIUI (the process was succesful, but it can't booted up to TWRP)
The problem exist in CM13 based with fingerprint compatible
- Santhos build after fingerprint compatible
- Mokee ROM
- CM13 flour mo build
The only ROM I can't use are CM12.1 or CM13 with fingerprint uncompatible (without bootloader being relocked)
but unlike this version because the battery drain is very fast (Android OS, and system used more battery than SOT)
I can't use MIUI and AOSP because random reboot issue that I have mentioned in my first thread
Anyone please help, this phone is driving me crazy :crying:
Did you try a reflash of miui in EDL mode?
for some reason whenever I flash supersu or Magisk the phone just hangs at the MI logo with 7.6.15 global beta rom, I do the same flash method every time and this is the first time it has happened..
try 1
zcx twrp, flash 7.6.15, flash supersu, reboot and it doesnt boot
try 2
zcx twrp, flash 7.6.15, flash magisk, reboot and it doesnt boot
try 3
zcx twrp, flash 7.6.15, reboot, -boots fine
edit:
try 4 .
zcx twrp, flash 7.6.15, flash just supersu 2.82, reboot and it boots, so now I can say it has something to do with Magisk or Xposed
so I might now try to flash Magisk, but run the xposed uninstaller incase the magisk.img image still carries xposed module from previous installs this way I can narrow it down from xposed or magisk
I'm having the same issue. I try to flash Super SU after flashing MIUI 7.6.15 and I also try to flash Xposed but it hangs on the Mi logo and won't boot properly. If I hols the power button down for ten seconds to turn the phone off and then get to recovery mode by holding down the volume up button with the power button I can reflash MIUI and it works fine on its own. Wonder is it a Super SU issue? Might try an older version of MIUI....
Same issue, tried everything. :'(
Magisk and zcx super su working but not xppsed niether systemless nor solarwarez editon.
+1
just updated my phone via zcw twrp. su and magisk works fine, only xposed got me stuck at the logo.
No problem with magisk v12, boot normal
Problem with xposed v87, stuck in logo
now back to v7.6.7, and waiting for FIX
Flashed v87.1 xposed
Worked
adiversion said:
Flashed v87.1 xposed
Worked
Click to expand...
Click to collapse
Link?
Sent from my kenzo using XDA Labs
Flash the modified xposed, it's working with the latest global beta. Link:
https://forum.xda-developers.com/xposed/unofficial-xposed-miui-t3367634/page77
Btw: why u guys still use xposed? Any recommendations for modules except YouTube adaway which I should try?
the issue is with SuperSu 2.86, should flash Supersu 2.76, im in build 7.6.8+Supersu 2.76 and all works fine and Xposed not work fine in this builds
I am really happy with Carbon 5.1, but thought Oreo might have achieved similar stability
Problem is that after flashing .570 and .291 there is a bootloop into recovery when attempting to flash any Oreo boot.img
The crazy part - the device was bought used with D6502 in the settings, and after flashing .291 using flashtool? Baseband patch fixed connectivity issues - Then I pull out the MicroSD strip and lo and behold its actually D6503. Then any RR/Carbon/lineage Oreo boot.img throws the recovery into a bootloop
Immediately flash the 5.1 Carbon boot.img and things return to normal. A bit confusing here.
Apologize if this is dumb - but can I just install Oreo ROMs without the initial boot.img flash, or even on top of one extracted from Andro/Advanced Kernel?
Okay just pushed through it
I didn't flash the RR boot.img coming from carbon 5.1 N. Just RR 6.0 or 8.1 with gapps regular style and not a single hiccup. I forgot to download magisk and came back and the Recovery loop began
I decided well WTF let's try to flash magisk in between loops it does modify the boot.img. The loop stopped and I took my time flashing xposed 8.1 and the baseband patch.
RR 8.1 or 6.0 works beautifully without a hitch but entering recovery begins the loop. I am going to try flashing older TWRP versions or the modded 3.1.1 by the generous developer
Problem solved - Just installed TWRP recovery 3.1.1, many thanks to aboodyaiman - https://forum.xda-developers.com/xperia-z2/development/recovery-twrp-3-1-1-0-touch-recovery-t3640856. And as I suspected it was a boot.img / recovery issue. Now running on my desk for 30 minutes without a hitch in recovery and no problems with LOS / RR Oreo
Great work everyone ITT, congratulations all round
Anyone have any solution for the flash to work with magisk?
If i uninstall and install SU my flash will work?
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
tremalnaik said:
Replace the kernel with the MK2000, flashing it with TWRP after Magisk, and the flash will be back.
Click to expand...
Click to collapse
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
thunderc8 said:
There is an Oreo mk2000 kernel? I used it for nougat, I'll give it a look.
Click to expand...
Click to collapse
It's still a beta version, but on my phone is working perfectly.
You can find it here, in the same thread of the Nougat version: h850 mk2000 kernel
I installed the kernel and after magisk again but the flash light is not working again.
I get the same error.
I have to wipe everything again?
Never mind i just flashed mk again without flashing magisk again and its working.
thunderc8 said:
I installed the kernel and after magisk again but the flash light is not working again.
Click to expand...
Click to collapse
I get the same problem.
After flashing TWRP I do this:
don't wipe Data, but "format" data (you have to type "yes" to delete encryption)
intall Magisk-v17.1.zip
install xposed-v90-sdk26-arm64-beta3 (optional)
install driver Adreno 530 rev21 non treble (optional)
install as last zip: KERNEL MK2000 v1.0 Beta5 (for OREO)
reboot system
now flashlight works fine.
So installing "no-verity-opt-encrypt" (DM-verify) is not necessary.
P.S.
I was on Fulmics 5.5 (stock 7.x) with unlocked bootloader, the correct twrp flashing for me was this:
with LGUP
flash kdz android 7.x (flag on refurbish) (I tried upgrading directly to 8.x, but the G5 was gone in bootloop)
flash kdz android 8.x (flag on upgrade)
(the bootloader still remain unlocked, so you have not flash unlock partition with unlock.bin file)
Phase 2
Boot, skip all settings, Enable Developer, enable Debug USB and accept request permissions etc...
open ADB and type
reboot bootloader
fastboot flash recovery twrp.img
don't reboot!
remove cable, remove battery, reinsert battery
power on in recovery mode (correctly, or you have to return at Phase 2)
double yes for reset factory (to enter in recovery)
you should enter in TWRP recovery
Is there any way to fix the "flashlight" bug with the stock kernel, still with the stock recovery
and rooting with Magisk by patching the boot image beforehand and flashing it in fastboot ?
I tried using the mk2000 kernel, but no img image is provided for this, only a zip,
but I don't want to root by using TWRP and flashing zips.
Why, I want systemless root, in case OTA updates will appear.
Thank you.
Even though I'd really suggest you to install TWRP permanently (if you accidentally enter in the stock recovery, the whole internal memory gets erased permanently), you may try to install Magisk from TWRP and then flash again the stock recovery.img using fastboot.
By the way, the Magisk zip is systemless: it doesn't flash executables on the system partition; it's just packed as a zip file for convenience to be easily read by TWRP.
On the other hand, if you want both original kernel and Magisk with a working flashlight, you can't. Flashlight with Magisk only works with MK2000 kernel at the moment.
It's new version mk2000 kernel v2.0 stable version from 04 January 2019, for Oreo try it. I want to unlock BL and make root, pls tell us it is flash work ? Sorry for my English.
Wysłane z mojego LG-H850 przy użyciu Tapatalka
I din't try the latest version, but I'm currently using mk2000 with unlocked bootloader and Magisk, and everything (both root and flash) is ok.
Edit: I now have the latest version of mk2000, and I can confirm everything is ok.
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
BBCAtomic said:
My flashlight and camera flashlight are not working too. I have to back read just in case I am not the only one with the same problem. I see there is a lo of suggestion and I tried it and it worked like a charm. I used H850_v1.0-mk2000 to make it work.
Click to expand...
Click to collapse
read previous massages
https://forum.xda-developers.com/showpost.php?p=77832747&postcount=6