[WIP][TWRP] porting for Galaxy Ace 4 Neo SM-G316ML - Samsung Galaxy Ace 4

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm attempting to port TWRP to the Samsung Galaxy Ace 4 Neo SM-G316ML (vivalto3mve3gltn) device. As of now I've got successful builds, but non-functional images (they brick the device).
The (experimental) device tree is hosted here, and is configured to build TWRP as its recovery (my plan is to also use it to build LOS 14.1, but after building TWRP).
I'm somewhat new to the Android devel. However, I've learned a lot, I'm familiarized with the AOSP/LOS source code, I use GNU/Linux as my main OS since some years ago and my skills are good enough to deal with this. The only problem is that, as this is my first time in porting a recovery to an unsupported device, I'd like some help. Anyone with knowledge and willing to help me in this project is welcome, just leave a comment so we can discuss how to manage this, like the access to the repository or pull requests, etc.
For the more-technical discussion about the porting, please do in this issue from the repository.
XDA:DevDB Information
SM-G316ML unofficial TWRP port, TWRP for the Samsung Galaxy Ace 4 Neo
Version Information
Status: Testing
Device Information
Device Name: Samsung Galaxy Ace 4 Neo
Device Model: SM-G316ML
Device Chipset: SC8830
Created 2018-06-18
Last Updated 2018-06-18

No working image yet? i'm going crazy triyng to root this phone

uanesgtgt2 said:
No working image yet? i'm going crazy triyng to root this phone
Click to expand...
Click to collapse
Not so desperate now. Made a working image of TWRP for this device, and rooted with magisk. thanks anyways!

uanesgtgt2 said:
Not so desperate now. Made a working image of TWRP for this device, and rooted with magisk. thanks anyways!
Click to expand...
Click to collapse
Can you send me the twrp img so i can flah my ace 4 neo?

Related

[Development state][Needs another Dev]TWRP for Duos Variant N7502

Hi all, this thread is only for the sole purpose of porting TWRP on the duos variant n7502
I've seeked help for a month now and found a dev to make one, however, I think he's given up on the project but published the tree to github.
The project was first meant to port CWM but we had problems we cant solve so we shifted to TWRP, the first problem's gone but another two came.
Here's the github link:
https://github.com/OUDhs/android_device_samsung_hl3gds
Here's a log for the TWRP:
http://d-h.st/9yq
and Here's a screenshot of the TWRP:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
additional info:
The TWRP boots up but the screen is messed up (as shown on the screenshot); Touchscreen works fine, I can navigate through the recovery but since the screen is messed up, I have no clue as to where I was going. The first problem we had was we can't mount any partition. Shifting to TWRP solved that but the /cache still can't be mounted.
We badly need a dev. Hope someone takes over.​
annson08 said:
Hi all, this thread is only for the sole purpose of porting TWRP on the duos variant n7502
I've seeked help for a month now and found a dev to make one, however, I think he's given up on the project but published the tree to github.
The project was first meant to port CWM but we had problems we cant solve so we shifted to TWRP, the first problem's gone but another two came.
Here's the github link:
https://github.com/OUDhs/android_device_samsung_hl3gds
Here's a log for the TWRP:
http://d-h.st/9yq
and Here's a screenshot of the TWRP:
additional info:
The TWRP boots up but the screen is messed up (as shown on the screenshot); Touchscreen works fine, I can navigate through the recovery but since the screen is messed up, I have no clue as to where I was going. The first problem we had was we can't mount any partition. Shifting to TWRP solved that but the /cache still can't be mounted.
We badly need a dev. Hope someone takes over.​
Click to expand...
Click to collapse
i could help to test any builds but if any developer can help us through that ... please anyone take this device into consideration its great
Please (((
Recovery neo help...

Asus Fonepad 7 FE170CG development

Hello Friends, today I am giving some stuffs of Asus Fonepad 7 FE170CG for devs which might be useful for them to unlock, create custom recoveries and ROMs. I hope some day this device would have a custom ROM and recoveries.
Boot.img extracted - Lollipop: here
Droidboot.img extracted - Lollipop: here
Kernel extracted from Boot.img: here
Partition details
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stock recovery.img - To be flashed only if you're in Lollipop: here
Stock Boot.img: here
Recovery.fstab: here
Build.prop from stock lollipop ROM: here
KitKat kernel source: here
Lollipop kernel source: here
Stock ROM(unstable) - Lollipop - version=WW-12.8.1.26 : here
Asus has pulled this firmware since it was buggy
Stock ROM - KitKat - Version=WW_V11.2.3.33 : here
Please note that all these are for development puposes only and applies to Asus Fonepad 7 FE170CG!!! Never use for daily life...
Don't post this else where, respect my work!
Hit thanks if i helped you...
hi....did you know how to unpack boot.img from intel device....?
in my last device, qualcomm device, i use android image kitchen....
but it not working on my k012....
(sorry for my bad english)
yudh4.php said:
hi....did you know how to unpack boot.img from intel device....?
in my last device, qualcomm device, i use android image kitchen....
but it not working on my k012....
(sorry for my bad english)
Click to expand...
Click to collapse
Sorry for late reply! Yeah, our device is NOT supported by Android kitchen at all. And the Fonepad images are recognized as "Intel x86 bootsector" So, we have to do the official way. The tools for unpacking and working with Intel Android images are located here. But this is an entire Android AOSP source of Intel x86 devices with the size of awesome 23GB. You need Linux PC with this source code to get it working... We need a real hardcore Dev to work with this device!
You can also get more details from the PDF attached below.
Is there any custum recovery for FE170cg?
siamak5561 said:
Is there any custum recovery for FE170cg?
Click to expand...
Click to collapse
a temporary recovery is available
check this thread https://forum.xda-developers.com/fonepad-7/general/discussion-asus-fonepad-7-me175cg-t3145725

[KeralaRomJ7][Lineage OS 15][J700F][Exynos][2018]

Dec 1 2017
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am looking to bring Lineage OS for our beloved j7 15 exynos model.The thread will be updated about ongoing progress.Currently looking for the possibility for a base Rom.
Thanks in Advance.Good advise will be appreciated.
ഞാൻ എന്റെ പ്രിയപ്പെട്ട j7 15 exynos മോഡലിനായി Lineage OS കൊണ്ടുവരികയാണ്. തുടക്കം പുരോഗമിക്കുന്നതിനെ കുറിച്ച് Thread അപ്ഡേറ്റ് ചെയ്യും. ഇപ്പോൾ നിലവിലുള്ള അടിസ്ഥാന റോം സാധ്യതയെക്കുറിച്ച് അന്വേഷിക്കും.
അഡ്വാൻസ് നന്ദി. നല്ല ഉപദേശങ്ങൾ അഭിനന്ദിക്കപ്പെടും.
Reserved
Reserved2
Yessssss
niceeeee
I dont know if you can do that checking your experience based on your thread history
Lots of people waiting almost stable aosp rom...Good luck
?
If you need J700H tester please dm me!
it would be nice if it were not an error
Yes
Yes
The cm based ROMs for our j715 have problems of lagging and camera .
If these could be solved than we would have stable AOSP rom
@SduosGt7562 A3 2016 aosp dev booted oreo Nexus Os. As it have same Soc of our J7 15. Will recommend u to talk to him or join us on our telegram community.
SduosGt7562 said:
Dec 1 2017
I am looking to bring Lineage OS for our beloved j7 15 exynos model.The thread will be updated about ongoing progress.Currently looking for the possibility for a base Rom.
Thanks in Advance.Good advise will be appreciated.
ഞാൻ എന്റെ പ്രിയപ്പെട്ട j7 15 exynos മോഡലിനായി Lineage OS കൊണ്ടുവരികയാണ്. തുടക്കം പുരോഗമിക്കുന്നതിനെ കുറിച്ച് Thread അപ്ഡേറ്റ് ചെയ്യും. ഇപ്പോൾ നിലവിലുള്ള അടിസ്ഥാന റോം സാധ്യതയെക്കുറിച്ച് അന്വേഷിക്കും.
അഡ്വാൻസ് നന്ദി. നല്ല ഉപദേശങ്ങൾ അഭിനന്ദിക്കപ്പെടും.
Click to expand...
Click to collapse
PlaceHolder threads are not allowed thus this thread is closed.....Please PM me when you have valid DL links and we can reopen this thread then....This looks as to be a great addition to the J7 family......

[TWRP][OFFICIAL][NICKLAUS] TeamWin Recovery For Moto E4+

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.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
DOWNLOADS
NICKLAUS
HOW TO FLASH IT??​
Code:
- Reboot into bootloader
- Plug your phone
- run the command "fastboot flash recovery file_name.img"
- Boot into twrp :)
Contributors:
SamarV-121
Version Information
Status: Stable
Created: 2018-10-29
Last Updated: 2018-10-29
partner does not install the twrp says it is very long the file marks error
jason2781 said:
partner does not install the twrp says it is very long the file marks error
Click to expand...
Click to collapse
Use the file before latest one
yes that I use, I wanted to install that new one to see if this was the beginning of the update of lineageOs 15.0 android 8, because it tries with the previous twrp and it does not happen of the blue screen, I hope soon it finds an update to install android 8 and this time if start Thank you!
Hello,
I have a new moto E4 plus XT1773 variant with android 7.1.1 security patch from august 2018 and i am a bit confused with all these post about you need a special TWRP for your variant. My question is, will twrp-3.2.3-1-nicklaus.img work for my device?
I understand, the first step i need to do is unlock the bootloader and then flash the twrp-3.2.3-1-nicklaus.img file right? i won't need the no-verity-opt-encrypt.zip or a patched boot image in order to a successful install?
I am trying to do all these things just to root it. Kinda difficult! i guess... I'd wish kingroot work!
Thanks in advance!
Regards.

Question When time coming lineageos based custom roms?

hi everybody, i want flashing lineageos based custom roms.
twrp recovery is currently available, but unfortunately, a stock android based or lineageos based, custom android roms has not been released. I can't support development because I don't know coding or have no command of these issues. Can you add a list of custom roms under this topic? Thanks everyone
There seems not much, you can limit this device thread to "Development":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are just two, one ROM, one recovery...
systmrrr said:
I can't support development because I don't know coding
Click to expand...
Click to collapse
Excuse my wise words but then perhaps it would have been better to look first what's available (as in custom ROMs) and then buy accordingly.
Sounds tedious but I always crosscheck my buys beforehand with
https://wiki.lineageos.org/devices/
That usually saves you from rare and unsupported/unsupportable devices (like those based on Mediatek SOCs).
Developers will prepare custom roms when source codes are released by manufacturer xiaomi
sedat2934 said:
Developers will prepare custom roms when source codes are released by manufacturer xiaomi
Click to expand...
Click to collapse
Is that right? I thought, they cannot prepare customs before code is released by manufacturer... slight but noteworthy difference, right?
SigmundDroid said:
Is that right? I thought, they cannot prepare customs before code is released by manufacturer... slight but noteworthy difference, right?
Click to expand...
Click to collapse
Custom roms cannot be prepared without releasing the source code. I am impatiently waiting for the day when I will upload custom rom. When will the source code be released?
Poco F4 GT kernel source · Issue #4044 · MiCode/Xiaomi_Kernel_OpenSource
Please open the source code for Poco F4 GT kernel. We need it!
github.com

Categories

Resources