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
Related
So Guys ROM twrp Root etc Now available for MI max 2. [oxygen 2]
You can Download official ROM from http://en.miui.com/a-234.html
and Flash it with MI flash.
or if you have dead Device follow deep Flashing Guide Here.https://forum.xda-developers.com/redmi-note-3/how-to/guide-how-to-flash-hard-bricked-redmi-t3490055
twrp ported From mido Download Here
Flash with fastboot
Code:
fastboot flash recovery recovery.img
Flash magisk From here https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
in trouble watch video-
Thank you! TWRP worked as intended, installed root manually. Donated as well.
TiMbl4 said:
Thank you! TWRP worked as intended, installed root manually. Donated as well.
Click to expand...
Click to collapse
ok thanks for Donation..
Lineage OS available https://forum.xda-developers.com/mi-max-2/development/linageos-14-1-mi-max-2-t3634864
Great toolkit but I have a couple questions. In the instructions on your site and youtube video it has a step to flash noverity. Is this really needed or is it just a precaution? Also, could I just flash the recovery via fastboot and then just pull noverity and magisk from their source and flash them? I always like to flash things myself the normal way so I understand what's going on.
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
XN Logos said:
noverity is just to protect from bootloop. i use noverity on all Nougat Devices. and also it can't cause any damage to device so don't worry.
correct meaning-
you can Root Your Phone without modified boot.img which is Must Require on Many Devices.
Click to expand...
Click to collapse
Thanks for the quick response. I have one more question. Can I substitute SuperSU in place of magisk? After using the toolkit, I tried to update magisk to the latest version (13.2) using magisk manager but instead it gave an error. It didn't brick my phone or anything but when I rebooted and went into magisk manager it showed the phone was still properly rooted but reported that magisk wasn't installed. Not sure if it's a compatibility issue or not. I also tried flashing the latest version of magisk using twrp and got the same error in magisk manager upon reboot.
At any rate, do you see any problem with using SuperSU instead?
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
XN Logos said:
Flash SuperSu 2.79 make Sure you have a backup because Bricking Change me present.
or try with No verity.
Click to expand...
Click to collapse
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Did you have to unlock the bootloader for installing twrp?
ikecomp said:
Thanks. I restored my phone from the nandroid backup I took after installing twrp and then flashed noverity and supersu and it all worked perfectly. Thanks again
Click to expand...
Click to collapse
unlock with developer rom
XN Logos said:
unlock with developer rom
Click to expand...
Click to collapse
Since 5 days i have been trying to unlock bootloader. Every time I get "Device not bound to account". I have tried everything. Can you help me?? I am already on developer rom..
yes that means You have not applied for unlock, First of all apply for unlock then when you receive Confirmation msg wait 72 hrs, then login mi unlock app with same account and then try to unlock
Magisk not detect root
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I follow all instruction,i flash no verity and flash xnmagisk.zipafter reboot magisk appear like that? Have format but still not detect root, can root manually flash superusu but i want magisk to for hide root. So what next stepp for solve this problem? Let me know. Thanks
Hi guys, any idea why when I flash magisk 14.0 over a fresh 7.9.7 global developer rom I get CTS profile mismatch? It still shows safetynet as passing but android pay refuses to work. Also, is it safe to install OTA updates with magisk flashed?
How to root after flashing the official miui9 ? (my device is rooted miui 8.5)
please help (Device Mi Max 2 )
{
"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"
}
Descendant is a customised Android ROM that focuses on enhancing UX and UI
over stock Android along useful features.
Downloads
Head to the download page. Download the zip and *-boot.img for your device.
Sources
Githubhttps://github.com/Descendant-Devices
Backup internal storage, wiping data will delete everything.
Reboot to fastboot and flash the provided boot.img with the following commands:
Code:
adb reboot bootloader
fastboot flash boot /path/to/*-boot.img
Reboot into recovery using volume and power buttons and select "Apply update from ADB," then:
Code:
adb sideload /path/to/rom.zip
In recovery before rebooting, make sure to factory reset/wipe data on first install. No wipes are needed between updates from Descendant itself, unless specified.
Reboot into the system and you should be good.
But please, mind, we won't support any issue arising from Magisk nor relative modules.
Listing all the additions would be a huge wall of text, that you wouldn't even read.
So, head over the Telegram group and feel free to lurk.
Preloaded applications
Google Apps are included.
Having a bug or not booting for whatever reason?
Look for "How to report bugs" on this post.
Bug reports without logs will be ignored.
@phhusson | @Letzen | @krule031 | @ezio84 | @linuxct
Android OS version: 10.0.0_r32
Security patch level: March
XDA:DevDB Information
Descendant X, ROM for the Google Pixel 3a XL
Contributors
johngalt1, Dil3mm4
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Stable
Created 2020-03-09
Last Updated 2020-03-11
Cool cool some more love coming in
Magisk Question
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
crypto69 said:
Hello. First of all, great ROM, thank you for putting it together and supporting our device! I just picked up the Pixel 3a XL and am getting it configured with my first custom ROM. I installed it this morning and it seems to be working great.
I have a question about Magisk and how to use it with a custom ROM. While I have been using custom ROMs for years on my devices, this is my first attempt to use Magisk on a Android 10 device with the new partition system (without TWRP). I followed the basic instructions for Magisk and was able to get it working on the latest stock ROM but I am unsure whether I need to patch (from Magisk) the included Boot.img file that comes with Descendant or do something else. I tried patching it but when I rebooted after installing via the bootloader, the Magisk app is saying its not installed. Any help you could provide would be appreciated. Thanks again for the great build.
Click to expand...
Click to collapse
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
johngalt1 said:
Myself and most others have done it the same way you have: manually patch the downloaded boot image in magisk manager after setup, reboot to bootloader, fastboot flash boot magisk_patched.img.
I'd recommend trying to patch and flash magisk_patched.img again from the boot image you downloaded.
Click to expand...
Click to collapse
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
crypto69 said:
Thank you. Working now. Turns out, I was flashing to the wrong slot...still learning
Click to expand...
Click to collapse
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
johngalt1 said:
That's great! For the future, try pretending like slots don't exist and just doing fastboot flash boot magisk_patched.img rather than specifying a slot :good:
Click to expand...
Click to collapse
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
crypto69 said:
Yeah, the odd thing is, at least so far, I've been getting "FAILED (remote: Failed to write to partition Not Found)" when not specifying a slot during a flash. So I use GETVAR to figure out where I'm supposed to go and flash there.
Click to expand...
Click to collapse
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
stompysan said:
Update your platform-tools. This is likely due to the change they made a while back to how specifying a partition is handled in fastboot.
Click to expand...
Click to collapse
Thank you, will do.
If anyone wants to install V4A, I can confirm it works on this ROM. Use this guide and follow steps 1-15.
https://www.the***********.com/install-viper4android-android-10-guide/
What version do I have to download for a 3a xl device ?
Benxxx said:
What version do I have to download for a 3a xl device ?
Click to expand...
Click to collapse
I'm not sure but assuming it's the a/b version to download. I also don't see a boot.img on the download page. Am I missing it somewhere?
Hasn't been updated in like 2 months if I am reading it right
DISCLAIMER: I am not responsible for any bricked phones or otherwise but this is how I updated to the latest version.
Flashing backwards has not been tried by myself, use at your own risk.
Only flashing the same version of ROM was tried, global for global.
I tried the local update method that is built into the MIUI ROM, my bootloader is still locked, and you can only use OFFICIAL MIUI ROM's.
{
"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"
}
Sorry guys , I'm don't find a right thread!
I don't know but plz help me .
I'm on stock ROM 12.0.16 global RKFEUXM , rooted an tw recovery !!not decrypted!!
I have on my ex SD card ,the newest Stock ROM flashabl.zip. ,Magisk and the twrp.img.
I don't know now the right steps to update to new with out losing data ,root ant tw recovery .
plz help me with the right steps .
what is needed to format ?
then the steps to flash an boot
thank you
Plz help me!!!
Thank you guys
Jakkomo77 said:
Sorry guys , I'm don't find a right thread!
I don't know but plz help me .
I'm on stock ROM 12.0.16 global RKFEUXM , rooted an tw recovery !!not decrypted!!
I have on my ex SD card ,the newest Stock ROM flashabl.zip. ,Magisk and the twrp.img.
I don't know now the right steps to update to new with out losing data ,root ant tw recovery .
plz help me with the right steps .
what is needed to format ?
then the steps to flash an boot
thank you
Click to expand...
Click to collapse
Flash full stock rom > flash magisk patched boot image (optional) > flash twrp > flash dm verity disabler > reboot
Spudsicles said:
DISCLAIMER: I am not responsible for any bricked phones or otherwise but this is how I updated to the latest version.
Flashing backwards has not been tried by myself, use at your own risk.
Only flashing the same version of ROM was tried, global for global.
I tried the local update method that is built into the MIUI ROM, my bootloader is still locked, and you can only use OFFICIAL MIUI ROM's.
View attachment 5344411
Click to expand...
Click to collapse
Hello,
I am on Miui 12.5.4 rooted with Magisk right now, no TWRP, and OTA update 12.5.6 is available.
With the above procedure, can I install the update without losing root and without losing my data ?
Thank you very much.
[email protected] said:
Flash full stock rom > flash magisk patched boot image (optional) > flash twrp > flash dm verity disabler > reboot
Click to expand...
Click to collapse
Sorry Bro information not with the right steps!
It is needed to wipe ?
After flashing ROM it is possible to flash Magisk? Or only patch boot IMG?
Flashing TWRP ?
Booting from Recovery to Recovery??
Plz right steps I'm in hospital I don't have a computer here.
Thanks a lot
Jakkomo77 said:
Sorry Bro information not with the right steps!
It is needed to wipe ?
After flashing ROM it is possible to flash Magisk? Or only patch boot IMG?
Flashing TWRP ?
Booting from Recovery to Recovery??
Plz right steps I'm in hospital I don't have a computer here.
Thanks a lot
Click to expand...
Click to collapse
You've older version of miui installed with twrp and device is rooted.
1) you don't need to wipe anything. Just flash the rom and If you want you can wipe caches after flashing the rom.
2) TWRP might get replaced with stock one so flash twrp immediately after flashing the ROM. Also flash DM Verity disabler zip otherwise miui will replace twrp with stock recovery.
3) According to topjohnwu, the method of getting magisk by flashing in recovery is old & deprecated and maintained with minimal efforts & no longer recommended.
I am on Miui 12.5.4 rooted with Magisk right now, no TWRP, and OTA update 12.5.6 is available.
With the above procedure, can I install the update without losing root and without losing my data ?
Click to expand...
Click to collapse
Ok so for those interested, here’s how I did it :
- in Magisk I chose uninstall - restore image
- did the ota the normal way before any reboot
then had to reroot :
- downloaded the fastboot firmware here
- extracted boot.img from archive and transfered it to phone
- in magisk click install then select boot.img
- magisk writes a new file magisk_patched_[random_strings].img, copied it to pc
- booted the phone in fastboot mode
- used fastboot.exe with command fastboot flash boot magisk_patched_[random_strings].img
Done. No data or settings lost.
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
{
"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