Database Info

[Root] Boot / Root / Recovery

Thanks to some questions and awnsers I was able to create the
rooted boot.img for our HTC Bolt devices.
This was tested on the HTC Bolt Software 1.17.651.11 Android N 7
How To: (downloads at bottom of page)
Connect Device to computer
Insure that usb debugging is on as well as OEM unlock is checked.
The device must be Boot-loader unlocked to do this!
place both the patched_boot.img and the magisk_cache.img in the same directory your fastboot files are setup at ( c:/android/sdk/fastboot or wherever you have it)
Boot the phone into Download mode. ( Power + VOL down)
Open up terminal on the computer and run both these commands:
fastboot devices
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
followed by fastboot reboot
you'll need to head over to :
http://forum.xda-developers.com/htc-10/development/root-magisk-autoroot-magisk-phhs-t3507505
Grab the manager.apk and the super user apk to complete the setup.
Give these guys a thanks also for getting this going, gonna build a rom with debloat next and see if the twrp will flash it with this boot.img behind it.
shall see
Thanks to:
@OMJ Everything!
@topjohnwu magisk
@Captain_Throwback -twrp,root
@Chainfire - root
Downloads
Patched boot.img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528674
Cache img (For Magisk) - https://www.androidfilehost.com/?fid=601296195406528673
***********DevDigitel Custom Images************
Secure Boot Img: https://www.androidfilehost.com/?fid=457095661767122602
Unsecure Boot Img: https://www.androidfilehost.com/?fid=745425885120693359
Flashable ZIPS:
SuperSU:
https://www.androidfilehost.com/?fid=673368273298916495
Radio Fix Zip/FP Scanner Fix : https://www.androidfilehost.com/?fid=673368273298916521
Device will bootloop once, and when done will install su. Please be patient

Nice!

suprised that it went so smoothly, su being systemless is a little buggy here and there with Android N, but otherwise i was able to navigate the internals, remove the bloat, make some build prop edits and theyve stuck. so far so good.

Went ahead and tried to use flashify and flash the twrp image from other post. Flashed and was able to make a backup to sd only. I didn't flash or try to restore it yet but I did have to relock and restore 3x with the stock ruu after removing too much system and trying to flash xposed

thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first

S off
urbster1 said:
thanks for this! was able to get root on mine as well.
any idea how to get S-OFF? looks like Sunshine isn't compatible with Magisk, probably should have done that first
Click to expand...
Click to collapse
Not sure.. Probably gonna be some time with Android N.
I was able to change carrier types in Ui.
Got vzw 1x 3g 4G icons
Hot-spot mod
And a few other things working.
No radios to flash.. No kernels and I don't dev kernels.
So I don't need s-off really.. It's more so just having to re-lock
To go back to stock.

I just ordered a Bolt, can't wait to play

Screen shots

OMJ said:
I just ordered a Bolt, can't wait to play
Click to expand...
Click to collapse
Yey can't wait! It didn't want to be the only one working
On it!

Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...

zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.

zombie673 said:
Just curious about how you went about unlocking the bootloader? Tried using the HTC dev service but they don't seem to support the Bolt yet. Also, haven't had too much experience with the bootloader since I've mostly been on Samsung Verizon devices. lol...
Click to expand...
Click to collapse
Use the other supported devices section at bottom.
Just follow the steps on htc dev.
Save the unlock.bin file HTC will email you. You need it Every time you need to lock/unlock. Without s-off (removing the 2nd lock that protects the radios)
* the phone has to be re-locked to be restored with the stock htc software "ruu's"
Htc ruu is a 1 click style restore program...similar to odin that Will run on the PC and restore phone to stock.
It also comes in a update.zip format that can be flashed with the stock Signed recovery only via sd card slot.
Twrp is currently working on bolt / but has limitations because Its not 100%

More screenshots
Random stuff that can be unlocked hidden in the phone.

urbster1 said:
it is supported, just choose "All other supported models" and follow the instructions
Restored boot and tried Sunshine but it failed. Hopefully S-OFF will come soon.
Click to expand...
Click to collapse
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...

OMJ said:
@jcase has said Sunshine will support the Bolt but Android 7.0 must be supported 1st...
Click to expand...
Click to collapse
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.

jcase said:
We are working on 7.0 support, we will have to build a device profile and test after 7.0 works. Probably just need to dump some data off a bolt, but may need to buy/borrow one.
Click to expand...
Click to collapse
@jcase let me know if you need any more partitions, or anything else dumped... Worse case I can send you mine.

Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!

Team DevDigitel said:
Full root with Su support in other thread
This will no longer be maintained. Links will still stay good for those wishing to use this. Please go to the magisk forum page for related questions to his root tools.
Thank you for the support!
Click to expand...
Click to collapse
I actually just switched to this method after s-off, due to safetynet failing after detecting a unlocked bootloader...magisk can hide the detection

I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?

Team DevDigitel said:
I've done some research on safety net. What instances are people needing to pass the safety net check? Google api isn't stopping any of my processes or apps. Even banking etc. Is this directed towards things like android pay?
Click to expand...
Click to collapse
yep...AP is my only goal
there's a kernel patch to bypass detection but I don't know squat about kernel modding

Unable to install OTA updates since unlocking bootloader

Hello everyone!
Since I've unlocked and rooted my Pixel 2 it keeps failing the OTA update. I get the notification and the update is downloaded but when it's being installed, there is an undefined error. For all updates I had to sideload the OTA file via ADB. Honestly, I don't really know what could have caused this issue, as the first OTA update when I got the phone with all stock settings and roms it worked fine. Currently I can only instal the OTA.zip updates via ADB.
Things I did so far which could have caused the issue:
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Things I tried to resolve the issue:
Lock the bootloader again
Flash full stock rom with fastboot and official google script (failed "couldn't write bootloader.img" altough I had it unlocked)
Factory reset
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
Does anyone else have similar experiences?

ekalz said:
Things I did so far which could have caused the issue:[/B]
flash boot.img via fastboot (Magisk Root)
unlock bootloader via fastboot
Click to expand...
Click to collapse
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
ekalz said:
Also, everytime I reboot my phone i get the message that something is wrong with my phone and I should check it with my vedor. But everything is working perfectly - except for the updates.
?
Click to expand...
Click to collapse
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.

SweetSofie said:
My understanding is that anytime you modify the file system, etc (rooting patches some files) then it will fail the integrity check and not OTA.
Yes! I have that exact same message when I reboot. I flashed TWRP, rooted with Magisk Manager. I can't tell any negative concequences either.
Click to expand...
Click to collapse
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.

Can you root without patching or unlocking the bootloader so you don't fail the integrity check?

robocuff said:
The error you see about system integrity (or whatever it is ) when you boot the phone is due to Magisk patching the dtbo partition. It's a bug and will most likely get fixed eventually. It's nothing to be concerned about though. You can safely ignore it.
Click to expand...
Click to collapse
Thanks for the clarification! I would love to learn more about that stuff, I'm just not sure where to start learning.

I have the same problem with my pixel 2. I have tried full factory reset by flashing stock image. I have tried the recovery script some user posted in the p2 forum.
I contacted Google support about it and now i am waiting for 2nd line to contact me.
I will post here if/when i get a solution.

With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete

socal87 said:
With an unlocked bootloader, you will not be able to update via Android; you must sideload. However, sideload will fail if you do not have the factory boot and dtbo.
So, assuming you are rooted:
0. You must start with factory boot and dtbo images; if you are running custom, download the factory image that corresponds to your build, unpack and flash boot and dtbo
1. Download the latest ota.zip from the Google Developers website
2. Connect phone to computer, use ADB to reboot into bootloader
3. Once in bootloader, hit Power + Vol Up to bring up menu, use volume buttons to scroll to Apply update via ADB
4. Use ADB to sideload:
Code:
adb sideload update.zip
5. Select Reboot System in recovery when complete
Click to expand...
Click to collapse
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?

smorgar said:
That would explain a lot but are you sure its the unlocked bl that causes this problem? Google support told me it should not matter. Would it work with ota if i lock the bl again?
Click to expand...
Click to collapse
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread

socal87 said:
I am not certain, but with unlocked bootloader and stock kernel, the OTA still failed to install within system. I was able to sideload it, but the kernel had to be stock.
I just posted a guide how to get around this by using the factory image, as it does not appear to perform signature checks.
Thread
Click to expand...
Click to collapse
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)

smorgar said:
I tried relocking BL and proceeded to install OTA but same error presists. (OTA: Feb patch -> Mar patch)
Click to expand...
Click to collapse
Did you try to sideload via ADB?

socal87 said:
Did you try to sideload via ADB?
Click to expand...
Click to collapse
No I am waiting to get it resolved by Google so that I can install OTA in the future.

smorgar said:
No I am waiting to get it resolved by Google so that I can install OTA in the future.
Click to expand...
Click to collapse
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.

socal87 said:
Why don't you try sideloading the OTA? It worked for me. As for the future, you might not able to take OTAs without a completely stock image, but if you're just trying to get the March security update, either sideload the OTA, or flash the stock system image from the most recent factory ROM as described in my thread.
Click to expand...
Click to collapse
I was trying to fix the problem permanently so that i dont have to sideload if i dont want to.
**** went to ****... I did factory reset as the Google support person told me. Tried installing OTA again but it did not work. So they left me waiting for second line support to contact me but its now been the whole weekend and no support.
After support told me to do reset the last time the phone began to freeze and crash apps randomly. So i tried to install full factory image via fastboot but that was the last time the phone booted up. Now its completely dead.
When i try to boot the phone nothing happens. If i hold power button for 20-30 sec i sometimes get a short vibration and a line of pixels flashing by on the screen then nothing more happens. Now im waiting for Google support for real. Pray for my dead pixel2
If anyone have some tips for me im willing to try. The phone does not seem to boot and the PC does not recognize it at all.

You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.

davidisflash said:
You'll need to go into fastboot mode. Download the latest factory image and unzip. You'll find a flash all batch file to run in Windows. It will then do its magic. Remove the "-w" parameter at the end of it so that it doesn't wipe your system. You can always manually factory reset. That parameter has been known to have issues.
Click to expand...
Click to collapse
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
And so how did everything work out for you? Were they able to get you resolved, or are they just RMA'ing your phone?

No resolution. I sent it back to uk for replacement via seller.

smorgar said:
How do i enter fastboot mode when the phone wont turn on and the PC cant recognize it?
Some update regarding google support:
I was told to wait for 24-72h for second line support to contact me. They contacted me this saturday, about a week later and they are absolutely useless. They dont read what you type fully and they seem to not really know what they are talking about. I honestly feel like they have outsourced their support to Bagdad or something. My own enligsh skillz is not so good, but theirs is as basic as it gets. Feels kinda like chatting with a bot.
Some tips when contacting google support via chat: Dont use any advanced words. Dont type more than 5-10 words per sentence or they will not read it fully. Have patience, they take forever to respond, even a short sentence like: "What can i do for you?"
/rant
Click to expand...
Click to collapse
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716

davidisflash said:
How are you trying to turn on the phone? What about it just holding the power button for like 30 seconds, releasing, then again but this time holding power button AND volume down? Is the battery charged?
There are two separate drivers for Windows. When the phone is in fastboot mode, you'll need to use the separate adb / fastboot drivers. In fact in device manager, this will appear as a separate device (that's because the device will register under a different device ID).
The main Windows driver is here:
https://developer.android.com/studio/run/win-usb.html
The adb driver is here:
Good page I used to debug it not being recognized:
https://forum.xda-developers.com/pixel-2-xl/help/device-recognized-adb-fastboot-t3698716
Click to expand...
Click to collapse
I have done all the basic and advanced stuff. I had it dead for about a week to play around with. Used to work in a mobile repair shop so this isnt something new for me.

Xperfix

Hi Friends
My wife by mistake deleted important files. Tried Dr. Fone and others but need to root before doing deepscan to recover. I spend hours and but error all the time at 80% because no root access.
I have no choice but to unlock bootloader without backing up TA neither I know how to do it.
Due to late night no time to manually sideloads, but bought Xperfix to do the job to TWRP/ROOT/DRM
So far twrp installed successfully but not rooted nor installed magisk . Let me pull the usb at 20% and wait twrp to reload after 100% nothing done. Maybe twrp not mounted system properly?
I am also worry now after seeing others saying that unlocking bootloader will effect the camera functions?
But as per xperfix 3.0 it says the problem been solved.
How is this Xperfix does it really work ?

try flashing magisk 16 in recovery and see if you get root.

ofuroinu said:
How is this Xperfix does it really work ?
Click to expand...
Click to collapse
When you bought Xperiafix you also bought support from the developer. Go back to sToRm//'s website and raise a support ticket.
If you include the txt logs found in c:\xperiafix that would be helpful
I have used his tool on my XZ1 compact, so I know it works, but getting the right drivers installed on your Windows machine is a real minefield. Windows chooses the wrong drivers by default when you connect the phone with TWRP running. This sounds like your problem to me. You have to manually add them with the phone connected TWRP on.
Also, you can't just install the drivers in Windows 10 (Windows doesn't tell you it failed to install the drivers, you just can't connect.), you have to go into safe mode and install the drivers with 'driver signing disabled',
There is a lot of helpful advice in the original Xperiafix thread, along with the links to drivers required.
Edit: you have to pull the USB at 20%, go into TWRP yourself (from powered off, hold volume down & power, wait until phone starts, keep volume down for a few more seconds) and swipe to make system partion writeable, then reconnect phone and Xperiafix will do the rest.

appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.

ofuroinu said:
appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.
Click to expand...
Click to collapse
you should be able to flash drm fix from xperifix folder. if im right it should be in you Local Disk C folder.

raven213 said:
you should be able to flash drm fix from xperifix folder. if im right it should be in you Local Disk C folder.
Click to expand...
Click to collapse
Hi Raven I can see the DRM Folder with files but which files to flash or if have any instructions somewhere to follow to avoid error.
DRM >
Lib folder
Lib64 folder
sfk application
Or I just need to run sfk app in twrp that's it?

ofuroinu said:
appreciate your reply , I have tried many times reflashing with xperifix when twrp reach 20% to restart it wont restart auto I need follow on screen instructions to do and mounted the system untic the and finished to 100% but again no magis and no drm . I copied the magis file from xperifix folder and flashed directly now have rooted already. Only thing why I have been using xperfix because of camera issue and is green. Support no reply yet since yesterday.
Can I manually flash the drm and fix the camera issue ? Please guide me my wife is so sad about this incident.
Click to expand...
Click to collapse
Can you post the logs from the C:\Xperiafix folder?
Once you have reached the 20% step and gone into TWRP to enable system file write and plug the phone back in, Xperiafix continues if it does nothing then the drivers are wrong.
You will know when the drivers are right as the phone restarts itself once it's been reconnected to Xperiafix.
Read this thread on the original app, everything is explained and the drivers linked

Explanation from sToRm//, help is on the way!

I got it fixed by reinstalling and use WIN10 . Now all set. Appreciate to all my friends on XDA for assisting me.
I want to now after this will I be still getting OTA from Sony can update or need manually update?
How is the battery life after using xperfix?

Hi Friend I am back again with some help need.
I want to know how to install Android Pay on root phone?
My wife said she failed to install because phone is rooted.

ofuroinu said:
Hi Friend I am back again with some help need.
I want to know how to install Android Pay on root phone?
My wife said she failed to install because phone is rooted.
Click to expand...
Click to collapse
Android pay will work if you follow Xperiafix. Magisk will install and if you select 'magisk hide' in the settings you will be able to use android pay. It's ok, you don't have to pretend it's your wife's phone

Hi Mate
Thats what we did but failed with Android Pay at counter.
Also bank applications refuse to install because phone was rooted.
Do banking applications works on rooted phone?
Tapatalk を使用して私の MIX から送信

ofuroinu said:
Hi Mate
Thats what we did but failed with Android Pay at counter.
Also bank applications refuse to install because phone was rooted.
Do banking applications works on rooted phone?
Tapatalk を使用して私の MIX から送信
Click to expand...
Click to collapse
Have you tried to run Safteynet after you have installed Magisk? (on the Magisk start page)
Do you have Xposed installed?
There is no way to hide Xposed and it will fail Safteynet
I have several banking apps that work and one that refuses to install

Nope I did not install xposed.
Here is the problem after clicked start safety net the status all are failed.
ctsProfile:false
basicintegrity:false
Magisk version v.16.0
Installed ver 16.3
Tapatalk を使用して私の MIX から送信

Got is solved by hiding safety check passed.
But still the citibank app refused to run due to rooted phone.
Anyone tried this app if working?
Regarding android pay do I need to run safety net check each time before using it?
Tapatalk を使用して私の MIX から送信

Now we have received notifications of OTA Updates I want update her phone . Do I need to follow exactly as per below link ?
How about settings and data will that remain? Because I use TWRP on my other phones to flash roms which is fast and safe.
Why we dont have same solution for Sony but need use newflasher tools?
https://forum.xda-developers.com/showpost.php?p=72958788&postcount=16

Question How to relock bootloader?

I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?

phaw16 said:
I root my phone before and I found out the most of the app I used doesnt work with rooted phone. I did flashed the original firmware but I am always getting an error prompt every time I restart my phone or turning my phone off. I also found out that all my banking apps doesnt work if the bootloader is open.
So, I am hoping if by any chance I can have my bootloader relocked?
Click to expand...
Click to collapse
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.

You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.

Anubarak16 said:
You can make your banking apps work with magisk hide - that's an option to hide your root state for certain selected apps.
Click to expand...
Click to collapse
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.

twistedumbrella said:
You can't change your mind later. Are you sure you can't use one of the safetynet fixes to use the apps?
Beyond that, I believe the locking command was never found. There was a post stating the ones for the ROG 3 didn't work, but I'm not sure if that was ever resolved.
Click to expand...
Click to collapse
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.

Whenever that I boot into fastboot it's showing fastbootd and not fastboot.

phaw16 said:
I tried the safetynet fixes it doesn't work for me for as long as the boot loader is tampered it wont work. The ROG 2 relocking bootloader worked for me before using tool in one but now I'm not sure how to fix it. I may need the latest boot loader IMG it might fix the issue.
Click to expand...
Click to collapse
You're correct about Safetynet fixes and this device. Some (or all?) apps seem to be able to detect the open bootloader on ROG 5 somehow if they want, even if you get a visual pass on Safetynet with fixes. Don't know how and not sure if there are fixes out there that may work - I didn't find one. I use another device for banking apps.

phaw16 said:
Whenever that I boot into fastboot it's showing fastbootd and not fastboot.
Click to expand...
Click to collapse
Try Fastbooting with the physical buttons (Vol Up + Power) instead.

phaw16 said:
From where I am at its not the root state that's causing the issue, my phone is not rooted at the moment its running on stock ROG5 firmware the latest one still it doesn't work. Its the unlocked boot loader that's causing the issue.
Click to expand...
Click to collapse
Continued at https://forum.xda-developers.com/t/how-re-lock-bootloader-asus-rog-5.4285013/

You can continue discussion in the existing thread here
Thread closed
Thanks

Moto One 5G Ace Rooted with TWRP using stock Firmware

First of all, I am not a dev and this write up contains steps used by various devs to achieve fulll root. For some, these steps have worked out well. But, not for me. I had issues with some of the steps not fully working as they should, so I did some research until I could piece together something that worked for me. Here's what I did and managed to get fully rooted using the boot.img from the stock firmware after doing all the steps from this link Articul8Madness's Rooting Guide and couldn't get full root access even after using the steps from this link Articul8Madness's Guide for R/W Access. As I have said, these steps worked for most people. I wasn't one of them.
I followed the steps up to the step where the boot.img is modded by Magisk. This is where I omitted using the modded boot.img and used the original boot.img from the stock firmware and I then ran the flashfile script as mentioned in the steps. After everything was applied I then, rebooted the phone, started setup, disabled System Updates, and I then proceeded to install TWRP using the steps from this link https://drive.google.com/drive/folders/1KZ0xhstQ9V_7TYt3xs7P5XdroYX61CEA after opening Minimal ADB and Fastboot applying these scripts
adb reboot fastboot
then apply this
fastboot flash recovery twrp-3.5.2_10-kiev.img
I then rebooted into recovery and installed TWRP to all available partitions. I then installed Magisk, enabled Systemless Hosts in settings, and rebooted. Afterwards, I used the steps here Munjeni's RW in Super Partition Tool to get RW in super partitions after downloading and using superrepack. I had omitted the ./superrepack /dev/block/bootdevice/by-name/super system_a in order to have it applied to all available partitions. Everything worked out great. I then rebooted, updated Magisk, installed Root Checker and Root Explorer with Superuser root access. I then installed Adaway from https://github.com/AdAway/AdAway and clicking on the Get It On AdAway image. Anything that requires root access here on out, can now be installed. As for the SafetyNet issue, I have not had any problem with it at all even though the check had failed. All is now working well and I sincerely hope that this guide will help others as it have helped me. I may have done this write up but, all credits goes to the true devs.
Time for devs to start making custom Roms now that TWRP can be installed.

Your first link doesn't work for me. The Adaway link works. FYI.

RETIEF said:
Your first link doesn't work for me. The Adaway link works. FYI.
Click to expand...
Click to collapse
WOW!!! I see what I did wrong. All links are now working.

Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Sorry, but you will have to ask one of the Devs in the links that I've provided in the OP. Perhaps they are more suited to help with that.

eurovive said:
Hi there. As i understand Windows PC is required for this unlocking? Any idea on Linux emulated on Chrome OS?
Click to expand...
Click to collapse
Linux will work fine. All the commands required are done thru a terminal session. Use a text editor to get the long unlock code from the phone.
Good luck.

Ok about terminal. I used cmd , but bootloader cannot be unlocked official way nor at&t unlockable coz i don't live in usa.I will try 3rd party helpers.

iceman19631 said:
First of all, I am not a dev...
Click to expand...
Click to collapse
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.

egalambos said:
You did a fantastic job. This worked perfectly. Some notes:
1) You must install the Motorola device driver in Windows. Doesn't work with leftover drivers that seem to communicate just fine with the phone.
2) You have to unlock the bootloader via Motorola's website if it is locked. Key step not communicated: when you enter in the code to unlock at the computer with a fastboot command the phone will ask you to confirm that you want it unlocked. If you don't look at your phone and answer the question it will time out.
3) When you boot into TWRP it will ask for a password if you have a screen lock set. The password is your screen lock. No big deal.
4) Once you are in TWRP install the Magisk Zip file and let it do its magic.
5) Enjoy a fully unlocked stock firmware. It's awesome.
Thanks again.
Click to expand...
Click to collapse
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.

iceman19631 said:
You're very welcome. And thanks for the added info, I forgot to add that in the steps. Thanks again.
Click to expand...
Click to collapse
Any plans for an update to 3.6.0 for Android 11??

egalambos said:
Any plans for an update to 3.6.0 for Android 11??
Click to expand...
Click to collapse
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.

iceman19631 said:
Sorry for the late reply. I really haven't decided yet if I'll update to Android 11. I would imagine it'll be rooted in the same manner. If I could get ahold of the US version, I may give it a shot.
Click to expand...
Click to collapse
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.

egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
egalambos said:
I've update to android 11 and am continuing to use your version of twrp but it's off a little bit in terms of the partitions it loads. Seems to work otherwise.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I don't have an answer for that at this time since I'm still on 10. That'd be too much like a blind man in a desert looking for shade and telling another which way to go.

Greetings, I have a few questions. re the Moto G 5G (One 5G Ace)
I've not found a TWRP for this phone yet which were you using?
In other phones it was important to backup the IMEI (EFS ) and 'persistent' partitions. Do we not do that with this phone as well?
Thx in advance

Sorry for the late reply. I used this version of TWRP twrp-3.5.2_10-kiev.img. As far as the IMEI (EFS) question, it wasn't required when using this root process. However, you can back those up if you like.