No apps, almost no respons - Shield Tablet Q&A, Help & Troubleshooting

Hi there.
I got a stock K1 with lastest OTA system.
I normaly don't shut it down because it will do it itself after 6 hours.
Yesterday my last use was Netflix (steaming to chromecast)
Today the shield would not boot and i put it on a charger, no symbol in display but i let it there for about an hour.
Now it almost won't boot up:
Long time bootscreen, no apps to be found, almost no respons at softbottons.
powerbutton wont show a menu.
How to factory reset in this case?
Best regards
UPDATE: the Micro SD functioning as internal memory seemed te be corrupt

Related

[Q] Screen freeze

Over the last couple of days I have been having an issue with the sensation. I can boot up the phone and have full access to the boot loader.
The problem occurs when I leave the phone in standby for a while. The phone will become un-responsive and wont turn ont at all.
I was running the latest RCMix rom and everything was fine. I then decided to install j4n87's tweaks I know it is for a newer base but I just wanted to try it. Ever since I installed the tweaks the phone hangs when the screen is turned off.
I have tried full wipe and reinstall of everything but cant fix the issue.
Even noticed that if I pull the battery and power it back on the screen will stay black. You can hear sounds see button lights and power light but nothing on the screen. It then takes a couple of attempts of using adb reboot to get the screen to come back on again.
Any Ides.
Just tried flashing stock rom fro ruu same issue.
Edit 1:
Hmm I am wondering is my SD card causing the issue. With it in the phone when the phone is on stand by the freeze will occur in a couple of minutes. On the stock rom with the SD card out I am able to leave the phone in stand by for 10+ minutes and it is waking with out any issues. I will try it with ICS to see how it behaves.
Edit 2:
Interesting: it does look as if it is the SD card causing the problem. I restored my RCMix ICS rom and left the card out of the phone, with the phone on. I left it on standby for half an hour and it woke up with out any issues. Looks as if I could be getting a new SD card!

[Q] Flytouch / superpad Android logo freeze

A few years back I purchased a Flytouch II / Superpad. Installed several custom roms and had no issues. It sat in my parts box for a while and I figured I drag it out and see what I could use it for.
Initially it booted fine (running Tim6...I think) once it was up and running it started lagging and would not respond (Screen got too hot and it stopped seeing my touches)
One of the icons on the screen was a shutdown script pre-loaded. Apparently it had pressed this, the script popped up and I tried to hit close before it shutdown, The script closed and after a little more playing I shut it off by holding the power button down, then sliding the power off slider that came up.
The next day I went to power it up and it just freezes on the android logo screen. No bootanimation, nothing.
Since I'm not shy about taking stuff apart it carefully took it apart and removed the internal sd card (4gb) and made a backup of it using dd. I then loaded an sdcard v4 image I found online, it still just hangs at the green android screen.
Also tried several "brick fixes" here on xda.
If I boot it without an sdcard it says "No Card in Machine!!!" so I think the systems is ok hardware wise.
Any ideas of other steps to take?
Got it figured out. Feel kind of silly.
Just needed to format both cards to fat32 and add the two files from tim6a back to the external card. It booted, reflashed and away it went.
Phew, thought I was going to have to rig up a touchscreen for my computer

TF700 Boot Looping / Freezing in Boot Loader (experienced user)

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...

System UI has stopped notification stuck in loop right after Nvidia logo.

I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a low battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now I have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now, every time I boot it up, once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
This would normally be no problem but the instant I click OK the same warning pops back up. It is just stuck in the same loop, process stops, I hit OK and repeat for as long as my patients lasts and I try rebooting...
(why a 16gb WiFi only model even needs the cellular data process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Factbook gave this result :
Cold booting Linux
Then the Nvidia logo, and the same system UI has stopped warningtI have read several threads on similar problems but none that are the same as mine.
I bought my shield tablet (16gb wifi) off Amazon so I can't really tell you much about it's exact specs. All I know is that I was told that only early manufacturer runs had rooting and OTG issues, and that newer runs had OTG out of the box.
Mine doesn't have OTG enabled, and it would not root with most of the common self installing root apps. So I believe it is an older version.
I have been installing all Nvidia updates as the update notification comes up on my tablet except for the latest one released a couple days ago. (waiting for WiFi to down load)
I was running marvel future fight at the time my tablet did a forced shutdown for a dead battery.
Later I plugged it in to charge for a few minutes. When I first plugged it in I got the normal warning image of an empty battery telling me I could not boot yet.
I waited several minutes and tried to boot, but the boot process took an extensive amount of time.
But the real issue is that now every time I boot it up.
Once the Nvidia logo disappears instantly before the lock screen or anything else can come up, the notification that one of two processes have stopped comes up. Those being System UI, and Cellular Data.
(why a 16gb WiFi only model even needs that process is beyond me or why it would prevent a complete boot... )
Any way I started research and found the power + volume down bootloader option.
It took me several tries to figure out how to even get the timing right for that to work. But once there it was no help.
First option for Fastboot
It says cold booting Linux the displays the Nvidia logo, but up comes the same warning of one of those stopped processes that will pop up as fast as I can click OK, for as long as I will click ok...
I tried the recovery option and that gave me the error of no command with the dead android with the warning sign popping out of his insides.
Just hit the reboot option and as of right now it did not boot... Will try holding down the power for manual reboot. As it will not power on normally now.
Manual reboot to the options again and going to try the power off option.
I am thinking that I might be able to fix this by flashing from a pic... But I wouldn't know as I have never gotten into that stuff before.
Cellular data stopped is still coming up on boot attempt... Only other option I know to try is open the menu back up and try the recovery again or maybe on the of chance hitting continue might do something different that changes things up and let's it finish booting.
I assume it is not actually completing the boot cycle as I cannot bring up the soft keys nor does the lock screen come up.
(don't get me started on the evils of soft keys. )
Anyway any help anyone can give would be great!

Power died on SMP-900, now having problems with apps, Lineage OS and TWRP

Back story:
My beloved tablet ran down on power as I was using it today (note to self - change warning percentage from 5% to something like 15%)! I tried shutting it down, but it died before the shutdown was finished. I put it on the charger and let it charge until about 65%, took it off the charger, powered it up. It started coming up, got to the the PIN screen, then nothing. Couldn't do anything, touch screen wasn't doing acknowledging anything. I think things got corrupted as it was powering off...
Powered it down, waited a few minutes, then powered back up. Took about 10 minutes to start after I entered my PIN, and it was behaving strangely:
1. WiFi said it was off, but I was getting e-mails (sent one to myself from another device to confirm it)
2. Settings would start, but got nothing, just a white screen.
3. Most apps would start but really slow, then suddenly shut down
4. Tried booting into TWRP 3.1.1 - got the initial screen, there it sat for the next 20 minutes before I rebooted.
5. I can get into bootloader, but fastboot from my Linux laptop doesn't work - can't find any devices when the tablet is plugged in.
6. "adb devices -l " shows the tablet is connected, but get no prompt on the tablet screen about adb starting
6. "adb reboot bootloader" and "adb reboot recovery" from my laptop just sits there - nothing happens on the tablet.
I'm on Lineage OS 14.1 (latest weekly for the SMP-900) and TWRP 3.1.1 on the tablet, and Fedora 25 on the laptop. Rebooting is iffy - sometimes it starts, sometimes it doesn't and just sits on the Lineage boot animation. I also have my 128Gb SD card set up as part of the internal memory (i.e., can't pull it and stick it into another device) Every reboot takes longer, and I fear the next power on will have me just sitting there, staring at the Lineage boot screen forever.
I have Nandroids from TWRP, but doesn't do me much good if I can't get into TWRP to use them. I have TWRP image and tar files, but jodin (a Java based Odin type of program that works in Linux) doesn't get a response from the tablet and therefore won't flash.
If I could get the tablet back to the point where I can get TWRP working again, I can reload from the TWRP backup. I also don't have a Windows computer available at all, but I do have Windows XP in a VMware virtual machine as an absolute last resort on my laptop.
Does anyone have any ideas or pointers to get me running again? Right now, it's powered off and charging...
Thanks for any help....
Patience, patience, patience ...
I'm answering this myself - just so there is an answer.
If you ever run into this problem, read the heading above! I got the tablet to boot up finally by pulling the 128 Gb SD card first, then powering up the tablet. I plugged in the SD card back in and it started slowing down, but checking under Storage, it indicated it was checking the encrypted card. I set it aside, checked it 2 hours later - still checking the card. Plugged it into the charger and went to bed, got up this morning and it was shut off. Powered it up, it booted up, this time around it recognized the encrypted card as part of internal storage and Life is good again.
My assumption is that when the tablet died, the card was marked dirty (I.e., not shut down properly.) When I tried TWRP, it noticed that the card was flagged dirty and started checking it before it would give me the home screen - same thing with Lineage when it tried to boot. And yes, I changed the battery power warning to 15%.
Thanks for your update on that problem.

Categories

Resources