Cannot turn TF101 off. - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi peeps,
I got a good one here for you. I have been given a TF101 with keyboard dosk. It’s in lovely condition and I thought it would run Kodi nicely … however
The previous owner has flashed a different rom. Not sure what but there is a picture of a cartoon dog and four pulsing coloured balls behind. The thing is. It stops at this screen forever. I cannot turn it off. I have attempted different combinations of power/volume buttons and even the hard reset hole … nothing works…
Anyone got any ideas?

UPDATE .........
I finaly managed to get in. I had to let the thing run flat then I was able to power up and do a wipe. It's still not too happy ... specificly it crashes when I try to run Kodi ... but that literaly a subject for a different thread

Keverso said:
UPDATE .........
I finaly managed to get in. I had to let the thing run flat then I was able to power up and do a wipe. It's still not too happy ... specificly it crashes when I try to run Kodi ... but that literaly a subject for a different thread
Click to expand...
Click to collapse
There's an Kodi APK for 4.0.3, didnt crash and was snappy just the loading on channels was a headache

Related

Almost bricked !! really ! help needed before it dies !!!

Bonjour
I upgraded to WM6 (pdaviet) 2 months ago (I guess..), and problems started to appear a few weeks ago. First it just was hard to boot sometimes, had to reboot several times to get it up and running, but when it could start everything was fine. Then since yesterday, it became harder. And today, couldn't start it at all. Tried several times, and everytime the screen went melted, corrupted, like if it couldn't stand an o/c, but it always runs at normal speeds. I guess it has something to do with the battery and the way WM6 handles it (or at least the implementation we have on our prophet).
I tried to hard-reset, I left it a long time on the format screen (before the actual HR) and it handled it for long enough, but the same thing started while setting up WM.... too bad !
While writing this message I tought I could try to downgrade, and I did using AKU3.3-Jester-b1.
I had no problem while the phone was in guest mode after the HR.
Everything went nice during first step upgrade, but on final reset it did the same thing, and now..... it cannot start at all !!!!
Someone has an idea ? I own a G4 and it has the following roms :
IPL 2.10, SPL 2.20, GSM 2.47 (or something like that)
It won't charge (but my batteries are full, I've got an external charger), it won't start from battery nor from power, even if the battery is removed.
Damn, at least I guess I can return it like that to orange, since it cannot start one can't see the modified rom...
If anyone has a suggestion, it is more than welcome ^^
Thanks !
Niko
huh !
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
lastnikita said:
back to semi-life ^^
After a few hours left alone without battery or sim card, it started again...
but it still resets every few minutes, or the screen goes melted (actually its like white scanlines that fulfill the screen).
I'll try to leave it shutdown for the night, see if I can at least put the orange splash screens and rom back for warranty purpose.
But it now has serious HW problems, for sure. And my opinion is WM6 has something to do with that. BEWARE !
Another strange thing is that I now have to keep the reset button pressed for half a second to reset, where it reseted instantly before. Those devices really have unstable hardware.
FYI, it was almost brand new, as it was warranty-replaced about one week before I installed WM6.
Click to expand...
Click to collapse
Hey LastNikita,
I had the same problem ! The white scanlines thing just after re-updating a WM6 version (pdaviet), because I was tired of the constant reset issue.. suddenly, the update went wrong, and I stupidly followed the "recovery" process, which tells u to remove the battery... bang ! screen went corrupted !
Like you, I tought it was over... but I noticed that if you connect your phone and PC with USB, and keep pressed power (ON/OFF button on side) + camera after reseting (little hole on bottom - press during 5 sec!), the PC recognizes a USB device (not the usual phone drivers...) at this moment, I launched the Jester 3.3 (step1) update, in order to downgrade from the ugly WM6 pdaviet... My phone was not yet fixed (still with white scanlines), but at least, I could hear again the WM "start" sound, the scanlines would also "move" across the screen borders when I touched the screen, which made me imagine I was on the calibrating process... also, while connected to PC, after a while, ActiveSync would launch, asking for 1st time synch... this kept me confident as the phone (software) seemed to be reacting fine although HW prob...
I completely charged the phone again (till green light) then kept on reseting the phone (until I hear the WM sound) hoping the lines would finish scanning and come back with the normal .. and guess what, it did !!! Of course, PIGHEAD as I am, I wasn't totally happy it recovered with WM5, so i digged for a better rom, and I can tell you I'm very happy with the smart1 (wizard version) which works fine, but still has some minor bugs as Live Messenger not working... but runs fine (specialy when pressing the ON/OFF button !
PS: Make sure the ALWAYS completely switch off your phone (ON/OFF for 3 secs) before removing the battery... it did happen again... when I stupidly trusted the "recovery" process, again !
DUHHHH !!!!
PS: at least, now you ALL know !
Kokiri
Finally ok for warranty )))
Thanks for sharing mate
I finally managed to downgrade to my original Orange rom, and I'm in the process of putting the original Orange splash screens back (I made the nk.nbf but I can't find the right utility to upgrade... "Update utility cannot open the requested file").
BUT I still have that HW problem afterall.... so I guess it still has to go back to warranty right ? This isn't a big deal since Orange is VERY prompt (I guess I'll get it tomorrow or monday morning, the delivery guy brings a new one and goes back wiv my phone, quite nice !), and I have a button which is stucked (from the begining) anyway ^^
While I'm writing this my phone is docked and synced, and it seems fine.... but, I guess, as soon as I will reset it will start over again.... I'll keep you posted.
Anyway, I'm no longer desesperate and that's good news (for me ^^)
++
niko
yip
ok, everything's back to original.
Actually, it works well when docked, but it freezes/melted screen as soon as I tried to use it on battery, so that I'm quite sure it has something to do wiv WM6.... I'll post that on some crossbow threads this weekend if I have time enough (there are so many of them now !)....
But once more, if YOU read this, keep that in mind.
Hope you guys won't have that kind of failure while trying it.
++
niko
confused
I am having the same problem except the screen showing white scanlines everything else is working on the handset. Could it be a LCD Problem?
Me too...
I have the same issue (black/colored vertical lines and a white screen). I think it has to do with upgrading to WM6 or with overclocking with batteryStatus, not sure. This are the suspects in my opinion....
Now I downgraded to WM5 but the problem seems to persist, I disabled batteryStatus and will see if the situation improves... crossing fingers
Uhm ... possible Overclocked!
I have read 3 threads with same errors!
how much was your highes clock? do you use it for navigation? long time on highest clock or only for speed up?
i dont have a problem with scan lines but with my prophet i use the scaling option and go max to 234 i also set to 234 when using certain apps.
is this damaging to my prophet?
at the moment trying to upgrade to PDAViet 4.0.0.0.3 with a world of pain but thats another topic!

[Q] HELP! Capacitive side buttons stopped working!

Hey guys,
Oh i dunno whays happened. Everything worked fine yesterday then i went to sleep. Next day the side buttons stopped working. The touch screen still works but the side capacitive buttons stopped.
It doesnt even work when i boot into clockwork mod
I have so far tried:
Reboot did nothing
Put calibration.ini file in root directory
Put calibration.ini in sdcard2
Put calibration in sdcard root
Reboot
Didnt fix it.
I got it ebay as i live in australia so warranty may be difficult.
I am using button saviour to get by for now but until i can get the side buttons to work i can no longer navigate clockwork mod because the home button is the select button.
I'm usibg vegantab b5.1 at the moment.
Any help would be really appreciated!
BAM
If you haven't, you might want to try this: http://forum.xda-developers.com/showthread.php?t=934500
Just tried it but still no joy. Looks like the side buttons are on a different touch interface to the rest of the screen. I guess it could be worse. Vegantab is a nice rom to be stuck on.
I wonder if there is a way to make clockwork mod work with a usb keyboard?
Woohoo! It's working again! Just in time for honeycomb too
I searched and searched for similar issues and finally read about either draining the battery or opening up to find the hidden reset button.
I opted to drain the battery.
Now I'm still not going to rubber stamp that draining the battery fixed it but when I did finally plug it in and fire it up I found the buttons worked again.
Another theory I have is that viewsonic might have some poor soldering. The reason I suggest that is because in Australia we've had some stinkin hot days here at 42degrees Celsius with high humidity. So it wouldn't surprise me for a dry solder to become temperamental under these conditions.
Anyways happy ending for now. Well hopefully it'll keep running until a reliable honeycomb rom turns up for gtab hey
I have encountered a similar problem. The side buttons stopped working after a few days of use. They do work sometimes randomly. Is there a reliable solution to this problem?
I tried calibration.ini, and the buttons worked once. They have stopped working again.

Touch screen problem on Motorola Defy

Hello, I have recently discovered a very annoying problem with the touchscreen on my Motorola Defy:
I have noticed that the touch screen acts strange sometimes, so I have installed a touch test application(Touchtest by Hermit). In this application I have noticed that if I touch the screen in two different points in a fast succession, a line appears between these two dots. This makes a lot of application that require multitouch pretty much useless, because I have to restart the application to have the touch screen working again.
Is there any solution for this? I have heard that this may be a software issue, so I have e-mailed Motorola, but they have not answered yet.
I have attached two pictures to illustrate what I am saying, one taken before this strange error, and one after pressing on two spots very fast. You can see the line connecting the dots in the second picture. I can make a video if you still can't figure out what I am saying.
Thank you.
Im having a very similar problem here on my defy. When I play games on psx4droid and when I keep pressing x key, it stops working for a while then I have to release the button and when I press it again, it stops working and it continues
I encounter similar problems with my Defy.
When for instance using slide to unlock , 1 / 5 sildes fails. I have to slide 2 - 3 times until it unlock.
It also scrolls very slow in applications and the same thing happens when typing a message.
Solution : Unse lock button.
It currently runs Pays ROM, but the situation appeared since I installed 2.2.1.
I don't remember having this problems on 2.1.
Don't know if the situation is only related to software but it is really annoying.
Found this info regarding touchscreen slowness, but I am using the original charger so it doesn't apply for me.
Motorola Defy Touchscreen Problem
I recently got my Motorola Defy,my Defy's touchscreen acts sometimes really weird, on keyboard it's hard to enter 'r' or 'b' and some other characters, it takes little while to unlock the phone, it automatically opens applications, I don't know if it's due to faulty handset or software, I am considering it returning to Phone4U and get a replacement handset.
What version of Android are you using ?
Same problems here, but I think it is a software issue.
I'm having the same problem on my Defy.
After a while, the multi touch stops. I posted on the Motorola Forums
https://supportforums.motorola.com/thread/44733
but no response.
I used YAMTT and when having two touches, after 20 seconds, one of them disappears
This is repeatable
2.51.1 UK with 2.1 Android
Well, it is clear that this is a problem that affects many Motorola Defy users. But I wonder if someone could fix this thing?
Looks like the new software version 2.51.1 did not fix this bug. I haven't tried it yet, but I see some of you have.
So it looks like our only solution could be a developer from XDA. Could someone help please?
This is ridiculous...i've sent my phone to motorola only because it was giving this problem and basically what i think is that their own software is causing this problem so i'll be waiting for 3 weeks and when i get my defy...it'll still have that problem...Ridiculous...
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
efpob said:
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
Click to expand...
Click to collapse
Defy doesn't support cynogen mod and 2.3
I was messing around today and even the single touch disappears after a while
30 seconds or so
Mine sometime stop response after few seconds
really wierd
Tell me who is on stock rom and is having problem..because im on 2.2 leaked..so i cant really say if u hv this problem on 2.1...
I got this response from a Motorola employee. Anyone know of a way around this?
Motorola Employee said:
If you touch the screen and don't move for a long time, the screen will eventually try to ignore that touch as it'll be considered invaild. That's what you're seeing. If you continue to move your finger(s), touch will continue to work. Also, when you release the screen, it acts to clear the invalid touch region that you generated earlier.
Click to expand...
Click to collapse
https://supportforums.motorola.com/thread/44733
have simular problems............100 procent hardware problem..... if i twist phone a little it will go back to normal for a while
any ideas for disable it?changing some parameter or something?
I have the same problem. screen sometimes go crazy. i am using stockrom eclair SEA 2.59. sometimes it seems that it tap icons or part of the screen even without I actually tap on something. and it seems it affect the capacitive button under the screen. I am not touching the search button but the search box suddenly appear.
I have to push the power button and unlock the screen to make it normal.
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
brjshshrma said:
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
Click to expand...
Click to collapse
i returned my defy months ago but what you can do is, try to flash cyanogenmod on your defy...that should fix the problem.
Hi, I've registered myself just a minute ago, reading the link that efpod left here and I've remembered that I charged my Defy with a Galaxy S i9000 charger friday (I've charged it once the batery was drained later with my original charger) and today it is failing A LOT, it's really anoying.
I got Cyanogen Mod (latest) installed on my phone so that doesn't fix the problem.
I'm uncharging it with "StabilityTest - CPU / GPU Test" and when the battery drains out I'm gonna charge it with the original one, after that, I'll test it during the day and I'll leave a messege to keep you informed.

[Q] Touch screen problem!

After updating to 3.2, I noticed that the touch screen has a ton of bugs. I used this program to check the inputs (I can't post links now due to forum restrictions):
Multitouch visible test
Basically if I scroll from far left to far right (Asus logo on the top left of my view), there is always a cutoff somewhere on the screen.
I never or hardly ever notice this problem when I'm in 3.1.
Any ideas on how to fix the problem? Or is it just 3.2 that has this and I should go back to 3.1?
Help is totally appreciated. Thanks!
Update:
Sent in the TF to Asus (to Ontario Canada) on August 9, 2011
Received it back from Asus on August 29, 2011 via UPS
Problem: they only reloaded the OS and did NOT test the touch screen so I have the exact SAME problem... Requesting RMA again
Can you grab a video of the issue?
Plonk it on youtube and then stick the url on here.
Cheers
Video is at youtube:
www(dot)youtube(dot)com/watch?v=ukdzYMKYtFE
Basically a portion of the screen does not respond to touch, and the classic turning screen on and off does not fully solve this problem.
had this problem before 3.2.
my screen have only small places..quarter of inch, random places.
noticed this only after rooting. and with some kernels more than others.
have you rooted?
No root. All stock since I am too lazy to do anything other than install apps, view video and manga.
blastdabomb said:
Video is at youtube:
www(dot)youtube(dot)com/watch?v=ukdzYMKYtFE
Basically a portion of the screen does not respond to touch, and the classic turning screen on and off does not fully solve this problem.
Click to expand...
Click to collapse
Quality vid there, top notch.
Have you tried a hard reboot?
And a restore to factory default settings?
For some reason that sounds sarcastic there... but the video was taken by a Desire HD so it's not that good quality. It conveys the point (I hope).
Haven't tried hard reboot or factory default settings because that would mean I have to reinstall stuff and re-setup things like gmail.
Lol dude, i wasnt being sarcastic, for some reason i was expecting some half-assed effort.
Hard reset shouldnt wipe your data.
Hard Reset:
Unplug the power cord and shut the unit off and Press and Hold the power button and the "Down" volume button together for 6-10 seconds and let them both go. After a few seconds you should see a couple of shapes in the middle of the screen called "Wipe Data" and "Android". Wait a few more seconds until the term "Cold Boot" appears in the list near the top of the screens and just press and release the "Down" volume button again and let it reboot. If you own the dock be sure and do this with the dock connected.
Sorry man, I guess my sarcasm detector is pretty off today.
I tried the hard reset and the same problem persists. I will have to see how this can be fixed though (I see that many people have similar problems though).
Thanks for your help =)
might be worth giving asus a tinkle and see what they say.

[Q] Galaxy Nexus Boot Loop (stock)

I have an unlocked HSPA+ Galaxy Nexus imported from the UK to the US. Ordered from Negri Electronics.
It's not rooted or modded in any way.. Mainly because I don't know how to. As far as I know, it's running stock ICS.
I was using it normally, (using the fb messenger app if it makes any difference) when it suddenly rebooted by itself. The Google logo comes up, then the start up animation, and sometimes the home screen will appear but is not touch sensitive (i cannot slide it to unlock), and then it 'hangs' and the screen goes black. Repeat.
I've tried to fix this by myself and there's a video on youtube (sorry, noob here. can't post links. video is by robbidwv and title is "my galaxy nexus won't boot..") of the same problem that I have, but the posted solution doesn't work for me.
So far, I have entered Coin Mode and pressed Start. Entered Fastboot mode and gone into Recovery Mode (no options appear after that. it just starts booting up and the loop begins), and I've also tried Restart Bootloader.
I've almost given up. Now all I want is to extract my SMS, if they're still on my phone. I can't access the folders on my computer because it won't boot up and connect. Is there a way that I can extract my SMS by using DOS in either Coin Mode or Fastboot mode?
Or even better, does anyone have a solution to this boot loop problem? I'll contact Negri Electronics tomorrow and hopefully they can send me a replacement.
Please help!! Thanks
that problem just started happening with me an hour ago!!
i hate this!!
we need a solution please!
Hey guys, sorry about the issue.the major problem I see here is you wanting to retrieve your txt messages, which might be possible with a little Modding, but if yourwilling to lose them to get a working phone back, then this is what your going to have to do. Make sure your phone is completely off. Hold the 2 volume buttons and the power button together. You will get into a mode with an android Guy. Press the volume button up or down until it says reboot recovery at the top. Press the power button. It will rebootand come to a screen with an android. Hold volume up,down and power at the same time. A menu will come up. Go down to wipe data. Click it, and after it is done reboot. Your phone should work now.
If this helped you, or you simply appreciate me taking the time to write this out then please press the thanks button
Hey!
Thanks. Yeah I 'fixed' it already. I was just about to post something similar. After a while I just gave up on trying to recover my data. Good thing that Google syncs everything so the only issue would be recovering my messages, which I decided weren't worth sending it in for a repair which would probably not be able to recover anything anyway.
The thing I didn't know about was to press power + volume up WHILE on the recovery screen. I thought navigating to the recovery screen was it!
Still, this kind of sucks. I love my GNex, but I can't help but be slightly pissed seeing that my crappy iPhone 3GS never did this in the 2 years I had it. Oh well, hope it doesn't happen again!
hey guys! i also did a complete wipe on my phone and got it working again!
but i wonder why this happened in the first place?
last application i installed before the crash was double twist, i dunno why but i feel that it was the reason behind the boot loop!
Sorry for reviving this thread, but I just had this happen to me TWICE!
It happened to me first last Monday, the 23rd - the phone crashed when trying to send an email with an attachment - and went into a boot loop - Google logo would appear, no make it to the animation, and reboot....
I performed a full reset and things worked again. I didn't install all the apps I had before - figuring it must have been due to some app messing with the OS.
Well, it happened again to me yesterday! I was connecting to my bluetooth headset when the phone crashed and went into the boot loop. Full reset worked again, and I've installed even fewer apps - essentially only those that I use on a daily basis.
My phone is still on 4.0.1 and I'm hoping once 4.0.4 is pushed this may get resolved? I have a canadian GNex from Negri. I will call them again (I called the first time, but when the full reset worked I never contacted them again).
I would like to this this is a software issues, and not hardware.
I have the same problem. If you figure it out let me know.
Today my phone also entered a boot loop: [Google logo]->[black screen]->[vibration]->[Repeat]
I tried Recovery Mode, but this is what happens: (sorry for the link but I am not trusted with powerful tools such as outside links apparently, as I have not yet reached the maturity of a person with eight posts... )
dl(dot)dropbox(dot)com/u/53568097/Android.jpg
This is what I see when I navigate to Recovery Mode
For a split second I can see an image of an Android with spinning cogs in his innards, but then this little sad fellow appears. WTF is this?
EDIT:
Oh, and I'm running Android stock 4.0.2, never rooted or unlocked, Swedish. At the time when the phone started doing this, I was using Endomondo, and was about to set off on my bike when it died on me.
Stock ROM galaxy nexus bootlooping after wiping data also.
Hi,
My GNex went into a bootloop so i searched xda and found that factory reseting would be helping my prob. But after wiping the data also its still in going through the loop . Please help .:crying:

Categories

Resources