Related
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
stayboogy said:
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
Click to expand...
Click to collapse
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
vampirefo said:
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
Click to expand...
Click to collapse
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
stayboogy said:
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
Click to expand...
Click to collapse
In Linux you need to make user rules if you don't want to use sudo to fastboot, my .50 recovery is a straight pull from CyanogenMod's 4.4 tree.
other recovery straight pull from CyanogenMod's 4.3 tree
Hi...
This is the tutorial to root any Moto G
To root any Moto G, three basic steps need to be followed... you can either do them manually or use a tool do them for you. It is advised to follow them manually so that if there's some bug in the tool you don't get into any trouble.
CAUTION - You will lose all data and files so better back them up.
For Google Play edition devices, the process is same and only the recovery.img file is different. For GPe CWM Advanced Edition recovery go here https://goo.im/devs/philz_touch/CWM_Advanced_Edition/ and select falcon_gpe and download the latest one.
For AT&T and Verizon models don't do anything written above. Just download the Towelroot app. Its a one click root app and doesn't require a PC. Itis trustworthy but is not guaranteed to work but you must give it a try since it won't do any harm and claims of never bricking a phone. Please reply with the result and your android and kernel version.It will probably not work on phones build after June 3 but you can give it a try. You can download it from the website https://towelroot.com
The three steps are :-
1) UNLOCKING THE BOOTLOADER
2) FLASHING CUSTOM RECOVERY
3) INSTALLING SuperSu.zip FILE THROUGH RECOVERY. (SuperSu is acknowledge as the best app to give superuser and root rights)
UNLOCKING THE BOOT LOADER - The instructions to unlock the boot loader are given in the official Motorola website here https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a . Don't be scared by their warnings.
UPDATE - There currently seems to be an issue with unlocking the bootloader on devices running 4.4.4 though it works for 4.4.2. The issue is with Motorola and is that, the unlock code given by the company is showing an error. They are fixing it and it may take some time though you can give it a try as it won't do any harm. Or you can downgrade the boot loader to 4.4.2 and then unlock it.
As confirmed by the Motorola agent, the problem of unlocking bootloader on 4.4.4 has been fixed
FLASHING CUSTOM RECOVERY :-
To flash a custom recovery, you need these things
1) PC and a USB data cable
2) Android SDK ( developer.android.com/sdk/index.html ) For flashing recovery only SDK is needed but it's your wish if you want to download the ADT bundle. After downloading and unzipping the sdk , open the SDK manager and download only the platform tools for this.. rest is your wish..... and separately download ADB tools and fastboot and extract them minimal-adb-and-fastboot.software.informer.com/1.1/
3) Recovery.img file - You can either use CWM foum.xda-developers.com/showthread.php?t=2563599 or CWM advanced editionforum.xda-developers.com/showthread.php?t=2639583 or TWRP forum.xda-developers.com/showthread.php?t=2561757. EDIT - If your phone had come pre installed with 4.4.4 then use only CWM Advanced Edition. CWM Advanced Edition doesn't make backup on XT1033
4) Motorola drivers https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/97326/p/30,6720,9050
5) Enable USB Debugging mode in your phone by going to Settings-About Phone and then tap the build number until you get the toast 'You are a developer'. Now go to Settings again and you will see a new Developer Options there. Go there and enable USB debugging.
6) Have at least 25% of charge on your phone.
After getting all these things:-
1) Download the recovery.img file to your PC and copy paste it to android SDK/platform tools folder.
2) Boot your phone to fastboot mode by first switching it off and holding the volume down and power button for 3 seconds.
3) When in fastboot mode, connect your phone to pc, go to the platform tools folder, there pres shifft and right mouse click simultaneously and select 'open command prompt window here'.
4) In the command window enter
Code:
fastboot devices
If it shows a number and fastboot then we are good..
5) Then enter
Code:
fastboot flash recovery recovery.img
( where in recovery.img the recovery is the name of your recovery file. Example if the name of recovery file is ABC then enter fastboot flash recovery ABC.img)
5) Press enter and if the command prompt window displays the message okay then the recovery is successfully flashed.
6) Now just boot your phone to recovery mode through fastboot mode by following the on screen instructions and in recovery mode select Reboot System Now to reboot your phone normally.
(see attached images below for screenshots)
INSTALLING SuperSu
To install SuperSu :-
1) Download SuperSu zip file download.chainfire.eu/452/SuperSU/ and transfer it to your phone
2) Reboot to recovery via fastboot.
3) Select install zip and select choose from SD card.
4) Locate the file and install it.
5) Now reboot your phone.
YUP.. YOU ROOTED YOUR PHONE!
Download any root checker app from the Play Store to check whether your phone is rooted or not.
If you get into any trouble, please contact and don't forget to hit thanks if it helped
Consider rating the thread by going to the option 'rate thread' which is located above the thread on the right side. You can also participate in the poll
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
sisqoboy said:
I have a huawei p6 but I'm absolutely not satisfied with that and I bought a moto g for my girlfriend and that is awesome.
The only thing why I haven't bought the g for myself as well is the rooting. That time I didn't find an easy way to root it.
If it is a working method than I will buy the 4g verson with sd card support
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Yup dude...this works for sure..!
I also added screenshots.. check them out.
Meuuks13 said:
Yup dude...this works for sure..!
Click to expand...
Click to collapse
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
motocruiser said:
Does this work with the latest bootloader on 4.4.4? Im still stock but i wanna root it so much
Thanks
Click to expand...
Click to collapse
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
xrilex said:
And does this work for Verizon model
Sent from my XT1028 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You have Verizon I see. The only you will probably face is unlocking the bootloader.. Oh, wait first let me laugh... lol...OK....At one point of time you couldn't unlock the bootloaders for AT&T and Verizon and then we were blessed by the 'one click root' app by the famous hacker geohot called TowelRoot. This app claims to root all the AT&T and Verizon devices with just a click. You don't even need a PC. Just download the app and in the app chick 'make it rain'. Though this is not guaranteed to work but must give a try as it won't do any harm but there's a chance of bricking the phone but you can easily recover from a soft brick by flashing the stock firmware.
Towelroot - https://towelroot.com/
P.S. - Please reply if you tried this and if it didn't work reply with your android version and kernel version. Well reply with your android version and kernel version anyway.
Edit- I added it to the OP
Meuuks13 said:
I looked into it just now... Currently there's an issue with Motorola with unlocking the bootloader when on 4.4.4...As people say, the unlock code given my Motorola is showing an error... You can still try it.. maybe it's even fixed by now.. Even if it fails there wouldn't be any harm.. Though the unlocking works fine with 4.4.2... You can revert back to 4.4.2, unlock the bootloader and then update to 4.4.4... The thing will be same as you will lose all data and files when unlocking the bootloader and so in reverting to 4.4.2.....(Remember, only unlocking doesn't mean you won't recieve updates, you won't receive updates only if you flash a custom recovery.)
EDIT - I added it to the OP. Thanks for bringing it to attention.
Click to expand...
Click to collapse
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
motocruiser said:
thanks for your help dude but i heared that if you flash back to 4.4.2 your bootloader is still the latest so its still unlockable...
i have found a fix on a motorola customer forum for this problem, but when i flash this testdrive motoboot image file it goes wrong and i cant fix it by my self
Click to expand...
Click to collapse
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell which android version your phone came preinstalled with and what recovery you used.
Also when you reboot to recovery, after the blank screen do you see the android logo lying down with a red triangle?
t.lou91 said:
Hey! I have followed all the steps. When i flash de recovery.img, the command prompt says everything is ok, but when i try to reboot into recovery trough the fastboot, it just turns off! It dosn't rebot into recovery! Thanks man!
Click to expand...
Click to collapse
Please tell your phone's android version and the recovery you used and what did you enter at the command prompt?
Meuuks13 said:
Sorry I didn't know that. Downgrading the bootloader is a very risky process.
What did you exactly do?
Click to expand...
Click to collapse
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
motocruiser said:
Well it doesnt go wrong like you think so my phone is actually not bricked.
But the command window says that the operation failed so i think something is wrong with this testdrive image from the moto forum.
thanks
Click to expand...
Click to collapse
Testdrive image?
Meuuks13 said:
Testdrive image?
Click to expand...
Click to collapse
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
motocruiser said:
Yeah they say, if you on 4.4.4 and want to unlock your bootloader you have to flash the motoboot_testdrive.img file wich downgrades the bootloader to i think it was called 40.15 or so after that you have to unlock your bootloader and then flash the motoboot 4.4.4 stock image so that you have the actual one but for me it failed while i try to flash this testdrive image
Click to expand...
Click to collapse
So basically you want to downgrade the bootloader and then unlock it?
Well if you are on KitKat you can downgrade the bootloader by flashing 4.3 , then unlocking the bootloader and then updating to KitKat
Thanks for the guide. I've already recommended it to someone who was having problems.
jselene said:
Thanks for the guide. I've already recommended it to someone who was having problems.
Click to expand...
Click to collapse
Cool.
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
JDCGW said:
Thanks Meuuks13. This worked well.
Also, I've found that you can remove the "unlocked bootloader warning message" shown on boot-up by following the method in the Moto X forum:
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566
Click to expand...
Click to collapse
I got something wayyyy better than that!
I let you remove that sign and use the pics given here forum.xda-developers.com/moto-g/themes-apps/shareboot-logos-t2875147 or you can give me the pic you want and I will make it in such a way that you can use it.
Hey, trying to flash my Nexus 6P with Android 7, buy when I try to unlock with fastboot flashing unlock, I just get a list of command options. I've updated Android Studio and the SDK, but nothing changes. What can I do?
Try Nexus Root Toolkit... But why don' you just sideload the OTA with ADB?
fodi97 said:
Try Nexus Root Toolkit... But why don' you just sideload the OTA with ADB?
Click to expand...
Click to collapse
How do you get adb to recognize the phone? Minimal sdk can't find the phone
Envoyé de mon Nexus 6P en utilisant Tapatalk
Reinstall all drivers with the toolkit. And delete all previous SDK and driver installs
Can the toolkit root the new NRD90M?
Envoyé de mon Nexus 6P en utilisant Tapatalk
fodi97 said:
Try Nexus Root Toolkit... But why don' you just sideload the OTA with ADB?
Click to expand...
Click to collapse
adb doesn't see the phone. Is there toolkit for Linux?
Do you have USB debugging enabled in developer options?
And oem unlock enabled?
Sent from my Nexus 6P using XDA-Developers mobile app
pipnmike said:
Do you have USB debugging enabled in developer options?
Click to expand...
Click to collapse
Yes. fast boot itself works and fastboot devices returns a listing for my phone. As I said in my first post, it is fastboot flashing unlock that returns the command options.
aSystemOverload said:
Yes. fast boot itself works and fastboot devices returns a listing for my phone. As I said in my first post, it is fastboot flashing unlock that returns the command options.
Click to expand...
Click to collapse
i faced the same problem. i used method 2 as described in the link below
http://forum.xda-developers.com/nexus-6p/general/tutorial-how-to-flash-factory-image-t3252931
For what it's worth, i flashed the OTA image yesterday. When booted, adb did recognize the phone. But when in recovery, adb did not see it. At that point, i just unplugged the phone from the PC and plugged it back in. The PC proceeded to install the drivers again. After that, adb worked.
aSystemOverload said:
Yes. fast boot itself works and fastboot devices returns a listing for my phone. As I said in my first post, it is fastboot flashing unlock that returns the command options.
Click to expand...
Click to collapse
You don't need any toolkit. Your problem is an outdated SDK.
http://forum.xda-developers.com/showpost.php?p=62924139&postcount=3
Hmtsjmftsch said:
And oem unlock enabled?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Please read what I've written, I'm trying to unlock it with fastboot flashing unlock, but it just returns a bunch of command options
Heisenberg said:
You don't need any toolkit. Your problem is an outdated SDK.
http://forum.xda-developers.com/showpost.php?p=62924139&postcount=3
Click to expand...
Click to collapse
No it is not. I've complete removed Android Studio and the SDK and reinstalled/redownloaded from scratch, still the same.
aSystemOverload said:
No it is not. I've complete removed Android Studio and the SDK and reinstalled/redownloaded from scratch, still the same.
Click to expand...
Click to collapse
Are you sure? Is your platform-tools package up to date? The only reason fastboot throws a list of possible commands is when it doesn't recognize the command you're trying to issue. The only reason it wouldn't recognise the command you're trying to issue would be if it was out of date.
Heisenberg said:
Are you sure? Is your platform-tools package up to date? The only reason fastboot throws a list of possible commands is when it doesn't recognize the command you're trying to issue. The only reason it wouldn't recognise the command you're trying to issue would be if it was out of date.
Click to expand...
Click to collapse
Yes, I'm sure. I deleted the Android Studio and separate android-sdk folders and re-downloaded both from scratch. I've sorted it, I did it on my work Win10 laptop. But adb won't work period (problems conecting to the daemon) and fastboot works, but doesn't recognise flashing unlock. On a side note, i realised I hadn't allowed unlock from developer settings, but even after fastboot flashing unlock still didn't work. *shrugs*
aSystemOverload said:
Yes, I'm sure. I deleted the Android Studio and separate android-sdk folders and re-downloaded both from scratch. I've sorted it, I did it on my work Win10 laptop. But adb won't work period (problems conecting to the daemon) and fastboot works, but doesn't recognise flashing unlock. On a side note, i realised I hadn't allowed unlock from developer settings, but even after fastboot flashing unlock still didn't work. *shrugs*
Click to expand...
Click to collapse
So if you type in adb in command prompt does it tell you which version of adb you have installed? It sounds like you have some issues with you're install of SDK tools. Is java up to date.
aSystemOverload said:
Please read what I've written, I'm trying to unlock it with fastboot flashing unlock, but it just returns a bunch of command options
Click to expand...
Click to collapse
I ment: did you enable oem unlock in settings (developer options)?
Heisenberg said:
You don't need any toolkit. Your problem is an outdated SDK.
Click to expand...
Click to collapse
x2
Guaranteed, this is your problem.
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
avansledright said:
My Nexus 6P is seemingly bootlooping.
I can boot into the bootloader menu but not into recovery. My bootloader is not unlocked so I cannot flash anything.
Issuing the command: "fastboot flashing unlock" does not work nor does "fastboot oem unlock". I cannot flash a custom recovery. Because my bootloader is locked.
Any help would be great.
Click to expand...
Click to collapse
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Fe Mike said:
You say that your bootloader was not unlocked, so I'm assuming you didn't have developer options turned on and USB debugging checked before fastboot flashing unlock?
Click to expand...
Click to collapse
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
avansledright said:
I don't recall if i had them turned on or not. I know my device was enrolled in the Android beta program.
Click to expand...
Click to collapse
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Fe Mike said:
Do you remember if you modded anything prior to bootloop? The reason you can't unlock bootloader is because USB debugging isn't on. What version of Android were you on when it happened? I believe you can still use google factory Image to restore your phone.
Click to expand...
Click to collapse
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
avansledright said:
The last thing i did was installed the new Google camera 4.2 but it worked fine after that.
Click to expand...
Click to collapse
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Fe Mike said:
Since you don't have twrp you probably don't have a backup, which what I'm going to suggest will bring you back to stock and may lose everything. Though it's better than a bricked phone. Since I never did the flash-all.bat you may lose your stuff on internal SD. In this link, download the correct image your phone was on (under angler) and if using windows use the flash-all.bat in fastboot. If you're phone isn't 32 GB, extract all from zip and flash everything except user data. Forgive me for assuming you may be new. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
,
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Do you get the error on all that you try to flash? Maybe just try the recovery img only to see if you can at least get that. If that works you should be able to sideload ota through recovery. With having a locked bootloader you might be at a loss. But on the flip side, having everything locked and not rooted you should be ok for warranty replacement.
avansledright said:
Tried that. Continue to get the "Remote: (device is locked)" error every time it tries to flash a new image.
I'm not worried about losing any data on the phone. everything is backed up in the cloud.
Click to expand...
Click to collapse
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Fastboot is useless since your bootloader is locked. Try to ADB sideload the latest OTA image from Google and see if it will boot.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Ahh, missed that in your first post. I'm not sure how you can get recovery going if it's bootlooping when you access it.
Sent from my Nexus 5X using Tapatalk
avansledright said:
How would i get into ADB mode without being able to boot into recovery? I thought of this as well but haven't been able to find a way to boot it into an ADB mode
Click to expand...
Click to collapse
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Fe Mike said:
Check out this thread at post number 268 they mention using adb through mtp mode when not able to use recovery.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page6
Click to expand...
Click to collapse
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
avansledright said:
Tried running through those steps. I can't even get a temporary boot of TWRP or stock recovery continues to bootloop even though WugFresh claims it was successful. Tried doing it manually via Fastboot and continue to get the error in flashing.
I just received my replacement phone. So I might just call it a day on this one. :crying:
Click to expand...
Click to collapse
Good to hear about replacement! There are a few people in these forums that have a brick and can't get out of it. I thought you couldn't Hard brick these phones unless that was your goal. And most of these users who have bricks don't even know what causes it. Just a random reboot then loops. Kinda scary.
I am using Andriod Oreo. Im locked out of my phone. I use a lock screen PIN. My phone says, with 3 more wrong attempts, my phone will be wiped. I would like to recover my data.(I do not have a custom recovery installed)
Here's what I have done till now.
1. I have installed adb and fastboot.
2. My device is recognized under fastboot while my android is in the System boot menu.
3. My device is not recognized under adb.
4. Before getting locked out of my phone, earlier, I have tried enabling "developer options" and "usb debugging" as well. I think both should be enabled. (I am not sure though)
5. I have tried using apps like mobogenie and moborobo as well. They don't have the latest oreo support. Even Dr.Fone doesn't support my device.
My device details: Moto G5 plus :with Android Oreo 8.1.0 update.
Guidance of any sort will be very helpful.
Thanks in Advance,
Shaen
Ok so you have fastboot. Running "fastboot devices" shows device?
If so, download latest twrp and "fastboot flash recovery twrp.img" (or whatever yours is named as, I usually rename mine to twrp).
After twrp is installed, flash the unlock lockscreen zip:
https://www.google.co.uk/amp/s/foru...o-unlock-android-lockscreen-pin-t3619871/amp/
Cupcake 1.5 said:
Easy, flash the zip to unlock lockscreen.
I you cannot get twrp flashed or use adb/fastboot, simply boot into stock recovery (power +volume -) and reset phone. Sorry, but if you alll out of options, you have to factory reset.
Click to expand...
Click to collapse
Thank you for your reply.
I do not have twrp installed. I am not able to use adb. But I am able to use fastboot.
With the above mentioned, is there a way where I can either bypass the lock screen or I can recover my data.
And, Sorry, i do not understand "flash the zip to unlock lockscreen." , being an amateur.
Thanks again,
Shaen
shaenthangaraj said:
Thank you for your reply.
I do not have twrp installed. I am not able to use adb. But I am able to use fastboot.
With the above mentioned, is there a way where I can either bypass the lock screen or I can recover my data.
And, Sorry, i do not understand "flash the zip to unlock lockscreen." , being an amateur.
Thanks again,
Shaen
Click to expand...
Click to collapse
Sorry, I changed my post after you had seen it.
Ok so you have fastboot. Running "fastboot devices" shows device?
If so, download latest twrp and "fastboot flash recovery twrp.img" (or whatever yours is named as, I usually rename mine to twrp).
After twrp is installed, flash the unlock lockscreen zip:
https://www.google.co.uk/amp/s/foru...o-unlock-android-lockscreen-pin-t3619871/amp/
Make sure you have the Moto drivers installed on pc.
If you have issues with fastboot not flashing twrp, use this one, it has never failed me:
https://forum.xda-developers.com/showthread.php?t=2588979
Cupcake 1.5 said:
Sorry, I changed my post after you had seen it.
Ok so you have fastboot. Running "fastboot devices" shows device?
If so, download latest twrp and "fastboot flash recovery twrp.img" (or whatever yours is named as, I usually rename mine to twrp).
After twrp is installed, flash the unlock lockscreen zip:
https://www.google.co.uk/amp/s/foru...o-unlock-android-lockscreen-pin-t3619871/amp/
Make sure you have the Moto drivers installed on pc.
Click to expand...
Click to collapse
Thanks again !
Yes. fastboot devices - shows my device.
In the conditions mentioned in the link, I have a problem . My bootloader is not unlocked.
Is there any other way around?
shaenthangaraj said:
Thanks again !
Yes. fastboot devices - shows my device.
In the conditions mentioned in the link, I have a problem . My bootloader is not unlocked.
Is there any other way around?
Click to expand...
Click to collapse
You would have to unlock bootloader.
First try this. Uninstall the fastboot/adb setup you have, if it is an installer one. And install the one I linked above. Now try adb again with device booted.
With this adb installer, you can simply open a command prompt and type "adb devices". It's a system wide adb install.
If you still have no adb, you have only two options. 1) unlock bootloader and do as I said above or, 2) factory reset in stock recovery and lose data.
Unlock guide:. https://www.google.co.uk/amp/s/foru...-unlock-bootloader-moto-g5-plus-t3573879/amp/
Cupcake 1.5 said:
You would have to unlock bootloader.
First try this. Uninstall the fastboot/adb setup you have, if it is an installer one. And install the one I linked above. Now try adb again with device booted.
With this adb installer, you can simply open a command prompt and type "adb devices". It's a system wide adb install.
If you still have no adb, you have only two options. 1) unlock bootloader and do as I said above or, 2) factory reset in stock recovery and lose data.
Unlock guide:. https://www.google.co.uk/amp/s/foru...-unlock-bootloader-moto-g5-plus-t3573879/amp/
Click to expand...
Click to collapse
Thank you!
Sure, Will definitely try this out and let you know.
Also, in the point 1 you have mentioned, is there a way to unlock bootloader without wiping data?
Regards,
Shaen
shaenthangaraj said:
Thank you!
Sure, Will definitely try this out and let you know.
Also, in the point 1 you have mentioned, is there a way to unlock bootloader without wiping data?
Regards,
Shaen
Click to expand...
Click to collapse
Got your link!
Will try it out and let you know.
Thank you once again. And bye for now. I appreciate your help a lot.
If there is another way, I'm sure someone else who knows a way will post.
Cupcake 1.5 said:
If there is another way, I'm sure someone else who knows a way will post.
Click to expand...
Click to collapse
Thank you so much for your time. I will update the results of my testing with your detailed steps.
Can you please confirm this. I have downloaded the drivers from the below link for my phone.
https://support.motorola.com/us/en/solution/MS88481
Regards,
Shaen
shaenthangaraj said:
Thank you so much for your time. I will update the results of my testing with your detailed steps.
Can you please confirm this. I have downloaded the drivers from the below link for my phone.
https://support.motorola.com/us/en/solution/MS88481
Regards,
Shaen
Click to expand...
Click to collapse
Just to be sure, use the one's from here:
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
Cupcake 1.5 said:
Just to be sure, use the one's from here:
https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
Click to expand...
Click to collapse
Thanks!
Additional question:
Thanks for your help and I am following the steps mentioned.
It's on my mind that USB debugging might not be enabled. Sorry to put this now.
I thought you should know this. If this changes anything, please let me know.
If it is mandatory, is there a way to enable USB debugging through fastboot.
Regards,
Shaen
shaenthangaraj said:
Thanks for your help and I am following the steps mentioned.
It's on my mind that USB debugging might not be enabled. Sorry to put this now.
I thought you should know this. If this changes anything, please let me know.
If it is mandatory, is there a way to enable USB debugging through fastboot.
Regards,
Shaen
Click to expand...
Click to collapse
As far as I am aware, there is no way to enable adb other than to toggle it within the system.
shaenthangaraj said:
Thanks!
Click to expand...
Click to collapse
Hi, Here's and intermediate update. And a doubt as well.
I have downloaded the 15 seconds installer from :
https://androidmtk.com/download-15-seconds-adb-installer
https://androiddatahost.com/293a2
Installation is completed.
Also I have downloaded and installed the drivers from : https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
The wizard is completed.
But I don't see the drivers in device manager. How do I know if the drivers are installed properly.
Thanks,
Shaen
shaenthangaraj said:
Hi, Here's and intermediate update. And a doubt as well.
I have downloaded the 15 seconds installer from :
https://androidmtk.com/download-15-seconds-adb-installer
https://androiddatahost.com/293a2
Installation is completed.
Also I have downloaded and installed the drivers from : https://forum.xda-developers.com/g5-plus/how-to/how-to-lock-bootloader-potter-version-t3694952
The wizard is completed.
But I don't see the drivers in device manager. How do I know if the drivers are installed properly.
Thanks,
Shaen
Click to expand...
Click to collapse
You should see under android something relating to Moto at least on my laptop it does.
Cupcake 1.5 said:
You should see under android something relating to Moto at least on my laptop it does.
Click to expand...
Click to collapse
I tried again.
I don't have "Android" itself in the device manager list.
Is there something I am missing ?
My is under Portable Devices -> MTP USB Device
shaenthangaraj said:
I tried again.
I don't have "Android" itself in the device manager list.
Is there something I am missing ?
My is under Portable Devices -> MTP USB Device
Click to expand...
Click to collapse
If you can't get twrp or adb, there is little chance of saving your files. You eventually have to factory reset and in future have files on SD card. Because your bootloader is locked, you cannot unlock to put twrp on device because that will also reset phone. Your out of options here.
Cupcake 1.5 said:
If you can't get twrp or adb, there is little chance of saving your files. You eventually have to factory reset and in future have files on SD card. Because your bootloader is locked, you cannot unlock to put twrp on device because that will also reset phone. Your out of options here.
Click to expand...
Click to collapse
Thanks.
https://www.youtube.com/watch?v=HbwVsYQajC0
Is this true.
shaenthangaraj said:
Thanks.
https://www.youtube.com/watch?v=HbwVsYQajC0
Is this true.
Click to expand...
Click to collapse
You need adb debugging enabled as he shows in the YouTube link you posted. You have no way to do that. Also to unlock bootloader, you need the other developer option enabled called "OEM unlocking".