[Q] Broken Screen, Trying to Recover SMS & App Data - Verizon Droid Charge

First time poster, I apologize if this post is a mess.
I recently dropped my Droid Charge down a flight of stairs. The phone itself still seems to work - I can boot it up, it plays all the proper sounds, and my 7pm alarm even went off today (hadn't had it on to test that before), but the screen is completely dead.
I've already upgraded to a Galaxy Note 3. I had a backup with SMS Backup & Restore from April; same for my Checkbook app - these are the two apps I'm most concerned about. I'd like to get the additional data since April 22.
My Charge is rooted, though I got a lot of walkthrough to do it - I also did the root over two years ago.
I have these links in the chatlog with the friend who helped me root, if that helps at all:
http://forums.androidcentral.com/dr...charge-windows-drivers-w-direct-download.html
http://www.mediafire.com/?yn37uc4z3cx3bl6
http://rootzwiki.com/topic/10515-odinall-in-oneep4d-gingerbread-236-w-cwrimo-kernelrooted/
http://forum.xda-developers.com/showthread.php?t=1172182
Problem: USB debugging was turned off when I dropped the phone. I didn't know any better until I'd already broken the screen. I've tried MoboRobo, MyPhoneExplorer, and Samsung Kies, and nobody sees the phone. It beeps when plugged in, and with Kies the hard keys light up about ten-twenty seconds later, but that's the furthest I've gotten.
I'm willing to boot to recovery and use adb/command prompt/whatever, but I can only find these instructions for other phones, and I'm worried that if I use the wrong phone's menu instructions I'll end up wiping it instead of booting to recovery. I'm also not too clear on if ADB is a different build for different phones... this is my first time doing this.
I don't have a mini-HDMI cable but if that's the better solution I'll get my hands on one.
Any help is appreciated, thank you!

Related

[Q] Phone won't start after attempting return to stock

Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
try putting it back in download mode and see if odin recognizes it if it does do the return to stock agian
fawn87 said:
Hi all, this is my first post here, but I've been reading walkthroughs for a while now. I really apologize for being such a noob, but any help/pity to help a girl figure out if she's just bricked her phone would be greatly appreciated.
I tried to flash a Gingerbread beta I got through one of these forums. I used Odin to root and it seemed like the install went OK, but when the phone started back up the screen went through a crazy colors standby (red, green, blue lines all over it), right after Samsung and before AT&T. This continued to happen at that point of startup every time, in case that's helpful. I also would randomly not send texts even though it looked on my end like they sent. I must not have rooted it properly because I tried to install an app (ROM Manager, I believe) that needed root permissions it said it couldn't get. I decided I was not ready for the phone ROM world and read up on returning it to stock.
To do that, I found this thread:
http://forum.xda-developers.com/showthread.php?t=1116251
I used GTG's Ultimate Unbrick, but again, I must have done something wrong. I downloaded Odin3 v1.70, ran as Administrator, and connected my phone in download mode. I clicked "PIT" and selected infuse.pit, I clicked "PDA" and selected PDA_UCKD5.tar.md5, then "PHONE" and PHONE_UCKD5.tar.md5. The "Re-partition" box was checked. The first time it said it failed. Two subsequent times it said nothing happened. For some reason my phone said it was "Downloading" even though nothing was happening on my computer and it said it had failed. It had been at that same screen for probably ten minutes or so with no progress I could see, and the thread mentioned it might boot loop or something, so I unplugged it. After that, it never started up again.
So far I've tried:
- Holding down power and volume buttons
- Removing the battery for about an hour
- Leaving it on its charger for about two hours
- Plugging it into the computer without SIM, SD or battery
I'm at a loss and at this point I'm pretty sure I've bricked it. I bought it from someone else (it was fully functional up to the point I tried flashing the ROM, although it said it was missing something it needed for a factory reset), so no warranty here. I'm hoping some brilliant dev will have some insight to save me from going back to a dumb phone!
Thanks for any ideas.
Click to expand...
Click to collapse
Check out my thread on the HOW TO. The link is on the signature line. Read it a few times.
re: the first paragraph with the colors -rainbow - it's due to lack of GB bootloaders.
The part where the phone is not responsive:
http://forum.xda-developers.com/showthread.php?p=19445643.
This link give you various method of getting into DL mode.
If it doesn't work,
try a different usb port on the pc, diff usb DATA cable, try a diff computer.
IF the phone is still not responsive, you a need a usb jig to put the phone back in DL mode.
search youtube for "usb jig". There's a vid that shows you how to make one.
gl

[Q] stock i9001 with broken touchpad

Hello!
A few days ago my phone got wet.
After that I can no longer use the touchscreen. Everything else works fine, including unlocking it using facial recognition.
The phone is a Samsung Galaxy S Plus (i9001), with a replaced screen (Crushed it 6 months ago..).
The phone has been dropped many times, but it always worked fine afterwards.
I've already decided i'm buying a new phone, but I still want to try to recover all my data on the phone (messages and appdata is important to me).
So my question is: Is there some way I can access my files? The wifi is off, and so is 3G. usb is set to mass storage mode, so I can't use kies.
Maybe I can upgrade the rom with something that automatically activates some form of filesharing?
Thanks in advance for any ideas.
Also: Do you think there is still hope to get the screen working? When It is unlocked I see that one of my apps is "selected" so it would seem the touchscreen is frozen - not necessarily defective.
I've read that a factory reset can help with this kind of trouble, but I don't want to do that before I have my files..

[Q] MK808B won't start after plugging ubuntu pendrive

Hi,
First of all, great site you've got there, been checking it ever since I laid my hands on my first htc g1.
Secondly, and I hope I'm not double-posting about an issue already raised, as I've screened the threads quite thoroughly.
Here's the issue I have with my MK808B.
I've tried to start it with a USB ubuntu pendrive plugged into the USB OTG (I had saved some files I wanted to transfer, didn't realize it would mess things up).
Regular start up with this hdmi key is Google tv screen > android screen > home screen.
I get stuck at android screen, no matter how long I wait.
Out of nowhere, I tried to use another 2A power supply, as this had been advertised on other threads, no sucess... I also tried to start it with a paperclip pressing the reset button, didn't work...
Honestly, I don't know what to do exactly, I think it might have tried to boot ubuntu out of the usb stick...
I think I have no option left but to flash it (thus losing all that is installed already on it).
Is there any trick that could restore things the way they were? Any suggestion welcome.
Thanks for your time and help.
Solved by flashing
Hi,
Since no mgic trick happened to save the day, I was left with no choice but to flash it.
Used rockchip batch tools, crossed my finger so the stick wasn't a clone with the mediatek chip, flashed stock plus goodies rom, waited 10-15 minutes, and voila!
good as new, got rid of the chinese apps I couldn't even log on, but got a full wipe of my data.

[Q] S4 Help needed (Warning: Long story)

Hey guys, let me just start off by saying I have spent almost 8 hours straight today trying to figure this out and dig myself out of a hole I've created for myself, that being said, I'm going to try and be as detailed as possible so you guys know EXACTLY where I am and what I've tried. This post looks long but that's because it is. It's pretty much my entire day's worth of trouble typed out. So just bare with me and see if you guys can help me out here!
I have a T-Mobile Galaxy S4 model: SGH-M919 it has Android 4.4.2. Now on to the problem: I've had this phone for almost a year now and a few months ago I rooted it. Did a simple Youtube tutorial and used Odin to do the work and everything worked out fine. A couple months down the road (yesterday), after using the phone like a teenager, downloading apps and cluttering it up it started to slow down and not run some apps. After thinking about it I decided to factory reset it. All of my contacts, photos, and videos were backed up on Google so I thought "why not?" Well, this is where $#!% hit the fan.. being rooted then factory reset, right before the phone came online it had me answer two questions about the root. Something to the effect of "Do you want to keep root? (This option is not reversible)" I thought since I wasn't using the features I originally rooted the phone for I figured nah just get rid of the root. So the phone did its T-Mobile boot up and started the Initial setup.
Everything up to to this point was fine until I wanted to log in to my Google account during the setup. Please understand that where I am I have full 4G LTE coverage and have access to a pretty fast and sturdy wifi connection. Well, when it came to the google sign in I entered my email and password and it came up with a message reading "Can't Sign in - Can't establish a reliable connection to the server" (believe me i wish that was the only issue) so after reading that, I thought I'd try with my wifi.. nope. Same thing. Since neither my 4g or wifi worked I thought it was Google's servers so I tried again this morning, same thing. (keep in mind at this point i think my phone isn't rooted anymore.) I call the t mobile store and they give me a technical support number, so I call it and I tell them i cant sign into Google. The gentleman told me he cant do anything because he can tell my phones been rooted. Only thing he suggests is to contact Google, well, the customer care number just tells you go to google.com/support and there's nothing there about my problem.
This is where I dig my hole even deeper. I tried another factory reset and up in the top left corner i still see that root text. Even the rooted android symbol pops up before the Samsung logo or t mobile. Since I saw that I thought "ohh it just didn't get unrooted all the way." I look up ways to completely remove a root and a lot of them require plugin your phone into the computer and using Odin to flash a stock firmware on to the device. I went to plug my phone into the usb port but my computer didn't recognize the usb device, having experienced this a long time ago I searched around for the latest Samsung usb drivers and I installed those. Device still isn't recognized. Let me just note before people tell me to use MTP mode or Developer tools> usb debugging or connection mode.. The only thing that happens when plugging my phone via usb is the phone starts charging and my computer makes the trumpet noise like something is plugged in. Other than that, there is NO notification of it being plugged in. The reason i stress this is because I called Samsung technical support at this point and the guy (not gentleman) treated me like a 5 year old and ran me through all of these options after i told him I already did everything he was suggesting, including downloading Samsung Kies 3 and having it install the drivers. It does not pick up the device either.. at this point I looked up ways to remove the root without the computer. I found out you can just go into the root app "SU" or something and theres a remove root option. I jumped on that opportunity and had it removed. I restarted the phone and all the problems still persist, it even still has the root text on the top left when you factory reset it again. However now, even if you factory reset and select the option "keep root," thinking it would bring back the"SU" app it does NOT.
So lets recap. I have a phone that thinks its rooted and even appears rooted to t mobile but doesn't have any of the root apps or privileges or capabilities to fix my Google log in issue (like the host file in filemanager). And I can't re-root to get that app back because none of my 3 usb ports, 3 different usb cables (one being the cord that came with the phone), or any of the ports/cables on someone else's computer will recognize the darn thing to work on that way! I have all these issues that are supposed to fix each other but I can't do any fixing because they cancel each other out too... I'm at a dead end.
In case this isn't the right forum/website/thread/post area etc.. I have this whole message saved in Microsoft Word document so I can repost it anywhere you guys might suggest better results. Any help/advice will be much appreciated.

Is this a hard-brick?

I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben
Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Categories

Resources