Sorry if this is wrong place. I'm new and can't find right place to add this.
When i try to unlock my phone bootloader using adb. I get stuck on waiting for device. I know i installed everything right when i add the adb devices command it show my phone. I even used it successfully used it to turn SD card into internal storage. I'm in android 7.0 just fyi
Related
I am looking for guidance this time.....I have a Nexus s I9020 (t mobile version) and a couple weeks ago I don't know what happened really but i may have been messing around with a newer version of clockwork recovery late one night .... then the phone wouldn't boot past the google screen and I couldn't do anything to fix it... I tried to figure things out the next day and this is a list of things i have figured out...
1. in clockwork it can't mount anything....like anything at all pertaining to the internal memory/storage
2. I was tired and irresponsible
3. I tried fastboot just about everything
4. I tried flashing newer/older versions of clock work......nothing worked
5. I have tried downloading and installing roms via adb and fastboot but an error message comes up...
6. now this I know is retarded but make fun of me as you will... I fastboot locked the device......i know stupid because now when I type in fastboot oem unlock it hangs and does nothing after I check unlock on the phone...
I can get into fastboot mode and it says no boot or recovery img?
now if I had access to the internal memory I would def. be able to go back to stock but there in lies the problem what on earth can i do to make this thing a paper weight?
this is what i'm talking about, the bootloader doesn't unlock it just hangs .... any thoughts?
"w w w.youtube.com/watch?v=C4cS0kMj4AI"
Hey guys,
I really need your help on this one. Apparently my HTC magic does not read ANY SD card anymore after rooting the device and installing European RUU. Its practically unmountable.
Its definitely not hardware based as it's able to partition via clockworkmod. Im thinking it could be a software problem but I can't install any rom because it can't mount any sdcard.
Also I can't flash the ruu rom anymore.. it doesn't detect my device even though HTC sync and adb is connected.
I only have access to adb shell commands. I.e adb shell reboot etc
Fastboot commands doesn't work as it gives error. Some weird remote denied thing.
Please help as I'm really at a dead end and I don't wanna give up doing this.
Thanks guys.
Turn phone off.
Turn phone on by pressing and holding Back + Power.
Write here first 5 rows (all symbols are important)
This info need to understand what type of Magic you have
Hello,
I bought my wife one of these tablets for her birthday. It was running great, decided to root it so that I can uninstall the bloatware that was eating this tablet up after using it for a week. Uninstalled all the happy lenovo stock softs, everything is all good... Well I decided to put JB on this tablet after root stock rom was running great. I made a backup, but somehow I completely crashed the file system, and I can get into recovery VOL+ VOL- POWER, while usb plugged in. I had a hell of a time getting drivers install in windows, and also debian. Drivers are like NOT installing properly, or it will install properly in windows, then I have an error on another device etc. I cannot get past the lenovo splash screen that does nothing, and the only way I can get adb devices to recognize the device, is when it is in splash screen mode on lenovo, but NO other adb commands will work! adb shell will simply freeze terminal or dos. It will not read micro SD card when I boot recovery, linux or windows has no idea how to even read my device when I plug it in while in recovery, im about to buy her a new one. I have googled and googled for days and hours for a fix on this. If you need detail, please ask, and I will gladly give you info. Please help, my wife is super pissed.
Thanks!!!
hey have you managed to solve this problem? I think I have the same issue as you. my tablet just doesn't want to boot normally even after reloading roms.
Hello,
I just came back from my honeymoon and all of my pictures are on my N4. Of course before I pull the pictures, I drop the phone is the screen is cracked and the touch does not work anymore.
I'm really desperate to get these pictures. I've read all over online but my problems are this with all of the help out there:
My phone is the latest 4.4.2 on T Mobile.
It has stock EVERYTHING (bought straight form google), and the USB debugger is not enabled. (next phone I get this is the first thing I'm enabling.
I've been trying to follow instructions online but a lot of items have changed between last year and Kit Kat now and some steps such as unlocking the bootloader seems to wipe out everything on my phone.
I've been trying to use ADB and Freeboot but really havent gotten anymore.
I've also read that I can maybe use a usb mouse to substitute and unlock my phone? USB OTG? How do I know if my nexus has that enabled?
I'm even considering getting a new screen so I can try to replace the current one and get my photos. I dont care what happens to the phone but the pictures are priceless to me.
Is there any thread or guide that incorporates 4.4.2? the more detail the better of course.
Much thanks in advance.
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Shubhamqweasd said:
have u tried getting into stock recovery ?, and pulling files with ADB ??
i think stock recovery has ADB enabled by default ...
Click to expand...
Click to collapse
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
zhanism said:
Thank you for the quick reply.
I do manage to get into stock recovery, I get past the green guy lying on his back, though the method isnt always reliable. I get to the screen where it gives you the options to reboot, apply update from ADB etc.
I select to apply ADB file and it says "now send the package you want to apply..."
However, when I go into the command prompt on my PC, and type ADB devices, and nothing shows.
Do I need to install the drivers that makes the phone a ADB device and not the normal MTP device?
Thank you.
Click to expand...
Click to collapse
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Shubhamqweasd said:
Yes u need proper adb setup on ur pc ..
U can find and install nexus 4 drivers with adb setup from this forum threads..
After u have done that check if you can find ur device using adb from recovery..
If u can find the device by recovery .. Then rest is easy ..
Just follow this link afterwards
http://forum.xda-developers.com/showthread.php?t=2449652
Click to expand...
Click to collapse
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
zhanism said:
Thank you for your help. However, while I have gotten ADB to recognize and list the device, I still have the same problem in that I cant unlock my phone using the screen and so when type something like "adb pull /sdcard/dcim/, i get "error closed"
Is there anything more I can do? These photos are priceless to me.
Thanks.
Click to expand...
Click to collapse
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
acejavelin said:
Get the screen replaced, or do it yourself. ADB in the stock recovery is very limited to "adb sideload" commands only, you can't pull files this way.
Click to expand...
Click to collapse
I have same problem with broken screen, i bought for 56$ full kit on ebay, no need separate glass from screen. took me 1h20min, never done before but what a relief seeing everything working
You do not need USB debugging to transfer files. On windows, open file explorer and with your nexus 4 connected it should appear on the left side as Nexus 4. Or if you have osx use http://www.android.com/filetransfer/.
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