yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy S 5 General] A Cool User:
@jrkruse

Any chance this could be used for the AT&T variant (SM-G900A)?

Thanks!

EDIT1:

Using the method specified in the above post , it results in a file being the size of 26640. This does not fit on the boot partition (The boot partition has a size of 26624). Also trying to unpack the resulting image with unpackbootimg results in this:

Android Image Kitchen - UnpackImg Script
by osm0sis @ xda-developers

Supplied image: patched.img

Removing old work folders and files (as root)...
Setting up work folders...

Image type: AOSP

Splitting image to "split_img/"...
ANDROID! magic found at: 0
BOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3
BOARD_KERNEL_BASE 0x037f7fd0
BOARD_NAME SERPKLUV001
BOARD_PAGE_SIZE 2048
BOARD_HASH_TYPE sha1
BOARD_KERNEL_OFFSET 0x00008000
BOARD_RAMDISK_OFFSET 0xfe808030
BOARD_SECOND_OFFSET 0xfd708030
BOARD_TAGS_OFFSET 0x0a808030
BOARD_HEADER_VERSION 0
Unrecognized format.
Error!

Running the same program on one of your patched images works fine...

EDIT2:

I tried using the TWRP for EMMC11, and when trying to boot with recovery it just hangs. It did not fail with a unauthorized software error though.
[Verizon Galaxy S 5 General] A Cool User:
If the patched recovery is made with cat exploit.bin recovery.img > recovery_patched.img, there would be ANDROID! magic twice, as the TWRP image and exploit both have ANDROID! magic at the start of the file. However, the patched TWRP has it only once. How was that TWRP patched?

Thanks!

EDIT1:

Sorry, looked again and found the android magic twice..
[Verizon Galaxy S 5 General] jrkruse:
You have to be on certain versions of bootloaders they latest version doesn’t work
[Verizon Galaxy S 5 General] A Cool User:
I was testing this on OF1 G900AUCU4AOF1
[Verizon Galaxy S 5 General] jrkruse:
Is that marshmallow
[Verizon Galaxy S 5 General] jrkruse:
I assume so
[Verizon Galaxy S 5 General] A Cool User:
It is KitKat. 4.4.2.
[Verizon Galaxy S 5 General] jrkruse:
It only works on marshmallow bootloaders
[Verizon Galaxy S 5 General] A Cool User:
Thanks for the info! Will upgrade to marshmallow and report back.
[Verizon Galaxy S 5 General] jrkruse:
Do you have safestrap for that device
[Verizon Galaxy S 5 General] jrkruse:
Contact me on telegram
[Verizon Galaxy S 5 General] A Cool User:
Yes, https://xdaforums.com/t/recovery-locked-nd3-safestrap-recovery-v3-75-2014-06-26-b03.2794087/
[Verizon Galaxy S 5 General] jrkruse:
See the issue you’re going to have is you have to have the whole thing to be able to flash while your rooted because you can’t simply flash stock marshmallow and patch the boot img and twrp because you have no way to flash them
[Verizon Galaxy S 5 General] A Cool User:
I Think I need to create a zip flashable in Safestrap like your EMMC_11_Rom but base it on the AT&T Files for QC1 from here.
[Verizon Galaxy S 5 General] jrkruse:
See your phone jumped bootloader revision several times on marshmallow so there is a good chance that your bootloaders might be to updated on any bit 4 firmware for it to work
[Verizon Galaxy S 5 General] jrkruse:
You probably need to be on a version ending in DP** for it to work because after that time frame it was patched
[Verizon Galaxy S 5 General] A Cool User:
Found it! https://androidfilehost.com/?fid=312968873555011029
[Verizon Galaxy S 5 General] jrkruse:
If you contact me on telegram I can help you better
[Verizon Galaxy S 5 General] A Cool User:
I don't have telegram, sorry
[Verizon Galaxy S 5 General] jrkruse:
Well if you want or need anymore help you will get it because this isn’t an efficient way to communicate
[Verizon Galaxy S 5 General] jrkruse:
The ATT device will take all new stuff you cant use any files from the verizon emmc11 thread
[Verizon Galaxy S 5 General] jrkruse:
So it appears the S5 AT&T version was released with a to updated version of android 6 marshmallow for this exploit to work
[JAMin, XDA Neo, S200 General] vinod_machani:
Please help me about these white flickering lines from past 5-6 days it started tried restarting restoring even flashing to other rom nothing changed.. screen keeps flickering like the white lines increases and decreases some time on the white part (Lower bar) upper part ka statue bar shows little transparently :(:( is there anyone who can help me in this … I badly what to get it done ready :(:( please help
[JAMin, XDA Neo, S200 General] vinod_machani:
someone there to reply ??
[JAMin, XDA Neo, S200 General] lyndel4:
It could be the LCD try to get it exchanged and see if that helps its not a software issue becouse you already tryed reflashing it and still same problem well I don't know much you prophet is good the only problem you have is those white lines try to get it replaced I think it could just fix your issue :)
[JAMin, XDA Neo, S200 General] skydemon:
sorry, but what the shell do you use on device??? Please answer me, I'm very interesting in it, thx :)
[Google Pixel 7] mikerowes69:
So this for everyone whom has the Pixel 7 and purchased GOOGLE STORE preferred care through ASSURANT. There website will automatically deny your claim. I added a claim for the chipped glass in the rear lens, as this is a well known warranty issue reported. This was denied without the option for rebuttal or contact. I was pissed, but what I to do. Well you have options. I contacted my state attorney general's office and filed a claim. As well as the FTC. I provided a screenshot of being denied, as well as proof of purchase with the preferred care. They sent a letter and within a week I received an email from Google telling they would be glad to replace my device with a authorization charge. So once I receive my new device and send back the old one, the authentication will come off. Assurant is a very crooked company that will deny any and all warranty claims or accidental claims. Please consider purchasing a different insurance company before purchasing your device in the future. Don't ever give and always pursue your claims no matter what. Don't let these crooks get the best of us as we all paid damn good money.

As for the FTC, I have heard nothing but I will push this issue through with them as well. If this dont continue to get my authorization charge removed then I file again with the state attorney general's office and my state insurance commission. Never stop!
[Google Pixel 7] 96carboard:
Would you expect anything different? Insurance *is FRAUD*. Insurance companies make money by NOT paying out on claims.
[Google Pixel 7] O.J. Simpson:
In the long run, it's usually cheaper to do D.I.Y. repairs than pay for phone insurance.

But I'm glad you got things sorted out. Sorry you had to jump through hoops to do so but...insurance companies are gonna insurance company (deny, deny, deny).
[Google Pixel 7] ktdt00:
The EVIL TRIAD!!! Lawyers, politicians, insurance companies!!!
[Samsung Galaxy Tab S5e Questions & Answers] OregonDude2U:
Hello,

Recently purchased a non functional SM-T720 and discovered it is stuck in the Qualcomm Emergency Download (EDL) mode.

Where can I locate the "firehose" files to use with the Qualcomm Product Support Tool (QPST)?

Thanks!
[Nook Touch Themes and Apps] kazikas:
Would it be possible to make it work on BNRV520?
[Nook Touch Themes and Apps] nmyshkin:
I imagine it is "possible".

The devil, as they say, is in the details. Based on what I have seen in the online manual, there appears to be only one way to turn the light on or off, that is, through the control panel opened via the light icon in the status bar. If that is correct, then I have no ideas for adapting the app. Without an actual device in front of me....well, let's just say I flunked out of Hogwarts.

If, on the other hand, there is still a shortcut long-press of the "n" button to turn the light on at its last intensity value, then there might be something to talk about and test.

Basically what I am saying is that I need more info about how the light is controlled before I could even hazard an adaptation. Can you enlighten me?
[Nook Touch Themes and Apps] kazikas:
Maybe this app would help https://github.com/Ryogo-Z/imx6_device_settings

I've tested it on BNRV520 and everything works besides turning light off.
[Nook Touch Themes and Apps] nmyshkin:
Nope. I'm not working in java but via Tasker. You didn't answer an important question: can the light be toggled by a long-press of the "n" button?

If the answer is "yes" then I can assemble a few test apps for you to try, just to see if I can get control of the light by standard Android means.

BUT, I have no idea about the secondary light feature. The system may be able to finesse that on its own if you have it set to "auto", but I just don't know.
[Nook Touch Themes and Apps] kazikas:
Yes it can, even with locked screen.
[Nook Touch Themes and Apps] nmyshkin:
OK, that's a good start. I'll work up a few little test apps later today and post them for you to try (I assume you have root access?).

According to what I've been able to find online the screen is 1448 x 1072 pixels. Is that correct as far as you know?
[Nook Touch Themes and Apps] kazikas:
Correct
[Nook Touch Themes and Apps] nmyshkin:
I've attached some apps in the zip below for you to test. These are NOT a final product, only an exploration of how the light might be able to be manipulated outside the B&N overlay.

Because these apps were produced with Tasker they share a dependency on two small files which are also included in the zip. These files must be in place (followed by a reboot)

before

you try to install the three apps. The files don't do anything so even if this all fails you could just leave them in place--or delete them, as you desire.

The files should be placed as follows:

/system/etc/permissions/com.google.android.maps.xml

/system/framework/com.google.android.maps.jar

Set permissions for both files to rw-r--r-- and reboot. Without these files resident, the apps will not install.

After that, install the three user apps provided. First try "GL Toggle". You will get a prompt for root access and then the light should come on and the status bar icon should change to reflect that. There may be a small delay (like a long-press on the "n" button). IF the light

does

come on, then tap on the icon again to see if it goes off.

If all that checks out, then turn the light on again (just tap on the icon again). Next tap on the "150" app icon. The light should change intensity (255 is max.). If that works then tap on the "20" app icon. The light should significantly dim.

If these changes work, turn the light off again (tap on the icon) and then back on. Did it come back on at the intensity where you left it last (20?) or some random brightness?

This is the minimum information I need to construct an app for you.

IF the apps refuse to install, all is not lost. I can compile them with a more current version of Tasker but my experience with all but the most complicated tasks has been that this older version works fine in general for KitKat.

IF the light does not toggle on/off then B&N has used some non-standard code for the "n" (home) button for some ridiculous reason. We would need to discover the code value to proceed. That's not a difficult task.

I'll keep my fingers crossed and await your responses.
[Nook Touch Themes and Apps] kazikas:
20 and 150 works as intended, but toggle doesn't.
[Nook Touch Themes and Apps] nmyshkin:
I interpret this to mean that the toggle app does not affect the light status at all but if you turn on the light in the usual way, the two intensity adjustment apps work correctly. This is useful information for constructing the slider routine.

Can you tell me one more thing? When you turn off/on the light in the usual manner does it come back on at the same intensity where you left it? (150 or 20?).

I have checked the "GL Toggle" on my NSTG and it works fine so it must be the keycode for the "n" button which has changed (unless you lack an SU control app...that would be a problem--did you get a prompt? The app MUST be able to access root).

On the NSTG there is a file /system/usr/keylayout/gpio-keys.kl

It is just a text file which includes the keycodes for back, home and power (158, 102, 116).

I have a small KitKat "phone" which I use as an audiobook and music player and to compile the Tasker apps. It also has a file /system/usr/keylayout/gpio-keys.kl

The keycode for home there is 102 (the standard). Check if you have a corresponding file on your NG3.

Edit: if you have ADB working with your device and PC, try sending this command:

adb shell input keyevent --longpress 3
[Nook Touch Themes and Apps] kazikas:
Light intensity works correctly, stays as left. With a 'n' button and with a ADB command.

The keycode for home button is 102, but the file on my nook is named imx-keypad.kl
[Nook Touch Themes and Apps] nmyshkin:
Wait! Does this mean that the ADB command I gave you toggles the light?!
[Nook Touch Themes and Apps] kazikas:
Yes
[Nook Touch Themes and Apps] nmyshkin:
Please install the attached app (you can install over the original if it's still on your device) and confirm that tapping on it toggles the light. If that works you can uninstall the three test apps.

We are nearly there! The last part is potentially the trickiest. Tasker apps, for all their seeming "magic" are limited to the device size and resolution they were made on if they contain graphical elements (without a lot of complicated programming, forking, etc.). Obviously the old NSTG and your NG3 have very different screen resolutions and pixel dimensions. But owing to some annoying behavior of Tasker on the NST when a full-screen display is wanted, I have learned over time to edit the xml content of an otherwise completed display task. That includes dimensions. But I've never tried it for dimensions outside the range of the device.

So...some time today I will put together another small test app which will (hopefully) display a colored rectangle where the swipe zone should be (see the first post for an example). My goal is to get something that is similar in scale for your screen resolution. If that works, then we are good to go with all functions pretested.

Edit: the test app is attached below. It should place a black vertical bar at the left edge of your screen, 927x36 pixels, roughly vertically centered. There should also be a small but faint "x" near the bottom corner of the bar. That's how you get rid of it. Otherwise, just uninstall the app and it will go away. If the size/position is totally wrong, a screenshot of some kind would be helpful. I can create and compile the app on a tablet with a higher resolution, if needed, by restoring a CM 11 ROM from a backup. Hopefully I won't need to do that.

BUT, as I stated earlier, I have no idea how this might interact with the secondary light feature ("night" light). In many ways this was a lot easier than writing the app for the NSTG because the NG3 light uses the standard Android brightness control. The NSTG uses a complex series of arcane maneuvers and I have to keep track of the current intensity, update databases, etc., etc.

I suppose there is a second brightness control on many e-readers now which use back and front lights. But I might be wrong. There might be only one set of lights which are are able to change in color tone (as many LEDs can) based on current changes, etc. First I have to complete the app and then you can find out for yourself.
[Nook Touch Themes and Apps] kazikas:
Sorry for the late answer. GL_Toggle works as intended and remembers last light value.

Test_Bar appears on the screen, but neither the toggle nor the slider works. And Test_Bar haven't asked for root access.
[Nook Touch Themes and Apps] nmyshkin:
The test bar is not supposed to do anything at this point. I only need to know if it's in the correct position. If so, then I will start work on the actual app. The position should be at the left edge of the screen (up against the bezel), approximately centered vertically, and pretty narrow (only 36 px). It should look similar to this:

View attachment 5968427
[Nook Touch Themes and Apps] kazikas:
Cha, I've even tried with a stylus...

It looks like in your screenshot.
[Nook Touch Themes and Apps] nmyshkin:
Excellent. Give me a day or two and I'll have a beta for you to try out.
[Nook Touch Themes and Apps] nmyshkin:
The original inquiry seems to have sort of died on the vine so I have no idea whether/how this performs on the NGL3. If

you'd

like to try it out for yourself, you need to get the dependency files for Tasker apps on KitKat from the zip in post #9 (discard the various test apks and place the maps jar and xml files as described in post #9). After a reboot install the app attached below. Please let me know if it works at all and whether it could use some adjusting.

I've attached an initial attempt at the app. Should be considered "beta" as I do not own the device to test it on. That's your job :)

Uninstall all the various test apps if you have not done so already. Be sure the light is

off

and then install the new app and tap on the icon. You should see a brief toast indicating that the app is activated. Unless the system kills the app, you do not need to tap on the icon again--ever (even after a reboot).

On the NSTG the app will rarely be dealt a death blow by the system when it is very busy or doing something really memory intensive. I can tell because there is no response to either a long-press or a swipe. Then I go back and tap on the app icon again and all is well. Presumably the GL3 is more robust memory-wise and you may never (fingers-crossed) experience this. Of course, the standard light controls continue to operate, so you're not going to be in a situation where you lose complete control of the light function.

Once the app is activated, a long-press right next to the left bezel should turn the light on (so your finger or thumb is partly on the bezel frame and partly on the screen--remember, the swipe zone is only 36 px wide). Once the light is on, the active area becomes swipe-sensitive and the slide of a finger or thumb right next to the bezel will change the light intensity. Remember, the swipe zone is really an accumulator, not a slider. So there's no need to run the entire length (although you can) to get to a certain intensity. You can just do some short swipes which eventually add up. Your preference. But, don't make a slide so hesitant that it is interpreted as a long-press, or the light will go out!

I tried to adapt the sensitivity to your display which has many more and much smaller pixels than the NSTG (and probably better response to swipes and scrolling in general). If it seems either too fussy or too sluggish, let me know and I will play with the numbers a bit.

The light should never drop below an intensity of 10 via swipe. Instead, to turn it off completely (at any intensity), execute another long-press next to the left bezel until the light goes out. Once the light is out the area is no longer swipe-sensitive.
[TCL 10 Pro  Questions & Answers] civan34:
Hello friends. I have a TCL-T782H model phone and the bootloader is locked. The phone restarts constantly and I need to install firmware. I couldn't find the software for this phone anywhere, can you please help. I need firmware for this model.

View attachment 5867281
[TCL 10 Pro  Questions & Answers] DoctorBooty:
Have you tried using this https://www.tcl.com/nl/nl/support-mobile/rma/mobile-upgrade?

Select your model and download it.

At this moment it's not possible to unlock the bootloader of this phone.
[TCL 10 Pro  Questions & Answers] civan34:
Yes, I tried that program. The firmware installation did not take place because the phone is up to date.
[TCL 10 Pro  Questions & Answers] sec6023:
Benimde başıma geldi çözüm bulan oldumu
[TCL 20 Pro 5G] jrevans:
On Friday I received a notification on my phone that an update was available for my T810S that I'm running in the USA on Cricket!

View attachment 5867323

View attachment 5867325

So, it's finally available!

Anyways, I just finished up backing up the images and other things from my phone, and am going to try installing it tonight.

My 64GB SD card has been full for some time, and I was saving stuff to the internal phone memory, which I don't like to do. But, I got everything copied to my PC, my RAID server and my backup drive, so I'm going to clean the items from my phone and do the update.

I sure hope that this fixes the notification issues.
[TCL 20 Pro 5G] jrevans:
Alright, I was able to successfully install the Android 12 update!

I really like the upgraded looks of the user interface changes, and it showed me a nice little tour of the Android 12 features. The extended screenshot capability feature could be really useful.

I'll give an update in a few days to let you know how it's working.

Here are the screenshots.

After clicking the install button it started showing a slow percentage increase, so I left it alone for half an hour while I did other stuff. When I came back, it was showing this.

View attachment 5867371

After the update, it showed this:

View attachment 5867373

Here's the About Phone screen, showing that I'm now running Android 12.

View attachment 5867375
[TCL 20 Pro 5G] jrevans:
Just a quick update to let you all know that everything has been working well for my TCL 20 Pro 5G (T810S) since I installed the Android 12 update. I actually get notifications from all of my applications, and battery life doesn't seem to be any different than when I was on Android 11. Having notifications from all apps again is a real game changer for me!

I uninstalled and reinstalled some of the applications that I had previously manually tweaked the power settings on.

The only oddity that I noticed, is that if I have JBV1 auto-start with Android Auto (like I've always had), it locks up Waze and freezes Android Auto! I need to look into why that is happening, but for now I just disabled the auto-start functionality of JBV1.
[TCL 20 Pro 5G] jrevans:
On May 10, 2023 I also received another OTA update, putting the system up to TCL UI v4.0.5EFV (from version TCL UI v4.0.5EFI)

I don't know what the update changed, but I installed it and it's been fine. Waze and Android Auto still hate each other in my truck though.

Here's the update installing:

View attachment 5973419

And here's after it has been installed:

View attachment 5973421

View attachment 5973423

Although it's cut off in the image, Build number is now 8.
[TCL 20 Pro 5G] jrevans:
I still have to have some issues with background applications being silently killed. I added them to the non-optimized battery usage list, but that didn't make a difference.

One of the apps that is closing is my password manager (KeePass) which I use a big ugly password to open, and then biometric/fingerprint to unlock once it is opened. It seems to stay locked in the background for about half an hour, letting me open it again with my fingerprint, then after a while it totally closes, requiring me to enter the ugly password again to re-open it. Sure would be nice to be able to keep it from being killed in the background.

The other app that I notice dying, is JBV1, an awesome radar detector utility program. I have it configured to automatically launch when I start Android Auto, but the AA launch watching process dies in the background and it doesn't autostart JBV1 when I start AA.

There are probably more apps that aren't running, but I use these two a lot.

Anyone know any other Android 12 tips to avoid apps/processes being killed?
[TCL 20 Pro 5G] ozyow:
Hi, I have one of these phones in Australia and I have not received the Android 12 update. Checking to see if its possible to trick the updater to allow the download in Australia.
[TCL 20 Pro 5G] Nadir Mohamed:
hello sir i tried to do a update to my phone and now its broken can u upload this rom or can u send it to me to flash it pls .
[Google Pixel 6 Pro] rayraycarter4:
Does anyone know how to get the pixel stand gen 2 working on a custom rom because it seems like none of the custom roms support the pixel stand... I've tried downloading the pixel stand app and it does nothing