yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 Questions & Answers] dmasteller88:
This phone is garbage period. I wish I would've never bought this piece of ****. It's glitchy it lags the connection is fcking awful and by far the worst hardware I've ever seen in a device....... My htc palm was better than this phone in 2003.
[Touch Diamond, MDA Compact IV ROM Development] SiemensLover:
Hallo,

sorry für this question but is it possible to have a Soft-SPL instaed of a Hard-SPL to jump the SPL protection like the HTC-Prohet.

with my Old HTC Prophet i used always the Soft-SPL (copy some files in the Phone, run them and the phone boot in bootloader mode, then flash any ROM) so i do not need to worry about warranty or else! it is more secure than a Hard-SPL

is that not possible with our precious diamond?

Thanx in advance

WBR
[Touch Diamond, MDA Compact IV ROM Development] cptsunshine:
This might not be a satisfying answer, but you can revert to a stock SPL at any time, see here: http://xdaforums.com/showthread.php?p=2324837#post2324837

-Alex
[Touch Diamond, MDA Compact IV ROM Development] SiemensLover:
yes i know that, but i do not want to swim in the Hard-SPL stories (change from 1.xx to 1.40, flashing, ROMS compatiblilty (some has problems with Hard-SPL after ROM flashing), reflash to stock SPL.. and so on..)

any way thanx for ur answer

WBR
[Touch Diamond, MDA Compact IV ROM Development] racerx_:
the issue is not necessarily jumping the SPL protection.. Hard-spl remains on your phone and protects you in case of a bad flash.. it is removable and doesn't really make any sense to not use it unless you're desperate for a really expensive paperweight..
[Touch Diamond, MDA Compact IV ROM Development] scorpio16v:
To answer your question, yes there is a kind of SoftSPL.

It was used to flash the HardSPL and is loaded by the batch, you executed.

It uses JumpSPL by pof and a modified mfg bootloader in .nb format.

Theoreticaly, you can take JumpSPL, the Bl.nb and a shortcut with the right arguments to the device storage and execute it.

Or use the SSPL from Developer HardSPL, it's one file.

And, no. I'll not explain more, because I won't write a How To for device bricking.

But it is highly recommended to use a HardSPL.

There is always a way back and in case of a crash, it may protect you from a nice brick. :D
[Touch Diamond, MDA Compact IV ROM Development] sumitescp:
It is safer to use HARD SPL.

DO NOT USE SOFT/JUMP SPL TO FLASH ROMS OR RADIOS.

THERE ARE CHANCES TO BRICK YOUR DeVICE USING JUMP/SOFT SPL.
[Touch Diamond, MDA Compact IV ROM Development] Fabliv:
I'm totaly agree with that. :)
[Touch Diamond, MDA Compact IV ROM Development] SiemensLover:
Thanx to all

vote for the HARD-SPL.... ;-)
[Touch Diamond, MDA Compact IV ROM Development] stepw:
Re-flashing SPL is the most dangerous part.

To use SSPL you don't have to re-flash SPL, so it IS safer.

If OS doesn't boot though, SSPL can't be used. HSPL is your best bet if you want to flash just anything you come across without damaging SPL.
[Touch Diamond, MDA Compact IV ROM Development] sumitescp:
Yeah but imagine your running sspl to install a rom, and your flash did not go well eventhough it completed the 100%. Now you are stuck on bootloader. You can´t do anything coz you did not have hard spl on. I think you can still recover using mtty.exe but that is a long thing. Do not take the risk of losing your phone forever by bricking it.
[Ubuntu Touch Ports to Android] Screenhacker101:
Hello, could anyone make an ubuntu touch port for the samsung tab 4 7.0 please?

I would want to make some use of the device by running ubuntu touch because android got discontinued for the tab 4 7.0 at android 4.4.2 which is very old now and not suppprted by anyone.

Thank you
[Amazfit] Rmopinto:
Hi.

I'm a go kart racing driver and I use the Verge on Cycling (no karting) to track my exercise. However, the GPS rate frequency seems to be very low and not accurate, as the track path goes all over the place, not only the track. I want to purchase and connect and external GPS with higher frequency. Tried QstarZ but it didn't connect. Do you know any other models? Have you tried any? Any suggestions to fix this?
[OnePlus 8 Pro Questions & Answers] Helio0:
Hi,

I received my OP8pro today and I am missing force dark Mode from developer option on op7pro.

It has a dark Mode on Utilities , but it's not usefull, the only app to choose os WhatsApp...

Any alternative to force dark mode on apps without It?
[OnePlus 8 Pro Questions & Answers] blaze9090:
Try in oneplus Labs options "dark mode for Apps"
[OnePlus 8 Pro Questions & Answers] Helio0:
That is what I said on Utilities, but you only can choose WhatsApp in my case, and WhatsApp already have dark Mode.... So it's useless.

I would like a force dark mode that turn almost every app to dark mode, like op7pro
[OnePlus 8 Pro Questions & Answers] dlads:
What apps aren't in dark mode?
[OnePlus 8 Pro Questions & Answers] Helio0:
Banking apps, news app like Flipboard. I don´t check all my apps yet hahaha, I want to unlock oem today and mobile will reset.
[OnePlus 8 Pro Questions & Answers] dlads:
One I turned it on most of my phone went dark. Don't think you're going to get 100% of apps to go dark.

Least not from my experience
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
May 2020 QQ2A.200501.001.B2 "CORAL" Magisk-Patched Boot Img [+UPDATE/KEEP ROOT GUIDE]

Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.

I've also installed and tested / verified that Kirisakura 4.2.0 is working great with this month's patch so far.

Also have EdXposed Canary 0.5.0.0 (4548) YAHFA installed. SafetyNet still passing as of now.

Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796392

Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796399

THESE FILES ARE FOR 10.0.0 (QQ2A.200501.001.B2, May 2020, All carriers except TW) ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!

If these files and/or guides are helpful, please drop a thanks and let me know. =)
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).

** You can only follow this guide exactly if coming from build QQ2A.200405.005, Apr 2020. But the general idea is the same for other builds, you just need the correct files for your device.

coral-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796390

coral-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796391

May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq2a.200501.001.b2-8309f363.zip

I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY

1. boot into bootloader

----------------

** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images

2. fastboot flash boot coral-qq2a.200405.005-factory-boot.img

3. fastboot flash dtbo coral-qq2a.200405.005-factory-dtbo.img

......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations

-----------------

4. use volume keys to change selection to boot to Recovery Mode

......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten

5. choose option "Apply update from ADB"

6. adb sideload coral-ota-qq2a.200501.001.b2-8309f363.zip

7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)

8. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img

9. done, start the phone

(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)

This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.

EDIT: Issues after updating?

If you end up unable to boot or bootlooping afterwards, you most likely have a module that isn't playing nice with the new build. There are 2 main things you can do:

1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly if you're in a bind.

2. I would recommend checking Tulsadiver's thread: https://xdaforums.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557

Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
[Google Pixel 4 XL Guides, News, & Discussion] elkay:
Worked like a charm, just like previous months. 3 minutes total once the factory image was downloaded. (I edit the flash-all and remove the -w) Thanks a bunch!
[Google Pixel 4 XL Guides, News, & Discussion] boonthongw@gmail.com:
Perfect method. Thank you.
[Google Pixel 4 XL Guides, News, & Discussion] Zerosbar:
hi good day...

With this method can i activate motionsense and always leave it active?

I belong to a country where the factory does not come active and i would like to have it, only i have read that every time the telephone is re-enabled.

In advance thanks for the help.
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
I just used this Magisk file and after it boots up past the G logo - All i get is a black screen. the only thing that I can do is hold the power button and reboot to same result. I had to revert to factory boot to restore with no root. What am I missing? PS I just used step 8 and 9...

I am on the May update already///
[Google Pixel 4 XL Guides, News, & Discussion] sidhaarthm:
It seems some of your previously installed modules/mods (using systemui) are interfering with the new update. I had the same issue a while back and eventually had to remove all Magisk modules and start afresh.
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
That is the thing though. I was not rooted and I had uninstalled Magisk for the last several months. So now I wanted to root again, and followed steps 8 and 9 after installing Mag Manager. Could the sysemui mods you are referring to be from many months ago before when I uninstalled Magisk/
[Google Pixel 4 XL Guides, News, & Discussion] sidhaarthm:
Its' hard to say without knowing what is/was installed bud. In my case I had some mods that changed accent colours, fonts and clock positions etc. I learnt the hard way and always made sure that I remove such modules before upgrading. I just upgraded from April to May OTA and it all seems to have gone down well. Root restored, Face Unlock working and Kirisakura 4.5 flashed :)
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?

I just tried to install the patched img again with the same results - black screen

Thank you in advance for any help!
[Google Pixel 4 XL Guides, News, & Discussion] sidhaarthm:
Yes, hang on, let me find the steps I took to fix.

---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------

Look at this post - https://xdaforums.com/showpost.php?p=81926759&postcount=46

I had success following these instructions. There's some other posts I found on XDA where users had similar issue - this is the only way without having to fully wipe and restore.

Hope it helps!:good:
[Google Pixel 4 XL Guides, News, & Discussion] Badger50:
Just curious, but are you fastbooting the patched.img via power shell or command prompt? And, are your platform-tools up to date, and are you using a USB A to C cable?
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
Fastbooting from command prompt

Platform tools downloaded yesterday

Yes on the USB cable

---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------

Unfortunatey, it does not look like it is working for me, when I open an abd shell and then type su nothing happens. What is supposed to happen? The curorsor just move down to the next line.

This is of course after fastbooting the patched img and have the system ui crash (black screen)
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Try booting in Magisk Core-Only mode. If it boots, it probably was an old module causing the issue. Then you can open Magisk Manager and try disabling modules until you find the problematic one, and remove it.

See this thread for more info: https://xdaforums.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557

I haven't had to boot into Magisk core mode yet on this device so I can't help you much. But according to Tulsadiver (OP of that thread), I believe he said the April boot image works fine for May (see pg 13).

Good luck!
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
Unfortunately, I dont think that i can do this since it says you must be rooted for either method. The problem is that I am not rooted and have not been for some time, but now i am trying to root via magisk...
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Try flashing the May Magisk patched boot image (which will root the phone), then fastboot boot image-new.img (NOT FLASH), the image Tulsadiver shares in his OP: https://androidfilehost.com/?fid=4349826312261766039 - don't worry the device says Pixel XL in AFH - he probably just uploaded it to an old folder of his. It's definitely the 4 XL core only boot image.

This should start up your phone rooted, but with all modules disabled.

Edit: also, I'm pretty sure he's referring to needing root in order to follow his processes and use those methods to generate the core-only boot image itself. However, he provides the bootable image for you luckily. Either way, I would still flash the May Magisk patched boot image first, otherwise when you reboot after booting core mode it'll just boot back into the existing boot file (in your case, stock). Also, I just tested for you, and that image-new.img works perfectly fine. I just tried it on my phone and it booted into core mode, exactly as if I did it through Magisk Manager. I also didn't need to use the additional script or delete the .disable_magisk file in the /cache folder - all I needed to do was uncheck core only mode in Magisk Manager. YMMV. I would also recommend installing Magisk Manager .apk before any of this to make your life easier.

So for you:

1. Install Magisk Manager if you haven't already - https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1

2. Reboot into bootloader

3. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img

4. fastboot boot image-new.img

5. Hopefully the O/S loads, open Magisk Manager, disable offending modules.

6. In Magisk Manager, go to settings and uncheck "Magisk Core Only Mode" option.

7. Reboot.
[Google Pixel 4 XL Guides, News, & Discussion] aaronc_98:
Thank you! You are my hero! Thank you for taking the time to explain this- everything is working as expected
[Google Pixel 4 XL Guides, News, & Discussion] i5lee8bit:
Glad it worked out for you. Make sure you thank Tulsadiver for his work too, his core-only guide is totally clutch ;)

I'm gonna edit the OP for some basic steps in case of errors. Thanks for keeping us posted.
[Google Pixel 4 XL Guides, News, & Discussion] snovvman:
Thanks for the patched kernel. I usually patch the kernel before I flash the update so I can boot with a patched kernel after the update. I was distracted and forgot. You saved me bunch of extra work!
[Google Pixel 4 XL Guides, News, & Discussion] Miustone:
Little hint from a Xperia 5 User.

use: fastboot --set-active=b

To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.

use: fastboot --set-active=a

To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.

BR

---------- Post added at 16:44 ---------- Previous post was at 16:43 ----------

Little hint from a Xperia 5 User.

use: fastboot --set-active=b

To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.

use: fastboot --set-active=a

To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.

BR
[Samsung Galaxy Note 10+ Questions & Answers] akaSk8krew:
Hi devs:)) sorry for my bad english first..second i need make you a question: is there or anybody have a kernel to work 100% with kali nethunter?? I just make a question..i know its not easy to make one..but, if anybody interesting in pentesting, can work about this...i need to know more about this, and i need to work in this. [MENTION=3931450]dr.ketan[/MENTION], [MENTION=1649452]geiti94[/MENTION] [MENTION=4610599]Ivan_Meler[/MENTION] are you interested?? Sorry my bad english..wheel in the air:D
[Samsung Galaxy Note 10+ Questions & Answers] nightmarerep:
it seems no one will help us mate
[Samsung Galaxy Note 10+ Questions & Answers] akaSk8krew:
I know:"( it is what it is..i use kali on pc..i liked to try on my note too..but with total functions ok, but needs kernel working for total support..
[8525, TyTN, MDA Vario II, JasJam General] genekrtr:
Hi. How do i remove installed software that i automatically installed when i flash the original att htc rom for the 8525. I want to remove office, and install the cabs. basically i want to free up room and place everything on a sd card. also i don't want to touch or replace the original rom core system. Thank you in advance for your help. genek
[8525, TyTN, MDA Vario II, JasJam General] MikeChannon:
Well I appreciate you do not want to change ROM, but essentially what you are wanting to do is exactly what a customised light ROM does.

However, what you can try is to do a hard reset. When the screen comes up saying that it is installing provider customisation, you put the stylus in the reset hole. This effectively stops the installation of the ROMs customised programmes.

Now all you have to do is find cabs of the programmes you want.

Of course the essentials of the programmes are still on your device taking up some space, but not installed.

You might want to also investigate "extended ROM" use the search facility.

Also check the differences between program memory and storage memory all previously discussed here.

Mike
[8525, TyTN, MDA Vario II, JasJam General] genekrtr:
thank you for your reply. I will look around and see what I can find. Thanx for pointing me in the right direction.
[Galaxy Tab S2 Q&A, Help & Troubleshooting] tensux:
I have owned several sm-t713s and an sm-t817. I could have sworn at one time the haptic feedback worked on the sm-t713s. I thought it worked before rooting and installing various lineage roms. Odin with fresh firmware does not bring it back. the haptic feedback works fine on the sm-t817.

I just picked up an sm-715. The haptic feed back worked on first boot. Now i am afraid to install a new ROM and risk losing the haptic feedback. does anyone know is this a difference among the models? i do want to install LineageOS
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] amanisthebest:
At first I thought it was because my gyroscope sensor stopped working. But I tested it with an app and it works fine. So it must be some software issue. Does anyone know how to fix this?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] matar_shady:
Hello, have you resolved the raise to wake issue? My problem is similar, my redmi note 9 pro on android 11 stock launcher has the raise to wake feature that stops working every 5 days, meaning every 5 days I reboot phone for the feature to work, then after 5 days it seases to work and I have to reboot phone again for it to work and so on.

Any idea what could be the issue? Gyroscope is working fine as well as accelerometer.

Appreciate any help, i haven't rooted the phone yet, so cannot do much from shell termux...

Regards
[Google Pixel 4 Guides, News, & Discussion] i5lee8bit:
May 2020 QQ2A.200501.001.B2 "FLAME" Magisk-Patched Boot Img [+UPDATE/KEEP ROOT GUIDE]

Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.

I've also installed and tested / verified that Kirisakura 4.2.0 is working great with this month's patch so far.

Also have EdXposed Canary 0.5.0.0 (4548) YAHFA installed. SafetyNet still passing as of now.

Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796525

Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796524

THESE FILES ARE FOR 10.0.0 (QQ2A.200501.001.B2, May 2020, All carriers except TW) ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!

If these files and/or guides are helpful, please drop a thanks and let me know. =)
[Google Pixel 4 Guides, News, & Discussion] i5lee8bit:
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).

** You can only follow this guide exactly if coming from build QQ2A.200405.005, Apr 2020. But the general idea is the same for other builds, you just need the correct files for your device.

flame-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796522

flame-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261763724

May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq2a.200501.001.b2-46940f66.zip

I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY

1. boot into bootloader

----------------

** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images

2. fastboot flash boot flame-qq2a.200405.005-factory-boot.img

3. fastboot flash dtbo flame-qq2a.200405.005-factory-dtbo.img

......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations

-----------------

4. use volume keys to change selection to boot to Recovery Mode

......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten

5. choose option "Apply update from ADB"

6. adb sideload flame-ota-qq2a.200501.001.b2-46940f66.zip

7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)

8. fastboot flash boot flame-qq2a.200501.001.b2-magisk_patched-20.4.img

9. done, start the phone

(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)

This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.