yashsingh1/xdaforums huggingface dataset:
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] :
Nice android 10 rom

Nice rom

Having some issues like after applying some system settings the rom restarts automatically...

When i installed Nova launcher,it restarted.

I have also noticed some features missing,

The geusture of stock asus is missing...only buttons are available.

Some customisation features like

1. Changing QS tiles

2.fonts

etc

Are missing...

I haven't tested any games yet....

I think stardust won't disappoint us....!!

I have found that Banking apps are also not working
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] camaroamarelo:
SAR or Non-SAR?

Edit: It's Non-SAR

Edit 2: I think the ROM need a little more work to make it stable.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] wintage4davin:
Noob question, Which one is better System As Root or non SAR?

Also can use Google pay in this ROM. I don't want root, just need to pass safety net.

If I use non Asus way to unlock the bootloader help in anyway?
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] camaroamarelo:
In practice there is no difference.

Can't help you about Google Pay information.

Unlock bootloader method will not interfere.

You should also use non-official unlock since you can relock it if you need.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] rajeev88in:
Rom needs much improvement.

1. Stuck most of the time. Needs Restart.

2. More customization

3. Inbuilt camera has no portrait option. Changed it by using another Gcam

4. Phone identification in XDA as Asus Rog Phone II

5. Gapps must not be included. Should be chosen by User.

6. Face unlock not available.

7. Battery backup improvement needed.

8. Pixel launcher should be replaced by Lawnchair or Ruthless Pixel Launcher

9. Sound quality is low

10. Call recorder must be included.
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Viperpranab:
When i try to flash magisk,the phone does not boot up
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Akibtech:
Few bugs and suggestions

1.Navigation gesture not working after changing dark to light theme,need to restart

2.ram manegement is average compared to pie on stardust kernel

3.Charging speed is slow even on lower Temperature

4.Battery Backup Is Average,Idle drain need to be fix(7 to 8% drain at night in 7 hours)

5.Network Indicator Sometime Not show

6.NXP Should Be Included

7.Three Finger Screenshot Missing

8.Launcher should be replaced By Latest Lawnchair As default Launcher does not have dt2s like features and customisation
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Freegeeek:
Wait mate the os source is still beta boi most will be fixed soon
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] tcpcd:
sometimes FP not work, but rest is good and smooth

---------- Post added at 11:39 PM ---------- Previous post was at 11:37 PM ----------

i have never face battery drain issue. i got 2% drop on night

and charging speed is slow, i can confirm

---------- Post added at 11:41 PM ---------- Previous post was at 11:39 PM ----------

mine inbuilt gcam not working, somehow it stuck on shutter button

i tried every possible way to get working but no solution found.

+1 for the rest point

---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------

use magisk v20 or 19.1

if you stuck on bootloop then press power button and reboot (I FACED THIS ISSUE)

---------- Post added at 11:45 PM ---------- Previous post was at 11:43 PM ----------

well i have magisk and phonepay with magisk hide enabled, and works welll
[Asus ZenFone Max Pro M1  ROMs, Kernels, Recoveries] Kandolito:
Im in 058 now

Can i direct flash this rom or need to downgrade in 053?

Thank you
[Google Pixel 3 Questions & Answers] Pink Unicorn:
Recently I am receiving a new error with my Pixel 3. If I use Google Assistant it works perfectly with my voice being recorded as well as keyboard voice input or any voice recorder. Thought when I use apps that require mic for live calls like Discord, Google Duo, Skype or Telegram they do not receive any input and sometimes they do not even provide any output. So basically I cannot talk and sometimes I cannot hear other people talking either.

This is extremely annoying. I am not even able to talk to people because of this. I used bluetooth headset and native pixel headphones during these calls and none of them worked properly.

Anyone ever stumbled upon anything like this? It seems like apps do not receive right permissions (even though I've manually set them) or something else software related. I do not understand how to Google this issue either, most issues are about mic being broken physically or something similar. Any suggestions? I appreciate your attention.
[HTC Excalibur] DotStig:
Trying to do some homescreen design and I'm wondering if anybody has the analog clock plugin? If so, would you care to share? Thanks in advance
[HTC Excalibur] DotStig:
Ok, I found the RJTime one, any others?
[HTC Excalibur] Rip Syntaxx:
I don't know of any, but if I run across some I'll let you know.
[HTC Excalibur] DotStig:
Thanks, appreciate it.
[Nokia 6 Questions & Answers] piechan:
my nokia 6's battery has been drained out and has switched off. the power button is broken and i need help on opening it. i have tried all the usual methods (of opening an android without a power button) and they don't seem to work.
[Nokia 6 Questions & Answers] Yakia:
maybe you can try to reboot on download mode with ost la and then type fastboot reboot ?
[Magisk] VAnylO:
Hello,

I'm using Android x86 in Virtualbox and managed to install Magisk by creating a boot.img and let Magisk Manager patch it, then replace original kernel and ramdisk.img.

Magisk shows as installed and managing superuser rights works, but I can't install any modules. From what I understand from the logs, Magisk couldn't mount the system block.

thanks in advance for any help!

Here are screenshots, the magisk logfile and a mount output:

thanks in advance for any help!
[Magisk] i5510:
Unfortunately, I'm facing the same problem here.
[Magisk] jscheah:
Same here. Most of the modules went missing.
[Magisk] i5510:
Milestone

Thanks to [MENTION=5550662]youling257[/MENTION] finaly there is some hope that Magisk will soon work on Android x86. ;)
[OnePlus 7 Pro Questions & Answers] wr3zzz:
My understanding is that 7pro has a built-in DAC but I already have a dongle with Hi-Res DAC built-in and don't feel like spending $15 for a passive dongle just for comparison.

Am I hearing the phone's DAC or my dongle's?

PS: I don't listen to any source with higher sample rate than lossless CD quality.
[G3 Q&A, Help & Troubleshooting] ehsanonlineco:
Hello everyone

My G3 (d855) (fulmics 8.0 ) started restating yesterday. when I turn it on, it restarts on lg logo before android come up and it stucks in a loop.

At first i thought it's a software issue and I did a factory reset usinng TWRP but still the same issue.

I reprogramed the same rom and then I programmed Official rom and still the same.

Today I found sth out. sometimes phone starts normally or after just one bootloop when the charger is pluged. so i think the battery may have problem.

I tried using a power supply to turn the phone without battery but it stuck again in bootloop. (phone draws 1.1A max)

any idea ?
[Android Head-Units] Imaginati0n:
Hi

I just bought this radio 1GB/16GB:

https://pt.aliexpress.com/item/Silv...167.html?spm=a2g0s.9042311.0.0.2742b90apiEUzI

I'm new on the Android Car radio. I already intalled the unit all is functioning well. But mine came with the version 6.0 of android. The seller already sent me a lot of firmwares to flash but or they didnt run or the one it worked kept the radio on 6.0 version. (8227L UI06-firmware_v14_20190219.zip) - I uncompressed the two files for the root f the external sd.

Anyone have a firmware for this model? I can send the name the firmware that seller sent me that worked but kept the model on 6.

FOr updating the seller told me to make a reset and put five fingers on the screen.

By the way I was waiting for the update to see if the function will appear but this firmware doesnt have a favorite contacts widget so it's easy to call contacts. I tried some alternatives from google play but when dialingit said i cant find the phone app. Anyone knows an alternative to solve this situation.

Thanks in adavance and I'm familiar with android but this is my first car radio. :)
[Android Head-Units] Imaginati0n:
Is there any post regarding this model? I didnt understand yet if they are OEM with different layouts or if its a need for the seller release an update...
[Android Head-Units] Imaginati0n:
I see that this forum is not very active like other xda :( ....It's my first time with a car radio and there isn't one person who can help...
[Android Head-Units] ighostsgunnaz:
search thread for 8227l firmware or youtube ighostsgunnaz. i believe i have android 9 file that is for touch only. i needed file for touch and key press (volume knob). am uploading zip fiiles to file share host now hope u see and it helps.
[Samsung Galaxy J7 (2017) Guides, News, & Discussio] chichareal:
https://www.sammobile.com/firmwares/galaxy-j7/SM-J730F/PHE/download/J730FXXU4CSF1/275072/
[Samsung Galaxy J7 (2017) Guides, News, & Discussio] waledakmal:
can you reupload to another link cause sammobile not download here redirect to premium .. Firmware Spain
[Xperia Z3 Compact Q&A, Help & Troubleshooting] theoneill:
Hello all,

I am pretty sure my problem has nothing to do with Carbon ROM, but one of the symptom I have is the unability to perform OTA update from CR-6.1, I ask for help here instead of on the ROM thread in case someone experienced the same :

- I used TWRP to flash CR-6.1 on a Z3C with TWRP. I unlocked the bootloader and flashed the recovery using fastboot (fastboot flash recovery xxx.img).

- CR-6.1 was properly flashed, boots without issues, but then if I try to reboot on recovery from here (using the power menu), the phone just reboots, and won't go to TWRP. Then it seems logical that when it tries to reboot on recovery to perform the OTA update it fails, since it just reboots to CR.

- My only was to access recovery is to press the down volume button while powering it up : It boots to TWRP successfully

- But then, if I try to manually flash the .zip file downloaded by the OTA, I get an error message (error 7): The devicename does not match, TWRP (official release 3.0.2-1) detects the phone as "". Note that with unofficial release 3.2.3-0 found here I get no error 7 message : The manual flash is successful.

I checked other posts here on XDA, one solution would be to just modify the device name in the .zip, then it works but I wonder if all these are not a symptom of an incorrect TWRP flash as recovery. I tried to reflash it from TWRP, unfortunately, it only proposes me to flash to boot. Flash to recovery is not available.

Thanks for your help!

Lionel
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Fudgemond:
I'm dealing with this exact problem on my wife's phone. I've made progress though. First up, boot into bootloader, "adb reboot booloader", then boot into recovery, making sure you have a suitable twrp image on your desktop, "fastboot boot twrp-3.2.3.img". Now you're in TWRP, which is where I now am. I'm going to wipe the recovery partition, boot back into the bootloader and flash recovery. Let's see how that goes.

---------- Post added at 11:29 AM ---------- Previous post was at 10:59 AM ----------

Ignore the above, got it working. It seems that the version of CarbonRom is playing funny for some reason. Here's the recipe to fix things:

- On the phone, check and download the latest CarbonRom. Don't flash it.

- Run "adb reboot bootloader"

- Run "fastboot boot twrp-3.2.3.img"

- In TWRP, install the latest CarbonROM from sdcard/CarbonDelta

- Reboot

- Reboot back into bootloader, "adb reboot bootloader"

- Flash recovery, "fastboot flash recovery twrp-3.2.3.img"

- Run "fastboot reboot"

Everything is back the way it should be.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] NeoArian:
Good Morning,

I am the dev of the LineageOS 16 builds for this device and i have been working on a new TWRP tree. Therefore i have found some things according to you problem.

First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0

To make this work there is this binary to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.

According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits

However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm

So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://xdaforums.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.

I hope i presented it clearly and in the right way,

Have a nice day!

EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Fudgemond:
Hi NeoArian,

I've been away for a while and have just gotten back to playing with the z3c. I still have problems but that may just be my misunderstanding of things.

When the phone is in the bootloader, I update FOTAKernel thus:

fastboot flash FOTAKernel twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'FOTAKernel' (13264 KB)...
OKAY [ 0.419s]
Writing 'FOTAKernel'...
OKAY [ 0.885s]
Finished. Total time: 1.322s

And update recovery too:

fastboot flash recovery twrp-3.3.1-0.3-z3c.img
target didn't report max-download-size
Sending 'recovery' (13264 KB)...
OKAY [ 0.421s]
Writing 'recovery'...
OKAY [ 0.878s]
Finished. Total time: 1.318s

Yet I'm unable to boot into recovery.

From the bootloader, I this is what I see if I try boot directly into recovery:

fastboot boot twrp-3.3.1-0.3-z3c.img
Downloading 'boot.img'
OKAY [ 0.419s]
booting
FAILED (remote: dtb not found)
Finished. Total time: 0.499s

I've read through quite a bit of the forum notes but still am no wiser. I do however much admire your work and that of others and the time you spend helping others.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Fudgemond:
I now think this isn't correct. Work I've done on another phone (Xperia Z) suggests that unpacking CarbonROM and extracting the boot.img is what I should flash to FOTAboot. Something to try.
[Xperia Z3 Compact Q&A, Help & Troubleshooting] liberteus:
Did you manage to get twrp to work again? I want to move away from CR6.1 to LOS16 or 17 (just to give it a try), but I'm stuck now.
[Meizu MX] dape16:
Is there a way to flash an international ROM (ex. 6.2.0.0G) on a MX4 Pro running 4.8.2.1 CN?

I have tried to root with Kingroot 4.8.5, 4.8.9, 5.0, 5.3.7, Kingroot PC and Farmaroot without success.

When trying to login with my FlyMe account there is no way to enter country code, so I can not root that way either.

When trying to update using a G-firmware in recovery it says it's corrupt.

Is there a specific CN-firmware I have to use to be able to get root with Kingroot or other tool?

Thanks.
[Huawei Mediapad M3 Questions & Answers] Lothgar:
Hi everyone, yesterday I unlocked and flashed TWRP on my CPN-L09 following this guide.

I successfully rooted stock with latest magisk, the only problem is that the fp sensor stops working.

After some research i've found this issue on magisk github: https://github.com/topjohnwu/Magisk/issues/862

Some users are reporting fp sensor problem with magisk 18+.

So I would like to try patching boot.img with magisk 17.3, do anyone knows a way to do it? As magisk manager tries to download the latest version.

Also I paid 15€ on easy firmware to download the FullOTA of my tablet so I can restore as it was. Really dont know if I can share a mirror with that file, and I have some credits that im not going to use so, if someone need the full ota I could share it. Again I dont know if sharing a mirror is against the rules so let me know.

UPDATE:

I successfully rooted my CPN-L09 (Mediapad M3 Lite 8 LTE) using a custom recovery that I made.

You can find the recovery here: https://mega.nz/#!9VdlRKaQ!jgUX6n9lIK1Ey-c9gk2fegHmjtgYtbPO6bum05Q5RCk

Ignore the errors while flashing, also I didn't test other twrp functions so be careful this is my first time making a custom recovery.

Steps for rooting:

1- Flash recovery using fastboot "fastboot flash recovery recovery_magisk.img"

2- Enter recovery power button + volume up

3- Flash this magisk version.

4- Boot and install this version of magisk manager.

5- Disable update check for magisk.

6- Enjoy root with fp sensor working.

As usual im not responsible if you brick your device. You do everything at your own risk!
[Touch Dual, MDA Touch Plus ROM Development] sgash:
Heeelllp!!!

I installed opera 9.5 on my 20 keys keyboard touch dual, it's the touch diamond grabbed version.. I found it in this post http://xdaforums.com/showthread.php?t=393740

but since I installed it, when I hold the sym/xt9 button nothing happens, the alt button doesn't work too... anyone can help me to reenable the keyboard?

I uninstalled opera but nothing changed....

thank you very very very very very very much!!!!!!

Sgash
[Touch Dual, MDA Touch Plus ROM Development] sgash:
I found this thread....

http://xdaforums.com/showthread.php?p=2144958

I uninstalled pocketcm keyboard and all returned working...

:rolleyes:
[Touch Dual, MDA Touch Plus ROM Development] mjanek20:
yeah ok ... I've flashed my device with Mary 0.2 rom with touch.dll from s600. It worked well BUT I still have problems with the keyboard!!!

In most standard Windows apps it seems working normal. SMSes and emails are fine and stuff but e.g. in Opera I get only numbers ... The same in Java apps. Does somebody know the solution for that??? I've already enabled T9 in rom options and made a hard reset if that would be your fix ...

Please help !!!
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
Hi,

soo I wanted to go from a Android 6 RR ROM to the newest Android 9 one.

Flashed new TWRP, and then the ROM using TWRP. Didn't boot, I looked it up and found that I needed to flash a 2.5 or 3.5 ZUI first.

I tried flashing a 3.5 ROM for about 5 hours using QFIL, with various errors (pretty much tried everything).

I was finally able to flash it using a 2016 MiFlash version (it reported "success").

I then plugged out the phone and tried rebooting it. Now, whatever I do (even just plugging in the cable), it vibrates once, and then over and over again every 12 seconds or so. No LED flashes.

I tried every possible key combination to get it back into EDL, unsuccessfully (while having to disconnect the battery lead each time because I can't get it to turn off).

I would greatly appreciate any help, as I'm now completely lost here. I've never seen a phone that is able to be bricked that hard before.

Kind regards
[Lenovo ZUK Z2 (Plus) Questions & Answers] P650SE:
I bricked my Z2 Plus on two separate occasions whilst trying to flash ROMs. The first time I was able to get into EDL mode using the hardware buttons on the device, but it was incredibly difficult and relied on precise timing because the device was stuck in a reboot loop to the bootloader screen, hence it kept switching off whilst trying to do the button combination.

The second time I bricked this phone, I was unable to get into EDL mode using the hardware buttons. So I had to resort to making a 'deep flash' cable using the USB Type-C cable that came with the device. You have to strip the coating off the cable and then stick a pin through two of the wires to force the phone into EDL mode.

There's a guide here that I used to help:

https://zukfans.eu/community/thread...-from-hard-brick-state-9008-mode-easily.3504/

Alternatively you can purchase a proper 'deep flash' EDL cable from somewhere like eBay or AliExpress. It's just a normal USB cable with a button on it that you can press to get into EDL mode. Hope this helps.
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
Thanks. I managed to get the phone into EDL mode by making the cable suggested, but I still find myself unable to flash anything properly. The port shows correctly as Qualcomm HS-USB QDLoader 9008 (using Qualcomm driver 2.1.22).

I now tried flashing a 2.5 ROM and the 3.5 one again using MiFlash (version 2016.03.30.0) and it fails with various errors (Reached EOF while receiving hello packet etc.).

Trying to flash using QFIL (version 2.0.1.1, installed using QPST) gets me this error:

14:43:15: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
14:43:15: ERROR: function: sahara_main:924 Sahara protocol error
14:43:15: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download

I already tried many of the steps suggested to fix that (like shortening the path etc.), but even before bricking I could only get past the Sahara Fail error a few times.

Thanks a lot
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
I tried again using MiFlash and it got to flashing but crashed in between with

Fatal Error(0x8000ffff: Send configure command)
[Lenovo ZUK Z2 (Plus) Questions & Answers] JV Spartacus:
Install latest qfil ,load rom in it

Click on download as soon as phone boots to edl
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
I installed it from QPST.2.7.460.zip, is that the latest version?
[Lenovo ZUK Z2 (Plus) Questions & Answers] P650SE:
I think QPST 2.7.474 is the latest. I would also recommended you use QFIL 2.0.1.9 instead of MiFlash. As JV mentioned you must start the flash process quickly after the phone enters EDL mode. If there's a delay then that can cause errors to appear.
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
Ok, this is the furthest I got so far:

https://pastebin.com/EQgXDwEe

And the last (relevant) lines from the mentioned logfile:

https://pastebin.com/3ZmMiBZA

Do I have a damaged image file? I downloaded it from this thread (This file: http://cdn.zui.lenovomm.com/downloa...SER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip)

Thanks
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
Got a little further with the 2.5 Image, but not quite there yet:

https://pastebin.com/c0xGg2qy

Is it a connection problem?
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
I finally managed to flash 2.5 using QFIL and get the phone to boot again. Thank you very much!
[Lenovo ZUK Z2 (Plus) Questions & Answers] d0ntflash:
This is how you make a proper "deep flash" cable guys :p

Cheers!