trackball stuck - Nexus One General

so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)

can you select to boot normally from fastboot? or hboot

nope...i can't move selection while in fastboot... i'm pressing vol+- but nothing happens... probably because it thinks trackball is pressed all the time...

I had the same thing happen with my power button. I had to send the phone back to be repaired and it took almost two weeks.
I don't know if anything has been posted yet but I remember someone saying the N1 has the same trackball as one of the blackberries. Maybe there is a guide on swapping them or even just disassembling it to clean.

well... sending it back (from serbia to usa) is definitely not an option, partly because it would probably take at least month to get it back, partly because i don't want to risk having to pay duty&tax when it comes back.
disassembling, however, is an option, and i will do it if no one has better idea
thanks for replies anyway...

alt+64 said:
so... this morning i noticed that trackball isn't functioning... i could move it in any direction and press it, but nothing happened... so i tried to reboot and now it keeps going into fastboot (as it's always pressed)
now, since i'm not anywhere near any of "supported" countries, sending it to back to htc is not an option... is there anything i can do to override going into fastboot and to boot it normally (i don't usually use trackball, i don't really care if it's working, i just want to boot)
Click to expand...
Click to collapse
When you press it does it make the clicking noise? if it doesn't, replacing the trackball wont fix your issue. The trackball popple that registers the click when a short is made is depressed fully and is always making a short. you either have to rebend this popple or replace it entirely. You need something similar to this

When you press it does it make the clicking noise?
Click to expand...
Click to collapse
yes it does... click, feedback... everything is exactly the same as it was...
btw... i'm at home now, so i connected it to usb and managed to boot with "fastboot reboot"... problem is that it boots into safe mode (i guess it does it if you hold trackball during whole boot process) so i cant open any 3rd party apps which makes it kinda unusable...
btw2... scrolling with trackball is working normally.. clicking does not
i guess ill take it apart and try to disconnect trackball completely..
any last thoughts before disassembling?

some witchcraft happened today, and my trackball is kinda working now, but phone keeps booting to safe mode...
taking battery out for 2 minutes, as some suggested, didn't help, and neither did holding trackball while booting... any other idea?

did you try factory reset?

yes... no luck...

Related

I need some serious help.

My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.

HELP! Trying to help a friend out.

So a friend called me today and said he is having problems with his Vibrant and wanted me to come take a look at it. He explained that he flashed a rom and now everytime he boots it up, it gets stuck in a force close loop hell. I got there and verified that's happening and said that I could just flash him back to stock. Well, come to find out he's also hardware locked! I tried to figure out a way to enter safe-mode (have used this on my Mytouch but it had actual buttons to make this work) but it was no-go since it's capacitive. On top of all this, he doesn't have debug mode enabled and I can't get to the settings due to the force close loop and no working launcher/home. I couldn't get any adb commands sent to the phone due to no debug mode, so that means I can't even adb reboot into recovery. I spent almost 2 hours on it before I had to give up. Does anyone have any suggestions that I may have overlooked or not thought of?
Greatly appreciated! XDA has some of the smartest damn people around!
Have you checked this out?
http://forum.xda-developers.com/showthread.php?t=804305
Duce HD2 said:
Have you checked this out?
http://forum.xda-developers.com/showthread.php?t=804305
Click to expand...
Click to collapse
Yes, in fact I had that very thread open on my netbook as I was working on his phone. There's one (of many) problem with this:
"turn on USB debugging in Settings-->Applications-->Development"
As I stated in my OP, he doesn't have debugging turned on already, and I'm unable to get to it in settings because at startup it's in a FC loop and I can't get to settings either by holding MENU or using the launcher.
Is there another way to get to phone settings besides those two methods? How about going into safe mode? I've done that before with my MT3G, but it has hard buttons that facilitate this with ease. With capacitive, not so much. Is it possible to enter safe mode on the SGS phones with capactivie screen?
I seriously doubt this has stumped the brains of XDA!
Email me lets see if I could help
[email protected]
What do you think caused the force close loops? Was your friend tinkering with his phone? Did he install a lagfix?Are you doubly sure he's hardware-locked?Did you try Download mode?
Lots of questions...I had this problem once. It was due to the fact that installed Ryanza's early lagfix and tried to remove it. My phone had a force close loop, BUT I had enough patience to wade through the loops and in the very short gaps at which they appeared, I managed to navigate the phone into settings (~an hour). The moral is: Try very hard to get into settings and don't lose your patience.
You can try booting into safemode, maybe that will help. Just turn it off and when it powers on the second you see the animation start press and hold the home button.
cthach11 said:
What do you think caused the force close loops? Was your friend tinkering with his phone? Did he install a lagfix?Are you doubly sure he's hardware-locked?Did you try Download mode?
Lots of questions...I had this problem once. It was due to the fact that installed Ryanza's early lagfix and tried to remove it. My phone had a force close loop, BUT I had enough patience to wade through the loops and in the very short gaps at which they appeared, I managed to navigate the phone into settings (~an hour). The moral is: Try very hard to get into settings and don't lose your patience.
Click to expand...
Click to collapse
From what I gathered, he tried installing the FrankenTwiz rom and something went wrong. He couldn't fully explain exactly WHAT went wrong, and so I'm coming into this whole thing without a lot of answers to help troubleshoot it. I know he's HW locked because that was the first thing I tried (recovery mode) and it's not able to get into it. When I fist got my Vibrant it was HW locked and the behavior is the same. I exchanged mine the next day for a non-HW locked. I tried every method to get into recovery/download mode but unable to. I remembered "safe mode" from my MyTouch 3G, but it needed the hard button (menu) pressed on bootup. Being capacitive screen, it doesn't respond the same way so I couldn't even use safe mode. He doesn't have USB debugging enabled and I can't get to settings to enable it due to the FC loop. I sat there pressing CLOSE a million times to find that "break" in the process to try and get to settings with no luck. Hope that answered everything.
icandy75 said:
You can try booting into safemode, maybe that will help. Just turn it off and when it powers on the second you see the animation start press and hold the home button.
Click to expand...
Click to collapse
That didn't work. I thought safe mode was MENU, not home? (btw- which animation? The tmo pink or the Galaxy S? Tried both an no result.)
Ok, figured out SAFE MODE!
Power up the phone and start pressing the capacitive buttons. As soon as they light up during boot up process, press and hold MENU & HOME all the way through until you see SAFE MODE appear in the bottom left of the screen. At that point you can release the buttons and you will now be in safe mode.
Now I just need to get in touch with my friend and meet up with him to try this. Hopefully it will break the FC loop from Hell and I can get into his settings to enable debugging mode.
**MODS - I didn't find how to get into safe mode anywhere in the Vibrant forums. Maybe it can be added to the Bible to help others? Thanks!**
That's new for me, mine goes holding the home key. Timing is of the essence though. I have to press and hold the second the S forms on boot.
icandy75 said:
That's new for me, mine goes holding the home key. Timing is of the essence though. I have to press and hold the second the S forms on boot.
Click to expand...
Click to collapse
I tried multiple times using your method and no dice. I get consistent results with my method (MENU + HOME), so not sure what to say...
Anyhow, it looks like he's screwed. Met up with him after work and even though I can get into safe mode, the TW Launcher is still going nuts, FC hell! Unable to get it to stop long enough to get to settings to enable debugging. He's going to put it on Ebay for parts. Dude had it for a week and is out $400. Feel so bad for him, but I guess it teaches him a lesson. If you don't know what you're getting into with flashing ROMs, better step back and either ask for help from someone with experience or just not attempt it at all. This was his first flash attempt and he crashed hard.

[SOLVED (KIND OF)] Transformer display dead and stock ROM installed - warranty?!

Guys, thanks to all of you - especially frysee, who was a big help via Gtalk - the biggest part of my problem is solved:
My Transformer is still bricked and display won't turn on, but I was able to go back to stock ROM and wipe all personal data. So I won't get any trouble with warranty
If anyone is interested, me or frysee could write a How To for returning to stock ROM and retrieve warranty when screen is dead.
Thanks again!
qwer23
_____________________________________
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
demonotter said:
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
Click to expand...
Click to collapse
Hi!
First of all, thx for your answer.
Well as I said, the first time the problem occured, the device was out of the box and untouched before. So I don't think it has to do with something I did.
For me it normally also happened when device was in sleep mode, except the first time out of the box
I installed a custom ROM + Clockworkmod Recovery after that, hoping it'll fix the deep sleep problem. And it really didn't happen again - until now
I didn't turn off OTA updates as I first saw that thread when the device was already dead Perhaps it tried to OTA update itself but I guess I would have to confirm this manually right? And I didn't do that...
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
frysee said:
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
Click to expand...
Click to collapse
yes, being unable to wait for the german release, i imported from uk
adb gives me "device not found". even though i'm not a total noob, i don't know what i have to change to make it work. any advice? sadly i'm working while my tf is charging @home so can't really try something. i only hope you guys have some ideas
Sent from my rooted X10i using awesome custom roms
qwer23 said:
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Click to expand...
Click to collapse
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
demonotter said:
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
Click to expand...
Click to collapse
no i guess that it is indeed the same thing that happened to you, sometimes it worked, sometimes not. only this time it doesn't come back from the not working part I guess you see yours in explorer too if it troubles to get out of deep sleep. i guess it's just the screen that sometimes doesn't turn on for all with that problem. but for me it doesn't even turn on for booting
Sent from my rooted X10i using awesome custom roms
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
demonotter said:
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
Click to expand...
Click to collapse
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
qwer23 said:
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
Click to expand...
Click to collapse
You just plug it in.
qwer23 said:
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
Click to expand...
Click to collapse
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
checkbox111 said:
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
Click to expand...
Click to collapse
Tried that a lot of times already. No help.
Phone still won't turn on, but I just realized I cannot only access my SD Card, I can also access internal storage.
Is this of any help?
qwer23 said:
Tried that a lot of times already. No help.
Click to expand...
Click to collapse
Then your ****ed!
checkbox111 said:
Then your ****ed!
Click to expand...
Click to collapse
I guess so
I'm getting a mini-hdmi cable today to determine if the screen is broken, because i have the feeling that ***** is booting but not showing anything...But I'll have to send it to ASUS nonetheless. Has anyone ever sent a device in for warranty reasons with custom software (CWM, Custom ROM) on it? What kind of trouble will I have to face?
I'd say try it with the HDMI cable, see if you get anything up on it and if the touchscreen/everything else still works, see if you can get the latest official ROM on there, see if that fixes the problem.
If nothing else, you can then send it back with an official firmware on it.
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
sbirsen said:
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Click to expand...
Click to collapse
Not possible since I installed CMW.
stuntdouble said:
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
Click to expand...
Click to collapse
Big bummer And sadly there are no "ASUS Stores" around where I could use a stupid employee who has no clue and is convinced it's hardware related.
Well I don't have my HDMI cable by now and will try this first, but if that doesn't work:
Can someone give me a step-by-step how I can access the restore function of CWM without seeing anything on my device? I did a backup in CWM before installing the custom ROM. Perhaps tell me sth. like this: "press power+vol. down on start, then after approx. x seconds press vol up, wait a bit to make sure CWM started, press vol down twice, to go to recovery, ..."
And can someone do the same for the stock recovery to reset the device? Perhaps there's a chance that a failed OTA update deleted CWM an there's the stock recovery.
I know the chance to save it like this are small, but otherwise a lot of money is lost
Regards,
qwer23
On the flip side however, you could probably make some money by being the first to dismantle your device, and sell the photos of the internals to some website like iFixit. Then you could also sell it off as parts on eBay. Obviously it might take more effort than you are willing to give it, but at least it's another option.
If you do decide to open it up I would love to hear what mA rating the battery has on its label. Not being able to find out the actual proper rating from any site has been driving me nuts. I believe it's 6800mA but im not 100% sure.

Phone wont boot [Goes directly into HBoot]

I woke up this morning and my phone will not boot. It automatically boots into the bootloader (hboot) and the up/down (volume keys) wont move the cursor to allow me to get to the recovery option. Also if I try to boot into recovery using the hard button combo it vibrates 3 times and the led turns to green, then it just sits/never gets to recovery. Since hboot is looking for the PDimg file I figure I could use this file to revert to stock but I was hoping someone here might have a better answer.
If not can someone let me know how to go about flashing with a PD15img file and where I can find a copy?
Thanks guys
Sounds like your volume button is stuck
Sent from my HTC Glacier using xda premium
Nope because it knows when I'm using them to try to go straight to recovery also the power button cannot be used to select either but it works to turn the phone one. They just stop working in hboot.
A constantly pressed button will of course also react when you're trying to boot directly to recovery. The phone doesn't "know" anything.
Another option is a stuck trackpad.
If all else fails you might try to reflash recovery and or Hboot, it never hurts to try from a clean install.
Nic
Jack_R1 said:
A constantly pressed button will of course also react when you're trying to boot directly to recovery. The phone doesn't "know" anything.
Another option is a stuck trackpad.
Click to expand...
Click to collapse
I think you guys are misunderstanding the point. This has nothing to do with the buttons. My issue is when I turn my phone on (by hitting the power button once) the phone will only boot into hboot. Once in hboot none of the keys (power or volume) work. If I try to boot directly into recovery by holding vol up/down + power; the phone will viberate 3 times and the LED lights up green. It then just sits on a blacklit black screen and does nothing else.
I am looking for eirther; Anyone that has ever had this issue and may be able to shed some light onto why it happened. Which by the way was completly random, I shut the phone off before going to sleep and woke up too it viberating like crazy then when I tried to turn it back on; this is what happened.
Or the answer to this question; How do I install a rom from hboot? Can I just install any rom as a "update" by using the method of naming it PD15IMG? Since it does search for this file when I have a sd card in at boot. But if my memory serves me correct it will ask; "Would you like to install this update?" and if my hard buttons do not work and I cannot click yes than what else can I do?
Thanks for all the help guys!!!!
- M
And I think you can't read. You've been told in 3 posts that the phone boots directly to HBOOT because EITHER A VOLUME DOWN BUTTON OR A TRACKPAD BUTTON IS STUCK, ON ELECTRICAL LEVEL - THE CONTACTS ARE ALWAYS CLOSED. And THERE'S NOTHING YOU CAN DO ABOUT IT ON SOFTWARE/FLASHING LEVEL. You need to fix what's broken, and you've been told what's broken. Patience isn't one of my skills. Good luck from here.
Jack_R1 said:
And I think you can't read. You've been told in 3 posts that the phone boots directly to HBOOT because EITHER A VOLUME DOWN BUTTON OR A TRACKPAD BUTTON IS STUCK, ON ELECTRICAL LEVEL - THE CONTACTS ARE ALWAYS CLOSED. And THERE'S NOTHING YOU CAN DO ABOUT IT ON SOFTWARE/FLASHING LEVEL. You need to fix what's broken, and you've been told what's broken. Patience isn't one of my skills. Good luck from here.
Click to expand...
Click to collapse
I do thank you for your help but you may want to aquire some patience if you plan to continue helping people... since people in need of help are most likely confused.
Thanks though :highfive:
Im my experience Jack_R1's answers are always right and are the answer to your question. If you think otherwise one of two things is happening.
1) You did not explain your problem thoroughly.
2) You need to examine his post(s) more closely.
He has zero tolerance for stupidity or ignorance due to laziness (i.e. not searching). I'm not trying to speak for him or defend him or anything else. He's grown and quite capable of handling all that. The man just knows the answer and gets to the damn point.
I wish we had more people around here like him.

Recovering pictures from Crashdump blocked phone?

Hey guys,
I was on my honeymoon until yesterday, celebrating in CancĂșn (Mexico), taking some great and important pictures for us with my OP8P, and in one of the places the phone got a bit of water inside it but it kept working fine for the next two days (even charging up after dried it). Then, next day we tried to take a picture, camera app looked like it were inside water and front camera had condensation on it. When restarted the phone, it got stuck into "Qualcomm CrashDump", and forever there. It reacts to pushing vol + vol - and power going into fastboot menu, but recovery mode doesn't work.
I understand that my phone got softbricked (as hard means no reaction at all, right?) and that I need to restore it to have it working back; thing is, I really want to save my honeymoon pictures before wiping everything away with MSM (never used it but saw that's the way to flash and revive the phone), but can't find a way so far to get my pictures back... Could you guys help me please?
My phone is a IN2023 version, original stock rom and unlocked developer mode from menu, but never rooted nor touched anything else.
Thanks in advance!!
EDIT: As another piece of info, when I plug the phone into windows I hear the "plug and play" sound, but don't see no new unit in the "my computer" area.
Should be able to just hold power and volume up for about 10 seconds to force it to reboot to android
jamescable said:
Should be able to just hold power and volume up for about 10 seconds to force it to reboot to android
Click to expand...
Click to collapse
Nope, it doesn't. If I do that, it goes back to the 1+ screen, then goes black, and then instead of loading OxygenOS, goes to Qualcomm Crashdump...
Alohran said:
Nope, it doesn't. If I do that, it goes back to the 1+ screen, then goes black, and then instead of loading OxygenOS, goes to Qualcomm Crashdump...
Click to expand...
Click to collapse
Then yeah, your only option is msm. Even if you sent it to one plus, that's the tool they use. You could always factory reset in recovery but once again, that will delete your stuff. Either way, you lose it all

Categories

Resources