Database Develop

[boot.img] Patched boot.img files & patching tool

Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
https://www.mediafire.com/folder/zx0167qqaknc3/Redmi_7a_patched_boot
Note: The one for xiaomi.eu is custom rom, not stock EU.
If you can't find a patched boot.img for your version, you can also patch it yourself with this tool:
http://www.mediafire.com/file/c5e0idf6cy5ap25/patcher.7z/file
(follow instructions in readme file; credits to Russian 4pda forum)

Where i can find xiaomi.eu ROM for this device?

NV-Dev said:
Where i can find xiaomi.eu ROM for this device?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=4349826312261652844

Can you please upload patched boot for 11.0.2 indian rom???

Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?

anonymousfun122 said:
Can you make a patched boot for the Mokee rom because when I try to patch it with the patcher it has ramdisk error. Can you help me?
Click to expand...
Click to collapse
Here for you
Mokee_boot.img
{
"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"
}

Not working for me
Auto Reboot to recovery

It worked
sjcbank said:
Here for you
Mokee_boot.img
Click to expand...
Click to collapse
Thank you so much !!! It worked instantly . I was trying weeks to make magisk working on the mokee rom.
Thank you !!

Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.

Tenome7 said:
Hey,
I have MIUI v10.2.6.0.PCMINXM(Indian version), actually I downgraded to this version. Please help me install Mokee on my device. Enlist all the steps I need to take from scratch.
Your prompt response would be really appreciated.
Click to expand...
Click to collapse
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.

sjcbank said:
Any rom version can install mokee. It's very easy, anyone can do it.
I am 60 years old, I am Vietnamese, I do not know English, all instructions are available online, I use Google, Google Chrome and Google translate.
Click to expand...
Click to collapse
I've been toying around with Android since it's Lollipop versions, rooting them, intalling custom ROMs etc. Probably 6 years. More than 7 devices.
As far as installing a custom ROM on this phone (Redmi 7A) is concerned, the different versions, like Indian, Global have different drivers or HAL's.
So, after successfully booting up into MOKEE OS on my variant 3-4 times, Torch, Audio, Video, Calls...... Nothing worked.
And to be very honest, there was nothing mentioned about this in MOKEE OS thread, as to which version of this device is not compatible with the ROM. The only reason I messed up was because the introduction of GSI ROMs has made the custom ROM creation process easier, but introduced a ****load of work in some devices, and ending up causing trouble.
This was the reason I requested all the steps in the thread so I could verify if I was missing some important step as far as the Indian variant is considered.
But thanks to everyone, I successfully booted Mokee ROM with everything working on my variant, including superuser privileges.
Also I messed up partitions in TWRP, and ended up with only 22gigs of Internal storage available, lol.
Thanks.

Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.

Ok I figured it out, AFTER you flash the patched boot.img you need to format the data partition, you'll loose all your data, however the ROM will boot.
I'm running Android 10 mokee os, more stable and no bugs compared to lineage os 17 rom

cg730620 said:
Here you can find several patched boot.img files for various stock rom system versions of Redmi 7A.
Click to expand...
Click to collapse
Hi
Do you have a patched boot.img for my 7A 11.0.18.0 (PCMEUXM) ?
Thanks

axy_david said:
Tried @Tenome7 patched boot file for latest nightlly mokee OS 10, it bootloops, patched my own boot file, it still boot loops.
It seems impossible to get magisk working in mokee OS.
Click to expand...
Click to collapse
Sorry for being so late to reply here. I would suggest using MIUI v10.2.10.0 as the base over which the Mokee OS needs to be installed.
As far as root is concerned, I tried Magisk but it gave me bootloops every time. As an alternative to getting root, I flashed the AddonSU installer which I downloaded from the Mokee Official site. You would just need to find it on the website.
I hope this helps. If you have further doubts, I'll stay a bit more active here. :fingers-crossed:

I want to unroot, but when i choose restore images in magisk manager it says stock backup doesnt exist. I downloaded the patched boot and stock boot.img prior to rooting, i didnt use magisk to patch the stock boot. What do i do now, i want to unroot and install ota on my xiaomi mi a3.

Can anybody help me?
I need the new version of patcher and the creator's website doesn't load me correctly.

Anyone have got pine 11.0.7 global patched boot image??? Cz yaalex patcher is down showing internal error

redmi7a
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you

I asked the developer about a similar issue with the downloadable patcher, and he suggested me to try with the online one, which is more up to date.
https://patcher.yaalex.xyz/
romam suchanek said:
Hi
carried out
bootfromrecovery.bat - Reboot to recovery, connect to PC, install adb driver and run this file. this will extract boot.img from running phone, patch it on the fly and flash back patched boot.img
..but it didn't happen
* Requires internet connection. (it downloads latest Magisk release during process)
..I still don't have root
someone will help
Thank you
Click to expand...
Click to collapse

[RECOVERY][UNOFFICIAL] TWRP 3.5.2 for Xperia 1 II

Disclaimer
Builds are provided AS-IS without warranty or repair. I am not responsible if you brick your device.
About
I was using the existing TWRP build that's been floating around and noticed it had a few issues, so I made a device repo and rebuilt an improved version.
Noteworthy features:
English language defaults
Added support for microSD
Added support for USB storage mounts
Added support for userdata encryption
Support for MTP and ADB
Added backup options for DTBO, verity meta, OEM partitions
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
Downloads are available at https://github.com/shinyquagsire23/twrp_sony_pdx203/releases/
Flashing
Flashing is only supported on phones which have an unlocked recovery and verified booting disabled!
Code:
#!/bin/bash
# Reboot to fastboot
sudo adb reboot bootloader
# Flash recovery img
sudo fastboot flash recovery recovery.img
# Reboot to recovery
sudo fastboot reboot recovery
Source Code
Source code is uploaded at https://github.com/shinyquagsire23/twrp_sony_pdx203/. I also provided some brief compilation instructions in the README.md for anyone interested.
Special Thanks
Thanks to Sjll for twrp_sony_pdx201, which I based my repository on.

Thank you, I will be testing this weekend.

Very cool, thanks for sharing.

You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!

Junior-J said:
You my friend are a life saver. I installed a magisk module (riru sui) that bootlooped my device. Tried every damn near every option to remove that module...couldn't gain access via ADB as my device was coming up as "unauthorized". I fastboot flashed your twrp successfully....got into file manager and manually removed the module..and my phone booted back up. THANK YOU!
Click to expand...
Click to collapse
thats why older Samsung phone running android 7 and lower are considered the safest. they have a inbuilt download mode to recover their software incase of a bootloop. but xperia phones aren't the hardest to root either since they are one of the most used. only problem is that some xperia phones will have their recovery menu and commands etc in chinese/japanese depending where you bought them.

Thanks for sharing，Great Works ~!

Does this not support decryption? I wasn't able to get in with my password using this version of TWRP, but I was with OrangeFox.

Can you give me build.prop from Sony xperia 1 ii Please? give me in my mail or telegram : t.me/Info_Shakib [email protected]

Seems there is a fix for fastbootd @ https://gerrit.twrp.me/c/android_bootable_recovery/+/2910
If I have time next week I'll try patch and make PR shinyquagsire23 unless someone does it first..

Can someone tell me how can to compile twrp recovery for xperia 1(j9110). I need some guidance. Thanks.

TWRP flashed on xq-at51 android 11 without any issue, thank you for the guide

Is it work for experia 1 iii ???

recovery not booting up after flashing stock android 12 january patch, the screen keeps getting splashed with the logo of twrp

Ask, Pixel Experience Plus 12.1 v413 is only img after decompression, can only use TWRP to flash the machine, 1ii 12 has no TWRP available, whether to downgrade 11, use TWRP to flash .img, which partition to flash into TWRP, still trying to learn, Please enlighten me.

Thanks so much. Exceptional.
Works on XQ-AT51 (Europe, dual SIM) . Flashed twice to _a and _b. on Android 11.

I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help

marcvie said:
I'm having the same problem, whenever i boot into recovery, TWRP logo just keeps flashing, like it's crashing , android 12 btw, any other possibilities to root the 1ii? thanks for the help
Click to expand...
Click to collapse
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/

Gunseng said:
To my knowledge, you don't need TWRP to get ROOT. This guide should help: https://forum.xda-developers.com/t/...re-and-gsi-rom-flashing-without-twrp.4119493/
Click to expand...
Click to collapse
Thanks for the reply, that will be handy for flashing, but i eventually got my 1ii rooted using this guide: https://www.getdroidtips.com/unlock-bootloader-root-sony-xperia-1-ii/

If u r on Android 12, just use recovery of this thread:
[ROM][Officiall][pdx203][12.1] LineageOS 19.1
LineageOS is a free, community built, aftermarket firmware distribution of Android 11, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
Not twrp but almost the same (lineage).
Flash recovery, then "fastboot reboot recovery"

And this is really working on a rooted stock rom ?

Question Recovery A/B

Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?

Devione said:
Hi everybody,
I just got a ZenFone 8 16GB ram, I recently unlocked the bootloader and flashed TWRP.
So I've managed to flash LineageOS, but I'm not sure exactly what is going on. I wasn't able to flash the usual way via TWRP, but sideload via ADB. When reboot to Recovery, it reboots into Lineage Recovery.
I am somewhat aware that there is an A/B partition and this is my first A/B device, is there any way I can access TWRP? Or it has to run Lineage Recovery? Any way to only run 1x Recovery?
Click to expand...
Click to collapse
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.

HyperCriSiS said:
As far as I know, Lineage overwrites TWRP with its own recovery, so you have to flash it again.
Click to expand...
Click to collapse
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot

Devione said:
Hey thanks for the quick reply. I wasn't aware that was the case.
So this means that my "A" slot is now vacant and I will now need to reflash TWRP yes?
Thanks for your time.
Edit: Lineage Recovery shows that it's on "B" slot
Click to expand...
Click to collapse
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).

Freak07 said:
A/B (Seamless) System Updates | Android Open Source Project
source.android.com
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
If you update the firmware on your device, it will flash new update to the opposite slot. usually a firmware.zip that is let´s call it a "full firmware.zip", such as lineage or the stock rom has recovery included. so you´re ending up with TWRP being "overwritten" in case you flash an update.
Unpack the payload.bin in any of those full firmware.zips via payload extractor on your pc. You´ll see all the .imgs contained. All of those partitions will be updated on the opposite slot if you flash the full firmware zip.
That means boot.img will be overwritten (magisk will be gone if you don´t choose the install magisk to inactive slot after OTA in magisk manager before rebooting the phone after the stock firmware.zip has flashed for example).
Click to expand...
Click to collapse
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?

Devione said:
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I don't know, but I guess if LOS supplied in form of payload.bin instead of many .img files then I think it's better to unpack all img's from there replace recovery and patched boot and "repack" it back if it's possible. At least that was the way I did that on Samsung phones. But there was only .tar archives, so that was much easier than .bin to repach which I think you will need some additional software.

Devione said:
Cheers thanks for your reply and explanation.
Appreciate your efforts and time taken to explain. Thanks for your time.
EDIT - just to be sure, if we were to update the firmware on our devices while running say LineageOS, the payload.bin will need to be extracted and the relevant files flashed correct?
Click to expand...
Click to collapse
I'm not sure about the current situation on unofficial lineage. I'm also not using it on my zf8 but from others phones, which should apply to zf8 as well.
I'm pretty sure official lineage builds have an inbuilt OTA mechanism. Unsure about the unofficial one. Better ask in the lineage thread.
However, you can boot to lineage recovery and flash the lineage.zip from there without wiping the device if you were previously on lineage and are just updating.
If you want to be rooted you need to patch the boot.img from this update (extract from payload.bin if not already available) and flash it via fastboot after updating.
By telling you to extract payload.bin I just wanted to visualize what's being updated during flashing a firmware.zip so you have a better idea how it works.

Hi there, thanks for the replies.
Sorry I wasn't being clear. By firmware updates I meant the official Asus firmware updates which are zips containing payload.bin.
What I really meant to ask was the possibility of updating the Asus firmware when still running a non Asus ROM eg LineageOS.
Earlier on I've tried to reflash TWRP over the existing LineageOS recovery and it didn't seem to work so not sure what I did wrong there. Device still boots to LineageOS and running Lineage Recovery on "B".
Thanks guys for your time and replies.
Edit - the goal at the end of the day I guess is to
1. run a custom ROM (LineageOS, GSI, Omni etc.)
2. run TWRP
3. able to update Asus firmware when available

hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
{
"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"
}

[email protected] said:
hello everyone , sorry if I posted in the wrong place, searched and did not find,
ANDROIDE 10 A/B what is the name of the partition that is recovery?
guys, I have a k41s, on android 9,it went into recovery, it ta with root,,
I wanted you to tell me , on which partition the recovery is located, please.
View attachment 5478501
Click to expand...
Click to collapse

[ROM][12][OOS CAM] CherishOS 3.4 for OnePlus 8T [OFFICIAL][2022-02-16]

{
"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"
}
CherishOS is an AOSP based rom focusing on Unique and Smooth UI with handy features. CherishOS is a reborn of pie based Dot-ExtendedOS.
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
CLEAN FLASH(for first install) :​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Format Data & Reboot to System
2nd Method(Using Sideload):
Note: You can't sideload with any recoveries, only some recoveries support sideloading this rom. I have provided one below
1. Download ROM zip from sourceforge and put it in adb folder
2. Download recovery.img from here
2. Put it in the folder where you have your adb files, and then open a terminal and execute the command
Code:
fastboot flash recovery recovery.img
3. Reboot to recovery
4. Choose "Apply update"
5.
Code:
adb sideload rom.zip
6. Reboot to recovery
7. Factory reset / Wipe all data
8. Reboot system
Dirty Flash(to update):​1st Method(Recommend):
1. Reboot to bootloader
2. Download Fastboot Enhanced Tool
3. Open it, select your device, reboot to fastbootd
4. Download the ROM zip from sourceforge & extract it and find the payload.bin file inside it.
5. Flash Payload.bin via the tool. Reboot to recovery after you have flashed the rom.
6. Reboot to System
2nd Method(Using Sideload):
1. Download ROM zip from sourceforge and put it in adb folder
2. Reboot to recovery
3. Choose "Apply update"
4.
Code:
adb sideload rom.zip
5. Reboot to recovery
6. Reboot system
Download ROM(Gapps)
-Lineage OS
-AOSP
-Pixel Experience
-DotOS
- @1249131356
- @chandu dyavanapelli
- Others who I forgot to mention
Based on Android 12.0
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Fingerprint reader
NFC
Lights
Sound / vibration
Known issues
You tell me? (none)
Cherish-OS Source
Kernel Source
Telegram Group
REPORTING BUGS!
As soon as the problem occurs, take a logcat!
for more READ THIS
​CherishOS for OnePlus 8T
Device: kebab
Maintainer: @Amsal1
Build Type: Official
ROM Kernel: Linux 4.19.225
Based On: AOSP
Android OS version: 12
Security patch level: January 2022
Version Information:
Status: Stable
Current Stable Version: 3.3.5
SELinux Status: Enforcing

Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!

Reserved

Amsal1 said:
Build Info:
- Inbuilt OnePlus OOSCam, Gallery and Dolby
- Oneplus Device Settings with TouchGestures added
- Safetynet passes by default
Screenshots Attached to the post!
Click to expand...
Click to collapse
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why

Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake

Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use

Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing

Zekedw said:
Can anyone help me? Just got this device and wanted to try some android 12 roms. I was under the impression that oneplus devices would be easy to flash too. However this A/B partition thing is a real pain. Can't get anything flashed and all of the tutorials don't work. Used fastboot enhance, tried ADB sideload (doesn't work, some kind of version doesn't matc client or something) and twrp that I used to use on my other devices is a headache to use
Click to expand...
Click to collapse
The main thing you need to know for this device regarding A/B is that you need to have the latest firmware from Oneplus on both slots.
Run all your updates and then find the Lineage Wiki for kebab. There is a script there that will copy firmware to both slots so you can start flashing ROMs.

Zekedw said:
Well I guess that's it for me and modding this device then. I have read countless posts and watched videos and followed them step by step and still no progress. Not looking to be spoon fed, just trying to see if there is something I might me missing
Click to expand...
Click to collapse
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.

kjslabber said:
A lot more involved than just flashing a rom, such as "do you know how to repair you phone when it bootloops?" It will eventually happen. What partitions you should backup before flashing a rom. Sorry, that's just the reality.
Click to expand...
Click to collapse
I have actually repaired it from a boot loop many times. I've been modding and flashing for many years. It's just that this is my first a/b device and despite all the tutorials and research I've done it still hasn't worked. I'm not giving up tho, just wondering what I'm missing. I actually did get a couple roms to work. But I don't know why I'm not getting them to work now. More research I guess...

double tap to wake works while aod is on?

I have many problems trying to install these roms on my phone using sideload or twrp no matter what recovery I use. End up dumping files from payload bin and flashing individual files using fastbootd. Only handful of files to flash, not like oos rom. Almost foolproof. Just make sure you reboot to recovery and format data before booting to system.

GbnrVR said:
Question does face unlock ACTUALLY work because last time I saw a A12 rom say it has face unlock it was a mistake
Click to expand...
Click to collapse
No. I mistakenly wrote face unlock in a hurry which is removed from OP now

kjslabber said:
Every a12 rom pretty much has it's own method and recovery to flash with. You just have to do your homework and read the op's for each rom. Do a little research on how a/b partitions work. Nobody will spoonfeed you how to do. If you have problems almost every rom has telegram channel you can ask on?
Click to expand...
Click to collapse
Yes. That is because A12 latest standards uses a different assert verification process (which is used to detect the device before loading packages into the recovery). TWRP and old recoveries are still using old asserts from A11 standards. I don't like to implement the old assert thus you can either flash using any fastboot installer script or fastboot enhanced. One tester confirmed me that lineage recovery also worked fine for him but I still recommend fastboot installer mode.

Muntasir Mahmud Saif said:
double tap to wake works while aod is on?
Click to expand...
Click to collapse
Yes.

Ivanherrero said:
I like the rom, but I don't know why the color of the letters in dark mode are not white, it is in a pink tone and I don't like it, that's why I change the rom, I have tried to modify it but it never goes blank
the only rom that doesn't happen is in the dev one, I don't understand why
Click to expand...
Click to collapse
Have you tried changing monet colour through Cherish Settings->Themes->Custom Color?
Can you give more details, since I can't reproduce the issue and many of my testers have tested it for days and have no issues with changing monet colours.

Amsal1 said:
Yes.
Click to expand...
Click to collapse
can not find any payload.bin in the folders after extracting

All you need to do is change wallpaper. Color is controlled by wallpaper theme in a12.

Muntasir Mahmud Saif said:
can not find any payload.bin in the folders after extracting
Click to expand...
Click to collapse
Did you download the zip file or md5?

[ROM][PixelExperience 12.1][A70][FN]

{
"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"
}
View info: https://www.xda-developers.com/pixel-experience-12-hands-on/
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation).
Your warranty is now void!
>I am not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
>You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
What is working?
-Everything is working (also fingerprint; bluethooth; 1 sim/maybe 2)
-File's Download-
>Vendor: https://forum.xda-developers.com/attachments/vendor_a11-zip.5336611/
>Rom: https://github.com/zainullahk/universal-pixelexperience-samsung/releases
make sure to download the arm64-ab-12.0 and not the arm64-ab-vndklite.
!Optional!
>Kernel: https://opensource.samsung.com/uploadSearch?searchValue=A70.
>Magisk: https://github.com/topjohnwu/Magisk/files/7819803/app-debug.zip
-Installation guide-
>Enter recovery (TWPR).
>Press "Wipe"-->"Format Data" -type "yes".
>On PC Extract the rom.
>And copy "Vendor_A11.zip";"PixelExperience_Plus_arm64-ab-12.1-20220613-UNOFFICIAL.img";"app-debug.zip" to the external/internal sd storage.
>First install the vendor follow steps below:
>"Wipe"-->"Advanced Wipe"-->Select Dalvik; Cache; System and Vendor -->"Swipe to Wipe".
>Now click on "Install" then select "Vendor_A11.zip".
>Then go back and flash the rom as "System Image".
--------------------
>!Optional!
>Flash magisk (debug.zip) !DON'T DO OTA UPDATES FOR NOW IF YOU USE MAGISK!
--------------------
>Reboot System and it should work for samsung a70.
(I did't created the rom; vendor; magisk i just have found a way to install the rom onto a galaxy A70).
-Pixel Experience 12 v402-
>New update to pe!
>Check the Updater page on Treble App to OTA update.
>Sync with February sources of PE (give a warm welcome to Face Unlock).
>Sync with AOSP 12.0 v402 by @phhusson.
>Fix permissions on dynamic su binary.
-OFFICIAL SITE-
Home - Pixel Experience
Home - Pixel Experience
download.pixelexperience.org
-COMMENT BELOW FOR ANY ISSUE-

USE THE STOCK KERNEL TO BE SURE THAT THE ROM WORKS!

Is volte working with this rom?

MarvinMod said:
Is volte working with this rom?
Click to expand...
Click to collapse
Yes sure the LTE connection is working!

Topo's said:
Yes sure the LTE connection is working!
Click to expand...
Click to collapse
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
I had read "LTE" and not "VoLTE"

rttxda said:
VoLTE is something different than LTE, it allows you to make calls over the 4G network which is absent in custom roms for this phone
Click to expand...
Click to collapse
thanks! you are right

Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.

Dakshxda said:
Getting "Verifying VBMeta Image error"
Tried flashing with and without Magisk but nothing happened.
Edit: That seemed due to my incorrect TWRP flash. But now I am getting bootloop after install.
Click to expand...
Click to collapse
@Dakshxda remember to have the stock vendor of your device!
Follow my updated guide:https://forum.xda-developers.com/t/rom-gsi-100-working-a70-no-bootloop.4470471/
this 100% work
​

"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+

Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop

removez said:
Hi. After flashing the system, the /system_root partition is not mounted. Can't change device name in build.prop
Click to expand...
Click to collapse
You dont need to change the build.prop..
Why would you need to?

Ive been very busy with work, building a house. I may jave time this evening to flash and confirm Volte working or not.

Can install on a70f?

I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?

MarvinMod said:
You dont need to change the build.prop..
Why would you need to?
Click to expand...
Click to collapse
The Samsung Wear program refuses to work with this firmware. I could change the name of the device and it would work

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
I installed it once crookedly and did not start up was a bootloop. Then I flashed the stock firmware and then this one and it started. But magisk worked crookedly, the /system_root partition was not mounted

So here's what I did:
1. Flash stock via Odin
2. Reboot and then power off, then go to download
3. Flash TWRP 3.6.2
4. Reboot to recovery
5. Follow instructions above
6. Got Vbmeta error so I flashed VBMeta.tar from here
7. Rebooted but now it bootloops
Topo's said:
"Verifying VBMeta Image error" to fix the error you must flash stock firmware and then twpr 3.6.0+
Click to expand...
Click to collapse

Jinetty21 said:
I tried this gsi before but i can't boot. I have to ask it. Firstly, is it a ROM or GSI ? Because Pixel Experience is a GSI and secondly, this post seems like copied from https://forum.xda-developers.com/t/...e-for-a70-all-models-fod-working-gsi.4395073/ and third, who tried and got working ?
Click to expand...
Click to collapse
1)I have wrote the post and i didn't copied.
2)I have tried this and worked whit my 2 devices (Galaxy a70FN;A70MN)
3)It is a generic system image

Moderator Info,
Thread has been closed at OP's request. @Topo's if you decide to progress further with the ROM, please report the first post and request to have it opened. We will be able to open it for you.
Thanks,
Stephen