[q] moto x locked! - Moto X Q&A

Admins, excuse if i posted on wrong forum, verify me if im wrong.
I got this MOTO X locked with pattern, i have a lot of important info in there that i don't want to lose, I don't have the gmail account for recovery... is there any solution?????, if so ill be so glad please help

asesinoboy said:
Admins, excuse if i posted on wrong forum, verify me if im wrong.
I got this MOTO X locked with pattern, i have a lot of important info in there that i don't want to lose, I don't have the gmail account for recovery... is there any solution?????, if so ill be so glad please help
Click to expand...
Click to collapse
The **easiest** way is to just erase all userdata if you don't mind losing everything on the phone.
Boot into bootloader mode (Power off phone, hold down VOL DOWN + POWER). The phone should boot into the bootloader and show "AP Fastboot Mode".
Now assuming you have the Motorola Drivers, and the Android SDK installed, you can open a command prompt and type:
fastboot erase userdata
fastboot reboot
Bam! No more lockscreen OR google account. Phone will be factory reset and you can set it up as you like, using your own google account and such...

samwathegreat said:
The **easiest** way is to just erase all userdata if you don't mind losing everything on the phone.
Boot into bootloader mode (Power off phone, hold down VOL DOWN + POWER). The phone should boot into the bootloader and show "AP Fastboot Mode".
Now assuming you have the Motorola Drivers, and the Android SDK installed, you can open a command prompt and type:
fastboot erase userdata
fastboot reboot
Bam! No more lockscreen OR google account. Phone will be factory reset and you can set it up as you like, using your own google account and such...
Click to expand...
Click to collapse
I don't want to lose any data, is there any other solution?

asesinoboy said:
I don't want to lose any data, is there any other solution?
Click to expand...
Click to collapse
Yep. Use the [much more complicated] adb method:
http://forum.xda-developers.com/showthread.php?t=1409304
Good Luck :good:

Hmm.. Any Moderator reading threads here?

bmszabo said:
Hmm.. Any Moderator reading threads here?
Click to expand...
Click to collapse
I had the same thought actually.....what can ya do though. Unless they outright say it, we kinda have to assume it is legitimate...

I don't see how anyone owns an android with no gmail(google) account. Perhaps asking the person who owns the phone for their pin is the easiest solution? ?

This all sounds a bit too suspicious for my liking as I agree with the above.
Thread closed

Related

NO OS installed.... Cant mount

So im stuck with my nexus with no OS... after flashing pure shamu it booted to just a password box... I input my password and it said i had corrupt data. I hit reset... wiped phone... all files GONE... Now what do i do. I cant mount to put recovery on.... I cant do anyting with this phoen right now... anyone had this happen... If so what steps to remedy?
Sounds like you need to try and fastboot the original google files, nuke and repave....
flash the stock img then start again
Flashing stock as we speak... was hoping another optino.... but after years of doing this I kinda know better... live and learn
hell
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
asphalte7 said:
Hi there, i'm new with Android and my problem is the same as yours on my Nexus 6.
after a failed root, i accidentally deleted all data. Now i'm without OS, boot locked, and the TWRP recovery has been deleted too (when i select recovery mode, it come back to the fastboot menu). i cannot use "fastboot oem unlock"
I don't know what i have to do . I really need help, i just want to restart from the beggining like official rom ...
sry for bad english.
Click to expand...
Click to collapse
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Evolution_Freak said:
Try using these fastboot commands:
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
asphalte7 said:
done, what can i do after this ?
it says : created filestystem.... OKAY (with a lot of parameters)
Click to expand...
Click to collapse
Should be able to boot twrp now.
but i have to unlock first ... my device is locked
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
you cant unlock it without booting up and enabling allow oem unlocking in the developer options
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
If you can boot to TWRP recovery, then you can ADB push a ROM to recovery and boot it.
Edit: Sorry, I missed the fact that TWRP had been deleted too.
asphalte7 said:
but i have to unlock first ... my device is locked
Click to expand...
Click to collapse
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Evolution_Freak said:
No, if you can boot to TWRP, as @rootSU said, you can move a ROM to internal and get up and running. Then you can go about unlocking.
Click to expand...
Click to collapse
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
asphalte7 said:
and how can i boot twrp ? i'm like john snow, i know nothing
i only have a console, and a nexus - which cannot exit the "bios"
Click to expand...
Click to collapse
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
Or, if you are still in fastboot, issue this command > fastboot reboot recovery
Evolution_Freak said:
Power off the device. Once completely shut down, hold power and volume down until bootloader screen appears. Then use the volume keys to select recovery. Then push power to select.
Click to expand...
Click to collapse
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
asphalte7 said:
as i said before, when twrp has been deleted, the Recovery mode is useless : when i hit it, it instantly return to bootloader screen
Click to expand...
Click to collapse
Then I'm afraid you may be stuck. A RMA may be in your future if no one else can offer a solution.
simms22 said:
from your original post, it says your not running twrp anymore. have you tried just letting the phone try to boot up? have you tried reflashing twrp to your phone via fastboot. id try, and if its successful, id push a rom to my phone then. if not, try flashing a factory img.
Click to expand...
Click to collapse
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
asphalte7 said:
i left my phone during half an hour on the "Google" screen ....
i cannot flash twrp with fastboot because its locked..
or which command i have to type to install it ?
how can u flash a factory img ? i dowloaded the official 5.1 rom for nexus 6
Click to expand...
Click to collapse
flashing twrp..
fastboot flash recovery recoveryname.img
and flashing a factory img is done while the phone is in its bootloader. there are instruction how here on xda. but to be honest, i dont know if that will work. where did you buy your n6 from btw?

[Q] bricked? wiped out?

my xt 1032 moto g is not working. it stays on unlocked bootloader warning. worked great after rooting it, but I think I erased everything off it. I cannot do any factory resets, nor can i manage to push a rom to it. I can access it using adb, but I always end up with some kind of error, likely on my noob behalf.
Can someone please help me with this, I tried to push a rom but it said stat cannot access file, or something like that. I think i need help most with the correct steps on doing this, already unlocked bootloader and rooted. adb only recognizes my device when in recovery mode.
Keep pressing volume down + power until your phone turns off and then quickly repeat. Now you should be in fastboot mode. Find your stock firmware and flash it.
xGiorgos said:
Keep pressing volume down + power until your phone turns off and then quickly repeat. Now you should be in fastboot mode. Find your stock firmware and flash it.
Click to expand...
Click to collapse
Thanks but thats not the problem. I need to know the proper words to put in the adb command window, and figure out why it wont push to the sdcard
lee7611 said:
Thanks but thats not the problem. I need to know the proper words to put in the adb command window, and figure out why it wont push to the sdcard
Click to expand...
Click to collapse
Ok you say XT1032 ??? thats Moto G original not the 2nd Generation that this forum is
GO HERE http://forum.xda-developers.com/moto-g

HELP PLEASE! Stuck in bootloader, NEXUS 6

Hi, I wanted to flash the 5.1 update to my new Nexus 6.
I went all over the basic steps.
After I unlocked the bootloader I tried to flash the image with the flash-all command.
It failed, so I remembered maybe I forgot to click on USB debugging? (This confuses me because I think I shouldn't be able to unlock bootloader without this).
When I wanted to start android I locked it first, so I would unlock it afterwards and erase everything to start as new.
Whan I locked it, I could not unlock it again. I can't access Android, neither do anything else like factory reset nor Recovery Mode. I return to the bootloader as soon as I press anything.
There are red words at the top: AP Fastboot Flash Mode (Secure). Does this means anything?
Is there any way to force unlocking the bootloader? When I try it, the phone tells me to go to Developer Options but I can't access Android.
Please HELP! Is there any way to flash a rom or android again in locked state? Recovery?
Thanks for reading this and thinking about a solution! I really hope I won't be stuck forever in bootloader.
Uh oh... Were you trying to downgrade back to LRX22C from LMY47D so that you could upgrade to LMY47M, by any chance?
If so you might be fooked.
Actually no. I was trying to upgrade from 5.01 to 5.1. I'm really scared of having my Nexus 6 bricked. I can't do anything to unlock the bootloader. Maybe I could sideload a recovery? But do I need to be unlocked?
Sent from my Nexus 7 using XDA Free mobile app
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
I hope you get it sorted out. I have read SO many bad things regarding this topic and people being screwed that they cant get back in to re-unlock after relocking
toknitup420 said:
Try here this might help you. I hope.
http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
I think you are 100% right. I am in panic mode, thanks. I'll do it again following every step. I'll let you know.
sotnasnauj said:
I already tried this solution, I think mine is a little different. At the end of the post it says to enter fastboot and restore with a factory image. I can't because I am not unlocked. In order to unlock my device I have to go to Developer Settings (it is the message when I use the OEM unlock command). but I can't access to Android. I am stuck in the bootloader but can run fastboot commands.
Click to expand...
Click to collapse
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
toknitup420 said:
You should be OK. People in that thread have reported success flashing the new factory image while locked. Check the last few pages of the thread.
Click to expand...
Click to collapse
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
sotnasnauj said:
Thanks! I've been reading a lot from this thread but I get something unusual as the other people are experiencing. When I try to flash partition gpt.bin I get (bootloader) Unlock before flashin.
It is kind of contradictory as this fix supposedly fixes flashing without unlocking. I don't know if it is a problem of drivers. My PC sees my N6 as Google Nexus Bootlader Interface. In the thread, the PC sees the device as "Bulk" or "Qualcomm ....... etc etc".
My panic mode isn't turning off. I may be missing something.
Click to expand...
Click to collapse
Did utry fastboot devices to see your device is connected...then fastboot oem unlock?
Also, I'm the one who has found a fix for the bricked issues when it comes to locking and unlocking the boot loader...in boot loader...when u go to recovery....what happens?
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
idtheftvictim said:
The solution that was posted should work, but you need to use RSD Lite in order to flash the factory image, not fastboot.
Read it over nice and slow again, because you are in panic mode right now, so take your time and you will get it back up and running with no problems.
Click to expand...
Click to collapse
Now I've tried everything in that thread, when I was reading I thought flashing gpt.bin would be the solution but I can't do it, I can't flash it.. It says "Unlock before flashing". Supposedly flashing gpt.bin would allow me to flash without unlocking.
My last resource is trying this on a mac, I've read you don't need drivers so maybe it is a driver thing. I HOPE SO..
Can't access adb with my pc.
You don't need adb.
sotnasnauj said:
Yes, my device is connected. I've tried everything. I've been reading the last thread and posted what is happening to me, this is the URL of my posts.
http://forum.xda-developers.com/showthread.php?p=59659030
I can't go to recovery, I return to the BL.
Click to expand...
Click to collapse
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
jamescable said:
Download factory images...extract them....pull the stick recovery and use the command fastboot flash recovery recovery.IMG
Also...did ubuse fastboot OEM unlock?
Click to expand...
Click to collapse
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
sotnasnauj said:
Yes, I used it but it tells me I need to go to Developer Settings and Allow OEM Unlock which I cant because cant access Android.
I can't flash anything as I am OEM Locked
Click to expand...
Click to collapse
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
rootSU said:
I think you should lock this thread. Following advice from different people in different threads is a really BAD idea.
Click to expand...
Click to collapse
I agree because op is somehow confused.....fastboot has nothing to do with develope settings USB enabled
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
hlxanthus said:
Yes it does. He flashed the factory images, then relocked (which defaults to disabled oem unlocking). But something failed (guessing possibly userdata failed). I would recommend fastboot formats userdata to perform a factory reset from the boot loader to see if you can get android to boot.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes.
Running
Code:
fastboot format cache
fastboot format userdata
Make sure it's FORMAT not erase.
Then walk away, watch some T.V. and don't check it for a while. (Panic mode will make it seem forever, trust me! I did the same thing as you!)

New Nexus 6 stuck in a bootloop trying to update to 5.1, please help.

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.
Any help, advice etc would be hugely appreciated. Thanks
Markh2001 said:
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.
Any help, advice etc would be hugely appreciated. Thanks
Click to expand...
Click to collapse
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
AndroidSlave said:
Read the guide on how to fastboot flash a factory image. No toolkit necessary.
Click to expand...
Click to collapse
Would you mind posting a link to a guide? I forgot to add that I don't want my phone to become rooted by trying to fix this issue, I want to keep it stock like it was, also does not have developer options enabled stop me from going further.
Sorry for the questions I'm a noob to this and quite anxious.
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Markh2001 said:
Can anyone still please help! I'm a noob and so need instructions on what to do! Please!
Click to expand...
Click to collapse
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Markh2001 said:
All foreign language to me what your saying, trying my best to self learn right now. I'm downloading the adroid SDK and extracting the files, really want to sort this myself. Any pointers to getting into bootloader mode? And adb on the PC?
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/showthread.php?t=2588979 for easy adb installation. Read this too http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481.
To get into bootloader mode power down the device and after that press volume down + power. Here`s a guide to setup the sdk/adb http://www.redmondpie.com/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/.
gee2012 said:
If you connect the phone to the pc is it recognised in bootloader mode? Do you have adb installed onyour pc?
Click to expand...
Click to collapse
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Markh2001 said:
I've made the fastboot adb folder on my PC and attached my phone whilst it was in bootloader mode, I types in the command box adb devices and there is no list of attached devices.
I presume this is because I didn't enable developer options or USB debugging?
Click to expand...
Click to collapse
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Markh2001 said:
Sorry to be a noob but how do I do this? Is this on the PC I presume?
Click to expand...
Click to collapse
There is nothing you can do with a locked bootloader, claim warranty/RMA
gee2012 said:
When in bootloader mode type : fastboot devices
-Edit- just read that your bootloade is still locked so i`am afraid there is nothing you can do to fix the issue as you cannot flash firmware with a locked bootloader. Best is to claim warranty because of a software issue while updating.
Click to expand...
Click to collapse
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Markh2001 said:
Thought this would be the case, I went into adb fastboot and typed in fastboot devices and its showing some letters and numbers next to fastboot on screen if that helps.
In the future I presume I should make sure to enable developer options first so I can get out if this mess?
Also would it be best when I get my new n6 just to sideload the latest update marsmellow by getting the factory image from the Google website? Last question can I skip from 5.0 straight to 6.0 sideloading or do I have tobdo it one at a time?
Thanks for trying to help matey
Click to expand...
Click to collapse
Next time enable usb debugging and ENABLE OEM UNLOCK, both in developer options. You can flash the latest firmware available directly in fastboot by flashing the individual img files.
Here is a link to setup adb/platform-tools https://www.google.nl/url?sa=t&rct=...orial/&usg=AFQjCNGolazOWoMssTikMpokJ6TtwEND5A.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Markh2001 said:
This is getting very weird now as I just typed into the adb fastboot window : fastboot oem unlock and its giving me a message on my screen to click yes and unlock the bootloader?
Click to expand...
Click to collapse
Well click the power button and in the next screen scroll down with the volume button to select yes and push power.
gee2012 said:
There is nothing you can do with a locked bootloader, claim warranty/RMA
Click to expand...
Click to collapse
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Markh2001 said:
It says this on my Nexus 6 phone screen.
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from your phone (a "factory data reset".)
Press the volume up/down buttons to select yes or no. Then press power button to continue.
Yes (Unlock bootloader, may void warranty)
No. ( Do not unlock bootloader and restart phone)
Click to expand...
Click to collapse
Click yes, see my above post
gee2012 said:
Click yes, see my above post
Click to expand...
Click to collapse
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Markh2001 said:
Okay but will I be able to relock and put it back to the way it was? Can you please stay around to help me do this step by step?! I'd appreciate it a million
Click to expand...
Click to collapse
Sure, but first we have to get the phone working again,

[HELP]Making ADB work with Moto G 2014

Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
PsyClip-R said:
at first learn what ADB is.
at second - fastboot it the proper place to begin with.
Click to expand...
Click to collapse
Well, fastboot don't want to work neither so that answer didn't help at all
Tenderenden said:
How can I fix this?
Click to expand...
Click to collapse
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
doppelhelix said:
ADB can only be used from a fully booted device (you have to be past the login screen. It's a security measure so no one can mess with your data without approval). You can use fastboot commands though.
Try this
Download Minimal ADB and Fastboot and install it.
start "Minimal ADB and Fastboot" by navigating to the Start Menu Folder you choose to create during installtion or the desktop shortcut you choose to create and selecting "Minimal ADB and Fastboot"
You should now see a command window open.
Put your device in fastboot mode and connect usb.
Now just do verify type this command
Code:
fastboot devices
the output should show something like this (your number is different)
Code:
fastboot devices
XXXXXXXXXXfastboot
Now do your thing, like flashing stock ROM. Multiple tutorials exist for that.
Click to expand...
Click to collapse
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot? Because I think that flashing stock ROM will erase any personal data, but I really need to get it.
Tenderenden said:
That is the answer that I needed!
Can I somehow pull data from this phone using fastboot?
Click to expand...
Click to collapse
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Okay, I got it. Now, have you got any suggestions how to get contacts and (hopefully) SMS back?
Tenderenden said:
how to get contacts and (hopefully) SMS back?
Click to expand...
Click to collapse
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
doppelhelix said:
No. That would defeat the lock screen. Just imagine someone steals your phone and can access your data just by booting into fastboot.
Click to expand...
Click to collapse
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
Click to expand...
Click to collapse
Does this work with locked bootloader? That would be really messed up.
Tenderenden said:
Hi,
My friends Moto G just died and now it is just bootlooping. He asked me to try get contacts through ADB but it is not finding phone.
I installed Motorola Device Manager and it seems that it found phone and successfully used command "get variable", but when I use ADB via CMD it don't even finding phone.
How can I fix this?
Click to expand...
Click to collapse
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
PsyClip-R said:
Loading custom recovery via
fastboot boot TWRP.img should do the job.
than one can can make a full backup, which might be extracted on pc as a regular archive.
Click to expand...
Click to collapse
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
doppelhelix said:
Contacts are synchronised with your Google account (unless you choosed not to). Can't say the same about SMS.
Click to expand...
Click to collapse
Unfortunately in this case contacts weren't synchronised.
LuK1337 said:
Is your bootloader locked?
Can you try fastboot oem partition dump userdata (using mfastboot, not Google's fastboot)?
Click to expand...
Click to collapse
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Tenderenden said:
I will try that. Firstly my friend want to message the seller to get his phone repaired. So I can not touch anything in software until he is done.
Unfortunately in this case contacts weren't synchronised.
Well, it seems that I have to read something more about what you said here firstly xD
And the bootloader is locked.
But I appreciate any new idea that may lead to solving this problem.
Click to expand...
Click to collapse
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
LuK1337 said:
fastboot oem partition dump userdata may work with locked BL and it'd be great to know if it does...
Click to expand...
Click to collapse
I will try it as fast as I can. Thanks

Categories

Resources