Database Users

Cant open play store or connect to any google account

After installing MedroM I got this problem and couldn't connect to google account and every google app would crash if I tried to log in, so I flashed b161 and I still have this problem, even after numerous factory resets, has this ever happened to anyone ?

Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.

gtdaniel said:
Yes, it is happening to other guys around here...
In fact is happening to all who flash B160/B161 firmware...
Is not possible to flash any firmware previously to B160/B161.
Workaround is to unlock bootloader, flash twrp, root it, reflash oeminfo for your device,
and after that you can flash another firmware again.
Click to expand...
Click to collapse
i'm in the same situation, i tried to do what you've said, but twrp says that the installation failed. how can I have play store working again? please help, this situation is driving me crazy!
i'm on c900 b161.

I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.

No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware

raffabraz said:
No need to touch the oem stuff, just extract the boot.img and system.img and flash through adb, for dat you need bootloader unlocked and fastboot drivers then you can downgrade firmware and fix your sign problem or just wait for a new firmware
Click to expand...
Click to collapse
That would be much simpler, I didn't consider that. Would you mind writing up a guide?

I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..

sirlex said:
I've had the same issue and have resolved it pretty easily,
i did the following steps ;
- download both medrom versions
- do full factory reset
- install medrom v1
- do all settings of google etc
- reboot recovery and install v2
- wipe dalvik and reboot
-- all works now except for the forceclose on facebook
ps : this answer is also in the thread ( not as extended as this but it's there )
Edit : some other apps are Force closing to, my guess is that there's a shared resource of some kind that's corrupted or something..
Click to expand...
Click to collapse
Force closing is caused by the oeminfo in my experience. Can you check in the "About Phone" section which build number your phone currently has? Should be something along the lines of "VNS-L31C432B161" where C432 indicates the region code.

since I am Running MEDROM v2 it shows just that. However , I do know it is based on b161

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
After 2 days of trying different stuff, here's what gave me a functional device with TWRP and Root back:
-Back up any data you want to keep, obviously.
-Reflash stock ROM (put UPDATE.APP on your dload/ folder on the separate SD card, then boot into the update function by turning the phone off and then holding Vol+, Vol-, Power. Just wait until it's finished.
-Unlock Bootloader again
-Download the Toolkit: http://forum.xda-developers.com/huawei-p9lite/development/europe-vns-l31-toolkit-bootloader-t3432873
-Flash TWRP through the toolkit
-Boot TWRP and root
-In Android, enable ADB
-In the Toolkit, go to Dual Sim>Individual and select the appropriate custom.bin and oeminfo.img from the thread of the toolkit. For my European one it was L31 SS C432. Press flash and grant Root permissions on your phone.
-Turn off your phone and flash the stock ROM again like in step 1.
-If you want root, you need to unlock the Bootloader again, flash TWRP and then root it from there.
DON'T WIPE ANYTHING IN TWRP OR YOU WILL HAVE TO START ALL OVER AGAIN!
Don't ask me how I know.
Hope this saves someone from wasting their time with this nonsense like I have.
Click to expand...
Click to collapse
Thank you so much , you saved my phone !!
Fllashing stock rom again isnt necessary , just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !

simo255 said:
Thank you so much , you saved my phone !!
it doesn't need to reflash stock rom again, just flash the oeminfo, reboot, they will tell you an encryption password, so you have to do a factory reset AND DONE !
Click to expand...
Click to collapse
Interesting, when I tried to do a factory reset after that screen, it always failed.

HeavyHDx said:
Interesting, when I tried to do a factory reset after that screen, it always failed.
Click to expand...
Click to collapse
You have to flash the stock recovery to do a Factory reset

medRom v2 fix
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.

Could someone provide me the correct oeminfo and custom.bin for a European/German model? C432? The images inlcuded in the toolkit don't work for me, it still crashes or can't communicate with the google server

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installing Android System Web View apk from apkmirror solved the problem for me (arm + x86 package). Thank you

HeavyHDx said:
I had the same issue. I did a clean flash of the new 161 update and that made my device a C900. I have a Eurpoean model (T-Mobile Germany).
Click to expand...
Click to collapse
I got my P9 Lite from Congstar in Germany. I didn't knew, that the device would be branded by Telekom. I flashed the B161 and couldn't connect to any google account. Thankfully updating the webview apk via apk mirror solved this problem. But this leaves me with 2 questions and maybe you could answer these...?
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
I would be really happy if someone of you could help me. :good:

MartinMo said:
1) Do you know which stock rom would work the best with my device (VNS-L31 without the possibility to use two sim cards ) and where I could download this stock rom.
2) Is the B161 supposed to work fine after solving this issue or are there other problems with it?
Click to expand...
Click to collapse
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.

HeavyHDx said:
1) The best stock ROM would either be, well, the stock ROM, or the Revolution ROM.
Click to expand...
Click to collapse
Isn't Nougat still a beta...? I'm looking for a stable stock version of EMUI...
HeavyHDx said:
2) I've had some strange behavior with Relay for Reddit and frequent crashes of WhatsApp when sending messages. Right now I'm on Lineage OS 14.1 and it's really great. Camera's a bit slow, but otherwise I love it. I missed stock Android.
Click to expand...
Click to collapse
Thank you, tomorrow I'll test if Whatsapp working fine or not, that's important for me. Is Lineage 14.1 the most stable Lineage version?

Nougat is still in beta, yes. The full version is expected to come out within the next few weeks.
14.1 refers to the Android version which is 7.1.1. They adopted CyanogenMod's naming scheme. You'll still need to update LineageOS to get bugfixes and such. The dev releases a new update every 2 or 3 days, just check their website periodically.

Deddline said:
Hi all.
I think i found solution for Google login issue.
I use European VNS-L21-C432B161 dual sim phone with lattest rom.
I flashed medRom v2 with full wipes.
Ofcourse i Can not log in Google Services.
Today i download 3 Google apk files. Installed and it works.
Sorry. I cant post ling on XDA now.im newbie
Link in My profils.
There is instruction how i do:
1. Installed Gmail apk and login.
2. Installed Android System Web Wiev apk.
3. Installed Google Play Service apk
Proof: in My profils description in Youtube
Download Files: watch in YOUTUBE description.
Hope helps for someone.
Click to expand...
Click to collapse
Installed Android System Web Viev .apk did the trick for me, too. muchos gracias.

S7 edge , pin code removal unrooted with twrp without loosing data

Hello
Thanks for all support can members produce in this website
i am a new french user , happy to join you.
i will expose you my situation , normaly i don't found any similar post before
so i have a S7 edge g935F version , pin code and google account forget
but i need to recovery all data from it before hard reset .
so i found solution of TWRP for remove the password.key and/or gesture.key in data/system right ?
the s7 edge developper mode is not active / also no rooted .
Can i flash with ODIN twrp-3.1.1-0-hero2lte.img.tar in pda section
and just apres reboot in recovery twrp and nagivate in folder for delete files concerned ?
thanks so much for your help .
hope i can help you soon
Regards

abdel59 said:
Hello
Can i flash with ODIN twrp-3.1.1-0-hero2lte.img.tar in pda section
and just apres reboot in recovery twrp and nagivate in folder for delete files concerned ?
Regards
Click to expand...
Click to collapse
To flash TWRP you need to have OEM unlock enabled in Developer Settings. Otherwise your device will not boot.
There is a guide here
I'm pretty sure if your device is not rooted or anything already beforehand there isnt a way to remove the password without loosing your data. This is to protect a users data incase there phone is stolen or lost.

EasyAndroidPro said:
To flash TWRP you need to have OEM unlock enabled in Developer Settings. Otherwise your device will not boot.
There is a guide here
I'm pretty sure if your device is not rooted or anything already beforehand there isnt a way to remove the password without loosing your data. This is to protect a users data incase there phone is stolen or lost.
Click to expand...
Click to collapse
Hello
thanks for fast reply
what about TWRP official website , they explain that on s7 edge we can install TWRP without root with ODIN in download mode
but i don't found information about the after install, can i will boot on recovery twrp or not to mount file ?
thanks
best regards

abdel59 said:
Hello
thanks for fast reply
what about TWRP official website , they explain that on s7 edge we can install TWRP without root with ODIN in download mode
but i don't found information about the after install, can i will boot on recovery twrp or not to mount file ?
thanks
best regards
Click to expand...
Click to collapse
Hi sorry for slower reply im at work.
This is the same post i linked you.
Yes - you can install TWRP without installing root but you still need to have OEM unlock ticked in developer settings.
Also once flashing TWRP you will not be able to mount data or boot your device unless you FORMAT data which will loose all your files on your internal storage.
i think the solution "so i found solution of TWRP for remove the password.key and/or gesture.key in data/system right"
is only for people that already have TWRP installed on there device before they loose there passwords.

EasyAndroidPro said:
Hi sorry for slower reply im at work.
This is the same post i linked you.
Yes - you can install TWRP without installing root but you still need to have OEM unlock ticked in developer settings.
Also once flashing TWRP you will not be able to mount data or boot your device unless you FORMAT data which will loose all your files on your internal storage.
i think the solution "so i found solution of TWRP for remove the password.key and/or gesture.key in data/system right"
is only for people that already have TWRP installed on there device before they loose there passwords.
Click to expand...
Click to collapse
thanks for reply
so maybe i will try search another method for this situation
thanks
best regards

Oneplus 5 Update fails

Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help

Mouchoir said:
Hello everyone,
For a while now, I have been delaying this, because I can't afford to lose the content that I have on this device
I have a Oneplus 5 OxygenOS 5.1.4 release that I can't install. Everytime I do, it just fails, and reboot. A while after, I have a new notification telling me that the update is available
My phone is not rooted but I think the bootloader is unlocked. TWRP isn't installed either
Is there any way for me to easily update my phone witout risks of losing what I have on it ? Might be a dumb question, but I'm a huge noob
Thansk a lot for your help
Click to expand...
Click to collapse
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?

Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state

strongst said:
Do you get the bootloader unlock warning message at boot? Is the device new or used? You want to update from 5.1.4 to 5.1.5 with ota right? Does the ota download 1.7GB or detect root before downloading?
Click to expand...
Click to collapse
You did not answer all questions, so I only can guess...
Mouchoir said:
Hello strongst and thanks for your answer
The phone is old but it's always been mine. I rooted it a while back but I reinstalled everything, which is why the bootloader is unlocked even tho the phone isn't rooted.
I do have the warning message when I boot
I'm trying to update with OTA indeed. When I do so, it downloads the update, reboots, and then I get this :
"Instaling, please wait..." and a few seconds after "Installation failed"
Then I just rebot the phone and everything is back to its initial state
Click to expand...
Click to collapse
I'm guessing it downloads partial ota and not a full rom like about 1,7GB so the update fails. In case you have twrp you can easily download the 5.1.5 FULL zip from here and flash it https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190

I am sorry that my answer wasn't complete.
- I do have the bootloader message
- The device is a year old, but only used by me
- It's trying to download 5.1.4 OTA which is 1609MB. It downloads everything and tries to install it
- No root is detected
- I don't have TWRP on the phone
Thanks for your answers

Best way it simply install latest TWRP like Sian, do a dirty flash with the full OOS Rom package (5.1.7) for force update.
1/ Do a full backup of your data / sms / pictures on your computer (just for be sure, you must always backup for big changes, especially with encrypted roms)
2/ install TWRP Sian
3/ On TWRP > Wipe > Dalvik/ART - Cache paritions
4/ Install > the latest stable OOS 5.1.7 Rom
5/ Just after that flash Magisk (if you want keep the custom recovery) or don't flash Magisk (stock recovery will erase TWRP after SetupWizard)

Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot

Mouchoir said:
Hello Pho3nX, thanks for your answer.
I tried to figure out what "TWRP Sian" is, but I couldn't find anything. I found this one : https://twrp.me/oneplus/oneplus5.html and I'm planning on following the "Fastboot Install Method". Is that OK ?
Do you recommand me to flash Magisk ?
Thanks a lot
Click to expand...
Click to collapse
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...

Pho3nX said:
This : [RECOVERY] TWRP-3.2.3 with Pie decryption support [experimental]
And yes i advise to install Magisk for keep TWRP & tools / root, permit using useful root app like Titanium/Theme/Adaway/Explorer etc...
Click to expand...
Click to collapse
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff

Mouchoir said:
Hello
I'm back Thanks for your answer. However, there is no explaination on how to use the .img I've downloaded. Could you point me to some instructions ?
Sorry I'm not good at this stuff
Click to expand...
Click to collapse
If you have no twrp already installed on your device you must flash the twrp.img file with fastboot like "fastboot flash recovery twrp.img"

Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Pho3nX said:
4/ Install > the latest stable OOS 5.1.7 Rom
Click to expand...
Click to collapse
Would it work if I download it instead of the one you sent me ?
Thanks a lot

Mouchoir said:
Hello,
You haven't heard from me because I wait to be at home so I can safely follow your instructions.
I just saw a news about Android Pie 9.0 beta being released for Nexus 5.
Would it work if I download it instead of the one you sent me ?
Thanks a lot
Click to expand...
Click to collapse
Error 7 for me i tried i'm with unlocked bootloader latest TWRP by Eng.stk and i removed form the zip also compatibility.zip

Hello,
I finally managed to install the zip thanks to TWRP, but it seems that my cellphone is stuck on the boot turning logo with the two red dots turning around the big red one

Fixed : https://forum.xda-developers.com/oneplus-5/help/bricked-oneplus-5-t3884364

After updating to Oxygene 10..3.7 'Unable to boot,

Hello,
need some help.
Phone was setup with Oxygene OS 10.3.6, TWRP 3.0.3.2, Magisk. Target was to update the Full OTA of 10.3.7 via TWRP from downloaded file..
Unfortunat4ely im not able to boot the Phone anymore. Im able to try to start a update by sideload from TWRP wich doesnt work (getting error code KInstallDeviceOpenError )
By rebooting into TWRP i wasnt asked for the Pincode (?)
Any hints or tips would be appreachiated very much.
Thx. a lot

:jolt: said:
TWRP 3.0.3.2
Click to expand...
Click to collapse
Are you sure about that TWRP version? Either you are using a very old outdated version of TWRP, could be the problem, and likely the reason you weren't prompted for a pin, or that's not the correct version.
You need the latest version of TWRP which hopefully you can boot from fastboot.6T TWRP Downloads here. Note, 3.4.0.2 did fix the rom flashing issues, and you can use the installer zip no issues now. If you are able to get back into TWRP, I would backup your data as soon as you get access to it just in case. These phones are easy to fix, as long as you aren't worried about your data.

Thx for your reply, should been version 3.2.3.2. All in one Tool works and i flashed the imagge again, unfortunately all userdata was deleted.
Backup, a liddle old, was avaible .. so not a really Problem. Only the Time that i have wasted..

Magisk 23 to 24 ruined

Hi!
I had Magisk v23 working fine with Magisk hide but then I upgraded to v24. Magisk app successfully installed and shows Magisk not present. And when I try to DirectInstall Magisk, I get verification failed error. Attached both screenshots.
Now, I have installed and confirm TWRP is working but do not know how to make Magisk working again and it seems it gonna be a wipe. Any help appreciated.

[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html

Issue is that on my other phone, Sony Xperia XZ Premium G8142, the same in-app upgrade weas successful with out any issues. I lost Magisk Hide but an extension recovered that function. But it all went haywire on this S8

xabu said:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Step by step: Magisk 24.1 is new and as you have seen completely different.
Installation instructions: https://topjohnwu.github.io/Magisk/install.html
Click to expand...
Click to collapse
This guide expects me to know what ROM I have. Thing is, I do not know what my device really is. It's running a ROM that I do not recognize (My post: https://forum.xda-developers.com/t/...l-and-odin-cannot-flash.4372669/post-86069051). I do not have the sources for it so I cannot acquire the required two files. Ramdisk is Yes as per my screenshot but I cannot follow the rest of the guide without the files.

try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .

xabu said:
try this
Check hardware and software info Galaxy:
*#12580*369#
Android 9 shows almost certainly a stockrom Pie .
Click to expand...
Click to collapse
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.

Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!

Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Maybe only European ?

xabu said:
Your phone needs twrp and a new good custom ROM ...
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Here are certainly members of the forum with lots of expertise!
Click to expand...
Click to collapse
I just TWRP it. It went smoothly. I love a new ROM but need to know what device is it.
Download mode say it is SM-G950N
Android say it is SM-950FD
Both SIM slots have the same IMEI number. This part is beyond my understanding.
I have Odin and know the basics. Just need to find a ROM I can go for: What official I should flash first and what custom. Any recommendation?

As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.

xabu said:
Maybe only European ?
Click to expand...
Click to collapse
Doomer D. Great said:
I can't seem to get that code run when I dial it. Also, calling doesn't do anything.
Click to expand...
Click to collapse
Just found out:The "famous" secret codes only work on stock based ROMs ¯\_( ͡❛ ͜ʖ ͡❛)_/¯

xabu said:
As soon as you make a TWRP total backup, you can see your boot.img and move a copy to your internal sd-card. There it can be picked up by Magisk and patched....Magisk will put it in your download folder on the internal sd-card ...
for the best Rom ask members with your S8 phone. I'am on the S7 Edge.
Click to expand...
Click to collapse
I have been trying to make the total backup but I do not see any boot.img:
And I do not see the file in the Device/TWRP/Backups:
Again, I must be missing something obvious. And as per the Magisk guide, I need the boot.img

magisk 24 is ****, it's bricking MediaTek powered Samsung phones

Boot.img from TWRP backup
In clockworkmod kernel and recovery are backed up as IMGs. But in TWRP it is boot.emmc.win Anybody know how to convert jt to boot.img? Help will be really appereciated. Sent from my HTC One X using xda app-developers app
forum.xda-developers.com
I must tell you that my custom rom for the s7 gives me the boot.img as the first file as soon as i open the zip.
the boot.img can also be reached by downloading the right stock rom for your phone. In that case it is the best practice to patch the whole
AP file by using Magisk.