Database Info

[ROM][7.1.2] AOSPA Paranoid v7.3.1 for Honor 6x

Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
Code:
* Your warranty is now void.
* We are 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.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
This ROM is provided by CodeOfHonor​
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/codeofhonor-dev/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Honor 6X
Contributors
haky 86, HassanMirza01, felix-development
Source Code: https://github.com/codeofhonor-dev, Meticulus and the stuff of CodeOfHonor.
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-04-27
Beta Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-04-27

ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.

I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out

MadMurl0c said:
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
Click to expand...
Click to collapse
10% mark?
Did you entirely remove all the fingerprints before flashing this Tom?
Go back to Elite or Stock, remove all fingerprints and reinstall the Rom
For Root, you can try changing recovery or using an older version of Magisk that worked for you

I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't

After I downgrade from emui 8 to emui 5 in 5 minutes now I can fix this rom so expect a build within these days

hoping to try this rom , following for updates

Hey guys I just installed the rom, but I did notice that I don't have access to any Gapps. How to I install them? I'm using TWRP. I was just able to get my unlock code from Honor today, so I unlocked and rooted, and flashed your rom as the first thing, so I'm running a fresh flash of the latest version.

Flash package with Twrp: https://opengapps.org/

Thanks guys, I realized that yesterday right after I posted lol. So far I'm really loving the plain stock-ness of this rom, hopefully it give the device some more life so I won't have to upgrade soon.

MadMurl0c said:
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
Click to expand...
Click to collapse
Yeah I'm having the same issue to, with no root.

Can someone tell me why this rom is different to all others ? Why is this one using stock vendor and can we easy revert to Emui ? Why don't all others ?
I'm on stock now.

How is the quality of the photos compared to stock rom? It is possible to install Emui camera or other huawei cameras?

** Note **
developments of hi6250 is end reason: switch to another phone, have phone.

** Note **
Developments for hi6250 has been resumed but just for this ROM, sorry for the inconvenience.
I'm already downloading the source for releasing new build but AOSPA will take a wile since have bigger source.

** Note **
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.

Had anyone tried installing Xposed yet?

Support BLL version? Honor 6X

The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.

MadMurl0c said:
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
Click to expand...
Click to collapse
Guys to flash magisk or superSU use Meticulus TWRP, other twrp like eliteTwrp show an error when it is recompilling the boot.img

[AOSP][9.0][GSI] AOSP Treble A750FN

This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
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.
*/
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix *click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon

compatibility
does it work for A750FNXXU1ARK2/ARK4?
Which file do I need to flash, vanilla, floss or gapps?

NickDeveloper said:
does it work for A750FNXXU1ARK2/ARK4?
Which file do I need to flash, vanilla, floss or gapps?
Click to expand...
Click to collapse
It should work with EVERY firmware on FN, but I simply was not able to try it out this way. Vanilla don't have gapps, use gapps imo.

This is awesome, thanks. Would there be a way to use stock camera app for wide lens support?

hhadi said:
This is awesome, thanks. Would there be a way to use stock camera app for wide lens support?
Click to expand...
Click to collapse
Only way to do it would be porting default camera app together with libs/drivers :c

Finger print option is not there in the settings for me. Is this a /vendor problem?

It sucks to be a a750gn user right now

Bootloop after flashing (help)
Erecik said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
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.
*/
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix *click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon
Click to expand...
Click to collapse
Am I the only one who is having a bootloop after flashing? (I did everything exactly like in the instructions.) Can anyone help me?

limeswift said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
Am I the only one who is having a bootloop after flashing? (I did everything exactly like in the instructions.) Can anyone help me?
Click to expand...
Click to collapse
Same here, I spent whole day on this thing and tried it 5+ times and lo luck. Maybe because I was trying it on A750F varient

I try to install 4 times. SM-A750FN
2 times got boot without network, ROM detects 2 SIM cards but unknown, cant search for networks, no phone numbers, only WiFi works.

Erecik said:
This guide is based on information posted here:
GUIDE
A8 GSI by prashantp01
All credits for ozontec, and for prashantp01 for creating GSI for A8+
AOSP PIE GSI on A750FN
I'm not responsible for whatever damage this can cause to your device
How to:
Update to latest official firmware (tested on ARIC and ARL4)
Make full boot at least once
Make sure you have a TWRP installed, follow *click me for TWRP*
Boot once after installing TWRP
Download the latest AOSP GSI
Boot into recovery
Perform a Factory Reset, don't touch System or any other partitions
Flash Magisk
Flash AOSP image as System
Flash Camera Fix*click me for fix*
First boot may take up to 10 minutes
Download:
AOSP GSI - Pick arm64 one with "aonly", rest is up to you!
If anything went wrong, flash stock firmware with ODIN!
What is working:
-Calls
-Wifi, Bluetooth, NFC
-Camera
-SD Card
-Dual Sim
-Vibrations, Speaker, Microphone, Sensors
-Everything but...
What is not working:
-USB to PC
-VoLTE / VoWiFi
-NFC menu is laggy, very laggy...
Remember to say "thank you" to those people:
Credits:
@ozontec for creating raw guide
@prashantp01 for creating GSI for A8/A8+
@ashyx for TWRP
Screenshots soon
Click to expand...
Click to collapse
A7 2018 is released with Oreo,So It's support A/B Partition

a750fn android pie
in my a750fn with this firmware A750FNPUU1BSC4, the aosp gsi rom not work. The only custom rom work for me is Android P (PR1) sGSI that is unofficial rom and it is google pixel rom but data not work! please can you help me?

I followed all the instructions.... Bootloop on SM-A750GN.

This Havoc OS version is working on my 750FN
https://forum.xda-developers.com/showthread.php?p=79267026
I've updated to newest Pie One UI Firmware first.
I had Havoc OS at my Xperia XZ and its a very light rom.
And I like the customization features.
With GApps aroma you can pixelfy it very well.
Camera is also working.
In my opinion the battery drain is more less than Stock Samsung ROM (and i installed a lot Google stuff with GApps aroma).
There are two annoying bugs;
-In windows no Drives appaer with usb connection (MTP device is present in device manager)
-No auto brightness.
Maybe someone could help with this two bugs.

It dose not work on my A750F Pie version. The build number is A750FNPUU1BSC4. I tried this rom to flash but I faced with bootloop every time, I tried other versions of GSI also but not worked yet!
Is there any solition? Plz help me!

As you can see in my post, it's for A750FN!

Erecik said:
As you can see in my post, it's for A750FN!
Click to expand...
Click to collapse
Can you tell me why it will work only for A750FN and not other firmware version like GN etc.

blazzer12 said:
Can you tell me why it will work only for A750FN and not other firmware version like GN etc.
Click to expand...
Click to collapse
It's not firmware difference. GN, FN, F, G, etc are different HARDWARE versions, so some minor changes are present in every version of phone. That makes it works only on FN

Erecik said:
It's not firmware difference. GN, FN, F, G, etc are different HARDWARE versions, so some minor changes are present in every version of phone. That makes it works only on FN
Click to expand...
Click to collapse
Thank you for clearing that up for me.

Hijacks said:
This Havoc OS version is working on my 750FN
https://forum.xda-developers.com/showthread.php?p=79267026
I've updated to newest Pie One UI Firmware first.
I had Havoc OS at my Xperia XZ and its a very light rom.
And I like the customization features.
With GApps aroma you can pixelfy it very well.
Camera is also working.
Click to expand...
Click to collapse
Sorry to ask that annoying question, but do you know if VoLTE and or WiFi Calling are working on any of the GSI ROMs?

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption

[UNOFFICIAL][ENCRYPTION][wrappedkey] TWRP 3.3.1-6: proper system_as_root & decryption
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Introduction
This is an unofficial build of TWRP for Redmi Note 7 Pro (violet). Differences with the official one include:
- Supports CAF-based wrappedkey encryption (decryption) properly (tested with MIUI 10.3.5.0)
- Supports decrypting devices that have screen lock set up after Android 9 May update, which introduced a new key derivation function.
- Mounts the system partition at /system_root as per AOSP standards. This makes the auto-backup scripts (e.g. GApps / Magisk survival script) work properly during updates, and you no longer need any 'patch' to flash GApps / Magisk properly. However, this may break some existing ROMs. See below FAQ section for details.
- Appended DTBO to the recovery image so it doesn't depend on the dtbo partition. No standalone DTBO image required.
Flashing instructions
- Download and extract the img file
- Reboot to fastboot mode
- fastboot flash recovery whatever_img_file_you_extracted.img
- Reboot and press Volume + to enter recovery
- DO NOT try to run 'fastboot boot recovery.img', it won't work.
- DO NOT flash the fcrypt disabler if you use my recovery. There is no need to do so, and it is possible to mess stuff up if you don't know what you are doing.
- You have to format the data partition if and ONLY IF:
1) You were not encrypted, now going to an encrypted state, or vice-versa OR
2) You were on a ROM other than MIUI that does not support "wrappedkey" (ROMs would often state it supports wrappedkey if it does), now going to a ROM that supports it
Limitations
DO NOT boot this recovery with empty system and vendor partitions. It will fail to decrypt any data partition with empty /system and /vendor. DO NOT wipe system and vendor partitions without installing a new one before rebooting. I am working to remove this limitation.
Now works even with empty system and vendor partitions after 3.3.1-5. No need to worry about formatting system and vendor breaking TWRP any more.
The restore zip created by the Migrate app is NOT compatible with this recovery. It's a problem of the Migrate app, not this recovery. Please DO NOT try to flash the restore zip created by Migrate.
FAQ
- Q: Do I need any specific DTBO image to make this recovery working?
- A: Nope. It is appended to the recovery image so it will work with any DTBO.
- Q: What is wrappedkey?
- A: It's a different mode of FBE implemented in CAF, the Qualcomm branch of AOSP.
- Q: This cannot install ROM X, why?
- A: Because it mounts the system partition at /system_root, which is AOSP standard behavior for A-only system_as_root devices, but is broken in some custom ROMs currently (MIUI should work though). To make any ROM work again, they will need to include this commit from LineageOS Gerrit https://review.lineageos.org/c/LineageOS/android_build/+/247066
- Q: Decryption doesn't work with ROM X, why?
- A: Decryption should work for most ROMs based on the CAF branch (not AOSP). CAF ROMs (including official MIUI) use a different scheme for key storage, which is why TWRP hasn't supported it till now. I have ported the CAF encryption changes (wrappedkey) to TWRP, but unfortunately this will break ROMs that do not support the CAF wrappedkey mode of encryption. Here is a list of patches non-CAF ROMs need to support CAF-encrypted /data partitions https://mokeedev.review/q/topic:%22fbe-wrapped-key%22+(statuspen%20OR%20status:merged). If you confirm your ROM is CAF-based but the decryption still does not work, please open an issue on my GitHub repository which you could find below. (XDA threads are no good for issue tracking, sorry)
- Q: Why not contribute to the official TWRP?
- A: All the patches to the TWRP code base have been submitted to the official gerrit code review, though not merged yet, which you can see below.
Downloads
3.3.1-6: https://mega.nz/#!3QIRQYhK!Jq5QrGfJw5VCYZ8sq_BO1qNZecrFqlM9IB1IdSwogvI
changes: updated kernel to support pstore instead of /proc/last_kmsg. If you don't know what this is, it's probably not relevant to you.
Here you can find an unofficial LOS build with wrappedkey encryption and also proper system_as_root support for those survival scripts https://forum.xda-developers.com/redmi-note-7-pro/development/unofficial-lineageos-16-caf-encryption-t3933532. In addition, all official MIUI builds should flash just fine.
History versions:
3.3.1-5: https://mega.nz/#!nMowHKiL!zRvoTM0iIZKArmUDnZzaEFtXQv0_q7hIHUCmTHTOmOM
changes: 1) Now works even with empty /system and /vendor partition 2) Fixed brightness problem; 3) Enabled EDL Reboot
3.3.1-3: https://mega.nz/#!yAYXxAzZ!FNMYLzLphnSmJ-DbBx-OZUgxxYiftgn8e4Jn3kxiQik
Patches and sources
Patches for TWRP are available here:
https://gerrit.omnirom.org/#/c/34091/
https://gerrit.omnirom.org/#/c/34093/
https://gerrit.omnirom.org/#/c/34092/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/34096/
Patches for ROMs to support wrapped key have been given in the above sections.
Source of the current device tree for TWRP: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp
Kernel source: https://github.com/PeterCxy/android_kernel_xiaomi_sm6150, note that the device tree uses a prebuilt kernel image.
Contributors
PeterCxy, Dyneteve, merothh
Source Code: https://github.com/PeterCxy/android_device_xiaomi_violet-twrp

Now fixed and tested with MIUI.

PeterCxy said:
Now fixed and tested with MIUI.
Click to expand...
Click to collapse
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.

I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?

Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?

Can confirm this successfully decrypts storage, running xiaomi.eu on my phone. Thanks for your work.

Dwughjsd said:
Could you please tell us what is fixed and what is wrong with the previous one? Just out of curiosity.
Click to expand...
Click to collapse
It did not decrypt MIUI 10.3.5.0 successfully due to magic (I missed some commits from qcom). It was fixed by pulling more commits in.

Jpwner said:
I’m not new to installing custom recoveries and installing ROM, but I am new to Xiaomi devices.
In the simplest form possible,
With this I should be able to just run the ‘fastboot install recovery twrp.img’ and not have to run “fastboot erase userdata’?
also
Do I still need to flash the zip I have that disables forced encryption?
Click to expand...
Click to collapse
You won't need to erase userdata or flash fcrypt disabler anymore, if all the ROMs will update to support the wrappedkey encryption

Naveenthemi said:
Could you provide instructions to flash this ?
Or is it just the same as the 'official one'?
Click to expand...
Click to collapse
just fastboot flash recovery whatever_you_downloaded_and_extracted.img

PeterCxy said:
just fastboot flash recovery whatever_you_downloaded_and_extracted.img
Click to expand...
Click to collapse
So it's possible for me to flash OTA Updates without encountering a bootloop and such?

Can someone please provide an alternate download link? The Mega link doesn't seem to work for me.
EDIT: Worked on a different device. Thanks.

Naveenthemi said:
So it's possible for me to flash OTA Updates without encountering a bootloop and such?
Click to expand...
Click to collapse
+1
Please answer

Good job! ?
I want you to know that your patch has been merged with the official one. I was away for a while so I hope you understand the little unfortunate delay.

In latest update can we flash any custom roms without any issue?

Yogendra Kher said:
In latest update can we flash any custom roms without any issue?
Click to expand...
Click to collapse
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in

PeterCxy said:
You have to wait until custom ROMs pull in necessary system_as_root changes. Currently it seems only my LOS build pulled that in
Click to expand...
Click to collapse
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)

Naveenthemi said:
Is it possible to flash OTA updates without encountering bootloops and such? (MIUI)
Click to expand...
Click to collapse
Should work fine with MIUI. At least from what I have tested.

kushal.purkar said:
+1
Please answer
Click to expand...
Click to collapse
PeterCxy said it would as far as his testing had been done.

Gapps aroma not installing in this one as well. error 255

Can I flash Magisk and root my phone with this build.?
Do you have any Magisk zip file that will work.?
Thank you for your work

[A/B][TREBLE][9.0][A530F/A530W/A730F]SaR patch and kernel for Pie Vendor

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 features included in this patch
* 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.
*/
INFO:
This is a patch and SaR kernel made for @prashantp01's Vendor Dumpster V1.1.
SaR (System as Root) means the system partition is mounted as the root filesystem.
This allows our phone to boot System-as-Root (also labelled as A/B) GSIs which are the only type of GSIs still supported officially by Google.
There are two types of boot images I'm providing:
Android 9 style ramdiskless SaR
Android 10 style 2-stage init SaR
In general, you should use the Android 9 version for Android 9 based GSIs, and use whichever you want for Android 10 or newer.
The kernel is a modified version of @prashantp01's Quantum Kernel v4.0.
Source code for it is available here: github.com/VDavid003/universal7885_SaR
If you are used to using PHH-Magisk, now you don't have to: you can use normal Magisk on A/B GSIs, but
NOTE:Magisk currently doesn't work on Android R! (20.4, newer ones may work in the future)
NOTE:The patch and kernel are currently not tested on A530W and A730F. Please tell me if it works or not!
BUGS:
-Basically every bug that is present in the original Vendor Dumpster V1.1
-Secure lock screen can't be set (no pattern/pin/password unlock)
-Seems like Android 11 Developer Preview 2 and later does not currently work. DP1 works fine tho, you can download it here.
INSTALL INSTRUCTIONS:
Follow the instructions to install Vendor Dumpster V1.1.
Flash the SaR Patcher zip from TWRP(this will still let you boot non-SaR GSIs, but it will make the vendor compatible with SaR GSI)
Install a SaR boot.img (P or Q) for your model. (TWRP -> Install -> Install Image -> Select your boot.img -> Select Boot from the list -> Swipe to flash)
Flash an A/B or SaR GSI as you would do normally.
DOWNLOADS:
The root folder contains the vendor patcher zip, and the boot.img folder contains boot.imgs
Naming scheme for them: boot_[MODEL]_[P/Q].img
DOWNLOAD HERE
SPECIAL THANKS:
@prashantp01 for his vendor and kernel. Go support him!
Everyone involved in his vendor/kernel.

CHANGELOG
1.0:
-Initial release with some stuff accidentally left out
1.1:
-Fixed RIL (temporary fix currently), and enabled the media codec fix I forgot to enable in 1.0

I'm assuming it's for A/B only and won't work for A-only devices?

lanadelreywhore said:
I'm assuming it's for A/B only and won't work for A-only devices?
Click to expand...
Click to collapse
Since A530F is a A-only device i assume it works for both, OP correct me if i'm mistaken
Looking forward to test this after the Lock bug is fixed, that's kinda a daily must for me

lanadelreywhore said:
I'm assuming it's for A/B only and won't work for A-only devices?
Click to expand...
Click to collapse
OverLineMusic said:
Since A530F is a A-only device i assume it works for both, OP correct me if i'm mistaken
Looking forward to test this after the Lock bug is fixed, that's kinda a daily must for me
Click to expand...
Click to collapse
The patch shouldn't break aonly GSIs but it should allow an A/B(that's actually the wrong name but it's called that because of historic purposes) GSI to boot IF you install a SaR boot.img thus converting your phone to SaR. After installing a SaR boot.img you can't boot Aonly GSIs until you flash an Aonly boot.img again (by installing the regular quantum kernel for example)

VDavid003 said:
The patch shouldn't break aonly GSIs but it should allow an A/B(that's actually the wrong name but it's called that because of historic purposes) GSI to boot IF you install a SaR boot.img thus converting your phone to SaR. After installing a SaR boot.img you can't boot Aonly GSIs until you flash an Aonly boot.img again (by installing the regular quantum kernel for example)
Click to expand...
Click to collapse
Yeah I finally understood that a few days ago but I guess cause of my a8 being a530W model it's not working cause I do all the steps as instructed and when I try to boot it bootloops on splash screen. Will reboot every 3-4 seconds or straight to download mode. Tried a handful of different a/b gsi and no luck. Only a preview of Android 11 booted actually

lanadelreywhore said:
Yeah I finally understood that a few days ago but I guess cause of my a8 being a530W model it's not working cause I do all the steps as instructed and when I try to boot it bootloops on splash screen. Will reboot every 3-4 seconds or straight to download mode. Tried a handful of different a/b gsi and no luck. Only a preview of Android 11 booted actually
Click to expand...
Click to collapse
Huh, weird.
Have you tried the pie boot.img?
If that doesn't work, can you provide logs? (from /proc/last_kmsg)
I'd be interested in what might be the problem, since I can actually boot my a530f with the a530w kernel and it works.

My A530F is now up and running the descendatx a/b GSI. Great Work thanks

Hllo,
I want to ask about GSI FiX Boot.zip comes from prashantp01
Do I need to flash it ? Or just go straightforward as described instruction from OP ?
Sent from my SM-A530F using Tapatalk

hi.. i don't understand why there is boot_a530f_P_and_Q.img . do i have to install boot_a530f_Q.img when i install GSI android Q? can i install GSI android Q or above just by installing boot_a530f_P.img.. basically my device is android P..

suh4rji said:
hi.. i don't understand why there is boot_a530f_P_and_Q.img . do i have to install boot_a530f_Q.img when i install GSI android Q? can i install GSI android Q or above just by installing boot_a530f_P.img.. basically my device is android P..
Click to expand...
Click to collapse
Yeah very curious to know Aswell

Development [ROM][OFFICIAL] LOS-Modded 19.0[DISCONTINUED]

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.
*/
LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.
LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.
All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.
Make sure to wipe userdata, ensure you have at least taken one stock OTA!
Flashing Instructions:-
TinyFastbootScript:-
Make sure to wipe userdata
1. Download TinyFastbootScript
2. Download the ROM named *Images*
3. Unpack TinyFastbootScript and the ROM into the same directory
4. Run the bat file for TinyFastbootScript
5. Choose latest fastboot version
6. Place device in bootloader mode
7. Run the command for flashing custom firmware
8. Done!
Fastboot Method:-
1. Download the Images zip
2.
Code:
fastboot update *Images*.zip
3. Reboot and enjoy!
Bugs :
Permissive
Safetynet
DualSIM
Some Settings Functions
* Drop a comment down below if you need any help, you can also Join https://t.me/electimonrel on telegram if you need any help.
Downloads:
Lineage-Modded:
https://build.lolinet.com/file/lineage/nio/
Contributors
@Electimon, @erfanoabdi, @dianlujitao
Source Code: moto-sm8250
Version Information
Status: Beta
Jan 06: initial release

Amazing work

awesome

Great work on the ROM electimon, smoothest available, and the battery management is excellent.

Hi,
I think scoped storage doesn't work properly on my Moto Edge S with Lineage 19. I'm trying to use some apps that require it, but they crash every time I try to add a directory, like aethersx2 for example.

Hi all
I successfully installed the Rom but only sim 1 work
How to activate two sims please .
Thanks all

Makhreta said:
Hi all
I successfully installed the Rom but only sim 1 work
How to activate two sims please .
Thanks all
Click to expand...
Click to collapse
check again the above bug list

bawitdol said:
check again the above bug list
Click to expand...
Click to collapse
Yes i know ,
so this mean no solution for this problem ?

Makhreta said:
Yes i know ,
so this mean no solution for this problem ?
Click to expand...
Click to collapse
Some people on Telegram have reported both sims working by flashing Evolution X, then flashing to los-modded 19 without wiping. Your results may vary though

Beetle84 said:
Some people on Telegram have reported both sims working by flashing Evolution X, then flashing to los-modded 19 without wiping. Your results may vary though
Click to expand...
Click to collapse
but i cannot find evolution x rom for this device ???!!!

Makhreta said:
but i cannot find evolution x rom for this device ???!!!
Click to expand...
Click to collapse
Motorola Moto G100 / Edge S
The Motorola Moto G100 / Edge S is a 6.7" phone with a 1080x2520p resolution display. The Qualcomm SM8250-AC Snapdragon 870 5G chipset is paired with 6/8GB of RAM. The main camera is 64+16+2MP and the selfie camera is 16+8MP. The battery has a 5000mAh capacity.
forum.xda-developers.com

is it android 12?

i tried version 18 and the two sims is o.k

HOW TO INSTAL MAGISK in this rom
1. download TWRP 3.5.2 and magisk 23.0
2. command <fastboot boot twrp.img> in bootloader mode
3. command <adb push magisk.zip /sdcard> in twrp
4. flash magisk.zip file
5. reboot to system
^^

Works great thanks!
having some issues with Android Auto showing black display since switching to this tho?
anyone know how to fix?

Is there a newer build?

xisa11 said:
Is there a newer build?
Click to expand...
Click to collapse
Under development

Just wondering what the differences would be between thins and the non-modded Lineage? I'm assuming more features, add-ons, but what are they?

Hello and thanks to everyone who is working on these different Roms for the g100!
One question, which is the most stable Rom for the g100 (without Google) to use as an daily driver?
Is this Rom 19.0 capable as an daily driver?
Thank you

How do I flash this on Linux ?. I suppose it is a bunch of fastboot commands but I am not sure.