yashsingh1/xdaforums huggingface dataset:
[Android General] Bubba The Hack:
I posted this on the other thread, but it applies here too.

You may find my experience helpful, and I am glad to pass it on. I am using a Debian 11 (Bullseye) OS with Xfce 4.16 installed. My tablet is the early cheapo from q-link.

After trying with Linux and getting mislead into using windows, I had nothing but confusion and problems. As a last ditch effort, I went back to my Linux desktop and started fresh. Here are the simple steps.

First, open Synaptic Package Manager to install ADB, Fastboot and android-sdk-platform-tools. (Not sure I needed the last one.) USB device drivers appear to be already installed.

Pressed power button on tablet and entered regular system.

Followed steps to enter Developer mode.

Turn off lock and USB debugging.,

Shutdown tablet.

Held volume-down and power buttons until text came on screen and then release power button. Release volume-down button when green android appears.

Plug in cable from tablet to computer.

Open terminal window.

Type in:

fastboot devices

and press Enter.

See tablet's alphnumeric text string listed there.

Type in:

fastboot oem unlock

and press Enter.

See that it states that it is unlocked.

Download the patched_boot.img file.

Go back to terminal window and change directory to location of the img file.

Type in:

fastboot flash boot ./patched_boot.img

and press Enter.

You might get back something like::

Invalid sparse file format at header magic

Sending sparse 'boot' 1/2 (32764 KB) OKAY [ 1.317s]

Writing 'boot' OKAY [ 2.596s]

Sending sparse 'boot' 2/2 (1408 KB) OKAY [ 0.083s]

Writing 'boot' OKAY [ 1.871s]

Finished. Total time: 5.964s

Type in:

fastboot reboot

and get back:

Rebooting OKAY [ 0.008s]

Finished. Total time: 1.761s

Let everything sit for a while and then hear tones from the tablet.

Type in:

fastboot devices

and get back nothing. (Evidently the tablet rebooted and came back on in different mode.)

When I pressed the power button once, the screen lit up and showed the desktop screen. It was ready for use.

I liked how easy that was to accomplish the task on my regular desktop. (I strongly recommend every windows user to set up a dual-boot and include some Linux distro on their systems. After using it for a time, you'll never go back. ;))
[Android General] Viva La Android R.I.P.:
So which patched boot image did you flash? Im guessing you flashed the Android 11 Go Edition boot image. This is why you are stuck on the logo. No worries, you cant hard brick an Allwinner tablet. You need to flash a patched boot image that corresponds with the firmware installed on your variant. Did you read this statement in the beginning of the thread?

IMPORTANT NOTE:

This guide is strictly for the QLink Scepter 8 models that shipped with Android 11 Go Edition. I recently learned that a new model of the Scepter 8 has been released, powered by an upgraded Allwinner-A133 chipset platform, 2 GB RAM, and runs on Android 12 Go Edition. I have already contacted the manufacturer and requested the latest factory firmware image. I will update this thread accordingly when I receive news.

In theory, because of the modern Android Common Kernel implementation, the Android 12 Go Edition model of the Scepter 8 should be fully compatible with this guide in terms of unlocking the bootloader and achieving root access. However, I have not yet confirmed this theory. As such, there is potential for bricking or damaging your device. In the event this guide is used in conjunction with the upgraded QLink Scepter 8, you have been warned of the risks involved.
[Android General] Viva La Android R.I.P.:
@ScarletWizard, now that I'm finished giving you the speech on reading over everything carefully, I can help you get your tablet up and running with root. So, you patched the boot image from the Android 12 firmware? You are probably going to need to disable verity by flashing /vbmeta via fastboot.
[Android General] Viva La Android R.I.P.:
Yes, the header magic notification is normal. Pull vbmeta.img from the Android 12 GE firmware and save it in your fastboot directory. Boot your tablet into fastboot mode again, connect to your PC and execute:

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

This should allow you to boot up with root access. John Wu overhauled the codebase on the v25.x Magisk builds. Patching your boot image no longer disables verity by default. You now have to do it manually. I apologize for giving you a hard time. I can tell you have been thorough. And yes, you have the latest Allwinner-A133 upgraded Scepter 8. More RAM, better performance.

I will be updating the thread to include patched boot images for both Android 11 & 12 GE variants, with dm-verity already disabled.
[Android General] Viva La Android R.I.P.:
Cool. You remind me a lot of me. I love finding damaged treasures and bringing them back to life. Nice find 👍
[Android General] Viva La Android R.I.P.:
I like you already. Welcome aboard. Good to have you. So you're setting it up to boot the OS from the external? Are you using live boot?
[Android General] Viva La Android R.I.P.:
Yes, I recall seeing a guide on creating Windows 11 Go boot media. Nice. That will undoubtedly make you a nice laptop.
[Android General] Viva La Android R.I.P.:
Hey @ScarletWizard one more thing: as you likely recall, whenever disabling verity, you must format /userdata in order to fully decrypt the device. After running the fastboot command i outlined, you may need to boot into stock recovery and initiate a factory data reset before booting into the OS. As we speak i am working on a patched boot image with dm-verity set to opt-encrypt via edits to the fstab. I should have it posted shortly if you want to save some time.
[Android General] Viva La Android R.I.P.:
As luck would have it, my own PC has crashed. I installed the new AMD Adrenalin GPU drivers and one of my settings didn't go well apparently. Oh well, I will boot into safe mode and hopefully resolve it.

I do have a simpler solution for you. Patch the same boot image again using Magisk v24.3 or earlier. The earlier versions disable verity during the patching.process. After you boot up, you can update Magisk by direct install from the app and you wont lose opt-encrypt.
[Android General] Bubba The Hack:
@ScarletWizard , it does sound like you might have the latest version, especially if you just got it. Could you please tell me from where you got your screenshot?

Also, I strongly recommend the Linux method. You might wish to see my notes on that. comment #153

Thanks.
[Android General] Viva La Android R.I.P.:
Yeah @ScarletWizard I can vouch for the efficiency of @Bubba The Hack's Linux method. Also, since Bubba also has the latest model tablet, following his Linux method is highly suggested if you have the setup to do so.
[Android General] Bubba The Hack:
Well, actually, I cannot say I have the latest version. Mine is the FCC ID #2APD4-AP10, and Build number is Scepter_8_Tablet_V2.0_20210423, with Android Version 11.
[Android General] Bubba The Hack:
ARM Cortex-A53 1.46GHz 4-core

1GB RAM

16GB internal storage

board is exdroid

hardware is sun50iw10p1

Only one checker program found anything even remotely related to All Winner and that was the RIL version named softwinner...
[Android General] Viva La Android R.I.P.:
Yeah my bad Bubba. I.had you mixed up with the member who first informed me of the Android 12 GE variant. Yeah yours is the "AP10" model, which has the Allwinner-A100 platform. If you take the back cover off your tablet, you'll see

Allwinner-A100 emblazoned on the SoC. One of the codenames for the A100 is sun50iw10p1

I have the same model as yours. Your Linux method will work on the new model as well. The A100 and A133 are strikingly similar in terms of architecture and lithography.
[Android General] Bubba The Hack:
Thanks for the info. Your screen is different than mine. I do not have that display. Maybe that was a stock thing, but I never set up the stock because it required a google signup, so I can't be sure.
[Android General] Viva La Android R.I.P.:
@ScarletWizard here is a no verity boot image patched with Magiskv24.3, from the latest Android 12 GE firmware build.

File on MEGA

mega.nz
[Android General] Bubba The Hack:
Pardon me, but you've used that term a couple times. What does "no verity" mean?
[Android General] Viva La Android R.I.P.:
Starting back with Android 4.4.4 KitKat, the Android kernel has been implemented with a security protocol known as dm-verity (device mapper verity), which performs a block mapping integrity check during each boot sequence. You will often here this called verified boot or secure boot. This feature is premised upon establishing a chain of trust beginning with the bootloader, all the way up to the Android system image. More recent implementations of dm-verity include AVB (Android Verified Boot) 1.0 & 2 0. The root key used by dm-verity is stored in the boot image ramdisk. As a consequence of using dm-verity, the system image can no longer be mounted read-write, since doing so will write to the superblock, thus invalidating the block-level hashes maintained by dm-verity. Consequently, on the majority of Android devices that are rooted and modified, dm-verity is triggered and causes boot failure. The solution is to modify the boot image ramdisk and disable dm-verity/AVB. By "no-verity," I am referring to a boot image in which this security feature has been disabled.
[Android General] Bubba The Hack:
Thank you for that very good explanation. Even I could understand that.

Then this definitely has something to do with my boot-up message:

"Your device cannot be checked for corruption. Please lock the bootloader."

I have been just ignoring it.
[Android General] Viva La Android R.I.P.:
Yeah, other than being an eye-sore and a persistent nag, the "please lock the bootloader" prompt during boot up is harmless. I am going to modify the lk.img file to return the boot logo to normal and alleviate that persistent notification.
[Android General] Bubba The Hack:
Can you enlighten us about the .img files? I know I'd like to know more. Basically, all I know is that Android devices have a ROM which contains the custom OS.
[Android General] Viva La Android R.I.P.:
The .img firmware file in this instance is an archive encompassing individual partition firmware images (.fex files) and some config files containing data specific to the firmware build. If you want to extract the .img file to see its contents, I recommend using the ImgRepacker utility for Windows. Once extracted, the boot.img.will be a f8ile named boot.fex (you can simply rename.the.file, including extension,.to boot.img. The same goes for the.othet .fex files.

This is ImgRePacker. Download it, extract the contents of the archive to your desktop, and select Runner.bat within the directory. Right click to run the batch file with Administrator privileges. Drag and drop your .img.firmware file to the interface. Type smt and then Enter. ImgRePacker will unpack the .img firmware file and extract all its contents to a separate folder..

File on MEGA

mega.nz

So, the firmware .img contains all firmware for the device, including the boot image, Android OS, proprietary vendor firmware, recovery image, bootloader, crypto header, trust zone partitions, etc.
[Android General] Bubba The Hack:
That sounds like more than a custom ROM, or am I wrong?
[Android General] Viva La Android R.I.P.:
Well the ROM encompassed within these firmware packages isn't custom. It's the stock Android OS. But, in addition to the Android OS, there is also all firmware that is needed for full functionality and operability of the device.
[Android General] Bubba The Hack:
Well, I think I understand. Thank you very much for the explanation and clearing that up for me.

So I assume one could then just add a custom ROM to more easily get rid of google's tendrils?
[Android General] Viva La Android R.I.P.:
You can install a custom ROM without going through the procedure to flash am entire firmware package. Technically, only four partitions need to be flashed in order to install a custom. ROM: /boot, /system, /vendor and /product. But, since the QLink Scepter 8 uses a /super partition (the /super partition includes /system, /vendor and /product), only./boot and /super would need to be installed. Those can be flashed via fastboot or fastboot.d mode.

Your basic premise is correct. For example, i could extract the super.img from the firmware .img and manually remove all Google apps and services. I can then repack the super.img, archive it back in the firmware.img, and the installation would then install the.Android OS without any Google apps or proprietary services.
[Android General] Bubba The Hack:
Did you try the Linux method?
[Android General] Viva La Android R.I.P.:
I linked you a boot image that I patched to disable verity and for Magisk root support. Download that patched boot.image, save it on your PC in your ADB/Fastboot directory. Boot your device into fastboot mode & connect it to your PC or laptop. Open a command window in the path of your fastboot directory and execute these commands:

fastboot flash boot_a opt-encrypt-magisk_boot.img
fastboot flash boot_b opt-encrypt-magisk_boot.img
fastboot reboot

Or, alternatively, you can follow @Bubba The Hack's Linux method to achieve root.
[Android General] Viva La Android R.I.P.:
The legacy fastboot mode. Your screen will show an Android graphic in the middle of the display. From recovery mode, you can get there by choosing bootloader mode. If you see a display indicating FASTBOOTD, that's the wrong mode. Technically, either mode should work, but legacy is preferred.
[Samsung Galaxy S22] jarome1:
I have a T-Mobile S22 Ultra. In my house, the connection flips from 5G (low band) to 5gUC (mid band). When I am outside, it is more often 5gUC. When it works, I get about 600 Mbps down outside, and anywhere from 0-60 Mbps up. Things work well, listening to my home music server (Emby). But if I run a second internet program (e.g., Speedtest), the program usually works once, but then my internet connected programs all freeze. The 4-5 bars are still displayed, and I can make phone calls. After about 5 minutes, they come back again.

Switching to 4G did not help yesterday, even after a reboot.

I reset all my networking (WiFi, Bluetooth, Cell data), and swapped for a new SIM card (today). It is better today than yesterday, but still freezes. Emby just crashed actually, but the music came back when I restarted Emby.

I would appreciate any suggestions.
[Samsung Galaxy S22] Post Nine:
have you contacted T-Mobile?
[Samsung Galaxy S22] Tanle11:
Can you try "Samsung band selection" apps?
[Samsung Galaxy S22] jarome1:
It does not seem to support 5G low vs Mid band.

But, I think I fixed this. I needed a new SIM, and T-Mobile was fiddling with the towers. It seems fixed now.
[OnePlus 5T  Questions & Answers] derei:
EDIT: Solved.

I followed this tutorial: https://xdaforums.com/t/official-oxygenos-10-0-1-android-q-10-0-ota-for-oneplus-5t-dumpling.3709265/

I removed the compatibility.zip on my pc using 7zip and then loaded the file on the phone while it was on recovery mode (twrp). The installation went fine.

---

I was following this tutorial: https://forums.oneplus.com/threads/...bootloader-easiest-step-by-step-guide.733862/

But, when i go to flash the downloaded OTA Rom, TWRP throws a lot of red errors:

Zip Treble compatibility error!

Invalid zip file format!

Error installing zip file <pathname>

Now I got a phone with no ROM, only TWRP on it... and not sure how to progress from here.

I tried with two OOS versions:

OnePlus5TOxygen_43_OTA_048_all_1904191530_f1dedf62ffb14bff.zip

OnePlus5TOxygen_43_OTA_069_all_2010292144_76910d123e3940e5.zip <-- this seems to be the last one on OnePlus website.

Any suggestions to fix this?
[Fire TV General] EngineerMind:
I just disabled updates for my brand new 4k Max, so it's locked into version 7.2.5.5

Does anyone know where there might be a release notes document that shows the fixes from 7.2.5.5 to the current version of 7.2.7.3?
[Fire TV General] Sus_i:
Never ever saw release notes for fireTV updates :)
[Touch Diamond, MDA Compact IV General] gus77:
Hi guys,

I got a new Diamond to replace my old Trinity.

I backed up and restored everythiong using PIMBackup, but after restoring to Diamond everything is a mess. In the Inbox folder I have my received messages threaded, but all the outgoing messages are in the Sent items folder non threaded. Anyone got a solution for this problem?

I am using Swtos latest rom 1.6

Thanks in advance!

gus
[Touch Diamond, MDA Compact IV General] Techno-Freak:
PIMBackup does not restore Threaded SMS.

Better solution would have been something like Jeyo Mobile Companion.
[Touch Diamond, MDA Compact IV General] Pietje_1985:
Sorry Techno-Freak, but PIMBackup DOES WORK with restoring sms and ALSO Threaded sms...!! at least...it's working perfectly for mine....

2Gus77

about your problem....I never had any trouble caused by PIMBackup...what you can do....give it another try:

1. when you have the option to choose which account and folders to restore, I usually select only my inbox and untick the rest (you can have a look for yourself whatever you prefer)

2. At the restore options menu choose for this option: 'Delete all existing messages from the database'

Hope this works for you...please let me know:D;)

Greetzz Jeroen
[Touch Diamond, MDA Compact IV General] gus77:
Hi again guys,

Thank you very much for your replies.

I tried backing upo only the Inbox folder from the Trinity and restoring it to the Diamond using PIMBackup, but only the incoming messages were restored, so I couldn't test the threading.

I also used Mobile Companion to backup and restore all the messages but I still have the same problem. The threading works only for the incoming messages and the sent messages are stored in the sent items folder without threading. I tried it on different ROMS but the results were the same. :-(

Any other idea?

gus
[Touch Diamond, MDA Compact IV General] Davey101:
I think this is normal behaviour for the Diamond. Inbox is the only folder that displays threaded (including some sent messages) and all the other folders appear normal unthreaded.

Seems logical to me, you would only visit the other folders if you were looking for a specific individual item.
[Touch Diamond, MDA Compact IV General] Addicteddddd:
PIMBackup does NOT restore threaded sms, you have to set it up awkwardly prior to backing up to revert to threaded sms however and this is how you do it:

1. Turn off threaded sms

2. make the PIMBackup

3. on the new ROM, turn off threading

4. restore PIMBackup

5. enable threading again
[Touch Diamond, MDA Compact IV General] gus77:
Worked perfectly!!! Thank you very much! :D :D :D
[Touch Diamond, MDA Compact IV General] mugglesquop:
How do you disable/enable threaded SMS?

i have Panosha ROM, and it is not threaded, do i need a cab to make it threaded?

Cheers,
[Touch Diamond, MDA Compact IV General] gus77:
HKEY_CURRENT_USER\Software\Microsoft\Inbox\Setting s\OEM\SMSInboxThreadingDisabled

DWORD

value set to 1.

You have to create the OEM folder yourself but apart from that it seems to work okay.
[Touch Diamond, MDA Compact IV General] gus77:
Got it from another thread:
[Touch Diamond, MDA Compact IV General] ashmont:
You don't need to turn off threaded sms before backup

I did a backup of my SMS before reading this thread so hadn't turned off threaded sms before doing it. It doesn't seem to matter. All that matters is you disable threading before doing the restore and then turn it back on afterwards. Seems to be ok for me. Also I didn't have to do any soft resets or anything. I just had to kill tmail.exe before disabling and re-enabling.

Cheers,

Ashley
[Touch Diamond, MDA Compact IV General] fulgore:
That did it for me too, disable, restore, enable.

Even without killing tmail.exe

Under WM6.5

Thanx!
[Touch Diamond, MDA Compact IV General] bigasif:
Hey guys, I've got a problem.

So I made a PIMbackup of all my sms's. I then flashed my phone to another ROM and tried restoring the sms's. Didn't seem to work properly, so I then hard reset the phone and disabled SMS threading. I then restored the texts from the backup file, and then re-enabled threading.

Now, all the texts are there, however, they're pretty much sorted according to date.

For example, if I had a sms convo of about 5 msgs back and forth between a friend and I, it's sorted by that day where it has all of their messages first (incoming) and then my messages after (outgoing).

So they are threaded, but they're split into incoming then outgoing for each day per person.

Does anyone know how to fix this? It doesn't seem to be threading properly...does anyone have or had a similar problem? Thanks!
[Touch Diamond, MDA Compact IV General] fabius88:
i think you have to delete every sms...then (with new messages) you can see SMS threading as default..
[Google Pixel 6 Pro] Morgrain:
There has been some talk about Sammi versus Pixels on XDA. If you care for camera performance, this review might aid your decision.

Excerpt from the article:

Samsung Galaxy S22 Ultra

Pixel 6 Pro

Samsung Galaxy S22 Ultra — these photos show how far Samsung is behind Google

The Galaxy S22 Ultra is allergic to the sun

www.tomsguide.com
[Google Pixel 6 Pro] p51d007:
Shadow detail & color contrast much better on the P6P
[Google Pixel 6 Pro] 86rickard:
On first glance the P6P looks best, but after a while too processed and too heavy on the HDR. The natural photographic nature has been replaced with a video game like processing look more and more as time goes by on Pixel.

Looking back at my pixel 2 photos, they are more natural looking than the p6 ones now.

All you need to do is check out edited RAW files and what the p6 camera is capable of is drowned in a over processing.
[Google Pixel 6 Pro] TonikJDK:
My kid has both, he agrees that the Pixel camera is better.
[Google Pixel 6 Pro] darkriff:
Still people just care about a "good" looking photo. Problem with samsung is that it still take lots of blurry photos
[Google Pixel 6 Pro] hand-filer:
Depends on the review TBH. Both phones are in the top 3. The S22 Ultra is more expensive but has better specs, storage capacity and build quality. It's not made in China which is important to some of us.
[Google Pixel 6 Pro] arsenal74:
I have both and for most things the Pixel camera is just better.

Problem is for everything else on the phone the S22U is better.
[Google Pixel 6 Pro] hand-filer:
And now we have an honest unbiased response. (y)
[Google Pixel 6 Pro] hand-filer:
Both of these flagship phones are seriously flawed. Not a day goes by that I'm not sorry for selling my S20+ in anticipation of the Pro 6 that never came and the S22U that is 2 weeks delayed and counting. 🤦‍♂️
[Google Pixel 6 Pro] MrBelter:
The Samsung shot is way more natural but there is no way you can make a judgment on just one photo. For the majority of the time the Pixel doesn't turn in to an HDR mentalist like it has here and the results are very pleasing.
[Google Pixel 6 Pro] arsenal74:
Then thing is this type of photo is one where I would expect Samsung to be competitive with the Pixel and in this instance I think I do prefer the S22U image, the slightly blown sign and building in the distance do not ruin the photo for me.

It is photos of people and pets where I think the Pixel excels which is probabnly 90%+ of the photos I take on a phone. If I was heading out to take some cityscapes I would not worry which one I took with me TBH. I'd probably take the S22U though as the Pixel on cellular would likely have a dead battery by lunchtime :)
[Google Pixel 6 Pro] Alekos:
^^ 100%.

One photo? come on. Both phones are great. can we just be content that phones are this good.

And there's so much more to it, than just one photo captured in one moment of time. It''s not black and white. This is much more complex to just have a blatant statement like that and these types of features have to perform well for billions of people in billions of different environments. all flag ships from 2020-22 do very, very well.
[Google Pixel 6 Pro] Noexcusses:
Not anymore sir... After may update camera on pixel isn't so good on sharp