[RECOVERY] TWRP v2.6.3.0 for D605 - LG Optimus L3 II, L5 II, L7 II, L9 II

Team Win Recovery Project for d605
upstream source v2.6.3.0 build
Source
found no bugs in nandroid backup and restore
Only some false translated touch event issues at terminal emulator.
Install: flash the file in CWM:
Download zip file

Give more happiness to your tutorial!

Thanks good man,
We've waited a long time,
CWM is good,but TWRP......
Ty again.......

This is happening omg
Edit: waiting for some feedback before installing, someone PLEASE try installing paranoid android using this

It works good, but not solve Paranoid black screen problem.

Maydar said:
It works good, but not solve Paranoid black screen problem.
Click to expand...
Click to collapse
R.I.P.

Thanks for informations, happy that is working for you. I know, tutorial is a bit short

If you have CWM, then you just backup whole rom, and then youre good. That zip overwrites only recovery partition
RaawrItsTomi said:
This is happening omg
Edit: waiting for some feedback before installing, someone PLEASE try installing paranoid android using this
Click to expand...
Click to collapse

Nice work man! Thanks for this
Sent from my LG-D605 using CM11 V11

Good job, I think it would be great if you gave link to the source code you used to build it in the OP. I think it's required by Original Development section to include the source?

PA
TWPR is working perfectly whit pa

Do you plan to make an update to current version?

I can update it for you if you want. I don't have the device though so I need a good english talker to give me some info about the device.
EDIT: I ported latest TWRP for your device. Need someone who can test it and tell me if it's good. Do not worry worse it can happen is not boot. No hard-brick dangers.

Sorry for long silence everyone, now isnt need for update. So maybe latter or if someone find bugs in my build.

Can I install future builds by Varcain with this? Or I'd have to install the new CWM?

I think that it will work with new builds...
Sent from my LG-D605 using XDA Free mobile app

Does it (TWRP) have Loki integrated like CWM? If no then it won't work - unless you lokify the boot.img inside zip manually. I am switching to new release method and it also depends on recovery being able to Lokify the boot.img when needed.

Thanks, you need to patch that boot.img. I was thinking that every roms would be already patched before compresion.
Sent from my LG-D605 using XDA Free mobile app

I will be thankful for pushing code at github, so we can stay up to date. If you decide to not publish your updates, I can reinvent wheel and make some ugly hack, that do same work in TWRP.
Varcain said:
Does it (TWRP) have Loki integrated like CWM? If no then it won't work - unless you lokify the boot.img inside zip manually. I am switching to new release method and it also depends on recovery being able to Lokify the boot.img when needed.
Click to expand...
Click to collapse

I messed my building tree so badly, that i need start from scratch once more time. I made no changes to twrp source. Only few setting at BoardConfig.mk
but if its required, here it is: http://frame.jailbrake.cz/recovery.zip
Varcain said:
Good job, I think it would be great if you gave link to the source code you used to build it in the OP. I think it's required by Original Development section to include the source?
Click to expand...
Click to collapse

Related

[RECOVERY][YP-G70] TWRP v2.8.0.0 [METICULUS]

bigbiff said:
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues:
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Support:
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers
Click to expand...
Click to collapse
SPECIAL NOTE: "Alternative recoveries" only work with ROM's built after 20140510 and only on the Nutella Kernel.
Download: meticulus.co.vu
XDA:DevDB Information
TWRP for Galaxy Player 5, Tool/Utility for the Samsung Galaxy Player 4.0, 5.0
Contributors
Meticulus
Version Information
Status: Testing
Created 2014-09-05
Last Updated 2014-09-11
Dude you are awesome
Sent from my YP-G70 using XDA Free mobile app
also work with beanstalk last build ?? btw great job again :good:
lildhiel08 said:
also work with beanstalk last build ?? btw great job again :good:
Click to expand...
Click to collapse
Yep?
Meticulus said:
Yep?
Click to expand...
Click to collapse
btw ur new rom bro ? nexus5 wel it work for switch internal
lildhiel08 said:
btw ur new rom bro ? nexus5 wel it work for switch internal
Click to expand...
Click to collapse
Its not my ROM. Its @kykint ☺
Meticulus said:
Its not my ROM. Its @kykint ☺
Click to expand...
Click to collapse
oh ..sorry bro
Status 7 error
edit: nevermind, I didn't go thru the alternative recovery install procedure...duh
Hi Meticulus,
Thanks for all you do !!
When I try to install, I get "This package is for m470 devices; this is a "YP-G70" "
beeewell said:
edit: nevermind, I didn't go thru the alternative recovery install procedure...duh
Hi Meticulus,
Thanks for all you do !!
When I try to install, I get "This package is for m470 devices; this is a "YP-G70" "
Click to expand...
Click to collapse
I double checked everything... looks like you downloaded the wrong one. Make sure to download from here: http://www.meticulus.co.vu/p/twrp-2630-for-galaxy-player-5.html
EDIT: alternative recovery procedure not needed, just flash in current recovery. m470 is Hisense Sero 7 Pro.... Definately downloaded the wrong one...
Meticulus said:
I double checked everything... looks like you downloaded the wrong one. Make sure to download from here: http://www.meticulus.co.vu/p/twrp-2630-for-galaxy-player-5.html
Click to expand...
Click to collapse
Thanks again. That's exactly what I did !!! :good:
All I am receiving is cloud storage when I try to download recovery.
iselfseeallah said:
All I am receiving is cloud storage when I try to download recovery.
Click to expand...
Click to collapse
You need to either "Request the Desktop site" or install the MEGA app from the playstore.:highfive:
Not, I will do with out.
OP updated with new link...
Meticulus said:
OP updated with new link...
Click to expand...
Click to collapse
I have Clockwork installed and it acts as if it flashes OK but when I reboot or restart its reverted back to clockwork. Thoughts?
cvondra said:
I have Clockwork installed and it acts as if it flashes OK but when I reboot or restart its reverted back to clockwork. Thoughts?
Click to expand...
Click to collapse
Um try READING the op.
I'm a little late to the party, but I've gotten my hands on an YP-G70. I tried installing TWRP on it, but CWM complaints about it being the wrong version. I couldn't see any different versions of it...I've also tried flashing it with Rashr flash tool, but that one also says it's not a valid recovery.
Any hints as to what I can do next?
I have been attempting to install CM12 / Carbon 5.1.1. I have worked my way up from GB to CM 11 / Carbon KK 4.4.4 then I get stuck.
After installing on reboot I get an initial Nutella logo for a few seconds and then the screen goes black (although you can tell it is still backlit) and then nothing. Left it for a couple of hours just in case it required a long install time... nothing. I can get it into this rudimentary recovery fwiw.
So came across this, Is it still mandatory to install TWRP 2.8.0.0? If so could someone kindly upload or add a new link please. Most are to Mega which is now kaput.
I tried installing from Slim 4.4.2 ( Beanstock is also on Mega but it only has TWRP 2.6.5) as suggested somewhere but no go either.
Thanks for breathing life back into my Player 5, I am eager to try Lollipop on it.
Thanks in advance.
How do I install it? I am on stock firmware, do I need a custom firmware first?
tiwas said:
I'm a little late to the party, but I've gotten my hands on an YP-G70. I tried installing TWRP on it, but CWM complaints about it being the wrong version. I couldn't see any different versions of it...I've also tried flashing it with Rashr flash tool, but that one also says it's not a valid recovery.
Any hints as to what I can do next?
Click to expand...
Click to collapse
I'm stuck at the same place. The error msg seems to imply its for the USA version:
"This package is for yp-G70, venturi,venturi_USA" devices. This device is a "herring".

[ROM] [5.1.1_r1] [Deb] Lustrous Lollipop for Nexus 7 (2013) LTE

Introduction
I'm not really into writing long elaborate OP posts, so here it goes. This is an AOSP compiled, flashable ROM. This ROM is fast and smooth, it is not bloated with useless features. Lustrous ROM has features being added that make it even more useful. You need the 4.04 bootloader! I put a lot of work and love into this rom, if you like it show me some support by donating!
Downloads
ROM Download: Click here!
SuperSU: I'm using 2.40 found Here
First Time Install
Put the file onto your Internal Storage/USB-otg
Reboot into Recovery (CWM/TWRP)
"wipe data/factory reset"
"install zip" -> "install zip from sdcard" -> choose the .zip and confirm (Optional: Add the other zip to flash... TWRP Only I believe)
"Clear cache/bla bla bla"
Flash Gapps
"Clear cache/bla bla bla"
Reboot
first boot may take up to 10 minutes
Features
RRO built in (for Layers)
Super smooth
OTA Updates
Build.prop edits for stability and speed
Super close to stock AOSP
stock kernel
BUGS
I am not sure of any bugs, haven't come across any. If you find some let me know and I'll get it fixed right away!
Credits
Thanks to @sykopompos for being my mentor and helping me out with a lot of things
Thanks to @scrosler for some tidbits and ideas
Thanks to @Chainfire for root
Thanks to the Simple AOSP team for the new gapps
Disclaimer: I am not responsible for anything that may happen to your device, yourself or your family. Flash at your own risk!
XDA:DevDB Information
[ROM] [5.1.1_r1] [Deb]Lustrous Lollipop for Nexus 7 (2013) LTE, ROM for the Nexus 7 (2013)
Contributors
skiman10
ROM OS Version: 5.1.x Lollipop
Based On: AOSP
Version Information
Status: Beta
Created 2014-11-08
Last Updated 2015-06-02
Reserved
Reserved
Thanks for posting. Will update you after I install the ROM
Sent from my Nexus 7 2013 LTE using XDA Premium 4 mobile app
Sweet thanks. Downloading, going to give it a spin.
And yep, that SuperSU is the latest.
Thx @skiman10 will Test it in the evening.
@skiman10 Is this an updated permissive boot image?
great many thanks for your work! Finally lollipop has come to DEB!
Thanks for this ROM. Finally can use android 5.0 on my deb nexus 7.. Successfully flashed this and so far so good. No problem or force close yet. Haven't tried with sim. Everything's run smoother now.
I can confirm that the mobile data is working however I lost my TWRP recovery after flashing it
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Everything's working great except Earth and Google Maps, even if the location is ON in high accuracy mode.
Where do i get the 4.0.4 Bootloader for DEB? I only found it for FLO...
mkretzer said:
Where do i get the 4.0.4 Bootloader for DEB? I only found it for FLO...
Click to expand...
Click to collapse
Flash the FLO bootloader. It's OK.
is it only working as primary via multiRom recovery?
I installed it as secondary and it failed to boot.
Google+ still missing for me here
Just finished booting.
Root is no-go for me (says binaries not installed despite having installed supersu zip).
Gonna see if I can tinker around with it to make it work, but for now no root for me.
jayfallen said:
is it only working as primary via multiRom recovery?
I installed it as secondary and it failed to boot.
Click to expand...
Click to collapse
That is an affirmative.
Also after you install it as primary, you'll need to install a kexec kernel to be able to boot to your other (now secondary) rom.
ElementalX 3.00 should work fine for that.
Ambious said:
Just finished booting.
Root is no-go for me (says binaries not installed despite having installed supersu zip).
Gonna see if I can tinker around with it to make it work, but for now no root for me.
That is an affirmative.
Also after you install it as primary, you'll need to install a kexec kernel to be able to boot to your other (now secondary) rom.
ElementalX 3.00 should work fine for that.
Click to expand...
Click to collapse
root does not work
on this core
I flashed my deb to stock 4.4.4, installed twrp, followed all instructions in op, and I cannot root. Thus I second another user's experience with root not working/SuperSU saying there are no binaries installed. I did install the supersu zip in twrp.
Also can't install Google+ neither from Market nor APK.
Fixed by flashing newer gapps package found here.
hhairplane said:
@skiman10 Is this an updated permissive boot image?
Click to expand...
Click to collapse
I might have to update the boot.img more, I'm pretty sure it is in permissive mode right now. I'll check that out right now.
BladeRider said:
I can confirm that the mobile data is working however I lost my TWRP recovery after flashing it
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hmmm you shouldn't have lost your recovery.... I should have turned that off. Let me look. Also you still rock a Galaxy Nexus? Respect.
florynn2003 said:
Everything's working great except Earth and Google Maps, even if the location is ON in high accuracy mode.
Click to expand...
Click to collapse
Ok so GPS is a no go. Got it
hhairplane said:
Google+ still missing for me here
Click to expand...
Click to collapse
What gapps did you flash?
DeathmonkeyGTX said:
I flashed my deb to stock 4.4.4, installed twrp, followed all instructions in op, and I cannot root. Thus I second another user's experience with root not working/SuperSU saying there are no binaries installed. I did install the supersu zip in twrp.
Click to expand...
Click to collapse
I'll look into root right now. I might have missed something in the bootloader
Good morning everyone! I'm awake and ready to smash bugs!

[ROM] VanirAOSP [unofficial][5.1.1]

​
VANIR AOSP 5.1.1 UNOFFICIAL​
Here is my litte private ROM from VanirAOSP which I really like.
Till now this ROM only has the VanirAOSP Features.
It's based on 5.1.1. The orginal VanirAOSP is based on 5.0.2
This is my FIRST ROM. Please try it and give me a Feedback.
I search Guys who are interested to join my little Project, pls PN me
Features
- Theme Engine
- Statusbar Mods
- Buttons
- Quicksettings
- Gestures
...all Vanir Features.
Installation
-Backup
-Full Wipe
-Flash Rom
-Flash Gapps
-Fertig
Downloads
ROM
GAPPS​
nice!
awesome love aosp
which gapps should i download?
I use these: [ ]
51Current-DHO-GAPPs.zip
malavan said:
awesome love aosp
which gapps should i download?
Click to expand...
Click to collapse
Any 5.1 gapps should be fine.
Transmitted via Bacon
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
Could someone please mirror this, i keep getting a"download failed" error on google drive
Sent from my A0001 using XDA Free mobile app
rogi19 said:
Could someone please mirror this, i keep getting a"download failed" error on google drive
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
You need to ask the dev if he allows mirrors first please.
Awesome sauce
Is this built with Uber or stock google GCC?
Wont flash.. Something about the binary zip error..
OmegaBlaze said:
Wont flash.. Something about the binary zip error..
Click to expand...
Click to collapse
Booted up perfectly fine for me.
_ASSASSIN_ said:
Booted up perfectly fine for me.
Click to expand...
Click to collapse
Recovery? Multirom?
OmegaBlaze said:
Recovery? Multirom?
Click to expand...
Click to collapse
I don't use multiROM.
I personally see it as a security risk as well as great way to f**k up your device.
_ASSASSIN_ said:
I don't use multiROM.
I personally see it as a security risk as well as great way to f**k up your device.
Click to expand...
Click to collapse
What's so insecure about it.. And what recovery are you using..
OmegaBlaze said:
What's so insecure about it.. And what recovery are you using..
Click to expand...
Click to collapse
I use the latest TWRP 2.8.6.0 with the material design theme but I don't that changes too many things.
_ASSASSIN_ said:
I use the latest TWRP 2.8.6.0 with the material design theme but I don't that changes too many things.
Click to expand...
Click to collapse
Multirom IS TWRP.
LOL gotta stop being scared man. Its fine.
OmegaBlaze said:
Multirom IS TWRP.
LOL gotta stop being scared man. Its fine.
Click to expand...
Click to collapse
Multirom is not twrp. Its based on twrp but has some hacks in it that let's you boot another ROM.
I have no idea about how it works but its certainly not harmless and can have problems when using it
I don't use it. Not because I am worried about security or it messing up my device. More just because it takes hardly any time to just make a backup of a ROM I am using
ogrillion said:
Multirom is not twrp. Its based on twrp but has some hacks in it that let's you boot another ROM.
I have no idea about how it works but its certainly not harmless and can have problems when using it
I don't use it. Not because I am worried about security or it messing up my device. More just because it takes hardly any time to just make a backup of a ROM I am using
Click to expand...
Click to collapse
You have "no idea how it works", nor have you flashed it so I can't listen to you. All hearsay.
OmegaBlaze said:
You have "no idea how it works", nor have you flashed it so I can't listen to you. All hearsay.
Click to expand...
Click to collapse
Did I say I have NEVER flashed it, no.
You should learn to do research BEFORE you flash something on your device.. You are opening yourself up to all sorts of problems.
This is direct from the creator of multirom thread.
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Anyways done with this discussion.
Sorry for going off topic OP its disrespectful to your thread. Thank you for your work, and providing a ROM to this community.
timmaaa said:
You need to ask the dev if he allows mirrors first please.
Click to expand...
Click to collapse
Sure, you can upluad it to a Mirror.
I flashed it in TWRP and everything was fine

[GUIDE] Helper zips to switch between OOS 3.0 and OOS 2.2.1 firmware

At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
We are waiting for AD release. At least a beta?
mido25 said:
We are waiting for AD release. At least a beta?
Click to expand...
Click to collapse
Don't you know how to use the JustArchi's github?
Wow, really helps. I wish I have my OnePlus2 now.
Guihardrock said:
Don't you know how to use the JustArchi's github?
Click to expand...
Click to collapse
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
mido25 said:
No sir. I do not know. Once I tried downloading a build from the below location and tried flashing it but recovery didn't allow me to flash it.
https://t.co/96EZIl6dJJ
I don't know why is it failed. My knowledge about github and making builds are limited.
Click to expand...
Click to collapse
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Guihardrock said:
ok so i will explain you when you download that file you have to unzip it and then you will have a folder with another folder (if you choosed unzip in archidreoid etc.zip so inside that folder you will have the necesary files (view the attached screenshot) you will have to pack them in a zip file
hope it helps but try to download the latest file to do that cause last time i tried the oneplus2 archidroid there were things that dint work such as ad filter
Click to expand...
Click to collapse
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
mido25 said:
Thanks a lot for your guidance. Appreciate if you can give a link to his latest build.
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Lost recovery
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
JustArchi said:
At the moment we have rather dfficult situation because custom ROMs based on AOSP (such as my AD which is not yet public) require previous OOS LP firmware, while OOS 3.0 includes new MM firmware which breaks both older recoveries and custom ROMs.
As I need to switch between OOS 3.0 and my AD quite frequently, I created two helpful flashable zips so I can do that easily, and because it's useful for me, perhaps it'll be useful for you too.
Download: MM | LP
Instructions:
- Download the firmware you want (or both, if you want easy switching)
- Unpack downloaded zip, you'll find firmware-update.zip and recovery.img inside
- Put both of those files on your phone, in appropriately named directory such as "firmware-LP" or "firmware-MM"
- When you will need to do a switch, simply firstly flash firmware-update.zip, then flash recovery.img as recovery image via "flash image" option in TWRP
- Reboot to load new firmware
That's it, this way you firstly flash chosen firmware version, and then TWRP recovery that works with it.
So if you have two TWRP backups - one of OOS 3.0 and one of CM13.0, make sure that you have proper firmware (and recovery) after restoring backup - LP for CM13.0, and MM for OOS 3.0.
Situation should soon improve (when OnePlus pushes kernel sources, and MM-based ROMs will rebase), but until then it's wise to keep both of those firmware + recovery combos on your sd card, so you can do a switch without any problem on as-needed basis.
Hope it helps. Try to be careful with those, if you mix up wrong recovery with wrong firmware you'll need to flash proper recovery.img variant via fastboot. You can't hard brick anything by using those files, in worst case soft-brick if both your recovery and your ROM will be for wrong firmware you have.
Have fun.
Click to expand...
Click to collapse
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
eswa1068 said:
Hi sir,
I have flashed MM using the TWRP recovery as normal. But now I have lost my recovery. I am not able to boot into any recovery. Pls help.
Click to expand...
Click to collapse
Use fastboot to flash the recovery
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
Thank you Sir
Tierri said:
Your ll recovery is in chinese. How to change it?
EDIT: Forget it. I found where to change the language! Thanks.
Click to expand...
Click to collapse
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
amit_sen said:
Hi,
Can u let me know where to change the language of twrp ?
Sent from my ONE A2003 using Tapatalk
Click to expand...
Click to collapse
Yes. See the images to help you.
Guihardrock said:
Here you go https://github.com/ArchiDroid/ArchiDroid/archive/oneplus2-cm-experimental.zip but its experimental so you can expect bugs
Click to expand...
Click to collapse
It's around 900 mb zip..?
And did anyone try that build..?
Mohit31 said:
It's around 900 mb zip..?
And did anyone try that build..?
Click to expand...
Click to collapse
Its because of the aroma you can choose the gapps of your choice...
Guihardrock said:
Its because of the aroma you can choose the gapps of your choice...
Click to expand...
Click to collapse
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
This thing should be STICKY
Finally was able to install CM13 properly using this recovery without Google Services crashing.
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
Now i am in oos3 but when justarchi release archidroid i wont use any other rom, i had so great experience with this on my s3
Edit: i am gonna try it :3 yo made me do it
Mohit31 said:
OK... Thanks
Btw Are you on this build..
A quick feedback on the ROM would be great
Click to expand...
Click to collapse
rom is smooth as h*ll and battery is better than in normal cm13 but as i said the backed dont work yet :3 and aroma is not fully functional with the bootanimation and root (but the rom has the cm superuser)

[RELEASE] F2FS bug fix kernel (Qualcomm)

I patched the kernel for 7.1.1 on Qualcomm Moto E4 Plus. This is useful to get Magisk fully working with modules and settings that can be saved.
I compiled the fix from the released kernel source: MMI-NPR26.58-25
Here are the unsigned boot.img and zImage, use whichever one suits your fancy to patch the kernel.
Download boot.img
Download zImage
Edit: I've uploaded a build for the regular Qualcomm Moto E4 here.
Installation:
You should backup your Boot in TWRP before installing, that way you can restore if something goes wrong.
If you have Magisk installed, you'll want to patch the boot.img using Magisk Manager. Just tap install, and patch boot rom image. Then copy the patched file back to your computer to flash it.
Easiest way is to flash the boot.img while in fastboot:
Code:
>fastboot flash boot /path/to/downloaded/boot.img
Did not work, phone would not boot after flash, had to restore stock kernel.
TheJAYpoop said:
Did not work, phone would not boot after flash, had to restore stock kernel.
Click to expand...
Click to collapse
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
SeanStar said:
Hmm, having tried it myself, I see that without patching the image with magisk from inside magisk manager, it seems the rebuilt boot image does not work. But it does work after it's been patched in magisk, so you can try that.
Here's a link that's already been patched with Magisk 14.6 beta: https://drive.google.com/open?id=13vaUgq22fNnVnWqq5ai9kGC1KsO3ZEmJ
Click to expand...
Click to collapse
That worked perfectly, awesome!
TheJAYpoop said:
That worked perfectly, awesome!
Click to expand...
Click to collapse
Merry Christmas! Enjoy the full Magisk experience, it was really bothering me when I got this phone about half a week ago.
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
GetOffMyLawn&!+¢#{$ said:
Nice, I was planning on doing this after Christmas. Saved me the trouble. Merry Christmas to you too! It worked fine just flashing the patched img with TWRP. Want to save me the trouble of doing one for the regular E⁴ also?
Click to expand...
Click to collapse
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
SeanStar said:
If you point me to the kernel source you specifically want patched, I can make it. You'll have to test it for me though, as I don't own the regular E^4.
Click to expand...
Click to collapse
That would be great. I'll pm you a link since I can't post links yet. I've been spending all my spare time trying to get data working properly on both devices. I have no problem testing it.
Sent from my Moto E (4) Plus using XDA Labs
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Thank you very much for taking the time to do this! Especially today. Just to point out how I installed the kernel, I simply flashed it as an img with TWRP, flashed the no dmverity/forceencrypt zip, then flashed Magisk V15.0 that was just released. It stayed on the n/a screen a minute then bootlooped a couple times, but it eventually booted just fine, so be patient with it. I had the latest Boost firmware installed and Magisk v14.6 at the time. Enjoy!
Sent from my Moto E (4) Plus using XDA Labs
Thanks @SeanStar for the regular e4 boot.img. you rock bro. Works great. Tested, successful
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
jasonmerc said:
@SeanStar would you mind uploading the source to your kernel, like maybe on a GitHub repo or something? I'm working with a friend who has the owens and I'm trying to see if we can get a more functioning Lineage 14.1 on here
Click to expand...
Click to collapse
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
SeanStar said:
Though the kernel I am currently working on is slightly modified more than what is provided here, the OP only has the fix for the f2fs loopback issue, as described here: https://forum.xda-developers.com/showpost.php?p=70492947&postcount=8793
You can download the stock kernel build source from Motorola's own repository here: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPR26.58-25
Also, I admit that I'm currently in the process of porting Lineage 14.1 to this phone, but it may take more time than I had originally planned for. It's not a priority for me at the moment, especially considering how much I like the stock rom.
Click to expand...
Click to collapse
Well dang, I'm working on porting lineage 14.1 to this thing too. Maybe we should join forces.
And moto's source is in a zip file, I was hoping I could get one that was unzipped and in a github repo already, for easy syncing when trying to build Lineage 14.1
Thank you for your work. I agree that stock isn't too bad with root magisk and Xposed working fine. But lineage is pretty tasty! I will shoot you both a PM if I can assist in any way
@SeanStar check out these screenies everyone:
Sent from my Moto E (4) Plus using XDA Labs
GetOffMyLawn&!+¢#{$ said:
@SeanStar check out these screenies everyone:
Click to expand...
Click to collapse
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
SeanStar said:
I'm not sure if they're still doing updates for this phone from what I've heard, but if they do this would be very nice.
Click to expand...
Click to collapse
That sucks to hear, but although I do actually like stock on this device, that's why I build custom ROMs. Budget Motorola's never get updated more then a few times. Hopefully it will get added for future devices and ones that don't get abandoned at least.
Sent from my Moto E (4) Plus using XDA Labs
SeanStar said:
Qualcomm Moto E4 f2fs fix for perry 7.1.1 (Built and patched from NCQ26.69-48 source) kernel boot image for anyone that wants it is linked below. Thanks to GetOffMyLawn&!+¢#{$ for testing. See the OP for installation instructions, and please remember to make backups of your stock Boot.
Download:
unsigned boot.img
zImage
Click to expand...
Click to collapse
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
PimpMy5Ton said:
Hey @SeanStar would it be possible for you to do this on the latest update for the kernel on the E4 Perry please?? The reason being is this one can't be used on the latest update of the firmware, it fails to boot all the way up.
EDIT: The latest is NCQ26.69-56
Click to expand...
Click to collapse
Considering there is no kernel source for NCQ26.69-56 on MotorolaMobilityLLC github, you're SOL, there's no easy way to patch it without the source. Sorry bud.
EDIT: I wouldn't try to downgrade either, I'm sure they updated the baseband. You'll probably knockout your service if you even try.

Categories

Resources