Database Info

Best Method to Re-flash & Re-root Plus Have Internal Storage Working

Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!

bzowk said:
Hey Guys -
I have had my A9 for about 2 months and love it. When I first purchased it, I rooted it using the method pinned to this forum which seemed to work well. Soon afterwards, I found out that when I inserted and tried to format an SD card as "internal", it wouldn't work and result in it showing as "corrupted." I soon found out that this seemed to be due to the root replacing the original boot.img which messes with encryption. Since the root was posted, SuperSU has been updated and that step has changed supposedly.
Now that I have some time, I want to fix this issue. Before doing so, I've read through many posts and think I have a plan. I wanted to post the steps I need to follow as I understood them to make sure my plan is correct and will result in not only being able to format an SD internally and be rooted, but also a working phone Below are the specs of my phone, the steps I think it may take to resolve, and a few questions I have after reading through numerous posts. Any help is appreciated!
Phone Specs
Some as currently listed in Settings
- HTC One A9
- AT&T USA
- Rooted / s-off
- Android 6.0 / Sense 7.0g
Software Number: 1.10.502.3
Kernel: 3.10.73-perf-g28d66e0
Baseband: [email protected]_29.05_F
Build: 1.10.502.3 CL635081 release keys
Android Security Patch Level: 2015-10-01
Steps to Fix
1. Backup any data desired (I have a nightly Titanium backup)
2. Download RUU for same version (1.10.502.3) from http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Should I use newer version or are those for different carriers?
3. Apply RUU (via embedded EXE or try to extract and apply using adb/fastboot)
4. Once phone is restored, make a backup of boot.img from phone just in case it's needed later
5. Install TWRP via adb/fastboot
6. Install SuperSU via TWRP
At this point (if I can make it to this point), test and see if the phone's rooted and I can format the SD internally. If so, great. If not, continue with the following steps...
7. Download & flash modded boot.img from A9 Root post
8. Install TWRP via adb / fastboot
9. Install SuperSU via TWRP
10. Flash original boot.img backed up in step #4 to my phone (since modded one was only needed initially to install SuperSU) So that encryption keys match and I may successfully format sd cards for internal use
My Questions
1. Are the steps above basically the process i need to perform or is there a better / easier way? I don't know if I could flash a common boot.img from an RUU or if it needs to be flashed to phone first for encryption purposes. Even if I can, I've tried to extract it from ruu.zip before and could not
2. Should I use an RUU for a newer version (over 1.10.502.3) or are those for different carriers and not work with my AT&T phone?
3. Does it make a difference if I install the RUU via embedded EXE or extract and apply using adb/fastboot?
4. What versions of TWRP & SuperSU should I use?
Any additional suggestions would be appreciated - I just want to get this resolved once and for all! - Thanks!
Click to expand...
Click to collapse
First off, this isn't Development.
Secondly, I explained to you how to fix this in the very root thread you linked several times.
Thirdly, there's a newer, official RUU from HTC right on their ROM Downloads website. I'd start by installing that (though I also have a recovery-flashable version of that ROM in my Base ROM thread).
Fourthly, with access to an official RUU, and my ROM decrypt script, you have access to the stock boot.img (which is also in the firmware zip in my Base ROM thread), which you can use as your baseline for restoring the verity key to the ramdisk, thereby allowing you to use adopted storage without any issues. Note however that I was only able to use adopted storage with the "forceencrypt" flag enabled.
Fifthly, you can't just restore the stock boot image (at least not if you want to stay rooted). You can be both rooted and encrypted, but you have to first make sure SuperSU is flashed and set up prior to allowing the device to be encrypted again (adopted storage only works with an encrypted device, and then you won't be able to access your storage with TWRP).

OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!

bzowk said:
OK, OK - sorry.... It had been a while since posting and honestly forgot about that thread - my fault.
I decided to start fresh so have already restored the phone to HTC's latest RUU (1.27.502.5 ATT) as I already had it downloaded. I've also flashed TWRP 2.8.8.1 to the phone, but am obviously prompted to enter a password when I try to enter recovery. Based off what I've read, the steps below seem to be what I need to do so that I may be rooted + still have encryption for internal sd formatting. Is it correct (or close to it)
Using an Ubuntu 14.04 x86 VM...
1. Download & extract your decrypt script to a temp folder in linux vm
2. In Windows, run same RUU I applied and copy out rom.zip from %temp%
3. Rename "rom.zip" to "rom_a9.zip"
4. Copy rom_a9.zip to the ""place_rom_zip_here" folder of your extracted script in the vm
5. Run ./decrypt-htc and wait for script to complete to get img files
On Phone (Currently has same RUU installed + TWRP but not rooted)
6. Root phone using original method of flashing modded boot.img, install SuperSU, and get rooted
7. Once done and rooted, flash boot.img I extracted using your script above to phone via adb
Once that's done, it should be rooted + have encryption thus allowing me to use internal sd card, right? Sorry to be such a bother - just want to get this fixed and done with
Thanks!
Click to expand...
Click to collapse
Re-read my post. If you flash the stock boot.img, you will no longer be rooted.
And as I said in the original thread, you need to pull the rooted boot.img and add the verity key from the stock one to it. Also you'll need to add the forceencrypt and verify flag back.
P.S. You also need to re-read the instructions in the decrypt thread. You don't have to rename anything anymore.

Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks

bzowk said:
Good Afternoon -
OK - sorry to frustrate you, but I think I finally have it figured out. I started from scratch, re-read many posts, and took notes. I was a little confused on the last part so wanted to verify, please...
I've already unpacked the boot.img from the latest HTC A9 (AT&T) RUU and have the two folders. I restored the same RUU to my phone, flashed TWRP 2.8.8.1, backed up the boot.img, and unpacked it before realizing that I should have probably rooted it first.
Correct me if I'm wrong, but here's all I need to do to finish....
1. Download modified A9 boot.img from top of root thread
2. Flash modded boot.img using fastboot
3. Verify TWRP is still installed then use it to install SuperSU 2.67 (latest)
4. Back up boot partition just like I did before in TWRP
5. Unpack it on PC to create ramdisk and split_img folders
6. Copy verity_key from unpack of the actual RUU and overwrite one in rooted unpack
7. Edit the file fstab.qcom in the ramdisk folder of the rooted unpack in Notepad++ and add the "verify" flag after the wait flag on the fist uncommented line - save
8. Repack rooted boot.img
9. Flash phone with repacked boot.img using fastboot
10. Reboot & enjoy a rooted phone + encryption allowing sd internal formatting
Promise not to bug anymore if I can just get this resolved.
Thanks again for your assistance!
UPDATE
Hmm - was just prepping and went to download modded file from root thread's first post. Doesn't seem to have one that matches newest build of RUU I flashed - if I'm interpreting it correctly. Researching further, but if know of alternate method or another solution to get through steps 1 & 2 about (assuming they are correct), I'd appreciate it. Thanks
Click to expand...
Click to collapse
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?

Captain_Throwback said:
You don't need anything from that root thread. Everything there is deprecated (which I've said several times).
If you already have the stock boot.img unpacked and ready to go, all you have to do is flash SuperSU, then back up the rooted boot.img that you now have on your device thanks to SuperSU. Unpack that boot.emmc.win and add the verity_key from the stock ramdisk and replace the fstab.qcom with the one from the stock ramdisk. Repack, flash to your device via fastboot or TWRP, and your device will encrypt on that first boot and you'll be good to go.
Just to make sure - you did a Format Data in TWRP prior to flashing SuperSU, correct?
Click to expand...
Click to collapse
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!

bzowk said:
Thanks -
Well, that's the thing... One of the two unpacked boot.img I have currently is wrong. The two I have are:
- One unpacked boot.img extracted from latest RUU using your script in linux
- One unpacked boot.img backed up from unrooted phone which only had TWRP flashed
That was part of my question. I know that the 2nd unpacked boot.img above is worthless as the phone needed to be rooted prior to me backing it up. The question for me is how to flash superSU onto the phone (which currently has the same latest RUU + TWRP 2.8.8.1 installed) if I can only access TWRP is a read-only mode as I'm prompted for password upon booting to recovery. That's why I brought up the legacy root method as I don't know of an alternative... unless SuperSU doesn't require write permissions to whatever TWRP has locked down currently.
Once I can root it, backup it's boot, and unpack it; I just need to literally copy & overwrite the "verity_key" and "fstab.qcom" files (assuming the only difference is the fstab.qcom I'm overwriting doesn't have the verify flag), repack, then flash back to phone via fastboot, right?
Thanks for your patience!
Click to expand...
Click to collapse
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.

Captain_Throwback said:
Once you Format Data in TWRP and reboot recovery, you can flash SuperSU and you will be rooted. You just have to back up the boot.img after flashing SuperSU on the unencrypted device to re-enable verity so that adopted storage will work.
P.S. And no, the verify flag isn't the only difference. As I also said earlier (I'm constantly repeating myself), the device must be encrypted for Adopted Storage to work, so the forceencrypt flag from the stock fstab must also be present. That's why it's easier just to replace the whole file. The problem you have at the end of the day is that, while you'll be rooted and be able to use adopted storage in Android, you still won't be able to access said storage (or /data) in TWRP.
Click to expand...
Click to collapse
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
4. Flash SuperSU 2.76 zip
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
9. Flash newly packed boot.img to phone using fastboot
10. Enjoy
I really appreciate your help and patience with me!

bzowk said:
Great - Thanks!!
Just to make sure, below's my plan with a small question @ step #5. Does it get your stamp of approval?
Phone (A9) already had latest RUU restored (same RUU I ran against your script to pull boot.img from) and TWRP 2.8.8.1 flashed
1. Boot into TWRP & bypass initial screen prompting for password
2. Format Data
3. Reboot back into TWRP
Click to expand...
Click to collapse
Good so far . . .
bzowk said:
4. Flash SuperSU 2.76 zip
Click to expand...
Click to collapse
I'm sure this is just a typo, but that should be 2.67, not 76 (there is no 2.76).
bzowk said:
5. Reboot to system then back to TWRP and backup boot partition? / Stay in TWRP and backup boot partition? / Reboot back into TWRP and backup boot partition?
Click to expand...
Click to collapse
Bolded the correct one above (no need to leave TWRP as the necessary modifications have already been made).
bzowk said:
6. Unpack backed up boot partition from phone
7. Copy "verity_key" & "fstab.qcom" files from ramdisk folder in unpacked RUU boot and paste into & overwrite same files in ramdisk folder of unpacked boot from rooted phone
8. Repack rooted phone boot (which includes both new files)
Click to expand...
Click to collapse
Looks good . . .
bzowk said:
9. Flash newly packed boot.img to phone using fastboot
Click to expand...
Click to collapse
TWRP can also flash the new image, but fastboot is probably the most reliable way to do it.
bzowk said:
10. Enjoy
Click to expand...
Click to collapse
Hopefully . . . You'll likely get a reboot on the first boot (possible multiple reboots), as SuperSU needs a reboot to install the necessary files. Since your device will also encrypt on that initial boot, I'm not sure whether there will be a conflict or not.
bzowk said:
I really appreciate your help and patience with me!
Click to expand...
Click to collapse
Guess we'll see if it all works out . . .

Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!

bzowk said:
Thanks!
I proceeded by formatting data, booting directly back intoTWRP, flashing SuperSU, backing up the boot partition, then mounting and copying it over to my PC. The boot.img size was 65,536kb - the same size as the one I unpacked from the RUU. Once unpacked, it was missing the verity_key file and the fstab.qcom file was different + missing the verify flag.
I replaced those two files, then ran repackimg.bat which created image-new.img which I renamed to boot.img. Interesting, though, that this file was only 45,890kb. If it's a repack, shouldn't it be the same or similar? Anyways, the phone was still in TWRP (hadn't booted to system since before the format data) so booted it into bootloader directly and tried flashing boot using my new 45mb boot.img.
If failed - but - my phone was only at 17% power. Don't know if that's why it failed or not so it's charging right now while still in the bootloader. Below is what was echoed when I tried flashing it:
Code:
c:\adb>fastboot flash boot boot.img
target reported max download size of 800000000 bytes
sending 'boot' (45890 KB)...
OKAY [ 3.488s]
writing 'boot'...
(bootloader) HOSD CL#656287
FAILED (remote: 4 RU_BATTERY_LOW please connect charger (17% < 30%))
finished. total time: 4.506s
The reason I didn't boot to system is that I thought that was when the encryption might take place. Going to wait until above 30% power then try flashing again. Powered down to charge, but plan to boot straight back into bootloader to flash. If you see anything that stands out or that I need to do otherwise, please let me know. Otherwise, I'll report back what the result was after getting above 30%.
Thanks again!
Click to expand...
Click to collapse
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.

Captain_Throwback said:
The repack is smaller because the backup uses "dd" to copy the entire block device. Not all that space is actually used after compression. That's nothing to worry about.
And these devices are very picky about flashing only when there's sufficient battery, so I'm sure that's the only reason it failed. TWRP, however, doesn't care how much battery you have, so you could always flash the new boot.img in recovery.
Click to expand...
Click to collapse
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!

bzowk said:
Hey, hey, hey - think it worked!!
Once I got above 30%, I flashed without issue. I rebooted and was able to format an sd internally successfully, too. Now, I just need to verify it's rooted, but think it is. Thank you so much for your help! I'm going to write a guide for newbs like me to use in the future soon.
Thanks again!
Click to expand...
Click to collapse
If your adopted storage doesn't show as corrupted, and you're able to open the SuperSU app in your app drawer and not get a message that no su binary is installed, you should be good to go .

bad topic

Problems after Magisk update - can only enter download mode and recovery

Hey there,
I am currently struggeling with my Samsung Galaxy S7 (Exynos) device, running on superman rom (Android 8).
What happened?
For root I´m using Magisk Manager and for banking apps I have Magisk hide running. Then the program told me that there is an update (Magisk App) available. So, as always and recommended, I choosed "Direct Install" but that failed for some reason. OK I thought´, no problem. Later I wanted to reboot my phone but it didn´t. The screen says "Downloading.... Do not turn off device!". I only can enter "Download Mode" and "Recovery Mode via TWRP".
What I tried so far:
1) Wipe cache/dalvik --> not successful
2) Tried to do a factory reset via twrp --> not successful
3) Tried to flash BL via Odin --> not successful
At this time I realised that the same problem occured to my Galaxy Tablet SM-T580. So I came to the point that I did something wrong with updating magisk on both devides.
What I also tried next:
4) Tried to delete magisk modules via twrp --> not successful
5) Tried to uninstall magisk through twrp by downloading the latest Magisk app and rename it to "uninstall.zip" as recommended in installation guide --> Not successful because of Error installing zip file: Unsupported /Unknown image format (unpacking image format)
What can I do next?
Can anyone please help me, since I have two bricked devices now????

A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.

Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
Mohamedkam000 said:
A simple kernel flashing would fix the problem, extract the original boot.img of your current ROM, and flash it via TWRP.
Cause it is clearly a problem with your boot.img, if that didn't work (I'm sure it will), then just dirty flash your current ROM.
Click to expand...
Click to collapse
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Mohamedkam000 said:
P.S. If you are encrypted, you might encounter an error doing a simple factory reset, you'll have to format the whole data partition.
Click to expand...
Click to collapse
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.

capitarider said:
Hi @Mohamedkam000,
many thanks for your help. After hours of browsing the web and trying various methods I was able to get my 2nd device (Samsung Galaxy Tab A from 2016) back to life.
What I did: I installed the latest samsung mobile phone drivers on my PC then I connected the tablet to it. I was able to access the internal memory and in the folder "data" Magisk put a backup of the original boot.img. So I installed this "boot.img" via TWRP and voila.......everything works fine again
I´m very happy now.
But unfortunately this method didn´t work with my Samsung Galaxy S7. I just couldn´t find any boot.img file on the phone.
How do I have to do this? Sorry I´m a little unexperienced so could I get a kind of an step by step guide please?
Don´t understand this. Could you please explain again?
Thank you so much already.
Kind regards,
cap.
Click to expand...
Click to collapse
Glad your tablet revived again.
Magisk creates a backup of the boot.img found just before flashing magisk, it is compressed in gzip format, so you need to pull it, extract it, and push it back to the phone, then flash it.
The file is usually in /data/stock_boot_${SHA1}.img.gz
You can extract it using the built-in terminal of TWRP, if PC is not accessible at the moment by writing and executing the following command:
gunzip {stock-boot-name}.gz
Replace {stock-boot-name} with your backed-up boot name (without the curleybrackets), or you can use the following command:
gunzip *.gz
That'll extract the gzip archive, and the boot.img will be in /data of which you can navigate to it and flash it.
There's another guaranteed method, if you have the file of the ROM you're using right now, you can just open it (it's just a zip archive) and search for the boot.img of your specific phone model and flash it.
Another guaranteed method will be by flashing a custom kernel compatible with your current ROM, like Moro AiO kernel, of which has a wide support for ROMs starting from Oreo, and up to Q, AOSP, or stock-based, just in one file.
Moro's thread: Moro Kernel

you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot

aIecxs said:
you can't access kernel backup because TWRP does not support encryption and Magisk Manager might removed encryption in boot
Click to expand...
Click to collapse
Doesn't seem like he's encrypted, he found the boot backup of his tablet in /data so he has probably searched for a similar file on his S7, but since it is compressed, he won't find it solely.
Also he would've told us that his /data is empty or something.

start from scratch with older magisk, current 22 has bug
https://github.com/topjohnwu/Magisk/issues/4008

Thank you for your help.
I had a n old twrp backup on another external hard drive. I extracted the boot file and repached it with 7zip to boot.img and flashed through twrp. That also didn´t work for various times. TWRP always said "failed".
In the end I didn´t manage it to bring my phone back to live. Anyway, I decided to flash the latest LineageOS (Android 11) and now its running smooth again.
Thanks again.

Try using sp flash tools flashing the boot.img

[UPDATE / KEEP ROOT GUIDE] MAY 2021 (RQ2A.210505.002) - "CORAL" Magisk & Stock Boot / DTBO Images

(Sorry guys, this would have been up sooner, but Android File Host hasn't been letting me upload all day for some reason, so I just temporarily uploaded May 2021's files to my Google Drive for now instead. Enjoy! --- moved back to AFH )
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210505.002, May 2021"!
Magisk v22.1 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794185
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794183
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693794180
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ2A.210405.005, Apr 2021". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693776320
coral-rq2a.210405.005-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693776321
May 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210505.002-ca3e88b3.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq2a.210405.005-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210405.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq2a.210505.002-ca3e88b3.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210505.002-magisk_patched-22100.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdX/LSposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!

I am getting an error with unpacking the boot image with both the one provided as well as the one direct from Google. Any fix?

@AlphAndroid, I had no problem with Google's boot img. Maybe you should download the factory image again and check the SHA-256 checksum to make sure the download is not corrupt.
@i5lee8bit, thanks for the guide as always, worked fine! Just adding that the platform tools have been updated to r31.0.2 from r31.0.0: https://developer.android.com/studio/releases/platform-tools

AlphAndroid said:
I am getting an error with unpacking the boot image with both the one provided as well as the one direct from Google. Any fix?
Click to expand...
Click to collapse
What do you mean with unpacking the boot image? Are you trying to patch it yourself in Magisk Manager and talking about the step where it says unpacking the boot image? @Ghisy's advice is good, check the hash checksums. Here are various hash checksums of the untouched factory boot image for this month:
File: coral-rq2a.210505.002-factory-boot.img
CRC-32: cedb0fab
MD5: 987f7849b32f3a652c7d8378bbe0048a
SHA-1: f55f0e4a3fc7d4e321a4f8fea0cad157f371f564
SHA-256: d2a53c9527b21f51526a4343506b2617c8b78100c3e6fb90df517372493145ba
SHA-512: 9a3c027b5fdc9072c7955b01be5489060f66ff718ddf51dcd1350324f84d56219f20086cd8ce128721246d6b88c08fbb0de6642d3dec60c141f2496f42316364
SHA3-256: 74fe9d3d65f6e186dfc0c7708f12b7f308e2f014720fc8930549c7d2c349aaef
SHA3-512: 48d3890a8e014ff65d4e81fdaa9f13746aa4ab9632f6e600cebb1e697bff45ebbe22b16b205965d31e8056667361f217ad29db6f9a0b9d44927bfb065cf82f0c
Are you downloading from PC and then copying to the phone? If you're using MTP or FTP, sometimes they mess with the file in tiny, almost unnoticeable (annoying) ways. Try downloading directly from the phone (and check the hash while you're at it).

i5lee8bit said:
What do you mean with unpacking the boot image? Are you trying to patch it yourself in Magisk Manager and talking about the step where it says unpacking the boot image? @Ghisy's advice is good, check the hash checksums. Here are various hash checksums of the untouched factory boot image for this month:
File: coral-rq2a.210505.002-factory-boot.img
CRC-32: cedb0fab
MD5: 987f7849b32f3a652c7d8378bbe0048a
SHA-1: f55f0e4a3fc7d4e321a4f8fea0cad157f371f564
SHA-256: d2a53c9527b21f51526a4343506b2617c8b78100c3e6fb90df517372493145ba
SHA-512: 9a3c027b5fdc9072c7955b01be5489060f66ff718ddf51dcd1350324f84d56219f20086cd8ce128721246d6b88c08fbb0de6642d3dec60c141f2496f42316364
SHA3-256: 74fe9d3d65f6e186dfc0c7708f12b7f308e2f014720fc8930549c7d2c349aaef
SHA3-512: 48d3890a8e014ff65d4e81fdaa9f13746aa4ab9632f6e600cebb1e697bff45ebbe22b16b205965d31e8056667361f217ad29db6f9a0b9d44927bfb065cf82f0c
Are you downloading from PC and then copying to the phone? If you're using MTP or FTP, sometimes they mess with the file in tiny, almost unnoticeable (annoying) ways. Try downloading directly from the phone (and check the hash while you're at it).
Click to expand...
Click to collapse
i also used a hash checksum, checked out the same

I'm just a bit hesitant to use the provided patched boot image now that I'm getting the issue.

I also had an error at 96% sideloading the OTA (something like: sideloading failed, no error 0). I then did NOTHING, stayed in Bootloader and downloaded the latest adb platform tools (mine was 30.0.5 from nov 2020, rather old) - with the newest platform tools I sideloaded again and then it worked (even though it stayed on 90% for 3-4 minutes, idk why, after that it smoothly went to 100% and finished sideloading) - then after that just normally flash the magisk patched file and the phone booted up again and is working fine. It seems to be more important than I thought to have the most up to date adb tools - never had an issue with that before. Thankfully my phone didnt go into bootloop, lol.
So it seems that the newest Pixel 4 xl OTA file is uncompatible with (maybe specific) older adb platform tools, ergo people if you have a problem, check your platform tools version - the OTA file that is linked here in this thread is fine and is not the rootcause of any issues.
Best place a remark into the mainpost @i5lee8bit that it is very important to keep the adb platform tools up to date and always check it before trying to update. It might save some people from trouble.

Hello all.
I need a little help please.
I am coming from:
10 (QQ2A.200305.003)
Magisk 21201 / 8.0.4
It’s been a while since I have done this and I would like to update to the Android 11 May version and I would like to make sure that what I am about to do is procedurally correct.
And, I am hoping this is the correct place to post
Download 11.0.0 (RQ2A.210505.002, May 2021 (coral-rq2a.210505.002-factory-0ec4212f.zip)
Unhide/Uninstall Magisk - Restore Images
Is this necessary with a factory reset?
Factory reset
Boot phone into fastboot mode
Flash-all.bat –w
At this point, once the phone re-boots, I should have a “working” phone on Android 11?
Extract boot.img and copy to phone
Download Magisk-v23.0.apk to phone and install
Do I set the update channel to beta or canary?
Install/select & patch boot.img
Reboot
Copy patched boot.img to computer
reboot into fastboot
Should I / could I fastboot flash boot boot.img --slot all at this point just to be safe?
Fastboot flash boot patchedboot.img
Fastboot reboot
Safetynet fix
Set update channel
Enjoy.
Am i missing anything?
Thanks in advance
ƒ

Tutorial : Root Galaxy S10 Series Android 12 One UI 4.1 Stock Firmware

Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk ​Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 - UI 4.1 Latest Version (I tested G970FXXSGHWC2) ​(Without combination keys for active Magisk after normal restart – Without press power key for warning massage booting) ​
How to root:
1. Extract your downloaded Rom and patch AP file with magisk (Recovery Mod)
2. Go to download mode.
3. Uncheck auto reboot in Odin.
4. Flash your patched AP file with BL CP CSC.
5. When flash passed, again we should go to download mode.
6. Hold volume down and power key, and after vibration release power key and hold Bixby key and volume down for going to download mod again.
7. Reset Odin and again uncheck auto reboot, put twrp recovery,
To AP and flash, it.
8. When passed, we need again reset and go to twrp recovery, volume down power key, after vibration release volume down and hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release.
9. We should be in twrp recovery mod, format data, rename magisk.apk to magisk.zip, copy magisk.zip, kernel, multi disabler and twrp boot logo to the sd card.
10. Mount your sd card and install first magsik.zip, then multi disabler, twrp boot logo and finally kernel.zip
11. Restart to system.
12. After booting to android 12 open the magisk app and let download the latest version.
13. When download finished open magisk, you will see one massage for install complete magisk after reboot in 5 seconds, cancel it and go to setting and active Zygisk and Magisk Hide, rename it.
14. When magisk hide process finished. Open again magisk, you will see the reboot massage again.
15. Tap ok and wait for rebooting.
Fix Internal Storage Size:
First Format Data.
If it doesn't work :
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​
After reboot, your galaxy is rooted without any problem. And you can install modules zips. And enjoy your root same stock Rom without any opened bootloader warning massage first of booting android. And without press power key after that.
---------------------------------------------------------------------------------------------------------
UPDATED (G970FXXSGHWC2) Android 12 - One UI 4.1 - March 2023​​For update your android without losing data, follow these steps:​1. Download: One of Kernels - Multidisabler Samsung 3.5 - TWRP Bootlogo Patch - Magisk - Odin 3.14.1-3B Patched.
2. In Odin uncheck Auto reboot, flash (BL - Patched AP File with Magisk - CP - Home CSC).
3. Reboot manual to download mode again, Flash TWRP Recovery in AP slot.
4. Reboot to TWRP recovery, flash Magisk.zip, Kernel and Multidisabler then TWRP Bootlogo.
5. Reboot to system and finished.
Download the latest Firmware version for your galaxy here: https://samfirms.com
Download the latest TWRP recovery version for your galaxy here: https://twrp.me/Devices/Samsung/​Download the latest Magisk version for your galaxy here: https://github.com/topjohnwu/Magisk/releases​
Special Thanks to Ambasadii Dev. And CruelKernel Develop Team For Kernels. Magisk Dev. TeamWin For TWRP Recovery And Odin3 Patched.​

Happy to see your post!
I have Android 11 FUL1, with Magisk 23000 (last versioin with Magisk Hide and Modules) and last Official Twrp and I want to pass to Android 12.
So my question:
May I patch android 12 AP file G970FOXMEGVA4 and patch also twrp but under Android 11 and Magisk 23000?
My aim is to maintain the Twrp already present and to avoid to install stock Android 12 only to patch AP file and twrp.
Then I should start immediately with Odin, AP patched, twrp patched, multidisabler, kernel and all the orther things.
Is this possible?
And just for info, your kernel is the same as Ambasadii rom?

will try but, what to do with Downloaded Kernel?

Hello everybody, thans for the work.
I tried your method but it's not working for me.
All is good until step 7.
At Step 8, the phone restarts good on TWRP but a script is executing and the phone restarts.
On this restart, i do like you explain (hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release) but the phone don't restarts in TWRP and the phone vibrate instead, then the phone is freeze on SAMSUNG logo
EDIT : A resolved it by flashing the CSC file instead of the CSC HOME file.

is.Mehrdad said:
Root Samsung Galaxy S10 Series Android 12, WITHOUT Ramdisk
Root Samsung S10+ - S10 - S10e SM-G97xxx, Stock Rom Android 12 Latest Version (I tested G970FOXMEGVA4)
(Without combination keys for active Magisk after normal restart – Without press power key for warning massage booting)
Sorry For Bad ENGLISH
https://1drv.ms/w/s!AiUnkR9HkhduiqRfflrkvHqg5Ai_lQ?e=fIGiFi​
Downloads:
1. Download the latest stock ROM for your galaxy here: https://samfirms.com
2. Magist the Latest Version 24.0: https://bit.ly/3rYnEzQ
3. Kernel: https://bit.ly/3o55bR1
4. TWRP Recovery, The Latest Version: https://bit.ly/3ADTk1F
5. MultiDisabler: https://bit.ly/3r693mY
6. TWRP Boot logo: https://bit.ly/33TNrRT
7. Odin 3.14.4: https://bit.ly/3o67YcG
How to root:
1. Extract your downloaded Rom and patch AP file with magisk (Recovery Mod)
2. Go to download mode.
3. Uncheck auto reboot in Odin.
4. Flash your patched AP file with BL CP CSC.
5. When flash passed, again we should go to download mod.
6. Hold volume down and power key, and after vibration release power key and hold Bixby key and volume down for going to download mod again.
7. Reset Odin and again uncheck auto reboot, put twrp recovery,
To AP and flash, it.
8. When passed, we need again reset and go to twrp recovery, volume down power key, after vibration release volume down and hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release.
9. We should be in twrp recovery mod, wipe data, rename magisk.apk to magisk.zip, copy magisk.zip, kernel, multi disabler and twrp boot logo to the sd card.
10. Mount your sd card and install first magsik.zip, then multi disabler, twrp boot logo and finally kernel.zip
11. Restart to system.
12. After booting to android 12 open the magisk app and let download the latest version.
13. When download finished open magisk, you will see one massage for install complete magisk after reboot in 5 seconds, cancel it and go to setting and active Zygisk and Magisk Hide, rename magisk to “manage” (without R).
14. When magisk hide process finished. Open again magisk, you will see the reboot massage again.
15. Tap ok and wait for rebooting.
After reboot, your galaxy is rooted without any problem. And you can install modules zips. And enjoy your root same stock Rom without any opened bootloader warnning massage first of booting android. And without press power key after that. ​
Click to expand...
Click to collapse
Fantastic instructions! Worked like a charm....except that my internal storage has gone from 128gb, to 32gb.
How can this be resolved?
I notice that the instructions did not include flashing vbmeta. Could this be problem?

BlaqqSL8 said:
Fantastic instructions! Worked like a charm....except that my internal storage has gone from 128gb, to 32gb.
How can this be resolved?
I notice that the instructions did not include flashing vbmeta. Could this be problem?
Click to expand...
Click to collapse
After step 8 you are in TWRP Recovery, You must “Format Data” in TWRP then again boot your device to TWRP recovery. After Wipe data, vbmeta and your storage will be fixed.​
Be careful, After Wipe Data don't boot in OS, because you must pass other steps before boot to OS.​

bruram said:
Happy to see your post!
I have Android 11 FUL1, with Magisk 23000 (last versioin with Magisk Hide and Modules) and last Official Twrp and I want to pass to Android 12.
So my question:
May I patch android 12 AP file G970FOXMEGVA4 and patch also twrp but under Android 11 and Magisk 23000?
My aim is to maintain the Twrp already present and to avoid to install stock Android 12 only to patch AP file and twrp.
Then I should start immediately with Odin, AP patched, twrp patched, multidisabler, kernel and all the orther things.
Is this possible?
And just for info, your kernel is the same as Ambasadii rom?
Click to expand...
Click to collapse
No, not working, you should install multidisabler and other files in twrp recovery.
Kernel is same

DelNero said:
Hello everybody, thans for the work.
I tried your method but it's not working for me.
All is good until step 7.
At Step 8, the phone restarts good on TWRP but a script is executing and the phone restarts.
On this restart, i do like you explain (hold volume up and bixby key with power key after splash release power key and hold your volume up and bixby for 1 second then release) but the phone don't restarts in TWRP and the phone vibrate instead, then the phone is freeze on SAMSUNG logo
EDIT : A resolved it by flashing the CSC file instead of the CSC HOME file.
Click to expand...
Click to collapse
Happy for resolved problem.
But I wrote in step 4 CSC File, Not CSC Home.
4. Flash your patched AP file with BL CP CSC.

is.Mehrdad said:
After step 8 you are in TWRP Recovery, You must “Wipe Data” in TWRP then again boot your device to TWRP recovery. After Wipe data, vbmeta and your storage will be fixed.​
Be careful, After Wipe Data don't boot in OS, because you must pass other steps before boot to OS.​
Click to expand...
Click to collapse
Thanks for the quick reply.
Just one more thing: Can I flash vbmeta in the CP slot, at the same time as flashing TWRP in the AP slot? Or do I have to flash them individually?

BlaqqSL8 said:
Thanks for the quick reply.
Just one more thing: Can I flash vbmeta in the CP slot, at the same time as flashing TWRP in the AP slot? Or do I have to flash them individually?
Click to expand...
Click to collapse
I don't think so
What is exactly the problem with vbmeta ?

is.Mehrdad said:
I don't think so
What is exactly the problem with vbmeta ?
Click to expand...
Click to collapse
There's no problem with vbmeta that I know of. It's just that, following your instructions, I still only have 32gb of internal storage instead of 128gb.
It would really help if you could update your instructions to include flashing the vbmeta file either via Odin, or using vbmeta.img in TWRP.

BlaqqSL8 said:
There's no problem with vbmeta that I know of. It's just that, following your instructions, I still only have 32gb of internal storage instead of 128gb.
It would really help if you could update your instructions to include flashing the vbmeta file either via Odin, or using vbmeta.img in TWRP.
Click to expand...
Click to collapse
Test this, if not working, I will test again all of my files.
After flash your patched AP, Boot to TWRP and mount all of your partitions, then restart again to twrp recovery and then do Wipe Data and again reboot to recovery for flash other files.
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​

is.Mehrdad said:
Test this, if not working, I will test again all of my files.
After flash your patched AP, Boot to TWRP and mount all of your partitions, then restart again to twrp recovery and then do Wipe Data and again reboot to recovery for flash other files.
Boot into TWRP recovery.​
Select Wipe » Advanced Wipe.​
Tick/check the Data partition.​
Select Repair or Change File System button.​
And lastly, select Resize File System button. (Let TWRP resize your file system. It might take some time, have patience)​
Click to expand...
Click to collapse
From reading many posts\instructions on how to install\root A12, I think that, where you say "WIPE DATA", It should be FORMAT DATA - YES.
I'm going to try it that way, and will let you know ow it goes.

BlaqqSL8 said:
From reading many posts\instructions on how to install\root A12, I think that, where you say "WIPE DATA", It should be FORMAT DATA - YES.
I'm going to try it that way, and will let you know ow it goes.
Click to expand...
Click to collapse
Thanks, I edited my post to Format Data.

So I followed all the steps. I did everything and everything worked as it should. However, when I get to magisk wanting to update, it does so, patches everything successfully but on restart, I get a bootloop.

Hello. Does anybody try to do it on USA Snapdragon model?

How do we install magisk with ap file?

patched ap file I did as you said but it won't load. It gets stuck loading system.img.

VenfefulRat said:
So I followed all the steps. I did everything and everything worked as it should. However, when I get to magisk wanting to update, it does so, patches everything successfully but on restart, I get a bootloop.
Click to expand...
Click to collapse
Same thing here....
Impossibile to update magisk

Gamras606 said:
patched ap file I did as you said but it won't load. It gets stuck loading system.img.
Click to expand...
Click to collapse
Uninstall Samsung drivers and install it again, reboot your pc and check it again with another USB port.

How To Guide [Pixel 7 Pro] [TD1A.220804.031] Root guide + Extracted Images + How to

How to root:
You have two options for this, 1 is the recommended way and 2 is the lazy but works way.
Option 1 (RECOMMENDED):
Download the latest factory image from: https://developers.google.com/android/images#cheetah (at the time of writing this, it's TD1A.220804.031
Unlock bootloader (If you don't know how to do this, do not proceed further)
From the downloaded image file, extract the init_boot.img file and copy it to your phone (directory shouldn't matter)
Install the Magisk apk from: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
Launch the app, select install, patch a file, select the init_boot file you placed in your phone
After it's done, it should place a file in your phone's download folder called magisk_patched-<VERSION>_<XYXYXYXYXY>.img
Copy that over to your PC and now boot to bootloader
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Option 2 (LAZY BUT WORKS):
I'm sharing my magisk patched init_boot from the TD1A.220804.031 build (post 73MB update). Instructions are:
Unlock bootloader (If you don't know how to do this, do not proceed further)
Boot to bootloader
Download the patched init_boot from: https://sourceforge.net/projects/ag.../magisk_init_patched-25205_EfWOu.img/download
Run the following commands from Powershell/commandline:
Code:
fastboot flash init_boot magisk_init_patched-25205_EfWOu.img
And then reboot, you'll be rooted
Install Magisk apk from here: https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-release.apk
To get SafteyNet working:
Open the Magisk app
Open the settings from top right, Enable Zygisk
Reboot
Flash the MODIFIED SafteyNet fix module by @kdrag0n from the attached files on this thread from within Magisk Modules
Clear Play store data and you should be good!
Voila!
FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!
VERIFY THE MD5 OF THE FILE AFTER DOWNLOADING!!!!!!!
Mirror 1 | Mirror 2
MD5: 43613f520697722840ded6a15eb27459
Massive shoutout to @Some_Random_Username for Mirror 1 and @akhilnarang for Mirror 2 since SourceForge was facing issues!
Now documentation on how to do it yourself (which I'd highly recommend since you should never trust any file given, always try to do it yourself!):
How to dump your own device:
1. Download a GSI which is userdebug/eng and equal/newer Security Patch of the current build on your device from any of the unofficial community builds here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
2. Install the DSU Sideloader app from: https://github.com/VegaBobo/DSU-Sideloader/releases/latest
3. Follow instructions in the DSU sideloader app readme here: https://github.com/VegaBobo/DSU-Sideloader/blob/master/README.md
I'd recommend enabling the userdata toggle and typing 32GB as the size
4. Reboot into the DSU from the notification
5. When the device boots up, type the following in the terminal:
Code:
adb root
adb shell
mkdir -p /sdcard/dump
for file in /dev/block/bootdevice/by-name/*; do
if [ "${file##*/}" != "userdata" ]
then
echo Dumping "${file##*/}"
dd if=$file of=/sdcard/dump/"${file##*/}".img
fi
done
6. Once the dump is done, you'll have files in /sdcard/dump/
7. Copy those over to a PC
8. Voila

A massive thanks to @AndyYan @Some_Random_Username for their help (well hand holding) throughout the entire process <3
Also thanks to @OmkarTheAndroid for the re-brush up of the Android basics I forgot

Reserved

Thanks!

Have you had any luck with SafetyNet yet? People on another thread are saying that even the Modded version by @Displax isn't working on P7P with Canary Magisk

I'd like to remind all that, 1) the DSU method requires some Android/shell knowledge to correctly carry out, and 2) you're discouraged from actually flashing/using those GSIs (TD-based Android 13 GSIs are still in early phase, and P7/P will almost certainly get proper, fully functional device-specific ROMs shortly anyway).

Thanks for the dump! Could you maybe mirror it yourself to be sure? At least until Google's facory images are up Sourceforge is incredibly slow for me (and probably for others too).

so looks like vendor_dlkm has been replaced by vendor_kernel_boot and the init_boot is just the first-stage init. This will be interesting moving forward with AVB and custom images. I will start working on something when source drops. I will likely need to have some testers to see how much this requires to get a custom image up and running.
EDIT: vendor_boot is actually the one that has been separated out a bit between vendor_boot (holding modules) and vendor_kernel_boot, which has some ramdisk stuff like the vendor_boot has on Pixel 6 devices.
Kernel now consists of 6 images. init_boot, vendor_boot, vendor_kernel_boot, vendor_dlkm, dtbo and boot.img

I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro

mrteii1 said:
I downloaded the init_boot.img file then got a big problem bricked my pixel 7 oro
Click to expand...
Click to collapse
this is a soft brick, just flash the correct partition back using the stock image

Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking

I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?

whatsisnametake2 said:
I think i'll hold fire on rooting until things are a little clearer. unlocking the bootloader in the usual fashion should be ok tho right?
Click to expand...
Click to collapse
Yes, unlocking the bootloader is still the same and will wipe data.

Current SafetyNet Status (with modded universal SafetyNet Fix + Magisk Props):
Play Integrity API Checker:
MEETS_DEVICE_INTEGRITY: fail
MEETS_BASIC_INTEGRITY: pass
MEETS_STRONG_INTEGRITY: fail
YASNAC:
Basic integrity: pass
CTS profile match: fail
Edit: GPay does work on the Pixel Watch, even though it doesn't on the phone (when rooted).
Make sure to add your cards there if you're using the Pixel Watch and can't use GPay on your phone.

zetsumeikuro said:
Yes, unlocking the bootloader is still the same and will wipe data.
Click to expand...
Click to collapse
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.

mrteii1 said:
Tahnks forbyour reply. How to get the stock image? Now it brickes. Im panicking
Click to expand...
Click to collapse
In the OP, the part with:
"FASTBOOT IMAGES:
I'm sharing the stock extracted images of the TD1A.220804.031 build, should be a good reset point from fastboot incase any of you get stuck somehwere:
DO NOT MIRROR THIS PLEASE!!!!"

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?

Misterxtc said:
If you can boot to recovery try a factory reset from there or you will have to power it off and wait until Google releases the image.
Click to expand...
Click to collapse
Maybe you replied to the wrong user?

Hey everyone, a slight update on the website for the image dump, SourceForge was giving people incomplete files so @Some_Random_Username is generously hosting it on his servers <3
please verify the MD5 of the downloaded zip before trying to modify any parititons using the following commands:
On windows:
Code:
certutil -hashfile cheetah-TD1A.220804.031-compressed.zip MD5
On Linux/MacOS:
Code:
md5sum cheetah-TD1A.220804.031-compressed.zip
The MD5 should be: 43613f520697722840ded6a15eb27459

whatsisnametake2 said:
? unlocking is just going to do a data wipe/factory reset anyway. not sure why I would need the factory image for that? or to do an additional factory reset from recovery?
Click to expand...
Click to collapse
I was thinking the reset would force it to boot off the other slot.