Database Info

Stock TF700 boot loop, can't turn off device.

Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.

Wow - you're in a difficult situation...
You being on stock I can only imagine the bootloop is caused by something you installed.
So if you can access settings and are able to uninstall apps, just keep doing it until you are back to the original stock setup.
Are you sure the files you are trying to save are still on the SD card? Don't know how you flashed 10.6.1.14.8, but flashing a complete firmware package ususally erases /data - although your persisiting bootloop indicates it didn't...... if the bootloop is caused by an app. And I can't imagine what else would cause it.
You could try to do a factory reset in Backup&Restore but you will loose the contents of your /data partition...
You can flash the 10.6.1.14.10 firmware file, but most likely you will also loose your data.
The only way I can think of to replace your bootloader and firmware without data loss is if you try to find a copy of the 10.6.1.14.10 dlpkgfile. That is the OTA update file Asus pushes out to users. It's a patch file, meaning it only replaces/updates new files and leaves everything else alone.
If you find the dlpkgfile on some forum you would have to place it into your /cache directory and reboot - and I don't know if you can copy it to your tablet before it bootloops again.
Unfortunately the reason for your bootloop is probably an app on the same partiton with the data you don't want to loose. Unless you manage to uninstall the culprit I don't see much hope....
Good luck!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4

Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.

_that6042401 said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
He's bootlooping..... How does he go into settings and turn on USB debugging?
I think the best option maybe to flash a stock Asus ROM from their site but that will wipe all data including those photos......

zanadoo22 said:
Back in June, I turned on my TF700 with the dock attached, it started as usual.. I turned on my wifi, opened up my browser to look up plane tickets, then it restarted. I didn't think much of it, and when it loaded up again, I tried to look up tickets again, and it did the same thing. I gave up, closed it and zipped it up in my sleeve. It was a few hours before I got home, and when I took it out of the sleeve, it was quite warm! It was constantly rebooting and there was no way to turn if off. I left it out of the sleeve and let the battery die. I didn't use my tablet for a few days, and when I went to turn it on again, the same thing happened, and has been happening ever since. I have tried to start the tablet while connected to the dock, the wall charger, without the dock, with wifi on, with wifi off, etc. The tablet gets to the lock screen, I unlock it, and I only have about 10 seconds before it freezes and restarts. I am unable to turn off the device, because when I choose "shut down" from the menu, it shows that it's in the process of slowing down, but then the spinning wheel freezes and it vibrates and restarts before it can fully shut itself off. Since I can boot into android, I thought it was something that the tablet is trying to run upon startup that was causing problems. I was able to quickly get to settings and apps, to uninstall several apps, but nothing has helped. I used to have a task manager widget on the home screen, and uninstalled that too.
After doing research into the problem, I found that most people who have boot loop issues or constant restarting, are rooted and are experiencing difficulties with a new ROM. I am 100% stock. I have held down power and volume down. It gives me RCK, Android and Wipe. I have tried cold booting into android, but the same restart loop after 10 seconds occurs. I thought it might have been a bad firmware update that went through unbeknownst to me. So I downloaded the firmware file from ASUS, renamed and flashed it sucessfully. However, no change in the reboot problem. I am running the following version: US-epad-10.6.1.14.8-20130514. I know there's a new version out, but wasn't sure if I should try to flash that yet.
I am willing to try absolutely anything to fix the problem, with the EXCEPTION of wiping data. I know that would be the easy way to go, but I have photos and videos from my best friend's engagement and they are the only copies. If I am able to get my tablet to be stable enough to copy those off, I would then be willing to wipe and have a fresh start. I have tried connecting my tablet to my computer, and it is recognized. After it boots up and I unlock it, then the tablet begins to mount (I'm on windows 8). However, I still only have 10 seconds or so before the tablet restarts, and that's not enough time to even view the folders from the tablet.
It's been 3 months since this started, and I have done lots of research and tried lots of things, but nothing has helped yet. Since I haven't delved too deeply into the dev side of android (I've only rooted my S3) there is lots of android speak that I don't understand fully, or have experience with, like ADB. If someone is willing to offer suggestions on what to try, I am very good at following directions! Thank you for any help or leads you can offer.
Click to expand...
Click to collapse
I have not use this method but you could try.
You need a boot OS tool on your external sd and run it from your external sd so you can access to your internal sd to copy files from there. You can search on the internet and you should find more information on how to use them depending on what boot os you are using.. Good luck.

zanadoo22 said:
and I only have about 10 seconds before it freezes and restarts.
Click to expand...
Click to collapse
sbdags said:
He's bootlooping..... How does he go into settings and turn on USB debugging?
Click to expand...
Click to collapse
Preferably FAST.
---------- Post added at 07:51 PM ---------- Previous post was at 07:51 PM ----------
LetMeKnow said:
You need a boot OS tool on your external sd
Click to expand...
Click to collapse
What is a boot OS tool?

_that said:
Try getting adb access, this should allow us to diagnose the problem you are experiencing.
Tablet side: go to settings, developer options (if it is not visible, tap the build number 7 times), enable USB debugging
Computer side: no idea, they say Windows 8 is a bit tricky to get the drivers installed correctly.
When you have adb running, do "adb pull /proc/last_kmsg" and post the downloaded file - it should contain valuable info about your reboots.
Click to expand...
Click to collapse
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?

zanadoo22 said:
I was actually able to get usb debugging turned on. It took me quite a few tries, but I did it!
I've never used adb, but here's what I've done so far.. I downloaded the Android SDK and ASUS Pad PC Suite (which contains Asus Sync).
I was able to use the command prompt to navigate to the platform-tools folder and open adb, however when I type in adb devices, it doesn't recognize my device. What steps to do I take from here to be able to use adb to see my device, so I can pull the file to diagnose what's going on? How do I know if I have the right drivers installed so my computer can see my tablet? All I did was install the asus suite. Do I need to do anything further on that end?
Click to expand...
Click to collapse
What Windows version do you have on your PC?
You can check your drivers in Device Manager. Open it, look for your tablet under Portable Devices and check if the driver has a yellow exclamation mark next to it. You should be able to update/install/uninstall the driver from here.
Try to find out if there is a setting in your Windows version to only allow Microsoft signed drivers and disable it.
Sent from my DROID4 using Tapatalk 2

[Q] Ultra Power Saving Mode not working

At first I though this was because I froze too much with TB but now when I've unfrozen everything it still doesn't work.
So far I've found "EmergencyManagerService" is related. I started trying one by one and found this one but then unfroze all.
I get a pop-up saying to wait while it configures (0/100)
But it doesn't ever turn on.
W8. Stock rom. Rooted.

same to me
no way to turn it on

No problem here....
Android 5.0.2 - Rooted

[Q] Turned Tablet Brightness Off

Hi,
I've got an envizen tablet which I accidentally turned the brightness off on completely. This is a serious problem, seeing as this is essentially a write-only device (see the wiki articles since this website is under the impression that I'll spam some links). If this somehow has a fix at all then it will be extremely hard to debug since a) I install many applications, b) I use a custom launcher, c) I have an applock enabled and settings is hard to get to now to enable USB debugging, and d) One of the first things I did to my tablet was disable the Android Device Manager. This is caused by a little program called Dimly, and even though I can successfully log into my tablet, the USB connection isn't set to allow ADB to debug.
This is the application-layer equivalent of a bricked device.
Please help me.

Resolved
This issue has been resolved by a force-shutdown and a viable timing window in which the services start up.

Question incoming call notification delay

I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you

MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)

k3lcior said:
MIUI is trash that's why. And it's related to agressive memory management. (killing apps in background, even system ones)
Click to expand...
Click to collapse
I have tried in the built-in power manager to set the power saving option for the dialer app to none, but no luck

Try disabling "Turn on MIUI optimisation" in the Developer options (scroll to the bottom of the page). It may work, or it may not work. Xiaomi thinks that disabling it can cause issues ...

Updated at 12.5.2.0 (RJUEUXM) and the problem is still present.
Do anyone have the same problem?

surcof said:
I don't know when it has started, but now when everyone try to call me the phone ring but i have to wait about 3-5 seconds before i get the notification on screen and i can answer
I have got the MIUI global 12.5.1.0 (RJUEUXM) and i know it is quite buggy, but i have googled a bit and none seems to have my same problem.
I read that i could try to wipe the system cache (on a oneplus one forum) but the standard recovery mode doesn't have this option, and i really don't want to wipe the phone to get another one
Any suggestion? Is there a way to wipe the system cache without formatting? Do anyone had my same issue?
Thank you
Click to expand...
Click to collapse
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.

kd276 said:
Similar problem with notification delays, in my case it affect sms and clock, dunno if this the same as your, however i post anyway, just disable via ADB the DOZE feature for apps affected with delays (do not work if i disable battery optimization in the normal settings).
Enable developer options in the device, enable usbdebug, connect the phone to the pc, install the correct usb MI drivers (use the MiUsbDriver.exe command), surf to adb directory and whitelist the system apps you want to have instant notifications.
To retrieve the list:
adb shell dumpsys deviceidle whitelist
To whitelist apps affected:
adb shell dumpsys deviceidle whitelist +com.xxxxxxxx.xxxxxxxx
Of course replace the apps name xxxxxxx with the correct name of system apps installed in your device.
Use the first command and check again if the apps you whitelist are now in the list as "user". Setting is permanent until you do a clean flash or flash a new rom.
No idea if you need to unlock the bootloader to apply such change, try it if work.
Click to expand...
Click to collapse
thanks for your replay, but no look for me.

surcof said:
thanks for your replay, but no look for me.
Click to expand...
Click to collapse
Sorry this isn't helping for your specific case.

Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.

Ochrana said:
Hi,
yes my brother has this problem when a friend calls his second sim card ... he uses two SIM cards at once, you also use two cards at once? (At once=two sim cards in mobile)
I only use one sim and I don't have this problem. the above advice did not help my brother, the problem is definitely in the dual sim function (implementation). Please report it to someone on xiaomi to fix it.
PS: can you try to use only one SIM card? if your problem goes away. let us know if this is the core of the problem. Thank you.
Click to expand...
Click to collapse
i only use one sim card, never used two

I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...

DrunphO said:
I have the same problem but in my case I think it's about having Zepp app giving notifications to my watch. Do you have a similar app? You can try to disable phone access to all apps except dialer and see if works...
Click to expand...
Click to collapse
Nop, the only app i use is the dealer

Have you found any solution?
Happen to me as well on mi9t pro. Further googling led me to believe this was issue with phone app by google. You can check theor review on playstore and most people having this issue.
i have factory reset my phone and problem is still there.

Little update: i have had this issue for all the time when i was in holiday with a poor interbet connection, now that i'm returned home, where i have quite alwais signal the issue seems gone.
May be that the dialer need internet access to work properly?

Hi,
I'm having the same issue with my poco x3 i keep having a delay before my screen turns on when i'm receiving call. Is someone still having this issue or it's just me ?
I don't think there's a link with Wifi, at least that's really strange to me.
Thanks

Answer is in second post, this doesn't happen on custom ROM's. (unless they are based off MIUI)

Same problem with Xiaomi mi 11

Try to remove all the email accounts from the gmail app, it should fix.

Same issue... POCO X3...
3/4 secs delay in notifications...
the phone rings and I can't see who is calling... After 3/4 sec it shows the notification...

It's very funny how everyone is ignoring @k3lcior 's posts, when he is just spitting truth in your face.
Sorry, guys, but you can't just ignore the real cause and look for a cheap workaround that might fix it in theory. In reality, ROMs like the official one from Xiaomi (MIUI) are extremely aggressive in terms of killing background apps, etc. They want to reduce battery strain, no matter how much stuff it breaks.
This is a problem across different apps. There are tons of issue reports from app users, that can't use some apps properly, because MIUI keeps killing it, even though it already has been whitelisted in the power saving list, as not allowed to be killed. It still gets killed, though.
So, if you guys want to keep your apps alive and not getting killed all the time, you have no choice but to switch to a different ROM. Even if you find a workaround on the official ROM, then it's still very unreliable.
To be clear, once again:
Even if you whitelist your app, it can still get killed, because MIUI does not give a crap, if you need the app. It still may get killed!

Recovering data through USB

Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5

Yolco said:
Today my phone felt down totally flat. The screen hits the floor directly.
It carries a protector above the screen, and apparently it is the only part that broke down
The screen seems to be in perfect status.
But the problem is screen is not working. None light is shown, and no reaction is performed.
If I touch the power button during 20s, the phone vibrates and it seems to be restarted.
When I connect the charger, the led works fine. Although no sound is played.
I would like to repair the phone, but at least (and this is important) I need to download all the data to the PC.
Question: is there any way to access to the data in the phone without having the screen available?
PHONE: MI9
OS: MIUI12.5
Click to expand...
Click to collapse
If you did not USB debugging enabled in system settings before the screen broke, you will not be able retrieve your data. Now that your screen is broken, there is no way for you to enable USB debugging in order to retrieve your data.
Your options are:
1) repair the screen so you can retrieve your data.
2) forget about your data and get a new device.
Live and learn. I keep USB debugging enabled on all my devices for this very reason.

I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.

Yolco said:
I found that I can retrieved my data thanks to custom recovery. I had a bit of lucky because with adb, data can be retrieved trhough custom recovery.
Usually, I have USB debugging activated but this time it was not activated as from last ROM update it is deactivated by default.
Now, I will deassembly the phone just to understand which is the root cause as touch sensor is working fine. So I need to understand if the problem comes from the screen or in the worst-case from connectors or PCB. In this last case I would need to get a new device, and I would like to keep this one for a few more time, even when there is no more OS update.
Click to expand...
Click to collapse
I was going to suggest that but wasn't sure you would actually be able to install it or even if a custom recovery existed for your device since you didn't post what model you have. Also, if you had needed to unlock your bootloader to flash a custom recovery, unlocking the bootloader would have wiped your data.
Yes, you were lucky, most users in this condition are screwed out of recovering their data.