yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 20 Ultra Questions & Answers] donc:
I just used the text system samsung has setup. It went quickly but I am not certain if that is the same number they use in Canada. It might be worth a try iof you are having issues.

Text HELP to 62913 (from the samsung website)
[Samsung Galaxy Note 20 Ultra Questions & Answers] funziebear:
Got mine in white about a week ago
[Samsung Galaxy Note 20 Ultra Questions & Answers] GDHAMTON7:
Just got mines
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] heykal:
Hi everyone

So i just bought brand new purple poco f2 pro 2 days ago and today i realized there is bunch of dust and particles under the edge of back glass specially in the left side amd bottom of the back glass then i realized i can push the edge of wrapping plastic through that gap so easy for maybe 1mm or so then it stops by inner glues of back glass and it is possible to move those particles under glass but i can't pull them out. This is happens just in left and bottom side of the back glass .... Is that a common problem should i do something ? The purple back glass show those particles on the edges in the some lighting condition i don't know about other colors . But my main concern is it possible for this dusts and particles penetrate more inside the phone and reach to camera lenses ?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] heykal:
this picture should explain what i mean this wrapping plastic did not pushed inside by any hard force the gap is just larger than the plastic wrap ......
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] coyot352:
Hello,

I have purple too and i dont have this issue, The rear window is perfectly adjusted and leaves no space

Sorry but i think its a good solution to call the After sales service ?
[Xiaomi Poco F2 Pro (Redmi K30 Pro) Questions & Ans] batuken:
It certainly is a quality control issue. However, the device doesn't have IP certification so this is kind of expected.
[Off-topic] bernest44:
I have a Motorola Edge Plus. It's September and I'm still on Junes Security Patch. Motorola 2nd tier support is telling me June's Security Patch is the latest update. How are they getting away with this?? That's a flat out lie. They said that Android hasn't given them an update. Huh???
[Off-topic] ManojNairOnline:
Well I saw this thread and began checking the last update on my phone, a so-called brand new m32. I clearly remember the last update was dated November of 2021. Guess what, there was a new update just waiting to be downloaded.
[Off-topic] orb3000:
Im really intrigued why you answer all OT threads that are 2 yrs old or more.

You try to increase post count?
[Upgrading, Modifying and Unlocking] S_hades:
I am in over my head once more and could use help from someone more experienced.

The problem?

I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.

Here's what I did, step by step:

1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504

2. I enabled USB debugging in developer options and set the OEM Unlock option to ON

3. I trusted the connected computer in order to use the adb commands

4. I rebooted to the bootloader and executed the command Fastboot OEM unlock

5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command

6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.

And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.

Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img

I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.

Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.

I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.

Any help would be greatly appreciated.
[Upgrading, Modifying and Unlocking] S_hades:
After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.

Problem solved.
[Tilt, TyTN II, MDA Vario III Themes and Apps] ReYCangri:
I'm having problems with iGo 8 not displaying POI's, I have June 3rd update if that hellps. Tried the sys.txt change so it displays pois from an earlier date but that won't fix it either. I've tried uninstalling it and wiping everything away and still won't fix it. I hope someone can help me with this. Thanks.
[Tilt, TyTN II, MDA Vario III Themes and Apps] kareeem:
If you had the old POIs, they wont work. You need to get the new ones and if you bought the program ain a legit way, that shouldn't be a progrblem ;)
[Tilt, TyTN II, MDA Vario III Themes and Apps] khaytsus:
iGO8 POI's are in KML format and are placed in:

/iGO8/content/userdata/poi/

Your KML key *data* must be named properly, or you'll get categories which don't match your data so might be hard to find. I believe the filename is arbitrary, but I'd suggest keeping the same filename(s) if you update/add POIs later.
[Tilt, TyTN II, MDA Vario III Themes and Apps] guitarguy:
I have the same problem, poi's don't work since I've upgraded versions.

Found this over at PPCGeeks, but haven't had a chance to try it myself. Give it a go and let me know if it works...

Add this to \Program Files\Igo8\sys.txt

[poi]

enable_pois_before_080217=1
[Tilt, TyTN II, MDA Vario III Themes and Apps] ReYCangri:
nevermind guys i got it working..for some reason my poi file wasnt in there...thanks eveeyone
[Tilt, TyTN II, MDA Vario III Themes and Apps] zagorka:
Yes, this worked for me. Now i have POI's with USA 071010 maps and iGO8 v.44366
[Tilt, TyTN II, MDA Vario III Themes and Apps] finlay777:
hi what about the poi icon? it seems that it cannot be chnage and its defaulted to google icon
[Tilt, TyTN II, MDA Vario III Themes and Apps] khaytsus:
You mean an earth icon. :) Anyway, that one is a pain in the ass. There has been a long-standing bug where they apparently ONLY look at the icon files in one of the zip files they use on the fly if that file is available. You can remove the file and your custom icons will work again.

HOWEVER. Getting that zip to work right again I have lots of problems with, I don't recall how I fixed it last time to be honest. Just random zip on it doesn't seem to work. You might post on the Navi forums to see if they can help.

Ah, from my post on this long ago it looks like I wound just swapping out some data files, since I never could get my modified zip file to work properly.

https://telesystem.naviextras.com/shop/mvnforum/viewthread?thread=2194
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] maha sandhy:
MIUI 12 BASED or CUSTOM ROMS
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Mathvediz:
i use Evolution X which based on Pixel Experience with a lot of customization.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] jonathan240196:
I use OmniROM with MicroG.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] cris2d2:
Bliss ROM 12.11 (OSS vendor) with stock immensity kernel.
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Sandeeep Kiran:
derpfest july's update. (cause its stable af, and I'm lazy as hell to update to the latest)

will probably try mortal inception next
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] hrdlw:
But which is the best for battery life? (Not including microg roms)
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] rasik107:
try latest Evo-X 4.7

I am using it from past 3 days and getting a good battery life (compared to 4.6 :D)

approx 5-5:30 hours of SOT with 2 hours of PUBG and still around 15-16% left

so u can consider one more hour :laugh:
[Tasker Tips & Tricks] elora_c:
I have a Samsung Galaxy Watch and a Samsung S10 phone. Several times over the past week or so, my watch battery has completely drained in about an hour. I only notice when it vibrates at 15%. There doesn't seem to be anyway to get a notification either from the watch or through the Samsung Wearable app when it reaches 30% instead of 15%. Is there a way to create a task on the phone to notify me when the watch's battery level reaches 30%?

Thanks.
[Tasker Tips & Tricks] xe0r:
Sorry I have no answer to your question but as a user of the gw myself, what are you doing to drain the battery that fast? Do you have the 42 or 46mm version?

Gesendet von meinem HD1903 mit Tapatalk
[Tasker Tips & Tricks] elora_c:
I have the 42mm. Unfortunately, I'm not doing anything. It is a bug with the watch (or phone). It happens to my husband's 46mm as well. It will suddenly just become unresponsive and burn through the battery. It can drain a full battery in about an hour. Several times, I've charged it completely before bedtime, put it on to sleep, and then sometime during the night it'll drain and turn off. Happens randomly during the day, too.
[Tasker Tips & Tricks] xe0r:
That for sure makes the watch unusable. I am using the 46mm variant and use it heavily for tracking sports and / or use the navigation while sport (eg riding bike). Even with this heavy usage I never had less than ~40% in the evening. For everyday use I get 3 days with 30 percent left with my medium usage setup, if I switch off some sensors I would even get more I guess. That's what you can take as a comparison for the 46mm watch.

Now how to get there? Don't try to spend time into tracking this drain with tasker or whatever, instead pull it by the root. Sounds like some app is misbehaving (in the background?). I would try to start looking for apps on the watch. What 3rd party apps do you AND your husband have both installed? Remove them, one by one, and watch the result. I have only 3 3rd party apps (GPS navigation, wrist camera and watchevents). If it doesn't get better after you only have the stock apps installed, you unfortunately have to make a reset to the settings. If the behaviour comes back after the reset with only the stock apps, send it back if you still have warranty.

Btw, you know that you can see the apps that are running in the background on the watch? I put this overview on the double tap action on the home button. You can also use this for further investigation, like close all apps instead of one, like the suspicious one and so on...

Keep me updated on the results! :)

Gesendet von meinem HD1903 mit Tapatalk

*Edit*: just some typos.. =)
[Tasker Tips & Tricks] elora_c:
How do you see which apps are running? I know through the Samsung Wearables app that I can see what apps have used the most battery since last charged, but unfortunately that is no help in this situation. I just removed a couple of apps that were on the watch that I don't use (Samsung Flow, and one or two others). Now the only uninstallable apps are Timer and Stopwatch. Everything else is a stock app (most of which I never use).

Thanks.
[Tasker Tips & Tricks] xe0r:
I don't know how it is called in English, so I roughly translate it on the fly:

- Settings

- Expanded settings (4th entry with the orange gear and plus sign)

- Double tab home button

- tick recent apps --> [x]

Now you get an overview of the open apps when you do a double click on the home button.

Why does it not help to see which app is using the most battery in the wearable app? Whas it a 3rd party app? System app?

Gesendet von meinem HD1903 mit Tapatalk
[Redmi Note 8 Questions & Answers] maxpower9122:
Hi, I need help.

Is there any possibility to unlock the bootloader without xiaomi's Miunlock app? I need your help please, buy an RM8 and when you turn it on it has a Miaccount lock

I have the Miflash application but it asks for my authorization
[Redmi Note 8 Questions & Answers] loopypalm:
there is no way , just do your best to recover the Miaccount
[LG V30 Questions & Answers] Dugdugofdug:
I bought my LG V30 (LG-US998) secondhand from a phone reseller and "Factory data reset is disabled by Kill switch" pops up when I try and boot into recovery by holding/letting go of the vol-/power buttons.

I still managed to root it despite this, because even though I can't boot recovery through hardware, I can still use fastboot commands, as well as my custom power menu, to reboot into recovery. The problem with this is that I can only boot recovery if I can access Android, which means that I have very little brick protection despite having TWRP installed. I had a bit of a scare trying to install LineageOS because of this, but I managed to recover it. This scare made me decide to stick with the stock ROM for the last few months, but I really would like to check out some of the other options.

I read somewhere that removing your saved Google account credentials can remove the kill switch, but it didn't work for me. Based on some of what I've read, I shouldn't have been able to set up the phone with the kill switch enabled, but I could, so I'm not really sure what's going on.

Has anybody figured out how to remove the kill switch yet? With root, it seems like it should be possible, but I still haven't found any way to do it. Unfortunately, I can't return the phone as it's been far too long since I bought it.

Thanks in advance.
[Android Q&A, Help & Troubleshooting] Michael Carroll:
Hi all, I have a number of the same Android devices connected to a 10-port USB hub. I'm curious as to why some devices show up as their serial number and the others show up as usb_xxxxxxxx devices.

I'm trying to troubleshoot some connectivity issues and I'm not sure if it's related to this or not.

Thanks in advance

Michael
[Android Q&A, Help & Troubleshooting] Deleted member 1890170:
Seems USB-mode of these devices isn't set to adb but anything else.

On these devices you might run

adb devices
adb shell "svc usb setFunctions adb"
adb reboot
[Android Q&A, Help & Troubleshooting] Michael Carroll:
Thanks for the reply jwoegerbauer! I think I may be on a goose chase, thinking this was my connectivity problem.

I discovered I can still login to the shell on the devices, by using the usb identifier as the serial number with the -s switch.

i.e.

.\adb -s usb_007997e8 shell

What I was seeing was the devices occasionally disappearing from the hub, when I noticed that some were turning back up as usb devices I thought that may have been the issue. But if I can still login to the shell, I don't think that's the case. Next I found switching ADB versions seems to fix the issue, as the devices appear correctly identified with serial numbers.

I think I'll need to have a bit more of an investigation to see where my issue lies.

Thanks again

Michael
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
U da man Homeboy76. Really appreciate all the work you did putting this together. Thanks.
[Google Pixel 4 XL Guides, News, & Discussion] mikepopo99:
fastboot flash boot magisk_patched.img.--slot all

i have to remove the period after the patched.img. if not i get a no such file in directory
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
Worked like a charm for me. I did a clean a clean install. No issues. Just like flashing a monthly update.
[Google Pixel 4 XL Guides, News, & Discussion] mikepopo99:
Bootlooping

no matter what I do I keep bootlooping. I'm doing everything on the instructions list. IM trying to root android 11 on my pixel 4 xl. I just flashed the update with the flash all and wiped everything. But when i try to root it gets stuck at the google logo. i have the Magisk Canary Channel installed and patched the boot image and everything. I get the no valid slot to boot in the bootloader.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Curious

- SDK Platform-tools r 30.0.4?

- What slot did the September 2020 Factory image flash to?
[Google Pixel 4 XL Guides, News, & Discussion] mikepopo99:
I'm not sure what slot. But yes I am using the newest platform tools. How can I check. I just did the flash all script from Google and did a clean install.
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Check: Boot fastboot mode (#1 in the guide) see boot slot.
[Google Pixel 4 XL Guides, News, & Discussion] Utini:
Best guide on xda.

I just wonder: Can I flash Android 11 on top of Android 10 and keep my data (by removing -w) or is it recommended to clean flash Android 11?
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
I recommend clean flashing.
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
I would never try to tell anyone which way is the correct way since opinions vary. Having said that, I updated without the -w and have had zero problems thus far. However, I would take all necessary precautions as usual:

1. Update your platform-tools.

2. Remove/disable all magisk modules.

3. Remove your face unlock before starting.

4. You'll need to be on the latest canary magisk if you want to root.

5. If you patch your boot.img, make sure the finished image is 32.55 mb. I personally patch the new boot.img before even starting the update process so it's ready to go.

Again, this is how I like to update my device, and is not the be all end all method that others may like to use. Best of luck to you no matter which method you may choose to use. :good:
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
A second opinion is good. :)
[Google Pixel 4 XL Guides, News, & Discussion] madmaverickmatt:
Any tricks to getting Safetynet to pass? I did a clean install and build updated everything and safetynet is still failing.

Thanks all.
[Google Pixel 4 XL Guides, News, & Discussion] aquadisaster:
great guide! i almost messed up bad when i flashed first time it froze up and stalled i realised my ssd main drive ran out of space. freed up some space and retried and all worked great! (its a lot bigger than i thought when installing)
[Google Pixel 4 XL Guides, News, & Discussion] ucantescape1992:
Great guide. Boot image is patched and flashed on Android 11.

I can't pass SafetyNet however. Is anyone on Android 11 and passing? Any tips?
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Safetynet

https://xdaforums.com/apps/magisk/module-magiskhide-props-config-t3789228
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
Post deleted!
[Google Pixel 4 XL Guides, News, & Discussion] TheDiabolicaL1:
So, I've been out of the flashing game for a long minute but I had to do something about all the ads I was getting. Blockada seemed to work okay but always left something to be desired. I missed Adaway, so....

I had a hard time getting Magisk installed in Android 11 on my Pixel 4xl. I followed this well written tutorial to a tee but when I flashed magisk_patched.img to boot, then "fastboot reboot," it would kick me back to fastboot after the "G" screen and spit out the error "no valid slot to boot." Three times in a row after clean flashing the factory image too!

I did end up getting it working. What I ended up doing was instead of "fastboot flash boot magisk_patched.img --slot all" I "fastboot flash boot magisk_patched.img" and for whatever reason that seemed to work.

I did not take the OTA update if it matters. I had intended to wipe the device with a clean install of Android 11, then Magisk (just for ad blocker) from the get so, I'm guessing slot b wasn't used? I'm honestly not really sure how it works.

Even then though, I had some trouble getting the order right from flashing the factory image to being rooted, so this is also what I found.

First, unlock the bootloader of your device, then clean install Android 11 and get it set up. Download Magisk manager canary, then adb push the boot.img from your computer to your device. Use Magisk manager to patch it, then adb pull magisk_patched.img back to your computer. From there, fastboot flash boot your magisk_patched.img and you're golden. Fastboot reboot should put you back in to Android and then Magisk manager will recognize root.

I had tried several times to use a boot.img I had already patched some days earlier but it never seemed to work. It would boot okay, once I figured out not to "--slot all," but Magisk would never recognize it was rooted unless Magisk manager patched it and I flashed that particular patched file. If I tried to flash any other patched file, Magisk manager wouldn't recognize root. Even recently patched boot.img's that were flashed to the device (not the days old one I had pre-prepped) wouldn't work. Magisk manager only seemed to recognize patched boot.img's that were made by it in that particular install. If I tried to use a boot.img from any other Magisk Manager install it wouldn't recognize it. Weird? I dunno, but, I got it up and running!

Thanks Homeboy76 for making this tutorial. Without it I would have been lost. :good:
[Google Pixel 4 XL Guides, News, & Discussion] Homeboy76:
[MENTION=4343547]TheDiabolicaL1[/MENTION]

Thanks for the kind words.

Glad you got it working and, thanks for posting this information: fastboot flash boot magisk_patched.img

It provides an alternative method of flashing the magisk_patched boot.img for the members getting boot loops.

However, fastboot flash boot magisk_patched.img --slot all does work without boot loops:

C:\android-sdk_windows\image-coral-rp1a.200720.009\platform-tools_r30.0.4-windows>fastboot flash boot magisk_patched.img --slot all

Sending 'boot_a' (33336 KB) OKAY [ 0.234s]

Writing 'boot_a' OKAY [ 0.326s]

Sending 'boot_b' (33336 KB) OKAY [ 0.234s]

Writing 'boot_b' OKAY [ 0.335s]

Finished. Total time: 2.509s
[Google Pixel 4 XL Guides, News, & Discussion] techbeck:
What I did a little bit ago. Didnt do a clean update and everything fine so far.
[Google Pixel 4 XL Guides, News, & Discussion] madmuthertrucker:
I installed 12 and I can't pass safteynet to save my life. What am I doing wrong? I tried every version of Magisk there is. I passed it for a second and then it failed a minute later.