Database Develop

Going back from 5.1 to 5.0

Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk

You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty

rootSU said:
You can upgraded / downgrade from any ROM. Its not a HTC
The locked boot loader issue is user error. If you lock the BL and the phone doesn't boot, you'll have to get Moto to fix it. And yes that would be covered by warranty
Click to expand...
Click to collapse
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk

kenbrownstone said:
Do I need to flash old boot loader or radio? Thanks for your time.....mods are welcome to delete
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It depends what you're expecting in future. If you want OTA, you'll need everything to be 100% stock and the right version. If you don't care about that, minimum is system.img and boot.img.

i tried to downgrade my bootloader through fastboot from 5.1's bootloader to 5.0.1 and fastboot throws an error from moto saying it cant be downgraded.
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.

freebee269 said:
have a question. is it ok to flash the factory 5.0.1 system and boot while on the 5.1 bootloader and radio? i have read a few threads of people bricking but it's unclear if it's possible to use an aosp rom that's 5.0.1 or 5.0.2 on 5.1 bootloader and radio.
Click to expand...
Click to collapse
I had been running Chroma 5.02 with the 5.1 bl and radio. I reverted the radio because of issues with TMo, but the bl seemed fine. FWIW, I made all my changes via fastboot.

kenbrownstone said:
Can you go back to 5.0 after flashing 5.1 Roms? Was just wondering because seen a lot of bricks ..Some bricks from licked bootloaders others from flashing..I just don't want to brick because I bought mine from someone and don't have insurance .Unless it could fall under factory warranty replacement....
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app

Konfuzion said:
Just make sure you have OEM Unlock checked under dev options and you will be fine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
It resets on boot. Check it boots before relocking

rootSU said:
It resets on boot. Check it boots before relocking
Click to expand...
Click to collapse
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?

naresh2990 said:
Since it gets reset then do I need to recheck OEM unlock option at every boot or its fine to leave it as it and I can reboot anyway I want?
Click to expand...
Click to collapse
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.

rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.

naresh2990 said:
Seriously this thing is giving me a headache, I am not going to toggle anything in bootloader now and it's a pain to check this option everytime before doing a reboot, it was good before 5.1, it used to stay as it is.
Click to expand...
Click to collapse
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2

rootSU said:
It really depends what you want to do. If your bootloader is remaining unlocked, it doesn't matter. If you are locking it again, to unlock it, you must set the option before booting to bootloader so if you want to minimise risk, then you will need to set it every boot. We do not know where this setting is stored yet. I really don't understand the need for this option to be honest.
Click to expand...
Click to collapse
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app

pwned3 said:
Just leave it unlocked. If you plan on manually updating I don't understand why you would lock it. just in case something goes wrong if it's unlocked you have options. If it's locked you have very, very few
Sent from my Nexus 6 using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.

Konfuzion said:
The setting is due to Google's new anti theft options ( http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/ ) . If you have OEM Unlock checked this protection can easily be bypassed with a flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.

naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
rootSU said:
But who really cares if a thief can "use" the phone when it is stolen? They can't use it as a phone because the IMEI will be blocked. If they unlock it, it will wipe your data too. I'd rather not have to set an option within android to allow me to unlock my bootloader and the problems here have proven this to be a detriment to people who flash.
Click to expand...
Click to collapse
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?

naresh2990 said:
I am not going to lock my bootloader. I like it Unlocked but my point of concern is that OEM unclock option get reset to uncheck at every boot. I want to know what will happen if I reboot my phone and OEM unclock option is unchecked(means bootloader is locked, this is what I think) while my bootloader is actually Unclocked.
Click to expand...
Click to collapse
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
the_rooter said:
I am confused about something if the device is already unlocked does it matter if that OEM is ticked? I reboot twice already and it reset it back to being unticked. So what I am saying is if i go from one rom to another and that isnt ticked will it cause issues even if the bootloader is already unlocked?
Click to expand...
Click to collapse
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app

Konfuzion said:
No if it is unchecked your bootloader is still unlocked, but you will not be able to unlock it again without booting into your device and checking it again.
Where people are getting bricks is they are downgrading their radio and bootloader, at which point their bootloader relocks, and they are stuck at bootloader as they can't access anything other than bootloader and that is locked.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 07:56 AM ---------- Previous post was at 07:50 AM ----------
No issues going from Rom to Rom with it unchecked. Issue lies in... No OS so you can't boot up and check oem unlock, stuck at a locked bootloader screen, so you can't flash a custom recover, can't restore because you can't access recovery.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?

the_rooter said:
I do use a usb otg stick and usually wipe the entire phone before each rom to make sure I start fresh. After I wipe everything in twrp i go to reboot back into recovery and it brings up the no os are u sure u want to do this. This wont cause issues even if unchecked correct?
Click to expand...
Click to collapse
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app

Konfuzion said:
No you won't have any issues doing that. If you want to be safe though you should check oem unlock before you start flashing and wiping. We all know flashing doesn't always go as expected and the last thing you want is to end up stuck. As long as oem unlocked is checked recovering from soft bricks is easy.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Like I said after a reboot it goes unchecked so if i check it and then reboot to recovery wouldnt that uncheck it again?

Why Are There So Many Bricked Nexi?

Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?

JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop

jiv101 said:
I believe they are relocking the bootloader, and then not being able to unlock again causing it to bootloop
Click to expand...
Click to collapse
There are two separete issues. One is what you're describing, and one is the device just completely dying - "you can't even get to fastboot". The first one has thread here, as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no cause :/

JulesJam said:
Is it because people are trying to downgrade their bootloaders? In general, you should never do that on a motorola phone although sometimes you can get away with it.
Or is it because people are messing around with their phones without unlocking the bootloaders?
Click to expand...
Click to collapse
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app

Tasssadar said:
as for the second one, there really isn't a comprehensive thread yet. I'm not even sure what is causing it anymore, at first I thought the bootloader doesn't like being downgraded (which you can do accidentally very easily, since CM ZIPs contain bootloader, for some reason), but there are people reporting bricked devices with pretty much no no cause :/
Click to expand...
Click to collapse
Are they sure of what bootloader versions they had?
I know this is a Nexus device but it has a Motorola bootloader. It is safest not to downgrade the bootloader OR the partition table from my experience with the Moto X. I know there were some exceptions and that is how jcase was able to get root on at least one bootloader version, but the general rule was don't try to downgrade the bootloader or the partition table to stay out of trouble.
I was thinking of making a post on General with this advice in it for people to help them stay out of trouble:
1) know your bootloader and partition table versions before you flash anything and if you aren't sure what will happen, do not attempt to downgrade either the bootloader or the partition table; and
2) make sure OEM unlock and USB debugging are enabled before you flash anything.
I understand that the advice above may be overkill for those who know what they are doing, but clearly people who don't know what they are doing are bricking their devices. I feel bad for them and don't want to see more people in that situation.

I was bricked by CM. Last nexus I had with cm was galaxy nexus so I don't know how cm is done on nexus 5 but why do they reflash bootloader and radios on each update. It wasn't that way before. Thats what bricked my device. I just got confirmation that I'm getting my replacement device.

akellar said:
This is a Nexus phone made by motorola, not a Motorola phone. Big difference.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Still a Motorola bootloader

rootSU said:
Still a Motorola bootloader
Click to expand...
Click to collapse
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app

akellar said:
Not in the manner that is being discussed. It can't be downgraded because of the new security implemented in 5.1, not because moto is involved.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Fair enough

[Q] Best way to get off of 5.1 LMY47D?

Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!

you can always use fastboot to go back to 5.0.1

stas333 said:
you can always use fastboot to go back to 5.0.1
Click to expand...
Click to collapse
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?

i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.

simms22 said:
i flashed 5.0.2 roms after flashing a 5.1 rom, and my device isnt bricked.
Click to expand...
Click to collapse
Hmm, I guess I am confused as to what is causing the bricks for those that downgraded? I'll go ahead and do that right now but... I've read direct quotes from others stating that downgrading a Motorola bootloader is an instant brick and others have said it has happened to them.

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.

gee2012 said:
Unlock your bootloader and enable oem-unlock in developer options and you can flash any image in fastboot.
Click to expand...
Click to collapse
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.

EmperorX said:
Word, thanks!
Just curious then... how are all these people bricking by downgrading? Does the wugfresh toolkit not use the fastboot method to downgrade or something?
Click to expand...
Click to collapse
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
EmperorX said:
Thanks man, I think I will just wait for the M images to be posted... Any harm in relocking my bootloader after I get them installed? I've read that too... though, some people it works out for, others not so much.
Click to expand...
Click to collapse
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
Click to expand...
Click to collapse
I wasn't planning on it, just curious how all these people are bricking?

gee2012 said:
I wouldn`t advice a toolkit mate, use fastboot (android-sdk-tools). A lot quicker and safer imo because you have control over whats happening
---------- Post added at 06:09 PM ---------- Previous post was at 06:07 PM ----------
Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flashing anymore if an incident would occur.
Click to expand...
Click to collapse
Also, I will absolutely need to relock my bootloader per organizational policies.

EmperorX said:
I wasn't planning on it, just curious how all these people are bricking?
Click to expand...
Click to collapse
Most of them because they wiped their system and couldn`t flash a image anymore because oem-unlock wasn`t enabled as i heard.

Sweet, successful downgrade!

I saw it mentioned in another thread that now that I have successfully downgraded I may brick when I get the T-Mobile 5.1 OTA.
Is there any credence to this? I am back on 5.0.1 now, relocked my bootloader, etc. Just wanted to make sure. It doesn't seem as if that would be the case to me but... Just wanted to be safe rather than sorry.
Thanks!

Disregard! Got it handled. Thanks guys!

Unlocking the bootloader makes no difference for receiving and installing OTA`s, make sure you always have oem-unlocking enabled because then you can`t flash anything anymore if an incident would occur and you`re without a OS.
Click to expand...
Click to collapse
Couldn't agree with you more....specially on the sentence I highlighted in bold. Got into the same problem yesterday. I excitedly upgraded from LMY47D to LMY47E. Later realised it's a Verizon image. So, thought let me go down to 5.0.1 and get a OTA - the "proper" way to upgrade.
While flashing, it didn't let me downgrade my bootloader. Mistake #1.
Then continued to flash the remaining images (radio, recovery, cache, system, userdata).
Then I locked my bootloader, so that it continues to look like "fresh out of the box". Mistake #2.
Then when I rebooted, it was constantly giving the error that NFC has failed and the Phone has failed. I couldn't get past those errors. It was continuously giving me that error.
It wouldn't let me unlock the bootloader, as the new bootloader (5.1) needs the OEM unlocking enabled in Developer's options.
Then I realised that there was a slight gap of time between showing the NFC & Phone error and the next set of NFC & Phone error. Using that, with great difficulty, setup the phone - going through every tap using the gap that was available between 2 sets of errors. Then I unlocked the developer's options, then enabled the OEM unlocking and finally got my bootloader unlocked.
Torrid - Horrible task. Was scared I had bricked my phone....but through some hard work (and sleepless night - up until 6am), got this finished.
Guys - seriously suggesting you NOT to lock the bootloader, IF you have unlocked the bootloader. Speaking with experience. Learn from my mistakes.
EDIT: I realised what the problem was and why NFC & Phone were erroring out. It was because I forgot to flash the Boot image. So, Bootloader & Boot were 5.1 & the rest were 5.0.1

EmperorX said:
Sweet, successful downgrade!
Click to expand...
Click to collapse
How did you downgraded the bootloader??

Downgrade of bootloader is not possible.
Sent from my Nexus 6 using XDA Free mobile app

EmperorX said:
Hey everyone, not quite sure what to do here, predicament is as follows:
I am on T-Mobile, phone is stock, bootloader locked, not rooted. This is the first phone that I have not wanted to root/tweak (been with Android since the HTC Hero). Anyhow, I sideloaded the LMY47D 5.1 build when it came out the other day... Now, I feel like I am stuck.
I'm reading various threads with contradictory information, but it seems that I can not downgrade from 5.1 to 5.0.1 because my phone will brick? That said, it sounds like there will NOT be an OTA from D (and maybe even E), so I will need to hopefully wait for M to go to the google factory images page...
When it comes down to it, I need my bootloader to be locked and phone unrooted after I figure out what to do here.
So... What is my best course of action? Is downgrading out of the question, because ideally i'd just downgrade to 5.0.1 right now and then wait for the OTA (and capture it if no has by that time!)? If not.. I guess I just need to wait and hope for M factory images.
Thanks!
Click to expand...
Click to collapse
How about you just leave it on D?
What do you think you will gain by changing to M?

root tool kit help

if i clicked flast stock and unroot, did that relock the bootloader and re-enable encryption?
im trying to sale the nexus

GreeleyXda said:
if i clicked flast stock and unroot, did that relock the bootloader and re-enable encryption?
im trying to sale the nexus
Click to expand...
Click to collapse
you should check, you have the phone, not me.

im not rly sure how to.
also while trying to prep, i deleted everything from twrp and now i dont have an OS it says.
any clues/help?

GreeleyXda said:
im not rly sure how to.
also while trying to prep, i deleted everything from twrp and now i dont have an OS it says.
any clues/help?
Click to expand...
Click to collapse
if you deleted your os, then you will have to flash the factory img if you want to sell the phone stock.
but you can always check your bootloader if its locked, by just booting to it. and in your security option in the main settings will tell you if you are encrypted or not.

simms22 said:
if you deleted your os, then you will have to flash the factory img if you want to sell the phone stock.
but you can always check your bootloader if its locked, by just booting to it. and in your security option in the main settings will tell you if you are encrypted or not.
Click to expand...
Click to collapse
clicked flash stock and unroot from sofy bricked/bootlooped on the tool kit
it got my phone up.
then i clicked oem unlock.
what else do i need to check?

GreeleyXda said:
clicked flash stock and unroot from sofy bricked/bootlooped on the tool kit
it got my phone up.
then i clicked oem unlock.
what else do i need to check?
Click to expand...
Click to collapse
using a toolkit, im clueless.

Well whatever you do do not re lock it. I do not know what toolkit you're using but he should be able to flash a system image.
if you relock the boot loader it doesn't matter if you were using a tool or not you may have screwed yourself .
Sent from my Benzo'd Google N6 on VZ

simms22 said:
using a toolkit, im clueless.
Click to expand...
Click to collapse
wuggfresg nexus root tool kit

DebianDog said:
Well whatever you do do not re lock it. I do not know what toolkit you're using but he should be able to flash a system image.
if you relock the boot loader it doesn't matter if you were using a tool or not you may have screwed yourself .
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
why did i screw myself?
im on 5.0.0 now btw

Can you load recovery? You are very vague in your descriptions of the status of the phone .
Sent from my Benzo'd Google N6 on VZ
---------- Post added at 06:11 PM ---------- Previous post was at 05:58 PM ----------
If you relocked your boot loader and cannot boot recovery I am not sure I can help you recover your phone
Sent from my Benzo'd Google N6 on VZ

DebianDog said:
Can you load recovery? You are very vague in your descriptions of the status of the phone .
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
no i cant theres a red triangle sign when i try.
but the device is locked, unrooted on stock 5.0.0, and encrypted. everything wiped
dont i need twrp installed to get to recovery?
im confused, did i not re add something when i reinstalled the stock os?

GreeleyXda said:
no i cant theres a red sign on the adroid when i try.
but the device is locked, unrooted on stock 5.0.0, and encrypted. everything wiped
dont i need twrp installed to get to recovery?
Click to expand...
Click to collapse
nope. that one, with the android lating down, is the stock recovery. sounds as its where you should be. did you check if the bootloader is locked?

If you did relock your bootloader and do not have an alternate recovery aka TWRP that you can boot then you have screwed yourself.
However if you can boot to bootloader
fastboot format userdata
fastboot format cache
Get into TWRP you could flash a zip or backup and be back in business
Sent from my Benzo'd Google N6 on VZ

DebianDog said:
If you did relock your bootloader and do not have an alternate recovery aka TWRP that you can boot then you have screwed yourself.
However if you can boot to bootloader
fastboot format userdata
fastboot format cache
Get into TWRP you could flash a zip or backup and be back in business
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
which one is the bootloader again?
i get go AP Flashboot Flash mode. is that it?
it says deviced locked on that screen
simms22 said:
nope. that one, with the android lating down, is the stock recovery. sounds as its where you should be. did you check if the bootloader is locked?
Click to expand...
Click to collapse
i think it is

update, i found out when the red triange is there im suppouse to hold power and click the vol + button.
i got into recovery mode. now what?

GreeleyXda said:
update, i found out when the red triange is there im suppouse to hold power and click the vol + button.
i got into recovery mode. now what?
Click to expand...
Click to collapse
yup, thats stock recovery. if your bootloader is locked, then youre good. well, after you delete whats in your storage
---------- Post added at 06:42 PM ---------- Previous post was at 06:40 PM ----------
@DebianDog thank you for trying to help, even though that wasnt his issue

Toolkit + inexperienced user = expensive paperweight.
Yet we, the "traditionalists" are repeatedly scorned for being negative about toolkits.

Running command lines willy-nilly or clicking buttons on a toolkit. doesn't matter - inexperience is inexperience
Sent from my Benzo'd Google N6 on VZ

simms22 said:
yup, thats stock recovery. if your bootloader is locked, then youre good. well, after you delete whats in your storage
Click to expand...
Click to collapse
sorry haha i never got a handle on all this, im used to locked samsung devices (verizon)
wipe data/factory reset in Cust Recovery should take care of deleting everything right? (although i alrdy had wiped every option in twrp which is why my os was gone)
also on swappa it asks if its carrier unlocked and rooted (has the device been rooted)
its direct from motorolla, so idk if that counts as a yes
and im assuming they mean is the device currently rooted?

DebianDog said:
Running command lines willy-nilly or clicking buttons on a toolkit. doesn't matter - inexperience is inexperience
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
True and I regret leaving the comment I did but it had to be said.

Root without unlock bootloader?

I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA after bootloader unlock?
Sent from my A0001 using XDA Premium 4 mobile app

aungkhaingoo said:
I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
you cant root your device without unlocking the bootloader. to root, you need to flash a custom recovery, then flash the supersu.zip file. none of which tou can do with a locked bootloader. in order to flash a custom recovery, you need to unlick the bootloader. and you will get an ota with root, but you cant apply it, so its pointless.

aungkhaingoo said:
I am a newbie for nexus lineup. I am going to jump to N6 from oneplus one. As far as i know from search, every post says N6 can only root after unlock bootloader. So i just want to know can i root without unlock bootloader? And is it possible to get update OS from OTA after bootloader unlock?
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You may be able to do this by using chainfire's autoroot tool. But why the reluctance to unlock? It's not difficult. Unlocked bootloader has no effect on accepting OTA. On the other hand, root will prevent you from accepting OTA. It's easy to fastboot flash back to stock when a new OTA becomes available. And it's even easier to download the Google factory images and fastboot flash them. Plenty of "how to" threads on the general section.
With that said, the only reason I can see for not unlocking your bootloader would be if your employer has restrictions, or your are really worried about someone stealing your device and getting your personal information.
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
simms22 said:
you cant root your device without unlocking the bootloader. to root, you need to flash a custom recovery, then flash the supersu.zip file. none of which tou can do with a locked bootloader. in order to flash a custom recovery, you need to unlick the bootloader. and you will get an ota with root, but you cant apply it, so its pointless.
Click to expand...
Click to collapse
I seem to be walking in your footsteps today. Sorry about that.

cam30era said:
You may be able to do this by using chainfire's autoroot tool. But why the reluctance to unlock? It's not difficult. Unlocked bootloader has no effect on accepting OTA. On the other hand, root will prevent you from accepting OTA. It's easy to fastboot flash back to stock when a new OTA becomes available. And it's even easier to download the Google factory images and fastboot flash them. Plenty of "how to" threads on the general section.
With that said, the only reason I can see for not unlocking your bootloader would be if your employer has restrictions, or your are really worried about someone stealing your device and getting your personal information.
---------- Post added at 12:16 PM ---------- Previous post was at 12:16 PM ----------
I seem to be walking in your footsteps today. Sorry about that.
Click to expand...
Click to collapse
na, thats ok, even great! im just bored at work at the moment, lol