Development [DISCONTINUED] droidontime 6.0 for moto g50 - Moto G50

Hi everyone
Today I'm announcing dot os 6.0 for moto g50.
Development starts Q3 of 2022 , because I need to gather vendor and other files to begin compiling. I don't know it will be GSI based or just straight up with TWRP. I just need some time to start. Also wait for the dotos team to release it, or just get now started on Beta versions.

reserved

reserved

Hi. Do you know guys when TWRP will be ported for this phone? This custom rom will also needs TWRP. Thanks.

IulianBoss25 said:
Hi. Do you know guys when TWRP will be ported for this phone? This custom rom will also needs TWRP
Click to expand...
Click to collapse
It dosen't need to use TWRP. It will use dot os recovery for installing updates and etc. For TWRP you'll need to wait cuz i don't know how to actually port it to g50 because there isn't any vendor images in stock files and needs to be pulled from device it self.

Related

Troubleshooting, touch screen not working in TWRP

Hi everyone, so some mistakes have been made today. While playing around with substratum theme engine on my mix running lineage-os 14.1, i had uninstalled one of the themes and then decided to uninstall the app entirely, however after uninstall it didnt reset the theme, so i rebooted. While attempting to reboot it got stuck in a boot loop. At this point I plugged my phone into my pc and booted into twrp so i could access my files and get them off, however when attempting to boot into twrp i could not use the touch screen which is preventing me from re-flashing my rom. and so after troubleshooting for an hour or soi had all my files off of my device, so i decided to format the system partition. so now i have no rom flashed and a twrp that i cannot use due to lack of touchscreen, its temporarily bricked i guess. So my questions are; A. can i use an otg cable and a mouse to control twrp? B. Is there some way to directly flash a rom from adb or from the connected pc. Then I should also state that I have tried older/newer versions of twrp to try to get the touchscreen working, to no avail (currently running 3.1.1-0 lithium). Ive read that it may be touchscreen drivers or something that are mis-matched from the rom. the onlyt issue is that there is no rom, also ive heard that the touchscreen is at a kernel level so i may need to flash a new kernel to get it working. TBH im not going to do anything else so that i dont completely brick my phone. Thank you all in advance for helping out!
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
You're a god, this is exactly what I needed, thanks!!!
raupe said:
Please try this (older) TWRP by MrRaines: https://www.androidfilehost.com/?fid=673368273298927160
It's TWRP 3.0.2-0 based but has different kernel/driver that is more compatible with a varous bunch of ROMs.
Click to expand...
Click to collapse
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
kanej2006 said:
I LOVE you, spent hours trying to get recovery working. This was the only fix!
Thank you so much brother.
Click to expand...
Click to collapse
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Just see the kernel img, ramdisk and boot files/blobs
raupe said:
Ok glad to read that it works.
Please keep in mind: the TWRP of MrRaines is an older one and is heavily modified.
ATM i'm trying to investigate what's the specific reason other TWRP versions are conflicting with touchscreen drivers on every new release of an stable or dev rom but MrRaines TWRP is still working ^^
The TWRP compatibility case has become even worse with the release of some Android 7.x / Nougat based ROMs - without an official kernel source release for Android 7 by Xiaomi (Android 6 kernel sources should have been released some weeks ago).
Could take a couple of days to find a reason and some more to find a solution...
... any help, tips and confidential information is very welcome @MrRaines @jcadduono
Click to expand...
Click to collapse
Hmmm. I did try two or even three other versions of TWRP. The first two would not even flash giving me an error. The third worked but touch screen would not work. Final attempt was the one from MrRaines which worked perfect!

[TREBLE][SAGIT] ProjectTrouble reloaded

Project Trouble reloaded
What is Project Treble:
Project Treble basically partitions your device into two separate partitions, a system and a vendor: system contains your generic system image, while vendor partition has your device specific files required for booting and running your phone. This way we can easily change the system image and be able to run our device on different system images with the same kernel and vendor partition
Read more about Project Treble
What's a GSI?:
A GSI literally means Generic System Image. It is a general system image meant for no specific device. Treble enabled devices have the capability to run a GSI.
Install:
Download Project trouble reloaded. Link
Download a GSI. Link
Reboot to latest Official TWRP. Link
Wipe everything and format data - yes.
Flash Firmware newer then 8.4.19 and Project trouble reloaded.
Install the GSI
Reboot
Thanks to
Demon000 the highest GOD for all
Demon again
everyone who thinks that he/she did something great
Note:
Use Magisk 16.7 and Shev-T TWRP if you want to install magisk
​
XDA:DevDB Information
Project treble for Xiaomi Mi 6, ROM for the Xiaomi Mi 6
Contributors
NeoArian
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.4.19
Version Information
Status: Alpha
Created 2018-07-04
Last Updated 2018-07-04
XDA:DevDB Information
Project treble for Xiaomi Mi 6, ROM for the Xiaomi Mi 6
Contributors
NeoArian
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.4.19
Version Information
Status: Alpha
Created 2018-07-04
Last Updated 2018-12-22
Amazing work man. Really appreciated.
Just wondering, once treble activated, do we only install future gsi and nothing else needed? Forever?
That is fantastic. thank you for the reload.
Hi. may us know if theres any bug? Thanks.
Thanks Bro!!!
neXus PRIME said:
Amazing work man. Really appreciated.
Just wondering, once treble activated, do we only install future gsi and nothing else needed? Forever?
Click to expand...
Click to collapse
We will See Android P Not released
Shimizux said:
Hi. may us know if theres any bug? Thanks.
Click to expand...
Click to collapse
NFC doesnt Work on aosp, but on Lineage Based Roms. Rest ist fine.
NeoArian said:
NFC doesnt Work on aosp, but on Lineage Based Roms. Rest ist fine.
Click to expand...
Click to collapse
Noted. Anyway, Any GSI's recommendation? Can we Flash SuperSu instead of Magisk??
Shimizux said:
Noted. Anyway, Any GSI's recommendation? Can we Flash SuperSu instead of Magisk??
Click to expand...
Click to collapse
DotOS, Aosp, just choose one from the year section you can use supersu I stead of magisk.
It doesn't world with Pixel GSI image, apps keeps crashing and then, the system starts bootlooping
smsalom said:
It doesn't world with Pixel GSI image, apps keeps crashing and then, the system starts bootlooping
Click to expand...
Click to collapse
Check this instructions given by PE.
New Update for Project Trouble : https://www.androidfilehost.com/?fid=5862345805528050776
The new Project Trouble is based on the official LineageOS build from 07/17
anyone else flashed p via pt?
kpzhao said:
anyone else flashed p via pt?
Click to expand...
Click to collapse
Does not work in our Mi 6... At least in mine. I've tried various forms of instalation but no success... I Think that our kernel ins't compatible yet.
Rick_BR said:
Does not work in our Mi 6... At least in mine. I've tried various forms of instalation but no success... I Think that our kernel ins't compatible yet.
Click to expand...
Click to collapse
It works, you just need to disable fbe.
NeoArian said:
It works, you just need to disable fbe.
Click to expand...
Click to collapse
Strange... You mean format data? I've tested with and without... Still no luck. :/
Rick_BR said:
Strange... You mean format data? I've tested with and without... Still no luck. :/
Click to expand...
Click to collapse
No you need to flash this
View attachment fbe_disabler_treble.zip
imjohncarlo9 said:
No you need to flash this
View attachment 4552863
Click to expand...
Click to collapse
Wow! I will test and give feedback here. Thanks!
imjohncarlo9 said:
No you need to flash this
View attachment 4552863
Click to expand...
Click to collapse
where can i find a guide to install this semi-p
NeoArian said:
New Update for Project Trouble : https://www.androidfilehost.com/?fid=5862345805528050776
The new Project Trouble is based on the official LineageOS build from 07/17
Click to expand...
Click to collapse
Work fine! Thanks.
I installed Google Experience GSI and the unique problem is google not recognized my device, but, I thinks it´s problem the Google Experience rom.
The mi 6 is on bootloop with Android P GSI Preview, but it's normal, it's a beta.
Greetings

Official Custom Rom..request to developers

Anyone knows when official custom roms will be released for moto X4. I like to flash official ROM as its my daily driver device.
In custom ROM section, those are unofficial.
There are only Lineage, Resurrection Remix v6.1, Carbon ROM, & that too Unofficial Version.
When can we see Pixel Experience, Omni ROM, AOSP extended, Liquid Remix, CrDroid, Firehound ???
It looks like Moto X4 is neglected device, one side MOTO is not releasing regular update, for my XT1900-2 its still on android 8.0, jun patch, & Other side there are no official popular ROM, i request all developers on XDA to focus on moto X4 so that users like me can enjoy bunch of latest android features.
Unbelievable.
There's no ETA for anything...
But, LineageOS 15.1 will become official and you can flash the GSIs found at Project Treble section, just follow the guide to install Android Pie found here.
No official yet,and process of porting android 9.0 is too complex. Can't we have flashable rom zip one file for android 9 moto x4
abrfilho said:
There's no ETA for anything...
But, LineageOS 15.1 will become official and you can flash the GSIs found at Project Treble section, just follow the guide to install Android Pie found here.
Click to expand...
Click to collapse
omky_b4u said:
No official yet,and process of porting android 9.0 is too complex. Can't we have flashable rom zip one file for android 9 moto x4
Click to expand...
Click to collapse
WILL become official... Just wait, maybe Tuesday...
The only zip available for Pie is LineageOS 16, but it's in development, not only for our device, but the system itself.
Great news, eagerly waiting...
abrfilho said:
WILL become official... Just wait, maybe Tuesday...
The only zip available for Pie is LineageOS 16, but it's in development, not only for our device, but the system itself.
Click to expand...
Click to collapse

[Discontinued]Pixel Experience P[UNOFFICIAL][14.12.2018][S9/S9+/N9]

Samsung Pixel Experience P​By CodeFox & OpenSauce9810​
What is this?
This is a Semi Generic System Image. That means it's a generic system image that's been optimised as much as possible for our Samsung Devices. This is what differentiates this rom from the one you can find in the Project Treble Forum. I also plan to provide regular updates and improvements very frequently. I'm aiming for weekly if not more.
Why not Rainbow_Dash?
We're a part of the same team and he's taking a break from developing for the moment, so I'm going to do my best to support you with regular updates and support where possible. So his previous version should be considered redundant.
How the heck do I flash this?
It's slightly different than flashing a zip, so here's what you need to do.
Download the image file
Flash BRJ6 Vendor (If you're not on it already)
Flash a compatible kernel (I believe Endurance Kernel AOSP Works fine)
Flash the System Image to your System Partition
Optional if you want root (but reccomended): Reboot to recovery again then flash your choice of Magisk. I use 17.1 as I can get galaxy wear to work with that version.
Reboot your device and you should be good to go! No need to flash gapps as they're included.
To boot recent GSI Builds, on S9/+ be sure to have:
•BRJ6 Vendor
•Eamons latest Endurance Kernel based on 8.1 (AOSP)
•Soldiers latest ELS
*On some ROMs you will find Fingerprint doesn't work, so flash Soliders latest ELS, try and let your phone boot and then flash Endurance again after. You will notice your Fingerprint process isn't in a loop anymore*
What's different to the PE in project treble forum?
Thanks to GRaf for this guidance ^^
Smoother UI Performance Fixes
Debloated unneccessary libs from other devices
Vibration Motor has been corrected (it's too powerful in GSI)
Regular Maintenance / Builds & Support
Changelog:
30.11.2018 - Initial XDA Release & Unofficial rollout.
01.12.2018
Animation integers corrected to be smoother
Black boot-animation added, no more being blinded by the boot animation
Pixel Live Wallpapers included
High Resolution default wallpaper added
09.12.2018 (Now maintained by @malinathani
Made system ui a hella smoother compared to before
Face unlock works
Phh settings removed. All samsung options should now be persistent.
14.12.2018
-Fixed fingerprint on note 9, should work now with almost any vendor so get the latest one
-Almost everything works now
Bugs:
Auto brightness and home button in always on display.
You tell me
Downloads:
System Image
Link to Endurance Kernel Thread for compatible kernel
Support & Feedback
I'm happy to provide as much support as possible. Through XDA here or you can get in touch with me and the rest of OpenSauce9810 + our community at our Telegram group here
If you're happy with the work I've put into this (endless amounts of hours trying to perfect GSI building) then a simple thanks here or clicking the thanks button below is very appreciated!
Credits and Thanks
Ivan - Thank you for helping me out every now and then when I'm being stoopid.
Rainbow_Dash - Pointing me in the right direction with regards to fixing the errors.
malinathani - For fixing the UI Jank which we experienced in GSI's. His fix is widely used in other GSI's now.
GRaf - best tester
The guys in telegram as a whole, thank you for the feedback and support.
XDA:DevDB Information
[Discontinued]Pixel Experience P[UNOFFICIAL][14.12.2018][S9/S9+/N9], ROM for the Samsung Galaxy S9
Contributors
CodeFox, Rainbow_Dash, malinathani, Mohammed Nathani, Opensauce9810, Ivan Meler, phhusson
Source Code: https://github.com/PixelExperience
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: BRJ3 Vendor
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-11-30
Created 2018-11-30
Last Updated 2019-01-07
working fine on s9+
Awesome thank you very much ?
thank you, could please post some screenshot.
Does not progress from white pixel boot screen for me s9+.
I'm a little confused by the instructions. I am on the BRJ8 vendor currently. Do i flash it in this order?
Wipe system, data, cache, dalvik cache
Install the rom img into the system partition
Reboot into recovery
Install the endurance kernel aosp 9.0
Correct?
LavaSnake54 said:
I'm a little confused by the instructions. I am on the BRJ8 vendor currently. Do i flash it in this order?
Click to expand...
Click to collapse
tried, doesn't go further than boot logo after flashing all that on BRJ8 So you need BRJ6
a_swed said:
doesn't go further than boot logo after flashing all that on BRJ8
Click to expand...
Click to collapse
read read read read
I've updated the OP with further guidance regarding getting it to boot. I don't have the S9/S9+ so I had to to go to a buddy and ask him. Hopefully this will help you get it booting now.
Wait what...... You're telling us to flash an android 8.1 kernel to an android 9 rom?
LavaSnake54 said:
Wait what...... You're telling us to flash an android 8.1 kernel to an android 9 rom?
Click to expand...
Click to collapse
Well we don't have a pie kernel sources yet, so yes. Plus it's a Generic System Image. The 8.1 kernel works fine.
New build posted. see OP for details.
One more question, I am already on BRJ8 firmware, and I heard somewhere that samsung doesn't allow you to downgrade to an older firmware. Is this true? Do i just flash the BRJ6 firmware on my already current rom?
LavaSnake54 said:
One more question, I am already on BRJ8 firmware, and I heard somewhere that samsung doesn't allow you to downgrade to an older firmware. Is this true? Do i just flash the BRJ6 firmware on my already current rom?
Click to expand...
Click to collapse
You need the vendor, nit the firmware. And yes, you can flash vendor and firmware.zips how you like. Versions up and down. I am speaking about the flashable version for TWRP.
---------- Post added at 06:41 PM ---------- Previous post was at 06:32 PM ----------
Flashable Vendors:
http://cloud.timo-ehlers.de/S9(+)/Vendor/
Nice work! Glad to hear you going with weekly updates too! Flashing this one asap tomorrow!
Snapdragon
I'm assuming this doesn't work on the US Snapdragon variants? Figured I'd ask. Nice job and keep developing people
notsotet said:
I'm assuming this doesn't work on the US Snapdragon variants? Figured I'd ask. Nice job and keep developing people
Click to expand...
Click to collapse
It will indeed work for SnapDragon variants friend. It's Samsung specific but still a generic image.
I'm stuck on Google logo
Came from ZRKZ
Factory reset - flashed vendor BRE6, flashed img, rebooted twice into Samsung, booted into google, progress bar keeps going and going... 20 minutes.
MidnightDevil said:
I'm stuck on Google logo
Came from ZRKZ
Factory reset - flashed vendor BRE6, flashed img, rebooted twice into Samsung, booted into google, progress bar keeps going and going... 20 minutes.
Click to expand...
Click to collapse
Have you flashed the 8.1 Endurance Kernel? Sounds like you may still have the pie kernel.
LavaSnake54 said:
Wait what...... You're telling us to flash an android 8.1 kernel to an android 9 rom?
Click to expand...
Click to collapse
Strangely enough Pixel Experience will only boot with Jesec's 8.1 ramdisk that my 8.1 kernel utilises. I'll update my OP to address this.
CodeFox said:
It will indeed work for SnapDragon variants friend. It's Samsung specific but still a generic image.
Click to expand...
Click to collapse
I will need a custom recovery though right? US Snapdragons are bootloader locked so I don't have any way of doing that

Hello everybody! My Meizu M5 (M611H) makes me desperate.

Hello everybody.
I like doing small repairs in electronics. In the past I have reflasced in some wifi routers and installed LineageOS in an old Sansung Grand Prime SM-G531F.
Instead I have not been able to unlock the bootloader of my Meizu M5 (M611H) for months. There are many self-styled guides but in the end they give generic indications for the majority of android systems. For example, I do not need external applications to root because it is provided by Meizu itself through the login on the Flame OS site, and the other thing is that Meizu M611H in the developer options does not have the "Unlock OEM" option. do it via fastboot commands. I'm really desperate ...
Hi, you can flash this twrp recovery with mediatek flash tool.
you not have to unlock bootloader.
Meizu M5 TWRP
Hello. Thank you!
I will certainly try to flash you twrp.
Could you please tell me which is the best firmware you have found for this device?
Thank you very much!
Paulo
paulosubs said:
Hello. Thank you!
I will certainly try to flash you twrp.
Could you please tell me which is the best firmware you have found for this device?
Thank you very much!
Paulo
Click to expand...
Click to collapse
The kernel source code of this device is not open source.
incapable of action.
This device has lineage 14.1, which was created by the Russians, but there are many problems, such as the sound doesn't seem to work !
Only official firmware can be used !
iamverycute said:
The kernel source code of this device is not open source.
incapable of action.
This device has lineage 14.1, which was created by the Russians, but there are many problems, such as the sound doesn't seem to work !
Only official firmware can be used !
Click to expand...
Click to collapse
Can I use mediatek flash tool with any Flyme Firmware installed on the M5?
In the past I always reinstalled the first Flyme 5.2.10.3G version
while trying to install twrp.
I currently use the version 7.8.8.31 beta which I found on page Flyme 7 Experience Beta for M5 & M5s.
If I can't install a custom rom, how can I take advantage of the trwp? In addition to doing the root and being able to make a full backup of the rom image?
Thanks Iamverycute!
Paulo
paulosubs said:
Can I use mediatek flash tool with any Flyme Firmware installed on the M5?
In the past I always reinstalled the first Flyme 5.2.10.3G version
while trying to install twrp.
I currently use the version 7.8.8.31 beta which I found on page Flyme 7 Experience Beta for M5 & M5s.
If I can't install a custom rom, how can I take advantage of the trwp? In addition to doing the root and being able to make a full backup of the rom image?
Thanks Iamverycute!
Paulo
Click to expand...
Click to collapse
Yes, you can.
All functions of this recovery are available.
If you try to install Android 5, after restarting the device, this recovery may fail !

Categories

Resources