Database Develop

[HOW TO] Return to stock

Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips

Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.

If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.

Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy

Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!

full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!

esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.

NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE

WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.

Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP

when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?

cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.

moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from

irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip

So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?

How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.

Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.

robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.

A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.

hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this

At&t G8 Bootloader Unlocking Guide

Edit before publishing: I started writing this for all variants other than sprint, but I'll now make a separate thread for variants that have kdzs and those that don't, otherwise this will be a mess.
Firstly, keep in mind that no one is responsible if you end up bricking your device! There is currently no way to recover from a hard brick other than sending your phone in for repair, so make sure you follow every single step carefully if you wish to proceed!
Additionally, flashing an xbl through DD may not pass randomly even if it appears that it has worked, so be aware of the risks. Only at&t users will need to flash the xbls anyway since that is the only variant other than sprint which does not have kdzs available.
Users with the AT&T variant who are stuck on pie: temp root only works on android 10, as such you will unfortunately not be able to bootloader unlock your device. The firehose may leak at some point in a few months, and you will be able to unlock (and update manually) if it does.
The process for unlocking bootloaders on models other than the sprint one (specifically At&t for this guide) is practically identical; however, it uses different xbl_config.img and xbl.img files, which need to be specific for your device from the pie firmware.
The version naming may not be the exact same for other models, but you just have to ensure that you are on the March patch or below. If you are on April, you can find the guide to switch slots and do so in order to revert to March. To STOP UPDATES, fully uninstall or disable the update center packages either with ADB or package disabler pro for LG, which you can easily find online.
So I repeat, you're going to follow the sprint g8 bootloader unlocking guide, but you have to use the xbl and xbl_config for your device rather than the ones provided in the sprint guide. The engineering abl is the same, but I'll include it here anyway so that you don't have to mess around with any of the files provided in the sprint g8 guide.
Now, steps that are to be ignored and steps that may differ slightly:
Keep in mind that I'm only mentioning what you should be aware of and what may be different, but you still have to follow the guide written by BrandonB1218 in general.
1a: Of course, you still need a vulnerable firmware, and sadly AT&T does not provide kdzs, so you cannot bootloader unlock if you are on the May patch.
You can Ignore this: I found that another method that most likely stops updates is following this guide on youtube. It's supposed to bypass frp lock, but it also gets by all the LG agreements you have to accept, so it will ask you to agree to these if you ever open up the software update option in settings and will probably not update if you don't.
2: Some people had issues with different versions of the mroot script, so try all of them before you come asking for help please. I also suggest that you just temp root without running the temp root magisk setup as you may end up bricking if you accidentally flash a module or make magisk flash a patched boot img (DO NOT FLASH ANYTHING OTHER THAN WHAT'S INCLUDED IN THE GUIDE).
I suggest running the backup script and the commands to make sure you're completely safe, but make sure you keep them separate because a lot of the partitions included in the commands that @BrandonB1218 mentioned are device specific and include your IMEI. The backup script should only backup the partitions that aren't device specific such as system, and this is probably the one you'll need if at all because you shouldn't be touching other partitions. STILL DO BOTH THOUGH
3a: Yes, you have to run the command to find out which slot you're on, but you will not flash anything from the pie or 20d sprint backup that's listed there, or else you will likely brick.
3b and 3c: This should all be the same: If your active slot is A, follow 3b, and if your active slot is B, follow 3c. The commands should also be the same, just with different files.
If your active slot is A, but the files included for your device are also named xbl_a.img, for example, you can just rename them to fit with the command.
Otherwise, you can just change this, for example,
dd if=/storage/emulated/0/Download/xbl_b.img of=/dev/block/bootdevice/by-name/xbl_b
to this:
dd if=/storage/emulated/0/Download/xbl_a.img of=/dev/block/bootdevice/by-name/xbl_b
You also need to flash the engineering laf, so either rename the file or change the command so it works. The link is embedded
Overall, its just important that you take the right file in the first part of the command and flash it to the correct partition of the correct slot in the second part.
If I remember correctly, the method to boot into fastboot is hold vol- and power until the screen goes black (while the phone is plugged into the computer) and then to let go of power as soon as that happens.
4a and 4b: You do not want to do either of these as the boot img and other partitions vary per variant. I unfortunately do not have the magisk patched At&t boot img, but you can patch it yourself from the backup you made and flash it. It might be good to do this beforehand, but you could also just temp root again and dd flash it.
Alternatively, you can flash the metaphysics 1.7 kernel with twrp and magisk included, but you still have to follow the rest of the twrp installation in the sprint g8 bl unlocking guide. TWRP is the same for all US variants.
Congrats! You should now be bootloader unlocked and ready to go at this point. If you ever find yourself unable to boot on the slot which DOES NOT have the engineering abl, you can always switch to the slot with the engineering abl, go to fastboot, and fastboot flash your backed up partitions.
Credits:
Obviously to BrandonB1218, for writing the sprint g8 bootloader unlocking guide
vl48 for basically answering all my questions and providing the needed files
j4nn for writing the temp root
Mr. Zhu for twrp
KamioRinn for metaphysics
Anyone else who contributed in telegram to get this to work!

Amazing! Can't wait to do this. I'll report back when I get this phone unlocked.
Thanks for taking the time.

Files can't be downloaded dead link

blumix said:
Files can't be downloaded dead link
Click to expand...
Click to collapse
No issues here

Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.

Pietrobell86 said:
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Click to expand...
Click to collapse
No sorry. Not sure exactly what your problem is, but it might be solvable with root

Shtiff1 said:
No issues here
Click to expand...
Click to collapse
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
Click to expand...
Click to collapse
I am talking about the AT&T_G8.zip

blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
@antintin zip not downloading, FYI
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
I can't find it, sorry. I'm on Verizon

Hey, thanks for the guide. I'm rather worried about trying this as LG's newer models are so darn easy to brick. AT&T variant has no LG Bridge support which is incredibly stupid. At least we have kind people like you helping us free our phones

My LG G8 is a secondary phone right now, and as such, I'm very interested in trying this out. Unfortunately, the download link for AT&T_G8.zip give me a 404.

Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?

Espen115 said:
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Click to expand...
Click to collapse
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other

antintin said:
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
Click to expand...
Click to collapse
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.

lightningdude said:
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
Click to expand...
Click to collapse
Why would it have to be removed?... I'll just upload it when I get home and have time

antintin said:
Why would it have to be removed?... I'll just upload it when I get home and have time
Click to expand...
Click to collapse
Just out of consideration for space in your account, in case you were low on free space. I also didn't notice that it was a < 3MB file.

so is someone going to reupload the file or what? cant even download it from the op attachment.
does this even work with 20m or are those of us out of luck?

File Broken
Anyone has the copy of AT&t_G8.zip? Its 404 now.

MaemoToWindows said:
Anyone has the copy of AT&t_G8.zip? Its 404 now.
Click to expand...
Click to collapse
Always has been.

I have it but it won't let me add it

Can u email it to me? [email protected]

[TWRP] A8M Ported Moto One 5G Ace TWRP (An Experimental Work In Progress)

Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.

Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.

useless789 said:
Hi. I appreciate a lot your efforts. I know the feeling when you progress with stuff like this. I'm sorry I have no time in these months to assist. Anyway, I hope you'll manage to go forward with this. Keep up with the good work.
Click to expand...
Click to collapse
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.

Articul8Madness said:
CAn you at least tell me how to port a TWRP on Android 10? Can't find any useful information with the new filetypes.
Click to expand...
Click to collapse
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?

Articul8Madness said:
Follow the following at your own risk! I am not responsible for any mishaps with your devices. This will NOT obviously work for Verizon, AT&T, and Cricket phones.
Okay, So I've been asking questions, playing, unpacking, and repacking, trying tools, etc. And I got a very experimental port of TWRP happening. VERY EXPERIMENTAL.
THINGS TO KNOW AFTER THE EXCITEMENT DIES DOWN:
For starters, yes THIS DOES BOOT TO TWRP! I'm quite proud about that. This is my first ever port of anything like this. I mostly just fiddle with making bootable stock roms, and not too much since Android 9 and this new nuts file system. Anyway, I set out to try and get a TWRP together for this phone and that happened, so I'm proud of myself I didn't get discouraged.
Having said that, it has ZERO touchscreen functionality. From my research this was also an initial problem for the peeps over at the Moto One 5G Plus variant (Nairo) before they worked out the bugs. Hopefully they will take mercy on us and come give some feedback.
Also, this is a port. I used @Hovatek's Qualcomm tool to accomplish this since unpacking, repacking, copying and pasting a port from Nairo in the Carliv Image Kitchen or Android Image Kitchen just soft bricked my phone. It also doesn't help the traditional porting methods prior to Android 9 don't work anymore. They came up with a great tool, Gawd Bless Em'.
Should you try this for hoots and giggles just know you will have to hard reset. Android will force a factory reset because of the vbmeta flashing, and your phone will be factory brand spanking new. Backup your contacts, pics, messages, and anything else you want to keep just in case.
I'm not going to put detailed instructions on this just yet since it's experimental - this is really for folks that know what they're doing with their phone.
Notes:
You must have the bootloader unlocked and be rooted with Magisk for this to fly. Can't say how this would work on locked bootloaders without root so proceed cautiously on that.
1. Flash VBmeta first. The VBMeta is a blank file and that's to make sure DM-Verity isn't acting up (which as of now I'm 50% certain it is and that's why I had to go ahead and factory reset). The commands to disbale dm-verity didn't work for me. If anybody knows how to get that shut off please add to the discussion.
2. I didn't replace my original recovery. I just did fastboot boot recovery image to see if it would load. I wouldn't advise flashing it to replace the current recovery as it might seriously bootloop.
If anybody wants to try and work on this with me (or take over since I'm a hobbyist at best) then by all means share. But at least now we're getting somewhere, slowly but surely.
Today was a good day in hacking Android 10 on this phone.
Click to expand...
Click to collapse
This is tremendously amazing work. TWRP would be a killer feature with the 5G Ace. Couple that with Lenovo having released the source code, and this forum may get popping again!

useless789 said:
I'm not sure what you mean by filetypes. Do you mean the A/B partitions (and the fact that there's no separate recovery partition) or something else?
Click to expand...
Click to collapse
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.

Articul8Madness said:
I was referring to the super_sparsechunk type files that when you look at their "filetype" it has 0 image by its name if its super_sparsechunk.0, 1 if its super_sparsechunk.1 and the like. This is different than the old basic img files that read .img. This is where the learning curve for me kicks in.
Click to expand...
Click to collapse
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.

useless789 said:
I see. Thanks for the explanation. I'm not sure if this could help, but a quick search on google led me to this (a bit old) video:
I'm really busy until the end of the month so I can't really dedicate my time to this stuff though I would love to.
Click to expand...
Click to collapse
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.

useless789 said:
I see you already tried this here: Post in thread '[Tool] SparseConverter v1.0.1' https://forum.xda-developers.com/t/tool-sparseconverter-v1-0-1.2749797/post-84767377
If I manage I'll take a look at this asap.
Click to expand...
Click to collapse
Any and all contributing help is appreciated!

@Articul8Madness I managed to combine the sparse chunk files into a raw image file. I also managed to mount the image, but only in read-only mode. I'll post with updates as I get passed this obstacle.

Seems the US version of this phone isn't popular enough for dev support...oh well I have R/W access so I was able to delete system app bloatware and I have xposed installed. Stock Reteu firmware is working perfectly on Metro...good luck everybody.. I'm looking for a new 5G phone..

Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.

PEACH-PIT said:
Unfortunately, there are no developers here.
All we can produce is a ported twrp where the touchscreen does not work.
The touchscreen does not work due to problems with the porting tool and the smartphone.
I heard that if you build it from source yourself, it will work.
But I can't find any tutorials for android 10+ and I don't even know what files I need.
Click to expand...
Click to collapse
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.

Articul8Madness said:
I posted the source code. The guys over on the Moto One 5G know what tools you need. I was using Carliv's kitchen to build but I've never built before - they had the same problem as us with the touchscreen and had to make modules. That counts me out because that's above my paygrade, lol.
Click to expand...
Click to collapse
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.

https://github.com/moto-sm7250/android_device_motorola_kiev/tree/android-10
Will this not work?
I do not know how to build it.

fddm said:
Not entirely sure what you mean. If your doing some kind of frankenstein recovery, I'm sure you just failed to copy some module or firmware, obviously the ts works in the official software.
1.) Find out what touchscreen chipset your device uses (you can use kernel log or system info apps or whatever)
2.) Determine which kernel module supports it (all modules built will be in your kernel config)
3.) modprobe that module from adb in your recovery. If it doesn't just work, you will receive some error on the command line or dmesg that you can use to fix it. Could need a configuration file or something, idk. It's likely an opensource module that you can read through and I bet you can find specific info online since your not the first to hit this issue.
If your wondering how to build the kernel, I can help a little, but it's incomplete:
Kernel source:
GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
Linux Kernel for Motorola devices using MSM-based chipset - GitHub - MotorolaMobilityLLC/kernel-msm at MMI-QZK30.Q4-40-52
github.com
Build instructions:
readme/MMI-QPN30.33-40.txt at master · MotorolaMobilityLLC/readme
Readme's for motorola builds. Contribute to MotorolaMobilityLLC/readme development by creating an account on GitHub.
github.com
Snapdragon LLVM Toolchain:
snapdragon-llvm-8.0.6-linux64.tar.gz
drive.google.com
Retail config is on your device:
/proc/config.gz
The instructions don't cover the qcom toolchain, you just take the files here:
snapdragon-llvm-8.0.6-linux64.tar.gz/toolchains/llvm-Snapdragon_LLVM_for_Android_8.0/prebuilt/linux-x86_64/*
and place them here:
$my_top_dir/vendor/qcom/proprietary/llvm-arm-toolchain-ship/8.0/
When building, skip the cat command, and place your config manually to $kernel_out_dir/.config
The step I haven't done is build a device tree. It's not that it's too difficult, I just haven't put in the time required to do it. It's not strictly necessary to achieve for my goals since I only wanted modules and know how to patch the kernel to be able to use them.
Click to expand...
Click to collapse
This recovery I built in this thread I used Hovatek's tool to do. I have never built a recovery and I was hoping if someone got the ball rolling we could get a dev to jump in. That hasn't happened.
The guys with the other variant of this phone said they had to create modules. Go to the Moto One 5G forums and see the thread. They had the same problems too, but they had more dev support than we do.
I have never built a TWRP, let alone from source, so half of what you sent I have no idea what it is or how to decompile it (yet).
I have posted the entire Kernel Motorola released its in the other thread. The Device Tree is official and out on github.

Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.

useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work

Tomspector said:
Is this the correct twrp for this phone?
Root Motorola One 5G Ace XT2113 and Install TWRP Recovery 3.5.0
Easy tutorial to Root Motorola One 5G Ace XT2113-2, XT2113-3, XT2113-5 easily. For rooting, you have to flash TWRP Recovery 3.5.0 on Android 10 through guide.
www.androidweblog.com
Later guys, keep up the good work
Click to expand...
Click to collapse
This is a fake. It's non-functional garbage.
There is no harm in trying it, unless you flash it, but there is no need to try it.

useless789 said:
Guys, I'm a developer, just that I'm still really busy. I'm following your posts and have looked into some of the stuff, just I'm proceeding slowly due to lack of time. I'll post as soon as I have something working.
Click to expand...
Click to collapse
I have a request to the developers.
GitHub - moto-sm7250/android_device_motorola_kiev at android-10
DT for Moto G 5G / One 5G Ace. Contribute to moto-sm7250/android_device_motorola_kiev development by creating an account on GitHub.
github.com
Can you please build this twrp?
I'm trying to build it.
But I don't know how to solve the error.
I don't think I can build it.

Pixel 5 terrible connectivity and dropped calls

I am struggling lately with my P5 that can't seem to manage simple cell to cell hand-offs. My calls are dropped when traveling down well covered roads, and all kinds of weird lacks of connectivity even when getting a strong signal (I keep seeing the LTE icon with multiple bars but a little "x" over it). Sometimes it takes a couple of minutes to regain connectivity to the next tower. Sometimes it seems that I get knocked off a call when a text comes in. Sometimes texts just won't send.
I hate to attempt to do a full reset and start from scratch. I'm running factory 11 rooted with magisk on Verizon.
Is there a way to refresh the modem drivers or otherwise cause a rebuild of the drivers without full reset? Or do you think it's a hardware issue??
Any help would be appreciated.

You have a Verizon device, so the only way to refresh/flash the modem.img isn't possible since you can't unlock the bootloader.
Backing up through Google in your settings menu and factory resetting is unfortunately the way you may have to go. Hopefully someone else replies with something I'm not thinking of.
EDIT: you may be able to make a flashable.zip of the modem.img that you can use with TWRP. I'd like to give instructions, but it's been years now since I've made a flashable.zip for that. Google can help you with instructions.
EDIT 2: You're on A1Q still? Another option would be to update your Android version. It could be the older modem.img is causing some of the issues. Updating you Android version will also flash and update the modem.

xunholyx said:
You have a Verizon device, so the only way to refresh/flash the modem.img isn't possible since you can't unlock the bootloader.
Backing up through Google in your settings menu and factory resetting is unfortunately the way you may have to go. Hopefully someone else replies with something I'm not thinking of.
EDIT: you may be able to make a flashable.zip of the modem.img that you can use with TWRP. I'd like to give instructions, but it's been years now since I've made a flashable.zip for that. Google can help you with instructions.
EDIT 2: You're on A1Q still? Another option would be to update your Android version. It could be the older modem.img is causing some of the issues. Updating you Android version will also flash and update the modem.
Click to expand...
Click to collapse
Actually, I have an unlocked Google version P5, so I believe I can flash whatever I want, correct?

amajamar said:
Actually, I have an unlocked Google version P5, so I believe I can flash whatever I want, correct?
Click to expand...
Click to collapse
Yes.
When I answered yesterday I was busy packing, making dinner and booking a flight, and my answer wasn't totally accurate.
What you need to flash on Pixel devices is the radio.img, not a modem.img.
Download the factory image that matches your current version (you can find this in settings > about phone > build number) and unzip it. The radio.img is in there. It will be named something like "radio-redfin-g7250-00208-220623-b-8759277.img" (<---the radio.img from the last update for August). To make things easier you can rename it to simply "radio.img" instead of having to type that all out. Put that into your adb/fastboot folder, boot to bootloader, and enter:
fastboot flash radio radio.zip

xunholyx said:
Yes.
When I answered yesterday I was busy packing, making dinner and booking a flight, and my answer wasn't totally accurate.
What you need to flash on Pixel devices is the radio.img, not a modem.img.
Download the factory image that matches your current version (you can find this in settings > about phone > build number) and unzip it. The radio.img is in there. It will be named something like "radio-redfin-g7250-00208-220623-b-8759277.img" (<---the radio.img from the last update for August). To make things easier you can rename it to simply "radio.img" instead of having to type that all out. Put that into your adb/fastboot folder, boot to bootloader, and enter:
fastboot flash radio radio.zip
Click to expand...
Click to collapse
Thanks for this. Is it generally safe to reflash just the radios? I take it by your response that it is. Thanks, I'll give it a try...

Question Where are proximity, compass, auto brightness sensors stored in android 12 OOS?

As the title states, my auto brightness, compass and proximity sensors are all broken, I believe this is a failure of a partition similar to persist.img where the fingerprint used to be stored.
Had this issue a while back but I hadn't noticed the compass being broken
I've ran through the tests in engineer mode *#*#4636#*#* and the results are all null for the above sensors.
Factory wipe did nothing, moving between bases 12-13 did nothing, installing a GSI only affected only system.
I'd rather not RMA if I don't have to..
Any ideas anyone??

Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro

g96818 said:
Have you tried installing lineage and then reverting back?
https://www.droidwin.com/how-to-install-lineageos-rom-on-oneplus-10-pro
Click to expand...
Click to collapse
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.

dladz said:
That's a GSI buddy, yes I've installed them all.. but they only affect system so the issues will remain as the partitions that house the sensors aren't affected...
Similar thing happened on the 8 pro with the fingerprint, the perist partition was the culprit.
Have mentioned all this in the OP.
Click to expand...
Click to collapse
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com

g96818 said:
i see. i'm not paying attention to any roms for this phone since there's no msm available to use without paying.
I haven't been followed this thread, but you could try flashing this fastboot rom. I'm not sure if anyone tested it, but the 9RT version worked great to convert COS to OOS without side effects.
OnePlus 10 Pro Fastboot ROMs (and how to make for any device)
First of all and most importantly, I want to say that this is not my work. This is a port of the work done by @abhinavgupta371 and @HELLBOY017 for the OP9RT. I merely made sure there weren't extra or missing files and edited the .bat and .sh...
forum.xda-developers.com
Here's the original post it was built from
[FASTBOOT][ROM][UNOFFICIAL][OP9RT] OxygenOS A.04-A.08 for MT2110 devices
Greetings, I've appreciated @abhinavgupta371, @HELLBOY017 for initial version of this firmware and @penguinus for continuous support and testing. PLEASE NOTE THAT FASTBOOT ROMS CAN ONLY BE USED IN DEVICES WITH AN UNLOCKED BOOTLOADER!!! AND BE...
forum.xda-developers.com
Click to expand...
Click to collapse
Have you used fastboot enhance to flash a rom?
AFAIK it's just a case of deleting the cows then extracting the payload then flashing it in fastbootd

I think the partition needs nuking then rebuilding.
On the 8 pro they used MSM, different ROMs and and fastboot, nothing worked.
Have you any idea where these sensors information is stored? What partition?

Anyone else have any idea?
Finding out where the proximity, compass and auto brightness sensor data is kept would help me

Answered my own question.
It is indeed within the persist partition.
How to Fix Android 10’s Sensors Bug Caused by Corrupted Persist Partition
A step-by-step guide on how to fix the Android 10 Sensors bug caused by corrupted Persist partition, on devices like Google Pixel, Xiaomi Mi A3, and others.
www.thecustomdroid.com

To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working

dladz said:
To fix this is need someone elses persist.img
Could someone extract theirs so i can use it please?
Theres nothing i can use in there i'm just using it as the files in mine are corrupt.
To pull it it's quite simple.
Connect your phone to your computer and open an ADB terminal then type the following
adb shell
Press enter and allow the prompt on your phone if you get one.
su
Press enter and allow the root prompt on your phone
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Press enter, this will put a file called persist.img on the root of your phone, it contains functional calibrated files for auto brightness, fp reader, proximity sensor and compass.
I'm not able to see your fingerprints or anything like that, its just going to be used to restore my device to a functional state.
Hope someone can help with this, anyone who's rooted can do this and it won't affect them.
Cheers
PS: if this works, then we'll have a fix for broken sensors if anyone should run into it, i'm happy to share mine once it's working
Click to expand...
Click to collapse
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.

g96818 said:
it doesn't seem like a file that gets updated during updates since it's not in the payload file. I can send you my vanilla persist.img from the moment i first rooted, but idk if 2215 and 2213 images are the same. AFH is giving me errors again with uploading. I'll PM you a google link instead.
Click to expand...
Click to collapse
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.

dladz said:
I appreciate that mate, thank you.
I'm just updating to A_17
But you're right, it doesn't update it, i've just used fastboot enhance and flashed a payload from A_13, same issue.
It's so horrible man, missing these things isn't breaking the phone but it's really inconvenient.
Click to expand...
Click to collapse
yea it sucks, especially since oppo isn't releasing the msm tools.
hope the file works for you. it came out of my A.10 rom. hopefully A.10 shared more files than just the boot image.

It flashed and did affect the fingerprint but unfortunately didn't fix the other sensors.
Restored mine and my FP is working again but all other sensors are broken.
I think RMA is the only way at this point.

Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.

dladz said:
Just found this.
[Guide] About repairing/fixing the persist partition
Disclaimer: I am not responsible for the results of any of these operations. Everyone knows that the persist partition is responsible for sonsors and carrier network etc. Once this partition is failed or lost, your phone will go wrong. I just...
forum.xda-developers.com
Going to give this a whirl.. I reckon it could work.
Click to expand...
Click to collapse
It didn't..

dladz said:
It didn't..
Click to expand...
Click to collapse
were you able to solve the problem?

crhistiandavidbonilla47 said:
were you able to solve the problem?
Click to expand...
Click to collapse
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.

dladz said:
Nope...still can't use proximity, nor auto brightness, I'll send it back prior to the end of my contract, then sell it..but not until then.
I don't believe there is a fix for it.
Click to expand...
Click to collapse
without a doubt my worst purchase was this device

crhistiandavidbonilla47 said:
without a doubt my worst purchase was this device
Click to expand...
Click to collapse
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.

dladz said:
Haha, try to see the good, you live and you learn..
I've bought some stinkers, Nokia Lumia 800, note 4, Sony Z1, Huawei p20 pro, HTC Evo 3D.
You take the good with the bad.
You'll learn to avoid this problem in future, I'm sure you'll have another problem with a future phone and you'll learn from that too.
Just try to see the good.
Performance is unreal
Battery life is superb
Speakers are great.
Cameras are top notch.
We have root.
We have some mods
We have TWRP
Sure no ROMs but that could change (maybe)
Lot of updates.
RMA is solid.
For most people that above list is way more than enough.
Click to expand...
Click to collapse
Yeah, you are right