Develop Bugs

(OTA) T-Mobile Lollipop 4.20.531.4 Sense 6.0 Zip

This is the official 5.0.1 Lollipop (4.20.531.4) Sense 6.0 OTA for T-Mobile HTC One M8. (4.20.531.4)
Nothing modified. Just a straight copy. Enjoy!
If you just need the firmware or rom you can download the zip and extract what you need from it. It's pretty simple.
I'll try to get around to extracting everything and posting links for the individual firmware as well. Don't get mad if I don't get around to it though.
Don't do anything with this unless you know what you're doing.
Download Link: https://docs.google.com/uc?export=download&confirm=mOs6&id=0B83tee7zNQDVTTRsTjJ1dzhHeUU

Would it be possible to upgrade to this without having to flash back to stock first?

How to go back to stock and apply OTA.
douglasf01 said:
Would it be possible to upgrade to this without having to flash back to stock first?
Click to expand...
Click to collapse
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad

bradley_e_smith said:
Going back to stock and flashing this is not that hard. The main thing is to have a stock ROM that is not rooted and the correct stock recovery.
So here are the steps I used via TWRP custom recovery. Note I was coming from 4.4.4 kit kat
- first you need to be on a stock t-mobile rom. I used my original backup.
- then I used TWRP to backup - note I made sure that compressed was not checked
- then unziped TMOUS-M8-3.32.531.2-Stock-TWRP.zip (which is located in this group just a different thread) and copied the files from this backup onto my backup replacing the files
- then I booted into recovery and restored this backup and at the end when it says that the backup is not rooted do you want to root? Make sure you click 'No' and reboot
- At this point I made sure that I removed any programs that relied on root xposted, greenify, reboot programs, etc. I also made sure that I had no root. I used adb shell then typed 'su'.
- At this point I then rebooted into recovery and made another backup (just in case) and then I went into the boot-loader.
- I flashed the 3.32.531.2 recovery (https://www.androidfilehost.com/?fid=95897840722642978) via the 'fastboot flash recovery recoveryfile.img' command and rebooted.
- next up I downloaded the OTA via the about phone and installed and bingo you are updated.
hope this helps.
-brad
Click to expand...
Click to collapse
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks

douglasf01 said:
I dont have an original backup of my device, which is a rookie mistake I know. I just never intended to go back to stock.
Since my phone is going to be a work/personal phone I cant have it rooted or flashed with a 3rd party rom. Would this TMOUS-M8-3.32.531.2-Stock-TWRP.zip be ideal to use to flash back to stock on? This will also reset my recovery back to stock also?
Thanks
Click to expand...
Click to collapse
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad

bradley_e_smith said:
Not being an expert and all, flashing the stock rom will not set the recovery back. Basically you need to restore the ROM and then the recovery. I would like to add that the above worked for me, but I am researching a wifi issue I am having so take what I did with a grain of salt.
**update**: I ended up doing a factory wipe and now the wifi works.... oh well.
-brad
Click to expand...
Click to collapse
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?

douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).

bradley_e_smith said:
No, I just downloaded the recovery file, did 'adb reboot-bootloader', then did the 'fastboot flash recovery recoveryfile.img' (where recoveryfile.img is the actual filename).
Click to expand...
Click to collapse
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?

This is the issue I am presented with trying the CMD with fastboot

douglasf01 said:
I see, that is not the case for me. If anything I have the utility that can do all this, but that wasnt working for me either.
I guess I am just lost on this I suppose, especially since I didnt do anything but apply TWRP and root the phone, but kept the phone with the stock rom and not a 3rd party rom. I would figure killing the root and applying a stock recovery would be all I would need to do in order to OTA and be updated.
I have noticed each time I have flashed the recovery through the utility, I try to get in to the stock recovery and the phone acts as if it is not there and displays a red triangle with an exclamation point in it. I imagine this is an indicator letting me that a recovery is not present.
Any thoughts ?
Click to expand...
Click to collapse
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.

bradley_e_smith said:
That is what you would see if you go into recovery. To see more all you do is press both volume keys (up and down) at the same time and press the power button. Then you should see a menu. The stock recovery is not as nice as TWRP.
If you remove root that still may not work (and if someone else knows more please chime in) b/c when you root, it changes the filesystem. I am unsure what the OTA checks on so I would try your 'unroot' method, but if that doesn't work you may need to install a stock un-rooted ROM.
---------- Post added at 11:32 AM ---------- Previous post was at 11:31 AM ----------
it looks correct, are you sure you have the file exactly typed out and also make sure you are the boot-loader screen.
Click to expand...
Click to collapse
I went into the supersu application and there was an unroot option that clears the cache, system, and modifies something. I also flashed the stock recovery back after your last comment, I have never owned an HTC Android device and wasnt aware that was a default. I am going to try the OTA and see if this works out. I will let you know.

I have always just reflashed stock recovery.... Made sure I enabled all of the apps I disabled (like bloatware or whatnot), and then was always able to update. I actually can't recall if unrooting was required.
But I do know that locking the boatloader is not necessary.
---------- Post added at 03:15 PM ---------- Previous post was at 03:14 PM ----------
I am just sad to say goodbye to Xposed....

T-Mobile US 4.20.531.4 firmware
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip

douglasf01 said:
This command fastboot flash recovery recoveryfile.img, did you have to select any options or switches for it to work correctly? The reason I ask is that when I opened up a CMD and CD to the adp/fastboot folder I ran the command line and was given a list of switches/options to run it with.
Any suggestions here?
Click to expand...
Click to collapse
When you get the red triangle, hold volume down for a few seconds...you should get a log screen (although it may be volume up, I can't remember, try both)...it will tell you what is wrong.
Also, from my past experiences, if I didn't flash a new stock Rom (but just tried to "clean up" my existing stock Rom), I would run into problems because I had some app on the phone that even if I had deleted it, had originally modified build.prop... And that is one key thing the update checks before proceeding with install. So you have to make sure you have a stock build.prop file.

Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.

douglasf01 said:
This is the issue I am presented with trying the CMD with fastboot
Click to expand...
Click to collapse
You need to rename the recovery file.
Avoid using '+' in files names.
If you have spaces in a file name, ALWAYS put a "quotation mark" around the file name.

DROITURK182 said:
Here is the new T-Mobile US firmware from today with the recovery and boot.img removed, just need someone to do their magic and remove red text.
https://dl.dropboxusercontent.com/u/...4/firmware.zip
Click to expand...
Click to collapse
The link doesn't seem to work.

epsix said:
Anyone notice when WiFi is on 4glte icon is also on at the same time too just like kk4.4.4? It supposed to be when WiFi is on and 4glte icon should be off.
Click to expand...
Click to collapse
This is something that always happens with HTC devices. I don't know why.

OfficialLocdoGg said:
This is something that always happens with HTC devices. I don't know why.
Click to expand...
Click to collapse
Yeah, I try changing the sku id in ACC/default.xml to metro pcs, and other carriers it works but not good signal.

Okay, I have got APNs unlocked, root, restriction-free tethering working over IPv6, busybox installed, and a kernel with modified initramfs. Anyone interested in a nice simple debloated stock ROM?

NEED HELP

I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!

bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242

1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.

SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong​ SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.

bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.

Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?

bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1

All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!

You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.

TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!

bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?

have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.

bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.

noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!

SuperSU won't install through TWRP

Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!

wireaudio said:
Hello everyone,
I'm facing a very odd issue. I recently installed 7.1.2 from factory image and decided to also install TWRP in order to install a few modifications.
I was able to install the new kernel that allows Android pay to work with unlocked bootloader just fine.
However, I can't install SuperSU for some reason. I'm installing the zip file from TWRP just fine, however when I go searching for the app it's not there, and even if I install it from Google play it's telling me the system is not rooted.
I tried even downgrading a version of TWRP and SuperSU and still no go.
Anyone have any idea what is going on?
Thanks!
Click to expand...
Click to collapse
Are you flashing su2.79sr3 ?
Make sure your using this one. Is the newest

Correct, I am flashing the newest and also tried previous version well, still no go!

wireaudio said:
Correct, I am flashing the newest and also tried previous version well, still no go!
Click to expand...
Click to collapse
Hello,
I'd try reflashing stock boot.img from your 7.1.2 factory image.
The fastboot boot TWRP.img and install TWRP zip.
Install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Reboot to system. From here you should have superSU​ installed.
Reboot to TWRP and install custom kernel zip.
Hopefully it will work...
Good luck...

I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.

wireaudio said:
I will try that, in that order, but before i do, can someone give me a brief explanation on what slot A and slot B are and what they do? I have a feeling it may have something to do with this. I looked for answers on the forums and I wasn't able to find a clear answer.
Click to expand...
Click to collapse
Hello, it's right here: https://www.xda-developers.com/exclusive-dual-boot-may-be-possible-on-pixel-phones/
I also see you posting in another thread. I'm going to answer your question here, so all Infos remain in the same place...
wireaudio said:
I basically installed the factory image without the -w flag, turn booted in TWRP (without flashing TWRP) and installed kernel, then flashed super SU then rebooted. Didn't work so I rebooted in TWRP and flashed TWRP and then flashed SuperSU. Note that I had SuperSU installed in 7.1.1 so I assumed it would overwrite. It didn't work so I uninstalled old SuperSU and re-flashed SuperSU 2.79. it still didn't work so I downgraded SuperSU and TWRP one release and reinstalled. Still no go. And that's where I'm at.
---------- Post added at 09:18 AM ---------- Previous post was at 08:47 AM ----------
Better question is, how do we select what slot stuff gets installed in? It doesn't seem to be clear, more like a game of chance!
Click to expand...
Click to collapse
Your explanation in the other post and this one are different. Just try in the order from my previous post...
For your information, you can choose the active slot. It's not "like a game of chance". Just use the proper command:
fastboot --set-active=a
Or
fastboot --set-active=b
Good luck...

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.

Bootloop after flashing magisk_patched.img

I get into a bootloop after flashing magisk.
The only way out of the bootloop is to flash the original unpatched boot.img (after which everything works perfectly).
I am on 10.0.8. Anybody else have any idea how to troubleshoot this?

I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.

hectorviov said:
I don't think you have to flash Magisk patched boot image, you just have to boot from it. Don't know if its the same thing.
What I do is "fastboot boot magisk_patched.img", then when it boots on the Magisk Manager app, select install -> direct install. After installation is done reboot like normal and Magisk should be installed normally by then.
Click to expand...
Click to collapse
Hmm, I try your method and I think it's roughly the same.
When I do fastboot boot magisk_patched.img, my device goes into a bootloop. I waited 8 minutes (exactly) and figured it was never gonna boot, and so I killed it. When it booted again, it booted fine with no problems (except not rooted, obviously).

Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?

hectorviov said:
Then maybe you're using a wrong boot image, what's the Build number on Settings -> About phone? (It should be something like "Oxygen OS 10.0.8.HD65AA", that's what I'm currently on). Also, is your bootloader unlocked?
Click to expand...
Click to collapse
It's "Oxygen OS 10.0.8.HD65AA" under about phone. I'm also sure my phone is already unlocked because under developer options it says "bootloader is already unlocked" (and fastboot oem unlock gives me an error saying "device already unlocked")
I'm pretty sure it's the right boot image, since I used payload dumper and made the magisk image myself from the dumped boot.img. (both preserve force encryption and perserve AVB are checked)

I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.

hectorviov said:
I have the same, maybe the payload dumper did something wrong with the boot image, or magisk patcher. Try and use this one. Is the one I created and it worked perfectly.
Click to expand...
Click to collapse
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...

ixrs said:
I tried your file and it still gave me a bootloop =/
that said your fastboot boot boot.img trick is really handy since now I don't have to flash my old boot.img to fix the bootloop, haha
Edit: I solved it, all I needed to do was to do a system wipe (ugh) and everything worked...
Click to expand...
Click to collapse
I'm having a similar issue, but when I flash the patched boot image I created, I'm only able to reboot into bootloader and it won't boot back into Oxygen OS for me to do the next steps with the Magisk Manager.
When did you do the system wipe, before you rebooted into Android, and did you do the system wipe using TWRP or stock recovery?

I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.

ixrs said:
I flashed the original boot.img then booted up normally. I then wiped everything. Then I set up my phone again (ugh) and flashed the patched image and it worked.
Click to expand...
Click to collapse
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)

I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?

ixrs said:
I actually did it from within the phone (settings, system, reset, erase all data). I believe it would be equivalent to reset system setting?
Click to expand...
Click to collapse
Thanks, was going crazy. Tried so many times, will post this to the main root guide on xda in case it helps someone else. Yay. Vanced Youtube here I come

lockekey said:
Thanks, just to be clear (I've done this 30 times with no success, and I'm not new to xda or rom/kernel/gapps installation, so this has me scratching my head).
When you say wiped everything, was it:
1) With TWRP from this thread (https://forum.xda-developers.com/oneplus-7t/development/recovery-unofficial-twrp-recovery-t3976961)?
1.1) If with this TWRP, was it a factory reset, dalivik/cache wipe or another wipe OR
2) With original recovery
2.1) If with original recovery, was it Reset system setting, Wipe cache or Erase everything (Music, pics, etc)
You are the only one I've seen with similar issues (you were in bootloop, I'm always rebooting into bootloader) with something I haven't tried yet, so this might get me over the hump (fingers crossed)
Click to expand...
Click to collapse
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.

PriPhaze said:
First the OP was in a bootloop cuz he flashed but not booted the magisk_pated.img so when he tried to boot from magisk_patched it didn't work.
So you can either simply go and download the OnePlus last 1.0.8.0 fastboot ROM and extract the boot.img then flash that using the command and so you will be out of the bootloop.
Don't use the twrp!... it's been stated plenty of times that there's no working android 10 twrp for our device yet.
*start from here...*
Instead all you need to do is to download magisk 20.3
-Extract last APK from the zip
-Install apk (magisk manager)
-Inside magisk manager choose install and then choose patch IMG
-Choose the image that you got from the fastboot official rom.
-You will get the magisk_patched.img in your downloads folder
-Take that file to the pc
-Put your phone In fastboot mode
-Then cmand fastboot boot magisk_patched.img
-Phone will boot
-Open magisk manager again.
-Choose install again and you will have a new option called direct install.
-Choose that and just reboot once and done...
Now you are rooted.
It's simple.
Click to expand...
Click to collapse
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Sent from my HD1905 using Tapatalk

lockekey said:
Never used TWRP. Knew it wasn't working.
Tried all three methods from the main Root thread on xda and none worked (including payload dumper to extract my boot image,etc etc).
Please see my reply above yours. I've added those details to the main Root thread in case it helps someone else.
No idea why I could only reboot into bootloader as I only updated to 10.0.8 using oxygen updater and could never Root with all the methods I found on xda.
Erasing all data fixed my issue and I am Groot.
Click to expand...
Click to collapse
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.

PriPhaze said:
There's no need for payload dumper..
Also you must been using a wrong version of magisk cuz there's no way to fail if you do follow the steps correctly .
All you had to do it was too restore boot.img from fastboot ROM in case you made the mistake to flash the magisk_patched.img instead of booting on it.
And that's it then you just follow the steps.
Yea obviously doing factory reset helped because it restored the boot.img but is like you decided to take the long way instead of the quick and easy way.
Click to expand...
Click to collapse
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.

lockekey said:
I had no trouble flashing the boot.img without issue to restore my access to OOS. That wasn't the issue. I used the right magisk_patched boot. That wasn't the issue (confirmed this evening when I used the same image to root successfully after I erased my data). The payload dumper method was from this guide (https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307) and if the easier 1st 2 methods worked, I wouldn't have tried the 3rd payload dumper method (which got me another version of the same original boot image that I couldn't patch and get to work).
I could never reboot to OOS to install magisk manager and complete a direct install (either after a boot or flashing of the patched image), until I erased data.
Flashing the patched image works as well, it's just another method. I highly recommend reading the above thread.
A tip, you kind of need to know what a person has tried before making suggestions, let alone telling people what they must have done wrong or that they wasted time by using the wrong method.
I highly recommend reading the above thread to learn how to respond to people without coming off as condescending and overbearing. I lot of people tried to help me there and I was very appreciative of how they tried to assist.
Click to expand...
Click to collapse
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your problem although the solution was a bit weird.
Seeya

PriPhaze said:
No one is trying to be condescending... just pointing out facts ..
Thanks for the advice I guess?
But it doesn't really matter; these days people get offended so easily that I'm starting to consider to don't post anymore..
I mean obviously as you can see I have been here for long and lately things have changed that I can't even say anything without being called rude.
And we'll I'm glad you managed to fix your orientation although the solution was a bit weird.
Seeya
Click to expand...
Click to collapse
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.

lockekey said:
You may not be trying to be condescending but you are. And you continue by calling what you say facts and ignoring anything I say.
I've been on xda a long time (since nexus 4, 2012), installing kernels, Roms, etc. I'm not a noob and try and help when I can. I've never been called rude and noone ever seemed offended by any of my posts.
I don't think I have run into anyone as rude and condescending as you on xda.
But it's not you, it's everyone else.
I didn't need your help. It was clear I had the info I was looking for and a potential solution to my issue, if you bothered reading. Not sure what point you were trying to make.
Seeya.
Click to expand...
Click to collapse
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.

PriPhaze said:
And there we go.. you got triggered.
Sorry but this is a forum and well is open so everyone can come and comment.
Even if you dont need anyone's help anyone can come and quote you if they want.
Click to expand...
Click to collapse
I thought you were considering not posting anymore because everyone is so triggered.
It was never a free speech issue. It was always you being a condescending know it all issue.
Just don't cry about people being triggered when people call you what you are.
You're amazing and you know it. Don't change a thing.