Database Develop

Hydrogen OS 2.5.1 to Oxygen OS 3.5

Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:

logansrun24 said:
Hi everyone,
I literally just got the Chinese version of the oneplus 3T (A3010) and I want to move from Hydrogen OS 2.5.1 to Oxygen OS 3.5 official with OTA. Does anyone have the file or instructions how to do this? I found instructions for the oneplus 3 but not sure with this model. I'm sure any help would help out a lot of people who are gonna ask this question.
Also will this unlock the bootloader? Just curious about it affecting android pay.
Thank you!:laugh:
Click to expand...
Click to collapse
Wanna do me a favor and grab a nandroid backup of your rom before you kill it? I actually want h2os
Aside from that, you should theoretically be able to: ("Official" guide https://forums.oneplus.net/threads/...oid-efs-backup-and-more.475142/#post-15431571)
Unlock the bootloader
Flash TWRP
Flash dm-verity
Flash OOS 3.5.3 from the ROM page, I have a mirror too (http://forum.xda-developers.com/oneplus-3t/how-to/zip-flashable-firmware-modem-t3509015) mirror on pg 2.
and you'll be set, you can flash the original recovery if it's available on the OnePlus page as well and relock to go back to full stock just English version
PS: Since there is no stock recovery image available yet, maybe will have to run TWRP temporarily, rip the recovery off and then proceed? I dunno

Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.

Well you can try flashing the image straight. It's a stock image anyways so it could work.

logansrun24 said:
Thanks for your quick reply! I was hoping more along the lines of the adb Sideload method and keep the bootloader locked for now though. If I go the root method sure I can share the nandroid backup.
PS the rom looks really similar to the oxygen rom, so far it looks like only the launcher is different. I guess this is part of the plan to merge the two.
Click to expand...
Click to collapse
Basically what I meant was to do the opposite of what is suggested here http://forum.xda-developers.com/oneplus-3t/how-to/rom-h2os-2-5-oneplus-3t-released-t3511443 but with the 3.5.3 ROM

Help needed with android pay and OOS clean install
I'm in a similar situation with a chinese bought OnePlus 3G from Lazada.sg that came with Hydrogen OS. I've managed to install TWRP but because I'm completely new, got stuck and instead managed to install OOS 3.5 (now 4.## from the official website) using adb sideload.
I do have 2 questions:
1) My internet connection drops occasionally even though my WiFi is still connected, is that an issue because I might not have installed it correctly? Would a clean flash solve it?
2) I understand android pay is disabled when you unlock bootloader but even after that, will it be possible to wipe the phone clean and do a fresh install of the lastest OOS and the phone will pretty much be like the international version, with android pay re-enabled?
I believe you can use Sultanxda's patch as another way around, but it sounds complicated as hell for a new person, so I'll continue digging around while waiting for a reply.
Thank you, and any advice will be greatly appreciated.

Searching V405EBW owners for TWRP/ROM tests

Hello everyone
Some might know me from the V30... Also got my hands on a V40 now (which I will also give my best to develop for).
I'm currently searching for people who are capable AND willing to test different things.
With that I mean:
- You know how to take logs (logcat, dmesg)
- You know how to recover from a soft brick (either how to get into TWRP for example, or in really bad cases fastboot or flashing a kdz)
- You know how to follow orders
I currently have a (somewhat decendly) working TWRP build (cant decrypt stock encryption atm).
GSIs are a complicated thing, because of not only vbmeta but also because of our 8.1 vendor (Pie GSIs work, if you remove some sepolicies from their system, Oreo GSIs dont have that issue)
What I would need more people to test for:
- stock decryption
- trying out different ways when something (doesnt) boot (e.g. need to flash magisk for xy to not crash to fastboot)
and so on
After everything is somewhat stable (I had to reflash a kdz today, as somehow nothing, no twrp in either slot, or restored stock rom didnt wanna render anything anymore, even though usb/adb worked just fine)
Also working on LOS for this device btw (but thats far more work in progress)
If you wanna be part of this upbringing, reply here, and I'll message you via PM the details.
PS: Having Telegram would be very beneficial.

I volunteer for this. Happy to see you step up for our forgotten device.

How did you reflash the KDZ?

I`m also interested in testing.

onslaught86 said:
How did you reflash the KDZ?
Click to expand...
Click to collapse
In my case i used LG Bridge, at first it complained that MTP wasnt running, but after clicking a few times ok it was fine with that lol
but i read in another thread that a lgup_cmd is able to flash kdzs to the v40

I think I can participate in the test, I have a V405US ROOT phone。
Please forgive me for my bad English. :）

In +1

Hi, how you rooted LG V40?

Any movement on this?

Evilmonstertruck said:
Any movement on this?
Click to expand...
Click to collapse
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.

SGCMarkus said:
Camera/Fingerprint have issues so far.
Camera tries to load libraries it has no access to (because treble restrictions, so that also shouldnt work on stock, LG did some tricks there again i guess).
Fingerprint loads, log looks normal (same as on stock) just that it stops at one point without error or anything else.
Would use the prebuilt vendor, if it wouldnt have issues with Pie, thats why im building my own currently.
Other than that, havent had much time in the past 1-1.5 weeks.
Click to expand...
Click to collapse
Any update is a good update. I appreciate all the work your doing. I know it's not easy. Thanks again

I can test out twrp and or ROM! Best regards.

Need help, stuck in fastboot?

Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Edit 3: Okay so new issue, everything is all good TWRP is installed phone is rooted, but im trying to update to the latest MIUI 10 version (on MIUI 9 atm) and i can't install it? It downloads fine but it wont install? Do i have to flash the update file since it wont update through the updater?

JasonBjorn said:
Hey all, so yesterday i got my phone stuck in a "boot loop". I was trying to install TWRP and magisk to root my phone, after 2 hours of constantly reinstalling TWRP i finally got it to work. Every time my phone would end up just being on a black screen not being able to get to the TWRP menu but i could still access fastboot, i fixed it by "installing" orangefox TWRP, it never actually installed it but i got back into my phone at least, however now thats not working, and im stuck here only being able to get into fast boot. I followed this tutorial - https://forum.xda-developers.com/k20-pro/how-to/guide-redmi-k20-pro-unlock-root-t3974127. When i eventually did get it to install TWRP its because i used the All in one tool. Im currently stuck in the loop again, all i did was follow a youtube video on overclocking my display to 81hz, so i was in TWRP, made a backup of a file, flashed the 81hz.img and now i cant get into twrp or my phone.....How do i fix this?
Im currently flashing a stock rom with MiFlash, taking a few minutes but this is the last thing i can think of to fix this, no im not using the flash and lock method.
Edit: So i decided to use the All in one tool to flash the rom instead, i can now get into TWRP but the phone still by default boots to Fastboot, it wont actually go into the phone? What do i do?
Edit 2: Okay so that fixed it, now to reinstall TWRP with the all in one tool and reroot my phone.........
Click to expand...
Click to collapse
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.

Robbo.5000 said:
A bit of advice.
If you don't know what your doing, don't follow random YouTube videos.
There are some very good videos and some very bad videos. If you don't know what you're doing, you won't know the difference between a good video and a bad one
Until you're comfortable with flashing mods, etc. stick to advice given here. It might not be instant, but you'll get good advice (if it's not good advice then someone else will point that out).
When asking for help give us more info.
What phone do you have?
What ROM was on the phone before first trying to install TWRP?
What version of TWRP have you been trying to install?
Why did you change from using Mi Flash Tool to the all in one tool?
Did you wait for the Mi Flash Tool to finish but it didn't work, or did you get bored of waiting for it to complete and cancelled it?
I appreciate this is a bit late now and not necessary as you've eventually sorted it yourself, but giving the info I've pointed out, at the time, may have actually got you some useful replies before you actually got there yourself.
Click to expand...
Click to collapse
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?

JasonBjorn said:
I have a rough idea on what im doing i've done all this stuff before loads, but xiaomi just seems to be different idk. Considering this is the k20/k20pro section i assumed its obvious thats what i was using.......Everything is sorted like i said but i cant get MIUI to update, it downloads, i hit reboot and it boots me to TWRP instead of installing the update.......i've come to really like the MIUI without the app drawer but now i have an app drawer as im on Android 9, I flashed the lastest rom but before flashing i didnt have an app drawer and was on the latest build so no idea whats going on there......guess i just have to live with this now?
Click to expand...
Click to collapse
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.

Robbo.5000 said:
What's not obvious is whether you have a Chinese or Indian K20 Pro, or a global or European 9T Pro. Also whether you're trying to install the version of MIUI that is correct for the phone, or if you're flashing from a different region. As you say Xiaomi does things a bit different, so we're seeing things in these forums that what works on one version of the phone doesn't quite work on another.
Click to expand...
Click to collapse
well heres the weird thing, i bought the EU version of the phone, which i know is supposed to be the 9t pro, but not only did the site call it the K20 pro, but in the settings its model number is also the K20 pro. I got everything working fine.

[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.

Question (Q) GSI images

Have never needed to install a GSI before but as we're kind of stuck here without a single custom ROM, I thought I'd have a look.
AFAIK installing one of these would still leave the door open for stock recovery to be used should something go wrong, so as long as you've made a back up it should be fine.
I'm just curious as to the method of installation?
Has anyone had any experience with GSI ROMs before.
How was it? Did it work?
Would DSU image loader be an option?
I've attached what treble version we have and the relevant info required from the treble info app.
Apparently we have VNDK compatibility, not sure what that is but we have it.

Hi @dladz, I ran into a similar question three years ago when I bought a Xiaomi Mi 8 Pro. I was so used to using custom ROMs that I didn't even check before I bought it whether any custom ROMs would be available.
I was honestly shocked to see that that wasn't the case - there was absolutely NOTHING available - and that I had ended up with a device that couldn't even be unlocked right away, you had to wait and open a Mi account to be allowed to unlock it. I couldn't believe it at the time, I had come from a OnePlus X and had helped others root and install custom ROMs on other OnePlus phones without any problems, so I felt like I had just thrown quite some money out the window to run around with a mobile Chinese Spyware gadget I didn't want to use.
That was the first time I ever came across the term GSI ROM and it took me several weeks to figure out how to flash a ROM that I could also use afterwards. I knew I wouldn't want to have a stock ROM by a company that has very loose data privacy standards and even clearly states they collect your data (Lesson learned, I thought, I just had to buy a "proper" phone again and no more phones from budget manufacturers).
Several weeks later, after I had finally managed to get a custom GSI ROM working on my device I posted a lengthy how-to here on XDA.
Again, it took me weeks to get everything to work that I could not go without. And even then, I had to resign to the fact that many features of the phone would not be working (The fingerprint sensor, for example. Also, the Xiaomi Mi stock rom apparently had excellent GPS support (dual GPS support) but GPS positioning is just alright on the GSI ROM I'm using, also there were many cool Xiaomi apps like a compass app that wouldn't work outside MIUI). But I was more than happy I had gotten different GSI ROMs to work in the end and settled on one that I could live with, knowing my phone wouldn't be sending data to some Chinese servers constantly.
Now that the Mi 8 Pro has become a bit slower over time with all the latest apps, I took the plunge and spent a ton of money on the OnePlus 10 Pro 256 GB version only to be disappointed again, but this time by a company that used to be the epitome of openness when it came to custom development.
I got my OnePlus 10 Pro on release in my region in April, together with the 50W wireless charger and both have been sitting here since April, I'm not touching that phone until I can remove all the Spyware it comes installed with. At this stage, I'm not yet willing to go through the weeklong trial-and-error again that it took to get the Mi 8 Pro running a custom GSI ROM (also considering that some of its features never worked...), but if OnePlus doesn't get its **** together soon with the MSM tool and some openness towards developers, I will seriously just consider selling it on eBay again (It is brandnew after all) and will never buy another phone from OnePlus again. This has been an extreme disappointment and I'm still struggling to understand why they wouldn't support custom development any more. I had checked the OnePlus 9 Pro threads on XDA just to see if there's still custom development going on for OnePlus and it seemed everything was still OK, but now... .
On a more positive note: The Mi 8 Pro did eventually get some custom ROM love and there are now several ROMS to choose from, so to answer your original question - If you ask me, don't bother with GSI ROMs until we can be sure there won't be any custom ROMs for our phone. I'm still hoping that will be the case.

Gsi will work but no fingerprint or faceunlock.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"

MrScarl3t said:
Gsi will work but no fingerprint or faceunlock. And many more visual glitches.
Installing is easy just reboot to fastbootd open device with fastboot enchanted and delete all _cow files and reboot too bootloader flash stock vbmeta with
"fastboot --disable-verity --disable-verification vbmeta vbmeta"
Download gsi that you like and flash it in fastbootd using "fastboot flash system gsi.img"
Click to expand...
Click to collapse

Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro

MrScarl3t said:
Gsi will work but no fingerprint or faceunlock.
Click to expand...
Click to collapse
Unless someone posts a step-by-step guide with screenshots of a successful flash, I wouldn't believe anything.
This sounds more like it:
Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .

yo-less said:
It took me weeks going back and forth, going back to stock and retrying again before I had any luck at all with my Mi 8 Pro.
Theoretically, it should work, but you can easily hard-brick your phone if you take one wrong turn and then goodbye to a phone with a premium price tag and no open MSM tool available... .
Click to expand...
Click to collapse
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k

Twiggy000b said:
Yeah was not happy said screw it and went back to google at least ive got lineage os now lol but still what a waste of 1k
Click to expand...
Click to collapse
Did you try sending it in?

I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.

nah i reached out and oneplus never got back to me.

sorry to hear that :/

Twiggy000b said:
Well... I tried GSI and some steps and sure enough I broke my phone (hard brick) so now I'm on Google 6 pro
Click to expand...
Click to collapse
What phone was you on mate??

MrScarl3t said:
I'll make a guide just like I did with the Xiaomi 11t pro. Post it within a week
Already did it when I got the device but I use the fingerprint alot so not for me.
Only tricky is reflashing system when you want to go for stock again.
Click to expand...
Click to collapse
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.

dladz said:
That would be great, I'll be your test subject, I can live without fingerprint and face unlock.
Think the camera might be a bit meh but maybe I can live with that.
Another odd thing is I got treble check and it said I cannot use treble ROMs?
No idea if that's true but that's what the app said.
Click to expand...
Click to collapse
Yeah camera is gcam but the main sensor is fine with it.
Every OnePlus 10 pro works with gsi, and general boot images as well. I will start tomorrow making the guide.
Will test if you can use rollback zip to get back to stock

Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/

MrScarl3t said:
Here you go https://forum.xda-developers.com/t/how-to-flash-a-gsi-on-oneplus-10-pro-t.4479429/
Click to expand...
Click to collapse
Legend