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
Related
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
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
shahrukhraza said:
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
Click to expand...
Click to collapse
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Paddington said:
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Click to expand...
Click to collapse
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
shahrukhraza said:
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
Click to expand...
Click to collapse
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Paddington said:
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Click to expand...
Click to collapse
Yessir thanks for replying. However I now have a whole new problem. Do you have any suggestions for that? It is the post above^
shahrukhraza said:
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Click to expand...
Click to collapse
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
ewalk4866 said:
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
Bootloader as in vol. down + power button right? Thats not working too. I also tried other combinations to no luck. And before it was turning on but now its not even booting to the boot animation. Thanks for the link though, if it does magically boot into the bootloader then i'll know what to do at least.
Edit: Okay so theres the charging animation, so thats a start, I guess. Still no luck on the bootloader tho.
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
shahrukhraza said:
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
Click to expand...
Click to collapse
Yes that's right remember you only have to flash system
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Nah man that didnt mess it up, some other stupid thing did it lol. Nothing on you, rather thanks for the help.
ewalk4866 said:
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Click to expand...
Click to collapse
I agree that Toolkits can make you lazy and not learn how to fix things on your own, but when you need a quick fix and don't have time to figure out what is going wrong, it's always nice to just boot your phone into fastboot or recovery and fix things with a few keystrokes on your computer.
I got it to work guys! Thanks for all the help. It was much appreciated.
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
viper1402 said:
sorry if this has been covered but i cant find anything the same as my situation and im pretty stuck.
I have just bought a nexus 6 and the phone prompted me to update to 5.1 so i have, once it restarted i am now stuck in a boot loop with it saying optimizing apps then restarts and the same again, i have tried booting into recovery and wipe data but just get the same.
I have tried using nexus root toolkit (wugsfresh) however cannot find fastboot connectivity so im stuck there.
The phone is not rooted and i cant seem to get access through adb ( i have not turned usb debugging on as the phone is new)
I really am not too clued up so im sorry if i need things explaining abit more.
Thanks in advance
Click to expand...
Click to collapse
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
simms22 said:
flash a factory image, your update went no good. if you havent ever done this, i DO NOT RECOMMEND using a toolkit. toolkits are good for people who know what they are doing. if you dont kniw, you will remain clueless, and could make things much worse.
Click to expand...
Click to collapse
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
viper1402 said:
am i able to flash a factory image without being able to connect the device via adb? i just wasnt able to find the device on it
Thanks for the reply
Click to expand...
Click to collapse
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
simms22 said:
factory images are only flashed while youre in your bootloader, via fastboot. thetes a stick for directions in the general thread.
Click to expand...
Click to collapse
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
I'd suggest avoiding the OTA's and fastboot flash the latest factory image. LMY48I
IMHO....
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
is it worth it? YES! if you want, you can flaah the factory image for 5.1.1 instead of taking the ota. but chances are that the ota will be fine.
viper1402 said:
right got it sorted thanks for the help now its saying i have an update for 5.1.1 is it worth doing this or is there a strong chance it will bootloop again ?
Click to expand...
Click to collapse
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great ?
boxa72 said:
How did u get it sorted? I just had a friend call me with exactly the same problem! He's not very tech savvy so it's proving difficult talking him thru it, so if u found an easy solution for me to pass on that would be great
Click to expand...
Click to collapse
As stated before. Forget OTA. Unlock bootloader and fastboot flash the images manually. Do not take OTA with bootloader locked. If OTA fails have to RMA. No fix.
I had the same issue today and like PRDOG1 said I was talking to him on my forum post. As soon as you get the phone unlock that bootloader, then just do flashes through the bootloader. It is safer, and as long as that bootloader is unlocked you can go ahead and load up any image you want thats factory and you will be fine.
Well it should be fine then coz the carriers in Aussie don't lock bootloaders. I just told him to bring the phone to me n I'll re-flash a stock image for him but I thought u may have found another way as I'm more familiar with Samsung and Windows than I am with Nexus. It seems pretty common this bootloop stuff after OTA with the N6.
Sent from my SM-G920I using Tapatalk
I suspect you are confusing carrier SIM lock with bootloader lock.
Carriers do not usually do anything with bootloader lock - they may force a SIM lock to their SIM cards however.
On the Nexus 6 however, unlocking the bootloader is pretty easy (assuming you can boot to the OS and select the option to allow OEM unlock). I'd recommend leaving the bootloader unlocked and flashing twrp asap, in case of any issues later.
Altho in Australia they don't carrier lock bootloaders the software comes locked for security reasons. If he didn"t unlock prior to the OTA update it is bricked and will require RMA.
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.
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.