Hello. A few days ago my one arrived (with two hits in the frame). I used it without any problems until the battery was at 2%, then I put him in charge and when it came to 100% it started to reboot constantly. The few times it doesn't stop on the 1+ screem it works without recognizing the sim only for a maximum of 2 minutes (but usually a few seconds). Then it "restarts to restart". When I had the time to do that I noticed that in the settings the IMEI is unknown. Is this a problem that someone has already had? Is it fixable? I tried everything, all types of wipe and also to flash the stock from fastboot in two different versions but nothing. I unlock the bootloader and I install the CWM recovery to try installing the CM11 or ColorOS but there is no way to transfer them on the phone. Nothing also with twrp. I try adb sideload but it blocks at 17 %. When the pc recognizes the opo the copy of the rom stops in the middle. Adb push doesn't work. Can be an idea try to remove the battery? I don't want to do it if it is not necessary. I opened a request for a replacement but given the long development times I would like to solve by myself. Thank you for the attention and sorry for my bad english.
you can access your phone through adb yeah? have you checked logcat? at what point is it restarting?
eudemonics said:
you can access your phone through adb yeah? have you checked logcat? at what point is it restarting?
Click to expand...
Click to collapse
Yes I can access through adb. I can use the phone for 3 second such 2 minutes, so there is not a fixed point. It restarts when it wants. Five minutes ago I flashed cm11 through otg with cmw, but I didn't solve the problem. A moment ago I flashed coloros through otg but nothing. I completed the configuration, i did two swipes, than it restart the bootloop. I'm going crazy. Francly I don't know logcat
please someone help me
Have u tried to flash via fastboot the full image from cyanogen web site?
Hey bud, I'm having similar problems as you,no imei,reboots,bootlooping...all of it.
Sent from my ME302C using Tapatalk
bagadj said:
Have u tried to flash via fastboot the full image from cyanogen web site?
Click to expand...
Click to collapse
of course, I tried it with the 25r version of the cyanogenmod and also with the 22q many times
tdamocles said:
Hey bud, I'm having similar problems as you,no imei,reboots,bootlooping...all of it.
Sent from my ME302C using Tapatalk
Click to expand...
Click to collapse
It's incredible. I opened a RMA but I am still waiting for a response.
gallici96 said:
Yes I can access through adb. I can use the phone for 3 second such 2 minutes, so there is not a fixed point. It restarts when it wants. Five minutes ago I flashed cm11 through otg with cmw, but I didn't solve the problem. A moment ago I flashed coloros through otg but nothing. I completed the configuration, i did two swipes, than it restart the bootloop. I'm going crazy. Francly I don't know logcat
Click to expand...
Click to collapse
it's an ADB command used for debugging. you might be able to see just what's causing the phone to bootloop.
https://developer.android.com/tools/help/logcat.html
Related
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
Hey guys
So a couple of days ago I was browsing on facebook when suddenly my One froze and rebooted. After that I suddenly didn't have any connectivity.
I figured I might be able to fix this by rebooting the phone, but after the reboot the phone worked for two seconds and then froze, restarted etc.. It keeps doing that.
Now I looked up if this was a common problem and it is, there is also a fix for it. The fix requires fastboot, but I can't get fastboot to work because I get the QHSUSB_BULK error on my PC.
This usually indicates a hardbrick but my phone still starts up, I can also boot into recovery, I just can't use the fastboot.
Is there anyone who can help me?
Thanks in advance.
Unlegit said:
Hey guys
So a couple of days ago I was browsing on facebook when suddenly my One froze and rebooted. After that I suddenly didn't have any connectivity.
I figured I might be able to fix this by rebooting the phone, but after the reboot the phone worked for two seconds and then froze, restarted etc.. It keeps doing that.
Now I looked up if this was a common problem and it is, there is also a fix for it. The fix requires fastboot, but I can't get fastboot to work because I get the QHSUSB_BULK error on my PC.
This usually indicates a hardbrick but my phone still starts up, I can also boot into recovery, I just can't use the fastboot.
Is there anyone who can help me?
Thanks in advance.
Click to expand...
Click to collapse
I believe there is a way to recover from hardbrick by installing colorOS and reinstalling CM.
Please check here: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
CravingMender9 said:
I believe there is a way to recover from hardbrick by installing colorOS and reinstalling CM.
Please check here:
Click to expand...
Click to collapse
Yeah, thanks. Gonna try that one, but I still fear for the phone's inability to use fastboot.
Unlegit said:
Yeah, thanks. Gonna try that one, but I still fear for the phone's inability to use fastboot.
Click to expand...
Click to collapse
No problem. Do let us know how it goes.
So I was going to reinstall Cataclysm ROM because it has been giving me problems the last few days, mainly it's been dropping my WiFi signal forcing me to switch it on and off just to use my phone, like once every minute
So I downloaded the file to my device, and went to flash it, but I wiped the dalvik and cache, and I pressed data I'm pretty sure, 100% by accident cuz I was so mad at my WiFi signal constantly dropping
Anyways now my phone says "No OS Installed, are you sure you want to reboot?"
I just did a few hours worth of research and... nothing seems to work
I've tried a few ADB sideload guides but I can't seem to follow what they're saying since my screen shows something completely different than what theirs shows
I checked a couple forums too and no one else was experiencing what I am
So I've come to you guys to help D:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Any other ideas?
I saw the USB OTG method works, should I just buy one of those and try it out?
It's just like an add on hard drive that I'll load the ROM onto right?
Do I have to flash the stock img or can I flash a new ROM, like Cataclysm again, or Carbon or something?
I'm going to go buy one of those USB OTG drives, a Kingston 32 or 64gb one from Canada Computers
#fingerscrossed it works guys!
If you have anything else for me to try let me know!
devchaube said:
Basically I have TWRP installed, my computer doesn't recognize the device when I use the flashall.bat in Windows, so I tried a few different cables, same thing
Click to expand...
Click to collapse
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
beekay201 said:
Flashall.bat, which uses the program fastboot, isnt meant to be used with a recovery (in this case, TWRP). It is to be used on the bootloader.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Back in business! Picked up a couple of USB 32GB OTGs for $15 each (WICKED)
Plugged them into my PC, transferred 3 ROMs over (Cataclysm, XtraSmooth, and Stock IMG)
Just tried Cataclysm now, and it's working, everything was successful, and no problems!
Damn I love USB OTG
devchaube said:
Yeah the bootloader is the menu with the reccovery, restart BL, and start, and poweroff right
i tried it on that menu too, did not work
be back in an hour, gonna go get the usb otg, good sale right now, $15 for 32gb!
Click to expand...
Click to collapse
If it did not work there, it must have been a missing driver issue. Or your fastboot setup.
Sent from my Nexus 5 using Tapatalk
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
devchaube said:
Okay so I flashed Cataclysm ROM and XtraSmooth ROM but they both give me a black screen after the white "android" logo is done
I think its the black screen of death
Any ideas on how to get rid of it?
Click to expand...
Click to collapse
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Wipe /data before you switch roms
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got it working last night, since I couldn't do it using TWRP or CMD
I just used Wugs Toolkit, selected the bricked / bootloop option, and flashed stock + unrooted it
Loaded the newest imgs available, so I'm good for now
I'll wait a bit, see if the WiFi thing comes back on stock, if not then it was probably something to do with Cataclysm, I didn't even save any logs to hard to see what it was
Thanks for all your help though!
It didn't work because you didn't install the drivers for adb/fastboot properly. Anyhow nice to see your device is working again!
Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!
acmilandroid said:
Hi guys. I have an unlocked AT&T LG G3 D850 and I cannot for the life of me figure out why it's stuck in a bootloop. I've tried just about everything but nothing works. I'm able to access both recovery and download mode, but every time I exit it, I just get thrown into another bootloop. Strangely, I didn't do anything to the phone recently, and it was working absolutely fine minutes before I noticed the bootloop.
First thing I tried was wiping everything and reinstalling the ROM. I am rooted and was running a Marshmallow distro of Resurrection Remix, with TWRP 3.0 (I think) running my recovery. I booted into TWRP and cleared everything, reinstalling the ROM. Didn't work. Okay, so maybe the ROM is to blame. Tried some different versions, still nothing.
I then tried flashing stock firmware using download mode, and kept getting errors at the beginning of the LG flash tool utility. After switching USB ports, it started working. However, after about 30 minutes, it would fail, and I would get a message saying it couldn't communicate with the device. I tried this multiple times to no avail.
Eventually, I ended up running the program one last time and left it for a couple hours. When I got back to check it, I was super relieved because the phone had apparently successfully been flashed back to stock firmware. Keep in mind this process usually only takes 4-8 minutes, whereas my phone took hours to get it done.
Finally, I booted the device, full of hope. NOPE. Bootloop again. I tried resetting it using the volume down combo, but it stays in a bootloop every time.
I am running out of options and getting desperate, and I really don't wanna fork out the cash for another phone if I don't have to. Any help would be greatly appreciated. Thanks everyone!
Click to expand...
Click to collapse
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk
hyelton said:
Did you try choose board_dl on flash tools?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Not yet, but I definitely will. What difference does it make? Thanks for helping!
acmilandroid said:
Not yet, but I definitely will. What difference does it make? Thanks for helping!
Click to expand...
Click to collapse
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk
hyelton said:
When flashing an AT&T choosing that will make the phone boot into mini OS then you'll select reset/restart and it should boot unless there's an hardware issue
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?
acmilandroid said:
It says download failed at 517 seconds. "We can't communicate with phone." Meanwhile, the phone is back at 0%. Should I leave it for a couple hours like I did the one time it actually worked?
Click to expand...
Click to collapse
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk
hyelton said:
Did you freshly put the phone into download mode? And using a usb 2.0 port right?
Sent from my LGLS675 using Tapatalk
Click to expand...
Click to collapse
Yes. However, I'm not sure if I was able to manually boot into download mode or the phone automatically did it. I did pull the battery before connecting the phone, and I did hold volume up. I just don't know if I physically put it into download mode myself.
New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.
acmilandroid said:
New issue. Got to about 89% when I get an "fboot fail" error message. My phone is bootlooping again.
Click to expand...
Click to collapse
Were you able to solve the issue and progress any further???
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.