Closed per OP request
TWRP 3.3.1-0 FOR GALAXY J5 (2015)
DISCLAIMER : I AM NOT RESPONSIBLE VOIDING YOUR WARRANTY OR ANY DAMAGE CAUSED TO YOUR DEVICE
This is a port of TWRP 3.3.1-0 to Samsung Galaxy J5 (2015).
This project is discontinued. Please visit Unofficial TWRP 3.3.1 thread. Recoveries are built from source. [url]https://forum.xda-developers.com/showthread.php?t=3946500[/URL]
Thanks to @RioFebrian for his work on TWRP 3.2.1-1 PRO.
Thanks to @Augustoandro for his TWRP porting guide
Base: TWRP 3.2.1-1
[url]http://forum.xda-developers.com/galaxy-j5/development/recovery-recovery-pro-galaxy-j5-2015-t3728264[/URL]
Port: TWRP 3.3.1-0
[url]http://dl.twrp.me/tilapia/twrp-3.3.1-0-tilapia.img.html[/URL]
FEATURES
-Standard TWRP features
-Backup/restore/format/mount:
-IMEI 1, IMEI 2, FRP PARTITION, EFS, APNHLOS, RPM, MODEM, HIDDEN, QSEE, QHEE, PERSDATA, USB OTG
-Support All languages
-Android 9.0 compatible
BUGS/KNOWN ISSUES
-N/A
DOWNLOAD
J5LTE (F/G/M/NO/Y)
Removed
J5NLTE (FN)
Removed
J53gxx (H)
Removed
Source
Removed
Thank you so much for your work. I have flashed your recovery 3.3.1 over version 3.2.1. It works fine (there are those bugs you wrote about. I haven’t yet found other bugs). I backed up the system and then successfully flashed the firmware [ROM] [J500xx] [TW-7.1.1] [v5.0] SEPerience-ROM A8 2018 Port. After these actions, I made logs. And special thanks for the support of AROMA))
Here are the links: https://drive.google.com/open?id=1-h1PjViT_eHCe99EIecHAAiB2akMj5v7
https://drive.google.com/open?id=1-UEHGpxoTEjnI3cbATiZmjlYgyRmsjxJ
My device J500H
Tested & Worked on Samsung Galaxy J500G. :good::good:
Thanks for the hardwork, flashed a [ROM][9.0.0_r40]PixelExperience for Galaxy J5 (All variants) and it was success!.
No other bugs than you mentioned so far.
Olexpz said:
Thank you so much for your work. I have flashed your recovery 3.3.1 over version 3.2.1. It works fine (there are those bugs you wrote about. I haven’t yet found other bugs). I backed up the system and then successfully flashed the firmware [ROM] [J500xx] [TW-7.1.1] [v5.0] SEPerience-ROM A8 2018 Port. After these actions, I made logs. And special thanks for the support of AROMA))
Here are the links: https://drive.google.com/open?id=1-h1PjViT_eHCe99EIecHAAiB2akMj5v7
https://drive.google.com/open?id=1-UEHGpxoTEjnI3cbATiZmjlYgyRmsjxJ
My device J500H
Click to expand...
Click to collapse
That actually did help, i found and fixed the usb otg error. I'm still looking into the other issues. I will upload fixed files in a few hrs. Meanwhile i am looking back into building from source, but you know how life is.
Question to those who know more than me, would you build from twrp's main repo or the minimal manifest repo? Obviously the branch would be twrp-9.0 in either case.
UPDATE
-Fixed USB OTG mount
-Removed cursor in middle of screen
palmbeach05 said:
That actually did help, i found and fixed the usb otg error. I'm still looking into the other issues. I will upload fixed files in a few hrs. Meanwhile i am looking back into building from source, but you know how life is.
Question to those who know more than me, would you build from twrp's main repo or the minimal manifest repo? Obviously the branch would be twrp-9.0 in either case.
Click to expand...
Click to collapse
I just updated your recovery. The bug with the cursor in the middle of the screen has disappeared. Recovery works without complaints. So I tried to dig in the settings (I changed the brightness (it still does not work) and i made logs:
https://drive.google.com/open?id=11rRsWPpfHSJnzHmCqMqJdcAqFrowot9d
https://drive.google.com/open?id=1tAGDjuKB8plg-iRryst9Z2xIk4F2DOS6
I'm expecting to depreciate this thread in the coming days.
Thread depreciated, requested to be closed. Links to be removed. Builds from source now available in unofficial twrp 3.3.1 thread.
[url]https://forum.xda-developers.com/showthread.php?t=3946500[/URL]
Sent from my [device_name] using XDA-Developers Legacy app
Hello,
As the thread where I originally announced this was locked for reasons apparently unrelated to my build, and the links removed, I'm creating a new thread to keep the community aware of these builds.
I've been building LineageOS 14.1 from the official LineageOS source repository for my personal devices for some time now, and it finally occurred to me that others might find them useful.
These builds are created every Saturday night from a 100% unaltered LineageOS repository, which is synchronized with upstream every day. I must stress that there are NO MODIFICATIONS at all; if it worked/didn't work in the last official Cyanogenmod/LineageOS releases, it works/doesn't work in my builds. At Apple we called these "sustaining builds" -- they keep devices in sync with the latest security patches, but receive no new features.
The build for the Asus Zenpad 8.0 Z380K[N]L (aka P024) is at https://lineageos.disavowed.jp/p024/. This appears to work on both the Z380KL (as reported in the locked thread) and my Z380KNL. There are other devices being built as well ... if you would like me to add a 14.1 or 15.1 device to the weekly build roster, please let me know.
I hope this helps out folks who want to extend the service lifetime of their gear. Share and enjoy.
Edit: per moderator request, I need to provide a link to the source repository used to generate these builds to comply with XDA's interpretation of the GPL. It is the stock LineageOS repository, located at git://github.com/LineageOS/android.git. TheMuppets binary repository was used for the vendor blobs; it is at https://github.com/TheMuppets/
Hi, I have been using your build and updated my device weekly! it' s still good and awesome. (I also use your build for my nexus7)
if you find Oreo, Pie version! please let everyone know. Thank you.
Thank's keep update bro.
Hi, I don't see your weekly build for 22 Nov 2019.
Are there any issues ?
Nice update thanks friends l.
Yeap yesterday i reported, and TS promised to update.
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Argh, apparently I wasn't subscribed to my own thread. Fixed.
Sorry about the SIM recognization problem. Somehow my private dev builds were being uploaded instead of the sustaining builds. @DEV87WHY pinged me a few days ago to let me know. The newest build is from the correct tree, and hopefully this won't happen again.
Sorry about that ...
Question about Unofficial rom for Asus ZenPad 8.0 z380knl
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
poka_dan said:
How do you update device with rom without losing apps and data? Is it possible to update from unofficial lineage os 14.1 from your repository to latest unofficial lineage os 14.1 build from your repository without having to reinstall apps? My understanding is that you follow the process of normal flash of rom but you don't wipe? Is that it?
Another question:
Does MTP(file transfer) work with this ROM?
Also, did you manage to unlock bootloader(oem unlock). I know it is possible to flash the rom without bootloader unlock. Is that how you do it or you have found a way to unlock bootloader?
Thank you so much.
Click to expand...
Click to collapse
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
As soon as I find out MTP is working I will flash the rom
wileyc said:
Hi there,
First off -- thanks for the gift! Much appreciated.
If you're just flashing one of my newer builds on top of one of my older builds, then you shouldn't have to do anything special. Just kick the device into recovery and flash on top of the older build. If you're coming from the ancient Cyanogenmod or the stock ROM, then AFAIK you'll have to wipe.
MTP *should* work but I've never tried it. I don't have my device with me right now so I can't do a quick verification.
For unlocking the bootloader, I'm trying to remember (this was several years ago). IIRC I put it into fastboot and did a tethered recovery boot (i.e., "fastboot boot /path/to/recovery_image_on_pc.img"). Then I did a full wipe and a flash ... and bricked the device because I had a Z380KNL and the Cyanogenmod image at the time supported only the Z380KL.
I then put the stock ROM back on, and when the KNL bits hit the Cyanogen repository, I flashed it with success. At no point did I ever successfully unlock the bootloader as far as I can tell -- I downloaded the ASUS unlock but it never reported success. When booted into fastboot, there's a locked symbol at the lower right of the screen. That doesn't interfere with flashing anything from recovery.
Oh, and important safety tip: to enter recovery from fastboot after you've flashed it via the tethered recovery boot, you'll have to choose "factory reset" on the KNL.
I hope that helps.
Click to expand...
Click to collapse
Gift was my pleasure
The info is most usefull. Thank you for that.
I am currently running my ZenPad 8.0 z380knl on Asus stock rom but ardently looking to upgrade to android 7.1.2 for security reasons as well as other reasons.
I was investigating if everything is working on the new rom. Also upgrade procedure from stock rom to lineage os and from lineage os 14.1 to latest 14.1 lineage os. Thankfully you cleared all that up. Thanks so much !
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
BTW, I haven't seen your new buld since last week.Will there be no update ?
Is everything working with this ROM?
Can i get confirmation from someone who is actively using it..
MTP and everything else working?
pokadan said:
Gift was my pleasure
Only thing that remains for me to find out is if MTP is working on rom, so please check it for me when you have the time.
Click to expand...
Click to collapse
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
androidlover2019 said:
BTW, I haven't seen your new buld since last week.Will there be no update ?
Click to expand...
Click to collapse
There should be an update (or two!) today. The build rooster hung about midway through last week's build for deb, and was actually still running after seven days. I killed off the deb build process and it's progressing to the other devices, although much slower than it should be. I'll troubleshoot this after the regularly scheduled build completes late tonight.
(I'm using Arch Linux on this build machine, and it seems that something in the filesystem layer in kernel > 5.4.10 doesn't like operating under sustained heavy load)
I saw your new build today and have installed it. Thank you
However, The latest security patch has not been applied yet. Hope it will come in next build.
Thank you so much for maintaining the device.
Thank you wileyc !
wileyc said:
I just tried MTP (using OpenMTP-2.4.1 on MacOS) and it seems to work fine.
Click to expand...
Click to collapse
I have put the latest available rom lineage-14.1-20200202-UNOFFICIAL-P024.zip on my device and works flawlessly!
Million thanks
I have installed the newest one (built on 08 Feb)
the Android security patch was updated to Jan 2020! Thank you very much.
I am worried how long you will keep sharing your build weekly.
Hope next 2 years Thanks again.
I have also installed the latest. Thanks so much!
Thankyou for the update :good:
What about selinux?
Hello everyone,
I was wondering if anyone knows if you can flash LOS 18.1 with TWRP 3.5.1?
As far as I could determine, TWRP does not yet officially support Android 11.
I am not really eager to use Lineage recovery because of the lack of backup support, but if there is no way around I guess I have to
Br,
GeForce66 said:
Hello everyone,
I was wondering if anyone knows if you can flash LOS 18.1 with TWRP 3.5.1?
As far as I could determine, TWRP does not yet officially support Android 11.
I am not really eager to use Lineage recovery because of the lack of backup support, but if there is no way around I guess I have to
Br,
Click to expand...
Click to collapse
Hey,
Ofc you can flash it via TWRP. It should work perfectly fine like any other ROM.
If you need any information about installation or something else, check my POCO F1 Ultimate Collection & Guides
Most of the TWRP projects are gone, official one is only for the PRO (vayu) version.
At this point we don't have single trustworthy recovery (except limited LOS), and still bunch of available custom ROMs.
Which version can we use with some security?