hi everyone, I have a challenge for you...
My MZ604 Wifi Xoom is completely unresponsive. No boot logo, no screen nothing.
A few months ago I flashed a US stock to get a hold of the ISC update. it went off without a hitch and I was very happy with it.
A few weeks ago I picked it up and it was black and not booting, even to the logo. Nothing.
The only things that light up are the white charging light when it is plugged in.
When I plug in the USB (Win7x64) it registers as a Motorola Flash Interface and charges through my computer- but not all the time.
I have tried many combinations of button pressing and holding, and the only indications I get that it is working underneath the black screen are the white front light going on and off and the device registering in device manager.
Oh, and it makes the battery low sound when low on battery, which i hope is a good sign.
Adb fastboot does not recognise the device no matter that I do.
Has anyone ever come back from this???
Desperate,
Bloggorus
Bloggorus said:
hi everyone, I have a challenge for you...
My MZ604 Wifi Xoom is completely unresponsive. No boot logo, no screen nothing.
A few months ago I flashed a US stock to get a hold of the ISC update. it went off without a hitch and I was very happy with it.
A few weeks ago I picked it up and it was black and not booting, even to the logo. Nothing.
The only things that light up are the white charging light when it is plugged in.
When I plug in the USB (Win7x64) it registers as a Motorola Flash Interface and charges through my computer- but not all the time.
I have tried many combinations of button pressing and holding, and the only indications I get that it is working underneath the black screen are the white front light going on and off and the device registering in device manager.
Oh, and it makes the battery low sound when low on battery, which i hope is a good sign.
Adb fastboot does not recognise the device no matter that I do.
Has anyone ever come back from this???
Desperate,
Bloggorus
Click to expand...
Click to collapse
This might be a case for the Motorola Programming cable from the Black Hat Team (google it). You can also make one. There are instructions somewhere in one of these threads.
Have you tried to take the cover off and remove the batter(ies)? Look for the thread with instructions for that. You will need a Torx screwdriver (#5?).
I'll bet you can bring it back.
thanks okantomi,
I just ordered a torx set, hopefully a battery disconnect will work.
Very hard to figure this out, every single search i made for 'bricked xoom' came up with silly buggers with frozen boot screens. Not a real brick at all...
If you don't hear from me again, assume it's fixed!
Thank again
Good luck!
We havent hear from you since so hopefully you fixed your xoom!
Can you share your experience for whoever has simmilar issue....
Thanks
&
Good Luck
Related
OK, so I haven't used my TF for a couple of weeks...it was in a sleeve and I assume the battery died. I went to boot it tonight, and it wouldn't (no real surprise)...so I plugged it in and let it charge for some time...still, nothing.
The screen does turn on, but it remains black - but you can tell the screen still works. Occasionally, when I hold the power button it the whole screen flashes blue and it quickly displays a bit of the Android Alien...never, ever, seen a blue screen with the Android logo on the tablet.
Anyway, I can't get it to boot. I've tried holding the power button, tried booting while holding the Vol+ and Vol- button...still, nothing.
Any ideas? Searching yields nothing like this...it's similar to the deep sleep, but clearly the screen still wakes (but remains black), and then I get a little flash of blue, too.
Thanks fellas.
polkadots said:
OK, so I haven't used my TF for a couple of weeks...it was in a sleeve and I assume the battery died. I went to boot it tonight, and it wouldn't (no real surprise)...so I plugged it in and let it charge for some time...still, nothing.
The screen does turn on, but it remains black - but you can tell the screen still works. Occasionally, when I hold the power button it the whole screen flashes blue and it quickly displays a bit of the Android Alien...never, ever, seen a blue screen with the Android logo on the tablet.
Anyway, I can't get it to boot. I've tried holding the power button, tried booting while holding the Vol+ and Vol- button...still, nothing.
Any ideas? Searching yields nothing like this...it's similar to the deep sleep, but clearly the screen still wakes (but remains black), and then I get a little flash of blue, too.
Thanks fellas.
Click to expand...
Click to collapse
I've Googled again and again...nothing...all it does when I try and boot is flash to an old school Windows style blue screen...It flickers so I can't make out what it all says, it's doing some kind of memory check (?)...and something else, I think...but that's it. I tried this too: http://www.addictivetips.com/mobile/how-to-unbrick-asus-eee-pad-transformer-honeycomb-tablet/
Is this thing FUBAR???
Nobody has any clues about what to do hear? Seriously?
I can't even get it to boot...the screen turns on, but remains black, unless it flashes that blue screen...what do?
nvflash a flashable rom...
http://forum.xda-developers.com/showthread.php?t=1123429
"bricked" is such an overused phrase on xda.
EDIT: sorry, didn't click the link on the second post
what does 'it doesn't work' mean in the context of nvflash? does it refuse to connect? does it successfully flash it but not start? more info would be appreciated
Yea, it connects. My computer recognizes it, I can get in ADX (?) mode, it flashes. From my computer side of things it works, but the entire time the NVFlash process is going I don't see anything on my screen. So it appears to work on the computer side of things, but not on the tablet side. I still have the booting problems and the blue screen.
Thanks so much
Sent from my PC36100 using Tapatalk
Probably something hardware on the inside then.
^Agree with the above post
although while you are flashing something, you aren't supposed to have screen activity on it. I hope you didn't pull the plug because of that.
I hope that you can find a solution to your problem, but it might actually be a ram problem or something
Damn...I was afraid it would be hardware related. So, I was (am?) rooted and was running a custom ROM...can I still send this to Asus? Will they replace it, or am I just effed? Thanks guys, I appreciate the insights.
Sent from my PC36100 using Tapatalk
They will replace it, but they might charge you for it. Most of the time you can get away with "custom rom? what does that mean? I just used the installer thingy with the cord in the computer and tablet" Just ask them for an RMA #, they're pretty good at that kind of stuff.
Unless, of course, you overclocked it to something insane and fried the circut board, you should be good to go.
Dyskmaster said:
They will replace it, but they might charge you for it. Most of the time you can get away with "custom rom? what does that mean? I just used the installer thingy with the cord in the computer and tablet" Just ask them for an RMA #, they're pretty good at that kind of stuff.
Unless, of course, you overclocked it to something insane and fried the circut board, you should be good to go.
Click to expand...
Click to collapse
I was running Revolver. Then I followed the unbricking instructions on that link...no change.he in how my TF acted before or after. I filed for an RMA online, and will go that route. No crazy overclocking. Thanks.
Sent from my PC36100 using Tapatalk
Asus told me the screen on mine is dead. i have to send it to them
mine boot but after 2 sec the screen goes black. even when i press the power button it only turns on for 2 sec. good thing i went back to stock before all that madness went down
kinda sucks i wanted to try all the new roms now i gotta wait at least a week still the RMA send it back
same problem black screen flashes blue
same problem as polkadots
screen lights up (i.e. not backlight problem) stay lit and then flashes blue. You have to press power to shut off the black screen (i.e. not backlight problem). I have not tried to do any roms it was a refurbished product that worked fine for a month and then had this problem. have tried hard and soft resets and the black screen comes on and acts like it is working. then it flashes blue upon the touch and goes back to black screen. any ideas? anyone with same problem? do i have to send back to Asus?
I've got a 4G Xoom, that I bought new about 13 months ago. It's been great to me so far. I had it rooted and was running CM 9 on it and had been doing so for about a month without any issues.
Yesterday, it was plugged into the charger and I happen to glance at it and it was doing some strange things with the screen, flashing on/off, black lines on part of the screen. I powered it off and left it alone for an hour or so.
Since then, it's been completely unresponsive. I've tried Vol Up+Power button countless times without it working. The charge light (white) came on briefly while plugged in, but then went off, never to return. The only reaction I can get is that after holding Vol up+Power causes an orange light next to the front camera to blink twice. That's it.
Any suggestions? Is it completly dead?
danman7 said:
I've got a 4G Xoom, that I bought new about 13 months ago. It's been great to me so far. I had it rooted and was running CM 9 on it and had been doing so for about a month without any issues.
Yesterday, it was plugged into the charger and I happen to glance at it and it was doing some strange things with the screen, flashing on/off, black lines on part of the screen. I powered it off and left it alone for an hour or so.
Since then, it's been completely unresponsive. I've tried Vol Up+Power button countless times without it working. The charge light (white) came on briefly while plugged in, but then went off, never to return. The only reaction I can get is that after holding Vol up+Power causes an orange light next to the front camera to blink twice. That's it.
Any suggestions? Is it completly dead?
Click to expand...
Click to collapse
Open up the back take the battery out, put it back in.
Mjamocha said:
Open up the back take the battery out, put it back in.
Click to expand...
Click to collapse
Given that it's sealed, how is this done? I hadn't even considered cracking the case.
danman7 said:
Given that it's sealed, how is this done? I hadn't even considered cracking the case.
Click to expand...
Click to collapse
You may not need to remove the battery as several people have reported success with just slipping some paper between the contacts for 30+ seconds. You will need to open it up though and here's a post with info and pictures to guide you through that: http://forum.xda-developers.com/showthread.php?t=1578365
On edit: here's another thread with good info for you http://forum.xda-developers.com/showthread.php?t=1528706&page=3
Good luck.
Well, I did the paper under the battery terminals for 15 minutes and still no joy.
One item of note is that when I plug the charger in, I'm not getting a white (or green) light. At least not much of the time. Occasionally, I can wiggle the plug a bit and it will light up, but I'm not getting to green at all.
I can put a multimeter on the battery leads, does anyone know how many volts/amps I should be reading?
Are we sure that its not just a crap connection with the charging plug. It is a wimpy little pin and my Xoom needs me to do a rain dance to get it to charge. I have to plug it in, wait a few seconds and then the white light comes on , but only if the wire is flipped back over the top of the screen. Another thought is I use Tiamat ics and there is an option to have the light on or off during charge and I think it is set to off as default, maybe you didn't set that up. I would bet its something stupid and you just need to keep playing with the wire and see if you can get it on. Good luck.
Sent from my Xoom using XDA
Hi Everyone,
I'm have a problem with my One XL. It's an Australian Telstra item. I got soaked in the rain and the phone got wet. I put it in rice for a few days to soak up the moisture, then charged it up. After this the screen backlight would intermittently fail, and i noticed if I squeezed the LHS of the phone it would sometimes make the screen go on or off. The problem got worse over the space of about an hour and eventually the screen would not come on. I opened up the case, and noticed there was a split in the ribbon cable that is part of the screen at the point that it is folded over 90deg (I'm not sure why this was never a problem before the phone got wet?)
So I stupidly got straight stuck into taking it apart to replace the screen before backing up all my stuff. I ordered a new screen of ebay and replaced the old one. Now I am having the following behaviour:
1-Press and hold power button - Phone vibrates once, then does nothing. Screen doesn't come on.
2-Plug into PC - LED flashes red for a while then goes solid red. Screen doesn't come on. Nothing pops up in "My computer"
3-Press and hold (~10sec) power after 2 - Red light goes off. Phone vibrates once every ~30 seconds. Screen doesn't come on.
4-Press and hold power after 3 - Home/Back/Apps LEDs flash 20 times, no other change.
I also tried a number of combos of power + vol -/+ with no success.
Also, I was being lazy and doing this without putting the case back on, and my power button has fallen apart. It looks like that ribbon cable is only ~$5 on ebay, so no big deal, but means I cant really do anymore troubleshooting at the moment.
So I guess the big question is, can the phone still be salvaged? I'm thinking maybe it's stuck in a boot loop with the screen also not working?
Any help is greatly appreciated.
Cheers,
Chris
The first question I have would be did you make sure you got the right screen? There are three different types of screens that came on this phone and you need to make sure you match it correctly. You can identify the type of screen by the colour of the flex cable attached.
Secondly, you should never use the power + volume up button combination, I'm not sure where you saw that information but it puts the phone into Qualcomm download mode which you definitely don't want. The only button combination that should ever be used is power + volume down.
Sent from my Evita
Hi Timmaaa,
Both screens had the same orange/brown flex cables. I did read that there were different screens, but had thought there were only two and that the other had a green flex, so I definitely didn't get that one. Are the other 2 colours close?
I'm not sure where I read the power + volume up thing as I have read a heap of different threads. What would the expected behaviour be if I had put it into that mode?
Thanks for your help.
Cheers,
Chris
The three different screens have very different colour coding on the flex cable, so matching should be a piece of cake, which I believe you've done correctly. Putting the phone into Qualcomm download mode is kinda like a bricked state, if you're getting the red charging led and the cap button lights flashing I think you're ok.
Another thing to note is that you usually need to sync your new screen when you install it. From memory I believe you need to power the phone on, remove the old screen while the phone is on, and install the new screen while the phone is on. If you didn't follow this process that might be why your display isn't working. Other than that your phone might have just suffered some fatal hardware damage due to the liquid ingress, which isn't going to be fixable.
Sent from my Evita
Thanks again Timmaaa,
I had a closer look at my old screen and it does have the small green section on the flex cable which I didn't notice the first time around. Bugger.
So i disassembled it again and swapped back to the old screen. The display still doesn't turn on, but the phone itself now stays on and the computer recognises it! I'm transferring all my photos across to my computer now, then I'll try to sync it properly and see if that helps.
Cheers,
Chris
Ok so I swapped the screens back and forth with the power on, and now it's working! Thanks Timmaaa, I would never have guessed I needed to have the phone turned on in order to swap parts, seems pretty weird. Now just got to get a new power button.
Cheers,
Chris
Awesome. Glad to be able to help.
Sent from my Evita
was running a solid PA 5.0 Rom then My screen broke about a month ago so I broke out one of my cheap $30 Wal-Mart phones until I decided what to do with it. Finally decided to get a screen + digitizer kit, replaced it all no problem went to turn it on and had a red light blink for a few seconds and then nothing. . Tried all volume & power button combos but no dice. Been trying and googling for days now. I can plug my phone into a pc and get it into adb fastboot mode by holding vol- and power button sometimes it gets recognized a mtp usb device but wont install any drivers and if I hold all three buttons it shows up as qhusb_bulk but it still won't boot up normally tho and nothing displaying in the screen. bought it from swappa over a year ago so the warranty is probably up. any suggestions?
qhusb is a brick. Try and follow this guide:
http://forum.xda-developers.com/google-nexus-5/general/fix-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
I had the same thing. Phone in a drawer and red light fluttered then that was that. I put a new battery in.
As you probably know when the battery dies there its in fact 10% left for boot up. In my case it had gone to zero so there was nothing to power the charging circuits etc. Worked for me. I found a way to charge the other later and it's a spare
SENT BY ENTANGLEMENT
theesotericone said:
qhusb is a brick. Try and follow this guide:
http://forum.xda-developers.com/google-nexus-5/general/fix-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Click to expand...
Click to collapse
alright did that now it gets recognized on my computer as normal and phone vibrates when i turn it on, guessing the screen i got was bad cuz that still doesn't work, I'll just send it back and get a new one. many Thanks!
Hey guys,
I've got a problem and since I'm not an expert I've got into a dead end.
I was trying to root my HTC One M8s. I managed to unlock the bootloader, but when I tried to flash a custom recovery (TWRP 2.7.0.2) it went completely black. Since then only reactions it has are the red LED is on, if I put it on charge the turned off charge screen comes on. And if I try to hold the power button and volume down, after 10 seconds it goes black again, even the red LED, like it tries to reboot, but it after that it only goes back to the charging screen if it's on charge or only the red LED if it isn't. I can't install factory image, because the computer won't recognize the device.
Do you, guys have any suggestion or is it completely bricked?
Any answer is appreciated!
hegtam said:
Hey guys,
I've got a problem and since I'm not an expert I've got into a dead end.
I was trying to root my HTC One M8s. I managed to unlock the bootloader, but when I tried to flash a custom recovery (TWRP 2.7.0.2) it went completely black. Since then only reactions it has are the red LED is on, if I put it on charge the turned off charge screen comes on. And if I try to hold the power button and volume down, after 10 seconds it goes black again, even the red LED, like it tries to reboot, but it after that it only goes back to the charging screen if it's on charge or only the red LED if it isn't. I can't install factory image, because the computer won't recognize the device.
Do you, guys have any suggestion or is it completely bricked?
Any answer is appreciated!
Click to expand...
Click to collapse
The m8 and m8s are different devices and it looks like you installed the wrong recovery did you install this one ?
http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
it does look like it's out of date
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8s-wont-boot-recovery-t3219219
As long as your pc recognises your phone you should be ok, try asking in this thread here
http://forum.xda-developers.com/htc-one-m8/help/htc-m8-blank-screen-logo-screen-wont-t3394286
the experts there will be able to help you
Good Luck
Sawdoctor
Fixed!!!
sawdoctor said:
The m8 and m8s are different devices and it looks like you installed the wrong recovery did you install this one ?
http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
it does look like it's out of date
http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8s-wont-boot-recovery-t3219219
As long as your pc recognises your phone you should be ok, try asking in this thread here
http://forum.xda-developers.com/htc-one-m8/help/htc-m8-blank-screen-logo-screen-wont-t3394286
the experts there will be able to help you
Good Luck
Sawdoctor
Click to expand...
Click to collapse
The PC didn't even recognized it, like nothing would be plugged-in.
But eventually, I found the solution. I share it, maybe it's gonna be useful for someone in the future.
I had to take the whole phone apart, which was quite an experience, considering the built of the phone. But there are some guides out there.
https://www.youtube.com/watch?v=CJtVKlmEbcU
https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650
Detach the battery, wait a couple seconds and then reattach it again, push the power button and it was like nothing happened. Except the battery was on 5% what was odd because I was trying to charge the whole previous night!
Anyway, it is a happy end!
Thanks for the advice, though.
Cheers!
hegtam said:
The PC didn't even recognized it, like nothing would be plugged-in.
But eventually, I found the solution. I share it, maybe it's gonna be useful for someone in the future.
I had to take the whole phone apart, which was quite an experience, considering the built of the phone. But there are some guides out there.
https://www.youtube.com/watch?v=CJtVKlmEbcU
https://www.ifixit.com/Guide/HTC+One+M8+Battery+Replacement/41650
Detach the battery, wait a couple seconds and then reattach it again, push the power button and it was like nothing happened. Except the battery was on 5% what was odd because I was trying to charge the whole previous night!
Anyway, it is a happy end!
Thanks for the advice, though.
Cheers!
Click to expand...
Click to collapse
That's great news so glad you fixed it
Sawdoctor