Related
I will be accepting donations if you like my work. After contacting HTC, they informed me that my device is not under warranty, as a technician determined it to be "user related" damage and that all repairs will be at owner expense.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8141983
If you follow my twitter, you know I bricked my G1. I am trying to get it repaired, but due to the long response time I had to buy a mytouch (no point having two G1s IF the other one gets repaired). Using this bad luck to my advantage, I scripted a way for hero to run on both with two simple commands.
How I rooted a brand new "perfected SPL" MT3G and installed Hero in 15 min:
http://forum.xda-developers.com/show...&postcount=154
Link to original thread: http://forum.xda-developers.com/showthread.php?p=4365404#post4365404
Updated, but still feeling slow? Back up. Try rm system/sd/app_s then reboot to recovery and wipe data. then install fresh. Before restoring your data, open the backup folder on your sd card and remove the subfolders for programs you no longer have or need to have backed up.
I noticed a 10% increase in speed and my phone was far from lagging to begin with.
Losing messages? Make sure that system/sd/app/com.android.mms.apk does NOT exist, as this was an old release. Go into settings for messaging (from the conversation list panel) and set priority to "High"
Most Recent:
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-6.0.zip
Now includes dynamic swap. Rewrote the method of apps to sd for myTouch.
Build will move system apps, user apps, and dalvik to sd on a g1 device.
Build will ONLY move user apps to the sd when using a myTouch.
This will allow the system apps and dalvik to remain on internal device.
This is a completely new method of doing a merge build so bear with me.
I am going to be rewriting things for users without a lot of user apps, like myself.
This will allow the entire build to be placed onto internal for mytouch users.
Once you have updated and are ready to use the phone, execute Terminal and enter the following commands:
su
magic
This configures the system to the specific device. This is until I finish automation.
LEDs have been restored to 93%
Bluetooth restored in MT3G
Porting my own boots for MT3G
Based on the System Image from Haykuro
Using the Kernel and Boot.img from JAC
Extensive system script edits were done
SwitchROM installs itself to system/sd/
LEDs are at about 90-100% brightness
CPU Optimization turned off by default
Enhanced Terminal included
Fixed My Account included
G1 / MT3G: http://twistedumbrella.slackdev.com/ZeroXd-5.2r5.zip
http://twistedumbrella.slackdev.com/Resources.zip
twistedumbrella said:
MultiTouch for MT3G being patched NOW
Click to expand...
Click to collapse
Does that mean multitouch doesn't work and one more unanswered questio IS it from the latest release that modaco did, i asked it since 5.0 so please answer
White Rosie doesn't work i tried it but i doesn't show up and it doesn't even install shows parse error, can you do something about that. Really appreciate your work. Will donate as soon i finish with my exams, I came to US for a holiday for 3 months and as i came back i have exams, only 3 left, have to finish 6 books per subject (thats f*****ng 3 months syllabus) and i have exams after 2 day holidays , thats why i have been a bit inactive in the community, will be active on 24 and will provide a special version of HERO based on my favourite ZEROXD.
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
mgorman said:
Installed JACHeroSki 2.0 and i get stuck on a boot loop. i've tried wiping and re-flashing and same thing.
Click to expand...
Click to collapse
For me 2.0 working fine,but cannot install ZeroXd-5.2r4-installation aborted:/
In v2.0 cannot run wifi:/somebody else?
Had to fix scripts. Check the link on original thread for download. They are the same files. The verification fail happens when your downloading as I upload. It was a last minute fix on the way to work. Sorry for the issues.
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
tq745 said:
hey twisted...great work on the roms...
couple issues with me...
auto-rotate doesn't work...
auto correct and dictionary doesn't work also...
is there any way we can correct this?
Click to expand...
Click to collapse
Thank you... h.nocturna for the fix, and nacron for the heads up...
Here is the fix for auto-complete... Worked for me on 5.1r2
Everything in
open dos prompt.
adb remount
(***back up the original***)
adb pull /system/sd/app_s/HTC_IME.apk c:\(*your directory*)\HTC_IME.apk
(***install the new one***)
adb push c:\(*your directory*)\HTC_IME.apk /system/sd/app_s/HTC_IME.apk
start your Messaging it will crash the first time you want to use the keyboard... restart Messaging and it should work...
HTC_IME.apk here: http://www.mediafire.com/?te0symyx4yz
Mms auto-rotate works for me in 5.1r2 so I dont know. But possibly you still have the old Mms.apk. Try pushing the new one from 5.0 or later rom...
Twisted are you using BFS in your new builds??? Post 5.1 that is....
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambesey's way
twistedumbrella said:
What device are you using? MyTouch? Did you run the terminal command?
BTW, for everyone else: http://twistedumbrella.slackdev.com/user.conf
Did some testing, seems to run a little smoother
Click to expand...
Click to collapse
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
same issue as above :-(
1.8 is running pretty awesome.
i guess its safe to assume that i shouldn't try 2.0 yet? lol
zeroxd 5.2r4 seems to be faster than jacs 2.0 but i cant get auto rotate to work or multitouch and when i try the commands in first post i get "/system/xbin/su: not found''
did you try running the commands via adb ?
im not familiar with doing it that way i dnt even know wat adb is
just connect your phone to the pc
install the drivers from android SDK
start > run > cmd
cd to the android tools directory
and adb shell
that's how i did with my phone and works perfectly
im not gona risk any damage ill deal without the rotate for a day till its fixed
tq745 said:
so i opened up better terminal and when i entered su it says
/system/xbin/su: not found
help?
in the meantime i'll try zambezy's way
Click to expand...
Click to collapse
should be under /system/bin not xbin
Hello,
with several roms every week, suddenly appears this image.
After showing and select "force close" comes again and again and again. Then I reboot the device and the same problem. I have to reinstall again the rom or install a new one, but as i mention before, it happens every week.
I am going to appreciate if someone told me why happens.
Thanks a lot in advance.
ortigosano said:
Hello,
with several roms every week, suddenly appears this image.
After showing and select "force close" comes again and again and again. Then I reboot the device and the same problem. I have to reinstall again the rom or install a new one, but as i mention before, it happens every week.
I am going to appreciate if someone told me why happens.
Thanks a lot in advance.
Click to expand...
Click to collapse
1. are you using cm7 or any cm7 based roms? if you are, do not use the 2g/3g toggle in the cm power widget. that is a known issue.
2. have you ran a fix permissions? this is needed every once in a while especially if you are flashing different roms. theres a few ways to do this. you can run fix permissions in whatever recovery you are using on your nexus s, except stock recovery. or you can do it via terminal emulator on you phone. open the terminal emulator, type su(press enter) fix_permissions(press enter)
Fix permissions and clear cache!!!!!!
Sent from my Nexus S 4G using xda premium
simms22 said:
1. are you using cm7 or any cm7 based roms? if you are, do not use the 2g/3g toggle in the cm power widget. that is a known issue.
2. have you ran a fix permissions? this is needed every once in a while especially if you are flashing different roms. theres a few ways to do this. you can run fix permissions in whatever recovery you are using on your nexus s, except stock recovery. or you can do it via terminal emulator on you phone. open the terminal emulator, type su(press enter) fix_permissions(press enter)
Click to expand...
Click to collapse
First of all, thanks for your answer.
1)I am using cm7.
2)Till now i never used this option called "fix permissions"
I disabled the 2g/3g toggle and I fixed permissions, i hope now works better...if the problem comes i will let here know.
Thanks a lot!
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
by posting lamely, U r not helping the developer u r just spamming his thread
to really get help, make sure u have a logcat of your problem
What is logcat?
Logcat is the command to view the internal logs of the Android system. Viewing logs is often the best way to diagnose a problem, and is required for many issues. This way you'll find out what apps are doing in the background without you noticing.
Advantages of Logcat
Debugging
You can see what processes are running, if a process is running after a certain interval of time, it will eat battery. So you can also find out what is draining your battery.
What developers need is a logcat To know what is the issue
i will tell u how to make it on a phone itself
1) download an app called ALOGCAT
2) install app and open
3) u will find random text coming there (its not random literally )
leave it in background by pressing homekey
4) this step is specific
for eg. if are having trouble in switching on wifi , try to swtich it on or do fiddle wid anything u have .. just play around with your cell, run the app u think is buggy or whatever
once done
5) press home button for long, select alogcat app,
6) click on options hardware button (right one ) and click on save.
logcat will be saved to sdcard/alogcat folder in the form of txt files.
7) now either u can directly upload the logcat.txt while telling about your problem
or
u can copy the contents of that txt file and paste on www.pastebin.com
after pasting u will get a link something like pastebin.com/******
just copy link and paste along wid ur problem
8) now next time u have a problem make sure u attach a logcat along with it
this method is not useful if u r not able to boot the phone
for that u need to have a pc and android sdk installed along with the drivers
if u have everything installed then
Open the 'run' dialog by pressing the 'Windows' + 'r' buttons on your keyboard (minimize the browser & other non-windows programs)
cmd (this will open a DOS prompt)
cd c:\Android\tools (go to the directory where you extracted the SDK)
adb shell
Now you'll see just a '$'
logcat
You can now just press the power button on your phone to see what happens. It displays everything the device is doing.
This is my first post regarding logcat , so i m sorry for any discrepancy (if there, notify me plz)
P.S - logcat is also useful in case if u r having some trouble wid stock roms
thanks @El_Dark for extending the op.
When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
Thank you, Now problems will be solved easily.
__________________
Sweet Devil >_<
GT-P3100
Android 4.0.4 ICS
Sun Cellular
"LG should go bankrupt"
GApps+ | Not your typical Gapps.zip
Very good to know. Thanks!
Sent from my SGH-i777
Nice tks!
Thanks for the tips, I use app called CatLog. Works good.
Sent from my Nexus 10 using Tapatalk HD
Thank u very much for ur thread
Sent from my Micromax A50 using xda app-developers app
doctor_droid said:
Many off us here are using custom roms and are spamming the developer thread by posting our issues without attaching a logcat
simply like
my bluetooth is not starting
my hdmi is not working
Etc bla bla...
..............................
...............................
Click to expand...
Click to collapse
Thanks. This is very useful...
Thanks for the post. :good:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
El_Dark said:
A little .20 more to this When you guys are experimenting on a custom rom (i.e. nightlies, betas, RC's, "just cooked", etc.), it's very likely that your phone might not boot correctly, fear not and instead, try using ADB there are loads of guides regarding how to properly set-up your PC for using ADB, starting by the Android SDK's page itself lol
Now, to do the said logcat, open a command window and do:
C:\Users\Dark> cd \<Name of your Android SDK folder>\sdk\platform-tools [Hit ENTER!]
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe devices (just to make sure your computer detected your phone lol)
C:\<Android-SDK folder>\sdk\plarform-tools> adb.exe logcat -v long > somefile.txt (the "-v long" part creates a nicely formatted file )
That's it!! Remember to zip the file if it's too big
Another tip: Some phones are very catchy when under heavy issues (like mine ) in those cases, timing is essential between rebooting and getting your log, however!!! The adb logcat command makes sure to wait for the device to get detected
HTH!!
Click to expand...
Click to collapse
i will add this to op if u permit ..
doctor_droid said:
i will add this to op if u permit ..
Click to expand...
Click to collapse
Of course!! That's the idea
Thank you! Very useful to know.
hi guys
i have a weird problem, every time i turn on or restart my phone it keep rebooting
when i remove my sim card phone work great.
when i insert sim card phone keep rebooting again until i connect it to the charger
what is wrong with my g3 D850 ? :crying:
i live in iran so sry for my bad english :d
any tips?
I was having the same problem but only with one Rom that was stock based. Switched ROMs and have had no issues since
jasonpantuliano said:
I was having the same problem but only with one Rom that was stock based. Switched ROMs and have had no issues since
Click to expand...
Click to collapse
what rom you use?
king_siavash said:
hi guys
i have a weird problem, every time i turn on or restart my phone it keep rebooting
when i remove my sim card phone work great.
when i insert sim card phone keep rebooting again until i connect it to the charger
what is wrong with my g3 D850 ? :crying:
i live in iran so sry for my bad english :d
Click to expand...
Click to collapse
To get a decent answer, it may be best for you to run a logcat.
Folks the best way to help with device issues is to post a logcat.
The Android logging system provides a mechanism for collecting and viewing system debug output. Logs from various applications and portions of the system are collected in a series of circular buffers, which then can be viewed and filtered by the logcat command. You can use logcat from an ADB shell to view the log messages.
For complete information about logcat options and filtering specifications, see Reading and Writing Logs.
For more information on accessing logcat from DDMS, instead of the command line, see Using DDMS.
Syntax
[adb] logcat [<option>] ... [<filter-spec>] ...
You can run logcat as an adb command or directly in a shell prompt of your emulator or connected device. To view log output using adb, navigate to your SDK platform-tools/ directory and execute:
Click to expand...
Click to collapse
Here are 2 excellent XDA threads explaining Logcat "How to"
[Tutorial] How To Logcat <<< explains how.
[GUIDE] Installing ADB/SDK and How to make a logcat
Or, this app from the market can allow you to create one direct from your device>>> aLogcat ROOT
While we can say we have problems, we (the community) are by no means Android mind readers
So help others, help you... logcat, it may help save the life of another frantic flasher :good:
The Rom was 855 minus 5.
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.