Related
Hi all, I updated with the Asus download, and rooted with debugfs. For some reason, now, whenever I unlock or wake tablet up, I get an error message at bottom of screen. Says "ERROR. No root access or incompatible devise." (Yes, is spelled with an s)
Is there some way to find out what is causing error message and fixing? I AM rooted, and everything seems to be working, it's just HIGHLY annoying.
Thanks.
My suggestion is to unroot, restart, then re root.
That didn't work, BUT, it allowed me to find out it was touchscreen tune app causing error. Anyone else have a problem with it?
I read somewhere about a way to read error logs, but can remember. It will save some hair pulling next time something misbehave's. Can anyone point me to the link?
why don't you just uninstall the app and reinstall it? Or clear the data,cache from the app? I'm sure that would resolve your error messages.
I did both of those when I found out which app was doing it. No luck. Not overly concerned about it, but next time an app miss behaves, would be helpful to be able to find out which one.
did you go in superuser and try wiping everything in there so everything will ask for root access again? After wiping it, I'd reboot first, but that's another troubleshooting tip. Not sure about the log option.... most times you won't see these types of errors, or shouldn't anyways.
redheadplantguy said:
I read somewhere about a way to read error logs, but can remember. It will save some hair pulling next time something misbehave's. Can anyone point me to the link?
Click to expand...
Click to collapse
logcat is good tool to use. you can run it through a terminal emulator or through the adb interface from your computer. just search for adb and logcat and you'll find what you need.
I have disabled these root notifications -- so I never get thm -- but you might want to go into SU (or the recommended SuperSU) and find out if the permission is correctly set there. From there, you should be able to reset the permission (so it asks next time), or just put the correct permission in there (which would be accept for root access)...
On another note: does the Touchscreen Tune app even work on the TF700?
Sent from my ASUS Transformer Pad TF700T
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
adam_4049 said:
Hi all, I have completely screwed my surface rt last night.
I was trying to do a reset and it wasn't working then I tried a bunch of other things ive read on the forum and my surface wont even boot up. its just in a constant loop ive trying to do an automatic repair and diagnosing and keeps bringing me to the boot menu.
I made a recovery usb but it doesn't seem to be working so im assuming the OS was already corrupt hence the reason the reset option in "change pc settings" wasn't working.
I would really love if someone could upload a recovery image of their surface rt. I cannot find one any where and the ones I have found they have pulled the links down.
hope someone can help me out here.
cheers.
Click to expand...
Click to collapse
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
C-Lang said:
Next time do a search. You would have found a thread on this. And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you. Take it to Microsoft and have them replace it.
Click to expand...
Click to collapse
i did do a search and nothing has been able to help me so far. i also did read that it is device specific but have also read it has worked for some people. unfortunatley in australia we do no have any microsoft stores so its not that easy to just take it somewhere.
I feel like there are files missing from c drive. Almost like it started to do a restore then stopped halfway. In which I have never been able to get it to that stage for that to be the case.
I did some reading and was able to find the recover partition and tried to run the install.wim file from which I understand to basically be the “OS”. When I try to run it it says “no such interface supported”
From what I understand there is just no way to do a fresh install on these things regardless of what the problem is which is disappointing on Microsoft’s behalf.
C-Lang said:
And, as was said in the aforementioned thread these recoveries are device specific, so even if I got mine to you, it wouldn't work for you.
Click to expand...
Click to collapse
No. Those recovery images are device-type specific. Not device-specific. You can safely take one WIM file from the recovery partition of your device and use it to recover a different device of the identical model.
adam_4049
I see that you were able to start a restore process and it fails in the middle.
You may try the following: boot into the command line mode and format the boot partition (probably drive C: ). This would fix the disk errors if they are present, but you'll lose everything. Use diskpart tool to find the disk letter. Be careful with diskpart - do not delete partitions or issue "clean" command.
Then assign the letter to recovery partition with diskpart (say, R: ), then expand WIM file from the recovery partition with the command like this:
Code:
Dism /apply-image /imagefile:R:\RecoveryImage\install.wim /index:1 /ApplyDir:c:\
R:\RecoveryImage\install.wim - a path to install.wim on the recovery partition.
More info: http://technet.microsoft.com/en-us/library/hh824910.aspx - you need only "Dism /apply-image" part, bcdboot is unnecessary. Lets hope that "apply-image" option is present on RT.
This would forcibly expand the WIM file to your disk C:. Or at least you'll be able to see why it fails.
This may help. Or may completely brick the device and you'll need to go to service. So use it on your own risk. And you should be familiar with the command line - so don't ask how to use diskpart.
I had a problem with the recovery process when I've played with BCD and added a boot from VHD option. Had to delete that extra boot setting - and then recovery went fine. But I assume that you have not played with BCD.
Yeah, looks like people dont use search, what you want is a nice useful soul that creates a USB recovery from his EN-UK Surface_RT and puts it up on Copy, or Dropbox or something like that...
Lately this error appear a lot in my cm10.1.5. Do you know any way ti fix it? I ask to start trying every solution you post, even that I have already tried a lot of possible ways (all of them wrong) Thanks
As a last resource you could always wipe all your partitions and reflash the ROM.
I never got such an error though, so I don't know what your are talking about. Maybe with you could post some log file about the error, it would be easier for the people here to help you with it.
I've recently started having problems after changing ROMs a couple of times.
I tried installing a new Rom (CM12.1) but it is still happening and I've installed a new GAPPS each time too so I guess the problem runs deeper than that.
The ROM runs fine for a bit but then all of a sudden I get a force close which constantly keeps coming up no matter how many times I press 'Ok'.
I've had a few different processes stop but the last two that spring to mind are 'process.android.phone', 'Swiftkey' and 'Google Play'.
I have to reboot but then end up stuck at the splash screen at boot. I then have to Power+Vol Down to go into recovery and then reboot system from there. It then runs through the App optimisation screen brfore restarting.
I've never touched kernels since I've been changing ROMs so whether thats the issue.
Any help with this would be great as otherwise this is the best Rom Ive used.
Thanks in advance
A logcat showing traces of these force closes would help
Aquous said:
A logcat showing traces of these force closes would help
Click to expand...
Click to collapse
I didnt do one on account of me not having a clue what the hell one was
Luckily my friend Google does know what the hell one was.
I've attached a couple of log files created around the time of the unpleasantries which hopefully might shed some light.
This one attached might be better, this was taken after I sorted out my Root Access again so might have more info.
Regards
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Aquous said:
Looks like a resources issue. Are you running any custom CM10 theme? What happens if you install such a theme providing an icon pack?
Click to expand...
Click to collapse
Hi, thanks for your reply. I havent been near any other custom themes. I've had this problem over a couple of Roms too.
I've tried to generate a catlog to get some error messages around the time its happening but I keep getting constant force close boxes which stop me doing anything (for a couple of different processes). The only way to stop them is to reboot but then the logs stop and reset when it boots so I cant get the info.
I've had to reboot about three times today and each time it has had to optimize the apps for some reason.
I've tried to get a catlog through ADB but I cant run the Android SDK as I need to install the JDK which keeps giving me 'Error 1500' on the install (even though I am most definately not already trying to install it).
Thanks for your help so far though and taking the time to read through the previous log.
Every solution I try just seems to create more problems
I've managed to attach a text file of all the error files its had since it started up (they are all in the space of about 10mins)
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Aquous said:
I'm not seeing any force closes in there. In your previous log, I saw these lines:
Code:
07-15 18:24:07.919 W/ResourceType(2356): No package identifier when getting value for resource number 0x00000000
07-15 18:24:07.919 W/PackageManager(2356): Failure retrieving resources for [insert any package here basically]: Resource ID #0x0
which led me to identify resources (i.e. icons, drawables, etc) as your culprit.
What we need to do with that information, I wouldn't know. Ask the rom dev, I suppose?
Click to expand...
Click to collapse
Well I'm assuming their force closes. I get a white box popping up that says 'unfortunately XXXXX has closed' and when I click 'ok' the box goes away but either comes straight back or another similar one pops up. Its Trebuchet quite a lot.
I can't do anything then, if I try to get to LogCat that closes too and I can't really do anything until I reboot.
Its happened over 3 different Roms so dont think theres much the Rom compiler (is that what they're called, lol) can do.
I'm am probably going to have to see if I can get a Log through ADB, if I can remember how to use it, when I have time.
Cheers
I've managed to connect the tablet through ADB and managed to get some errors taken at the time I started getting all the 'Unfortunately XXXXX has closed [ok]' boxes kept coming up.
All the error messages attached came up in the space of a few seconds.
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Aquous said:
Ahh, now this is interesting. The main cause of your problem is that your filesystem is remounted read-only, which Play Store Services doesn't like.
As to why this is going on I can only guess, but it's possible that it's due to filesystem corruption. Can you try running fsck from recovery?
Click to expand...
Click to collapse
Hi,
Thanks for looking through them errors.
To be honest I haven't heard of fsck. Is it something I can pick up fairly simply or am I more likely to do more damage? I've done a few searches and it looks a bit difficult and couldn't really find any threads that sounded similar to what I might need.
Thanks again
Update : I've gone into recovery and found files in /system/bin called fsck.exfat and fsck.f2fs is it a case of running a command through terminal command in recovery from this directory?
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Aquous said:
Fsck is the linux file system checker. The binary is named e2fsck. I think the command should be:
Code:
e2fsck -pv /dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS
This will try to automatically fix any errors (be sure to note whether there are any). If it complains about unexpected inconsistencies, you'll need to remove the 'p' argument to prevent it from trying to do any automatic fixing.
Note: the whole point of this command is to check and, if needed, modify low-level filesystem structures, so there is a risk of data loss on your DATAFS (i.e. /data) partition.
Be sure to note if there are any errors. If there are, we need to investigate where those are coming from. If not, something else is causing your fs to remount readonly (because THAT is ultimately what is triggering your system to flip out).
(Apologies for the delay, it's been a busy week)
Click to expand...
Click to collapse
Hi,
No worries mate, I wasn't sure if what I said didn't make sense thats why there were no replies
The problem seems to be a lot better now but I've still had it a couple of times over the last two days.
I've tried to run the command above but with no joy. I'm still only learning the basics of ADB so still having some trouble.
I wasn't sure exactly where to run the commands from through the SDK so just went to the Terminal Command in Recovery and after navigating to the system/bin folder tried that command but it came up with the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS is in use
esfsck: cannot continue, aborting
I apologise if some of what I am doing seems nonsense but I am trying to pick up what I can by myself from various sketchy threads to avoid being a 'tell me what to do cos I can't be bothered looking myself' person. I dont know if this is doing more harm then good
Thanks again in advance for your help.
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Aquous said:
You cannot check a filesystem while it is in use. Solution: boot to recovery (sorry, I should have specified), then make sure your data partition is not mounted (in CWM it isn't by default, which is good). Then it should be able to run.
(so: boot tablet to recovery, on computer run 'adb shell', in adb shell copy/paste the actual fsck command)
Click to expand...
Click to collapse
For some reason I cannot get my PC to pickup the tablet in a command window when in TWRP so I was unable to run through ADB. 'ADB Devices just did not show anything.
In the end I did it all on my tablet in TWRP through the 'Command Terminal'. I navigated to the necessary folder (the one with fsck.exfat and fsck.f2fs in - /system/bin) through the Command Terminal and after typing the command in I got the following:
/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS clean, 9086/791520 files, 694414/3160055 blocks
Is that good?
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Aquous said:
It means that your emmc is fine and that there's a different reason why you're getting force closes. Can you post a dmesg next time it happens?
Click to expand...
Click to collapse
Hi, yea sure. I could use a bit of guidance with exactly how to do that though. I take it that is something I would have to run through ADB from my PC before I reset my tablet? Step by step instructions would be appreciated a lot (as has your extensive help already, creep creep ).
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Aquous said:
Boot to normal android. Wait until you start getting force closes. Stick your tab into your computer, run 'adb shell', then run 'dmesg'. If it says permission denied, run 'su' first and then run 'dmesg' again. Post the output.
Click to expand...
Click to collapse
Right, first thing this morning I had some errors, so I've managed to paste the results of a dmesg into the log file attached.
Cheers!
Hmmmm, now this is interesting. It looks like random services are failing to load - they are immediately exiting after being restarted. This is basically the same problem as with your apps force closing - something at the lower layers is causing everything to crash immediately upon launch.
Yet you're able to run basic programs (e.g. adb, dmesg) just fine, meaning that it's not likely to be a hardware issue.
What happens if in adb shell you run su and then 'stop' followed by 'start'? What should happen: when you run 'stop', the whole system freezes, and when you run 'start', you see your boot logo and android starts booting up again. Is this indeed what happens in this case, or do you get a bootloop? If so, post another logcat when you're stuck in the loop; you can get out of it by simply entering 'reboot' in your still-open adb shell.