[Solved] I think I messed my phone up - Verizon HTC 10 Questions & Answers

I have an HTC 10 VZW on .18
I had Magisk 12 and SuperSU 2.79 systemless installed.
TWRP is recovery.
I uninstalled SuperSU with its app's permanant uninstall
thinking to reinstall via TWRP later.
After doing the diagnostics that VZW said I needed to do.
I went to reinstall it and found even though its zip installed
correctly in TWRP I did not have root.
I was thinking if I backup the data partition with TWRP
and the /sdcard directory via MTP .
I thought maybe I could restore via
2.41.605.18_Firmware_No_Boot.img_No_Recovery.img_No_Dzdata_chunks.zip
which should leave boot, recovery & data (& /sdcard) alone. then redo magisk and supersu to recover?
Does this contain everything in RUU except the noted partitions?
Code:
2.41.605.18_Firmware_No_Boot.img_No_Recovery.img_No_Dzdata_chunks.zip
aboot_signed.img
adsp.img
android-info.txt
apdp-8996-1.img
apppreload.img
cache.img
cmnlib32.img
cmnlib64.img
cota.img
cradio.img
cs_cy8c.img
devcfg-8996-1.img
dsp.img
fsc.img
hosd_signed.img
hyp-8996-1.img
keymaster.img
lksecapp.img
pg2fs_ship_signkey.img
pmic-8996-1.img
radio.img
rfg_2.img
rpm-8996-1.img
sensor_hub.img
slpi.img
splash1.nb0
tp_syn3708.img
tz-8996-1.img
usb_typec_otp.img
usb_typec_otp_ad.img
venus.img
xbl-8996-1.img

fuzzynco said:
I have an HTC 10 VZW on .18
I had Magisk 12 and SuperSU 2.79 systemless installed.
TWRP is recovery.
I uninstalled SuperSU with its app's permanant uninstall
thinking to reinstall via TWRP later.
After doing the diagnostics that VZW said I needed to do.
I went to reinstall it and found even though its zip installed
correctly in TWRP I did not have root.
I was thinking if I backup the data partition with TWRP
and the /sdcard directory via MTP .
I thought maybe I could restore via
2.41.605.18_Firmware_No_Boot.img_No_Recovery.img_No_Dzdata_chunks.zip
which should leave boot, recovery & data (& /sdcard) alone. then redo magisk and supersu to recover?
Does this contain everything in RUU except the noted partitions?
Code:
2.41.605.18_Firmware_No_Boot.img_No_Recovery.img_No_Dzdata_chunks.zip
aboot_signed.img
adsp.img
android-info.txt
apdp-8996-1.img
apppreload.img
cache.img
cmnlib32.img
cmnlib64.img
cota.img
cradio.img
cs_cy8c.img
devcfg-8996-1.img
dsp.img
fsc.img
hosd_signed.img
hyp-8996-1.img
keymaster.img
lksecapp.img
pg2fs_ship_signkey.img
pmic-8996-1.img
radio.img
rfg_2.img
rpm-8996-1.img
sensor_hub.img
slpi.img
splash1.nb0
tp_syn3708.img
tz-8996-1.img
usb_typec_otp.img
usb_typec_otp_ad.img
venus.img
xbl-8996-1.img
Click to expand...
Click to collapse
Dont use that. A couple of other people have had issues with that firmware package.
I think you need to flash another clean boot image, then reflash magisk, and you should be set. Just dont flash the zip package. It doesnt contain the boot.img anyways

Related

Cannot browse files to Flash in TWRP

After manually flashing files to upgrade to 6.0.1, I flashed TWRP 2.8.7.0. But I am not able to flash supersu from sdcard because when I browse to the folder, it looks empty.
Anyone has any idea why this is happening?
if you have not formatted userdata after you flashed the recovery img in fastboot that would be one reason, the other reason could be if you used a pin/pattern/password for your phone. if you disable that or format the userdata in fastboot then you should be able to see it.
TWRP 2.8.7.0 didnt support decryption, and that may be why you cant
starting with 2.8.7.1 and now 2.8.7.2 it does support decryption.
Please download 2.8.7.2 and flash that and report back, bet ya its going to work fine after that.
MPAI said:
After manually flashing files to upgrade to 6.0.1, I flashed TWRP 2.8.7.0. But I am not able to flash supersu from sdcard because when I browse to the folder, it looks empty.
Anyone has any idea why this is happening?
Click to expand...
Click to collapse
You're using an outdated version of TWRP, it can't decrypt your storage. Update to the latest version and it'll be fine.

Guide to Update OOS ROM on rooted phone without loosing TWRP

Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.
Reserved
Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.
Lossyx said:
Why not just flash magisk directly after flashing the ROM? In that way recovery stays and you have root.
Click to expand...
Click to collapse
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.
kapil_dheer said:
OOS Rom needs a boot before magisk.
If you flash magisk directly after rom flash, it bootloops.
Click to expand...
Click to collapse
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.
FMXP said:
No? You have always been able to flash Magisk directly after an OOS update. You are installing the full zip, not the incremental correct? If so, flash the full zip from TWRP, then flash Magisk right after, then clear cache/Dalvik, then reboot. Everything works after that.
Click to expand...
Click to collapse
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.
paour said:
I just installed 5.1.2 this morning and flashing oos and Magisk together worked fine, and I still have TWRP.
Click to expand...
Click to collapse
Yep, same here, I've also flashed TWRP img right after flashing the ROM, just to be sure it's still there, then Magisk zip and custom kernel, everything works fine, no bootloop here.
kapil_dheer said:
Hi Friends,
For every incoming update, full ROM gets downloaded & after flashing via TWRP, TWRP recovery gets replaced by stock recovery, of course we loose root.
Only way to get back TWRP is via Fastboot commands, flashing TWRP & Finally Magisk. This might not be a big deal to many but certainly much to those having limited access to PC.
After many hits & misses, I was able to update my 1+5t without needing to reflash TWRP & maintaining ROOT.
Word of Caution:- Before giving it a go, please take a TWRP backup of your current setup & keep it safe......just in case anything goes wrong.
I am not responsible for any bootloops / bricked devices. Proceed at your own risk.
The procedure has been tested by me since last 3 updates & did its intended work well.
Prerequisites:- 1+5t with unlocked bootloader, TWRP already installed & rooted by MAGISK.
You can achieve plenty of & much detailed guides on how to unlock the BL, flash TWRP via Fastboot & root by Magisk.
Tools Used- A file manager capable of handling zip files.......my personal choice X-plore File Manager, free version from playstore.
The fun part begins:-
1. Download the full ROM.zip from whatever source of the OOS ROM you intend to install.
2. Make a copy of the ROM to work upon.
3. Open the zip file in the file explorer.
4. Select boot.img & copy it to some other folder. I selected Magisk Folder.
5. Now open Magisk Manager & Click Install.
6. Press Install again.
7. Out of available options, press Batch Boot Image File.
8. File explorer will open. Navigate to place where you copied boot.img from zip file (magisk folder in my case).
9. The phone will start downloading Magisk zip file.
10. After the download completes, it will start patching your boot.img.
11. Do not reboot & get back to MagiskManager folder.
12. A new file in the name of patched_boot.img gets created.
13. Delete original boot.img file.
14. Rename patched_boot.img to boot.img.
15. Select the boot.img & copy it back to the zip file from where original boot.img was extracted.
16. System will ask for overwrite permissions. Grant it.
17. The file manager will repack the files to form a final flashable zip file.
Your modded Rom.zip is ready to flash via TWRP recovery.
This flash should update your system while keeping your TWRP & Root installation intact.
Please give your feedback for the results achieved.
Any queries are welcome.
Click to expand...
Click to collapse
Thank you so much after trying everything and still getting bootloop your method worked.. ?? thanks for such easy solution
kapil_dheer said:
You sure? I tried it plenty of times but it bootlooped every time.
I'll try this anyhow in next update again.
Click to expand...
Click to collapse
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.
Lossyx said:
But doesn't flashing full ROM uninstall magisk? I've updated 9 times without flashing Magisk uninstaller, works fine for me.
Click to expand...
Click to collapse
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.
I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?
perama said:
I used the procedure of this threat to update to OOS 5.1.2. Everything is OK except the Smart Lock menu. I lost it completely! All Smart Lock options are gone! Any ideas?
Click to expand...
Click to collapse
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!
rquinn19 said:
Known bug, unrelated to anything discussed in this thread. Remove Smart Lock from Trust Agents, reboot and re-enable. Happens over and over though. Annoying!
Click to expand...
Click to collapse
Thank you very much my friend!
BigBrosMo said:
You would think so but I've also had bootloop issues which required flashing the uninstaller. So now I just make it part of my routine.
Click to expand...
Click to collapse
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk
jmtjr278 said:
Are you also wiping caches when you were getting bootloops? Wiping caches does pretty much nothing. I have never uninstalled magisk or wiped anything. Just make sure to remove substratum theme. I have forgotten that and gotten bootloops.
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
Wiped caches in between ya. I don't use substratum but I do use xposed though Magisk. I think it has to do with that but am not certain. At any rate, I just use the uninstaller (it's two extra clicks) and don't have any more problems. This was back in January that I had these flash/bootloop problems. Maybe it's not an issue anymore but I just have my routine and it works so...
My steps are when i was in 5.1.1 OOS ( I modified some system parts so downloaded full 5.1.2 OOS firmware)
Removed Pattern/Password (For Safety)
Enter TWRP
Wipe Cache
Wipe Dalvik Cache
Wipe System
Flash 5.1 .2
Install TWRP.img
Flash Magisk
Flash No Verity zip
Reboot
No PC needed. Yea its booted and all apps are there. No data lose..
Flashing uninstaller was not successful when I tried to install 5.1.1 and 5.1.2.
Baldesarra said:
You can flash magisk right after the full ROM. BUT!!!
For an update without bootloop or without loosing TWRP you have to do this:
Go to TWRP
Flash Magisk Uninstaller
Delete Dalvik and Cache
Flash full ROM (Update)
Flash Magisk
Delete Dalvik and Cache
Reboot
The key is to flash magisk Uninstaller before updating. Then you won't get a Bootloop
Click to expand...
Click to collapse
I use the simple method of downloading the full Update ZIP to my phone, rebooting to TWRP, clearing caches, flashing the Update ZIP, flashing Magisk, clearing caches and reboot. That way always worked for me.
No need for such a complicated process based on my experience.

Help! OP 6t McLaren 9.0.12 won`t boot into system after Magisk update /uninstall

Hi everybody,
I have a OP 6T McLaren, Oxygen 9.0.12 and I tried to uninstall Magisk 18.1 and update to Magisk 18.2 canary and something went wrong. After flashing I got the following error:
!Unable to unpack boot image
---
Updater process ended with ERROR: 1
Error installing zip file `/sdcard/Download/magisk-uninstaller.zip
The same error when I try to flash any Magisk version.
Phone doesn`t boot into system now. I can fastboot into TWRP and access files and folders.
Thank you very much in advance for your help.
Flash the magisk uninstaller then reboot. Then flash magisk.
I can't flash magisk uninstaller or magisk. It gives me the above error.
Even if I flash twrp installer in temp twrp it installs without error but after reboot it boots only in bootloader.
What can I do now to get the system working again?
-flash stock boot.img (where do I get file for McLaren 9.0.12?
-use MSMdownloadtool from here?
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
flash this ota via temp twrp?
https://forum.xda-developers.com/oneplus-6t/how-to/official-oxygenos-9-0-4-ota-oneplus-6t-t3860953
Try
Reflash OOS 9.0.12
Flash twrp
Reboot recovery
Flash magisk
Reboot system
Backup your data
Sent from my OnePlus6T using XDA Labs
Mclaren uses the same stock restore image.
I've been there format data .my friend let's his SD card encrypt or get errors on top of letting twrp (wrong version won't decrypt data either) if you do that reboot in system make sure adb is on and oem and auto updates are off
use different twrp the test build works better I had problems with orginal TWRP too
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
kika1992 said:
Solved!
All I had to do was flashing stock boot.img to boot_A and boot_B. Now It's working again...
Thank you very much for your help.
Click to expand...
Click to collapse
Ah.. Stuck in exactly same situation. Did you unzip the stock rom and flash boot.img through fastboot? Or did you take any different steps?
Niks.
Yes, unzip and flash both files via fastboot.
Just a note.
When installing Magisk and TWRP; I always install Magisk in one slot and reboot. I then use a partition backup tool to grab the stock boot image.
I then flash the stock boot image so the phone is completely stock again.
At this point I go through the TWRP and Magisk install the normal way.
I do this so I can always flash back to stock.
I also don't care about retaining TWRP or root.
I just start all over. It takes a few minutes but I don't usually have issues.
I also local install the same ROM to both slots before I install anything.
This way the opposite slot will always boot with the same version of the ROM.

Need help about twrp

so I'm in twrp 3.2.3-0 and using custom roms without flashing that decrypt.zip and i want to update my twrp what to do?
and if i want to update, can i flash the img file via twrp?
Download higher twrp.img file and flash via exsisting twrp in recovery partision ,your recivery will be updated.

(help me) how to install twrp on android 10 fw407?

I reinstalled fw 060 and lost twrp, then I continued to upgrade to fw407 and started reinstalling twrp and now I can't install twrp anymore, I have tried many ways (still unlocking bootloader). Everyone help me reinstall twrp.
is your bootloader locked or unlocked?
Twrp flashing process is same as earlier. Unlock bootloader if it is not already and flash recovery from fastboot. Reboot to recovery before 1st boot...
Harry_00s.HS said:
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
Unlocked bootloader.
satyajeetb said:
Twrp flashing process is same as earlier. Unlock bootloader if it is not already and flash recovery from fastboot. Reboot to recovery before 1st boot...
Click to expand...
Click to collapse
Has unlocked the bootloader before.
Hehehe
1. Backup ur data
2. Wipe everything
3. Extract the boot.img, save to xternal sdcard, Flash rom (407)
4. After 1st boot, follow the instructions until homescreen
5. Download and install latest magisk manager canary
6. Patch boot.img with magisk, save to external "sdcard/otg"
7. Reboot to bootloader, flash twrp, reboot to twrp
8. Format data, reboot twrp again, flash magisk_patched.img from ur xternal sdcard
9. Flash decrypt.zip 059 from Mr. sagar makhar
Reboot system
10. Done, sorry for bad english???
I've already installed magisk+edxposed and gravitybox...thx
Normanbayuaji said:
1. Backup ur data
2. Wipe everything
3. Extract the boot.img, save to xternal sdcard, Flash rom (407)
4. After 1st boot, follow the instructions until homescreen
5. Download and install latest magisk manager canary
6. Patch boot.img with magisk, save to external "sdcard/otg"
7. Reboot to bootloader, flash twrp, reboot to twrp
8. Format data, reboot twrp again, flash magisk_patched.img from ur xternal sdcard
9. Flash decrypt.zip 059 from Mr. sagar makhar
Reboot system
10. Done, sorry for bad english???
I've already installed magisk+edxposed and gravitybox...thx
Click to expand...
Click to collapse
So the decrypt work? That's great
8vasa8 said:
So the decrypt work? That's great
Click to expand...
Click to collapse
No, without modified boot image (magisk_patched.img)

Categories

Resources