Hi all
I know this will sound old school but, does anyone know how to get the startup of the sola to show what is actually loading?
Like when you accidentally hit the esc key on your keyboard and the ubuntu boot screen disappears and shows you what is actually happening.
Like I said STOCK STARTUP!
Now mounting system to /system.........
Mounting data to /data..........
Type of thing, similar to MS Windows 98 SE.
I know there must be a way
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
I'm also interesting about it. To disable boot logo (bootanimation.zip) and see what's happening behind
Basically nothing, you just get your manufactures logo and thats it. Nothing more nothing less. We probably have to edit a file somewhere
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Ok....... anyone know how to startup in debbugging mode atleast?
DEV Device: MB511 (deodexed)
Current System: MT27i
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
Possiblilty
finally found something that should work except..... you need UART or JTAG access......
Any how thanks Adam Outler!!!!!!!:highfive:
http://forum.xda-developers.com/showpost.php?p=16466682&postcount=5
Edit:
The settings in SBL prompt are
Code:
setenv SWITCH_SEL 6543
setenv PHONE_DEBUG_ON 1
saveenv
Code: Starting kernel at 0x32000000... Uncompressing Linux................................................................................................................................................................................... [ 0.000000] copy: bad source 0 [ 0.000000] mout_audss: bad source 0 [ 0.090142] KERNEL:kernel_sec_get_debug_level_from_boot=0x574f4c44 [ 0.094877] KERNEL:magic_number=0x0 DEBUG LEVEL low!! [ 0.099895] (kernel_sec_set_upload_cause) : upload_cause set 0 [ 5.833835] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery' sh: can't access tty; job control turned off $ [ 11.433364] init: no such service 'bootanim' [ 24.851663] init: sys_prop: permission denied uid:1000 name:wifi.interface [ 35.227503] init: no such service 'bootanim' [ 38.484304] init: sys_prop: permission denied uid:1000 name:dpm.allowcamera su sh: can't access tty; job control turned off # dmesg|tail [ 47.443068] [email protected] [ 51.363390] mook - wm8994 TTY Off [ 51.666438] eth0: SIOCSIWSCAN : ISCAN [ 51.667822] +++: Set Broadcast ISCAN [ 53.013468] [email protected] [ 54.447852] Send Event ISCAN complete [ 54.448053] eth0 wl_iw_iscan_get_scan buflen_from_user 8192: [ 54.448067] eth0: SIOCGIWSCAN GET broadcast results [ 54.448111] wl_iw_iscan_get_scan return to WE 803 bytes APs=3 [ 84.445803] wl_iw_set_ss_cache_timer_flag called #
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
will give it a try. i wish there was a guide on the hijack for the motoboot file.
Edit: thank you! It works like a charm, now to strip it and see how it works. When I get cash I will purchase the full version lol! Chainfire kicks ass! :thumbup:
n2droid said:
This app shows you live dmesg at boot [requires root]. Not exactly what you wanted, but close enough on the geek scale.
https://play.google.com/store/apps/details?id=eu.chainfire.livedmesg.lite
Click to expand...
Click to collapse
I found logcat live wallpaper and loving it!
https://play.google.com/store/apps/details?id=org.jraf.android.logcatlivewallpaperlite
DEV Device: MB511 (deodexed)
Current System: MT27i xICS
Long Live: V9 Ferrari Rom
code.google.com/p/motorola-flipout-files
I apologize because I just posted a thread very similar to this one recently, but I felt this warranted a new thread because I have a lead on the cause of the problem. I've been having random reboots on various AOSP ROMs (stock, crpalmer, and torrented's kernel, makes no difference) for the past few months, and I think I found the cause of it but I have no idea what to do about it. My phone has been fine for 2 or 3 days but I just got 2 random reboots in a row and I was finally able to take a last_kmsg of it and I found this:
Code:
Kernel panic - not syncing: SurfaceFlinger PC:fput+0x24/0x32c LR:ion_import_dma_buf+0x210/0x238
[ 480.493575] c0 251 [MDM][COMM] mdm_panic_prep: setting AP2MDM_ERRFATAL high for a non graceful reset
[ 480.894338] c0 251 set_restart_reason: set restart reason = 776655aa
[ 480.894368] c0 251 set_restart_msg: set restart msg = `KP: SurfaceFlinger PC:fput+0x24/0x32c LR:ion_import_dma_buf+0x210/0x238'
Can one of the anyone, particularly a kernel dev, possibly shed some light on what I can do to fix this? Again, I'm getting these reboots no matter what kernel I'm using. I'm not sure if it's the same cause every time but this is something. I'm going to run it on stock again for awhile and see if I get different messages. Thank you.
Contact crpalmer in the original development forum.
I've had the phone for 2 months without any issues (other than the crappy GPS and compass) and about a week ago, all of a sudden it started to randomly turn itself off. At about the same time it completely destroyed the SD card, after warning me a few times that it was 'unexpectedly removed' which always fixed itself on its own within a few minutes - anyway, gutted about losing all my precious data but I suppose it's otherwise unrelated, the new card runs OK so far.
The shutdowns occur on average 3 times a day and the phone can't be turned on without removing the battery, which is the biggest annoyance. Running stock G4W 20130819-085550 (upgraded from previous version but not sure what that was) but even tried MIUI 3.11.16 by sta-s2z - same problem. Bought it from uredeal.com which appears to be down so can't even ask about warranty. Not aware of installing anything that could be the cause.
Some logs from CatLog are attached, surprised by the huge number of errors, some fatal in case of the 2nd and 3rd log but they don't seem to be the same cause (?) also suppose the 1st log might not have any fatal errors only cos I had the write period set too long, then reduced it to 5 lines. I have no idea what to do or try next. Any ideas, please?
One more log... can somebody help please?
bump... please... :crying:
If u can access play bstore, searcha and install jiayu.es application, it´s in english . it will give u access to latest stock rom without the chinese stuff.
Hope it solves your problem.
guerrix: thanks but unfortunately the issue prevails under that ROM, too
My Nokia phone also appears you this kind of situation, I am very upset, don't know how to solve.
tyrol_gangster said:
I've had the phone for 2 months without any issues (other than the crappy GPS and compass) and about a week ago, all of a sudden it started to randomly turn itself off. At about the same time it completely destroyed the SD card, after warning me a few times that it was 'unexpectedly removed' which always fixed itself on its own within a few minutes - anyway, gutted about losing all my precious data but I suppose it's otherwise unrelated, the new card runs OK so far.
The shutdowns occur on average 3 times a day and the phone can't be turned on without removing the battery, which is the biggest annoyance. Running stock G4W 20130819-085550 (upgraded from previous version but not sure what that was) but even tried MIUI 3.11.16 by sta-s2z - same problem. Bought it from uredeal.com which appears to be down so can't even ask about warranty. Not aware of installing anything that could be the cause.
Some logs from CatLog are attached, surprised by the huge number of errors, some fatal in case of the 2nd and 3rd log but they don't seem to be the same cause (?) also suppose the 1st log might not have any fatal errors only cos I had the write period set too long, then reduced it to 5 lines. I have no idea what to do or try next. Any ideas, please?
Click to expand...
Click to collapse
Experiencing exactly the same issues with a Jiayu G3S, did you manage to get to the bottom of it????
phatrat: afraid not
ok so work-around found thanks to jiayu.es forums, use app Wake Lock to setup partial wake + apply on boot + notification. eats lots of battery but no shutdowns for several days now.
I have this same problem of random shutdowns. It switches of completely random, at least that's what it looks like. I have found out at least two things:
1)Try to turn of wifi! If you turn of wifi, it has never happened to me that it shut down randomly. I do never use 3g or 2g mobile internet, so I don't know if an active 2/3g makes the phone shut down. At least I recommend you to do it.
2) Most oftenly, the phone turns off when I receive some whatsapp messages. I can see it, because of the warning light on top of the phone that is flickering. Furthermore removing your complete whatsapp and reinstall it cleanly, does not solve it. Cleaning or removing your SD neither does. I'm still on it, but do not expect major breakthroughs from my side. I'm not a phone technician.
I haven't tried a fresh install, somewhere I think it would solve the problem. But that is my phone instinct.
Do you guys have changed stuff in the internals? Like change the framework, install xposed, etc?
tyrol_gangster said:
ok so work-around found thanks to jiayu.es forums, use app Wake Lock to setup partial wake + apply on boot + notification. eats lots of battery but no shutdowns for several days now.
Click to expand...
Click to collapse
Thanks for the reply. Could you be more specific in regards to the steps necessary, is the app required called 'Wakelock Detector-Save Battery'? I had a look on the Jiayu.es forums but couldn't find anything in regard to the solution you suggested (doesn't help it being in Spanish). Any help would be greatly appreciated.
foro.jiayu.es + google translate: Install an app called Wake Lock (A light bulb with a padlock.) This application makes it unique is that the phone when "locked" not enter hibernation state and therefore the CPU is always running. Advantage : Well, so far has not given me any failure mobile and took almost 3 days with the application. Disadvantage : It is assumed that sucks a lot of battery, but I loaded it yesterday evening and now I have 78% battery. How is this application set? 1. Open the application. 2. Click "PARTIAL_WAKE_LOCK". By pressing a series of numbers appear (to 4) and put as text "Partial. Ensures That the CPU is running. The Might not be on screen.". 3. Press the button on the left to open the mobile application options and click on "Options" and have labeled "Autostart on boot" and "Notification".
deleted
tyrol_gangster said:
deleted
Click to expand...
Click to collapse
I have a G4A. Which model are you running -- basic, or advanced or other? What ROM are you running?
Have you tried any kind of debug or test to determine which component of the phone is the culprit? Try to fresh power-on the phone from power-off, enable debugging in settings, connect a USB cable to a computer (and phone) and running "adb bugreport > results.txt" command and post the results.txt file here. Also can use "CatLog" app or some other logcat app or dmesg app to record logs, and post the log file to here.
Just for kicks, you can also try 'factory mode' ? This will test hardware and output some messages. This can be done by taking out the battery, hold the VOL DOWN button, plug in a USB cable to computer, keep holding VOL DOWN button until the phone powers on and shows a chinese menu. On the first menu item, press POWER button once.
http://adbshell.com/commands/adb-bugreport/how-to-use-adb-bugreport.html
I have the same problem (i;ve tried 4 different roms)
I've tried the last official
staz and kiloes miuis
with no luck
i've seen that when i use two sim cards the problem is worse..
i'm posting the adb bugreport (because i cannot indestand it..)
miaoumiaou said:
I've tried the last official
staz and kiloes miuis
with no luck
i've seen that when i use two sim cards the problem is worse..
i'm posting the adb bugreport (because i cannot indestand it..)
Click to expand...
Click to collapse
bump!:victory:
miaoumiaou said:
bump!:victory:
Click to expand...
Click to collapse
didn't see anything bad in your 'results txt' file. try logcat or catlog app from android google play or download its apk file and record / save its log and post that here. note: some devices show nothing useful from logcat or catlog (like my Jiayu)
also try a "dmesg" log app.
UIComposeThread -- Error
petesimon said:
didn't see anything bad in your 'results txt' file. try logcat or catlog app from android google play or download its apk file and record / save its log and post that here. note: some devices show nothing useful from logcat or catlog (like my Jiayu)
also try a "dmesg" log app.
Click to expand...
Click to collapse
Code:
<4>[ 8964.893014] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.895583] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.908995] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.911452] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.925037] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.927552] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.942011] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.945884] (1)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.958120] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.961902] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.975137] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.981266] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8964.991238] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8964.997252] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.007323] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.013268] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.023325] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.029292] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.039414] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.045342] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.055405] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.061320] (0)[16302:pal.androidterm][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.071463] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.086371] (0)[641:ndroid.systemui][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency = 0
<4>[ 8965.087409] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.103667] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.119479] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<4>[ 8965.135596] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
i got this error report when i was trying these directions "Fortunately, there is a kernel file /proc/kmsg which does exactly the same thing. One can just run the following command to continuously dump the kernel messages. "
with this command # adb shell cat /proc/kmsg
but i cannot understand these errors..
miaoumiaou said:
Code:
<4>[ 8964.893014] (0)[546:UIComposeThread]ERROR!!!Layer 3 format error!!!
<5>[ 8965.086371] (0)[641:ndroid.systemui][Power/GPU_DVFS] mt_gpufreq_keep_frequency_non_OD_get, mt_gpufreq_keep_specific_frequency
i got this error report when i was trying these directions "Fortunately, there is a kernel file /proc/kmsg which does exactly the same thing. One can just run the following command to continuously dump the kernel messages. "
with this command # adb shell cat /proc/kmsg but i cannot understand these errors..
Click to expand...
Click to collapse
disregard those messages because I also got hundred's of those when I capture kmsg output but my phone works fine. I don't know what those messages mean either. but no worries.
Code:
adb kill-server
adb devices
adb shell su -c cat /proc/kmsg > kmsg-output.txt
[ CTRL C ]
zip kmsg-output.txt.zip
did you try "logcat" app or adb logcat command? try this. the file will be large so please zip (compress) the file and attach this zip file here.
Code:
adb kill-server
adb devices
adb logcat -v long > adblogcat-output.txt
[ CTRL C ]
zip adblogcat-output.txt.zip adblogcat-output.txt
if adb logcat does not work then try this alternative command (needs root) :
Code:
adb shell su -c cat /dev/log/system > adblogcat-output.txt
[ CTRL C ]
you may see my logs for comparison. good luck.
I started getting random reboots a few weeks ago. I cant tie it to any app in particular and my phone doesnt seem to be getting hot. I thought maybe unlocking the bootloader and flashing a custom rom might help so i flashed CM13 and it seemed to get more frequent and it would almost go into a bootloop that i could only stop by going into recovery and rebooting that way. I eventually flashed stock lollipop back onto it and it slowed down to every once in a while and didnt do the bootloop thing anymore. I did a logcat through ADB but i dont know how to interperet it. Could anyone help?
Code:
[ 03-21 20:30:54.246 1429: 1429 D/KeyguardViewMediator ]
handleMessage dt = 0
[ 03-21 20:30:54.249 16086:16086 I/View ]
ssignParent(ViewParent parent) parent is: com.android.mail.ui.SwipeableListView{262fdc16 VFED.VCL .F....ID 0,0-720,1022 #7f0f0194 app:id/conversation_list_view}
[ 03-21 20:30:54.270 1964: 1982 I/HwSystemManager ]
HoldService:callUid: 10009 notificationType: false
[ 03-21 20:30:54.270 1964: 1982 I/HwSystemManager ]
HoldService:pkgName[0]: com.google.android.backuptransport identity: 42988327681828
[ 03-21 20:30:54.276 876: 891 V/SMCSAMSHelper ]
SMCSAMSHelper.addSTPEvent: cost 0 ms end.
[ 03-21 20:30:54.276 876: 891 V/SMCSAMSHelper ]
SMCSAMSHelper.smartTrimAddProcessRelation: cost 0 ms end.
[ 03-21 20:30:54.280 16164:16315 I/PG Utils ]
acquire_provider pkg:[com.android.providers.contacts] pid:[] send to pg
[ 03-21 20:30:54.296 1964: 2071 I/HwSystemManager ]
HoldService:callUid: 10009 notificationType: false
[ 03-21 20:30:54.297 1964: 2071 I/HwSystemManager ]
HoldService:pkgName[0]: com.google.android.backuptransport identity: 42988327681828
[ 03-21 20:30:54.298 876: 1508 V/SMCSAMSHelper ]
SMCSAMSHelper.addSTPEvent: cost 0 ms end.
[ 03-21 20:30:54.298 876: 1508 V/SMCSAMSHelper ]
SMCSAMSHelper.smartTrimAddProcessRelation: cost 0 ms end.
[ 03-21 20:30:54.301 16164:16315 I/PG Utils ]
acquire_provider pkg:[com.android.providers.contacts] pid:[] send to pg
That was the last of what it picked up before it rebooted. Any ideas?
I too am getting a sudden burst of rebooting after rooting my phone while on B322. I am working on removing apps one at a time though I do not think this to be the issue.
This error message has been showing up for weeks and my camera isn't working. I found something interesting in my logcat files. The back camera rarely works but the front one always works I need to fix this I've missed many good photos. I am running Ressurection Remix 5.8.3 (Android 7.1.2) With ElementalX kernel. I don't know a lot about logcat files or what any of this means and I wound really appreciate if someone could help me out.
[ 07-11 19:54:31.990 29825:29825 E/Camera3-Device ]
Camera 0: getStreamInfo: Device has encountered a serious error
[ 07-11 19:54:31.990 29825:29825 E/Camera2-StreamingProcessor ]
updatePreviewStream: Camera 0: Error querying preview stream info: Function not implemented (-38)
[ 07-11 19:54:31.990 29825:29825 E/Camera2Client ]
startPreviewL: Camera 0: Unable to update preview stream: Function not implemented (-38)
[ 07-11 19:54:31.990 29825:29825 E/Camera2Client ]
updateRequests: Camera 0: Error streaming new preview request: Function not implemented (-38)
[ 07-11 19:54:31.999 29825:29907 E/Camera2Client ]
autoFocus: Camera 0: Call autoFocus when preview is inactive (state = 1).
If I need to provide the whole logcat I am able to do so.
Which device was it?