Related
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before. Honestly though, I feel like I'm at end. I've scoured Google & xda-dev for 5+ hours now and I can't find a single answer that works. So here's my "special" problem:
Info: Windows 7 Home Premium 32-bit
Kindle Fire (previously) temp rooted with BurritoRoot. Installed TWRP 2.0, firefirefire, google-framework.apk, and the rest of the lot, then de-rooted.
Yesterday, I realized that the Music tab on my KF was crashing. I was literally unable to look at my music. About half an hour later, I was unable to read books as well. Thinking about it now, I'm pretty sure that it was because I had forgotten to uncheck "update automatically" for the stock kindle apps in the Android Market/Play Store, making it unusable in the stock Kindle OS. Oh well, at least the source of the problems was found.
Of course, being the happy little idiot I am, I thought I should just restore the firmware via stock OS. I could just re-root and reinstall all of my apps, right? Huge mistake. After buzzing around for thirty seconds, Kindle rebooted. Instead of launching into the stock OS for initial config though, it dropped itself into TWRP 2.0 without me even pressing the power button. TWRP, of course, kindly informs me that the entire device is blank.
I fretted for a little bit, then connected my Kindle to my computer. I already have the adb drivers installed, but Windows shows it as Unknown Device.. It also helpfully insists that it has malfunctioned and tells me to buy a new one.
I turned to Vashypoo's KFU. A bunch of threads said it was stuck in fastboot and KFU could could put it back into regular (4000) boot. However, KFU's bootmode menu is unable to find the device, which is in the TWRP menu.
I tried using command prompt to gain access.
Code:
adb shell
then
Code:
fastboot -i 0x1949 idme bootmode 4000
gives me "/sbin/sh: fastboot not found" which is really scaring me.
Back to KFU, I tried reinstalling stock firmware from there. It apparently installed fine (how?). I doubt that it did, but TWRP is showing some signs of an OS in the device (not sure if its the full OS or not). Bootmode 1 now giving me no response (!)
Since all I really need is access to the SD storage to upload the OS, I tried to reinstall the drivers. Windows implores that its "Unknown Device" driver is the correct one. Trying to choose the "Android Phone" driver sens me back to "Unknown Device" for some reason.
I went back to basics. Used the mount function in TWRP to mount USB storage. AS you can probably guess, absolutely no response from PC.
Dearest XDA-devs i reach out to you. I'm at end. I don't know what else to do. If any of you can help me, I'll be grateful. While I'm not a complete noob (know my way around computer root, experienced jailbreaker/rooter, know basic command line) I'm utterly lost at what to do know. At the risk of sounding like a pretentious prude, I'll make a list of accomplishments to help anyone else who happens to have strangely fallen down the same path I have. As always, if you ever need more details, just ask.
nxtfari
-----------------------------------------------------------------------------
[X] Reason for stock app crashes (Play Store auto-updated stock Kindle apps)
[X] Reason for boot loop (I'm an idiot/Restore via stock OS)
If you can able to get to adb shell, you won't be able to run fastboot commands from there. Fastboot commands can only be issued to the KF when the KF is in fastboot mode... adb commands can only be issued when the KF is in recovery or booted to the OS. Also, the fastboot command is on your computer (probably in the same directory as adb). If you are in adb shell, it's going to run executables stored on your KF, so you are essentially looking in the wrong place for fastboot. That's why it's telling you that the command can't be found.
If you can get into adb shell while booted into TWRP, you should just be able to just run 'idme bootmode 4000' to get the bootmode back to normal and reboot. Hopefully, your system is intact and is able to boot up. Otherwise, you need to get back to TWRP and you can probably just 'adb push' the stock software onto your /sdcard partiton and use TWRP to install it.
Thank you so much
Thank you so much,
i have the same problem, and with this on a cmd:
#adb shell
#idme bootmode 4000
#reboot
now I have again a kindle fire ^_^
Thanks again
nxtfari said:
Hello all,
I realize that I am a noob. I realize you can see the "posts=1". I realize that you guys have probably seen the above title a million times before.
Click to expand...
Click to collapse
I think I speak for most of the people here when I say, your valid attempt at thoroughly explaining your problem, how you arrived at your problem, and the steps you took to resolve your problem is greatly appreciated and goes a LONG way towards getting the help you need in a timely and orderly fashion.
If everyone addressed their problems this way, our forums wouldn't be constantly inundated with threads that require twenty replies to fix a simple problem when it should only take a couple at best.
Wishful thinking
Sent from my Amazon Kindle Fire using xda premium
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Solved
Solved.
appearantly the decive announces itself slightly differently in this mode.
solution:
The aur version of adb (arch linux) handles this correctly. no drivers needed.
so for all having problems, with this device, my recommendation for now: archlinux or archbang bang live, "packer -S adb" .. "adb shell"
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
da root
FiltroMan said:
Hi,
you managed to root your A2107A? I've been googling for two weeks and I didn't figure out... Could you please me tell me how you achieve that?
Cheers
Click to expand...
Click to collapse
sure thing.
as always first check, that all batteries are charged. (laptop, tablet, ..)
** first you need to enable usb debugging in the menu.
** then plug it in and check on windows that it is recognized properly.
it should show up as "lenovo(or android) composite adb interface" somewhere in device manager.
otherwise tell me, and i'll try to find the proper drivers. (on archlinux it worked without drivers, so if you fail on windows for some reason, that is an option too,)
** after that you need this:
https://dl.dropbox.com/u/31794772/Root_with_Restore_by_Bin4ry_v15.rar
i don't remember where exactly i found this on xda-deverlopers. credits to whoever put that up in the first place, sry.
** choose option 1 in the script.
follow the instructions on the tool. it will ask you at some point to push restore on the tablet, no worries, this is completely intended you wont loose any data if it works right. just leave all fields blank and hit restore.
congrats, you are now rootet. the device might require a reboot and might do that from itself (dont remember)
:good:
ps: doing backup like this first is generally a good idea: http://forum.xda-developers.com/showthread.php?t=1420351
I have the a2107-F will this root process work too?
valravn said:
I screwed up.
I just experimented with enabling phone mode on that device, after i had it rooted.
so i modified recomipled and signed the framework.apk but i had a typo in my script and the name of the new file is botched up.
My device instantly crashed of course. This is pretty forward to fix once i get access to /system in any way.. also i have a backup of that file on the pc.
Needless to say, without framework it wont boot. I *can* however get into recovery. but there is no adb option in there.
while i am in that menu, the pc recognices the device as "lenovo adb composite" but the adb does not seem to recognize it.
The drivers are set up correctly. the adb worked on the fully running device before the crash. (obviously, since i rooted it that way)
Any suggestions?
and what is the recovery menu point "download cap-firmware" doing exactly?
any help and potential helpfull links very much appreciated, i googled half the night and found next to nothing..
Click to expand...
Click to collapse
valravn,
Can you please elaborate a bit on modifying the framework.apk?
The solutions I found require flashing a whole rom which I wouldn't like to do (looks like I got the tablet with the latest FW).
Your help will be much appreciated.
Thanks.
I think i bricked my ideatab. i tried to update the CWM via ROM Manager unfortunately when i restarted the device, it got stuck on the menu showing "Press and select the Country Code". after pressing and selecting one of the choices it will just restart and return to the same menu.
Can you please help me guys? thanks in advance.
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
maltydog said:
I briefly took over another thread where this issue didn't belong, but since I am still having issues, I thought I would start my own thread. Okay, so I am on Sprint, sideloaded several of the updates, including most recently the Oreo Beta. I have been very happy with the beta, and was looking forward to the update due this week. However, yesterday evening I dropped the phone on the sidewalk and it cracked very badly, and as I am paying insurance with Sprint I want to bring it to a store and have it fixed. Not only is the screen badly cracked, but the keyboard is acting up a bit also.
Anyway, I was getting advice on the Oreo thread about how to do this, and as I said, I had hijacked the thread, but I was at work and didn't get to try this until tonight when I got home. Anyway, I had originally plan to just find the Ota and sideload it, but it was recommend that I use flashall and the full image file from the Essential site. I tried to do that, but when I restart the phone to get into Bootloader mode, it disappeared from the list of devices visible on my desktop and via adb. It was a bit disturbing to me as I am not used to working in Bootloader, previously did anything like this via recovery, and I wasn't sure how to exit the bootloader, but I chose power off, and saw a weird screen with what looked like a coffee cup, and eventually the phone rebooted and seems unchanged at the moment.
I still want to revert to the sprint nougat before I bring the phone in, but I admit I am a little nervous now about the best way to do this. I could use some suggestions. I hope this post is not too long-winded, but I wanted to explain as much of what has happened as possible.
Click to expand...
Click to collapse
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did to flash the stock firmware.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
maltydog said:
I was following those directions, but what happens is that though the phone appears as a device in adb before rebooting, once I reboot into fastboot mode, it is no longer listed. I also noticed that when tried to reboot the phone into bootloader mode with an adb command, instead, it did a regular reboot, and when it did that reboot, it again was no longer listed as a device, because it went into charging mode. So I'm not sure how to keep this from happening.
Click to expand...
Click to collapse
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
kbonnel said:
The reason why the adb command (to go into bootloader mode) didn't work is it is broken when you installed Oreo, that is why you need to do it manually.
When you put your phone into fastboot mode (power button / volume down) plug in your phone into your computer, and from command prompt (make sure you are in the adb folder), type fastboot devices (don't type adb devices) and see if anything replies back.
Click to expand...
Click to collapse
Thanks, I understand now. I can't start this tonight, but I will try the again next time I have time at the desktop.
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
damn it, I read somewhere that there are problems while using adb on the current official beta. There was a command for getting connection again. But I can't find it right now.
Just to be clear. when the phone is on, you enabled USB debugging and plugged in the USB cable and checked the tickbox before you granted debugging access, right? If you don't check the box, there is no access granted after a phone reboot.
take care, I had problems getting through the initial phone setup after I did a factory reset. The Oreo beta still has some hickups. I got it to work after a few reboots. Without finishing the intial phone setup you can't enable USB debugging, you know.
emowing said:
You are probably missing the phone's driver. Download this, Essential device driver for Windows machines. Supports 32/64 bit on Windows 7, 8 and 10., from the essential developer site and install it.
Click to expand...
Click to collapse
Good point on the driver, I wasn't even thinking about that.
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
maltydog said:
Well, my phone was being read when I previously sideloaded updates, so I think I have the right drivers, but I will double check. Can anyone suggest why the phone keeps defaulting to charging mode rather than file transfer every time I reboot it?
Click to expand...
Click to collapse
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes.
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks.
F
iceman#1 said:
that's a typical android habit. charging mode is default.
did you checked the tickbox when debugging window is appearing?
Click to expand...
Click to collapse
Yes, I did, thanks. Trying to reply and it doesn't appear. Edit: Sorry for the multiple posts,they all appeared at once.
Okay, I am back to this now, I had time today. I installed the windows drivers from the Essential site (I am running Windows 10 64 bit) and the device was recognized in fastboot devices. The phone wiped my data and restarted with a setup screen. So far, so good. So I shut down the phone again, turned it on again in fastboot mode, it was unlocked. I went into a CMD screen and typed fastboot devices, and the phone was still listed there. So I opened windows explorer and got to the folder where I had unpacked the image files and also copied the flashboot file. I right-clicked the flashall.bat file, chose run as administrator. When I did this, I got a bunch of error messages that went by so fast, they were practically impossible to read, though they seem to say something about files not found. I didn't see any log file in the folder, so I guess they are not created. I went back to the Essential site and downloaded the zip file with the correct image files again and tried a second time, with the same results. Anyway I have wiped my phone, but still have not reinstalled the Sprint nougat software I need on this phone. Any other suggestions?
Okay, I tried again, and I was able to read the error message. They all said cannot load "filename" no such file or directory. It sounds like some kind of path error, right? I expanded the file from the Essential download for build Build NMI81C into their own directory, a subdirectory of a library where I have been keeping various android files, and I copied the flashboot file into the same directory from the platform-tools download, but only that file. That seems to be what instructions specify.
Also, I notice on this thread https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681/page3 it mentions also using the command "fastboot flashing unlock_critical" but I do not see that elsewhere.
I was able to get flashall to run using the command prompt instead of Windows Explorer. It seemed to run okay, except a couple of items cause me some concern.
I got a message "FAILED (remote: Flashing is not allowed for Critical Partitions)" for the abl.img file.
And the other command "Did you mean to fashboot format this ext4 partition".
Are either of these a problem?
Try running the commands one at a time. Open the flash-all.sh in a text editor and copy the commands.
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
maltydog said:
As I said in my last message, I was able to get Flashall to work when I ran it in the CMD prompt rather than in windows explorer (which is how it was done in the video posted on Youtube, but didn't work for me). My only concern at this point is whether I should be concerned about the two commands posted in the email.
Interestingly enough, my phone did an update to the build NMJ32F as soon as I started it up.
Click to expand...
Click to collapse
Did u not do the flashing unlock_critical?
Airwolf79 said:
Did u not do the flashing unlock_critical?
Click to expand...
Click to collapse
No I didn't. It was not mentioned by anyone but me in this thread until you did.
So far I have received no error messages since I did the reversion to stock. As I said,
I did get an update almost immediately.
I've tried several times to unlock the bootloader and it will not respond to any commands once in fastboot mode. I've tried to follow this guide https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/ but whenever I type "fastboot oem unlock" it just says "waiting for any device" and nothing happens. I have usb debugging enabled and oem unlocking on so I don't know what I'm doing wrong. I have the platform tools from Google installed. I can run adb and type "adb reboot bootloader" and it responds, but after that, no fastboot commands work. I mainly just wanted to root so I could restore my apps and data via Titanium Backup. Is there a temp root solution I can use? Or has anyone else experienced this?
Let me know if you need more info. Hopefully this is an easy one.
What do you get if you run "adb devices"?
thedrizzle said:
What do you get if you run "adb devices"?
Click to expand...
Click to collapse
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
blockhead428 said:
I feel like it's something simple I'm missing. I've never had trouble figuring this stuff out. I've been rocking an HTC M8 on VenomRom since forever ago so it was time for an upgrade. I've looked at several different guides, but some of them seem to be incomplete. Like the guide at the official TWRP page says to power off the phone. Then it says to hold volume up to go into fastboot mode. I tried following those instructions to a T, but that didn't actually do anything. It doesn't say where to put the twrp.img file, it just says to run the command to boot the .img. Getting into fastboot isn't a problem. It's that no matter what I do once it's in fastboot, I just get "waiting for any device". I've tried the OnePlus6t Manager because I thought maybe I needed a one-click method. But again, it gets to fastboot and goes nowhere from there.
Click to expand...
Click to collapse
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes ? I'm not sure if I can put a link on here
DinarQ8 said:
Do not forget to enable OEM Unlocking in Developer options
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I've done that also. Developer options are enabled, USB debugging, and OEM unlocking. Are there newer drivers I need? But if that was an issue, it wouldn't allow me to do "adb reboot bootloader". It'll reboot to fastboot mode, but after typing "fastboot oem unlock" it just says waiting for any device.
blockhead428 said:
ADB: USAGE: unknown command DEVICES
Or do you mean run it while it's in fastboot?
Click to expand...
Click to collapse
In the picture it shows you typed your commands all capitals letters
Dr8ven said:
Just my 2 cents I'm not an expert but it Might be your drivers or when you installed adb did you do it with administrator rights? The first time tried I couldn't get it to work it wasn't detecting the device in fastboot so I reinstalled adb and then it worked
I just rooted mines today but I went off a YouTube video I looked up and they had everything you needed to download in the description. Took about ten minutes I'm not sure if I can put a link on here
Click to expand...
Click to collapse
Try and post it. It let me post the link to the guide in the initial posting. You could be on to something.
This is where I got my version of ADB. https://developer.android.com/studio/releases/platform-tools It's not so much an "install" as it is unpacking a zip archive.
twinnfamous said:
In the picture it shows you typed your commands all capitals letters
Click to expand...
Click to collapse
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
blockhead428 said:
I did not know it was case-sensitive. I just tried again and it seems to show my devices (I'm transferring files off of my m8 which is why it shows two).
Good call, brother! Where do I go from here?
Click to expand...
Click to collapse
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
I used the adb installer from the same video. Once you unzip it. It's an .exe file which I granted administrator rights to install... it installs adb and drivers and it worked for me
That's the video and did it to a T
Another thing don't use power shell use command
twinnfamous said:
you need to be careful in fastboot. One wrong command can lead to a catastrophe.
Click to expand...
Click to collapse
I'm following a video now. I'm thinking I didn't have the ADB drivers installed so I'm trying that now.
Let us know how it turned out ?
Dr8ven said:
Let us know how it turned out
Click to expand...
Click to collapse
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
blockhead428 said:
Still getting nowhere. I thought my problem was that I didn't intall the drivers as administrator. So I did it again, following this video https://www.youtube.com/watch?v=B-XZy27wy5o When I reboot into bootloader, I type "fastboot devices" and it just goes right back to the command prompt. Nothing happens. I guess I'm going to try the old fashioned computer restart and see what happens. If all else fails, I can unplug it from the wall and blow on it, lol.
I swear, I've never been this simple before.
Click to expand...
Click to collapse
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
blockhead428 said:
::sigh:: Still no joy. Restarted pc, ran adb devices and it showed my phone. So i reboot into bootloader, typed fastboot devices and it still took me right back to the command prompt.
Click to expand...
Click to collapse
I was thinking that maybe the latest OTA broke the bootloader unlock process, but someone else in this thread said they just unlocked theirs. I don't understand what the issues is. I've followed this video so closely I could re-enact it in my sleep.
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Nice! For a noob I wasn't too far off lol it just had to be one of those two issues
Enjoy happy rooting ?
blockhead428 said:
Got it! I had two sets of drivers installed so I uninstalled both and it finally recognized my phone in fastboot. My old drivers from my m8 from 2014 were probably interfering with it. I knew it was something simple. I feel like Carl in Sling Blade when they bring him the lawn mower engine and he says "ain't got no gas in it, mmhmmm".
Click to expand...
Click to collapse
Hi I have the same problem, when fastboot it says waiting device. I also had rooted my other phone, so how to find my other driver phone in device manager because I can't find it
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
hackmythinq said:
Hi all; thanks for stopping by,
I've looked through multiple seemingly related threads but have been unable to find adequate answers and I am in way over my head to begin with, so please bear with me. Recently my LG G7 ThinQ became totally unresponsive so I figured I'd just use my old Moto G4 Plus while I work on fixing the G7. Problem is, the phone is locked and I have no idea what my swipe password is and I don't want to just completely wipe the phone as there is sentimental content on the phone which I'd like to access anyway.
The G4 Plus is OEM locked but I can access the bootloader, USB debugging is enabled, and I have an SD card. It is "athene_retail," operating on Android 7.0, and I do not have TWRP or CWM or the like installed on the phone. My PC is running Windows 10. Part of my problem is I'm not entirely sure how all this is supposed to work, but after hours of disorganized research I decided this thread was my best bet: https://forum.xda-developers.com/showthread.php?t=2620456 , so I have downloaded a lot of files and whatnot but am struggling with troubleshooting myself as I am likely not using them properly anyway. I tried the simplest-looking Methods -- 1 and 5 -- without success.
The problem I seemed to run into with Method 1 is at step #4 with "Apply update from ADB" and "Apply update from SD card" in Recovery Mode. What would happen is I'd "mount" the "/system" and proceed to choose one of the aforementioned "Apply update" options and the screen would just go black and then after a few seconds it would revert to a "No command" screen. Reading more into Method 1's instructions it seems like I might have to install TWRP or CWM onto my phone in order for this to work, but if that's right, how am I supposed to get them onto the phone if not through those options?
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
LMSA has a pin reset, you could try that.
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
hackmythinq said:
The problem I kept running into with Method 5 is "adb shell" would return "error: closed" and I haven't been able to determine why exactly. I opened cmd.exe from within the ADB folder and got "daemon started" and was able to attach device "emulator-5554" but after this point even "adb usb" would return "error: closed." I tried killing and restarting the server and a couple other potential solutions I found but to no avail. I am using
Code:
Android Debug Bridge version 1.0.41
Version 30.0.3-6597393
Any help would be greatly appreciated! :good:
Click to expand...
Click to collapse
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
[email protected]!$h said:
"emulator-5554" ? This is a emulator and not your Moto G4. Are you using any emulator? If so, stop it and connect your G4.Once your G4 is connected to ADB, it should show your G4's Serial Number in list of devices attached.
Click to expand...
Click to collapse
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it? In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
hackmythinq said:
Thanks for the reply.
That did seem odd but I'm a noob, so I do have BlueStacks installed on my laptop but I don't believe it was even running at the time. Could that be it?
Click to expand...
Click to collapse
Yes, it could be bluestacks. It's adb connection runs in the background.
In which case, that means my laptop wasn't even recognizing the phone at all to begin with? Hmm, ok, well I think I found the problem: when I click "adb.exe" a black screen (possibly cmd?) flashes on-screen for a tiny fraction of a second and that's it. Should it be doing something more than that? Does it have a GUI?
Click to expand...
Click to collapse
adb doesn't have any GUI and cmd flashing for a second is general behaviour when you run adb.exe. You should always run it from command prompt like you did before.
try installing Moto drivers : https://support.motorola.com/in/en/drivers
if already installed better try different port/cable/pc