Hello XDA,
It's been awhile since I've made a post, but I'm very unsure about what I'm trying to do.
I have a T-Mobile HTC One S, about 4 years old, that has a damaged display, but I am trying to do a backup to pull out photos and whatnot that I had on the phone before I broke it.
My question is, is there a way for me to do a backup of the whole Android OS and whatever file there is on the phone to emulate it on my Windows PC?
Now for what I've done so far with a bit of back story. The phone broke about 4 years ago when I dropped it and damaged the display and I never got around to fixing it or trying to do a blind backup through the recovery until a few days ago.
I had a friend replace the screen and the phone booted up, except it was soft bricked and was stuck at the splash screen. I was able to get into the recovery and tried to mount the phone to my computer, but it wouldn't let me and I've forgotten what the error message was.
My problem now, is that I've dropped the phone again and the display is broken yet again, but I was curious if I could extract every single file out of the phone and use an emulator so that I can try and get back into it.
Thank you
I've reposted this thread into the Android forums please close. Thank you
Related
Alright so I know that there has been some discussion on this POS model of a phone, but I would love to know before I get the digitizer replaced, if it's a bug or something else.
I guess it started about 8-10 months ago, my brother bought the phone from Mobilicity here in Canada and he let his friend borrow the phone for a call. She dropped it on the cement and the glass cracked. The LCD itself is functioning, but when I got it I had to wipe the device through the recovery menu using Power-X then ALT-L. Anywho every month or so since I got it a few months back for free and long story short it's been glitching out constantly.
Now finally the screen barely works and until I got the "smart" idea to recover it again thinking it would fix but the screen only reads the bottom right side and nothing else. Oh and I'm stuck on that stupid Touch Android to Begin screen. So I'm pretty much SOL'd. Basically my question is this; is it the digitizer, corrupted FW, the phone is just shot or all of the above?
If it's repairable could someone please tell me how to enable usb debugging without the touchscreen or in the very least bypass this Android screen with the keyboard, PC or both? I used Droid Explorer a couple days ago to even control the screen with ScreenCast?
I know of ADB, Input Events, and stuff like that but I really can't figure out what to do. I thought about Clockwork but because the phone has a locked bootloader, I wasn't sure I could even install. Hell I even consider using my other phone to do a NANDROID backup but even that won't work.
So in short what the hell do I do?
I sold my Android phone recently, which was only 3 months old and in perfect condition. However, the person I sold it to was using it for around a month without any problems. Then all of a sudden he said the phone was stuck on the Android logo/Boot up screen and does not go to the Swipe screen to unlock screen. I am assuming he has tried to root the phone or install, flash a custom ROM, but messed it up. Is it possible to find out whether or not someone has attempted (incorrectly) to root the phone or install a custom ROM, causing it to be stuck on the boot menu, by looking at the phone? Note: Power ON + Volume Up/Down is still functional on the phone. Or is there another possible reason as to why this could of happened?
Chances are the phone has been tampered with and incorrectly.
Just buy the phone back for 1/3 of the original cost informing him that he bricked it and move on. You don't need liabilities like that floating around and coming back to haunt you, or worse, shoot/stab you because they're retarded. I never sell a phone to somebody I know is too stupid to use it properly in whatever fashion they'll likely think of. Just something I found out over the years selling used items to idiots on Craigslist and having to play tech support for them later for stupid simple things.
I sent my LG G2 back to LG some months ago as the top of the screen was unresponsive and the screen was starting to get unglued. It was right before my warranty ended. When I got it back, as my warranty was already expired I decided to root the phone (using stump), but I kept the stock rom. Actually the only reason I rooted my phone was to install jishnu's camera mod as I wanted better quality pics and 4k video (and that never happened as I never got to see the lg g2 version of it).
After a couple months, my phone started rebooting with no apparent reason. After a week of this shenanigans, I woke up one morning to a bootloop. I was able to get it in download mode, so I tried flashing the original stock to undo the rom using the LG flash tool method (http://forum.xda-developers.com/showthread.php?t=2663369), but It didn't go through because it said it was a different version of the phone. I even try with the alternative dll provided in the post with no luck.
Two days later, after fighting tirelessly with the phone, I was able to get into recovery (twrp). At this point, I installed a Rom (slimkat) and that seemed to fix the problem. Then, a couple days later my phone started doing the same stuff again. Most of the time, the reboots were quick and it only bootlooped every now and then, and finally going into android. It get's really hot around the camera though.
Today it's absolutely stuck in a boot loop and won't go into recovery. I was able to pull the logs a couple days ago right after a reboot.
I would really appreciate if anyone could look into them and tell me what's wrong and if it's possible to fix. My biggest fear is it is hardware related (which would suck because it basically just came back from being serviced).
Except for these last episodes, it's the best phone I ever had. I love the quality of the pics, the size, the screen and I was hoping not having to upgrade for a couple years.
Thanks in advance.
(I removed the Logs because even though I scrubbed personal data from them, I still got 16 downloads and not a single reply related to them, and just to be safe, I will minimize the chances of anything going sour)
Have the same issue. It just started going in bootlops. Sometime I can get a few hours of use if I am lucky but no matter what I do (diff roms,baseband, lg flash tool to original firmware) bootloop will not go away.
Seems like something many people are experiencing after a year.
Let me know if you figure it out
Hey All,
I posted this over on r/nexus5 as well, but figured id see if anyone here had any ideas as well.
I replaced my screen/frame earlier today and started having some trouble, figured I'd see if anyone else has had a similar experience and can give some advice.
I replaced my screen about a year ago, and all was well until a month ago. Dropped it again and cracked the screen, so I ordered another. Decided to spice things up and get a red frame as well, so this afternoon I took it apart. Tore it all down, and moved all the parts over to the new frame, everything went over nice and easy, and I got it all about together and booted it up. I see the Google logo with the unlock symbol, hangs out for about 15 seconds, and then reboots. Will do this for a bit until I power it down.
I read some other threads with some similar symptoms. A few people suggested the power button was being held down and causing the reboot, but that isnt the case here. I can get into the boot loader/fastboot screen, and can see it over adb. Soemone else suggested it was the long wide noddle cable not properly connected, so I've reseated that about a dozen times with no luck. I have checked all of my connections over a handful of times, but still the same deal.
So since my pc can see it in fastboot, I ran the nexus toolkit and did the force flash. Files transferred over and were written successfully, and as far as NRTK was concerned, it all went well. so it tells me the phone to reboot, and of course its the same 15seconds of google logo, rinse/repeat.
So I am thinking maybe my motherboard got damaged somehow during the transition? I just cant find any signs of damage, and I was pretty careful during the transfer. This was a replacement from China, but I figured since it shows the google logo and boot loader, the screen is indeed working... could it be the screen/digitizer preventing it from fully booting? I think its odd that root toolkit could still see the device, send data to it, and write it successfully.
Any thoughts would be much appreciated.
Actually now that I think about it, I will throw the guts back into the old frame in the morning to confirm if it is the new screen causing the problem or not.
So it turns out it was the chinese knock off screen that was the problem. put the guts back into my old phone, and all was well. Going to return it and get a new screen on the way.
hello all,i have a little problem with the recovery of my data from a nexus 5 (lg d820) i used the phone almost for two years the phone without any problem ,until a few months ago,when i decided to put aside the nexus (the lcd was cracked in some parts :crying: and the battery begins to show little problems) anyway, i bought a new phone and in the meantime i decided to buy a new screen for fix the old phone and sell it.
Now,before sell it,i would like to recovery my old stuff on it like some contacts and photos,because, unfortunately ,when i changed my phone i forget about that.
The problem,is in conclusion , that i totally forgot my pattern and now i can't unlock the phone,and i can't connect it directly to wifi,because i don't know the pattern anymore and i can't neither put my card back in ,because the new phone have a nano, i tried some hard solution like adb,but i can't access the phone because show me the device as locked when i wirte the command adb devices or shell,also if the debug is on and when i put the phone on my computer a pop up say: debug usb connected
please anyone know how ,at least, recovery my contacts and photos, if possible,thank you in advance,awesome forum