Question Unlocking the device using MiUnlockTool (First step) - Redmi Note 10 Pro

Good morning/evening,
I'd like to unlock my device using MiUnlockTool and I was wondering if it wipes the phone data ?
I've already done some researches but replies are mixed and pretty old, + since it's clearly saying "Unlock will erase data" I'm wondering if it's related to the "first" unlock, or the "true" one you're doing after waiting for 7 days.
I hope I gave enough information about my problem, thanks in advance !

It will erase your data while unlock process

code28h4p said:
It will erase your data while unlock process
Click to expand...
Click to collapse
That's what I thought then, thanks for replying.

Related

[Q] Bootloader unlocked factory reset

Hi,
Today I tried to unlock my bootloader on Xperia T, because I recently downloaded android 4.3. When the bootloader was unlocked, I tried rooting the cell through usb debug. But it didn't work, I decided to look at it tomorrow, or at a later point. But when I restarted my phone, it was been factory reset. Some of the photos were recovered, but ALL my notes are gone and a lot of apps are gone, I never chose to format my phone or anything.
Is there a fix for this issue?
Thanks in advance!
EDIT: my phone contacts seem unlinked from WhatsApp too... So the contacts are there, but WhatsApp doesn't recognise them.... I think the internal memory and the phone memory are corrupting each other
EDIT2: the contacts don't even seem to be there now, not even on Google, while I am 100% sure I saved the contacts to my Google account
I never heard of this issue before, but a bootloader unlock always factory resets the phone. Are you sure that your bootloader can be unlocked, and that it is still unlocked now? For unlock just follow the instructions on the official Sony page, they're clear enough.
I don't know a method for recovering data after factory reset, other than restoring your nandroid backup.
Sent from my LT30p using xda app-developers app
I am sure the bootloader unlock is possible, it might be that I unlocked the bootloader, while it was unlocked already. I don't know if this is the problem.
vonis22 said:
I am sure the bootloader unlock is possible, it might be that I unlocked the bootloader, while it was unlocked already. I don't know if this is the problem.
Click to expand...
Click to collapse
Did you unlock your bootloader before? If not, then it is still locked. However, the status now is a bit unsure Did you check in the service menu? ('call' *#*#7378429#*#* (*#*#SERVICE#*#*) and check Service Info -> Configuration -> Rooting Status, what does it say?)
Mad Marty said:
Did you unlock your bootloader before? If not, then it is still locked. However, the status now is a bit unsure Did you check in the service menu? ('call' *#*#7378429#*#* (*#*#SERVICE#*#*) and check Service Info -> Configuration -> Rooting Status, what does it say?)
Click to expand...
Click to collapse
Thanks for the reply, I did this, my phones bootloader is UNLOCKED, I was confused and did it again, so i double unlocked the bootloader, this seems to be the problem. Is there any way to get the data back?
vonis22 said:
Thanks for the reply, I did this, my phones bootloader is UNLOCKED, I was confused and did it again, so i double unlocked the bootloader, this seems to be the problem. Is there any way to get the data back?
Click to expand...
Click to collapse
Well, good to see your bootloader is indeed unlocked
If you didn't make any backups, there is almost no way to recover your data. The only thing I can think of is trying to recover something with data recovery software like Recuva (from Windows, not an Android app), but you should stop using your phone immediately, because if sectors on SD or internal storage are overwritten with new data it diminishes the chances of recovery of old data.
Now would be a good time to start backing up regularly, or at least before you start flashing roms, unlocking things, etc. There is a reason why we say 'always make a nandroid backup!' :angel:
Mad Marty said:
Well, good to see your bootloader is indeed unlocked
If you didn't make any backups, there is almost no way to recover your data. The only thing I can think of is trying to recover something with data recovery software like Recuva (from Windows, not an Android app), but you should stop using your phone immediately, because if sectors on SD or internal storage are overwritten with new data it diminishes the chances of recovery of old data.
Now would be a good time to start backing up regularly, or at least before you start flashing roms, unlocking things, etc. There is a reason why we say 'always make a nandroid backup!' :angel:
Click to expand...
Click to collapse
I am afraid that I lost my data. I am going to try a root in the afternoon, I will update this post if any problems occur
Thanks for the help and replies so far!

[Q] Extremely Slow Xperia SP

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

[Q] I think I hard bricked my N6

Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Aanze said:
Hi there,
So I just bought a brand new N6.
Did nothing to it, did not unklock the bootloader, di not flash anything.
Just ran it a first time, set my account, donwloaded the 5.1 OTA when proposed to and then it was over.
After the OTA installation my phone displayed a dead android and "Error".
When rebooting my phone, the apps are "optimizing" undefinitely and then the phone will restart.
I tried factory reset from recovery, that did nothing, I mean, the phone will still bootloop endlessly.
My bootloader is not unlocked so I cannot flash my phone..
Is there anything I can do ?
Thank you in advance
Click to expand...
Click to collapse
try fastboot formatting userdata and fastboot formatting cache
simms22 said:
try fastboot formatting userdata and fastboot formatting cache
Click to expand...
Click to collapse
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Aanze said:
Same story.
Black screen then reboot, then optimizing then reboot and so on...
Click to expand...
Click to collapse
unfortunately, that might have been your only option. as you need to boot up first, to enable unlocking of your bootloader, to reflash the factory image. and you cant boot up
Evolution_Tech said:
Well, since you haven't enabled OEM unlock, there's not much you can do besides RMA at this point.
Click to expand...
Click to collapse
That's what I thought.
I thought I could use the fix described here http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518 but my device does not appear as "qhusb_bulk" like specified so I guess its over.
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
simms22 said:
id get the phone refurbished, from google or from motorola, since it wasnt anything that you did, but was the updates fault. btw, that happens, very rarely, but it does happen that updates can cause issues.
Click to expand...
Click to collapse
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Aanze said:
Well thank you anyway, looks like I have no other choice than send the device back.
One last question, since my phone won't stop rebooting endlessly is there any way to turn it off ? Long press on power does not do anythng, it will stil restart...
Edit: I found how to turn it off through bootloader.
Click to expand...
Click to collapse
exactly. i was just gonna write how to do that.
simms22 said:
exactly. i was just gonna write how to do that.
Click to expand...
Click to collapse
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Aanze said:
Sorry to come back on this thread.
So now I have noticed that when in fastboot, if I type "fastboot oem unlock" I'm getting the popup proposing to unlock bootloader.
As I never selected USB debugging nor enabled developper option when my phone was working, I doubt it would work properly.
Would I have any chance to recover my phone if choosing to unlock the bootloader ?
Click to expand...
Click to collapse
yes! if you can unlock the bootloader, then you can flash the factory image via fastboot while youre in your bootloader. which would fix you not booting
prdog1 said:
If getting that it should unlock. Got nothing to lose and if does unlock it is recoverable.
Click to expand...
Click to collapse
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
Your good to go. Just need to fastboot the stock images.
just return it, if you find that you cant recover it after unlocking the bootloader then they wont take it back
Aanze said:
Wow.. So I tried.. and.. "Device is unlocked" is displayed... I guess I have a chance to flash something now.
Click to expand...
Click to collapse
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
simms22 said:
grab a factory image, and read directions for flashing a factory image. you want to flash each individual file inside separately, instead of using the flash-all script.
Click to expand...
Click to collapse
Yep, doing it right now.. flashing system currently.. crossing fingers;.
crossing my fingers for you over here as well
It worked !! IT WORKED !
I love you xda ! really do love you.
Thanks a million.
(Although it's a bit strange that I was able to unlock bootloader without usb debbugging mode enabled no ?)
This is very interesting indeed. To the OP, where did you purchase the device? I find it very peculiar that you were able to issue the OEM unlock command without using the toggle in settings.

ASUS Unlocking Tool Not working

Since ASUS changed its website since 2014 and changed the way you unlock your device, I have been trying to unlock my tablet with the unlock tool for TF701t. (Which btw is going out of warranty next week). I've been getting "Invalid Password" message! Password is correct. Does anyone know how to get pass this issue. What am I doing wrong? The firmware is on the most current one. I'm dumb founded??? Please help. Thank You.
sunnytexas said:
Since ASUS changed its website since 2014 and changed the way you unlock your device, I have been trying to unlock my tablet with the unlock tool for TF701t. (Which btw is going out of warranty next week). I've been getting "Invalid Password" message! Password is correct. Does anyone know how to get pass this issue. What am I doing wrong? The firmware is on the most current one. I'm dumb founded??? Please help. Thank You.
Click to expand...
Click to collapse
Sorry for the question! Solved the problem - You have to delete google account in tablet before using unlock tool.
When checking off the agreement and question and you hit the unlock button - the tool will notice you don't have a google account and it will ask you if you want to proceed to unlock the tablet - Say "Yes" and you are good to go.
I spent hours trying to unlock this tablet!
sunnytexas said:
Solved the problem - You have to delete google account in tablet before using unlock tool.
When checking off the agreement and question and you hit the unlock button - the tool will notice you don't have a google account and it will ask you if you want to proceed to unlock the tablet - Say "Yes" and you are good to go.
I spent hours trying to unlock this tablet!
Click to expand...
Click to collapse
Seriously bro, you made my day :good:
I was stuck at this step, and almost all the topics on forums talking about unlocking the Transformer Pad are from 2013. Thanks a lot for the tip!
Thanks, this helped me, too! I had to do a factory reset to delete the Google account because I couldn't find the delete button. But ultimately, this allowed me to run the unlock tool.
Hello guys, it seems that the asus support for the TF701 is over(unlock tool get no connection anymore) and i have not found any solution to unlock the bootloader .
Has anyone an ides what else i can try?
cort101 said:
Hello guys, it seems that the asus support for the TF701 is over(unlock tool get no connection anymore) and i have not found any solution to unlock the bootloader .
Has anyone an ides what else i can try?
Click to expand...
Click to collapse
I have the same problem - no connection when trying to unlock. Found any solution?
JerryBels said:
I have the same problem - no connection when trying to unlock. Found any solution?
Click to expand...
Click to collapse
Same here please help!
senate194 said:
Same here please help!
Click to expand...
Click to collapse
Take a look here
It works fine.

Nexus 6 Motorola Help Needed

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.

Categories

Resources