[ROM][Custom] - = EDGE PURE EDITION = - - Motorola Edge ROMs, Kernels, Recoveries, & Other D

[ROM][Custom] - = EDGE PURE EDITION = - - Motorola Edge ROMs, Kernels, Recoveries, & Other D

Can i Flash from Lineage or need stay in stock?

VitilinVk said:
Can i Flash from Lineage or need stay in stock?
Click to expand...
Click to collapse
"New and Clean Stock firmware is required"

Upgraded Edge Pure Edition!
- created an image in a different format which reduced its size by 6 GB;
- full mount of system in r/w and r/o, allowing the system to boot up fully if you forget to put the system in r/o after making edits to the system partitions;
- updated GApps to the base of 27/02/21.

I'm not sure if you actually know the rules but wrz are not allowed

Upgraded Edge Pure Edition!
- updated ROM to the latest versions of stock firmware QPD30.114-80-4 (09 March 2021) ;
- updated GApps to the base of 12/03/21.

Upgraded Edge Pure Edition!
- Chrome bug fixed

Updated the ROM to a version based on Android 11(R).

Anyone using this daily?

I use. Why can't this ROM be used as the main firmware?

Hi, I tried installing the android 11 version of this from after clean restoring to stock. I installed the .img to the super partition and the phone wont boot. I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address. Any help? Thanks

Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11

Nicktsaab said:
I get the "unable to open block device /dev/block/loop (20, 19, 18, 17): no such device or address.
Click to expand...
Click to collapse
This message appears because TWRP is not adapted to Android 11. Ignore it.

ilia3367 said:
Have you fully read and followed all the points in the instructions? Have you installed Magisk?
To install Edge_R_Pure_Edition, the firmware RPD31.Q4U-39-26-4, Android 11, must be installed on the device.
Download Stock Android 11
Click to expand...
Click to collapse
Ahh thank you, I was trying to install on the Android 10 base. Thanks!

what is the difference between r and q? android 10 and 11 i assume?
also ive been out of the rom loop for quite a while (lg g8, just got unlock like a month ago), what is wrz and why is it not allowed? just curious.

im having a weird issue. i bought 2 edges recently, and wanted to install this rom. both are on final android 10 firmware, and im flashing the q img. obviously both are bootloader unlocked and using twrp 3.5.2.
i followed instructions on one, and it went perfectly fine no issues. on the second whenever i flash the image it wont boot and the twrp log has a few errors about partitions. also there are 2 super partitions listed. even restoring my bone stock twrp image or flashing the factory fimware i have the same issue and the twin super partitions persist. the phone will boot on the stock rom fine however.
edit: weirdness continues, now all of the sudden the rom image flashed perfectly fine, when i rebooted back to twrp for magisk.zip i had no errors. however there STILL is 2 supers listed. but i flashed magisk and booted to system... and it boots. idk.
in the select partition to flash to menu the partitions listed (in order) are: boot, dtbo, boot logo, recovery, super, vbmeta, vbmeta system, super. ive tried both instances of super and both had problems except for this time where it succeeded (i did the first instance this time).
i should also note that this was like this when i made my initial twrp backup, there were 2 super partitions in the backup menu. but, the other phone that had no issues, did NOT have 2 super partitions at any point. again... idk.

Unfortunately, I didn't understand a lot of it, because I don't know English very well.
The fact that in TWRP in Backup you see two Super partitions, it's not a big deal. Choose both, but in fact your backup will have one Super partition.

its just strange but i guess if it works.
but im also having issues with applications. for one, the asus gallery and file browser that are bundled always ask for storaage permissions, even if i grant them they wont launch and keep asking for permissions. wipe data, force stop, grant permissions again, nope they still ask for permissions. i dont know whats going on with them. also i cant set a picture wallpaper. not with gallery, google photos, google gallery, nothing. i get a notification that says "error, could not load media" every time i do it no matter what app i try to use. live wallpapers are fine.

There should be no such problems. This behavior can only be when you try to make these applications (Asus Gallery, Asus File Manager) system applications using, for example, RootExplorer.
I don't have this problem even after restoring a backup.
Install ROM on a clean, re-installed stock firmware.

Related

[MOD] Disable Forced Encryption on Robin [Updated 2016-10-09]

I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
{
"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"
}
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.

Thanks, worked well!
Thank tested, will se if it gets any faster. Have been having some problem with lag that comes from time to time that I haven't seen on other devices.
Otherwise, great to see support for such a small phone!

The Robin devs are trying to be Community friendly as much as possible its good to see.

can it still be updated using this mod boot ?

kanded said:
can it still be updated using this mod boot ?
Click to expand...
Click to collapse
Unfortunately no, because the OTA includes an updated delta for the kernel as well (which means the /boot needs to be 100% stock).
If you want to install via the OTA, you need to restore the stock boot.img (and the system partition - if you're rooted or modified it in any way, and the recovery too, if you have TWRP installed).
Alternatively, you may simply flash the updated stock ROM zip on top of your existing install - just be sure to flash the new boot.img zip immediately after (as well as SuperSU and any other mods you may have, if you want to preserve your current setup).

Thank you for this [deXter] it works great.
However does anyone have a solution for how to get rid of the 5 sec nag screen popping up at reboot?
Thanks in advance/arc.

For June update 350 please.

I need help!
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?

Angeldgaf said:
When I boot up and finish setup ,my battery percentage said : 3.0858 % and Wi-Fi wasn't turning on did I do something wrong?
Click to expand...
Click to collapse
This mod only allows you to use your phone unencrypted - it shouldn't affect your battery or WiFi. Are you sure you flashed the correct version?
Goto Settings - About. If you're on the June 1 ROM (Build 00WW_1_350) then your kernel version should say 3.10.84 Wed Jun 1. If these numbers do not match then restore to the latest factory image/ROM and start over. Also, have you tried a factory reset yet?

For 450 Please

Updated for build 450.

Hi everybody! Just receveid the OTA notification
I'm currentyl on 6.0.1 1450 rooted with twrp, do you have the modified boot.img for the Nougat beta as well? Thanks

Many thanks for this work. Getting the Robin rooted and usable was a struggle compared to the Nexus4. This mod helped greatly.

Boot image for N88 please. Thanks in advance.

So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?

Steffen1st said:
So did I understand right, I only can use this mod for stock ROM (not for LineageOS 14.1)?
Click to expand...
Click to collapse
Yes. Lineage does not have forced encryption.

[deXter] said:
I've modified Robin's boot.img to disable forced encryption.
With encryption gone, you'll be able to use TWRP to flash mods etc, without having to wipe your data every single time.
Other benefits include faster performance and better battery life.
Unfortunately, to actually remove the encryption - you will need to format one last time.
But once done and set up, you'll see that your phone is no longer encrypted.
Requirements:
- Unlocked bootloader
- PC / Mac
- fastboot (+ USB drivers if needed) -or- existing TWRP install
Instructions:
If you're using TWRP:
1. Perform a factory reset from within TWRP and reboot back into it (Note: This isn't required if your upgrading from an existing unencrypted stock install).
2. Flash the included zip file
3. Reboot
Manual flash using fastboot:
1. Download the zip and extract the boot.img file
2. Reboot your Robin into fastboot mode
3. Flash using the command:
Code:
fastboot -i 0x2c3f flash boot boot.img
4. Factory reset. (This isn't required if your Robin is already unecrypted and you simply want to update your /boot)
Note: If you skip this step, your phone will remain encrypted.
5. Reboot
Rollback:
1. Re-Enable encryption from Settings -> Security -> Encrypt Phone
2. Flash the stock boot.img
Credits:
@reddv1 for the original modification instructions (adapted from Nexus 5X) and @osm0sis for AIK
----
Disclaimer: Disabling encryption on your phone *will* reduce it's security. These files / instructions are provided only for those who understand and accept the risks of using an un-encrypted device, and are comfortable with modifying the internals of their phone. I will not be held responsible for any loss or damages occurred as a result of following the instructions and/or downloading the files listed on this page.
Click to expand...
Click to collapse
Boot.img for N108?

Use the modified FED Patcher for the Robin from this thread:
https://forum.xda-developers.com/ne...d-patcher-robin-forceencrypt-disable-t3352006
It worked fine for me on 108. After flashing the latest 108 7.1.1 file from the Razer forums, I flashed TWRP 3.1.0-0, then the FED Patcher, and finally Super SU 2.82.

[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
{
"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"
}
CHANGELOG for 3.2.1-0:
- minui fixes (cryptomilk)
- Better android-8.0 compatibility in ROM trees (Dees_Troy)
- Fix missing library in android-8.0 (nkk71)
- Fix inconsistent SDCard naming (DevUt)
- Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD LINKS:
Current and past versions of TWRP can be found at one of the mirrors below:
- Primary (Recommended)
- Primary (Backup)
INSTALL INSTRUCTIONS:
TWRP install (requires TWRP 2.8.4 or higher already installed):
1) Download the latest version of TWRP appropriate for your device/firmware
2) Reboot to TWRP
3) Hit Install and tap the "Install Image" button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find other alternative installation methods on our website (direct link to your device)!
BUGS:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log to SD, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed.
If your issue is determined to be a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP for Xiaomi Mi Note 2, Tool/Utility for the Xiaomi Mi Note 2
Contributors
joe2k01
Version Information
Status: Stable
Created 2018-04-06
Last Updated 2018-04-06

I really want twrp 3.2.1-1. Miui firmware not Packed in new.dat are not installed on Android 8.

Thank you very much! Very nice to see the official one!

Sorry about the noob question but I'm not sure. Is possible updating with this version without getting the official recovery? Any explanation helps, thank you!

Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Sent from my Nokia 7 plus using Tapatalk

Stransky said:
Hi
I hope someone can help me. I unlocked my Note 2 running MIUIPro 9 (Android 7) and then installed TWRP 3.2.1.0 Scorpio and rebooted into TWRP via fastboot and now my Note 2 will not boit, it just sits on the MIUIPro unlocked screen.
I have tried to transfer the Global MIUI 9 Firmware file to the internal storage while connected via TWRP but the PC keeps telling me the phone is not connected although I can access the root of the phone on the PC and have the drivers installed.
TIA
Click to expand...
Click to collapse
I had the same problem a few days ago trying to recover root after updating to MIUI 9.5.4 and sadly have no idea whats going on.
I fixed it downloading the MIUI firmware to my PC (fastboot option) and used Mi Flash Tool to flash it above the existing one (no wipe) and it booted again normally.
I recently updated to 9.5.5 but I haven't tested yet if now it works. So far I have no clue what I'm doing wrong.
Sorry if my english it's not perfect, hope it helps.

Good morning friends!
I installed Rom Beta MIUI 10 Global 8.7.5 in TWRP 3.2.2
However, the system does not boot even though I'm formatting with TWRP.
Would there be some other method for ROM to reboot?
Can anyone help me with this question?
I install MIUI 10, do the procedure by installing TWRP, restart Smatphone via TWRP, install SuperSU, format the System. But when I restart my Smartphone, it does not leave the startup screen

Thanks a lot man. I've got a minor issue. Mouse cursor in the center for all time.

hi is there any way install twrp in mi note 2 with support of ota update

kmanilpillai said:
hi is there any way install twrp in mi note 2 with support of ota update
Click to expand...
Click to collapse
Always need to flash the full rom instead of ota after installing twrp. Why?

kmanilpillai said:
Always need to flash the full rom instead of ota after installing twrp. Why?
Click to expand...
Click to collapse
If you are referring to MIUI OTAs, those are differently sorted inside(folder wise) the archive... So TWRP will not find the files he needs to read...
Full ROMs are normally arranged inside (folder wise) and that's why you can flash them...

New version available 3.3.0-0 as of 20190412.
No changelog for scorpio, but article on XDA here about changes.
https://www.xda-developers.com/twrp-3-3-0-release/
Maybe useful if you need encryption, or edl?
Been using previous version for Xiaomi.eu with no problems.
Scorpio is actually a really good phone, very dependable, as long as you don't overheat it.

latest version of miui (miui11)
did it the latest twrp 3.3.1.0 work/run/installed fine on latest miui (miui 11.0.2.0) please help me
thanks in advance

I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)

Shok II said:
I can boot the latest version of TWRP (3.4.0) through fastboot, but everytime I tried to install it (whether via fastboot or booted TWRP), it reverts back to mi recovery. Any suggestions? Do I have to install 2.8.4 first? (Please note that the 2.8.4 version image file no longer exists in twrp's site)
My device is bootloader unlocked running on Global MIUI 11.0.2.0 (OADMIXM)
Click to expand...
Click to collapse
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.

cobben said:
Official MIUI will always revert back to Mi recovery.
You have to flash a custom rom if you want to keep TWRP, without rebooting to MIUI.
Click to expand...
Click to collapse
Ah so that's why.
Flashed Lineage 17, and now TWRP is persistent, thank you!
Oh right, I noticed that the display brightness is not working (default is too bright btw), as I slide to the right or left, there is no brightness change, TWRP 3.4.0. Haven't tried the older versions tho. Display brightness settings in Lineage works fine.

[ROM][angler][10.0.0_r40] AOSP 10.0 [2020/07/05]

Install Instructions
Grab our recovery from the OP Post section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.

Changelog
AOSP-10.0 2020705
July Security Patch

Omg .. Pixelboot is amazong ???

Both build folders seems empty right now...

daigoro64 said:
Both build folders seems empty right now...
Click to expand...
Click to collapse
Check again. They should be back.

PixelBoot said:
Check again. They should be back.
Click to expand...
Click to collapse
Google Drive is fine. Thanks!

Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
New here btw, thank you very much!
Click to expand...
Click to collapse
It will not cause any issues

Rodeze said:
Probably a noob question, but how do I know if I have the bootloader, vendor and radio installed? And if they're installed (which I don't know) and I flash the ones linked above, would it cause any issues to my phone?
Click to expand...
Click to collapse
Bootloader and radio are installed for sure by default. You can check their versions starting the device to bootloader.
If there is a Vendor mismatch is show to you as soon as you enter the home.

if I am doing a clean install is it necessary to flash Gapps ?

nueloc said:
if I am doing a clean install is it necessary to flash Gapps ?
Click to expand...
Click to collapse
No. You can either flash or not flash GApps.

I just wanted to chime in and Say thank you @PixelBoot! Also does anyone have a recommended stock like Gaaps that replaces all default apps with their Google counterpart?

I hope there's anybody can help me. I wiped system & data & cache, then flashed the rom. As TWRP said - successfully. While trying to boot the system I saw the message that there is "no OS installed". I tried to boot it anyway and it worked. System booted normally, but it's looking very old fashioned. According to system information in the menu it is android 10 aosp. I realized there is no gapps so I wanted to install them. And here my problem starts - while trying to open TWRP from bootloader by choosing 'Recovery mode' it every time boots the system instead TWRP.

1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.

yourrealking said:
1. It seems the official TWRP 3.1.1.0 does not work, and one must use the "FBE" version. Otherwise it will not boot and the recovery cannot decrypt the storage.
2. After each startup, recovery becomes inaccessible. Trying to boot to recovery just boots to the system instead. I had to re-flash the recovery each time.
3. Background music slightly stutters when other sound clip starts to play (for example, a button sound effect in an app) or the screen rotates.
4. Some useful LineageOS features are not present, such as: double-tap to wake, ADB over Wi-Fi, volume button reorient when rotating, scramble number positions for lock screen PIN input, power button long-press for torch.
5. Auto-brightness seems often suddenly to make the screen too dim.
6. Fingerprint sensor is a lot less sensitive than the stock or LineageOS.
Click to expand...
Click to collapse
Here is my takes on these "issues":
1. I have linked the recovery which works in the OP thread both for 4 core and 8 core users. Don't see the reason of flashing the recovery from the TWRP website.
2. Yes. I have noticed this. It is an inconvenient bug, but since recovery isn't used too much, we'll have to deal with this minor issue.
3. Logcat would be appreciated if sent while listening to the music.
4. I'm not sure if you are aware that the reason behind this ROM is for the simplicity and stock AOSP. This is not about being feature packed, but is supposed to simulate a newer version for the Nexus 6P's previous firmwares.
5. This setting is set to the default one of AOSP. No modifications were set unlike that of LineageOS.
6. This should be more or less the same as the experience found on LineageOS as the device tree is very similar.

1. I just happened to already have the official 3.1.1.0 installed before installing this ROM. I read the description and thought that since my version was already 3.1.1.0, I did not have to install a new TWRP. This caused me a lot of problems (wasted time waiting it for to boot, lost all files on the Data, because I had to re-flash the stock ROM). I wrote this to help other users so that the may not experience the same thing I had.
3. I have tried Google Music and another third-party music player and the symptom was the same, so I thought it was a known issue. Anyway, this is not really a big issue, just a small stuttering, and I have disabled screen rotation. I just wrote that to help others to know about it before they decide to move to this ROM.
4. Yeah, I know. I did not write that to complain, or force you to implement those, but as other things, I wrote that to help others to decide before installing. Because changing ROM is a big and time-consuming thing, so it is good to know what it can do and what it cannot do before doing it.
5. I see. I could find a workaround, like creating an app that can modify the dimming degree, or disable auto-brightness.
6. This is strange. I can definitely feel big difference. I had been using LineageOS, and most of the time, I used the fingerprint sensor to turn on the phone instead of pressing the power button. Well, this is not a deal-breaker. I just have to put my finger one or two more times or wait one more second till it gets unlocked.
Thanks for the ROM. So far, for me, the feature I can get from Android 10 outweighs the downsides above. I had been stuck at Android 8 for over two years, and it was boring.

Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here

zzitam said:
Is it normal that my google bar looks like this?
link: https://www.fotosik.pl/zdjecie/7bfdf769a6834334- sorry for the link, but I've got some issues while uploading photo here
Click to expand...
Click to collapse
Yup, completely normal.

Can’t modify the system in any way e.g copying Pixel Launcher to system
Is this because of data encryption?

BlackShark3S ROM or Recovery do you have? [Resolved!]

I know it's out of place, but I'm posting here because it's not registered this device with XDA. Forgive me.
I have a BlackShark 3S, but I can't update it because it broke Recovery.:crying:
Therefore, BlackShark 3S Full OTA or Recovery dump is required.
If you have it, would you please share it?
Thank you for reading.

Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.

Sorry xda was not allowing me to upload for whatever invisible reasons. it seems to have worked after 200 attempts but 7z is not allowed (its smaller xda!) so i renamed to .zip. Just rename it back to KLEN2009280CN00MQ3TWRP_3.4.2B_repack.7z and extract it....

Hi @wertus33333
I saw it now.
I'll try it now.
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
That's really true.They also don't provide source code of linux kernel. (You are also mentioned here. https://forum.xda-developers.com/t/...l-and-up-to-date-china-rom-downloads.4197717/)
I was saved because you were there. Thank you.

koumaza said:
...
I was saved because you were there. Thank you.
Click to expand...
Click to collapse
Happy to help. So it worked out?

wertus33333 said:
Try the following:
1. Unlock bootloader (if not already) https://forum.xda-developers.com/t/blackshark-3-3-pro-3s-unlock-bootloader-files.4141537/
2. Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview
3. Get Fastboot https://developer.android.com/studio/releases/platform-tools
4. Flash my fixed (updated with new bs3 and 3s kernel) TWRP from the attachment (fastboot flash recovery_a *Link to the downloaded TWRP image* and fastboot flash recovery_b *Link to the downloaded TWRP image*)
5. Boot to recovery (fastboot reboot recovery/fastboot boot *Link to the downloaded TWRP image*)
6. (recommended, not necessary) wipe all partitions in TWRP/Factory data reset/format as F2FS (updated it)
7. plug Phone to computer, copy the KLEN2009280CN00MQ3.zip from 2. to internal storage
8. install the zip in TWRP
9. (optional) after install, reboot to fastboot and flash TWRP again (if you don't do that you will have stock recovery)
10. boot the system
Other option:
instead of 2. Find the exact rom you have on your device https://pan.ydxby.com/刷机包/黑鲨3/
4. Extract the payload https://forum.xda-developers.com/t/guide-payload-bin-install-ota-zip-without-twrp.3865319/
5. install the recovery by fastboot flash recovery_a *Link to recovery.img* and fastboot flash recovery_b recovery.img
11. Tell me if sth worked for you so the next one with this problem sees
12. never buy a phone from someone who does not provide official stock ROM downloads/bootloader unlock again.
Click to expand...
Click to collapse
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again

LuigiHacks said:
Thanks a lot! Working perfect!
Some comments what I found:
- After flashing ROM, safety net fails, all points
- Rooting without any problem
- Magisk Hide working well for that apps wich doesn't work if detect root
- Smali Patch not working for spoofing in PoGo
- I used this method because after unlock mi BS3S couldn't even once, login into google account, now can login anytime
Still have to find the way to make smali patch works, but at now looks fine
Thanks again
Click to expand...
Click to collapse
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD

wertus33333 said:
Happy to have helped,
-Maybe safety net fails bcs its CN beta rom
-If you only need location spoof you could try enabling dev options and selecting a mock location app from aurora-/playstore/F-droid no idea if it works with PoGo tho
to further optimize the ROM you could disable some of the bloatware with a magisk system app disabler.
would also be quite interesting if GSI's work (so we would have multilanguage support on nice interfaces with newest CN firmware...) but i filled that 256GB and backups take ages without USB3.0 xD
Click to expand...
Click to collapse
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards

LuigiHacks said:
Hello my friend, you deserved a cold beer
I flashed back KLEN2009280CN00MQ3, flash noverity zip, root magisk, smali patcher + spoofing signature, full Google apps and now everything works perfect, sing in all my accounts, magisk by passing safety net and spoofing PoGo without issues. Really thanks for your help.
One last question, do you know how to lock apps working in background and holding his reference in the notification bar? (Even when you release memory closing apps) it's for the joystick that am using.
Regards
Click to expand...
Click to collapse
nice.
so you want the app to stay active in background? remove it from battery optimizations (not sure if cleaning recents will still clean it but the system won't stop it)
also check the app permissions of the apps you want to keep in notification bar maybe there is an option somewhere

safety net passed in beta
{
"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"
}

And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD

koumaza said:
And I recommend litegapps
LiteGapps
Download LiteGapps for free. LiteGapps is a custom gapps which is ,small, friendly and complete. LiteGapps is an Custom Gapps for smartphones, tablet, desktop, free and open-source software. by providing complete, stable support and several additional features.
sourceforge.net
It works systemless xD
Click to expand...
Click to collapse
i recommend no gapps most apps "requiring" play services work perfectly without (they are telling different stories tho xD) and there is aurorastore

I've seen it, it's awesome!
Unfortunately, I need a Google Play license, so I'll use both.
And I just tried it, and the app is amazingly complete!
I will now use the aurora store to manage my apps.

Thanks for the post. Just got my BS 3S, i would like to root it and debloat most of the apps. Also is there any way to change the launcher? I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2. Thanks

I tried in the settings, default apps, it says cant set because the launcher that Im trying to use is not allowed my JOYUI, Im trying Nova and Lawnchair 2
Click to expand...
Click to collapse
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.

koumaza said:
Try installing and using quickswitch with magisk.
Then you can change the SystemUI native launcher.
Also, CustoMIUIzer is an interesting app so please try it.
Click to expand...
Click to collapse
My BS 3S is not yet rooted, can you guide me?

hello can update
Download https://pan.ydxby.com/刷机包/黑鲨3/KLEN2009280CN00MQ3.zip?preview ??
Can't download now

iampatricktan said:
My BS 3S is not yet rooted, can you guide me?
Click to expand...
Click to collapse
I write the method I performed.
First, one thing to keep in mind is that the BlackShark 3 and 3S are partially compatible.
1. Unlock Bootloader.
Follow This Thread.
BlackShark 3/3 Pro/3S unlock bootloader files.
This unlocking method was researched by myself, so I bought two machines to study it. I know that many Chinese can unlock the Bootloader, but they are unwilling to announce it. They charge high unlock fees to unlock for users in need. This is...
forum.xda-developers.com
2. Flash Magisk from TWRP
TWRP-LINK: https://mega.nz/folder/KU8DTZhR#M2YjCHUrmupBkovTam2HtQ
If you don't know what to do for, please ask me.

Development [Recovery] [A325x] [Stable-ish, Unofficial] TWRP 3.7.0_12.1 - Galaxy A32 4G

{
"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 <not_my_phone.h>
#include <std_disclaimer.h>
/*
* 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.
*/
TWRP 3.7.0_12.1 - Samsung Galaxy A32 4G
Current Status: Stable-ish
Supported Models:
SM-A325F: tested by @Long266 .
SM-A325M: tested by @Melky777 .
SM-A325N: not tested.
Bugs known so far:
TWRP cannot decrypt userdata if you set lockscreen. (one said it works, other it doesn't, so idk I'll just leave it here, YMMV)
Flashing anything shows many "unlock" red lines. (They are currently harmless by our knowledge).
USB-OTG
<!> There can be many more bugs unknown to me and testers. Report as soon as you face problem.
<!> PSA: I don't have the device to verify some of these bugs.
Download:
TWRP (3.7.0): https://github.com/almondnguyen/twr...a32-20230208/TWRP-3.7.0_12.1-a32-20230208.tar
Samsung USB Driver: https://developer.samsung.com/mobile/android-usb-driver.html
Odin (3.14.4): https://samfw.com/Odin/Samfw.com_Odin3_v3.14.4.zip
Disable VBMeta: https://forum.xda-developers.com/at...236537/?hash=f7249adaefe16f3aeac3256a63063f0a
(Optional) Root using Magisk: https://github.com/topjohnwu/Magisk/releases/
Install:
If you have TWRP or any custom recovery installed and bootable, you can upgrade instead; Look below.
<!> the installation will require WIPING DATA. You will also lose access to all Knox-based solutions like Secure Folder.
Backup every precious data you have on your phone.
<!> PC is required. Windows is preferred. (You probably know what you are doing when using Linux/Heimdall. We don't talk about Macs)
Unlock Bootloader:
Go to Settings > About Phone > About Software. Tap build number (10 times) until "you are now a developer" toast shows up.
Go back, go to Developer Settings.
Turn on OEM unlock toggle.
Turn off your phone, hold vol-up + vol-down, then plug in charging cable (please don't use 3rd-party charging-only cable, it must have data transfer capability).
Your device will boot into download mode with a warning. Accept it.
Hold volume-up until the phone shows the bootloader unlock panel "Unlock Bootloader?".
Press volume-up again. Now your phone bootloader is unlocked.
<!> It will now begin the process of wiping data. Let it do its job.
‎
When it reboots to OS, finish setting up your device.
Double check to make sure OEM Unlock is still ON.
‎ ‎
Preparing for the installation:
Download everything above onto your PC.
Install Samsung USB Driver.
Open Odin.
Connect your phone to your PC. There should be a COM entry on the top.
Make sure your phone is in Download Mode. (see step 4 of section Unlock Bootloader)
Make sure that OEM LOCK and REACTIVATION LOCK on your screen show "OFF". If it's not off, DO NOT PROCEED ANY FURTHER.
<!> For those with lock ON, use your device for 7 days without rebooting once. Then check the locks above again.
‎
Installing:
Ensure phone is in Download mode.
In Odin:
Load in Userdata: VBMeta_disabler.tar file.
Load in AP: TWRP TAR file.
Prepare yourself. keep your hand on Volume-up and Power button (don't press yet).
In Odin, press Start. It will flash, then reboot. When the screen turned off, quickly press Vol-up and Power button to boot to recovery (this should take about 20~30 seconds).
<!> You should have TWRP up and running now.
‎
Post-Installation:
MUST: Trigger Multi-disabler.
In TWRP, go to Advanced > Terminal.
Type multidisabler, then enter. If it fails with something about vendor free space, run it again.
Run multidisabler again.
Go to main screen. go to Wipe > Format Data, type yes then swipe.
Reboot to Recovery. Now you can do other stuff.
Should: Backup all vital partitions:
In TWRP, go to Backup
Backup: EFS, Modem, NVRAM.
Enjoy: Reboot your phone to have a rooted stock, install custom stuff or do whatever you want.
Upgrade:
<!> Use when you already have any custom recovery installed (TWRP, SHRP, Ofox and the likes)
Download the tar recovery image, then extract it to get recovery.img
Copy it to phone, then reboot to TWRP (Combo is Power + Volume-up)
Go: Install > Install image > select recovery.img file > select Recovery
Swipe to confirm flashing.
If success, reboot to recovery.
<!> You can also use Odin to upgrade, the steps similar to the Install section. All Post-installation, if already done, is unnecessary to do again.
GSI and related stuff:
GSI should be directly flashable now. Big credit to @Long266
Install TWRP, do all the instructions.
Download a GSI. Phh's is a good start.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
If downloaded a compressed file (the extension is not .IMG; e.g: `gsi.img.gz` ), extract it to get an IMG file. Copy the IMG file to your phone.
Reboot into TWRP.
Tap Install > Install Image > Select your GSI .img file.
Select System Image, then flash.
If previously you were on stock, Wipe > Format data.
Reboot System.
Profit.
Source codes:
Kernel: https://github.com/long266/android_kernel_samsung_a32/tree/s
TWRP device: https://github.com/almondnguyen/twrp_device_samsung_a32/tree/twrp-12.1
Credits:
Devs involved in the making and maintaining of TWRP, twrpdtgen, Magisk and base software.
All the Testers.
@Long266 as tester, collab-dev.
@ianmacd for multidisabler.
@afaneh92 for a32x base tree and MTK-Samsung multidisabler.
@dronkit and @Mighty_Rearranger for Magisk-IMEI fix on MTK devices.
@klfld for GSI installation guide.
Older Release(s):
TWRP 3.6.2_12.1-20220703: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/tag/TWRP-3.6.2_12.1-a32-20220703
TWRP 3.6.2_12.1-20220528: https://github.com/almondnguyen/twrp_device_samsung_a32/releases/twrp-3.6.2_12.1/
TWRP 3.6.1_11: https://github.com/almondnguyen/android_OTA/releases/TWRP-3.6.1_11-a32-B20220324
Footer Infos:
Status: Beta
Current Stable Version: 3.7.0_12.1
Created: 2022-03-24
Last Updated: 2022-07-03

chmod 550 /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI must run on OS, not TWRP, since TWRP cannot mount /mnt

I can't install large IMG files to internal memory? For example a gsi?

Melky777 said:
I can't install large IMG files to internal memory? For example a gsi?
Click to expand...
Click to collapse
I should clarify that I don't own the device and all the testing was/is done by @Long266 .
These specific questions should be inquired to him instead (on his thread here: https://forum.xda-developers.com/t/...hawk-recovery-project-3-1-2021-03-24.4420469/ ).
Anyways, the bug that you are mentioning means that you can't flash images FROM internal SD card. GSI and image stuff should be flashable from other places like external SD or cache. Zip files are so far working as intended (as is they are flashable from anywhere).
To be fair, there could be flaws in his testing methodology and you should try it yourself.

Thanks Bro
I will owe the test of the A325M. I have no SD card at the moment.

Build 2022-03-25 changes:
Add backup entry for NVRAM, so in case Magisk messes up you still have a working copy intact.
Fix flashing image causing file size exceeded limit.

Updated TWRP Link, previously pointing to dead end.

It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
can u send recovery.log ?

Melky777 said:
It worked fine on the A325m, but I had NULL errors when I went to do some actions, and the USB OTG is not working!
Click to expand...
Click to collapse
just skip NULL errors

How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?

YellowSM said:
How to update the TWRP version if it is already installed?
Is it enough to just flash the new TWRP version in Odin?
Or do I need to do the same steps as with the first installation (i.e. multidisabler, etc)?
Click to expand...
Click to collapse
You can use the "install Image" under TWRP.
From the <!> For more info part, download .img file instead, copy it to your phone. Then go to TWRP > Install > Install Image > select TWRP img > select Recovery to flash.
If you've done, Post-installation steps are unnecessary to do again.
edit: upgrade section added to main post.

How to deactive KC Client and
Knox Enrollment Service?

Hi, I wanted to try a GSI with this, is it safe to try it? Thanks for developing this TWRP, I can help with testing too.

Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.

klfld said:
Okay, I tested flashing phh's AOSP GSI, TWRP doesn't have the entry to flash to the dynamic partitions (system, vendor, product, etc). It can flash only to the super partition. Tried to flash the GSI there just in case, but i get a bootloop obviously. Restored successfully through ODIN. I wont test magisk because I don't want to lose IMEI.
Click to expand...
Click to collapse
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22

Long266 said:
can u send recovery.log ?
Click to expand...
Click to collapse
On the same day I removed the twrp and blocked the bootloader.

Melky777 said:
try flashing via fastboot!
I saw a video of a Brazilian doing it on the A22
Click to expand...
Click to collapse
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
To flash the GSI you have to rename the .img file to system.img, put it in the same location than the zip and flash the zip. I have the scripts inside the zip to check if it didnt do anything weird and the source code seems safe, tried two GSIs today.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
For file transfer i'm using ADB with this tool, it's even faster than MTP somehow Python ADB File Explorer
EDIT: Uploaded vendor.img with the overlay for this device, ill push the changes to github later.
Download here: vendor.img

klfld said:
I could install the Lineageos 19.1 GSI! I had to use this zip as a workaround ChonDoe_Flasher.zip, that allows flashing dynamic partitions even if the TWRP doesn't. I also made a treble overlay for this device (vendor.img), that fixes power profiles and all this stuff, ill upload it now if anyone is interested.
What doesnt work with the Lineage GSI or phh's AOSP is MTP and the fingerprint reader. Also i can't get encryption to work, the GSI crashes if i don't use multidisabler to remove encryption from the fstab. Everything else works flawlessly from my testing.
Click to expand...
Click to collapse
Very good job!!!
Makes a topic, I think I'm not the only one who wants to install a GSI.

Develop Bugs

welcome