I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
gmermel said:
I am on VZW. My phone status was "UNLOCKED" upon arrival from Moto. Since then, I found that the status has changed to "LOCKED". The status has not changed back to "UNLOCKED" after a factory reset. I have neither unlocked the bootloader or rooted.
Does the status refer to the bootloader, or did my phone lock to the carrier. Either way, is there a way to return the status to "UNLOCKED"?
Click to expand...
Click to collapse
Are you talking about the status in the bootloader?
If you want to unlock your bootloader there are a few guides on here to show you how.
skaforey said:
Are you talking about the status in the bootloader?
Click to expand...
Click to collapse
I am on the recovery screen itself. Before moving to the bootloader screen.
gmermel said:
I am on the recovery screen itself. Before moving to the bootloader screen.
Click to expand...
Click to collapse
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
rootSU said:
Bootloader comes before recovery. The screen where you pick to boot to recovery, is the bootloader. Is this where you mean?
Click to expand...
Click to collapse
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
well, when verizon finally releases, it might be sim locked. but you bought from motorola directly, and wont be sim locked to verizon, ever.
gmermel said:
Then yes, the bootloader screen.........
Does that mean my phone is still not locked to VZW?
I guess now you know WHY I haven't rooted.
Click to expand...
Click to collapse
The phone shouldn't have come unlocked from the factory. I suggest you backup your data and oem unlock the phone.
How do do an oem unlock?
gmermel said:
How do do an oem unlock?
Click to expand...
Click to collapse
Using fastboot commands you type fastboot OEM unlock to unlock your bootloader. This will wipe all of your data so you should back up anything you don't want to lose.
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
simms22 said:
not really. the right way is the easiest way, and you learn along the way. using a toolkit, you will learn nothing, not even the basics. the right way to do it takes about 3-5 minutes..
1. fasdtboot oem unlock(this unlocks the bootloader)
2. fastboot flash a custom recovery
3. flash supersu in your new recovery
4. reboot with root.
Click to expand...
Click to collapse
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
encephalon9986 said:
Just because I am using the toolkit doesn't mean I don't know the basics. I've been modding phones since the droid x days and before android I had windows mobile. I just prefer the simplicity of toolkits. Wugfresh does an excellent job making this program. I agree knowing the basics is a good thing because you should know what needs to be done for this all to happen but then again toolkit is very simple.
Click to expand...
Click to collapse
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
simms22 said:
who said anything about YOU? if you know what you are doing already, use a toolkit, i dont care. but if you are new to this, toolkits are not for beginners. simply because they dont teach anything, nor do you learn any of the basics.
Click to expand...
Click to collapse
Very true I agree. Learning the actual way is the best to learn. Sometimes I like using the cmd because its more fun doing it yourself. Either way works but remember mod at your own risk (for the op).
encephalon9986 said:
This is the easiest way to get everything done from unlocking and putting a custom recovery. This will also help you if you need to go back to stock for any reason.
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
gmermel said:
Are there Mac tools as powerful and straightforward as Wugfresh?
I rooted my N7 using this tool. Simple for even me. However, that was when I had bootcamp on my Mac and could use Windows.
I use Apex launcher and am happy working in stock. The feature I miss is being able to use Titanium/TWRP for recovery. I have learned how to rebuild my system easily via file transfer, and using Terminal to root the phone isn't worth the down-side risks to me.
Click to expand...
Click to collapse
You can use fastboot on a Mac. Its even easier than windows. If you don't know how to use fastboot, if you've been reading the thread, we're saying do not use a toolkit.
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.
rootSU;58263052
Do you even need an unlocked bootloader? I don't think it came unlocked from the factory.[/QUOTE said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
gmermel said:
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
what is fastboot? http://www.androidcentral.com/android-z-what-fastboot
download fastboot for Mac http://www.androidcentral.com/sites/androidcentral.com/files/uploads/tools/fastboot-mac.zip
gmermel said:
Probably not. I was more interested in whether the "lock" referred to the phone/SIM. As long as that's not an issue I'm good.
However, in the spirit of the flow, I would like to learn to root on my Mac for its own sake. That being said, I'm not confident that I understand the various how-to's I've read to give it a go. As I mentioned, I don't want to play in Terminal, and I've never heard of "fastboot" as it relates to the Mac. If, however, the fastboot you are speaking of is the one on the phone itself (not the Mac), my lack of knowledge should be self evident. At least I know enough to not go where I don't know enough........
Click to expand...
Click to collapse
You would have to use a terminal but its very simple.
A terminal just means you type stuff and press enter instead of clicking buttons.
Fastboot is on both the phone and the computer. From the computer there is a fastboot for windows, Linux and Mac. You simply install them and type the commands from terminal.
This is my nexus 5 thread. Everything is relevant except the windows USB driver section
http://forum.xda-developers.com/showthread.php?t=2807273
Related
So, I've upgraded my Nexus One with the OTA from Google and I've lost root, is it anyway to root my device again? I want my crack back!! preferably without unlocking the bootloader, something like universal androot, or z4 root (none of them work, at least market versions), thx for your answers
Rikarudo said:
So, I've upgraded my Nexus One with the OTA from Google and I've lost root, is it anyway to root my device again? I want my crack back!! preferably without unlocking the bootloader, something like universal androot, or z4 root (none of them work, at least market versions), thx for your answers
Click to expand...
Click to collapse
I guess the only way is to unlock the bootloader. Why do you want it locked anyways? I guess your warranty is long gone + HTC doesn't check the unlocked bootloader as far as i know.
After unlocking you can install a custom recovery and use su.zip ( its there in the android dev section ) and flash it.
siddharthsai said:
I guess the only way is to unlock the bootloader. Why do you want it locked anyways? I guess your warranty is long gone + HTC doesn't check the unlocked bootloader as far as i know.
After unlocking you can install a custom recovery and use su.zip ( its there in the android dev section ) and flash it.
Click to expand...
Click to collapse
In guess I'll havce to unlock my bootloader then but I havent done it before so im kind of scared, just find it way more complicated doing it that way that whit the mentioned exploits, like universal androot: click root, install room manager, enjoy
You're kidding right? It takes 30 seconds to unlock the bootloader, install a custom recovery, and another minute to install a custom ROM and reboot. I had mine done as soon as I took it out of the shipping box.
YOU DO NOT HAVE TO UNLOCK THE BOOTLOADER. All you have to do is roll back to a build of Froyo. Search for PASSIMG.zip. Apply that through the bootloader. Then you can root using Super One Click or any of the other methods and flash a rooted GB ROM.
Know-Fear said:
You're kidding right? It takes 30 seconds to unlock the bootloader, install a custom recovery, and another minute to install a custom ROM and reboot. I had mine done as soon as I took it out of the shipping box.
Click to expand...
Click to collapse
..But an hour to learn about and set up the SDK first Once done though it makes life sooo much easier and gives you a lot more versatility.
DirkGently1 said:
..But an hour to learn about and set up the SDK first Once done though it makes life sooo much easier and gives you a lot more versatility.
Click to expand...
Click to collapse
That.
An hour might be more or less - depends on a user.
uansari1 said:
YOU DO NOT HAVE TO UNLOCK THE BOOTLOADER. All you have to do is roll back to a build of Froyo. Search for PASSIMG.zip. Apply that through the bootloader. Then you can root using Super One Click or any of the other methods and flash a rooted GB ROM.
Click to expand...
Click to collapse
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Jack_R1 said:
That.
An hour might be more or less - depends on a user.
Click to expand...
Click to collapse
I think I can make it in less than an hour, lol, anyway, i just wanted to root again because i thought that after OTA the call wonkyness in CM7 got fixed, but it seems is still there, so I'll stay with official GB for a while or untill my abstinence syndrom comes back, and in that case ill try with passimg method just becuase it is a pain in the a55 to setup the SDK (I've done it before, too much data to download and Im currently reliying in thetering to have internet at home).Thnx for your answers.
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
The only benefit is aesthetics, if it really matters to you. I don't much care for the lockscreen, lol. Aside from that, you're right..unlocking the bootloader isn't any worse. It's just personal preference. My point is that you never HAVE to unlock the bootloader.
Unlock Icon
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
To not have a ****ing unlock padlock
Also I don't like thing the easy way. I like "flash_image" instead of "bootloader"'s way of flashing images.
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
OMG!! Don't even mention it!! I can't stand open padlocks!!! they make me feel dirty!! like I have to wash my hands 20 times! LOL.
Seriously, I don't know, I just find it easier with exploits.
Having the bootloader unlocked is the easiest way to do anything.
Sent from my Nexus One using XDA App
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
MitchRapp said:
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
Click to expand...
Click to collapse
Gingerbreak... when it's released.
MitchRapp said:
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
Click to expand...
Click to collapse
It's already been stated, use PASSIMG.zip method to downgrade to 2.2 or whatever you'd like then root. There is currently no way to root a 2.3.3 ROM with any sort of 1 click.
There is, but it's not 1-click - having unlocked bootloader allows you to flash SU and change permissions accordingly.
Those demanding 1-click will have to wait until there is any 1-click solution - and this might take time.
I just tried unlocking my bootloader but it says I'm missing AdbWinApi.dll ... I have it though. I've used the SDK for rooting before without any errors like this. Must be my day...
http://forum.xda-developers.com/showthread.php?t=781386
If you upgraded a rooted device - you can also try the "RErooting guide", in one of the threads where you've asked if it's wiping the whole device. It doesn't. But it might not work without unlocked bootloader - I'm not sure that locked fastboot allows you to boot non-stock, even to memory using "fastboot boot" command. If it does - it's a rooting option completely overlooked until now.
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
I am at this same point. How did you fix it?
chris23445 said:
I am on my. Way to return the phone to best buy. I was rooted and with an unlocked bootloader and had TWRP. I used the Nexus Toolkit and relocked the phone before flashing stock and now it won't boot. It just shows the team win logo flashing over and over. Please please help as they close in 30 minutes. Also it isn't detected in adb or fast boot.
EDIT: fixed it!
Click to expand...
Click to collapse
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
ADB is your friend!
TheAnarchist1 said:
I am at this same point. How did you fix it?
Click to expand...
Click to collapse
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
radicalisto said:
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Boot loops
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
Or, the moral is follow the toolkit developer's directions.......
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
Yep. That/don't rush when resetting the phone and do it in the wrong order.
aiiee said:
Or, the moral is follow the toolkit developer's directions.......
Click to expand...
Click to collapse
No, it isn't because...
chris23445 said:
I had to figure it all out as I went because I couldn't figure it out online lol.
Click to expand...
Click to collapse
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
rootSU said:
No, it isn't because...
but if a toolkit had never been used in the first place, there would be nothing to figure out as it would all have been learned in the rooting process.
Click to expand...
Click to collapse
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
Thus proving my point.
radicalisto said:
Going to assume he managed to Re-flash factory images.
Moral of this story is don't use toolkits and learn how to recover from bootloops and read about potential problems that could arise.
Click to expand...
Click to collapse
rootSU said:
Thus proving my point.
Click to expand...
Click to collapse
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
aiiee said:
Not in the slightest . Your logic is skewed. Good luck with that.
Click to expand...
Click to collapse
How is it skewed? If, when he first got his phone, he unlocked and rooted in the normal way and not used a toolkit. He would have known how to use fastboot, including how to flash stock and lock the boot loader. He would not have used a toolkit today and wouldn't have used the wrong order and this thread wouldn't exist.
If you're an advocate for the cheat way and the way that makes it harder for us to help people, so be it. But 95%.of us prefer users to learn things properly and not become a burden to the forum. But you can help them all. Good luck with that.
chris23445 said:
No lol I would have completely been screwed without the toolkit. All that happened was I did the steps wrong and I have no idea how to unlock the bootloader and relock it and root with adb and the toolkit was easier for me. I could have googled the adb thing but it would have been much more of a hassle.
Click to expand...
Click to collapse
how to properly root.
1. run the command "fastboot oem unlock" in fastboot. this unlocks your bootloader.
2. flash a custom recovery via fastboot.
3. flash the latest supersu in your new recovery.
4. reboot with root.
5. woohoo!
this takes about 3-5 minutes.
aiiee said:
Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
Adb is absolutely nothing to do with any of this. Another misconception of toolkit users. Which again, proves my point.
aiiee said:
Not in the slightest . Your analysis is flawed. You assume this problem was caused by not understanding the underlying structure but it wasn't. It was caused by failing to follow directions. Which would have caused him problems had he used ADB or not.
Click to expand...
Click to collapse
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
simms22 said:
you dont use adb to root. nor will adb work while you are in the bootloader. fastboot is what you use
Click to expand...
Click to collapse
You can use adb. Fastboot is used for the oem i lock and recovery flash. If you want to put the supersu file on the phone without downloading it on the phone you can just adb push and flash in recovery. Done.
Thanks
chris23445 said:
Hold the power and volume down button until it boots into recovery. Then plug the phone into your computer. Download the stock 5.0.1 zip (luckily I already had it downloaded). Use the toolkit and unlock the bootloader. It will say its successful but the phone will boot loop again. Boot into recovery and should say the bootloader is unlocked. Then flash the stock zip file and it should work! I had to figure it all out as I went because I couldn't figure it out online lol.
To be fair, I was in a huge rush and relocked the bootloader before flashing stock. Totally a user error and not a toolkit error.
Click to expand...
Click to collapse
Thanks for the clear explanation.:good:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
TheAnarchist1 said:
@rootSU
For those curious. I figured I would check back in with this thread. I did not use a toolkit to begin with. I have the sdk properly set up and know my fastboot and adb commands and the difference between both. What I did:
1. Fastboot oem unlock
2. Fastboot flash recovery recovery.img (it was twrp)
3. Booted into recovery and it would not let me access the recovery, just kept flashing the TWRP splash over and over and over.
The issue I think for me, was that I did not wait until the Nexus had wiped itself and booted back into Android to rebuild the file system. Hence TWRP farting out. I simply started from scratch again, flashed all the proper stuff that was needed and followed steps, and I was alright after that.
I have since returned the device though and exchanged it with a new Nexus 6, because my back cover had started to pop up in the top right corner above the power and volume buttons....but THAT is another story for another thread : p
Cheers all!
PS: It has been a while since I have owned a Nexus device, hence my own failure to follow the rules. Things have changed a bit with this Nexus it seems, and it was my fault. I am all good now though (or I will be after I set up this new Nexus 6)
PSS: No toolkits were used, or will ever be used in the creation and resolution of this debacle. My life is hard enough without blindly wandering through the forest of Android customization with my hand held by a complete stranger.
: p
Click to expand...
Click to collapse
after fastboot oem unlock, you have to reboot once before flashing the recovery. rarely it doesnt stick, so you just flash it again if nothing appears
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
droidstyle said:
if your bootloader is unlocked you should be able to fastboot clear cache and user data , then flash a rom from twrp. I would refrain from ever locking the bootloader back up since the update where you have to enable unlock bootloader in Dev Options.
Click to expand...
Click to collapse
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
hadifreestyler said:
me too I'm have Nexus 6 5.1.1 no recovery...except the bootloader that's locked Code: 2 , i can't unlock it, any solution !!?
Click to expand...
Click to collapse
no you are bricked unfortunately. the unlock bootlader option in dev options really seems to have caused more issues then good.
I am wondering if Jtag will fix these devices?
jpl81905 said:
Suggestions?
Click to expand...
Click to collapse
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
scryan said:
Stop.
Read.
A lot.
You have an unlocked nexus with custom recovery installed, and you don't know what to do? You shouldn't be messing with this stuff. You lack VERY basic understanding. Read the stickies.
https://developers.google.com/android/nexus/images?hl=en
Factory images. Follow their directions.
Click to expand...
Click to collapse
Thank you. I think.
jpl81905 said:
Hi guys -
I'm somewhat a newbie here. I think I have bricked my Nexus 6. I had root and an unlocked bootloader. I had Chroma riom installed and was trying to go back to stock rom, unrooted with locked bootloader and through TWRP i deleted everything, including the OS I believe. So now my phone is locked on the Google startup screen (unlocked bootloader) . Suggestions?
Thanks -
John
Click to expand...
Click to collapse
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
backdown00 said:
The easiest way if you are not familiar with ADB is to download the nexus tool kit located on these forums from WUGFRESH. That tool will walk you through a step by step process on how to flash stock back. You are far from bricked. I have deleted my entire phone many a times and just re flashed stock back easily. As long as your boot loader is unlocked you are fine
Link to toolkit: http://www.wugfresh.com/nrt/
The option you are going to want to use is on the front of the toolkit called flash stock + un-root. You can watch some videos on his website as well for flashing stock. That is all you need to do .
Any questions let me know, send me a PM
Click to expand...
Click to collapse
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
danarama said:
It is not the easiest option. The easiest option is plug the USB cable in, boot to TWRP, enable MTP mode and copy a rom to the sdcard.
Also, many senior members here will discourage the use of toolkits for those who are not familiar with adb or fastboot. It is best to learn these and use them at least once before starting to use toolkits. Toolkits do not "walk you through". They take you through without explaining anything.
Click to expand...
Click to collapse
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
backdown00 said:
In a perfect world, I am sure we would all love to dive in and discover everything and be experts in all fields as time would not be a factor. I do not disagree it is helpful to learn ADB and fastboot commands and understand what they do. At this point in time though, the end goal here is to get his phone back up and running as fast as possible and then he can do the post-mortem to figure out what he did wrong and how to fix it .
I am guessing hes not very familiar with TWRP since he wound up in this situation. The toolkit alleviates the need for knowledge and gets the job done. I'm sure after this, the OP will research how to use his phone before trying to do anything next.
Click to expand...
Click to collapse
..but even so, your method is overkill. It is really simple to boot into TWRP and look in the menu for the "Enable MTP" option. Once that is done, the phone appears in "Computer" as an MTP device, just like when you boot into android. Then, simply dragging and dropping a ROM onto that device then flashing it via recovery will get him back up and running. There is nothing simpler or quicker than this.
Sorry, I do not intend to be confrontational here.
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
TPADroid said:
Hi Everyone
I have recently returned my Nexus 6 back to stock from Rooted 5.1.X roms by manually flashing the official google Marshmallow images. Now that 6.0 Roms are making their way out, I would like to get back to having the ability to flash the different roms. However, I am a little confused on how to successfully and easily accomplish the root and TWRP install process. I see that some of the new 6.0 ROMS say they are rooted, but I am confused on what that means.
Does anyone have a link or steps with links that you can provide so I can get my Nexus 6 ready to have custom roms flashed?
Thanks in advance!
Click to expand...
Click to collapse
First this does not belong in the Development sections, moved here. Secondly please read the Forum Rules on posting...thanks.
Thank you for moving to the appropriate location.
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
simms22 said:
as it is for every nexus, regardless of what android version youre on..
1. unlock your bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu in twrp recovery
4. reboot with root
on marshmallow, with the stock rom, you will also want to flash a custom kernel with as well.
Click to expand...
Click to collapse
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
The boot.img files that your referring to are probably to un-encrypt your phone. I personally don't but other always have. Supposed to make it faster although i haven't been bothered by it being slow.
To unlock the bootloader all you have to do is used fastboot oem unlock via fastboot while your phone is in the bootloader mode.
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
mbiscuits said:
You don't need a custom kernel anymore thanks to Chainfire. Just use the Nexus root kit. Be sure to change the root settings in the NRK to approve beta SuperSu by Chainfire as stated in wugfresh Google+ post in step 3.
plus.google.com/u/0/113329792100896065459/posts/93WR63UHuEp[
Click to expand...
Click to collapse
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
---------- Post added at 12:21 PM ---------- Previous post was at 12:20 PM ----------
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
thats a kernel thatll let you unencrypt, if you want.
simms22 said:
no more kernel then, cool. but this is not a good idea to tell a newbie to use a toolkit, as he wont learn a single thing about , ever. and root toolkits mess up on occasion. they mess up enough to make a newbie think they bricked their phone. sure, chances are that everything will be fine, but the op will come out of it learning absolutely nothing, when the proper way is very easy and faster.
Click to expand...
Click to collapse
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
mbiscuits said:
He did say easy and it doesn't get any easier than the toolkit. But if you want to do it manually follow the easy to read instructions found here: androidmarvel.com/index.php/2015/10/15/402/
Click to expand...
Click to collapse
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
mbiscuits said:
I agree with you IF you know what you are doing and have everything setup. However that didn't seem to be the case which is why I recommended the toolkit.
Click to expand...
Click to collapse
which is why i always recommend that someone new root their phone the proper way the first time, to learn how to do it, and to learn a general way to fix your phone in case you mess up. after the first time, use toolkits all you want. but the learning how to do it properly is a very important.
TPADroid said:
Thank you Simms
When you are referring to unlocking the bootloader, it seems pretty self explanatory, from the google search...but I have seen where there are new boot.img files to apply via adb....is this unlocking the bootloader in 6.0? Or am I making this more complicated than it really needs to be. It seems that most ROMS now have an embedded Kernel...so I would flash one immediately #3. The one ROM I would like to try first is Chroma on 6.0.
Getting TWRP installed, I completely get and every step after that one...its the modified boot.img files I have seen, that is confusing me.
Thanks!
Click to expand...
Click to collapse
That modified img allows for root because you cant just flash SU on the stock one (not yet anyway). Unlocking the bootloader is something different.
simms22 said:
sure, the manual way is MUCH easier than the toolkit. is it hard typing fastboot oem unlock? is it hard typing fastboot flash recovery recoveryname.img? well, thats it. i just unlocked my bootloader and flashed the recovery.
Click to expand...
Click to collapse
Anybody knows where is the correct toolkit?
cpugeeker said:
Anybody knows where is the correct toolkit?
Click to expand...
Click to collapse
in my opening, there is no 'correct" toolkit.
Jnewell05 said:
Well you need an unlocked bootloader and a custom recovery to flash custom roms.
1. Make sure that you have OEM unlock ticked in dev options
2. Use fastboot oem unlock command to unlock bootloader (this will wipe your phone completely, make a backup before doing this)
3. Use fastboot to flash twrp recovery
4. If you would like to keep stock rom and have root then you need to flash root script from chainfire or install custom rom with root already built in
5. Download and flash any rom of your choice (You can use adb sideload to sideload roms instead of having to copy them to the phone to flash)
Here is a good place to start to learn how http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
Click to expand...
Click to collapse
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
If you haven't rooted for over a year why do it now? There are sure to be updates to how to root on the Nexus 6 and since I don't use my nexus 6 very much I hate to steer you in the wrong direction, as to backup information. I recently got the android 7.0 update and I haven't really had a chance to check it out yet. But I bet there are dozens of ways to backup if you would search Google.
Sent from my SAMSUNG-SM-G935A using Tapatalk
jtmartin22 said:
Hey thanks for all of this information. So far I'm stuck on step 2. I'm about a year into owning this phone and don't want to lose everything. One of the main reasons I want to root is to use titanium backup. However, you say to be sure to back up your phone. How do you recommend doing this.
Click to expand...
Click to collapse
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
istperson said:
By unlocking the phone you lose everything. That's why when buying a Nexus phone, the first step should be unlocking the bootloader.
But if you want to root it anyway, then you should copy all your media and camera files to your computer. Then if you unlock it, you'll only lose some app settings. Most apps save to the cloud anyway. You can backup your text messages, and Google backups a lot of data like wallpapers or WiFi passwords. Also it will reinstall all your use apps, and since Marshmallow it will restore some app data, but that's far from consistent. For that you really need TB.
Click to expand...
Click to collapse
Thank you very much!!!!
Hey everyone I'm looking here as my last resort before sending my phone back to Motorola.
Bought a Nexus 6 from motorola uk which was delivered yesterday, switched phone on and all the Google apps on the phone updated, then had a notification OTA to download and install android 5.1 which I did, towards the end of the install process I had an error with the green android and a red exclamation mark.
I powered the device off with the power button and it turned back on and ever since it says "Android is starting" "Optimizing app 1 of 125" once it goes through all the apps it gets to the android boot screen then just goes back to the "Android is starting" "Optimizing app 1 of 125" over and over and over. (Infinite bootloop)
Pointers: The phone is not unlocked or rooted as I'm a noob its just fresh out the box, also I never opened/unlocked the developer options.
I have tried various recovery mode fixes, wiping cache and wiping all data and then rebooting the device with no luck.
Is there anyway I can hook my N6 up to my computer and fix this with a tool kit etc? I'm willing to try but I'd need basic instructions and reassurance it wouldn't muck up my warranty if it didn't work as my only other option is to exchange for a new device.
I'm a noob so I need detailed basic step by step instructions.
Any help, advice etc would be hugely appreciated. Thanks
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
ixon2001 said:
Just send it back, no point messing about with it if it brand new could down to a fault with the hardware itself.
Click to expand...
Click to collapse
Iv'e heard this is a common problem with the N6 whilst trying to update the OTA 5.1 I had no other apps on the phone it was fresh, I did nothing wrong, I know someone who has been through 4 devices with the same bloody issues! In the end he had to sideload 6.0 and I'm not confident in being able to do that.
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
ixon2001 said:
Well best bet is to download wugfresh toolkit 2.10 i think is the latest version, follow the instructions carefully because first you need to unlock the bootloader then flash 6.0.1 which has just come out.
Using Wugfresh is the best way to go if your new to flashing & you can't really go wrong with it.
Click to expand...
Click to collapse
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
gee2012 said:
I`am sure most xperienced users (me included) will not agree with you The best way to unlock, flash and root is still adb/fastboot. Especialy for lesser xperienced users that are lost is something goes wrong while using the toolkit, wich happens frequently btw. Just check the help threads.
Click to expand...
Click to collapse
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
ixon2001 said:
Lol it's not rocket science using adb, been doing that way for years but for somebody that never flashed, rooted ect I still think the toolkit best way to go at first because everything is done for you at a click of a button.
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
Lets agree to disagree
OK
ixon2001 said:
Yes things can go tits up when using toolkits, mainly because they don't follow simple instructions.
Click to expand...
Click to collapse
No, but because toolkits are always behind at least one version with marshmallow. People kept bricking their devices with toolkits when marshmallow came out and they thought they could root it. As 6.0.1 came out they'll do something else wrong.
Toolkits are not help. It's the lazy way if everything is already working and up to date.
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Sent from my Nexus 6 running cyosp using Tapatalk
istperson said:
N
Also what can a toolkit do if this phone doesn't even have developer options turned on? If it's in boot loop, as the OP said, then the Enable OEM unlocking was never set, then the only solution is to send it back. Unless there's a toolkit magic we don't know about.
Click to expand...
Click to collapse
I think op created another thread http://forum.xda-developers.com/nexus-6/help/nexus-6-stuck-bootloop-trying-to-update-t3266100 for this issue - and was somehow able to unlock the bootloader (not sure how that worked if OEM unlock was never set)
jj14 said:
(not sure how that worked if OEM unlock was never set)
Click to expand...
Click to collapse
It was said that some of the first Nexus 6s with the original 5.0 came out with a bootloader that didn't check for this switch.