Database Users

[GUIDE] Simple, Non-Destructive Root for Nexus S i9023, i9020A and 4G Gingerbread

Disclaimer
This may work on other versions - I can't see any reason why not - but the only ones it is confirmed working for is the i9023 and the i9020A running 2.3.6 and the Nexus S 4G running 2.3.7. If you use this to root other handsets then reply in the thread and I'll update this. This assumes you are starting with a completely stock Nexus S.
About
This works with Windows only by using DooMLoRD's excellent Easy Rooting Toolkit to root without deleting your data in under a minute.
Credits
This is a noob-friendly mashup of various tutorials and sources to provide you with root access on the stock Gingerbread ROM, and nothing else. Credits to DooMLoRD, for his amazing toolkit and kursk for the original i9023 tutorial that made me think Consider donating to DooMLoRD if you find this helpful.
Steps to Root your handset
Preparation
1)Update your Nexus S to 2.3.6 if it isn't already, getting the update file from here.
2)Rename the file you downloaded to "update.zip". Place it in the root of your SD card.
3)Reboot your phone into Recovery Mode by powering it off, then on again while holding the Vol + button.
4)Now you’ll see a triangle with exclamation mark, now repeatedly press Vol+ and power button to enter Recovery Mode.
5)Select "apply sdcard update.zip" and if necessary, follow on screen instructions to slect the update.zip file.
6)Reboot the device and you will be updated to 2.3.6
Click to expand...
Click to collapse
Connecting to your Computer
1)Download and install the Android SDK. This may not be necessary for the rooting process but is certainly handy for future hacking or mods that you will likely want to do once you've rooted.
2)Install the Nexus S drivers as detailed here.
3)Make sure USB debugging is still enabled on your device and you are ready to proceed to rooting.
Click to expand...
Click to collapse
Rooting your Nexus S
1)Download DooMLoRD's Easy Rooting Toolkit here.
2)Extract the zip to your desktop.
3)Connect your phone by USB and confirm USB Debugging is still enabled.
4)Double click the runme.bat file located in DooMLoRD's Easy Rooting Toolkit
5)Read the command prompt and press any key to root.
6)Your handset will be rooted and then reboot. The process should take around 1 minute.
7) Congratulations! You now have the stock ROM rooted and Superuser installed.
Click to expand...
Click to collapse
Further Steps
Now that your phone is rooted, you can use apps that require superuser access such as Root Explorer to modify system files.
You can install ROM Manager and use that to flash custom ROMs.
You may wish to unroot your device. This can be done as detailed by DooMLoRD here
Click to expand...
Click to collapse
I hope that some people find this useful.

But what's wrong with just flashing the signed superuser zip from stock recovery or any other superuser zip from cwm?

marcelnn said:
But what's wrong with just flashing the signed superuser zip from stock recovery or any other superuser zip from cwm?
Click to expand...
Click to collapse
Unlocking the boot-loader erases the phone. Hence the "Non-Destructive" part of the title.

Yes, this method does it in under a minute and doesn't wipe your phone, making it easier for people who are new to modding or just want an easy and quick root.

Rooted an 9020a stock 2.3.6. Great work, thanks.

TheManicGibbon said:
or just want an easy and quick root.
Click to expand...
Click to collapse
. zing!

Can someone please confirm if this works for i9020T OTA 4.0.3?

I don't *think* it will work on ICS...but you could give it a try, or wait for someone else to if you don't want to

Couple quick noob questions...
Does this unlock the bootloader?
Is this considered the old fashion way of rooting the NS4G?
I've tried the One Click Root by ShabbyPenguin with no luck
So I'm lookin to get this NS4G runnin 2.3.7 Gingerbread rooted..
Hoping someone can answer these questions for me thanks.
FWIW I'm not a complete noob I'm coming from a rooted EVO4G so I'm a noob in the NS4G area completely lol thanks in advanced

I've just checked my Nexus S i9023 and it appears the boot loader is still locked, in answer to your question. It is not possible to unlock the boot loader without wiping all your personal data.
Hope this helps.

TheManicGibbon said:
I've just checked my Nexus S i9023 and it appears the boot loader is still locked, in answer to your question. It is not possible to unlock the boot loader without wiping all your personal data.
Hope this helps.
Click to expand...
Click to collapse
Not really....
I'm not really worried about the phone being wiped clean I could careless its not my phone Im just confused about rooting this NS4G..and what actions need to be taken to do so...
I ran the One Click Root by Shabby but I keep getting
"error: device not found"
And I've installed every single driver that I've found and I still get the same error running the one click root
I guess my question should've been
What's another way to root the ns4g without the one click root?
Tell Siri I said SUCK IT!

Sorry, I forgot to answer your other questions
This method can be used to root a Nexus S 4G: I can't confirm it personally because I'm in the UK and don't have access to any kind of 4G tech, but "Samsung Nexus S 4G 2.3.7" is listed in the supported devices post here in DooMLoRD's Easy Rooting Toolkit Thread

TheManicGibbon said:
Sorry, I forgot to answer your other questions
This method can be used to root a Nexus S 4G: I can't confirm it personally because I'm in the UK and don't have access to any kind of 4G tech, but "Samsung Nexus S 4G 2.3.7" is listed in the supported devices post here in DooMLoRD's Easy Rooting Toolkit Thread
Click to expand...
Click to collapse
Awesome I'll give it go this evening thanks for answering the other threads Ive posted are dead nobody answers questions so I'm gonna proceed in hitting your thanks button. Lol
Tell Siri I said SUCK IT!

Yeah it can occasionally seem a bit like no one answers
Glad I helped.

Worked on my Rogers Nexus S I9020A, Thanks!

TheManicGibbon said:
Yeah it can occasionally seem a bit like no one answers
Glad I helped.
Click to expand...
Click to collapse
Didn't work what windows should I be running to do this?
Tell Siri I said SUCK IT!

question
I run the runme file and every step gets a
"the system cannot find the path specified"
error
then it says all done and the phone never reboots and nothing changes
I have installed the samsung drivers and tried again and still nothing changes
so . . .
now what?

TheManicGibbon said:
Yes, this method does it in under a minute and doesn't wipe your phone, making it easier for people who are new to modding or just want an easy and quick root.
Click to expand...
Click to collapse
Sorry, I don't understand. How you can install custom ROM as mentioned in OP if bootloader stays closed? Does it give only root access, doesn't it?
Sent from my Nexus S using xda premium

I'm getting a nexus s i9020T soon and was wondering if this root method might work for it? When it comes to computers I'm a complete idiot. If something does go wrong I'll be clueless how to fix it. The reason I want to root is to remove some apps I can't uninstall and also so I can do a full backup including app data. If this method is not suitable what is the best way to do it? A super easy one click method would be preferable. Thanks!

Yes! This Method Works! If you follow this step by step! It will Unlock the bootloader and give root access! I just rooted this morning ladies and gents!

New to rooting - What is easiest?

Hi everyone,
I'm new to "rooting" android devices, although I have jailbroken all my iPhones and "rooted" my palm pre.
As a newbie, it seems the "root toolkit" is the best way to do this? Is this Windows only, or is there a Mac version?
anything else I should read up on / know before rooting? I basically want to root, initially at least, to get sixaxis support and stickmount working.
Thank you all for your help in advance.

First of all, this is the wrong section. You should post inquiries in the q/a section.
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Sent from my Nexus 7

Take a peek at the nexus root toolkit thread in this forum...quick and easy.
Sent from my Nexus 7 using xda app-developers app

The tool kit is windows only, correct?

Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?

Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
I would agree with:
evonc said:
In terms of rooting, I personally find the easiest way is to unlock the bootloader, flash a custom recovery such as cwm/twrp, and then install the supersu zip via recovery. You should be able to unlock the bootloader and install recovery via fastboot. After that the rest is just copying a file to the device, booting into recovery and installing a zip file.
Click to expand...
Click to collapse
Then you know what is happening, and how it works... so if you run into troubles later, you know what to do.
Hard to brick this device.

Foxman2k said:
Any reason to NOT use the tool kit and go with other more manual methods?
Click to expand...
Click to collapse
For practice, and maybe the one-click solution is not flexible enough for your means. It's usually dependent on the developer to update it, so do check if it has any limitations.
Also, the ones I've seen are Windows only.
Foxman2k said:
An iphone is virtually impossible to "brick" - Is the same true for the N7?
Click to expand...
Click to collapse
As long as you don't mess up the bootloader, it should be possible to reflash stuff via recovery or fastboot. Bear in mind there have been exceptions (though that came about because of a serious kernel bug, rather than due to user error) so this can't be a guarantee.

I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it

spdecoste said:
I was new to rooting too, using the nexus toolkit helped me learn a lot about rooting and all the android stuff I wasn't used too!
I really recommend it
Click to expand...
Click to collapse
Another recommendation for WUGS rootkit - literally very easy foolproof step by step menus/instructions - only prob I had were the drivers - just manually pointing to driver directory sorted this out.

I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.

exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?

exzacklyright said:
I made a guide that could help you. http://exzacklyright.blogspot.com/2012/07/nexus-7-guide-for-adbunlocking-rooting.html There's really only 3 commands. I don't recommend toolkits.
Click to expand...
Click to collapse
This seems to rely on Windows. Any Mac tools available?

Foxman2k said:
Great, will check that out!
Can someone explain to me, in layman's terms, what "unlocking the bootloader" does?
I'm familiar with what "root" technically means as I've been using Linux since back when it had to be loaded on floppys and manualy configuring X LOL. So basically "root" means you have access to super user privileges.
Why is the bootloader locked in the first place? Once it's unlocked can it be locked again?
Click to expand...
Click to collapse
Unlocking the bootloader allows you to mess with the bootloaders progression at startup, which gives you the ability to install a custom recovery and gives us the method to gain root access. The bootloader can be unlocked by many different methods - some manual and some "one-click". I'd suggest doing it the manual way first, so you understand the process, and are able to fix it manually if anything goes wrong.
To my understanding, it's locked so that people who don't know what they're doing can't mess the device up. It's a safety procedure basically.
To relock the bootloader, you just type (I only know how to do this in windows - Linux and Mac work as well al beit differently)
Code:
fastboot oem lock
and you're all set.

Foxman2k said:
This seems to rely on Windows. Any Mac tools available?
Click to expand...
Click to collapse
The Android SDK and ADB tools are equally available on Linux and Mac. You won't have to do the "Adding to Path" thing. All of the ADB commands will be the same, though.

I didn't know anything about rooting at all too, despite having an android phone for more than 2 years.
I went with the one-click root process.
Download this file, plug your Nexus 7, follow the instructions- which means typing Y, N, Y etc
Done in 5 minutes. There's a youtube video on it too. Go check it out.
I still dont know much about the process.. except I'm unlocked and rooted =)

I have a few naive questions
Do I have to do the OEM unlock to root the device? I would prefer not to wipe it.
Assuming I don't hard brick the device, can I go back to stock for warranty work?
Does rooting the device mean I can't get OTA updates from Google? For now I just want to run the stock kernel/rom and get updates. I just want root to run titanium and certain other apps that require root.
I've seen a thread that suggest that the play store (market) doesn't work on rooted devices. Is that true?

[Q] Question about rooting

Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!

timour79 said:
Hey everyone. I was wondering if you could root without unlocking the bootloader first. I know i wouldn't be able to flash roms and such, but I just want the Superuser app so I can use apps like Titanium backup and sixaxis controller. Thanks in advance!
Click to expand...
Click to collapse
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.

Billchen0014 said:
sorry to tell you, but there is no way of rooting without unlocking the bootloader, since its secured and you won't be able to flash the necessary super user scripts. i could be wrong, but i think its necessary to unlock the bootloader.
Click to expand...
Click to collapse
Can I unlock the bootloader, root, then relock the bootloader and keep the root?

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
if you choose the relock bootloader option in the toolbox, it removes superuser as well

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
Alright, thanks

Billchen0014 said:
if you choose the relock bootloader option in the toolbox, it removes superuser as well
Click to expand...
Click to collapse
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock

timour79 said:
Can I unlock the bootloader, root, then relock the bootloader and keep the root?
Click to expand...
Click to collapse
What's your reason for wanting it relocked?
Sent from my HTC Vision using xda app-developers app

noneabove said:
What's your reason for wanting it relocked?
Click to expand...
Click to collapse
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?

Nate2 said:
I'm not the OP, but I don't like the open padlock icon that shows that the device's bootloader is unlocked.
Any disadvantage to re-locking the bootloader?
Click to expand...
Click to collapse
Well I dont want to completely void the warranty, unless rooting already does that. If it was mine then i would've unlocked and rooted. I'd probably already have a rom and kernel on it. But it's actually my dad's, and he said I can root it if I don't do anything too serious(like I said, I just want Superuser so I can use things like the sixaxis controller app.)

comminus said:
This is a good example of where using a toolkit fails.
You can re-lock the bootloader without affecting root. Boot the phone in fastboot mode, connect to computer and run the following command:
Code:
> fastboot oem lock
Click to expand...
Click to collapse
Would that be manual rooting?

NRT questions
hey there
have some newb questions about rooting along the same lines of the OP. hope you can help me
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
sorry for the newb questions but there are so many different guides out there and some of them refer to older versions of the NRT so just want to clarify these points.

timour79 said:
Would that be manual rooting?
Click to expand...
Click to collapse
No. All you are doing there is unlocking the bootloader. Unlocking the bootloader is the equivalent of pre-heating your oven. You haven't messed with any ingredients or cooked anything yet.
---------- Post added at 01:05 PM ---------- Previous post was at 12:53 PM ----------
Lemegeton300 said:
1. what are the chances of bricking the nexus by rooting if all i am going to do is the same as the OP. use sixasis and the usb stick apps. has anyone completely bricked their device or is there always a way back. i have seen a lot of info and guides to suggest you can always get the factory image restored.
2. does the superuser app already need to be installed on the nexus or does the toolkit install it for me?
3. if i am only rooting for basic stuff like sixasis is there any point installing clockword mod?
4. i have downloaded the toolkit and tried the driver installation. my experience was different from the screenshots in the toolkit and guides i have seen but when i run the driver check/step 3 it comes back with success and i have managed to make a backup. so does this imply i can safely unlock and root.
5. if i have to get my device repaired and relock the device and un-root it will my warranty be ok or can google still detect rooting has been done?
Click to expand...
Click to collapse
1. The chances are pretty slim for permanently bricking. That is the beauty of Nexus devices - the entire factory image is available to be flashed back on if you screw things up. That is the equivalent of reformatting your harddrive & reinstalling your OS on your desktop.
2. mkskip's toolkit will install it for you. I am sure wug's will too.
3. You don't have to install CWM, especially if you are thinking that you will pretty much always stay stock. But, the bug might hit you in a month or two to start playing around, and then CWM or TWRP is your friend. I installed CWM & made a backup pretty quickly in case I do something I shouldn't, such as accidentally deleting a vital system app. That way you do not have to do the factory reinstall route. Every few weeks you can make yourself a fresh backup just for fun.
4. You should be fine - the drivers must be working if the toolkit is doing backups for you. I am assuming you are using mkskips toolkit based on this question - his instructions say that sometimes in 1 step it says drivers didn't install correctly when they actually do - Windows is...Windows. If you want to be sure, ask away on mkskip's thread. He is quite helpful.
5. If you reflash the factory image & the bootloader is relocked, there is nothing for them to see...not that they'd really care since the point of a Nexus is to develop on it. You would only be returning it for a hardware issue, and the software unlocking has no impact on the hardware problem, since your hardware issue would've happened no matter what software you had on it. The only way a software thing could cause a hardware issue would be if you over-overclocked it & cooked some parts. You'd really have to work at doing that since these things usually shut down when the temperature gets too high.
In short: root it & enjoy it!

Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app

Lemegeton300 said:
Thanks for the info. Its wugs tool I am using so not sure what happened with drivers but like you said its good to go. So will the clockwork mod essentially create a restore point for me ?
Going to go ahead and root the device now. Thanks for the help.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes. When you restore a backup it will be just as it was when you made it. Have fun!

Stuck on Google Logo, Can't Unlock Bootloader

Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?

Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.

if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.

Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?

hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.

I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?

Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M

Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.

Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?

Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/

Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.

Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.

Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.

Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea

Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.

akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.

THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.

trouble unlocking tmobile bootloader

I SIM unlocked my T-Mobile one plus 6t and went to OnpePlus website and followed the directions to get my T-Mobile unlock code but when I put my phone in bootloader mode and executed fastboot command it's stuck on waiting on device. The phone says device is locked on bootloader screen.

Follow this guide and you should be fine you are likely missing drivers or something simple
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789

bladestonez said:
Follow this guide and you should be fine you are likely missing drivers or something simple
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
Thank you, I will try updating my adb and fast boot drivers and see if that works. Adb worked fine as it listed my device.

bladestonez said:
Follow this guide and you should be fine you are likely missing drivers or something simple
https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789
Click to expand...
Click to collapse
Hey I just want to give you a big THANKS! I updated my adb and fasboot drivers and binary and sent in my OEM unlock code. I know there is other ways to switch it to the international version but I'm playing it safe. Again thank you

spasecowboi77 said:
Hey I just want to give you a big THANKS! I updated my adb and fasboot drivers and binary and sent in my OEM unlock code. I know there is other ways to switch it to the international version but I'm playing it safe. Again thank you
Click to expand...
Click to collapse
Not a problem happy to help.