Search results

Having the same problem on OnePlus 7, Anroid 11, on Q it works fine. Magisk 21.4 A/B YEes SAR yes Crypto File Ramdisk Yes Sometimes, it gets stuck on boot, sometimes I get the following: Boot reason : RescueParty Unable to parse kernel log. For more information, adb pull /mnt/vendor/op2/rbr_log...

GREAT, that tool is awesome.

Try Mauronofrio's Tool-All-In-One Try Mauronofrio's Tool-All-In-One: https://forum.xda-developers.com/oneplus-8-pro/how-to/tool-tool-one-driversunlocktwrpfactory-t4103509 I use it and no problems anymore

will this work on MIUI 12? Hi, will this work on MIUI 12? Thanks

Could be a Magisk module causing it Could be a Magisk module causing it - had this on 2 phones with 2 different providers - deleted all Magisk modules -fixed it

Could be a Magisk module causing it Could be a Magisk module causing it - I had this problem on 2 different phone with 2 different providers and when I deleted all Magisk modules, it worked again.

Could be a Magisk module causing it Could be a Magisk module causing it - I had this problem on 2 different phone with 2 different providers and when I deleted all Magisk modules, it worked again.

I am unable to figure out and find the correct xXx version for my OP7 on Q? Any help is higly appreciated. Thanks

It is stable as long as you do a CLEAN FLASH. I tried a dirty flash and device reboots every 5 min.

Radio broken after flashing Magisk I flashed the newest Q-Beta: OnePlus7Oxygen_13.W.11_OTA_011_all_1910081730_50fc71487fcf4334.zip. I installed TWRP: twrp-3.3.1-72-guacamole-unified-installer-mauronofrio.zip Up to this pont, everything was working fine Then I used the Payload Extractor to get...

Since when does Xposed work for Android 10 or did I misunderstand something? Do you refer to something else than the Magisk module for Xposed?

THANKS, how did I overlook this bloody typo

How did you do it? I just tried it for FUN: C:\adb>fastboot flash revovery twrp-3.3.1-46-cepheus-mauronofrio.img target reported max download size of 805306368 bytes sending 'revovery' (65536 KB)... OKAY [ 1.633s] writing 'revovery'... FAILED (remote: (revovery) No such partition)...

For me, I don't consider a "soft-brick" dangerous. Once you get into rooting, soft-bricks will happen. I use Mauronofrio's great All-In-One-Tool if I have to go backwards or un-brick.

EDIT: I got TWRP to work and stick on RevOS, Android 10: fastboot flash boot twrp-3.3.1-46-cepheus-mauronofrio.img Flash recovery didn't work!

As far as I know, TWRP will work on Q only once, and only like this: Flash once again with 46: fastboot flash boot twrp-3.3.1-46-cepheus-mauronofrio.img Unplug the cable after fastboot is finished with flashing. After first flash don't use fastboot command to boot into twrp! Hold vol up and...

Flash once again, unplug the cable after fastboot is finished with flashing. After first flash don't use fastboot command to boot into twrp! Hold vol up and power until the phone reboots. ---------- Post added at 13:53 ---------- Previous post was at 13:51 ---------- What exactly do...

I tried and I can't use any Android 10 on my Mi 9! REASON: De-Bloating soft-bricks the device. I went back to RevOS Pie and all is fine now.

I use the pattern in TWRP and it works. It should automatically recognize it from the settings in the OS. ---------- Post added at 04:16 ---------- Previous post was at 04:11 ---------- I will flash it tomorrow and report back the results. I'll take the risk for you

Stock contacts are broken, I use Google Contacts. they work fine.

Had the same problem and resolved by a dirty flash -over. Has nothing to do with you router. On 10 this happens sometimes.

I set it as the default dialer made sre all permissions are correct and I have no dialer, I can only call out from contacts, no way to hang up or take a call. When I go to: "Installed from the Play Store" and click on it, it opens Play Store and says; "This app is incompatible with your device"...

Hi, I really LOVE your great piece of awesome work. It solved a million problems for me. It seem that the following option # 3 is removing the OOS Dialer. I can still dial from Google Contacts but I can't hang up nor receive calls. I reverted to option # 0 and all is fine with the stock...

Same happened to me but after a dong a dirty flash over it workes now fine.

I am running the latest Windows 10. When I use the "Update" inside the tool, Windows reports: "This program cannot run on your PC". When I run the version downloaded from the original threat, it works fine.

FX works just fine for me.

Thanks for such great: "Deutsche Wertarbeit" - it works like a charm and finally, I am able to de-bloat!

can i straight up update the phone via the normal way? YES, you can, no formatting

OnePlus 7 stable Android 10 doesn't like to be de-bloatet. In Q-Beta, I was able to heavily de-bloat, now this is happening on stable OTA, Android 10: 1. Checked slot, active slot was “a” 2. Flashed OTA Android 10 internal 3. fastboot --slot all flash boot magisk_patched.img 4...

You need the correct version for your ROM! Use "Payload Dumper" https://androidfilehost.com/?fid=818070582850510260 Extract boot.img Transfer to device Patch with magisk Transfer to PC Flash

Then, my problem must have been the old TWRP and Magisk versions. Just tried again, now it works, no more Qualcomm crashes! Thanks UPADATE: 1.) Flashed TWRP installer in Magisk again. 2.) Flashed Magisk-v19.5-16b40096(19402).zip in TWRP – not the magisk_patched.img 3.) NOW...

TWRP gets lost when upgrading to Q and you need to boot from ADB into TWRP and use the installer. There is NO going back to PIE with TWRP, only a full down-grade will do it! Are you talking Android 10? ---------- Post added at 02:16 ---------- Previous post was at 02:13 ----------...

I don't get your question?

OnePlus 7, 1903 After update to Android 10, on the second boot and all subsequent boots into recovery, I get a Qualcomm crash. I did the following: 1.) Updated OS with official stable 10 which was suggested by Oxygen Updater: OnePlus7Oxygen_14.O.20_OTA_020_all_1909172052_2ac103c26f8.zip...

Thanks for the idea, will try right now. ---------- Post added at 23:17 ---------- Previous post was at 23:04 ---------- Did a clean flash and used Canary, so far everything fine, Thanks

Hi, maybe anyone can help me? On my Mi9, I flashed RevolutionOS 9.9.21 over xiaomi.eu_multi_MI9_9.9.3_v10-10 and evreything worked fine until I flashed MAGISK 19.3. Since then, I get constantly: "android.process.media" keeps stopping. I tried clearing cache and data of Gapps, re-installing...

WOW! Again you did some GREAT work, Thanks!

There is no TWRP for Q!

Hi Frank, since this is my tool, please go to the link and ask the dev.

Does this work on Q-Beta? If yes, in what mode does the phone need to be in? Thanks

Now why in all the world would you be so ignorant to DEMAND updates at least once a month? If you think that the ROM needs upadates, you can write them yourself or send 5.000 USD to andr68rus

Some chinese sellers like GearBest change the ROM to international and include EU-Power-Adapter. They also have very good tech. support and flashing guides. Smaller sellers, especially on AliExpress will sell you the chinese version with chinese ROM and no adapter. Never the less, you can unlock...

Hi, sure you can do it manully or use the tool, as you wish. Best Luck

Check this out, this will fix it: https://forum.xda-developers.com/oneplus-7-pro/development/tool-tool-one-driversunlocktwrpfactory-t3930862

Sorry, I sent it to you by mistake ---------- Post added at 02:26 ---------- Previous post was at 02:24 ---------- I just found a tool that will make the entire process very easy: https://forum.xda-developers.com/mi-...loops-t3818900

You have to download the ROM, then go to: "Local ROM file"

I just found a tool that will make the entire process very easy: https://forum.xda-developers.com/mi-6/themes/xiaomitool-bootloops-t3818900

Of course it works with EEA Rom. But with your vage description, nobody will be able to help you. WHAT EXACTLY is you trouble? DESCRIPTION???

I did a little Night-Shift for you, wrote these instructions for you and made file that should fix your GPS-troubles. Here the instructions: 1.) FIRST OF ALL: Make a BACKUP of all the data that you are not willing to lose! 2.) If you clean your Google Library of all unwanted apps, then...