{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restores the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
SUPPORTED DEVICES
- dubai (XT2203-1)
HOW TO INSTALL LINEAGEOS WITH LINEAGE RECOVERY
- Make sure your phone is running firmware from at least 12-S1RD32M.55-67. If not? Please download and flash it first before installing this ROM.
Please follow the official instructions on the LineageOS Wiki here:
Install LineageOS on dubai | LineageOS Wiki
wiki.lineageos.org
HOW TO UPDATE LINEAGEOS WITH LINEAGE RECOVERY
Please follow the official instructions on the LineageOS Wiki here:
Update LineageOS on dubai | LineageOS Wiki
wiki.lineageos.org
KNOWN BUGS/ISSUES
Widevine L1 lost upon bootloader unlock (reverting to stock ROM and relocking bootloader does restore it)
Intermittent HBM flicker when you use UDFPS when screen is off (screen will flash brightly for a split second)
Setting 48Hz minimum refresh rate with anti-flicker (DC Dimming) can cause gamma flickering and might cause UDFPS accuracy issues. Either bump minimum refresh rate to 60Hz or disable anti-flicker. Motorola only ever intended 48Hz for peek display mode and not regular use
Inverted colors doesn't work. It will cause the screen to mostly go black and then you need to remember where to tap to disable inverted colors
MAIN DOWNLOADS
Lineage:
- Official:
LineageOS Downloads
download.lineageos.org
- Unofficial:
https://osdn.net/projects/lineageos-for-dubai/releases/
GOOGLE APPS (GAPPS) DOWNLOADS
- MindTheGapps:
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
GOOGLE CAMERA (GCAM) DOWNLOADS
Google Camera:
Please check the Telegram Edge 30 Photography group:
Motorola Edge 30 | Photography
Welcome to Motorola Edge 30 Photography Hub! - English only. - No OT. - Don't send more than 11 pics at once. Group: @MotoEdge30
t.me
DEVELOPER RESOURCES
GitHub - LineageOS/android_device_motorola_sm7325-common
Contribute to LineageOS/android_device_motorola_sm7325-common development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_motorola_dubai
Contribute to LineageOS/android_device_motorola_dubai development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_kernel_motorola_sm7325
Contribute to LineageOS/android_kernel_motorola_sm7325 development by creating an account on GitHub.
github.com
Motorola SM7325 Devs
Motorola SM7325 Devs has 13 repositories available. Follow their code on GitHub.
github.com
HOW TO CONTRIBUTE
Send your patches up for review: https://review.lineageos.org/
Read the guides on the LineageOS Wiki: https://wiki.lineageos.org/
Source Code: https://github.com/LineageOS
DONATIONS
Pay Marc Bourgoin using PayPal.Me
Go to paypal.me/ThEMarD85 and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.
www.paypal.com
Heyyo! W00t! Happy new years my friends!
Attached is pictures of LineageOS 20 on dubai
ThE_MarD said:
Heyyo! W00t! Happy new years my friends!
Attached is pictures of LineageOS 20 on dubai
Click to expand...
Click to collapse
Successfully installed LineageOS 20 and I love it. I also installed Magisk with it so I can have full screen gestures. I'm super happy now. Thanks so much for the support and LineageOS build!
edit - turns out there is an option to hide gestural navigation hint, my bad!
This is great news.. im buying a new Motorola Edge 30, purely to install LineageOS 20 on it. I was looking for the most recent device (with the most recent chipset) that already runs LOS 20, and im moving away from the OnePlus 10T because it lacks a ROM scene due to not being a developer friendly brand anymore. I don't need a flagship anyways, i've watched UI interaction and performance videos on the Edge 30 and not to speak that paired with LineageOS it should perform even better
Thanks for supporting this device, i hope it's a keeper
* Note: its sad that XDA doesn't think the Edge 30 deserves its own subforum. I saw a request elsewhere that was even liked by a responsible moderator, yet it's not been done
Heyyo @mxz55 , Well I'm glad you're interested in the Motorola Edge 30! I was super lucky that Motorola actually sent me one to develop LineageOS on since they don't have any official device seeding program and yeah this thing is a great device.
Please note that unlocking the bootloader (at least the official way) will void your warranty and unfortunately it also wipes the DRM keys so you will be stuck on Widevine L3. Another thing to note is LineageOS doesn't allow for any SafetyNet haxxs so if that is important to you as well you will need to install Magisk and SafetyNet mods.
Otherwise? It is super stable and smooth as I've been running LineageOS 19.1 since October and then LineageOS 20 since late November. I do use MindTheGApps 13 as it does everything I need anyways and yeah I've had zero issues.
That's too bad for the OnePlus 10T though... I super loved my OnePlus One and I still have it... I got a OnePlus 7T for my mom to use and that is a super crazy good device too and she loves it too. There is a chance too since the OnePlus 10T is such a new device and new SoC it might take time to get it up and going on custom ROMs? I'm not too sure tbh as I don't really follow OnePlus custom ROM scene as I haven't been part of it in a long time.
ThE_MarD said:
Otherwise? It is super stable and smooth as I've been running LineageOS 19.1 since October and then LineageOS 20 since late November. I do use MindTheGApps 13 as it does everything I need anyways and yeah I've had zero issues
Click to expand...
Click to collapse
Thanks, i really can't wait to try it out, im gonna install the ROM as soon i stop being blocked by this issue. Anyone that wants to buy this device in order to install a custom ROM right away should be wary of that, it's a day 1 bootloader roadblock (OEM unlocking greyed out) that Motorola is throwing up, unfortunately.
// Update: in my second post on that topic about bootloader lock, i put an edit stating it took only 72 hours for the automatic unlock to occur. So now we know that the Bootloader lock on the Motorola Edge 30 lasts 72 hours, that differs per device. Anyone that buys this device for flashing LineageOS should know this.
On another note, don't let the low exposure to your release thread discourage you or make it feel like there's less user interest for LineageOS on the Edge 30 - it's obviously a result of the lack of a dedicated device forum, where the owners look for an overview of what exists. I still can't wrap my head around it that a well received, popular upper-mid range device has no forum. It also demotivates certain developers due to the exposure thingy. // Edit: i lodged a request the right way, at https://forum.xda-developers.com/t/new-device-forum-requests.1660354/post-87944129 so let's see what happens
@mxz55 yeah Motorola have a bootloader unlock timer like Xiaomi, I think it's partially to deter resellers from modifying the stock ROM as that was an issue I remember on Xiaomi devices which they kept getting bug reports on what they found was modified code not from them...
XDA also doesn't have a dedicated device forum for the Poco F4 GT as I keep seeing requests for that device too, so I don't know how XDA pick devices since they tend to have a bunch of devices from companies that don't release kernel source code or allow bootloader unlocking to have forums which is odd since that's the main reason I thought XDA Forums existed???
Hi @ThE_MarD , this is amazing work here and I am excited to see whats ahead for this device. Was wondering if there is anything in the pipeline this year for moto edge 30 fusion as far as lineageos is concerned. Thanks in advance!
Heyyo @Harry8242 , thanks man! As for Edge 30 Fusion (tundra) unfortunately I don't own one but I started some device trees since sm8350 and sm7325 are very similar and in theory can share a device tree and kernel too.
GitHub - moto-sm7325/android_device_motorola_tundra
Contribute to moto-sm7325/android_device_motorola_tundra development by creating an account on GitHub.
github.com
GitHub - moto-sm7325/android_device_motorola_sm7325-common at tundra/lineage-20
Contribute to moto-sm7325/android_device_motorola_sm7325-common development by creating an account on GitHub.
github.com
GitHub - moto-sm7325/android_kernel_motorola_sm7325 at tundra/lineage-20
Contribute to moto-sm7325/android_kernel_motorola_sm7325 development by creating an account on GitHub.
github.com
Files · lineage-20 · moto-sm7325 / proprietary_vendor_motorola_tundra · GitLab
GitLab.com
gitlab.com
Files · tundra/lineage-20 · moto-sm7325 / proprietary_vendor_motorola_sm7325-common · GitLab
GitLab.com
gitlab.com
There's probably some more kernel changes needed to get it to boot but it's a start.
I also think that tundra is the most beautiful device of 2022 and I'd love to have one but I don't have any spare funds to buy one
Heyyo! Well looks like XDA gave us our own forum section! Good news indeed
Heyyo! So the January 12th official update includes the UDFPS improvements to correct for HBM flicker and also updated automatic brightness too
ThE_MarD said:
Heyyo! So the January 12th official update includes the UDFPS improvements to correct for HBM flicker and also updated automatic brightness too
Click to expand...
Click to collapse
Nice. if you dont mind me asking, can display gamma changes due to variable refresh rate be fixed?
I purchased a Motorola Edge 2022 which I thought was the Edge 30, however I realize now it's an XT2205-1 rather than XT2203-1. As I've run into an inability to flash recovery as the partition is to small, I'm guessing it is unlikely I'll be able to get Lineage to work on this device even if I fix the boot_a partition. Can anyone confirm this?
hi guys
its ages since i flashed roms there was a time i would flash like 5 roms in a day long back during the HTC era asumng lots of things have changed do want to on my Moto edge 30 do point me to a guide on the same
thanks in advance
hari
I'm thinking of installing this ROM, I would like to know if apps like Pokémon go, Google wallet, Android auto work ?
Also if there is any tutorial to return to stock with bootloader lock?
Heyyo @Swapnil Kadlag, if you have minimum refresh rate set to 48Hz the gamma shift will happen as Motorola don't officially supports it, but we left it in for users to decide if they want to use it
@wonderfullyrich sorry but the XT2205-1 is a completely different device as it uses a MediaTek SoC where-as XT2203-1 uses Qualcomm. Tbh I will never touch a MTK SoC since they don't care at all about the open source community even though Android OS and Linux kernel are based on open source so that's a big slap in the face. Qualcomm has CodeLinaro (CLO) and it is a boon for open source development.
CodeLinaro
www.codelinaro.org
Maybe a dev might come along for the Edge 2022 but tbh I wouldn't hold my breath as there's only a handful of MTK devices with any custom ROM development...
@haree there is guides linked in the first post please check there
@guta12 yes those apps will work but for them to pass SafetyNet you will need to use something like Magisk and SafetyNet mods for it in order to make them work properly. I haven't tried that stuff so I don't know how it works though
ThE_MarD said:
@wonderfullyrich sorry but the XT2205-1 is a completely different device as it uses a MediaTek SoC where-as XT2203-1 uses Qualcomm. Tbh I will never touch a MTK SoC since they don't care at all about the open source community even though Android OS and Linux kernel are based on open source so that's a big slap in the face. Qualcomm has CodeLinaro (CLO) and it is a boon for open source development.
CodeLinaro
www.codelinaro.org
Maybe a dev might come along for the Edge 2022 but tbh I wouldn't hold my breath as there's only a handful of MTK devices with any custom ROM development...
Click to expand...
Click to collapse
@ThE_MarD Many thanks. That was my guess. I'll see what I can hunt which has eSim and a microSD in Lineage. Appreciate the feedback and the work!
@ThE_MarD I've been following the custom ROM scene since the days of the Samsung Galaxy Y S5360 and the flashing tool "Odin" in 2012. I never bothered to create an XDA account until recently. My device purchases have always been based on custom ROM support, general attitude from the manufacturer about bootloader unlocking and warranty, etc. My devices have been the Samsung Galaxy Y, Galaxy S4, OnePlus 3, OnePlus 6T, OnePlus 8T, and OnePlus 9 Pro. Since the battery on the last mentioned is dying, I was looking for my next device. Since the merger of OnePlus and Oppo, everything after the 9 Pro has been a huge letdown, they lost there soul and support in the modding community. With the Moto Edge 30 8GB/128GB being sold new at 260 Euros, with 3 maintainers and a great shape of the LineageOS port, it was a no-brainer for me to buy this device three times based on the assumption that I will install LOS 20. I will use one device for personal use, one device to develop an app, and one for my dad, with possibly more devices coming in for other family members. Your work is a blessing in my life since this device is currently the only sane option besides the (probably) upcoming Pixel 6/7 (Pro) LineageOS support. This enables me to do advanced work like patching the Kernel for Docker support, etc. I'm currently waiting for the devices to arrive.
@ballin_ wow I'm feeling the love and I'll pass on the word to the other devs! Thanks for the kind words!
Yeah I'm definitely a fan of Motorola since even before I got my Edge 30 from them since the Moto x4 is a super solid budget device so it's easy to see why they're doing so good on budget devices and the Edge 30 is a really darn good high end device as everything it does is done really well and yeah they've been quite kind to the custom ROM scene with kernel source code releases and they just released a new tag recently so we will be working on updating it too.
I'll definitely be keeping my Edge 30 for quite a few years as well since it does everything I need.
There's also a few more custom ROMs in the works for dubai as I've seen a few test builds go up on our Telegram community and hopefully more to come too
I think about buying an Edge 30 smartphone and use it with LineageOS (same as my current phone). Maybe someone can comment on a few remaining concers/questions I have:
SafetyNet: I need to be sure that the device runs my banking app (ING DiBA) and Netflix/Disney+. Otherwise, the smartphone will be useless for me. I don't need/don't want root access. I only need these apps.
With my current phone (osprey with official LineageOS 17.1), I never had to mess around with any additional software like Magisk. Banking and streaming apps worked out of the box and the yasnac app shows on my old phone that it passes SafetyNet.
1) Why do I need Magisk and the patches on this phone to pass SafetyNet (and why does it work with no additional software on my old phone)?
2) When do I install Magisk and how? I read so many different tutorials that I'm completely confused. Some say that I flash it right after the LinageOS image (before the first boot), some want me to install the apk after the installation in the running LinageOS, some say I need root, some say the opposite. Maybe someone can bring some light into the darkness.
Firmware updates: For my old osprey, I had to flash Android the stock image to update the firmware (baseband, etc.) to fix security issues, and then I could install LineageOS. From Xioami, I heared that there's a tool which extracts the relevant files from the stock rom and creates a file that you flash to update the firmware for the latest security fixes the vendor publishes every month.
3) How do I update the firmware on dubai?
TWRP: I like this recovery because it allows me to backup and restore everything without root access. Unfortunately, LinageOS recovery doesn't have this funtionality (at least the last time I tried it).
4) Does anyone know if someone works on TWRP for dubai?
5) Is there another way to backup the whole device without root in a similar way? I don't need a daily or automated backup. I just want to create one from time to time manually to be able to reset my device to this state if needed.
SELinux:
6) Is it enabled?
Thanks for taking the time to answer my questions. If I can overcome my concerns and buy the Edge 30, I'll share my experiences of course, report bugs, etc.
And thanks to the maintainer for making LineageOS work on this phone.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (countless other scenarios apply here). Please do some research if you have any concerns about features included in the product you find here before flashing it. You are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you (seriously, I will laugh really hard!). Your warranty will be void if you tamper with any part of your device / software.
Introduction:
MoKee OpenSource is based on the Google AOSP and CyanogenMod project. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.
The Mfunz Forums launched this project on the 12th of December 2012, and is committed to make this ROM better and better.
Since this project is open source, anyone interested can participate in the development. Newcomers are always welcomed!
Types of Releases:
MoKee OpenSource has 4 kinds of releases: official release, beta, nightlies, and unofficial builds.
Official release: This version is tested throughly by developers and users, so it is the most stable build
Beta: When a device is newly added, there will be beta versions for testing, but there might be unknown bugs and problems
Nightlies: Nightlies are compiled automatically by servers, so it will have the latest features but beware of uncompleted works
Unofficial builds: These builds are compiled from source or ported by non MoKee developers
Official Releases:
MoKee Open Source supports many devices, but the developers may not have all devices in hand, so if there are device maintainers that can help out, the official releases will be decided by them, MoKee Open Source will only maintain the nightlies to ensure the usability of the ROM. However, for devices with no device maintainers, MoKee Open Source will decide when to release official builds or nightlies. Therefore, if you have a device maintainer, please get the official releases from your respective device maintainer's thread or nightlies from MoKee Open Source.
Features:
Incremental updates
OTA updates - update on the fly!
ListView animations
Multi window
Calendar - with lunar and solar calendars
Lunar calendar in lock screen
Task switching sidebar in recent apps (the list will increase if you install supported apps)
Bulk SMS recipients
Adjustable SMS font size
SMS sending delay
Smart dialing
Speed dialing
IP dialing
Custom carrier name
Network speed in status bar
Built in timer in Apollo - determine when to stop playing music
MoKee NotePad
MoKee Setup Wizard
Active Display
HALO
Adjustable navigation bar height
Unique Power Saver functions!
Custom screen off animations
** Not yet merged
PIE control
Auto hide status bar
Smart capture
Preview option in launcher (similar to the preview function in launchers found in Play Store)
Many more! Since we are constantly adding new features, see changelogs to keep updated!
Links:
Official Site:
http://www.mfunz.com
Statistics:
http://stats.mfunz.com
Bug Tracker
http://issues.mfunz.com
Changelog
http://changelog.mfunz.com
GitHub
http://github.com/MoKee
Code Review:
http://review.mfunz.com
Installation Instructions:
1. Wipe data/factory reset
2. Flash ROM
3. Flash Gapps
4. Reboot
Issues with themes:
Please refer here: http://forum.xda-developers.com/showthread.php?t=2577469
Donations:
http://www.mfunz.com/en/donations/
Credits:
- MoKee Developers: http://www.mfunz.com/en/contributors
- CyanogenMod
- AOSP
- Koush for open-sourced SuperUser
- ParanoidAndroid for HALO
- Slim Roms
- @gimmeitorilltell for helping me through some initial build errors
XDA:DevDB Information
MoKee 4.4 (Unofficial), a ROM for the AT&T HTC One X
Contributors
Black!Jack
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 2.14/2.15
Based On: CyanogenMod/MoKee Open Source
Version Information
Status: Stable
Stable Release Date: 2014-02-10
Created 2014-01-25
Last Updated 2014-02-10
Downloads
Mod Edit: Download links removed.
GApps Downloads
PA GApps
BaNkS GApps
Recovery Downloads for 4.4 Roms
CWM
TWRP
Changelog
All MoKee changelogs can be found HERE.
Z1cK said:
Look cool. Downloading... Will report feedback. Good job !!
Sent from my One xl
Click to expand...
Click to collapse
I hope you enjoy it. I have been running it for quite a while and I have no complaints.
A Q&A thread has been started for non development related questions, requests, chatter etc...
Here is the link:
http://forum.xda-developers.com/showthread.php?t=2623699
Let's all try to keep this thread clean!
Sent from my One X using Tapatalk
OK. It booted fine and everything is working well. :thumbup:
Sent from my One xl
gimmeitorilltell said:
This looks great! I'm excited to see that I was able to help someone out! This rom looks promising and it seems like it's gonna be a busy thread for you. Congrats!
Click to expand...
Click to collapse
Thanks to you my friend! I appreciate your help. It was nice to have someone to "steer" me in the right direction; and not actually "drive" me to my destination. Logic prevails yet again!
Z1cK said:
OK. It booted fine and everything is working well. :thumbup:
Sent from my One xl
Click to expand...
Click to collapse
Of course it is!
And just so that everyone knows, this DevDB project includes some important tabs at the top.
Screenshots
I have uploaded a bunch already, and I plan to add a whole lot more!
Downloads
In addition to my dev-host account, I will also be uploading them to XDA - you can find them in this tab; complete with md5 checksums.
Q&A
Pretty self explanatory. Let's keep anything not development related there; after-all, that is what it is there for! I will ask mods to move posts that do not belong here there. Repeated requests to the same people will get you BlackListed and ignored. Really, it's not that big of a request!
If your post disappears, it was probably moved to the Q&A Thread for this ROM, since the OP has asked that this thread stay dev talk, and questions etc go into the Q&A thread.
Thanks.
Madcat8686 said:
BJ, WIFI works for me and so does ADB. I am really digging this Rom. Battery life is phenomenal as I have come to expect from 4.4.2 Roms.
I saw one minor glitch when I first was setting up the Rom. The "X Remove" stayed at the top when I was removing a widget. It eventually went away after a reboot but I consider this cosmetic at best and it never happened again.
Other than that I have nothing but thanks for the outstanding Rom to report.
Click to expand...
Click to collapse
Great to hear. As this was sort of a dry run I didn't add or take anything away from the initial build. However, moving forward, I will be adding some useful features, and removing some unneeded nonsense. At the top of the main ROM page there is a tab for Feature requests. If you, or anyone else has a request for something you would like to see added, or subtracted, please put it there. It will be easier for me to keep track of everything that way. I have already received some great suggestions and look forward to receiving more. Please remember that I do this with my free time, and that I am not obligated to make all changes requested. That being said, I will do my best to accommodate "reasonable" requests. Thanks.
Additionally, at the top of the main ROM page there is also a section for Bug Reports. Please try to place all bugs, or possible bugs there. Again, this just makes things easier to keep track of. And as always, logcats are always appreciated when reporting issues.
Sent from my One X using Tapatalk
Black!Jack said:
Great to hear. As this was sort of a dry run I didn't add or take anything away from the initial build. However, moving forward, I will be adding some useful features, and removing some unneeded nonsense. At the top of the main ROM page there is a tab for Feature requests. If you, or anyone else has a request for something you would like to see added, or subtracted, please put it there. It will be easier for me to keep track of everything that way. I have already received some great suggestions and look forward to receiving more. Please remember that I do this with my free time, and that I am not obligated to make all changes requested. That being said, I will do my best to accommodate "reasonable" requests. Thanks.
Additionally, at the top of the main ROM page there is also a section for Bug Reports. Please try to place all bugs, or possible bugs there. Again, this just makes things easier to keep track of. And as always, logcats are always appreciated when reporting issues.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Sweet. Will do. I can't for the life of me think of anything to add I really like it as is but I'm sure there is room for improvement. Tomorrow I'll be taking the phone into "Cell reception hell" and we will see how it handles a lot of red lines in reception. There have been a few Roms that couldn't hang there.
And as for the free time, I take my hat off to you sir. I am pretty much in the same boat and I have to manage my time accordingly. I really want to churn out a Rom as well. Any tips and note you have would be much appreciated. I have Pheonixita's guide and a few other guides from the Android dev thread but I'm not there yet.
I envy you! JK (You are my hero right now though!)
Ok. Two days in "cell signal hell" and here's what I got. The phone only rebooted twice when the signal was weak or not present. I say "only" because other Roms rebooted multiple times during weak to no cell reception unless in airplane mode.
I captured a Logcat and I hope it is useful. Funny thing is, I'm not totally convinced it was a reboot because the phone woke up as usual but when I checked the battery status there was a gap with a red signal status underneath it.
I also included a screenshot so you can see when it happened.
The battery still had 40% when I plugged it in to transfer files so it's been pretty good.
For others, this is after extended periods in and out of extremely weak to no cell signal which is tough on any Rom. Even when the phone was stock I had reboots and shutdowns because of this.
I ran the 3.18 RUU and wiped my SD card last week to clean out the phone so I know the hardware is working great.
Madcat8686 said:
Ok. Two days in "cell signal hell" and here's what I got. The phone only rebooted twice when the signal was weak or not present. I say "only" because other Roms rebooted multiple times during weak to no cell reception unless in airplane mode.
I captured a Logcat and I hope it is useful. Funny thing is, I'm not totally convinced it was a reboot because the phone woke up as usual but when I checked the battery status there was a gap with a red signal status underneath it.
I also included a screenshot so you can see when it happened.
The battery still had 40% when I plugged it in to transfer files so it's been pretty good.
For others, this is after extended periods in and out of extremely weak to no cell signal which is tough on any Rom. Even when the phone was stock I had reboots and shutdowns because of this.
I ran the 3.18 RUU and wiped my SD card last week to clean out the phone so I know the hardware is working great.
Click to expand...
Click to collapse
I'm no expert with logcats, but right before AndroidRuntime started its shutdown process it looks like it was trying to load "xposed" binary 47. What xposed modules are you running?
Sent from my One X using Tapatalk
Black!Jack said:
I'm no expert with logcats, but right before AndroidRuntime started its shutdown process it looks like it was trying to load "xposed" binary 47. What xposed modules are you running?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I running greenify and CPU temp in status bar. I wonder if one of the Greenify experimental options caused it?
Black!Jack said:
Of course it is!
And just so that everyone knows, this DevDB project includes some important tabs at the top.
Screenshots
I have uploaded a bunch already, and I plan to add a whole lot more!
Downloads
In addition to my dev-host account, I will also be uploading them to XDA - you can find them in this tab; complete with md5 checksums.
Q&A
Pretty self explanatory. Let's keep anything not development related there; after-all, that is what it is there for! I will ask mods to move posts that do not belong here there. Repeated requests to the same people will get you BlackListed and ignored. Really, it's not that big of a request!
Click to expand...
Click to collapse
Nice Black!Jack your first KitKat! I thought about this one, but Ive got something else special coming.
Amazing rom, fantastic job.
wait what ? rom is all that but I think I am having a problem
the ringtone thing ... when its on vibration it works but when its on ringtone (there is sound) and some one call me I hear nothing and I cant notice my phone ringing ...
Never had that problem on this ROM. Did you clean flash?
Sent from my Evita
Getting ready to brunch new build now! Removed Asian apps. Attempting to integrate battery bar. Any last minute requests before I start the build? No promises though.
FYI... The work iPhone really sucks. Trying to be open minded, but not seeing anything that wows me. Mediocre at best, and definitely behind the times in features... From what I can tell so far. Oh, and you have to pay for everything. Pffffftttt. At least I got to keep my One XL too!
Sent from my HTC One XL using Tapatalk
Black!Jack said:
Getting ready to brunch new build now! Removed Asian apps. Attempting to integrate battery bar. Any last minute requests before I start the build? No promises though.
FYI... The work iPhone really sucks. Trying to be open minded, but not seeing anything that wows me. Mediocre at best, and definitely behind the times in features... From what I can tell so far. Oh, and you have to pay for everything. Pffffftttt. At least I got to keep my One XL too!
Sent from my HTC One XL using Tapatalk
Click to expand...
Click to collapse
The only APK I can think of would be F-Droid (open source play store equivalent). This Rom is outstanding. I don't see how this day can get any better. I picked up a Grouper for 30 bucks like new. The guy just didn't want it and never used it. lol.
P.S. Don't forget to let us know if it's a boy or girl!
I've got a new build ready. Uploading now.
This one is still completely stock. Bouncing between edits and housework (prepping for the baby). Hopefully tonight I can release the more feature packed version i have been envisioning.
Greetings Srs,
I'm the Zero 5 Pro owner which I guess, most of the Zero series owners, we are a little disappointed about the support from the vendor.
For this matter, I'm starting to compile from ASOP with the latest source code for this device.
I found Infinix already removed the stock firmware from the official website, so I can't find the current firmware which the device is currently running x603-h575b-n-190610v136 (if any of you have it back up and don't mind sharing the flashable version please add a link for the binaries, it could be useful).
I'm figuring the device tree, new kernel, and MT6575 documentation (along with the other device's documentation the phone it's built with) so I can customize as much as I can to make a clean build, no blobs, and trash, just to have a feel of the new Android in which I think a phone that could live a couple of years more.
Since the Android Studio AVD is not that customizable as I would like to replicate the phone components I0m looking for a decent emulator where I can specify the devices I know the phone has, and try it there first before going to the hardware itself.
Since I can't post directly in the Infinix Zero 5 Thread, if you please move the post to that thread, do so for me.
Also if you want to share advice, tips or suggestions, tools, etc, please feel free to let your comment below.
If I have news and advances in this process I'll be sharing under this same thread.
Cheers,
crappy OS GREAT HARDWARE...
Phronesis ROM had more useful function than the 05
Since lineage announced the official support for lineage 17.1. So just wondering if the moto g7 power will have official support for lineage 17.1. If so that would be great.
This coming weekend I may try a preliminary build. Seeing as the G7 and G7 Plus are officially supported, there's not much in the way of getting Lineage on this device, plus, we have build instructions for Lineage with MicroG floating on here - doable and much easier now, we just need someone to build and maintain for this device.
I'll take a stab with a build, but I doubt I have the free time to start maintaining a device with the now mandatory OT at work due to covid19.
I'll let you know if I have any success once it completes - my build box is pretty jank in terms of power and specs.
jbb3k said:
This coming weekend I may try a preliminary build. Seeing as the G7 and G7 Plus are officially supported, there's not much in the way of getting Lineage on this device, plus, we have build instructions for Lineage with MicroG floating on here - doable and much easier now, we just need someone to build and maintain for this device.
I'll take a stab with a build, but I doubt I have the free time to start maintaining a device with the now mandatory OT at work due to covid19.
I'll let you know if I have any success once it completes - my build box is pretty jank in terms of power and specs.
Click to expand...
Click to collapse
I had previously had success building lineage 16 micro4g using a docker script.
I also wanted to take a stab at making a preliminary build for 17.1
I figured i would download the 17.1 source code, then the moto g7 vendor, device, and kernel blobs.
I have dl the 17.1 lineage sources and the device sources: https://github.com/luizdores ( Credit to the dev) i imported into an xml file under local_manifests.
this is where i am stuck:
brunch ocean
[100% 139/139] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -l out/.module_paths/Android.bp.list -b out/soong -n out -d out/soong/build.ninja.d -globFile out/soong/.bootstrap/build-globs.ninja -o out/soong/build.ninja Android.bp
internal error: failed to find dex jar path for module "WfdCommon"
internal error: failed to find dex jar path for module "WfdCommon"
07:57:48 soong bootstrap failed with: exit status 1
#### failed to build some targets (56 seconds) ####
If you are able to get a successful build, please pm me or let me know b/c so far i haven't had any luck. I would be willing to help build the device.
I was going to use luizdores or rondeau's (crdroid10) parts for Ocean and shoot for the moon. That said, there are so few differences between the 3 devices - River, Lake, and Ocean - we should be able to get something that is at least bootable I expect. Usable may take a bit.
I did get tomorrow off work, so I have 3 days to bang my head against the wall on this. I'll let you know how my builds go, and we can compare notes on what we missed or what may be needed.
jbb3k said:
I was going to use luizdores or rondeau's (crdroid10) parts for Ocean and shoot for the moon. That said, there are so few differences between the 3 devices - River, Lake, and Ocean - we should be able to get something that is at least bootable I expect. Usable may take a bit.
I did get tomorrow off work, so I have 3 days to bang my head against the wall on this. I'll let you know how my builds go, and we can compare notes on what we missed or what may be needed.
Click to expand...
Click to collapse
I was able to successfully build it on the second try! Looks like I forgot android_external_bson and android_system_qcom in my original .xml file.
I also switched from luizdores to grimtruth repos(credits to both devs).
I hope to flash it in the next day or so. Attached is the xml file i created and put in my local_manifests dir.
Hey guys! Dunno if you know, but we have a Telegram group where there's already a working Lineage Q ROM and devs happy to receive new friends . Can't send you any link, but search us.
BETA215 said:
Hey guys! Dunno if you know, but we have a Telegram group where there's already a working Lineage Q ROM and devs happy to receive new friends . Can't send you any link, but search us.
Click to expand...
Click to collapse
Why is Telegram used instead of XDA? Is that common now?
Greek2me said:
Why is Telegram used instead of XDA? Is that common now?
Click to expand...
Click to collapse
It is pretty common nowadays and the Moto G7 Power telegram is probably the best group of people there is. I just go there and read. I don't usually comment except on rare occasion. They're most always doing things. I think we have pretty close to every custom rom there is to date already made for this device and they all work really well too. I signed up for the "text free" app off PlayStore and used the VoIP phone # from that to sign up on telegram. Super easy! If XDA had a telegram type app I'm sure people would be using it.
PS: There is a Lineage 17.1 build and it has May security patch and it's great! You probably already know this by now. I just noticed the date on your post. ?
flash713 said:
It is pretty common nowadays and the Moto G7 Power telegram is probably the best group of people there is. I just go there and read. I don't usually comment except on rare occasion. They're most always doing things. I think we have pretty close to every custom rom there is to date already made for this device and they all work really well too. I signed up for the "text free" app off PlayStore and used the VoIP phone # from that to sign up on telegram. Super easy! If XDA had a telegram type app I'm sure people would be using it.
PS: There is a Lineage 17.1 build and it has May security patch and it's great! You probably already know this by now. I just noticed the date on your post.
Click to expand...
Click to collapse
Yeah. I don't understand why Telegram? why everybody using whatsapp with privacy issues because of Facebook ownership or Telegram, sth with weak security and which is probably controlled by russian intelligence? why not Signal for example?
xyzex said:
Yeah. I don't understand why Telegram? why everybody using whatsapp with privacy issues because of Facebook ownership or Telegram, sth with weak security and which is probably controlled by russian intelligence? why not Signal for example?
Click to expand...
Click to collapse
Yeah I'm not sure about using telegram either but looks like that is what everyone is using now.
twfs said:
Yeah I'm not sure about using telegram either but looks like that is what everyone is using now.
Click to expand...
Click to collapse
I peruse the file hosting sites. Google search gets some t.me content, but haven't seen anything not listed on the top 4 or 5 popular hosting and official ROM sites.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RootMyTV is a user-friendly exploit for rooting/jailbreaking LG webOS smart TVs.
Website: RootMy.TV
GitHub: https://github.com/RootMyTV/RootMyTV.github.io
For further details, and a full writeup, please check out the GitHub repo.
Spoiler: Original pre-release post
TL;DR; If you want root on any* current WebOS LG TV, do not install updates for the time being, and wait patiently. If you're a developer or researcher, read the latest update below.
*The exploit requires "ThinQ" support, which seems to only be available on TVs running WebOS 4.0+. I will update this when we know more about which versions support it.
RootMy.TV is an 0-click (kinda) web-to-root exploit for WebOS.
Website (placeholder): RootMy.TV
GitHub (placeholder): github.com/DavidBuchanan314/RootMyTV
After this bug in Download Manager was published (which, on its own, allows rooting the WebOS emulator), I was motivated to find new bugs which can be combined with it, to get root on actual TVs.
Given the relatively severe impact of this exploit chain, its publication will have to wait at least until LG makes official patches available for the Download Manager bug. After that, I will be publishing the exploit, along with a full writeup.
During my research, I received invaluable advice and information from members of the openlgtv Discord server - I definitely couldn't have done this without them. Please join us, if you would like to assist with testing the exploit etc. in the hopefully-near future: https://discord.gg/9sqAgHVRhP
Update 2021/02/15:
LG claims to have fixed the Download Manager bug, but they haven't really. To motivate LG to actually patch the bug, I will be disclosing my exploit chain to them under a 30-day public disclosure deadline - after which, I will be publishing the exploit here. Assuming I send my disclosure to LG email tonight, that sets the RootMyTV "release date" at 2021/03/19.
Update 2021/03/18:
The release date is now 2021/03/21 - I have a few things I need to finish up...
Update 2021/03/23:
Sorry for the delays...
I am attaching a bare-bones vulnerability report and PoC for the exploit, which is enough to get you root. This "pre-release" is intended for developers and researchers. If you're not a developer or researcher, please be wait for the "full" release, which will hopefully arrive in the coming weeks. The final release will be more user friendly, and include a "Homebrew Channel". If you would like to contribute to development of the Homebrew ecosystem, please visit us on Discord.
Some notes/disclaimers about the exploit: (READ FIRST!!!)
- This will void your warranty, don't blame me if anything goes wrong etc. etc.
- Amazon's "google play store" link, described in the writeup, is currently broken. As a workaround, you can search for "google search" on Amazon, Click the top result, Click "developer info", then click the link to Google's privacy policy. From there, you can click the menu icon in the top-right and continue with the rest of the instructions.
- Something I forgot to mention in the report - you must update the value of the "HOST_PREFIX" variable in index.html, to point to your local webserver.
- If you were previously using Developer Mode, then overwriting `start-devmode.sh` will have broken devmode features like `ares-install`, and the jailed sshd. You can fix this by putting the old `start-devmode.sh` back again, with some edits.
- For some TVs that don't have the ThinQ login page, you can access an equivalent page via "Account Management" in the settings. This doesn't work on my TV (the amazon link opens in the web browser), but apparently it works on some models/versions.
- The current version of the exploit will give you a root telnet server, accessible on the default port (23), without authentication.
Hi, my device OLED65CX6LA wait your Hack ..
This is exciting! I knew in my gut that I should avoid the update I saw pop up a few days ago. Can't wait to see what this all entails. Please give us an update when you can! :]
great job, thanks for this, can't wait for the final release
Thanks again for the efforts! I can confirm that worked like charm, I have tested on LGC9 05.00.03, very smooth, haven't seen any errors.
For me worked
OLED65CX6LA in italy
soft ver. 03.21.16
thanks
Connected to lgwebostv.fritz.box.
Escape character is '^]'.
webOS TV 5.2.0 LGwebOSTV
/ # ls
bin etc lib mnt proc share usr
boot home linuxrc opt run sys var
dev lg media overlay sbin tmp www
/ #
is possible to use oscam now?
lg 55uk6470plc
software version 5.30.10
WebOS version 4.3.0-9703
Confirmed working!
Is it possible to install Web OS FW of a LG Commercial Signage Display on to a matching Consumer Retail model? How?
I am the same model as your TV. However, as you mentioned, I searched for google search on Amazon and went in, and after that, I proceeded the same, but rooting did not work. Are there any other points where I can rooting?
Using com.webos.app.iot-thirdparty-login in webOS 4.9.1-53409 for this exploit doesn't seem to work anymore, because the app now seems to open all links in the web browser app instead of its own instance. No matter which link I tested, they all open the external web browser.
Update:
The underlying issue still exists though and I managed to use a slightly different method but the same privilege escalation method to get in anyways.
Code:
Connected to XXXXXXXXXX.
Escape character is '^]'.
webOS TV 4.9.1 LGwebOSTV
/ # uname -a
Linux LGwebOSTV 4.4.84-169.gld4tv.4 #1 SMP PREEMPT Fri Mar 12 02:53:12 EST 2021 aarch64 GNU/Linux
/ # whoami
root
LLP42 said:
Using com.webos.app.iot-thirdparty-login in webOS 4.9.1-53409 for this exploit doesn't seem to work anymore, because the app now seems to open all links in the web browser app instead of its own instance. No matter which link I tested, they all open the external web browser.
Update:
The underlying issue still exists though and I managed to use a slightly different method but the same privilege escalation method to get in anyways.
Click to expand...
Click to collapse
Perhaps you might share the approach you found so others don't struggle helplessly?
I had the same problem. After getting to the Amazon log in page, all links mentioned above opened in the web browser instead of within the ThinQ app. Eventually I tried entering non existent credentials into the Amazon login form, then after being prompted to enter a captcha, I again entered invalid credentials a second time. When shown the login form a third time I clicked the bottom link (can't remember what it was - maybe privacy or forgot password or similar) and this time the link opened within the ThinkQ app rather than an external browser, and I could then follow the rest of the exploit successfully.
Does rooting WebOS remove the DRM? Could someone check if Netflix is still working?
And if the DRM will be removed, is it possible to restore it by resetting it by it's factory defaults or a software update?
@retr0id awesome work! Have been waiting on this for a long time
roykaandorp said:
Does rooting WebOS remove the DRM? Could someone check if Netflix is still working?
And if the DRM will be removed, is it possible to restore it by resetting it by it's factory defaults or a software update?
@retr0id awesome work! Have been waiting on this for a long time
Click to expand...
Click to collapse
Currently root exploit in the first post only exposes root unjailed telnet session and disables some telemetry. It does not affect any existing apps, unless content providers add explicit root detection. (which in of itself would require jail escape exploit on their part) Netflix seems to work fine so far on 2018-era webOS 3.8 LG TV.
spartakles said:
Perhaps you might share the approach you found so others don't struggle helplessly?
Click to expand...
Click to collapse
If there really is a "0-click" exploit as promised, these steps become unnecessary.
Until then, anyone who knows the ropes should have no problem finding the way I mentioned. At least when you take a closer look at the source code of com.webos.app.iot-thirdparty-login. And if you have problems with this, you should probably leave this method alone anyway.
That's why I won't post any more details about it - at least for now.
LLP42 said:
If there really is a "0-click" exploit as promised, these steps become unnecessary.
Until then, anyone who knows the ropes should have no problem finding the way I mentioned. At least when you take a closer look at the source code of com.webos.app.iot-thirdparty-login. And if you have problems with this, you should probably leave this method alone anyway.
That's why I won't post any more details about it - at least for now.
Click to expand...
Click to collapse
What gibberish.
I provided a way forward to others in my response. I followed it and it worked, so I shared it.
You simply turned up with no useful information, just to say "hey your instructions no longer work. I found a way round it. Not going to share". It would seem you're posting on entirely the wrong forum.
spartakles said:
You simply turned up with no useful information, just to say "hey your instructions no longer work. I found a way round it. Not going to share"
Click to expand...
Click to collapse
That's not true at all. The info I shared is that the vulnerability is still present in the latest firmware v05.00.30 of the 2019 models and that it's still possible to use the exploit.
I also said that I do not share the details "for now", depending on the "0-click" exploit status.
spartakles said:
It would seem you're posting on entirely the wrong forum.
Click to expand...
Click to collapse
The official subtitle of this forum is:
Technical discussion of WebOS development and hacking. No noobs please.
Click to expand...
Click to collapse
So if anyone is wrong here, it's you.
This forum is not for users who need step-by-step instructions.
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
has anyone tested a LG 65SK8500LLA? Dont want to brick my one
MaxSnacks18 said:
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
Click to expand...
Click to collapse
If I am not wrong the OS does verification , so trying to modify something will trigger it to not boot....
As of now.
MaxSnacks18 said:
If someone can use this to make a custom firmware that adds back in the 120hz black frame insertion to the LG C9 (and maybe even older models) that would be amazing. LG removed the feature last minute despite it showing up in C9 reviews samples, but it did make it into the CX as OLED motion low and mid. I remember in some old interviews hearing that the feature is all algorithm based and could be added into older OLED TVs but they never did.
Click to expand...
Click to collapse
You're in luck. Just this week a user at AVSForum reported that you could enable Motion Pro on the C9/E9 with a simple command on the tv. The only disadvantage was that you need to execute this command with root privileges. Now that is where this thread comes in.
I've managed to get root access to my C9 and have executed the command and it works! Motion Pro low, medium and high is available and works at 120Hz.
This is the command that you need to execute:
Code:
luna-send -n 1 -f "luna://com.webos.service.config/setConfigs" '{ "configs": { "tv.model.motionProMode": "OLED Motion Pro" } }'
To get more android ROMs 11 and 12 I need the support of the community and the way to give it is by testing my builds
I am currently unofficially maintaining moto e5+ havocOS and working on the creation of the 4.9 kernel which will be a huge improvement on the existing roms with new additions like EAS and more which will allow better performance, battery life and why not a small or medium overclock when I figure out how to do it right.
This also opens the way to stable android 12/L builds (remember that the current kernel 3.18 is not supported on android 12 and while the builds do start they are quite buggy.
for the work with 4.9 I am receiving a great help in the development from marcost22 but in addition to developing the kernel if it is not tested it is a waste of time, we are doing everything possible so that the device does not die and if you want that is yours time to help
there is currently no 4.9 support for hannah and ahannah so if you want to be a tester and you have that variant the builds will take time to arrive as I have to spend some time adding the dtb and first I prefer the kernel to be somewhat functional
in case you were wondering the builds with 4.9 already start but have some issues like audio, fp, gps, vibration and the camera can't record video, once that is fixed we will start working on adding support for the remaining variants and stuff like EAS and frequencies, after this I will build havoc with 4.9 and start working on android 12/L
I don't usually look at xda's private messages much, so it would be better if you send a message to @STKUser , if you don't know things like how to get logs don't worry because nobody is born knowing and everything can be learned.
With the help of the community great things can come, stay tuned.