yashsingh1/xdaforums huggingface dataset:
[Windows RT General] hectorantonio:
Previous script works at times, don't blame me, I took my time to read, research and test, it's not that simple as "brightness gets broken after suspension", and it's not as easy to solve as "set your custom brightness level right after first boot", at least testing over and over prooves it.

But this one is bullet proof (PowerShell)

$d = Get-PnpDevice| where {$_.friendlyname -like "NVIDIA Tegra 3*"};
$d | Disable-PnpDevice -Confirm:$false;$d | Enable-PnpDevice -Confirm:$false

What it does is, it gets the screen device and disabled it and enables it again, the screen will just blink but the brighness control is fully restored, you can run it at any time it gets stuck. Not pretty but efficient. You could even set it on the task scheduler to run after wake up (I prefer not to).
[Windows RT General] gishanstc:
Is this method still work?
[Sprint Samsung Galaxy S 4 Themes and Apps] dfw123:
Hello! Why apps can not back compatible with older android like windows? This is bad. not convenience. you spend more to buy a new phone!!!
[General Questions and Answers] Nova328:
Hello Guys,

im new to this forum and i like to read some threads here from timt 2 time.

And since i got my own pocket pc, i wondered if anybody could help me with a question.

The Windows Mobile Version of mine is a spanish one. And i would lik to have an english version of it. Is it somehow possible to install a language packet or to get another version of WM?

I hope you guys can help me with this. I know this isnt exactly a pocket-pc-forum, but maybe you know something.

Ill tried to search the web, but i got no result :confused:

Please help me, any answer would be very kind :)

Best regards
[General Questions and Answers] N1c0_ds:
Just like Windows desktop OS's, you must reinstall the OS to change the language.

It's not an easy process if you are not familiar with your device. Scroll down to the bottom of the page, there is a forum devoted to your device. You should find a lot of information there.
[General Questions and Answers] Nova328:
Hey N1c0_ds,

i thought i have to reinstall or flash a new rom/OS.

I can read as much as possible and i dont fear the work :D

And because im not very familiar with my pda, i think it will be some work to me....

Thanks for your advice... i guess you meant the Other "HTC manufactured phones" forums. Ill have a lokk at these
[Samsung Galaxy A50s Questions & Answers] Christanval:
Hello everyone please help my samsung A50s has bootloop and keep restarting after update android Q?

I have flash latest firmware with odin work successfully but it not solve the bootloop problem its keep restarting

Please help
[Galaxy Grand Prime General] Hilal GR BRO:
I am posting this thread at Samsung galaxy grand prime site because people view very much . I am asking to do this for me that my android tablet un-t707 is kit kat and do not support all apps I want a ROM and a recovery with android 6 and up for my tablet I am a ff player that my mobile is broken and can't repair because of no money

I am requesting to the developers to do this work for me

Tablet model:UN-T707

Tablet name:Universal 4g

Android version :4.4.2

SDK version:19

Plzzz make a better ROM without bugs

If you can succeed this project that will be so kindful for me I will share the ideas to everyone I know

So plzz make it quick
[Magisk] Didgeridoohan:
There's nothing official, but there has been similar reports here in the Magisk forums from time to time (you'll likely find finding if you search for a bit).

There's also been Github issues opened, like here:

No OTAs available with Magisk · Issue #2657 · topjohnwu/Magisk

Please see a reddit discussion I created for this issue. Since owning my Pixel 4XL since launch, and being rooted with Magisk, I've yet to receive one OTA update via the settings app. When a monthl...

github.com

I do not have any answers to your closing questions, but there are some tips and hints found here and there (like in the above linked GitHub issue).
[Magisk] scootley:
Thanks! Actually after uninstalling Magisk (restoring stock boot image), I still have no OTA update showing as available, so for now it does seem that for whatever reason it really is not available for me and I presume it is unrelated to Magisk.

However, if you look at the comments on that github issue and the related reddit thread, several overlapping/conflicting theories are presented, including:

1) Having your bootloader unlocked (independent of Magisk) prevents OTA updates from being made available to you [which to me is absolutely in conflict with my personal experience in the past]

2) Having Magisk installed prevents OTA updates from being made available to you [consistent with my experience]

3) Even after uninstalling Magisk, OTA updates are not made available to you for either some time or forever due to a theory that Google knows you had Magisk and penalizes you (either on purpose or perhaps as a protection from update failures including some time buffer for extra safety) [consistent with my experience]

4) If you ever manually check for updates while Magisk is installed, it prevents them from being made available to you then and subsequently (for how long I dunno). But for a Pixel device I find this to be nonsensical, since even with "Automatic system updates" turned off, a Pixel device will still check for updates (daily?) and notify about them. It just won't install them and prompt for reboot. With this setting on (the default), it will actually install them and prompt for reboot.

5) See the first post for other items. The list in this post is no longer being updated.

But in general I wish this were better understood with supporting evidence on what is really happening, and can certainly try to contribute to that research myself if someone has suggestions on how.
[Magisk] Didgeridoohan:
Yes. I haven't seen anyone with any proper info on what is actually going on. Only (more or less credible) theories... But I haven't actually looked into it.

If I had a Pixel device I might have been tempted to do some research myself. The only possible piece of info I've got that could be remotely related is that OnePlus (at least used to, I haven't used an OEM build in years) detect root with their OTAs and would only offer the full ROM package unless you added the OTA service to MagiskHide.
[Magisk] BostonDan:
I found that if you even have magisk zip on your sd card, the update will detect and prevent install of system updates. This stays set until the next month's update (at least that was my experience with pixel 3xl and my current 1+ 8 5g.)

Cheers,

B.D.
[Magisk] Didgeridoohan:
Prevent the installation, or the OTA check/notification?
[Magisk] BostonDan:
Didgeridoohan, you are correct. Prevent OTA check/notification. Sorry for my misleading verbiage.

Cheers,

B.D.
[Magisk] dcarvil:
I have a Pixel 3, and I've had the problem off and on for the last 18 months or so. I've never been able to find any pattern on what causes it to start or stop working. I received OTA notifications and updates for several months after rooting my phone, then one month OTA notifications just stopped working (no longer detecting updates). I took a logcat while checking for updates and saw the update program errored complaining about a corrupt partition.

That continued until the end of September. The Android 11 update came out at the beginning of September, and I was still getting "no updates available". I delayed manually installing the update, and near the end of September the updater suddenly notified me of the update and was nagging me to install it.

I installed the update, and for a couple of months after that, I could check and install OTA updates by restoring the stock boot image. That stopped working after two or three months, and OTA notification has not worked since.

If you want to investigate further, check logcat for the OTA error.
[Magisk] scootley:
Anybody know the package that is responsible for this on a Pixel? Is it com.android.google.gms?

It's possible that "corrupt partition" just means a partition that is checked for integrity before an update has been modified, which could mean if you were rooted that the rooting (and for example magisk's modification of the boot partition on a pixel) was detected somehow. I'll try checking logcat too.

Thanks. In my case I do have the magisk apk and a magisk patched boot image in /sdcard/Download/, so I guess I could try removing those, but...

I checked with my carrier, who did in fact confirm that the update is delayed using language like:

"As of right now there is a delay and we don't have any additional info on it just yet"

"It is defiantly [sic] a delay. We are working with Google to resolve . You are able to check back for updates"

So I guess I would say I am like 75%+ confident that this is accurate and the cause of the delay for me.

After even more discussion with the carrier, they have revoked their prior statement and now say that because they do not sell the pixel 5 themselves, they do not ever delay updates for it and they are 100% up to google.
[Magisk] dcarvil:
Since the January update is out, I got another logcat of my OTA update error. When I manually did the "Check for Update", the updater found the update, said it was starting the download, then said "Your system is up to date" without doing the update.

If I am interpreting this correctly, the reason for the update failure is system_b does not have the expected checksum. Magisk does not modify system, so whatever caused this is not Magisk. As far as I know, I have never modified system. I've never encountered any problems other than these OTA failures, so I am not convinced there really is a problem with system_b.

The same error occurs with both the stock boot image and the magisk patched image.

[ 01-05 11:51:13.144 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/system_b

[ 01-05 11:51:13.151 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(938)] boot_b is not in super partition metadata.

[ 01-05 11:51:13.153 1205: 1205 I/update_engine ]
[INFO:dynamic_partition_control_android.cc(319)] Loaded metadata from slot B in /dev/block/bootdevice/by-name/system_b

[ 01-05 11:51:13.162 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1158)] The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.

[ 01-05 11:51:13.163 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1163)] Expected: sha256|hex = CC6CD98FB684FDEE9B4E8253338D4E8B34CAEC90FA533E638C45132C89DAA175

[ 01-05 11:51:13.164 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1166)] Calculated: sha256|hex = 8950BA8882AE17BC240BA54603811E50AC22FFE7E54706004F4D42ECF41FF24B

[ 01-05 11:51:13.165 1205: 1205 E/update_engine ]
[ERROR:delta_performer.cc(1177)] Operation source (offset:size) in blocks: 0:1,7916:1

[ 01-05 11:51:13.190 3159:14736 E/SystemUpdate ]
[Execution,PreDownloadValidateAction] UpdateEngine.verifyPayloadMetadata() failed.
[Magisk] Didgeridoohan:
@dcarvil That's different from the described issue in this thread though. Here, the update isn't even found at all...
[Magisk] scootley:
You could probably look in /data/system/system-update-info.xml or maybe see here to find the URL of the OTA update zip that it is attempting to install.

Then download the zip somewhere, open it, and find where in the update script in it looks for the quoted expected checksum and verify what partition it is looking at.

And then you could just try to re-flash that partition from a factory image to get it back to normal.
[Magisk] scootley:
Correct. In my case, I don't see any error like this in logcat when checking for an update.

Although @dcarvil's symptom is that it seems to only say there is an update available for a split second and then go back to saying there isn't one.
[Magisk] dcarvil:
The control.installation.current_update_url tag in the xml file is empty. I got a checksum of the system.img file in the December factory image, which is currently installed, and it does not match the expected checksum. That makes me a bit reluctant to try to fix system_b, as I am used to manually installing updates anyway.

Thanks for the suggestion, though.
[Magisk] scootley:
Is it possible that you have the December update installed for one carrier and your phone is checking for the OTA for another carrier? Did you switch SIMs or carriers? Looks like Verizon has its own OTA and other carriers use a separate one.
[Magisk] dcarvil:
I suppose it is possible, but I don't think so. I have a non-carrier branded phone purchased directly from Google, with a Verizon SIM from an MVNO. I've always thought my OTA updates came from Google, but don't know how I would confirm that. I've never switched SIMs. All my manually applied updates have been Pixel Factory images (the non-Verizon version) direct from Google at https://developers.google.com/android/images.

Since I have had successful OTAs at times in the past, that doesn't seem likely.
[Magisk] scootley:
Yes they come from Google but you can see on that link you sent that there are Verizon-specific Pixel 3 images (lately).

So if you you manually applied the non-verizon one from that page for a month when there was a verizon one (on the same site, listed right below/above the other images for that month), then later OTAs would presumably fail due to a checksum mismatch.

See here too.

EDIT: I don't think it matters where you bought your phone, but I could be wrong. In other words if you are on Verizon and there is a Verizon pixel image then that is the image that your phone will install even if you bought that phone from Google unlocked and without a carrier designation at purchase.
[Magisk] dcarvil:
That's interesting. Thanks for the info.

I downloaded the Verizon December factory image, but the system.img checksum in that image does not match the expected checksum either. I'm just going to stick with my manually applied updates for now. I do not want to get any Verizon software on my phone, even if that resolves the OTA issue.
[Magisk] scootley:
Here's an update:

I got an OTA update notification for the December 2020 Pixel 5 update on 13-January 2021. This is about 7 days after re-rooting and enabling "MagiskHide Props Config" and using it to get SafetyNet to pass and to get my device to be Play Protect certified.

My regular MagiskHide settings have it enabled for:

1) com.android.dynsystem (including every sub-item within it)

2) com.google.android.gms (including every sub-item within it)

3) com.android.vending (including every sub-item within it)

I have no idea if those things are connected or if it's just a coincidence and something else (see my original post at the top of the thread) caused the delay.
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
This guide only applies to the phones with region number C636!!! I'm not responsible for what you do with your phone, take your own risk.

This guide will erase all the data on your phone, so backup before following.

If you downgraded your phone to 10.1.0.131 install GMS and then your phone&HiSuite keeps telling you that 131 is the latest version, this guide is for you.

All credits goes to "GSMFix" youtube channel and "Ictfix" website.

1) Get a USB OTG cable/stick (USB Type-A to Type-C). I got mine for 1.5 Dollars at Mr.DIY.

View attachment 5176071

2) Download this file. Firmware

3) Copy the "Dload" folder to your USB stick.

View attachment 5176075

4) Using your OTG cable/stick, insert the usb stick to your phone.

5) In your phone dialer, dial *#*#2846579#*#*

6) Click on Software Upgrade

View attachment 5176081

7) Click on Memory card Upgrade

View attachment 5176083

8) Wait patiently. Upgrade should take around 10 minutes.

9) After you boot into your phone, set up your phone and install GMS using Googlifier.

10) Voila! Now you can update your phone in the settings! First, it will update to 10.1.0.182 and then 11.0.0.151
[Huawei P40 Pro Guides, News, & Discussion] jovemfla:
Works perfectly, congratulations on the tutorial
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
Glad to help
[Huawei P40 Pro Guides, News, & Discussion] desertflyer:
The firmware download link in the op is broken. Could someone mirror it?
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
It works now
[Huawei P40 Pro Guides, News, & Discussion] bckfrm:
It says the file is corrupted or needs a pasword pasword to extract. Is there a pasword?
[Huawei P40 Pro Guides, News, & Discussion] Okijaamaka:
Hello thank you for the tutorial

Please I am on 10.1.0.131 (C636) and have install GMS

will I lose everything if I upgrade via USB?
[Huawei P40 Pro Guides, News, & Discussion] Okijaamaka:
This is my current Version

Will it work

View attachment 5285153
[Huawei P40 Pro Guides, News, & Discussion] Ronju Khan:
My GMS is working absolutely fine enabling the phone to use all my banking apps and wallets. If I follow this

it seems like to reinstall GMS again and loosing settings and data.

So rather I will stick with EMUI 10 cause not guaranteed that banking apps will run perfectly on this method of GMS installation.

Thank you
[Huawei P40 Pro Guides, News, & Discussion] Okijaamaka:
Me too

I have decided to stick on this version rather than upgrading

My only problem is puch notifications
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
Yes.
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
try re-downloading and make you you followed the guide exactly. It's not corrupted and doesnt have pass. Maybe try with another pc?
[Huawei P40 Pro Guides, News, & Discussion] Okijaamaka:
Thank you but I will not doing the update again since I have gotten my push Notifications working 100%
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
I also have my push n. working with the latest EMUI 11 update
[Huawei P40 Pro Guides, News, & Discussion] Keysii:
My current version is ELS-LGRP4-OVS 10.1.0.183. I've just recently reset to factory settings. will this download update my phone to EMUI 11? i originally thought that resetting back to factory would enable auto updates from OTA.
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
You need to look at your region number, if your OTA updates are broken, resetting won't fix it. If your region number is C636, this guide can fix it.
[Huawei P40 Pro Guides, News, & Discussion] Keysii:
did the flashdrive need to be empty to do this?
[Huawei P40 Pro Guides, News, & Discussion] faceliler:
I don't really know
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
Better to be empty and formatted NTFS.
[Huawei P40 Pro Guides, News, & Discussion] Nadym:
My one is C636 (original build was C636E3R5P4) but still getting an "Incompatiblity with current version" error when trying this. Current version is C636E3R5P1 10.1.0.182.

Any reason as to why this could be?
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
I don't understand you. ”when trying this” what are trying? What firmware version do you try to install?
[Huawei P40 Pro Guides, News, & Discussion] Nadym:
When I tried this guide, i.e. the DLOAD method using the C636E8R5P1 build in the first post.

I tried another firmware too but all it does in eRecovery is just show a blank screen with the EMUI logo then turn off the screen, then turn back on and show the same thing.
[Huawei P40 Pro Guides, News, & Discussion] Nadym:
One thing I did notice is that the build number says N39 instead of N29, I'm 100% sure I used the right firmware in HiSuite proxy. Any ideas?
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
No. You made a mistake. I think you used a P40Pro+ firmware.

See here.
[Huawei P40 Pro Guides, News, & Discussion] Nadym:
Oh thank you, do you have the firmware for C636? Because in your post it's only for C432?
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
I have many things. I dont know if I have what you need because more details are needed and it is something to work on it. You can use my thread as an example.
[Huawei P40 Pro Guides, News, & Discussion] huutho444:
It can update to EMUI 12 ?
[Huawei P40 Pro Guides, News, & Discussion] midnightx86:
Hi, i have the same problem, but with C432, do you know how to fix that?
[Huawei P40 Pro Guides, News, & Discussion] lapu:
i tested this thread R5 on the version as yours (R4).

unfortunately, it didn't fix the OTA broken issue.

i dont know where to get R4 dload version to try again.
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
It is no R4 on dload firmware. You can restore R4 upgrading with HiSuite proxy, on a particular moment (between EMUI10 and 11 or 11 and 12).
[Huawei P40 Pro Guides, News, & Discussion] lapu:
these are broken after downgraded to 10.1.0.134:

1. connection with hisuite (no more adb connection)

2. OTG (adaptor works with my Mate10)

3. OTA

4. Huawei asistance (no update selection at all)

i got GMS installed. but the app that i use everyday does not work: mcdonald apps (lol)

so, i gave up on GMS and wanted to restore the phone to normal mode.

the only option i have now is the NM-card (transfer file from PC using wifi) which i did with the firmware of this thread.

C636 dload format is hard to come by, lession learned.
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
Not really. See my upgrade message on first page of my thread from signature. That means using Hisuite Wi-Fi version.
[Huawei P40 Pro Guides, News, & Discussion] lapu:
oh! i really miss this one. thanks for the hint! much appreciated!
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
1st point, there is a link. You need to use that just first time. After first upgrade you can use OTA. Sim card in the phone.
[Huawei P40 Pro Guides, News, & Discussion] lapu:
ha, downloading version 10.1.0.158 right now. thanks again yo!
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
It is easy, right? Keep an eye on my first page of my thread.
[Huawei P40 Pro Guides, News, & Discussion] lapu:
if you know the way :)
[Huawei P40 Pro Guides, News, & Discussion] Baronz17:
Hello, please help me, I want to downgrade my huawei p40 pro to install GMS, but I have a mistake in the fw selection because my region code is like in the picture. And also there is also a "preload software version"

Please help me thank u

View attachment 6023574
[Off-topic] akshay00087:
wq
[Off-topic] akshay00087:
as
[8525, TyTN, MDA Vario II, JasJam General] chasx003:
My screen alignment issue is not the same as the reported "upper right corner pressed down" instead, my screen is always pressed down on the left side. So if I if press the screen anywhere the screen registers all the way to the left. occasionally the screen will align correctly, but only in one mode. if i align the screen in portrait, and then change to landscape, the alignment is off. The weirdest thing is while playing solitaire, i will drag a card off the deck, and leave my sytlus at the same point, and the card will jump around as if i am moving the stylus. I have done the "business card" trick, and while it works sometimes, the left side issue comes back. any ideas?