Hi everyone:
I am attempting to boot AOSP 4.0.4 (r1) for the Galaxy Tab 10.1 wifi (GT-P7510). I have merged pershoot's CM9 3.1.10 kernel and been able to get through a few errors noticed in last_kmsg. However, I'm trying to figure out why servicemanager is now crashing and can't seem to get a hold of a logcat. I must be doing something stupidly simple incorrectly...have searched high and low and every example I have seen of someone complaining of a servicemanager crash with the same output has a logcat to provide.
Basically what's happening is I try to boot, see the Samsung Galaxy Tab logo, it sits for about 20 seconds and then auto-reboots back into recovery after the 4th servicemanager crash.
I edited the init.rc to increase loglevel to 8 which is showing me more detail, but not enough. I've attached my last_kmsg, init.rc and init.p3.rc to this thread in a zip file.
Here's what I'm doing to try and pull logcat:
1) Boot into recovery, wipe my device, install my rom/kernel + gapps
2) Run "adb logcat -v long > logcat.txt". I get the obvious "-waiting for device-" message
3) Attach device to computer
4) Reboot device and wait
When the device goes back into recovery after the failed boot, I check the output file and it's empty. What dumb thing am I forgetting? Or is it legit that the system is just not getting far enough into the boot sequence to start adbd?
Thanks all very much in advance for any assistance you can provide.
Never mind, worked it out on my own.
Sent from my Infamous Tab.
I've been experiencing random freezes, at least one daily, which force me to hold power to restart the phone. The phone otherwise appears to operate just fine. I finally figured out the SDK system and got an error-filtered logcat. I have no idea how to interpret whats going wrong, and before I pin a logcat in the wrong dev forum, how can I determine the relevant causes of the errors recorded?
adb logcat *:E
cm 10.1.3
ajk 4.8
ucmd8 modem
4.1.2 bootloader
-Cyril
Good day all
I bought this device from a seller of eBay (from USA), I am in South Africa
I had to network unlock this device, and it all ran perfect, no issues whatsoever
Recently I have noticed my device doing random reboots, once every day(literally), it will reboot when I take it off from charging or when I press pwer button to wake up. After reboot, it will show the Glowing Samsung Logo, and just stay there continueously.
To fix this, I need to do a factory reset, or just clear the Data partition then it works fine again.
This happens at random, so every day I need to reinstall all the apps, it is such a pain, and obviously something is wrong...
Device: Samsung Galaxy Note LTE (i717)
ROM: Blackstar Blackjelly 4.1.2
Baseband: I717 UCMD3
Recovery: TWRP (latest v.)
Just for the record, ,it all started happening recently, the first time it happened, I was browsing 9gag using the app, then my device rebooted in my hand while scrolling, agter going to recovery, my sdcard and internal sdcard has been formated, and all internal partitions has been formated to....
I have no idea what is causing this but I am pretty sure it is not the rom, since I have had this rom for a while now...
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
BachMinuetInG said:
What kernel do you use, and can you take a logcat?
(To take a logcat, enable ADB, plug in your device to your computer, and run adb logcat from the Android SDK. You can grab that here: http://developer.android.com/sdk/index.html?hl=sk )
Click to expand...
Click to collapse
after running the logcat with "
Code:
adb logcat > logcat.txt
" for just more than 2 hours, i stopped it...it is 1250kb, see attached, it is compresssed in a zip file
p.s. Im quite positive it shouldnt take that long
any help would really help!!!
Nothing seems to have triggered this as it was working fine for years. However now when I try to enable bluetooth, the button turns light green indicating that it's trying and a couple minutes later it turns back to off state. No error message is generated. I have rebooted several times and also booted into safemode with no change.
The phone is rooted and I downloaded logcat to try a track down the error. I could probably use some direction on what specifically I'm looking for to troubleshoot but I do see 2 items that stand out:
1) an attempt to open /etc/bluetooth/bt_vendor.conf fails
2) set_bluetooth_power: write(/sys/class/rfkill/rfkill10/state) failed: Operation not permitted (1) [happens twice]
Any ideas?
Recently I've been experiencing problems trying to listen to online radios through mpv in Termux and Terminal Emulator. It used to work before.
It runs the command, plays for less then a second because I can hear something, then it stops and gives me the segmentation fault.
My phone is an Xperia Z C6603, rooted with stock rom, debloated to the bone by myself, locked bootloader -> no recovery.
I've tried hard reset and reflashed the phone twice with Sony software repair, but i still get the error.
I've read here and on other websites that an fsck must be performed, but:
- i don't have a recovery so I cannot unmount the partitions
- I don't know which partition to fsck: I get a TON of lines when I type su -c mount
Could someone please help me?
EDIT: I've managed to install TeamWin dualxzrecovery. Now what?