Related
Well, first of all, this is not my work, I'm just sharing this guide that worked for me, it should work on any kirin device.
I have a P10 (VTR-L29C432), don't ask me if it works on X device, just try it for yourself as I did.
1) You need an unlocked bootloader and FRP
2) If you don't want to lose any data, backup your internal memory, because you'll need to do some wipes on stock recovery.
3) Reboot into TWRP and flash the "Huawei_remove_encyption_data_2.zip", here's the link: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-decrypt-data-mate-9-hi3660-t3834748, you can use blackball's TWRP (p10 plus) or twrp from Honor 9 lite forum (both works on any emui and pie's rom, but you'll need and sdcard in order to flash the file)
4) After that, reboot into bootloader and flash your stock recovery and wipe data and cache
5) Reboot again into bootloader and flash again your favorite Twrp.
Some Twrps:
https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 P10 plus TWRP
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 Honor 9 Lite TWRP
https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917 Honor View 10 TWRP
https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993 P10 plus TWRP (blackball)
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 Themes for TWRP, download and flash as a normal zip.
If your device isn't hi3660 (kirin 960), you'll need to do it manually, first go to vendor/etc and look for a file called "fstab......" (you'll need to remember that name), go to the zip file that you previously downloaded and extract it, go to the folder vendor/etc and you'll see the fstab.hi3660 file, rename it with the name of your fstab and paste it into vendor/etc (if it ask for overwrite, hit the YES button), reboot and do the wipes on stock
If it was useful for you, go and say thanks / donate to @micky387 for their work and to the Devs that made possible the tools that we use. :highfive:
did it work on oreo 8.1 based roms ? (problem is with encrypted data partition)
yes, it works.
for me it wont work... TWRP stuck at TWRP screen
Edit
ok, i flashed recomended recovery from tutorial and now works
thanks
doktor29 said:
for me it wont work... TWRP stuck at TWRP screen
Edit
ok, i flashed recomended recovery from tutorial and now works
thanks
Click to expand...
Click to collapse
The p10plus recovery?
sfoot13 said:
The p10plus recovery?
Click to expand...
Click to collapse
nope, this dont work for me... it stuck on TWRP logo
i flash one from tutorial, twrp_recovery.img
in order to make any twrp working, first you need to reboot into fastboot and type fastboot -w, after that flash any twrp and follow the steps, I tried it with many recoveries, even with p10plus version.
Actually I'm using one from PRA forum, it works with custom roms
but internal memory is encrypted, but is not a problem for me.
i flash 3.1.1 twrp for oreo 8.0 based roms
this one see more partition to backup like others
@micky387 updated the files and the process, so I updated the thread all the credits to him
sfoot13 said:
Well, first of all, this is not my work, I'm just sharing this guide that worked for me, it should work on any kirin device.
I have a P10 (VTR-L29C432), don't ask me if it works on X device, just try it for yourself as I did.
1) You need an unlocked bootloader and FRP
2) If you don't want to lose any data, backup your internal memory, because you'll need to do some wipes on stock recovery.
3) Reboot into TWRP and flash the "Huawei_remove_encyption_data_2.zip", here's the link: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-decrypt-data-mate-9-hi3660-t3834748, you can use blackball's TWRP (p10 plus) or twrp from Honor 9 lite forum (both works on any emui and pie's rom, but you'll need and sdcard in order to flash the file)
4) After that, reboot into bootloader and flash your stock recovery and wipe data and cache
5) Reboot again into bootloader and flash again your favorite Twrp.
Some Twrps:
https://forum.xda-developers.com/showpost.php?p=77262856&postcount=166 P10 plus TWRP
https://forum.xda-developers.com/9-lite/development/recovery-twrp-3-2-1-0-t3789306 Honor 9 Lite TWRP
https://forum.xda-developers.com/honor-view-10/development/recovery-twrp-3-2-1-0-t3769917 Honor View 10 TWRP
https://forum.xda-developers.com/p10-plus/development/recovery-twrp-3-2-1-0-oreo-t3734993 P10 plus TWRP (blackball)
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 Themes for TWRP, download and flash as a normal zip.
If your device isn't hi3660 (kirin 960), you'll need to do it manually, first go to vendor/etc and look for a file called "fstab......" (you'll need to remember that name), go to the zip file that you previously downloaded and extract it, go to the folder vendor/etc and you'll see the fstab.hi3660 file, rename it with the name of your fstab and paste it into vendor/etc (if it ask for overwrite, hit the YES button), reboot and do the wipes on stock
If it was useful for you, go and say thanks / donate to @micky387 for their work and to the Devs that made possible the tools that we use. :highfive:
Click to expand...
Click to collapse
Why would you need to unlock the data ?
haddadadam35 said:
Why would you need to unlock the data ?
Click to expand...
Click to collapse
why you quote the whole post?
That's annoying.
Do you know MP? Just asking because it's out of context. If you want to teach lessons, why do it on public instead of MP which is ethical.
And yes I'm doing the same mistake, but I hope to prevent many.
Will I be able to enrcypt my system on a ROM Basis afterwards? I want an encrypted device but I also want to be able to do backups in TWRP.
hansiohne said:
Will I be able to enrcypt my system on a ROM Basis afterwards? I want an encrypted device but I also want to be able to do backups in TWRP.
Click to expand...
Click to collapse
I experimented similarly on two P9 phones with Oreo, and was able to encrypt back by doing:
Install latest + Factory reset from eRecovery
Of course, before eRecovery, you must revert to stock Recovery (and stock eRecovery, Kernel if they were flashed over) and unroot (stock Ramdisk) - without you risk a brick
Edit: Also, while having decrypted Data and internal memory, successfully received an OTA patch (Huawei stopped updating but sent a smalll OTA patch to the existing firmware)
zgfg said:
I experimented similarly on two P9 phones with Oreo, and was able to encrypt back by doing:
Click to expand...
Click to collapse
But as I said I don't want to encrypt back because if I had no need to permanently decrypt (for TWRP backup reasons, I have berkeley and encryption doesn't work there on TWRP) I wouldn't do it. Instead, I want to decrypt and then do a normal device encryption in AICP. Or am I getting it wrong and it's the same type of encryption in the end?
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Sebaxe07 said:
My phone just got the android 9 update, I already had installed root with twrp on my device with android 8.0
So when I tried to re-root my phone I needed to reinstall the TWRP but it couldn't decrypt the data
I tried all of the posible solutions to this but nothing
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Do I need to wait until someone update the TWRP version or what can I do?
Thanks in advance
Click to expand...
Click to collapse
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
SubwayChamp said:
Formatting data have to decrypt it, you have to be sure that TWRP is able to mount data partition.
Click to expand...
Click to collapse
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Sebaxe07 said:
So I need to erease all of my phone data to be able to use twrp? But why it didn't have this problem the first time?
Click to expand...
Click to collapse
You are upgrading now; for this you need to decrypt it for first time and probably every time that you switch from a miui to an AOSP rom. Be sure that your data partition is mounted and I guess you can´t see the files under TWRP. Try first with this zip https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Stock Miui re-encrypt data on first boot after factory reset, so you need to flash Universal DM-Verity
I also need TWRP for pie.
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Thanks
SubwayChamp said:
Try this recovery, It has more features than TWRP https://sourceforge.net/projects/orangefox/files/test_builds/OrangeFox-R9.0-1-platina.zip/download
Click to expand...
Click to collapse
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
cidxtc said:
Would you happen to know if opengapps aroma works with this recovery. I have tried 3 or 4 other revoveries and once options are selected and install starts recovery reboots. After that I have to hold power to force reboot because no matter what reboot option I choose it just goes back to recovery.
Click to expand...
Click to collapse
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
SubwayChamp said:
Unfortunately I can't tell you for sure cause left 3 days to unlock my bootloader but I used this recovery in two Xiaomi devices (R5Plus and Mi Max) and was the best I ever tried, never had issue flashing Aroma zips.
Be sure that once finished the installation Reboot box in Aroma be unticked
Click to expand...
Click to collapse
Never had an issue with redmi note 4x and aroma either. The reboot box does not make a difference because the install never happens. I will download and try.
Sebaxe07 said:
I think that is the TWRP version that can't decrypt data in android 9.0
But in the web isn't any version that support the Mi 8 LIte with Android 9.0
Click to expand...
Click to collapse
If you are using the wzsx150 3.2.3 twrp found under the ROM/recovery section, versions 0121 and 0212 are both supposed to be for Android 9. I haven't tried myself though, as I am still on 8.
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
So heads up for anyone trying to use open gapps aroma installer. No recovery will install it. Tried batik, orange fox, perp, and wzsx150 twrp and all do the same. After all the selections when the actual installation starts the device reboots (installs nothing but does save setting options) back to recovery. All reboot options (system, fastboot, etc) all reboot back to recovery only holding power button will allow device to boot into system.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
MetallicGR said:
I can confirm version 0212 does indeed decrypt data partition, making it mountable it inside TWRP. Of course phone's now running on official Android 9 MIUI 10, updated on Wednesday.
Click to expand...
Click to collapse
Any idea why is 0212 half the size of 0121, and the others for that matter (28MB vs 60MB).
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
MetallicGR said:
I believe it's somehow compressed. If you open these files with something like 7zip you'll see the size is very close between the two.
Click to expand...
Click to collapse
Oh okay. That would make sense.
lexridge said:
I am using wzsx150 3.2.3-1003 and it does not decrypt data, even with proper password.. Where can I find 0212. I cannot find it in this forum. ..only the bad one I am using.
EDIT: Nevermind. Found it.
Click to expand...
Click to collapse
Can yo share the 0212 img to Pie I'm stll in Oreo and the Pie update notification is a little annoying so I want to update but I haven't found the twpr 0212 for mi 8 lite.
Here you go. https://forum.xda-developers.com/showpost.php?p=78876979&postcount=46
Another member replied to your other thread as well.
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Click to expand...
Click to collapse
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Fcleon said:
Hi everyone so I am about to root my Poco F1, but my main objective is just root it with magisk and install some modules, mainly something that block ads, and something to control the battery, so it doesn't charge pass 80%, I can find those modules, but in essence that is what I want.
- I have backed up everything and I have activated oem unlocking and usb debugging, and I have also opened the mi unlock app on windows and I need to wait just one more day to unlock the bootloader.
- I need to be sure about the next steps, so as far as I know, and correct me please if I am wrong, after that I need to install TWRP (I guess I should download it from https://twrp.me/xiaomi/xiaomipocophonef1.html) or should I use another version?, I have read that the official has touch issues, also I wanna be sure about the security part, I read that if I just wanna root with magisk I should just use fastboot boot TWRP, so it is just temporary and like more secure, it will help me a lot to know the differences, but as I told, I just need something simple root it with magisk, maybe do a backup of everything for safety reasons and that's it.
- I should I also flash DM-Verity , ForceEncrypt and Diskquoata disabler? even if I just want a simple root with magisk?
Any way I think that after that, the other step is just flash the latest version of Magisk right?
Thanks in advance guys
Click to expand...
Click to collapse
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
YasuHamed said:
i am on 3.3.3-1 unofficial, the touch issues fixed in this one
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
download link
https://mega.nz/#F!bdwQVIyK!OWNLH72HNT-ecmC-vAVmPw
- Magisk disables Dm Varity itself while flashing
- but for DFE you need to flash saperate Disable Force Encryption - Treble.zip
i replied similar question(s) and more YESTERDAY at https://forum.xda-developers.com/showpost.php?p=80170044&postcount=3
if you can manage some time, Please do read ~ its about rooting to custom rom flashing
edit: https://www.youtube.com/watch?v=BsHtfLh6azw plz see
Click to expand...
Click to collapse
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
guhvanoh said:
Yes, that's the correct place to get the TWRP image file from. You've backed up so that's good. Make sure the PC you're using has USB 2.0 ports. If it only has USB 3.0 ports you'll need an external USB 2.0 hub for this to work. fastboot boot the TWRP image file and backup using TWRP. I backup system image, vendor image, boot & data. You don't need System or Vendor. Flash Magisk and install the Magisk manager apk. I use AdAway for blocking ads which requires root. You don't need to flash dm-verity, DFE or diskquota disabler. Nor do you need to worry about security.
Click to expand...
Click to collapse
Alright then, I have another question, I am right now on 10.3.7 when Xiaomi releases a new version how do I update it, after rooting, normal OTA or I need to do another process?
Fcleon said:
Ok but in my situation and for the things that I am gonna do, do you really think I need to disable DFE and the other things?, disabling all this things are for what reason?
Click to expand...
Click to collapse
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
YasuHamed said:
now the question is SHOULD you be disabling DFE and if yes why? if no WHY ?
Google has been putting great efforts recently to keep users data secured !
force encryption encrypts data (internal storage) for the user . however it consumes battery and later if you are trying to flash roms , there are high chances you will be locked out! because twrp cannot READ that encryption. hence after installing rom, if you go back to twrp! and try to access internal STORAGE, twrp will give your error that unable to Mount storage!
now at the time CLEAN FLASHING if you had flashed DFE, it will DISABLE GOOGLE Encryption and twrp will able to access your data
Click to expand...
Click to collapse
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Fcleon said:
Alright so in theory is better to disable force encryption to improve battery and to have the option to install a custom ROM, although at the moment I do like MIUI. And what about disk quota disabler ? What is the reason to disable that?
And if I disable FDE I have to permanent install TWRP ? Because since I just want magisk for the moment I wanted to just use TWRP temporarily and like for making my phone kinda more secure if someone steals it from it
Click to expand...
Click to collapse
1. for disk quota disable or not and why please read more on this subject at https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389. (mainly to make storage stats faster, disk quota is used and to obsolete them you disable it)
2. Twrp is the flasher! and you can flash any modes, roms (designed for the device in your hand!) hence you don't have to keep it flashed! you can call the twrp from fastboot command from pc when you want to!
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Fcleon said:
Thanks everyone I finally unlocked the bootloader, and then used fastboot boot TWRP, backup up everything, then flashed magisk, and then FDE, I can say that the device feels much faster, maybe is the placebo effect but anyway I like it.
The last question that I have is what happens when Pocophone releases a new stable version?, should I just use TWRP and flash the ota file? and i guess flash magisk again and fde again right?
Click to expand...
Click to collapse
What I always do when updating is:
1. fastboot boot twrp
2. uninstall magisk
3. install full rom (not ota)
4. install magisk
5. reboot
6. install magisk manager
7. install modules
Is there a system app or security feature on the sm-j737p 9.0 pie U7 that needs to be disabled in order to gain root access? I cant get it to flash any su on the device nor get magisk to work right on it. I cant find a guide that will work for it. Is it unrootable?
Look inside here.
jwoegerbauer said:
Look inside here.
Click to expand...
Click to collapse
Iv seen and followed that guide before, when I flash twrp onto my device it fails. I'm on android 9.0 pie U7.
I cant get two to flash.
dunnothename said:
Iv seen and followed that guide before, when I flash twrp onto my device it fails. I'm on android 9.0 pie U7.
I cant get two to flash.
Click to expand...
Click to collapse
If not already done yet, unlock phone's bootloader and also disable Android's AVB & Android's dm-verity .
jwoegerbauer said:
If not already done yet, unlock phone's bootloader and also disable Android's AVB & Android's dm-verity .
Click to expand...
Click to collapse
I cant get the bootloader unlocked cause the phone doesnt go into fast boot mode
dunnothename said:
I cant get the bootloader unlocked cause the phone doesnt go into fast boot mode
Click to expand...
Click to collapse
Read here
nope, isnt working . cant disable any dm-verity or AVB, theres no fastboot mode on this phone, the usual things that go into rootin a samsung isnt possible with this one for some reason
Success!!
I got it rooted
. Stock firmware AP > Magisk > magisk.tar > Odin > flash > Root.
Hi can you possibly tell me where I'm going wrong, I've been at this for hours and can't seem to get it working. So based on the guide I've been following, I got the correct firmware file for my phone and then flashed it with magisk. I turn off the phone and put it in odin mode where I flash the patched tar file. Then it says to immediately put the phone in recovery mode, which I do, and wipe the data then reboot and it should be root with Magisk installed. However, this does not happen, instead it just runs through the new phone setup where it downloads a system update and there's no way to bypass it. I also tried flashing twrp, and I made sure it was the latest version and for my model yet when I try to flash twrp and boot straight into recovery (or not, it doesn't matter what I do at this point) the phone just bootloops until I put it back in odin and flash the firmware again. I just don't understand, I've rooted many phones and tablets and I've had a lot of trouble but there always seemed to be more resources and people having similar issues that would help.
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
If the file size was wrong, you were probably using the wrong file...although there's been issues with the latest Platform Tools, and bad USB cables can cause problems too.
TheMystic said:
Boot to fastboot mode and install TWRP or any custom recovery on both slots.
Now reboot to recovery and change the active partition.
Click to expand...
Click to collapse
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
V0latyle said:
TWRP isn't really relevant to A/B devices unless installing a custom ROM. If he's able to get into bootloader, TWRP isn't going to be any more help than reflashing the factory image.
Click to expand...
Click to collapse
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
TheMystic said:
In case of a bootloop, one can boot into recovery if it is installed on both slots. And from there the active partition can be changed, and this is possible only using custom recovery.
This is my understanding. I could be wrong because it's been a while since I got away from all these stuff, which are also becoming increasingly complex for no proportionate returns.
Click to expand...
Click to collapse
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
You could potentially live boot TWRP since this doesn't flash the boot partition, but again this is generally unnecessary and won't be of much help when you can simply reflash the original boot image
V0latyle said:
The problem is, the recovery kernel is packaged into the boot image alongside ramdisk and the system kernel. Most A/B devices like Pixels do not have a recovery partition. TWRP does not support the compression that's used for the stock recovery as packaged, and if you flash the TWRP image to /boot, it overwrites everything else - meaning that your system will only boot to TWRP, because that's the only thing in /boot.
Click to expand...
Click to collapse
Are all these done to enhance security or discourage custom mods? Or both?
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
TheMystic said:
Are all these done to enhance security or discourage custom mods? Or both?
Click to expand...
Click to collapse
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
TheMystic said:
For a short time when I had rooted my OnePlus 8T, I would flash TWRP on the inactive slot. That's because Oxygen OS would replace any custom recovery with its own recovery during boot, so this allowed me to boot into the inactive slot (which now has TWRP) and then run commands from there, so I don't have to use a PC each time.
Click to expand...
Click to collapse
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Xeust said:
Hi! I was on the February update and was trying to update to the March update using the factory images.
While updating I was faced with sparse file too big or invalid error. Then my device was stuck at bootloader. After that, I proceeded to stupidly change my active partition from b to a. Now my device won't boot at all. Is there any way I can recover from this? Or is there a chance at all?
Click to expand...
Click to collapse
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Lughnasadh said:
The likely reason this occurred is because you used Platform Tools 34+. These 34 versions can't boot into fastbootd. For now you should be using Platform Tools 33.0.3.
You can't just switch slots and boot up the slot you switched to. You can only boot into the slot where the last firmware was flashed to. Therefore, when you changed your slot from b to a, you would have to flash the firmware onto slot a before it would boot into that slot.
If you can still get into the bootloader/fastboot mode, try flashing the factory image or using Android Flash Tool.
Click to expand...
Click to collapse
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
V0latyle said:
What happens when you turn your device on? Are you able to boot to bootloader? Does the screen turn on at all?
Click to expand...
Click to collapse
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that, its only a black screen.
Is there any way to flash the firmware or change the partition through other means that does not require bootloader/fastboot?
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Xeust said:
For now its not booting at all. My pc can still detect it for a moment while I'm holding the power button but its not booting into bootloader so I can't do anything at the moment afaik.
Nope. Nothing and as I mentioned above, my pc only detects it while I hold the power button. Aside from that its only a black screen.
Click to expand...
Click to collapse
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Lughnasadh said:
There have been several people who have ended up like you after using Platform Tools 34+. None have been able to recover that I know of. The issue is known to Google (they are working on a fix). Can you confirm you were indeed using Platform Tools 34.0.0 or 34.0.1?
Click to expand...
Click to collapse
Yes it was the 34.0.1
V0latyle said:
Ah. It sounds like the bootloader can't start, so the device is probably in QUSB mode. Unfortunately your only recourse is to have it repaired, as the files and tools you'd need to fix this are not publicly available. While it's possible to find the software (QPST/QFIL) you won't be able to find the necessary binary images to reflash your device.
Click to expand...
Click to collapse
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Xeust said:
Yes it was the 34.0.1
If there's nothing I can do on my own, is it still possible to get it repaired? Or my only option is to send it back to google?
Click to expand...
Click to collapse
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
V0latyle said:
If you're still under warranty, try to get repair that way. Warranty or no warranty, Google will probably refer you to a repair center like uBreakiFix.
Click to expand...
Click to collapse
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Xeust said:
Unfortunately not under warranty anymore. And its hard to reach google. or ubreakifix from my country :/
Thank you everyone. I conclude that my chances are pretty slim so I guess I'll consider getting a new phone.
Click to expand...
Click to collapse
If you do end up contacting Google, you can refer them to this issue. Frankly it's there fault. They know their current Platform Tools are borked and yet still leave them up on the site for people to download and use.
Anyway, I wish you luck.
For those of you having the Platform Tools 34+ bug, as I did because I'm old and stupid at times, you may want to go thank this guy since using the 33.0.3 version of the PLatform Tools
did the trick for me.
V0latyle said:
Neither. It's just compression to reduce the amount of space the recovery kernel takes up in the boot image. If TWRP supported this compression we could potentially replace the stock recovery with TWRP. But, there isn't really much need to do this; most custom ROMs for the Pixel series just flash everything via web ADB.
That's not the case here. The boot slot cannot be changed without booting into TWRP. You could potentially install TWRP to boot_b, then set slot B as active; upon the next boot, the device will load TWRP. You could then do whatever you need to in TWRP, then set slot A as active, but you'd have no way of getting back to TWRP.
Click to expand...
Click to collapse
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Deleted, since it's not for here.
Jaitsu said:
Wait, hold up. TWRP? On the Pixel 6? That exists?
(edit: nevermind, think I misread)
Click to expand...
Click to collapse
That What I want to know!