It had been slowing down for quite a while and often it would just stop responding for a 30 seconds or so. After trying every tweak I could find I decided it was time to upgrade it with a custom ROM. I read through the instructions in “Beginners Guide to root and flashing a custom ROM on the TF700T”. I followed the directions closely, installed TWRP then updated the ROM to ZOMBi-POP. Everything went well and I was pleased with the performance and I installed my apps back on the tablet. I used it for a couple of days but then restarted it on the third day which is when the fun began. After it started it seemed to get stuck on the boot animation, the white lines on the black background that look like sound waves or shock waves, so I rebooted it again, nothing.
Tried the long hold on the power button, Haptic buzz, then Nada, nothing on the display. Tried the long hold on the power button plus holding Volume down, Haptic buzz, then Nada. No matter which combination of buttons and reset I long hold all I get is the haptic buzz then nothing.
I’ve since read through as many articles as I can find on unbricking without any luck…
What I’ve tried and the status:
When plug it into my Windows 10 PC's USB it's recognized initially as an unknown device.
Installed the Universal Naked drivers on windows 10 and have updated the drivers to APX, then Android fastboot, and then Android ADB
Neither Fastboot nor adb show any devices with any of the drivers I’ve used.
I've read through every thread having to do with bricking on the XDA forums and tired what I could try to no avail.
I’m totally at a loss. Now what?
Related
Hey, all.
What does the internal reset button actually do? I was expecting it to reset to factory settings, but fortunately for me it didn't do this. I'm actually happy it didn't, as it means I didn't lose any of the customizations I had done or applications I had installed.
I just cracked open the case on my gTablet and pressed what I assumed to be the reset button, a tiny little white switch in the center of the unit. After pressing and holding it for about 3 seconds, the tablet immediately powered back on and returned to its previous state. Everything appears to be functioning perfectly normally and exactly as it was before.
What does the reset button actually do? Do I need to worry about battery meter not being accurate or any other weird side effects? I only mention that because the battery gauge is showing 100%, but the external red charge light is still on.
I'm not sure what prompted it, but earlier today, my gTablet went blank and wouldn't turn back on at all. My son had been playing Angry Birds for an hour or so and I had been using it heavily showing it off to my in-laws, so I thought perhaps the battery had simply gone dead. I had not plugged in the charger the night before, so it seemed to be a reasonable explanation.
I plugged the charger in and the external red light was visible, so I let it charge for a little while, then tried turning back on. I could press any number of different key combinations (power & vol+, power & vol-, holding button for long time followed by short press, etc.) but I got nothing but a black screen. There was no indication whatsoever that anything was happening.
I was assuming something had gone quite awry, but didn't panic. My wife was not quite so calm, but I reassured her that I would be able to find the answer on the XDA forums. Thanks to everyone who has contributed to this great community, by the way!
First, I tried plugging in the USB cable to my Windows 7 laptop and heard the distinctive 'bing-bing,' notifying me that hardware was recognized, so I knew it wasn't dead. But, it didn't show up anywhere, so I checked the Device Manager. Interestingly, there was no yellow exclamation mark anywhere, as I expected from reading some other posts about NVFlash. I finally found it listed under the 'Disk Drives' section as: 'NVIDIA Tegra 2 USB Device.'
I remembered reading about people experiencing problems with the unit going into APX mode, but I also remembered reading about the internal reset button on the gTablet. So, I figured before I attempted to use NVFlash, I would try the reset button first. Fortunately, these devices were designed well and the case was very easy to pop off.
By the way, I was running the stock ROM, but with the TNT 3588 Enhancement Pack (Gapps with nVidia Drivers) provided by edirector. I had also installed the z4root application. I used the default ROM for the first day, but was comfortable with the idea of flashing othe ROMs, as I've done it with my HTC Aria phone. I flashed roebeet's TNT Lite 4.40 and used that for several days before going back to the factory ROM with the enhancement pack.
Thanks in advance,
Calvin
Well,
I've been reading these forums since last November and I don't know of anyone who
has really reported on "pushing" the reset button before!!!
Usually when people crack the case to push the reset button or unplug the battery
for 10-15 seconds it is a situation where they can't get the machine to start and
literally have nothing to loose.
Sounds to me (in terms of 30+ year of different computers) that you did a hardware
reset and boot. I assume something was locked up inside and the reset key released
it to restart.
Glad for you!!!
Rev
Hello XDA friends. This is my first official posting on the XDA site and I'm in need of serious help.
I've noticed that intense research and development has been put into this phone. With so many rom selections available for the MT4GS I decided to try out several different roms kind of playing around. Many of the roms available were very well put together.
I decided to try out the Doubleshot MIUI v0.3 as I have used on other devices in the past and liked its customization. After installing the rom I made some adjustments in the settings to personalize my phone. Everything was working fine until I rebooted my phone and now it is hard-bricked. My device is S-Off with bootloader unlocked, and prior to installing MIUI I formatted all data, Dalvik, and system. I don't know what I did to brick my device and I can't find similar issues among others.
Issue Details:
When I have the phone powered off then hit the power button my backlight will slightly light up (very dim with no splash or image), and it will vibrate (Like on a normal boot). What else is crazy is every 37 seconds it will vibrate, and this is ongoing if I let the phone sit in that state.
If I have the phone off and plug it in a power source I get no love.
I'm unable to access HBOOT or Recovery mode, and the phone is not detected when connected to PC.
Please help me.......
that looks like a screen/digitizer problem. I don't think you're even bricked seeing as you didn't mess with any partitions according to what you did above. Also if the phone vibrates and the backlight turns on then it's still alive.
Thanks for the response. I'm sure the screen is fine. I performed the reboot when the issue first happened. This phone is driving me crazy.
wait u said you phone isn't connecting to adb right?
Did you try Fastboot?
I'm not able to bring up the HBOOT menu to enter fastboot mode.
have you tried a battery pull?
Thanks for the reply. I have tried pulling/replacing the battery and didn't have any luck. I also have two spares and the issue continues........
I can't figure it out, or figure what I did exactly to cause this.
Any other ideas?
does adb recognize it when it is plugged in?
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
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.
My MI4c is stuck in the Enter Download Mode and now its Blacked out (wont turn on, tried pushing buttons and its combinations but nothing seems to work)
So, the chronology before this catastrophe happened is as follows :
>I was interested to try the new MIUI, and followed the following tutorial : miuitutorial.com/2016/09/sudah-jamannya-miui-8-xiaomi-mi4c-kamu.html
>As the story goes, i finally ended up in the Enter Download Mode (the tutorial stated that under the mode, the Screen will go Blank, and it did, up to the moment i posted this)
>The next step in the tutorial is to open MiFlash and push the Refresh button, but when i did the program responded with 'Specified Cast is not Valid'
>I tried the following solution i found in here : miuitutorial.com/2016/08/bermasalah-dengan-driver-signature-mi.html
>I did it through again up to the restart laptop phase
>The Screen was still Blank (no signs of life whatsoever, the charging lights wont even beep upon charging)
>I was beginning to suspect something was wrong, and as i checked MiPCsuite, the Tray Icon showed that no device was connected (the phone was officially dead)
>Thus i panic and tried almost everything, pressed buttons and combinations, plugging chargers on and off, etc. but nothing seems to work
There goes my story, for the record, the phone i have is still new and everything.
I havent tried googling deep for this matter, but as i am panicking i think my judgement and analyzing skills are currently on the low, so if anybody have anything that might help or links or anything please Hook me Up, I'm all Ears.
Thanks a lot beforehand and Big Ups to the XDA community.
vivasto said:
My MI4c is stuck in the Enter Download Mode and now its Blacked out (wont turn on, tried pushing buttons and its combinations but nothing seems to work)
So, the chronology before this catastrophe happened is as follows :
>I was interested to try the new MIUI, and followed the following tutorial : miuitutorial.com/2016/09/sudah-jamannya-miui-8-xiaomi-mi4c-kamu.html
>As the story goes, i finally ended up in the Enter Download Mode (the tutorial stated that under the mode, the Screen will go Blank, and it did, up to the moment i posted this)
>The next step in the tutorial is to open MiFlash and push the Refresh button, but when i did the program responded with 'Specified Cast is not Valid'
>I tried the following solution i found in here : miuitutorial.com/2016/08/bermasalah-dengan-driver-signature-mi.html
>I did it through again up to the restart laptop phase
>The Screen was still Blank (no signs of life whatsoever, the charging lights wont even beep upon charging)
>I was beginning to suspect something was wrong, and as i checked MiPCsuite, the Tray Icon showed that no device was connected (the phone was officially dead)
>Thus i panic and tried almost everything, pressed buttons and combinations, plugging chargers on and off, etc. but nothing seems to work
There goes my story, for the record, the phone i have is still new and everything.
I havent tried googling deep for this matter, but as i am panicking i think my judgement and analyzing skills are currently on the low, so if anybody have anything that might help or links or anything please Hook me Up, I'm all Ears.
Thanks a lot beforehand and Big Ups to the XDA community.
Click to expand...
Click to collapse
See here if this helps http://en.miui.com/thread-170110-1-1.html
post #7