[RECOVERY][SURNIA]TWRP 2.8.6.0 for Moto E 2015 LTE - E 2015 Original Android Development

Hi guys I'm reposting this from another forum, this is not my work, just figured people might like to have this, if it has helped you please thank SuperR over at AF...
[QUOTE="SuperR"
DISCLAIMER: By using this recovery, you agree that you are the only one responsible for anything good or bad that may occur. Use at your own risk.
Install img:
Unlock bootloader
Download surnia_twrp_2860_v2-3.img to PC
Reboot to bootloader
Plug phone into PC
Open terminal in directory where the img is located
Issue the following command to flash:
Code:
fastboot flash recovery surnia_twrp_2860_v2-3.img
Or this command to test before flashing:
Code:
fastboot boot surnia_twrp_2860_v2-3.img
Enjoy!
Note: I only have the Boost Mobile XT1526 so that is the only device this has been tested on. It should work on the other variants as well. Please post feedback [/QUOTE]
Download: https://www.androidfilehost.com/?fid=23991606952612207

Hi @goldeneagle1972
Full work?

How is this different from the other TWRPs for surnia that are already here? We already have the original @cybojenix one (2.8.5 with prebuilt kernel), mine (2.8.6 using my kernel built from source), and the @vlcdsm one (2.8.6 with qseecom support).

Not my work, you'll have to ask SuperR on AF if you want an answer to that question, and for the record just because other varieties of TWRP are posted does not mean another one can't be posted, just want to make that perfectly clear
Sent from my XT1526 using Tapatalk

It's not appropriate to post another version if it is just an uncredited copy of the original versions developed here. Do you have a link to the sources?
EDIT: I found the SuperR thread http://androidforums.com/threads/twrp-2-8-6-0-for-moto-e-2015-lte.920652/
He's released a new version since the first post here. He says that he fixed date/time in this recovery, so that would be the main visible difference compared to the recoveries we have here. He hasn't posted any sources for the device tree, which is a bit suspect, but could be okay if he made it from scratch (which may or may not be the case). Closed source development hinders progress.

squid2 said:
It's not appropriate to post another version if it is just an uncredited copy of the original versions developed here. Do you have a link to the sources?
EDIT: I found the SuperR thread http://androidforums.com/threads/twrp-2-8-6-0-for-moto-e-2015-lte.920652/
He's released a new version since the first post here. He says that he fixed date/time in this recovery, so that would be the main visible difference compared to the recoveries we have here. He hasn't posted any sources for the device tree, which is a bit suspect, but could be okay if he made it from scratch (which may or may not be the case). Closed source development hinders progress.
Click to expand...
Click to collapse
I'm not going to argue with you about this, ok?? Just move on to another post cause I'm not disputing this with you any longer
Sent from my XT1526 using Tapatalk

I like Apple Pies.and the file link says 404 not found

squid2 said:
It's not appropriate to post another version if it is just an uncredited copy of the original versions developed here. Do you have a link to the sources?
EDIT: I found the SuperR thread http://androidforums.com/threads/twrp-2-8-6-0-for-moto-e-2015-lte.920652/
He's released a new version since the first post here. He says that he fixed date/time in this recovery, so that would be the main visible difference compared to the recoveries we have here. He hasn't posted any sources for the device tree, which is a bit suspect, but could be okay if he made it from scratch (which may or may not be the case). Closed source development hinders progress.
Click to expand...
Click to collapse
This is the best working TWRP that I have found for surnia. Thank you for the link.

Sleepycloud said:
This is the best working TWRP that I have found for surnia. Thank you for the link.
Click to expand...
Click to collapse
You're welcome @Sleepycloud
Sent from my XT1526 using Tapatalk

Hi,
You should update the FIrst Post of this thread with
- a good download link
- a link to the original thread
- fix the "Code" Tag which seems not well formatted
Thanks !

Shreps said:
Hi,
You should update the FIrst Post of this thread with
- a good download link
- a link to the original thread
- fix the "Code" Tag which seems not well formatted
Thanks !
Click to expand...
Click to collapse
I've tried doing all that, mods remove this thread since so many people wanna complain about sh**, I'm fu***** done with how people wanna criticize sh**, I try to help by contributing in whatever way I can and it seems like it's still not good enough for the crybabies on this board, I could care less about what happens to this post, please take it down so the crybaby whineasses will shut the hell up, GOD!!
Sent from my XT1526 using Tapatalk

Compatible with Moto E xt1524?
Inviato dal mio MotoE2(4G-LTE)

Hello
Please can upload the recovery to another server, in my country I can not download this.
thanks in advance
mfeliu07

bump for 2.8.7 - thanks to @SuperR.
https://www.androidfilehost.com/?w=files&flid=33085
http://androidforums.com/threads/twrp-2-8-7-0-for-moto-e-2015-lte.920652/
changelog: https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html

Small tip but relieving
Works!! Even if I use a newer version of TWRP, I recommend that when it is flashed, it does not restart, because it will not install correctly. It is best to directly enter the TWRP in the fastboot (after flashing it) and you will see an option to install it. Then they reboot the system from the TWRP options and that's it. Good luck (sorry but use the Google translator)
I used a surnia XT1527

Related

[RECOVERY] TWRP v2.6.3.0 for D605

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

[ROM] [5.1.1] Unofficial CarbonROM

New thread here - http://forum.xda-developers.com/oneplus-2/development/rom-carbonrom-t3305117
Hello everyone,
i finally compiled my first ROM from source. Since no official carbonROM was available for oneplus 2 so i tried compiling it myself and found out that oneplus 2 is officially supported by CarbonROM. Although i don't know why they haven't made any thread so far. Maybe waiting for all the bugs to be fixed. So i just wanted to compile and give it a try myself. If anyone else would like to give it a try as well then go ahead.
Download Links
Please make sure to check the Md5sum after downloading the file.
Google drive
My webserver -still uploading so check back after a while. will remove this warning once upload is complete. (update: looks like i am having some issues uploading the file. Will take more time then expected. So if anyone wants to create a mirror then please do and PM me so that i can mention the link here)
it has all the usual CM bugs and features like fingerprint, etc not working.
i have problem with my SIM
slo73 said:
i have problem with my SIM
Click to expand...
Click to collapse
Try activating and disabling airplane mode. Should fix the issue. Happened just once with me. Never after that. And since i don't use dual sim so can't comment on that.
Also reboot after that.
Sent from my ONE A2003 using Tapatalk
done, working good, tnx:good:
New thread here - http://forum.xda-developers.com/oneplus-2/development/rom-carbonrom-t3305117
Thread closed at OP's request.

[Recovery][G901F] Official Team Win Recovery Project for Galaxy S5 Plus (3.0.2-0)

Team Win Recovery Project 3.0.2-0
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxys5plus.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin to flash when possible.
You can find a zip containing Odin as well as a link to Samsung's Mobile drivers page here:
https://idlekernel.com/flash-tools/
CHANGES
v3.0.2-0 - See here for the changes.
v3.0.1-0 - See here for changes!
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
Backup & restore of modem/baseband/firmware (not bootloader!)
ADB root
Full SELinux support
Built in android 6.0 tree
KNOWN ISSUES
Samsung encryption is not supported
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree: https://github.com/TeamWin/android_device_samsung_kccat6 (android-6.0)
Kernel: https://github.com/jcadduono/nethunter_kernel_kccat6 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Galaxy S5 Plus, Tool/Utility for the Samsung Galaxy S 5
Contributors
jcadduono, the Team Win Recovery Project team
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-04-05
Created 2016-04-02
Last Updated 2016-07-11
I'm unsure why but this thread doesn't show up in the forums.
For me TWRP working perfect.
Thank you very much @jcadduono
jcadduono said:
You can find the device page here:
http://teamw.in/devices/samsunggalaxys5plus.html
Click to expand...
Click to collapse
404 - Page not found
jcadduono said:
Temporary: Please let me know if 3.1.0-0-test1 @ http://idlekernel.com/twrp/kccat6/testing is working for you!
Click to expand...
Click to collapse
Seems to be working well. Backup, Restore, Install from zip, Mount, Settings all worked flawlessly for me. Only concern: CPU temp rose to about 80C during backup, with a spike of 95C.
aelfinn said:
Seems to be working well. Backup, Restore, Install from zip, Mount, Settings all worked flawlessly for me. Only concern: CPU temp rose to about 80C during backup, with a spike of 95C.
Click to expand...
Click to collapse
did you actually feel the heat (that intense) or did it just say that on the screen?
its possible the temperate may be being misread
official build is up now
jcadduono said:
did you actually feel the heat (that intense) or did it just say that on the screen?
its possible the temperate may be being misread
official build is up now
Click to expand...
Click to collapse
it is felt, simply touch the screen to feel it. the display go haywire at that temperature. and the phone is very hot.
jcadduono said:
did you actually feel the heat (that intense) or did it just say that on the screen?
Click to expand...
Click to collapse
The phone got quite hot, but not worryingly so.
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
jcadduono said:
Team Win Recovery Project 3.0.1-0
Click to expand...
Click to collapse
The thread title still says “3.1.0-0”, btw.
aelfinn said:
The phone got quite hot, but not worryingly so.
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
The thread title still says “3.1.0-0”, btw.
Click to expand...
Click to collapse
fixed the version in title, the arial black thing is actually a bug with xda forums that they introduced a few days ago I think
I can't see our device in the device list of TWRP Manager. Is not all official builds available through the app?
I can't thank you enough for your hard work!
daeymon said:
I can't see our device in the device list of TWRP Manager. Is not all official builds available through the app?
Click to expand...
Click to collapse
Same here.
And I'm probably missing something, but .img files are not flashable through Odin...
Néocray said:
Same here.
And I'm probably missing something, but .img files are not flashable through Odin...
Click to expand...
Click to collapse
I got an answer on that separately. The app isn't actually officially supported by the TWRP team. The app maintaner has to add new models/builds to the list. Once I found out it was unofficial I just carried on using Flashify, which offers similar, except its list includes our device.
As for the img file thing, you are correct. You either need to convert it (which I did try, and didn't succeed at) or use something like Flashify to flash the img file.
My g901f is encrypted with TWRP 3 in recovery. I can't change kernel. Can't TWRP support encryption?
Sent from my SM-G901F using XDA-Developers mobile app
ok installed via flashify, thanks to the poster who posted this, twrp shame on them for not fixing their documentation.
Now the issue is its still buggy like theunofficial builds.
1 - brightness setting doesnt work
2 - vibrate doesnt work
3 - if dont touch screen for 5 seconds it then freezes for 30 seconds before responds again
4 - device reboots during backup
chrcol said:
official support already removed?
download links only have odin files so I grabbed the app, kccat6 isnt listed.
Click to expand...
Click to collapse
See the official TWRP page.
I managed to do backups now, so at least it functions now. Will keep this over philz since CM/philz is dead.
and yes I did read the offiical page, it has incorrect info, as it says to use the app which wont work, I used flashify. They need to edit that page to tell people to use flashify and warn some features dont work, thats all.
sorry guys, having trouble keeping track of all my threads. updated the thread and building tars soon.
chrcol said:
ok installed via flashify, thanks to the poster who posted this, twrp shame on them for not fixing their documentation.
Now the issue is its still buggy like theunofficial builds.
1 - brightness setting doesnt work
2 - vibrate doesnt work
3 - if dont touch screen for 5 seconds it then freezes for 30 seconds before responds again
4 - device reboots during backup
Click to expand...
Click to collapse
i don't own this device myself, if you have those issues then come to #twrp on freenode irc and we can work on making test builds to fix those issues.
the tester had told us that everything was working fine.
jcadduono said:
sorry guys, having trouble keeping track of all my threads. updated the thread and building tars soon.
i don't own this device myself, if you have those issues then come to #twrp on freenode irc and we can work on making test builds to fix those issues.
the tester had told us that everything was working fine.
Click to expand...
Click to collapse
OK will be there later this week but number 4 is OK now it is stable for backups now
Thanks
Sent from my SM-G901F using XDA Free mobile app
Can some folks please try this: https://idlekernel.com/twrp/kccat6/twrp-3.0.2-1-b4-kccat6.tar.md5
I've updated f2fs drivers, now using CPE1 kernel sources from Marshmallow.
I've added more partitions to EFS backup, and fixed any possible issues that might be happening during modem/firmware backups.
I also added CM13 hardware qcom encryption support.
And fixed the brightness adjustment hopefully...
Of course I still need someone to report back and let me know if these are actually *fixed*.
I'm still going in blind as it's not a device I own.
Here are the complete changes: https://github.com/jcadduono/androi...mmit/dc77b5ca4fde9148211515d7600776b1b27da1ca
Please also let me know if there are other issues I don't know about!

[ROM][N6][NRD90U] Useless Nougat

I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the source.
V4 Flashable ZIP: https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA
Obligatory screenshots: https://imgur.com/a/cXrnH
Working
As Shamu is a supported device, most things work well here:
Booting
Cellular (Calling, SMS and data)
Audio
Wi-Fi
Bluetooth
GApps (see below)
Easter egg
Not working (?)
Not working on Verizon, as reported here
There are probably more
GApps
This build has dm-verity enabled. With the stock kernel, GApps will not show up, or a warning is displayed when booting. To solve this, either use a custom kernel or use FED-Patcher.
After installing OpenGApps, you may encounter force closes during the Setup Wizard.
replica102 said:
You can just skip setup without editing the build.prop. Just tap on the four corners of the screen, starting from top left, clockwise. Do it right, and you'll get sent to home screen.
Click to expand...
Click to collapse
Afterwards, to get rid of the Play Services force closes, go to Settings > Apps > Three dot menu > Show system and find Google Play Services. Enter the Permissions menu and grant all the permission it needs.
If apps requiring WebView force close, try excluding "WebviewGoogle" using the gapps-config config file. Details are available here.
Sources
This build was compiled on a modified tree. See the changelog for details.
Vendor blobs are downloaded from https://developers.google.com/android/nexus/blobs-preview
Changelog
Code:
V4 - NRD90U - That's what I call "Useless"
Flashable ZIP: [url]https://mega.nz/#!qkpBHQwY!9fWIu36NCDtP4NXnTnWE_FblWlk9vrwNtDE13eJbocA[/url]
- Updated to 7.0.0_r6/NRD90U. So you want the shiny new build number? Here you go!
V3 - NRD90S
Flashable ZIP: [url]https://mega.nz/#!35Zl0QyY!gUYM79Fs_I6tm2RdEJw1v5S30qQqJ2RA1B3EosKlSqk[/url]
- Updated to 7.0.0_r4/NRD90S, with September's security updates.
V2 - NRD90M - A proper build... and more!
Flashable ZIP: [url]https://mega.nz/#!f4wSnTDL!3ifsV_qC_r-MJ-y45yDcwemkgTGY_jTr_OObHRktC-M[/url]
- The product name is now "Nexus 6" instead of the default "AOSP on Shamu". The modified device tree is available [URL="https://github.com/zhaofengli/device_moto_shamu"]here[/URL].
- The navigation bar editor is now accessible in System UI tuner. This is done by reverting [URL="https://android.googlesource.com/platform/frameworks/base/+/72195a011128d1c516149763c4c156539a470ed5"]this commit[/URL].
- I found out that I checked out the master branch for a handful of repositories when playing around. This is now fixed.
- This build was compiled with external/icu at [URL="https://android.googlesource.com/platform/external/icu/+/683055d9b50491dedbadea4e8ffb484e99e4f52b"]683055d[/URL] (the current master). This is to get RIL working.
- Developers: See [URL="http://forum.xda-developers.com/showpost.php?p=68556855&postcount=10"]this post[/URL] for a full explanation of the solution to get RIL working on 7.0.0_r1.
V1 - Initial build
Note: On a closer look, this is actually not a proper 7.0.0_r1 build. You should download V2 instead for a smoother experience.
Flashable ZIP: [url]https://mega.nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY[/url]
Mods: Please move this thread to the appropriate section if required.
Where did you get blobs from?
Kernel source?
Well done on being the first XD
neobuddy89 said:
Where did you get blobs from?
Kernel source?
Click to expand...
Click to collapse
Blobs are from https://developers.google.com/android/nexus/blobs-preview
And as said, I haven't changed the source in any way. Kernel source is available at https://android.googlesource.com/device/moto/shamu-kernel/+/android-7.0.0_r1
Edit: Wow, didn't look too closely. That's the prebuilt kernel, and the corresponding source hasn't been uploaded yet.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
The mega link don't work.
serch826 said:
The mega link don't work.
Click to expand...
Click to collapse
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Twiggy000b said:
Yes it does, you have to copy and paste but remove the <dot>
---------- Post added at 06:20 AM ---------- Previous post was at 06:11 AM ----------
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
I removed the <dot> but it doesn't work.
serch826 said:
Real question is, is this installed through factory recovery or can it be used through TWRP... Deff just tried TWRP and no success. will try flashing back to normal.
Click to expand...
Click to collapse
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
looks like mega is having server issues... i got it though
---------- Post added at 06:28 AM ---------- Previous post was at 06:25 AM ----------
Zhaofeng Li said:
Installing via TWRP will show a couple of warnings about the missing "log" function, but should still succeed nevertheless.
Click to expand...
Click to collapse
the log shown was simulating actions and then went to success. let me try again
Twiggy000b said:
looks like mega is having server issues... i got it though
Click to expand...
Click to collapse
Thanx mate!
cerico76 said:
I removed the <dot> but it doesn't work.
Click to expand...
Click to collapse
i retract my last response lol, you also gotta put a "." between mega and nz lol mega is alive!
Thanks, will download and try asap!
EDIT: i guess it will encrypt the device?
Zhaofeng Li said:
I just can't wait for Google to upload an official Nougat image for our beloved Shamu, so I compiled this from the 7.0.0_r1 source. I can't take any credit for it, as this is built using the built-in build target, and nothing more.
https://mega<dot>nz/#!K9YwGCJK!ezU_1dYTAOcCERletT-wK4demwI0-ZLRYiN4wrcXZLY
Mods: Please move this thread to the appropriate section if required. I don't have permission to post in the development sections yet.
Obligatory screenshots: https://imgur<dot>com/a/cXrnH
Edit: Added screenshot link
Click to expand...
Click to collapse
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Q9Nap said:
Just curious why you're calling it "useless"?
Have you tested it at all, and if so, what works and what doesn't work?
Iirc, at the very minimum, you need to symlink vendor to system to get cellular connectivity working.
*edit*
Here is more info regarding the need for symlinking:
https://groups.google.com/forum/#!topic/android-building/Lru4hX8JOnc
https://github.com/CyanogenMod/android_build/commit/47aaaa704a56f37889a8b54498fbb7daf9a6de30
https://github.com/CyanogenMod/andr...ff93604#diff-78ec901c9c29ef6a20b79592fd93f941
Click to expand...
Click to collapse
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Noob Question:
Where can I get the GApps file for this build?
Thanks!
edwaine said:
Noob Question:
Where can I get the GApps file for this build?
Thanks!
Click to expand...
Click to collapse
Use open gapps
Sent from my Nexus 6 using Tapatalk
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
In twrp I wiped everything except internal storage. flasked. still have my files. So, no it does not force encrypt. Your welcome.
Zhaofeng Li said:
Thank you. Cellular connectivity is working, and the vendor blobs are present in the build. The exclamation mark on the screenshots are due to Google servers being blocked in China (which you can fix by changing the captive_portal_server global setting, in case if you are in the affected regions).
The reason I call it "useless" is that Google will likely get the official images out very soon, and this build will quickly become obsolete.
I will update the original post to include the test results.
Click to expand...
Click to collapse
So.. this probably force encrypts device, right?
Droidphilev said:
Maybe my question got ovelooked because of an edited post but:
does the kernel force encrypt?
Thanks a lot!
Click to expand...
Click to collapse
harpin14789 said:
So.. this probably force encrypts device, right?
Click to expand...
Click to collapse
Flash this after flashing the rom zip and you don't have to worry about it:
http://forum.xda-developers.com/and...-fed-patcher-v8-forceencrypt-disable-t3234422

Review of CyanogenMod 13.0 for SM-J500*

Original ROM thread: https://forum.xda-developers.com/galaxy-j5/development/rom-6-0-1-cyanogenmod-13-0-samsung-t3454915
Keep up the great work.
Device: SM-J500F on 6.0.1
Status: Rooted, Debloated and BusyBoxed. No other modifications.
Country: India
Recovery: TWRP 3
Advantages of custom ROM-
Faster. Sleeker. And Smoother.
Really lag-free.
Multi-Window Mode
Startup takes little time, even the first one.
Internet speed increased considerably.
High storage space available due to small ROM
High RAM available
Button reconfiguring in Settings
Viper4Android, SU installed.
Additional appealing functions in settings.
Debloated.
MTP and other PC functions such as debugging worked fine.
Pre-installed useful features and apps.
However, I also noticed some of the below bugs and disadvantages.
Camera failed (as you said). I tried Google Camera, doesn't seem to work at all. Displays camera screen but closes showing "Unable to connect to camera."
Google Play Store is very fast but downloading never happens. (Solved - see 10 Jan 2017 Update)
First startup requires network connection from either SIM or WiFi.
Suggestions:
I think that replacing the two scripts (files) in the Camera folder in the zip flash file of the ROM with the stock one might have the camera working. I tried it myself but couldnot extract the files from the stock image. Trying.
Notification panel must be more customisable.
Mobile data enable in one click from notification panel. Like in stock Samsung.
Alternative option for enabling stock notification panel. (I just love the Samsung one. Very convenient.)
The rest are all fine.
So, why was this thread closed. I know "GPL Complaint". But is this site for discouraging custom modifications and creations?
Update - 10 Jan 2017
Solved: Google Play Store downloading. Just a temporary network glitch.
Bug (may have been mentioned before in earlier posts): Unable to switch to 3G only mode in either SIMs. Option shows selected but doesn't work actually and connects to 2G. 3G works if automatically detected.
KaushikMajumdar said:
So, why was this thread closed. I know "GPL Complaint". But is this site for discouraging custom modifications and creations?
Click to expand...
Click to collapse
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
#Henkate said:
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
Click to expand...
Click to collapse
I didn't open the thread to question the closing. You misunderstood me. I did it to review on the ROM and encourage the developer.
And yes, starting up discussion of developing Cyanogen mod 13 for J500* is a part of it.
KaushikMajumdar said:
I didn't open the thread to question the closing. You misunderstood me. I did it to review on the ROM and encourage the developer.
And yes, starting up discussion of developing Cyanogen mod 13 for J500* is a part of it.
Click to expand...
Click to collapse
All your gonna do by starting up this discussion again is cause an argument.
It ain't gonna lead any where.
The Dev responsible for this ROM ain't gonna start up this ROM again on XDA.
If finished his work, posted it on a different site and has moved on by finishing his work and changing phones to find a development community that appreciates his work.
Sent from my Honor 8 using XDA Labs
johnhux7 said:
All your gonna do by starting up this discussion again is cause an argument.
It ain't gonna lead any where.
The Dev responsible for this ROM ain't gonna start up this ROM again on XDA.
If finished his work, posted it on a different site and has moved on by finishing his work and changing phones to find a development community that appreciates his work.
Click to expand...
Click to collapse
Just a review. Don't think so further. It's not THAT serious.
KaushikMajumdar said:
Just a review. Don't think so further. It's not THAT serious.
Click to expand...
Click to collapse
That's the problem though mate it was that serious.
Read up on the old threads and you will see the history of it all.
Bad times
Sent from my Honor 8 using XDA Labs
johnhux7 said:
That's the problem though mate it was that serious.
Read up on the old threads and you will see the history of it all.
Bad times
Click to expand...
Click to collapse
CyanogenMod 13 for J5 can be rebuilt without the violations over again.
KaushikMajumdar said:
CyanogenMod 13 for J5 can be rebuilt without the violations over again.
Click to expand...
Click to collapse
Cool, good luck. R u the man for the job ?
I thought that nick and co where building CM13 ?
The one that Zonik build has been finished a while back.
It's available in FB
Sent from my Honor 8 using XDA Labs
johnhux7 said:
Cool, good luck. R u the man for the job ?
I thought that nick and co where building CM13 ?
The one that Zonik build has been finished a while back.
It's available in FB
Click to expand...
Click to collapse
Well, if it is so then could you please forward me the link to the Facebook page.
And is the Zonik Build for J500F on 6.0.1?
KaushikMajumdar said:
Well, if it is so then could you please forward me the link to the Facebook page.
And is the Zonik Build for J500F on 6.0.1?
Click to expand...
Click to collapse
PM me
Deleted
Sent from my Honor 8 using XDA Labs
The thread is still open for your suggestions XDA Community. I am awaiting for response.
Deleted
Let me remind everyone here that providing links to non GPL compliant development, via PM or otherwise on XDA, is against the rules.
The Merovingian said:
Let me remind everyone here that providing links to non GPL compliant development, via PM or otherwise on XDA, is against the rules.
Click to expand...
Click to collapse
I am sorry if posting this was a violation. As you see I am a new member. I am not giving an excuse but the purpose of this thread was to start further development of CyanogenMod ROM for J5 and not continuation of the original non-GPL complaint ROM. It was just an cited example to illustrate the ROM type.
If I knew how to make a kernel (and had the correct resources) I would happily continue where zonik left and why don't you warn before performing what you did, aren't humans error prone?
#Henkate said:
If you know why it was closed, why do you ask?
XDA has rules like any other forum. You must obey the rules. If you're not obeying them, then it's your fault.
Simple as that.
I don't know why you made this thread, because it won't change anything. Actually, it will just start discussions again.
Click to expand...
Click to collapse
1. DJ_Steve's kernel IS GPL complaint
2. Now the developers that are banned from XDA made a aroma TWRP AND stable cyanogenmod 13
3. (for mods) unban them
Telepracity said:
1. DJ_Steve's kernel IS GPL complaint
2. Now the developers that are banned from XDA made a aroma TWRP AND stable cyanogenmod 13
3. (for mods) unban them
Click to expand...
Click to collapse
1. https://forum.xda-developers.com/showpost.php?p=69643216&postcount=217 .
2. I will try AROMA TWRP in future too.
3. Read rules.
4. Dont reply to this post.
#Henkate said:
1. https://forum.xda-developers.com/showpost.php?p=69643216&postcount=217 .
2. I will try AROMA TWRP in future too.
3. Read rules.
4. Dont reply to this post.
Click to expand...
Click to collapse
1. Why does skiesrom use that kernel and has not been taken down?
2.Nice
3.No need, I already read them
4.Sorry, I had to. I need to clean the forums
1. I'm always watching.
2. See #1.
The Merovingian said:
1. I'm always watching.
2. See #1.
Click to expand...
Click to collapse
1. I know.
2. I know.
o sh*t this is going offtopic xDxdD

Categories

Resources