Search results

Appreciate the work, dev, it is by far the most stable custom ROM for this device in my opinion, regardless of version (10 or 11). I've had no issues with the FOD or V4A. For anyone having issues with getting V4A to work, just install the Audio Modification Library module and enable Legacy...

It still does not and I don't think the developer intends to. Also, is anyone else having issues with FOD after rooting? I'm rooting the device by booting a patched imaged and then doing a direct install from Magisk. After perm root, FOD is broken.

Sorry for the noob question, but is Android Auto functioning on this ROM? I used to run MSM Xtended and every time I plugged my phone into my car to run AA, it would restart my phone. Is this a widespread issue with the other Android 11 ROMs as well?

Apologies for the late response, so I'm a dummy that likes to skim. I figured it out after work. Fastbootd does not support "fastboot boot", but regular fastboot does. jerryhou85 Sorry to bother, but please close this thread as the issue was resolved.

When you check the driver properties do they match what's in the attached image?

Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).

I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below: https://adb.clockworkmod.com/ After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and...

Nevermind, fixed by enabling "Turn off A2DP hardware offload" in Developer options.

I have to turn BT on and off a few times in order to get music playing from my car's speakers. Anyone else having this issue? I've tried re-pairing my phone to my car's receiver with no luck.

Your solution worked on my A71 (GTO). It's odd, when I tried BK's method my phone only bootloops as soon as I try booting via vol+/pwr. The the only way to fix that was by wiping data which kinda defeats the purpose of following the original process.

Anyone else having this issue alongside of excessive battery drain?

Anyone having trouble with getting V4A to work on OOS10? Everytime I open it up after a reboot, it keeps asking to re-install drivers. Any solutions?

I mean the fingerprint scanner

Pretty good other than terrible FPS performance.

Genuinely curious here, where at? I just spent money on an unlock service that apparently has its "systems down", now. I'm about to open a case with PayPal to get my money back.

bricked my a6013, lol. build ver/hw ver mismatch.

I had the same issue. Like some others have said, AEX works fine with the same install process.

Then what was the point of asking this? It's so pointless. You don't even have a legit understanding of AB yet you request support for AB.

So far so good, thanks for the ROM

Interesting, I own a hard bricked 9T. I flashed MIUI 11 on it but forget to flash the decryption zip file. After a week of troubleshooting I just f all and zapped my sda disk. Do you know if an EDL cable will work the K20 Pro instead of opening the phone and using the test point method or if...

I guess you could try to buy an EDL cable instead.

Funk Wizard Could you kindly lock this thread?

gdisk's zap doesn't wipe, I think** it deletes/zeroes the partitions on the sda disk and everything would need to be re-partitioned again. But I get you, I gave up and bought a Pixel lol. Edit: I'm going to tag a mod to lock this thread since we've all given up.

Yes but this is EDL after wiping the entire sda storage.

Any volunteers? Out of boredom and a bit of depression, I "deleted" /dev/block/sda with gdisk and now I'm met with: "System is destroyed" on boot. TWRP is gone and the bootloader relocked itself. Fastboot can't erase or flash jack since the BL is locked. I feel like if I bought an EDL cable...

I'm going to be that guy. You can help yourself to the K20 Pro device forum. Posts like these, especially with people actually reaching out to help and supporting this kind of behavior/tactic, really irks me.

I give up with this device. Best of luck.

I trailed back to your solution and found the correct path: /dev/block/sda. I was able to delete userdata (sda32) through gdisk and create a new userdata partition but after exiting, it seems like nothing has changed. When I reboot into TWRP, it still remains stuck on the splash screen and...

I was at 11 last night then messed something up. Can you try to put a rom on internal storage and see if it goes through?

apparently the k20 data partition is f2fs by default according to some forum that deals with EDL stuff.

I flashed the persist from a MIUI 10 firmware file and it didn't do anything. This was when my internal storage was accessible, after some poor choices it's inaccessible, again. If I get access to internal storage, I could check the MIUI11 zip to see if there is a persist image and flash it.

I have a Mi K20 and tried to find a solution to my issue on the device's sub forum. So far, I've only found a few people who are currently dealing with the same issue I'm facing. I think what caused this to happen was failing to disable verity and force encrypt before reboot after flashing a...

The Chinese one... I was able to put persist.img from one of the firmware updates onto internal storage and am currently flashing it. No idea if it'll work or not since it's taking forever, I'll probably give it 30 minutes.

Yes. It took me about 1-2 hours to boot into it until now. It might have something to do with the storage size.

Update on my end: I have no idea what I'm doing, but now cache and persist are the only partitions that can't be mounted cause of the I/O error. When connected to my PC, my computer recognizes the device and says that it has 11.3 GB of free storage (for some odd reason). I've done the following...

Is there another way though? We've tried miflash, .bat file from stock firmware zip, and gdisk.

I tried it, opened gdisk*** and input my userdata partition /dev/block/sda32 but when trying to delete it, it says, "No partitions" I really do not know wtf is going on. I booted into the Chinese TWRP and disabled forceencrypt, checked a file and saw that userdata is no longer encrypted...

I got into that TWRP during my commute, it took nearly 2 hours. I've tried to do some other tricks as well and it all failed. There has to be a way to fix this.

How long did that TWRP version take you to load? I'm still on the splash for a little over an hour now.

No, sadly. I tried fixing my phone earlier at work, it took about an hour to boot into Greek TWRP but froze. 4PDA TWRP doesn't boot at all, gave my phone a little over an hour this morning to boot it up. Edit: Didn't work.

I'm back waiting at the Greek TWRP splash screen for over an hour now. Hopefully what you've done works and solves the problem because this is a serious headache.

Took me around 50 minutes to get into TWRP and experiencing the same problem he has (I/O error, cannot mount etc...)

This makes sense as I remember trying to boot into stock recovery early in the morning. I woke up and it finally booted, but the recovery was in Chinese. I will give 4PDA TWRP about an hour and see what I can do. Thanks.

I seem to have hard bricked my 9T after flashing the MIUI 11 rom from xiaomi.eu. I think culprit is a totally botched/corrupted boot loader and I have no idea how it happened. I've tried reflashing back to stock through stock image .bat files, but no dice. It flashed everything but the device...

How about you request to delete this and then post your question in the right section?

No ! No !

and? ---------- Post added at 05:38 PM ---------- Previous post was at 05:37 PM ---------- Okay???

So you formatted your data in TWRP (typed in yes and all that), flashed a xiaomi.eu MIUI ROM (I used 10.3.14) and then flashed this ROM afterwards? Also you're not flashing gapps by any chance, are you?

Clean wipe, flash MIUI, then flash this ROM