Unable to decrypt my G8 Power :( - Moto G Power Questions & Answers

Hello all,
After a lot of searches and trying multiple combinations of steps I was unable to decrypt my G8 Power. Has anyone tried and successfully decrypted their Moto G/G8 power. If Yes I would kindly need their advice. Thanx in advance.

How do you guys switch ROMs? I was unable to do so because my memory is encrypted and restoring a twrp backup doesn't seem to work (TWRP Asks password and doesn't accept the right one) and I have to do a format data to start using the backup Rom which is kind of useless. It used to work before(with Sammy S6 Edge) I tried using Disable_Dm-Verity_ForceEncrypt_01.19.2020. But doesn't seem to work. Suggestions Appreciated.

Forget twrp. Reinstall stock and then Havoc.

I used vbmeta.img in fastbootd

Jcth1 said:
I used vbmeta.img in fastbootd
Click to expand...
Click to collapse
I Too tried using an empty vbmeta as well as vbmeta from Havoc. But drive is still encrypted. Need to format to boot.

Quantumstate said:
Forget twrp. Reinstall stock and then Havoc.
Click to expand...
Click to collapse
How do you move apps, data sms, logs etc across ROMs?

Related

Bricked RN3 PRO - Locked bootloader and fastboot working fine

I know there are several threads about unbricking RN3 but I didn't find any article that could solve this problem, not even in other forums.
This started when apps were continuously force closing for no reason and I decided to flash a new official ROM (going on MIUI settings) but the problem persisted. So I did that via MI Flash and I had the same result.
As this force closing situation were being more and more frequent I flashed several times different official MIUI ROMS from EDL mode (developer and stable) and then, after one of this times, it just don't start the system anymore, its just keep bootlooping again and again.
I also tried another methods, like flashing updated fastboot ROMS but didn't work out.
Another thing, I've flashed TWRP once but it asked for a password so I couldn't access the files and flash a custom rom and my phone is locked (that xiaomi lock situation). But after that I've restored the original recovery (that appears an image of a unplugged/plugged phone to use with pc suite but it doen't recognize my device).
So, I don't really know what to do anymore.
I didn't even use this phone for a complete year and xiaomi lacks of support in my country and they wont help me, like they replied my by email.
Anyone could help me with this issue?
Thank you, by the way!
Try unlocking bootloader unofficially if can't do officially . Try edl mod
tom jp said:
Try unlocking bootloader unofficially if can't do officially . Try edl mod
Click to expand...
Click to collapse
Actually, I tried to flash a file to do that, but didn't work out. Maybe it's the method that I've used.
Could you recommend anyone?
the simple reason is your phone is soft bricked...
all yoi have to do is flash fastboot rom via edl using mi flash tool... you will find thered relating to it in guide section of this forum.
~peace
adithyan25 said:
the simple reason is your phone is soft bricked...
all yoi have to do is flash fastboot rom via edl using mi flash tool... you will find thered relating to it in guide section of this forum.
~peace
Click to expand...
Click to collapse
Actually, I did that several times... so, that's not the solution
lucasmp.paiva said:
Actually, I did that several times... so, that's not the solution
Click to expand...
Click to collapse
didu done a full wipe via miflashtool?..
adithyan25 said:
didu done a full wipe via miflashtool?..
Click to expand...
Click to collapse
Yes, I did.
Cleaned all and with multiple roms.
lucasmp.paiva said:
I know there are several threads about unbricking RN3 but I didn't find any article that could solve this problem, not even in other forums.
This started when apps were continuously force closing for no reason and I decided to flash a new official ROM (going on MIUI settings) but the problem persisted. So I did that via MI Flash and I had the same result.
As this force closing situation were being more and more frequent I flashed several times different official MIUI ROMS from EDL mode (developer and stable) and then, after one of this times, it just don't start the system anymore, its just keep bootlooping again and again.
I also tried another methods, like flashing updated fastboot ROMS but didn't work out.
Another thing, I've flashed TWRP once but it asked for a password so I couldn't access the files and flash a custom rom and my phone is locked (that xiaomi lock situation). But after that I've restored the original recovery (that appears an image of a unplugged/plugged phone to use with pc suite but it doen't recognize my device).
So, I don't really know what to do anymore.
I didn't even use this phone for a complete year and xiaomi lacks of support in my country and they wont help me, like they replied my by email.
Anyone could help me with this issue?
Thank you, by the way!
Click to expand...
Click to collapse
Hi my friend if you cant mount data in twrp. your internal storage is encrypted by custom rom
to solve your problem
1-format data (not wipe)
2-wipe
system
cache
dalvik cache
internal storage
3-flash(clean all and lock) latest miui rom in edl mod
and if your problem solved tell us
(my english...)
farshad9500gy said:
Hi my friend if you cant mount data in twrp. your internal storage is encrypted by custom rom
to solve your problem
1-format data (not wipe)
2-wipe
system
cache
dalvik cache
internal storage
3-flash(clean all and lock) latest miui rom in edl mod
and if your problem solved tell us
(my english...)
Click to expand...
Click to collapse
I've tried to install TWRP but it needs a password to decript data. So it appears 0mb on everything and shows an error to format, wipe or do anything.
Remember, my device is still locked by miui.
lucasmp.paiva said:
I've tried to install TWRP but it needs a password to decript data. So it appears 0mb on everything and shows an error to format, wipe or do anything.
Remember, my device is still locked by miui.
Click to expand...
Click to collapse
take a picture of data format error and put here
Make sure you have try this:
wipe->format data->type "yes" and ok
also try this command in fastboot mod:
fastboot erase userdata
and remember use latest twrp

Password in all recoveries except TWRP 3.3.0.0

First of all I must apologize for my low level of English.
I will try to explain something strange that happens to my Pocophone since the arrival of the OTA with Android 10 and Miui11
Since I bought the Poco I have always used TWRP as recovery.
I currently use the 3.3.0.0 official TWRP version downloaded from its official app and I have no problem until the past weekend-
However, I have tried installing OrangeFox Recovery Project (OFRP), PitchBlack Recovery Project (PBRP) and an unofficial TWRP mod whose name is twrp-3.3.1-2-beryllium-adil2.img
And now I tell you I miss it.
If I boot into recovery using TWRP 3.3.0.0 it does not ask me for password, but if I flash OFRP, PBRP or mod 3.3.1.2 adil 2, it always asks me for a password when booting and tells me that the partition /data is encrypted. I do not know the password and I have never encrypted the Poco. Also the 3 revoveries show that is not installed any Tom, but when a reboot the system works perfectly.
Some colleagues have indicated to me that the data partition had been encrypted so I followed the next process to try to install a clean rom.
1. Boot in bootloader with Power + Vol-
2. Via fastboot flash OFRP
3. Boot in recovery (OFRP)
4. Format data and factory reset
5. Reboot recovery OFRP
6. Wipe: cache, Dalvik/Cache, Data and System partitions
7. Install rom XiaomiEU V11.0.4.0.QEJMIXM.zip
8. Flash DFE + Magisk
9. Reboot system
10. Complete ROM configuration
When I start again in recovery, it asks me for a password, informs me that data is encrypted and I cannot mount it, and I can't install anything.
However, if I flash TWRP 3.3.0.0 via fastboot, it no longer asks me for a password and I can mount the data partition and work normally.
If I flash again OFPR, PBRP or twrp-3.3.1-2-beryllium-adil2.img, ask me for a password again and it tells me that / data is encrypted
I tried to delete from /data/system the files locksettings.db, locksettings.db-shm and locksettings.db-wal but it continues asking me for a password if the recovery is always different of TWRP 3.3.0.0
otraver said:
First of all I must apologize for my low level of English.
I will try to explain something strange that happens to my Pocophone since the arrival of the OTA with Android 10 and Miui11
Since I bought the Poco I have always used TWRP as recovery.
I currently use the 3.3.0.0 official TWRP version downloaded from its official app and I have no problem until the past weekend-
However, I have tried installing OrangeFox Recovery Project (OFRP), PitchBlack Recovery Project (PBRP) and an unofficial TWRP mod whose name is twrp-3.3.1-2-beryllium-adil2.img
And now I tell you I miss it.
Click to expand...
Click to collapse
First off, your post belongs in the Q & A section. Please ask a moderator to move it as it has nothing to do with ROMs or development. Secondly, if official TWRP works, use it. Stop switching between recoveries and getting yourself all flustered.
PS: your English is fine. Don't sweat it.
Sent from my Galaxy Tab S5e using XDA Labs
Thank's for your answer.
guhvanoh said:
First off, your post belongs in the Q & A section. Please ask a moderator to move it as it has nothing to do with ROMs or development.
Click to expand...
Click to collapse
I don't know how conctact with the moderator. I'm a veteran user of the XDA-forums but I don't usually write frequently because my difficulty with the English language.
Secondly, if official TWRP works, use it. Stop switching between recoveries and getting yourself all flustered.
PS: your English is fine. Don't sweat it.
Click to expand...
Click to collapse
You're right. Here, in my country, we usually use this saying "if something works, don't touch it"
I wanted to try other recoveries because the official TWRP does not support USB-OTG access well.
About one year ago, I tried using a 256GB flashdrive with a m.2 ssd to perform a faster backup of the rom, but TWRP don't recognize the drive.
I read in these forums that TWRP had a problem managing USB-OTG and installed PBRP and it worked fine until last week I received the Miui11/Android10 OTA. After flashing it, PBRP started asking me for the password and displaying the message "I don't detect any rom installed". Despite having a recent backup (I always do it before flashing) I was a little scared.
I decided to reinstall TWRP by fastboot and I was surprised that the rom had been updated and everything worked ok.
As some colleagues tell me that I have the encrypted / data partition, I tried to make a format of the / data partition and new installation, with the result I commented above.
However, when I received the previous OTA, which was Android9 and Miui11, there was no problem.
I just wanted to share this strange situation.
I appreciate your message.
otraver said:
Thank's for your answer.
I don't know how conctact with the moderator. I'm a veteran user of the XDA-forums but I don't usually write frequently because my difficulty with the English language.
I appreciate your message.
Click to expand...
Click to collapse
Not a problem. If you view this in a web browser there is a button at the bottom left or right to report a post. Use that and ask for this thread to be moved.
PS: your English is still great.
Sent from my Galaxy Tab S5e using XDA Labs
otraver said:
First of all I must apologize for my low level of English.
I will try to explain something strange that happens to my Pocophone since the arrival of the OTA with Android 10 and Miui11
Since I bought the Poco I have always used TWRP as recovery.
I currently use the 3.3.0.0 official TWRP version downloaded from its official app and I have no problem until the past weekend-
However, I have tried installing OrangeFox Recovery Project (OFRP), PitchBlack Recovery Project (PBRP) and an unofficial TWRP mod whose name is twrp-3.3.1-2-beryllium-adil2.img
And now I tell you I miss it.
If I boot into recovery using TWRP 3.3.0.0 it does not ask me for password, but if I flash OFRP, PBRP or mod 3.3.1.2 adil 2, it always asks me for a password when booting and tells me that the partition /data is encrypted. I do not know the password and I have never encrypted the Poco. Also the 3 revoveries show that is not installed any Tom, but when a reboot the system works perfectly.
Some colleagues have indicated to me that the data partition had been encrypted so I followed the next process to try to install a clean rom.
1. Boot in bootloader with Power + Vol-
2. Via fastboot flash OFRP
3. Boot in recovery (OFRP)
4. Format data and factory reset
5. Reboot recovery OFRP
6. Wipe: cache, Dalvik/Cache, Data and System partitions
7. Install rom XiaomiEU V11.0.4.0.QEJMIXM.zip
8. Flash DFE + Magisk
9. Reboot system
10. Complete ROM configuration
When I start again in recovery, it asks me for a password, informs me that data is encrypted and I cannot mount it, and I can't install anything.
However, if I flash TWRP 3.3.0.0 via fastboot, it no longer asks me for a password and I can mount the data partition and work normally.
If I flash again OFPR, PBRP or twrp-3.3.1-2-beryllium-adil2.img, ask me for a password again and it tells me that / data is encrypted
I tried to delete from /data/system the files locksettings.db, locksettings.db-shm and locksettings.db-wal but it continues asking me for a password if the recovery is always different of TWRP 3.3.0.0
Click to expand...
Click to collapse
Hi bro I also facing same issue my problem is I m using orange fox recovery 10.0.1 version and when I flash miuiQ stable global with dfe it ask me to enter password when I boot to recovery don't know what happened. By the way is twrp official work perfectly????
---------- Post added at 04:07 PM ---------- Previous post was at 04:01 PM ----------
otraver said:
Thank's for your answer.
I don't know how conctact with the moderator. I'm a veteran user of the XDA-forums but I don't usually write frequently because my difficulty with the English language.
You're right. Here, in my country, we usually use this saying "if something works, don't touch it"
I wanted to try other recoveries because the official TWRP does not support USB-OTG access well.
About one year ago, I tried using a 256GB flashdrive with a m.2 ssd to perform a faster backup of the rom, but TWRP don't recognize the drive.
I read in these forums that TWRP had a problem managing USB-OTG and installed PBRP and it worked fine until last week I received the Miui11/Android10 OTA. After flashing it, PBRP started asking me for the password and displaying the message "I don't detect any rom installed". Despite having a recent backup (I always do it before flashing) I was a little scared.
I decided to reinstall TWRP by fastboot and I was surprised that the rom had been updated and everything worked ok.
As some colleagues tell me that I have the encrypted / data partition, I tried to make a format of the / data partition and new installation, with the result I commented above.
However, when I received the previous OTA, which was Android9 and Miui11, there was no problem.
I just wanted to share this strange situation.
I appreciate your message.
Click to expand...
Click to collapse
So bro twrp official never give encryption error if I flash miuiQ using it right ?
Hey there!
I have the same Situation here and I figured at least some points out:
- the Upgrade to Android 10 encrypted the data Partition. You can see that in in your phone settings under security and password. For some security reasons of Android Q I guess.
But what password and how to change is a mystery. There are tons of articles out there which are related to "encrypt with lock screen password" but thats something different. We have this Option too in developer settings but it is not Set. So the way of our New encrypted device is still a Secret.
- Official twrp is the only one to decrypt the data correct. If you go to the "save logs" section in twrp and save it you can see the log and it says that it decrypts with Standard password. But I wasnt able to find out that this is. And as I stated before we dont use the lockscreen password to decrypt, I tried to change and disable it but guess what... I didn't change anything.
I hope we can figure out as a community what's exactly going on here.
THE PASSWORD IS:
"default_password"​
guhvanoh said:
Not a problem. If you view this in a web browser there is a button at the bottom left or right to report a post. Use that and ask for this thread to be moved.
Click to expand...
Click to collapse
Reported, thanks
sachin5555 said:
Hi bro I also facing same issue my problem is I m using orange fox recovery 10.0.1 version and when I flash miuiQ stable global with dfe it ask me to enter password when I boot to recovery don't know what happened. By the way is twrp official work perfectly????
Click to expand...
Click to collapse
I'm ussing the 3.3.0.0 and works perfectly...
So bro twrp official never give encryption error if I flash miuiQ using it right ?
Click to expand...
Click to collapse
In my case I have not had any problems.
I am currently using the global stable 11.0.4.0 QEJMIXM + TWRP 3.3.0.0 + Magisk 20.3
Fritzko said:
Hey there!
I have the same Situation here and I figured at least some points out:
- the Upgrade to Android 10 encrypted the data Partition. You can see that in in your phone settings under security and password. For some security reasons of Android Q I guess.
But what password and how to change is a mystery. There are tons of articles out there which are related to "encrypt with lock screen password" but thats something different. We have this Option too in developer settings but it is not Set. So the way of our New encrypted device is still a Secret.
Click to expand...
Click to collapse
I have checked what you say about ""encrypt with lock screen password" in developer settings and in my case it is disabled.
- Official twrp is the only one to decrypt the data correct. If you go to the "save logs" section in twrp and save it you can see the log and it says that it decrypts with Standard password. But I wasnt able to find out that this is. And as I stated before we dont use the lockscreen password to decrypt, I tried to change and disable it but guess what... I didn't change anything.
I hope we can figure out as a community what's exactly going on here.
Click to expand...
Click to collapse
Where can I find the logs you comment to check?
fraggy2 said:
THE PASSWORD IS:
"default_password"​
Click to expand...
Click to collapse
Seriously?
I will not be able to try it until tomorrow. The motherboard of my PC has said that it doesn't work anymore and I am waiting for the arrival of a new one.
Where can I find the logs you comment to check?
Click to expand...
Click to collapse
Go to Twrp > advanced > copy logs. They are saved on your sd card.
fraggy2 said:
THE PASSWORD IS:
"default_password"​
Click to expand...
Click to collapse
I tried wit "default_password" (without quotes) and don't work
Fritzko said:
Hey there!
- Official twrp is the only one to decrypt the data correct. If you go to the "save logs" section in twrp and save it you can see the log and it says that it decrypts with Standard password. But I wasnt able to find out that this is. And as I stated before we dont use the lockscreen password to decrypt, I tried to change and disable it but guess what... I didn't change anything.
Click to expand...
Click to collapse
I checked the TWRP logs and have you reason
Code:
I:Unmounting main partitions...
Successfully decrypted with default password.
I:Decrypt adopted storage starting
I:PageManager::LoadFileToBuffer loading filename: '/data/system/storage.xml' directly
I:successfully loaded storage.xml
Updating partition details...
I am using SHRP recovery for poco for 2 months now and I haven't faced any encryption problem (recovery asking for password). I would recommend you to try it buddy.
Champ16 said:
I am using SHRP recovery for poco for 2 months now and I haven't faced any encryption problem (recovery asking for password). I would recommend you to try it buddy.
Click to expand...
Click to collapse
If i flash it over twrp will it ask me to enter password?
sachin5555 said:
If i flash it over twrp will it ask me to enter password?
Click to expand...
Click to collapse
No
Champ16 said:
No
Click to expand...
Click to collapse
Done ! Thank u
Champ16 said:
I am using SHRP recovery for poco for 2 months now and I haven't faced any encryption problem (recovery asking for password). I would recommend you to try it buddy.
Click to expand...
Click to collapse
I don't think it works, but sure I will try it.
I have already tried everything I have been reading through many forums and I always get the same result.: the ****ing password
I have tried to deactivate the PIN, screen pattern, passwords, I have even logged off the Mi account and then I have tried to flash OFRP, PBRP and a TWRP mod and always, always ask me for password
I've tried booting on TWRP
1. Factory reset
2. Format data (not only wipe) (I answer "yes")
3. Reboot recovery
4. wipe cache, Dalvik / cache, Data and System
5 Install rom (miui_POCOF1Global_V11.0.4.0.QEJMIXM_74f88e6c8f_10.0.zip)
5. Flash twrp
6. Flash orange fox + DFE + magisk
7. Start rom and configure.
And without entering a PIN or blocking pattern, only gmail and Mi account and when returning to reboot in recovery it asks me again for a password.
SOLUTION:
I removed lockscreen password and flashed official TWRP.
Now it's decrypted successfully
The same kind of thing happened to me. I wish that I had seen this thread before. Lost all my data. ???
You can check it here
https://forum.xda-developers.com/poco-f1/help/miui-11-eu-android-10-encrypted-data-t4049421

Question Anyone has stock recovery.img for nord 2 DN2101 for OS version DN2101_11_A.11?

I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
sako21 said:
I am stuck with unlocked bootloader and not able to lock it back. When I do, I see the "destroyed boot/recovery image" error screen.
Though I have stock boot.img, I don't have the stock recovery.img. Or both should help, just to be sure!
If anyone has it saved, please share, I would like to try locking it again.
Click to expand...
Click to collapse
Flash latest A13 update u will get stock recovery
pankspoo said:
Flash latest A13 update u will get stock recovery
Click to expand...
Click to collapse
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
sako21 said:
Thanks for replying!
I did that today. It wasn't happening, it was failing with error - boot partition has expected contents.
Did a lot of erase and restores of partitions from rom backup with TWRP. Finally got through it somehow and it got installed with System Updates feature.
Now that it is flashed, can I simply try fastboot flashing lock and it will go through?
Not willing to spend too much time with trying it as it might wipe data (not sure of it though), hence asking here.
Or will it result into "destroyed boot/recovery image"?
Click to expand...
Click to collapse
Just try keep unrooted boot. Img backup of your current rom.
Then go ahead though it's got currpted (one person faced that at insta but he used that commnads when he has twrp it must work with stock recovery) but after restoring boot imgae all was fine.
But try at u r own risk later don't tag [email protected] pankspoo - guide
Thanks. Will try that out.
And yes, wont tag you!
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
Wait u want to relock bootloader?
You need a otg adapter. Put Stock boot.img and the last ota update file to the usb storage.
flash stock boot.img via FKM
go to developer settings and lock oem
uninstall magisk with restore all (not image)
start phone in bootloader
fastboot flash relock
fastboot reboot recovery
select update from storage
use otg adapter with ota file
install
restart
done
For any assistance contact @sakarya1980
sako21 said:
Thanks. Will try that out.
And yes, wont tag you!
Click to expand...
Click to collapse
did you get the relock bootloader?
If you're still searching for the stock recovery, I've attached the .img file (unzip it first)

Question [Help] Pixel 6 bricked after installing Blu Spark via FKM

Hello everyone, really looking for help here to unbrick my pixel 6.
I was on Stock Jan build, rooted with magisk. I tried to install Blue spark kernel via FKM, everything seemed to worked fine but once it rebooted, I got a message saying my device is corrupt. I pressed the power button to continue and it just gets stuck at the splash screen and reboot. I tried reflashing a factory image but it tells me the system partition is not found. I then tried to switch to the other slot to flash a factory image, but it tells me the system parition is too small to flash system.img. I know of no way to unbrick my pixel 6 at this point. Seems like installing Blu spark somehow messed up my paritions.
Any help is truly appreciated. I am stuck with a brick at this point.
Delete all your partitions via fastboot and then flash stock ROM.
Have you tried to boot in safe mode?
You can also try to flash the stock boot.img, which normally will work.
fastboot flash boot boot.img
vandyman said:
Have you tried to boot in safe mode?
Click to expand...
Click to collapse
I read on a telegram chat that s/he/they were able to restore using kdrag0n's ProtonAOSP web installer.
phaino00 said:
I read on a telegram chat that s/he/they were able to restore using kdrag0n's ProtonAOSP web installer.
Click to expand...
Click to collapse
Thanks for the info.

TWRP for Pixel 6/7?

Why won't Team Win make TWRP for the pixel 6/7 line? Maybe I don't know something and there are some restrictions? This would really make it easier to create/install firmware and GSI firmware
TWRP is generally of little use on Pixel devices, which do not have a recovery partition. Since the bootloaders are easily unlocked and accept flashing commands, firmware can be flashed via ADB.
Installing GSIs is easy, just flash the system image to /system.
V0latyle said:
TWRP is generally of little use on Pixel devices, which do not have a recovery partition. Since the bootloaders are easily unlocked and accept flashing commands, firmware can be flashed via ADB.
Installing GSIs is easy, just flash the system image to /system.
Click to expand...
Click to collapse
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
I literally just told you. GSIs come as an image. Flash to /system. Only works if the system partition is bigger than the image. Not sure how to safely resize.
There's also several guides around XDA that can help you. There's also the official Android Source guide.
Kind of wanted to follow up...
If recovery on Pixel isn't that useful (I don't know how much I agree with that. TWRP has saved me multiple times on my Pixel 5 and 2XL in the past), what is everyone doing for backing up/restoring the entire phone image?
100% agree. Both myself and a friend of mine never try new ROMs because we don't have a perfect backup of the current setup.
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
Which MIUI gsi did you try? thanks
mac231us said:
Which MIUI gsi did you try? thanks
Click to expand...
Click to collapse
All a13 on nippon chanel
Max0nchik said:
All a13 on nippon chanel
Click to expand...
Click to collapse
Thanks-I got this in hopes of trying some gsi's - returning it sadly ...and this is not related to your efforts but just in general about this device-am not interested in some super security graphene o/s etc....for that I simply take out my google account and don't sync (re-add it once in a while for some update) (and also remove many google apps, and change permissions in all or lock them down) regardless which flavor of android I am on....even the overlooked snooping gboard
Max0nchik said:
All a13 on nippon chanel
Click to expand...
Click to collapse
from what I recall on mi max 3, mix 2s etc when trying out gsi, there are other files that need to be flashed to make them boot-not sure how that can be done without a custom recovery
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
This should fix it without TWRP
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
Same for the b slot. You will find the needed images in the Factory Images ig.
Miustone said:
This should fix it without TWRP
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
Same for the b slot. You will find the needed images in the Factory Images ig.
Click to expand...
Click to collapse
this not work
DevanteWeary said:
Kind of wanted to follow up...
If recovery on Pixel isn't that useful (I don't know how much I agree with that. TWRP has saved me multiple times on my Pixel 5 and 2XL in the past), what is everyone doing for backing up/restoring the entire phone image?
Click to expand...
Click to collapse
Absolutely agree. I like to randomly change things and revert... Like all the time. This is the first phone I can't really play with the way I like.
https://www.reddit.com/r/Pixel6/comments/r8ylqf/_/i2u2n0p
This should help u understand. Btw. Lineage OS and some ROMs are coming with own Recoveries since quite a Time. Had Xperias for long without TWRP and it sucked. But TWRP has hard Times with modern Android so...
Since short I own a Pixel 6a with Android 13. I want to flash KernelSU in order to root it. How would I do? I'm asking because TWRP method drops out. TIA
unlock bootloader, download pre-patched boot image and flash it from fastboot.

Categories

Resources