MHL/OTG in recovery? Or ADB CWM backup possible? - Android Q&A, Help & Troubleshooting

I have a Tmobile Galaxy S5. The screen will not turn on but I believe the digitizer is working since it still vibrates when I enter try to swipe my pattern lock, wish I had left it as fingerprint locked. The phone is rooted and has CWM. ADB lists the device as offline when phone is booted up but if I boot into recovery ADB works but I couldn't find any way to command cwm to create a backup. I tried screencast with adb but the S5 must capture screen shots in a different way than screencast was designed for. I'd like to just create a CWM back up some how. I dont know if the digitizer is reading the touches in the right spot or not either since I havent been able to unlock the phone by attempting to swipe the lock pattern blindly. I was thinking maybe I'd buy an MHL/OTG adapter and hopefully be able to navigate the phone but they all seem to be hit or miss if a mouse will work while using HDMI and I cant find any info if MHL and OTG even work while in a recovery or not. Any info or ideas are greatly appreciated.

Related

[Q] LG Vortex stuck at boot screen, can anyone help to get into recovery mode?

I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
EDIT: I've gained access to the SD card by plugging it into an external reader. I can see the recovery image that clockwork made. How can I get the phone to boot into it?
theevan117 said:
I rooted my LG recently to get rid of the crapware that was on by default. But, of course, it wasn't enough for me. I tried to flash a new ROM, and everything went to hell. Now the boot screen won't go past the LG logo. Does anyone know how to reset the device back to factory standard?
Hard reset doesn't work (home + volume down / up + power)
Windows/Linux doesn't see the plugged in device.
adb doesn't see the plugged in phone
I tried to put cyanogenmod on, which was probably a bad idea. I've heard that this problem may be irreperable, and I just want to see if there's any way to avoid having to try and deal with Verizon.
Before flashing (using rom manager), I made sure to choose the backup the current rom option. I've heard that I should be able to restore that backup, but there's no way to actually connect to the phone at the moment.
Any help would be appreciated.
Click to expand...
Click to collapse
LOL wow i just did the same thing ... i am "was" experimenting with the optimus v cyanogen rom and now im stucc at the skate droid screen.. any help would be nice
msg me for help got my self out of it
u got out that situation? i installed a app and my phone needed to reboot now im stuck
I need help. Vortex stuck on LG logo after i flashed a rom using rom manager!
Please Please help!
infamousr60z said:
msg me for help got my self out of it
Click to expand...
Click to collapse
Consider posting how you did it here for everyone to see.
naenee said:
Consider posting how you did it here for everyone to see.
Click to expand...
Click to collapse
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
[Solved!]
s3rvant said:
Yes, please do post it. I attempted the LOL 1.4.2 rom for Optimus One and am now in this same situation. I have a working rom on my sd card if I could just get to the recovery screen.
Click to expand...
Click to collapse
I read a few posts mentioning that they were able to reset their phone using their ac adapter, but I hadn't any luck trying it that way, until a good friend of mine used some google-fu to determine that the order in which you do things matters! Here's the steps I had to take:
Remove battery from phone
Begin holding power, volume down and home
Plug phone into ac power WITHOUT LETTING GO OF BUTTONS (wasn't easy for me either)
Phone should boot into recovery (in my case the custom recovery)
You can let go of those buttons now
Install battery
Flash your phone and rejoice!
THANK YOU! The part I wasn't getting was the plugging into A/C while holding the buttons down...you're a lifesaver!!!
This did not work for me. I tried putting the phone into recovery mode, but it still just booted up as normal. I'm running out of ideas and patience here...
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Lgtools
estoy en la misma situacion, yo cuento lgtools de Setool Box3, la cual soporta lectura y escritura de sistema de Lg vortex vs660, pero no logro que me lo detecte para cargar firmware completo, mi problema fue que flashe el recovery desde el ROM MANAGER y se queda en el logo.
I recovered my friend's phone using the following procedure
I just fixed a friends phone so I thought I would share in case it helps anyone. This is for the LG Vortex on Verizon. Might work for other carriers.
Download and install the Vortex drivers from LG's mobile support site www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Download and install the LG Mobile Update utility www dot lg dot com/us/support/mc-support/mobile-phone-support.jsp
Run the LG Update app and make sure your phone is up to date. You can also try the Recover option if it can't update. This phone's firmware was up to date.
Install the Android SDK from google.
Access backdoor recovery through ADB
Plug phone in to laptop usb
Press and hold down the volume down key, the home key, and the power key at the same time. Keep them pressed until the screen goes black then you can release. If it goes in to some other visible recovery you can simply skip some of these steps
At this point your computer should start to recognize the phone and go through a series of driver installs
Once that is complete you should be able to go to the command line and enter the ADB shell
Follow the procedure at the following link to get the clockworkmod recovery installed
androidforums dot com/getitnowmarketing/330813-all-one-recovery-thread.html
Once you are able to boot in to clockwork, immediately do a backup. Then clear your data, cache and dalvik cache, then reboot. This won't always work, but many times it will allow you to boot a ROM that gets stuck booting (like this phone). If that doesn't work then just go back to recovery and utilize a manual ROM flashing procedure you can find on many forums.
This process worked great on this phone so hopefully someone else may have similar luck.
Sorry for cutting up the links, i'm new to the forum. Just replace the "dot"s with . obviously.
Try this worked for me
Here's a different method of unbricking your vortex V660. With limited support and methods for this device it seems to make everything more complicated in finding a soluttion around certain but complex problems. I tried to use some of the other metheds listed on android central and XDA...such as, taking the battery out, holding home, vol -/+ and power key at the the same time the phone back in while it was connected to the computer. I wasnt able to get anywhere with these methodes,I also thought qbout trying the unbutu method to unbrick it then I thouht that was to much of an effott. I read all the comments and differnt methods and decide it wasn't worth the risk, I re-woked a different method for unbricking, there's prob about a 90% possibility of it working for your LG.This just happenes to be my own solution or workaround if you find yourself screwed like i did with no type of support.
The reason this didn't work was because I didn't have cwm installled nor did the phone have the original firmware installed, my mistake, I wiped that off too, happenes when you have to much to drink lol, the hard reset buttons were a no go as well since they take you into cwm or the orignal firware from verizon {all mine did was take me to a black screen because there was nothing there for it to load.} Some how or another all was wiped clean and I was in a catch 22 while being bricked. I found the vs660 recovery firmware but I knew i really didn't need to install it so i didn'nt.The bricked happened after I installed Titanium Backup then uninstalled launcher pro so then I restarted and got to the point where the ring Fire or boot animation was trying to load ,and it just just hung there. I don't care for the app launcher pro I would rather use awd launcher, if u haven't noticed you have to pay for the pro version of launcher pro just to rezize widets, so im wondering why this app was added to the Rom Cyan7.2 in the first place. So with no cwm, no stock image, and no way to make an sdcard boot into m to unbrick it my hopes and last resort were to pray that.I had usb debugging enabled.
First thing you have to install is called jdk-7u3-windows-i586] the other file called installer_r_windows wont't allow you to install until the install of JDK is complete.It'd ok to lauch the installer-r26-windows first because it ill drnf you directly to the site to downloadthe JDK file. Install these two programs first, (google how to ADB tutoria if needed? So after downloading that you will need to download the right drivers (for the voerex) Software name (Driver_WHQL_ML_Ver_4.9.7_All_Win7_LGEAll)(Google Search It)} There's 1 other thing we to have to do before seeing if your decice is listed in ADB. We need to add a line to the Envioronment Varibles section under System Variables at the bottom. Here's how to get there in Win7, right click on my computer, advanced tab, at the bottom Environmental Variblesm, click itlook down under system variables and scrooldowm until you see something called Path and add this line to end of it, ofcourse clickit edit then copy and past his line including the semicolon ;c:\android-sdk-windows\tools;c:\android-sdk-windows\platform-tools now save it amd exit. The reason this is done is so we won't have to contantly navigate through cmd prompt to the directory and list commands. This is prevent you from have to navigate to the folder evertime u want to run the program or any cmds. Now that were all setup lets connect to you phone's data cable to the pc and the phone, and again make sure abd debugging is enabled. Settings, applications, development, the check in the box for debugging, if it's not enabled you will get the turn on usb feature your phone so not what we want. Now opem the cmd prompt run the cmd cd.. then cd.. now you should C:\>, you can run the cmd adb devices now hit enter and you you see a long 14 to 16 digit # then that means your devices is succesfully connected and talking to your PC.That long # should be your MEID HEX# to your phone if you dont see that and you see somethine else then go back though the guide to see if you missed something during setup. If setep properlly in the cmd prompt type adb devices and your phone will automactically show its long#, after that type the cmd adb reboot at which point through cmd promt the device will reboot itself. Here a little secret just because you don't have youtr verison's orignal firmware nor a working ROM on you phone such as froyo 2.2.1 or 2.2.2 doesn't mean anything, you are still rooted and wont have to downgrade to 2.2.1. Side note ( z4root didn't work for my lg vortex, I tried gingerbreak 1.10 and later gingerbreak 1.2 which both worked just fine, z4root just hung on my phone, sry i bounced off topic but i took me 24 hrs of troubleshooting till I got it back up and running.
This method I would say this only applies to the ones that don't have cwm installed on their internal drive it acccidently wiped the original firware off their phones and don't have anything to boot into. I don't have the orignal verizon stock installed, essentially you hit the same buttons on the phone to do a hard reset or to boot into recovery as you normally would. If you neiher on your phone then ADB is your saving grace. Another tutorial I seen was something about installing ubuntu lunux, it just seemed liked to muck work for me, plus I didn't want linux on my box anyways, not til im ready for building a linux kluster later.
let get started...go and download the Adb software which is called Android-debug-brigde...you will also have a visual demo to guide you through the setup) (ADB file) name installer_16-windows,install this this file last to the root of C:/ once done its location will look like this c:\android-sdk-windows ( this is important to make sure you extract the exe to C:/android-sdk-windows (you can take advantage of youtube's a great resourse for viual walkthroughs} or google it,.i have had to do i know's our there , well if you more of a reader search google or xda it will breakdown the core or the installing of the actual files can't post links here but you have to post a minimum if 8 tines b4 you can post links outside this site.
Once all that's setup you need to confirm that its linked properly. Phone off or on during this process I wouldn't think it matters,my devices were on, so conntect you data cable to you usb port and the other end to your phone where you normally power it. This is the time you better hope USB Degugging is enabled. If it is you will see the little Android character and something that looks like a usb icon in the status bar of your phpne, so if you pull down your status bar is will tell your if you are in use debugging mode,. in the status bar depending on where your bricked. if you are in a booploop all its going to do it make that noise of connecting and disconnting. you may have to find fifferent approach to fix it, only solution I can give you if to try home, vol +, and power down til you get a black screen and hope it hangs there there long enough to so you clear it. So it this aproach words on a bootloop let me know in the comments.
Once everything looks good open up your device manager
Just under your computer mame u should see somethig called ADB Interface
under that from the drop arrow you will see android plactform sooner single ADB Interface, click on that and you will see android plattform sooner single ADB Interface, then under modems you will see LGE Android Platform USB Modem, and last at the bottom your youw will see universal serial bus controllers, select that and you should your see LGE Android Platform Composite USB Device, If you see all that that your 100% convered
Now to get your phone out of that nasty brick and we don't need need any firware or Roms to do it...
Open cmd prompt, type cd.. then cd.. again now your in C:\>
now type cd android/sdk/system (note the CD just means change directories) now were in the folder called c:\android-sdk-windows
From this directory is where were going to run our commands since we can't do it in cwm.
type wipe system and hit enter
wipe system you will see a alot of errors like it didnt do anything but that's ok next step
type wipe data hit enter
once done pull cable reboot phone wait to it to come up to where to you have to touch the andoid like your setting up the phone for the first time again, warming u more that lickly will get an FC during setup and it will brick again on the same screen. Repeat wipe system and wipe data again, the gp though the setup on the phone again, if have have another FC one last time so again wipe system then wipe data, this time there shouldn't be anymmore FCs, I have to go through wipe system and data 3 times b4 the FC's stooped and I will able to to to the activaton screen > My phone is a refurb so if would let me past the activation screen this time as when im loading up in CM7. last issue I faced was the accivation screen, Now I did some reading on this and there are a couple of thing you can one of which worked for me., You can tap the four counrers in the clockwise direction which didn't work for me, or what did, I click activcate then entered *228 then hung up, avtivate again *228 hungup, then activate again,*228 hugnup and this time I was able to skip activation anb and was again to load cwm and flash my phone, so its not longer bricked and I dont have to worry about the avivation all though it will comes up U can stip it and It wont keep me from me phone, I have VIOP setup over my 4g LTE, any questions about this type hack just let me know, ( I have an 18 Page Paper about how it works how to set it up, its free and no download charge for the APK) and I will post it. Forwaring the paper 18 pages long and pretty in depth, I dont explain the backend of how it works but just a little, its mainly the frontend and to set it up and all the routing.
I also have video demonistrations on youtube for bypassing the registration of your Nook Color
Channel is under wudamnify
Vortex sux
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Here's what worked for me
corydespain said:
Okay ... so my vortex is nothing more than a paper weight at the moment. When I turn it on, the LG screen comes on for 3 seconds, then the screen goes blank, then it starts over again. I can't turn it off after it starts its boot loop. I have tried using the recovery keys, and nothing. If I plug it into the computer it will turn on and do the loop over and over again, and i still cant power off. I have a 4gb micro with cwm recovery, but i do not know how to get this phone to boot into the cwm recovery. your help would be appreciated.
Click to expand...
Click to collapse
I was in a similar situation and was able to get to recovery by taking out the battery, holding down the buttons required to get into recovery and then while holding down the buttons, plugging the phone into the wall charger. Once it was in recovery I put the battery back in and flashed back to a known good rom. Not sure why this worked over just turning it on normally, but it's worth a shot.

[Q] Completely Stuck

I have been trying to fix this for days, I am not a complete noob and have combed the internet/ forum for an answer and have not found one.
About a week ago I was standing on a street corner and someone from a moving car threw a Samsung Galaxy Player 5.0 at me. It caused me pain, so it is mine now.
No joke.
Having had some experience with rooting, flashing, and unlocking a Samsung S3, I thought I would see if I could get it going.
1. There is a pattern lock on it (couldn't read the grease).
2. The volume up button is not responding (I even took it apart to see if it was just the rocker).
3. It seems that USB debugging is not enabled.
I am trying to clear the Pattern Lock. I can't get into recovery because of the volume button being busted, but I CAN get into download mode and Odin DOES recognize it. I've tried everything I can think of to get ADB to recognize it, but it won't.
Is there anyway to Factory Reset from download mode?
I tried re-partitioning it with a Bit file and that still did not clear the Pattern Lock.
Please help.
Have you tried looking up how to crack the pattern and if you want to get in to recovery, then download ROM manager to reboot into recovery. If the down rocker works then you can navigate to wipedata and cache. But I would get a recovery that supports touch like twrp or philz recovery.
Sent from my YP-G70 using XDA Free mobile app
I have looked up how to crack the pattern, but the answers I have found tell me that I need to be able to make sure that I have USB debugging enabled and then access through ADB.
Go on YouTube and look up how to enable USB debugging through computer
Sent from my YP-G70 using XDA Free mobile app

[Q] Access Pictures with broken screen

Hi,
First of all: I have already read a lot of threads about this topic, but none of them was able to help me so far.
I have a broken Galaxy S3 (GT-I9300). The screen doesn't work anymore. And when I say it does not work, I mean it: Nothing is displayed and it doesn't react to touch gestures any more, it is completely dark. Nevertheless my phone still works. The LED lights up, when I turn on the phone and my computer recognizes the phone. But I am not able to access the data on my phone as it is locked. I already removed the SIM Card to avoid being prompted to enter the PIN, but there is still the screen lock, which i can not pass.
Unfortunatelly I have USB Debugging disabled, so I can not access it via ADB. When i type adb shell the response is just "device not found" and (surprise surprise) when i type adb devices the list is empty.
Is there a way to get my phone to work with ADB again? Tried to start it in recovery mode with Volume Up, Home Button and Power, but that didn't work out either.
I am grateful for every hint
Cheerio
Buntspecht

MHL/OTG in recovery? Or ADB CWM backup possible?

I have a Tmobile Galaxy S5. The screen will not turn on but I believe the digitizer is working since it still vibrates when I enter try to swipe my pattern lock, wish I had left it as fingerprint locked. The phone is rooted and has CWM. ADB lists the device as offline when phone is booted up but if I boot into recovery ADB works but I couldn't find any way to command cwm to create a backup. I tried screencast with adb but the S5 must capture screen shots in a different way than screencast was designed for. I'd like to just create a CWM back up some how. I dont know if the digitizer is reading the touches in the right spot or not either since I havent been able to unlock the phone by attempting to swipe the lock pattern blindly. I was thinking maybe I'd buy an MHL/OTG adapter and hopefully be able to navigate the phone but they all seem to be hit or miss if a mouse will work while using HDMI and I cant find any info if MHL and OTG even work while in a recovery or not. Any info or ideas are greatly appreciated.
Incase anyone searches this, I have had no luck getting HDMI to transmit and use a mouse at the same time. Also the recovery will not transmit in recovery mode.
Joe333x said:
Incase anyone searches this, I have had no luck getting HDMI to transmit and use a mouse at the same time. Also the recovery will not transmit in recovery mode.
Click to expand...
Click to collapse
Sorry you havent got any response, but could you help me?
when you say " recovey will not transmit in recovery mode" do you mean that the mhl will not work when you enter recovery mode? i know it seems obvious but im about to try the same thing
thanks best regards
Sperare said:
Sorry you havent got any response, but could you help me?
when you say " recovey will not transmit in recovery mode" do you mean that the mhl will not work when you enter recovery mode? i know it seems obvious but im about to try the same thing
thanks best regards
Click to expand...
Click to collapse
correct no MHL in recovery mode you cannot use a mouse or external display while in recovery

EMERGENCY (not histeric)Password not recognized on Xiaomi Redmi Note 3 -Fastboot mode

Hi there XDA community,
I am turning to you with a specific question that I have regarding the issue with my Xiaomi Redmi Note 3 from 2/2017.
I had an accident where the phone fell on the side directly on the Volume Down button and it was constantly pressed in. I used to have issues with waking up my screen as it would automatically switch off if I didn't press the Volume Up and Back buttons simultaneously. Otherwise the phone is still in full working condition and I managed to unstuck the Volume Down button since.
When I ended one phone call, the black screen wouldn't turn on no matter what, so I got frustrated and played with the buttons and entered the Fastboot mode. I didn't do anything there so I just left and turned the device back on normally.
I was prompted to enter my password, which is always the same 4 charachter all-numbers code and it wouldn't get recognized by the phone no matter what. I am sure I typed it in correctly.
Ever since, I have been locked out of the phone and am looking for options to gain access to it.
The Android Device Manager is of no help, I do not have any Forget Password buttons, my bootloader is locked as far as I know because I didn't change anything there and the USB debugging is disabled.
Do I stand any chance of accessing my data without losing it, perhaps with use of some special software tool or passcode remover?
I don't know exactly what my firmware is, but it probably is MIUI 8 or 7.
Thank you very much for your help and advice!
Wish you to end 2017 being your bestself possible!
Odinlo
Did you tried this ?
http://en.miui.com/thread-292962-1-1.html
Hey,
the Android Device Manager is of no use because the phone is too new to change the password.
Also the recovery mode is inaccessible because the bootloader is locked any my USB debugging is not enabled.
Can you help yourself with the Fastboot mode in any way?
Also, I don't understand why something like this would happen and what is the password now that the device demands.
Do you know of any software tool that would recover all the data after restoring the phone and deleting all the data?
Thank you very much!
Odinlo said:
Hey,
Do you know of any software tool that would recover all the data after restoring the phone and deleting all the data?
Thank you very much!
Click to expand...
Click to collapse
Wait , what kind off lock is on your device ?
1. Pattern lock
2. MiAccount Lock
3. Lock Screen Password
Here is a tool to remove password :
https://mega.nz/#!10UDXQTI!sZb9wjh07rGAsSbE2YpOWyuu-0Vi4fujbHvSTnyz_I8
Warning!!! I didn't check file against viruses so do check .
How to use:
https://www.youtube.com/watch?v=eDb9BNLmiJ4
Hi Teddy Lo,.
thanks for help, I really appreciate it. It is the Lock screen password on the device

Categories

Resources