Related
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
what exactly is happening when you try and unlock the bootloader?
xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
Is urs the AT&T One? Then the bootloader unlock process is different. If urs is the standard international SIM unlocked, then ideally you should see a splash after you run the bootloader unlock command, which prompts you to unlock the bootloader. Please state what exactly ur issue is when u try to bootloader unlock
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
xxshererxx said:
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
Click to expand...
Click to collapse
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
http://rumrunner.us/downloads-2/
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
raghav kapur said:
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
Click to expand...
Click to collapse
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
xxshererxx said:
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
Click to expand...
Click to collapse
I think you'll find more help here: http://forum.xda-developers.com/verizon-htc-one
Hello.
Im abit new to the forum but here goes.
Ive read tons of posts everywhere and there aint any exact answers anywhere to find.
In the past ive never known about the TA and DRM so happy as i am i just unlocked the bootloader on all the phones and still happy. The latest phone is the Xperia Z1. It has been abit buggy to say the least but im hoping software updates will cure this.
Anyway, i rooted my phone and unlocked the bootloader on the .681 firmware and now i am on .757 firmware. Using Doomlords kernel. I thought id check if i could backup my TA partition after unlocking the bootloader. And from what ive read its suppose to be wiped when you unlock the bootloader.
Well it was no problem backing up the TA partion. All files were there and it came out with no errors. So the question, how is this possible ?
I posted this same thing in General, sorry for that but i posted it here now so if a moderator finds this post in general then please delete it.
/Jonas740
If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.
eclyptos said:
If you Unlocked your Bootloader without Backup TA (DRM keys) first, then your DRM Keys are lost forever and you can Backup TA how much you want but there is no DRM Keys at all. The application to Backup TA do not give errors because you can backup partitions with or without DRM Keys, in the case you want switch between Locked and Unlocked Bootloader.
So long story short, you don't have DRM Keys, your warranty is lost forever, you cannot Update via OTA,PC Companion or SUS.
Click to expand...
Click to collapse
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app
well.
HellRoot said:
The one time I had to use my warranty there was no problem with missing TA.
So there is hope for people without it
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce
Jonas740 said:
dunno if the previous author saw what i wrote in my post but when i relocked my Xperia V using flashtool i could update with the pc companion or sony update or whats it called nowdays
And funny thing is, i actually have a case at Sony about this phone since i do have some issues with it but i think thats software related since ppl have been getting all sorts of errors from the KitKat firmwares. But i said how it was that i have unlocked bootloader and all that and she replied that my warranty was still valid and i could send it in for them to test it.
And i need to say this. Since sony posts an official way on their webpage, for ANYONE to read about how to unlock the bootloader and they also supply the code for unlocking it. Then i think it shouldnt affect the phone in any way or brake the warranty. (Sure it does say something about that, but all aint reading stuff like that). So if a developer wanted to unlock the phone. Why not have them contacting sony instead.
And surley, DRM keys (i just think sony shouldnt even bother having them) can be put back in if you let Sony do it. They put it there in the first place you know. And in the lovely electronic world we live in we all know that, if Sony can put thoose there, anyone could do it with the knowhow. But since the keys dont really mean anything, not that ive noticed you could really think about what use they actually do. And Sony knows that if ppl cant have the phone it was meant to be even with a unlocked bootloader, they will probably get some other phone or just whine hard enough so that Sony makes a software where everything works the same way with locked or unlocked. Camera stopped to work if you unlocked before 4.3 right ? What can you read about that like everywhere ? Loads of whining and Sony released a software that works just as good with locked or unlocked.
God damn this became a long post. So with this said im just saying. Why even bother in the first place having DRM keys if the rules dont apply anyway ? An everyday user doesent even need them either, he or she doesent even know what rooting or unlocking is anyway. And the ones that do know about it, also know about how to whine to get sony to fix the errors wich an unlock will produce
Click to expand...
Click to collapse
closed for being a duplicate.
use this link for other thread.
http://forum.xda-developers.com/showthread.php?t=2730169
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
bravept said:
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
Click to expand...
Click to collapse
first of all (search for doing this !! )
take a TA partition backup and then unlock your bootloader .....then install the recoveries on the stock ROM>>then replay to me after that
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
bravept said:
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
Click to expand...
Click to collapse
I think unlocking your bootloader resets everything so backup your apps for re installation once your are done.
I unlocked my bootloader the good old fashioned way via fastboot :
1 - Check if unlocking possible by typing *#*#7378423#*#* in the dialer and going into Service info > Configuration.
2 - If it says something like Bootloader unlock allowed - Yes then its unlockable. If its already unlocked, it will say something along those line as well.
If neither option appears then it isn't unlockable.
3 - Get the unlock code from Sony after filling the necessary details along with the IMEI no. of the phone.
3 - Open command prompt in the adb & flashboot folder by holding Shift + right click and selecting the "open command window here" option.
4 - Type fastboot.exe -i 0x0fce getvar version to check if device is connected properly.
5 - Type fastboot.exe -i 0x0fce oem unlock 0xKEY. Repalce KEY with the code that was received from Sony and hit Enter.
Alternatively the BLU option in FlashTool can be used to simplify things as it automates most of the above procedure. It can also be used to relock your bootloader.
There's also a new app called Kingo SONY Bootloader Unlock that apparently unlocks your bootloader with one click. Check it out.
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
bravept said:
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
Click to expand...
Click to collapse
If it says no then dunno what the chances of success are.
Came across this Youtube tutorial : https://www.youtube.com/watch?v=Li8Eim6gugw
Don't know how legit it is since its been posted a few months back and there are no comments at all so please proceed with caution and of course don't blame me if you brick your device
Also did you try the Kingo unlock app I mentioned?
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Just install some 4.4.4 lbl build, for example cm11 by mateo337 is really good and even up-to-date.
You will not be able to unlock the boot loader i had XSP that said no and i was not able to do anything about it.
Dont use 5.x.x builds, they are really outdated and have a lot of bugs.
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
bravept said:
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Click to expand...
Click to collapse
No you should still be able to enter fastboot mode. Are you using the latest version of FlashTool and have you installed all 3 required drivers? Does your phone show up in device manager when you connect it in fast boot mode?
I am not sure abt the last 2 procedures I posted but the first 2 require your phone to boot into fastboot and stay there till the job's done.
bravept said:
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
Click to expand...
Click to collapse
Yeah. Since your phone's rooted now, you can follow a LBL procedure for flashing a custom recovery to allow you to install custom ROMs.
Sent from my Xperia SP using XDA Free mobile app
Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan
Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.