Database Develop

[RECOVERY] TWRP 3.3.0 for Galaxy M20

Team Win Recovery Project​
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Disclaimer:
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be reset in any way, so think twice before flashing this.
- Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me.
Installation:
- First, make sure your phone isn't RMM Locked.
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip, latest Magisk.zip and RMM Bypass zip by Black Mesa, and copy all of them to your external sd card.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Connect your phone to your PC, press and hold Power, Vol + and Vol - buttons together )
- Open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now flash the no-verity-opt-encrypt, Magisk(necessary to prevent bootloops) and RMM Bypass zip you downloaded before (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition and without RMM Prenormal lock.
Download:
TWRP
Sources:
Soon
Changelog:
Check Post #2.
Telegram Group:
Join the Telegram Chat group for Galaxy M series: https://t.me/GalaxyMSeries
Credits:
- Samsung Open Source Centre for kernel source code
- TeamWin for their awesome recovery
XDA:DevDB Information
TWRP for Galaxy M20, Tool/Utility for the Samsung Galaxy M20
Contributors
DarkLord1731
Version Information
Status: Stable
Stable Release Date: 2019-05-08
Created 2019-03-03
Last Updated 2019-05-08

Changelog:
8/05/19
Fixed internal storage corrupt error
Updated and improved support for treble
28/04/19
Updated to TWRP 3.3.0 (Read about the changes here)
Fixed MTP
Added proper support for treble
3/03/19
Initial Releasease

Reserved

GG

Great to see development kick starting early. Hope that Custom Roms too also will be available soon.

Will this recovery work on M30? They have same processor.

kushal.purkar said:
Will this recovery work on M30? They have same processor.
Click to expand...
Click to collapse
No a seperate recovery will be needed for M30. If you're interested in testing then PM me.

Anyone tried out this recovery and hoping to test a build for fixing MTP then PM me.

GG boii @DarkLord1731

prashantp01 said:
GG boii @DarkLord1731
Click to expand...
Click to collapse
Sur gib aosp for m20

Harvey_Spectar said:
Sur gib aosp for m20
Click to expand...
Click to collapse
Sand volte and wifi calling fix ?

prashantp01 said:
Sand volte and wifi calling fix ?
Click to expand...
Click to collapse
Gib test build first

Harvey_Spectar said:
Gib test build first
Click to expand...
Click to collapse
NoU sand fix first?

prashantp01 said:
NoU sand fix first?
Click to expand...
Click to collapse
Forget it then.... Let m20 die then

DarkLord1731 said:
3/03/19
Initial Releasease
Click to expand...
Click to collapse
How to Enter Download Mode?

harsinghal said:
How to Enter Download Mode?
Click to expand...
Click to collapse
Read the OP

DarkLord1731 said:
Read the OP
Click to expand...
Click to collapse
Alright done all the steps and TWRP Works. Thanks.
But sad part is i'm stuck on Bootloop now.

harsinghal said:
Alright done all the steps and TWRP Works. Thanks.
But sad part is i'm stuck on Bootloop now.
Click to expand...
Click to collapse
You probably missed to install the no-verity-opt-encrypt.zip which should remove dm-verity and prevent bootloop. Follow the instructions correctly.

Inquiry
Hi can I flash this on my Samsung galaxy M20 (SM-M205G). Thanks. and if there is available root already for this device?

Anyone try flashing magisk on this phone? Which version should i use?

[ROM][9][OneUI] Korea's rom for A5|7 2017

[ROM][9][OneUI] Korea's rom for A5|7 2017
As you probably know by now a Korean variant of A7 2017 has recently received firmware update to android 9 and OneUI. I made it working on my international variant and cleaned it up, so I'm sharing with the community.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
{
"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"
}
​
ROM Info & Features
Based on A720SKSU5CUJ2
Kernel built from A720S sources
Enforced SELinux policy
Removed forceencrypt and verity
Disabled OEM Unlock toggle
Prepatched KG. See here
Ported features
Added support for A5 2017, too
Added dual sim functionality
Fixed secure folder
Debranded and debloated
Removed unnecessary preinstalled apps
Removed Korean region-related apps and services
Removed SKT bootanimation
Supported devices
SM-A720F
SM-A720S
SM-A520F
SM-A520W
SM-A520S/K/L
Bugs
Korean base doesn't have full support for all countries (some languages, local features missing etc.).
No FMRadio.
Second sim slot only works for calls/text.
Installation Steps
Make sure you had Samsung's Oreo firmware bootloader and modem before installing this
Download the rom
Download koreanaddons.zip (optional)
In TWRP format data (if you still have stock rom encryption)
In TWRP wipe system/data/cache
Flash the rom
Flash koreanaddons.zip (optional)
Reboot
Download
ROM: MEGA | androidfilehost || koreanaddons
Donations
If you find the work I do helpful, you can support me by donating via this link.
Changelog
27012022
Revert "Enforced SELinux policy"
Revert "The rom now passes SafetyNet naturally"
06112021
Rebased on A720SKSU5CUJ2
Updated the kernel drop from A720SKSU5CUJ2
Enforced SELinux policy
The rom now passes SafetyNet naturally
04032021
Rebased on A720SKSU5CTL2
Updated the kernel drop from A720SKSU5CTL2
Slight a5y17lte-only firmware changes
14072020
Rebased on A720SKSU4CTF2
Further debloated - removed unnecessary preinstalled apps
Enabled more csc options by default by @George35000vr
06032020
Fixed screen mirroring
Stopped forcing dual-sim prop for all devices
12122019
Added support for dual sim
Fixed secure folder
Permissive sepolicy
08122019
Added support for A5 2017
Kernel built from source
Fixed settings bug with superfluous options
Rebased on A720SKSU4CSK2
28092019
Initial build
A720SKSU3CSH1
Telegram:
There's a telegram group made by A5|7 users where they hang out. Feel free to check it out.
Special thanks to:
corsicanu
de_inferno
khongloi113
dvdhngs
yash92duster
SuperR
George35000vr
Joe
SGTPresticle
XDA:DevDB Information
[ROM][9][OneUI] Korea's rom for A5|7 2017, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
Option58
Source Code: https://github.com/universal7880/android_kernel_samsung_universal7880
ROM OS Version: 9.0 Pie
ROM Kernel: Linux 3.18.91
ROM Firmware Required: Samsung oreo bootloader and modem
Version Information
Status: Stable
Created 2019-09-27
Last Updated 2021-11-06

Reserved
FAQ
Is it possible to flash stock oreo firmware after using this rom?
Yes, of course. Flashing this rom doesn't update your bootloader.
I have A5 2017, but battery capacity shows 3600mAh.
You can ignore this. That's only in about phone. The kernel knows your true battery capacity.
How to add csc codes
Korean base doesn't support multi-csc. But we can still unlock region-related features by using special codes. I won't post them here, you should search around xda for the specific one that you need.
For example here I will be adding network speed indicator in the status bar. The code for this is:
Code:
<CscFeature_Setting_SupportRealTimeNetworkSpeed>TRUE</CscFeature_Setting_SupportRealTimeNetworkSpeed>
But you can add something else, too.
You'll need a PC. Steps to take are:
Download THIS zip to your PC.
Extract the zip.
Open system/csc/others.xml with Notepad.
It looks like this:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<SamsungMobileFeature>
<FeatureSet>
<CscFeature_Setting_ConfigOpMenuStructure>GLOBAL</CscFeature_Setting_ConfigOpMenuStructure>
</FeatureSet>
</SamsungMobileFeature>
Add your code like below:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<SamsungMobileFeature>
<FeatureSet>
<CscFeature_Setting_ConfigOpMenuStructure>GLOBAL</CscFeature_Setting_ConfigOpMenuStructure>
[COLOR="Red"]<CscFeature_Setting_SupportRealTimeNetworkSpeed>TRUE</CscFeature_Setting_SupportRealTimeNetworkSpeed>[/COLOR]
</FeatureSet>
</SamsungMobileFeature>
Code:
Repack the zip.
Copy to your phone and flash.
Now when you go to settings -> status bar you should see the network speed indicator toggle appear. Or any other change that you added.

Nice bro,.. im waiting long for this

???

Thank you for sharing Option58.
Any chance of someone adding support for A520F?

Is it supports multi CSC?

Boozika said:
Thank you for sharing Option58.
Any chance of someone adding support for A520F?
Click to expand...
Click to collapse
It could come someday.

It can't flash. TWRP says format() expects 5 args, got 6
updater process endedwith error: 7 what should i do?

Ethelwulf said:
It can't flash. TWRP says format() expects 5 args, got 6
updater process endedwith error: 7 what should i do?
Click to expand...
Click to collapse
Do you have latest TWRP?

Ethelwulf said:
It can't flash. TWRP says format() expects 5 args, got 6
updater process endedwith error: 7 what should i do?
Click to expand...
Click to collapse
Oh, derp. Tomorrow I'll be replacing the build to fix that.

Boozika said:
Thank you for sharing Option58.
Any chance of someone adding support for A520F?
Click to expand...
Click to collapse
I hope it will be possible

I waiting for a520f

Yes
Simon1511 said:
Do you have latest TWRP?
Click to expand...
Click to collapse
Yes I have flashed latest twrp 3.3.1.1 but still having this It seems I should try redownload

Option58 said:
Oh, derp. Tomorrow I'll be replacing the build to fix that.
Click to expand...
Click to collapse
I got too,.. can't flash it
---------- Post added at 06:27 AM ---------- Previous post was at 06:12 AM ----------
It Doesnt work

Guys. Still can't flash?

Ethelwulf said:
Guys. Still can't flash?
Click to expand...
Click to collapse
Yes

Alright i will use hadesrom until that fixes

Option58 said:
Oh, derp. Tomorrow I'll be replacing the build to fix that.
Click to expand...
Click to collapse
done.
Sorry. Those of you who already downloaded should re-download.

Option58 said:
done.
Click to expand...
Click to collapse
Working now??

I flashed the rom. Its okay but there is a problem in settings. They're not in "Connections" section.

[RECOVERY][UNOFFICIAL][RMX2170][v3.0.0] Pitch Black Recovery [10/12/20]

{
"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"
}
Code:
/*
*Disclaimer
*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Introduction
Pitch Black Recovery is a fork of TWRP with many improvements to make your experience better. It's more flexible & easy to use.
Based on TWRP version: 3.4.0
PitchBlack version: 3.0.0
For device: RMX2170 aka Realme 7 Pro
Maintainer/Authors build: @TheMalachite
PitchBlack Source Code: https://github.com/PitchBlackRecoveryProject
Device tree: https://github.com/DragonBigClaws/pbrp_realme_RMX2170
Kernel: https://github.com/DragonBigClaws/pbrp_realme_RMX2170/tree/android-10.0/prebuilt
PitchBlack Team: @rezaadi0105, @shovon, @manjot.gni, @androiabledroid, sagar
Features
Fully native android like UI
Supports Treble and non-Treble ROMs
Up-to-date kernel, built from sources
Full dark theme with changeable accents
Reorganized menus
MIUI OTA support
Disable DM Verity
Use AromaFM as default file manager
Various tools are include
Universal flash-able file for all variant of a device
Many bug fixes & optimization & much more
Click to expand...
Click to collapse
Installation Instructions
Download the PitchBlack recovery img on your PC
Reboot your phone to bootloader (adb reboot bootloader)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery recovery.img
Reboot to recovery
Enjoy
Changelog
PBRP Side Changelog
Code:
v3.0.0
- Fully Redesigned UI
- Added new Keychecks While Flashing PBRP or recovery.img or Ramdisk
- Fully Redesigned Website https://pitchblackrecovery.com
- New Android like Power Menu (Activated via power key hold)
- Flashlight toggled by Vol up(+) on hold
- New Scrollable Advanced menu
- Totally Redesigned Icons
- Removed old unnecessary Theming Stuff
- Tested on almost all handy Resolutions
- Flashlight toggle on Lockscreen
- More checks for SAR/Non-SAR\
- New Navbar
- Support on almost all Android version (5.0+)
- Update ozip decrypt
- Fix up ozip print logs & take all paths
- Update FUNDING.yml
- Fixed encrypted removal checks & buttons
- Add Flag for disabling treble compatibility by default
- Is_Data_Wiped: Simplify function signature
- Unified AB_OTA_UPDATER
- Change AB device log storage to /data/recovery
- Delay start if specified in board
- Optimize touchscreen driver initialization delay.
v2.9.0
- Update kernel
- Update DM Verity Logic
- Update magisk
- Update unroot magisk
- Some bug fixed
Device Side Changelog
Code:
10/12/20
- Initial build
13/01/21
- Fix ozip flashing
Bugs
- You tell me!
Downloads
VBMeta img
PBRP recovery img (13/01/21 Build)

Reserved #1

Reserved #2

Have you tested the recovery on a real phone? all sections are visible for MAIN MENU-BACKUP?

Does system file encryption work fine with this recovery?

Lark5 said:
Have you tested the recovery on a real phone? all sections are visible for MAIN MENU-BACKUP?
Click to expand...
Click to collapse
Yes it's tested on an actual realme 7 pro

can it just boot temporary via fastboot, to install magisk, without flashing twrp and vbmeta?

harmonia3 said:
can it just boot temporary via fastboot, to install magisk, without flashing twrp and vbmeta?
Click to expand...
Click to collapse
You need to disable vbmeta for installing magisk anyway so no, you can't

TheMalachite said:
You need to disable vbmeta for installing magisk anyway so no, you can't
Click to expand...
Click to collapse
And how do I do when my Bootloader still not be being unlock as I'm still searching for the in-depth apk for me realme 7 pro. TKS.

eeeemc said:
And how do I do when my Bootloader still not be being unlock as I'm still searching for the in-depth apk for me realme 7 pro. TKS.
Click to expand...
Click to collapse
Check this {Mod edit: Link removed}
Work fine on India and Russia variant, idk about other

TheMalachite said:
Check this {Mod edit: Link removed}
Work fine on India and Russia variant, idk about other
Click to expand...
Click to collapse
Thankssss
Should worst things happen, where I can find desktop application (like odin for Samsung) to flash original ROM to unbrick the phone?
edmond

YAMEROOO WRYYYYYYYYYYYY!!!

Haven't found a TWRP for Realme 7 Pro. Any alternatives?

Djikstra said:
Haven't found a TWRP for Realme 7 Pro. Any alternatives?
Click to expand...
Click to collapse
Why you need twrp?

Zgadnijcie said:
Why you need twrp?
Click to expand...
Click to collapse
I wanted to delete bloatwares and keep a backup in case I **** up with any system apps.

Djikstra said:
I wanted to delete bloatwares and keep a backup in case I **** up with any system apps.
Click to expand...
Click to collapse
Can't you just use PBRP for the same thing ?

TheMalachite said:
Can't you just use PBRP for the same thing ?
Click to expand...
Click to collapse
I didn't know PBRP lets me backup. How do you backup with PBRP?

PBRP = TWRP from other developers

TheMalachite said:
Check this {Mod edit: Link removed}
Work fine on India and Russia variant, idk about other
Click to expand...
Click to collapse
Thanks and finally unlock bootloader following your hints.
However, what is the easiest way and safe way to ROOT the India version RM 7 PRO with latest build v.23?
I understand little adb fastboot flash command as I ROOT xiaomi myself.
Couldn't see YouTube about rooting so I'm timid to start.
I still love the phone as it's build quality, the stereo speaker, stronger WiFi signal....etc.
Thank you very much.
edmond

Its working very good on realme 7 pro , just encryption not working

[RECOVERY] TWRP 3.7.0-9.0 for Samsung Galaxy J3 2016 [SM-J320FN/F/G/M/H] [UNOFFICIAL]

{
"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"
}
An essential tool for anybody that loves to modify their Android device is a good custom recovery. TWRP has been around since the invention of the wheel back in 1996 and has been providing modders with all kinds of great tools.
Okay so..I managed to compile TWRP 3.6.1-9.0 finally for this device. I started with stock recovery kernel which obviously didn't work due to the "unsupport". So after a month, I tried @djeman's TWRP 3.2 OREO kernel which worked, maybe it had a feature which booted it up. But Android Oreo will never work on our device. Thanks to @NMTdontknow who tested my TWRP ​
Code:
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this RECOVERY
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
IMPORTANT!!!!!!!!!
If you have SM-J320FN/F/G/M, flash the J3XLTE twrp image!
If you have SM-J320H, flash the J3X3G twrp image!
Installation instructions
Spoiler
Turn off your phone
Restart it in download mode by keeping volume down + home + power
Confirm the entry in the download mode with volume up
Plug your phone into your PC and run Odin (you should see the COM port in blue)
Click on AP and select the .tar recovery file
Click on options (Disable checkbox Auto Reboot) and leave only "F. Reset Time"
Click Start
(Your device will not restart automatically this is voluntary because otherwise the original rom will erase TWRP.)
To restart it keep down volume down + home + power as soon as it goes off restart it on recovery by keeping it up volume up + home + power
When you boot for the first time on recovery, it will prompt you to change the language and avoid deleting the recovery.
Note: For this device it is necessary to have enabled OEM Unlock in:
Settings -> Developer Options -> OEM unlocking
Or you may encounter "BLOCKED BY FRP LOCK" on boot.
Known issues:
Spoiler
MTP (SM-J320H)
CPU temperature doesn't show up (SM-J320H)
Download:
Spoiler
Below attachments!
Credits:
Spoiler
@NMTdontknow for testing the TWRP
@djeman for the Oreo kernel and the work for this device
4PDA user Mr.Precise for testing my TWRP builds for SM-J320H
Me for making TWRP
TeamWin
OmniROM
LineageOS
Device-specific tree:
Spoiler
SM-J320FN/F/G/M: https://github.com/NotNoelChannel/twrp_device_samsung_j3xnlte
SM-J320H:
Spoiler
https://github.com/unlegacy-devices/android_device_samsung_j3x3g

Hi,
It's not really oreo that don't works on the j3 but I never found a compatible gpu driver ...
Android have modified deeply the gpu driver interface on oreo and the driver is not open source.
So I abandonned but all the boot sequence was good only this driver was missing.
Thanks for the new recovery

djeman said:
Hi,
It's not really oreo that don't works on the j3 but I never found a compatible gpu driver ...
Android have modified deeply the gpu driver interface on oreo and the driver is not open source.
So I abandonned but all the boot sequence was good only this driver was missing.
Thanks for the new recovery
Click to expand...
Click to collapse
Hey djeman, I didn't except that you are going to comment here lol!
You're welcome for the recovery! I might try to bringup other recoveries like PBRP(Pitch Black Recovery Project) and OFRP(OrangeFox Recovery Project)

I can confirm that it works. The touch is simulating a mouse however, I think. The click action is weird. But usable.
Also, both recovery images work just fine on my device, I actually do not know which of the 2 variants my phone is. I think they are pretty much the same so you can just offer one recovery for both. If the device has the nfc chip soldered on or not should not matter for the recovery.

L3P3 said:
The touch is simulating a mouse however, I think. The click action is weird. But usable.
Click to expand...
Click to collapse
Yip, this is an issue because this device tree "has been ported" from j3lte (Snapdragon variant of the J3 2016) . I guess that's why the click action is weird

notnoelchannel said:
Yip, this is an issue because this device tree "has been ported" from j3lte (Snapdragon variant of the J3 2016) . I guess that's why the click action is weird
Click to expand...
Click to collapse
Already did figure out why it is lagging. Making test builds to make sure the click isn't weird anymore

Fantastic! I will enjoy it in 10 years then when some retro computing geek finally creates a new rom for it.

New update!
Status: built-from-source
Updates:
- Sync latest TWRP sources
- Fix lags
- Fix MTP
You can find the update in OP below attachments

New update! 2022-04-17:
Changelog:
* Fixed recovery.fstab, you can install any roms without crash now!
* Added custom LUN path
* Added EFS, OTG, Micro SDcard, preload and etc stuff on recovery.fstab
You can download below attachments

New update! 2022-05-01:
Changelog:
* Happy Mothers Day!
* Synced latest sources
* Updated to omni branch twrp-6.0
You can download the recovery below attachments

New update! 2022-05-06:
Changelog:
* Updated recovery.fstab
* Modified device tree to not cause any crashes
* Added F2FS/ext4 support
* Added PERSIST partition (Means you can install any ROMs without crashes on SM-J320FN/F)
* Updated sources
You can download the recovery below attachments

should I try to bringup cyanogen recovery?

notnoelchannel said:
should I try to bringup cyanogen recovery?
Click to expand...
Click to collapse
++++ yes

notnoelchannel said:
should I try to bringup cyanogen recovery?
Click to expand...
Click to collapse
I ported it but it doesn't work stably

ALEKSKART said:
I ported it but it doesn't work stably
Click to expand...
Click to collapse
because if you port from Lenovo A1000 it won't work fine

djeman said:
Hi,
It's not really oreo that don't works on the j3 but I never found a compatible gpu driver ...
Android have modified deeply the gpu driver interface on oreo and the driver is not open source.
So I abandonned but all the boot sequence was good only this driver was missing.
Thanks for the new recovery
Click to expand...
Click to collapse
why can't we use software rendering tho? BUT because of our processor it would be VERY slow

2022-06-07:
Changelog:
- Added TWRP 3.6.1-9 support for SM-J320H . !!!TESTING NEEDED!!!
You can download TWRP in the OP (there's no update for SM-J320FN/F/etc for now)

New update is up!
Changelog:
- Rebrand to TWRP 3.6.2-9.0
- Removed TWRP 3.6.1-9's download link for SM-J320H due to not fitting partition for now.
You can download the recoveries below the OP.

up

Hello dev, TY for this recovery. I have a problem with latest version (sm-j320fgm-twrp-3.6.2-20220614) The sdcard can't be mounted. TWRP treat it as if it were the internal storage. So, when I try to mount the sdcard, the internal storage is mounted instead. Also despite the file manager shows "sdcard", it access to internal storage. Finally the "/storage" folder is missing. Testing in SM-J320M.

[ROM] [PORT] [FIG-LX1] [12.1] LeaOS - Unofficial Lineage OS 19.1 GSI port from P20 Lite

Unofficial Lineage OS 19.1 port from P20 Lite
for FIG-LX1 devices (P Smart 2018)
{
"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"
}
​
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Introduction:
This is the Unofficial Lineage OS 19.1 thread for the Huawei P Smart 2018 (FIG-LX1). This version of Lineage OS is a modified version of the original, containing different patches in order to make the device functional. I have made a couple of tweaks in order to boot on this device, as this rom is ported entirely from another build made for P20 lite (not made by me, credits at the end of the post).
DOWNLOAD LINKS:
ROM: Here
TWRP - Recovery: Here
GPS Patch: Here
(Only for devices running EMUI 9.1.0.405 or higher) DRM Patch: Here
GAPPS: Here
Other mentions and requirements:
You'll need a microSD card (at least 8GB).
The bootloader must be unlocked. You'll need a tool called DCUnlocker or PotatoNV (The first one is paid - around $5, the second one is free but requires you to physically open your phone). Also, you need to make sure that you are running on EMUI 8.0.0 build before JUNE 2018. Otherwise, you'll need to downgrade to an early version. I have downgraded to 8.0.0.128. I think it works with 129 too. Tutorial Here and additional info Here.
After getting the bootloader code, you'll have to put it in a safe place and upgrade again to any eEMUI 9.0.0.xxx. THIS ROM WILL NOT WORK WITH EMUI 8.0.0.xxx!!!
Also, the rom is not very stable for daily use. So, I do NOT recommend to use this ROM on your primary device! It's stable enough to be functional. (See bellow)...
INSTALLATION:
1. Download all the files (look for download section)
2. Extract the img file from the ROM zip
3. Flash system image : fastboot flash system <drag system.img here>
4. Flash TWRP image: fastboot flash recovery_ramdisk <drag twrp img here>
5. Boot into twrp: power and vol+ simultaneously while NOT connected to pc
6. Resize system: Wipe > Advanced Wipe > Check System option > Repair or Change File System > Resize File System > Swipe
7. Wipe cache, dalvik/art cache, internal storage, data
8. Copy GPS Patch, DRM Patch (see notes if you need it or not), GAPPS onto the microSD card
9. Reboot and ENJOY
Optionally, you can install Magisk via recovery by flashing the apk. Tested with the last version of Magisk, not working, cause bootloop. Further testing is required
Bugs and other problems:
Charging while the phone is powered off (atm there is no fix available)
Bluetooth pairing with code (FIX: search for Bluetooth Force Pin app)
After the first boot, there is a system crash (everything crashes) and the system is unusable. (FIX: Restart the phone)
Weak signal with some carriers (atm there is no fix available)
Other UI settings and device specific functions
Secondary camera - testing EMUI camera port for Custom ROMs (Possible FIX, not tested - GCAM)
Possibly other things
Source Code:
https://github.com/Iceows
ROM OS Version: Android 12L (12.1)
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9
Based On: Lineage 19.1
CREDITS:
https://forum.xda-developers.com/m/1960538/ ~ PHH (Huawei tweaks)
https://forum.xda-developers.com/m/8281637/ ~ eremitein
https://forum.xda-developers.com/m/3777227/ ~ TureX (kernel)
And
https://forum.xda-developers.com/m/altairfr.11572895/ ~ AltairFR (The original ROM)
THANKS EVERYONE WHO TESTED THIS ROM AND HELPED
atm no support group for this model

Screenshots

Reserved 1

Reserved 2

Hello,
does this rom work for the P smart 2020?

hello I do not understand the steps to take when I download the file it turns out that it is a 7z file

Hey, any updates or the post are dead?

kracc said:
Hey, any updates or the post are dead?
Click to expand...
Click to collapse
Hi
I have release an update for FIG-LX1 with Android 13
LeaOS-A13-20230105-iceows-google-fig.xz
LeaOS-A13-20230105-iceows-fig.xz
And new AGPS Patch
4-Huawei-AGPS-AB-v1.2-signed.zip
And a patch to fix RIL restart or not 4G data
11-Huawei-MonoSim-FIG-AB-v1.0-signed.zip

AltairFR said:
Hi
I have release an update for FIG-LX1 with Android 13
LeaOS-A13-20230105-iceows-google-fig.xz
LeaOS-A13-20230105-iceows-fig.xz
And new AGPS Patch
4-Huawei-AGPS-AB-v1.2-signed.zip
And a patch to fix RIL restart or not 4G data
11-Huawei-MonoSim-FIG-AB-v1.0-signed.zip
Click to expand...
Click to collapse
wow android 13. but i have the fig-lx3 version, will it work for me?

kracc said:
wow android 13. but i have the fig-lx3 version, will it work for me?
Click to expand...
Click to collapse
Yes

AltairFR said:
Yes
Click to expand...
Click to collapse
Wow, no bugs bro?

I have not the time to test

kracc said:
wow android 13. but i have the fig-lx3 version, will it work for me?
Click to expand...
Click to collapse
Well can you help me ? I can not flash because img is heavier than my system partition. im on a FIG-LX1 (Europe)
(i replied to the wrong comment srry)

Use my tools HWGSIPartitionti increase system size

AltairFR said:
Use my tools HWGSIPartitionti increase system size
Click to expand...
Click to collapse
I have a same error and im tried to use your tool but im getting this error in cmd : adbd cannot run as root in production builds.Im installed chainfire's adbd insecure app and adb_root magisk addon,adbd insecure will dont work and when i installed magisk addon my pc cant recognize the phone and phone is only charging(when i removed magisk addon fixed this problem).Sorry for my bad English and this is my first message on this forum.

AltairFR said:
Use my tools HWGSIPartitionti increase system size
Click to expand...
Click to collapse
Where I can download this tool??

PROUFUK said:
I have a same error and im tried to use your tool but im getting this error in cmd : adbd cannot run as root in production builds.Im installed chainfire's adbd insecure app and adb_root magisk addon,adbd insecure will dont work and when i installed magisk addon my pc cant recognize the phone and phone is only charging(when i removed magisk addon fixed this problem).Sorry for my bad English and this is my first message on this forum.
Click to expand...
Click to collapse
You can enable root adb in the developer option in settings

vfsdz said:
Where I can download this tool??
Click to expand...
Click to collapse
Search on xda

AltairFR said:
Search on xda
Click to expand...
Click to collapse
sorry but i'm new on xda and i don't know where to look for it and what it's called, sorry if it's a problem for you