Develop Bugs

recovery without power button

Hi, let me explain my problem:
I have a desire with power button broken.
last 6 months i use it normally wiht a rooted room (but s-on). When i want to turn on the device I pull off and on the battery twice.
Recently i installed an application and after a reboot the device keeps stuck in the initial splash animation.
So, i ONLY can access to HBoot (0.93 S-on). But i can't enter to recovery to erase userdata and format all and reboot a new room (as usual) because Hboot enter key is the ****ing power button XD.
I tryed to S-OFF in linux with alpharev 1.8 or revolutinary when showing splash but they start and suddenly stop because smthg was wrong.
So the only thing i can do is send basic HBoot commands.
any idea?

You might get more response posting in the correct forum.
Sent from my HTC Desire using Tapatalk

You can download Quick Boot (Reboot) from market. Use it to Reboot, Recovery, Bootloader or Power Off.
Anyway, you're posting this in wrong section, should be in Q&A.

ckpv5 said:
You can download Quick Boot (Reboot) from market. Use it to Reboot, Recovery, Bootloader or Power Off.
Anyway, you're posting this in wrong section, should be in Q&A.
Click to expand...
Click to collapse
Mate, his device is not even reaching the bootanimation, I wonder what kind of market you suppose him to have to use it in splashscreen or bootloader?
Sent from nowhere

tajimura said:
Mate, his device is not even reaching the bootanimation, I wonder what kind of market you suppose him to have to use it in splashscreen or bootloader?
Sent from nowhere
Click to expand...
Click to collapse
Haha.. I got confuse with his statement " When i want to turn on the device I pull off and on the battery twice." So I thought he can boot the phone Wrong section wrong answer
Thanks anyway

Code:
[strike]fastboot oem gencheckpt[/strike]
Good development you've got going here.

Mate flash an original wwe stock rom with its own flash utility (just run the executable) but you will loose root after that use the alpharev utility once your phone has started.
Sent from my HTC Desire using XDA

I had this same problem a while ago. Tried many apps to work around power button (mine was stuck "pressed"). Got to the point where I couldn't do anything without getting into recovery. Used a spare phone until I ordered the flex cable assembly from Ebay.. $40 or so..
Despite many years of working with electronics, it was still quite nerve racking to swap the part out... you have to re-use your camera module and a couple plastic parts stuck to the original (on back of volume buttons i think).
Read instructions and watched videos online several times before starting, and again as I did the work, and size/fit was ever so slightly off... but everything works now and I am a relieved and happy camper

I see the development is active for 4 days now.
Sent from my HTC Desire using Tapatalk

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
And please do not swear in Posts

HOX won't boot

Hello, i'm sorry that my first post on this forum is an question about my no longer working htc one x. I have been gathering information of this forum for a long time, and allways helped me, but this time i am really stuck. So in advance i thank you for all the help you already have given me
This is what happened
my first HOX had a defect sim reader, was declared DOA so i got a new one, so far so good
but after using the phone for about 2 weeks,
all apps started closing one at a time, untill the phone went black (it was still on, but nothing was working)
at first i tought i installed a bad app, so reset the phone to factory settings.
after i did that it worked for a few days untill the same phenomenon happened again.
this time i reset the settings via the power+volume button boot menu, and in android wiped the SD card.
again it worked for a few days,
untill it all started going haywire.
all the apps i installed the last time where whatssap and dropbox (no games and such)
now i rarely can get my phone to boot, or go into recovery.
when i connect it to my charger it has no red light.
if i get it to boot, i usually cant get past the sim unlock screen.
i have been thinking about returning it, or installing another rom (wich i have done before on my htc desire wich worked great)
problem is, i cant go into android to tick on the usb debug.
sorry for the long post, i'd be really happy if you could help me out in this one.
my htc is from the dutch vodafone provider.
cheers,
Schella

schella said:
Hello, i'm sorry that my first post on this forum is an question about my no longer working htc one x. I have been gathering information of this forum for a long time, and allways helped me, but this time i am really stuck. So in advance i thank you for all the help you already have given me
This is what happened
my first HOX had a defect sim reader, was declared DOA so i got a new one, so far so good
but after using the phone for about 2 weeks,
all apps started closing one at a time, untill the phone went black (it was still on, but nothing was working)
at first i tought i installed a bad app, so reset the phone to factory settings.
after i did that it worked for a few days untill the same phenomenon happened again.
this time i reset the settings via the power+volume button boot menu, and in android wiped the SD card.
again it worked for a few days,
untill it all started going haywire.
all the apps i installed the last time where whatssap and dropbox (no games and such)
now i rarely can get my phone to boot, or go into recovery.
when i connect it to my charger it has no red light.
if i get it to boot, i usually cant get past the sim unlock screen.
i have been thinking about returning it, or installing another rom (wich i have done before on my htc desire wich worked great)
problem is, i cant go into android to tick on the usb debug.
sorry for the long post, i'd be really happy if you could help me out in this one.
my htc is from the dutch vodafone provider.
cheers,
Schella
Click to expand...
Click to collapse
mmh i read about same problem with someone, here on xda, are your bootloader unlocked?
it seems to be a firmware problem, so you can try to install a ruu if it's available, and if it's not, you can try to ask for htc or vodafone to change it with another hox, or you can unlock bootloader and install a custom firmware, hoping that it will not give you the same problem! (unlocking bootloader MAY void all or part of your warranty)>>it depends only from htc... in some country they don't care, in some other, they will not repair it.

aha
glukosio said:
mmh i read about same problem with someone, here on xda, are your bootloader unlocked?
it seems to be a firmware problem, so you can try to install a ruu if it's available, and if it's not, you can try to ask for htc or vodafone to change it with another hox, or you can unlock bootloader and install a custom firmware, hoping that it will not give you the same problem! (unlocking bootloader MAY void all or part of your warranty)>>it depends only from htc... in some country they don't care, in some other, they will not repair it.
Click to expand...
Click to collapse
i believe it is alowed here, but this was exactly my dilemma.. i think i'm going to return it for it is the safest option i guess. Maybe it is an hardware failure. thanks for the reply! my bootloader is locked btw

[Q] HOX all stock, not booting

Hello,
I know booting issues are possible when opening the bootloader and messing with kernels and rom flashing but that's not my case and I couldn't find a post that helped me so I hope someone can help me out on this.
I am a member of the HTC User Trial program and I'm currently testing the 3.09.401.100 Jelly Bean ROM, all stock, not rooted, never opened the bootloader or flashed any firmware besides official HTC RUU when OTA came out late (UK device, always last to get official OTA )
Last night I left my phone on before I went to sleep and it had low battery. This morning I tried to turn it on and it didn't work so I thought that the battery went out. Naturally, I plugged my phone to the charger and the red led didn't light red to indicate charging for a 30sec-1minute period, than it flashed red a few times and afterwards it lighted up red as if the phone was charging. I've left the phone turned off to charge for about 3.5 hours (even after the led turned green, just to get it really fully charged).
Now, when I try to turn the phone on, it get's stuck in the "HTC ONE" bootscreen with the beats audio logo at the bottom.
Long press on the power button reboots the phone but the issue repeats and the phone does not boot past the boot screen with the logo.
Couldn't attach my HBOOT photo so here's a link: https://www.dropbox.com/s/oxk8yz19ew0gi6s/hboot.jpg

Same
I'm having the same problem with an unlocked bootloader

sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean

Bram89 said:
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Click to expand...
Click to collapse
Contacted HTC with this issue and they are not familiar with it as well. They have asked me to send a bugreport using ADB and told me that a factory reset may be required.
I will update if anything new pops up.

What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)

Vcek said:
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Click to expand...
Click to collapse
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.

IdanK said:
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
Click to expand...
Click to collapse
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?

Vcek said:
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Click to expand...
Click to collapse
I got the update directly from HTC as I'm a member on the User Trial program, no flashing what so ever, just plain OTA download & install.
I was chosen to participate in the User Trial program because I'm also a member on HTC Elevate and they asked users to join the program for testing One X software update.

[Q] Multiple problems, one cause?

Hi there.
At some point in your life, your mobile phone will hit the street hard. It was the first time in 12 years for me (missed the inner pocket of my jacket, and it fell right down). Screen: wasted. Ive got it replaced by an original glass/lcd unit. 150 euros, but not the 290 euros that HTC wanted for it.
For a week i was very happy, but all of a sudden i started to get com.google.process.gapps errors, not solvable by the download manager fix, account sync fix, whatever. Hard reset helped only temporarily. I did notice however that problems started to occur after two minor HTC updates for contacts / sms that came OTA. Hard reset let me choose again: do you want to install the updates? This time i chose NO, and the error happens way less often (but still exists). Of course, this can be caused by the shock on the pavement as well. However, a lot of times there are no problems at all noticable. At other times, making photos does not work (you hear shutter sound, but no picture on SD)
At that point, i noticed that the volume down + power does no longer bring me into the bootloader / recovery menu as it did before. With the all in one toolbox for htc one X i can enter the bootloader menu >>locked<<. Choosing boot to recovery, only shows me a red triangle with an exclamation mark, and a phone.
The same red triangle i get to see when i choose 'get token ID'. I do not get a token idea, it just hangs on the red triangle screen.
My original plan was to install a new rom (venom) to hopefully prevent the errors, but at this point i think there are first other problems to solve.
At this point i still use a rom that came with my phone, updated OTA.
The HTC i have is :
android 4.1.1
sense 4+
software no 3.14.161.27
it is vodaphone NL branded.
Can it be that somewhere some system files are damaged or is there some way to check if this is indeed the case?
If you would boot to recovery: what should you see instead of the red triangle?
Hopefully this story is a bit comprehensible, otherwise i will add info if requested for it.

System files shouldn't be buggered, because a hard reset resets them.
You have stock recovery, you shouldn't see anything besides the triangle.
Looks like a hardware problem to me.
You could've tried a RUU, but none exists for your main version.

I think the problem with the motherboard when your phone had hit the ground
it maybe with the sd card as you say that you don't get photos in camera app even after the shutter sound
but it is surley a hardware problem and I have a question where did you repare it ?

elmaghraby said:
I think the problem with the motherboard when your phone had hit the ground
it maybe with the sd card as you say that you don't get photos in camera app even after the shutter sound
but it is surley a hardware problem and I have a question where did you repare it ?
Click to expand...
Click to collapse
Repair was not at HTC. Which voids my warranty anyway. Although the hit on the floor did that too.
At the moment, camera functions as it should again. Weird.
I also noticed that after i did a hard reset, problems with the gapps n all started as soon as play reinstalled programs. (that just happened).
Could it be caused by some 3rd party software as well? (i hardly have any though)

3rd party apps should not interfere with the gappspackage.
The red triangle you see when choosing recovery is normal.
The red triangle is the stock recovery.
To get your unlock token you need to be in fastboot mode and not recovery.
Contrary to what the other poster said. Doing a hard reset does not touch your system files. It only erases userdata.
To count out any software you can find an ruu for your software version. You can find plenty of instructions on this in the forums. It will fully reflash a stock ROM
Sent from my HTC One X using xda app-developers app

My Galaxy Nexus in a boot-loop (I need help!)

Sorry if the thread is not in the right place and not fancy written, I don't use forums a lot..
So I've had that phone for about 3 years now. I've never rooted the device, never installed any custom roms, nothing. Only did a factory reset/wiped data couple of times.
One day I woke up (on 2nd of January), looked at my phone (it was charging whole night) and it was showing the "Google" logo. After that it switched to "colorful X", then it turns off, vibrates and all over again.
I was doing it until I took out the battery for a half an hour. Plugged it back in, turned on... Same thing was happening.
I've removed the battery again and plugged it back in. Pressed the power + vol up + vol down buttons in order to get into the bootloader. Got to the "recovery" and wiped the data/factory reset, and wiped the cache.
Restarted, didn't work.
Got mad here and decided to first time to attempt installing a rom. I've got to the google developer website where there are factory images. There were a couple of versions of the Galaxy Nexus. I didn't know which one to pick, so I've picked the first one (GSM with google wallet latest version). (I've already had Android SDK) so I've followed the instructions by using the "fastboot oem unlock"
then "flash-all". It failed. And the reason is when it rebooted, the bootloader locked again and the script couldn't continue installing/flashing.
So every time I unlock the bootloader and reboot, it locks it again.
I've decided to flash every img individually. By using this pattern:
fastboot oem unlock
fastboot flash bootloader bootloaderblabla.img
fastboot reboot-bootloader
fastboot flash...... and every single image including the radio, boot system, etc....
basically every time I flash and reboot, I unlock the bootloader.
That however didn't fix the problem, it was still remaining in the bootloop.
So I am not sure which version of the galaxy nexus I have, I've tried doing that will few versions of the factory images with no success.
So I came here, in a chance to get it fixed by some magic!
Please help?

Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.

Same thing happened to me and I changed my motherboard
Sent from my Galaxy Nexus using XDA Free mobile app

playitlouder said:
Corrupted EMMC (internal memory chip).
Currently no solution to this, unfortunately.
Basically the firmware of the internal Memory Chip screwed up. The firmware on the memory thinks your data might be in danger and switches to read only mode (these firmwares are similar to SSDs for PCs, so thats a good thing in general). So if you unlocked your bootloader, you could retrieve your data.
This is however solveable by reflashing the chips firmware, but it's unshure if this even could be done while the chip is soldered onto the motherboard.
Check the latest pages of the CM12.1 thread, there was some discussion about this topic. If you find a good phone repair place they might have a JTAG flashbox and could reflash the EMMC.
Other soultion would be to replace the board.
Click to expand...
Click to collapse
Ahh that's unfortunate, I think it's better to upgrade to a new phone.. It became laggy anyway.
Thanks!

Hello, please for help, I will not create new thead.
I have a problem, I'm tring to start phone and stucks on bootloop.
The solution should be start recovery, but my second problem is volume down doesn't work.
Is any chance to get to recovery throught ADB while phone is turned off?
Thanks.