I need help - Android Q&A, Help & Troubleshooting

I need help - Android Q&A, Help & Troubleshooting

I have a samsung galaxy sm-a325m and sl try to root it, the odin gives me the following error: CUSTOM BINARY BLOCKED BY OEM LOCK . vbmeta, but when putting the file that was not altered by magisk if it lets me, does anyone have a solution?

The message is pretty self-explanatory. before trying to flash custom binaries make sure it is allowed by OEM.
enable OEM unlocking in developer options. enter Download mode and unlock bootloader (will factory reset device). reboot into One UI and double check OEM unlocking in developer options.
then you can flash magisk patched boot + vbmeta.

Welcome to XDA and enjoy the forums!
Cheers

'Introductions' are only for introductions. Support goes into the appropriate section.
No introduction in post, thread deleted.

Related

[EOL][Guide][Newbie] Resource/Help Thread [Noob Friendly][albus][Moto Z2 Play]

This guide is outdated now. Please refer to the thread OPs of the respective projects.
Hi all, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all. I will try my best to update this thread often. You can ask any question regarding Moto Z2 Play aka albus here. Our XDA Community will try to help you. Make sure you always read before posting the same queries. If you're stuck in a problem, make sure you provide us with as much as information of what you were exactly doing and what happened along with your device details ofcourse.
Also remember that unlocking the bootloader will void your warranty. Relocking it won't give you back your warranty. If you are visiting a service center for repairs of any kind, they will come to know that you have unlocked your bootloader (you put a code on their site lol). But yea you can try your luck by visiting them after you lock your bootloader using the fastboot firmware.
No one, but you are responsible for whatever you do to your device. If something happens due to your ignorance or lack of backups or knowledge, only you are responsible, not the developer, not the XDA Community. Just read the respective posts, search (at XDA and at Google) before posting and you might probably find answers. Cheers.

Setting up adb/fastboot on your system:
These drivers are quite essential for every android user.
How to use?
Windows:
Minimal Fastboot/ADB: https://www.androidfilehost.com/?fid=745425885120698566
Just install the setup. Reboot your phone in bootloader mode (Power off and then press and hold power + vol down simultaneously) and connect via USB cable. On your computer, navigate to the directory where you installed them. Press shift+right click and choose Open Command Window / Powershell here. Type:
Code:
fastboot devices
If you get a serial number, fastboot is working.
For adb to work enable Developer Options and turn on USB Debugging on your device. Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Now authorize USB Debugging by allowing it (Choose something like Always trust)
Type this on your command window / powershell window:
Code:
adb devices
Again it should return a serial number.
If both these fail, you might consider rebooting your computer or even installing (MDM) motorola device manager. Make sure you don't have any crappy or outdated drivers. (Always keep your system upto date ) Anything else, you'll have to google up things.
Motorola Device Manager:
For more info regarding adb/fastboot open this: https://developer.android.com/studio/command-line/adb.html
Linux users might need to install it from their respective package manager repos, Ubuntu for example:
Code:
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
Arch Linux on the other hand:
Code:
yaourt -S android-tools --noconfirm
Similarly for the other distros.
Commands are the same. fastboot needs to be used with sudo.

Unlocking the bootloader:
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and register your E-Mail ID.
Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader/fastboot mode (power off the device, then press the power and volume down buttons simultaneously).
On your computer, go to the directory where you installed the adb/fastboot drivers (or make sure this folder is in your $PATH to acess fastboot and adb system wide).
Open CMD/Powershell/bash in here. (Windows users might need to Shift+Right Click and choose "Open Command/Powershell Window here" , Linux users can open terminal as per their respective distro. Now , type
Code:
Code:
fastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be:
Code:
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device:
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
fastboot oem unlock your_code
and wait your device to reboot !

Flashing TWRP Recovery:
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to format data once via twrp wipe options and reboot back to twrp for functioning of /data
Downloads : http://www.androiddevs.net/downloads/
Keep the twrp recovery file (.img extension) in the adb/fastboot folder
Reboot to bootloader, open cmd/bash and type:
Code:
fastboot flash recovery filename.img
(if you want permanent flash) or
Code:
fastboot boot filename.img
(if you want temporary
boot)
Now you must flash the verity disabler zip.
HIGHLY RECOMMENDED:
After the twrp is done and you have successfully rebooted to system, it is a good time to reboot to TWRP again and backup your phone. (System and Boot most necessary)

Flashing Stock ROM:
Will be updated as soon as the fastboot version of the stock ROM is available.

Unbricking your hard bricked/dead device:
Connect your device via the usb cable, extract this zip file to the adb/fastboot folder and then run:
blankflash.bat file if on windows; the .sh file if on linux.
Once this is completed, you must flash the full stock firmware via fastboot. This is MANDATORY.
Blankflash zip: http://cloud.vache-android.com/Moto/albus/blankflash/blankflash.zip

Reserved

please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW

OneArm said:
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
Click to expand...
Click to collapse
Yeah, I am not sure what is going on this time around with the VZW variant. Since the Droid Z was bootloader locked and the unlocked Z wasn't (but not VZW compatible) I am almost expecting the same here, but I keep being told that the unlocked version of the Z2 will work on Verizon so maybe they just don't care anymore. I mean, the unlocked Nexus 6 and VZW Nexus 6 were pretty much the same phone too, and both were bootloader unlockable.
The only thing that gives me pause from going out now and getting the VZW version vs the unlocked model (whenever its slated to come out) is that Motorola's Bootloader Unlock page doesn't have it listed (yet). Either it can be and they are behind on updating the list, or it can't... at which point the unlocked one will be listed with a (Except VZW Model) like the other phones have. But... if either version works on VZW... what's the point of making one unlockable and the other not? Seems like a waste of time.... of course VZW's past decisions on phones don't make sense in some aspects.
All I know is... I want one of these if they are unlocked. Once the keyboard mod is released I will be back to the nerdy bliss that is a sliding keyboard and making this phone the spiritual successor to the Droid 4.

After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
After installing TWRP it asked for the encryption password so I put it and it opened normal I went to restart> system, then appeared option to install the application twrp, I slipped it to be installed, then went on reboot> system and stopped on the screen Of bootloader unlocked .. help me: |

m.lucas said:
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
Click to expand...
Click to collapse
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.

yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
how should I proceed? My device has no ROM only TWRP installed. :s

m.lucas said:
how should I proceed? My device has no ROM only TWRP installed. :s
Click to expand...
Click to collapse
Start TWRP, and you can transfer zip file from PC by using "adb push"
"adb sideload" may work too.

yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

Junior Passos said:
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).

yunzo said:
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
Click to expand...
Click to collapse
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.

Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
tywinlannister7 said:
Reserved
Click to expand...
Click to collapse
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.

@niteshpant kindly edit your post and remove the reserved post from the quote.
Moreover, the links will be added here as soon as the firmware is available.

Junior Passos said:
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Click to expand...
Click to collapse
As I wrote before, I have failed both of 54e6a79 and latest.
Error message on TWRP is same.
Have you met this message but rooted successfully after boot?
Today I tried system-mode SuperSU, and met boot failure which continues to show Motorola/lenovo logo.
It is different from dm-Verity failure (which shows unlock warning).

Stuck in TWRP, Help
I have successfully flashed the TWRP but now it is looping at TWRP and when try to do factory reset, in just seconds it is boot again and shows TWRP main screen again, moreover storage shows about 50000 mb in internal memory, secondly my memory card is not accessible, selection is not working only shows internal memory. As I think at this stage my bootloader(stock) is fine, original stock recovery is replaced by the TWRP 3110 . My factory Android rom is still there in my phone because twrp inernal memory option shows about 50000 mb space captured in internal storage. I have clear delvik and cache but all fails, how I can get the OS by the TWRP. I assume if my old OS has been erased then twrp should have give the "no OS install" massage but this is not happening in my case. Any help...... I am not doing something more due to complete device failure in this stage mainthing is this no factory rom image is available yet, very annoying issue.... regards

[Guide][GSI] How to flash GSIs on Nokia 3.2 (00WW)

Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/

Btw is it safe to downgrade?
Stupid question but as i had told u that im on latest January update is it necessary to just flash an old update to get things working?
Cant u plz provide me a patched boot.img based on latest January update?
Plus which GSI rom u have used and find it better ? (In battery and stability). .what were the bugs ?

I need latest boot.img plz i have 00ww varient
On latest January 2020 update

If you want to flash gsi just downgrade your firmware using the pack I've created. Because I don't have boot img file from January 2020 firmware

Can you explain what is GSI ? Is it a flash-able custom ROM or what ?

GSI is a Generic System Image that could be from Google itself or from Custom ROM developers like LineageOS. The GSIs use drivers from manufacturers. Any devices that support project Treble (GSI support) have the drivers for dealing with a GSI image and Adapting the Android version to your device.

s3tupw1zard said:
Hi,
I've packed the Firmware (without system.img) into a 7z file for flashing GSI easier.
**DISCLAIMER**
* Your warranty is now void.
* I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
**DISCLAIMER**
Step-by-Step Guide:
1. Download and unpack the nokia_3.2_october_gsi_base.7z file anywhere on your computer. And reboot to bootloader mode (i think you already unlocked your bootloader)
2. Go ahead and first execute flash-all.bat and then flash-magisk-nodm.bat. Thats because for having the October 2019 firmware on your device, because the magisk patched image file is from October firmware and has removed the AVB/DM-Verity parameter.
3. Download any GSI ROM you want, but best is if you use a GSI with GApps included, because you can't flash GApps manually. (I've got a TWRP Port but you could brick your device and you can't flash anything to system with it, so it simply useless)
I can recommend Havoc OS from ExpressLuke GSI. (It now has GApps included)
4. After unpacked the xz file just flash it with 'fastboot flash system GSI_ROM_FILE_NAME_HERE.img'
5 Reboot and Done!
Downloads
https://drive.google.com/open?id=1NxEMAOZvEvx8Nw0qsw9_1jaEC4UYS-fu
How to unlock Bootloader:
How to Unlock the Bootloader of the Nokia 3.2
Step 1 – Enable OEM unlocking
You need to enable OEM unlocking, which can be done by enabling the developer settings on your device. To do so, go to Settings, About phone and repeatedly tap Build number. Developer options will then be added to your system settings, where you can then enable OEM unlocking.
Step 2 – Unlock your phone
Set up adb, reboot into your bootloader and run the following command. Yes, it’s really that simple!
fastboot oem unlock
You can reboot into the bootloader by switching on USB debugging, setting up adb and fastboot and typing “adb reboot bootloader”. Alternatively, you can hold volume down and the power button to boot up your device. USB debugging is also located under the developer options.
Source: https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/
Click to expand...
Click to collapse
File is in trash xd

MKashifSajjad said:
The file is trashed.
Click to expand...
Click to collapse
I have the Android 9 October 2019 images here:
https://drive.google.com/drive/folders/16bxdyEKEnBEVadC6lbrAoXxJIDAnGw0m
If anything goes wrong after using flash bat/sh files just run this command using fastboot:
Code:
fastboot --set-active=a
you can also try setting "b" as the active slot, both works. No differences.

Can anyone with a lineageos or AOSP/Phhusson GSI confirm what is working and what is not working?
WIFI
RIL (SIMcard)
GPS
Thanks

link is broken plz update the link

Followed all steps and its working...

Galaxy A11 SM-A115 Need TWRP

I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing

Why not compile a matching TWRP by yourself?
Look inside here.

@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.

ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!

what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone

ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...

I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?

I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.

flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.

Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.

Is there any updates that can be flashed with stock recovery

griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating

sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.

griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply

sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.

[GUIDE] - ROOT Motorola One Fusion (XT2073-2) in 10 steps

WARNING:
You should only proceed if you are familiar with unlocking and rooting android cellphones in general or... if you dare. Instructions assume you have a working computer with adb installed.
1. Getting the cellphone ready
Enable Developer mode
Enable USB Debugging
Enable OEM Unlock
2. Download magisk apk
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
3 Install the apk using adb
adb install MagiskManager-v8.0.5.apk
4. Download original firmware (check precise version at About phone > Compilation number)
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
.... YOU MUST BE ABSOLUTELY SURE THIS IS THE SAME VERSION !!!!!
5. Unzip and copy boot.img to /sdcard/Download
adb push boot.img /sdcard/Download
6. Patch the boot.img
Open magisk on the cellphone and click Install (upper right corner)
"Select and patch file"
7. Copy the patched file to your computer
adb pull /sdcard/Download/magisk_patched_XXXXX.img
(replace XXXXX with appropriate characters)
8. Unlock the bootloader
Standard process for all motorola phones. Go to the bootloader:
adb reboot bootloader
Get the unlock data
fastboot oem get_unlock_data
With this information complete the process at:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
When you have the KEY, unlock with:
fastboot oem unlock <KEY>
9. Flash the unlocked boot.img
fastboot flash boot magisk_patched_XXXXX.img
10. Reboot and you're done
fastboot reboot
Don't forget to disable and uninstall lots of the built-in rubbish
Happy hacking!

Does it work with Moto One fusion + ?

I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?

Skycr0nos said:
I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?
Click to expand...
Click to collapse
You mean disable the message saying "your bootloader is unlocked, don't store data on the phone" ?
I'm not sure, but i don't think it's easy...

Can I root my device motorola one power fusions plus.?
Root work on this device .?
If root is work why YouTube not making videos about this device.?
I want to root my device. Than I need custom recovery.IMG file and magisk stable version.
Can you help me guys

Thanks, it worked for me, XT2073-2 128GB

BruceWawe said:
Does it work with Moto One fusion + ?
Click to expand...
Click to collapse
It does but make sure to download different stock firmware (its called liber go back a few folders in the link OP gave)

Doubt about image kitchens

Hello everyone. As I said on earlier posts, I'm trying to port TWRP recovery for an Alcatel 1T 7 8067 Tablet (mt6580 processor, 600x1024 px resolution). I've tried the kitchen method; I've used auto TWRP porter, Carliv Image kitchen, Android image kitchen, image tool; but none of them have worked for me. Worried for these failures, I decided to make an "experiment". I tried just to unpack stock recovery, without altering it, and after, repack it, and then, reflash it to my device. I did that with carliv Image kitchen, android kitchen, and image tool, and suprisingly, none of the repacked images worked. So I thought, "If the repacked original recovery, doesn't work, ¿how could work a ported recovery?"
At this time I don't if that is a bug of these programs or a bug or lock of my device. About the last, I must say that when I flash an edited recovery (that doesn't works), system boots warning me with "red or orange state", and when I flash the stock recovery, that warning dissappears. As I understand, that warning comes from a security system on the tablet, to ensure the integrity of the files, I mean, the authenticity of the files; so I don't if when the system detects an unoriginal image, it will lock it o something like that.
I don't know... so please guide me if you know about this. Thanks in advance.

only stock recovery can work on locked bootloader. if you are using osm0sis AIK (as recommended in linked guide to your double post) you might have noticed that AVB signature. unlock bootloader first

aIecxs said:
only stock recovery can work on locked bootloader. if you are using osm0sis AIK (as recommended in linked guide to your double post) you might have noticed that AVB signature. unlock bootloader first
Click to expand...
Click to collapse
Ah ok. So you're saying that I can flash any image that I want with sp flash tool for instance (that I know if bootloader is locked I can't do that via fastboot commands without unlock bootloader first) , but if this device has its booloader locked, despite image works, it won't with locked bootloader... I'm gonna do the homework (unlock bootloader and repeat the "experiment") and I'll tell you if that worked.

Camilo Gil said:
Ah ok. So you're saying that I can flash any image that I want with sp flash tool for instance (that I know if bootloader is locked I can't do that via fastboot commands without unlock bootloader first) , but if this device has its booloader locked, despite image works, it won't with locked bootloader... I'm gonna do the homework (unlock bootloader and repeat the "experiment") and I'll tell you if that worked.
Click to expand...
Click to collapse
Ok, I did the "homework"; took me a while unlock my bootloader, because it was a little tricky, but finally I made it. So then, I did the "experiment" of unpack and repack stock recovery without any modification; then reflashed it, and tried to enter recovery, and... yes you did have reason Cheerful for this news, I decided to "cook" again, a TWRP using Mediatek TWRP Auto Porter 1.3, flashed it, booted on recovery mode and... ¡Woo hoo! it booted on TWRP version 3.2.1. And the best is, that someone told me that posibly if I could port TWRP, touch screen support won't work, ¡but it's working!
PS 1: I guess that on every tutorial about recovery porting, the publisher must warn firstly, that as previous requirement, is needed to have an unlocked bootloader, to avoid all this odissey.
PS 2: Now i'm having rooting issues with TWRP, but that's another topic.

the generic twrp I used was 3.3.1

Better Mobile App

welcome