yashsingh1/xdaforums huggingface dataset:
[Realme GT Neo 2] wootje_:
IMPORTANT

This guide works for RealMe GT Neo 2 on Android 12 with RealMe UI 3.0.

Do it at your own risk. I will not be responsible for any damage that may occur.

Requirements

Bootloader unlocked RealMe GT Neo 2

https://xdaforums.com/t/bootloader-unlock-realme-gt-neo-2-rmx3370-all-variants.4391679/

A PC (Linux, Mac or Windows) with adb-fastboot installed

https://developer.android.com/studio/releases/platform-tools

USB cable

Magisk stable Apk (attached)

twrp.img (attached)

Software needed

ADB-FASTBOOT setup

twrp.img

Magisk APK

Root Checker APK

How to

1. Copy Magisk APK, Root Checker APK & “twrp.img” to root of USB storage of your phone

2. Copy “

twrp.img”

to your PC “C:\adb” folder

View attachment 5813067

3. Boot your device into fastboot mode

Hold power button & volume down button for 6 seconds while phone is turned off.

4. Go to “C:\adb” folder ,

5 Press Shift and right click ,

6. Select open PowerShell / Command Prompt in this folder

For Command Prompt:

- Press the Windows button on your keyboard

- Type cmd

- Open Command Prompt

- Type “cd /d C:\adb”

7. Now type:

fastboot devices

8. Press Enter

9. It should show your device now

10. Now type:

fastboot boot twrp.img

11. Your device will reboot and after some time it will show TWRP logo (takes about 1 min)

View attachment 5813069

12. Tab the “Backup” button

13. In TWRP backup “BOOT, EFS, Modem & Persist-Image”

View attachment 5813071

14. When backup is done go back to TWRP home

15. Tap the “Install” button

16. Go to the folder where you saved the files

17. Select "install image"

18. Select “twrp.img “

19. Select "recovery partition"

20. Swipe to confirm flash

View attachment 5813073 View attachment 5813075

21. When the process is complete go back to TWRP home

22. Press the “Install” button

23. Select the Magisk APK file

24. Swipe to confirm flash - this will install Magisk

25. When the process is complete go to TWRP home

26. Tab the “Reboot” button

27. Select “System”

28. Now phone will reboot into system

29. Open the file manager app

30. Install the Magisk APK you copied earlier

31. Install the Root Checker APK you copied earlier

32. Open the Magisk app, it will show that Magisk is installed

View attachment 5813077 View attachment 5813079 View attachment 5813081

33. To be sure the Magisk is installed press the “Install” button

34. Select “Direct Install”

35. Press “Lets Go”

View attachment 5813083 View attachment 5813085

36. After process is complete press the “Reboot” button

37. The phone will boot back to normal system mode now

38. Now your phone should be rooted with Magisk

39. To be sure open the "Root Checker" app

40. Press “Check Now”

41. The root status should become ROOTED

42. You rooted your phone successfully
[Realme GT Neo 2] Feaqwell:
Work?
[Realme GT Neo 2] SanOne+1:
SafetyNet is broken
[Realme GT Neo 2] wootje_:
1.

Install the Safetynet Fix module for Magisk:

https://github.com/kdrag0n/safetynet-fix/releases

The issue should be fixed. If it isn't, you can try this:

2.1

Install the Magisk Hide Props Conf:

https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases https://github.com/wootje/MagiskHidePropsConf/releases

2.2

Install Termux:

https://github.com/termux/termux-app/releases

2.3

Open Termux

Type "su"

Type "props"

Change the fingerprint to a device that is Netflix, Disney+, etc. certified

If that doesn't help, you could lock your bootloader, but you won't be able to flash (custom) firmware.

1. adb reboot bootloader

2. fastboot devices

your device should be listed

3. fastboot flashing lock

or

fastboot oem lock

(old models)

4. fastboot reboot
[Samsung Galaxy A30 Questions & Answers] RaveSep1:
Hi, i had installed TWRP and magisk in few months ago, and for some reason, i installed stock rom file on my device. But I realized that my device got unrooted.

So, i flashed the same twrp.tar that i used before, now my device keeps booting into twrp (even when i select reboot>system)

Help me, thx
[Sony Xperia 10 II Guides, News, & Discussion] wootje_:
IMPORTANT

Rooting can break your phone. Do this at your own risk.

Intro

This guide explains how you can root any Sony Android phone without installing a custom recovery like TWRP. It's possible by downloading the latest firmware, patching the boot IMG file with Magisk and flashing the patched boot IMG.

Note 1:

If you have the XQ-AU52_EU_59.2.A.0.463-R14C firmware installed (Sony Xperia 10 II EU Android 12), you can skip downloading the firmware and converting the file from SIN to IMG. Flash the patched "boot.img" file in the attachment instead.

Note 2:

If you don't like the skin that's installed along Android 12 on the Sony Xperia 10 II, you can downgrade the firmware by using Sony Xperia Flash Tool - Emma.

Note 3:

All files I collected are available

How to

Install all Android updates on your phone

Back-up your phone with a tool or Google back-up

Unlock the bootloader (wipes all data on your phone)

Sony users:

https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/

Download the latest firmware

Sony users can use XperiFirm which you will find in the attachment

Make sure the version you download matches the one on your phone!

Convert the “boot SIN” file you just downloaded to IMG:

Drag the “boot SIN” file to “unsin.exe” and an IMG file will be created

(you will find "unsin.exe" in the attachment)

Copy the IMG file to your phone

Copy Magisk APK to your phone

(you will find Magisk in the attachment)

Install Magisk on your phone using the APK you copied

Open Magisk on your phone

Install Magisk (button in the app) and patch the “boot IMG” file you just copied

Get the files for ADB (platform-tools)

(you will find the files in the attachment)

Copy the patched “boot IMG” file to the “adb” folder on your pc and rename it to “boot.img”

Enable USB debugging on the phone:

a) Settings » About » Tap “Build” until you a message appears you are a developer

b) Settings » Advanced » Developer » USB debugging

Open a CMD window in the “adb” folder

a) Press the “Windows botton”

b) Type "cmd"

c) Click "Command Prompt"

d) Type "cd /d <path to directory with adb.exe file – i.e. c:\myfolder\adb>"

Start the phone in “fastboot” mode:

a) Turn the phone off

b) Press the "volume-up" button and connect the USB cable at the same time

Install the USB drivers

(you will find the files in the attachment)

Run "fastboot flash boot boot.img" (watch the file name)

Disconnect the cable and turn the phone on

Download "Root Checker" from the Play Store and open it

Tap "Check Root"

A popup will appear to grand root access to the Root Checker app

If a message stating "ROOTED" appears your phone is succesfully rooted

That's it!
[Sony Xperia 10 II Guides, News, & Discussion] metallic.steel:
Will these steps work in Sony Xperia 1 V on android 13?
[Sony Xperia 10 II Guides, News, & Discussion] wootje_:
Depends on the development of Magisk. Last time I checked, rooting Android 13 was not possible. But you can try using the latest version of Magisk.

https://github.com/topjohnwu/Magisk/releases
[Touch Pro, Fuze General] allhalf425:
As of late, my new Fuze (the 3rd one, I exchanged the other ones out because they got kinda scratched up) has been showing poor performance. And then today, the touch screen just stopped working. It still registers the touch, but it's like no matter where I touch it can only go to one of the two soft keys. Has anyone else been having this problem?

I'm going in to switch it out again, but I'm really not sure if I want to keep using the Fuze...overall, it's slow, buggy, and the GPS is trash. I love the phone, but it's just not working.
[Touch Pro, Fuze General] ecltech:
Are you using the stock ROM or did you use one of the cooked ROMs? I have a Fuze (upgraded from a Tilt) and everything works fine on mine. I read that a lot of people are having issues with the GPS. I did initially --- I could not get any GPS connectivity. I ran HTP GPS Tool and everything worked fine after that. Even after I flash another ROM it works fine. I use TomTom and GoogleMaps regularly and even GoogleMaps can get a GPS lock within 1 minute.

You may want to check the settings for the TouchFlo. Download DiamondTweak and Advanced Config 3.3. They have settings to improve the sensitivity of the touch screen... maybe you need this or at least give it a try.

As for slow, I think this has to do more with the ROM. Since I got my Fuze, the first thing I did was flash one of the cooked ROMs (of course, after HardSPL :)).

Good luck.
[Touch Pro, Fuze General] allhalf425:
I'm using the stock ROM, I'm kind of scared to flash a new one. I did all the performance tweaks and it made a pretty big difference, but it's still kind of slow. I can live with it though. The GPS works occasionally, but it isn't nearly as strong as other phones I've used/seen. And the touchscreen problem has nothing to do with the sensitivity, I'm fairly positive it's broken. Like, when I touch somewhere on the screen, it registers the touch as far to the left as possible (ie. I'm trying to close a program or open the task manager and it registers the touch as pressing the Start button). It may have something to do with the fact that I cleaned the screen with a monitor wipe, although I would assume that that shouldn't affect anything. It's just such a coincidence though; I literally used the monitor wipe like 2-3 minutes before it broke or screwed up or whatever. And it's not a software issue. I hard-reset it and it took a good 20 minutes to get past the screen alignment (I think it just gave up on me and went to the next screen). I'm just going to exchange it out for a new one I guess, although I'd really prefer an Xperia X1 at this point (or any point I guess...I just don't want to spend 700 dollars on it)
[Touch Pro, Fuze General] naa77:
Dude, I hear ya..... I'm getting the same issue, it registers touch etc, you press your home key it vibrates you softrest with button on back and it starts up and I know its booted WM as I can hear the windows startup sound, It's not the first time this has happened to me, one other time after flashing a cooked rom, It did the same thing then I managed to blindly navigate the device into the bootloader then reflash the device, the screen suddenly decided to come back on at the "tap to setup device" stage, you know with the screen alignment...., then I did like 2 hard resets, cause at the time I thought that this was something to do with it, then everything has been working good as gold up untill last night when I flashed the cooks latest version, it worked for a lil bit but in my messing around with the device, the screen switched off then stayed off, I've been trying the same process that I tryed before, but it's not working:eek::eek:, maybe I should of did the 2 hard resets straight away rather then fart arsing around loading cabs etc...?, not sure, as I'm at a loss with this one... maybe it was just on it's way out, upto HTC heaven and there's nothing I can do about it ?, God, I hope not !!, MY next thing I'm going to try is load a stock HTC ROM onto the storage card, and maybe that will work...hmmm??, anyway...do you know anymore or are you at a loss as well ?... Oh BTW, I'm using a Touch HD, with a manilla 2.5, 6.5 ROM, from one of the popular chefs, (I'm not gonna publish the chefs name) as I think it's not really his fault....everyone else seems to be OK, so must be something else, I've wondered sometimes about the amount of writes available on some types of memorys having something to do with it, but it can't be that..?, something with the screen, I've noticed it happens when the battery is running real hot as well !!, anyway if ya find out something, I'm keen to hear as well, as no one seems to be answering my post about it.....
[Samsung Galaxy Z Fold 2 Questions & Answers] !GreddyZC76:
the infamous Pink line, appeared on my Z Fold 2 outer Screen, less than 2 years old, and it happened 2 to 3 weeks, after updating to One UI 5... 😡🤬

any other Z Fold 2 users have same unfortunate encounters ?

now, thinking if roll back the firmware will remove that pink line...
[Samsung Galaxy Z Fold 2 Questions & Answers] pvillasuso:
now it's a hardware issue , rolling back won't fix it , sorry !
[Samsung Galaxy Z Fold 2 Questions & Answers] pnsdhrn:
From today onwards my Fold 2 also shows a pink vertical line on the outer screen.Will replacing the digitizer solve the issue? What will be the cost for this?I am in India.
[Samsung Galaxy Z Fold 2 Questions & Answers] _GRIZZLY_:
I think that yes but tell to service and ask him for costs.

Admittedly it's not update problem but it's known from one year or more

Fold 2 vertical pink line

A few days after the update, the vertical pink line appear on front screen, even during reboot it phone off while charging - just like other Samsung phone update. Please kindly come out with the fix or update.

r1.community.samsung.com
[Samsung Galaxy Z Fold 2 Questions & Answers] _GRIZZLY_:
Can you tell me about overall impressions about one ui 5.0 in fold 2?
[Samsung Galaxy Z Fold 2 Questions & Answers] !GreddyZC76:
imho, nothing much had changed, if possible , dont update it. 😊
[Samsung Galaxy Z Fold 2 Questions & Answers] _GRIZZLY_:
Thanks for reply. I still stay with A11 and Ui 3.1.1 and consider update to A13 to maybe little fresher my phone but after you answer, few themes about green/pink ( even from 2022 year) lines after any update probably I stay with old android and enjoy good working phone.

Admittedly few months ago I remember that my girlfriend S20 after any update and few days her S20 screen got dead green screen. Unfortunetly warranty end half year after this case.

Maybe it's only case but after experience samsung's phone from S2 series (S20 girfriend) and users opinion about aware aging products with software help I have strong opinion about similar situation like even your.
[Samsung Galaxy Z Fold 2 Questions & Answers] pnsdhrn:
The overall function of 5.0 UI is overwhelming.Buttersmooth home functions.
[Samsung Galaxy Z Fold 2 Questions & Answers] _GRIZZLY_:
Thanks for answer. I update my Fold 2 by OTA from A11 thru A12 to A13 and I can confirm for better smoot, especially in message app where a had lag 1-2 sek (A11) and now lag is a lot of smaller) A13. OS looking very similar to newer FOlds like F3 and F4.

After few days I am pleased, don't have any problems. Everything running good, no restarts or other issues :)
[Samsung Galaxy Z Fold 2 Questions & Answers] avirendra:
I got green vertical line after march 23 update. The only solution seems to be screen replacement. Service center quoted ₹11,150.

External vendor quoted ₹10250
[Samsung Galaxy Z Fold 2 Questions & Answers] avirendra:
What did you do? Did you replace screen? At what cost?
[Samsung Galaxy Z Fold 2 Questions & Answers] pnsdhrn:
I went to Samsung Service Center and got the screen changed.The cost is Rs.12000/-
[Samsung Galaxy Z Fold 2 Questions & Answers] sumii0358:
Hello! Having same pink line issue and phone is under warranty but they're saying it's not covered under warranty
[Samsung Galaxy A53 5G] duttondj:
I really busted up my phone this weekend. The screen is dead and I'm sure the digitizer is as well. I already got a new phone but I would really like to be able to recover my Signal messages. I thought I was backing them up to the SD card but they are actually on the internal storage. A couple questions:

1. Is there any way to be able to control the phone while also using an external display? I tried a couple different Type C dongles that have HDMI and a USB port but neither did anything and even my replacement phone didn't do anything in response. I've got Teamviewer installed that could possibly let me in (don't know if it's set up) but I don't know how to get past my decryption password prompt.

2. Is there any way to make a backup of the filesystem? I realize it would be encrypted but I do know my password if it's possible to somehow use that with some software. I've always had TWRP installed on my past phones so it was trivial to make nandroid backups. This phone is the US version and I had no ability to unlock the bootloader so it's completely stock.
[Samsung Galaxy A53 5G] blackhawk:
The encryption keys are unique and tied to that current OS load. A factory reset destroys those keys. The password isn't the encryption key...

Unless you can access it remotely this is your only other option.
[Samsung Galaxy A53 5G] duttondj:
That's disappointing. I'll got an identical phone now so I may try just following the same finger presses side by side to see if I can get it unlocked and get some sort of remote viewer installed. Another option I thought of is just to replace the screen but that's a bunch of work and would certainly be my last resort. The frame was a little bent but new screens come with a frame so as long as nothing further is damaged, it might work.
[Samsung Galaxy A53 5G] blackhawk:
Using the new phone as a template may work.

Realize the mobo may have been damaged as well.

Use a good case to protect your new phone.

I use the Zizo Bolt for my N10+, it would've been destroyed long ago without it. Provides excellent protection in 3-4 foot drops onto concrete. Zero damage after 3 years.

Backing up all critical data is the only way to prevent this from happening again, eventually.

Try to find apps that support import/export file backup like Poweramp and ColorNote. Samsung contacts support it too.
[Samsung Galaxy A53 5G] duttondj:
I got a new display and tried to migrate all the pieces over. One row of the contacts of the FPC connector on the motherboard were broken off along with some minor damage to the other FPC connectors. I can buy a new flex cable and daughtercard. The phone basically got bent so the FPC connectors and bluetooth cable were pulled sideways. Getting this thing working again would require a new daughtercard, a new flex cable, a new bluetooth cable, and a new FPC connector for the motherboard (yikes) which are all available for little cost. I've actually got the skills and gear to do the connector replacement but just not the time. Maybe I'll do it someday when I've got some freetime at work.

The actual screen replacement was surprisingly easy with a heatgun, a single spudger, and a #00 phillips. I found the FPC connectors much easier to use than the old days when everything used those ribbon cables that would slide into connectors and be held in with plastic clips, they were super easy to damage.

Interestingly, the replacement screen I got has a slightly thicker bezel. It looked legitimate but has a slightly different ending number in the Samsung part number.
[Samsung Galaxy A53 5G] blackhawk:
Sounds like a mess. Probably more hidden damage.
[Google Pixel 2 XL Questions & Answers] neilth:
While trying to install an OS on my Pixel 2 XL using either LOS or TWRP recoveries, my PC and the 2 XL hangs after the adb sideload OSinstallpackage.zip command. I have tried installing various versions of LOS and even tried installing the last Google OTA package for this phone. TWRP just says tha the package is being installed indefinitely, LOS recovery says verifying installation file. The PC just has a blinking cursor under the sideload command line, no install progress is displayed. Up until recently, this problem didn’t exist and I don’t know what changed. Does anyone out there have any idea how to resolve this problem?
[Google Pixel 2 XL Questions & Answers] V0latyle:
How long have you waited? Large files can take a while to process.
[Google Pixel 2 XL Questions & Answers] neilth:
I have waited 15-20 minutes. Typically, on the PC, you start to see the percentage of installation almost immediately when everything is working correctly.
[Google Pixel 2 XL Questions & Answers] V0latyle:
True.

It sounds like the issue is with TWRP. If you boot into OEM recovery, are you able to sideload the OEM OTA?

Have you tried different USB cables?

Are your ADB Platform Tools up to date? Using tools like Minimal ADB is not recommended; make sure you're using the original SDK Platform Tools from here.
[Google Pixel 2 XL Questions & Answers] neilth:
I am getting the same issue whether I use TWRP or LOS recovery. My ADB Platform Tools are the latest version. How do I get back to OEM recovery once I have used non OEM operating systems on the phone? And yes, I have tried several USB cables.
[Google Pixel 2 XL Questions & Answers] V0latyle:
Hmm. Let's still try the OEM recovery.

Good.

Just reflash the stock boot image from the factory image, then use the key combo to force a boot into recovery

Well...there's only so many possibilities.
[Google Pixel 2 XL Questions & Answers] runekock:
Does your USB connection transfer data fine in other cases? Maybe you just need to clean the port.

You could try connecting a USB drive directly to the phone and flash from that.

Or flash a file that's already on the phone - but that requires that TWRP can decrypt your data, and ISTR that TWRP hasn't been updated to the newest encryption scheme.
[Google Pixel 2 XL Questions & Answers] neilth:
I downloaded the last released official factory OTA zip of the operating system for the Pixel 2 XL from Google. How do I proceed to get the stock boot image and install it on my phone?
[Google Pixel 2 XL Questions & Answers] neilth:
Everything was fine with this phone running LOS 19.1. Last week I attempted to upgrade to the unofficial release of LOS 20 using the published LOS upgrade instructions and now I can’t even get LOS 19.1 to install again for some reason after having wiped the phone’s partitions.
[Google Pixel 2 XL Questions & Answers] V0latyle:
Factory images and OTA images are not the same.

Factory images for Taimen

Extract, then extract the image-device-builnumber.zip inside it. You'll find the boot.img in this archive.
[Google Pixel 2 XL Questions & Answers] neilth:
Thanks, I’ll have to see if I can try this tomorrow or Friday.
[Google Pixel 2 XL Questions & Answers] runekock:
Yes, good advice from V0latyle. Flashing factory usually fixes things.
[Google Pixel 2 XL Questions & Answers] neilth:
I downloaded and extracted the last (12/20) factory image from Google. I have the boot.img file you mentioned, how do I install it on my phone in the correct place?
[Google Pixel 2 XL Questions & Answers] runekock:
Just flash everything as Google instructed on the page (flash-all or flash tool). Note that this will delete the data on your phone.
[Google Pixel 2 XL Questions & Answers] neilth:
There was nothing on my phone to delete! I ran the flash-all.bat file which successfully installed the Dec. 2020 Android 11 OS, but did not resolve the issue with the adb sideload command hanging when attempting to install a non Google OS such as LOS.
[Google Pixel 2 XL Questions & Answers] runekock:
Well, at least you've eliminated some possibilities. To my mind, this means that:

- the USB connection is working

- fastboot works

- hardware problem unlikely

What remains:

- wrong USB driver on the PC - I believe it uses a different driver in recovery - check device manager with the phone connected in recovery

- wrong adb version on your PC

- defective recovery (but you tried different ones, I think)

- you doing sideload wrong - post screens from phone and PC
[Google Pixel 2 XL Questions & Answers] neilth:
Here are your requested screenshoots of the computer’s command prompt window where I run fast boot and adb commands, the phone screen showing the LOS recovery hung at "verifying update package" and a third shot of device manager showing the presence of the Android ADB Recovery Interface while my phone is connected to my computer via USB and in Recovery. I hope that you see something that I am missing here, I don’t see anything that stands out as a problem. Thanks for your assistance.

View attachment 5819921 View attachment 5819923 View attachment 5819925
[Google Pixel 2 XL Questions & Answers] runekock:
LeMobile is not the correct driver - for some reason Microsoft occasionally suggests it, but it's for some obscure phone. Try the Pixel driver package from Google.