First I'm using a MAC...
Sooo... I dropped my phone (STOCK SGS4GE, No root, Locked bootloader) while putting some things in my car and ran it over. Screen is destroyed, so i can't see anything.
I would like to get all my pics and stuff off the phone, and do a factory reset before sending it back to the insurance company.
Doing the reset isn't that big of a deal as I can mirror the buttons pressed blind on the phone as I have access to another.
I have my SIM locked upon boot... not sure if this matters.
(im pretty sure my phone is in debug mode... also wondering if I put in an unlocked SIM, if i will be able to connect.?)
When I plug my phone into my computer, Android File Transfer (AFT) loads, and then an error pops saying no device is connected.
doing an ./adb devices returns nothing.
Putting the phone into download mode, ./adb devices returns nothing.
If boot into recovery mode, and select 'load update via adb'
./adb devices returns
List of devices attached
cb4cxxx8 sideload
So far this is the only way I can get ADB to recognize the device, but as some of you may know... it appears what I can do is limited; I am unable to shell into the phone etc.
Anything I am missing/Any ideas for me getting my crap off the phone?
Help?
A friend of mine accidentally deleted his ROM on his LS980. I took his phone home today to try and fix it for him.
It still boots into TWRP (luckily). I tried ADB sideload, and I manage to install ROMs with no issue, but the device boots right back into TWRP on its own. I also have access to download mode and tried the LG FlashTool but it doesn't do anything. I've followed the instructions for it and I just get the COM41 port saying "READY!!" and stays there.
Any advice would be greatly appreciated, he's been out of a phone for two weeks now.
Edit: This is the error on TWRP. "E:Unknown File System: 'datamedia'"
Edit: Fixed. I didn't set the phone to COM41 in device manager. Oops.
Hi,
yesterday I got d802 phone to fix it. First the phone was stuck at LG screen with certification error which I fixed. Phone was recognized by PC and i installed twrp on phone. I tried everything (i guess) and now phone is stuck at LG screen and it doesnt move. Now i cannot go back to twrp recovery but i can get to download mode but phone isn't recognized by pc so i cannot flash kdz file to phone. I'm really stuck at this point. Is this real hard brick or is there any way to fix it? Any ideas what should i do or something i can try?
I tried to plug phone in other computers and it's the same thing. My laptop recognized that something is plugged in once but it didn't know what was it so by now. Somehow from time to time phone doesn't go to download mode but it goes in hardware key control mode.
Hope someone can help...
So far i manged to get to recovery mode but adb sideload isn't working. I tried to wipe everything and that didn't help. As we speak factory reset is in progress but I think it's stuck on formatting cache. I hope I'll be able to get the phone recognized in download mode. Any suggestions are appreciated
I have made some progress. ADB is working now and i pushed cyanogenmod and on installation it says that it cannot mount data and cache. I think that main problem is that phone isn't rooted and now I'm trying to root phone via adb. If someone knows anyway to do this that would be great
The title says most of my situation. I've had this since 2012 and some time early last year it just up and stopped booting into android. I have no idea what happened because my girlfriend was using it at the time and she swears she didn't change anything.
Anyways, the bootloader is locked and I have tried to go to recovery and factory reset with no luck. Wiped cache and did nothing as well. I am seeing that windows 7 is sort of recognizing the device. It shows up under device manager as "Android Bootloader Interface"
I've updated the USB drivers and installed ADB as well. When checking the command prompt for ADB Devices, it shows nothing.
I installed Wugs toolkit and it won't even find the nexus either. There has to be SOMETHING that can be done in this situation right?
:EDIT: I was able to unlock it using fastboot but I still can't get it to be found by anything else.
I can get it recognized using the fastboot command prompt, but I can't execute any commands in it. Everything like "fastboot flash boot boot.img" just returns a FAILED message with either invalid argument or no such address or device.
What I am trying to do is just recover it and start using it again. Of course I want to put Android 5.0 on it, but I would be okay with anything as long as it boots, really.
:EDIT: I was actually able to get it to work. I have no idea what specifically had fixed it, but I uninstalled and reinstalled the drivers a few times and ran fastboot and was able to wipe it and install Android 5.0! It was running great!
I realize there are many other threads on this, bear with me please, I was not able to find a solution that works.
-display is broken, shows light but nothing else
-digitizer is 99%? broken, back and menu buttons work, there is some heptic feedback in upper part of the screen
-phone does not have a lock pattern or password, just swipe to unlock
-voice commands work
-phone was rooted a long time ago, I don't recall the mehod, I think the current OS is likely 4.4 but i'm not sure (is there a way to check)?
-I had a custom recovery on it which i think was CWM, again, not sure how to check this now
-I can install apps via web appstore
-At some point I installed a clockroot app (never worked) it's probably still on the phone
-I don't have OTG, ordered one
-I don't want to order a new digitizer
Here are somethings that kind of work and some that don't
-dr.fone shows a USB debug promt with instructions on how to accept the RSA key. I'm guessing USB debugging mode is on but it's not the same computer
-if I have the device in download mode, it is "sometimes" recognized by dr.fone, just says its in download mode and asks to reboot
-if I have the device in recovery mode (i think), it's not recognized at all, does not even show up in device manager
-when phone is just on, it's recognized by the computer, I can browse and backup files (i need to backup google auth app)
-with phone on, its recognized by windows and adb, adb says the device is not authorized.
-however adb does not recognize it if I boot into recovery
I think my best best to just to push the rsa key to the phone in recovery but I'm stuck because the phone is not recognized. I will try re-installing drivers next but I doubt this will help.
Lastly, I wasn't sure if I really do have CWM installed or its stock recovery. So I tried to flash CWM using Odin, with phone in download mode, recognized by Odin, the flash fails with an auth error, i'm reading that might mean the phone is not rooted which is 100% not the case here, maybe the rootclock app is doing something to it.
Any advice?
I'm starting to recall the rooting process a bit and I'm fairly sure I used safestrap method, as I was on 4.4.2-4 NJ something kitcat at the time. So I may not have CWM installed after all.
little bit of progress to report. I'm fairly certain i have safestrap recovery on this phone. So booting into recovery must have been bringing me to the safestrap screen that needs a screen tap to recovery or continue. If I hit power it reboots, if its only 2 options recovery or continue to normal boot, volume down move me to the other option, + power....now adb detects the phone! in sideload mode, lets see if I can do something with this, fingers crossed.
no luck, sideloading seems useless. How can i get myself into recovery!?
I think if I can push the adb rsa key I would be set to use one of the screen mirroring apps. How can I sideload it in?