yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Compact Q&A, Help & Troubleshooting] roohooo:
Hi all,

I bought a spare Z5 Compact recently, it is a UK model with stock firmware "Customized UK" (1298-5497). I'm living in Germany and already have a German Telekom version of the Z5C, which is running the latest LOS 17.1. This phone is utilizing GPS, GLONASS and BDS satellite systems without any issues. With the UK model of the phone however, I am only able to get signals of GPS and GLONASS satellites.

I've tried flashing different ROMs, including a German Telekom stock ROM, but it did not solve the GNSS issue. Both phones are E5823 and use the same baseband version. According to the serial no., the UK phone should even be "newer" than the German one.

So question is - could this really be a phone model with different hardware, or will it be possible to make the phone utilize BDS satellites by software/firmware modifications?

Any advise or suggestions are much welcome!

Cheers,

r.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] Berni-0815:
As well as there are devices that are using different 4G (LTE) bands, there might be devices that uses different gps bands.

But that's a guess, though.
[Xperia Z1 Q&A, Help & Troubleshooting] flatauchen:
I am trying to install XZDualrecovery without success, can someone help me?

I received this when I tried to run:

==============================================

= =

= XZDualRecovery =

= Maintained by [NUT] =

= =

= For Many Sony Xperia Devices! =

= =

==============================================

1. Installation on ROM rooted with SuperSU

2. Installation on ROM rooted with SuperUser

3. Installation on an unrooted (Lollipop 5.0) ROM using rootkitXperia

4. Install ADB drivers to windows

5. Open an ADB shell

6. Exit

Please choose install action.

[1,2,3,4,5,6]?2

cannot connect to daemon at tcp:5037: cannot connect to 127.0.0.1:5037: Nenhuma conexão pôde ser feita porque a máquina de destino as recusou ativamente. (10061)

* daemon not running; starting now at tcp:5037

* daemon started successfully

=============================================

Waiting for Device, connect USB cable now...

=============================================

Device found!

=============================================

Getting device and ROM info

=============================================

Device model is C6943

Firmware is 14.6.A.1.236

Android version is 5.1.1

=============================================

Step2 : Sending the recovery files.

=============================================

adb: error: cannot stat '..\tmp\dr.prop': No such file or directory

adb: error: cannot stat '..\system\bin\chargemon': No such file or directory

adb: error: cannot stat '..\system\bin\mr': No such file or directory

adb: error: cannot stat '..\system\.XZDualRecovery\xbin\dualrecovery.sh': No such file or directory

adb: error: cannot stat '..\tmp\NDRUtils.apk': No such file or directory

adb: error: cannot stat '..\system\.XZDualRecovery\xbin\rickiller.sh': No such file or directory

adb: error: cannot stat '..\tmp\byeselinux.ko': No such file or directory

adb: error: cannot stat 'byeselinux\byeselinux.sh': No such file or directory

adb: error: cannot stat '..\tmp\wp_mod.ko': No such file or directory

adb: error: cannot stat 'byeselinux\sysrw.sh': No such file or directory

adb: error: cannot stat '..\tmp\modulecrcpatch': No such file or directory

adb: error: cannot stat '..\system\.XZDualRecovery\xbin\busybox': No such file or directory

adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma': No such file or directory

adb: error: cannot stat '..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma': No such file or directory

adb: error: cannot stat '..\tmp\installrecovery.sh': No such file or directory

=============================================

Step3 : Setup of dual recovery.

=============================================

Unable to open /data/local/tmp/recovery/install.sh: No such file or directory

Unable to open /data/local/tmp/recovery/busybox: No such file or directory

sh: /data/local/tmp/recovery/install.sh: not found

=============================================

Installation FAILED!

Please copy and paste the contents of this

window to the DevDB thread for troubleshooting!

=============================================
[Moto G Stylus (Moto G Pro) Questions & Answers] Marty4:
Hi everybody,

Right after upgrading my Moto G Pro to Android 11 (SOFIAP_AO_EEA_RPR31.Q4U_20_26_2), I wanted to install the February security patch and received the following message:

I wanted to apply the same procedure for OTA updates on my rooted phone that was working under Android 10 (cf. this posting).

Anyone has an idea how to solve this?

Thanks in advance for your help!
[Moto G Stylus (Moto G Pro) Questions & Answers] k3dar7:
today i receive february security patch (RPRS31.Q4U-20-28 (chanell: reteu)), install & root via this method without problem, also before upgrade from A10 to A11 work with same method...

sure you restore stock boot image via magisk manager (step 3) ? your error message look exactly as without restored stock boot...
[Moto G Stylus (Moto G Pro) Questions & Answers] Marty4:
Thank you for your reply! Yes, I did uninstall Magisk with "restore images" ("Restoration done!" toast appears on the screen) - but still the problem persists and I receive the error message when I try to update...

Any other idea what could block my OTA update?
[Moto G Stylus (Moto G Pro) Questions & Answers] k3dar7:
You have disabled SmartUpdates? (step 2)

Try:

1. Install Magisk again to CurrentSlot

MagiskManager/Magisk-Install/DirectInstall

2. Disable Wifi and MobileData

3. Reboot

4. MagiskManager/UnstallMagisk/RestoreImages

5. Enable Wifi and/or MobileData

6 . initialize manualy OTA search:

(Android)Settings/System/SystemUpdate

This steps maybe to not have Magisk installed when OTA is inicialized. Not know if help :-)
[Moto G Stylus (Moto G Pro) Questions & Answers] Marty4:
Thank you so much!

Yes, "Smart Updates" are disabled.

I tried what you suggested - unfortunately, same error message on step 6... :cry:
[Moto G Stylus (Moto G Pro) Questions & Answers] Marty4:
I still don't understand what blocks the OTA update on my device:

My current Android 11 was flashed with the Rescue and Smart Assistant (LMSA) after a full wipe.

I re-flashed the original boot.img (to completely unroot).

I re-flashed the original recovery.img on both partitions.

I deleted the cache of "Motorola Update Services".

...Now I'm running out of ideas how to get rid of the "Package verification failed" message...

This should be the relevant extract from logcat:

02-28 19:38:45.512 1580 1580 E update_engine: [ERROR:delta_performer.cc(1205)] 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.
02-28 19:38:45.515 1580 1580 E update_engine: [ERROR:delta_performer.cc(1210)] Expected: sha256|hex = 63B6A76F2009E796A2A1F3F6A70957DB12E2146A6929A659505F9EC5BCA16A53
02-28 19:38:45.518 1580 1580 E update_engine: [ERROR:delta_performer.cc(1213)] Calculated: sha256|hex = 6FE9E5AF9EC26F47B555E7088A8BED085C49BE551AAB5C584D140232F02D6C68
02-28 19:38:45.525 1580 1580 E update_engine: [ERROR:delta_performer.cc(1224)] Operation source (offset:size) in blocks: 0:2,4:1,43:2,161:56
02-28 19:38:45.527 1080 1218 E qdmetadata: paramType 2048 not supported
02-28 19:38:45.534 1580 1580 W update_engine: [WARNING:mount_history.cc(66)] Device was remounted R/W 46 times. Last remount happened on 1970-10-12 05:15:10.000 UTC.
02-28 19:38:45.544 8783 9015 D OtaApp : UpdaterEngHelper:verifyPayloadMetadata:isVerifySuccessful=false
[Moto G Stylus (Moto G Pro) Questions & Answers] androiddiego:
I still have android 10. The Feb security patch worked on my phone fine. You may be trying to install a 10 patch onto an 11 system.
[Xperia Z5 Compact Original Android Development] payjo73:
Good morning,Good afternoon or Good night,,,Depending on when you read this thread :LOL::LOL::LOL::LOL:

I created a Deodex patch from latest build 32.4.A.1.54 and include superusermod

I do that for my Z5 Compact E5803, but now I wanna share it with all Z5 Compact users. It should be work on E5823 too

Just edit your "build.prop" if you want.

I tested it there aren't any problems on it.

Installation :

You just reboot to twrp recovery and flash deodex.zip and wipe cache and dalvik cache

At the end reboot to system.

Create A Backup Before Flashing

I AM NOT RESPONSIBLE FOR ANY BRICKED OR ANY DAMAGE IN YOUR DEVICE!!!

​

Download :

CEKICROOT

Please HIT THANKS ! if my post helped you in any way.
[Xperia Z5 Compact Original Android Development] W1j:
thanks
[Xperia Z5 Compact Original Android Development] occho:
thanks agan payjo
[Upgrading, Modifying and Unlocking] back:
hi ihave break my hand set charging base . the charging base ways are broken any one have any picture or schematic .plz upload here or mail in my mail box lovingzaib@hotmail.com

thanks in advance

back
[Xiaomi Mi 10T Lite Questions & Answers] =Anderson=:
How to install mi 10t lite android 11 in Europe, when will it be available, does anybody know?
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
Either install the global ROM (with a factory reset) or wait a couple of days - EU ROM comes with a slight delay after the global version (if there are no major issues).
[Xiaomi Mi 10T Lite Questions & Answers] =Anderson=:
Do I lose warranty if I do that?

And how do I install global rom, can u send some tutorial link
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
You should not lose your warranty (at least in Europe bootloader unlocking won't void it).

I would suggest you to make yourself familiar with flashing in general (adb, fastboot, tools, rom formats etc.) before you attempt something.
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
Recovery Android 11 EU ROM, flashing from TWRP works fine. Notification LED is finally clearly visible with the latest ROM.

https://bigota.d.miui.com/V12.0.1.0.RJSEUXM/miui_GAUGUINEEAGlobal_V12.0.1.0.RJSEUXM_15bfbef742_11.0.zip

Source: 4pda
[Xiaomi Mi 10T Lite Questions & Answers] Barmenchik:
Good news but UK still with 12.0.8.0 (QJSEUXM)...
[Xiaomi Mi 10T Lite Questions & Answers] Wattsolls:
Try Switch Region to france and you´ll get 12.0.9.0 . At least in Germany it works. ;)

But it is only a very small Update.
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
It was the same for me, so I just flashed recovery ROM from TWRP (at first from 12.0.8.0 to 12.0.9.0 and then to 12.0.1.0). It should work with locked bootloader and stock recovery as well (some extra steps like renaming file to "update.zip" and putting it to the root of SD card, or using ADB sideload might be necessary).
[Xiaomi Mi 10T Lite Questions & Answers] Barmenchik:
OMG! It works for UK as well... Thank you. Now just waiting for Android 11... ;)
[Xiaomi Mi 10T Lite Questions & Answers] fizzy900:
I think the A11 EEA Recovery ROM got released but you have to be a Beta tester? Something to do with pilots lol

So hopefully that means there will be a full 11 rollout soon
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
I thought that EU Andoid 11 version is stable, but it seems to be really only beta as mentioned on 4pda. There are some misalignments in message notifications and phone crashed quite nastily once (had to reboot it 5 times until it finally fully started). RAM usage seems to be a bit too high as well resulting in more app redraws/reloads than necessary. I hope that fixed version will be out soon. 🙂
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
And the very same file is out as official "beta stable" now.. :)

Xiaomi Firmware Updater

The ultimate script that provides firmware packages for Xiaomi devices.

xiaomifirmwareupdater.com
[Xiaomi Mi 10T Lite Questions & Answers] =Anderson=:
Do you know for how long approximately we will have to wait for Android 11 stable in Europe because Beta is now out?
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
From what I understood how Xiaomi does the updates:

1. at first there is internal beta

2. after successful internal testing, it goes to closed beta

3. after closed beta it goes to public beta

4. if there are no (major) issues, the very same version is released to public in batches as "stable beta" (recovery ROM)

5. if there are no (major) issues, the very same version is released to public in batches as "stable" and fastboot ROM is released as well

So I believe that what we've seen is that "public beta" V12.0.1.0.RJSEUXM became "stable beta" and will transition to "stable" in the coming weeks. However when exactly is it going to hit your phone is impossible to tell, they chose phones by country + some random parameters. Manual installation is probably the best way how to have the latest ROM version.
[Xiaomi Mi 10T Lite Questions & Answers] plamennikolov3:
искам да попитам моя сензор за близост на светлина работи тук спира и го няма никъде В настройките Как да настроя това, за да поправя моля помогнете I'm sorry to write exactly This may not be the topic But I'm still with my ten lite and the sensor doesn't work andЗа съжаление there is no slider for incoming calls where to set it there are a lot of truncated functions why? Sorry I want to ask my light proximity sensor works here stops and is nowhere In the settings How to adjust this to make a fix please help
[Xiaomi Mi 10T Lite Questions & Answers] Ethan66:
Exactly this version is now arriving on my German stock phone as an OTA update today. The phone is new and I had never participated in any beta program or anything like that. Thus it should be stable production right now. Is this true?

Did I get this right? Xiaomi is not differentiating beta-version numbers from stable version numbers? In other words: I cannot differentiate the release train between a beta and a stable channel from looking at the version number?

Thank you!

Ethan
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
Yes, it seems to be considered as a "stable" now.

And yes, there is no difference in the version number between beta/stable. ROM is not being re-released, it's always the same ROM with the same download link and with the same hash. Beta/stable beta/stable is just a naming convention which changes over time. There is no special beta channel in a traditional sense as you might be used to from PC/ mobile applications.
[Xiaomi Mi 10T Lite Questions & Answers] Ethan66:
Thank you, _mysiak_! This is more clear now.

What is disappointing for me is, that now, after I have thoroughly decided to install the OTA update, it has disappeared again and is no longer found by the Xiaomi updater. How strange.

Maybe there were bugs and it is set back to beta status?

You probably never know the algorithms how Xiaomi distributes updates...

Maybe they just save bandwidth right now. ;-)
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
I've read exactly that explanation - if you don't install the update when it's received, your "slot" is released after few hours/days and offered to someone else. It is supposed to save bandwidth and prevent overload of Xiaomi servers. But I have no idea if it's really true.. :)
[Xiaomi Mi 10T Lite Questions & Answers] =Anderson=:
So the update will shortly be arriving now as stable update via phone updater. If someone has a link when it arrives you should put it here
[Xiaomi Mi 10T Lite Questions & Answers] _mysiak_:
Link will be the same as already provided, you can download and install the update anytime.
[Samsung Galaxy S (4G Model)] k24a1:
i know this device is really ancient, but i'd like to mess with it a bit and see if i can get a custom ROM to work on here. i'm not sure where to start and a lot of links appear to be broken as people have dropped support for these devices. help is very much appreciated.
[Samsung Galaxy S (4G Model)] Theraze:
Sorry, been a few months, but... any specific goals for what you're trying to play with? Fairly certain that I can dig up Omni (Marshmallow) and maybe Slim (KitKat) or some of those other ones, but... had a few hard drive crashes since my T959V was used for anything but either a remote camera station to watch new chickens grow or a locked down Zoom device. :)
[Samsung Galaxy S (4G Model)] Theraze:
Here are a few T959V zips from way back in the day. The general way you got new recoveries back then was by flashing ROMs and hoping that the newly included recovery worked and had better features than what you had, but Team Acid does have a few older standalone versions. All of the attached should be the original archives from 5+ years back. All of these were downloaded from XDA back in the day and are not my original content.

I do also have a panoply of different editions of Odin3, but unless you feel the need for Odin 3.07, 3.09, 3.11.1, or 3.12.7 specifically, then whatever you get online will probably be fine. In general, Heimdall can take care of any Odin needs and has the benefit of open source. If my memory serves right, in general Heimdall and Odin (and even Odin to Odin) didn't play nicely and often required switching the USB drivers manually. My recommendation is to stick with Heimdall unless you get entirely stuck.

Note that the best source for getting started working on the T959V that still remains currently is probably the TeamAcid SourceForge site, linked below. This includes the CyanogenMod7 and CyanogenMod9 often referenced for getting a device from GB to ICS, as well as many one-clicks and other tools.

Here are a few SF links that seem to still be up and should offer more options as well. I found these today by either searching for SGS4G or T959V. Most of these are actually GB (2.3.6) but Team Acid does have the first stable ICS (4.0, CM9) included.

Each is given as Name - last update: link, and with the newest first.

TeamAcid - October 2013 (CM9): https://sourceforge.net/projects/teamacid/files/

CM10.1 - June 2013: https://sourceforge.net/projects/cm101sgs4garies/files/

ICS - July 2012: https://sourceforge.net/projects/icsmuttforsgs4g/files/

JoyOS - June 2012: https://sourceforge.net/projects/joyossgs4g/files/

moKee - June 2012: https://sourceforge.net/projects/mokeesgs4g/files/

CM7 - April 2012: https://sourceforge.net/projects/cm7sgs4g/files/

MIUI - March 2012: https://sourceforge.net/projects/sgs4gmiui/files/

I've included the Heimdall I downloaded years ago in case it's down, but the official website is still up here, and lists versions for OSX and Unix:

Heimdall | Glass Echidna
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
CHANGELOGS

i will not be posting changelogs everytime so adding a link below for changelogs

GitHub - HyconOS-Releases/Source_Changelog

Contribute to HyconOS-Releases/Source_Changelog development by creating an account on GitHub.

github.com

this is initial build please comment if you find any bugs
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] Ratbyte:
DL PL2 not workink 404 Error
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] dippyshere:
I've been rocking this for about 3 days now, and it's amazing! This is the first custom ROM I've used since my first phone died a few years ago. The Hycon hub settings are pretty cool. It lets you change a bunch of settings like theming, status bar stuff, buttons, lock screen, and it even lets you set a custom header image.

The only issues I've run into are as follows:

5ghz home wifi rarely shows up, but all other 5ghz Wi-fi's I've tested show up and work.

System UI can often become unresponsive. Attached is a screenshot of the stack trace. I'm not sure what's up with that, its probably just something I messed up.

but thank you for this great ROM.

edit: I think the wifi issue can be blamed on the kernel I'm using (fenix hmp)

edit2: I checked, and in fact I was using the stock kernel, so I flashed popcorn kernel and wifi is fixed, but the lag issues are still the same, and sometimes even worse. i did wipe dalvik and clear cache after I flashed the kernel. I've been running on popcorn for about a week now and the lag can be very painful. I've tried: odexing system apps, zip aligning and optimising databases, setting scheduler to deadline, performance governer on all cores. the last one seems to help mitigate the issue, but its a big drain on battery life.
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] Bảo Dora:
I have used this rom before (during 1 week), and i'm so excited about it. UI is clean, beautiful and very like Pixel. Almost all worked well. However, performance and ram management are big problems. My phone was so so laggy. I couldn't listen to music while i was playing game (not heavy game). I couldn't use gcam or any other camera apps with hdr mode. Other kernels didn't help me anything. I hope you will fix it soon. Sorry for my bad english.
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
Thank you guys for details reviews I appreciate the reviews and I assure I will fix most of them upcoming builds soon
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
i have updated download links for july update
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] meta11er:
NFC does not work
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
fixed
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] gouthamram:
Screencast is working or not?
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] gouthamram:
Download link error on ever 100mb to 200mb @keneankit01
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] gouthamram:
Screen mirror not working

No message,no music😒

System update force close

More ram usage but not lag
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
suggestion use 1dm download manger on android or download on laptop using idm download mange you can refresh link both of this so it will resume download failed due to low speed
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
screen cast can be fixed but nokia aka jokia didnt release android 11 yet for sdm660 device for me to copy blobs from other nokia sdm660 device like form nokia 6..2 &7.2
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] MricCall:
These days it's showing android 12 update. I m pretty sure it's gonna brick the phone. Am I right?
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] MricCall:
This
[Nokia 6.1 (2018) ROMs, Kernels, Recoveries, & Othe] keneankit01:
android 12 rom source not yet ready so not yet started a12 roll out of hycon
[Xiaomi Mi 9 Questions & Answers] scarcrew:
Hi, i think i just hard brick my phone. Last time i stuck on fastboot but now its black screen already. I tried to flash fastboot rom via mi flash tool. When i start flashing, it ask for mi account login. Then it continue to load. Within 5 sec, it show authentication fail. Can someone help me? I attached full log. Below is some of the log. U could see it fail at sign edl.

[12:23:49 AM COM20]:origin:AQAAAFMBAAAX7dP4px_qF2OtzQfVI7Gbd8ZUpA

[12:23:49 AM COM20]:SignEdl

[12:23:50 AM COM20]:authentication failed result -6

[12:23:50 AM COM20]:System.Exception: authentication failed The operation completed successfully

at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()

at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)

at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash() at XiaoMiFlash.code.bl.SerialPortDevice.dlAuth()

at XiaoMiFlash.code.bl.SerialPortDevice.ConfigureDDR(Int32 intSectorSize, Int32 buffer_sectors, String ddrType, Int32 m_iSkipStorageInit)

at XiaoMiFlash.code.bl.SerialPortDevice.XiaomiFlash()

[12:23:50 AM COM20]:no provision exit:COM20

[12:23:50 AM COM20]:flashSuccess False

[12:23:50 AM COM20]:isFactory False CheckCPUID False

[12:23:50 AM COM20]:before:flashSuccess is False set IsUpdate:True set IsDone True

[12:23:50 AM COM20]:after:flashSuccess is False set IsUpdate:false set IsDone true
[Xiaomi Mi 9 Questions & Answers] Laptapper:
Did you try to flash img files via adb? Right fastboot flash files for your phone eea global cn...?

If not try it