yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 9] JustAStrangeName:
That won't work and don't try it. It will allow you to flash almost everything despite having a locked bootloader, but that means it will just see the OS as corrupted and won't boot. At that point you may be able to recover it with an up to date OTA image or EDL mode, I'm not sure, I haven't tried. So don't try that.
[Asus Zenfone 9] JustAStrangeName:
This might work, but not with an unmodified file. As a security measure the OTA updates contain the hashes of other files, including the file that contains the version number. I'm guessing that we would need to somehow reverse engineer that hashing algorithm to make a downgrade work. As far as I could tell it wasn't just a common hash like MD5 or any SHA. I'm guessing it's a base64 hash and that the equals sign at the end is just filler.
[Asus Zenfone 9] aesara:
They've supposedly made it work on ZenFone 8 using this ROM. I'd like to download it and see what's up, but I'm on a metered connection.
[Asus Zenfone 9] Firngrod:
Likely, it's digitally signed, in which case we won't get anywhere without the private key used, or some way of bypassing the check, unfortunately.

I thought that maybe it would be enough that the images were properly signed using Asus' keys, and that the bootloader would allow it to run. Well, good thing I didn't get around to trying it. Edited a warning into my post so other people don't try it without proper warning.

Can Fastboot be used to make copies of the partitions? Reverse flash, so to speak?
[Asus Zenfone 9] Firngrod:
Well, the payload.bin hash from payload_properties.txt in that Zenfone 8 ROM lined by @aesara is a base64-encoded sha256.

The same is true for the official .142 firmware for Zenfone 9.

I have yet to figure out what METADATA_HASH and METADATA_SIZE refers to.
[Asus Zenfone 9] Firngrod:
It appears that the METADATA_HASH refers to a part of the payload.bin file that doesn't get extracted with the tools I have yet tried. One tool refers to a file manifest of similar size, but doesn't give me any more. Regardless, I doubt that any tomfoolery is necessary in that direction, really. I think all we need is in the metadata and payload_properties.txt files.

One difference I have spotted between the Zenfone 8 ROM they used to successfully downgrade and the Zenfone 9 official .142 is that the Zenfone 8 one is set to wipe all data on the phone in the progress, both in payload_properties.txt AND in the metadata file. This may be why the Zenfone 8 one worked. I don't have the official version of the Zenfone 8 one to compare to. I will try to find it.

I have found a mirror for what I think is an official Android 12 ROM file for Zenfone 9: https://androidfilehost.com/?fid=14871746926876820869

I an snooping around inside that one now. It does not appear to be set to wipe the data on the phone.
[General Questions and Answers] Toasty1Too:
Growing up with DOS, and later Windows, I've always had local administrator on my PC. I've dabbled in Linux on desktop as well, and it's usually a foregone conclusion that the device owner will have top level authority over the OS and hardware.

While I can agree that security is important, and I want this feature to be secured behind a password and encryption, it confounds me that:

1) Android bootloaders are locked by default, even when I buy my device directly from a manufacturer, with no carrier involved. There doesn't even appear to be consensus within the industry that any given device should have an accessible bootloader.

2) Unlocking the bootloader *always* wipes the device, with no option to disable this feature for those who dislike it.

3) There is no way to lock the bootloader without similar problems as in #2, and there doesn't appear to be any setting within the hardware to allow this.

4) Updating the OS often results in a full data wipe.

5) Android has insufficient tools built in to allow full user data backup + restore. This is especially true of anything with Google services on it, but even many apps available on third party stores simply don't have provisions in place for a user to restore data on a new device. In many cases, this means the data is inextricably locked to the device it originated on, and no sanctioned method exists to transfer it.

Apple devices may be slightly better on the backup/restore side of things, but many applications still have no provision for user data to transfer to a new device, and Apple is arguably far more hostile on the matter of bootloader unlocking.

I'm aware many of these features exist to protect user data as a paramount consideration, but shouldn't the user have the final say in the way the data on their device is handled, and what gets wiped when?

The question is mostly rhetorical. I'm aware the question is far more complicated than that due mostly to politics.

What are your thoughts?
[General Questions and Answers] V0latyle:
The purpose of the bootloader lock is twofold:

1. Verify the images on the device are signed and untampered

2. Prevent flashing of the partitions

Android by default is designed to support bootloader unlocking to allow flashing and booting of modified/unsigned images, but you are correct that it seems like each OEM has their own ideas

This is a security feature to prevent unauthorized access to protected user data.

K...But why is this a concern? Most people who unlock their bootloader keep it unlocked. It's not designed to be repeatedly unlocked and locked again.

Not true. Regardless of seamless or out of band updates, the update process is designed to preserve user data. I don't know about other OEMs but this is true on Google and Samsung. OTA updates never wipe data, and full factory flashes can still be performed without wiping data.

There is a reason for this. Scoped storage means any app can only access its own data. Backing up and restoring app data by means of a third party app like Swift Backup or Titanium Backup requires root.

I could be mistaken but I believe Pixel devices will transfer user and app data to a new device via a USB cable

There's nothing arguable about it.

Android is designed from the ground up to be open source, free to use, and preserve the end user's freedom.

Apple only allows running iOS on their devices and downloading apps from the Apple Store. They intentionally cripple obsolete devices to try to force users to upgrade, and they have brought legal action against those attempting to jailbreak their iPhones.

You're quite welcome to develop your own hardware and your own implementation of Android. But, we are talking about mass produced consumer electronics that necessarily are designed to protect user data due to the potential liabilities, and are also designed to minimize the potential for unauthorized software that could render them inoperable.
[General Questions and Answers] Toasty1Too:
Much in the same way that I wouldn't leave my BIOS or UEFI interfaces unsecured on a PC, leaving my bootloader unlocked means leaving that avenue available to an attacker should my device ever be stolen. There's even a message at boot to alert anyone who cares that the device is easier to compromise. As stated before, locking the bootloader is likely to cause a user data wipe. There really should be a way to lock it after the use case is no longer needed, to resecure the device.

Correct, but most manufacturers disable OTA updates when the bootloader is unlocked, so this is a moot point.

I've yet to see a use case on one of my rooted Android devices with an unlocked bootloader, that allowed me to update the OS without risking a wipe of user data. Maybe I just have a lot to learn, but frankly, there should be no such risk.

Most current gen Android devices are capable of this, yes. But at the application level, the developer can decide they don't want user data to be able to be restored on the new device, and it simply won't be(there are many ways to implement this). I don't feel that should be decided by the application. I see no functional difference in leaving the data intact on an older device, and transferring it to a new device with a comparable OS feature set.
[General Questions and Answers] V0latyle:
I'm not sure I get what you mean. Re-locking the bootloader is always possible. Of course, you'd want to make sure that you have a valid root of trust installed that was used to sign the firmware.. This can be OEM, or it can be custom (self signed) - examples would be CalyxOS, GrapheneOS, or avbroot

Locking bootloader commands a data wipe, there's no "likely to cause", it's a requirement.

Not necessarily

Any specifics? Because as a general rule, there is little to no risk.

Sure, if you flash a Pixel factory image using the included script, it will wipe data - so don't use the script and just flash manually using ADB/fastboot commands, or use an automated process like the excellent PixelFlasher

Even the Android Flash Tool has selectable options when flashing or updating a device. Data wipe and lock bootloader are selected by default but you can easily deselect them:

View attachment 6054827

Flashing factory firmware on Samsung devices with Odin also doesn't wipe data by default; you simply have to choose which CSC file you flash. HOME_CSC is meant for updates and do not wipe data. CSC (no HOME) is for a factory reset.

In both cases, updating via OTA, whether automatic or via ADB sideload, does not wipe data.

It's not decided by the application. As I explained, it's due to scoped storage - by design, each app running on an Android system only has access to its own private data. So, for example, your Facebook app can't read your Venmo app's data. Even system apps cannot read private app data.

View attachment 6054830

Anything stored on shared storage (internal/external SD card) can be accessed if that app is given permissions.

And of course with root permissions, a backup app can read, copy, modify, and write private app data, hence the ability to create and transfer backups.

You are correct, however, in that individual app developers have the prerogative to prevent transferred data from working with that app; I'm not completely sure of the reasoning behind this, other than the possibility that they don't want someone to be able to use that app with a compromised private data set.
[General Questions and Answers] Toasty1Too:
These would seem to be contradictory statements, but this only illustrates my point. While I understand the point of wiping user data when *unlocking* the bootloader, I see no benefit to the requirement to do so when *locking* the bootloader. I should be able to secure my device without worrying about losing data.

This has been true on my ASUS Zenfone 6 and Motorola Moto G100, both of which also block OTA updates when the device's bootloader is unlocked. It's possible I'm just approaching the problem incorrectly though.
[General Questions and Answers] V0latyle:
How so? There's nothing contradicted, if a bootloader can be unlocked, it can also be relocked, and in both circumstances will wipe data

Yeah, I think I can generally agree - unlocking the bootloader necessarily involves a data wipe, so it doesn't make a whole lot of sense to require another data wipe when relocking

Well, this is the problem with Android OEMs all doing their own thing. I'm not too familiar with Motorola, but I know several Chinese/Taiwanese OEMs including ASUS, OnePlus, Xiaomi etc have been in hot water with Google for improper implementation of things like broken hardware keystores, compromised keys, etc. Google has actually revoked the OEM keys for many of these devices so they're no longer trusted as far as Google Mobile Services is concerned.

Most of the Chinese OEMs use third party methods for bootloader unlocking which is not at all within the Android model. ASUS, LG, and Huawei have removed their bootloader unlock tools, while companies like OPPO removed the fastboot binaries entirely. Xiaomi requires registration on their website (breach of user privacy IMO), a 1 month wait, and only allows one unlock per month.

I know this has nothing to do with OTA updates, but I think it just serves as an example of OEMs refusing to follow the prescribed Android model. If they did, I doubt you'd have any issue getting updates. Pixel phones are essentially the Android prototypes, and OTAs have never been disabled for unlocked devices, although in some circumstances the process malfunctions due to modified images.

By the by: In case this isn't clear, I'm not trying to argue over things. I'm just providing answers to what I think may be misconceptions. You aren't the first person to ask questions like these and you certainly won't be the last!
[General Questions and Answers] Toasty1Too:
The initial statement that precipitated this line of thought implies it's not possible without wiping user data. So it's contradictory to simply state that locking the bootloader is possible; this is true from a technical standpoint, but ignores the problem: it does wipe user data, and leaving it unlocked leaves the device vulnerable.

I understand you're not trying to be contradictory. I appreciate your input. I'm always trying to learn new things about Android, I just wasn't trying to go down this line of conversation when I posted the thread. Still, it's important to get things right if I'm going to be critical of a product.

I vote with my wallet, and Google's current offering of mobile devices, without exception, do not possess SD card slots. So while I can appreciate that they're trying to make a great OS, their hardware is found lacking and thus functionally useless to me. Adding to that is their(different segments of Google, not necessarily the Android team) track record of exceedingly poor user support, even at the level of their biggest supporters(not me), which means I trust them very, very little. I use their services, but to rely on them would seem foolish. I'm actively trying to find ways to reduce my reliance on Google. It's difficult when the best options available are companies that care more about their shareholders than their customers/users.
[Introductions] jakigaga:
Hello guys my name is jakigaga, greetings from Nigeria.
[Google Pixel 8] tosho1:
I just "upgraded" my OnePlus 8 with LineageOs to a Pixel 8, and I'm sorry to say, that I'm somewhat disappointed.

Not only that I got a slightly slower phone für 2.5 times the price of my used OP8, but so many functions and settings are missing.

One of the things I sorely miss is the fine adjustment of the screen color. In comparison to my OP8 (and also to a sheet of white paper) the screen is warmer but sometimes looks yellowish or greenish. In other words: Blue is missing, and as a result the colors are somewhat muted and not so radiant. (depends on the content and brightness)

I am aware that it's a question of taste, but I don't like even slightly tinted car windows. It always looks a bit like rainy weather to me.

For me it's a real pitty. The camera takes photos that are incredible for a cell phone, even better than my Canon G15, but the screen spoils them. Blue in particular loses its brilliance. On my PC they look really great.

Most smartphones have a tool to adjust the colors of the screen, but not the Pixel8.

Is there any way/tool to adjust the colors? I have Magisk and Pixel Xpert installed. Maybe there is a module to adjust the color?
[Google Pixel 8] blackhawk:
Developer options maybe. If the factory color calibration/rendering or WB is off there's no accurate way to calibrate it even if you can adjust it. It will really screw up the gamma accuracy too. I would find this extremely annoying. Compare with another one to see if yours is defective. It's a possibility.

With variable refresh rate displays it's are also harder to get the color calibration accurate; too many variables. One reason I still use the fixed rate N10+'s and didn't go with a N20U.
[Google Pixel 8] tosho1:
I don't think that the phone it's defect. The tint is really small, it's just that I am picky :-) When I compare my display with a Pixel 7 and a Pixel 8 pro they look pretty much the same.

I know about the color shift problem with the 60/120 Hz switch and turned it off also on my OnePlus.

It's a shame that Google doesn't implement a tool to correct the white balance and maybe gamma by small amounts. Xiaomi has a perfect tool for that, btw. It confirms my impression that Google don't pay much attention to customer wishes and impose what they think is right.
[Google Pixel 8] blackhawk:
It's simply impossible to accurately color calibrate by eye. Gamma calibration is highly dependent on accurate color calibration.

If I take a shot of a color calibration chart in the shade then compare the actual chart to that image the colors should be same if the calibration is good.

My impression is that all variable refresh rate displays have color calibration issues. This isn't changing anytime soon. A 90hz fixed rate with excellent color rendering be a good compromise.

Unfortunately Android is gimmick/fear driven and the bs hype is just getting worse by the year now. 2024 looks like another lackluster year for Google Android. I don't expect anything worthwhile out of Samsung either. blah.
[Google Pixel 8] 0oWow:
I use Color Changer Pro and it works great, but you'll need root.

Here is a link to the free version.

Color Changer Lite [root] - Apps on Google Play

Completely change screen colors (red on black night vision mode, no blue, etc)

play.google.com
[Google Pixel 8] tosho1:
I tried it before but did not fount a setting for the white balance. I don't want a green, amber or b/w display. Have I missed something here?
[Google Pixel 8] Geofrey Kazaula:
Hello,

I have the same issue on the Pixel 8 pro, the display is on the yellowish side (warm color temperature).

Spent 1000USD purchase this phone online, not happy with the display.

Will be great if we can get a solution to this, Is there a way we can address it to google?

If some developer can make a rom by putting a while balance slider will be much appreciated.

Regards,
[Google Pixel 8] 0oWow:
Use one of the "Custom" buttons and change the RGB levels individually. For example, I hate the green tint, so my setting is "Red-252, Green-215, Blue-255". That changes the white balance of the whole screen.
[Google Pixel 8] tosho1:
Yeha! That's it :-) I didn't understand (nor tried) the custom settings. Silly me :-)

I only made a small change; R/G/B 248/248/255.

It's a small step for mankind, but a giant leap fopr me.

Thanks for your help.
[Google Pixel 8] Geofrey Kazaula:
Hello,

Is root a must?

Kind regards,
[Google Pixel 8] 0oWow:
For this app, yes. Google doesn't let you modify the display colors without root privilege.
[Google Pixel 8] Geofrey Kazaula:
Ok, thanks a lot, I'll root and try it.
[Google Pixel 8] tosho1:
Root is a must anyway if you want to own the phone that you paid for instead of beeing owned by it.
[Google Pixel 8] tosho1:
You can suggest it, but they usually don't give a sh*t on user's whishes. THEY know what's good for you.

LineageOS (and others) will come sooner or later.
[Google Pixel 8] meili_33:
I just want to chime in and say that there is a Free and Open Source alternative to the app suggested above called OpenShift on Fdroid and I tested it out on Pixel 8 Pro and it works really well. No bloat or ads either its literally 3 sliders and a stop/kill button.
[Google Pixel 8] 0oWow:
Nice find! Beware that it was last updated 7 years ago and won't be automatically updated.
[Google Pixel 8] meili_33:
Yea, certainly. I looked over the source code and it is dead simple so it should be pretty resilient at least. Its really just a wrapper around a shell script that calls `service set SurfaceFlinger ...` so its basically a little hack but it actually works pretty dang well.
[Touch HD General] gadgetuk437:
I hate to admit it, prolly a terrible character flaw... but I can't learn to love Opera!

Anyone know which manilla file to edit to get IE launching from the TF3D Internet tab? (with PIE favourites/bookmarks too preferably)

I have already made PIE the default browser, but this doesn't affect the TF3D tab.

(I used Darkness's Fix IE.cab)
[Touch HD General] Elodie:
I had the same problem : I prefer NetFront than Opera and i used :

I use : http://xdaforums.com/showpost.php?p=2400995&postcount=1
[Touch HD General] walstuz:
Elodie--done that -- it worked for changing the browser in TF3D. Any body have a clue how to change the default on the hardware keyboard key to open PIE instead of Opera? It is the FN setting on the key that would normally open the symbol screen.
[Touch HD General] genesicgaogaiga:
I would also like to set IE as default.

WHere can I get this cab file??
[Touch HD General] gadgetuk437:
Look here,

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

AND

this fixes the TF3D tab (sorta),

http://xdaforums.com/showpost.php?p=2400995&postcount=1
[Android General] GooseyBoye:
Hello all,

The reason for thsi post is because one of my family's workers in our shop phone broke, and he was trying ot use the HotPepper Chilaca as a backup, but it has a FRP Lock on it.

He was locked out of it before and tried to factory reset as he forgot the original PIN, to our knowledge, theres no google account linked with th phone.

Ive googled a bit trying to find a solution but i am NOT tech savy enough to find something meaningful.

I would appreciate the help,

Thank you!
[Xiaomi Poco F1 Questions & Answers] sunnySingh1098:
Which is the best kernal for poco f1 with untutu score 4.7-5
[AT&T Samsung Galaxy S8 Questions & Answers] nlightning:
All USSD & MMI code combinations produce "Connection Error or invalid MMI code" even simple ones like *31# and ##004#. IMS is registered on my phone so that's not the issue. My modem is jammed up so badly whenever my SIM and number are in use on a phone. I think someone could have locked it out of my number. If that's the case what can I do on my phone to get MMI access back on the dial pad on my phone?
[AT&T Samsung Galaxy S8 Questions & Answers] blackheart6411:
U thought I wouldn't know
[AT&T Samsung Galaxy S8 Questions & Answers] blackheart6411:
View attachment 6054491
[Samsung Galaxy Note 8 Questions and Answers] Schwarzinger58:
So I messed up and two days ago accidentally deleted some important photos from both the SD Card and the Internal Storage of my old Note 8 N950F (Exynos).

This happened while transferring the folders to the PC so they didn't go in the Recycle Bin.

I actually managed to recover all files from the SD Card by using Disk Drill on PC but the software won't work on the Internal Storage.

The phone isn't rooted so I tried UltData and DroidKit to recover some files from the internal store - I managed to get back some of the Whatsapp photos but all the photos in the DCIM folder are still missing!

All attempts to root the device without wiping data failed. I almost bricked it after flashing the modified boot.img with Odin - it got stuck in an endless rebooting loop. Thankfully I found the stock boot.img and re-flashing it fixed the issue. I believe none of the exploits are still working since the phone is on the most recent security patch.

I'm out of ideas, so just a few questions:

- Any better software I could try on a non-rooted phone?

- Any method to root it without wiping that I have overlooked?

- What if I root it by wiping the data anyway and then use recovery software for a deeper scan on the wiped storage? It is probably foolish.

Anyway, I'm open to suggestions

Much appreciated
[General Questions and Answers] Peelp5090:
Can someone please guide me?
[General Questions and Answers] m4j0r4:
You can try project sandcastle. This lets you run android on iOS
[General Questions and Answers] Peelp5090:
Ok I’ll dig deeper into that
[General Questions and Answers] EllieCat:
It might be a little buggy and not all features are available as it is in beta.
[General Questions and Answers] Peelp5090:
I know most apps Off the Play Store don't work cause of the A10.
[General Questions and Answers] xXx yYy:
Full video guide here

Switch From iPhone to Android Seamlessly - Android

Discover how Android makes it easy to switch from your current iPhone and transfer all existing data to your new Android phone securely & seamlessly.

www.android.com