[Q] Is it Dead? - Hero CDMA Q&A, Help & Troubleshooting

Ok so tonight on my way home from the movie theater while riding the Harley i run into a down pour, now the hero is in the saddle bag which i was hoping would keep it safe, dry and happy, unfortunately that wasn't to be.
i get home and after getting the phone i go to look to see if i have any missed messages and find that it seems to have turned off, upon attempting to boot it goes to fastboot mode.
i currently have it sitting in a bowl of rice to try to dry it out, but does the fact that it still attempts to boot at all mean there is hope for my little hero?! I <3 that phone it's been so loyal! Even though i'm currently considering upgrading i'd like to get a backup of some stuff i haven't backed up recently before changing phones.

ok so it boots up now, my only problem is that the screen won't unlock now, i've tried changing out the glass touch screen to one i know works and that's not doing it, so does this mean i'm SoL? that something on the motherboard has gone wrong?

even though i'm not getting any responses going to update, couldn't find a way to unlock the screen with the touch screen not working, now that being said, i did find a command to pull my mms/sms database through ADB, now when i get a new phone will i be able to paste this database file in and it compile automatically, once i get root access that is?

Yes. Transferring the messages shouldn't be a problem.
What phone did you get?

Related

Touchscreen broke, way to bypass welcome screen?

Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Try placing your finger on the Android, press the trackball, then lift the finger and press the trackball again
Tommy
IzzeLing said:
Hey all, I've been looking around the past few days and didn't see anything on this particular issue.
Basically, I washed my G1 and had to get a new one. The one that got washed has been starting up (slowly, and not always), but the touchscreen no longer works. I reflashed the software to hopefully alleviate any of the problems when it was starting up. My initial thought was to use fastboot to flash the backup I made on my new phone with nandroid, but the bootloader isn't working properly (I'll try a reflash of that too).
So, do any of you guys know of any other ways to bypass the startup welcome touchscreen?
Click to expand...
Click to collapse
Flash the ADP1 software.
Edit: You'd still need touch for that, sorry.
The driver was all wonky, uninstalled, reinstalled, fastboot works now Flashed over to my new G1's state, but forgot to take off the lock screen... Flashing yet again. Everything should be good from here.
Edit: Alright, washing the G1 makes it wacky. The touchscreen works now after restoring it to the new G1's state. Weeeirrrdd.
Edit 2: Anddd now the touchscreen doesn't work :S
well.. when my touchscreen broke i used remote control software to control my ppc from pc .. thats one way to bypass welcome screen, but won't get you much further. I used it for making a backup from my phone.
just leave it off for a while and keep it someplace dry and warm so it can dry out.
You may try to modify build.prop in the rom you flash
ro.setupwizard.mode=DISABLED
I think it will skip the setup
Sorry can't help myself. In the laundry?
I guess I'm wondering what exactly you did. I'm assuming it didn't make it into the dryer....
If you need the data off it, you might be able to ADB pull what you want to keep. If I'm not mistaken, ADB is as close as we have to remote controlling for Android at the moment.
There may be some places around, like PPC Techs, that can do hardware repair. I'm guessing what will happen is you'll occaisionally get it to work for brief stints after reflashing or whatever, but it'll keep conking out until the hardware issue goes away/gets fixed. Hardware issues do that, printers, routers, sometimes PCs.
Not to be a naysayer, but I don't think changing out the software is going to help.
I washed my G1 (was in pocket of jeans under the water for about 90 seconds), and after that I disassembled it to let it dry. It was running fine up to the day I SPL bricked it.
Hey.. i split water on my phone.. it couldnt have been that much but the touch screen wasnt working.. thought if i factory reset it, it may started working..
I dont actually understand all the lingo you guys use.. but any ideas on how i can fix it?
J x
oh the main issue is i cant get past the touch android to continue set up... please i just want my android to work!!! J x
I'm having a similar issue... My phone randomly stopped loading android.process.acore and it's messing with my heart. The touch screen doesn't respond but I can use the trackball to navigate, and every acore process force closes instantly upon activation, such as dialer, contacts, music, etc. The wonderfully helpful people at T-Mobile instructed me to do a factory reset on my G1, and it should fix the problem.
New problem: I can't get past the "Touch me, I'm an Android logo" screen. When I click Emergency Dial, it force closes because the acore processes are still messing up. The intention today was to reload the Cupcake SPL and Radios onto the phone. The issue there is that I can't touch the screen to start the USB connection with my computer.
Anyone have any suggestions aside from paying another $130 bucks??
This will do the trick
google androidscreencast it will allow you to contol your G1 via your PC
...let me know if you have resolved android.process.acore im on the same boat and a wipe and flash has yet to solve it...
same boat for me too! wow, this is three, maybe 4 of us currently experiencing same problem!
I love screen cast. Droid explorer is great too, basically a GUI for adb, and has a plugin for screen cast. Too bad you have to be online though, I'd love to use screencast offline!
I'll update if I figure out the error problem!
Well it looks like a complete wipe and a flash back to non root status is whats gonna take to fix the android.process.acore issue. BUT now w/o root, I cant access the G1 via android screen cast...so im totally stuck on the "Touch Android to begin" screen... sucks to be me lol
I think I'm in the same boat. I didn't know about the screencast application before I did a complete wipe to stock. So I'm stuck at the "touch android" as well. This phones pretty much junk to me right now.
I wonder if any of you have tried restoring your latest back up?
Yes, no help, either on the touchscreen, or the incessant errors. I think there must be some code that checks whether the touchscreen works, and sends back an error if it doesn't. I've tried almost every combination of radios and spls mixed with several different cyanogen roms going back to 4.1, both fresh installs and nand restores.
Currently I'm running the latest cyanogen, radio and hard spl. I get errors often, and can't use the phone / dialer at all without force closing. For now texts and google voice work so I have at least some communication. Ironically, I can't even unroot because none of the spls will flash dreaimg.nbh, but that probelm is in my unresponsive bootloader thread.
Sorry to hear about your predicaments allthrottle and r1ch. Strangely you are right where I'm trying to get, I have warranty coverage to fall back on.

Nexus One stuck in bootloader

Pardon for the long post but my Nexus One has been out of comission for a few days now so I'll list everything I've tried to make it work in an attempt someone might be able to help me!
Okay, here goes.
A couple days ago I removed the battery on my phone to install an invisible shield. Prior to that I had owned the Nexus One brand new for about a week, had it rooted first thing with the HTC Desire ROM...it was running perfectly
After the installation of the shield was complete I reinserted the battery and hit the power button. The phone booted straight to the bootloader (aka white Robots on Skateboards screen). Funny thing, I was unable to navigate the bootloader (vol up/down) without fiddling with the trackball first by pressing it a couple times) Anyway if I would reboot the phone via bootloader it would return...power off the phone it wouldn't power off just reboot to bootloader.
In this mode I could still use fastboot perfectly and I could enter the restore screen. At this point I kept attempting a reboot and it actually went through at one point and did a full boot to the OS...when I powered down and booted up again however, it was back to the same issue.
On the modaco forum they suggested I flash an alpha2boot.img as the boot image replacement for r21 desire rom as a fix, I tried this method with no success. Since, I've factory reset the phone several times replacing it with various ROMs (currently running stock) none of it fixed the problem.
I also found a way to brute force the phone into safe mode via the fastboot command in prompt: fastboot-windows reboot Using this command the phone successfully reboots, albeit into SAFE MODE. In safe mode the phone works perfectly in every way. I'm just limited in that I can't install any applications and I can't reboot properly (without a computer and command prompt).
I was doing some research on the forums and read the problem could be with the trackball. It would make sense that the phone could only boot to bootloader if the phone had the key press for the trackball triggered somehow. That said, the trackball functions perfectly when operating the phone in safe mode so I doubt this is the issue.
Another idea is that the phone is stuck in some state in the SPL or bootloader...I was wondering if there was anyway to reflash the SPL or bootloader to see if I could resolve the issue that way. (how I would do this, I have no idea)
Any help, suggestions, or advice is very appreciated. As I already unlocked my phone I have a feeling I am out of luck for warranty though I would pay for HTC to repair it if they could. I would prefer to fix it in the software however and not send it in.
Reflash the stock ROM and see if that helps.
mortzz said:
Reflash the stock ROM and see if that helps.
Click to expand...
Click to collapse
He said he's running stock rom...
@ OP, if everything was absolutely perfect before putting the shield on, and everything to crap immediately after finishing the shield, then obviously something went wrong during the install.
The obvious yet unfortunate conclusion is that some solution got inside or something, most likely inside the trackball. =\
Detail exactly what you did when you installed the invisible shield.
Did you get you phone wet at all?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
Got the front of the phone a little wet and I'm guessing some did get in the trackball. That said, I do invisi shields every day for my job and never had an issue with any phone...wouldn't it be ironic that mine was the one that got screwed up.
I think it's interesting to note that the trackball still works perfectly when the phone is running in safe mode, no double clicks or anything like that...possibly a sensor was tripped?
So I called it quits on fixing this phone and I'm sending it out to HTC does anyone know how I go about getting restore back to factory settings?
Well you can't relock the bootloader, but if you can use fastboot when your phone's on the booatloader, you can use that to wipe the phone.
Oh wow, sorry to hear it.
If your phone will not boot without the help of fastboot, I wouldn't worry to much about what state Android is in (factory, or custom rom). HTC will attempt to boot the phone, toss it in a bin, and then send you a replacement.
Or that is my assumption anyways. A friend had a similar issue; he unlocked his phone and decided after flashing the Desire rom, that he wanted to stay stock with what came on his Nexus for a while. After flashing the stock images back, his phone looped into bootloader. Off to HTC it went and within a week he had a new phone.
Best of luck!
Sorry to post in such an old thread, but I'm having the exact same issue. Even the part with the invisible shield. Didnt install it myself, the idiot at best buy used too much of the liquid I guess. Did you send yours in or what? I managed to get the phone to work for about a month then it started acting up again today. Wont boot into anything other than safe mode, or fastboot. When it boots into safe mdoe, the phone turns off within a few seconds then goes straight to the boot animation. Would love to get this issue settled, really annoying
i am having same problem. fasboot doesnt even find my phone. i got into safe mode but when i turned it off and back on it went back to fastboot
Same
I am getting the same problem! this really sucks. I think the phone might have gotten a little bit wet, just a few drops of water, and that may have caused this. Should I just call HTC and send it in?
btw, the phone was working fine, even with the very little moisture that was wiped from it. But, I took out the battery when I got home, and this happened.
so is this because on invisibleshield? cuz i just ordered mine today!!
I think its from a little bit of moisture getting into the trackball. I've been doing many "tests" trying to figure out the problem, and my almost final conclusion is the trackball not working good. Most of the time I try to start-up the phone i get into safemode, and once I have gotten into the normal way of things, but the trackball wasn't working well. I think I might have to cal htc, and that sucks because I am going out of the country in 4 days... I won't be able to take my nexus if I can't come up with a way to fix it myself.
I DID IT!
Well, I think I did.
My theory that moisture was the cause of this bootloader stuckness is quite correct. I took a towel, and rubbed the trackball to it for a good 5-10 min, then I did it for another 5-10 min wiping while pressing down on the trackball. I'm very sure that there was some moisture extracted from the device. The trackball is working now. I now do not have to call HTC or send it in.
I kept on booting into fastboot and then recovery, being unable to press buttons, but then I rebooted again into safe mode, where the trackball wasn't working either. I kept moving around the trackball, and then I figured it out, because I felt a slight bit of moisture. Now, it boots up normally, I can access the recovery, and all selection is working.
But, I have a bad feeling that this problem will come back to haunt me. It's good for now though.
Phone is working great as usual.
Can confirm the same issue.
Drop of water on the trackball.
Rebooted into an unresponsive fastboot.
Fastboot reboot command from the computer got me into safemode.
Rolling the trackball while pressed fixed it, the phone boots properly now.

[Q] Please help: trackball constantly registering clicks even if not pressed

Hey guys
I tried to search but I haven't found anyone with this particular problem:
Today I had to swap the SIM card on my dad's N1. I must have touched something the wrong way since after doing so, it seems the trackball is constantly being pressed (even though it's not).
Here's some of the consequences of this, that are making me literally freak out:
1. I can't get into recovery (as soon as I do, a click is registered on "Reboot phone).
2. It only boots in safe mode
3. Navigating around the phone is almost impossible, opening up the app drawer immediately launches an app.
By hitting a text input field, I can observe how it's registering clicks really fast (by observing how the whole text field is selected/deselected)
I tried fiddling a bit with the trackball, long pressing it, clicking it, etc, but it's still a no go (long pressing it does register as a long press, but as soon as I let go, the constant clicking continues)
Seeing as how this happens whether or not after the ROM has booted, it looks like this is a hardware problem.
Has anyone run into something like this before? Any ideas on how to fix this myself?
I don't know if sending it to HTC is an option because of two reasons:
1. I live in Costa Rica, don't know if there's HTC support here, or if it'd be safe shipping the phone to the states for a repair.
2. My dad's N1 is rooted, but bootloader hasn't been unlocked. It's running a custom rom. Right now I'm not sure if I can't get it back to stock since I can't even get into recovery.
Please help! Thanks
I had this exact problem for about a day or so it turns out I had got the trackball wet try clicking it and rolling it also try giving it a day or two it might just come back good luck on your nexus
Sent from my Nexus One using XDA App
Turns out you were right!
I left it sitting for a day, turned it on and the problem was still there. I got a hair dryer and used it on the phone for like a minute, turned it on, and all is good now!
Thanks!
Problem has come back and won't go away now... definitely looks like a hardware issue, will call HTC support.

everything is Force Closing since yesterday

hey guys, I don't know what's going on with my S7 but yesterday was working fine and out of nowhere everything started to FC! From twitter to "Google Services Framwork", Gmail, browser, tweetdeck, calendar, voice, I can't pretty much use it anymore, I haven't done any new app installations so i don't know what's wrong! is it just me, or anyone else having this problem??
Any help will be much appreciated!
Thanks
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
djdanska said:
That has happened to me 4 or 5 times. It's like half of the device gets erased but the apps are there. Everything force closes. I end up having to erase the device and re-install everything. Reboot into recovery if you can't figure it out and format the system and data. For some reason when i do that, i keep root. Not entirely sure how that happens, but one less step for me. I think root is power and one of the volume buttons.
Click to expand...
Click to collapse
ha! i remember I already did that. After the Update we had, and I exchanged mine for a new one I decided to stay with no root (i don't know why! lol) so I guess I'll reset everything and go back to root I figured at the end I was gonna do that, but I was trying to see if it was just me or there was a fix
thanks man!
ok, so since yesterday I've been trying to factory reset the DS, and when it boots back on, everything stays the same!
I'm a little confused now, if I take a picture and I turn the tablet off, when I turn it back on, the picture disappears. Same thing happens if I move widgets, delete or create new ones on the screen, they go back to as the configuration was on friday night! GV not working, and the last message that shows there, same thing, shows the last one on friday. I don't know what can I do.... should I call dell??
duck tape and dynomite
stupid thing started crashing yesterday FC this and FC that ....cant restore it as i no longer have write access to the internal sd card
1) tried nv flash
2) tried restoring from clockwork
3) tried pushing files through adb
4) tried fastboot ....
if i didnt just dump money into this thing id blow it up ......
any help would be appreciated.......any tips to fix it or kill it completely so i can get another one
actually deleted all of the files on internal sd card and uninstalled every program on the device looked completly stock ....rebooted it and it went back to how it was yesterday ......theres gotta be a reason why other are having the same problem that started on the same day .....maybe dell pushed an OTA update and screwed us ......just a thought cause mine was fine till i went 4g yesterday so my sis could post facebook pics ....not sure but hope we can figure this out
Samething happened to me
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
jz83 said:
Hi, did you ever find a solution? my streak 7 was ran out of battery, before it shut off, the screen started flickering and then it turned off. after it came back on, it looked like it was fine, everything looked normal, but then everything started force closing, haven't found a solution
Click to expand...
Click to collapse
I'm running stock, and I discovered the hard way that you can't let the S7 battery run all the way down. The S7 will not power itself down in time. I had the same issue, and the only way around it was to do a complete factory reset, using the menu button from the main screen. I think the reset is in the "About" section, but I don't have my S7 with me now.
Being used to WM6, which powers the device down at 5%, I was not expecting the device to do this, but there it is.
dell streak 7
im not sure if I am the only one with this issue you but becareful with the streak 7 mine well both of mine wont charge properly and the newest one wont charge at all. i have to send it back to dell for them to fix it. Im not sure what cause this but my only advie is to never use a different charger for it only dell chargers. Im guessing that it messes up the battery callibration and then it gets really hot when charging

Extracting data from my malfunctioning handset?

Hey guys,
I have searched and couldn't really find anything to pinpoint my issue.
I'm new here and i have a bit of a problem with my Sensation XL.
Ok first a little bit of a story (sorry), i was in Athens for 4 weeks, and i think the 'extreme' temperatures has buggered my phone.
Two weeks into the trip my phone was shutting itself down randomly and when i rebooted it, the battery was completely empty. This carried on for about a week until it decided not to bother switching back on again and the notification light was flashing red and green continuously.
I eventually managed to get the phone on, but the screen was extremely dark and the handset heated up to the point where it was too hot to touch.
I switched the phone on today, the screen is black but it goes on, but doesn't stay on for very long.
I have contacted HTC and it is being picked up for repair on Monday under warranty.
Now that i have bored you with that, i have a few questions:
1. They claim that if it is water damage it will not be repaired, now is it possible that maybe the humidity in Athens (water) damaged my phone, or was it just the heat, or has anyone had similar problems that may know what has happened?
2. Is there anyway that i can possibly get the data (pictures etc.) off of my phone and onto my laptop with a black screen, and also taking into account that it stays on for about 30 seconds max. before it switches off again? HTC sync can't find my phone when it's plugged in, but iirc you need to click something on the phone to sync it with the laptop?
I only need my pictures, all of my graduation pictures are on it. Please someone help? :'(
Also my phone is completely standard in every way, only the factory issued update has been applied.
You can try play with adb.
Install drivers from google sdk or my signature.
Download ADB File explorer
pull out the sim card.
turn on phone and connect it to pc.
If this not working than sorry but i think theres no other way to take it out.
Is one but you loosing warranty.
Thanks for the reply,
I clicked on the ADB File explorer link you posted and it says its no longer available.
I managed to get my phone on very briefly earlier, however it is so dark it is almost impossible to see, i did however manage to sync it to my computer and started transferring my pictures but then it got very hot and cut out again within the space of a minute and the notification light was flashing red and green.
I guess i'll just need to keep trying this and hope that my phone stays on long enough to transfer the photos.
martinmac1 said:
Thanks for the reply,
I clicked on the ADB File explorer link you posted and it says its no longer available.
I managed to get my phone on very briefly earlier, however it is so dark it is almost impossible to see, i did however manage to sync it to my computer and started transferring my pictures but then it got very hot and cut out again within the space of a minute and the notification light was flashing red and green.
I guess i'll just need to keep trying this and hope that my phone stays on long enough to transfer the photos.
Click to expand...
Click to collapse
http://adb-file-explorer.googlecode.com/files/ADB%20File%20Explorer%20v031.zip
Try copy pictures one by one. But via adb will be better cuz you can turn off the screen.

Categories

Resources