Related
Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03
Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545
Future FAQ if necessary (let's hope not).
Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.
gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.
build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?
Flounder still isn't listed just lunch it anyway
Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse
belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.
gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.
AOSP MASTER BRANCH FOR MANTA DEVICE
Hello everyone, you can download on XDA many good ROMS but each of them are based on "stable" android releases. That's why I chose to share something else.
I am offering a master branch build
Why use master branch ?
clang 3.8 | daily updates | java 1.8
instructions :
reboot to twrp recovery ( you can use mine if you want to use f2fs or having issues flashing my packages)
flasy my package
reset factory and IF YOU COME FROM ANOTHER DISTRIBUTION delete /sdcard/Android/data folder
flash gapps package ( I recommend opengapps)
reboot
I recommend people to factory reset time o time because of the master branch, it can be required to remove some bugs
What is not working/bugging for now
ROOT: latest supersu are patching the boot image and this doesn't work currently with my master branch releases. You need to use SuperSU v2.56
MXPlayer: for some reasons mxplayer doesn't find libcutils.so while it does exists. So for now, you gotta to use some alternatives: vlc, or what ever
Download link
Sources
How to use AdwAway
In oder to get AdAway working you need to do the following:
1/ Set a file at
Code:
su/su.d
with the following content
Code:
mount -o bind /su/etc/hosts /system/etc/hosts;
2/ Make an empty host file at
Code:
/su/etc/hosts
I think you can find a working flashable package doing this on the unoffical adaway thred
XDA:DevDB Information
AOSP Master Branch for Manta, ROM for the Google Nexus 10
Contributors
Khaon
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Beta
Stable Release Date: 2016-04-22
Created 2016-01-27
Last Updated 2016-04-21
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
PainToad said:
Can I confirm this is 100% AOSP, untouched?
Are you doing automated nightly builds?
Thanks!
Click to expand...
Click to collapse
This is not 100% PURE aosp.
The base is aosp master branch. I have included some several extra such :
bootanimation
long press recent switches to latest app
led
...
Well nothing much.
The only critical thing I have touched is android permission : I override user's permission for google play service for the location permission access: otherwise it crashes.
I have uploaded a new build.
Too much changes to display here the changelog.
If you want extra tracking you should head here
To me, the main change, is clang prebult updated!
OP updated, root is now working.
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
ace9988 said:
I'm not being thick here (sure of that) but despite flashing SU 2.56 , I can't get root permissions at all. Am I missing something?
Click to expand...
Click to collapse
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Khaon said:
Hello,
hm this is kinda unexpected, I got supersu permission with this build.
Did you install anything else ?
Click to expand...
Click to collapse
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
HmHm it is kinda late for me ( european timezone) but I have no issues using app requesting SU rights. I will take a look however at it tmr.
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
what opengapps version did you isntall ?
I am using pico, and I have no issue flashing it.
ace9988 said:
Nope. I tried flashing superSU on the ROM + open gapps .....the ROM on it's own without the gapps too. Flashed the 2.56 beta build from the link you provided and although supersu appears in the app drawer, the "Enable Superuser" option appears to be greyed out and none of the apps even request root permission.
Click to expand...
Click to collapse
How is your supersu status ?
I have no issue with su.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
I was reported an issue when formating to f2fs rebooting to the rom would format the userdata partition.
I investigated the AOSP code source and some commit format the partition if it fails mounting. Ofc trying to mount a f2fs partition with ext4 is considered as a fail...
Flashing my standalone kernel permit to pass that issue : my stand alone kernel will transform ext4 entries to f2fs(and vice versa) depending on the actual underlying fs.
The current release I am using features fixes for this, however, something broke the libsensors, so I need to find out what.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
Ewww, it should work ! Any other informations ? such logs ?
-----------------------------------------------------------------------------------------------------------------------------------------------------------
I am uploading a new build, I had issues for days with the builds.
Please tell me if you got bootloop on reboot. From what I saw bootloops do not longer exist.
I uploaded a new build.
It features master branch 02/21 with my latest kernel.
You just need latest opengapps for marshamallow and supersu 2.56.
Have fun.
All I see is one dated 2/5?
Sent from my Nexus 10 using XDA Free mobile app
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Der_Graf said:
"Play Service stopped" after installing Gapps (Install without errors)
I try OpenGapps Pico and Nano.
Click to expand...
Click to collapse
Grant play service the location permission and it will be fixed.
Katamave18 said:
Cant install openGapps. It says Error code 25.Your ROM has no buid.prop or default.prop it says
Click to expand...
Click to collapse
I had this issue sometimes when installing the Rom and gapps in the same queue.. Installing the gapps seperatly afterwards worked then.. Try this out
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Der_Graf said:
Can´t give permissions because of looped warnings.
ROM only works fine.
I think i will wait for Khaons Kernel with DT2W Patch and use CM13.
Click to expand...
Click to collapse
@Der_Graf
Hehe sorry for you this issue happens, the real culprit is Google. Since MM, the dev got to ask permission if not given. Google Play Frameworks/Service doesn't ask for this. So that's why you got FC. You should try after a Factory Rest- you need to that anyway when coming from another ROM- not installing Gapps in order to not have the first setup screen where you will get stuck because of the fc's spam.
Then Install gapps, and, since you will boot on the Home Screen, you should be able, with some pain, to get access to the app menu to get Location permission for Google Play Services.
Then, for any upgrade install, you won't have issues as the permission is already granted.
I know this sucks, but I tried to force give the permisison and it doesnt work :angry:
Ewwwww.
I wanted to share my latest build, as of the 25th feb, but NFC is broken and makes continuous FC'S, this appears also on my friend nexus 6's device, which is still supported by Google. So this is the bad news I've got to understand why this happens, well until Google fixes it or I find the culprit.
However, the good news is, that this friend, maintains more extra features then I do, so the next releases will feature more extra features
A custom Kernel for LineageOS 7.1.1 based on the ideas and experiences of SunKernel corona (StockKernel) for Xperia Z5 series
XDA:DevDB Information
SunKernel Pedigree Z5 for LineageOS, Kernel for the Sony Xperia Z5
Contributors
zacharias.maladroit
Kernel Special Features: FauxSound, KCAL, reworked thermal engine, fast camera, etc.
Version Information
Status: Beta
Current Beta Version: 1.3
Beta Release Date: 2017-03-14
Created 2017-03-14
Last Updated 2017-08-30
Reserved
Changelogs:
14.1_I
initial release - Features:
Click to expand...
Click to collapse
14.1_I.2
changes ...
Click to expand...
Click to collapse
14.1_I.3
add throttling for orientation sensor input events (most likely NOT needed) to cut idle cpu high load of 15-20%
Click to expand...
Click to collapse
14.1_I.4
removed lots of sources for log-spam (dmesg/kernel-log)
BCL<-->KTM interface for BCL (battery_current_limit) driver is now used, faster, more reliable (less overlapping) and better hotplug during thermal events, etc.
more reliable bcl mitigation due to fresh SoC value, allowing frequency-based mitigation even with BCL set to off
MUCH improved sound output
more reliable sound playback
Click to expand...
Click to collapse
Reserved
Kernel Releases (Betas for now):
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
From now on
both LineageOS and Resurrection Remix are unified builds that work on Single SIM and Dual SIM devices - no separate kernel or ROM needed !
Resurrection Remix: already IS the unified build (thread is currently parked at the General Subforum: Resurrection Remix 5.8.2 for Xperia Z5 (unified build) )
LineageOS: please download the unified LineageOS builds from olivier: lineageOS ROM (as mentioned at: LineageOS thread )
those are NOT boot-tested but should work (need testing + feedback)
Reserved (3)
Notes:
The preamp of FauxSound or the actual sound/soc driver state seems to be a bit "mushy",
thus the white noise (swoosh-ing, hiss-ing) is a bit high - reduce headphone amp by 10 or 15 (-10 or -15) so that you get a clear and well-defined output,
it really depends on your headphones - with in-ear it is most likely more noticable.
This was with unmodified "stock"/"upstream" lineageOS kernel source and with a bit patched up - so nothing I can and will change
Kernel source:
https://github.com/zachariasmaladro...kami_r2/commits/Sun-Kernel_Pedigree_cm-14.1_I
Thanks, I hope you don't forget dsds variant.
It is a pleasure to have SunKernel in LineageOS.
Thanks @zacharias.maladroit
I will try after released stable LineageOS for dsds and SunKernel.
Flashing lineage and kernel, looking forward to try it
Thanks for upload
s.hossein said:
Thanks, I hope you don't forget dsds variant.
Click to expand...
Click to collapse
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Thx! But After flashing this Kernel i couldnt Boot up. Stuck ar Boot Animation. But the Animation did not stopped.
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
zacharias.maladroit said:
you have an up-to-date boot.img for dsds device ?
if yes, please upload
Click to expand...
Click to collapse
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
stipi69 said:
Same here, bootloop, can u look up to this?
We are so glad you put efforts in custom kernel for lineage, looking forward for an update
Click to expand...
Click to collapse
please update to the lineageOS builds from Olivier,
unless he has uncommitted changes locally in his repos - there are no changes,
my lineageOS build is at patchlevel March 5th 2017,
so with recent changes the kernel (more precisely the ramdisk) might be incompatible with the old builds from @Myself5
balrajs99 said:
I think the tree sources are unified so is there a need for special kernel for dsds? I'll try this one on my E6683.
Click to expand...
Click to collapse
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
In this minute i downloaded fresh update, flashed in this order:
1. lineage-14.1-20170316-UNOFFICIAL-sumire
2. open_gapps-arm64-7.1-nano-20161104
3. UPDATE-SuperSU-v2.78-20160905010000
4. Z5_SK_Enf_v14.1_I.3_sum
lineage from olivier from below link:
https://dl.olivierk.at/sumire/lineage-14.1/
lineage-14.1-20170316-UNOFFICIAL-sumire
i still get bootloop, scren is dimed, lineage animation keeps going for couple of secs, screen goes bright and bootloop from there on, waiting 10+ minutes now... maybe old superuser zipfile for this task? dont know realy, will make clean install
zacharias.maladroit said:
it might work, but you most likely run into a bootloop, too, if you're not using latest lineageOS builds (those from Olivier)
Click to expand...
Click to collapse
Yes, on latest build by oliver it ran into bootloop.
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
@zacharias.maladroit: Thank you a lot for your work. We should be very thankful to every developer on the Z5!
Just gave your Kernel a try on latest olivier's lineageos (0316). Got a bootloop. After 20 minutes, I did a power reset and dirty reflashed latest olivier's lineageos (0316) via TWRP. Telephone was functional again.
L33Tgod said:
actually this goes into bootloop, flashed latest olivier's lineageos.
edit : is there any proper order of flashing ? and can you share lineageos build that you are on ?
Click to expand...
Click to collapse
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Link to custom LineageOS 14.1 build (patchlevel March 5th 2017)
not sure what differs between this and the other builds:
https://drive.google.com/open?id=0BykGGWB96CBQR1VIb3QtdGpsTmM
I initiated the fetch of the repo files via
lunch lineage_sumire-userdebug
and added the blobs repo,
then restarted the build ...
Click to expand...
Click to collapse
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks
zacharias.maladroit said:
yes, currently uploading
I'd install LineageOS + gapps (opengapps),
go through all steps,
then go into TWRP, make a backup and attempt to flash the kernel.
I haven't flashed the ROM via zip,
I flashed it via the .img files and fastboot since the updater-script seemed to cause trouble ...
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)
Thanks[/QUOTE]
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
L33Tgod said:
I flashed the rom by flashing pixn kernel then booting into twrp when purple led comes on and it flashes rom normaly and to access twrp later i have to use your stock kernel and type fastboot boot boot.img and it can go into recovery, but can't flash lineageos because of that error 7.
Click to expand...
Click to collapse
yeah, that's why I wrote:
Can you guys post the content of the updater-script (in
Code:
tags), that works for you ?
I removed the assert line but it still didn't work for me,
also booting the stock ROM kernel via fastboot doesn't seem enough anymore,
it has to be flashed, then the VOL DOWN button pressed to reach TWRP on the recovery partition.
If you reach TWRP via a different method please let me know :)[/QUOTE]
might be that upstream changed the content of updater-script,
that's why I ask for a working variant ;)
Click to expand...
Click to collapse
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
What's new in 3.2.2-0:
</> CHANGELOG : ? </>
Code:
Code:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
</> DOWNLOAD ? </>
https://twrp.me
$ TIP $
You can update it from previous TWRP recovery if you already have it installed, else install it as fresh by using adb or Official TWRP Installer app from google play store or similar
To flash with Fastboot/Adb:
Code:
Code:
make sure OEM-Unlocking is ON
$ adb reboot bootloader
$ fastboot flash recovery twrp-3.2.2-0-woods.img
To contribute:
TWRP Code Review
TeamWin
XDAevDB Information
Moto E4 ROMs, Kernels, Recoveries, & Other Development
Contributors
iykeDROID™ {dumbDevpr*}
Source Code: https://github.com/TeamWin
Version Information
Status: Stable
Created: 2018-07-12
Last Updated: 2018-07-13
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
ka4o_pi4a said:
Great news. Now I'm waiting for stable and fully working Oreo ROM and start flashing.
Click to expand...
Click to collapse
from the looks of things on my side, i don't think that will happen in anytime too soon.
let's just hope for a God sent dev to take over the Moto E4(woods) development .
if any bug with the TWRP, create/open an issue regarding such bug on GitHub :
https://github.com/omnirom/android_bootable_recovery
( make sure to see how other issues were created and follow such trend )
thanks
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
EstebanxZ said:
I am getting a wrong architecture error (error 64 in twrp) when trying to flash ARM gapps.
Click to expand...
Click to collapse
wait for next update or use this at your own risk
https://t.me/motoe4woods/12179
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
ka4o_pi4a said:
Same here. Wrong architecture. Even the backup was corrupted and I wasn't able to flash back my stock ROM. This is my last Motorola device.
Click to expand...
Click to collapse
i used it to install Both XOSP & Gapps Pico today.
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
ka4o_pi4a said:
Few days ago I was spent my day on trying to flash some ROM, but didn't manage to flash any (Pico,nano, micro, etc) gapps... All finished with the same error 64. Then I install last beta of twrp and successfuly install gapps, but can't boot into system (boot into recovery every time).
Click to expand...
Click to collapse
please your issues on that specific ROM's thread.
As far as i know, the TWRP recovery works fine even before the unofficial beta... woods has come to it's best so far.
thanks.
Already do that. Also try with two or three different ROMs and get the same error. Doesn't matter, I'LL wait for some more stable version of twrp and some ROM.
Tks
Thanks man!
Laruzzo said:
Hi, this TWRP version to Moto E4 woods is not good.
It does not install GAPPS, and do not install SUPER SU.
With GAPPS the error is about 64 bits version. And with supersu it says that "Bad recovery no Unzip."
I tried with a unnoficial version and worked everything.
Please update in TWRP site to a new version with bug fix.
Look a this thread with the version that worked with Moto E4 woods.
https://forum.xda-developers.com/mo...rp-3-1-1-r1-port-xt1760-t3772249/post76177524
Click to expand...
Click to collapse
Dude,
learn how to read a full post with instructions & proper way of reporting an issue anywhere you find yourself.
Know you device SoC, Architecture, etc ... don't just talk any how.
also, commits has not been merged
see on gerrit.twrp.me :=> https://gerrit.twrp.me/#/c/android_device_motorola_woods/+/63/
Finally, always check to see if no one has report similar issue and been solved before you start writing sh*t into the air
https://postimages.org/
https://forum.xda-developers.com/showpost.php?p=77250466&postcount=6
NOTE : MOTO E4 SERIES IS ARM(32bit) Architecture Device, stop trying to flash/install ARM64 Gapps as you stop being dumb.
OK
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Laruzzo said:
Ok, I´m sorry you are the developer and I should thanks for your great work. May you please share here the alternative file that works with gapps? Because I cannot access telegram at the momment. Thank you very much and sorry again if my words was not good. I respect and admire your work.
Click to expand...
Click to collapse
Download ⍖ ?
TWRP-323.0-Unofficial-woods.img
iykeDROID™ said:
TWRP is an open source, community project.
..
..iykeDROID™[/URL] {dumbDevpr*}
Source Code: https://github.com/TeamWin
[/SIZE][...his other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
Abish4 said:
Format Data Partition with F2FS format is not available which is usually available with every Moto Device Kernel
Click to expand...
Click to collapse
please deal with the kernel source here : https://github.com/MotorolaMobilityLLC/kernel-mtk/tree/nougat-7.1.1-release-woods
Abish4 said:
Can you help with this other way cause I doubt about official ¿‽
Click to expand...
Click to collapse
due to negligence, you couldn't check the source code here : https://github.com/TeamWin/android_device_motorola_woods
also check the twrp site : https://twrp.me/motorola/motorolamotoe4.html
I cannot flash gapps arm 7.1.x
Hi. I have one MotoE4 XT1763 Mediatek MT6735 with unlocked bootload.
would you recommend flashing the
twrp-3.2.3-0-woods.img 15.1M
Or the
TWRP-323.0-Unofficial-woods.img 15.5M
for the Lenovo Moto E4(XT1762)
?
Thank you peoples. TWRP unofficial working fine
Hey peoples. Accidentally i wiped my system. I have a backup in pc. I dont have sd card right now. How can i put the backup wich is in pc back to TWRP backup folder in order to restore ?
As we all know the Oreo is something that is quite distant for our device.
We need testers for Oreo Builds who can report bugs with accuracy, provide the logs required and have basic experience in software testing.
Be aware that the current & later releases are unstable & cannot be used as daily drivers.
BUG:
I don't have device test
Installation Instructions:
- Download the ROM
- Put the downloaded zip files on your SDCard
- Reboot in Recovery
- Wipe System, Cache, Dalvik Cache, Internal and Data Partition
- Flash rom
- Reboot system
Download from google drive: https://drive.google.com/drive/folders/1ktJvwxpb6aFHIr36gOZmv9I32e6gZd2M
XDAevDB Information
[WIP] Oreo Testing & Bug Fixing (T00F/T00J), ROM for the Asus ZenFone 5
Contributors
@nutcasev1.5, @tank0412, @flex1911, @nguyenhung9x
Source Code: github.com/Zentalk-VN
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: Lineage
Version Information
Status: Alpha
Current Stable Version: None
Current Beta Version: None
Created 2018-08-17
New build flash to fastboot : lineage 15.1
good work
I have updater eror 7 when flash rom
aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
I will update again file zip , please wait
aman3378 said:
I have updater eror 7 when flash rom
Click to expand...
Click to collapse
https://drive.google.com/file/d/1jouImtwKCEjnKdrWLQ7lig8AdRvxtOtD/view?usp=sharing
Flash again , i have try fix it
nguyenhung9x said:
Flash again , i have try fix it
Click to expand...
Click to collapse
at the end flashing updater eror 11 and bootloop with reboot
Plz fix camera
as the title says, can you please fix the camera? I had no issues with the camera when unlocking the bootloader but when i flash this rom, it says cannot connect to the camera. thx
aman3378 said:
at the end flashing updater eror 11 and bootloop with reboot
Click to expand...
Click to collapse
I have update file zip new , please downloads and flash again
nguyenhung9x said:
I have update file zip new , please downloads and flash again
Click to expand...
Click to collapse
where can i download this ZIP , the link under the post has an old version
nguyenhung9x said:
I will update again file zip , please wait
Click to expand...
Click to collapse
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940
nutcasev1.5 said:
Hello. Seems like you are doing Z00T Z00F builds for lineage 15 using my sources.
You should atleast inform me that you were going to use my sources. Even if they were open. So that we could inform you of bugs & other things.
Also, you can not just plaigarize my original post in a thread I opened.
This feels like you want to use my work & take credit for it.
Click to expand...
Click to collapse
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post
is there any point to test on the zenfone 6?
nguyenhung9x said:
kkkk I have build lineage 15.0 and it boot last years , https://github.com/VTEK-TEAM , omg
https://forum.xda-developers.com/zenfone-5/development/rom-lineageos-15-0-nguyenhung9x-t3673940
Click to expand...
Click to collapse
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
nguyenhung9x said:
I use device base fugu oreo and + hardware/intel branch 8.1 of you , i have thanks you in post
Click to expand...
Click to collapse
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
I'm sorry, I'm lazy so I'm copying your post, but I'll milk it in the future
nutcasev1.5 said:
Yes. I have mostly you to thank for the ril somewhat working on Z00A/8.
Sorry.
Yes. I get it. I don't want a full banner in my name. But this thread is new. 2 days old. & you have mostly copied my threads original post. The opening paragraph is an exact copy. Layout is the same.
I guess it doesn't make a difference.
I apologize. I didn't know that you were actually contributing to the community & not just compiling someone's work.
Click to expand...
Click to collapse
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2
nguyenhung9x said:
If you and I help each other build the android device, I think maybe Ril will work on Zenfone 2
Click to expand...
Click to collapse
Most of my development happens on telegram.
Let's get in touch there.
t.me/nutcasev1_5
There are 5 or 6 things to fix in the data structures & then some shimming to do.
@nguyenhung9x Based on 8.1? I'm gonna try it once I get my screen repaired.
error 11 and bootloop
just at the end in twrp it shows error 11 and when tried to reboot to system, it sends me to recovery