yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Dan_firehd:
I am on Fire 7 (7th Gen) OS 5.6.0.0.

Recently, I also noticed that some apps randomly displayed SD error upon launching.

Thanks to everyone, this works like a charm:

(1). Settings --> Apps & Games --> Manage All Applications

(2). Swipe left in order to display "ALL" applications and then scroll down to select the application named "Home Pages"

(3). Tap "CLEAR CACHE" and then "FORCE STOP"

This fixes the problem of SD error.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] PcBrewer:
Dan_firehd, That worked...thanks for the help!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Freddyfry:
Thank you, resetting Home did it... You're a better man than I, Gunga Din!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Ludergirl:
Resetting home also worked for me. Thank you!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] synchron50:
:crying:Yeah it worked but it also ungroups all of your icons. Could be a lot of time to group them again.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Dan_firehd:
If you only tap "CLEAR CACHE" and DO NOT TAP "CLEAR DATA", (followed by tapping "FORCE STOP"), it will not un-group your icons.

Tapping "CLEAR DATA" is what caused un-grouping of icons.
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] ritchiesh:
Thank you soooo much, this works!!!

btw, I am a user from China, I found that if the system language is Chinese, this won't work, so I swith to English(US), and all goes right again.

Note here in case other users have the same problem.

Thanks again!!!
[Fire HD 8 and HD 10 Q&A, Help & Troubleshooting] Pbwhite53:
Good fix! I believe this occurs when you attempt (or allow via auto update) the Google Play store to update an app that was installed via the Amazon app store.

Turn off auto updates in the Google play store, and manually update each app that you know was originally installed via the Google play store.
[ZTE Axon 7 Questions & Answers] Doc Ames:
I finally found a ROM for this GD phone that fully connects to my Bluetooth deck. Yay! All other ROMs besides stock and PureNexus would say "Connected (no phone). However Xposed is not working. The Xposed Installer (v3.14) says that Xposed version 89 is installed, but not active. This is my first time trying Xposed on Nougat. I've used Xposed on all previous Android versions (since the inception of Xposed). Never had this issue. The installer says to check the logs. When I tried it says that it can't read the log (no such file or directory). I'm so sick of effing with this phone. I'm still using my OnePlus One because I can't find a ROM that has fully working Bluetooth that isn't the crappy stock ROM or PureNexus (PureNexus is unfinished and abandoned). Somebody, anybody...how the eff do I get Xposed to work?

What I did:

-Full wipe (dalvik, system, data, cache)

-Flash latest PureFusion (13NOV2017)

-Flash SuperSu v2.82

-Flash OpenGapps (pico)

-First boot

-Install Xposed installer v3.14

-Reboot to recovery

-Flash Xposed v89

I've also tried using the install option from within the installer. No joy. Changed SuperSu options to be more compatible and less safe (namespace speration, trust system user, enable su during boot). No Joy.

I'm about to smash this phone with a hammer. Finally found a ROM that sorts Bluetooth and now Xposed doesn't work. Next time I'll check XDA first before buying a phone to check the current status of development.

Edit: I'd like to avoid using Magisk if possible. I can't remember which root apps, but there are some that don't work with Magisk (last I checked).

Edit 2: Tried the following without success. Exact same results. A msg on the status screen saying Xposed is installed but not active:

-Unity version of Xposed

-Magisk 14.0 + systemless Xposed framework

-Probably something else I'm forgetting

I created the missing log file and gave it the appropriate permissions but nothing ever got written to it. I suppose I could do a logcat but I can't be bothered. If Xposed doesn't work out of the box for this particular ROM I'm not going any further with it. I posted this question in the ROM thread as well.
[ZTE Axon 7 Questions & Answers] Choose an username...:
Try Magisk 14.0, install the module, download the modified apk from the module download tab, install the app, see if it works

Edit: I just read the last line, sorry

that is the only thing that i've thought about. Stock is the other way around, normal method works but topjohnwu's module doesn't. But Magisk xposed worked on every custom ROM I've used.
[ZTE Axon 7 Questions & Answers] Doc Ames:
I would have ultimately tried Magisk anyways if all else failed. I will try later. Probably tomorrow. If it works I'll call it solved and you get the prize.
[ZTE Axon 7 Questions & Answers] Choose an username...:
Nah don't want any price. a thank is enough

Which are the apps that don't work with Magisk?
[ZTE Axon 7 Questions & Answers] AnonVendetta:
[MENTION=4801416]Doc Ames[/MENTION]: it's probably just the ROM you've chosen. I've tried lots of Lineage/AOSP ROMs for the A7, Xposed has worked flawlessly in all of them.

My setup:

Vertex Carbide

Hellsgate EAS kernel, with data and cache formatted as F2FS

Phh's Superuser, for root

Busybox 1.27.2 by YashadSaraf

Xposed v89 official

No GApps, except MicroG and Play Store

I try to avoid Magisk, it's a nice concept, but systemless is more trouble than it's worth. Magisk has caused me tons of issues. I've tried it off and on for months but I keep switching back to good ol reliable Phh. I stopped using SuperSU ever since it was bought by an Asian (Chinese?) company.

Good luck!
[ZTE Axon 7 Questions & Answers] Doc Ames:
I don't remember. If for some reason I have to use Magisk maybe I can find replacement apps.
[ZTE Axon 7 Questions & Answers] Doc Ames:
Thank you for the suggestion. The issue is that there is no other ROM for the A7 (save PureNexus and stock ROMs) that will properly connect to my Bluetooth deck. I was trying to pursue a solution to the Bluetooth issue with custom ROMs for the A7 but it affects such a small number of users that nobody seems to think it's an issue. I tried the ROM you are using and had the above mentioned Bluetooth issue. I've tried a ton of ROMs. I'd rather get a fix to the Bluetooth issue so I can use whatever ROM I want. However, I posted a question about my Bluetooth issue and everybody just gave me the whole, "It's working on my machine. Must be your deck."
[ZTE Axon 7 Questions & Answers] AnonVendetta:
[MENTION=4801416]Doc Ames[/MENTION]: Well sorry to know that you're essentially forced to used a specific rom just to get your Bluetooth deck working. I don't use Bluetooth for anything but transferring files, that's worked in every ROM I've tried. But I have had issues in the past where a certain device would work on one ROM but not on another. It could be a ROM issue, or maybe an issue with the Bluetooth device you're using. Maybe a combo of both. I'm not a dev so there's nothing I can do except be sympathetic. Maybe you can elevate your issue with A7 devs so they can maybe look into whether there are underlying Bluetooth issues in their ROMs that need to be resolved. If the deck didn't cost too much, you might want to look into selling it and getting a more known, compatible deck that works with most ROMs. I guess it all just depends on how much it's worth to you to be able to run whatever ROM you want without worrying about whether your deck will work.

Good luck!
[ZTE Axon 7 Questions & Answers] marcdw:
[MENTION=4801416]Doc Ames[/MENTION],

If you haven't yet, give the UNITY Xposed package (by [MENTION=5357345]ahrion[/MENTION]) a try. On my G3 I had nothing but troubles trying to get Xposed and ParanoidAndroid working. With UNITY everything came together to my surprise.

Also just flashed it tonight on the Axon B32 stock. Far as other ROMs go I've used both unofficial and official Xposed on various ROMs like VertexOS and Dark ROM without issue.

I too stay away from Magisk so I can't speak to any of the systemless installers.

http://xdaforums.com/showthread.php?t=3697756

[12/18/2017] Xposed Framework v88.9 [UNITY]

LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
[ZTE Axon 7 Questions & Answers] Doc Ames:
Thank you for the suggestion. I tried the UNITY Xposed. No joy. Same result.
[OnePlus 3T Questions & Answers] linux-colonel:
I've been running LineageOS 14.1 on my OnePlus 3T since last March when I bought it. On Friday 2017-12-15, I installed the weekly LineageOS update and the phone got stuck on the boot animation after entering the encryption password. I let it sit for about 45 minutes and then powered it off. Has anyone else experienced this?

Info:

* LineageOS 14.1 (build 20171215); no google play services

* TWRP 3.1.0-1

* 128GB version of the Oneplus 3T

* /data formatting: encrypted f2fs (so far)

Here is the troubleshooting I've done thus far and my observations:

* I have noticed over the past few months that it has taken longer to flash ROMs than when it was new. Sometimes when booting (although rarely), the boot animation freezes for a bit.

* Without reformatting, I restored a nandroid backup from 2017-11-25. I have previously restored this backup, so it's known-good. When booting, it wouldn't get past the boot animation after entering the encryption passwd. Sometimes, the boot animation would freeze entirely.

* I installed OxygenOS (version OnePlus3TOxygen_28_OTA_028_all_1707141503_fc82c5d2e3054e44). The phone booted very quickly and got past the passwd prompt without issue. OxygenOS ran noticeably faster. I let it install the latest OTA and that also went quite quickly.

* I nuked /data and installed a fresh LineageOS build 20171215 with no modifications (besides the su addon). The phone was able to boot all of the way, but apps were slow and some froze. The OS crashed (soft-reboot) twice. I have a logcat for that (can't find a way to attach; are new members allowed to attach?).

* I reinstalled OxygenOS and downloaded my music to it (~50GB). The performance of the phone still seems fine. I'm doing this to test the theory that it might be an issue with wear-leveling on the flash.

Next steps / tests:

* Based on the behavior, I'm not convinced it's a hardware issue. I suspect that maybe the binary blobs / and/or kernel are responsible for the difference.

* I'll try LineageOS with /data formatted as ext4 instead of f2fs.

* I'll try LineageOS, but booted with Oxygen's kernel via fastboot boot. I'm not sure this will even work at all, but it's worth a try.

I'll report the results of my tests / troubleshooting here.
[OnePlus 3T Questions & Answers] BillGoss:
This might explain your problems with booting LOS.

From the official OnePlus 3/3T LineageOS thread post #2:

Started from lineage-14.1-20170207-nightly-oneplus3-signed.zip, we provide unified builds for both 3&3T, and you need to install certain firmware to pass the TrustZone assertion. Currently they're the OxygenOS Open Beta 19/11 ones. As oneplus won't update them every time new OTAs are rolling out, firmware from other versions might also pass the assertion.
[OnePlus 3T Questions & Answers] redpoint73:
Just wanted to point out the thread title say "5T" but everything in the post says "3T" so I do presume you are on the 3T. If so, you may want to update the title, to avoid confusion. I saw the thread title myself, and was going to post "Dude, wrong device section" until I read the content.
[OnePlus 3T Questions & Answers] linux-colonel:
One test I did before updating my firmware:

I filled the userdata partition about half full with music (while running Oxygen). I then flashed my known-good backup and it booted. However, installing the update failed (boot animation for > 1 hour after entering encryption passwd). I wonder if there is something with the flash wear-leveling at play.

I upgraded the firmware from the latest OxygenOS beta (OnePlus3TOxygen_28_OTA_038_all_1711272148_5e0ea1454e8f4f0f.zip). Upgraded TWRP to 3.2.1-0 first. I'll do some more testing and report my results.

Only adspso.bin was the same.

Anyone know what each of these does? The more I understand, the better. :)

The complete list of files is:

BTFM.bin
NON-HLOS.bin
adspso.bin
cmnlib.mbn
cmnlib64.mbn
devcfg.mbn
emmc_appsboot.mbn
hyp.mbn
keymaster.mbn
logo.bin
mdtp.img
pmic.elf
rpm.mbn
tz.mbn
xbl.elf
[OnePlus 3T Questions & Answers] linux-colonel:
After upgrading the firmware, I restored my known-good backup and performed the following upgrades:

* lineage build 20171124 (restored from backup) -> lineage build 20171201 -> lineage build 20171215

* lineage build 20171124 (restored from backup) -> lineage build 20171215

It made it through 3 upgrade cycles with normal behavior.

Previously, it hung after upgrades after entering the encryption passwd. This is the stage where it "optimizes" all of the apps (someone feel free to correct me if there's a better term for this). I suspect that all of this flashing / upgrading caused the wear leveling to swap out the bad blocks that were causing the hang (assuming that was the problem).

I'm going to try completely filling /data with random files (i.e. for loop; dd if=/dev/urandom etc). I'll then completely wipe the phone afterwards. I'm hoping this will cause any other bad blocks to get put out of service and prevent this problem in the future. Are there any better ways of doing this and/or any advanced diagnostic tools for UFS hardware?
[OnePlus 3T Questions & Answers] linux-colonel:
After filling /data with random files, I ran through a few more upgrade cycles and it hung again. I noticed IOExceptions in the logcat, both on LineageOS and on OxygenOS. I'm pretty sure this is a hardware failure and I've filed an RMA with OnePlus. They're not making it easy (despite my detailed troubleshooting).

One interesting thing is they want to do essentially this procedure: https://xdaforums.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306

I don't think that will help considering it's just a different way of flashing the same bits to the storage.
[OnePlus 3T Questions & Answers] pitrus-:
This is the known side effect of using F2FS filesystem, me to had problems like this until I switched back to EXT4 and now it takes under a second to enter TWRP and phone doesn't go turtle when the storage gets filled up.
[OnePlus 3T Questions & Answers] linux-colonel:
Do you know why f2fs has this problem?
[OnePlus 3T Questions & Answers] linux-colonel:
So I finally got my phone back from repairs yesterday (yes, it's been almost a month). I noticed that wiping the phone from twrp (using format data) and then re-encrypting the phone after flashing lineage causes corruption on /data, even though the encryption process completed without error. The phone would boot, accept my password, continue to boot, get to the lockscreen, and then crash immediately. There were IOExceptions in the logcat. Booting to twrp afterwards also resulted in IOExceptions in the logcat.

Flashing Oxygen, letting it boot once to force-encrypt, and then wiping and installing lineage without formatting /data (encryption preserved) did not result in this issue. The phone behaved normally. I even had to set the password in Oxygen. Setting it in lineage (via the GUI) caused the boot to hang.

Since the phone's stock rom is force-encrypt, I suspect there's some sort of incompatibility between the device and the older encryption process (launched via settings) from AOSP.

I'd like to troubleshoot why this is the case. Any good tools in the Lineage source (I have the tree locally)?
[OnePlus 3T Questions & Answers] pitrus-:
No idea, guessing it's simply a buggy filesystem implementation.
[General Questions and Answers] electro_nik:
Hello,

can someone help with root , bootloader unlock, custom roms support for the cheapest dual camera phone infocus turbo 5 plus
[General Questions and Answers] electro_nik:
i got a way to root .. but need to install recovery .. i am not sure if TWRP will work on it to root the phone.
[General Questions and Answers] Tyson360:
Twrp won't work.

1. There's no official support.

2. I can port twrp for my phone but I can't get the bootloader unlocked. The porting of twrp would be useless if we can't unlock the bootloader. :(

[IMG="Every fastboot command gave gave the error except for "getvar unlocked (to check if the bootloader was unlocked)""]https://ibb.co/hcz51b[/IMG]
[General Questions and Answers] aashishkap.2010:
hi.. can you tell me how to root this device??
[General Questions and Answers] Sameem irfan:
can any one help to unlock bootloader of turbo5 plus...

when i try to unlock it says--

Failed( unknown remote command)

finished total time - 000005s
[Google Pixel 2 XL Guides, News, & Discussion] mrimage:
I hope to see some rom start to show up
[Google Pixel 2 XL Guides, News, & Discussion] Dielahn:
There are already posts like this. Alot of us are excited for roms to show but i dont think posts like this will speed anything up. Patience my friend they will come. Give the devs all the time they need.
[Google Pixel 2 XL Guides, News, & Discussion] KennyG123:
It is good to share your enthusiasm but as mentioned there are other similar threads.

Thanks

Thread closed
[Samsung Galaxy S8+ Questions & Answers] meza85:
Hi i want to know if anyone can help me, I have a samsung s8+ model SM-G55F i bought it online and the original csc code was TPA/TPA/TPA but I want to use Samsung pay in Mexico I tried flashing the Mexico firmware but it always change to the default multi csc in this case the mexico csc is IUS but now is CWW the default, How can I force it to this CSC?
[Samsung Galaxy S8+ Questions & Answers] MeltdownSpectre:
Flash this IUS firmware:

http://updato.com/firmware-archive-select-model?record=77FFCF79B9FD11E7963AFA163EE8F90B

Make sure to flash it while a local Mexican SIM card is inserted in the device, then do a factory reset after flashing and it should be on IUS.

CSC should say IUS/IUS/TPA then and Samsung Pay should work just fine.
[Samsung Galaxy S8+ Questions & Answers] meza85:
Hi thanks for answering! Unfortunately i doesn't work I did that it goes to the default CSC CWW, Originally i wanted the TCE code or any of those Mexican CSC I have sim of both operators but when i flashed with the TCE the code change to CPA ( Panama) Claro is the same carrier as TCE but different name and both are in the same Multi CSC firmware any ideas what to do? Already tried the *# codes
[Samsung Galaxy S8+ Questions & Answers] t.gazda:
Hello i change csc code in sm g955u from sprint . This solution it's works https://youtu.be/M-jOM9LXhqE

Wysłane z mojego SM-G955U przy użyciu Tapatalka
[Samsung Galaxy S8+ Questions & Answers] JeffDC:
Why "to flash it while a local Mexican SIM card is inserted in the device"?
[Samsung Galaxy S8+ Questions & Answers] MeltdownSpectre:
Because otherwise it won't change IUS to the active CSC.

Sent from my SM-G955F
[Samsung Galaxy S8+ Questions & Answers] JeffDC:
I've got to think that through/don't get it. Here is what I'm understanding from what you wrote.

So if I set up a phone, say throw a different ROM/custom on it, and flash a specific CSC region, the (new) CSC will not 'take' if the country SIM I'm wanting to change to is not in the phone when I flash the CSC zip?

Am I understanding correctly?

If I am, why doesn't the phone, having the new CSC in it, let's say without having the SIM in it when it was flashed...

know what region it's going to soon lock-on/expect when it boots, based upon the newly flashed CSC software?

There must be some necessary interplay between the two (new CSC and SIM).

Thank you.
[Samsung Galaxy S8+ Questions & Answers] MeltdownSpectre:
If you're flashing a custom ROM and/or using the flashable CSC method, then it doesn't matter whether you have the SIM card or not.

If you are on stock ROM, and you want the CSC for your country to be the active CSC, then insert your SIM card, then flash stock ROM, or just do a factory reset while your SIM is inserted in the phone. It'll reboot and the new CSC will be active.
[Samsung Galaxy S8+ Questions & Answers] space_eyes:
What if the correct csc is not packed with the rom?
[Samsung Galaxy S8+ Questions & Answers] amosolidu:
https://www.sammobile.com/forum/showthread.php?t=39155 use this tutorial !!! It helped me !!! Change my csc from rom to: btu,phn,xeo and now i'm on dbt ;)
[Samsung Galaxy S8+ Questions & Answers] arcaneck:
let me know if this work, because i want to go back to csc ius and i cant i have the same problem
[Samsung Galaxy S8+ Questions & Answers] amosolidu:
It works 100% Sam firmware tutorial !!! Status : official ; knox status 0x0 !!!
[Samsung Galaxy S8+ Questions & Answers] arcaneck:
can you explain me a Little more detail what to do? because for be honest i dont understand very good
[Samsung Galaxy S8+ Questions & Answers] amosolidu:
Just do it step by step and at step 5 in factory binary you will find a button named factory ime(not imei) and fype the code !!! Step by step !
[Samsung Galaxy S8+ Questions & Answers] meza85:
But what combination file do i have to download?
[Samsung Galaxy S8+ Questions & Answers] amosolidu:
Seach with Google:

COMBINATION_FA70_G955FDXU1AQD1_CL11075180_QB130870 97_REV00_user_mid_noship.tar
[Samsung Galaxy S8+ Questions & Answers] davioxx:
Did you got it to work back with ius/tce firmwares?

Regards
[Samsung Galaxy S8+ Questions & Answers] Blackwalrus:
Algún avance con tu problema?, yo estoy en las mismas, saludos!
[Samsung Galaxy S8+ Questions & Answers] yojosefo:
Lo sulucioné, mi celular es un S8+ comprado en Club Premier de Aeromexico. Versión latina, con CSC TPA...

Ya lo cambie a IUS y funcionó!!!

Saludos!

---------- Post added at 05:02 AM ---------- Previous post was at 04:42 AM ----------

So I finally managed to change my CSC from TPA on my unbranded S8+ (G955F) to IUS, and now I can use S Pay.

This is what I did:

1. Downloaded this Combination File from https://firmware.gem-flash.com/index.php, I had to pay $3 USD to get access to the download.

COMBINATION_FA70_G955FXXU1AQD1_CL11075178_QB13087097_REV00_user_mid_noship.tar.md5.rar

2. Downloaded Odin 3.12 (latest), other versions did not work.

3. Downloaded this ROM:

https://www.sammobile.com/firmwares/galaxy-s8-plus/SM-G955F/IUS/

Latest version (January 1st, 2018), it is from ATT, but I dont care care about that haha.

4. Run Odin, download mode on phone and install firmware downloaded from SamMobile.

5. Restart phone, enter OS and do factory data reset.

6. Remove "hidden.img" from HOME CSC (included in firmware) with 7Zip. It has to be repacked to a Tar file.

7. Go back to download mode, open odin and choose the combination file under AP and the recently modified version of Home CSC under CSC.

8. Reboot and enter factory mode.

9. In Factory Imei input *#243203855#

10. Choose IUS as the new CSC.

11. Boot back to download mode.

11. Reinstall firmware, now using normal CSC file (not Home CSC).

12. Boot up to ATT Mexico phone.

13. Morir en paz.
[Samsung Galaxy S8+ Questions & Answers] yojosefo:
Solucionado! Cualquier duda me avisas.
[One (M8) Q&A, Help & Troubleshooting] dedpossum:
The charging port in my Htc One M8 was really loose and barely charging, so I purchased a new port thinking this would solve the problem. At first it seemed like it might. However "new" charging port is just as loose as the old charging port even with a brand new samsung cable when I wiggle the cord I get a charge, so I'm inclined to think that the problem is at the port. Has anyone come across this and solved it?

Thanks!

ded
[One (M8) Q&A, Help & Troubleshooting] lucyr03:
Probably you get a faulty charging port, did you try another cable?
[One (M8) Q&A, Help & Troubleshooting] dedpossum:
Yes, I have purchased 3 charging ports atm, and 2 new cords, the last cord is supposed to be genuine HTC. I also replaced the battery. My third charging port was working great for a time, but now feels like it's 5 years old. I'm really having a hard time with this
[One (M8) Q&A, Help & Troubleshooting] mortmaru:
This appears to be a very common problem with official and unofficial ports it's just one of those flaws with this phone and a big reason why so many of my friends gave up on this phone.

htc will claim its due to not using official htc cable but that is bs