TWRP and Encryption password for data. - HTC 10 Questions & Answers

Hello there! thanks for your time.
I swear that I tried everything.
I received my HTC 10 like 1 almost 2 weeks ago.
I unlocked the bootloader, flashed the recovery, supersu, everything just fine. Everything works. Except that when I boot into the recovery TWRP ask for the password to decrypt /data. I put my pin = password failed. I tried to resetting the pin, tried putting a password, leaving it blank (tested default_password too) but I cant make TWRP work mounting /data. It always says that password is incorrect.
I even tried factory reset 2 times.
the version is: 3.0.2-2
Any ideas?
Thanks again guys! have a great day!

Anytime its asked me for a password I just press cancel.

My understanding is that the HTC 10 in encrypted by a proprietary HTC code.
Yep - just hit Cancel on that screen.
See the TWRP thread here - http://forum.xda-developers.com/htc-10/development/recovery-twrp-touch-recovery-t3358139
"NOTE: TWRP CANNOT decrypt HTC Sense ROMs!!"
And this in the second post
"5. My storage is encrypted, and TWRP can't decrypt it. How am I supposed to flash anything?
First, hit the "Cancel" button at the decryption prompt to continue to the TWRP Main Menu. Storage doesn't need to be decrypted to root the device or flash custom ROMs. If storage is decrypted on this device, mobile network will stop working.
6. Is it possible to retain encryption AND make a data partition backup in TWRP?
No. TWRP cannot currently decrypt /data on this device. That is due to HTC's use of proprietary encryption. Until someone figures out a way around that, the only way to access /data in TWRP is to unencrypt using the "Format Data" option in TWRP and disabling the forceencrypt flag in the ramdisk (which will break mobile network in Android)."

Hey! thanks!
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
well thanks again guys!!

deftoner said:
That is what I did, I hit cancel and flashed everything. But now there is an OTA Update. I downloaded, hit install, and the phone reboots on recovery, I thought that the password was needed in order to process the update.
Click to expand...
Click to collapse
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.

iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.

btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now

iteese said:
That's exactly what I did. And I just learnt (see my question here) that you can't install OTA updates with a custom recovery image installed. It seems, you'll either have to give up on the OTA update or you need to flash the stock recovery image to be able to install the OTA update.
There's a stock ROM in this thread. I THINK that rverts the recovery image as well. But it's a Euro ROM, not sure how that impacts other region phones.
---------- Post added at 01:21 AM ---------- Previous post was at 01:03 AM ----------
Here's the stock ROMs and stock Recovery image thread:
http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
You need to get the CID and MID of your phone first. I followed these instructions very easily.
I'm going to try flashing the OTA update for my model.... once I've read it all.
Click to expand...
Click to collapse
deftoner said:
btw I guess I flashed the incorrect recovery. Need to select the correct version I'm trying that now
Click to expand...
Click to collapse
If you're US unlocked variant, you can follow my guide, here:
http://forum.xda-developers.com/htc-10/how-to/guide-how-to-ota-receive-corrupt-message-t3378187
If you're another variant, reply in the above thread and I can help you find the versions of the files you need to flash.

deftoner said:
Hey, thanks for your reply.
In fact its easier than that, on this guide you have the recovery images to flash it back. http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
I flash the recovery back, and applied the ota, I have an error about the version of the ota for the phone, but you may have better luck.
Click to expand...
Click to collapse
Reboot download
Make sure your mid matches the US one (I had super cid for mine but apparently if the mid doesn't match it will give error as well)
fastboot getvar all
will tell you
then once it was all set
fastboot flash zip nameof_file.zip
DO IT TWICE!
Then reboot your download to see if the changes took place
You then have to reflash your TWRP recovery because the zip will flash stock recovery
if you are still getting the password box, click cancel for TWRP, wipe > advance and wipe data
good luck

With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"

Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
Are you asking for help?

jollywhitefoot said:
Are you asking for help?
Click to expand...
Click to collapse
No... I'm just complaining.

Orch4rd said:
No... I'm just complaining.
Click to expand...
Click to collapse
OK cool. Carry on then.

Orch4rd said:
With this encryption thing going on I can't even do a complete advanced wipe: "unable to mount storage"
Click to expand...
Click to collapse
you could...i do it often before flashing new build....

Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.

CryptoJones said:
Thanks for this thread. I spent an hour typing all of my different passwords into the phone trying to figure it out what it was. Then I hit cancel per this thread.
Click to expand...
Click to collapse
hay I really need help as in phones setting in security tap is says "encrypt phone - phone is encrypted".
is that a good thing? I want my phone to be "data" unlocked if u know what I mean? help
also I got my phone about 3 weeks and unlocked the bootloader but S-on and I live in Europe.
I try the rom with f2fs support and always when I try to boot the rom with "data" and "cache" formatted as f2fs it doesen´t boot and I try to boot the compatible rom and kernel with ext4 first and when I got a full boot I go to recovery to format cache and data as f2fs but this time when it boots "data" reverts back to ext4 and cache stays as f2fs?
any idea!
I use disk info app and is it because my phone is encrypted data never stays as f2fs or something else as I don´t know much about "decrypt or uncrypt" and the other...
thnx!

TWRP not PIN Pattern
Moved this post to main TWRP

Related

phone stuck on HTC boot screen and other stuff

I recently got a htc one m8 that is stuck on the boot screen.
i can get into the bootloader and fastboot seems to work.
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
if i reboot normally it goes back to the bootscreen with the green htc logo.
if i try to go to hboot adb doesn't recognize the device.
so i'm stuck now. i've read several tutorials and tried various things but have no idea where to go from here.
i can tell you that the bootloader says its unlocked and that its set to s-on and there is no os installed.
help
jodahall said:
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
Click to expand...
Click to collapse
Try fastboot erase cache, and flash TWRP again with fastboot.
What is your hboot number, and what TWRP version are you trying?
Also, was your phone recently updated OTA for the Stagefright patch? If so, its a known issue that this recent update does not work with TWRP for some folks.
jodahall said:
if i try to go to hboot adb doesn't recognize the device.
Click to expand...
Click to collapse
This is as it should be. adb doesn't work in hboot. You need to be booted into OS to use adb, possibly will work in recovery (but you can't boot into recovery, so that doesn't really matter).
my hboot version is 3.19.0.0000
i am trying to flash the latest twrp
I have not gotten the ota, this phone has been sitting in a drawer for about 6 months so nothing new has been applied.
I will try erase the cache and reflash the twrp
jodahall said:
i am trying to flash the latest twrp
Click to expand...
Click to collapse
What number TWRP exactly? And you're sure its the TWRP file for the M8, right?
I ask for the number, since I've seen at least a couple times where the person claims they are trying to use the "latest" or "current" TWRP. But when I ask for more info, it turns out the version is not even close to current.
Best to be specific when talking about version numbers.
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
I also tried your advice and from a command window erased the cache and then reflashed. It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Sent from my A0001 using XDA Free mobile app
oh, it worked. I am one step closer as it booted into the custom recovery.....whoohooo
I ran the command "fastboot format cache" from a dos prompt a couple of times, there were errors the first two times, then the 3rd time it created it without error.
ok onto the next steps that are in Vomers guides....
thanks for all your help
jodahall said:
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
Click to expand...
Click to collapse
You are correct, that is latest version (and correct one for the M8). You might re-download just to eliminate the possibility the file wasn't corrupted.
jodahall said:
It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
Click to expand...
Click to collapse
If you are still intending on doing this, don't try any version older than 2.8.4.0 or so. TWRP versions much older than that, won't work on hboot 3.19. TWRP will install and seem to work fine, but after you flash the ROM, the ROM won't boot.
jodahall said:
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Click to expand...
Click to collapse
In the technical sense, the emmc chip does have a finite number of times it can be flashed.
But in reality, I think the number of times the emmc can be flashed before failing is (supposedly) something in the thousands.
Of course, things sometimes fail before they are supposed to, and every extra flash may put you closer to that point (in theory). But I don't let that stop me from flashing what I want, whenever I want to. And flashing recovery a few extra times is not going to hurt anything much IMO.
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
jodahall said:
thanks for all your help
Click to expand...
Click to collapse
There's a button for that!

How to flash official nougat without wiping internal storage?

Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Edit : Nougat running on my op3.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
anshulajain said:
I was the same predicament as you. I finally took the plunge and now I have Nougat running on my OP3. Here is what I did :
Start: OOS 3.2.8 w/ custom kernel and modified TWRP
1. Flash stock recovery (Google for a forum post in the OP3 forums on downloading the stock recovery and flash it through fastboot)
2. Reboot and let 3.2.8 start
3. Download Snap VPN and change the country to Canada. You will be prompted for the system update.
4. Let the update download (~1 GB)
5. Install the update. You may see an error of the installation may fail as your phone is rooted. Ignore and go ahead.
6. The installer will now boot to stock recovery and reboot with Nougat. All settings and apps will be maintained
The only catch is that you may have ext4 instead of f2fs. I am okay with it for now... But your mileage may vary
All the best!
Click to expand...
Click to collapse
I don't have any issues with ext4, infact i do feel ext4 is more stable than f2fs so file system is my last concern. Thanks for your method, but then how did u root again? Installing nougat is fine but what after that? I have read that you can't use modified twrp without formatting internal memory first, as it'll show you the pin issue. Let me know how do you propose a safe method to achieve root.
Renosh said:
Are you rooted? Are you encrypted? What file systems are you using for your partitions? You're not giving full information. Why is formatting not an option if it'll give you the results you want?
Click to expand...
Click to collapse
Yes i am encrypted, rooted, stock OOS 3.2.8 + Franco kernel. Official TWRP(not modified). I am using ext4, never used f2fs at all. The time to backup data and then to restore it all back is the reason formatting is not an "preferred" option for me. I can do it, but i would have to wait until i find enough time to do the whole process. I am in a full time job, so i hope you would understand.
Puddi_Puddin said:
To get to F2fs (I do recommend it)
Take a backup of your Data partition. , copy it to your pc with "adb pull /sdcard/Twrp/whatever".
Now go to Twrp>Wipe>Advanced select data and click on change file system. Change it to F2fs. Now restore your backup (Reader the guide all info is there). Profit!
Click to expand...
Click to collapse
Well this again defeats the purpose of my original question, but thanks mate. I would definitely read the guide if decide to switch to f2fs.
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Puddi_Puddin said:
@abhibnl. BTW your encrypted. So the modified TWRP won't work.
How to fix:
Wipe Userdata with Fastboot / fastboot erase UserData
Boot into Twrp modified twrp.
Flash OOS 4.0 flash SuperSU and let it boot
You should be decrypted DO NOT install a boot password since you will be encrypted again.
Click to expand...
Click to collapse
Thanks a lot for informing me mate. I really don't want to decrypt my storage as of now. I guess flashing stock recovery is the only solution now. Will hope someone would pick up the twrp and update it.
anshulajain said:
I haven't rooted my phone again. My only reason to root is to install Adaway to block all ads. With DNS66 and Adguard, I have little incentive to root my stock nougat install.
Edit : I had encryption during 3.2.8 and it carried over to 4.0
Click to expand...
Click to collapse
Seems like stock recovery is the best way as of now. Seems like I'll have to love without root until someone updates twrp to support encrypted storage.
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Zielony360 said:
I haven't updated to Nougat yet, but I looked over Chainfire's SuperSU changelog and its installation script and both of them confirm that from March installing SuperSU prevents forced encryption. Also many guides suggest installing it as way for disabling forced encryption. Of course you have to flash SuperSU just after flashing ROM, before booting the system.
Click to expand...
Click to collapse
That i already knew mate. But i WANT my storage to remain encrypted. And that's the issue with modified TWRP. You can't enter into recovery on that if your storage is encrypted.
kpmohamedhussain said:
Very simple indeed...
1. Switch on wifi
2. Download OTA and click install whem finished
3. Once installation completed, flash twrp .28 and latest su
4. Reboot and ignore any errors, youwill beup and running fine...
Click to expand...
Click to collapse
Again, "You can't enter into recovery on modified TWRP if your storage is encrypted." So i won't be able to enter into twrp in the first place, let alone flash anything.
abhibnl said:
Hello all!
I am currently on OOS 3.2.8, and official TWRP. I have read all the instructions on the forums but all lead to one option, formatting internal memory. So, my question are:
1. Will flashing oos 4.0 work with official TWRP or 8 have to use modified 28 version?
2. How can I flash oos 4 with modified TWRP and not have to wipe internal memory?
I would appreciate all the responses. Thanks
Click to expand...
Click to collapse
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Go to twrp. Press backup. Select only data. Save to PC youre backup for safety..
3.2.8 it's Android 6, 4.0 it's Android 7. Some apps might not work from base to base.
If you want to change to F2FS it will format youre phone, wipe phone full internal memory. If you want to change it back to ext4, same.
Clean flash, full wipe it's always better.
dmoses1969 said:
In the same boat as you. I have OOS 3.2.8 encrypted, rooted and TWRP 3.0.2-1.26. I too would like to update but have way to much stuff on my phone to back it all up and restore it. Hope you or someone come's up with a solution. I will be following your thread.
Thanks.
Click to expand...
Click to collapse
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
anshulajain said:
My suggestion (and my steps are in #1), install stock recovery, install snap VPN, download the update and install (ignore any errors on root). Once done, you will have Nougat with stock recovery, encryption maintained and all app data also intact.
Click to expand...
Click to collapse
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
abhibnl said:
This is the last resort brother. With this method, unfortunately I won't have any root available. The only way now is to wait for updated twrp.
Click to expand...
Click to collapse
I dont know. I found this on Oneplus forum. May be worth trying. Just not 100% sure.....
Thanks! Will try and let you know
abhibnl said:
Thanks! Will try and let you know
Click to expand...
Click to collapse
Well, I tried something, waiting on it to finishing booting and see how it went.
I flashed twrp-3.0.2-1.28-oneplus3p version,
Flashed the OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip inside TWRP,
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip right after flashing OTA zip.
Its rebooting and says Android is upgrading. Fingers crossed.
EDIT: Its booted and I am on Nougat, didnt lose my data and phone is still encrypted!
Edit: Ended up having issues with settings app locking up. So, I went a different route and its all working great now.
Downloaded the stock recovery image and renamed it to recovery.img
Make sure after you rename it its not named recovery.img.img, If you have show file extensions enabled on your pc you should already see the file extension.
Rebooted to bootloader - adb flash recovery recovery.img
Using the volume keys and power button selected - reboot recovery.
Now in stock recovery - flashed OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
After rom is done flashing, went right back into bootloader. Did not let my phone reboot to start the OS.
Renamed twrp-3.0.2-1.28-oneplus3p.img to recovery.img
adb flash recovery recover.img
Powered off phone and Manually boot it into recovery by holding Power + Volume Down button.
Phone booted into TWRP
Flashed SR1-SuperSU-v2.79-SR1-20161221223537.zip
Wiped cache / dalvik
Rebooted system from TWRP and waited. System is really smooth now, no issues yet. Been playing with it for awhile now.
During the booting up process it might take a minute and it will reboot twice. Dont get nervous like I did thinking it was going to start bootlooping. It booted just fine. I read in a nother thread that SuperSU is what causes it to boot twice.
So......Now I have OOS 4.0 Nougat, Rooted, Encrypted and everything seems to be working fine.

Problem in TWRP?

I was on GPe so today i changed CID to SuperCID and my model is 0P6B13000,installed new firmware by given method in convertion post,installed TWRP and had no problem,but during factory reset i get Failed to mount /system (Invalid argument).Btw,after that i was able to boot in LineageOS,but was unable to boot into S-ROM,which i tried before flashing LineageOS.Also,i was unable to flash Stock Backup.Any ideas what's going on?
Fixed it.you can delete this
No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest
ckpv5 said:
No idea if the comversion post is still valid for current firmware as I don't know which one you refered to.
It' a simple process - (after SuperCID done)
1. Install 6.xx firmware
2. Install latest TWRP 3.x
3. Boot to recovery (TWRP) - select wipe, advance, select format data - type yes. Then main menu select reboot - recovery
4. Once in recovery again you can install any ROM that you like.
To revert to Gpe, same process but using Gpe firmware for no. 1 and follow the rest
Click to expand...
Click to collapse
Well i used just the Instructions,not the old firmware.I flashed 6.xx firmware(From your collection) . Did it all but can't install S-ROM(only this one).I guess it's just ROM problem.Don't know.Btw i got stock twrp backup from your collection,but twrp doesnt recognize it(i have it on my ExSDCard,yes).Any ideas about that?
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?
ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
Click to expand...
Click to collapse
http://imgur.com/a/uNK34
I forgot making backup of only boot and then pasting your stock backup.I'll try it now .btw thats my bootloader
ckpv5 said:
Did you do no. 3 ? That's very important.
What color is the bootloader now ? What is written on bootloader OS - xxxxxxx, any double no. ?
To restore a nandroid, you need to extract the zip and place it in right location as explained in its instruction on post #1.
In other thread you mentioned to convert it to tmob us.. why don't just use RUU ?
Click to expand...
Click to collapse
Another error occured during restoration. extractTarFor() process ended with ERROR:255
Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Another thing .. you do not answer my previous question .. did you do no. 3 when doing conversion ?
ckpv5 said:
Which version TWRP that you installed ?
Used to get that error due to wrong version.
You can try 2.8.7.0 but don't accept any root offered by twrp.
Also you can try RUU - http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
RUU will usually fix all errors unless it's hardware problem
Click to expand...
Click to collapse
Version is the newest one(3.1.1.0).I'll give a try with other version.
And about the question,yes i did step 3
I'm downloading RUU now.I guess everything will be OK.
RaZaR1998 said:
To use RUU bootloader needs to be relocked,right?
Click to expand...
Click to collapse
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
Thanks a lot,again
ckpv5 said:
Not needed for S-Off device.
What you need :
Windows with usb 2.0
Latest htc usb drivers installed which you can get by installing latest htc sync manager (then uninstall syc manager but leave the drivers)
A note about S.ROM - it may have alter your system partitiom & firmware because yours is S-Off. Always advisable to reflash firmware before installing other ROM. RUU will fix these.
Click to expand...
Click to collapse
I've just run RUU and ERROR occured around 50%.Now i'm left without everything ... Any way to get at least the stock recovery and stuff so i can get back to bootloader?
What error that you have ?
To get back to bootloader, press & hold both power & vol up buttons. When it turns black, release both buttons & press and hold vol down button only.
Also you can try to run command fastboot reboot-bootloader
Once on bootloader try to flash firmware again. (Your current bootloader has modified dsp which I believe comes from S.ROM)
I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...
When you said this
but during factory reset i get Failed to mount /system (Invalid argument)
Did you do factory reset on bootloader while TWRP was installed instead of stock recovery ? AFAIK you're not supposed to factory reset on bootloader with TWRP installed unless it is stock recovery
---------- Post added at 06:02 PM ---------- Previous post was at 06:00 PM ----------
RaZaR1998 said:
I don't remember what was the number of error,but now i get htc logo with four exclamation marks(one in each corner)... when i fastboot reboot bootloader this screen appears.I ran RUU twice,same happend both times...
Click to expand...
Click to collapse
That's RUU mode .. try the buttons press & hold method to get back to bootloader
I did Factory Reset before flashing TWRP.Now as you told me i flashed firmware again.Now my bootloader seems fine.I still dont get why RUU doesn't work.I'm S-OFF with unlocked Bootloader and as you said,re-locking is not needed.I don't get what's going on here ;d
Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again using twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
How about installing other Sense ROM (other than S.ROM), try that too.
ckpv5 said:
Your first post made me understand that you factory reset after TWRP was installed .. because your problem always related to that.
Maybe try a different RUU, try the Developer Edition RUU.
Before that can you try to restore nandroid backup again usin twrp 2.8.7.0 and see the error 255 still there.
Also you mentioned you can install LineageOS ?
Click to expand...
Click to collapse
Well yes i could install LineageOS and RessurectionRemix (honestly i dont like them).I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?
RaZaR1998 said:
I'll try stock backup with an older TWRP.
Now i got new TWRP but it doesnt show internal storage.is this normal?
Click to expand...
Click to collapse
That's not normal. This is where you need to format data in twrp then reboot to recovery again. You should see internal storage

Rooting 8.0 Guide?

I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
arebelspy said:
I have a USA variant, just got the Oreo / EMUI 8.0 update. Everything is stock.
I got my bootloader unlock code from Honor support (via the Google forms the USA Support tweeted out).
All guides for unlocking the bootloader and rooting are for Nugat (7.0).
I am wondering a few things.
1) Has anyone unlocked/rooted Oreo? What steps did you take? What TWRP version are you using (a link is preferable, if you have one)? Did you use the multi-tool, or directly with adb?
2) What root solution did you use? I prefer SU over magisk (for the ability to use xposed), but I heard SU isn't working, only magisk? What version did you use?
3) What backup system do you use when your phone will wipe everything for unlocking the bootloader? Is the Huawei stock "Backup" app that it comes with any good? Any better ones to use?
Basically there's no walkthrough for rooting with the current setup. It'd be awesome if someone wrote one that was basically:
- Backup using W method (backup app, or alternative).
- Unlock bootloader using X method (adb/multi-tool/whatever).
- Root using Y method (TWRP version, SU or magisk, and version numbers)
- Do Z activity (anything else to flash after? xposed? etc.?)
Any thoughts appreciated.
Click to expand...
Click to collapse
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
mrmazak said:
Already covered in this thread.
https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500
Click to expand...
Click to collapse
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
It also said backup partitions when in twrp image mount, and flash magisk 16 for root.
I'm about to try this same exact thing the twrp Oreo thread is a little confusing.
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. ? Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
arebelspy said:
That didn't even cover a fraction of the questions I posted. It *maybe* gave the relevant TWRP build, though even that is in question, as one of the most recent posts was "I couldn't get any of the TWRP versions listed in this thread to work fully. " and suggesting something else.
I'm curious if anyone has actually rooted stock 8.0 and what process they used.
Click to expand...
Click to collapse
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
allrockedout said:
K easy part done bootloader unlocked
Update: installed twrp. Did a few backups. Flashed magisk. Rooted now restoring apps in titanium backup. Adaway finally and going to clean up system. Safety net passes. Just a little confused on how to restore if I end up in a boot loop. I'm trying to backup still in twrp. But can't backup data and I don't see boot.img to backup. So yeah I'm scared.
Click to expand...
Click to collapse
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
ryang872 said:
I had posted that. Use this TWRP. Flash Magisk 16 through TWRP. Enjoy root.
---------- Post added at 11:45 PM ---------- Previous post was at 11:41 PM ----------
Flashing kernel.img and system.img from the Oreo update.zip should completely fix a bootloop/brick. I had messed around and bootlooped one of mine, and had to extract those .img files to flash them through fastboot to restore my phone. It will erase the system though so a backup of data through Titanium Backup should be safe.
Click to expand...
Click to collapse
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
ryang872 said:
Gonna upload them now. I'll edit this post when they're finished. Did you have root before updating to Oreo?
Click to expand...
Click to collapse
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
allrockedout said:
No I waited for Oreo before I rooted. I just rebooted again and booted back to system fine. I made a bunch of backups in twrp. But there useless if you don't have booted.img system and data.
Click to expand...
Click to collapse
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
mrmazak said:
there is no "boot.img" on oreo.
the traditional boot.img has been split into 2 partitions. kernel.img and ramdisk.img.
Click to expand...
Click to collapse
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Flashing kernel.img through "fastboot flash boot kernel.img" absolutely solved my bootloop/brick problem. I am completely new to Huawei phones so if I'm wrong please don't let me spread misinformation.
---------- Post added at 12:43 AM ---------- Previous post was at 12:41 AM ----------
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
You'd need to flash kernel as boot through fastboot(fastboot flash boot kernel.img). TWRP would be ramdisk (fastboot flash recovery_ramdisk *****.img). System and Data backed up through TWRP can be restored through TWRP. At least those worked for me in restoring a bootloop/brick.
---------- Post added at 01:00 AM ---------- Previous post was at 12:43 AM ----------
allrockedout said:
Where can I get system.img and kernel.img can you share it. I'm barely able to reboot keeps rebooting and booting into safe mode. Takes me like 10 minutes to boot to system. can barely get into twrp
Click to expand...
Click to collapse
system.img kernel.img
EDIT: This is for L34 update.zip. I'm going out on a limb by assuming that all honor 7x/mate se versions are the same minus the modem_***.img files. USE AT YOUR OWN RISK.
allrockedout said:
So we need kernel.img ramdisk.img which is boot. Than we need system and data. How do you flash the kernel and ramdisk when in twrp? I'm guessing ramdisk we select recovery ramdisk...and kernel? I got system and data backed up
Click to expand...
Click to collapse
Each partition is it's own. Kernel is kernel, ramdisk is ramdisk, etc.
Recovery_ramdisk is recovery_ramdisk
I preferred to make each partition backup as images. Using adb shell and DD commands.
I know it is not in this thread. But in the "(nougat) twrp complete" thread.
This is linked in I believe post two. Where it describes making backup useing DD.
But the partitions are different in oroe, so need to use different codes as in that thread.
I just posted almost same thing yesterday with the links.
Use this guide to make back up. But substitute the partition layout from the following link
Oreo layout
I might be putting together a script that does the backup form you . And put it into a zip file that you run as a twrp install.
I like that idea. Now I said it out load, yeah I like it
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
update..
It worked. All 56 partitions backed up. took over an hour. then I realized I had internal storage full of junk. Userdate backup took 23GB.
as long as your data is not so full, should be better time.
maybe someone else can help edit it to be better script.
completed recovery log attached. Truncated to remove screen timeout (sleep and wake messages)
mrmazak said:
I made first draft of my dd back up install.
It makes new directory on external card "twrp_backup" then makes dd copies of all 56 partitions. It takes a while to complete. , but gives you all the partitions, as they are. I added echo lines to the script to give you stautus of the backup, but the output is not shown on trwp install window. And it appears to be doing all the lines of the script at same time, not one at a time. So even if the echo commands printed output , it would be all at once.
well hold off on that statement of "it works" 30 minutes plus and still running.
No errors in current log, Adb shell ls (backup directory) shows all partitions. But mtp only showing 42 out of 56.
It appears to be hanging somewhere.
Will update when I find it.
maybe someone else can help edit it to be better script.
Click to expand...
Click to collapse
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
allrockedout said:
To return to stock recovery and factory reset what do I restore? Do I need to wipe anything?
Click to expand...
Click to collapse
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
mrmazak said:
none of those would be stock recovery. Because in order to have made that backup, you would have been on twrp. So the backup would be also twrp.
need to get the stock oreo recovery from extracting the recovery_ramdisk from update.app. update.app is in the update.zip of your oreo update. The main zip , not the "public" or "hw" one.
once you have the image. select install menu in twrp. change to install image. And install to "recovery ramdisk" also can be done with fastboot.
Click to expand...
Click to collapse
im having trouble extracting update.app i cant open it on my pc.
---------- Post added at 10:24 AM ---------- Previous post was at 10:13 AM ----------
allrockedout said:
K im downloading the update.zip now from firmware finder. I want to do another clean install magisk is force closing now. I'm using the p10 lite twrp.
---------- Post added at 10:13 AM ---------- Previous post was at 09:39 AM ----------
im having trouble extracting update.app i cant open it on my pc.
Click to expand...
Click to collapse
im downloading huawei update extractor
K I'm going to extract this
Here is stock recovery ramdisk for Honor 7x USA Oreo. https://drive.google.com/file/d/1IylCAhGs304boVkSXnSRrQQ1B5ozHwcX/view?usp=drivesdk
I haven't tested it yet. Going to flash in twrp. Hopefully boot back into stock recovery and factory reset.
I also extracted kernel.img.
I successfully flashed kernel and ramdisk recovery. I rebooted back into stock recovery. Going to try factory reset now.
?
Wouldnt boot up.
Flashed kernel.img through twrp didnt work had to flash through adb and it seems to be booting now.
HELL YEAH!! ok booted up to system now.

What is the CORRECT way to gain ROOT in PDP3?

I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
AndroidDevices said:
I have attempted :
-Fastboot boot TWRP.img
-Reboot Recovery
-TWRP Flash Magisk v16.4
-Reboot into System
Am i missing a Kernel? If so, where is the Kernel for PDP3?
Am i missing a Patched_Boot.img? If so, where is the PDP3 Patched_Boot.img?
What is the correction instruction for gaining ROOT on PDP3?
What else may i be missing from the recipe?
I have searched and asked others via PM or in the Thread, and have received half-ass replies.... So would someone please lay it out, if not, i guess i will go back to 8.1.0....where i had ROOT, Recovery, and Viper4Android... Thank God I made a back-up....
Thanks in advance,
T
Click to expand...
Click to collapse
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
EvilDobe said:
I'm generally curious how many times, and in how many threads, you're going to ask this question.
1) Flash DP3. Let the device boot, log in, set it up, etc.. I do NOT enable a pin/pattern yet.
2) Reboot to the bootloader & fastboot TWRP.
3) Flash Magisk 16.4.
4) Boot into the system & have root.
I've done this process damn near 10x going between dp2/8.1/dp3. There is no special trick to it.
Click to expand...
Click to collapse
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Tulsadiver said:
If he wants recovery, he needs to flash twrp-3.2.1-2-taimen.zip before flashing magisk 16.4
Click to expand...
Click to collapse
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
He did mention that he would want to go back because he had root and recovery.....
EvilDobe said:
OP didn't ask for recovery. OP asked how to get root. While you are 100% correct on how to get a static TWRP instance it is not relevant to the OP getting root.
Click to expand...
Click to collapse
I'll take TWRP as well, wasnt sure if there was an unofficial version for P or not...
Tulsadiver said:
He did mention that he would want to go back because he had root and recovery.....
Click to expand...
Click to collapse
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Tulsadiver said:
If he wants recovery, he needs to flash twrp-Pixel2XLinstaller-.zip before flashing magisk 16.4
Click to expand...
Click to collapse
After i flash the TWRP Installer, do i reboot and change slots, or no?
EvilDobe said:
Semantics. OP's post, and general boggle, is that they cannot obtain root on DP3. My response was directly related to the OPs post, and last like 10 comments across this sub. What OP had is presently irrelevant since the current goal is to obtain root. If the OP had an additional question as to how to obtain static TWRP I would have addressed that at a later date/time or your response would have been appropriate. Perhaps I took it for granted that the OP had an understanding on how to get static TWRP but, again, the point of this thread is getting root on DP3 which my response answers & yours does not.
Click to expand...
Click to collapse
I appreciate BOTH of your help, no need to get all technical!
AndroidDevices said:
After i flash the TWRP Installer, do i reboot and change slots, or no?
Click to expand...
Click to collapse
No, flash Magisk unless you want to try a custom kernel. If so, flash it before Magisk, flash Magisk, then reboot.
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Jameswebb97 said:
After flashing magisk, the phone will not reboot, instead keeping me in a bootloop and sending me back into TWRP. Any ideas? Im happy to go back to stock if thatll make my phone work again!
Click to expand...
Click to collapse
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
all43 said:
Hi James what exactly did you flash before magisk and I'm guessing you were flashing from stock and also not p?Also how did you flash?
Click to expand...
Click to collapse
Hey,
I was installing from P (9.0 DP3)
I installed TWRP first by flashing the image and then installing the zip file on to the phone.
Next i installed magisk, the installation all went through absolutely fine.
When i hit reboot, it goes onto the white splash screen, then brings up a small progress bar that goes across. This lasts for a minute or two, then dumps me back into TWRP.
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Tulsadiver said:
A complete wipe when going to P is the best way to ensure there are no problems but what has worked for me is after installing dp3, rebooting to fastboot, booting to TWRP and doing a factory reset in TWRP. You will not lose data but will have to set your phone up as new. Then, boot back to fastboot and following the instructions as stated in the prior posts to gain root and recovery.
Click to expand...
Click to collapse
Thanks, i'll give it a try again with a Factory Reset 1st...
AndroidDevices said:
I attempted all ways listed, and i end up Booting into Stock Recovery with a corrupt message forcing me to Power Off or Factory Reset or i got stuck at the Loading "G". Ended up restoring my June 8.1.0 Back up. Thanks for trying to help... I'll wait till there is more info on the subject...
Click to expand...
Click to collapse
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
EvilDobe said:
Which version of TWRP are you using (twrp-3.2.1-2 is the latest)? Are you seeing errors in the twrp gui while flashing? I'm not sure what you mean by "more info on it" because it's literally just flash the Magisk zip then reboot. The only things I can think of are that you're using an older version of twrp or the magisk zip is corrupt giving you a bad install.
Click to expand...
Click to collapse
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
Don't reboot, TWRP installer installs to both slots.
Flash installer, hit back button, find magisk.zip, flash it.
AndroidDevices said:
Yes, always using the latest TWRP Official Builds. No errors in the script. What i mean by more info, is just that, when someone posts a thread, and i see it is working for users without issue, i will take the plunge if this doesnt work this time. And im using Magisk v16.4beta...
I think i am so use to Fastboot boot TWRP3212.img, then flashing the installer and rebooting to switch slots. I'm sure i am just not following something. Do i need to reboot after flashing Installer and before flashing Magisk, or NO reboot?
Click to expand...
Click to collapse
What happens when you just do this:
Get DP flashed & configured. No passwords/patterns/security features.
fastboot boot TWRP3212.img
Flash your magisk 16.4 file.
Reboot.

Categories

Resources