Database Info

[Q] Transformer TF101 Will Not Turn On, Boot, Nothing.

Is my device bricked?
Had device inserted into keyboard and plugged in all night. Batteries should all be full.
Light on keyboard is green.
Cap Lock light comes on when pushed.
Computer makes camera shutter sound when "camera" button is pushed.
Nothing happens when holding power button down for 5, 10, 30, 60 seconds.
Same when holding power button down with volume up for 5, 10, 30, 60 seconds;
nor with power button down and volume down button for 5, 10, 30, 60 seconds.
Have a run into an permanent apx bootloop? (not sure what that is but doesn't sound good).
Have removed all usb and micro usb drives.
I have never rooted the device; recently did a clean factory install and had it working fine.
When plugged into my linux desktop, I was able to access it. I've created /media/transformer mountpoint, ran sudo chmod -R 755 /media/transformer
and then
sudo mtpfs -o allow_other /media/transformer
but then receive the error message:
"Transport endpoint is not connected"
This is new.
Then travelled to the USA and plugged in device to recharge at JFK at at least 2 places. None of the plugs worked. JFK was somewhat waterdamaged from recent floods. Could this have fried the device through a power surge?
Can't think of what else to do than perhaps let it power down completely and then try again.
Any suggestions would be greatly appreciated.
I purchased the device in Canada and now an living in Morocco so sending it back for an Asus RMA would be very difficult and likely more
expensive then purchasing a new Nexus to replace.
Do I now have an expensive paperweight?

Desperation?
I'm thinking of following the directions found at a tabletroms forums site that I can't post here becuase of xda forum rules, but it calls for "Nvflash Unbricking and forever root!" but would first hope there to be some simplier answer.
I've read a lot of other XDA posts and googled many a version of this question, but nothing seems to help, except, perhaps, for the link above.
Luckily, I always back up everything so nothing on the tablet is irreplacable.
Is it time for desperate measures?

Screen Visible when plugged into a HDMI TV
Going out on a limb, I plugged the HDMI cable into the TV and up pops the screen of my tablet, fully functional, battery levels OK, brightness on full and all working as it should...
...except that nothing is showing on the screen except pitch black.
Next step -- factory reset? or could this by a hardware misfunction?
I'm going to try a factory reset and see what happens. If it does not come back to life, I'll know it's a hardware malfunction and wait until I can return to Canada for an RMA, unless anyone else can think of something?

Factory Reset Did Nothing
... simply now have a factory reset tablet that can be only viewed when attached via an HDMI cable to another screen, while the screen itself, is blank.
Does that confirm an hardware problem?
I'll have to check my warenty, but my bet is that it too, just expired.

From what you described, sounds like your screen is broken.

Lingering Question...
Before turning this over as the tablet attached to the TV so the girls can watch programs from the NAT box; is there any hope that (A) reflashing a new ROM might breath life back into the old girl/tablet or (B) is there a way to do a quick fix via opening up those Torx T5 bezel screws and looking for a loose wire of two (not able to soder something that complicated).
Would that work or am I the one with the screw loose?

Broken Screen = RMA or paperweight?
So if the screen is broken, I either have to return it and hope it's under warenty, or find and replace a new screen (hmmmmm beyond perhaps what I can do) or leave it as an expensive keyboard / mouse with computer capability on an HDMI TV and if you touch the black screen in the right place -- which still works! -- then I can control the external video.
Solar.Plexus said:
From what you described, sounds like your screen is broken.
Click to expand...
Click to collapse

filosofic said:
So if the screen is broken, I either have to return it and hope it's under warenty, or find and replace a new screen (hmmmmm beyond perhaps what I can do) or leave it as an expensive keyboard / mouse with computer capability on an HDMI TV and if you touch the black screen in the right place -- which still works! -- then I can control the external video.
Click to expand...
Click to collapse
Sounds like a wire has come off or you have what is called a dry joint which happens when a soldered cable doesn't take properly, I very much doubt the screen is kaput

Surface RT stuck at surface screen - Normally an android guy

A co worker had her surface rt crash on updating and now its stuck at the booting surface screen.
I tried the steps I could find fiddling with the volume button and power button but it gets no where.
Honestly I have zero experience with these and normally use android.
Is there a way to connect this thing to a PC and push recovery files to it as it doesnt seem to want to see the recovery USB at all. It does know its there cause the power/reading light on the USB drive lights up.
Im trying another attempt at downloading and remaking the recovery USB just to see if I got a bad download but honestly wondering if this thing is toast. Just really trying to help them out cause it just ran out of warranty and MS wants to charge them 200$ to repair it.
Thanks

Hello there,
I would like to propose again this question, I summarize the problem of a Surface,
in my case a Surface 2 with Windows 8.1 RT stuck at the 'Surface Screen' and looping
in reboots alternating with the screen of 'preparing automatic repair', and then stuck.
If I reboot by holding down power button for 10 or 30 seconds, nothing changes and
the loop restarts by telling 'there is a problem screen', automatic reboot, 'Surface screen' and stuck.
I've tryed with 2 versions of the recovery image, an old one and one new, with two different
usb sticks. I've booted with "volume down" etc, the usb light flashes a couple of times but
the loop described above does not change.
Seems that many people out there suffer from the same problem, with almost all versions of the Surface, up to the Pro 4.
Many of them solved it with the usb recovery, but also a lot of them still have the same problem. Maybe we do something wrong
with the recovery files?
Any help is welcome, thanks for reading.

Try to keep the device on charge and leave it running for some hours, does it still stay stuck?

Hello Kephax,
I tried several times many strategies, even the one you suggested, nothing to do, always the same loop.
Hence I contacted Microsoft on 15th december, the support was very polite and efficient, in a week I was able to pack my device and give the pack to UPS. After 3 days, they returned me a new Surface2 for free.
I must say mine was only 6 months old, so warranty was still valid. On 24th december I was playing with the new device, so the whole procedure took 9 days. I am very happy.
However, I cannot say what was the fault of my Surface, a hardware problem or some updated went wrong? that's the question, I'm frightened that it was an update problem and that it can happen again to the new device. I can only guess it was a hardware problem because of the experience with the new device, less laggy, more fluid for graphics animations. Also the battery lasts longer.
I hope that this experience can help other user with same problem.
Best wishes for a happy new year,
dott_mat

Create a surface rt 8.1 bootable usb and boot from usb device.
If USB Device bootable, then first connect usb device, then press and hold vol down button, then press and release power button, when surface logo appears then release vol down button.
If all successful then surface will boot into recovery or directly boot from usb drive.

Replaced screen, not booting

Hey guys,
just replaced my screen by myself and it isn't working. It boots and the screen lights up for a few seconds but thats it. So it seems like I ****ed up somewhere. :/
Now I've got some questions for you guys.
1. What could cause this error? Since it's already not working I don't mind taking it apart some more and trying to fix it.
2. Do you think if I send it to the support from OnePlus they will take a look at it?
3. The whole reason I did this was to get my data back. Is there any way to access the data on the phone without the touchscreen? I encrypted it using CynogenMod. USB-Debugging is enabled.
Thank you so much guys, I'd really appreciate some help. This **** is really tearing me down since it was a lot of work.

I did this on my own phone but Idk about OPO. If you use the power+voldown method to boot into recovery (yes ik nothing on screen) then connect a usb and see what happens
If you power it on, wait 5 mins then call it and if the phone rings you should be able to rule out the display and speakers and storage, obvs if the display is still not on at this point it is probably the display.
you can also adb from recovery and or fastboot so you should be able to see it in there if it is still working (make sure you change the phone for a decent amount of hours before you do any of these) If the display is dead its likely its been on for the last day and dead

Sorry for the late answer, really appreciate your help!
So if I connect the phone to the PC (tried it in recovery and in normal mode) windows detects the phone under "Devices" but sadly if I type in "adb devices" in cmd it doesn't detect the device.
But still, windows is detecting the phone so it seems to still function. I booted into recovery and I could use the touscreen and the lower buttons. I couldn't see anything but it was vibrating whenever I was using the touscreen. So it seems like only the display part is broken.
Can't call the phone since it's fully encrypted so I need to type in a password before booting anything (recovery, normal mode, ...)
I'll try to contact the vendor of the display and see what he has to say.
If anyone got any more tips I'd appreciate them. I'm a pretty big noob so I even appreciate "common sense" tips.

I know this may be a "common sense" thing to say, but double check your connections. Sometimes the connectors aren't made properly and a pin could be covered so you can try connecting and disconnecting several times to see if it clears up.
Since the touch screen was registering and vibrating, then it could be the backlight that's broken. Try holding a flashlight at an angle and see if you can make out anything on screen. If it's the backlight, then you can probably back up your data in case your phone does end up breaking.

reconnected everything multiple times and also tried the flashlight trick. sadly with both no luck
but something good:
adb recognizes my phone in "recovery"
bad news: no commands work, most likely because the phone is encrypted. if I enter a command nothing happens, it looks like its loading forever.
any ideas?

Hey!
I also had the same problem after I replaced OPO's screen about one year ago. The replacement screen was from ebay.
I could see the Cyanogen logo but after a few seconds the screen became black. Booting into recovery mode worked well.
On the video also ROM boots well but the screen stays black.
https://www.youtube.com/watch?v=VcWDCJIkPKQ
Eventually, the screen was defective and I returned it and bought new one.

1st Gen Moto G - I can't get past the Fastboot menu

Hi folks.,
Daughter has a Moto G. It constantly powers on - goes to the "M" boot screen for a few moments then a sort-of black screen, although the screen is actually on - it is just displaying black pixels. It just stays there.
With a couple of long presses of the power button I can get it to turn off and then, if I'm quick, I can do the power/vol down combo to get into Fastboot menu.
HOWEVER - whatever option I choose Factory/Recovery whatever (other than the Barcodes - which shows the Barcodes) it just goes straight to the "M" screen for a few seconds and then the sort-of black screen again.
It's been a long time since I fiddled with Android stuff (I'm Windows Phone) so any help and guidance for an old idiot like me would be greatly appreciated.
TIA
SP

Same issue here
Hi, I'm having the same issue here.
Do you have an idea of what could have caused it? I mean, how did it start?
Do you ever get to see the battery charging icon when you plug it?
I thought it was a battery related issue at first, but guess it's not. Gonna try to install the firmware again to see if that helps.
I've noticed it shows the cmd getvar.all when I plug it to the laptop while on fastboot mode.
Does it say the fastboot reason?
Does your computer recognize it when you plug it?

Question Stuck in recovery mode PLEASE HELP

I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.

Hi, provided that you have already
- enabled adb debugging;
- installed adb.
Now you have to
1. enter fastboot mode;
2. in adb type
Code:
fastboot erase recovery
then, reinstall recovery if you want to.

s.0105._j said:
I thought this would be a good place to ask this.
A few minutes ago, I accidently pressed the volume up and down buttons for a long time on my zflip 3 and it booted into the recovery menu. Now this normally wouldn't be a problem.. if my power button wasn't dented in.
I refused to fix it due to the sheer cost of the fix and could turn my display off by double tapping. However, this means that I have no way to exit recovery mode. I tried using ADB on both my bac and pc (using usb 2.0, 3.0, and c on my pc and c/thunderbolt ports on mac).
My phone however would not connect of show up under devices, and I am suspecting it is because I have done something to the debugging settings. I let the battery run out and it would just boot back into the recovery interface once charged up. It even once went to a light blue screen that said something along the lines of how a custom os can cause major problems.
I am a noob at phone stuff and I really don't know what to do. I have a bunch of photos of my grandma who passed away last year and they aren't backed up to google cloud. I really need any help I can get. Thank you.
Click to expand...
Click to collapse
How about rebooting to system using volume buttons?