Database Develop

Install TWRP on locked bootloader with Android 5.1

Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?

Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
---------- Post added at 06:40 AM ---------- Previous post was at 06:27 AM ----------
Also, please list any steps you took, prior to the phone being in this present condition.

Evolution_Freak said:
Please provide some more information.
Can you boot into Android at all? (Does the phone work)
Can you get to the developer options menu?
Click to expand...
Click to collapse
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.

Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
The bootloader can be re-locked but there's a process that must be followed. Click the top link in my signature for more information.
So, you flashed a factory image and then locked the bootloader before booting into Android and ticking the button in developer options to allow OEM unlock, correct?
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.

Evolution_Freak said:
If this is the case, you are bricked. There is no fix for this. You can RMA or return it to where you purchased it from. Sorry.
Click to expand...
Click to collapse
Thank you but what do you mean by RMA?

Pr0fess0rX said:
Thank you but what do you mean by RMA?
Click to expand...
Click to collapse
RMA = Return Material Authorization. i.e. warranty return from your retailer.

Pr0fess0rX said:
Hello,
Kindly how can I install TWRP recovery on my Nexus 6 with Android 5.1 and locked bootloader and I don't have a working android (shows android figure and it maybe bricked)?
Is it possible to install a recovery to install any other custom ROM so I can make the device working?
Click to expand...
Click to collapse
Pr0fess0rX said:
I can't boot into phone and after I relocked the bootloader after the factory image installed (as I do usually since years to receive the OTAs for Nexus devices).
Unfortunaily Google changed the game here without notifying US about this big move and it should mention to not relock the bootloader after installing 5.1!
I know I can unlock the bootloader from the developers tools but I can't open (boot into) android.
Click to expand...
Click to collapse
cam30era said:
RMA = Return Material Authorization. i.e. warranty return from your retailer.
Click to expand...
Click to collapse
Sadly if u would have done a simple search you would have known this is something that has been talked about for a few months now. RMA is the only option.

While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums

jj14 said:
While folks who visit these forums regularly may have know about this, Google really should update the factory images site for those who are not regular to these forums
Click to expand...
Click to collapse
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.

I do agree that the factory images page should have some mention of the new procedure needed for locking. While it doesn't apply to all devices, it obviously applies here. Too many devices have been lost because of this.

kpierce2014 said:
Even if ur not a regular number one rule here is use the search, and u will find it. Simple search as issues with nexus 6 updating or updating nexus 6.
Click to expand...
Click to collapse
Not disputing that.
But realize that there are folks out there who may expect the Nexus devices to work the way they always have, and may not bother to ever visit xda (maybe they are ok with their devices completely stock). If a user doesn't visit xda, they aren't going to search xda (unless they don't know how to do what they want to do, or they suspect things have changed)

Why do I have to search about a standard procedure I am doing since years and there is no warning from Google that this time this procedure might brick the phone!!!

Pr0fess0rX said:
Why do I have to search about a standard procedure I am doing since years and there is no warning of Google that this time this procedure might brick the phone!!!
Click to expand...
Click to collapse
This is what we've been discussing in the posts above. The process has changed significantly with the new security features of 5.1 and Google needs to update their page to reflect this.
That being said, you still should read before jumping into anything because things change. Plain and simple, things and procedures change. We're talking about a whole new OS with lollipop. It is not entirely your fault but in a sense, you, with a bit of searching and reading, could have avoided this situation.
Sadly, this is a very common problem, which led to me working with others and creating the guide to safely re-lock. A 2 minute search of XDA would have given multiple results for you to read.
---------- Post added at 09:47 AM ---------- Previous post was at 09:35 AM ----------
I also feel that this hasn't been publicized enough. This thread is a perfect example. I understand that people have done things the same way for years but without an in your face warning of some sort, why would people think they were doing it wrong? Yes, my thread is mentioned in the sticky roll up thread, and for some that is enough. But as mentioned earlier, what about those that don't read the sticky roll up or use XDA at all?
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right? Why, also, have none of the Android forums or online magazines made mention of the new procedures? Obviously people use factory images and many have bricked. ???

Evolution_Freak said:
The blame should fall on Google for not promoting a new procedure. They have to be aware of it, right?
Click to expand...
Click to collapse
I agree - at the very minimum, update the instructions on the factory images site. Currently, here's what it states
6. Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
1. Start the device in fastboot mode again, as described above.
2. Execute:
fastboot oem lock
Click to expand...
Click to collapse

Flickering screen?

I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing

electrojas said:
I just sent back the N6 that had the screen burn out, I got my RMA device and its on just 5.1 not 5.1.1 should I update it or keep it does it matter? Also this N6 is doing some of the same issues that the other device did before it burned out. The screen has a lot of flickering and triangle flashes but only when I'm using my web browser, also, today I got off of a phone call and the proximity sensor failed to turn the screen on. What's up with that? I'm starting to wonder about these N6's man. Any ideas guys. I think I may need to just flash the s#-t out of this thing
Click to expand...
Click to collapse
If it was mine, I'd RMA this one too.

Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.

prdog1 said:
Unlock it. Fastboot flash the updated 5.1.1 factory image and see what you have. If bad send it back. If good it all good.
---------- Post added at 12:47 PM ---------- Previous post was at 12:39 PM ----------
What browser. It may be the problem. There were proximity sensor fixes in one of the updates. Not sure which.
Click to expand...
Click to collapse
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.

electrojas said:
I'm using adblock browser. I just updated to Windows 10 so now my adb is all jacked up for some reason. When I turned on the phone it said that there was a 5.1.1 update ready to be installed. Should I just take that one before I unlock the BL and root or do the unlock first? Thanks to all of you who are helping me out. Good people.
Click to expand...
Click to collapse
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol

I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks

electrojas said:
I'll have to check. I'm so gunshy now I only hooked this to pc just to put music on it. I'll unlock BL and try the update after. Thanks
Click to expand...
Click to collapse
If able to put music on your driver is good. Need ADB/Fastboot working or you are already dead in the water.

prdog1 said:
Unlock first. Too many been bricked on that update with bootloader locked. I wouldn't take it. Win 10 didn't jack with my adb. I have full SDK tho. Some are using the 15 minute adb/fastboot. I would search and try to reinstall it. Does your usb debug work as far as showing device MTP on PC. If not you lost the Google driver.
---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------
More than likely that browser is the flicker problem. I use Chrome but with Adaway and MOAB. No adds anywhere. lol
Click to expand...
Click to collapse
15 minute adb? What is that like a tool that does all of that for you?

electrojas said:
15 minute adb? What is that like a tool that does all of that for you?
Click to expand...
Click to collapse
It the lazy man ADB/Fastboot for those that don't want to install full SDK and edit the environmental path.
http://forum.xda-developers.com/showthread.php?t=2588979

So I just follow the unlock procedure in the how to post like normal now right

electrojas said:
So I just follow the unlock procedure in the how to post like normal now right
Click to expand...
Click to collapse
Enable unlock in developers options. Boot to bootloader. in command prompt type "fastboot devices" to make sure your device id shows up. If shows device type "fastboot oem unlock". Will see prompt on phone to agree.

It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it

I suppose now I can take the downloaded one or do you recommend a better file. I really would like to keep this Damn phone

electrojas said:
It's just finished so now does it matter which 5.1.1 I take, and do I have to put TWRP on this in order to do it
Click to expand...
Click to collapse
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock. DO NOT use toolkit. Do it manually with fastboot commands.

prdog1 said:
Latest for all carriers is I version unless you are on TMobile then it is the one that says TMobile only. They don't have the security update yet. No need for TWRP yet as long as unlocked. Get it booted and see if everything works. Do NOT relock.
Click to expand...
Click to collapse
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?

electrojas said:
Mine is unbranded factory unlocked. It's restoring all my backed up poo right now. I guess I have 2 options. 1 take the Ota they send down or install the one I downloaded yesterday. It says for all carriers except tmobile. I got it from Google yesterday. It's the exact one that was on the phone I sent back. Do you have any particular preference or reccomendation?
Click to expand...
Click to collapse
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.

prdog1 said:
The new I version has the Stagefright security fix otherwize the Z version is fine. That is what I am on. Haven't updated yet.. You can try OTA as long as unlocked. Have seen posts that say OTA won't work unlocked. Not sure. If it bootloops and it is locked you are hosed again and have to RMA.
Click to expand...
Click to collapse
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.

electrojas said:
The new I version? Is the best place to get it on here or Motorola? Also your gonna think this is a stupid question but what is I version? I'm coming from Sammy to LG back to Sammy, now this. Learning about fastboot its all new to me. Thanks bro
Sent from my Nexus 6 using XDA Forums Pro.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images

[How to]VS980 Confirmed Root and Recovery Installation Method

Hey guys,
Recently, I have been trying to re-root my LG G2 VS980 that was returned to lollipop stock (LG Firmware). However, all the tools I knew that previously worked, (Ioroot, Towelroot, Stumproot, Kingoroot, etc..) did not work. After months of testing, I finally found one app that currently works called KingRoot.
As far as I know, it is the only root method that acutally still works after LG patched most of the exploits so I thought I would share the info with you guys in case some of you are still interested in rooting your G2.
Instructions:
1. Install Kingroot: http://kingroot.net/ (the APK doesn't work for the G2)
2. Go to settings in your phone and click the build number 7-10 times to enable Developer Options
3. Go to Developer Options and enable USB Debugging
4. plug the phone into your computer and launch the program. Make sure you see the USB Debugging card that will pop up on your phone.
Launch the program and allow the program to root your phone.
Sidenote: The only downside to the app is it is all in Korean but it is very easy to tell what it is asking due to excellent pictures
After you receive root, download the app RootChecker just to make sure.
To Install TWRP:
1. Instructions: Go to Play Store and type in the search window, "AUTOREC".
2. Select the correct variant: ex. VS980=Verizon etc...
3. Install the app.
4. Watch TWRP Install on your phone.
5. Reward yourself on your hard work with a pat on the back.
So that's it; A fast easy, and trouble free method on getting root and installing TWRP

Thanks for this. I recently acquired a G2, and will be trying this out tonight.

tribalartgod said:
Thanks for this. I recently acquired a G2, and will be trying this out tonight.
Click to expand...
Click to collapse
No problem. Have fun with your custom ROM of choice.

Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean

I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?

y300owner said:
I managed to enable debugging mode which was by setting the 'USB Type" on the phone to "Internet -> Ethernet"
But Kingroot isn't managing to root the phone. It goes 100 percent and nothing.
Ioroot managed to get the phone into the reboot phase but the phone no longer processed the splash screen of the recover/bootloader. The splash screen which has the android mascot on its back with abdomen open.
"LG G2 One lick Tool" makes the phone go to "download mode" but its stuck at 0 percent. I disconnect and replug in hope of kickstarting it, doesn't work.
What can I do now?
Click to expand...
Click to collapse
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk

y300owner said:
Can you share the setup files? I also need to re-root my Verizon phone. The kingroot ownload links looks dead
i downlaoded it from here. I have usb dev enabled. now what? http://kingroot-pc.en.uptodown.com/download
Stuck on that step. I know its telling me to enable USB debuggin which I have, it doens' do anythong when I click Go in Korean
Click to expand...
Click to collapse
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/

mach01 said:
Hmm... Sorry for the late response. Try this link and see if it works: http://www.kingroot.org/
Click to expand...
Click to collapse
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
Jshokamp said:
Where you able to get it to work? I am running into the same problems.
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
What problem? Check one of the thread I started. Posted everything on it.

y300owner said:
Thanks I tried almost almost everything.
Stumbled upon Stump root last night and it brute forced it way in.
---------- Post added at 12:46 PM ---------- Previous post was at 12:44 PM ----------
What problem? Check one of the thread I started. Posted everything on it.
Click to expand...
Click to collapse
You on 39aa or just 39a?

Lawlrus said:
You on 39aa or just 39a?
Click to expand...
Click to collapse
No idea. I was on a downgraded stock ROM, VS980_27A or was it VS980_24A. Can't remember; 4.4.2
Whatever it was, none of the popular rooting method was working. They were managing to do 'semi root' as in root message was displayed in "hard reset mode" and in 'download mode' but there was no root when the OS fully booted. The 'stock recovery' was also corrupted as in it showed a dead android with red exclamation mark. From the searching I did, people were saying there was no recovery installed so I needed one but I could not install. No stock recovery means no 'adb'.
Stump root gave 'complete' root. I hope you understand what I'm trying to say.

Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.

UserofAndroid1813 said:
Will this work if I am on the 39aa update from Verizon? I am skeptical about this because this is my only phone and don't need to mess it up.
Click to expand...
Click to collapse
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.

Lawlrus said:
I don't think I've seen a way to root 39aa as of yet. One of our developers was asking about it as well, if you do find a way, please @ me so I can hook him up
I'm still looking around for a way.
Click to expand...
Click to collapse
I tried and failed at it. I am downgrading to VS98039A_05 and going from there. it seems VS9803AA was meant to patch root and also SF security patches.

This XML file does not appear to have any style information associated with it.
The document tree is shown below.
<Error><Code>AccountProblem</Code><Message>
Your Google account is not currently enabled for this operation. Please check https://code.google.com/apis/console/#:billing to see if you have a past due balance or if the credit card (or other payment mechanism) on your account is expired. You can find additional information at https://developers.google.com/storage/docs/signup</Message></Error>

Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-g2-running-lollipop-with-lg-one-click-root/

Interesting... I've tried that method four times and it never worked for me. Good to hear it works for other people though. I agree not to many people want to use
Korean deciphering skills just to root their phone but its just an option.

marathonjon said:
Thanks for this. For people who don't want to mess with Korean, or if Kingroot doesn't work, LG One Click Root still works on VS9803AA, although you may have to run it 3 or 4 times. Here's the original post: http://forum.xda-developers.com/lg-g...lipop-t3056951
And here's a good guide: http://webtrickz.com/how-to-root-lg-...ne-click-root/
Click to expand...
Click to collapse
Both of these links are dead.

CruelSun said:
Both of these links are dead.
Click to expand...
Click to collapse
Links are fixed. The whole URLs don't show in the post, but if you click on them, they should work.

those with the issue of kingroot not reading your phone plugged in. put your usb option on phone to PTP camera mode and it will work now.

Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
---------- Post added at 05:55 AM ---------- Previous post was at 05:54 AM ----------
Furqan Ullah said:
Even doing all, i m still unable to get my phone recognized. Switched many times befween ptp
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
And other file transfer option. USB picture is displaying sometimes or sometimes circle
Sent from my VS980 4G using Tapatalk

Back to Stock Roms

So here we have stock files pulled from the Motorola Firmware Team on AFH Just mirrored for your convenience
I cant include the firmware for Verizon & Att due to the fact there bootloaders are NOT unlocked. Therefore if somebody reads this and corrects me, they cant flash it.
I have the stock files and Flash Alls made by me and @Uzephi
Sprint Flash Alls made @Uzephi
Latest https://androidfilehost.com/?fid=889964283620761146
June https://androidfilehost.com/?fid=962021903579487984
Flash All T-Mobile made by me
August https://drive.google.com/file/d/1MW4JWa8Zij36hsO0u41Zf-9a6OT3FpbA/view?usp=drivesdk
June https://drive.google.com/file/d/0B1tqDJm_qQf4YWxreUJSWXJWeVk/view?usp=drivesdk
To use the flash all for Sprint and T-Mobile you simply unzip the file and put your phone into fastboot mode and hit flashall.bat and that's it. I have already included the fastboot file in the zip.
Requests: If you have a request for firmware please leave a message below.
Credits: @Uzephi
Motorola Firmware Team https://androidfilehost.com/?w=profile&uid=24269982087010314

Tested
Just tested the T-Mobile one and all worked perfect.

Will it work to downgrade from the OTA update yesterday?

crackerjack9249 said:
Will it work to downgrade from the OTA update yesterday?
Click to expand...
Click to collapse
Yes, i was on the Tmobile update 26.5 and it downgraded just fine.

Is it possible to flash a Verizon rom on sprint moto z2 force?

I got permission denied and now phone says corrupt won't boot, and to visit Motorola website unlock bootloader. Do I have to unlock bootloader first? How can I fix this?

lrosado said:
I got permission denied and now phone says corrupt won't boot, and to visit Motorola website unlock bootloader. Do I have to unlock bootloader first? How can I fix this?
Click to expand...
Click to collapse
I would say yes
Sent from my SM-N930F using XDA-Developers Legacy app

I am unable to enable one unlock since the phone bricked once I tried to install this. It wont boot. Any suggestions on how to get my device unbricked or any way to enable one unlock using adb?

Any chance we could get a tmo flash all of the august update?

Hasn't been released yet

Any way to fully lock this backup? Long story short the IMEI reads 0 and this didnt fix the issue, but I need to phone to be 100% stock.

matistight said:
Any way to fully lock this backup? Long story short the IMEI reads 0 and this didnt fix the issue, but I need to phone to be 100% stock.
Click to expand...
Click to collapse
I did a warranty exchange when this happened to me.
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
Question, is there a way to make the bootloader not say you've unlocked and flashed different software?

Also, can I just flash the stock boot?

anyone got stock boot img for t-mobile? if so can you send me a link please

Does anyone know if I can run the fasboot command to lock the bootloader after I've flashed this? I need to take mine back in for an exchange.

charlatan01 said:
Does anyone know if I can run the fasboot command to lock the bootloader after I've flashed this? I need to take mine back in for an exchange.
Click to expand...
Click to collapse
fastboot oem lock

cfriendr said:
fastboot oem lock
Click to expand...
Click to collapse
Yeah, I know the command. I was just wondering if that was all it takes and if it worked. Sorry my question was so vague.

charlatan01 said:
Yeah, I know the command. I was just wondering if that was all it takes and if it worked. Sorry my question was so vague.
Click to expand...
Click to collapse
It half-worked for me. During boot-up, it doesn't give me the "unlocked bootloader" warning, but it *does* give me a "The OS installed is different" message. Looks similar, but the text is yellow instead of orange.

cfriendr said:
It half-worked for me. During boot-up, it doesn't give me the "unlocked bootloader" warning, but it *does* give me a "The OS installed is different" message. Looks similar, but the text is yellow instead of orange.
Click to expand...
Click to collapse
I'm trying to get rid of the "your device has loaded a difference operating system". Did you find the way to get the phone back to 100% stock?

First off, wanna give a HUGE THANKS to joemossjr for releasing this package AND for that .bat installer! Long story short, I was about to either claim warranty or Jump! (T-Mobile insurance/upgrade program) due to me trying to hook a USB Thumbdrive in over USB OTG (Kingston 16GB) and then there were slowdowns and app crashes, everywhere... heck it was to the point where I kept getting spammed with android.process.acore keeps crashing messages! Couldn't use many internet apps, no phone calls, and could barely text just to name a few.
I do got a suggestion though: is it possible to have a modified version of the June ROM package on Sprint & T-Mobile to where instead of having the stock boot.img, you can have the modified version with the Magisk root access? That would be great and somewhat of a convenience (YMMV; I used this patched boot.img on the 26.2 version and both system updates & t-mobile visual voicemail setup kept falling flat on its face everytime)
Thanks again, YOU ARE THE MAN!!!

HELP: One plus 3t Root without bootloader unlock . New exploit

hi friends,
i want help regarding the tutorial explained here . This is because i wanted to recover deleted photos from my phone which need root . but on bootloader unlock phone will reset .
so friends can any one explain the guide provided below to achieve root. Thanks a lot
https://www.xda-developers.com/oneplus-root-access-backdoor/

I think its possible with one plus 3 and not with 3T because of the SOC...I might be wrong though

Where exactly did you get stuck? I went through the article and it's fairly self explanatory. Long story short: enable USB debugging, connect phone to PC, open adb shell and enter the command presented in article. That's the one and only step really.
Sent from my OnePlus 3 using Tapatalk

Do tge phone need to be in fastboot mode?

narutosri said:
I think its possible with one plus 3 and not with 3T because of the SOC...I might be wrong though
Click to expand...
Click to collapse
It is written in plain English in the article linked that it works with all OnePlus phones
---------- Post added at 07:31 AM ---------- Previous post was at 07:27 AM ----------
tcdcesr said:
Do tge phone need to be in fastboot mode?
Click to expand...
Click to collapse
The article is quite clear just copy paste the code line in your adb console on your computer. It just runs the application in the specific mode entering to have access to admin privileges. You then must install the root app I guess you'll find tuto for that.

https://forum.xda-developers.com/oneplus-3t/how-to/root-op3t-unlocking-bootloader-t3705238
Thanks friends. Anyone with similar difficulty like me can go to above thread and install angela fscoiety apk and follow the comment on that app after connecting with usb debugging on. The command should be modified as per your file path. Thats it
https://ibb.co/bFBqdR