READ THIS!
Me, myself, and I do NOT own ANY OF THIS nor do I take credit for any of this amazing work. I am simply reposting with some updated information. I will leave links for EVERYTHING.
OKAY AGAIN, LISTEN UP. Flashing ANYTHING like this may void certain warranties; and I, Albinoman887, or anyone else is responsible for dead SD card, broken SIM's, or bricked phones, or anything bad that may result from this. You are SOLELY responsible and are doing this at YOUR own risk.
All credit goes to TeamDouche and all other coders who contributed to CyanogenMod.
These builds are for KLTE (GSM) and (CDMA) variants.
Included in the unified (GSM) build are: KLTEXX, KLTELRA, KLTEMO, KLTECAN, KLTEACG, KLTEDCM, and KLTE
*Individual CDMA builds: KLTESPR and KLTEUSC*
*Individual GSM buulds: KLTEDV*
So, if your device is not listed in one of the Individual lists (The ones marked with an asterisk) Then you should flash the "Unified GSM" (Or KLTE) build.
So here are the features,
Built from CM Source
Service
Text
Data
Calling
Audio
Wi-Fi
Google Now
Bluetooth*
GPS
MMS
Video Playback
Audio Playback
Internal SD Card mounting
External SD Card mounting
IR Blaster**
NFC
*There has been reported issues of Bluetooth stuttering and some random crashes. This is a known issue. Complaining about it will do absolutely nothing. With that information, do what you will.
**IR Blaster has been tested using the Peel IR Remote (Link: https://play.google.com/store/apps/details?id=tv.peel.app&hl=en
Please note, some CyanogenMod Features have NOT been added yet, so be patient and don't be annoying about this.
Some things you do NOT want to do when flashing this,
Do NOT use superwipes,
Do NOT dirty flash, (And if you do, do NOT report bugs), do a clean flash (Which is wiping Data, Cache, and Dalvik Cache)
Download links!
Latest tested release is cm-13.0-20151227
G900I (kltedv) : http://www.team-hydra.org/kltedv/rel/
G900P (kltespr) : http://www.team-hydra.org/kltespr/rel/
G900R4 (klteusc) : http://www.team-hydra.org/klteusc/rel/
G900V (kltevzw) : http://www.team-hydra.org/kltevzw/rel/
If your phone's specific model number was NOT listed above and is a CDMA device, it is sadly NOT supported, for all other GSM devices flash the "Unified GSM" Build below.
KLTE Build archive: http://www.team-hydra.org/klte/rel/
GApps Package: www.opengapps.com
FLASHING INSTRUCTIONS!
You must have TWRP Installled in order to flash this ROM! Others may work but have NOT been tested!
This is really quite simple if you do this step by step.
Step 1.
Download the build specific for your device and grab a GApps package.
Step 2.
Move these over to an SD Card
Step 3.
Wipe Data, Cache, and Dalvik Cache.
Step 3.
Flash the downloaded Cyanogenmod .zip folder
Step 4.
Wipe Cach and Dalvik Cache
Step 5.
Flash GApps package
Step 6.
Wipe Cache and Dalvik Cache
Step 7.
Reboot System!
And congrats! It should work! And you can brag to all of your dev friends and tell them you're running Android version 6.0.1 ( Although the S5 has Marshmallow for it already.. :/ )
Now, here I will talk about NIGHTLIES,
IF you want to be as up to date as possible, I recommend flashing the NIGHTLY builds. The only thing is they may have some bugs lurking around. Although, I use these and have had NO problems whatsoever.
Unified GSM (klte) : https://download.cyanogenmod.org/?device=klte
G900I (kltedv) : http://www.team-hydra.org/kltedv/nightly/
G900P (kltespr) : http://www.team-hydra.org/kltespr/nightly/
G900R4 (klteusc) : http://www.team-hydra.org/klteusc/nightly/\
Hey, have a heart and donate to Albinoman877!
He does a lot, show your support!
Here's the link to a PayPal you can donate to. (Note, the name on the account says Patricia as it is a family account)
https://www.paypal.com/us/cgi-bin/w...63663d3faee8d6625bf1e8bd269586d425cc639e26c6a
I will be happy to answer any questions but note that I am NOT a developer, so I'll only be able to answer SOME more basic or "noob" questions. For everything else, post on the original thread.
THE ORIGINAL THREAD WHERE ALL IF THIS IS FROM IS HERE:
http://forum.xda-developers.com/gal...ent/rom-cyanogenmod-13-0-android-6-0-t3237502
And why is this thread needed in the Development section?
The original CM13 thread has all the information and the magical "search" button.
Any noob should first go through the General and Q&A sections before arriving here.
Could an admin close this useless thread?
Thank you in advance.
AlexVat said:
And why is this thread needed in the Development section?
The original CM13 thread has all the information and the magical "search" button.
Any noob should first go through the General and Q&A sections before arriving here.
Could an admin close this useless thread?
Thank you in advance.
Click to expand...
Click to collapse
Its a more noob friendly version, as I myself have helped many noobs over on the original thread. Making this was am attempt to help them and get rid of noobish questions, as it gets repetitive and annoying.
On top of that, this has some updated information concerning GApps, bugs, and etc. as previously stated.
AlexVat said:
And why is this thread needed in the Development section?
The original CM13 thread has all the information and the magical "search" button.
Any noob should first go through the General and Q&A sections before arriving here.
Could an admin close this useless thread?
Thank you in advance.
Click to expand...
Click to collapse
As well as those reasons, I am also planning on compiling for smaller devices that aren't supported in the original thread.
The last Cyanogenmod has fingerprint working, so if this is build from official CM13 source it should be working too
TacoTank said:
As well as those reasons, I am also planning on compiling for smaller devices that aren't supported in the original thread.
Click to expand...
Click to collapse
Yeah, man, but still this shouldn't be posted in the Development section
Right now there is zero development on this thread. In the future I plan to cook a ROM myself but you don't see me raising threads in the Dev section. Just saying
AlexVat said:
Yeah, man, but still this shouldn't be posted in the Development section
Right now there is zero development on this thread. In the future I plan to cook a ROM myself but you don't see me raising threads in the Dev section. Just saying
Click to expand...
Click to collapse
Which section should I put this in then?
TacoTank said:
Which section should I put this in then?
Click to expand...
Click to collapse
In my opinion it should be in the General section as an ultra-noob walkthrough guide for installing CM13 from absolute scratch. With the links towards a compatible recovery, root, as well as all the risks involved (breaking knox, changed/lost imei etc.)
AlexVat said:
In my opinion it should be in the General section as an ultra-noob walkthrough guide for installing CM13 from absolute scratch. With the links towards a compatible recovery, root, as well as all the risks involved (breaking knox, changed/lost imei etc.)
Click to expand...
Click to collapse
Alright, can a mod move this thread over to the general section please? And sorry for any troubles man. Thanks.
In this version of CM are we able to move apps, backups, TWRP files to the external SD card?
Motorola Moto E (4th Gen) xt1766 SPerry
Sprint, Boost Mobile, Virgin Mobile, TextNow
Stock Android 7.1.1 Nougat
Build No. NCQS26.69-64-11
TWRP Flashable Installer
WARNING • • • • • • •
Altering, modifying or otherwise tampering with your device's stock filesystem configuration will render your warranty null & void, and carries with it an inherent risk of causing damage to your device. By proceeding further, you acknowledge and understand any such risks, and take sole accountability for the integrity of your device. You are encouraged to fully read this guide prior to performing any steps. I assume no liability in the event you damage your device or render it unable to function normally. However, with that having been said, should you encounter any adverse issues installing any of the files herein, stay calm and describe your issue in comments, using clear and concise dictum. I will assist to the best of my ability to help you troubleshoot your problem. Follow the below instructions carefully, paying close attention to detail, and things should go smoothly.
• • • • • • • • • • •
IMPORTANT NOTE: I am new to XDA and I'm here to learn and grow as an Android enthusiast. When posting, please be respectful to me and other members. Under no circumstances should members ask for ETAs, updates, etc. Also, I respectfully ask that this thread stay on topic with stock ROM related subject matter only.
--SPECS:
• Model: Qualcomm xt1766 SPerry Only
• Providers: Sprint, Boost Mobile, Virgin Mobile
• Android Version: 7.1.1 Nougat
• Build No. NCQS26.69-64-11
• Kernel: Linux 3.18.31-perf
• Radio: M8920_15000.280.06.58.06R
• Security Patch Level: November 1, 2018
• Build Date: November 18, 2018
--CHANGELOG:
This is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
•Kernel Source Code: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NCQ26.69-48
--FEATURES:
• Systemless Root: Magisk v18.0-stable
• Init.d & su.d support
• BusyBox: v1.29.3 static binaries
• SafetyNet Pass: ctsProfile & basicIntegrity
• AVB/dm-verity disabled
• Force encryption disabled (opt encrypt)
• Zipaligned /system/app & /framework
• Debloated (see links below for debloated build)
--REQUIREMENTS:
An unlocked bootloader and TWRP custom recovery are required for installation of this ROM. I strongly recommend @squid2's TWRP v3.2.1-r1, to ensure the best results on installation. After installation of this ROM, you may then update your TWRP version/build. Also, for best results, you'll need an external microSD with at least 1.5 GB free storage space.
--INSTALLATION GUIDE:
1. Recommended -- download the baseband updater from the link below and install it via TWRP;
2. Download the ROM zip and save it to your device's external storage;
3. Boot into TWRP recovery mode. Perform a wipe on /system, /cache, & Dalik. Now select Wipe again and format /userdata (this is crucial to disabling force encryption);
4. Select Install, navigate to the saved location of the ROM zip on external storage, and commence with installation;
5. Done. Reboot System
** Following initial installation, prior to completing setup, it is completely normal to experience a couple of bootloops. Just be patient.
--F2FS LOOPBACK KERNEL BUG:
Like a great many Motorola smartphones, the Moto E4 (xt1766) ships with an inherent kernel issue known as the f2fs loopback bug. In a nutshell, the xt1766's /userdata partition is formatted using the f2fs filesystem standard. The bug prevents loopback devices (.img files) from being mounted read/write (R/W). Because Magisk implements a magisk.img loopback configuration for systemless root and systemless modifications, the inability to mount read/write is extremely problematic. Luckily, a workaround exists as a Magisk module, known as the F2FS Loopback Bug Workaround. The module works by moving magisk.img to the /cache partition, which uses the ext4 filesystem type, then symlinking it to its actual location in the /userdata partition (/data/adb/magisk.img). Moreover, shortly following each and every reboot, magisk_merge.img is automatically regenerated and is handled in the same manner as magisk.img. With this workaround, a patched or modified kernel is not needed.
After the initial setup following first boot, open the Magisk Manager app and follow all prompts and grant any necessary permissions. Then go to the Downloads section within the Magisk Manager app and find the F2FS Loopback Bug Workaround module. Download it, boot into TWRP recovery mode and install the module. On reboot, the Modules section in the Magisk Manager app should indicate that the F2FS module is installed. To avoid any future issues, it is strongly advised to install any and all Magisk modules from TWRP recovery mode, versus installing them via Magisk Manager.
DEBLOATED BUILD:
I have added a debloated build to the links below. This ROM has all attributes of the standard build except that I have removed all annoying Amazon and carrier-specific bloatware from /oem/app and /oem/priv-app. In addition, I have removed many non-essential Google apps from /system/app and /system/priv-app, leaving a moderately slimmed down and bloat-free stock ROM. This ROM should be installed using the above instructions as well.
THANKS/MENTIONS:
Thanks to @VR25 for his Magisk module for the f2fs loopback bug.
Thanks to @squid2 for his TWRP builds for this and many other Moto devices. Thanks to @topjohnwu for his Magisk Universal Systemless Interface and, last but not least, thanks to @madbat99 for his warm welcome to me, and his encouragement, and to @Davey126.
--BUGS:
No known bugs
Download Links:
_______________________________________________
Baseband (radio firmware) Updater
Version: M8920_15000.280.06.58.06R: https://drive.google.com/file/d/1YckU38KUWL9YiHP4eafVteK0zArcXonu/view?usp=drivesdk
Stock ROM (Rooted, BusyBox)
Build No. NCQS26.69-64-11: https://drive.google.com/file/d/19bEz9nHZn9NP42RAl4VQGfR8WSO_Bc9y/view?usp=drivesdk
Stock ROM (Debloated, Rooted, BusyBox)
Build No. NCQS26.69-64-11: https://drive.google.com/file/d/1EMkriY3thTejiyRndiSjM-hoQdGuh-3X/view?usp=drivesdk
Stock Recovery: https://drive.google.com/file/d/1GLj-2lMkuwJFlLMYs-S754oDv0YfgdUQ/view?usp=drivesdk
Unmodified Stock Boot Image
(secure boot, avb/dm-verity, force encrypt): https://drive.google.com/file/d/1Rau38EC2FTiuu-4MFhbzatagDlWe7hvI/view?usp=drivesdk
Debloated & deodexed version in the works.
Nice opening move to XDA. Contributing instead of leeching.
Wish I still had this device.
If I had a bic lighter in my hand bro... It would be lit in the air
madbat99 said:
Nice opening move to XDA. Contributing instead leeching.
Wish I still had this device.
If I had a bic lighter in my hand bro... It would be lit in the air
Click to expand...
Click to collapse
Thank you for the warm welcome @madbat99
Yeah, I noticed a lot of what you mentioned before I ever joined up. Seems like a lot of demanding, disrespectful behavior goes on. I see the Android Community as a place where we should all give and take equally. I can tell that you have that ideology, and I wish there were more like you.
Welcome! Thanks for the ROM, I will be trying it out soon.
Just curious as to how important it is to update the baseband? Will this rom still work if you don't? Thanks for any info about this or what updating it does.
[email protected]@bl3s said:
Just curious as to how important it is to update the baseband? Will this rom still work if you don't? Thanks for any info about this or what updating it does.
Click to expand...
Click to collapse
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
madbat99 said:
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
Click to expand...
Click to collapse
Aww - come on! No spoon feeding? ?
In all likelihood, this ROM should work fine with the previous baseband (M8920_15000.280.05.58.05R) version. However, I cannot confirm this one way or the other. For members fearing that updating the baseband will cause issues on custom ROMs (as has been the case on past OTAs), it certainly won't hurt to try installing this ROM without first updating the baseband. After all, once the baseband is updated, there is no going back. Like an old carpenter used to tell me, "it's always better to cut a board too long than it is to cut it too short."
But to emphasize, there were some significant changes made to the radio firmware via the latest update. For the best results, it is strongly recommended that you update your baseband in accord with the latest incremental update. With that being said, if updating the baseband does cause adverse issues on any custom ROMs, please don't use this thread as a forum to address any such grievances. Should I get any type of confirmation on this, I will certainly include such info in the OP.
To reiterate the OP and to stress what @madbat99 suggested, guys (& girls) please read the instructions and my informal changelog carefully, before installing anything. If there is something that isn't clear, please ask. If I don't know the answer then I'll do my best to find out.
Davey126 said:
Aww - come on! No spoon feeding? ?
Click to expand...
Click to collapse
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
LenovoTech said:
In all likelihood, this ROM should work fine with the previous baseband (M8920_15000.280.05.58.05R) version. However, I cannot confirm this one way or the other. For members fearing that updating the baseband will cause issues on custom ROMs (as has been the case on past OTAs), it certainly won't hurt to try installing this ROM without first updating the baseband. After all, once the baseband is updated, there is no going back. Like an old carpenter used to tell me, "it's always better to cut a board too long than it is to cut it too short."
But to emphasize, there were some significant changes made to the radio firmware via the latest update. For the best results, it is strongly recommended that you update your baseband in accord with the latest incremental update. With that being said, if updating the baseband does cause adverse issues on any custom ROMs, please don't use this thread as a forum to address any such grievances. Should I get any type of confirmation on this, I will certainly include such info in the OP.
To reiterate the OP and to stress what @madbat99 suggested, guys (& girls) please read the instructions and my informal changelog carefully, before installing anything. If there is something that isn't clear, please ask. If I don't know the answer then I'll do my best to find out.
Click to expand...
Click to collapse
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
madbat99 said:
Did you by chance read the op? Specifically the part that says "changelog?
Try again, you'll see your answer.
C'mon dude, the thread isn't even 1 full page yet and people are already skipping the original post.
Click to expand...
Click to collapse
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
[email protected]@bl3s said:
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
Click to expand...
Click to collapse
Not to start the thread off on a negative note or get into quarrels, and not to take sides, but I honestly don't believe anybody was necessarily talking down to you. There have been a number of threads on this device where members don't read the OP or don't read warnings, then they blame devs & contributors when things go wrong. @madbat99 and @Davey126 are both extremely knowledgeable individuals in the Android community. I think I can speak for then both by saying that they simply want to see members take greater care and pay more attention to detail. Such would keep these threads running more smoothly. I'm glad my elaboration gave you some insight, but please refrain from flaming or name-calling on the thread. I ask you that with respect. Thank you.
[email protected]@bl3s said:
Yeah, no spoon feeding but plenty of talking down to. You people are a$$holes and you know it. ?
---------- Post added at 10:22 AM ---------- Previous post was at 10:20 AM ----------
Thanks for actually answering the question rather than just talk down to me.
---------- Post added at 10:25 AM ---------- Previous post was at 10:22 AM ----------
Extremely helpful answer. You honestly would have been more helpful had you said nothing. Thanks for nothing. i see lenovotech posted the info I was looking for below.
Click to expand...
Click to collapse
I wasn't really talking down, just some light hearted sarcasm.
But I did answer you. Op says what the baseband does. I didn't have time to retype it, so I just mentioned where it was.
To be fair, the rules we all agree to when we sign up say, to fully read the OP and at least the last 10 pages of a thread before asking a question that may be answered already.
A successful, easily flashable stock ROM is just what this device needed.
LenovoTech said:
Not to start the thread off on a negative note or get into quarrels, and not to take sides, but I honestly don't believe anybody was necessarily talking down to you. There have been a number of threads on this device where members don't read the OP or don't read warnings, then they blame devs & contributors when things go wrong. @madbat99 and @Davey126 are both extremely knowledgeable individuals in the Android community. I think I can speak for then both by saying that they simply want to see members take greater care and pay more attention to detail. Such would keep these threads running more smoothly. I'm glad my elaboration gave you some insight, but please refrain from flaming or name-calling on the thread. I ask you that with respect. Thank you.
Click to expand...
Click to collapse
Ok, my apologies for getting upset. And I ageee with you, both madbat and davey are both pretty dang helpful on these forums. I've seen them on many different device forums for the same devices I have and they have both even replied to me and helped before (not to this account btw, another account that I lost access to) However sometimes it really seems that they do kind of make fun of,/poke fun at someone asking a simple question or they talk to them in a sort of condescending manner that isn't very helpful and sometimes makes the person asking the question feel attacked. I've seen it on more than one occasion. The times that they are very nice and helpful is way more than the times they aren't though. My apologies to both of these guys in this post. And once again thanks lenovotech for the amswer that you provided. I do appreciate it.
One last joke...? Don't hate me.
And for my own redemption... It is there in the op. @[email protected]@bl3s
Keep in mind, I gave you a thanks bro.
-CHANGELOG:
This build is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
madbat99 said:
One last joke...? Don't hate me.
And for my own redemption... It is there in the op. @[email protected]@bl3s
Keep in mind, I gave you a thanks bro.
-CHANGELOG:
This build is an incremental update from the NCQS26.69-64-10 build number, bringing the build up to NCQS26.69-64-11. With this update comes typical bug fixes, stability improvements, and Google security patches up to November 1, 2018. More noteworthy is the update to the radio firmware (baseband), from version M8920_15000.280.06.58.05R up to version M8920_15000.280.06.58.06R. This update patches some integrity issues with LTE data connectivity in some North American regions, improves seamless cellular data handover in domestic roaming scenarios, and fixes instabilities with 4G/LTE Band 41 (TDD-LTE), improving upon carrier aggregation. It should be noted that my stock ROM installer does not update your radio firmware, but only the Android OS, the /OEM partition, and the stock boot image. If you have not updated your device to NCQS26.69-64-11 by OTA or firmware package, you are strongly encouraged to update your radio firmware now, by downloading my baseband updater from the link below, and installing it via TWRP.
Click to expand...
Click to collapse
You just like to stir the pot don't you?
After lenovotech was professional with his response (which actually answered my question, unlike your replies) I made my apology for getting upset and yet you still feel the need to come in this thread and try to be funny (btw, your "joke" really isn't funny. Don't quit your day job bro) I guess this is just how xda is anymore. You should take notes on keeping things professional rather than trying to be funny. Like I said before your replies in this thread have been less than helpful. You have been more than helpful in numerous other threads I've seen you in so not sure why your posts in this particular thread are so useless/unhelpful.
Anyways, No hard feelings. Lenovotech did answer my question so I'm good and may flash this rom within the next few days.
P.s. I will not be replying back to anything/anyone relating to this off topic nonsense. I'm here for info on android and nothing else. Thank you lenovotech for the rom btw. ?
[email protected]@bl3s said:
P.s. I will not be replying back to anything/anyone relating to this off topic nonsense. I'm here for info on android and nothing else. Thank you lenovotech for the rom btw. ?
Click to expand...
Click to collapse
Excellent. Looking forward to more relevant posts which assumes due diligence prior to asking questions.
My post, and subsequent copy of op, literally answered the question to the letter. And even prompted a smile with the "member's" misinterpretation of my post (and the rules for that matter), and I'm still the bad guy....
Nice
Ba da bomp bomp baaa, I'm lovin it.
Guess I'm too old for the new generation.
We old timers realize when we jump to the wrong conclusion and are usually quick to laugh at ourselves.
No hard feeling intended, felt, or taken.
This thread will soon be populated by people thanking op for this. My guess, op has a great future here.
madbat99 said:
My post, and subsequent copy of op, literally answered the question to the letter. And even prompted a smile with the "member's" misinterpretation of my post (and the rules for that matter), and I'm still the bad guy....
Nice
Ba da bomp bomp baaa, I'm lovin it.
Guess I'm too old for the new generation.
We old timers realize when we jump to the wrong conclusion and are usually quick to laugh at ourselves.
No hard feeling intended, felt, or taken.
This thread will soon be populated by people thanking op for this. My guess, op has a great future here.
Click to expand...
Click to collapse
@madbat99 I have long been reading your threads, posts and guides, way before I took the leap and joined up. In short, you have been giving me Android knowledge long before I got the opportunity to meet you here. I consider both you and @Davey126 two of the most knowledgeable members on Motorola devices (and Android in general) here on XDA. So, your encouragement and kind words mean a lot. There is no doubt I will need your insight and advice during my journey on XDA. So I do want to sincerely thank you (and @Davey126) for everything.
Davey126 said:
Aww - come on! No spoon feeding? ?
Click to expand...
Click to collapse
reason my g6 play and E5 + twrp and decrypt guidez are short and simple
I have attempted to download the rooted stock, limited to my phone I have been unsuccessful. I'm not rooted, running the stock ROM. On either WiFi or network, it fails to download. I have been able to add it to my drive, but can't get it to work from there. I'm probably treading in off topic but I have tried everything I know with zero results. I'm hoping someone could suggest something that could help.
Galaxy Rom S20 Port for N960X + G960X-G965X
Changelog:
* Android Q | Version 10
* Base on latest Galaxy Note9 firmware
* Base port G985FXXU1ATBM
* Support multiple languages
* Support multiple CSC
* Patched SecureFolder
* Enable many hiden feature like:
App lock, Network speed, Screen capture toogle, etc...
* Enable Multi user
Official:
Telegram
MOD EDIT. Link removed
Donate for Dev:
MOD EDIT Link removed.
Special thanks and credit goes to:
@topjohnwu for Magisk
@amarullz for Aroma installed
@yarpiin for Kernel
@Grouxho for GrxSettings
@KHongloi for idea patch SecureFolder
and members come from @xda forum for some other guide
Contributors: Trần Phong
IF YOU LIKE AND RECPECT MY WORK, PLEASE DONATE
MOD EDIT. Link removed
JOIN MY GROUP AND SUPPORT
MOD EDIT. Link removed
========================================
INSTRUCTIONS:
1. To avoid bootlop/stuck logo you must be update bootloader to Q bootloader.
Download bootloader here: page 1
MOD EDIT. Link removed
2. Since Android Q s9 have system_root you must be install lastest TWRP with support system_root version.
Download TWRP here: LINK TWRP page 1
MOD EDIT. Link removed
3. If you instal lastest rom, u NEED updated bootloader because we NOT included in rom.
GUIDE INSTALL:
1. Reboot to recovery mode(press volume up+bixby+power)
2. make nandroid backup
3. wipe system
4. wipe data
5. wipe cache&dalvik
6. Format data/YES before flashing ROM ONLY FC theme services or bug gone
7. flash rom.zip
8. reboot system wait 3 minutes
I think this is kinda scam or something. All they do is asking about donations. And maybe the telegram kinks should be deleted. I joined the group and tried to communicate with them and all I got is flame, bad behavior and yet, asked to donate. I think the mods should delete the links to telegram and investigate if there is really a rom or just scam project from poor people trying to get some money from people on XDA.
Doing it this way, I think really kills the spirit of the XDA. Also, I notice when somebody don't speak their language, they don't give any support or information. Very disrespectful behavior. Seems like also the guy who build some los rom managing the project. I think people should stay always from this rom, there may be some spyware or adware inside. Sharing also a lot of warez on their channel, which is tottaly against the rules of XDA.
And one more...They think if you don't speak their language can insult you. Very disrespectful and ugly behavior.
However, if I somehow braking the rules by writing those post, I will take the consequence. But I think I had to throw some light on this case.
that's guys from LOS 120hz? Just reported.
Ganjax said:
that's guys from LOS 120hz? Just reported.
Click to expand...
Click to collapse
Yes he is. Those people should stay always from XDA. The mods did the right thing to lock his threat. Everyone knows there are hardware limitations and no one rom can provide such function.
Nevermind, the familiar developer Alexis port his rom to our device. He is trustworthy and I think is safe to try his rom. Everyone who want to try some s20 goodies.
Leon said:
Yes he is. Those people should stay always from XDA. The mods did the right thing to lock his threat. Everyone knows there are hardware limitations and no one rom can provide such function.
Nevermind, the familiar developer Alexis port his rom to our device. He is trustworthy and I think is safe to try his rom. Everyone who want to try some s20 goodies.
Click to expand...
Click to collapse
I know Alexis rom from S8. Really trusted developer.
Thread closed!