Hi,
No matter what patch I try. I still get "installing aborded" without any error. I upgraded safestrap to 3.72 I have CM 10.2 but the same problem I have when I try to install patch for stock ROM. Thanks for any help.
Related
My device's USB is not functioning, it was on CM11 final version till today morning. I tried to install CM 12.1 on it. assuming it would work. The device boots, but i dont have network (I guess baseband problem). I am stuck on the crappy cyanogen recovery that doesnt allow me to flash cm11 zip, or the backup. anything but the cm13 zip is not flashing. I cant install the baseband rils. or any other zips... need help how to fix the device.
srivmanu said:
My device's USB is not functioning, it was on CM11 final version till today morning. I tried to install CM 12.1 on it. assuming it would work. The device boots, but i dont have network (I guess baseband problem). I am stuck on the crappy cyanogen recovery that doesnt allow me to flash cm11 zip, or the backup. anything but the cm13 zip is not flashing. I cant install the baseband rils. or any other zips... need help how to fix the device.
Click to expand...
Click to collapse
Fixed : Flashed FOTA Restore and then flashed CM12.1, followed by dual-sim fix.
Trying to install any android 7.1.1 rom ( tried 4 or so). Installed twrp 3.0.2.0 i get an error 7. in dutch fout 7. Anybody an idea???
You need to flash v21c modem first if you want to flash cm based rom. Try it.
Hey guys, so I was running 3.2.8 firmware and modem (marshmallow) with latest AOKP stable (not nightly) nougat rom and things were working as they should...
Now the official 4.0 nougat oneplus oxygen rom comes out and I'd figure it's time for an update... So I do a clean install of oxygen 4.0, boot into system, and then flash twrp-3.0.2-1.28 recovery to flash aokp nougat rom.
After that I flash latest stable SuperSU 2.79, reboot and then boot back again to install Adaway systemless v2 zip
Problem is, my phone randomly un roots itself, busybox app would freeze (had to flash it through TWRP later) and Adaway won't merge hosts file.
I know it probably has to do with either latest root, the recovery, encryption/decryption, or firmware (or combination of some of these) from what I've read on the forums...
Can anybody tell me what is causing these problems and help me fix this?
I've tried installing twrp-3.0.2-0_blu_spark_v11 recovery, version 19 of bluspark's modified TWRP, and SuperSU 2.79 sr2 but I still can't get Adaway to work and system keeps unrooting...
Is it bc I have to keep the system read only in recovery? Update my partitions to f2fs? Do I need to encrypt/decrypt my device?
[HELP] Get stuck in bootanimation &then only boot to TWRP after upgrade Magisk & TWRP
I have sucessfully rooted my phone but yesterday when i upgraded Magisk from 16.4 to 17.1 and then flashed lasted TWRP, my phone some how corrupted .
After that I tried to flash Factory Image and boot TWRP portable -> Flash ElementalX 2.05 -> Magisk 17.1 -> VerifiedBootSigner-v8 -> Reboot but my phone get stuck in bootanimation about 5 min and then reboot to recovery. Then it will always boot back to recovery when I reboot.
I have searched here but couldn't find any solution.
I tried to flash ElementalX and TWRP only and my phone booting normally. But anytime I flash Magisk it can't.
Please help me, I don't know what to do next, Thank you and sorry for my bad English. :crying:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Cozmikk said:
I had the same issue as well. I think is is due to the latest TWRP update. I was running Magisk 17.1 with no issues, but once I tried installing the latest TWRP build, I was unable to boot. I even tried connecting to my computer and trying to boot using the boot.img from android. I am currently running the official release of android P. I ended up just doing basically a dirty flash of P over what was already installed to reset the bootloader, radio, etc. I'm going to just end up running the previous version of TWRP until the dev releases something that is confirmed to be stable.
Click to expand...
Click to collapse
What version of TWRP did you use?
Hello friends Im new year can you help me? My magisk wont update to 22.1 so I think I need to reinstall it and flash the latest realme ui from software update at the same time
I have been trying to uninstall magisk even if I click restore IMG it shows stock boot img doesnt exist or clicking complete uninstall will do nothing no error message or anything.
What I tried so far is
-Uninstall.zip from twrp
-Uninstall.zip from magisk module using the build v21 v22 v22.1 but it was still there.
As of now I do not have access for computer so can I also ask.
Will I be able to flash the latest android 10 from Color OS A.19 using twrp?
I know that you cannot install ota without stock recovery but I saw sometimes on some thread that they are flashing latest builds using twrp so Im a little confused now.
My phone is RMX1993 Pie Color OS A.19