yashsingh1/xdaforums huggingface dataset:
[OnePlus 10T 5G] Bhavishya_Yadav:
I also have a hardbricked phone where did you get it repaired ?
[OnePlus 10T 5G] Wilzzone:
In the website NCunlock .com you pay the fee and the guy with TeamViewer do the remote repair
[OnePlus 10T 5G] Revontheus:
There are ways to do it without TWRP, but the easiest way is flashing the Magisk zip in TWRP (you can rename the APK file from Magisk.apk to Magisk.zip). Once you reboot you will see the Magisk app.
[OnePlus 10T 5G] Wilzzone:
Ok, so instead of doing it in CMD via commands I should install TWRP? Any no dangerous guide?
[OnePlus 10T 5G] TheNewHEROBRINE:
But is TWRP available for the OnePlus 10T?
[OnePlus 10T 5G] Wilzzone:
For what I have been searching... No.

The only way is via CMD
[OnePlus 10T 5G] Revontheus:
If there is no TWRP available for your device. Install Magisk your phone and patch your phone's boot.img. You then proceed to install that via fastboot with the command:

fastboot flash boot boot.img

The TWRP does this patching and flashing process for you. Without TWRP, you just need to do it via Fastboot.
[OnePlus 10T 5G] Th3be4st:
That's not the right way to flash magisk, it's better to just "fastboot boot boot.img" just to test if everything is working and then direct install from the app. Using this method magisk backups your original boot.img so you can restore it anytime.
[OnePlus 10T 5G] Revontheus:
You already have the stock boot.img in the first place. That is what you will let Magisk patch. Therefore, if things go wrong, you can just fastboot flash boot stockboot.img
[OnePlus 10T 5G] Wilzzone:
Okay, little update a new problems:

-tried to boot without flash, read the image and failed bc it wouldn't find the "boot.img" and boot wasn't a valid command

-tried to flash boot and the same thing again.

I'm out, any solution?
[OnePlus 10T 5G] Th3be4st:
But installing it directly from magisk lets you use the "restore image" button from the app, so you can install incremental otas and keep root without ever using your computer again
[OnePlus 10T 5G] Th3be4st:
From fastbootd the boot command isn't available, so this error is normal, but "fastboot flash boot boot.img" should work fine. Are you sure it gave you the same error?
[OnePlus 10T 5G] Wilzzone:
From what I have seen yes, tomorrow will try again and update the info
[OnePlus 10T 5G] Wilzzone:
ok, so trying again

C:\Android>fastboot flash boot magisk.img

target reported max download size of 268435456 bytes

sending 'boot' (196608 KB)...

OKAY [ 4.331s]

writing 'boot'...

FAILED (remote: No such file or directory)

finished. total time: 4.342s

thats my actual problem

edit: maybe im doing wrong with the "fastboot flash boot magisk.img" and only need to put "fastboot flash magisk.img" but will wait for yours response
[OnePlus 10T 5G] Th3be4st:
Is magisk.img in the same folder from where you are launching adb? From what i'm seeing it should be in your "C:\Android" folder. Also check that you are showing extensions names in windows so your file isn't named "magisk.img.img".
[OnePlus 10T 5G] Wilzzone:
Is in the same folder, and extensions are alredy visible, nothing seems wrong.

I Adjunt Image of the folder just in case
[OnePlus 10T 5G] Wilzzone:
Update: I finally solved... I'm dumb as f.

The problem what's that the platform tools wasn't on the android folder.

Finally did the flashboot and it's rooted, thx to you guys who helped me and use your time in this post
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Skyrex04:
Has anyone got a kernel meant for overclocking the sm-t113 having lineageos 14.1?
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Revontheus:
At the time of writing, there is none.
[HTC Excalibur] eldustman:
I can't get OZ to work anymore. Does anyone have a version of OZ that works with 6.1 on a T-Mobile Dash? Or any other client that uses text service.
[HTC Excalibur] jdoggraz:
Yah man try downloading and installing this one, also if you are running the 6.1 rom make sure you run connection setup under the accessories.

http://www.mediafire.com/download.php?02f3mtsfdbb
[HTC Excalibur] eldustman:
Thanks man! Werks great!
[Android Q&A, Help & Troubleshooting] PrideTheArrogant:
Hello everyone,

I tried to follow this topic to flash my Teclast T40 plus, but I guess I messed up the boot partition, because when I try to turn it on, the logo appears with the words "INFO: LOCK FLAG IS: UNLOCK !!!" and it immediately shuts down. Also, it does not access recovery (tried power + volume- and power + volume+) and when connected via cable, the battery charging screen no longer appears.

Connecting it to the PC would seem to reveal it (I hear the sound), but it does not appear among the devices. Connecting it to a ubuntu machine, however, detects it for a few seconds and then obviously disappears when it shuts down:

View attachment 6056470

Is there anything I can do?

Thanks
[Android Q&A, Help & Troubleshooting] damcGo:
Hi All,

I'm currently facing challenges in detecting rooted devices, specifically those using Magisk version 26.1 on Android 9. I would greatly appreciate any insights or guidance from anyone who has experience with this particular scenario.

Here are some details about the situation:

Magisk Version: 26.1

Android Version: 9 (Pie)

I've tried various methods, including traditional root detection libraries and SafetyNet API checks, but haven't been successful in reliably detecting Magisk on Android 9 devices.

If anyone has successfully implemented a solution for detecting rooted devices with Magisk 26.1 on Android 9 or has recommendations on approaches that work well in this context, your assistance would be highly valuable.

Feel free to share your experiences, code snippets, or any relevant information that could help me overcome this challenge. Your support is much appreciated.

Thank you in advance!
[Android Q&A, Help & Troubleshooting] Oswald Boelcke:
Hello and good afternoon, @damcGo Welcome to XDA! I hope you'll always get the support you require and will enjoy your stays on our Forums.

However, prior to your next posting besides the XDA Forum Rules please read all the guidances that are stuck on top of every forum like

Note: Questions go in Q&A Forum

If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...

xdaforums.com

and the others. I've moved your thread to Android Q&A.

Regards

Oswald Boelcke

Senior Moderator
[ASUS ZenFone 8 Flip] maicol07:
*** Disclaimer ***

All flashing is done at your own risk!

While nothing from this thread should break your device,

don't come back here blaming anyone if it does!

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

The TWRP boot.img for Android 12.1-14 is attached to this post.

To boot it just run the following command in bootloader mode:

fastboot boot boot.img

Sources: https://github.com/maicol07/twrp_android_device_asus_I004D

Thank you @Captain_Throwback and @micky387 for the huge help while building the recovery!
[Other SmartWatches] thonkpt:
So i recently got a Colmi P71 for Christmas and i looked at it and started to wonder what could i do with it so i researched, reversed, etc. but now i only have some weird looking Chinese API domains from what seems like 3 different companies and a firmware file that seems to either be encrypted or packed in some way so now im here asking if anyone has any hint from where to go from here i can't find anything online and for the fun of it asked chatgpt which yielded nothing as expected.

Any hint on what the next step here would be?

Edit: it's some type custom firmware that they are running no wearOS or android or whatever and also some specs below

CPU: RTL8763EWE

BT: 5.1

Flash: RAM 270KB ROM 128Mb

APP: “Pubu Wear”

(Im still learning the ropes on this stuff and finally felt confident enough to go and jump into my first project but i wanna still go in blind so no spoilers of the journey please just some hints)
[Other SmartWatches] vxsw:
- most probably it's a some sort of a rtos.

- I don't belive in any encryption for this price level devices. just unreasonable.

- if you have an only 2pin connector, then you may work with firmware only via pcb directly.
[Other SmartWatches] thonkpt:
or some type of packing atleast i've tried using the file command on the bin file and DIE engine too either comes out "binary" or "data"
[Other SmartWatches] thonkpt:
plus i've seen in the android app it has some type of Download From User mode over bluetooth? similar to what a ytber called Aaron Christophel made (he made an app that from i could gather uses said DFU mode to flash binaries OTA called DaFlasher) but he used a p8 from COLMi (even cheaper model)

i am currently looking for a way to contact him for further info
[Other SmartWatches] thonkpt:
Currently trying to find ways in without busting the only one i got open
[Other SmartWatches] vxsw:
air can't give you full control of flashing. you may upload some data, but not download (if it's not provided). so I'm really not sure what you have an any way to get dump via bt, only via pcb directly.

also uploaded data must have an appropriate structure to correct installation, so you must understand fine enough as principles and structure exactly this modification of os, as completely understand ota update file structure and how it applies inside the os.

also keep in mind, what rtos have a lot of forks what may be as different enough as completely incompatible. try to compare at least by abilities any os like on your watch and zepp os (yep. it's based on rtos too, but try to feel the difference). so ota file formats even for similar forks may have their own modifications.

yep, it's not impossible, but tooooo complicated and would have a lot of efforts. it's m.b. interesting as experience but you must understand level of required work and it's cost (I more mean time and nervouse instead of money).
[Other SmartWatches] thonkpt:
not zepp os but how can i find other SmartWatch OSes im relatively new to this part of the modding scene
[Other SmartWatches] vxsw:
probably you can't. I'd never saw this information shared. you may find firmware images or dump it, but that's all.
[Google Pixel 7] uhero2:
I have a rooted pixel 7, with magisk, the only modules I have are "play integrity fix" by chiteroman and "systemless hosts". I have zygisk enabled and blocked all the google apps in the block list inside the magisk app settings.

Running the safetynet attestation with the app "YASNAC" tells me that basic integrity and CTS profile match PASS.

But when I try to add my credit card in the google wallet app, the app says that it can't add the card because the phone is rooted or modified.

Anyone can tell me why and how to solve this? Thank you.
[Google Pixel 7] simplepinoi177:
If you do not pass/achieve MEETS_DEVICE_INTEGRITY, Google Wallet and other services will not work.
[Google Pixel 7] uhero2:
I do not pass MEETS_DEVICE_INTEGRITY. I tried a couple of other magisk modules besides chiteroman's, but none of them work for google wallet.

Do you know any other way to make wallet work?
[Google Pixel 7] simplepinoi177:
nopes....Google Wallet depends and requires passing MEETS_DEVICE_INTEGRITY; non negotiable nor can be skirted around in any other way. If it were that easy, I doubt half of PIF users would be using PIF.

"couple of other magisk modules beside chiteroman's"...? Can you name which ones? because most likely you just need help setting it up properly with those modules....

But if you don't want to waste time and/or just get to it, I highly suggest just using PIF Manager component in the Pixel Flasher tool -- it should get you there without you needing to format, create, migrate, run-a-script, set up, or anything like that yourself (it will take care of it all)....

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Google Pixel 7] legaldexter:
PlayIntegrityNEXT fixed the issue for me.
[General Questions and Answers] Mario6w891:
I just got this phone a few weeks ago and decided to root it.

I managed to unlock the bootloader by requesting an unlock key from the official Motorola website.

From this point, I googled every website trying to find a way to root this but they are all fake. I'm asking you guys because I don't want to brick my Moto using wrong methods.

Edit: It worked using the traditional method!

Regards,

Mario
[General Questions and Answers] Prince_Of_Android:
Can You Please 🙏🏾 Elaborate The Traditional Method Which Worked To ROOT The Moto G84 Device ???

BTW I Hope Soon The Developer Community At XDA Post Some Custom ROMs For The G84 On XDA's G84 Device Development Page, Since It's Kernel Sources Are Already LIVE on GITHUB Which Makes AOSP Development For The Motorola Devices Quite Easier For The Developers.

Hey Have You Received Any OTA Update (Monthly Security Patch) Since You Purchased It ???

My Unit Has Pretty Low Bluetooth Audio. Are You Also Facing This Issue Too ??? 👀
[General Questions and Answers] Mario6w891:
As I said I unlocked the bootloader following official Motorola's website instructions. Note that it will void your warranty. Then I extracted the boot.img from my phone using DSU Sideloader and a rooted GSI (if you restart your phone it will go to your original Android version)

[ ICODE]dd if=/dev/block/by-name/boot_a of=/storage/emulated/0/boot_a.img

dd if=/dev/block/by-name/boot_b of=/storage/emulated/0/boot_b.img[/ICODE]

After that transfer these two files to your PC and restart your phone to the main system, install Magisk, patch the two files (you should upload the files from PC to phone again before patching) and then you should for the last time transfer the patched boot.img to the PC. The last step is to restart your phone to the bootloader and flash the image (I actually just observed that you can just do for the first patched file) using

fastboot flash boot (your name of the patched boot image).img

And you get Magisk installed on your phone!

Yes I did receive OTA updates! My currently Android security patch is December 1, 2023.

Sorry I didn't test Bluetooth yet
[General Questions and Answers] markdirven@:
Hello everybody. I am waiting for my ota update for Android 14, when it arrives, am going to try this (Latin American) 2347-1 boot image... I have rooted my motorola G84 since the first day I had it. And I have already done a complete firmware flash several times. Partly because of my own tweaks and adjustments, which did not work well, and also because I am working on getting Orangefox recovery working on this Motorola. At the moment it is completely stock ROM again. I only have to lock the bootloader. before I get another OTA update. i keep you updated....

*edit.... i forgot that 4 days ago, i already patched my own android 14 boot image. (XT-2347-2) euro variant. But i was stupid enough, to flash A13 boot.img to my device. Which of course resulted in a bootloop. And then I went back to the original A13 stock ROM. Once again done OTA to A14. new boot.img flashed. And everything seemed perfect. I had root, magisk, custom recovery, and I thought everything was working fine. But I had 1 big problem. No matter what I tried, I couldn't get any sound when making or receiving calls. And right now, from the debug data, I can't find many causes. What exactly the problem could be.

If anyone is interested in the original or the patched boot.img A14 from my G84. Let me know and I'll post a link.
[General Questions and Answers] G5 Plus Mate:
Hi markdirven@

Having a working custom recovery on the G84 5G with a working rooted ADB would be fantastic! That's what we would need to retrieve the boot.img from any rom, as long as we know where on the phone it is located (can change between Android versions). Please keep us updated on this.

However: I strongly advise not to EVER relock a bootloader again after unlocking!! You might end up being not able to EVER re-unlock it again! We had those cases in the Fairphone comunity. And there is also no reason to do it. You will not get your waranty back, once it is relocked. And for a software update the phone should be unrooted, but the locking status doesn't have any influence on this. So, my strong recommendation again: decide once if you want to have your phone unlocked (warranty gone) and leave it this way.

For a beter understanding: with the method I described above, there is no reason to every flash any boot.img. You only boot from it once via the PC and modify the existing boot.img on your phone with Magisk which always works. It works because it's the system's very own boot.img, which you modify with Magisk.

(Okay, we have to rely on Magisk not to ruin the boot.img when modifying it, but this never happened in my cases so far. But even then, we still can re-flash our saved boot.img(s) to the phone)
[General Questions and Answers] markdirven@:
Good morning. Finally it worked !!

I now have a working Android 14 with a patched boot.img and magisk installed.

and somewhat working custom recovery. (still laggy and far from stable)

I will post all the details later. Right now I'm uploading the original firmware (XT-2347-2), as well as the unzipped boot.img and patched boot.img for you to test or looking in to it.

What I do know is that it worked for me to also flash vbmeta.img and vbmeta_system.img AFTER flashing the patched boot.img with the commands:

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot flash --disable-verity --disable-verification vbmeta_system vbmeta_system.img

Without this, I again had problems with sound during calls. and other weird issues and bugs.

It was possible for me to obtain the new firmware using Lenovo's rescue software (Rescue-Smart-Assistant).

When i uploaded everything, i will update this post with a link to all the files.

And the way i did all this. later tonight

Here are the files:

Motorola G84 Files
[General Questions and Answers] v00d007:
and

@markdirven@

[Development] [Recovery] [Bangkk] TeamWin Recovery [3.7.1][OFFICIAL][13+] for the motorola moto g(84) 5g (25-02-2024)

#include /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns...

xdaforums.com
[General Questions and Answers] misterfx:
Hi,

thanks alot for the rooting instructions, it works.

But i've a problem to install OTA updates.

Followed the guide, installed the original (unpatched) boot_a.img to the current slot (a), but the update failed with "package verification failed"... any hints?

Thanks,

mistereffiks
[General Questions and Answers] markdirven@:
The only thing i think is, that the boot_a.img is corrupt, have you tried downloading the file again ? En then flash it ?.... You could also try to boot instead of flashing with the command fastboot boot boot_a.img, en then look what happens... I have no experiences with ota update files, but flashing on a/b devices i never have to flash a boot_a.img or boot_b.img. An unpatched boot.img would normally be the only thing you want to flash.

Sorry for the absence. I had very busy time.

The progress of a custom recovery. Is 50/50.. on original firmware, touchscreen works, but on rooted or custom roms, i have no touchscreen input.. i m not a developer of any kind, so for his problem i need the help of a experienced developer... The only thing i can think of is that some vendor touchscreen (focaltech ) driver doesnt work with recovery...

And before flashing you came from rooted firmware ?. Try flashing vbmeta.img before flashing boot_a.img with the following command:

fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

And then:

fastboot flash --disable-verity --disable-verification boot_a boot_a.img
[General Questions and Answers] homer1005:
Hi, I successfully carried out the root process with the Brazilian Android 14 rom, my problem is that I can't install the trwp recovery, can anyone help me? Thank you
[General Questions and Answers] djmarkd:
And what is exactly the problem? Flash failure, bootloop ?, If you are in fastboot mode. What does the following command do ?

fastboot devices
fastboot boot (nameofrecovery).img

Here is another download link for recovery

Twrp recovery for Moto G84

Greetings Mark
[General Questions and Answers] djmarkd:
I also found and tested a light (debloated) custom rom for the Motorola G84 and is called Bangkok light... So far no issues and rooted from beginning.

download:

Extract the ZIP file to a folder of your choice.

When the device is in fastboot mode,

execute in Windows powershell flash_custom.bat

for full new installations or update_custom.bat

for update from previous firmware, and everything will install automatically. Enjoy!

This custom ROM is a lightweight modification of the standard firmware. The limitation on writing to the system is removed, which is in read-only mode by default in Android 10, thus eliminating the possibility of modification. With this firmware, you can connect the system in Read Write (r/w), Read/Write mode. Encryption is preserved.

Root rights are obtained via Magisk v27.0.

The system is cleaned and lightened up.

All Google tracking is reduced to the core: telemetry, location history, Google Assistant, Facebook, Turbo, Wellbeing, Speech Services (voice-controlled search works), quick search Google Search (Velvet). YouTube has been removed. (Everyone uses ReVanced).

The following are built-in: Asus FileManager, Asus Gallery, AdAway, RootExplorer, NovaLauncher.

Ringtone, notification, and alarm sounds have been replaced.

Motorola and Google apps have been updated to the latest versions at the time of the custom build.

The volume has been slightly increased, and the speaker sound balance has been adjusted.

Additionally, Logo.bin and Bootanimation have been modified (boot animation is very cool)
[General Questions and Answers] homer1005:
hi, I downloaded the rom but when I click on flash.bat nothing happens, why?
[General Questions and Answers] djmarkd:
Hello. Can you give me more details please ? You clicked on the bat file ? I strongly recommend that you open a cmd terminal or powershell terminal in the directory of the extracted files. Both with admin rights ofcourse. And then execute _flash_custom.bat... and make sure you are in fastboot mode, and it should work automatically..... If not. Please provide me with more details. OR you can do all the following command manually:

fastboot --set-active=a
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash modem radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo_mod_bangkk.bin
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot erase carrier
fastboot erase ddr
fastboot reboot fastboot
fastboot erase product
fastboot erase system
fastboot erase system_ext
fastboot erase vendor
fastboot flash product product.img
fastboot flash system system.img
fastboot flash system_ext system_ext.img
fastboot flash vendor vendor.img
fastboot erase userdata
fastboot erase metadata
fastboot flash vbmeta vbmeta.img
fastboot flash boot boot_magisk.img
fastboot reboot
[General Questions and Answers] Mario6w891:
How do I flash the firmware on Linux?