Hi All,
I had ICS installed on my TF101. However yesterday it totally discharged when it was asleep and I had trouble turning it on. I never had this happen with HC. So I decided to go back to HC. I had my tablet rooted and su backed up. Had recovery installed.
I flashed official US HC fw and everything went fine until I tried to reboot the tablet. It's now stuck at the EEE Pad loading logo with the blue bar approximately half filled in. No amount of button combinations does anything. I can't enter Vol + & Pow button to enter ADB, and when I try to enter recovery mode, the white text shows up saying searching for OTA recovery and that's it, still gets stuck at the blue bar.
Any ideas or ways to get to my recovery before I return my 2nd tf101? Thanks!!
(Btw, I'm not a newbie, I would NEVER do this whole thing if ICS was stable and worked like it's supposed to, but I refuse to own a 390$ half working tablet that crashes, has battery drain issue and gfx glitches after the FORCED ICS update!)
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Goatshocker said:
Have you tried cold-booting it? (power + vol-, wait untill you get the option to cold boot or wipe)
Also, I dont understand what you mean by "forced ics update". I ran my TF for several days without updating (albeit, with the annoying icon in the notification area).
Although I guess you bought the tablet new and recently Im still going to ask. Whats your serial number (3 first)?
Click to expand...
Click to collapse
Hi Goatshocker!
I have tried to cold boot it, but it does not allow me to get to the 2 icons you're talking about. When I hold down Vol - & Pow, it shows the regular white letters from bootloader, and gets stuck at the blue loading bar EEE Pad screen.
What I meant by force, is that after 4 delays of the update, ICS will install itself automatically! Even when the tablet is in sleep mode. That's what mine did.
In order to avoid this, the user would have to root his tablet and use Titanium Backup Pro, and disable certain system update processes. Which is NOT for the casual user or for anyone who wants to keep warranty intact.
The s/n I have starts with C2O.
Related
Is there any way out? TF boots, flashes locked screen for a second and reboots.
I can shut it down with holding Power+Volume Up for 10 sec, I tried to "cold boot" it with Power+Volume Down but no luck, it just goes into the loop again. Maybe I've done it wrong when there were two shapes on the screen - "Wipe data" and "Anrdoid", volume down seem to toggle them. I think I tried both.
Will this "Wipe data" lose ALL my downloaded apps etc? Will I have to reenter a million of passwords again?
Wifi sometimes shows "No internet connection", sometimes "SMC" - my home network, the icon is gray with occasional little symbols on it, too.
I tried turning the router off and starting TF with wifi tether on my phone and it should remember the settings but it just shows "No internet connection" and reboots.
I took the microSD out, too.
I once saw an Anrdoid Robot with a big orange exclamation mark but it didn't do anything for a while so I just shut it down again. Should I wait a bit longer? I can't find the combination that got me into that screen again, too.
It doesn't actually reboot per se, it shows the "Asus, perpetual perfection" with a running gear screen.
All other threads about boot loop here are about rooted Transformers, not surprisingly, and the solution is to flash a better Rom or to do it properly.
What about unrooted device? What is the proper way to recover the tablet?
Had to wipe in the end.
Yesterday it happened again, so I wiped it again.
This time I rooted and installed Titanium Backup, at least recovering will be easier.
So I guess that is the answer.
Pure, "one-click" root, as per
http://forum.xda-developers.com/showthread.php?t=1198303
still keeps OTAs coming in case Asus figures the solution
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
jallweiss said:
Hi All,
Saw a few posts with similar things such as random reboots and bootloader issues, however my issue seems a little different. I already know the first few things I'm going to try but would just like a little bit of input.
The tf700 isn't my first transformer tablet, I had a prime back during release and replaced it with the 700 after my friend broke the screen. I have plenty of experience with flashing the devices and putting on custom roms etc. My infinity has been on JB since the OTA update came (infinity is 100% stock). I use the device every day extensively and it is in the keyboard dock about 99% of the time.
Today while checking my email the device randomly froze, went to a black screen, and then started up at the first asus logo (has happened before so I was not that surprised). After getting to the second splash screen with the silver asus logo I let it sit for about 15 minutes where I continued to get the loading animation. I decided to restart and go into the bootloader menu and thats where I noticed some issues.
Once in the bootloader it seems that Volume UP (to change between RCK, Data wipe etc..) is always recognized as Volume DOWN, meaning I cannot switch between any of the bootloader tasksJust realized they changed the input even though the bootloader text still has ICS commands listed. That leaves me the option of waiting 10 seconds for a cold-boot or starting the RCK. Unfortunately either task I decide to do freezes the screen on the bootloader. I know that the device is responding at first because of the highlight over RCK fading in and out, and then it freezes. Prior to the freeze the prompt always reads Signature Match when trying to cold-boot or start the RCK. Restarting the device again leaves me stuck on the first splash screen, and never progressing after that. I am somewhat concerned about possible corruption from this.
Currently I am letting the power drain all the way down while in the dock and will try charging it to see if that brings it out of this brickish state. In addition I also have a micro-sd in the device, as well as an SD card in the dock.
Other than power draining I would really appreciate some advice, because of freezing in the bootloader I am unsure whether I would be able to perform any sort of modification to overwrite whatever has been corrupted.
Thanks in advance,
Jon
Click to expand...
Click to collapse
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
buhohitr said:
Seems like you only have RCK option on your device. I would download the full JB .16 version from the Asus site, unzip it and rename the new unzip file to EP201_768_SDUPDATE.zip on your PC, plug in your micro SD card (make sure no other zip file(s) on the root of your micro SDcard), then copy this file to the root of your micro SD card, remove the micro sDcard and plug it back to your tf700, Hold down volume down and power button and let it boot to the RCK (by default) see if the device perform the update.
Click to expand...
Click to collapse
Thanks buho,
Full power drain and repower didnt seem to fix it.
I gave it a shot with the update and I still got the message saying that the signature matched and then freezing at the bootloader trying to use the update. As I edited in my post I found that the bootloader commands had been swapped, so I can get to the other options to work. However all of them freeze the bootloader, I cant get any kind of USB recognition at all.
Unfortunately things may have gotten even worse...
I figured since I just need the device to work I would do a full wipe, I started the data wipe, got the freeze after a bit of text. I left the device for about 20 minutes hoping it would go through with the wipe. It was still frozen on the bootloader so I reset the device again... After resetting I cant even get into the bootloader anymore, power button + volume down does nothing.
So currently Im stuck on the first splash screen, unable to access the bootloader. I would appreciate any help at all.
Just to update, I can get APX mode to function right now, but I am not really sure where I can go from there...
I honestly need help.
I'm not sure what to categorize my issue under.
I am stuck in a screen with the green android and the spinning thing in the middle, with a progress bar, but the bar just has a moving animation, looks like it is moving to the left, not getting longer or filling up like usual progress bars.
I am unable to get to the boot loader or recovery.
The issue started after I flashed Cyanogen Mod 10.2 Stable.
it booted fine then, but when I went to use it, it would have a never ending cycle of app not responding at the part where it asks to sign in to cyanogenmod account. I got to settings without signing in by quickly sliding the status bar and clicked on factory reset.
From there it proceded to reboot and now I am stuck in the screen described.
I have tried all the button combinations, reset with pin, nothing will get to bootloader or recovery.
ADB does not find the device, also no devices found when try fastboot devices line.
I have also tried putting the firmware zip on a microsd, but nothing new happens either.
any suggestions appreciated.
** edited ** Issue is resolved. Turns out I just needed to wait longer (about 2 hrs) ... I did turn it off using combo of power and Vol -, left it off overnight, turned it on in the morning and left it alone. I finished whatever it was trying to do, and now CyanogenMod 10.2 stable is working great.
Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock
Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.
a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed
jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:
A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.
I have to Asus tf700 that will not boot they were only vibrate when you push the on button. One is rooted with zombie and the other is stock I get a display on the rooted tablet on the monitor I have connected through HDMI and I am able to navigate on the tablet with the keypad attached. The other one stock unit I am NOT able to get a display on my monitor I have truck I have tried holding the on button and depressing the up and down volume keys no joy. I have tried pushing the manual reset button in the little hole on the side of the tablet. No joy. Is there anyone that can help me thank you in advance for your help.
I'd like to add that both tablets had their batteries drained and his condition appeared after I attempted to recharge them and start them up. Thanks again
Both of them started t do this at the same time???? Did you have power surge when you were charging them? Thunderstorms?
Very strange...
Anyway, if the rooted tablet boots normally and only the display is dead, it's exactly that: the backlight is out and you need a new screen.
The stock unit: Not much yoou can do with a locked bootloader. Can you get it into the bootloader menu with Power +Vol Down?
If not, there's not much more you can do. But you can cannibalize the sceen andput it into the rooted unit!
Sent from my ASUS Transformer Pad TF700T using Tapatalk
Restarts as soon as it enters recovery
Hi, my tablet froze last night and could not get out of the frozen screen, so I forced a restart , only to have it boot loop.If I try to go to recovery it just gets to the Twrp image and restarts again.
any help is appreciated.Unit cannot shut down and gets hot at the top left hand corner.Tried to hard reset using the side reset but to no avail.
Thanks.
This is happening a lot lately.... What rom and TWRP version are you running?
Check out the last few pages of the Katkiss Katshmallow thread. That's where we successfully solved this lately.
But I would really like to find out what's causing this. Can you try to access the tab in adb while it's looping in recovery?
Try to pull the recovery log and dmesg log.
Read this:http://forum.xda-developers.com/showthread.php?t=3040645
berndblb said:
This is happening a lot lately.... What rom and TWRP version are you running?
Check out the last few pages of the Katkiss Katshmallow thread. That's where we successfully solved this lately.
But I would really like to find out what's causing this. Can you try to access the tab in adb while it's looping in recovery?
Try to pull the recovery log and dmesg log.
Read this:http://forum.xda-developers.com/showthread.php?t=3040645
Click to expand...
Click to collapse
Thanks after a lot of attempts manage to get the thing going but could not get to get a log as it was restarting after a second or two in twrp screen but managed to push asus stock and unit is ok. Will root again and use a custom as it surely runs much better.
Thank you for your attention.
mgrankin said:
I have to Asus tf700 that will not boot they were only vibrate when you push the on button. One is rooted with zombie and the other is stock I get a display on the rooted tablet on the monitor I have connected through HDMI and I am able to navigate on the tablet with the keypad attached. The other one stock unit I am NOT able to get a display on my monitor I have truck I have tried holding the on button and depressing the up and down volume keys no joy. I have tried pushing the manual reset button in the little hole on the side of the tablet. No joy. Is there anyone that can help me thank you in advance for your help.
I'd like to add that both tablets had their batteries drained and his condition appeared after I attempted to recharge them and start them up. Thanks again
Click to expand...
Click to collapse
Hey, I'm experiencing the same issue right now.
In my search I found this:
http://forums.androidcentral.com/as...216663-tf700t-now-won-t-turn-post2270270.html
I plugged it into my pc and after a short period, pressing the power button showed a battery icon in the red zone. so I'm going to leave it plugged in overnight.