yashsingh1/xdaforums huggingface dataset:
[Realme Narzo 30 5G (AKA  Realme 8 5G)] Dhasx:
I'm experiencing the same problem, I didn't change the format all option when using SPFT and my phone got hardbricked, no access to fastboot or recovery, tried flashing firmwares with spft but no luck. Then I found a newer firmware with realme ui 3 and flashed it but still the phone wouldn't turn on. After that, everytime I try to use mtk client I get "31mCouldn't get device configuration" error and if I use spft it just never begins downloading.

Hope they can revive your phone.
[Realme Narzo 30 5G (AKA  Realme 8 5G)] DeviceMesser:
They actually revived the phone! Tbh, I had zero hopes for it, but thanks to them, I'm typing this on my phone. But, the rear camera isn't working for some reason. However, the phone is working as good as new .
[Realme Narzo 30 5G (AKA  Realme 8 5G)] Wojtek512:
do you have any solution for this because i have the same problem??
[Realme Narzo 30 5G (AKA  Realme 8 5G)] Dhasx:
Congrats!! What firmware did they install, same region ?, is the bootloader locked ?, does dual sim work normally ?. I'm sorry for the amount of questions but I'm really curious since only one technician was willing to try the chip off method but he looked sketchy.

Sadly no, I left my phone at a technician who said he would try to revive the phone using "special hardware", but I dont feel optimistic.
[Xiaomi 13 Pro] droidkoder:
Can anyone confirm if we would be able to easily root Xiaomi 13 pro?

I want to buy the phone only if it is possible to root this phone.
[Xiaomi 13 Pro] NOSS8:
Yep,possible but only with V14.0.4.0.TMBCNXM/V14.0.8.0.TMBCNXM ,for the moment
[Xiaomi 13 Pro] VincentThacker:
Hi, do you have a tutorial on how to root this device? I have tried using Magisk but it does not work at all. The patched boot.img flashes successfully but nothing happens after reboot. Nothing is installed at all and the system is exactly the same as before. My bootloader is unlocked. Booting directly using the patched boot.img does nothing as well. It is as if nothing has been flashed at all.

Edit: I found a solution. You have to use init_boot.img instead of boot.img.
[Xiaomi 13 Pro] NOSS8:
And is Magisk usable, zygisk, modules etc...?
[Xiaomi 13 Pro] VincentThacker:
Yeah, I've managed to get it working on 14.0.10.0.TMBCNXM. The only module I've tested is Universal SafetyNet Fix which is working. Google Play showing certified. Updating can be done without a PC as well. I first installed on 14.0.8.0, then installed 14.0.10.0 from the device updater itself. Before rebooting, simply go to Magisk and select the option to install to inactive slot. Reboot and you have Magisk working on the new version.
[Xiaomi 13 Pro] darrenlimch:
Bro can write a guide how to root? I try follow this method, but failed. https://xdaforums.com/t/root-poco-m3-pro-5g-yourself-and-optionnal-debloat-privacy.4337693/

Cuz i have a m3 pro. I thinking should be same. But seems like its not
[Xiaomi 13 Pro] NOSS8:
Nope,this not the same method.

https://xdaforums.com/t/root-gained.4290689/
[Xiaomi 13 Pro] darrenlimch:
Cuz you mention here use init_boot.img, i try use magisk patch the init_boot.img and flash it via adb, but then bootloop into fastboot. Mind write a tutorial for us? As i believe you are the first to root succesfully. Thanks in advance bro.
[Xiaomi 13 Pro] darrenlimch:
Misunderstood bro. I have a mi 13pro as well. China version. Need to root it. Im just saying that i have another poco m3 pro. I though they use same method
[Xiaomi 13 Pro] NOSS8:
Understood,You have to use init_boot.img instead of boot.img.

Common tutorial

1. Find or redownload the TGZ file for your current ROM or other rom.

2. Browse inside the zip file and find boot.img under the images folder

3. Copy this file to a temporary location in your PC first, and then transfer it to your phone

4. Install the desired version of Magisk app (V23?)

5. Run the app and choose Install under Magisk

6. Choose Select and Patch a File, then select the boot.img that was transferred earlier

7. A process will run and create a new .img file in the same folder where the original one was

8. Transfer the new file to your PC in the same directory where fastboot.exe is located

9. Open a command prompt window in that same directory

10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.

11. Run the command fastboot flash boot_ab magiskXXXX.img

Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
[Xiaomi 13 Pro] darrenlimch:
Tried this method. But like VincentThacker mentioned at first. After flash that modded.img, nothing was change. So might need his help already. No idea which init_boot.img is mentioning.
[Xiaomi 13 Pro] NOSS8:
I guess it is in the Fastboot rom or a command and root for what no rom or twrp currently available.

If it is to delete apps there are many tools or with ADB commands.
[Xiaomi 13 Pro] darrenlimch:
I need android auto to work, this china version doesnt have android auto :(

So yea, need use magisk to install that android auto module.
[Xiaomi 13 Pro] VincentThacker:
This is the guide. It's basically the standard method but you patch init_boot.img instead of boot.img. Both can be extracted from the fastboot firmware.
[Xiaomi 13 Pro] NOSS8:
So to summarize, extracting the boot.img from the Fastboot rom, V14.0.10.0.TMBCNXM/V14.0.22.12.26.DEV/V14.0.8.0.TMBCNXM/V14.0.4.0.TMBCNXM roms doesn't work?
[Xiaomi 13 Pro] VincentThacker:
Yeah, as I mentioned above, boot.img does not work; you have to use init_boot.img which has a size of exactly 8 MiB. If it does not have this size, you've got the wrong file. It probably has to do with the boot method used by the device as described here. The flashing command must also use init_boot_ab instead of boot_ab.
[Xiaomi 13 Pro] stathis95194:
Guys i was in the same boat.

I have successfully root Mi 13 Pro, but i have another issue if anyone can help. Mi Wallet keeps changing as default payment method even though i have GPay selected.
[Xiaomi 13 Pro] Jaberbenet:
Is it a must to include the "_ab" part in the command?
[Xiaomi 13 Pro] aygul12345:
Can I use magisk hide and passing safetynet with this device? Gonna buy this phone in Europe.

Wanna be sure that the module magisk hide props and universal safetynet-fix passes safetynet.

Can anyone confirm it for me?
[Xiaomi 13 Pro] wacayalu:
Yeah everything works with EU beta + DFe neo + magisk 25.2.. my phone passes safetynet without safetyfix module and google certified
[Xiaomi 13 Pro] panlaljpr:
@NOSS8 i just flashed the stock ROM which came pre-installed with my phone and after setting up the device, the play protect certification is saying that the device is not certified.

I have copied the device id and paste it on https://www.google.com/android/uncertified/?pli=1 but still nothing happened yet.

kindly help me with this.
[Xiaomi 13 Pro] NOSS8:
What rom?

Did you use Miflash and flash a Global or EEA rom?

If the bootloader is unlocked the device will not be certified.
[Xiaomi 13 Pro] ripelag:
Hello, root for the Mi13 Pro Global Version with rom xiaomi.eu weekly you can do?
[Xiaomi 13 Pro] NOSS8:
Yep, just extract the boot img from the Weekly and use this method.
[Xiaomi 13 Pro] ripelag:
Every time I update the xiaomi.eu weekly should I root or stay?
[Xiaomi 13 Pro] ripelag:
error
[Xiaomi 13 Pro] NOSS8:
With each update the root is removed.

Before the update remove the root with Magisk and disable the modules.
[Xiaomi 13 Pro] ripelag:
Since I update from fastboot with the windows_fastboot_update_rom.bat command, I can enter "init_boot.img" patched with magisk and renamed "init_boot.img" in images and then give the fastboot command?
[Xiaomi 13 Pro] NOSS8:
Only works if the init boot img of the update is the same.
[Xiaomi 13 Pro] ripelag:
So I can’t patch it and then put it in place of the original, to make fewer steps every time I update?
[Xiaomi 13 Pro] NOSS8:
Yep, I misunderstood, just check that they are the same size.
[Xiaomi 13 Pro] ripelag:
Do I still have to remove the root with Magisk and disable the modules or do I just give the fastboot command for the update after replacing the file with the one patched and renamed?
[Xiaomi 13 Pro] NOSS8:
At least disable the modules, for the boot it will be overwritten.

I haven't rooted my devices for a long time but I used this method to update the TWRP (recovery) when it was supplied with the rom (Xiaomi Eu rom).
[Xiaomi 13 Pro] ripelag:
Can I also enter "init_boot.img" patched and renamed directly in the fastboot command of the first installation? To get root now by simplifying the steps? Next I will insert it in the fastboot command for the update after disabling the modules in Magisk.
[Xiaomi 13 Pro] NOSS8:
for a first installation, root after installation.
[Xiaomi 13 Pro] JudgeJustice:
Hello I will be buying this Phone (global version) soon but Need to Know if there is a Updated Guide on how to Root the phone.
[Xiaomi 13 Pro] NOSS8:
Just flash the magisk.zip (magisk.apk renamed to zip) with the TWRP.
[Introductions] makkadiamonD:
I am back to try and get help on a Bricked Peloton Tablet Model PLTN-TTR01. the tablet is in Emergency Download mode. it does not turn on.

however it does output on Usb3 and shows in device manger as Qualcomm HS-USB QDLoader 9008 on com3.

I installed Qualcomm HS-USB QDLoader 9008 ver 2.1.2.2 from this site https://www.thecustomdroid.com/qualcomm-hs-usb-qdloader-9008-drivers/

QPST can see the tablet see attached. Can you experts advice me on the next steps. have searched high and low but not much info on the Peloton Tablet.

Regards View attachment 5795575View attachment 5795565
[Introductions] orb3000:
An HTC old timer!

Welcome to XDA
[Introductions] makkadiamonD:
can anyone give pointers on this.

I "believe" the tablet is in emergency download mode (EDL) https://en.wikipedia.org/wiki/Qualcomm_EDL_mode
[OnePlus 9 Pro] andrew_yousry:
I need help, My OnePlus 9 Pro.

So far nothing works for me. first got Sahara Communication error, then when unchecked sha256 check & checked use lite firehose, I got error device not match image. Tried to download the Global tool instead of the EU, it shows error unsupported target EU

N.B.: I can't access Bootloader, Recovery, Bootd
[OnePlus 9 Pro] AndyC76:
Can you answer the below, it will help:

Hardware model of your phone, if you're unsure it will be on the box the phone came in, or failing that it will be on the back of the phone above the charger slot.

Which ROM did you have installed on your phone.
[OnePlus 9 Pro] TheGhost1951:
Wrong version of the MSM tool. Your phone is a EU variant, that means to use the EU MSM tool.
[OnePlus 9 Pro] andrew_yousry:
EU Variant gives error device not match image, you can see the screenshot
[OnePlus 9 Pro] andrew_yousry:
Don't know the model, I suppose it's chinese version. box lost already, sticker on the back of the phone removed.

Now I'm downloading the Indian recovery tool will try it as a last thing to try.

There is no MSM tool for the chinese version I guess.

I was using last Android 13 F17 EU version
[OnePlus 9 Pro] AndyC76:
To find your hardware model, turn your phone so it is screen down.

Look at the bottom of the phone, just above the charging slot, you'll see the hw model in small writing
[OnePlus 9 Pro] andrew_yousry:
did you see anything written?

Nothing written on the back of the phone, I guess it's LE2120 the chinese variant
[OnePlus 9 Pro] kjslabber:
Indian MSM will cure a lot of evils, bypasses alot of checks. Maybe be necessary to check the firehouse lite box also. If it works then you can try EU version. It worked on my global version.
[OnePlus 9 Pro] TheGhost1951:
What I see in the first image under "status of communication" "unsupported target EU" means that the target, the phone is EU, and the MSM tool is for some other variant. I would advise using the Indian MSM tool as it will permanently change your phone to the IN variant. Try using the Oxygen updater app to install what firmware you want!
[OnePlus 9 Pro] JonasHS:
install the orginal driver and msm version, and it should work.

your phone work fine
[OnePlus 9 Pro] kjslabber:
It didn't change mine. That was the only way I could even get MSN to work period. I didn't even have bootloader, recovery ect. Just blank black screen.
[OnePlus 9 Pro] andrew_yousry:
you're right. Indian MSM worked like a charm.

Greetings to the people of India for such a good solution
[OnePlus 9 Pro] TheSayaMan:
I would take Global local upgrades to a13. I wouldn't stay on India. Keep in mind, since you used the India MSM, your device ID was changed so you can't use the Global or TMobile MSM anymore depending on what your original phone model was. Your device ID was Europe, that's why you got the unsupported device EU error before but since you used India MSM, it may have been changed to IN now.
[OnePlus 9 Pro] kjslabber:
I ran global MSM immediately after the India MSM and all went smoothly. Back to global then proceeded to update to A13.
[OnePlus 9 Pro] TheSayaMan:
Ok good, then your target is GLO otherwise it wouldn't have worked.
[OnePlus 9 Pro] way2aware:
AND... if worst comes to worse then don't give up hope entirely, lol (meaning unresponsive hard brick, unrecognized in any way by windows). I've had mine apart to change a cracked LCD/ digitizer and this phone does have the two test pads which when shorted together and power on will put your phone in Qualcomm EDL mode
[OnePlus 9 Pro] Jack Droid:
Hi,

hope you solved your matter and your phone has been back with us....!

Generally speaking, it is always a way to solve the soft-brick....This is the main reason I love to so much Android devices...( in Samsung devices, you can always use ODIN for restore to stock, for Oneplus you can always use MSM tool and that's it...)

I have had more than 1000 soft-brick and always relive my phone by using MSM tool...

Different things if you have an hard-brick.....In that case you have to pray....

But I hope this is not the case.....

If you have not solved and you want any help, feel free to reply so that I'll try to help you
[OnePlus 9 Pro] ChrisFeiveel84:
Op9/9p (not china )

you can not realy hardbrick

Than you can this self unbrick with msm tool
[OnePlus 9 Pro] Jack Droid:
Yes, it is
[Nvidia Shield TV & Shield TV Pro (2019) Guides, Ne] jenneh:
Hello Friends!

Today I wanted to re-write a guide for installing Lineage OS on the 2019 Pro.

This guide will be more to the point and have only the needed tools.

The SOURCE for the Lineage zip shared in the download section below.

Spoiler content hidden.

The ORIGINAL Guide if you want to see how much harder I made things not knowing what to do :)

This may be useful to locking the bootloader while lineage is installed!
[Nvidia Shield TV & Shield TV Pro (2019) Guides, Ne] jenneh:
The next two comments are notes about porting to different OSs and downloading the original source code. They are not full guides as I have not personally succeeding in fully building anything myself yet, just initiating repos and data gathering but will update when we get there..

Spoiler content hidden.
[Nvidia Shield TV & Shield TV Pro (2019) Guides, Ne] AP12345:
Hi I am planning to get a Nvidia shield pro 2019. I want to install lineageos and root it but would like to have all HDR & 4k codecs still supported and use the AI upscaling feature. Since you have experience with the device, could you tell me if this is all possible in one and if not what alternatives you know?
[Nvidia Shield TV & Shield TV Pro (2019) Guides, Ne] jenneh:
Sorry.. I do not know the answer to this, I am just learning these things myself and writing notes here publicly for anyone to pickup but here is the actual main thread for lineage os on the shield and the dev is very active https://xdaforums.com/t/rom-official-lineageos-for-the-shield-android-tv.3632652/
[Nvidia Shield TV & Shield TV Pro (2019) Guides, Ne] pggggggg:
Thank you. This is a great roundup. I have taken it upon myself to have a go at converting my 2017 Shield into a headless Linux machine. It has proven really difficult. Sadly the Ubuntu 18 port on the forum did not work for me. So, I'm gonna take on the stupid task of trying to build one myself. I think I'm way ahead of myself. Halium/Ubuntu Touch seem like really interesting projects. Their repos are vast and the documentation is good (but possibly outdated by 4 versions). I have already run into many problems lol

In the meantime, I will try rooting it and getting the latest lineage on it. Termux has also been really interesting although difficult to navigate the limitations when not rooted.
[Redmi Note 11 (spes/spesn)] lenny73:
Hello everybody.

I'm sorry if this was asked many times. I have a Redmi Note 11 (spes) model 2201117TL running a Global MIUI ROM on Android 11. Just like many users, I hate Google Dialer and Messages, especially after using MIUI 9 with MI Dialer (with call recording) and Messages for almost 5 years on a Redmi 4X. So I want to install the Indonesian ROM, the only for my device with those apps. I downloaded the ROM "spesn_id_global_images_V13.0.7.0.RGKIDXM_20220822.0000.00_11.0_global". I don't like the Dynamic Color and some apps I use fail with Android 12 so I downloaded the last one released with Android 11. And there's no ROM without NFC for this device. I already unlocked my bootloader but I'll have to relock it in order to get Play Protect certification. The Xiaomi.eu ROM looks nice but don't want to mess around with custom recoveries and all that, I'd rather stay with official software.

So my questions:

- Is is safe to use MiFlash to flash the Indonesian version on this device?? I've seen many videos were they do it on different devices. I want to know experiences on this one.

- Is there a problem if I install a ROM with NFC on a device without NFC?

- When MIUI starts I got a message that I have to activate the device, logging into my MI account because the device it's associated with it. I guess that's because of the SIM card in it. There's no problem with that flashing the Global ROM but should I take it off now for the Indonesian??

- Is there any serious bugs on the Indonesian ROM?? I want to flash a version with Android 11 but still I'd like to know if anyone had any serious problem.

Thanks.
[Redmi Note 11 (spes/spesn)] lenny73:
I did it and the flashing went fine. However, even though I locked the bootloader I lost the Play Protect Certification. I fixed it quickly following this tutorial: https://xiaomiui.net/how-to-fix-play-protect-certification-error-5405/

Now I logged in into my Google account. I'll continue installing my apps and testing the ROM. I'll keep you guys posted.
[Redmi Note 11 (spes/spesn)] lenny73:
Here's an update.

Some cons:

- Google didn't restore some of my apps's data after installing them, it worked before. I had to to it manually.

- I had trouble logging into Google from inside other apps, security from Google said I did it too many times. I just tried again later.

- I noticed the back of the cellphone getting a little warm for a while, it didn't happen with the Global ROM. The Battery section said the temperature was "Medium".

- There's some flickering on the keyboard in some apps like Color Note and WhatsApp. It's somehow related to the fact that this ROM has Mint Keyboard installed as a default (nobody ever mentioned that). If I select that keyboard, the flickering it's gone, I'd use it if I could add other languages besides English (I don't speak any of the other indian gibberish it supports). But if I select Gboard, no matter if I disable Mint Keyboard or not, the flickering it's sometimes there.

- The worst: I have the feeling that this ROM drains the battery faster than the Global ROM. I have no way to know for sure, it's just a perception. I guees it could be related to the fact that I use a Xiaomi Backup to restore my apps and settings, that backup was made on a Global ROM, that process messed some things up. Or maybe the fact I couldn't connect to Google from the beggining. I'll try later a factory reset and do everything manually again. Last thing to try: update MIUI to Android 12, it worked pretty bad on a Global ROM, maybe it's better on this one.

Some pros:

- MIUI Dialer and call recording work like a charm. The quality of the recording beats the sh*t out of the one of any third app (I tried several on the Global ROM)

- MI Calendar works perfectly, that's another simple and useful Xiaomi app missing from the Global ROM (Google Calendar is not that bad though).

- Bluetooth range seems improved: I can walk away from my cellphone and unlike before, I don't start losing signal on my earbuds right away. This is very useful to me, I love listening to music while I do things but I can't always bring the phone with me.

This is all for now.
[Redmi Note 11 (spes/spesn)] sameer lyf:
Thank you keep updated this thread.
[Google Pixel 6] libru97:
I've had my Pixel 6 for the better part of a year. To my memory, it hasn't really had any significant issues. Instead, I've found it far and away the most enjoyable phone I've ever owned.

More recently there have been times where I tap something and there's no response until I, like, go back and then try again. But that has only happened a few times.

I really like the camera, Material You, the feel and look of the device... I keep mine in a case that is very comfortable for me. I don't have a screen protector because I didn't want to pay for the installation and doing it myself is always an anxiety-inducing, perfectionists' nightmare. So, unfortunately, I have a small scratch on the screen from when I stupidly put my keys in my pocket with my phone.

Other than that, it's been a largely pain-free, and surprisingly positive experience.

How about you guys?
[Google Pixel 6] Jaitsu:
Honestly, as far as the phone itself goes - yeah, it's been problem-free, good performance, good battery, good signal, good... everything. The only thing that's bugging me is the fact that there's still no TWRP for it. I want to play around with custom ROMs and whatnot, but that's a big pain with no way to do quick and easy backups. That's not the phone's fault, though.
[Google Pixel 6] nutzfreelance:
its been ok, but nothing special and honestly a disappointment for a flagship device.
[Samsung Galaxy Note 9 Questions & Answers] xtc218:
Hello everyone, i have a Galaxy Note 9 N960U from Verizon, the device is unlocked for any carrier but i want to flash any N960u1 Firmware.

I was try with Odin Patched and always give me the same error "Could not open the COM PORT", I try with many USB Cables and two computers.

Anyone can help me?
[Samsung Galaxy Note 9 Questions & Answers] xtc218:
I finally fi my issue.

Thanks
[Samsung Galaxy S20 FE Questions & Answers] yuterra:
I want to change my csc on korean version of the phone, at the moment I have skc, I would like to change it to koo, who can help me?
[Android Stick & Console RockChip based Computers] fastvan67:
Hello everyone. I recently purchased a Q96 Max with Android 11.1, 8GB ram and 128GB ROM.

I knew the $27 price tag was a clue to its trust worthiness. Got it in and hooked it up. Looked good. However, in less than 2 min of operating, the system froze up. Had to pull the power. After 3 attempts at just trying any app only to be met with a freeze, I reached out to the seller. Seller says I need to mail it back to China at my expense and not be refunded for the shipping. This would be a NOOO!

Currently have a claim opened with PayPay.

Anyway.. I have had luck replacing the firmware on other boxes. So I am looking for one. Anyone know where I can find a replacement firmware? Android 9-11 should be fine.

Thank You
[Android Stick & Console RockChip based Computers] OrsoNerOne:
Are you enter in Recovery Mode?
[Android Stick & Console RockChip based Computers] WFAraujo:
Hello,

Did you get some update on this issue?
[Android Stick & Console RockChip based Computers] fastvan67:
Well, after a LOT of research, I found that these boxes actually NEVER manufactured with 8-16gb ram and 128-256GB ROM.

What they actually make is 1-2gb ram and 4, 8 and 16gb ROM.

I found the amlogic drivers and amlogic usb burning tools.

The logic board in line is model PS905V100A1-4-101017

Processor is Amlogic S905L-B