Database Info

Bricked? Please help, phone barely boots... Wifes phone and she is ticked

Some background... The whole reason I was rooting this phone was the volume button was malfunctioning... constantly pressing up. I used the hack-ace tool linked somewhere else and followed the directions. At one point during the install the phone went black and the red light began to blink... in command prompt window it just said waiting for device for a long time. Now all it will do it go into the clockworkmod recovery screen. If I try to restart hack ace it says the sd card is either not mounted or corrupted. Any help?!? this is my wifes phone so I need to fix it fast!

soniktoothe said:
Some background... The whole reason I was rooting this phone was the volume button was malfunctioning... constantly pressing up. I used the hack-ace tool linked somewhere else and followed the directions. At one point during the install the phone went black and the red light began to blink... in command prompt window it just said waiting for device for a long time. Now all it will do it go into the clockworkmod recovery screen. If I try to restart hack ace it says the sd card is either not mounted or corrupted. Any help?!? this is my wifes phone so I need to fix it fast!
Click to expand...
Click to collapse
When did you use AAHK? It has recently been retired and the files it needs are gone, so using it now can get you stuck. If you have CWM the phone was either S-Off or bootloader-unlocked at some point. Which is it?

bananagranola said:
When did you use AAHK? It has recently been retired and the files it needs are gone, so using it now can get you stuck. If you have CWM the phone was either S-Off or bootloader-unlocked at some point. Which is it?
Click to expand...
Click to collapse
Thanks so much for the quick reply! IT had no rooting done before today, it had gotten a little ways into the rooting before it quit... That must be how CWM is on there. It had gotten to the point of HBoot being installed when it quit.

soniktoothe said:
Thanks so much for the quick reply! IT had no rooting done before today, it had gotten a little ways into the rooting before it quit... That must be how CWM is on there. It had gotten to the point of HBoot being installed when it quit.
Click to expand...
Click to collapse
What does hboot say? In case you don't know how to get there, reboot holding power and volume-down.

bananagranola said:
What does hboot say? In case you don't know how to get there, reboot holding power and volume-down.
Click to expand...
Click to collapse
The only thing I can get into is CWM, and it is tricky getting it to run... I think it quit before loading HBoot... TO do that I have to pull the battery and have it hooked up by USB, then turn it on.

Hold volume down as you do your power up procedure
Sent from my ADR6425LVW using Tapatalk 2

soniktoothe said:
The only thing I can get into is CWM, and it is tricky getting it to run... I think it quit before loading HBoot... TO do that I have to pull the battery and have it hooked up by USB, then turn it on.
Click to expand...
Click to collapse
Turn off your phone (you can pull the battery), then hold power and volume-down.

dlamber7 said:
Hold volume down as you do your power up procedure
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
It doesnt seen to respond to that...

Do you have adb? You could try adb reboot bootloader.

bananagranola said:
Do you have adb? You could try adb reboot bootloader.
Click to expand...
Click to collapse
Is that accessed from cwm?

soniktoothe said:
Is that accessed from cwm?
Click to expand...
Click to collapse
From your computer. You will need to install adb.

bananagranola said:
From your computer. You will need to install adb.
Click to expand...
Click to collapse
Okay, I have the adb installed and went through the process of connecting my inspire with the adb. A serial number came up so assume all is not lost because it installed the drivers for this device.
Where shall I go from here? Once again I can't say thanks enough...

Connect your phone and type adb devices. If it finds a device, type adb reboot bootloader. What does it say?

Send him over to #aceroot, it will be faster.
Sent from a dream.

Yeah, do what Tei says. Head to the freenode channel #AceRoot.

Webchat.freenode.net
In channel put "#aceroot" without the quotation.
Sent from a dream.

Thanks for your time last week on this, today the phone booted up with one press of the power button. No idea what happened but whatever glitch there was... it appears to have worked itself out.

Go there and get it set up properly anyway. That should have never happened.
Sent via LG E970 SlickROM v6

[Q] Random rebooting does not stop

Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas

majorcrampas said:
Hi
This is a well known issue with the nexus 5. My device permanently starts rebooting. The google Logo occurs and then it rebotos again. There is no start animation. If I press the power and volume down bottom I just see the bootloader screen and after half a second it reboots. I can't do anything.
My phone is rooted (no custom ROM) and before I go back to the shop I want to unroot it. However, with this behaviour I'm not able to do it, or is there any chance? Does someone know at least, how I can boot normaly to unroot it.
thanks for your help
crampas
Click to expand...
Click to collapse
Hello, take a look at this thread http://forum.xda-developers.com/showthread.php?t=2513701

Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app

sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3

kboya said:
Is this really a well known issue? What were you doing directly beforehand? What have you tried to do to fix it? Have you tried using fastboot commands to reload factory images? Are you a toolkit only user? Have you tried a factory image through that?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Well IMHO it is a well known issue (see for example the wikipedia page or just have a look in tech forums). Directly before, I was writing an SMS and put it in my pocket (everything seems fine at that moment). 10 minutes later I just want to check my SMS and then it was already rebooting all the time. This was not the first time, I had this issue 2 todays before, but after approximatley 20 reboots it started correctly.
So far I was not able to use fastboot commands, since I can't enter fastboot. I didn't use a toolkit.

32299564
Madpiercing said:
sorry, i overlooked that you cant enter fastboot.take a look here instead http://forum.xda-developers.com/showthread.php?t=2521691&page=3
Click to expand...
Click to collapse
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.

majorcrampas said:
Thanks for the link. I will check it later, 'cause I have to leave. I will write again and let you know if I'm able to enter fastboot.
Click to expand...
Click to collapse
no problemi, i hope you can unbrick it!

Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.

mistahseller said:
Use this thread:
http://forum.xda-developers.com/showthread.php?t=2513701
Or you can use this toolkit (some people are not fans of these but I am):
http://forum.xda-developers.com/showthread.php?t=2525026
I have never heard of the issue where it was only rooted and it just randomly decides to reboot and keeps doing it for no reason at all without the user flashing something that it did not like. So are you saying that you cannot even turn the phone off it just keeps going into a bootloop and trying to enter fastboot does nothing?
I don't think this is a really well known issue.. Have not seen to many support threads about this.
Click to expand...
Click to collapse
If the wall charger is plugged into the phone, the nexus just starts rebooting. I see the white Google logo and after one or two seconds it reboots. Sometimes you see the boot animation (4 circles) but after a short time it restarts the phone not able get to the point where you unlock the SIM. Trying to get into fastboot mode is also not possible. The fastboot mode appears but after half a second the phone reboots again. If the nexus is not connected to a charger it repeats rebooting for about four times after that just a black screen appears. If I'm not able to get into fastboot mode I can't unroot the phone, right? So the links you shared are not useful in my case
I have the nexus now over a week and the phone worked perfectly fine the first week.
I have uploaded two films of the problem to youtube, see this link. One film is with the nexus plugged into the chrager and one where it isn't.

That is very strange.
I would definitely use Madpiercing's post and link to http://forum.xda-developers.com/showthread.php?t=2521691&page=3 to try and fix it.

Madpiercing said:
no problemi, i hope you can unbrick it!
Click to expand...
Click to collapse
I tried the method described in your link without success. Still the same behavior. See my last post, there I add a youtube-link where you can see what exactly happens.

Saw your video that is very strange

mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
The very strange thing is, that it worked well over a week. the random rebooting starts two days ago, first time it starts again correctly after 5 min. Now it seems to hang in a loop.

mistahseller said:
Saw your video that is very strange
Click to expand...
Click to collapse
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just starts working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happened while to rooting the phone?

majorcrampas said:
After a while I was able to get into the fastboot mode: I plugged my nexus into the wall charger for about 1 hour. Then it booted correctly. I had plugged my nexus into the charger before (over night) without leading to the same result. It seems that it just startes working correctly as random as it crashes
Do you think it is a bug in the bootloader or that something happend due to rooting the phone?
Click to expand...
Click to collapse
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.

jd1639 said:
It's most likely a hardware issue, bad cache memory on the cpu. I'd rma it.
Click to expand...
Click to collapse
I set it up again and give it another try. If something similar should happen again, I will rma it.

majorcrampas said:
I set it up again and give it another try. If something similar should happen again, I will rma it.
Click to expand...
Click to collapse
make sure you unroot and relock the bootloader and do this now while it is working.

mistahseller said:
make sure you unroot and relock the bootloader and do this now while it is working.
Click to expand...
Click to collapse
And triangle away or reset the flag or whatever.
Sent from my Nexus 5

boot loop - can't navigate bootloader to get into recovery mode

hi there,
I'm running CM11 nightly late feb. For no apparent reason my phone went into a boot loop this morning (n.b. I didn't flash a new rom or installed a new app). Now it constantly reboots (literally) and doesn't get further than the CM11 boot video or google logo.
If I press volume down and power, it will head into bootloader - but - I can't navigate beyond 'shut down' or 'restart bootloader'. It doesn't execute two consecutive volume up or down commands. In other words, it's impossible to get into recovery mode. Also, because my phone doesn't boot further than the video or logo, I can't make a fastboot or adb connection via my laptop.
Does anybody know how I can fix this issue? I'm clearly running out of luck. Many thx in advance!

reflash recovery?

Try to boot into recovery with cmd: fastboot boot TWRP.img (TWRP or your current custom recovery)
Then restore a nandroid backup or wipe data/system/dalvik
You can still flash the factory images. Fastboot mode is enough. Guide

suikerchiller said:
Now it constantly reboots (literally)
Click to expand...
Click to collapse
Stuck power button. Mash the power button really fast for 20 seconds to unstick whatever is in there.

gd6noob said:
reflash recovery?
Click to expand...
Click to collapse
can't flash anything, because phone is constantly rebooting. Have opened up the phone and took the battery out for 1 minute. Didn't help either. After starting up the phone I get stuck in the boot loop again.
Anyone else an idea?

suikerchiller said:
can't flash anything, because phone is constantly rebooting. Have opened up the phone and took the battery out for 1 minute. Didn't help either. After starting up the phone I get stuck in the boot loop again.
Anyone else an idea?
Click to expand...
Click to collapse
The phone doesn't reboot in the bootloader right?
If it doesn't either do what primokorn said or flash the factory image.
Sent from my Nexus 5

El Daddy said:
The phone doesn't reboot in the bootloader right?
If it doesn't either do what primokorn said or flash the factory image.
Sent from my Nexus 5
Click to expand...
Click to collapse
Well the issue is that it only stays for a fraction of a second in bootloader, which gives it enough time to navigate one step up or down. Not enough time to get into recovery.
How can I do what Primoken said? It doesn't seem to be possible to do a flash when the phone is constantly rebooting?
Thx for helping me out guys, much appreciated!

suikerchiller said:
Well the issue is that it only stays for a fraction of a second in bootloader, which gives it enough time to navigate one step up or down. Not enough time to get into recovery.
How can I do what Primoken said? It doesn't seem to be possible to do a flash when the phone is constantly rebooting?
Thx for helping me out guys, much appreciated!
Click to expand...
Click to collapse
Have you ever kept your phone in narrow pocket? Because it's definitely sounds to me like a stuck power button.

Simonna said:
Have you ever kept your phone in narrow pocket? Because it's definitely sounds to me like a stuck power button.
Click to expand...
Click to collapse
It's not a power issue. Also unscrewed my phone to see if that was what caused it. Nothing in there, mechanism functioned correctly.
UPDATE: For some reason my phone booted up out of nothing. I managed to flash an older ROM via CM Updater (through settings)- which seemed to work. Apps were updated and it was running normally. But after a couple of minutes it restarted out of the blue and now back to square one again.
Guess there's a chance I'll probably get a normal start up soon. Is it a good idea to do a factory whipe restart through the settings menu? Or is Primokorn's method safer?

suikerchiller said:
...Or is Primokorn's method safer?
Click to expand...
Click to collapse
Yes.

Is my phone dead now?

Hi,
I recently got my phone from service provider they changed the motherboard. I was trying to unlock the bootloader since I have new motherboard it was unsuccessful so I couldn't unlock it. I was in bootloader menu I choose fastboot to unlock it, after a unsuccessful try I decided to reboot. So I choose reboot option but phone stuck at that menu. Nothing happened for 2 minutes. I removed the battery and now I can't open my phone. What should I do now?
edit: after 10 minutes it suddenly decided to boot itself but it's constantly rebooting itself idk what I'm gonna do now.
edit 2: now it's stuck on beats audio logo...
edit 3: I removed the battery, did a factory reset. Now I can reach lockscreen but when I unlock it phone is not responding and it restarts itself.
edit 4: somehow I managed to boot my phone successfully. For test the phone I installed subway surfers I played like maybe 2 minutes and then it was frozen and it made a weird noise from speaker for 5-10 secs and phone restarted itself again. And the bottom of the phone is kind of overheated. Now I figured out that if I wait for 10 minutes and if phone was completely cold it can boot itself but if it's overheated it can't bootself. I really hate this phone.

koolthing said:
Hi,
I recently got my phone from service provider they changed the motherboard. I was trying to unlock the bootloader since I have new motherboard it was unsuccessful so I couldn't unlock it. I was in bootloader menu I choose fastboot to unlock it, after a unsuccessful try I decided to reboot. So I choose reboot option but phone stuck at that menu. Nothing happened for 2 minutes. I removed the battery and now I can't open my phone. What should I do now?
edit: after 10 minutes it suddenly decided to boot itself but it's constantly rebooting itself idk what I'm gonna do now.
edit 2: now it's stuck on beats audio logo...
edit 3: I removed the battery, did a factory reset. Now I can reach lockscreen but when I unlock it phone is not responding and it restarts itself.
edit 4: somehow I managed to boot my phone successfully. For test the phone I installed subway surfers I played like maybe 2 minutes and then it was frozen and it made a weird noise from speaker for 5-10 secs and phone restarted itself again. And the bottom of the phone is kind of overheated. Now I figured out that if I wait for 10 minutes and if phone was completely cold it can boot itself but if it's overheated it can't bootself. I really hate this phone.
Click to expand...
Click to collapse
did you try to use a RUU.exe?

rzr86 said:
did you try to use a RUU.exe?
Click to expand...
Click to collapse
phone is completely stock atm. Can I use a ruu.exe without s-off and unlocked bootloader? And that game / freeze / constant 5 seconds noise problem happened one more time but before all of these problems.

koolthing said:
phone is completely stock atm. Can I use a ruu.exe without s-off and unlocked bootloader? And that game / freeze / constant 5 seconds noise problem happened one more time but before all of these problems.
Click to expand...
Click to collapse
of course you can use it without S-OFF
only your bootloader must be locked or relocked
i assume is still locked since you tried htcdev method

rzr86 said:
of course you can use it without S-OFF
only your bootloader must be locked or relocked
i assume is still locked since you tried htcdev method
Click to expand...
Click to collapse
I bought this phone from Turkey so I downloaded Turkish Ruu file which is: RUU_PYRAMID_LE_ICS_35_S_HTC_TUR_3.32.468.112_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253106_signed.exe but I got 132 signature error which also means that I downloaded wrong RUU file. I'll try to s-off somehow to learn my phone's cid.

koolthing said:
I bought this phone from Turkey so I downloaded Turkish Ruu file which is: RUU_PYRAMID_LE_ICS_35_S_HTC_TUR_3.32.468.112_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253106_signed.exe but I got 132 signature error which also means that I downloaded wrong RUU file. I'll try to s-off somehow to learn my phone's cid.
Click to expand...
Click to collapse
you can use the cid getter app

rzr86 said:
you can use the cid getter app
Click to expand...
Click to collapse
I don't know why but I can't charge and turn on my phone. I think is hard bricked now.

koolthing said:
I don't know why but I can't charge and turn on my phone. I think is hard bricked now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1522351

rzr86 said:
http://forum.xda-developers.com/showthread.php?t=1522351
Click to expand...
Click to collapse
I'm on ubuntu 12.04 now and keep getting device can't be detected error. I think it's completely dead.

koolthing said:
I'm on ubuntu 12.04 now and keep getting device can't be detected error. I think it's completely dead.
Click to expand...
Click to collapse
if you know about jtag method then see this thread
http://forum.xda-developers.com/showthread.php?t=2775115
it is your last option
by the way try this
remove battery,sim and sdcard and charge the device as it is for 4-5 hours
put them back and switch it on
see if it boots

rzr86 said:
if you know about jtag method then see this thread
http://forum.xda-developers.com/showthread.php?t=2775115
it is your last option
by the way try this
remove battery,sim and sdcard and charge the device as it is for 4-5 hours
put them back and switch it on
see if it boots
Click to expand...
Click to collapse
jtag is too complicated for me. I left my sensation to charge overnight like you said but still no luck. Anyways, thank you so much for your help.

koolthing said:
jtag is too complicated for me. I left my sensation to charge overnight like you said but still no luck. Anyways, thank you so much for your help.
Click to expand...
Click to collapse
you take it to a local shop to do it
but know this, it may be expensive

I managed to get to QHSUSB_DLOAD mode. I had this output I dont have any sdx.
Searching for bricked device...
The bricked device is on
Use the above node to perform operations using the emmc_recover tool
Click to expand...
Click to collapse

koolthing said:
I managed to get to QHSUSB_DLOAD mode. I had this output I dont have any sdx.
Click to expand...
Click to collapse
did you try unbricking method again?

rzr86 said:
did you try unbricking method again?
Click to expand...
Click to collapse
ye i tried wire trick in this video https://www.youtube.com/watch?v=_Pcxt6nKI10 and i tried unbricking method.
problem is; in the output there should be a node about sdX
You should get something like sdX. We are interested on that "X"
Click to expand...
Click to collapse
but i didnt get anything about sdx in output... it can detect my device but i can't continue because of this.

OnePlus One - stuck on Resurrection boot

Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.

NSingh95 said:
Hello guys,
I apologize if this has been solved before but I wasn't able to find anything on it.
I have a oneplus one phone which I had running Ressurection Rom (I don't have the details as my father was using it for the last 2 years).
He dropped the phone and gave it to a shop for repairing of the screen. They repaired the screen but now they have somehow messed with the software where I am UNABLE TO BOOT TO FASTBOOT OR TRWP. The function of holding POWER + VOLUME DOWN or POWER + VOLUME UP doesn't work. When I attempt those two options, it still continues to boot as it normally would and then start optimizing apps. Does that for about 45 minutes and then just restarts and repeats the process.
I haven't messed around with android stuff for about a year now, so simplified instructions (rather step by step) would be extremely helpful.
Thank you so much for taking the time.
Click to expand...
Click to collapse
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!

Mr.Ak said:
This condition is called hard brick.To fix this,
https://forums.oneplus.net/threads/...ol-restore-stock-cm11s-fix-bricks-etc.237827/
Use this tool on winXp or win7(don't use 8 or 10),run it as administrator.Make sure you install the drivers correctly,good luck!
Click to expand...
Click to collapse
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you

NSingh95 said:
Hello, Thank you for your response.
I have tried the instructions that you provided and I am stuck in a place where the "Samsung" drivers for OPO are installed but the phone isn't detected by the computer when its plugged in. I assume that means the drivers aren't installed correctly. However, when I do open device manager and attempt to update or uninstall the drivers there isn't a device there that is representative of OPO.
How do I get to the point where the drivers can be installed without me having access to the phone. I can't really go into a bricked phone and turn on ADB etc.'
Thank you
Click to expand...
Click to collapse
Read the whole thread.
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Use Xp or win7(must).

Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?

NSingh95 said:
Okay so I have attempted this a tiring number of times; initially the phone at least was going on to loading apps, now it just flashes on the Resurrection load screen and doesn't change at all. Also when I try to boot into recovery/fastboot, nothing happens.
I have also tried installing different drivers from like a samsung phone, nexus but to no avail.
Is there anyone who can perhaps TEAMVIEW me and help out or live chat?
Click to expand...
Click to collapse
Device on Twrp works fine?

Mr.Ak said:
Device on Twrp works fine?
Click to expand...
Click to collapse
I'm not able to boot into twrp.

NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
@psxda97 ,can this be a battery issue?

Mr.Ak said:
@psxda97 ,can this be a battery issue?
Click to expand...
Click to collapse
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
NSingh95 said:
I'm not able to boot into twrp.
Click to expand...
Click to collapse
Try turning on your phone while connected to a charger.

psxda97 said:
I don't think so. If it is a battery issue he could go to fastboot since fastboot only uses a small amount of charge.
Try turning on your phone while connected to a charger.
Click to expand...
Click to collapse
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.

NSingh95 said:
I have, its definitely not a battery issue, because i have seen the phone stay on for an hour just on the bootscreen without being plugged in or anything.
Click to expand...
Click to collapse
Most probably your volume buttons were messed up during the repair. That's the only reason I can think of. There are some videos on YouTube about fixing the volume buttons.