Related
I build the AOSP successfully but in my case the microphone is buggy ... everything else is working. Is there Anyone who build it with a working mic? I've build r30 and r32 with the same result :/
I have not yet. Ordered my XZ1c yesterday. Should be here Monday. Hoping for more developer colaberation. Thank You for working on this!
Because of Treble it should be possible to build Lineage OS without interfering with the fingerprint sensor and T-Mobile VoLTE functionality, no?
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
N1ghtr08d said:
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
Click to expand...
Click to collapse
It's still going to be bad. Until we get a proper DRM backup method all custom ROMs will take awful photos.
Issues Flashing Build
Hi there -
If you don't mind me asking, did you run into any issues when flashing the build? I was able to build android-8.0.0_r30 successfully. After flashing android-8.0.0_r30, my phone boots to a screen covered in distorted colors. There is a small message, but most of it is cut off. From what I can tell, it seems that something is corrupt, or so I believe the partial message said.
Did you run into any issues while flashing?
Could you please offer some insight into your process?
Thank you for your time,
Dominic
[Edit]
I am getting the same screen of distorted color after the Sony screen when flashing android-8.1.0_r7.
Before flashing again this time, I went to another machine and used Sony's flashing tool, Emma, to flash a stock Sony ROM back to the device. This allows me to boot to what I assume is Sony's most current build available. The phone boots no problem this way. I decided to try another flash.
My specific steps for flashing post build:
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_yoshino.img
[Edit]
I am able to successfully use Sony's Flash Tool, Emma, on a separate system to get the phone booting to the stock ROM. Emma shows the following under Software:
Application Software:
1307-7511 47.1.A.8.49
[(Delayed) Edit]
I rebuilt AOSP from source and was able to successfully boot into the OS after flashing the partitions.
Maybe a corrupt image was generated during the build process.
Either way, I am updating this in case anyone else comes across it. Downloading the source and rebuilding it resolved the issue.
Hi guys,
I have a sunmi v2 android PDA, and i want to remove blocked OS.
I can't find bootloader, or i dont know how to enter on it, also i want to install a recovery mode to flash a new ROM.
Someone can help me please with this problem?
Thank You.
Hi, I have the same problem. Did you find a way to do it?
Can you tell me please?
Thank you
I have V.1.. Firstly, are you guys able to allow installation of apps from "Unknown Sources"?
Just wondering if you ever managed to load android onto the V2 and remove the Sunmi OS? I have managed to enable dev mode and allow untrusted sources but on installing google play services and store all I get is crash reports and have to factory reset.
Thanks
J
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
wesleybr90 said:
Can you tell me what you did to install apps from untrusted sources? and what progress have you managed to make?
Click to expand...
Click to collapse
To enable untrusted sources I had dev mode on but under security > device admin > unknown sources. I don't know if you need to enable dev mode to turn that on but if so go to about > build number > tap until it enables. I'm not really a software guy and was hoping someone on the internet would have a solution to rooting the device and maybe ADB it, I did ask a software engineer friend of mine and he did some research on them, these things talk to Sunmi's servers on boot with the current FW so they are heavily locked down, so progress wise for me is it's been in a drawer since January and I'm hoping someone will have a way to root the thing :S
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Noob Sailbot said:
So I have no idea about Android things but I bought secondhand Sunmi V2 that is locked on Glovo aplication.
For the last week I managed to do some research about that:
1. The thing runs custom OS with some kind of recovery-from-boot.p thing that prevents most of modifications, cause after reboot it reverts some system things.
2. I tried to use SP flash tool to do full backup, made mine scatter file and thing I have no idea about
3. Managed to download TWRP recovery to device recovery partition with use of SP flash tool, this did not do anything and the thing booted to Phoenix recovery as normal....
4. With the help of WWR 2.51 I managed to install applications on it...
5. Installed Kingroot, didnt do anything, installed, APKPure, works nice, Magisk, dont know how to root...
6. Tried installing google play, it says it is installed, cant uninstall it nor open it...
7. Can't and don't know how to enter fastboot...
8. I am afraid to flash complete ROM from some other same chipset device...
9. After powering up, Sunmi connects to its own server and does some kind of evil magic to preinstall software and settings.
10. I contacted Sunmi, they kinda don't want to help, cause I will resell device after unblocking it.
11. Fount "that guy" from youtube that does unlocking it, on the minus side he wants money for unlock... and from his videos he flashes complete EMMC_USER bin to device to unlock google play.
Do anyone know which steps can I take further to try to unlock it by myself?
I have some spare time at work to do this kind of playing around.
Update:
I managed to extract system.img from device and I am able to browse files on it, the plan is to see can i change some files and setting in it and reflash it back to device. This is all overwhelming to me as I have no experience in android development.
Click to expand...
Click to collapse
Thank you for the update, Im following this thread to see how this goes. Im trying to unlock my Sunmi V1 too
I managed to brick it, stuck at boot looping... Somehow I redownload boot and system from my backup with SP flash tool and got it working back again...
So I tried using ASSAYED Kitchen and remove some Bloatware, rebuild it, and upload it back to device, used two files: System.img and boot.img... This bricked my device.
What am I doing wrong? This must surely be my error. Do I need to do something to recovery partition?
UPDATE:
Managed to install custom recovery TWRP, made it myself using Carliv Image Kitchen
UPDATE 2:
Even thou TWRP seems working, It does not mount any partitions: /data, /system... Invalid argument...
Does anyone know how to fix it easy way? because I cant find too similar custom TWRP to Sunmi...
Any custom system.img that I flash with SP tool does not want to boot, never, and even if I only open ASSAYED Kitchen, do nothing and repack it. Is the only way to install it with TWRP?
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Noob Sailbot said:
BIG UPDATE:
I have done 99% of the job!
I could write full from zero to hero tutorial for this, but basically I used TWRP to recover /data/system/users/0/package-restrictions.xml and edit it as I pleased and unlock google play.
Click to expand...
Click to collapse
I am also looking forward to the results you have done
So amazing!!
I am slowly loosing interest in this. Whatever I do it is just endless loop...
When I modify package-restrictions.xml and settings_secure.xml files I got GooglePlay and Maps and stuff, but first time you connect the device to internet, SunmiBaseService overwrites them with options used for this DeviceID.
I renamed this SunmiBaseService to something else, got this working, but then since the whole thing runs on this sunmi backbone you can't install any apk's. I can normally install apks using USB and enabled BaseService.
It would be best if I could have just normal Android on this thing since it is unusable if you block BaseService, and if you would do any system upgrade on some point in time it would overwrite and install this service by itself. Like I said, it is endless loop. Even after contacting sunmi my region cant't have this for private use.
I can provide all files used in this process, my scatter files, my TWRP recovery and else...
The question is is it possible to port clean Android to this device, like we install new windows on a PC?
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Velcis Ribeiro said:
Hello guys, any news for Sunmi? I got one, but i wan't to remove the OS, or enable Play on it.
Click to expand...
Click to collapse
No, I tried everything I know. Only thing that I did not do is replacing sunmibase service with some kind of android base service or paying some youtube guy 20$ for unlocking, but I doubt it would work correctly. Couse after you, in some point in time, update software or something I highly doubt it would work after that.
{Mod edit: Quoted post has been deleted}
I am going to upload files that I have, but I need few days to do so.
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
Can you share the files again please, the links don't work anymore. Thank you
My buddy has toast loaded on an old device and was looking to replace the os so his kid can use the tablet. Sunmi t2
Noob Sailbot said:
So here are the files:
Original image downloaded from device:
Code:
https://mega.nz/file/G6R0mJ4K#rWNDGzWyerP68Pp0o9KCKj92wx_yzLgoJ98vccPgXaQ
Modded boot.img and recovery.img with TWRP (only thing that I did not configure in TWRP is vendor partition, but most things work:
Code:
https://mega.nz/file/WvgECC5a#WiIWe00gsc-TcjvwMgfX6sQc9B5zElvuu34hbUVOR0E
Scatter File:
Code:
https://mega.nz/file/7npzTSLJ#pfK7G4aB5EDKuY17UrJdNrcwzeiVt3dJnegKqUIJRkc
All other files that I have are some moded that I have tried to get it to work but did not have luck in making it usable, if any more files some of you want I can also upload them but this is part that work.
Click to expand...
Click to collapse
I am after these files also if you still have them
Would it be possible for you to re-upload the files?
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.
Ok... So while I acknowledge that this post isn't 100% about the OP 10pro ... It will have some impact if solved.
Basically I've found it... I've found out how Oppo is locking or removing the ability to unlock the bootloader of ALL of their phones that suffer from this. (Specifically the OnePlus 10T T-Mobile)
And realize that by helping solve this, I will be able to locate the file that is bricking all of our devices , when flashing different region fw.
(I said I wouldn't rest til I found it, and I have!).
They are simply appending the executable that launches the "Fastboot reboot bootloader" command, with an additional comment which adds another Reboot to the command.
So the phone basically receives "Fastboot reboot bootloader reboot" when we try to access it from adb.
(They made it so that simply invoking the word bootloader will trigger this to happen automatically and without any way to break the command up....)
^^ This function has a flaw though... Which is :. They put the instructions for where the command gets it's orders DIRECTLY into the android build properties. Which means it can be removed from the build prop and restore full functionality to the Fastboot protocol.
The problem lies in that there is no way to edit these properties without root access.... No bootloader means no root... And no root means no way to edit build properties .... This is something that I need your help with!
I know there are a plethora of devs and even tinkerers here who knows tricks to mitigate the security in order to write or amend the build.prop without having root ... I know that SOMEONE here might have a method that can do this. If someone is willing to offer that knowledge, they would be a god in my eyes and a savior to several ppl with an Oppo device that has no way to unlock the bootloader. I have checked several devices and this is the same method used on every one that has a "permanently locked" bootloader. It is just a few lines in the build properties that is disabling this.
Please help.... Pictures for proof of my discovery at bottom.
If you can find a way to edit these lines please dm me, or reply here... But please contact me!
Also be aware that Oppo has spies who pose as regular members on our site here, so if you are someone who might be interested in whatever solution comes about... I would highly recommend that you do not update your fw past the version you are on now. This goes for both Oppo and OnePlus users , because within 3 days of me revealing the method to switch region fw, OnePlus patched and removed the vulnerable rollback packages. So now that this has been brought to light, no doubt there will be a security update available within the next week or so, that has nearly nothing written in the changelog, but has the sole purpose of further hiding/blocking access to these settings.
This has ultimately been the reason I won't be purchasing the OnePlus 10 Pro, a Pixel is way superior at this point, however I will offer some advice.
Have there been attempts to use the QPST to overwrite partitions? I always thought that if someone made an MSM Tool with, for example, LineageOS in place of the partitions, that perhaps one wouldn't need to unlock their bootloader? Of course, the file would have to be encrypted the way that OPlus does it, but I thought it was plausible? I tried, but failed because the tool I was using kept not encrypting the files I was selecting, it only included a few in the final package.
I digress, I'm aware of someone saying that the partitions are different with the OnePlus 10 Pro, but would it be possible to kind of work backwards to reach the goal using Fastboot?
hammerhaigh said:
This has ultimately been the reason I won't be purchasing the OnePlus 10 Pro, a Pixel is way superior at this point, however I will offer some advice.
Have there been attempts to use the QPST to overwrite partitions? I always thought that if someone made an MSM Tool with, for example, LineageOS in place of the partitions, that perhaps one wouldn't need to unlock their bootloader? Of course, the file would have to be encrypted the way that OPlus does it, but I thought it was plausible? I tried, but failed because the tool I was using kept not encrypting the files I was selecting, it only included a few in the final package.
I digress, I'm aware of someone saying that the partitions are different with the OnePlus 10 Pro, but would it be possible to kind of work backwards to reach the goal using Fastboot?
Click to expand...
Click to collapse
well kind of... now i invite anyone to correct me here if i am stating something wrong, but it is my understanding that QPST/QFIL cannot write to individual partitions unless the instructions are defined in the rawpartition.xml, and patch.xml files.... because those are what the firehose loader parse to get the layout of what needs to be written to the phone. Like the partition tables are in the firehose i think, and the stuff that goes into each are in those xml files....
now if im correct then thats not the deal breaker... the deal breaker comes in the Firehose itself. ANY usage of a qualcomm flash tool, whether it be QFIL, QPST, MSM or any other, all require communication via a Sahara_Firehose... and in that sense, we dont have a Qualcomm Patched Firehose yet. So the firehose that comes in the fw packages has a security function called VIP mode built in, which performs some on board checks to validate the fw signature.
For this very reason, having Fastboot access sit on top of the throne for methods in which to mess with anything fw related.
Oxygen Updater - Has no direct flashing capability, only the ability to download any official OTA fw.
Local Update - Can flash pretty much anything, as long as it is in Payload.bin format, and the hash . . . . . . . .. . . . .. .. matches a valid package
System Update - will ONLY flash a package that is downloaded directly thru it, which eliminates customs.
Fastboot - Can flash payload.bin, or if the bootloader is unlocked it can flash individual .img files. Thus . . . .. . . . . . . .making it the most powerful tool we have at our FREE disposal.
With fastboot, and a flash of VBMeta, to disable Verity checks, along with "Unlock critical" , you can pretty much access every partition in the system without limits... and also this is the only way to gain root access, which as we all know is the MOST powerful of elevations, Writing anything TO the system partition requires a remount to R/W of the system partition, and that simply cannot be performed without Root.
So technically, fastboot access is the only thing we have that can give us a tool (root) with the freedom to make persistent changes to any partition on the device.
Since the edge 30 fusion is not on xda as a forum i thought i try it here,
i wanted to install magisk so i can change some stuff with gravity box etc. I came to understand that if i want my phone to be able to update i should not install a custom fw so i need to patch the boot image. But i need to have the same boot image as my device but i could not find it on lolinet.com. I kinda don't know which of the 100000 Versions of my phone i should get. My phones version is S3JS32.1-86-1.3. Where do i find that? is there some place else than lolinet? I've read somewhere that i can extract my own boot image but don't know how and if it is even necessary.
How do i do this?
Download and install RSA (Rescue and Smart Assistant) from Lenovo's site. If you connect your phone via USB while RSA is running, RSA will list the correct firmware for your phone in its downloads tab. Download the firmware to your PC hard drive and then open the file and extract the boot.img file. That is the file you want. Just make sure your phone is up-to-date with its firmware or else you may be downloading the upgrade firmware and not the firmware that your phone is running. You can compare versions through the RSA software.