Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Just a quick bump for this thread. I could use some suggestions/guidance.
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Beetle84 said:
To unlock your bootloader, follow the steps from this link: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Rooting is as easy as intalling recovery and flashing magisk.
Click to expand...
Click to collapse
Thank you very much for the helpful info. I am looking through this now. I am curious as to whether or not there is a Linux equivalent to the Motorola USB drivers. I only see Windows/MacOSX.
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Just a quick bump for the day.
PrettyDumbITGuy said:
Another issue that I've just come across is that the Android SDK cannot seem to find my phone when it is connected to my computer. When I run the command "fastboot oem get_unlock_data" I am met with a perpetual <waiting for any device> prompt. My phone does not show up in the file explorer or device manager either despite having downloaded the motorola drivers. Also, I have OEM unlock and usb debugging enabled. Does anyone have any ideas as to what the issue could be?
Click to expand...
Click to collapse
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Beetle84 said:
I hate to ask the stupid question, but you did reboot to the bootloader before the unlock command right?
Otherwise, Linux issues aren't my thing, hopefully someone else can give you a hand there
Click to expand...
Click to collapse
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Beetle84 said:
On windows 10 you have to disable driver verification I'm pretty sure for the fastboot drivers to work correctly. It's been awhile since I've done it so best bet is to google this.
Click to expand...
Click to collapse
I disabled driver verification with the following command "bcdedit /set testsigning off" and then connection my phone. The Win10 machine still does not detect the phone as a usable device. I receive a warning box with the following error "USB device not recognized. The last USB device you connected to this computer malfunctioned and Windows does not recognize it. "
PrettyDumbITGuy said:
.
Click to expand...
Click to collapse
PrettyDumbITGuy said:
Not a stupid question at all. I am very new to phone rooting/android phones in general so the inquiry is warranted.
To answer your question, I did boot to the bootloader after enabling OEM unlock. When in fastboot mode I receive a green prompt that shows a connection and that the phone is in transfer mode. However, when I execute the commands in Android SDK to unlock the boot loader my computer is unable to locate the device. This problem occurs on both Windows and Manjaro Linux.
Click to expand...
Click to collapse
Did you install android tools and android udev on Manjaro
BTK19 said:
Did you install android tools and android udev on Manjaro
Click to expand...
Click to collapse
Yes, I did. The problem I run into on Linux is much the same as the problem that I run into on WIndows. The computer simply does not recognize the phone as a device and the Android SDK tools do not detect the phone. I almost wonder if maybe something is wrong with the phone? Perhaps I purchased a defective device? I know that normally when you plug in your phone to a machine you receive a prompt on the phone asking you whether or not this is a "trusted device" but I receive no such prompt on my Moto G Fast. I'm almost wondering if I should just return the phone and get something else. Perhaps a Moto G8 power or maybe one of the new Nord line of One+ phones.
This may be redundant. But I suggest you try another cord. More often than not I find myself weeding through charge only cords till I find a data cord. Also try using a USB 2.0 port, preferably attached (rear of the computer) as opposed to any front ports or hub.
PrettyDumbITGuy said:
Hey All,
I just got my first Android phone to have a bit of a project for my first root/custom ROM of a phone. I chose the Moto G Fast because it seems relatively easy to unlock the Motorola bootloader and such, but I am still new to this so I wanted to see if anybody here had any suggestions insofar as rooting goes and what custom ROM to use for the phone. Ideally I would like to use Lineage OS but Lineage 17 (current) does not support the Moto G Fast and the release date of Lineage 18 is yet to be announced. So does anybody here have any recommendations for a custom android ROM and maybe some tips/tricks when it comes to rooting/unlocking the bootloader?
Thank you in advance. Any and all advice is greatly appreciated.
Click to expand...
Click to collapse
Unlocking my G Fast was Sooo easy, i asked Boost to unlock phone, no charge! then i 5apped UICC UNLOCK btn under About Phone, done & done.
Related
Hello friends,
How to get into fastboot to relock the bootloader, if my volume button is dead? By dead, I mean the ribbon has been ripped off of the mobo (it was soldered onto mobo).
Since I'm a brand-new noob, the only way I know of and have done is to get into fastboot mode and lock it back up like what I did when I unlocked it. Any other way to lock it, ideally within the Android OS? Since my volume buttons are completely dead, I doubt that I can get into any "mode" other than OS right now..
TIA!
adb reboot bootloader.
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
I would say doing whatever ripped the volume button cable out was what you shouldn't have been doing If you unlocked the phone you have the software you used to unlock, right? What software/guide did you use/follow? Are you using Windows/Linux/Mac? The only way to get to the bootloader w/o the volume buttons (afaik) is to use adb via usb. If you provide more details I can try to help you.
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure?
Click to expand...
Click to collapse
Once you're in adb reboot bootloader, do fastboot oem lock. Opposite of how you unlocked it in the first place
cswithxda said:
I've seen that command in a post from search earlier, but there was no response after that post.
Would you explain the procedure? I am afraid that I might do anything wrong on top of these disasters i've gone thru with this phone
Click to expand...
Click to collapse
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I also saw another line during earlier search: "if they don't know how to setup an adb command, they probably shouldn't unlock their phones"... Looks like I've done what I shouldn't..?
Click to expand...
Click to collapse
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Thanks for your help guys!
btw, anyone found xdadevelopers to load extremely slower in Firefox when compared to Chrome? (just offtopic)
Anyway, I unlocked the bootloader when I was switching to yakju cmd and this folder called "fastboot-and-adb" in which there is both adb.exe and fastboot.exe. I used command "fastboot unlock bootloader" or something alike.
I'll do some more search and learn. Don't want you guys to think of me as a lazy bone who unlocked their bootloader using 1-click toolkit
p.s. edit: in my other thread, someone suggested using quickboot app.
Thanks for your replies guys!
martonikaj said:
navigate your cmd line to the folder with adb and fastboot in it. Hook the phone up to the computer and type:
Code:
adb reboot bootloader
which will make your phone reboot into the bootloader mode. You can then proceed with what you need to do.
I agree with whoever said that. This is another example of people messing with things before reading and learning how they work.
Click to expand...
Click to collapse
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Try adb remount
The ad devices
This should list the serial number
Then all commands should work
Sent from my Galaxy Nexus using xda premium
cswithxda said:
Somehow it says device not found
I do have proper driver (Naked Driver Beta 0.5 by 1wayjonny) that my phone was able to be recognized under bootloader at the time when I could actually get into bootloader. My phone is also being recognized as media device now... I have also turning usb debug on...
Click to expand...
Click to collapse
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Thanks for the help at late night guys. I finally got into the bootloader, thru a mac tho Kinda ironic that I am a supporter of Windows, well, at least a firm user of Windows.
Tried adb remount, it still says device not found
synaesthetic said:
You need to turn USB debugging on, and then type "adb devices" and see if it shows up. It may not using the Naked Driver; I had to install the full Samsung USB driver package before ADB would see my Galaxy Nexus.
If it does show up, then you type "adb reboot-bootloader" and it should boot into fastboot. Then just type "fastboot oem lock" and it will wipe the storage partitions and restore the bootloader lock.
Click to expand...
Click to collapse
I believe that you quoted my "I have turned USB debug on" ;p
Gave up on trying Windows drivers. When I was flashing the Yakju, I tried Samsung full driver, and it didn't work on my machine, i.e., the phone can't be detected in bootloader mode, while the beta 0.5 driver worked. So I decided not to mess with it anymore.
It looks like when the phone is not under bootloader, windows recognize it fine as MTP devices and install proper samsung driver from the internet directly. This allows me to open it up in explorer to browse files and such, but the phone won't show up under adb devices somehow.
Looks like MTP device (when the phone is in Android OS) and the fastboot mode use two kinds of drivers. This is just my assumption, though.
Anyway, finally got into bootloader now with Mac, and it's pretty funny I have to do everything thru command as the volume rockers are dead
And most importantly, thank you guys for your help!
Just another update
It's real funny now that the bootloader is locked, I can't unlock it again cuz I don't have the volume button working, so I couldn't choose YES on the phone.
I'm not trying to unlock it again, but just to confirm if there's really no work around, in case I encounter this situation again in the future
Lucky that locking the bootloader won't erase everything, or I won't be able to flash a ROM with it locked... :cold sweating:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
notrium dweller said:
First I must say, I searched all over the internet for answer to this problem. None of the topics I read had matched my problem.
I want to unlock my bootloader so I can flash custom recovery and get root access.
When I want to access the bootloader ("adb reboot bootloader"), in my phone all goes fine (I see on my phone the Fastboot instructions, etc). The problem is in my computer that fastboot won't recognise my phone anymore. When I want to get the device-id, fastboot is stuck on "waiting for all devices". When I want to see the list of devices, ("fastboot devices"), I get nothing, wether my phone is on bootloader mode or not.
I installed all the LG drivers, including the ADB one. I am in USB debugging mode, and I disabled OEM protection.
Android version is Lollipop.
I need help on this matter, thanks in advance.
Click to expand...
Click to collapse
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
raptorddd said:
not all phones can be unlocked.. search for g4 list of bootloader unlock youll see the list if yours isnt there you cant . only root 5.1 no twrp.
Click to expand...
Click to collapse
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
notrium dweller said:
I know mine can be unlocked. I actually can get to the bootloader via ADB. The problem is that fastboot won't recognise my phone afterwards. (I believe it's the european version of the H815 model, and according to one-click-root app, my phone can be safely rooted. Also my Lollipop version is 5.1.)
There are other few issues also:
Fastboot won't recognise my phone, even if the phone is not in bootloader mode.
Windows will recognise all of the LG related drivers including the ADB related driver, while the phone is powered on normally.
However, it fails to do so, in bootloader mode. I see non working driver in Windows 7 Device Manager, under "Other Devices" by the name "Android" with yellow exclamation mark. Nothing else.
Still looking for advice...
Click to expand...
Click to collapse
am sorry i cant help ive nver unlocked mine..
Still looking for suggestions, people...
I have the same problem, adb detects my phone but fastboot does not. Same Phone btw
Still no solution until now ? I have the same problems
My device is H815
Hi !
I have had this problem too...solved with strong battle to understand myself...
My solution : when you have installed driver ,when your phone go to fastboot mode and the pc don't want to reconize the phone : on the pc on windows go to harware manager (config panel) and you can see in theory "android" with a "?" ==> you have to install manually the driver by searching somewhere on the harware list "android adb interface " (i don't remember where it is) ==> your phone wil be reconized ! And you will have the 2 lines of ID on the adb comand interface....and follow the tutorial...
I have read hundreds of issues with driver problems when it comes to windows.
Please try Linux instead. There are live distributions like Ubuntu available. Install it on USB stick and start from there.
No driver issues anymore. Just works.
.
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
@Loulou-13 , now i can see my device-id - solved -
but now have another problems, my imei is not match with my device-id ...
my device is H815
yes...i know i have sent an answer too late ... but my solution is one of this problem and eventualy can be useful for other people.
for your new problem ,what happen ? .......have you enter the corect number ,without space or other ?
Loulou-13 said:
@steadfasterX it need some knowledge for to use Linux OS for adb thingsv (unlock bootloader ,instal TWRP,rom,apps...etc...) ? maybe you can do a small tutorial for to help ?
For windows i have found these pictures for an eventual help (see ZIP on attach file)
Click to expand...
Click to collapse
Well there are hundreds of guides out there just use google...
adb and fastboot working the same way under Linux so there is no need to have a specific guide for linux.
I haven't tested that guide here but it looks very good as a starting point:
http://forum.xda-developers.com/showpost.php?p=44739402&postcount=1
As said there are other maybe better guides but Google will tell you.
.
@steadfasterX thank for your link ,it's useful for people who have problem and read this thread
It's not for me .... i have my bootliader unlocked ,twrp...( and this fabulous Imperium MM rom !!!! )
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Make sure that the drivers are installed properly from the SDK. Installing the SDK is not enough. Look in device manager and look for a yellow symbol with exclamation mark next to any Android device. Right click and get to select driver and point to "Google usb driver" that you extracted from the SDK then select either bootloader or ADB driver depending on what mode your phone is in when doing the above. It should then work. Sorry if that is not clear I am doing it from memory and I am not at my computer. Good luck!
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Try "fastboot devices" instead that will tell you of it's correct or not too
smartway4me said:
So I want to root my new phone but my phone won't be recognized with my windows 10 laptop when doing the adb 'partnership' with phone plugged in via usb. I unlocked oem on phone as well as allow usb debugging. I'm following instructions from
a google search of rooting oneplus5t on oreo I believe its from the***********dotcom.I've never rooted a phone successfully as the last time I tried was a galaxy s7 edge in which I found out it was a clone from someone on here lol.
I looked around but can't seem to get past the part of simply entering "adb devices" in the command after installing android sdk tools. Any help,tips,pointers, advice would be much appreciated! Thanks and have a great day!
Click to expand...
Click to collapse
Did you enable ADB debugging in Developer Options yet?
That must be done when plugging phone into your computer while the phone is booted up.
Ok guys I really need you help. I honestly feel like im losing it as I have not been able to make any progress with this. Believe me I have tried other threads to no avail....
Ok so, I bought this phone but the problem with it is that I cant use google pay due to its unlocked bootloader (bought it like this second hand). I'm on really old firmware (6.0.1, 1 September 2016 Security Patch) as you can see very behind from Oreo or whatever the latest firmware is because I cant get OTA updates due to the unlocked bootloader.
I'm literally just asking for a simple, noob friendly guide which will allow we to relock it and update to the latest firmware so my phone will be perfectly fine for work use.
Please guys. Apologies if I sound annoyed but this has been bugging me for ages. Let me know if I should add anything else.
Much appreciated guys!
EDIT: I Used this guide: https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190 and followed it exactly and enable USB debugging but keep getting "<waiting for any device>"?
bump
Hmm, with the 'waiting for device' issue, do you have the Motorola drivers installed on the computer? https://support.motorola.com/uk/en/drivers Also, if you are running Windows 10 or 8.1, verify that you have driver signature enforcement disabled on your computer, so the Motorola fastboot driver can load properly: https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/ or you can try to manually load the fastboot driver when your device is connected to your computer. This should then help your computer communicate with your device when you boot your device to the bootloader for flashing the stock ROM.
Verify also that you have a high quality USB data cable (preferably the original cable) and that you've got your device connected to a powered USB 2.0 or 3.0 port. Double-check the communication between your computer and your device - boot your device to the bootloader, connect to your computer. Open the ADB terminal and enter 'fastboot devices' (without quotes) into the terminal. Press Enter. If communication is working, this command should return your device serial number.
For that guide as well, you do not need to be on a custom ROM to follow it. If you do get your device talking, then extract the stock ROM as per the guide to your ADB folder, and execute both sets of commands to re-lock your bootloader. Be aware that the re-locking will erase your device, so back up if you have not already. OTA updates are not dependent on unlocked/locked bootloader status - as long as you have a firmware build that was deployed on the retgb software channel, you should get OTA updates regardless of whether your bootloader is unlocked or not. However, as you correctly point out, Android Pay does care about the bootloader unlocked status, however, rooting with magisk (to hide your bootloader unlocked status) may help you get Android Pay working if you want to keep your bootloader unlocked. Depending on your work IT requirements though, you may want a locked bootloader and no root to be compliant with the IT regulations.
Good luck either way.
echo92 said:
Hmm, with the 'waiting for device' issue, do you have the Motorola drivers installed on the computer?.
Click to expand...
Click to collapse
I have now installed the program but get "There are no updates for your device at this time. Current Version: N/A"? My USB debugging is enabled.
Thanks for the detailed reply mate. Im going to get some new cables and follow your advice. Might take me a few days as i'm busy with work but definitely am looking forward to fixing my phone once and for all!
Omg it works. I downloaded the Motorola program and opened up adb minimal fastboot whilst in usb debugging. I just pasted everything and it started to work!...oh I also held the volume down button whilst the phone was turning on so it went to a screen with the android mascot. Then I pasted the codes to adbmininal fastboot.
Thanks for all you help mate !!
You can get OTA updates even if your bootloader is unlocked.
Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.
PrettyDumbITGuy said:
Hey Everyone,
I've posted before but the thread died down and I'd really like to figure this out just for curiosity sake. A couple of months ago I purchased a Moto G Fast as my first root/Custom ROM phone and was never able to get the boot loader unlocked. I have the Android SDK downloaded, the Motorola drivers downloaded, USB debugging enabled, USB mode set to data transfer, etc. However, every time I try to unlock the bootloader the phone is not detected by the Android SDK. My computer detects a device, but does not know what kind of device it is. On the phone itself I never get prompted for a USB connection (from what I understand you usually get a "trusted device" prompt). I've tried this on both Linux (Manjaro) and Windows with the same result (or lack thereof). Also, just to be clear, I am booting the phone into fastboot when trying to unlock the boot loader. Does anyone have any help or suggestions? Also, I'm not sure which ROM to go with. I'd like to run Lineage on the phone but it does not appear that this phone is supported in Lineage 17. Any ROM suggestions as well?
Thank you so much for any suggestions. I appreciate any help that can be offered.
Click to expand...
Click to collapse
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
sd_shadow said:
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?
PrettyDumbITGuy said:
Thank you for pointing me in the right direction. Currently pouring over this info as we speak. At first I was inclined to think that this phone simply could not be unlocked (bought from Amazon marketplace and unlocked for all carriers), but even if that were the case the phone should still at least show up as a device either within my PC device or within the Android SDK command line tools. Perhaps I am wrong?
Click to expand...
Click to collapse
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.
sd_shadow said:
If you are connecting the phone to PC while already in bootloader mode, you don't need USB debugging enabled or USB mode set to data transfer.
There won't be a "trusted device" prompt if device is in bootloader mode.
If windows makes a connecting sound, it will be listed in device manager, if the bootloader screen doesn't show usb connected, that's a problem
Could be a bad usb cable, or bad usb port on the phone.
But none of that may matter, in settings/about phone it should say which software channel it's on something like Amazon, Retail US,
or it may say on the bootloader screen in the baseband or bootloader version.
Click to expand...
Click to collapse
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?
PrettyDumbITGuy said:
Software Channel returns as "US Retail" and Software Variant returns as "Retus" (which I think is normal?) Should I turn USB debugging off and the boot into fastboot?
Click to expand...
Click to collapse
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?
sd_shadow said:
You should be able to unlock US Retail, the usb settings don't matter in bootloader, but it's not in fastbootd is it?
What does the fastboot screen say?
Click to expand...
Click to collapse
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.
PrettyDumbITGuy said:
I apologize for the delay on this. The end of the week got pretty hectic at work.
To answer your question, the fastboot boot menu reads as follows:
AP Fastboot Flash Mode (Secure) - In red text
BL: MBM-3.0-rav-retus-c7bbc04d8e-210215
Baseband
Product/Variant
Serial Number
CPU
eMMC
DRAM
Console (NULL): null
Tools Mode Config: DISABLED
Power OK - in green text
oem_locked
Transfer Mode: USB Connected
The sections that are lacking in detail are sections I figured weren't relevant since they are phone specific (hardware) sections.
Click to expand...
Click to collapse
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
sd_shadow said:
Baseband and product could be relevant, not likely though.
I would reflash the firmware with Lmsa rescue
Skip the device details when asked just go straight to rescue.
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com
Click to expand...
Click to collapse
So I went through that post and installed the Smart Assistant. I attempted rescue but the application simply does not detect the phone in fastboot mode or in debug mode. I am not sure what the issue could be. I should probably just send this phone back and get a different phone.
PrettyDumbITGuy said:
. I should probably just send this phone back and get a different phone.
Click to expand...
Click to collapse
I agree
sd_shadow said:
I agree
Click to expand...
Click to collapse
Thank you very much for your time and assistance. I truly appreciate it.