Hi, I'm new here so don't know if i'm posting this in the right place but here it goes... Ok i gave my HTC Inspire to a friend to install the MIUI ROM to it. Afterwards it was running smoothly and had no problems with it. A few days later my Inspire notified me that it had an update to the ROM. At first i wasn't sure to install it because it is a custom ROM and not the default one, but did the update anyways through the phone. Again, the phone worked normal all day, but at some point the screen started glitching untill it turned completly off.
The one strange thing is that the phone seems to function normally because when charged and "turned on" i can hear the sounds and notifications(like email, text and app notifiactions). Also when i connect it to my computer, it recognizes the device.
That happened about three days ago and I have not been able to discover what really is the problem and how to fix it. If there's anyone that could help me i would REALLY appreciate it.
Thanks in advance,
Marialo
most likely was a bad update.
You should boot into recovery and reinstall miui everything should be back.
Keep in mind the devs have to set miui for each device, chances are you updated to the wrong base.
That's what i thought but can't boot into recovery because i can't see the screen... Any advice on that?
Btw, thks for the quick response
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Ok thanks; will try that then.
marialo said:
Ok thanks; will try that then.
Click to expand...
Click to collapse
or while the phone's on, if you have ADB installed - open a cmd prompt and navigate to where ADB is and type "adb reboot recovery"
Yup try what they said that should work. If not ruu the ruin and really root
sent from the dark obelisk
Ok, tried with the volume and power button, but nothing happened. Thanks for the advice, but I'm kind of new with all this and don't really know how to do the other stuff that you guys told me to do... :S Should I get someone that knows a bit more or is it something that i could do with a little info. from the internet?
anudist said:
Try shutting off the phone completely and booting into your bootloader the old fashioned way by holding down the volume down key, press power, and release volume down once you see the bootloader screen.
If your screen doesn't work during that, you may have a hardware problem on your hands.
Click to expand...
Click to collapse
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
marialo said:
I don't know if you would know but... If it were hardware problems; you think I could claim that to htc? Since the phone hasn't had any accidents or anything... :/
Click to expand...
Click to collapse
If its rooted warranty won't cover this. Get the ruu (stock exe) from the HTC support site and run it. If the phone still has a black screen after its been returned to stock then the problem is hardware related
sent from the dark obelisk
Related
I noticed that I couldn't control the volume when in Gingerbread, I restarted the Nexus S. The Nexus S is now booting into the recovery menu by default, I can't boot into the OS.
The volume in the recovery menu works as expected (though slightly delayed), the real problem is that the power button has the same function as the volume up.
My phone is rooted and the bootloader is unlocked, this was done several months ago though.
Any help would be greatly appreciated, thanks!
Sounds like you lost your OS, you need to re-install the rom through recovery. Just Wipe your data and cache, mount usb, transfer the rom to your sd, and install. EZ PZ
smoka206 said:
Sounds like you lost your OS, you need to re-install the rom through recovery. Just Wipe your data and cache, mount usb, transfer the rom to your sd, and install. EZ PZ
Click to expand...
Click to collapse
Thanks for the reply, I was able to boot into the OS using the fastboot command "fastboot reboot". I then flashed a previous backup I made three months ago, sadly this did nothing to alleviate my problem. I am convinced this is a hardware failure of some sort.
I have now flashed an unrooted stock rom and locked the bootloader as I intend to invoke warrenty and send it over to Samsung.
Naturally, this had to happen right when Ice Cream Sandwich launches on the Nexus S.
Yes my friend this happened to my buddy as I was lucky enough to get fastboot to recognize the pc after hundreds of tries so I could lock the bootloaders back up
Let me guess does your phone turn on by itself when you plug it in to charge?
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
Yes my friend this happened to my buddy as I was lucky enough to get fastboot to recognize the pc after hundreds of tries so I could lock the bootloaders back up
Let me guess does your phone turn on by itself when you plug it in to charge?
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
Woah, come to think of it my phone did turn on by itself! And it took me at least an hour for fastboot to recognize my phone. I assume your friend sent it in under warrenty? How long did it take until he got a replacement?
MikeUter said:
I noticed that I couldn't control the volume when in Gingerbread, I restarted the Nexus S. The Nexus S is now booting into the recovery menu by default, I can't boot into the OS.
The volume in the recovery menu works as expected (though slightly delayed), the real problem is that the power button has the same function as the volume up.
My phone is rooted and the bootloader is unlocked, this was done several months ago though.
Any help would be greatly appreciated, thanks!
Click to expand...
Click to collapse
Sounds like your volume key is broken and the volume down key is always pressed.
adam900710 said:
Sounds like your volume key is broken and the volume down key is always pressed.
Click to expand...
Click to collapse
That is what I thought at first, but the power button will not execute like it should.
He has some sort of best buy warranty and I just gave it back to him today with locked bootloaders
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
If your without warranty what I would do is install cyanogen mod and use the volume wake option or if you want to use ICS then get goto lock screen app from the market and use that to wake the device with the volume wake option
I say this because his power button went out completely and there was a major problem with his USB connection
Its like the power button is always being held in. This problem started for him before flashing any custom rom,it made it really hard to root and because mounting storage and fastboot drivers sucked but hang in there and keep this post alive as I'm going to take it apart tomorrow and see if something is loose or not making good connection
Were you hard on it? he is as we work in a sugar factory
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
mike216 said:
If your without warranty what I would do is install cyanogen mod and use the volume wake option or if you want to use ICS then get goto lock screen app from the market and use that to wake the device with the volume wake option
I say this because his power button went out completely and there was a major problem with his USB connection
Its like the power button is always being held in. This problem started for him before flashing any custom rom,it made it really hard to root and because mounting storage and fastboot drivers sucked but hang in there and keep this post alive as I'm going to take it apart tomorrow and see if something is loose or not making good connection
Were you hard on it? he is as we work in a sugar factory
BEST DAMN PHONE BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
Click to expand...
Click to collapse
I should still have warranty with Samsung as I bought my phone in May. I don't think I was too rough with my phone, that said it's in my pocket most if the time. The power button works fine, the volume up is another story. Thanks for helping.
no problem mike,please keep me posted on how your return to samsung turns out and if there are any obsticles you have to go through
mike216 said:
no problem mike,please keep me posted on how your return to samsung turns out and if there are any obsticles you have to go through
Click to expand...
Click to collapse
I called Samsung, they told me I could take it into my local Rogers store to get it repaired. When showing the Rogers employee what was wrong my phone just magically started working again, it seemed to good to be true. And as it turned out it was, as my phone cannot send or receive calls. Hopefully I won't be without a Smartphone for too long.
Thanks for all the replies everyone.
Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?
Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak
mustakg said:
Hi,
The same thing more or less happened to me.
My phone went dead one night and wouldnt turn on, charge or connect with the PC. I had already arranged a repair with HTC for another issue and so I sent it off to them and a few days later I now have it back and it is working fine so far.
They replaced the mainboard and a few other bits and pieces all under warranty.
I hope you get your phone fixed and sorted asap.
Mustak
Click to expand...
Click to collapse
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.
TP-Power said:
Hi guys,
I've run into some problems, I installed Android Revolution HD 6.5 two days ago. Everything worked like a charm, now I shutted down my phone to go in recovery, sadly enough my phone won't reboot, does not charge nor does it respond to my desperate pushes on the power button. Anyone experienced anything like this?
Worth mentioning also is that the battery was 80+% charged.. So it would seem strange to me that this would anything to do with eventual dead battery.
Just to be clear: hadn't installed anything, nothing less, nothing more.
If I could just get acces to bootloader through usb or anything like this.
I fear that there is someting seriously wrong here?
What are you guys thinking? Any possible solutions?
Click to expand...
Click to collapse
Hi,
Is there any chance the battery pins could be damaged or bent?
Is there any way for you to get hold of another battery(from a shop or friend) and try that?
I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?
TP-Power said:
I will test the battery in the laboratory tomorrow.. I've read you should get a minimum of 3.6V or something like that? Curious to see what has caused this problem. Do you think htc would see I flashed a custom rom on it if I send it to repair?
Click to expand...
Click to collapse
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.
malybru said:
Hi,
That is why i suggest a different battery.
If they can switch it on,they will see the s-off.
If they cannot,it does not matter.
Click to expand...
Click to collapse
They don't use a JTAG unit or anything like that to see what has went wrong than I presume? Well, first thing I'll do is test it right away at the laboratory. I will post the result in the evening.
TP-Power said:
Did you root it or anything like that? It really seems like an hardware issue.. Thanks for your reply also btw.
Click to expand...
Click to collapse
My sensation was rooted and had a custom ROM on, but I was preparing to send the phone back in when it got bricked. I had managed to install stock rom and do S-on but the phone had an unlocked bootloader using HTC dev website, so I was worried they wouldnt do the repair.
As it happens they did all the work under warranty and didnt say/ mention having unlocked bootloader. It has come back locked though.
Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks
asuen06 said:
Was anybody able to find a fix for this?
My sensation 4g has basically the same problem. After rooting and installing ICS it worked fine for a few days then it ceased booting or responding to a charger (no LED response). I was able to turn on the phone again by letting it sit for a while but no luck lately. I'm wondering if my phone is bricked?
When I press the power button the screen stays black with lights on (no LED).
I can't get into bootloader and the phone is not detected by ADB, I tried the unbricking project thread by Dexter, however my phone is not detected by linux. On windows, i did get it to detect as qhsusb_dload.
Any thoughts would be helpful!
Thanks
Click to expand...
Click to collapse
If your getting QHSUSB DLOAD I'm so sorry to tell you as I believe your device is HARD BRICKED. You can try jtag. If you search there are several companies who will jtag. I'm wishing you the best and I'm sorry about your device.
Sent from my HTC Sensation 4G using xda premium
I had to return my HTC Sensation to the repair center. Apparently the motherboard just fried. I got a new motherboard and just S-OFFed the phone again. Very weird problem though. As has been said in this post earlier, if they can't turn on the device they won't see it is S-OFFed and your warranty will apply.
Hey Guys,
a friend of mine just bricked his HTC-OneS and I'm here to help him get it back to life
He installed the latest PacMan Rom and everything was awesome.
All over sudden the Phone didn't boot up anymore.
It can be charged via USB, so maybe one can do something over USB
Windows-PC doesn't recognize the Phone he says...
As far as I remember its an HTC One s ville c2 (is there anything like this)
Due to the Fact that I'm a Motorola User, I have no idea where to start trying to recover his Phone...
Please Help me do it
do you know how to use some adb/fastboot commands? run fastboot oem getcid in the bootloader.
hold down volume down and power to go into the bootloader.
I would try to get into the bootloader first. That would provide a gateway to possibly fixing his (or her) phone.
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
I don't think I've ever seen a tool like that. I think the best bet would be to get into recovery, mount and try to flash a new rom (C2 roms in this case).
esok44 said:
Hope to get into bootloader, will get hands in his phone in monday.
Coming from Motorola i'm used to a factory tool where i can flash official Firmware via PC. Is there anything like this for HTC phones?
If not first thing i would try is flashing a New recovery system via fastboot to have sth to work with. Anyone agree with this plan?
Sent from my XT925 using xda app-developers app
Click to expand...
Click to collapse
Yes, go to androidruu.com, look for villec2 and click on it. The latest RUU should work unless he is carrier branded. Then you will need to use a carrier RUU.
Got hands on his phone and it doesnt do anything...
No bootloader nothing.
Only thing that happens is that it recognizes its on a wallplug...
Sent from my XT925 using xda app-developers app
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
esok44 said:
Anyone got an idea?
The little charging LED is red, is it possible that there is some kind of battery driver missing, so the phone won't charge anymore and the battery is empty?
and is there an option to solve this?
Click to expand...
Click to collapse
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
tivofool said:
Really sounds like it is hard bricked.
I could mention things that you have already most likely tried.
Holding power down for 30 seconds
holding power down for 10 seconds under bright light so the front sensor registers (prevents messing up your phone while in your pocket)
when plugged in computer, does device manager show it as "qhsusb_dload" (bricked)
Hold power down and volume down for 10 seconds. release power button and continue holding volume down.
From replies from manufacturer that people post here, often they replace the battery and (motherboard?) Seems like something happens and a sudden battery discharge messes up the works.
Click to expand...
Click to collapse
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
esok44 said:
Thank you for your response
So quick question, due to the fact that the Phone is hard bricked, can i send the Phone back in, and get things fixed, cause the Phone was s-off and rooted before, so warranty is void.
Is there any way they could find out about it? Like a blown fuse or anything?
Click to expand...
Click to collapse
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
tivofool said:
Your guess is as good as mine. There was one guy who posted here, that they did fix it, and when they sent it back they had turned back on security, or S-on. So they obviously knew and didn't care. One of those ymmv. I kind of doubt he did anything wrong and it is a defect. People post on here with completely stock w/ same symptoms.
Click to expand...
Click to collapse
Thank you dude, will give it back to him and tell him, that he should send the phone back, cause it seems like this is a common problem
Greetz Esok
Hey guys I need some help asap! I have had my Nexus 5 for about 2 weeks now. I had rooted it and put in cwm recovery. The other day I had switched over art from Dalvik. Later in the day I was using linux deploy from the app store. About an hour after when i was browsing the web the device returned an error stating that the devices memory was full..... I knew there was no way. I powered off the device and that was the last of it. It does not power on in the traditional sense it does not go into recovery it does not go into fastboot and it certainly not the OS. Just a black screen. However it does get recognized as a QHUSB device when connected to a PC after fussing with the drivers adb or fastboot drivers no matter the version do not work the device will appear in device manager as though it is there but running adb devices or fastboot devices returns no devices. After extensive driver version attempts and toold nexus rootkit etc i have found that the slightly responsive driver for anything is the LG AndroidNet Diagnostic driver. Although QPST hangs when trying to download via Sahara and CDMA workshop will connect but it does it fails when trying to read from phone. I know there are tools for devices in the same situation. Is there one for the nexus 5? Or can someone help me recover this bad boy? This version is the google play version and not the t-mobile or sprint variant. HEEELP!!!!!!!!!! Thanks.
Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app
Tried it
bitdomo said:
Try to turn off your phone. I know it looks like it is turned off but it's not. Press power button about 10secs then release it and then press and hold it with the two volume keys. You should find yourself in the bootloader and there you could flash stock rom back.
If that not works. Connect the phone to the pc. Open up device manager. Press and hols power button and when the qhusb dissapears press and hold both volume keys while you still pressing the power key. You may end up again in qhsusb, try to wait a little bit more with the pressing both volume keys after each try.
I hope it will work, but I know a guy who bricked his device like you with cwm, his phone also appears as qhusb device on the pc and he could not recover.
Tha last thing you can do is send it back to google to recive a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
Why did you pull the battery? You could have rma'd it.
jd1639 said:
Why did you pull the battery? You could have rma'd it.
Click to expand...
Click to collapse
Thank you your comment is of help right now....
joutcast said:
Thank you, I have tried that and it does not work. My fear is that I will not be able to return as I have pulled the battery and have custom software.
I was hoping there was some way to recover when the device is in the LG Android diagnostic mode.
Click to expand...
Click to collapse
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app
bitdomo said:
If there is no traces or signs you removed the battery (like finger prints or damaged back cover) then google will never find out you have custom rom on your device, because they cant turn it on. It does not worth the effort to google to somehow hack the data out from the broken flash chip. What they will do is that they try to turn it on, then they see it is not possible so they flas stock rom through qhusb ans that wipes all the data of your phone and reformat everything. Or maybe unbricking the device does not wort the effort too and google just send you a replacement device.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT???? I know it can be done on other devices as shown in the link below
http://forum.legija.net/showthread....g-galaxy-S4-(i9505-and-similar)-via-USB-Cable
joutcast said:
OK, GREAT that first option they do....DOES ANYONE KNOW HOW TO DO THAT????
Click to expand...
Click to collapse
You are asking for help with it. To answer your question. It's called jtag and lots of people know how to do it. I'd look for "mobile tech videos". QHUSB is a true brick.
EDIT: Or you could just RMA it. I think that might have been what you where asking to begin with. lol
@joutcast dude it sounds bricked. I'm sure Google will give you another device if you RMA it.
I'm very serious. Im Not being smart about it. I highly doubt Google will do anything to check unless you left obvious traces of it being tampered.
Sent from my Nexus 5 using Tapatalk
You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.
Work the problem and not each other.
Thread Cleaned
_MetalHead_ said:
You need to JTAG it. It'll cost you about $65 and you'll have a working phone again. I'd check craigslist for JTAG in your area, a lot of people are doing it now.
And stop being so sensitive.
Click to expand...
Click to collapse
Sensitivity is what I do best LOL. I went ahead with the RMA route and have been with out a phone for over 15 days. The reason being I am unemployed and could not afford the $450 for an advanced replacement. I still have not heard a peep out of Google as to when I can even think about getting a tracking number from them..... What cracks me up is the fact that if I had done an advanced RMA the hold on my card would of fallen off a long time ago and at that point they still would not have any security on the device. Not only that they have had my phone since Tuesday of this week.
I literally just woke up this morning and its stuck in a bootloop. It constantly reboots, and when i get into recovery mode it waits a second and then selects the thing thats on-screen. Really aggravating. Every time i use recovery i can only get upto either Restart bootloader<Start>Poweroff before it selects whats on screen.... This is the weirdest problem ever it boots into recovery why the F*** would it not let me select what i want. Is there a way to manually do anything through ADB??? Wasnt even flashing anything, was on the same custom rom for a few months.
Extreme solution if better one isn't found: flash factory image
Sent from my Nexus 5 using XDA Premium 4 mobile app
Sounds like another stuck power button.
rootSU said:
Sounds like another stuck power button.
Click to expand...
Click to collapse
Yep its exactly that, someone told me to tap it repeatedly under the power button and it booted up for a few seconds. Im rooted and i cant remember how long ive had it, can i RMA it? Ive still got all my personal stuff on it which puts me in a dilemma :S
GalaxySN00B:0 said:
Yep its exactly that, someone told me to tap it repeatedly under the power button and it booted up for a few seconds. Im rooted and i cant remember how long ive had it, can i RMA it? Ive still got all my personal stuff on it which puts me in a dilemma :S
Click to expand...
Click to collapse
If you bought it from Google play, you can RMA it in its current state. LG where you send it if you bought it anywhere else, can be a bit trickier.
You may be able to pull the power button a bit to aliviate the issue
rootSU said:
If you bought it from Google play, you can RMA it in its current state. LG where you send it if you bought it anywhere else, can be a bit trickier.
You may be able to pull the power button a bit to aliviate the issue
Click to expand...
Click to collapse
Thanks for that, I did buy it from Google and ive got the box so thats a plus. How will i tell them whats wrong with it, through email or do you have to ring them up and tell them?
GalaxySN00B:0 said:
Thanks for that, I did buy it from Google and ive got the box so thats a plus. How will i tell them whats wrong with it, through email or do you have to ring them up and tell them?
Click to expand...
Click to collapse
I've no idea, never had to RMA. Just tell them the truth. It's rebooting and cannot boot into anything because you suspect a stuck power button
rootSU said:
I've no idea, never had to RMA. Just tell them the truth. It's rebooting and cannot boot into anything because you suspect a stuck power button
Click to expand...
Click to collapse
Noted, thanks again
No probs