Database Info

[TWRP + ROOT] Galaxy J7 Refine (SM-J737P) (Oreo 8.0) (Boost Mobile)

TWRP has been successfully ported to the Galaxy J7 Refine (SM-J737p) (Oreo 8.0)​
DISCLAIMER: THIS IS NOT AN ODIN FLASHABLE TWRP. THIS IS NOT AN OFFICIAL TWRP. THIS IS A TWRP PORT THAT HAS BEEN MADE POSSIBLE BY BOTH @Dark98 & MYSELF. IT WAS BUILT USING FILES FROM R16NW.J737PVPU1ARG3. IT MAY OR MAY NOT WORK ON DEVICES WITH A DIFFERENT BOOTLOADER VERSION
You must have root access. I am currently working on making an Odin-flashable .tar for TWRP devs. Hopefully it will be available soon. Until then, root your device with Magisk. SuperSU is dead..
There is a downside & an upside to porting TWRP. The downside is that after you flash TWRP, you will lose root. The upside is that TWRP will remain so all you need to do to regain root is flash the Magisk-v18.1.zip. It's a very delicate process & you will need to pay attention or else you will bootloop & start over.
In order to flash, you need an app that will do so without booting into recovery. Flashify is the ideal choice for this procedure. View attachment flashify.apk Flash TWRP in Flashify but do not reboot from the app. Power off your device & boot into TWRP manually.
PAY ATTENTION TO THESE NEXT FEW STEPS!!!
- Boot into TWRP for the first time
- Swipe to allow modifications
- Wipe > Format Data > type yes when prompted (this will not delete any files you have in your Internal Storage)
- Once wipe is completed, go to TWRP home screen & Reboot > Power Off
- Once device powers off, reboot back into TWRP (yes you will boot into recovery twice)
If you fail to immediately boot back into TWRP, you will brick & have to restart.​First boot is to clear out the /Data partition to make room for your new recovery. Second boot is to secure it.​
Now that you have secured TWRP, go ahead & make a backup of your Boot + System + Data partitions. Keep in mind that you've lost root access so the backup will be "stock" firmware with TWRP.
------------------------------------------------------------------------------------------------------------------------------
Now to get root back
(In TWRP)
You will now flash Magisk-v18.1. With the new security measures Samsung put in late 2017, you will need to flash 2 .zip files after to ensure that root sticks. YOU NEED TO FLASH THESE FILES IN ORDER. DO NOT WIPE CACHE AFTER EACH FLASH. DO NOT REBOOT AFTER EACH FLASH. FLASH EACH PACKAGE ONE AT A TIME. WAIT UNTIL THE 3RD FLASH IS COMPLETE & THEN REBOOT DEVICE. IT WILL TAKE SEVERAL MINUTES SO BE PATIENT.
In this order, flash:
- View attachment Magisk-v18.1(18100).zip
- View attachment no-verity-opt-encrypt-6.0.zip
- View attachment RMM-State_Bypass_Mesa_v2.zip
DO NOT WIPE THE CACHE
Now reboot device normally. If you do not flash the verity & RMM zip files in order, you will fυck your sh¡t up & have to start over.
PROOF OF TWRP:
View attachment 4730415
View attachment 4730414
View attachment 4730413
View attachment 4730412
When you get to your home screen, you will receive a notification to update Magisk. Update by either selecting the notification or manually through Magisk Manager. Allow Magisk to install the update, not TWRP.
Extract the .tar from the .zip > extract the twrp.img from the .tar View attachment J737P.zip
This is for the Galaxy J7 Refine (SM-J737P) (RUNNING OREO 8.0) (J737PVPU1ARG3)
Special thanks to @topjohnwu for Magisk
Special thanks to @Dark98 for working with me on this project. Probably could've done it without you bro but it would've taken longer

work for j737t and j737t1?

juniorgerman said:
work for j737t and j737t1?
Click to expand...
Click to collapse
The root method should, provided you substitute in your own patched_boot.img from your stock firmware.
TWRP however, will not. Those variants are GSM Carriers (T-Mobile network). This is for Boost, a CDMA Carrier (exynos7885)

Thank you
Thank you for this as I will give it a go.

Kireej said:
Thank you for this as I will give it a go.
Click to expand...
Click to collapse
This thread should've been deleted already as it's not the main one. I've moved it to here. Please direct any further comments or inquires here as well.

Is there a rootable method for the J737P 9.0 Android update?

LeThAiL JoKeR said:
Is there a rootable method for the J737P 9.0 Android update?
Click to expand...
Click to collapse
Hello, I have a Galaxy J7 Refine from Boost. Recently I decided to root it. There are only a few places that have ANY info on rooting SM-J737P.
Not realizing that this was an OLD thread, I basically just went along with this and a little info from somewhere else and some knowledge of rooting from back when I basically HAD to have my phone rooted.
Good news is, first try it worked for me. But I had this issue that I figured would be easy to remedy.
There is a notification when I boot the phone saying Unauthorized actions have been detected. Restart your device to undo any unauthorized changes.
Without doing any research on the notification I immediatly lept into action and caused the phone not only to boot loop, but also not be able to boot into recovery, where I had made my backup.
I tried flashing several roms/files and trying to figure out the issue, I realized that this was an old thread and the Binary Update number on my phone was 7, and here i was trying to flash 1's, 2's, 4's, 6's. Like no wonder they didnt do anything to help.
Immediately trying to search for U7, I was hitting road blocks, because it seems as though everyone's list stopped at U6.
Fortunatly for you, I would not take no for an answer and spents HOURS trying to figure out what file I needed and then locating it. Not being able to boot into OS or Recovery, figuring out what version my phone was on was a bit tricky. Cross referanced this info with that info, yada yada yada.
I found the most up to date file in case you brick your phone, but also if your still interested, I can help supply the info and files I used to accomplish this.
But as I type this, I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
I'll get back to you on those results. For now, im done typing. I haven't typed this much in a LONG time.

I cant stop thinking about that notification. I need to find out if its going to cause me problems or if I can just shut it up and everything will be fine.
(Disable the app called securitylogagent do no th delete will cause bootloop) I am looking to see is there new firmware u7. i have binary 6 rooted and would like to find u7 to try root?

Disable image
......fix that notification

I found out using lucky patcher to get rid of notification. Which that was the first app I was going to install anyways. So it worked out great.
As far as the u7 binary, I found it. I'll upload it to drive and share a link here shortly.
Currently uploading file to folder, but when its done you should be able to access it here.
https://drive.google.com/drive/folders/1MD3owVbiAjgSyz0-f4Q_eSATV1zcXZeZ?usp=sharing

hello i'm on the u7 binary i'm having trouble rooting can someone share a link for the patched boot for the u7 or a flashable twrp if there is one? any help is appreciated and thank u

never mind i got it thanks anyway

How do you root a Samsung Galaxy SM-J737P Version 9

PlsHelpMeRootingImBegging said:
How do you root a Samsung Galaxy SM-J737P Version 9
Click to expand...
Click to collapse
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above

weric43 said:
I'm on 7 but I believe all u would do is flash twrp and patch ur boot img from ur binary with magisk and follow the rest the steps listed above
Click to expand...
Click to collapse
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible

PlsHelpMeRootingImBegging said:
But i can find my TWRP and no one click roots work i tried kingo root kingroot and SO many others none work and framaroot wont work either nothing works and my twrp idk if its compatible
Click to expand...
Click to collapse
I have the twrp flash file give me a few mins I'll get it to u

weric43 said:
I have the twrp flash file give me a few mins I'll get it to u
Click to expand...
Click to collapse
download files unzip files inside u will find flashable twrp

okey

PlsHelpMeRootingImBegging said:
okey
Click to expand...
Click to collapse
Did u get it?

weric43 said:
Did u get it?
Click to expand...
Click to collapse
so i installed magiska and tapped install to the tar file idk it never flashed so i tried again and it said their was no recovery.img found

[Guide] Update and Retain Root

*Note* Some people have had success with this, while some others have not. You do this at your own risk.
Prerequisites:
Magisk Manager might need to be unhidden based on reports from some users.
Magisk needs to have a backup of stock boot.img.
Preserve AVB 2.0/dm-verity must be enabled. (Have gotten mixed reports on this it might or might not be needed)
Check the following post if you don't meet the prerequisites
https://forum.xda-developers.com/showpost.php?p=81186247&postcount=73
Update Process
When phone detects update
1. Disable any desired Magisk modules, ex. Edxposed (I usually disable all modules just to be safe)
2. Reboot
3. In Magisk, select Uninstall, press Restore Images
4. Do NOT Reboot
5. Install OTA Update via Settings -> System -> System Updates
6. When prompted to reboot, Do NOT Reboot
7. In Magisk Manager press Install
8. Select Install to Inactive Slot
9. Reboot
10. Enable the Magisk modules one by one
In case of bootloop after enabling a module there are 2 ways that I know of on how to retain root and fix bootloop.
One requires ADB
While phone is stuck in bootloop, connect phone to PC and run this commands via ADB.
adb wait-for-device shell magisk --remove-modules
adb reboot
This will remove all modules and you should be able to boot.
The second way is via fastboot. More information in this thread.
https://forum.xda-developers.com/pixel-4-xl/themes/magisk-modules-disabler-booting-magisk-t3990557
Some information that might help some people.
eg1122 said:
I know some users flash patched boot.img that someone else patched, thus bypassing the creation of a backup. I think choosing or not choosing to preserve avb 2.0/dm-verity also affects if phone will take OTA. I always preserve mine and always patch my own boot.img so I haven't ran into any issues. I'll just have to wait and see what happens on my end once I get the update. This reminds me of some issues some people where getting early on when rooting. Some people had to flash the patched boot.img to both a/b slots and some people didn't. Having both slots with a patched boot will also break the restoring of stock boot.img as Magisk only restores the active slot.
Click to expand...
Click to collapse

If you do it this way you'll be using the patched boot image from the previous update and not the current one.

airmaxx23 said:
If you do it this way you'll be using the patched boot image from the previous update and not the current one.
Click to expand...
Click to collapse
No it doesn't. When you select install to inactive slot it patches the newly installed boot.img that has been installed to the inactive slot. Only reason phone promts you to reboot after an update is to switch slots.

For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.

pdfruth said:
For whatever reason, whenever I would try to do Uninstall - Restore images (in step 3 of the OP), I would get a toast error saying "Stock backup does not exist"
I'm not sure why the expected backup files hadn't been created. I suspect it has to do with the process of manually patching the boot image whilst initially rooting, as suggested in this Git issue.
Anyway, I was ultimately able to work around this, and was eventually able to get Uninstall - Restore images to work.
I wrote about my workaround method here.
Click to expand...
Click to collapse
Yeah, there needs to be a backed up stock boot img for this to work. Being able to restore images the way stated in the issue would solve this as you could just restore a stock boot.img then continue doing the steps.

So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!

DemonicMurderer said:
So does this work for every update? Just do the steps and it works? Im a complete noob when it comes to this stuff i just follow the write ups and pray!
Click to expand...
Click to collapse
Yes, it has worked for me all the time. These are the exact steps recommended by topjohnwu, I just made them more readibly available to users. Here is a link to his tutorial.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

This work for the Verizon Pixel 4 XL???

SAMCR02018 said:
This work for the Verizon Pixel 4 XL???
Click to expand...
Click to collapse
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.

Badger50 said:
Why would you need to since your not rooted with a locked bootloader? Just take the OTA.
Click to expand...
Click to collapse
Ok the can the Verizon version get the BL unlocked?

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
Nope. Unless you got lucky and they sold you a google version by mistake.

SAMCR02018 said:
Ok the can the Verizon version get the BL unlocked?
Click to expand...
Click to collapse
There is a write up for that.

Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?

Donric13 said:
Does anybody know if this also work with a custom kernel? I thought removing root and let magisk install old (boot) image should reinstall stock boot.img (if magisk first was installed through fastboot with stock kernel). Then i can take ota, patch inactive slot with magisk and then reboot. After reboot i can install custom kernel again througj ex kernel manager app. Does anybody know if this works?
Click to expand...
Click to collapse
Yes this method works with custom kernel. Magisk removed custom kernel when it restores stock boot.img

When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
I wouldn't do it until the Dec ota comes out and that may be later today or sometime this week. Which is weird since all the other Pixels got it but hey it's Google

in_dmand said:
When does the dec patch come out, on the 5th?
I just started the process then realized it wasn't out yet so I haven't rebooted. When I go to the step of installing to the inactive slot I get a warning that you should only do this after the ota update - does anyone know if I'll be OK to go ahead with it even though I haven't done the ota yet?
Click to expand...
Click to collapse
Since it's not out yet, just do a direct install in Magisk to re-install it

Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.

mkpansare said:
Thanks for this guide !
Does anyone know how to update and maintain root for manually updating using OTA files ? Usually the update takes a long time to reach my phone, so I update using OTA files.
Click to expand...
Click to collapse
The other way I update is using full factory images. Once you download the zip, extract it and find and open (via Notepad++ or similar advanced text editor) the flash-all.bat or flash-all.sh (depends on your system), find this line
fastboot -w update
replace with
fastboot update
Basically remove the -w, this will prevent a factory reset (wipe) on your device. Once it is done you will need to patch new boot.img via magisk and flash the newly patched boot.img via fastboot.
Hope this helps!
ps. I recommend to always disable Magisk Modules before updating as they could cause FC

eg1122 said:
Since it's not out yet, just do a direct install in Magisk to re-install it
Click to expand...
Click to collapse
Thanks that worked perfect... Was gonna be a long week without adblocker and lmt pie lol

Android 11 preview

https://www.xda-developers.com/essential-phone-android-11-developer-preview/
It's not quite over...

Nice!

garywojdan81 said:
https://www.xda-developers.com/essential-phone-android-11-developer-preview/
It's not quite over...
Click to expand...
Click to collapse
very nice!

It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?

NuAngel said:
It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?
Click to expand...
Click to collapse
I'm no developer, but I don't think it's that simple.

NuAngel said:
It's my understanding that the Essential was built to basically meet exact specs of what an Android phone should be. Is it possible to continue to get monthly security updates direct from google, even though Essential as a company won't be around?? Or is the firmware ALWAYS customized to the model?
Click to expand...
Click to collapse
There fact that there's still customizations and changes that have to be made even to the Pixel GSI to even boot on mata says the firmware has to be customized even though the specs themselves match

They just upload a new file, is a vendor for developers.

android 11 working realy good on essential phone i will upload complete package to flash BOOTLOADER UNLOCK NEEDED

Is WiFi and mobile data working?
Sent from my PH-1 using Tapatalk

on my site wifi is not working with the latest vendor image. i also miss some features like full screen navigation and some other features like fingerprint gestures.

I am interested.
veisen said:
android 11 working realy good on essential phone i will upload complete package to flash BOOTLOADER UNLOCK NEEDED
Click to expand...
Click to collapse
Like how good? WiFi and data and BT all working?
I have "OEM unlocking" on under developer options, what else do I need to do to lock and load?

freshlysqueezed said:
Is WiFi and mobile data working?
Click to expand...
Click to collapse
@mrmrkmail
on reddit they are saying data works but not wifi
edit: some other things not working either
edit: wifi fixed

IronRoo said:
@mrmrkmail
on reddit they are saying data works but not wifi
edit: some other things not working either
Click to expand...
Click to collapse
Looks like we need an updated boot.img to get WiFi working. Anyone create a user debug build and have the boot.img they can share with us?
https://github.com/EssentialOpenSource/device_essential_mata/blob/master/README.md
Sent from my PH-1 using Tapatalk

thanks for your responses.
the issue with the older kernel in the boot images (february) i have read already on reddit . i am also hoping that someone is able to provide us a boot image with a newer kernel that will work.
edit: on reddit there is a guide how to create a boot image: https://www.reddit.com/r/essential/comments/fbnmpg/comment/fj7yma5?utm_source=share&utm_medium=web2x
there is also a direct link to download a packed boot image.

The reddit thread links the GSI system image, the vendor image, and a custom boot image to get the PH-1 flashed successfully. The trick is that TWRP isn't going to install, so probably not Magisk either.
I checked the Wifi, Mobile Data, and voicecalls working. Did not check BT.
If anyone knows how to get Magisk working with this, please post instructions.

daverup said:
The reddit thread links the GSI system image, the vendor image, and a custom boot image to get the PH-1 flashed successfully. The trick is that TWRP isn't going to install, so probably not Magisk either.
I checked the Wifi, Mobile Data, and voicecalls working. Did not check BT.
If anyone knows how to get Magisk working with this, please post instructions.
Click to expand...
Click to collapse
I haven't tried the Preview yet, but if I were going to flash Magisk, I'd copy the boot image to my phone, open Magisk Manager, tap Install and choose Patch Boot Image. Then select the boot image. It'll make a new, patched boot image in addition to preserving the original. Then flash the patched boot image via Fastboot.

gk1984 said:
I haven't tried the Preview yet, but if I were going to flash Magisk, I'd copy the boot image to my phone, open Magisk Manager, tap Install and choose Patch Boot Image. Then select the boot image. It'll make a new, patched boot image in addition to preserving the original. Then flash the patched boot image via Fastboot.
Click to expand...
Click to collapse
I did run magisk manager with the boot image copied to the phone, but I didn't get an install option. Is there a specific location for the image?

Open Magisk Manager. Top should indicate if you have Magisk installed, update available, etc. To the right of that is an install button. Then it'll ask how to install.
The boot image will be wherever you saved it to on the phone, the patched boot image might default to the same directory, but mine usually goes to the downloads folder once patched.
https://images.app.goo.gl/NWF4h47zQQiyJNYGA
That link should show the install button and the option to patch a boot image. But it's not necessarily the proper steps.

gk1984 said:
Open Magisk Manager. Top should indicate if you have Magisk installed, update available, etc. To the right of that is an install button. Then it'll ask how to install.
The boot image will be wherever you saved it to on the phone, the patched boot image might default to the same directory, but mine usually goes to the downloads folder once patched.
https://images.app.goo.gl/NWF4h47zQQiyJNYGA
That link should show the install button and the option to patch a boot image. But it's not necessarily the proper steps.
Click to expand...
Click to collapse
Thanks for the help.
I got a little further. I must have failed to install Magisk Manager properly the first time,
This install worked and I was able to patch the boot image. I then attempted to flash it using fastboot, and got a failure.
FAILED (remote: 'unknown command')
fastboot: error: command failed
The boot image was modded by someone on reddit, maybe there is something in there causing problems.

daverup said:
Thanks for the help.
I got a little further. I must have failed to install Magisk Manager properly the first time,
This install worked and I was able to patch the boot image. I then attempted to flash it using fastboot, and got a failure.
FAILED (remote: 'unknown command')
fastboot: error: command failed
The boot image was modded by someone on reddit, maybe there is something in there causing problems.
Click to expand...
Click to collapse
You copied the patched boot image back to your PC? Did you use the following command?
fastboot flash boot_a magisk_patched.img
Replacing boot_a for the slot you're on?
It's also very possible that Magisk isn't compatible with Android 11, which is more likely the case than something about whoever built the boot image.
The errors tell me you typed something wrong. Maybe wrong command or the patched boot couldn't be found.

Motorola One Macro [Root Tutorial]

This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy

Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
hi...
this guide works for me.
Motorola One Macro LatinAmerican version Telcel.

Pretinaverse said:
This phone doesn't have its own section in the forum yet, so I decided to put here a little guide for those who haven't figured out how to root it yet.
There is no twrp version for this Motorola yet, so I'm going to teach you how to root it without recovery.
This is how I rooted my Motorola One Macro:
Unlock your bootloader here.
Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
Download THE SAME VERSION of your compilation from here.
Extract from the zip the boot.img
Copy boot.img in a folder of your choice in your phone.
Install Magisk Manager apk in your phone (download here)
Open Magisk Manager and choose Install --> Install --> Patch file
Select boot.img and wait until it's patched
A new file would be created in the same folder you put the boot.img, named magisk_patched.img
Copy magisk_patched.img to your PC.
Reboot your phone to bootloader
Now replace the boot.img of your phone with the new one patched by magisk using the following commands:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
fastboot reboot
And now you are rooted. Enjoy
Click to expand...
Click to collapse
This worked for me too.

Hello! Thank you very much for the tutorial for the Moto One Macro. I was tired of looking for a tutorial for mine.
But one question remained: Because I am unable to install a Recovery, am I unable to flash a custom rom? Because I was trying to root the device just to install a Custom Rom of the Lineage OS type of Android 10, considering that as far as Motorola is concerned, the pro 10 update will not come anytime soon. But I still thank you for the tutorial.
Sent from my Motorola One Hyper using XDA Labs

Question
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.

Screen mirroring Motorola one
Hello,
I have a root Motorola one Android 10, but I can't share my screen to my Samsung smart TV, i search a lot but I didn't have success, first I edited the build.prop lines,
persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0)
persist.hwc.enable_vds=0 (before it was persist.hwc.enable_vds=1)
I added this in the end
wlan.wfd.hdcp=disable
I added another line but I don't remember all because I erased it, i only remember the beginning
Persist.sys....
But it can't work, in my TV only show something like
"Screen mirroring: motorola is connecting" but then the signal is lost
Nothing that I tried work, only one thing is good and is that in my cellphone in the option of share screen after change this line: persist.debug.wfd.enable=1 (before it was persist.debug.wfd.enable=0) I could activate wireless screen and it let me TRY to connect with my TV but without success.
In other post show the last configuration with an extra thing, I should edit a file (wfdconfig.xml) and it supposed to stay in this direction system/etc/ wfdconfig.xml. But I search in all files and I didn't find.
Maybe someone can help me.
Thanks.

altffour said:
I have multiple questions I would like to ask.
1. Would this format the phone? Which partitions will get formatted?
2. Can you explain the namings of the folder in the link to the post? What do they mean? I've seen a compilation number close to mines in the 'retail' folder.
3. From where do people get these uploads? I've tried multiple times contacting Motorola for image uploads and they never sent anything. I am very interested in the origin of the files.
4. Is there anyway to recover from a failed patch?
The reason I want this is that I've tried patching the bootloader using an image from a fishy website and it soft-bricked my phone, I had to reformat the whole thing with a fresh image
Btw, thank you for contributing to the phone's community!
Update:
Installed successfully, magisk is enabled and root is functioning and whatnot. Problem is, sometimes on booting the phone hangs on the weird colorful animation. It's not consistent and I can't figure out why. I discovered force rebooting the phone multiple times boots the phone successfully but does not fix the problem. Boot times are slower, probably because of modules.
Click to expand...
Click to collapse
Motorola doesn't official share the firmware, but there has always been people with access to the firmware servers.
https://mirrors.lolinet.com/firmware/moto/ has lots of moto firmware
LMSA can also be used to get firmware for most moto devices
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

Can't find build number
Pretinaverse said:
[*]Check the Compilation Number of your firmware (probably something like PMDXX.XX-XX)
[*]Download THE SAME VERSION of your compilation from here.
Click to expand...
Click to collapse
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?

lorenzzv said:
Hi, I can't find my Build Number in there. Mine is PMDS29.70-81-3.
I see several PMDS29.70-81 but none of them have the -3 I need. Any suggestions?
Click to expand...
Click to collapse
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.

Can any one please confirm, if after rooting this phone are you able to do call recording both side clearly ?

Not working
Help, I did this and now my phone is stuck on the Motorola logo, ¿is a way to undo this process? T_T

just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest

atattooedgod said:
just download motorola smart assisstant on your laptop and plug your mobile to it and it will do the rest
Click to expand...
Click to collapse
That did the trick. MY ETERNAL GRATITUDE TO YOU, SIR. YOU ROCK.

HELP
atattooedgod said:
yeah me too, but I solved it, I just rooted mine just download and use Rescue and Smart Assistant to download your firmware and repeat the steps above and that's it, it took me about five minutes to root my phone.
Click to expand...
Click to collapse
Hey bro, im looking for this, can u upload? or give any link related? LMSA is coded by monkeys with cocaine in water and tells that my XT2016-2 is'nt compatible :\

Help!
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.

Do you have TWRP for XT2016-2 ?

mrmanson07 said:
I am from Brazil and I have a Motorola One Macro and the device does not appear in the list of supported devices for OEM unlocking on the Motorola website.
Click to expand...
Click to collapse
Ignore the list the list of never been complete.
The only way to know if the bootloader can be unlocked is to try to unlock it.
Sent from my Moto E (4) using Tapatalk

Nice

VD171 said:
Do you have TWRP for XT2016-2 ?
Click to expand...
Click to collapse
There is not, but i am working on developing one we'll see soon if i can complete it succesfully due actually there are a lot of problems with this one

TWRP would be a nice treat here. Keep the thread updated on any progress.

Question Semi bricked Poco X4 Pro 5g Need help!

Hi all,
So i've previously unlocked my Poco X4 Pro 5g and rooted it. All was fine until yesterday where i'm now stuck in the booting screen.
I have installed every OTA update and i'm running global Xiaomi ROM. I noticed the phone was getting buggy and since it hadn't been restarted in some time, I did so in the hopes the bugs would go.
Upon restarting which took a VERY long time, everything was un-rooted(?) following the reboot. I think this is happening because i had to hide Magisk previously for certain apps.
Anyway i tried to re-root by using Magisk by using fastboot to flash my boot.img that Magisk patches from my original install from previous updates back which is where i think the problem lies. Since numerous updates later, the boot.img may have changed hence now why i'm stuck in the boot screen.
What can i do since i can't find a download link the the very latest ROM. Using the original boot.img also causes boot screen freeze so now i'm out of ideas
Any ideas?

stevey88 said:
Hi all,
So i've previously unlocked my Poco X4 Pro 5g and rooted it. All was fine until yesterday where i'm now stuck in the booting screen.
I have installed every OTA update and i'm running global Xiaomi ROM. I noticed the phone was getting buggy and since it hadn't been restarted in some time, I did so in the hopes the bugs would go.
Upon restarting which took a VERY long time, everything was un-rooted(?) following the reboot. I think this is happening because i had to hide Magisk previously for certain apps.
Anyway i tried to re-root by using Magisk by using fastboot to flash my boot.img that Magisk patches from my original install from previous updates back which is where i think the problem lies. Since numerous updates later, the boot.img may have changed hence now why i'm stuck in the boot screen.
What can i do since i can't find a download link the the very latest ROM. Using the original boot.img also causes boot screen freeze so now i'm out of ideas
Any ideas?
Click to expand...
Click to collapse
Use this tool
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?

stevey88 said:
Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?
Click to expand...
Click to collapse
The root seems to be the source of the problem.
ARB problem: install a more recent rom or delete the lines concerning ARB from the rom script or use the script directly from the rom folder without going through Miflash or trying an older version of Miflash.
Indeed the flash will delete your data, if you have access to Twrp try to save, without guarantee that the backup or restore will work.
Miflash will allow you to recover your phone.

stevey88 said:
Thanks for your reply, could you tell me what has gone wrong with the phone and what i need to do?
I've followed the link, the flash tool wont install the drivers and crashes (i have created a log folder which seems to be a common issue but doesn't fix). I've attempted to flash but i receive the error:Antirollback check error.
I'm not sure what, if anything has happened but now im stuck in fastboot mode!
Looking at the images in the link, it looks like following this guide will wipe my phone?
I'd like to attempt to recover it first if possible, could you tell me what your link is intending me to do?
Click to expand...
Click to collapse
Hey, i had to use miflash tool today, and also got the antirollback error on my first attempt. Turned out, in my case it was caused by spaces in the path to the rom folder.
Might not be the case for you, but worth checking, eh?
Also, make sure to double-tripple check the "clean"/"clean and lock" flag in the miflash tool before flashing it. Wouldn't want to accidentally lock it again

JustRay76 said:
Hey, i had to use miflash tool today, and also got the antirollback error on my first attempt. Turned out, in my case it was caused by spaces in the path to the rom folder.
Might not be the case for you, but worth checking, eh?
Also, make sure to double-tripple check the "clean"/"clean and lock" flag in the miflash tool before flashing it. Wouldn't want to accidentally lock it again
Click to expand...
Click to collapse
I was able to miflash working by commenting out the anti rollback checks in the batch scripts. I had other issues due to long folder names. I was able to reflash and recover, thanks again to NOSS8
I really regret not backing stuff up before restarting although i should've before loading a boot.img
I'm attempting to patch the latest boot.img using Magisk, hopefully all will go well this time. At least I've got nothing to loose now!

Hello bro I understood your problem that was caused by magisk i also faced this issue and understood that it is making problem while patching the boot.img thats why I reccomend to not patch the image because it ends with a bootloop just rename the Magisk.apk to Magisk.zip and flash it normally with a custom recovery now al done you can use magisk without bootloop but dont forget to flash bootloop saver magisk module to be safe from other magisk module issues