Database Users

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required

[INFO] How to sideload 5.1.1 (LYZ28E), & maintain no encryption - no wipe required
Simplified procedures with LMY47M / LYZ28E now available as a factory image.
Hopefully this isn't blatantly obvious to everyone, it is a little different than the normal sideload procedure. Thought it might be useful to some who want to load 5.1.1 (and get Wifi calling with T-Mobile!) and not be forced to encrypt.
Requirements:
1. I'm assuming you have adb/fastboot working on your computer / connecting to your device and you understand a little bit about using adb / fastboot with an android phone.
2. Your phone cannot be encrypted, if you're encrypted already - this will not un-encrypt your data - you need to turn off forced encryption and format the "userdata" partition to disable the encryption.
3. You need to have an unlocked bootloader for this to work of course.
How to follow this procedure:
1. If you're on LMY47M (T-Mobile) and unencrypted, you can follow option 2, starting with Step 3 - only a small ~150MB download required.
2. If you're on anything other than LMY47M, you should use option 1 unless you have a desire to flash LMY47M and sideload LYZ28E.
I didn't do much here - except spent a bunch of time writing the procedure.
All Credit for tools / ideas goes to:
- efrant for his explanation of how to get OTA updates to work with TWRP ( http://forum.xda-developers.com/nexus-6/general/nexus-6-ota-help-desk-t2992919/page4 )
- hlxanthus for the NO FORCE ENCRYPT mod ( http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788 )
- Q9Nap and mhous33 for the LMY47M factory image ( http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 )
- bbedward and others for the original disable forced encryption boot.img ( http://forum.xda-developers.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715 )
- TeamWin - the TWRP Developer ( https://twrp.me/ )
——————————————————————————————————
OPTION 1 - Easy Method - Flash the LYZ28E factory image directly:
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Download LYZ28E for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lyz28e-factory-b542b88a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img (OPTIONAL - If you have TWRP or another alternative recovery you can skip this step)
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Restart the Bootloader, and flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the Bootloader again and then go to Recovery (TWRP). Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!
———————————————————————————————————————————————————
OPTION 2 - SIDELOAD Method (Makes sense if you’re already on LMY47M):
1. Download hlxanthus's NO FORCE ENCRYPT mod and put it onto your phone so you can flash it later (in /storage/sdcard0) - https://basketbuild.com/filedl/devs...u/misc/NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
2. Follow the normal procedure, if you're already on LMY47M you can skip to step 3. Download LMY47M for Nexus 6 ( https://dl.google.com/dl/android/aosp/shamu-lmy47m-factory-5228e84a.tgz ) and extract the files, there is a zip file you want to extract that too.
Boot to the bootloader ("adb reboot bootloader") and fastboot flash the boot, cache, recovery, radio and system:
Code:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash radio radio-shamu-<variable>.img
fastboot flash system system.img
3. Now flash TWRP, found here: ( https://twrp.me/devices/motorolanexus6.html )
Code:
fastboot flash recovery twrp-2.8.6.0-shamu.img
4. Restart the bootloader, and enter recovery mode (TWRP). Once in TWRP, go to Advanced -> ADB Sideload. You may need to unplug/plug in the USB cable to your computer again.
Download my version of LYZ28E from here: https://www.androidfilehost.com/?fid=23991606952609905
Note: I modified this version to work with TWRP, it will not work with the stock recovery (because I modified it, the signature on the file is now invalid). The only thing I changed was I edited the updater-script to remove the release keys check which seems to fail on the stock recovery and doesn't work right with TWRP).
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
5. After it finishes, do not reboot yet. Go back and I recommend rebooting to recovery again. Now flash NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip through TWRP, and flash SuperSU if you want root and whatever other zips you want to flash (Xposed, etc)
After flashing the NO FORCE ENCRYPT mod, reboot and you should be running 5.1.1 with all of your data and with your userdata partition intact and unencrypted!

why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.

simms22 said:
why would you think that you have to be encrypted to push anything to recovery??? plus sideload is only one method to do it, the other is adb push. and if you use twrp recovery, you don't need any of those method's, as you can just move files over to twrp via your usb.
Click to expand...
Click to collapse
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.

liqice said:
Sorry if I gave the impression you need to be encrypted to push to recovery, that wasn't my intent. Where did I give that impression? I can try to fix it in my original post. At no point in this procedure will your phone be encrypted - there will be times that the kernel will have the force encryption option turned ON in the fstab but you never will boot the phone when that is the case (like right after LRX22C is loaded, after LYM47M is sideloaded, and after you flash the stock boot.img for LYM47M - but you are not booting in any of these cases - not before you install a no forced encryption kernel)
adb push requires the phone is booted right? I wasn't able to get adb push to work in recovery.
I also didn't know TWRP allowed you to copy data over to your phone via USB, I know CWM recovery can do it - but that was a feature missing from TWRP - maybe they added it, I didn't check. You can do an adb push with TWRP, but what in my procedure would you change to use the adb push method in TWRP versus whatever I put in there? The only thing I can think of is asking you to put the mod file on the phone in the beginning.
Click to expand...
Click to collapse
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.

simms22 said:
"So I just figured out how to sideload LYZ28E on my Nexus 6 without enabling forced encryption. "
actually adb push is very easy.. boot unto recovery, type adb push filename.zip, then it pushes to your phone and is listed in the main storage filesystem. id say its nearly identical to adb sideload.
Click to expand...
Click to collapse
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?

Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.

cam30era said:
Step 3: "Hold down the Power and Volume Up button (may need to do it a few times) to get to the Recovery menu".
Actually, the correct key combination is: Hold power, then (while holding power button) press and release volume up.
Works first time, every time.
Click to expand...
Click to collapse
Thanks, updated the original post.

liqice said:
Sorry maybe that first sentence is poorly worded. What I meant was, I figured out how to get LYZ28E onto my phone and disable the forced encryption on the OS too. The process wasn't as straightforward because the 2nd sideload wouldn't work correctly without booting into the OS first. After that, I couldn't get the LYZ28E image to sideload on stock recovery or TWRP without errors - but I was able to modify the LYZ28E OTA file so it would load with TWRP, and then I was able to load the no encrypt mod and supersu and get the phone working the way I wanted again.
Are you saying it would be easier if I push the zip file to the phone and install using TWRP as a zip file instead of trying to sideload it?
Click to expand...
Click to collapse
easier/harder isnt an option here, since any way takes seconds. im just saying there are several options for this, thats all

liqice said:
Code:
fastboot flash f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
Click to expand...
Click to collapse
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?

So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?

Chahk said:
Shouldn't this step be
Code:
adb sideload f69096766706fab3c721163f02aad9073a989d00.unsigned-shamu-LYZ28E-from-LMY47M-fullradio-fix-superblock-use-TWRP.zip
instead of fastboot flash?
Click to expand...
Click to collapse
Oops, you're right. Thanks!

Gage_Hero said:
So if your starting out with 47E, your rooted and have TWRP ..... would you use adb sideload in TWRP or you issue the command from the PC?
Click to expand...
Click to collapse
This is where I was, LMY47E, rooted, unencrypted and with TWRP. I followed the entire procedure - went back to LRX22C using fastboot, then sideloaded LMY47M (T-Mobile version) - then flashed the no force encrypt boot.img - booted, after it finished booting, rebooted to the bootloader and so on ...
When you go to LRX22C you flash back to the stock recovery. So you need to boot into the stock recovery, pick "apply update from adb" and then run the adb sideload command from the PC.

Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?

With the factory images being posted, I just did the following:
Flashed the factory images
While still in bootloader, flashed TWRP
Rebooted into TWRP
Pushed SuperSU and the No_Force_encrypt to the /sdcard/ partition
Installed via TWRP
Profit.

lamenting said:
Cheers for this.. just what I was looking for. I'm at work so I only scanned this quickly, but any major change in the directions from what you've posted going from an unencrypted LMY47D?
Click to expand...
Click to collapse
For LMY47D you need to get to LMY47M first, so you would follow the entire procedure, downgrade to LRX22C and then sideload LMY47M and so on.

Heavily updated the procedure since LMY47M and LYZ28E factory images are now available directly from Google.
Should be a lot easier and more straight forward now!

I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?

Boot loader and radio only...
So if I understand the instructions correctly, if you are still encrypted but rooted, from any Lollipop installation, fast boot flash the factory images... then flash TWRP ... root and done right? Then I have another question... the kernel I am running EX 1.07 along with Flar's app is running perfect for me.... any dangers in just flashing the boot loader and radio? I would like to wait on the system part until the kernel has been updated.....
Also, if I needed to do a restore, if I only flash the boot loader and radio have I pooched being able to go backwards to a nand backup?

FYI, step 3 in option one should read:
fastboot flash recovery twrp-2.8.6.0-shamu.img
vs
fastboot flash twrp-2.8.6.0-shamu.img

frater said:
I just recently have this Nexus 6 and came from an LG G2. I went through the process of unlocking the phone and installing rooted LMY47D which meant 2 factory resets in a short period.
I'm now on 5.1 and would like to get rid of the memory leak which this build apparently has.
The title mentions "maintain no encryption".
I never found the time to find out about Lollipop. The title implies that encryption is mandatory on 5.1.1
Is this so?
I merely want the latest upgrade to 5.1.1 and don't want to enforce encryption on my data (Google already knows everything about me) is this the way to achieve this?
I am correct in thinking that I will not get an OTA offered anymore?
Click to expand...
Click to collapse
Starting with Android Lollipop (5.0) and newer - at least on the Nexus 6 - encryption is turned on by default for the userdata partition.
You would - if you wanted to - backup all of the data on your userdata partition (e.g. Any pictures you've taken with the phone, etc - all of the data basically that shows up when you plug your phone into your computer).
Then you need to be running an OS that doesn't force encryption (for example if you follow my instructions) - this would also get you running 5.1.1.
After that you need to format your userdata - it wouldn't be encrypted at that point, and then copy your data back if you want to.
If you don't care about encryption, you can simply flash the factory 5.1.1 image following my instructions and skip the TWRP parts.

Can't Update To 6.0.1...(Need Help)

I tried to update my phone to the latest version. I hit install from the notification, my phone reboots goes into TWRP recovery.... does nothing, then I have to "reboot into system" and then the phone boots up like normal.
Without updating to 6.0.1. Does anyone know why this is happening, or how to fix it?

I think you can't update the phone with official update method (Settings/About/System Updates) when you have unlocked bootloader and root.

READ.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

xT29c said:
I tried to update my phone to the latest version. I hit install from the notification, my phone reboots goes into TWRP recovery.... does nothing, then I have to "reboot into system" and then the phone boots up like normal.
Without updating to 6.0.1. Does anyone know why this is happening, or how to fix it?
Click to expand...
Click to collapse
You must return to complete stock, including recovery, before attempting an OTA update
Sent from my Nexus 6P using Tapatalk

As mentioned above, you can't use the traditional method of updating if you are are rooted and have TWRP installed. You will need to flash the images manually with your PC in order to update. There are multiple ways of doing this, but the easiest way I've found takes about 5 or 10 minutes and is documented elsewhere on this site, but long story short:
-install and confirm that ADB/Fastboot works on your PC and can see your phone
-download the latest image directly from google
-unzip the downloaded file on your PC and then unzip the file that was just extracted into your ADB folder
-edit the "flash-all.bat" batch file to remove the "-w" toward the end (to prevent wiping your data)
-put all extracted files into your ADB / Fastboot directory.
-connect your phone to your PC, power it on or reboot it into bootloader mode, and run the batch file that you edited (this will put you back to stock / unrooted)
-re-flash the twrp recovery image using fastboot
-re-root (install SU.zip using twrp).
That's my preferred method, and once you have everything setup (ADB / Fastboot working & factory image downloaded) is should only take a couple of minutes to perform.
As mentioned before, this is well documented elsewhere on this site. I may have missed steps or left out information as I am writing fast because I am currently at work.
Good Luck!

Please help me restore back my original LGUP dump! (H910)

I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!

zhangla said:
I tried to use the dirtysanta method to root my H910. Here is what I did:
1. Because I have the April 2017 security patch, I used LGUP to load up an kdz that is on Dec 2016.
This step was successful. Everything worked as expected.
2. Then I followed the dirtysanta approach, and everything worked great. I got into TWRP and wiped stuff as instructed.
3. However, at the last step, when the instruction says to adb fastboot into recovery, instead of booting back into TWRP, the phone boot into strange screen with stripes, and after a while it will show me a "kernel crash!" screen with a lot of text.
Question - is there any way to get my phone back? I cannot get into TWRP, and there is no more ADB. I also tried LGUP but it lists my phone under "unknown" model and I cannot select it.
Please anyone help me. Thanks!
Click to expand...
Click to collapse
Obviously you did not do enough reading on the ds root process because then you'd know static on boot is normal and you would have read about the button combo to get into twrp. I suggest you do some more reading
Sent from my LG-H910 using XDA Labs

I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?

zhangla said:
I admit I did not read the thread fully, because it has about 2000+ posts on several hundreds of pages...
I did read the OP's instructions very carefully, and followed it word by word.
Right now, I could get into fastboot and flash TWRP again. That can get me into TWRP but any ROM I flash (either stock based, or custom ROMs), the phone will simply just get back into the static stripes and eventually crash on kernel or modem.
Is this because I should not use H910 ROMs anymore, because the DS uses other models kernels? 996?
Click to expand...
Click to collapse
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.

Mysticblaze347 said:
Flash whatever rom you want/can and then after flash preferably the mk2000 kernel (your varient) right after initial flash of rom-then reboot. Static will vanish like tacos on fat Tuesday. You can then do whatever.
Click to expand...
Click to collapse
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?

zhangla said:
My problem now is that I can no longer boot into TWRP anymore.... I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom, vol- and power then power, yes and yes to factory reset, the phone just boots into statics then LG then statics then the initial setup wizard. No more TWRP.
Trying to use fastboot to flash TWRP again, but now my phone can only be seen by adb under MTP mode, not when it's in fastboot mode.
Any way to flash TWRP when I am in regular MTP mode (e.g. regular adb)?
Click to expand...
Click to collapse
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.

Mysticblaze347 said:
I believe that via adb you can type "push" then type your directed file area of located file (twrp). Double check with google search on how push files via adb
Yeah for some odd reason adb reads via mtp (or photo transfer) only for some reason.
Click to expand...
Click to collapse
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...

zhangla said:
The push command is to send files to external SD card while in recovery mode. I did that once. I don't think it actually flashes anything...
Click to expand...
Click to collapse
Might just have to redo Dirty Santa again...I really dont know what else other than researching ADB commands.
Im assuming that you already tried manual boot in twrp as Cnjax stated. Look into those as well. Different models sometimes have different button combos.

@zhangla
You best slow down and do more reading
You made another mistake
I had recovery-twrp-h910-2018-10-18.img flashed and worked fine, but after I flashed the H910 Oreo stock rom
Click to expand...
Click to collapse
The Oreo stock rom is Stock and flashes Stock recovery and removed TWRP.
Their are two v20 rooted Oreo h910 roms
you needed to use those.
You now need to start over by flashing the h915 nougat kdz and following the root guide
https://r.tapatalk.com/shareLink?ur...share_tid=3664500&share_fid=3793&share_type=t
[ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED)
Sent from my PH-1 using Tapatalk

One Plus 8 Pro features (Wifi / Camera) stopped working after root

I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.

Try latest stable magisk instead of canary. Mine works perfectly with regular magisk

I used the all in one tool by mauronafrio here. Worked flawlessly.
shagexpert said:
I rooted my OP8-Pro. I followed the instructions in this video:
https://www.youtube.com/watch?v=UVABAEGRgew.
To summarize, his steps were as follows:
1. Unlock the bootloader
2. Extract boot.img file from payload bin file (on Windows)
3. Install Magisk Canary 2020 app on the phone
4. Install the boot.img file through Magisk
5. Download Fastboot.zip in Windows and extract files
6. Download and place magisk.patched file in Fastboot folder
7. Connect the phone to Windows, use cmd to boot into bootloader
8. Flash the magisk.patched file on the device and reboot
This is a new method to me. In the past rooting always involved TWRP. Root checker shows that the phone is rooted but other features have stopped working.
WiFi no longer works. Even if I turn it on, it turns itself off. Camera keeps crashing and I can't even change the camera mode once I launch the app. My phone also rebooted itself a couple of times while I was testing it after root.
I also rooted my One Plus 6 in 2019 but had to use a custom TWRP (Bluspark) for it to be stable.
I rather start over with a factory reset than try to repair the device in it's current state (but will try to repair it if it's easier). I prefer to stick with the factory ROM and only need root for one app.
Click to expand...
Click to collapse

I used the all in one tool by mauronafrio here. Worked flawlessly.
Click to expand...
Click to collapse
So I tried that tool. I tried to flash factory image downloaded directly from One Plus website and kept getting the following error message:
"Error: flash-all.exe or flash-all.bat or flash_all.bat or flashall.bat not found!!!"
I think this has to do with the fact that I am using a secondary hard drive on my computer to store all the downloaded files and the bat file is supposed to be in the same folder as the zip file.
I also reset it to factory settings from the recovery mode but that didn't fix the WiFi issue.
Then I ran TWRP from the All in one Tool and installed the factory firmware from phone's internal memory. This soft bricked my phone.
After getting soft-bricked I installed Magisk through the tool but that didn't fix the issue.
Now it is stuck in a boot loop and keeps going into recovery mode. I can also boot into Fastboot mode and install zips through there but I would like to unbrick it first. Is there an alternative ROM that can unbrick it?

I think I am going to try and use the unbrick tool first and if that doesn't work I will try the Fastboot ROM, that already comes with the bat file.
I am a little confused as to which version goes on my phone though. They have Indian, Global and European versions but I live in the U.S. Global seems to be the most appropriate for my phone but I don't want to install the wrong ROM on it.

I remember reading that you can run into WiFi issues if you flashed the wrong version (from a different region) for your phone
I've rooted for many years and this is the first time I didn't go through TWRP as well.

If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.

If you use the unbrick tool you'll probably get issues with the fingerprint reader. But that's fixable, after you've rooted.
The easiest way to get root is to just unlock the bootloader, fastboot boot twrp (not flash), and then flash magisk 20.4 stable.
Before TWRP you had to patch the boot.img and fastboot flash it, but with twrp there is no need for it.]
Click to expand...
Click to collapse
Thanks for letting me know. I attempted to use the unbrick tool but it had problems connecting to the phone. And I also didn't want to run into finger print issues.
I downloaded the patched Rom (with flash-all.bat file included) and installed it via All in one tool. That unbricked the phone and I reset the system to start from scratch. I used the global / international version for my North American phone.
After setting up the phone, I rebooted into Fastboot and loaded TWRP via All in one tool and installed Magisk 20.4 and got the phone rooted.
Root checker shows the phone is now rooted. WiFi and camera also work. I am ready to transfer data from the old phone.
This would have gone smoother if I had just used the correct version of Magisk from the start.

TicWatch Pro 2020 Boot Load Loop Issue

Recently, I purchased a TicWatch Pro 2020 (saw that Kali Nethunter now seems to work on it and I thought it could be a cool device to add).
I have installed nethunter onto several other devices already (Nexus, OnePlus, etc.) and of course ran into issues. Usually I spend a long time on them and it is fun to do it. But I seem to have run into a wall recently with the watch.
When I was first trying to set up the watch, I could send commands with adb to get it into the bootloader menu but then it would not recognize it. I did eventually get the right drivers installed and had my VM recognize the watch with the ADB drivers.
I did manage to complete Step 1 of the tutorial https://www.kali.org/docs/nethunter...-on-the-ticwatch-pro/#1-unlock-the-bootloader
(unlocking it).
I went through to step 2, put it into bootloader again and flashed the vendor and twrp .img files. Once I did this, I tried to switch the device into recovery mode (after it went back to the bootloader menu on its own) as per instructions. But the weird thing is when I initialized recovery mode, it just sent me back to the bootloader menu, all while also not recognizing it on my VM/PC at all. When I tried to start the watch, it just sent the device into a permanent loading loop (after showing the logo and cycling the 4 different colored Google dots around the watch). I can get it back into the bootloader menu by holding both buttons down but I can't get my device to be recognized with a data connection (so it seems effectively bricked).
Normally I look this up myself but since there is not much information regarding this device and this specific rom out there just quite yet, I can't locate anything (compared to troubleshooting the OnePlus 7 Pro). Any ideas or input is appreciated!
Edit: will just let it run over night (drain battery to see if it may or may not help).

Thought I would leave a quick update in case you may be running into this issue yourself.
I let it run over night and run out of power to see if it would do anything. It now seems to be recognized by my pc, but it would not connect. I am installing everything through a VM but it appears that the PC could not recognize the device (I only had drivers installed on my VM, not my main device). When I installed the drivers on my main desktop it began to recognize it again on my VM. Not sure why this was an issue or how it became one or if it was a combination between everything but now at least I can send adb and fastboot commands to my watch again. Will try to flash a stock rom for it and try again to get out of the boot process (still confused as to why it will not go into recovery mode but it instead goes back into boot loader mode when I select it)...

Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?

i got nethunter and twrp working on the ticwatch 2020, it was a pain finding the right files to use and i soft bricked my watch many times in the process.
https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/ this post has the right vendor.img and twrp recovery image, in particular this mega folder https://mega.nz/folder/cVVBRaxL
1-Vendor-Images-22-Jun-2020.zip unzip this file it is located in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/ROM/22-Jun-2020 it contains the vendor.img you'll need
tic-watch-pro-2020-twrp.img in TicWatch-Pro-2020(Catfish-ext)/Custom-ROM/TWRP this is the TWRP Recovery.img you'll need
Magisk-v21.0.zip and nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip are both needed from the TicWatch_Pro_NetHunter_files.zip at https://build.nethunter.com/contributors/re4son/catfish/
1) Enable ADB and unlock bootloader then enter these fastboot commands on pc
fastboot flash vendor.img
fastboot format userdata
fastboot format cache
fastboot flash recovery tic-watch-pro-2020-twrp.img
2) Reboot into WearOS and Setup Watch
3) Enable ADB again and reboot into recovery
adb reboot recovery
4) move Magisk-v21.0.zip into the TWRP folder on the watch
install Magisk-v21.0.zip from TWRP recovery (it'll patch the boot.img itself)
5) Enable ADB Sideload from the Install menu in TWRP
adb sideload nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip
6) Reboot into wearOS with kali splash screen, you will have to open the magisk app after you open the nethunter app to give it root as there isn't a proper pop-up screen to give root access
**circle screen does semi cut off a few buttons in the nethunter and magisk apps, touch your watchface close to the "corner" where it is to select it
I hope this all helps! Cheers mate

unidentifieduser said:
Another update: I managed to find a stock image and some simple instructions. Credit to @sonnettie as it looks like it is working atm (going through setup).
Link: https://forum.xda-developers.com/t/ticwatch-pro-2020-stock-image.4107539/
Going through to try installing nethunter again if it appears to be fully functioning.
Edit: Using the stock image seems to let me now use my watch again. But whenever I try to install Nethunter, I install the vendor and recovery image. Once I do this and try to go into recovery mode, it just seems to bring me back to the boot loader menu. Anyone have solutions or know what is wrong?
Click to expand...
Click to collapse
i just realized i typed all the above and didn't reply to your message, it was a mixture of two install methods with leaving out the flashing of the rom file itself