• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Boot problem???

F

FloRida1999

Newbie
I have an unusual problem that maybe some of you guys can help me out with. For the last 3-4 weeks my phone will not boot up on the first try, but it will on the second try everytime! Im currently running half-ass mod, kk2.5 set to data, TWRP recovery and have partitioned my sd card and it is still doing it. Has anyone heard of this or know what I did wrong to make this happen? It's really just an annoyance for the impatient, as I'm close to throwing it into the next concrete wall i see. Thanks.
 
Well, might be a problem with formatting the the sdext..... And for your "wrongdoing"...... Maybe you should not use TWRP, since the download was pulled ! There are some problems with TWRP.... and while some people have no trouble, you could be the one running into trouble. I'd reinstall CWM5 for the time being, until a fixed TWRP is released. Not sure if this will fix your problem, but it might.

Cheers....
 
Thanks vce2005 for the reply, I didn't know twrp download was pulled, as I have been seeing it in the forums everyday. I'll change it back to CWM today and see if that does the trick. It's just weird because it doesn't do that on my girls' phone. Will post back with results.
 
I'm not so sure that recovery will have an effect on the normal system outside of that recovery making changes to the filesystem.
It is very strange that you would have an every other boot situation.

Personally, I never shut my phone off. Most people probably don't either.

You could try clearing the Dalvik Cache and see if that clears things up.

You could also try making a backup of your apps and settings, and then do a factory reset and see if that clears it up.

Before any of that though, I would personally like to see what shows up in the logcat when your phone is unsuccessfully booting. I'm suspecting that there is some app that is conflicting with another app, so if app 1 starts before app 2, things are good. If app 2 starts before app 1, they fight and prevent the system from booting
 
Hey Kouma, first off, thanks for reading my post. So, I reinstalled CWM and the problem still exists. I just got out of school, turned on my phone and this time it took on the 3rd try. I don't think I have any apps that have given me problems in the past, but I will get the log of startup and see what happens when I get home later.
 
Hi,

did you do what Kouma suggested ???

1. Go into Clockworkmod and "wipe dalvik" ( then try )

2. Get Titanium Backup and backup all your apps....

3. Go back into Clockworkmod and do the Factory Reset !
 
I did a factory reset and it is still booting on the second or third time. In CWM I went navigated to, Advanced/Show Log and this is what showed up when I looked at it in Root Explorer. I hope this is what Kouma was talking about. I have Noooooo idea how to interpret this guys, fyi......

Starting recovery on Fri Nov 16 01:57:25 2012
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /recovery bml recovery (null)
3 /system rfs /dev/block/stl12 (null)
4 /data rfs /dev/block/stl13 (null)
5 /cache rfs /dev/block/stl14 (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext ext4 /dev/block/mmcblk0p2 (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
mount: mounting /dev/block/stl14 on /cache failed: Invalid argument
W:failed to mount /dev/block/stl14 (File exists)
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_prevail-eng 2.3.7 GINGERBREAD eng.vaccar.20111020.203403 test-keys
ro.build.version.incremental=eng.vaccar.20111020.203403
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Oct 20 20:34:57 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=vaccar
ro.build.host=GX620-U2
ro.build.tags=test-keys
ro.product.model=SPH-M820
ro.product.brand=samsung
ro.product.name=full_prevail
ro.product.device=SPH-M820
ro.product.board=prevail
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=prevail
ro.build.description=full_prevail-eng 2.3.7 GINGERBREAD eng.vaccar.20111020.203403 test-keys
ro.build.fingerprint=samsung/full_prevail/prevail:2.3.7/GINGERBREAD/eng.vaccar.20111020.203403:eng/test-keys
ro.HOME_APP_ADJ=1
ro.PERCEPTIBLE_APP_ADJ=0
ro.ril.samsung_cdma=true
ro.telephony.default_network=4
ro.telephony.call_ring.multiple=false
ro.telephony.ril_class=samsung
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
wifi.interface=eth0
wifi.supplicant_scan_interval=45
DEVICE_PROVISIONED=1
ro.com.android.dataroaming=false
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
ro.media.dec.jpeg.memcap=20000000
ro.sf.lcd_density=160
ro.opengles.version=131072
mobiledata.interfaces=rmnet0,eth0,gprs,ppp0
ro.ril.hsxpa=2
ro.ril.gprsclass=10
hw.keyboards.0.devname=vino_keypad0
hw.keyboards.65538.devname=vino_headset
android.keylayout.vino-keypad=/system/usr/keylayout/vino-keypad.kl
android.keylayout.vino-headset=/system/usr/keylayout/vino-headset.kl
android.keychar.vino-keypad=/system/usr/keychars/vino-keypad.kcm.bin
debug.sf.hw=1
debug.composition.type=mdp
ro.compcache.default=18
dalvik.vm.dexopt-flags=m=y
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=64m
persist.sys.purgeable_assets=1
persist.sys.use_16bpp_alpha=1
persist.sys.use_dithering=1
ro.vold.umsdirtyratio=20
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.1.0-HROARK
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=sph-m820
ro.revision=9
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
 
Hey Kouma, I'm in the middle of getting my logcat in a .txt file, do I want to extract everything or are there certain (tags) that are more relevant to what I'm doing?
 
FloRida1999 said:
Hey Kouma, I'm in the middle of getting my logcat in a .txt file, do I want to extract everything or are there certain (tags) that are more relevant to what I'm doing?
Click to expand...

adb logcat *:W *:S > ~/Desktop/logcatALLwarnings.txt

So, the command above would give you all tags that had a priority of Warning, Error, or Fatal. It would silence (not show) everything else and would pipe the output of your log to your desktop as a text file named logcatALLwarnings.txt

(Taken directly from the link on posted)
 
Lordvincent 90 said:
adb logcat *:W *:S > ~/Desktop/logcatALLwarnings.txt

So, the command above would give you all tags that had a priority of Warning, Error, or Fatal. It would silence (not show) everything else and would pipe the output of your log to your desktop as a text file named logcatALLwarnings.txt

(Taken directly from the link on posted)
Click to expand...
i did, adb logcat-v long. I'm going to do this one now.
 
Lordvincent 90 said:
adb logcat *:W *:S > ~/Desktop/logcatALLwarnings.txt

So, the command above would give you all tags that had a priority of Warning, Error, or Fatal. It would silence (not show) everything else and would pipe the output of your log to your desktop as a text file named logcatALLwarnings.txt

(Taken directly from the link on posted)
Click to expand...

"~/Desktop" only works in linux
you have to use "%userprofile%\desktop" if you're using windows
 
Hey guys, I have my adb logcat, for persons smarter than me, to look at. Im sorry i havent done this earlier. I tried to attach it to this post, but its 150kb long and the max size for a .txt file is 58kb. Any idea how i could trim it down without cutting out the important parts?
 
Might wanna sign up for Dropbox, so you can upload the file and provide a link for others to download !! Not a bad idea anyway to have a free Dropbox account ! ;)
 
FloRida1999 said:
Hey guys, I have my adb logcat, for persons smarter than me, to look at. Im sorry i havent done this earlier. I tried to attach it to this post, but its 150kb long and the max size for a .txt file is 58kb. Any idea how i could trim it down without cutting out the important parts?
Click to expand...

Copy/paste to to pastebin.com and post the link
 
FloRida1999 said:
okay i got the link up for my logcat, v-long, (W)
Hey Lord, can u tell me if I did this correctly or not? Im not really sure what to look for?? I can redo it if this isnt what Kouma was talking about.

http://http://www.mediafire.com/view/?ef95wyecfpo3r6f
Click to expand...

Your mediafire like is broken.:p But as long as the logcat was taken at a time when the phone was stuck at the koumakernel logo, then yes you did it correctly.
 
Koumajutsu said:
just remove the extra http://
Click to expand...

*Facepalm*

browsing the forum while @ work fail...

RE-edit- my internet connection here is S L O W. It isn't even loading...

@kouma- You see anything jumping out at you? (if the text is there for you)
 
Lordvincent 90 said:
*Facepalm*

browsing the forum while @ work fail...

RE-edit- my internet connection here is S L O W. It isn't even loading...

@kouma- You see anything jumping out at you? (if the text is there for you)
Click to expand...

I see text, but nothing very useful.
It looks like the phone had been running for a while and anything useful had pushed out of the log buffer.

The only thing that stands out is something doing odd stuff named Finsky.

I don't have that in my logs.

FloRida: what you want to do is start collecting the log while the phone is off. It will wait for the phone to come online and will be able to get the log from the very beginning.
 
You must log in or register to reply here.
Back
Top Bottom