yashsingh1/xdaforums huggingface dataset:
[Android General] Aresix_klmn:
The Problem of 167

(1) Very poor lens imaging ( How come dxomark mark ? Money )

(2) WeChat late question

(3) Slow charging

(4) System not smooth

(5) Full of lies

(6) Poor game experience

(7) Poor after sales

(8) Poor after-sales discussion area

(9) Someone said , Poor GPS usage

I don’t like the negative optimization that THEY don’t do THEIR part .

When you buy a Huawei mobile phone, you will find that you are talking about any mobile phone in their official forum. They think it will affect them.

You never know that you bought a mobile phone but you can't reflect any problems. The most painful thing is that they will find someone to pretend to be your own operation problem.

There are often people who say this is not a game phone, so when you have problems playing the game, it is normal.

So i want to ask , how 穩 is ?

[IMG="A1"]https://screenshot.net/tw/e6odrhq[/IMG]

[IMG="A2"]https://screenshot.net/tw/4r3ngs4[/IMG]

[IMG="A3"]https://screenshot.net/tw/1kej7il[/IMG]
[Android Q&A, Help & Troubleshooting] mshnryman:
Hey there, I use a Pioneer XDP-100R as a personal media vault, but in the case of 1 particular application I use frequently, it requires an update for continued use, but the new app version is not compatible with Android L or earlier.

Is there a ROM out there somewhere for this device? Pioneer doesn't seem to have anything new for it since 2016 :eek:

Thank you for any ideas!!!
[Android Q&A, Help & Troubleshooting] Raymond.William:
No. I am using XDP-300R(S) now.

Pioneer doesn't even release the stock flashable ROM.
[Samsung Galaxy S9+ Questions & Answers] CynicalHeight00:
If it has CDMA bands and it's rootable, why hasn't a method for enabling the CDMA bands been found yet?

"I will also add that in the past the dual-sourcing made sense due to technical limitations. CDMA compatibility for Verizon and Sprint in the US and China Telecom in China made for compelling arguments for using Snapdragon variants in those markets. However since then Samsung has introduced discrete modems and Exynos SoCs with CDMA compatibility. Indeed the Exynos 9810’s new modem supports CDMA. Samsung’s licensing dispute with Qualcomm and their recent reconciliation points out to issues beyond “simple” technical matters. The fact that the Snapdragon 845 is produced by Samsung is also a factor at play. The foundry business used to be under the same corporate roof as the SoC business making Exynos chips, however last summer Samsung has spun off the manufacturing part into a separate business unit. What this means for the future of dual-sourcing Snapdragon and Exynos SoCs remains uncertain, but for now the Galaxy S9 still continues the tradition, for better or worse."

Source: https://www.anandtech.com/show/12460/samsung-announces-the-galaxy-s9
[Samsung Galaxy S9+ Questions & Answers] Devhux:
Sure you're not confusing CDMA with WCDMA? They aren't the same thing, and the Exynos variants don't have a CDMA radio (hence why the Snapdragon version is the one sold in the US for Sprint & Verizon).
[Samsung Galaxy S9+ Questions & Answers] CynicalHeight00:
"I will also add that in the past the dual-sourcing made sense due to technical limitations. CDMA compatibility for Verizon and Sprint in the US and China Telecom in China made for compelling arguments for using Snapdragon variants in those markets. However since then Samsung has introduced discrete modems and Exynos SoCs with CDMA compatibility. Indeed the Exynos 9810’s new modem supports CDMA. Samsung’s licensing dispute with Qualcomm and their recent reconciliation points out to issues beyond “simple” technical matters. The fact that the Snapdragon 845 is produced by Samsung is also a factor at play. The foundry business used to be under the same corporate roof as the SoC business making Exynos chips, however last summer Samsung has spun off the manufacturing part into a separate business unit. What this means for the future of dual-sourcing Snapdragon and Exynos SoCs remains uncertain, but for now the Galaxy S9 still continues the tradition, for better or worse."

Source: https://www.anandtech.com/show/12460/samsung-announces-the-galaxy-s9
[Samsung Galaxy S9+ Questions & Answers] Devhux:
Interesting..... Now of course there's the secondary issue in the US at least, in that Sprint nor Verizon would still have to activate the device on their network; something they tend not to do for most devices they don't sell. I also don't believe CDMA devices use a SIM card nor the IMEI number, so you'd have to generate an ESN or MEID number manually (something that could probably be considered as illegal as changing the IMEI in many areas).

Bottom line, there's more to CDMA than just activating the radio or ensuring the proper bands are supported - at least from my understanding of the technology. Of course, I may be mistaken here just like I was about the Exynos 9810 theoretically supporting CDMA, but I still stand by my belief that it's more complicated than how we could enable Band 4 LTE on the Nexus 4 back in the day.
[Samsung Galaxy S9+ Questions & Answers] CynicalHeight00:
Verizon wireless has BYOD, so I think that rectifies one issue. Well, it's a bummer I can't connect to VZW on an exynos S9. How do I go about making it work?
[Samsung Galaxy S9+ Questions & Answers] CynicalHeight00:
View attachment 4606528

On my unrooted S9+ UAE Exynos, I got into the Mobile Network Settings. It's axiomatic that there's an option for LTE/CDMA; however, I cannot make it stick. It may be a futile option, but I don't know . Can someone test this?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] relbourn:
Hi I recently received an xdaII with windows mobile 5 on it.

However the backlight wasn't working, even if I try to hold down the power button.

Also when I try vjeschaton to toggle it on or off (the other functions work) it doesn't work, could the phone be damaged or do I need to re do the rom somehow?

(ie the backlight auto switched off when the battery and backup battery went down but on recharge a bug prevented the light coming on again)

any ideas people?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] relbourn:
further problems now, I have tried installing xda II rom Xda_II_172187_Final and its predecessor and unfortunately it wont work, its stuck at the

USB v1.06 message page it seems I have problems updating it, maybe due to vista maybe due to active synch maybe due to something else... any ideas?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] relbourn:
Resoved the 1.06 Problem, looked like it was a vista/versioning problem with activesynch

But the backlight is STILL NOT WORKING!

I know the light function is being selected because the other buttons light up, just not the backlight for the LCD

anyone got any ideas?
[MDA II, XDA II, 2060 Windows Mobile 2005 Upgrading] Rudegar:
sounds like the lcd backlight "lamp" died to me
[Moto G5 Questions & Answers] TioNacho:
Hello people, I come to ask for help that I need urgently. Well at the beginning of the year install pixel experiencie and I did not backup the efs folder, when I returned to stock I lost it and from there every day I searched for solutions and I am still looking for some. If anyone knows any effective method or not, you can help me. Thanks greetings

(Sorry for the English, I use the google translator)
[Moto G5 Questions & Answers] Andrej_SK:
There's a possible fix until the moment you flash persist or restore EFS from another phone to yours.

ONCE AGAIN, DON'T TRY TO FLASH PERSIST OR RESTORE EFS FROM ANOTHER PHONE!!!

Just root your phone using Magisk and execute these commands using adb on your PC/laptop:

Things to note before you start executing commands below:

1. Make sure that USB debugging in your phone is turned on.

2. If everything is set properly and "adb devices" has been executed, u should see popup window about ADB allow on your phone BUT ONLY IN CASE YOU ARE USING ADB ON PC WHICH WASN'T USED FOR ADB YET. Make sure "Always allow from this PC" is checked and click "OK". Re-run command one more time. You should be able to see your device in cmd window now.

3. After "su" command, you have to grant root access to adb shell within 10 seconds.

4. "adb reboot" command will immediately reboot your phone, don't panic.

5. You are doing this at your own risk.

adb devices
adb shell
su
chown -R rfs:rfs /persist/rfs
chown -R rfs:rfs_shared /persist/hlos_rfs
adb reboot

Commands have been used from this thread: https://xdaforums.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
[Moto G5 Questions & Answers] TioNacho:
Good morning!

Look I was able to recover the signal (h +) with that command but not imei. Will not you know other commands that will make him recover or some method? regards
[Xiaomi Poco F1 Questions & Answers] r0ngm0sal0:
Can any one port the mi 8 google camra port of mi 8 for poco f1. They both hv same specifications. Mi 8 is in android 1 programe. Please can any one do it???
[Xiaomi Poco F1 Questions & Answers] eLaDiio:
Just use the apk of gcam of mi8, go to the forum of mi8 and install, for me works great
[Xiaomi Poco F1 Questions & Answers] Zeggi:
I'm using this and I've tried 3 different. MI8_V1_N6_GoogleCamera-Pixel2Mod-Arnova8G2-V8.2

Not sure if there is an update out tho

Skickat från min POCOPHONE F1 via Tapatalk
[Xiaomi Poco F1 Questions & Answers] chrome6boy:
Are you using this on MIUI or on a custom ROM?
[Xiaomi Poco F1 Questions & Answers] eLaDiio:
MIUI
[Xiaomi Redmi Note 5 Pro Questions & Answers] airtelmaza:
I am on miui 9.2.13.0 (arb3) . I just unlocked my bootloader. Now i want to install dot os. But dot os required latest firmware. How can i install latest firmware without goes to arb4
[Moto E4 Guides, News, & Discussion] AesopRock127:
Thanks for posting this! Looks very comprehensive and nOObproof.... I'm going to try this out in the next few days and I will report back if I had any trouble following the instructions and let your know if I feel anything needs to be clarified. I don't foresee having any problems with this though. I appreciate you and your hard work to put this together
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
No problem. I've been reading a lot of posts of members needing more up-to-date xt1765 stock firmware, so I hope it helps some members. These are the same instructions and structural format that I use on all of my Moto/Lenovo firmware threads. The order of the command lines are set out exactly the same as those used in certified Motorola/Lenovo service centers. If you follow the instructions to the letter, there is no doubt that you'll have your device fully restored to stock factory condition.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
When I have the time to do so, I'll use these firmwares with my Android Kitchen to cook up TWRP flashable stock ROMs for the MetroPCS & T-Mobile xt1765 models.
[Moto E4 Guides, News, & Discussion] AesopRock127:
My question is if i want to keep twrp as my recovery is it as simple as not running the command fastboot flash recovery recovery.img?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Yes. It is that simple. Just be advised that an OTA will not install normally unless stock recovery is in place. The OTA installation script runs checksums for stock recovery.

The best policy is to flash the firmware in full, install any pending OTAs while running unmodified stock, then reinstall TWRP once you're up to date on the latest firmware build.
[Moto E4 Guides, News, & Discussion] AesopRock127:
Shiiiiiit I didn't think about that I have an update I'm going to try to do it if it doesn't work guess I'll redo the full process all over again..... By the way I pmd you

EDIT: 69-64-6 updated no problem And immediately offered me 69-64-9 so maybe these updates aren't large enough to worry about twrp instead of stock recovery? Only time will tell I guess
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
To simplify things, just keep installing OTAs until you are on the current build. Then, reinstall TWRP. You shouldn't have to redo the whole thing as long as you haven't mounted system as r/w in TWRP. And as long as you haven't flashed Magisk or SuperSU for root. Just reboot into fastboot and flash the stock recovery and OTAs should be fine.
[Moto E4 Guides, News, & Discussion] AesopRock127:
so i know im a pain in the ass but i followed this guide with no issues and updated fully before installing twrp and root and then couldnt install xposed and ran into a bootloop so decided to go nuclear and start over. My only issue now is after fully following this guide again my OTA updates are failing in stock recovery and when i reboot i get tons of tmobile and moto app FC issues and it says im fully updated even though i started on 69-64-3 and it failed in stock recovery it still says im on 69-64-6 and ive been on 69-64-9 before so not only do i know im not fully updatedd but these FC are driving me nuts. Trying again but does anyone have any clues what could be causing my issues? im having a lot of problems with noverity flashing right and getting the newest twrp to flash instead of only temp boot as well and i feel these issues are all cnnected somehow. I might go back to RR if possible because i was able to get my phone the way i wanted on there for the most part im not sure why stock is giving me such issues? Unfrotunately i cant provide any logs or anything because i am retrying this guide again and see how it goes and didnt think until after the fact to post this
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Follow the instructions exactly, but avoid gpt.bin and bootloader.img. Those will fail as they are supposed to, so no need in trying them. Otherwise you should be fully stock on reboot and your device should install OTAs normally.

If that particular problem persists, file corruption within the firmware package could be the culprit. Try downloading the firmware again (delete the other from your PC) and start over from scratch.
[Moto E4 Guides, News, & Discussion] AesopRock127:
Ok thanks. I will try redownloading if it persists but is there any log or anything that would help out in identifying the problem if it still persists after a redownloading of the firmware? It's annoying that stock recovery says error! With no code to help identify the issue
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
When stock recovery says ERROR during installation of an OTA, the problem is with the checksums. In other words, the OTA installer is telling stock recovery that you are not running an unmodified stock setup. You can get an error like that from just mounting /system or /oem as r/w. The installer checks your /boot, /recovery, /system and /oem partitions to make sure they are untouched, unmodified stock.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Also, [MENTION=7109762]AesopRock127[/MENTION], there is a quicker and simpler method to install stock firmware to a Moto/Lenovo device called RSD Lite. You can Google for the basic instructions.

Here's a link to RSD Lite v6.2.4: https://drive.google.com/file/d/1MwZPdifKVpR4ZTsE3SSNAFBNr6KU29wY/view?usp=drivesdk
[Moto E4 Guides, News, & Discussion] AesopRock127:
Okay so I redid this and the updates are sticking like you said I must have changed something and made it non-stock.... So I do not need the RSD Lite as of yet but I did download it. Looking into it it seems that I may use it to root my device when I get to that point? For now I'm just setting everything up the way I like it and fully intalling stock updates before I get into TWRP and rooting. The goal is a up to date stock, rooted, debloated, and running Xposed and gravitybox. Last time everything went smoothly until I hit xposed. I think it's due to my crappy understanding of selinux permissions, encryption and dm verity.... The best thing about struggling to install stuff like this is it gives you an opportunity to learn. In the past I've been able to follow guides and everything worked as stated so I had no need to get technical and delve into some of the things I've needed to on my xt1765. Thank God for XDA and helpful people like [MENTION=7383447]MotoJunkie01[/MENTION] or I would have hit this phone with a Sledge hammer or chop it in half with a chop saw like I did with the Samsung j3 ?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
That's good news. I intend on making a TWRP flashable stock ROM for the xt1765 in the very near future. Once you are on the latest stock build, if you could make a TWRP backup of your system image and boot image and upload them, I could use the images to cook up an up-to-date stock ROM for the xt1765.
[Moto E4 Guides, News, & Discussion] AesopRock127:
Absolutely. will do this ASAP. Seems best if I do nothing except boot into TWRP and make the backup? Or can I flash it and it will still work? Basically is the stock recovery needed or can I flash TWRP before I make the backup

so system and boot only or system, system image, and boot? making one now with both systems and one with just normal system since im not sure which you need and dont want to give you to much **** to sift through. also does data need to be decrypted for this to be helpful to you? sorry dont know much about it but am willing to help lol
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
System image and boot backup with TWRP. Encryption of data isn't relevant to the backups. Whether you boot into TWRP or flash TWRP ....either will work
[Moto E4 Guides, News, & Discussion] AesopRock127:
[MENTION=7383447]MotoJunkie01[/MENTION] Nanodroid backup of encrypted fully uptodate stock system and boot.img only https://ufile.io/b0x6q

uploading the one with the system image too
[Moto E4 Guides, News, & Discussion] DB126:
Also verify checksums (MD5, SHA-1, etc) when offered. Fastest way to validate large file integrity. As a matter of practice I never flash critical partitions sans checksum validation.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Excellent point. A corrupt flash to a critical partition can equal lights out -- the proverbial hard brick.
[Moto E4 Guides, News, & Discussion] AesopRock127:
[MENTION=7383447]MotoJunkie01[/MENTION] https://ufile.io/phy2l 2nd one with system, system img and boot img

[MENTION=5488402]Davey126[/MENTION] i always forget thats there to help us... duh thank for reminding me
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Excellent point.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Thank you. I'll download the files and put them to use when I get some free time.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Since re-locking an already unlocked bootloader has absolutely no benefit (except perhaps for warranty related purposes) no disclaimer needs to be added. I am, however, taking up to date system and boot image files and making an up to date TWRP flashable stock ROM for both the T-Mobile and MetroPCS xt1765 models, for those members who merely want the latest stock OS versus flashing a full firmware package. I'm out on call working on the Hurricane Florence disaster, so it'll be some time before I get time to work on it.
[Moto E4 Guides, News, & Discussion] AesopRock127:
i was able to root with the newest stable Magisk 17.1 once fully updated with no issues... i just couldnt root with supersu or install xposed due to the f2fs loopback issue as i have no experience patching the boot img and it requires that for either of those to take effect. Ive heard that an earlier magisk in the 15.x might be able to do it with with the f2ffs loopback fix module but havent tried it myself and i cant speak on relocking the BL either because i havent tried this and not sure why anyone would tbh? Did you have root issues with Magisk or SuperSU?
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
You should be able to attain full systemless root with either Magisk v17.1-stable or v17.2-beta, by installing the F2FS Loopback Bug Workaround Magisk Module (v2018.9.2) with TWRP recovery. (Installing it from Magisk Manager will typically fail, so boot into TWRP and install the zip.) Upon reboot, open your Magisk Manager, select Modules, and the F2FS module should be displayed as installed.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Thanks [MENTION=8702179]Articul8Madness[/MENTION]. Would you be willing to test a current stock ROM on your device? I have basically taken dumps a member provided me of the system and boot images, fed them to my Android kitchen and built the ROM. AVB/dm-verity & force encryption will be disabled in the stock kernel, the script will install Magisk v17.1-Stable and static BusyBox binaries. I've also zipaligned all APK files in framework, /system/app & /system/priv-app to optimize RAM efficiency. Other than that, the configuration is stock. I have the ROM compiled already, I just need spare time to zip everything up into a TWRP flashable installer and upload it to my file host.
[Moto E4 Guides, News, & Discussion] MotoJunkie01:
Magisk v17.1-Stable or v17.2-Beta should root your device. Flash the Magisk root zip with TWRP. Upon first reboot and after initial setup, open your Magisk Manager app, in the menu go to Downloads and look for the F2FS Loopback Bug Workaround module and select it for install. It will fail. However, the module zip itself will be downloaded in your internal storage/Downloads folder. Reboot to TWRP and install the module. Reboot, open Magisk Manager app and go to Modules in the menu. You should see the loopback workaround module as active. Now you will have proper systemless root and the ability to install systemless modules without the need for a modified boot image.

In a nutshell, some devices with F2FS formatted data partitions (e.g. many Moto devices) have an inherent kernel bug which prevents loopback devices (.img files) from mounting read/write. Because Magisk systemless root requires the path of /data/adb/magisk.img, this poses a huge problem. Without the ability to mount magisk.img as r/w, systemless mods are an exercise in futility. The loopback workaround cleverly moves magisk.img to the /cache partition (which must be EXT2-4), and creates a symlink back to the original magisk.img path. Also, the magisk_merge.img file is recreated subsequent to each reboot, and is utilized exactly like magisk.img. This fix allows magisk.img to be mounted as r/w, and allows systemless mods without a patched kernel. Very important note: once the loopback workaround is in place, it is highly recommended to install every module from TWRP instead of from the Magisk Manager app. This increases the likelihood of loopback stability for your systemless mods.
[Moto E4 Guides, News, & Discussion] DB126:
Please take note of MotoJunkie01's account status as of this writing. Don't know what happened; account is disabled.
[Moto E4 Guides, News, & Discussion] Googleme35:
flash modem NON-HLOS.bin for MetroPCS / TMobile

I flashed a stock recovery everything works except the modem for the phone I get LTE/ text/ data but when I make calls the l caller can't hear me please help stick ROM Hannah MetroPCS/ TMobile
[Moto E4 Guides, News, & Discussion] madbat99:
Hannah? Wrong place dude
[Moto E4 Guides, News, & Discussion] skullkid383:
Nah he is in telegram E5 group but hasn't been to active but I will say the E5 forum has been dead recently since he went inactive
[Moto E4 Guides, News, & Discussion] sCOTTN916:
Seriously?

You left a download link, but we have to gain permission before we can access it? Seriously?
[Moto E4 Guides, News, & Discussion] Googleme35:
Get it from here then use those commands

https://mirrors.lolinet.com/firmware/moto/
[Moto E4 Guides, News, & Discussion] DB126:
Notice OP's account is disabled? Hum...could provide a clue. :rolleyes:
[Moto E4 Guides, News, & Discussion] madbat99:
He's gone dude. And please don't quote the entire op of a thread like this. It just makes scrolling through it a pain.