Related
Hi together,
since my new phone is pretty new, there are no real custom ROMs available at the moment.
I'd stick to LineageOS, but i prefer to stay with stock rom when xposed would be able to run on my Mix 2
I've understood:
-> root first
-> flash zip file with framework
-> install apk
-> add wanted modules
Okay, root seems to be a bit complicated now since there might be a TWRP image, but this is only available in some russian forums, where the registration gets a bit difficult with the captcha
But when rooted, what to flash next? arm or arm64?
The Oukitel Mix 2 has a Helio P20 (en.wikichip.org/wiki/mediatek/helio/mt6757) which is ARMv8 which can run 64Bit.
After some issues with the one TWRP availabe, finally fixed and found out that only Magisk seems to work at the moment.
(and it is a good idea to have the actually published system image from Oukitel available, fastboot flash system system.img saves hours )
When updating Magisk, my answer is solved: arm64, now flashing xposed-v89-sdk24-arm64.zip
Lonesome Walker said:
After some issues with the one TWRP availabe, finally fixed and found out that only Magisk seems to work at the moment.
(and it is a good idea to have the actually published system image from Oukitel available, fastboot flash system system.img saves hours )
When updating Magisk, my answer is solved: arm64, now flashing xposed-v89-sdk24-arm64.zip
Click to expand...
Click to collapse
Wait what did you flash? I got the TWRP 3.2.1 from pablo but what afterwards?
Note:- Credits To this guide goes to {Diablosss}
GUIDE FOR UNLOCKING BOOTLOADER OF MEIZU PRO 7
(Sorry for the inconvenience, but there are some issues in posting pictures. Therefore requesting you to please check the attached files for images)
This guide can also work with many other Meizu devices. Checked on 15, 16 all options (s, t, x) and on Pro7I post the archive and instructions in pictures.
Step 1: Download. Unpack. Run meizublunlocker.exe
meizublunlocker:-https://drive.google.com/open?id=1yEm_vZo4rsqEtii279AU6l1mBajiSPQ2
See Image 1 in Attachments.
Step 2:-We connect the phone to the computer in fastboot mode (hold down the Vol. Down and power buttons), click refresh. The program must identify the device.
See Image 2 in Attachments.
Step 3ress CheckBL to check bootloader status.
See Image 3 in Attachments.
Step 4:-Click the Create Request button. This will create a file with the end of req.dat in the folder with this program
We send it to the e-mail [email protected] and wait for the response file to unlock the bootloader.
(This takes usually 1 week to receive the unlocked file, but you can donate to get the file within 3 hours)
See Image 4 in Attachments.
Step 5:- After we received the unlock file with the end of res.dat, click UnlockBL and select the resulting file.
See Image 5 in Attachments.
If the file is correct then get this answer
See Image 6 in Attachments.
That's It. We successfully Unlocked the Bootloader.
Now the next thing is to install the TWRP in our Device. ( Further credits goes to{ sergpolov} )
Step 1: Download and install "adb_run"
adb run:-https://drive.google.com/open?id=1y4wdL53-P7mybKsj5XeimHRoMSpokMkQ
Step 2:- Download the required Files.
Stock Recovery Pro 7:-https://drive.google.com/open?id=1e2tRdqLi5jsT8J854RMcIA-jvZyR7xhT
Twrp Pro 7:-https://drive.google.com/open?id=1uYOT9HGractYuoJvRidgAgh8IBLhzFtu
Step 3:-We load the phone into fastboot mode, flash through the fastboot the recovery you need.
Launch the application shortcut
Step 4:-Click "3" - go to fastboot mode
See Image 7 in Attachments.
Step 5:-Click "3" - recovery
See Image 8 in Attachments.
Step 6:-Here we select the recovery file: - in the window that opens, we throw the file itself and close the window with the file and press any button.
See Image 9 in Attachments.
The process has begun.
See Image 10 in Attachments.
Step 7:- Choose "Y" and "Enter"
See Image 11 in Attachments.
The recovery firmware process is over!
Next Few Steps are Extremely Important , so follow with caution!Step 8:-Reboot into Recovery Mode(hold down "Power" and hold, as soon as the screen goes blank, hold down the second button "Volume +" - hold it until vibration and release "Power", and after it release the button "Volume +")
Step 9:-To disable encryption of the "Data" section (who installs TWRP), we immediately flash the zip archive - tool-root_unlock-Testing-Pro7.zip
(disables encryption of the "Data" section, disables Boot and Recovery checks, installs Magisk and disables system root) and reboot into the system.)
tool-root_unlock-Testing-Pro7.zip:-https://drive.google.com/open?id=1a3Gyyuoo2Jv3EN7EWPwj389tXorSwkxT
Attention ! When installing custom recovery (TWRP) on your device, for the full TWRP functionality, you should format the internal memory (Data section) of the device using TWRP itself, since the "Data" section on Meizu smartphones is encrypted, I highly recommend it before installing custom recovery , on creating backups using the internal Flyme firmware (after creating the backup, it is located in the "backup" folder of the internal drive), as well as copying all the necessary data from the phone’s internal memory to the computer!
NOTE:-No One shall be responsible to any damage ocurring to your device
Doubts and queries are welcomed .
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
XRed_CubeX said:
Hi, but doesn't this only work on Qualcomm processors? How does it work on a Meizu Pro 7 which is a Mediatek? I tried it on my Meizu M5C and it doesn't work.
Click to expand...
Click to collapse
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
adityadhage said:
Yeah you r right and this guide is also taken from meizu 16th only, but this is tested now because qualcomm devices requires port_traces.txt and unlocked bl.bin files whereas for pro 7 we are using to res.dat which uses fastboot driven commands only.. Thats why it got successfull. I am also posting pictures for proof. (Shared by diabloss).
Click to expand...
Click to collapse
But then for other MTKs like M5C it will never work?
XRed_CubeX said:
But then for other MTKs like M5C it will never work?
Click to expand...
Click to collapse
i know you have already tried this method with your device and it didnt worked. I am not sure that m5c will get another method in future or not. Bcoz we also got lucky with pro 7 that it got successful by the help of guide ported from Meizu 16TH a Qualcomm device.
its now per donation only.
spiramedia said:
its now per donation only.
Click to expand...
Click to collapse
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
cris2d2 said:
In this TWRP, could we install anny official ROM (Global or Chinese) in it's standard form (update.zip)? Or some file modification in the zip archive is required?
Click to expand...
Click to collapse
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
adityadhage said:
Some users reported that they can directly install the official update zip. But i would recommend you to modify the updater script before flashing. You can request your firmware to make it TWRP flashable we can help you with this.
Click to expand...
Click to collapse
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
cris2d2 said:
Well, it would be nice if some very talented enthusiast developer or team of devs would build a custom ROM based on Android 8 or higher (if it's possible, of course).
I saw there is single custom ROM, AOSP, but it's still based on Nougat, like stock Flyme. This makes it uninteresting for me, because it brings nothing new over already very-good-full-of-options Flyme ROM based on Android 7.0.
Maybe time will bring us custom ROMs based on a newer Android, at least Oreo.
Click to expand...
Click to collapse
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
adityadhage said:
theoretically its not possible to update android version.. Because we dont have the source code to develop a higher version kernel .. But still there is a hope to port a rom based on android 8 but cant sure for stability.
Click to expand...
Click to collapse
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
cris2d2 said:
I remember that Lenovo P2 smarthone officially stopped at Android 7 but people could install different custom Oreo, Pie and Q ROMs. This means that Lenovo published the source code?
Click to expand...
Click to collapse
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
adityadhage said:
Lenovo P2 is a snapdragon device. The source code and device tree can be found easily. Unlike mediatek , snapdragon never hides such things that's why the development is high on SD devices. Mediatek released kernel sources till Helio p10 then never disclosed anything. For higher android version roms we have to port kernel to higher version. Meizu pro 7 is right now on 4.4.15 kernel ver. For higher version we need kernel of 4.4.15+. I hope i cleared your doubts.
Click to expand...
Click to collapse
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
cris2d2 said:
So, it's all about the source code, kernel sources and so on.
From my point of view (and my knowledge), there are two major steps or two issues that need to be addressed to successfully develop ROMs and kernels for a phone:
1. As you said, the source code must be released publicly.
2. The bootloader must be unlocked (or easy to unlock), for all these mods and kernels to be installed through a custom recovery (IF a custom recovery is developed).
Please correct me if I'm wrong (I'm seeing these things from consumer/user point of view, not like a programmer/developer/coder).
Click to expand...
Click to collapse
basically you are right
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
deathbreath2010 said:
Thanks for your work. I got the Pro 7 X30 Variant. Anyone tried the guide for this version? Maybe i will try it anyways.
Cheers
Click to expand...
Click to collapse
this guide is now updated and guranteed to work with x30 also
follow this
https://www.youtube.com/watch?v=Rnuf-uNBnYA&t=319s
adityadhage said:
i am not sure about this but yeah 5$ is not a big cost for this. Like sincerely there is no other verified method to work and unlocking bootloader gives u many advantages. You can have magisk now and various other thing . You can directly flash service firmware now by flash tool. Custom roms are also there. Like 5$ dollars for a mediatek device is reasonable.
Click to expand...
Click to collapse
its not 5$ its now 15$ its too mutch
sajib_ngage said:
its not 5$ its now 15$ its too mutch
Click to expand...
Click to collapse
try asking them for lower price, they will help u i think. Tell them its for pro 7 bcoz pro 7 requires less work. try ur luck
vache said:
Here you go : https://drive.google.com/file/d/1x4t6ca8TLf1bNHrQa-jjCN_AhdV2W78u/view?usp=drivesdk
Boots on sofia (g power), sofiar (g8 power), sofiap (g stylus), sofiap_ao (g pro)
Click to expand...
Click to collapse
I started the thread, but did not make this build. Everything should work. Thank @vache.
Quick update I did get TWRP to build successfully. Unfortunately it just sits on the boot logo but doesn't go back to fastboot, but that was just a quick see what happens build. I haven't added everything I need to yet. Will work on it more tonight, but progress is good so far.
@CodyF86 thanks for taking the lead on porting TWRP to the G Power. The G Power appears to be the best "bang for the buck" phone on the market currently, and has been widely covered by the media so far. I expect that the Moto G Power sub will grow steadily in the upcoming months, leading to custom rom development for the G Power. Having TWRP ported would be a start to paving way for custom rom development.
So another quick little update. I have the device repo basically where it should be...give or take heh. It's changed a bit from what is on my github, but it's pretty close. The only issue i'm having is that compiling it with the minimal manifest isn't going to work. It doesn't compile right. It compiles, but it doesn't copy things over correctly and/or at all depending on what it is.
My repo is pretty close to what the moto one power and the g8 power have, at least for their android 9 device tree, and I can get TWRP to boot, if I use the moto one power image and just dump the moto g power kernel into it.
So short version is i'm downloading the full manifest, basically all of Omni, which should hopefully sort it out. It's downloading right now.
EDIT:
Actually it helps to read the documentation I guess lol.
https://source.android.com/devices/bootloader/system-as-root#using-vendor-overlay
Will keep playing with it.
This is exciting! Thanks for your hard work.
CodyF86 said:
Will keep playing with it.
Click to expand...
Click to collapse
Thank you for taking this on! Having TWRP recovery for "sofia" will really make this phone great!
GoodOlDan said:
Thank you for taking this on! Having TWRP recovery for "sofia" will really make this phone great!
Click to expand...
Click to collapse
I "should" have it working in a day or two...(or even tonight...) The Code Aurora repos have been helping greatly.
https://source.codeaurora.org/quic/la/platform/vendor/qcom/trinket/tree/BoardConfig.mk?h=LA.UM.8.11.r1-03800-NICOBAR.0
Quick question, is the Moto g power the same as Moto g8 power? If they get custom Rom they'll unified? From what I know, the g power is the us variant release of the g8 power, right?. Thx in advance
Been making changes and even trying to repack some files from our devices into chef from when I got chef to boot with a repacked kernel but the touch screen wouldnt work and it couldnt see any partitions really.
Part of the problem seems to be the build system. It's not populating the output image fully. It's not even putting the TWRP directory in there lol.....
Going to keep trying. Going to try to find a native android 10 device that has twrp working unless there isnt one yet. Also our device is a little different it actually puts certain things in /system where in android 9 they went into /vendor. Spent about 3-4 hours on it today, but not going to give up.
I think there is an issue with the OMNI build system though also.
CodyF86 said:
Been making changes and even trying to repack some files from our devices into chef from when I got chef to boot with a repacked kernel but the touch screen wouldnt work and it couldnt see any partitions really.
Part of the problem seems to be the build system. It's not populating the output image fully. It's not even putting the TWRP directory in there lol.....
Click to expand...
Click to collapse
HI, I'd be willing to help with this, I'm a developer, I worked with @tecknight on TWRP for a phone called the Wiko Ride. We never quite got a working TWRP but learned quite a bit about AVB and such. I've already got my Sofia (US unlocked retail, running on Boost Mobile) rooted and could use a new challenge.
I too have been quite baffled by the Android build process at times - the docs that exist seem to assume a LOT of prior knowledge - the barrier to entry seems higher than ordinary Linux kernel hacking by quite a bit.
rlrevell said:
HI, I'd be willing to help with this, I'm a developer, I worked with @tecknight on TWRP for a phone called the Wiko Ride. We never quite got a working TWRP but learned quite a bit about AVB and such. I've already got my Sofia (US unlocked retail, running on Boost Mobile) rooted and could use a new challenge.
I too have been quite baffled by the Android build process at times - the docs that exist seem to assume a LOT of prior knowledge - the barrier to entry seems higher than ordinary Linux kernel hacking by quite a bit.
Click to expand...
Click to collapse
Look at my github you can see the cluster ef of changes I made to at least get to a console. Ironically if you repack the kernel into the chef version of TWRP it boots to the GUI but the touch screen doesnt work.. Our device is weird although it is android 10 native but it has a /system folder. Also on android 10 you can just add things to the vendor partition without using the product partition as an overlay.
Unpack the stock recovery. I went back to the basics and am basically going to mirror the stock recovery then inject the twrp binary, but its weird, the omni build system isnt doing some things correctly it seems also.
This will be your greatest resource. Code Aurora has the answers.
https://source.codeaurora.org/quic/la
https://source.codeaurora.org/quic/la/platform/vendor/qcom/trinket/tree/?h=LA.UM.8.11.r1-03800-NICOBAR.0
https://github.com/codyf86/device_motorola_sofia
LA.UM.8.11.r1-03800-NICOBAR.0 is our current CAF version tree.
Actually I just started the repo over the commits were nasty. Everything important and pertinent is in the initial commit now.
Ive been compiling and hacking kernels for 10 years, building Android for probably the same and this switch to the new partition layout + TWRP has so far been the... I don't want to say hardest but longest thing i've tried to do without any forward movement.
Like I said I got farther just by repacking the our kernel into the moto chef kernel, but they have a system_root directory and we dont. We just have system.
Theyre lib64 goes in /vendor ours goes in /system.
unpack the stock recovery image to start also TWRP uses init.qcom.recovery.rc to do things on the init and init.rc hand off where as stock recovery version of that file is different.
Actually I know partially why it wont boot. I have the paths in the init.recvoery.qcom.rc messed up, but also [email protected] doesn't exist in our lib64/hw directories, but there is a [email protected] file in the stock recovery so going to try that, plus were building bootctrl.trinket.
Nm i found the -service binaries for the boot gatekeeper keymaster libraries etc. think I made some progress but I have to build it and make sure everything gets in the right spot. will keep on keeping on.
The current code I have on my github will boot the stock recovery lol (the build system is being weird)....the build system isn't putting things in the right spot still. I was able to get TWRP to boot by rearranging some things manually, but it isn't pretty. So there is some progress, but the build system is part of the problem at this point at least for android 10. I'm still working on it.
CodyF86 said:
The current code I have on my github will boot the stock recovery lol (the build system is being weird)....the build system isn't putting things in the right spot still. I was able to get TWRP to boot by rearranging some things manually, but it isn't pretty. So there is some progress, but the build system is part of the problem at this point at least for android 10. I'm still working on it.
Click to expand...
Click to collapse
Hey, do you have a telegram account for easier conversing? I feel we might be able to help each other here?(I'm working on sofiar)
Dark98 said:
Hey, do you have a telegram account for easier conversing? I feel we might be able to help each other here(I'm working on sofiar)
Click to expand...
Click to collapse
I can make one and ill dm you.
Here are my questions so far / some observations.
The init.rc that the twrp build system puts in the build is incorrect. It needs to be manually added...I think there is a flag for that actually, but I had to change it once it was built. (I was able to make it boot to the first screen by dropping in things in /sbin from https://github.com/TeamWin/android_device_motorola_chef)
The build system doesn't add the twrpres folder to the built image lol; or the twrp binaries to /sbin.
I literally had to copy them over from chef.
Also for example servicemanager and hardwaremanager aren't in the chef repo but they are in /sbin when you unpack the recovery image (chef), is the build system building them or putting them in from somewhere or are the repos not actually the final product and they had to hack the image a bit too.
I had ours added in then took it out when I couldnt find them in anyones device tree but they are there when you unpack all of the recovery images lol.
edit: It's actually putting most of the stuff (adbd) and symlinks in /system/bin including the recovery bin which is twrp, so let me readjust the init scripts.
our device is different it still has /system and not system_root.
another edit: Looking at android_bootable_recovery/crypto/ex4crypt I think im missing some libraries still.
Okay, if/when you do message me on there please, I hardly check XDA other than when I'm updating a Rom I maintain? @Dark998 is my username
@CodyF86
Interested and surprised to see that twrp for native android 10 is in the works.
After reading Dees Troy's article in late 2019 regarding twrp on android 10, I had resigned myself to the notion that twrp is more or less dead for android 10+...
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Hope you're able to get it working!
Q9Nap said:
@CodyF86
Interested and surprised to see that twrp for native android 10 is in the works.
After reading Dees Troy's article in late 2019 regarding twrp on android 10, I had resigned myself to the notion that twrp is more or less dead for android 10+...
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
Hope you're able to get it working!
Click to expand...
Click to collapse
I was absolutely able to get it to boot with adb up but with no touch screen and it couldn't see any paritions, but ive adjusted the fstab file.
Also slightly embarassed to say I repo synced and forgot to drop twrp 10 back in, but i need a libinit with twrp 10 and it actually gave me a couple solutions to that accidentally doing that, accidentally building aosp recovery once time lol xD
CodyF86 said:
I was absolutely able to get it to boot with adb up but with no touch screen and it couldn't see any paritions, but ive adjusted the fstab file.
Also slightly embarassed to say I repo synced and forgot to drop twrp 10 back in, but i need a libinit with twrp 10 and it actually gave me a couple solutions to that accidentally doing that, accidentally building aosp recovery once time lol xD
Click to expand...
Click to collapse
I was thinking that if twrp isn't possible, how difficult would it be to modify stock recovery to remove signature verification?
With stock recovery signature verification disabled, at least side loading would be possible. Thoughts?
Also, I'm willing to help test if needed
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.
Hi
I just successfully rooted my OnePlus Nord CE 5G, but I didn't use a custom recovery to do it. I still miss the features of custom recoveries, essentially the low-level backups.
I searched the Internet for TWRP and OrangeFox, I like both and have used them on previous devices. However, I couldn't find anything for this phone.
Does anyone know how to get that working on Nord CE? Or if there is any low-risk way of trying random recovery builds in the phone, and be able to re-flash the stock recovery if it goes wrong?
Did you make any progress on this?
diegolag said:
Did you make any progress on this?
Click to expand...
Click to collapse
None at all. I was waiting for answers here.
I guess that
- nobody really has specific knowledge about this on Nord CE
and
- the people who have generic knowledge about whether it's risky or not to flash random recoveries and recover with stock recoveries... those people aren't reading this thread.
I personally can't try anything risky, I am already relying on this phone as my main professional tool... and personal gadget.
pgorod said:
None at all. I was waiting for answers here.
I guess that
- nobody really has specific knowledge about this on Nord CE
and
- the people who have generic knowledge about whether it's risky or not to flash random recoveries and recover with stock recoveries... those people aren't reading this thread.
I personally can't try anything risky, I am already relying on this phone as my main professional tool... and personal gadget.
Click to expand...
Click to collapse
Well, then you have not bricked your phone as I did trying to root it without making a backup first
Good to know, I haven't found a solution yet
Right now orangefox android 11 tree is not released (if yes , i dont know), but twrp has. And already custom twrp compiled for ce but needs development and testing.
Right now I need storage on my personal pc , this weekend i will insert new ssd for development on CE (4. SSD ) . First target to see stable twrp (hope it will be official maybe) and then we can compile some roms kernels etc. But i will compile only gapps inbuild roms .
And second news, trying miui cam port to CE . Hope it will work . OxygenOS cam software is trash for me.
Here is the link to the TWRP thread:
[RECOVERY] [11] [ALPHA] TeamWin Recovery Project (ebba) (2021-09-09)
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Bricked mine too, but a repair request with 1+ was my way out. Without costs btw.
Doesn't solve the no backup issue ofcourse.
!PdK said:
Bricked mine too, but a repair request with 1+ was my way out. Without costs btw.
Doesn't solve the no backup issue ofcourse.
Click to expand...
Click to collapse
Can you please tell us exactly how you bricked it? Was it by installing the new TWRP available in the thread I linked?
Yes, by flashing incorrect TWRP to device and trying to update afterwards. Ended in booting into crashdump all the time.
Now discovered the a/b slots could have been the issue.
!PdK said:
Yes, by flashing incorrect TWRP to device and trying to update afterwards. Ended in booting into crashdump all the time.
Now discovered the a/b slots could have been the issue.
Click to expand...
Click to collapse
Did you tried latest msm? Should be fixed.
Already had it fixed by 1plus service request and now updated to 11.11 fw
Hi all, i have a build OrangeFox 11, but need testers.
Yes twrp recovery is available for nord ce 5g