yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S6 Lite Guides, News, & Discuss] warfront1:
Warning: I have only tested this on my own SM-P613 Samsung Galaxy Tab S6 Lite and I was willing to brick it to figure this out.

Perquisites:

LineageOS 20.0 for Galaxy Tab S6 Lite 2022 (Qualcomm)

I used the wonderful guide and prepared packages from this XDA thread:.

I am not sure if newer or older versions would work, but I would bet they do with slight modifications.

Magisk.v26.3.apk

I would imagine newer versions of Magisk would work, this is just the version I used.

You can find this version at this GitHub release link.

Installation tips:

I installed LineageOS 20.0 following the instructions above almost exactly.

Once LineageOS was installed I installed Magisk via adb: `adb install Magisk.v26.3.apk`

I then used 7zip to extract the boot.img out of the lineage-20.0 zip

I moved the boot.img over and patched it just like any other patching using Magisk. (You can follow a generic guide for that)

I then copied back over using adb pull PATCHEDMAGISKIMAGENAMEHERE, renamed it to boot.img, and copied it into the the lineage-20.0 zip

This will effectively replace the stock boot.img provided with lineage-20.0 zip with the Magisk patched version.

I then side loaded the lineage-20.0 zip as described on the LineageOS 20.0 installation instructions.

I then side loaded the apk `adb sideload Magisk.v26.3.apk`

adb

In the Android settings menu you will need the following enabled:

Developer Options

USB debugging

Rooted debugging

Steps:

Download init.qti.can.sh from this GitHub link.

Be sure to extract the zip folder, to get to the raw Shell script.

Execute the following two adb commands:

adb root && adb remount && adb push init.qti.can.sh /vendor/bin/init.qti.can.sh

adb root && adb remount && adb shell "chmod 755 /vendor/bin/init.qti.can.sh"

Execute the following adb command:

adb pull /system/etc/init/hw/init.rc

This will download `init.rc` to your local computer

Edit `init.rc` with your text editor of choice and search for the text "class_start charger", after it add a new line using the same spacing with the following text:

exec u:r:magisk:s0 -- /vendor/bin/init.qti.can.sh

For example my init.rc looks like the following:

on charger
class_start charger
exec u:r:magisk:s0 -- /vendor/bin/init.qti.can.sh

Save your changes to `init.rc` with the text editor you chose.

Run the following adb command:

adb root && adb remount && adb push init.rc /system/etc/init/hw/init.rc && adb shell reboot -p

Congratulations, you should now be booting automatically when a charger is connected.

*Note*: I added a failsafe into the shell script to not boot when there is less than 20% battery capacity remaining.

Also, I will be keeping long term archives of all files required for this procedure, so let me know if any of the links go down.

Thanks,

Warfront1
[Samsung Galaxy J7 Questions & Answers] HeatSense:
I am aware that my warranty is void and the related risks

I tried installing TWRP Recovery today but the phone got stuck in a bootload

What I did: (OEM Bootloading ON, USB Debugging ON, Currently in downloading mode)

1. Install Odin v3: From https://samsungodin.com/

2. Install TWRP .tar: From https://dl.twrp.me/j7xelte/ (Top of the list, upload of: 2017-12-09)

3. Opened Odin

4. Placed TWRP .tar in AP, configuration: Only F.Reset Time (Auto Boot was not active)

5. Started operation

6. Success: 0 Failures

7. Exited downloading mode

8. Turned on phone

9. Phone turned on without any issues, no signs of data lost

10. Tried to go to TWRP Recovery, did not open <---(?)

11. Searched around in all menus (Power button + Volume Up + Home and Power button + Volume Down + Home)

Observations: Warranty had already expired a few years back, the device status had changed to "Custom"

12. Search around about 3 more times

Observations: Device status changed back to "Official" <---(?)

13. Decided to install TWRP again

14. Opened Odin, loaded the same .tar file on AP

15. Started (same configuration in Step 4)

16. Turned on phone

17. Boot looping issues started <---(!)

18. Tried to solve it by myself but didnt work (Power button + Volume Up + Home and Power button + Volume Down + Home)

19. Power button + Volume Down + Home turned of the phone and turned it on again, getting stuck in a bootloop

20. When I did it about 3 times, the phone turned off completely

21. Turning it on again, it got stuck in the boot loop

**UPDATE (was experimenting while typing this)**

1. The phone was in the boot loop, suddenly turned off (assuming it was the battery)

2. Decided to go into download mode

3. Actually worked, asked me to continue or exit

4. Decided to exit

5. Phone boot up logo began

6. Died after 10 seconds

Power button + Volume Up + Home shortcut was not working

*It seems that the phone has reached 0% charge, downloading mode is the only thing that works but it turns off after 15 seconds when no action is taken*

Is the phone bricked ? Or can it be saved?
[Samsung Galaxy J7 Questions & Answers] HeatSense:
Update: Partial success?

Spent a whole lot of days through odin failures, stock rom downloading and driver hassle. Found out that I flashed a version which was meant for the J7 normal version, not its prime version. So I found a TWRP alternative on XDA and it worked. The TWRP menu is working however I am now faced with another issue

Phone is now going through an actual bootloop. It turns off and starts again, but the TWRP menu works. Can anyone suggest some tweaks i could perform through TWRP to get it back up and running?

TWRP Alt for SM-G610F (not mine): https://xdaforums.com/t/recovery-root-twrp-3-1-1-1-galaxy-j7-prime-sm-g610f-2016.3617377/

I have not installed any no-verity packages or anything else onto the phone
[Samsung Galaxy J7 Questions & Answers] HeatSense:
Update: Complete success!

After analysing the bootloader error by the phone, I checked on it and found out that I had to download a firmware which was a DD version and not XX version. From SamFW.

It seems like it is back to life.
[Samsung Galaxy J7 Questions & Answers] HeatSense:
Found out the issue with the phone

Apparently the recovery is bricking the phone. I loaded it again and it bricked the entire system
[Samsung Galaxy J7 Questions & Answers] HeatSense:
Mistake on my side

The device goes into bootloop because I did not disable dm-verity and force-encrypt

I have decided to let go of recoveries, now pursuing the path of rooting (which was a success using magisk) (I would have rooted and resetted my device around 5 times till now)
[Samsung Galaxy J7 Questions & Answers] animeuwu212:
Glad you managed to fix it yourself. :)

I'll leave the link to no-verity-opt-encrypt for people who need the same help.
[Windows Mobile Development and Hacking General] Kojote1980:
The "Next Element Deluxe" is a logical game, where your task is to destroy all the fields on the screen. To complete this task you have to rack your brain and deal with 80 levels. They all have interesting graphics and nice music. The "Next Element Deluxe" is a game with levels of rising difficulty, which tries to provide all players a lot of satisfaction.

This release was available to donators of Zielok's games, but has been made public for everyone now. The author still does accept donations ;)

PocketPC - System requirements:

Arm Processor - Support 240x240, 240x320, 480x480, 480x640

WM SmartPhone - System requirements:

Arm Processor - Support 176x220, 240x240, 240x320, 320x240

Authors page and download: http://zielok.com/?action=onegame&game=next_element_deluxe
[Windows Mobile Development and Hacking General] egzthunder1:
Not a bad game. Thanks for the info...
[Google Pixel 8 Pro] n3m35155:
Has anyone received the new camera update to 9.2 from playstore?

I tried side loading the APK but it just errors with wrong version message, shuts down and repeats.
[Google Pixel 8 Pro] Gilg@mesh:
download the bundle apk, and use the APK mirror app to install.
[Google Pixel 8 Pro] Mrowkarz123:
To people who have updated, can you confirm this? https://www.reddit.com/r/GooglePixel/s/UEwqqODmNR
[Google Pixel 8 Pro] Gilg@mesh:
no problems here.
[Google Pixel 8 Pro] Lughnasadh:
No problems for me either.
[Realme 7 Questions & Answers] jack.demolay:
Hello

After a few weeks trying to flash my Realme 7 without success, I managed to leave it as a brick.

My device is a Realme 7 with helio G90 MTK 6785 microprocessor, but it has some features, and that is that it is dual SIM+ SD (3 bays), so it is not the same as the RMX2151.

It is a device that can not enter fastboot mode. At the moment it is locked.

The only way I managed to install recovery and ROM is through brun mode, and with the MTKclient python tools.

But, the ROMs that I have managed to install do not work, some get to install, but then the phone does not have all its features, for example, they do not recognize SIM.

In my case the ROMs of the RMX2151, or the OPPO did not work.

The last ROM that I installed, has left me the phone as a brick, and now the MTKckient tells me that there is no PRELOAD

I've been looking at GITHUB MTKclient bkerler MTKclient page and says that the MTK678X chip is not supported.

So, ask if anyone knows.

can I install a preload from brun mode on a MX2155?
[Realme 7 Questions & Answers] mvikrant97:
Seems like you erased the preloader and the security partitions like NVdata and NVram.

Which stock ROM did you flash?

You can download the correct stock firmware from here.

{Mod edit: Link to paid services website removed. Oswald Boelcke, Senior Moderator}
[Realme 7 Questions & Answers] jack.demolay:
Hello.

Thanks for replying and for the link.

The problem is that not having access to the FASTBOOT I can not load the ROM, the only way is through the Broom and MTKclient tool shows the error that does not recognize the preload on the phone, so first I have to try to load the correct preload, but I do not know how to do it.
[Realme 7 Questions & Answers] mvikrant97:
I have License for unlock tool software.

If you want I can remotely assist you using it but I can do it tomorrow.
[Realme 7 Questions & Answers] jack.demolay:
Hello.

Thank you very much for your help

but that tool can flash in broom mode?

as I said the phone can't enter neither in Fastboot nor in recovery mode
[Realme 7 Questions & Answers] mvikrant97:
Yes it can flash in BROM mode as well as Preloader mode.
[Realme 7 Questions & Answers] jack.demolay:
Very nice.

what's the next step?
[Realme 7 Questions & Answers] jack.demolay:
Hello

it's already fixed.

With the MTKckient software from https://github.com/bkerler/mtkclient

Download a new ROM [azROM.net]2_REALME_7_RMX2151_MT6785_ROM_FULL_BACKUP_SCATTER

and extracted the boot.img, Vbmeta.img and preload.ini files

and burn them to the phone with

python mtk r boot,vbmeta boot.img,vbmeta.img --preloader=preloader.bin

After that, download all the other ROM files with

python mtk rl out --preloader=preloader.bin

At this point the MTKclient v.2 GUI recognized my phone, and I was able to install the latest ROM.

Thank you very much
[General Questions and Answers] IndigoHD:
After flashing the xiaomi.eu rom it leaves my system partition with exactly 0kb of free space.

Making it impossible for me to flash the NikGapps package.

Ive seen people resize the system partition in youtube videos and it seems straightforward, but "UnofficialTWRP" seems to be the only custom recovery available and it will let me adjust just about any other partition, but not the system-partition.

I've tried all night and im exhausted, i hope someone here might be able to help me out.
[General Questions and Answers] xXx yYy:
Recovery for Xiaomi devices - Browse Files at SourceForge.net

List of relevant recovery in one place

sourceforge.net
[Samsung Galaxy Fold Questions & Answers] PhamhuyN9002:
I have a Galaxy Fold 5G (F907N) from Korea, but it failed the inner screen. I accidentally reset it without knowing that the phone setup wizard will require to open the inner screen to setup the phone. If there anyway to do it on the cover screen, or any kind of bypass the setup wizard by ADB? Also I can't found any custom rom for this phone, so it would be more difficult to do work on this thing.
[Samsung Galaxy Fold Questions & Answers] shafictech:
i have the same problem, how did you fix it
[Samsung Galaxy Fold Questions & Answers] santogeorge:
Easy set up with the outer screen
[Redmi Note 12 4G] ShafiqTanwar:
Hi All,

I have Redmi Note 12 4g as a secondary device at home, I record all calls using default call recorder, however I want to hide the call recording icon (call recording button) which shown in calling menu while we are in a call and also I want hide call recorder option in dialer app settings but keep recording all the calls

Anybody here who can modd default dialer app which can have option to hide recording icon as well as call recorder settings so nobody can disable it.
[Samsung Galaxy S23] badaas:
I know there's the Dr Ketan, anything else lurking around the interweb?

Thanks
[Samsung Galaxy S23] badaas:
Wow XDA really did die 😝
[Samsung Galaxy S23] Xceeder:
There's another rom called beyondrom I'm using it and it's got some really cool mods ...
[Samsung Galaxy S23] ThunderShankar:
@Xceeder pls share your experience. How is Beyond rom ?

Do we flash gapps seperately or is it included by default. Also, do you use samsung services like samsung pay etc.. did you require something like KnoxPatch to get it working ?
[Samsung Galaxy S23] ThunderShankar:
I know there are GSI avaialble but fingerprint reader and 5G is not yet working it seems (refer here)

Haven't been able to try anything out since this is my only device at the moment.
[Android Q&A, Help & Troubleshooting] WIFIDarthMaul:
I received this phone (Blu View 4 B135DL) basically brand new for free from a friend and I wanted to root it. I enabled developer mode and didn't see a OEM bootlocker option, and was hoping this wouldn't be like my other phone (Galaxy S21 Snapdragon) where it can't be rooted. Anyone know anything?
[Android Q&A, Help & Troubleshooting] luridphantom:
have you tried using mtkclient?
[Android Q&A, Help & Troubleshooting] SuperUser666:
This is the current information for my B135DL. I pulled it from MTK Tools. I tried MTK SU on it, and got a whole lot of nothing - "Failed critical step init 1." IK want to get a device thread going on this in the BLU four, but don't know how to make that a thing.

Hardware : MT6761V/CAB

Model : B135DL

Build number : SP1A.210812.016 release-keys

Build date UTC : 20231028-094546

Android v : 12

Baseband v: MOLY.LR12A.R3.MP.V233.6.P20

Kernel v : 4.19.191-ge12a2fc01d0e (nobody@android-build) (Android (6443078 based on r383902) clang version 11.0.1 (https://android.googlesource.com/toolchain/llvm-project b397f81060ce6d701042b782172ed13bee898b79), LLD 11.0.1 (/buildbot/tmp/tmp6_m7QH b397f81060ce6d701042b782172ed13bee898b79)) #1 SMP Sat Oct 28 16:05:14 CST 2023
[Android Q&A, Help & Troubleshooting] SuperUser666:
After a little Google-Fu, I was able to find functional drivers that allow the device to be seen in Fastboot. After a fastboot getvar all command, I managed to pull the following output:

Spoiler content hidden.
[Android Q&A, Help & Troubleshooting] alecxs:
use mtkclient and dump the vendor_boot partition. root it with Magisk, unlock oem unlocking, unlock bootloader and flash magisk_patched.img from fastboot. if you don't have oem unlocking in developer options, use mtkclient unlocking instead. note: factory reset required
[Android Q&A, Help & Troubleshooting] luridphantom:
if you can root with mtkclient ill be down to get one myself, just that blu is pretty anti bl unlocking
[Android Q&A, Help & Troubleshooting] SuperUser666:
I'd love to, but MTK Client failed at init step 1. I'm guessing it doesn't see it. I'm on the client thread asking for help on that. If y'all have tips, let me know. I'll gladly do whatever I can to try and root, and then I'll make a TWRP port.
[Android Q&A, Help & Troubleshooting] luridphantom:
youre using mtk-su which is ancient

mtkclient is this https://xdaforums.com/t/guide-mtk-how-to-use-mtkclient-and-set-it-up.4509245/
[Android Q&A, Help & Troubleshooting] SuperUser666:
Yeah, that one just flat doesn't see the device. MTK SU was the one that failed at init step 1, and the tools are what I pulled my info from. I'll give it another go after I get some sleep, say around 1800GMT (Noon US Central). I'm still waiting on a reply from the guy with the MTK SU tut thread about why it fails.
[Android Q&A, Help & Troubleshooting] alecxs:
There won't be a reply just read the the thread more carefully.
[Android Q&A, Help & Troubleshooting] SuperUser666:
Yeah, I missed that bit. I've been out of the game for seven years - long story - and like a dumbass, went right to doing before the first, most important step: RTFM.
[Android Q&A, Help & Troubleshooting] SuperUser666:
View attachment 6086164

I'm sitting here just like this, and not getting anywhere. I'm open to ideas. I'm running Ubuntu 22.04 LTS, and I have all the things for the Linux version of mtkclient.
[Android Q&A, Help & Troubleshooting] luridphantom:
do the cmd line version and enter python mtk da seccfg unlock

if it throws a 0x7024 error its already patched up
[Android Q&A, Help & Troubleshooting] SuperUser666:
I got the 7024 from MTK Bypass. Am I likely to get it from client, as well?
[Android Q&A, Help & Troubleshooting] alecxs:
If you can wait a day or two there is new unlock method. ask here

Introducing the XDA DevBox - The Future of Development is Here

Update April 2nd: This was of course our April Fools' joke for 2024. Thank you all and be sure to check out our update here. The signature most mods had: The post: Fellow XDA Developers! We here at XDA are always pushing the boundaries of...

xdaforums.com
[Android Q&A, Help & Troubleshooting] SuperUser666:
So, after attempting to use everything listed in the posts above, I've come to the conclusion that we're not going to be able to root this device. It looks like BLU took a 💩 phone and made it worse by ensuring we can't do anything with it without a lot of risk. If anyone comes upon this thread later and has a method not listed above, or something that can get us heading in the right direction, let me know.
[Sony XA2 Ultra Questions & Answers] diver_2020:
Can anyone tell me where is the test point for xa2 ultra , my phone stuck in device manager shows SOMC flash drive , no flashmode and no fastboot i tried everyway to flash but cannot please i need serious solution tried and trusted not a solution of try this and that if anyone fall in the same problem and solved it please let me know . Thanks you .
[Sony XA2 Ultra Questions & Answers] Renate:
Well, maybe there isn't one and you need to be the trailblazer.

Here is some good advice for any Qualcomm device using single point test (which should make life easier).

https://xdaforums.com/t/dev-motorola-unbrick-tool.4491309/post-88894191
[Touch HD Themes and Apps] mallman:
Available in Downloads at www.swampthing.net
[Touch HD Themes and Apps] JohnQ:
well, ill be the 1st in xda to test this great theme!
[Touch HD Themes and Apps] mami:
Nice theme, but how do you move items on screen? It says "use d-pad...." What`s that?

Thanks

don`t bother, I figure it out. Thanks anyway!

Nice work!
[Touch HD Themes and Apps] mallman:
great let me know how the install goes

I placed a FAQ section in post #1 now. I see you figured it out but wanted to get your very good question there.
[Touch HD Themes and Apps] mallman:
new version 1.1 uploaded in post #1
[Touch HD Themes and Apps] GLOC:
Mallman,

There are a lot of calls being made to shortcuts that don't exist on my machine and as such I cannot open the theme.

Might be worth putting a list of the shortcuts from the first page in the post so that the scripts can be checked before running.

Good effort, looks better than V1

Regards
[Touch HD Themes and Apps] mallman:
thanks for the feedback. Can you let me know what those are? Are you on a WWE ROM? that is what I am building these from so the shortcuts you are referencing probably are wrong. They are probably the control panel shortcuts i put into the new doc on the first page.
[Touch HD Themes and Apps] GLOC:
I am using WWE rom (Orange UK) but I have moved lots of the shortcuts from the root Programs into other folders to make it easier to find programs.

Once all the shortcut errors 'ran out', the desktop was visible but was a mess.

To install I just copied the zipped folders over the top of the v1.0 installation, that may have caused some issues so when I get home this afternoon I am going to try a fresh install. Finally, the v1.1 theme needs to have a 1.1 title when loading through the settings pages as at the moment v1.0 & v1.1 have the same name.

Regards
[Touch HD Themes and Apps] twisted-pixel:
having a few issus with the carbon theme. When I click the windows button (bottom left corner) I just get a blank strip appearing on the left of the screen...so I can't get into the "start" to access program etc.

any ideas?
[Touch HD Themes and Apps] 1337_V1k1n6:
PROBLEM

Great theme, but along with the rest of your themes, I have a problem getting it to wor.. I run a norwegian rom and therefore mye storeage card is not called "storage card" but "lagringskort" this makes it impossable for the theme to find the icons :( is t possible to make a version where the icons are on the device? I have the same problem with your iphone theme..

thx

********* never mind!! I have to learn how to read "readme"-files
[Touch HD Themes and Apps] mallman:
lol on the never mine thing you wrote. Unfortunately there is no way around it other than to make the "storage card" folder in the root of your internal memory and go from there. That is just the way WAD2 works and I cant change that. Thankfully the themes are pretty small so they dont take up all your internal memory space
[Asus ROG Phone 6 / 6 Pro] d_ave:
I got a cheap Rog 6 with a broken display. As i have experience replacing displays i decided to give it a go. When i received it i noticed that the phone has already been opened and that the display was damaged from the inside - front glass is intact, but the amoled panel behind it has a puncture, probably from a screw. someone has disassembled the phone and probably mixed up the screws and damaged the display. that's ok, but it turns out this is not the only issue. phone won't turn on when i hold the power button - even with a broken display it should still vibrate when i turn it on. when i connect it to a charged the red led turnes on, but the phone still cannot be turned on. so my suspects are:

- dead battery. measuring the voltage between the + and - of the battery gives me only 0.23V. This doesn't change when i leave it on the charger. if i disconnect the battery and plug in the charging cable the red led is not turning on, so it seams that the phone is recognsing the battery. also if i leave it to "charge" the battery the mainboard gets a bit warm. not hot, just a tiny bit warmer than the rest of the phone, so it seams that current is flowing, but the battery is not charging

- power button issues. chances are that the power button is gone. any ways to try to power on the phone without the power button?

- dead board. is there a way to check if the motherboard is gone? if i connect the phone to my laptop nothing happens, it's not recognised at all. holding different button combinations also doesn't do anything

Any ideas hoe to identify what might be wrong?
[Asus ROG Phone 6 / 6 Pro] Dong-+:
Did you fixed it?