yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] printf():
While trying to modify my KW88 Pro watch to run AsteroidOS I took the advice of the program and clicked "Format All + Download" without fully understanding what it does. It deletes all partitions. The install then failed with some random errors but I had a brick. I managed to recover it with KW88 Pro firmware (KW88Pro_V1.5_NHH_B_20190114) I found on discourse.fullandroidwatch.com (don't know how legit it is but at least it works now).

While this guide is how to fix the "PMT changed for the ROM, it must be downloaded" error, the above is relevant. You must find firmware for your watch that has the default partition layout if you did not take a backup before formatting or if you don't know the partition layout. In a nutshell you get the PMT error when the partition layout of the scatter file does not match the partition layout of the device, and the stock firmware + scatter file is needed as a reference point. My error:

https://imgur.com/aFZKfOo

Let's compare the start addresses of those 3 partitions to the stock firmware:

https://imgur.com/rV3XBt2

Boot and Logo partitions are the same, but User Data starts at a different address.

If we compare the contents of both the scatter files we see the same thing:

https://imgur.com/OYw10d3

https://imgur.com/DNQ1Ztw

In a nutshell what you need to do is clone the partition layout (start address variables + offset variable) into the new scatter file, but maintain all other variables of the scatter file. It should also be mentioned that there are other partitions in the scatter file that I had from AsteroidOS that did not match the physical layout of the firmware I used, and even though I was not flashing them I still had to edit the scatter file.

Afterwards using these settings I flashed successfully:

https://imgur.com/TdVRDEV

I also want to note that the End Addresses will not match even with the correct partition layout because different firmware has different sizes on disk, despite the space allocated for the partitions. In theory if you want you could reclaim unused space by tweaking the original scatter file and then the custom scatter file, but it may also impact your future updates if the partition is too small.

Hope I made someone's day easier, best of luck
[Other SmartWatches] kutiz21:
Can you explain the getting the partition start and offset address part?

Because I think im going to brick my phone really soon if I can't make this auto-generated scatter I got from internet work to flash my phone back to stock rom.

The scatter itself already has some bugs with userdata partition (Too large)
[Other SmartWatches] printf():
Sure thing. The scatter file which is for stock firmware vs. the file for new firmware will not allocate the space on disk based on what partitions are actually, physically on it. The new scatter file for custom firmware will be for what the devs had on their device, but not what you actually have on yours (different hardware versions, android releases, w.e.). What you need to do is take the existing partitions of your device, the start addresses for them, add the size of that partition to get the end address and using that information supply that data to the new scatter file. You COULD in theory also change the partition sizes but that is more prone to error so I did not recommend that. So what I did would visually look like this, the | are partition start / end markers

Original scatter file:

|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxx|

vs new scatter file:

|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxx|

vs the patched scatter file:

|xxxxxxxxxxx||xxxxxxxxxxx||xxxxxxxxxxxxxxxxxxxxxxxxxxx||xxxxxxxxxxxxxxx....................||xxxxxxxxxxxxxxxxxxxxxxx....................................................||xxxxxxxxxx........|

Tl;Dr An offset is basically a way of saying address + data/space (until next segment at next address).
[Other SmartWatches] kutiz21:
Intersting

I used Smartphone flash tool version 3 and 5 and I have managed to use my own image to flash numerous phones, encrypted with a key or with no keys (Auth file).

Usually, I would use Google's method of flashing back rom that is using a zip file contains bunch of flashable system images and let fastboot app itself flash it.

I dumped my images using dd tool and img2simg (Full blown raw ext4 file, not sparsed.)

Because fastboot likes sparse images rather than raw ones and flashable sparse images can be easily flashed with SP tool normally (It can make phones bootable but will more likely making phone unbootable most of the time)

I do aware that I need to adjust the address thing. But normally, using the start address based on the scatter. SP app can automatically calculates how large the image and it can prevents you from flashing because it is too large.

But this particular phone won't flash even if it is the stock rom. Which dumped and got its scatter file generated by some sketchy "miracle box".

My best guess is that the scatter file was tied to specific emmc chip and it is not for my phone's emmc so there might be some difference there.

Because when I use the REAL flash scatter file from actual OEM (In this case, Nokia 1, European Variant). It can make my APAC counterpart can be flashed normally, even with my custom sparsed or raw image (These 2 variants were kinda different, technically.)

I would like to point out that newer SP flash tool app tends to hate to co-operate with scatter scripts so that could be a reason (I used older build of version 5 and it only gets the userdata bug, but it does lags the app when the bug "PMT changed for the ROM, it must be downloaded" show up. Because it was a bug and it hadn't fixed in that build, which is fixed in the latest build of SP app when I attempt to flash)

And flashing extracted "stock" rom from flash tool and flash it back over fastboot tool tends to break system OTA and make my phone on bootloop (I highly doubted it was the raw image thing, because of the free space it can allocated. I flashed it raw back then I think because i don't know what happened yet, keep in mind that stock rom images shipped for SP flash tool were most likely in raw state, not compressed like sparse images)

And SP flash tool also hates raw dd images too (too big?????)

So like. What do I need to fix the script? What program that can calculate the exact offset for it? I still be able to flash the stock rom with fastboot fine. But for "unforeseen consequences" that makes it unbootable, I still need it.

Say the scatter is not reliable or doesn't exist. How do I use the readback function and then use some aged apps like MTK droid tool to generate actual offsets and possibly generates scatter for me (Most likely will not work because my phone's Android is too new for it). I used to work with Android 4.2.2 so it's really easy back then.
[Other SmartWatches] printf():
I'm not sure how to get the data when no original scatter file exists, I was fortunate enough to find a reference for my stock OS. The other scatter file was for AsteroidOS. I think the easiest way to explain what I did would be to share the scatter files. Effectively start address + partition size should not be larger than the start address of the next partition.

Stock scatter file:

https://pastebin.com/tfFDCPfT

Original AsteroidOS scatter file:

https://pastebin.com/0z7DtL9u

Patched AsteroidOS scatter file:

https://pastebin.com/iiYZTzBt

Take note that in my original post screenshots, AstreroidOS was only flashing 3 partitions (corresponding to the is_download: true/false field of the scatter file). That told me that those were the partitions / boundaries that need to match, the other partitions were irrelevant (for the purpose of flashing anyway). AsteroidOS itself is contained inside the userdata partition, effectively leaving other ~20 partitions as "lower layers" or unused.
[Other SmartWatches] kutiz21:
So my insights were true. It does automatically calculates the free space of a partition to whether allow you to flash or not. But I tried fiddling with it and it doesn't work. I might try to individually comment out those partitions as unflashable and try it out.

One more thing is that I used to had this error. But it will be gone when I explicitly referencing SP flash tool the preloader partition image (flashing it or not doesn't matter) alongside with all of my custom images but they must be fully loaded in the app.

You will not be able to flash if it can't fully loaded all partitions that has the property "is_download: true". Maybe that should allow me to do the flash.

Any more thoughts on " boundary_check and is_reserved"? Because I used to poke with these and managed to flash my other phone successfully.

I don't have the phone to test right now but more food for thought I guess.

Cheers!
[Other SmartWatches] printf():
Not sure what is_reserved does, but boundary_check probably validates the scatter file vs. the layout on the disk. If you don't do the check though you are risking overwriting a partition which might be needed for the lower layer functionality - keystore, firmware, etc.
[Other SmartWatches] iceblue007:
Thx. Definitely clear about what u said. But still confused at is that all partitions recreate automatically when you trigger 'format all partitions and download' in SP Flash Tool and flash the firmware using the scatter file inside? Besides what u explained just like the disk partition is always solid no matter how u flash? Is that a truly theory? I had thought that the partitions are always controlled by ourselves like recreate, resize anywhere when we format the whole partitions.

I'm a totally Newbie, so any tips will be appreciated.
[General Questions and Answers] B4nDiT90:
Hello ,

I looking a new rom for my Acer ICONIA ONE 10 B3-A20 witch CPU Mediatek MTK8163

my actual Rom is Acer_AV0L0_B3-A20_RV03RC02_WW_GEN1-MT8163 and some app show me message ther cant be install because i have old android .. It show Android 5.1 .

There is any solution to update this room ? I know Tablet is old but have not bad spec .. Please help me if posible

Regards and Thx for all reply !
[General Questions and Answers] JoaWah:
Hi i'I'm looking also for an update of this old Android 5.1 to newer. Any possibility for a new version?
[General Questions and Answers] cmarmolejos236:
Same thing here. I have had mine for almost a year now, and no success with it.
[General Questions and Answers] Ottes:
You say Acer_AV0L0_B3-A20_RV03RC02_WW_GEN1-MT8163

but my Tablet has RV08 instead of RV08RC03, so at least newer builds should be available

Would love CWM :P
[General Questions and Answers] Tamjeffrey:
There are no new stock updates, you have to root and flash custom ROM by yourself.
[General Questions and Answers] jpg-93:
Hi Have somebody root such tablet B3A20 and with what tool ? (i tried a lot without anh succes kingroot, kingroot and others...) Manu thanks
[General Questions and Answers] ForestCat:
Has anyone had any success rooting this device?
[Touch Diamond, MDA Compact IV General] rlintacoma:
It would be great if my contact photos looked as nice as the demo of Grace Fuller and her friends, but mine seem rather grainy. Anyone have an idea what reso those Diamond sample contact photos were taken at?
[Touch Diamond, MDA Compact IV General] nickytheshaft:
I posted the same probleme and got answers.

You have to go to the album, select a picture and add it to your contat threw the album menu and tada, photo contacts look sharp.

Thank again to the people who gave me the answer
[Touch Diamond, MDA Compact IV General] corleno:
thanks !! that resolved my issue too !!!

and the perfect resolution is 256*256 at 12 kb
[General Questions and Answers] xinen12:
Hello, I have a j5 prime SM-570M with android version 8 I would like to go back to version 7. What tools do I use to make this change?
[General Questions and Answers] pol1345:
no 1 answering..?????
[Sprint LG G3] Onyxsolo:
Hello,

I have three LG G3 LS990s; two of which run LineageOS 16.0 fine. My 3rd G3 was actually the first I installed Lineage(14.1) on. This was working fine until I updated to 15.0. After that point I was no longer able to boot into Lineage ROMs. I'm able to install, boot and root stock ROMs; but lineage stays on the boot animation even if I leave it running all night. I recently restored stock LS990zv4 and redid the process of rooting and installing TWRP(3.3.1.0) . However lineage is still hanging at the boot screen.

I saved the logs from TWRP but I'm not sure if they show the lineage OS boot process. Any help at figuring out why this one phone is misbehaving would be appreciated. One thing that stood out in dmesg.log is below. It still mentions lineage 14.1 even after I restored stock before formatting,clearing Dalvic/Cache and installing Lineage 16.0.

"<4>[ 0.021435] WARNING: at ../../../../../../lineageos-cm-14.1/kernel/lge/g3/fs/proc/generic.c:323 __xlate_proc_name+0xb0/0xc4()"

I'm not familiar enough with linux/android partitions to understand how the boot process flows. I've also tried installing the boot partition from one of my G3s which boot lineage.
[Samsung Galaxy S9+ Questions & Answers] StonebridgeGr:
Yo, i have 2 sim on s9 plus g965f, the number 1 is getting only 4g, and the internet is very slow, the other one is different network getting 4g+, 80 mbps

I have tried

Having only one sim, the 4g one didnt help

Getting new sims didnt help

Restart phone doesnt help

Remove sim put back again , didnt help

Tried airplane mode didnt help

The ISP said must be phones problem wtf?
[Nubia Red Magic 3 Questions & Answers] DaemonKisure:
Plis if somebody knows or somebody can create a custom room for improve the red magic 3 with Android 10 like havos is, lineageos or evolution x something like that
[Nubia Red Magic 3 Questions & Answers] Irwan Fauzi:
You can try treble gsi image.. make sure it's an ab image..
[Moto Z3 Play Accessories] Elpidio:
has anyone figured out if there's a way to make this phone less slippery? I tried a bumper case, threw that away since it bulges in front of screen next to fingerprint sensor, I bought the battery back, it's a little more grippy but I'd like to use it without the battery back
[Moto Z3 Play Accessories] jasons1004:
Get a skin... It is pretty slippery lol

I use battery mod normally

:cool:
[Moto Z3 Play Accessories] Elpidio:
I went to Verizon and I tried the case made for the Z3, it fitted perfect and now looking to cut at the lines, I may be able to use the 3490 mAh battery mod
[Tilt, TyTN II, MDA Vario III General] khals:
Hi folks

Previous to upgrading to HTC's official WM6.1 upgrade I was just happy with everything on my HTC Kaiser. Extept for the fact that I have no T9 dictionary working since trying to solve my FN Space issue (Please see

SOLVED!!! - HTC WM6.1 ROM : Missing "Fn Space" function?). At first I could live without T9 as I always use the FN Space function to type non english characters (I'm a foreigner afterall), but recently, I'd rather go back to WM6.0 where everything was working 100%.

Does anyone know a solution for this?

Thanks in advance :)
[Tilt, TyTN II, MDA Vario III General] khals:
Word completion

Stupid me :o

All I had to do was go into Start>Settings>Input and check "Suggest words when entering text" under "Word Completion" :D
[Xiaomi Mi Mix 3 Questions & Answers] Overloke:
G'day,

I've had some odd issues with two consecutive Xiaomi phones, and I'm hoping someone here can shed some light on it for me.

With both my Mi Note 2, and now my current Mi Mix 3, after less than a year of owning each one (respectively), out of nowhere, the battery life drops through the floor, the phone gets really hot, and most oddly, I got wicked battery drop while the phone is off (e.g. I turned the phone completely off at 77%, and about an hour later, I turn the phone back on and it's at 43%).

On both phones, I've tried a factory reset, but it didn't work. It was, for all intents and purposes, fecked. At the moment, I'm waiting for the 15 day countdown for my Mi Mix 3 bootloader to be unlocked so I can try flashing the EU MiUI ROM and see if that helps, but that's still a hell of a long time to wait with a phone that idles at 50+° C and has a battery life of about 3 hours with minimal SoT.

I've installed BetterBatteryStats (using ADB to provide permissions), CPU-Z, CPU Monitor and Ampere to see if I could get some more information. I found a few things:

1. Somehow, with mobile data and WiFi enabled, the system was drawing SO MUCH power (reported by Ampere) that it literally wouldn't charge while plugged into a 2A wall port. It was drawing like 1300mA when it wasn't plugged in, and when it was, it was STILL drawing about 130mA, meaning no matter what, while the phone was on, I was losing battery.

2. BBS reported the biggest battery killer was under the 'Alarms' tab, caused by Android, which were "Intent: *job.delay*" and "Intent: *job.deadline*". I have literally no idea what these are, what's causing them, or how to stop it triggering.

3. I've done a full factory reset. The first hint that something was wrong was when I noticed that the phone wasn't charging when it was plugged in and turned on. I did the full factory reset, didn't help.

I'm currently running Global MiUI 11.0.4.0, Android 9.

Does anyone have any ideas? I haven't manually updated anything, I'm not particularly rough with the phone, but for two phones in a row, this has come straight out of nowhere. It's a shame, because the Mi Mix 3 has spoiled me with it's 100% screen real estate (no hole-punch, no teardrop for front camera), but I think my next phone is gonna go with something else.

Cheers.
[Xiaomi Mi Mix 3 Questions & Answers] Overloke:
Update: I've taken a squizz at the Google Battery Historian and basically, I have no feckin' idea.

The best I can get out of it is "Yep, something in the labyrinthine generic 'Android' system is causing it, but good luck narrowing it down or stopping it."

That being said, I've found that this Partial Wakelock is triggered fairly often (1-6 times per minute, give or take): IntentOp:.common.broadcast.BackgroundBroadcastReceiverSupport$GmsReceiverIntentOperation

I have no idea what the hell it is or does, and the only information I can find about it is from developers asking questions where it just happens to be part of their codebase, or a breakdown of how the WakeBlock app works.

It's getting woken up about every minute or so (usually more than once a minute). However, the wakelocks appear to be part of the core Google/Android systems that can't be individually disabled.

I'm still feckin' confused.
[Xiaomi Mi Mix 3 Questions & Answers] XDRdaniel:
I think it's an issue with your network operator
[Xiaomi Mi Mix 3 Questions & Answers] Overloke:
Any ideas as to how I'd further troubleshoot? I've gone into *#*#4636#*#* and changed the sort of signal it looks for, but it doesn't appear to have fixed anything.
[Xiaomi Mi Mix 3 Questions & Answers] Overloke:
In case anyone is interested, I've attached on of my Bugreports (from running adb bugreport), which can be viewed through Google Battery Historian.

I'm not saying there's a cash prize for anyone who can tell me what is happening and why, but I'm also not saying that there isn't.
[Xiaomi Mi Mix 3 Questions & Answers] Overloke:
So, I think we have our culprit (maybe).

I have attached several screenshots from a Battery Historian I took after having my phone on all day. The total phone on time was about 4-5 hours with, no joke, maybe 10 seconds of screen on time. Let's go through this absolute bullshittery together, shall we?

Battery - Full Time:

The full length of time captured by the Battery Historian/bugreport command. It's in Zulu Time (GMT+0) and I'm in Australia (GMT+10), so the line starts going up at 5PM last night, which is more or less when I plugged it in to charge. You can see, while 'off', it took 16 hours to charge to 100%, and this was from a 'cold boot' (phone is completely dead), so it didn't have any information about what had been running, etc.

Battery - Discharge:

The five or so hours time in which the entire battery discharged, starting from when I woke up in the morning and got ready for work. In the Screen row, you can see the small, three-to-four second windows throughout the day that I turned the phone on to check the battery. For almost the entirety of the time, the screen was off. You can see where the line next to Phone State goes from black to navy blue. This indicates that the phone has been put into Airplane Mode - you can see this is also where everything relating to network connectivity or mobile strength completely disappears. You can also see that App Processor Wakeup completely dies here - that means that actual installed apps (including GOOGLE_SERVICES and Xiaomi's preinstalled Facebook app stop sending commands to wake the CPU.

Battery - Cause:

At least once a minute, usually more, two things fire that keep the CPU running - Abort:Wakeup IRQ detected during suspend: 999 msoc-delta and Abort:Wakeup IRQ detected during suspend: 663 qpnp_rtc_alarm. I have no feckin' idea what either of those are, and Googling results in either developer guides or threads that lead nowhere. If anyone knows what they are, for the love of God let me know.

Battery - Foreground Processes:

While the phone was off, with every app closed, in Airplane Mode, we can see that there are still four apps that are somehow in the foreground: com.miui.mishare.connectivity (odd, since there's no connection), com.miui.securitycenter (which I tried disabling through ADB last night, and it stopped my phone from booting. Oops), com.miui.notification, and com.android.providers.contacts (which disappeared shortly after entering Airplane Mode).

Battery - Video:

You can see here, for the ENTIRETY of the time that the phone was turned on, this odd Video row was enabled. There is no other information about it - what causes it, where it's coming from, what 'Video' means, anything.

Battery - 7 Second Slice:

This is just a close-up of a seven-second period of time, wherein the above 999 msoc-delta and 663 qpnp_rtc_alarm kept the CPU running six times within 7 seconds. Not a lot on its own, perhaps, but over the course of hours, it clearly causes issues.

I've also attached the latest bugreport where I took these screenshots from if anyone wants to try and make sense of it.
[Xiaomi Mi Mix 3 Questions & Answers] CriGiu:
This looks to me like an hardware issue more than anything, what is the idle state of the cpu?
[Xiaomi Mi Mix 3 Questions & Answers] gorrinho.jr:
Same problem. Any solution?
[Samsung Galaxy Note 8 Questions and Answers] Tmansdc:
I coasted by for months not upgrading my note 8 because I heard bad things about pie on note 8. Well this morning I accidentally hit install now instead of backing out of it. Can I downgrade back to the final last version of oreo stock firmware? Here's my software info.

Can I and if so how to downgrade to tmobile note 8 oreo? https://imgur.com/gallery/puzXavA

Thank you very much.
[Samsung Galaxy Note 8 Questions and Answers] Anonymously_Unknown:
I don't have the "how to" answer for you. However, since you aren't on AT&T's locked bootloader, you can downgrade to any stock ROM you like. In either case, backing up your data, is a must.
[Samsung Galaxy Note 8 Questions and Answers] Tmansdc:
What is wrong with my phone/odin? What am I doing wrong?

https://imgur.com/a/Krs3cgS
[Samsung Galaxy Note 8 Questions and Answers] MrMike2182:
You can only downgrade if you use the same bootloader version you're on bootloader version 5 so you cannot try to flash any bootloader version below 5 it must be 5 or above! [MENTION=4485889]Anonymously_Unknown[/MENTION] is incorrect when he stated your bootloader isn't locked because your bootloader is locked unless you have the F version which you don't have. You have the American version not the international F version. Also you need to use the newest version of Odin available.
[Samsung Galaxy Note 8 Questions and Answers] Anonymously_Unknown:
Thanks for the clarification