Hello,
I accidentaly dropped my hero from the balcony. Fortunately it "works", im navigating with the trackball. the glass and the case is pretty much f-ed up.
I managed to do a nandroid though, is it possible to recover a new phone with that nandroid image?
btw, i cant understand how the electronics works after 20ish meter freefall, into concrete :O
Yep,... It will be fine.
I suggest just making sure you are using the latest version of the recovery utility on both handsets.
Related
Hi everyone! Unfortunately, my run with my T-Mobile G2 appears to be nearing it's end.. I've had this phone since November of last year, so fortunately for me, I'm still within the 1-yr warranty. I couldn't find a legit answer on the forum so far so hopefully someone will have the information I need to know now.
Lately, my phone has been getting crazy. Sometimes it would start pressing random things by itself. Apps would start by itself, things would type by itself, etc, etc. Then, at times certain areas of my screen wouldn't work at all, most noticeably the "y," "b," and "h" on my keyboards. And this doesn't matter whether I'm using the stock Gingerbread keyboard or Swype.
To answer any questions, yes I am rooted and I have been running CM 7.0.2. I tried to flash 7.0.3 to see if that would correct my issue but it didn't. I also tried to reset the phone via Privacy within the Android UI and via Recovery, both with no avail.
My question to y'all is how can I fix this if at all? If this problem is not fixable, can someone provide me with the MOST SIMPLE guide as to how to unroot and restore my original T-Mobile stock ROM if necessary for me to send it to claim warranty.. Finally, if I resorted to claiming warranty, does anyone know if T-Mobile will be sending me a refurb G2 or a new one or a completely different one?? Thanks ... This is EXTREMELY UNFORTUNATE.
it happens to me plenty. keep the scroll pad on the side from changing angles in direct light or it goes nuts. if theres any water on the screen at all touch commands work funny. its errors in the optical touchpad and cpacitive screen technology, not the;phone itself.
edit: im stock if youre wondering
It happens even in the dark though. I think its problem with the screen.
Any word on this? the same thing is happening to my phone.
Hui,
I was also having this problem for some time and was reallythinking of replacing the phone until I finally got rid of this last week. To start with I think this is a software issue but I'm still not sure what sw is causing this. n order to fix it I had to install the rom again from scratch and did not restore anything from google. Because independent from whatever ROM I installed the issue appeared soon after I set up the phone. So if you wnt to give it try, do a clean ROM install or factory reset to your phone and then while setting up your device uncheck the option to backup and restore settings to your google account. I know that setting up everything manually does not sound great but it's better than the crazy touch screen.
Digitizer issues
Sent from my HTC Vision using XDA App
Digitizer issues, T-Mobile just replaced my original release date G2 because of it.
They will send you a refurbished model and you have to send yours back in within 7 days or they bill you $400 I believe.
Sent from my HTC Vision using XDA App
I had serious digitizer issues last month and thought for sure that my G2 was finished. Come to find out I had gotten some oil on my phone, probably from answering a text or phone call while eating at work. I took it out of its case and completely cleaned it with a cloth dampened with peroxide...not soaked just damp, and now my phone is back to normal. Give that a try and rule that out first before you replace the digitizer or phone. Make sure you clean the inside and outside of the case/skin if you have one too.
I finally figured mine out. I guess the digitizer is really really sensitive to moisture. I usually take my phone into the bathroom with me when I shower in the morning, once I stopped doing that and gave the phone some time to dry out (in a dessicant container, but rice would work just as well) my screen is back to normal. I guess the steam from the shower was enough to bring up some bugs.
Hey guys, well I managed to do it. Smashed my first screen. On a new phone too... I would have expected to smash it after a year or so but NOOOO I went and messed it up after a month or so...
Anyway, I want to pull a full backup off of my phone. NANDROID Backup is it ?
It still works fine, and I can see tiny tiny parts of the upper left of the screen. and connect through ADB. But none of the ADB remote controlling things I have found work with my mouse/KB.... If I could do that I would be satisfied...
And when I try and remove the pattern via ADB I get permission denied.... Ive spend the last few hours trying to figure out what to do here but im at a loss...
Anyone able to help me out ?
Also, Anyone able to tell me how much money im gonna loose replacing this screen ? ;___;
I can also boot into CWM, But I dont know what is what, like, I dont know whats selected because I cant make out the words... I want to do a full backup of everything to external SD card if possible.... photos of the screens of CWM would help XD
I dont remember what version I have installed sorry :c
But yes, PLEASE HELP ME!
Some day I may be able to help you in return, Until then I extend my deepest thanks to all who can help me even in the slightest...
Additional notes:
Screen is buggered, one of these things for the most of it, And the digitizer glass itself is cracked quite a bit on the upper left... :c
I seem to recall seeing CWM 6.0.3 or something along those lines...
I tried these:
http://forum.xda-developers.com/showthread.php?t=1587717
http://forum.xda-developers.com/showthread.php?t=1800799
http://forum.xda-developers.com/showthread.php?t=1420351
http://forum.xda-developers.com/showthread.php?t=1800799&page=2
And a few on non XDA sites I shan't link due to possible rule violations
-CP
Ever find out?
Ever figure out CWM menu?
I'm in the same boat and waiting for the OTG USB HDMI out adapter to show up, hopefully I can get the mouse and HDMI going at the same time and Titanium Backup everything.
Good Luck!
Hey everyone,
I recently dropped my Note 3, SM-N900 which I originally got from Vietnam. It was dropped, display cracked, all black. I had the screen replaced but the repair tech didn't realize it was the international version. He only had parts for the Canadian versions of this phone. He somehow managed to replace the display despite having the correct components. He fixed replaced the screen without replacing the bezel.
The screen worked great again but I realized my IMEI is now null or "Unknown".
I can't say whether it was still OK after being dropped because the screen was black and I didn't bother trying to call the phone.
I have found a lot of threads on IMEI unknown/null but read several warnings that this can be caused by either hardware or software. A software fix won't work if it is caused by a hardware problem.
Is there any way to tell what the cause is of an IMEI unknown?
Can you distinguish whether it is caused by hardware?
If it is caused by hardware, do I have any way of repairing this? Component replacement?
Could this be caused by the mismatched screen? This thread indicates a wrong screen could put too much pressure on some components, causing null IMEI....
http://forum.xda-developers.com/galaxy-s3/help-i9305/loosing-imei-lcd-replace-t2175895
Thanks for any help here! Really want to be able to make phone calls again....
Nathan
Start by restoring your backed up EFS folder .
Thanks for the replay - I didn't back up my EFS folder prior to the phone being dropped.
There is no sense in trying to back it up now and restore again, correct?
Also, is there any way of determining whether the EFS folder is corrupted? I've never heard someone say there is a file in there with the IMEI in plaintext or anything like that. But I figured perhaps there's a way to check the folder and figure out whether it is corrupted?
There is something you can try... go to sammymobile and download the rom for your exact device and region/provider. As long as they are matching, it should restore things back to how they were.
(example: if your phone is from Vietnam, get the rom for your phone from vietnam - and everything will be back to normal after flash from odin).
Good luck!
Update! I factory restored my phone a second time now. Still got null imei after restarting.
Then in the same day in the evening, and the IMEI is back! This is the first time ive seen the IMEI since I dropped the phone.
All that happened during the day was that I put the phone in a backpack, went on a trip and took it out again. Not sure if it was turn3d off between, dont think so.
I read this has happed to others, where the IMEI came back randomly, but then also vanished just as randomly again.
This sounds like a hardware issue with a poor component connection. I heard someone mentioning reflowing... guessing that means stick parts in an oven for a while.
Thanks for the tips so far!
Nathan
Ive noticed when making a twrp backup my device becomes really hot, wanted to know if this is normal or not
Natjosh said:
Ive noticed when making a twrp backup my device becomes really hot, wanted to know if this is normal or not
Click to expand...
Click to collapse
Do you have compression enabled? That has made every phone I use get hot when backing up.
My non compressed twrp backup went through quickly and the phone didnt get hot at all
Galactus said:
Do you have compression enabled? That has made every phone I use get hot when backing up.
My non compressed twrp backup went through quickly and the phone didnt get hot at all
Click to expand...
Click to collapse
Yeah that what I was thinking of, thanks
I have several S7 and S7 Edge phones, various carrier versions that ALL get really hot around the edge(metal frame). Seems mostly at boot up. None of these are rooted or customized in any way. I have had the back covers off. Replaced back, swapped motherboard in to different LCD assembly, etc, etc. No change. Seems really too hot to me. What is the accepted thinking on this?
enable compression in kernel source rebuild twrp no issues with heat.
Long story short my phone was in a pool long enough to shut itself off. I assumed it would never come back to life but I got all the water out of it that I could by shacking it and such and then started the drying process.
The only reason I'm trying to recover the phone is because it appears I turned off Google Photos backup 4 months ago (it was trying to backup when I didn't want it to) and forgot to turn it back on and now I've got 4 months of pics/vids of my 8 month old son on there that are currently "lost". That's half of his life so clearly I'd like to recover these.
So I dried it for 3 days, charged it to 100%, and powered it up. Motorola logo displayed for a few seconds and then it went to a screen that said:
Your phone didn't start up successfully, use Software Repair Assistant on computer to repair your device.
Connector your device to your computer to get software repair assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
Failed to validate boot image
ERROR: failed to pass validation. backup to fastboot
Fastboot reason: Fall-through from normal boot mode
I downloaded the software repair assistant and when I connect my phone to the computer it is recognized by the computer and the software also recognizes it and starts the "finding phone information" process where it identifies the phone type and such (presumably). Problem is it just sticks at this and never does anything else. I left it connected for over an hour while it did this. I tried a few more times with the same result.
So my questions are does anyone know what the errors mean, how do I fix them, and if they can't be fixed without a factory reset (or at all), what's the best path to trying to recover the pics/vids? I considered attempting a factory reset and then using a recovery program/app but if there are any methods that don't involve first deleting the files via a factory reset and then requiring a recovery attempt, I'd love to try that first.
Thanks for your time.
Stinger2300 said:
Long story short my phone was in a pool long enough to shut itself off. I assumed it would never come back to life but I got all the water out of it that I could by shacking it and such and then started the drying process.
The only reason I'm trying to recover the phone is because it appears I turned off Google Photos backup 4 months ago (it was trying to backup when I didn't want it to) and forgot to turn it back on and now I've got 4 months of pics/vids of my 8 month old son on there that are currently "lost". That's half of his life so clearly I'd like to recover these.
So I dried it for 3 days, charged it to 100%, and powered it up. Motorola logo displayed for a few seconds and then it went to a screen that said:
Your phone didn't start up successfully, use Software Repair Assistant on computer to repair your device.
Connector your device to your computer to get software repair assistant.
AP Fastboot Flash Mode (Secure)
Failed to verify hab image boot
Failed to validate boot image
ERROR: failed to pass validation. backup to fastboot
Fastboot reason: Fall-through from normal boot mode
I downloaded the software repair assistant and when I connect my phone to the computer it is recognized by the computer and the software also recognizes it and starts the "finding phone information" process where it identifies the phone type and such (presumably). Problem is it just sticks at this and never does anything else. I left it connected for over an hour while it did this. I tried a few more times with the same result.
So my questions are does anyone know what the errors mean, how do I fix them, and if they can't be fixed without a factory reset (or at all), what's the best path to trying to recover the pics/vids? I considered attempting a factory reset and then using a recovery program/app but if there are any methods that don't involve first deleting the files via a factory reset and then requiring a recovery attempt, I'd love to try that first.
Thanks for your time.
Click to expand...
Click to collapse
I can't help you with the problem of getting your pictures, but I can tell you the "Software Repair Assistant" isn't going to help... It hasn't been supported for years on any model, probably 5+ I guess. It is just left over code that Moto hasn't removed from current devices that's saying that.
Most likely you eMMC chip is corrupt, that's your internal storage... If it took a dip in a pool, that's the worst possible place it could happen to get wet, chlorine and other chemicals in the water literally eat away the silicon internals of the phone. You would have better if to drop it in a muddy River or lake than a "clean" pool.
Honestly, at this point if the device won't boot and the bootloader is locked, your chances of recovery if any data is near zero.
you could try booting into fastboot, go to stock recovery and then adb pull
munchy_cool said:
you could try booting into fastboot, go to stock recovery and then adb pull
Click to expand...
Click to collapse
Looks like you need to know the exact file name for each file for that. Is that correct or can you somehow view a list of available files to pull?
Stinger2300 said:
Looks like you need to know the exact file name for each file for that. Is that correct or can you somehow view a list of available files to pull?
Click to expand...
Click to collapse
if you have enough space on your computer and you do
adb pull /sdcard .
that should pull all contents of internal storage to computer
munchy_cool said:
if you have enough space on your computer and you do
adb pull /sdcard .
that should pull all contents of internal storage to computer
Click to expand...
Click to collapse
OK, I'll give that a try after I get the SDK Manager updated. Thanks.
Well, I can't believe it but I hadn't messed with the phone since Wednesday (when it wouldn't boot) and when I plugged it into the computer and turned it on today it booted!
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.
Stinger2300 said:
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.
Click to expand...
Click to collapse
awesome news. see you in the x4 forums
Stinger2300 said:
Well, I can't believe it but I hadn't messed with the phone since Wednesday (when it wouldn't boot) and when I plugged it into the computer and turned it on today it booted!
I was able to pull 24gb of pics/vids/texts without any "tricks" and the only thing that doesn't seem to work on the phone (for now) is the camera (constantly get camera app has stopped errors and no camera apps will open) and the screen has some interesting artifacts like it's got a little water in between the screen layers. I'm using my old Moto X for now and I'm ordering a Moto X4 (waterproof) to replace it.
Either way, I can't believe it actually came back to life and I'm so damn happy right now! Thanks for your help even if I didn't end up needing to use it.
Click to expand...
Click to collapse
That means it was still wet underneath/around the nand chip (where data is stored) causing the images from the stock firmware not to write (and subsequently fail) good thing you didn't fry it, anything less than a week of drying is pointless really and probably only survived due to the excessive shaking and such. Really the best thing to have done would have been to leave it on a car dash for a week. Camera would have dried out and still been working (betcha got what looks like stains on the sides/top/bottom of the screen)
In the future, non removable battery phones when dropped in water long enough to soak through, DO NOT CHARGE IT FOR AT LEAST A WEEK, DONT TURN IT ON FOR A WEEK. If you wanna be as safe as possible, that is.
Ae3NerdGod said:
That means it was still wet underneath/around the nand chip (where data is stored) causing the images from the stock firmware not to write (and subsequently fail) good thing you didn't fry it, anything less than a week of drying is pointless really and probably only survived due to the excessive shaking and such. Really the best thing to have done would have been to leave it on a car dash for a week. Camera would have dried out and still been working (betcha got what looks like stains on the sides/top/bottom of the screen)
In the future, non removable battery phones when dropped in water long enough to soak through, DO NOT CHARGE IT FOR AT LEAST A WEEK, DONT TURN IT ON FOR A WEEK. If you wanna be as safe as possible, that is.
Click to expand...
Click to collapse
Thanks for the info, hopefully I'll never have to use it!
Yes, it looks like stains on the bottom portion of the screen.