I'm pretty sure I'm bricked now. Black ATT One X. Flashing updated twrp so I can flash 4.4 roms, but wasn't paying attention and typed boot instead of recovery out of habit. Now my phone only goes to htc splash screen and turns off again. I can't get into recovery or fast boot. I'm bricked aren't I?
Rcox100 said:
I'm pretty sure I'm bricked now. Black ATT One X. Flashing updated twrp so I can flash 4.4 roms, but wasn't paying attention and typed boot instead of recovery out of habit. Now my phone only goes to htc splash screen and turns off again. I can't get into recovery or fast boot. I'm bricked aren't I?
Click to expand...
Click to collapse
I'm assuming you are holding down the power and volume down keys at the same time to get into the bootloader?
Sometimes you have to hold both buttons (power button and volume down button) for 10 to 15 seconds. I've had to do this multiple times in a row to get out of a bootloop in the past.
If the phone attempts to boot and you can see the splash screen then you are not bricked yet. Bricked means nothing happens when you push the power button.
Madcat8686 said:
I'm assuming you are holding down the power and volume down key at the same time to get into the bootloader?
Click to expand...
Click to collapse
Yes. Doing that doesn't do anything until I take my fingers off, then it tries to do a normal boot and powers off again.
What command did you type exactly?
There is a fastboot command for just booting a recovery.IMG (fastboot boot recovery.img), but it wouldn't cause the problem you are having. It would just boot you into that recovery without actually flashing it.
Edit: what are your phone specs?... i.e. carrier, hboot version, etc...
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
What command did you type exactly?
There is a fastboot command for just booting a recovery.IMG (fastboot boot recovery.img), but it wouldn't cause the problem you are having. It would just boot you into that recovery without actually flashing it.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yeah I typed "fastboot flash boot recovery.img" on accident, pretty sure I ****ed up
Rcox100 said:
yeah I typed "fastboot flash boot recovery.img" on accident, pretty sure I ****ed up
Click to expand...
Click to collapse
Sounds like you flashed recovery to your boot partition.
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Sounds like you flashed recovery to your boot partition.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah that's what I was assuming, and I'm also assuming this kills the phone.
Black!Jack said:
Sounds like you flashed recovery to your boot partition.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes indeed. I was just about to type that most call it a "soft brick". I know how to fix this on other devices but not this one yet. I'm looking around for HTC specific info
Rcox100 said:
Yeah that's what I was assuming, and I'm also assuming this kills the phone.
Click to expand...
Click to collapse
Can you connect to your phone via fastboot at all?
Edit: have you tried a hard reset... Holding the power button down until the lights flash like 12 times?
Sent from my One X using XDA Premium 4 mobile app
Black!Jack said:
Can you connect to your phone via fastboot at all?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No, cant get to bootloader or fast boot, and computer can't see it when its off
Madcat8686 said:
Yes indeed. I was just about to type that most call it a "soft brick". I know how to fix this on other devices but not this one yet. I'm looking around for HTC specific info
Click to expand...
Click to collapse
Well its effectively a hard brick then if theres no info on solving it I guess
Rcox100 said:
No, cant get to bootloader or fast boot, and computer can't see it when its off
Click to expand...
Click to collapse
When its at the splash screen does it recognize adb or fast boot?
Try adb devices and fastboot devices
Sent from my One X using XDA Premium 4 mobile app
Try holding the volume down button while the phone is booting, keep holding it and when it begins the loop again hopefully it'll get you to bootloader.
Sent from my Evita.
Black!Jack said:
When its at the splash screen does it recognize adb or fast boot?
Try adb devices and fastboot devices
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Its too fast for that
btw if a mod sees this can they approve me or something so I can reply more often
Rcox100 said:
Its too fast for that
btw if a mod sees this can they approve me or something so I can reply more often
Click to expand...
Click to collapse
Did you try what timmaaa suggested?
Sent from my One X using XDA Premium 4 mobile app
If what I suggested doesn't work and there's absolutely no way to get to the bootloader or get fastboot to work, you're kinda screwed. You'll probably have to try getting a jtag repair done, I think that'll be your only option.
I doubt a moderator is going to bump up a new user's status just because you need to reply more often, it doesn't really work like that.
Sent from my Evita.
timmaaa said:
Try holding the volume down button while the phone is booting, keep holding it and when it begins the loop again hopefully it'll get you to bootloader.
Sent from my Evita.
Click to expand...
Click to collapse
Ok i just pushed down the power and then quickly pushed down volume without pressing power and I'm in bootloader now! My device is recognized also.
Rcox100 said:
Ok i just pushed down the power and then quickly pushed down volume without pressing power and I'm in bootloader now! My device is recognized also.
Click to expand...
Click to collapse
Good! You need to flash a valid boot.img to your boot partition. Absolutely do not reboot the phone until you've done that.
Sent from my Evita.
Rcox100 said:
Ok i just pushed down the power and then quickly pushed down volume without pressing power and I'm in bootloader now! My device is recognized also.
Click to expand...
Click to collapse
That is good news...looks like you are back on the road, congrats!
timmaaa said:
If what I suggested doesn't work and there's absolutely no way to get to the bootloader or get fastboot to work, you're kinda screwed. You'll probably have to try getting a jtag repair done, I think that'll be your only option.
Sent from my Evita.
Click to expand...
Click to collapse
Agreed. Unless you can get fastboot access back to overwrite your boot partition, your in a pickle. In any event, hopefully this will serve as a lesson to you concerning the detail and care you need to show when it comes to altering your phones.
Sent from my One X using XDA Premium 4 mobile app
Related
hey guys, i got a bootloop. usually i can get into recovery through adb, but this time my device isnt showing. is there an alternative i can use likeodin or something?
bestofrhcp said:
hey guys, i got a bootloop. usually i can get into recovery through adb, but this time my device isnt showing. is there an alternative i can use likeodin or something?
Click to expand...
Click to collapse
power + volume up, then use 'fastboot devices' in adb see if it comes up.
Billchen0014 said:
power + volume up, then use 'fastboot devices' in adb see if it comes up.
Click to expand...
Click to collapse
Power+up is good for boot loops but if you have a recovery installed you can access it through the boot loader menu
Sent from my Nexus S 4G using Xparent Red Tapatalk 2
ebs512 said:
Power+up is good for boot loops but if you have a recovery installed you can access it through the boot loader menu
Sent from my Nexus S 4G using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
No, stay on the bootloader interface, don't press anything, connect it to ur PC and type this in adb: fastboot devices see if you can see your phone's serial number.
oops! accidentally beamed from my awesome NEXUS S!
It doesn't show my device in the list on adb Command or fastboot
Sent from my Nexus One using XDA
bestofrhcp said:
It doesn't show my device in the list on adb Command or fastboot
Sent from my Nexus One using XDA
Click to expand...
Click to collapse
That's bad, I recommend to hand it in for repairs, since you can't even connect it to a PC nor boot into recovery.
oops! accidentally beamed from my awesome NEXUS S!
I got it going close one! Thanks anyways for giving the time to suggest some advice.
Sent from my Nexus S using XDA
bestofrhcp said:
I got it going close one! Thanks anyways for giving the time to suggest some advice.
Sent from my Nexus S using XDA
Click to expand...
Click to collapse
hey do you mind telling me what you did because the same thing just started to happen on my nexus , thanks in advance
hi.... i need help!!!!
i have the same problem stated above . my phone automatically switches on if the battery is inserted. i cant use the volume keys when in fastboot mode(even the power key doesnt work). any advice ??? i have done remedies to the best of my knowledge though...should this phone be brought to service (center)??? im running on stock ics 404
Hating life right now. Broken power button, once I get into fastboot it says 'No boot or recovery img' and fastboot doesn't respond and doesn't show up as a device during adb. Any tips or am I royally ****ed?
http://forum.xda-developers.com/showthread.php?t=1524858
Kitch16 said:
Hating life right now. Broken power button, once I get into fastboot it says 'No boot or recovery img' and fastboot doesn't respond and doesn't show up as a device during adb. Any tips or am I royally ****ed?
Click to expand...
Click to collapse
Step 1:
Download the appropriate factory image from: https://developers.google.com/android/nexus/images#sojuimm76d and make sure you have a working fastboot tool on your computer.
The thing is. I can get to fastboot, but it just doesn't respond, I can't use the volume keys during it...
Kitch16 said:
The thing is. I can get to fastboot, but it just doesn't respond, I can't use the volume keys during it...
Click to expand...
Click to collapse
Pretty sure your screwed. Same thing happened to me and there is nothing to do.
Sent from my Nexus S using xda premium
xsteven77x said:
Pretty sure your screwed. Same thing happened to me and there is nothing to do.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I'll send it back to Samsung. Hope they give me a new one :') doubt it though
Hey guys,
I found your forum after I gave a guy my phone so he could root it but he couldn't deliver. However, when I got back the phone it took longer to boot up and after it got past the "HTC One X" screen, instead of allowing me to put in my PIN to unlock (as usual), it sent me to a blank screen showing only my current wallpaper and the task bar (with the time, power, signal, etc).
The major part of the screen is unresponsive. The three buttons below are unresponsive as well.
I'm able to pull the task bar down and when I click the "settings" button I get this message: "unfortunately the process com.android.settings has stopped"
What does this mean for my phone? Can this be fixed?
Any help would be great. I've done a bit of reading, but I'm still very new to this. The phone is an AT&T HTC One X, 1.85, running 4.0.3.
Thanks in advance.
YAJones
YAJones said:
Hey guys,
I found your forum after I gave a guy my phone so he could root it but he couldn't deliver. However, when I got back the phone it took longer to boot up and after it got past the "HTC One X" screen, instead of allowing me to put in my PIN to unlock (as usual), it sent me to a blank screen showing only my current wallpaper and the task bar (with the time, power, signal, etc).
The major part of the screen is unresponsive. The three buttons below are unresponsive as well.
I'm able to pull the task bar down and when I click the "settings" button I get this message: "unfortunately the process com.android.settings has stopped"
What does this mean for my phone? Can this be fixed?
Any help would be great. I've done a bit of reading, but I'm still very new to this. The phone is an AT&T HTC One X, 1.85, running 4.0.3.
Thanks in advance.
YAJones
Click to expand...
Click to collapse
Yes it should be fixable but we don't know what that person did to your phone.. if he never got to the point of changing the cid. You can just run the 1.85 ruu and then root it yourself if you want because its not difficult. Or if root intimidates you you cab stay stock.
If he did happen to change the cid youll have to unlock the bootloader if its not already and either flash a ROM or s-off and then ruu.
I'm sure this can seem like a lot but everything will be fine. What I need to see is the information in your bootloader. And your cid.
How to get into your bootloader: press and hold power while your phone is on until the back home and recent apps buttons blink 5 times and then shuts off. Once the screen is off. Wait 2-3 seconds and then press and hold power and volume down.
Show me the bootloader.
Sent from my One X using xda app-developers app
exad said:
Yes it should be fixable but we don't know what that person did to your phone.. if he never got to the point of changing the cid. You can just run the 1.85 ruu and then root it yourself if you want because its not difficult. Or if root intimidates you you cab stay stock.
If he did happen to change the cid youll have to unlock the bootloader if its not already and either flash a ROM or s-off and then ruu.
I'm sure this can seem like a lot but everything will be fine. What I need to see is the information in your bootloader. And your cid.
How to get into your bootloader: press and hold power while your phone is on until the back home and recent apps buttons blink 5 times and then shuts off. Once the screen is off. Wait 2-3 seconds and then press and hold power and volume down.
Show me the bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi Exad,
Thanks for a quick reply.
OK... after holding down the power button and waiting for the buttons to blink, the phone does not go off... it reboots. Any ideas?
YAJones
Hold power and volume down at the same time. When lights stop flashing release power but continue to hold volume down.
Sent from my HTC One X using xda premium
Venomtester said:
Hold power and volume down at the same time. When lights stop flashing release power but continue to hold volume down.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Or hold down power button till the power menu pops up. Choose "restart". As soon as you hit restart, hold down ONLYthe volume down button till it goes to a white screen with 3 skating droids
Sent from my One X using Tapatalk 2
Venomtester said:
Hold power and volume down at the same time. When lights stop flashing release power but continue to hold volume down.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks Venomtester... that worked like a charm.
I've attached a picture of the screen as you asked Exad. Please tell me what you think.
YAJones
You're welcome. Exad will get you going.
Sent from my HTC One X using xda premium
YAJones said:
Thanks Venomtester... that worked like a charm.
I've attached a picture of the screen as you asked Exad. Please tell me what you think.
YAJones
Click to expand...
Click to collapse
Remove pic and blur ur imei
Sent from my HTC One XL using xda app-developers app
31ken31 said:
Remove pic and blur ur imei
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Done. Thanks 31ken31.
InflatedTitan said:
Or hold down power button till the power menu pops up. Choose "restart". As soon as you hit restart, hold down ONLYthe volume down button till it goes to a white screen with 3 skating droids
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
No need to hold volume down when shutting off. Only for coming back on into bootloader. Just tested.
Sent from my One X using xda app-developers app
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
YAJones said:
Done. Thanks 31ken31.
Click to expand...
Click to collapse
You're probably supercid. You'll need to unlock the bootloader and s-off. You should install the HTC drivers and fastboot and get to work. Do you want to be rooted and stuff or stock?
The reason I ask is, we will proceed differently if you just want to stay stock but if you intend to flash Roms and whatnot, we will unlock root and s-off and downgrade touchscreen firmware.
Sent from my One X using xda app-developers app
exad said:
No need to hold volume down when shutting off. Only for coming back on into bootloader. Just tested.
Sent from my One X using xda app-developers app
---------- Post added at 12:54 PM ---------- Previous post was at 12:47 PM ----------
You're probably supercid. You'll need to unlock the bootloader and s-off. You should install the HTC drivers and fastboot and get to work. Do you want to be rooted and stuff or stock?
The reason I ask is, we will proceed differently if you just want to stay stock but if you intend to flash Roms and whatnot, we will unlock root and s-off and downgrade touchscreen firmware.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi Exad,
Yes I would like to get this phone rooted.
What are the next steps to do this?
YAJones said:
Hi Exad,
Yes I would like to get this phone rooted.
What are the next steps to do this?
Click to expand...
Click to collapse
Do you have the HTC Drivers, fastboot/adb installed?
If not, Get ADB/Fastboot. Unzip and keep in a folder somewhere. Remember where. I use C:\Android myself. You can have yours wherever is most convenient.
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
HTC Drivers:
http://forum.xda-developers.com/showthread.php?t=2126036
Once you've installed those:
Boot to Bootloader/Fastboot
Plug your phone in to your PC
Shift right click inside the folder where you keep ADB/Fastboot and click in the menu "Open Command prompt here"
Then type in command prompt: fastboot oem readcid
And show me what it says after.
exad said:
Do you have the HTC Drivers, fastboot/adb installed?
If not, Get ADB/Fastboot. Unzip and keep in a folder somewhere. Remember where. I use C:\Android myself. You can have yours wherever is most convenient.
http://forum.xda-developers.com/attachment.php?attachmentid=1179735&d=1344782533
HTC Drivers:
http://forum.xda-developers.com/showthread.php?t=2126036
Once you've installed those:
Boot to Bootloader/Fastboot
Plug your phone in to your PC
Shift right click inside the folder where you keep ADB/Fastboot and click in the menu "Open Command prompt here"
Then type in command prompt: fastboot oem readcid
And show me what it says after.
Click to expand...
Click to collapse
< waiting for device > is the message that comes up in the command prompt window (and a flashing cursor on the line below).
YAJones said:
< waiting for device > is the message that comes up in the command prompt window (and a flashing cursor on the line below).
Click to expand...
Click to collapse
Did you select fastboot in the bootloader and install that driver?
formal ecesidu
exad said:
Did you select fastboot in the bootloader and install that driver?
Click to expand...
Click to collapse
Actually I just did and it says <bootloader> cid: CWS__001
OKAY [ 0.006s]
finished. total time: 0.006s
YAJones said:
Actually I just did and it says <bootloader> cid: CWS__001
OKAY [ 0.006s]
finished. total time: 0.006s
Click to expand...
Click to collapse
Next is temp root to change cud to supercid
Sent from my HTC One XL using xda app-developers app
no next is to RUU since OP can't use his phone currently.
Now here's the thing. I am not sure how far the last guy got with your phone. Your HBOOT says tampered.. If he modified the HBOOT, there's a chance you will full, unrecoverably brick. I don't want to be responsible for this happening. That's why I am telling you this. Here's the link if you want to take the risk.
http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe
31ken31 said:
Next is temp root to change cud to supercid
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks 31ken31.
How do I do a temp root? Forgive my ignorance.
exad said:
no next is to RUU since OP can't use his phone currently.
Click to expand...
Click to collapse
That's right. And how to do the RUU?
YAJones said:
That's right. And how to do the RUU?
Click to expand...
Click to collapse
See my last post, sorry, was updating with link.
Run that exe file with your phone plugged in, in bootloader/fastboot. It will, hopefully, return your phone to a working state.
Hey guys, I can't get my phone to boot up after flashing something that it didn't like and I can't get back into recovery because my volume buttons don't work. Anyone know of a way I could get it into recovery another way. When I turn the phone on it only boots to the warning about my bootloader being unlocked and that's it! Help, please!!
Sent from my SCH-I535 using Tapatalk
jakereeves31 said:
Hey guys, I can't get my phone to boot up after flashing something that it didn't like and I can't get back into recovery because my volume buttons don't work. Anyone know of a way I could get it into recovery another way. When I turn the phone on it only boots to the warning about my bootloader being unlocked and that's it! Help, please!!
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Is it recognized by adb or fastboot?
Sent From My Droid Ultra
Well, whenever I tried adb I typed "adb devices" and nothing came up and then I tried the command to reboot recovery and it said there was no device, so I guess it is not recognized by adb :/
Sent from my SCH-I535 using Tapatalk
jakereeves31 said:
Well, whenever I tried adb I typed "adb devices" and nothing came up and then I tried the command to reboot recovery and it said there was no device, so I guess it is not recognized by adb :/
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
How bout
fastboot reboot recovery
Sent From My Droid Ultra
What'd you flash?
Sent from my XT1080 using XDA Free mobile app
the issue here is that the buttons are not working, try pressing power and volume with something like a toothpick to get through fastboot or recovery
Caseyk621 said:
How bout
fastboot reboot recovery
Sent From My Droid Ultra
Click to expand...
Click to collapse
It just says "waiting for device"
akellar said:
What'd you flash?
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
It was some mod thing called Malivebooster.
Jaocagomez said:
the issue here is that the buttons are not working, try pressing power and volume with something like a toothpick to get through fastboot or recovery
Click to expand...
Click to collapse
I don't think that's gonna work. I've already taken the whole phone apart and I got to where the buttons push and there were like no buttons there. I figured the little buttons should look like the power button, but they didn't.
Sent from my SCH-I535 using Tapatalk
Guys, it just booted all the way up...it's been like this for the past week and I kept rebooting it and stuff and I rebooted it right now and it booted up for some reason!
Sent from my DROID MAXX using XDA Free mobile app
Hey Guys!
So I had Cyanagonmod on my Nexus 5 for quiete a while now. But yesterday my phone suddenly turned off. I've tried to boot it but all it does is showing me the Google-Logo and the "Unlocked"-Logo for a second and it reboots again and I see the same thing.
Important:
1. It only boots if it is connected via USB (Wallcharger, or connected to PC)
2. If I try to boot in the Bootloader through pressing the volume buttons + the power button it just reboots after a second and the google logo appears again
3. the computer doesn't recognize the phone even though it's connected
-> I already tried to fix the problem with the Nexus 5 Toolkit but as I said the PC doesn't even know that it's connected.
PLEASE HELP ME!
I thank you for your answers and your support!:good:
Sounds to me like your power button is stuck. If you have a case, take it off. Then try mashing the power button a number of times.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds to me like your power button is stuck. If you have a case, take it off. Then try mashing the power button a number of times.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thank you for your answer.
I can get into recovery mode for a second. That means that the power button reacts and is working.
I really think that this is more a software than a hardware problem
jeseven7 said:
I really think that this is more a software than a hardware problem
Click to expand...
Click to collapse
Really? What software problem affects the ROM, bootloader AND recovery? Answer below.
None
Its button or NAND issue.
Sent from my Nexus 5 using Tapatalk
rootSU said:
Really? What software problem affects the ROM, bootloader AND recovery? Answer below.
None
Its button or NAND issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is NAND the flash? Well but how am I able to access recovery?
If you wanna know how it looks like when it boots here's a YT-Video that looks just like mine
watch?v=jzj73qYg5HA
(can't post URL's under 10 posts)
jeseven7 said:
Is NAND the flash? Well but how am I able to access recovery?
If you wanna know how it looks like when it boots here's a YT-Video that looks just like mine
watch?v=jzj73qYg5HA
(can't post URL's under 10 posts)
Click to expand...
Click to collapse
It *could *.partially boot then fail although its note.likely a button issue...
Sent from my Nexus 5 using Tapatalk
jeseven7 said:
Is NAND the flash? Well but how am I able to access recovery?
If you wanna know how it looks like when it boots here's a YT-Video that looks just like mine
watch?v=jzj73qYg5HA
(can't post URL's under 10 posts)
Click to expand...
Click to collapse
by press power button + volume down, how you are supposed to. theres no key combo to get into your recovery, you go into the bootloader then press recovery. if your power button is stuck, then the moment you enter the bootloader, it gets pressed down to boot up normally.
rootSU said:
Really? What software problem affects the ROM, bootloader AND recovery? Answer below.
None
Its button or NAND issue.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Is NAND the flash? Well but how am I able to access recovery?
If you wanna know how it looks like when it boots here's a YT-Video that looks just like mine
watch?v=jzj73qYg5HA
(can't post URL's under 10 posts)
EDIT: SORRY! I got the Recovery Mode and the Bootloader mixed up! I ment that I only can boot into the BOOTLOADER for a second and I can't even reach the Recovery Mode because it just starts rebooting.
jeseven7 said:
EDIT: SORRY! I got the Recovery Mode and the Bootloader mixed up! I ment that I only can boot into the BOOTLOADER for a second and I can't even reach the Recovery Mode because it just starts rebooting.
Click to expand...
Click to collapse
Yes, so the power button is probably stuck.
jeseven7 said:
Is NAND the flash? Well but how am I able to access recovery?
If you wanna know how it looks like when it boots here's a YT-Video that looks just like mine
watch?v=jzj73qYg5HA
(can't post URL's under 10 posts)
EDIT: SORRY! I got the Recovery Mode and the Bootloader mixed up! I ment that I only can boot into the BOOTLOADER for a second and I can't even reach the Recovery Mode because it just starts rebooting.
Click to expand...
Click to collapse
because your power button is stuck. once you enter the bootloader it would press down to boot.
okay thank you guys!
do you have any suggestions what I can do?
Obviously I can't get any warranty service because they'll see that the bootloader is unlocked
jeseven7 said:
okay thank you guys!
do you have any suggestions what I can do?
Obviously I can't get any warranty service because they'll see that the bootloader is unlocked
Click to expand...
Click to collapse
well, if you bought it through google, they dont care, if its a hardware issue. its google themselves that made it so you can unlock the bootloader easy. btw, they made it so you can lick your bootloader just as easy.. fastboot oem lock.
jeseven7 said:
okay thank you guys!
do you have any suggestions what I can do?
Obviously I can't get any warranty service because they'll see that the bootloader is unlocked
Click to expand...
Click to collapse
If you bought from the Play Store, Google doesn't care about that.
simms22 said:
because your power button is stuck. once you enter the bootloader it would press down to boot.
Click to expand...
Click to collapse
Okay makes sense. But how is the power button set at the moment? Is it like pressed down the hole time?
And what are your suggestions? What should I do? Obviously I dont have any warranty because they'll see that my bootloader is unlocked
jeseven7 said:
Okay makes sense. But how is the power button set at the moment? Is it like pressed down the hole time?
And what are your suggestions? What should I do? Obviously I dont have any warranty because they'll see that my bootloader is unlocked
Click to expand...
Click to collapse
Google don't care about locked / unlocked. If you bought it from.play...
Sent from my Nexus 5 using Tapatalk
jeseven7 said:
Okay makes sense. But how is the power button set at the moment? Is it like pressed down the hole time?
And what are your suggestions? What should I do? Obviously I dont have any warranty because they'll see that my bootloader is unlocked
Click to expand...
Click to collapse
if you bought it from anyone but google, thwn you dont have a warranty. yea, its acting as pressed down the whole time. see if you can somehow "lift" it up.
a
rootSU said:
Google don't care about locked / unlocked. If you bought it from.play...
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yea I bought it from the play store.
Is it also okay if I have flashed a custom rom (Cyanogenmod) on it? I always thought that this would make your warranty invalid
jeseven7 said:
a
Yea I bought it from the play store.
Is it also okay if I have flashed a custom rom (Cyanogenmod) on it? I always thought that this would make your warranty invalid
Click to expand...
Click to collapse
if its a hardware issue, it doesnt matter what rom you are running, they will take care of you.
simms22 said:
if its a hardware issue, it doesnt matter what rom you are running, they will take care of you.
Click to expand...
Click to collapse
yea that would be logical but these dumbass companies always look for a reason NOT to give you the warranty
jeseven7 said:
yea that would be logical but these dumbass companies always look for a reason NOT to give you the warranty
Click to expand...
Click to collapse
Except it doesn't matter to Google as long as it's a legitimate hardware fault. And stuck power buttons have been accepted many times before.