AOSP 13
This is a moto-common project release under the codename borneo
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
What's Moto-Common?
Moto-Common is a set of trees common to every 4.14+ QCOM Motorola device, making it easier to do bringups based on SODP.
What's AOSP?
AOSP is Android as Google publish without other modifications.
Known issues:
You tell me
IF YOU DONT HAVE SLOT B FILLED YOU CAN BRICK
Instructions :
Download the latest build
Reboot to bootloader
Code:
fastboot -w
Code:
fastboot update PACKAGE.zip
You may need to install drivers in device manager after running the last command
Downloads :
Download
Telegram Groups
My chat
Source Code:
https://github.com/moto-common
Changelog:
Jan 25th 2023: Initial release on XDA
Feb 27th 2023: Pushed Feb update
June 19th 2023: Pushed June patch update
Fix fingerprint gestures for egis
Fix color mode listings
Fix aux cameras
Improve memory management
Improve Wi-Fi 5GHz strength
Numerous other changes
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
I have no idea , I just build to provide a base for others to work off of mostly.
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Does this rom bring unlimited google photos???
sdembiske said:
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Click to expand...
Click to collapse
Would an outdated twrp version work? There is an unofficial one for Android 11
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Renate said:
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Click to expand...
Click to collapse
Yeah thats known, sadly CID partition is signed and the flag is usually burned qfuse in the SoC which is burnt on all retail devices.
Electimon said:
... the flag is usually burned qfuse ...
Click to expand...
Click to collapse
I'm using the Firehose loader size=609,484, MD5=153a904c54963cb21b901b0dd10f0641
I can see that the CID is validated by cert chains.
But I also see lots of stuff like "ssm_flash_cid", "write_cid_store".
I see a bunch of smc (Secure Monitor Calls) and a bunch of SCM (Secure Channel Monitor) calls and functions for reading/writing fuses.
I also see one small function that writes a byte into memory that can disable restrictions.
It seems like a back door, but I haven't seen what activates it.
Would it be possible to use this device tree to make a pixel experience port?
LethalGamer2121 said:
Would it be possible to use this device tree to make a pixel experience port?
Click to expand...
Click to collapse
Yes
Feb 27th 2023: Pushed Feb update
Electimon said:
Feb 27th 2023: Pushed Feb update
Click to expand...
Click to collapse
sound isnt working after update. it started working after i downgraded to the jan release
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Thank you for letting me know, it will be fixed soon
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Please redownload the same link, ive updated it with the fixed package. Thank you
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
merith-tk said:
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
Click to expand...
Click to collapse
Use platform-tools r32, in the latest version google broke fastboot update.
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Small problem, phone has fastbootd, bootloader, recovery, and system (system being rom)
when you tell the phone to boot to fastboot, it goes to fastbootd which does not show up in fastboot.exe's list,
but if I send it to bootloader, it shows up
Edit, Updating drivers fixed it, IOBit Driver notified of out of date driver
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
merith-tk said:
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
Click to expand...
Click to collapse
Wipe data in recovery and let me know if its still an issue
Related
I've built a TWRP recovery for the 2015 Moto E 3G. This model is also known as Styx 3G, and has the codename otus.
3G model only! If you have the LTE model, use my LTE recovery instead.
Downloads are available on the downloads tab. In case you encounter any issues, I've also posted the stock recovery for otus on the downloads tab.
To try it out without flashing, run:
Code:
fastboot boot twrp.img
To flash it:
Code:
fastboot flash recovery twrp.img
Try at your own risk. I expect everything to work, but I make no guarantees.
I would like to thank cybojenix for creating the first-gen Moto E recovery. I used his device tree as a reference when creating mine.
Device Tree: https://github.com/sultanqasim/android_device_motorola_otus/tree/twrp
Kernel: https://github.com/sultanqasim/android_kernel_motorola_otus/tree/twrp
XDA:DevDB Information
TWRP for Moto E 3G (2015), Tool/Utility for the Moto E 2015
Contributors
squid2, cybojenix
Source Code: https://github.com/sultanqasim/android_device_motorola_otus
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-16
Created 2015-04-17
Last Updated 2018-08-16
Reserved
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
squid2 said:
My initial test release is up. Try it at your own risk, I don't know what works and what doesn't. All I know is that it can boot and see the on board storage. Thanks to @Ravx and @Hakkinukai for initial testing. If you want to stay safe, don't flash anything with it until I'm able to confirm that it works properly. I'm still waiting on my test unit to arrive.
For the adventurous, try it out and let me know what works and what doesn't. Be careful though, it's untested and could mess up your device. I'm not responsible for any problems it may cause you.
Click to expand...
Click to collapse
Further test results:
1.) Was able to succesfully backup my system with the recovery.
2.) wiping data gave error ( error code 255 i think ) but the data was still gone and the device got factory reset.
3.) Succesfully restored the data from the created backup.
will try to flash SuperSu now.:good::good:
Edit: The device is Successfuly rooted.
Here is the Screenshot of Successful Root.:good::good::good::good:
Bro i have created a saperate Guide for rooting. I hope you dont mind.
Glad to hear that it is mostly working. I'll look into the data wiping error when I get my test device.
Thank you very much squid
i try this command 'fastboot boot twrp-otus-2.8.6-test3.img'
and in first attempt , i got TEAMWIN screen on successful boot MOTO E 2nd Generation.
and from install option ,i install SuperSU from my internal memory.
and my device rooted successfully.
you are :angel:
:victory:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Thank you very much, I could finally rooting my moto E,
#Off topic could please make a version updated for the moto E first generation, the current version is 2.7.1.0 and the latest versions have many bugs,
squid2 said:
I've posted a new version (2.8.6-test4). This new version solves a problem that prevented my recovery from booting from flash storage. It's also smaller. Thanks to @Hakkinukai for testing.
You can safely flash this recovery to your device by doing
Code:
fastboot flash recovery twrp-otus-2.8.6-test4.img
I make no promises about reliability, but I'd expect most things to work. Use this at your own risk, I'm not responsible for bricking your device. I haven't tested this myself.
To avoid confusion, I've removed the old version (2.8.6-test3) from the downloads tab.
Click to expand...
Click to collapse
Thanks bro. I will flash and report back :good::good:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
great work man
Ravx said:
Is flashing the new recovery working for you guys. If yes I will update the rooting thread so that the method becomes more easy.
Click to expand...
Click to collapse
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
raghavarora1997 said:
The new recovery is working just fine for me, but i cant boot into recovery mode manually, i have to use a third party app either quick boot or apm+.
other than that everything works good.
Click to expand...
Click to collapse
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
squid2 said:
By booting manually, I presume you mean selecting it from the bootloader menu with the volume keys. What happens when you try that? I've had others report that it works.
Click to expand...
Click to collapse
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
raghavarora1997 said:
After selecting recovery from the bootloader black screen comes and nothing happens. I've tried it many times with no success.
Sent from my MotoE2 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
squid2 said:
Hmm, so it goes black right away and doesn't show the boot logo or unlocked boot loader warning. Strange.
Are you sure that you flashed it correctly? Is anyone else having this issue?
Click to expand...
Click to collapse
Yeah I'm sure I've flashed it correctly.
And yes it goes back right away. Still I will flash or again, just to be sure and then report back.
UPDATE: After flashing again I can boot into recovery manually.
Sent from my MotoE2 using XDA Free mobile app
The utterly incompetent Canada Post decided to lose my Moto E 3G. Their customer service was very unhelpful and just told me to contact the sender, and ask them to start a trace with the USPS. Traces take 3 weeks and often get nowhere. This is the fifth package to me that Canada Post has lost in the past two years. On average, I've found that 1 in 5 packages sent to me via Canada Post get lost. That is quite ridiculous, but they are a taxpayer funded government monopoly with no sense of customer service.
In addition to contacting the sender, as a last resort, I've taped a notice inside my mailbox to ask the mailman/woman if they know what they did to my parcel. God knows if I'll ever get it.
Anyway, enough of a rant for now. I'm furious that they lost a package that I spent $200 on (with taxes, shipping, markup etc.)
Due to you, this tut was possible @ http://androidmtk.com/root-motorola-moto-e-3g-2015
Good news! My Moto E was delivered to the wrong address by Canada Post, but the people who received it brought it to me yesterday. I've started looking into porting CM12.1 to otus, though it will probably be a week or so before I have something to show.
I Find some bugs:
1) The USB-OTG don't work (don't mounts)
2) adb sideload don't work (don't finds device)
3) strong button vibration (the default is 80, but 20 is ideal)
Hey guys, Kyuubi10 here again.
Recently I had an issue with my nexus 9, which is becoming increasingly common.
Where one can permanently soft-brick their nexus, for lack of ticking the "Enable OEM unlock" button, then bootlooping their device while locking their bootloader, thus making it impossible to reflash a system image through fastboot.
If you're lucky enough to still be able to access your custom recovery your device is still salvageable, but if as me you were performing a factory reimage when you locked your bootloader chances are that you have gone back to stock recovery, and only after realised that your OS was bootlooping.
From reading about it, I found out that it was virtually unrecoverable, unless you managed to keep your custom recovery, by either flashing a new system or if your recovery refuses to flash new system you can use this: http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539.
But in all of these cases you still need a custom recovery.
At the end most people gave up and either bought another device or used their warranty to replace their device (Which I am trying to attempt, if my warranty isn't completely voided.)
So, finally reaching the important point of this thread, I have had a couple ideas which could work to solve this issue but since I don't have enough knowledge I am unable to actually test the idea.
For the device to recognize the lock status of the device even without an OS present means that there must be a flag the bootloader reads. By reading further I found this. http://newandroidbook.com/Articles/Nexus9.html
This basecally explains that Nexus 9 has a partition called PST (Persist) whose only job is to provide the value of this flag. I was wondering whether it is possible by using Linux could get a more direct access to the partition and change its binary value to enable the "enable OEM unlock" variable (Described by fastboot as "Ability is 0").
I had this idea because one day when I bootlooped another device and ADB on windows failed to recognize the device I booted linux and used ADB from there. And the phone was reconized.
This works because Linux can view partitions with different filesystems, where as windowns can only see partitions which have been formatted into "Windows" partitions (e.g. FAT32, NTFS).
So in theory using a Linux OS to access the different partitions in Android should show up much more information, and give you better access. But apart from this I don't know much more. I will be testing this theory out in more detail. But I am challenging the more experienced contributors out there to help out in overcoming this issue!
Please, this is a real issue which is limiting newer nexus devices. If anyone has any new ideas please share by commenting, and lets help each other out to find a solution to this problem.
..
cam30era said:
@Kyuubi10
Have you seen this thread > http://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
Click to expand...
Click to collapse
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Kyuubi10 said:
Yes, in fact I have the same exact link in the OP.
But unfortunately as I have described my case is quite unique in which I don't have a custom recovery. This in turn means I have no access to ADB because no partitions are mounted.... I'm stuck with using fastboot for now.
Click to expand...
Click to collapse
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
defmetal96 said:
@Halleyscomet is very right, the N preview saved me from this problem, allowing me to enable OEM unlock and then go back to stock marshmallow.
Click to expand...
Click to collapse
Thank you guys for your reply!!
Unfortunately as described in my signature my N9 was stolen.
But I'll change the title of this thread to [SOLVED] so that others know where to find an answer.
Halleyscomet said:
The March 25, 2016 Android N Beta should be able to save you: https://developer.android.com/preview/download-ota.html
It can be pushed via adb to a stock Nexus 9 even with a locked bootloader.
Click to expand...
Click to collapse
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
For that a Moderator needs to be made aware ) Let's try do that!
angerized said:
Seriously, you are a lifesaver.
The simple fact that you can sideoad the preview and that it flashes system unconditionally saved my Nexus 9.
This infomation should be stickied because it is the only solution if you are stuck in between versions. I was on LMY48T and adb sideload of the correspondig OTA showed "unexpected content" (Error 7).
This allowed me to boot, and unlock OEM & bootloader.
Huge thanks!
Click to expand...
Click to collapse
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
joeish said:
Any chance you still have this file? Doesn't seem to exist on the internet anymore.Having same issue.
Click to expand...
Click to collapse
Hello,
I don't have this specific file anymore, but I think you can sideload the latest OTA from here:
Images OTA complètes pour les appareils Nexus et Pixel | Google Play services | Google for Developers
developers.google.com
The Nexus 6P goes to version (MTC19T)
According to Google, "The most severe of these issues is a Critical security vulnerability that could enable remote code execution on an affected device through multiple methods such as email, web browsing, and MMS when processing media files."
In total, 25 security vulnerabilities have been addressed, ranging from critical to low in terms of their assessed severity. 24 of these fixes affect Nexus or Android One branded devices. Google also stresses that there have been zero reports of any devices actively exploited by these fixes, and that their platform-level security protections and service protections like SafetyNet make the risk of actually being affected low. A quick summary:
Exploitation for many issues on Android is made more difficult by enhancements in newer versions of the Android platform. We encourage all users to update to the latest version of Android where possible.
The Android Security team actively monitors for abuse with Verify Apps and SafetyNet, which are designed to warn users about Potentially Harmful Applications. Verify Apps is enabled by default on devices with Google Mobile Services, and is especially important for users who install applications from outside of Google Play. Device rooting tools are prohibited within Google Play, but Verify Apps warns users when they attempt to install a detected rooting application—no matter where it comes from. Additionally, Verify Apps attempts to identify and block installation of known malicious applications that exploit a privilege escalation vulnerability. If such an application has already been installed, Verify Apps will notify the user and attempt to remove the detected application.
As appropriate, Google Hangouts and Messenger applications do not automatically pass media to processes such as mediaserver.
SOURCE: http://www.androidcentral.com/android-security-bulletin-may-2016-live-here-what-you-need-know
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
start downloading 8 minutes to go (oh man i have to install xposed again and i hate when catch need to optimize on boot )
I got an error message after I installed and booted it up for the first time. It said there was an internal error and to contact the manufacturer. After I clicked OK, it proceeded to start up fine but I restored my backup.
I may have missed a step flashing it (was multitasking while installing , so will try again later.
Sent from my Nexus 6P using Tapatalk
i hereby command the OTA zip to be made available for my flashing convenience. Where is it already?.
Damn I just updated my 6p to April like yesterday
C5Longhorn said:
I got an error message after I installed and booted it up for the first time. It said there was an internal error and to contact the manufacturer. After I clicked OK, it proceeded to start up fine but I restored my backup.
I may have missed a step flashing it (was multitasking while installing , so will try again later.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Stock, rooted here. I just flashed everything but userdata, worked fine. Always check your hashes.
Any other changes over then security updates?
My experience so far:
Updated manually
Reboot back to Android
Applied TWRP and Franco r16
Reboot back to Android
No issues so far, profit.....
Yea bootloader and radio version please I doubt it has changed
C5Longhorn said:
I got an error message after I installed and booted it up for the first time. It said there was an internal error and to contact the manufacturer. After I clicked OK, it proceeded to start up fine but I restored my backup.
I may have missed a step flashing it (was multitasking while installing , so will try again later.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I'm still receiving the error. I wonder if it doesn't like SuperSu version 2.68. The bootloader is version 03.51 and the radio is 03.61.
Sent from my Nexus 6P using Tapatalk
---------- Post added at 03:39 PM ---------- Previous post was at 03:01 PM ----------
I ended up having to reflash the vendor.img file again. The error went away.
Rick
coldconfession13 said:
Yea bootloader and radio version please I doubt it has changed
Click to expand...
Click to collapse
No Bootloader or Baseband changes, its the same
Was checking for factory images all day, then flashed Dirty Unicorns as a secondary in MultiBoot...while waiting for ProjectFi to activate - BAM - images available to download.
Just manually flash vendor, cache, boot, system
Booted to recovery
Installed Super SU 2.68, franco r16 (i do not want to encrypt so this will do for now), and then xposed, now Android is upgrading
OTA link?
I flashed the factory image off Google's web site. Well everything but the Bootloader, Radio, user data, recovery and all is well.
C5Longhorn said:
I got an error message after I installed and booted it up for the first time. It said there was an internal error and to contact the manufacturer. After I clicked OK, it proceeded to start up fine but I restored my backup.
I may have missed a step flashing it (was multitasking while installing , so will try again later.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
It sounds like you did not flash the vendor img. You can flash either by TWRP or fastboot "fastboot flash vendor vendor.img"
I do not see a vendor image in the zip file. Only Bootloader, Radio and image-angler-mtc19t is there.
hacksome said:
I do not see a vendor image in the zip file. Only Bootloader, Radio and image-angler-mtc19t is there.
Click to expand...
Click to collapse
You can unzip the image-angler-mtc19t that contains all of the partition img files that you can manually flash.
We are up to 2.71 for Supersu now. What is everyone stuck on 2.68?
floepie said:
We are up to 2.71 for Supersu now. What is everyone stuck on 2.68?
Click to expand...
Click to collapse
I'm using 2.65 still, the one with the 'Stable' and not 'Beta' tag
hacksome said:
i hereby command the OTA zip to be made available for my flashing convenience. Where is it already?.
Click to expand...
Click to collapse
www.whereisitalready.com
Edit: 2022 I have tested it it fully works as of this year!!!. disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk.
to flash it simply open up settings enable developer options and enable OEM on lock on your sm-t380, then use odin or Heimdall on a computer to flash the tar or raw boot.img to your device in download mode.
The features include selinux permissive and knox disabled and in theory rooting protection disabled
Updated Tue Jan 29 09:29:26 EST 2019 Defex disabled for full Root
If this kernel breaks Bluetooth Flash the Fix-Bluetooth.zip with twrp
I have a solution if you want selinux full disabled. https://github.com/AdrianDC/kernel_.../master/release/kernel_permissive_patcher.zip
However you can change it with the command line only flash that zip if you want it fully disabled forever.
Kernel Source can be found at
Samsung Open Source
opensource.samsung.com
Put SM-T380 in the box and find the XAR PP (PIE source)
I simply disabled defex and Selinux in the Kconfigs and Defconfigs
Rooting sm-t380 think you can help me get the flash you used OEM to be unlocked
Austcool said:
I have created a custom kernel for the sm-t380. I have not tested it myself do to the 7 day OEM unlock is locked for 7 days but I though I would share it for you guys on the xda here to test. disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk.
to flash it simply open up settings enable developer options and enable OEM on lock on your sm-t380, then use odin or Heimdall on a computer to flash the tar or raw boot.img to your device in download mode.
The features include selinux permissive and knox disabled and in theory rooting protection disabled could you please tell me what you used to or how to get the 7-day OEM unlock I have a Samsung tab A sm-t380 2017 build# NMF26X T380DXU1ARB3
Click to expand...
Click to collapse
Tyrone M said:
Austcool said:
I have created a custom kernel for the sm-t380. I have not tested it myself do to the 7 day OEM unlock is locked for 7 days but I though I would share it for you guys on the xda here to test. disclaimer, I am in no way responsible for this kernel screwing up you tablet so use at your own risk.
to flash it simply open up settings enable developer options and enable OEM on lock on your sm-t380, then use odin or Heimdall on a computer to flash the tar or raw boot.img to your device in download mode.
The features include selinux permissive and knox disabled and in theory rooting protection disabled could you please tell me what you used to or how to get the 7-day OEM unlock I have a Samsung tab A sm-t380 2017 build# NMF26X T380DXU1ARB3
Click to expand...
Click to collapse
oem unlock is hidden by default wait 7 days and go to about and tap the build number 7 times, then go to developer options to unlock it
Click to expand...
Click to collapse
Not even the op reported his own conclusion...Sounds like he simply wanted some guinea pigs. Too bad, I was interested.
Force oem unlock
https://forum.xda-developers.com/galaxy-tab-a/how-to/tab-2017-force-oem-unlock-t3874487
I'm interested in taking one for the team... Gonna download now and post my results after I flash it.... In a couple hours, of course.....
I have a new kernel for oreo
Has anyone actually tried this? If so, did you win?
Hello, what slot in odin do you place the .tar file in?
The Files have been fixed and updated let me know if you have issues with any of them I'm sorry guys for not fixing them sooner I've been busy with real life stuff
I added my custom Eleven installer but remember the disclamer I'm in no way responcable for flashing things that mess up your device void your OEM warranty or make your device unsuable!
Austcool said:
The Files have been fixed and updated let me know if you have issues with any of them I'm sorry guys for not fixing them sooner I've been busy with real life stuff
Click to expand...
Click to collapse
What slot in odin do I flash the new.PIE.tar?
allanseth23 said:
What slot in odin do I flash the new.PIE.tar?
Click to expand...
Click to collapse
AP slot is the regular place to flash files like system and boot
Austcool said:
AP slot is the regular place to flash files like system and boot
Click to expand...
Click to collapse
IT WORKED(rooted)!!! Thanks!
We also have this but we have not been able to make the recovery work right to properly flash it..... https://drive.google.com/file/d/1jhG0pvfNB7LLl2iuoD-xl-F4nvpUwKMv/view?usp=sharing
Austcool said:
We also have this but we have not been able to make the recovery work right to properly flash it..... https://drive.google.com/file/d/1jhG0pvfNB7LLl2iuoD-xl-F4nvpUwKMv/view?usp=sharing
Click to expand...
Click to collapse
Link seems to be broken…. Mind reposting? Thanks!
christophershaw said:
Link seems to be broken…. Mind reposting? Thanks!
Click to expand...
Click to collapse
Sure we are working on porting LineageOS to the SM-T380 we have working building trees atm... Flashing the rom is another story....
I believe this one works you can flash it from TWRP then reboot to LineageOS Recovery; be aware we are in the alpha stages things may not work as expected atm; if your device gets stuck in a black screen wait for the battery to drain then plug it into a computer while holding volume down to get to download mode I don't take credit for the porting this was all possible do to @andr01dfr3ak on XDA and on discord he's known as The Freaking iDroid. iDroid and me have been working with Galaxy Tab A 8.0 LineageOS porting awhile now.
https://drive.google.com/file/d/1jhG0pvfNB7LLl2iuoD-xl-F4nvpUwKMv/view?usp=sharing a ROM in the alpha stages as well we are working hard in my discord server to correct the flashing issues with the improper mounting at
Code:
/system/system
remember I don't take any such responsibility for your devices taking a crap on you for flashing any of my mods
The same file just uploaded to XDA instead of Google Drive.
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb