Can someone tell me why I keep getting the directory error at the bottom on my linux box? Sorry am learning linux as i go. I created a zip directory under bin so not sure why I am still getting this error?
no files for configid 26220739write xip block starting at 81800000, with 3 fileswrite xip block starting at 81980000, with 0 filesthis rom seems to be 3.17.03 ENG 2003-05-15 o2eurothis bootloader seems to be V5.22 2003-05-15 17:46:5580000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8026a804 -- kernel 13 files 11 modules802c2000 - 8057d330 9 OS 15 files 32 modules80580000 - 8075a69c 8 SHELL 79 files 27 modules80780000 - 80a13b04 7 BROWSING 9 files 14 modules80a40000 - 80d8a33c 6 COREAPPS 46 files 30 modules80dc0000 - 80ebd150 5 SYNC 12 files 22 modules80ec0000 - 810388e0 4 24MAPPS 13 files 13 modules81080000 - 81348248 3 24MCONSUMER 69 files 1 modules81400000 - 814019a4 -- xip chain 10 xip entries81440000 - 817f6f14 1 MISC 209 files 40 modules81800000 - 8184ac20 10 XDA_DEVELOPERS1 3 files 0 modules81900000 - 81925800 -- bitmap : 101a301a .. beb6fc8d81940000 - 81960278 -- operator rom 10 files81980000 - 81981054 11 XDA_DEVELOPERS2 0 files 0 modules./mkrom.sh: /bin/zip: No such file or directory
It looks as though you do not have an appropriate ZIP program...
You may want to see if bzip2 will work instead of zip, or get the linux version of RAR.
The issue though, is you do not have /bin/zip, which is an executable file, not a directory.
Maybe someone can verify what compression executable to use instead of /bin/zip...
J
Ok got that resolved but now when doing zip it gets permission denied. Any other assistance is greatly appreciated. Then should be able to have yorch and company's kitchen running
I would verify that the user that is executing the shell (mkrom) has execute permissions to the zip program...
you can run (as root)
Code:
chmod 755 /usr/bin/bzip2
to change permissions on the bzip2 executable file.
That will give root all access, and everyone else read/execute access.
Also, if the zip program uses any temp directories, make sure the same user has read/write permissions to those directories as well (Probably not your problem, though)
J
Ok got that resolved....now here's what i get....is this a safe error or something I need to worry about? How can I correct it?
./mkrom.sh: ./tounicode: Permission deniedwrite xip block starting at 81720000, with 6 fileswrite xip block starting at 81cb0000, with 72 filesCan't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.Can't exec "./dumprom": Permission denied at drparse.pl line 22.readline() on closed filehandle FH at drparse.pl line 24.!!! your rom is not known to me: md5: dad2e3cad6095282bf1d58ccf12171e8this bootloader seems to be V5.22 2003-05-15 17:46:55no operator rom found80000000 - 80040000 -- bootloader 0 files 1 modules80040000 - 8015df78 9 XIPKERNEL 5 files 5 modules80180000 - 80376f10 8 KERNEL 10 files 14 modules80380000 - 8064306c 7 OS 20 files 36 modules80670000 - 80be66a8 6 SHELL 107 files 88 modules80c00000 - 8102ce98 5 BROWSING 11 files 36 modules81050000 - 813ef114 4 COREAPPS 95 files 44 modules81400000 - 815d2238 3 EXAPPS 34 files 7 modules815f0000 - 8171bc7c 2 PHONE 56 files 19 modules81720000 - 8177ffe0 10 XDA_DEVELOPERS1 6 files 0 modules81780000 - 81781c34 -- xip chain 11 xip entries817c0000 - 81ca1b44 1 MISC 225 files 42 modules81cb0000 - 81d4eb7c 11 XDA_DEVELOPERS2 72 files 0 modules81ec0000 - 81ee5800 -- bitmap : ffffffff .. ffffffff../rom.exe: found a preamble of 35328 bytes adding: English/NK.nbf (deflated 44%)Archive: rom.exe;The comment below contains SFX script commandsSetup=start.batTempModeSilent=1Overwrite=1 Length Method Size Ratio Date Time CRC-32 Name-------- ------ ------- ----- ---- ---- ------ ---- 0 Stored 0 0% 07-28-03 15:28 00000000 English/ 262144 Defl:N 11018 96% 05-20-02 18:27 f4419bea English/CLoader_serial.nb 262144 Defl:N 12683 95% 05-20-02 18:17 d576b33c English/CLoader_usb.nb 4608 Defl:N 1094 76% 07-17-02 17:22 578b9c86 English/GetConnectionType.dll 18432 Defl:N 7650 59% 04-24-02 15:44 e4ed8f0a English/remote_flash.exe 3584 Defl:N 856 76% 08-21-01 16:43 da38a539 English/SetSystemTime.dll 73728 Defl:N 36119 51% 07-09-03 07:09 95cf7c18 adaptrom.exe 155648 Defl:N 50839 67% 08-28-02 15:23 f5a4ac25 PROGRAMME A.exe 3548 Defl:N 1078 70% 08-28-02 15:25 65d98105 readme.rtf 25 Stored 25 0% 07-28-03 15:28 ecfe543d start.bat32505888 Defl:N 18306975 44% 10-11-03 21:28 34cc9720 English/NK.nbf-------- ------- --- -------33289749 18428337 45% 11 files
Looks like you have the same execute permission problem with the tounicode exe.
Try to fix that.
About the drparse.pl, I have to look at that file, to see what it is trying to do...
Ok, here is the line:
Code:
open FH, "./dumprom $romfile|";
Looks like it is trying to open (as a file) the output of the dumprom executable.
So, dumprom is failing, probably ... yes, I see it now..
Verify the permissions on dumprom as well...
In fact, all *.pl and *.sh files should have execute permissions, use the same command as above to set them.
This reply is a rambling one, I know, but I wrote is as I was doing the research.
Let me know if it helps you.
J
Here's what is weird. I have changed those permissions as you said previously and still get the same error. What's strange to me though is I can run the kitchen with rom ver 3 something, but all of the ver 4 roms come back with the error. Any idea as to what the cause of that might be?
btw jta thanks for all the help. If you have time and would like to look at the box for me I will get access to it for you. Thanks.
I got it all working now. Thank you thank you thank you very much for the help.
Ah, good to hear that you have it all working now!
So, when do we get to try it out?? (wink wink)
J
Very soon....we are now putting finishing touches with other software installs....so will be very very soon.....
type:
cd /usr/local/bin
# ln -s /usr/bin/zip zip
Trying to solve audio stuttering...
I'm currently running the Eclair build from Kenia from
http://forum.xda-developers.com/showthread.php?t=827537
Like the speed, most things working fine.
... but playing media results in audio stutter.
Problem is apparently well known and affects more devices, see also
http://forum.xda-developers.com/showthread.php?t=711692&page=364
Indeed, killing battery service solves stuttering, but I'd like to keep it running, of course
Any build/kernel out there that does not suffer from this?
I'd like to find out what's different, since in the past it seemed to have worked, but with pushing more accurate battery readout in the latest kernels, this problem was introduced...
Maybe just putting an old battery service in a current kernel could work?
Cheers,
Robbert
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
g3rm0 said:
I can confirm that audio shuttering is a common problem, but I wasn't aware it can be related to the battery code. Can anyone check if killing battery service helps with shuttering audio (youtube maybe?) on other build (e.g. FRX03)?
TBH battery code is unfinished since Camro (the guy who did most of it) bricked his phone. If it's really a kernel issue maybe I'd could build test kernel w/o battery code sometime next week.
Click to expand...
Click to collapse
Hi, g3rm0,
Always happy to do some more testing!
Took me some time to get a FRX03 build back working (not my daily build, Froyo is just too slow on blackstone, I'm afraid)
Anyway: Using the FRX03 build from
http://forum.xda-developers.com/showthread.php?t=711692
(full package, so using the included rootfs, zimage and modules.)
I can *confirm* that audio still stutters, and also on this build stuttering immediately disappears when battery service is killed!
Hope it helps?
If there's need to test different rootfs/zimage/modules/startup/..., just let me know!
Actually, for me, I just want to disable battery service so I can listen to music on my 15min bike ride to work!
But I am a linux Noob, so although "kill -9" is in my power to stop the service, actually restarting a service is momentarily out of reach...
Any help with restarting the [battery] service would be greatly appreciated!
Cheers,
Robbert
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
You don't need to compile a kernel tbh, why don't you just create an init script which includes the "kill -9 28" command? The init script will get launched on startup therefore killing the battery service as desired.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Hi, Stickman89,
Yes, I read this also somewhere, thanks for reminding me!
My bigger wish is to be able to restart the battery service after finishing listening to music, not having to restart Android (and first WinMo) because that takes way too much time.
How do I restart the service, any idea?
Cheers,
Robbert
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
well to do that you would need to install a mobile terminal app from the market and create two scripts, one to disable the service and the other to enable it. Only problem is this would not be automated and you would need to execute the script via the terminal app installed.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
I could live with that (still hoping for a proper fix, of course!)
Most builds come with a terminal app (Busybox is popular, if I remember correctly) that's what you mean?
But still I need the command line / script lines to execute, and that's where I'm stuck, since I know how to kill the service from the prompt of my terminal in the phone, but not how to "unkill" it!
"Disable/enable" sounds much better than "kill/unkill", but how???
As a side note, I also get the impression that the android terminal does not give me full access to a shell environment, since, for example, the "ps" command is severely limited! (wanted to find out more information on process "[battery]", but no chance with the crippled "ps" command...)
Maybe there are better (more functional) terminals out there?
Or do we actaully have access to "enable/disable service" commands in this "busybox" and I just don't know the proper command?
(just for reference: I'm running Kenia's eclair build that includes busybox 1.5 as terminal)
Cheers, Robbert
Even better, look what I just found for you: http://forum.xda-developers.com/showthread.php?t=486486
Basically you can create a homescreen icon and assign a shell command to it, simply create an icon and assign the "kill -9 28" command to it which will kill the battery service, I would have to check out the process name to be able to start it again. Let me take a look for you (I don't think "start -9 28" will work as we have only issued the process ID and since it is no longer running will be useless)
Best Regards,
ST1Cl<^^aN
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Code:
# ps
ps
PID USER VSZ STAT COMMAND
1 0 312 S /init.android
2 0 0 SW [kthreadd]
3 0 0 SW [ksoftirqd/0]
4 0 0 SW [watchdog/0]
5 0 0 SW [events/0]
6 0 0 SW [khelper]
7 0 0 SW [suspend]
8 0 0 SW [kblockd/0]
9 0 0 SW [cqueue]
10 0 0 SW [kmmcd]
11 0 0 SW [btaddconn]
12 0 0 SW [btdelconn]
13 0 0 SW [kondemand/0]
14 0 0 SW [smd_tty]
15 0 0 DW [rpcrouter]
16 0 0 SW [kadspd]
17 0 0 SW [detection/0]
18 0 0 SW [button/0]
21 0 0 SW [kswapd0]
22 0 0 SW [aio/0]
23 0 0 SW [panel_on/0]
24 0 0 SW [tty_wq/0]
25 0 0 SW [usb_mass_storag]
26 0 0 SW [kstriped]
27 0 0 SW< [krfcommd]
28 0 0 SW [krpcserversd]
29 0 0 DW [battery]
54 0 0 SW [mmcqd]
71 0 0 SW< [loop2]
90 0 0 SW< [loop0]
94 0 0 SW< [loop1]
133 0 1736 S busybox telnetd -b 192.168.20.1 -l /bin/sh
1168 0 1740 S /bin/sh /bin/userinit.sh -c /sdcard/conf/froyo.user.
1226 0 1740 S /bin/sh
1227 1000 812 S /system/bin/servicemanager
1228 0 3728 S /system/bin/vold
1229 0 1736 S /bin/sh /bin/netd
1231 0 668 S /system/bin/debuggerd
1232 1001 5464 S /system/bin/rild -l /lib/froyo/libhtcgeneric-ril.so
1233 0 87964 S zygote /bin/app_process -Xzygote /system/bin --zygot
1234 1013 26664 S < /system/bin/mediaserver
1238 1002 1260 S /system/bin/dbus-daemon --system --nofork
1239 0 824 S /system/bin/installd
1240 1017 1612 S /system/bin/keystore /data/misc/keystore
1241 0 3340 R /sbin/adbd
1243 0 3720 S /system/bin/netd
1258 1000 246m S system_server
1330 10054 124m S com.swype.android.inputmethod
1345 10011 129m S N com.google.process.gapps
1434 1001 134m S < com.android.phone
1685 1000 123m S com.android.settings
2847 0 0 DW [audmgr_rpc]
3391 0 0 DW [ksdiorqd]
3392 0 0 SW [tiwlan_wifi_wq]
3400 1010 3004 S /system/bin/wpa_supplicant -Dtiwlan0 -itiwlan0 -c/da
3588 10007 107m S com.android.quicksearchbox
4937 10053 159m S android.process.acore
5076 10058 108m S com.appspot.swisscodemonkeys.apps
5083 10023 105m S com.android.voicedialer
5095 10004 110m S com.android.vending
5106 10026 114m S com.google.android.googlequicksearchbox
5113 10002 126m S android.process.acore
5233 10037 105m S com.android.defcontainer
5243 10030 112m S com.google.android.apps.genie.geniewidget
5273 10010 111m S < android.process.media
5284 10014 114m S com.google.android.gm
5338 0 0 SW [pdflush]
5462 10064 106m S mobi.infolife.taskmanager
5524 0 0 SW [pdflush]
5532 10070 123m S stericson.busybox
5584 10061 115m S com.facebook.katana
5631 0 1736 S sleep 500
5635 10059 114m S cn.miren.browser
5662 0 740 S /system/bin/sh -
5665 10060 122m S com.voxmobili.phonebook2
5691 10056 108m S com.miui.player
5697 10028 108m S com.google.android.apps.uploader
5705 0 1740 R ps
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "command-removed".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "command-removed" (remember that the PID number may vary so please check) to start the service again.
FYI charging will stop at this point and battery stats will freeze at there current percentage.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok here are the processes running, PID 28 is krpcserversd, interestingly we also have the PID 29 which is battery.
Click to expand...
Click to collapse
Same here for me: PID is 29 (it may different in some builds) but... when I killed battery service (kill -9 29) audio shuttering stopped. It also solved "audpp: DMA missed" messages in dmesg so maybe we're on the right track.
IMHO killing battery service every time is not a solution. Maybe code just needs to be cleaned up a little.
Anyway, for now kill -9 is the only (known) way to achieve smooth playback.
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
Ok then all we need to do is adjust the scheduling priority until we find the sweet spot via renice
That way we wouldn't need to kill anything and that can be added to init fairly easy, we would have to test some values first.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Tried that already, afraid it might not be so easy...
Gave the audiomanager -20 or so, and the battery service +20 or so, no effect, still stuttering...
But maybe your mileage may vary, did you try this on your build?
Cheers,
Robbert
Stickman89 said:
If you have a working adb setup then type: "adb shell ps -w"
or download a mobile terminal and type: "ps -w"
Ok here are the processes running, PID 28 is krpcserversd in our case which is incorrect so we need to look for the battery service which is PID 29 for me.
Click to expand...
Click to collapse
Also for me, number 29 it is.
Stickman89 said:
Once the battery service has been located so in my case PID 29 then to kill that PID via adb simply issue "adb shell kill 29" (PID number may vary so please check) and to start the PID issue "--locating-process--".
So if you want to use the application i linked you to over at the G1 thread then simply assign the commands "kill 29" to kill the service and "--locating-process--" (remember that the PID number may vary so please check) to start the service again.
Click to expand...
Click to collapse
Huh?
Something must have gotten "lost in translation" here, I have really no idea what is meant by the command "--locating-process--", I guess it's not literally typing in this phrase, what am I missing?
Ah, just noticed your statement in an earlier post "I would have to check out the process name to be able to start it again", I guess that's what you meant by "--locating-process--" in the next post...?
Well, to be continued...
Cheers,
Robbert
The service isn't successfully starting after being killed, I initially thought it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Stickman89 said:
The service isn't successfully starting after being killed, I initially though it had but it appears it failed to kill on first try therefore it was still running. I will keep looking into this though, stuttering isn't that bad on my build. I will upload it soon, it is there but isn't too bad.
Best Regards,
ST1Cl<^^aN
Click to expand...
Click to collapse
Yeah, noticed that too, sometimes the service takes a few seconds to unload (or at least "ps" still shows it.)
Maybe someone else has some bright ideas, posted it also at Neopeek, some good guys over there, too
I just hoped someone had a quick solution, but we may have to wait for some more kernel development. I'll keep my eyes open, if something pops up I'll update.
Cheers,
Robbert
May I ask what application you guys are using to kill the process? I downloaded the terminal emulator app, however when I type "kill 29" it says operation not allowed.
I'm assuming this is because of a rights issue. I am using Android 2.2 (FroYo) by the Brilliant Mistake [03 Sep 2010] (V1.6) with the latest kernel, zimage, rootfs along with FRX03 update.
I'm a bit confuse as to how I can "root" my device in order kill the battery process so I too can listen to my music without the annoying stuttering.
Any info would be appreciated. Thanks
Just type "su" first
g3rm0 said:
Just type "su" first
Click to expand...
Click to collapse
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
James62370 said:
Thank you for your reply.
I type "su" then enter...
I get a "#" prompt
then I type "kill 29" enter
I don't get any type of confirmation just another "#" prompt
I try listening to my music, stuttering is still there... What am I doing wrong?
Click to expand...
Click to collapse
"kill -9 29" has a better chance
Did you check before killing it, that [battery] is process 29 for you? (use "ps" command in shell)
Did you check afterwards that process 29 [battery] is indeed gone?
Just wait for viruscrazy submit the patch to phh to be merge in the main tree.It already in Jerome tree HERE
Code:
/* Patch to fix "audpp DMA missed" messages on AMSS version 52.62.25.34 */
1423 if ( machine_is_htcdiamond() || machine_is_htcblackstone() ) {
1424 if( !(snd_state & SND_STATE_PLAYBACK) ) {
1425 dex.cmd = PCOM_GET_BATTERY_DATA;
1426 msm_proc_comm_wince(&dex, 0);
1427 } /* else {
1428 printk("Skipping battery pcom call to avoid audppp DMA miss\n");
1429 } */
1430 }
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Questions go in the Q&A section
CharlyBrok said:
Hi all,
I have a problem with my defy, whitout fall or update the touch screen stop responding.
After some resets & sbf flashing I've noticed that the touch screen is ok only when there is no sdcard.
I've tried over sdcards with no more success.
The sdcard is readable, I can access with adb.
Clockworkmod access the sdcard too.
With sdcard dmesg :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_enq
touch_write: Error while trying to write 2 bytes
qtouch_set_addr: Can't send obp addr 0x 0
qtouch_process_info_block: Cannot read info object block
qtouch_ts_probe:Cannot read info block -121, checking for bootloader mode.
Without sdcard :
qtouch_force_reset: Forcing HW reset
Unable to get gpio pin num for touch_pwr_en
qtouch_process_info_block: Build version is 0x10
qtouch_process_info_block: Object 5 @ 0x00f2 (9) insts 1 rep_ids 0
qtouch_process_info_block: Object 6 @ 0x00fb (6) insts 1 rep_ids 1
qtouch_process_info_block: Object 38 @ 0x0101 (8) insts 1 rep_ids 0
(...)
Can it be a HW problem ?
What do you think I can do ?
Click to expand...
Click to collapse
AFAIK, it is HW related..
Best choice, get it to the SC..
Maybe I'll try to change the digitizer (20€ on ebay).
Warranty period is finish.
I want more log,
The goal is to enable logging debug in qtouch_obp_ts
I put in /system/etc/init.d/77debug
Echo 0xFF > /sys/module/qtouch_obp_ts/parameters/tsdebug
But no change at all...
What I am doing wrong ?
Envoyé depuis mon A500 avec Tapatalk
Hello,
My Axon 7s (the dual cam one) (https://www.gsmarena.com/zte_axon_7s-8658.php) has an overheating issue. The battery melts dows super fast and the phone heats up alot even in standby with no sim card and wi-fi enabled. Factory reset did not helped at all. It is Android 7.1.1, ZTE2018V1.1.0B11. Is there any way to install custom firmware or update the stock one, ore anything else that will help prevent this issue?
Thanks!
no its not possible
It sounds like a bad battery more than a software issue. The Axon 7s does have some comments online saying it overheats frequently however.
If you're comfortable in doing so and your warranty has expired; I would try replacing the battery and maybe even the thermal paste inside.
After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...
Markovo said:
After resetting the phone, the problem disappeared. It was cool for 2-3 hours. Then I logged in my google account, installed Viber and it started heating and draining the battery again. The Phone is 4 months old. Never played games on it. Only Facebook and Viber. I had another Axon 7 (without "s") before with the same problem. Changed the battery 2 times and nothing happened. Still discharges super fast...
Click to expand...
Click to collapse
Had the same problem - in my case MediaServer locked up upon a corrupt MP4 file and utilitzed 1 core at 100% constantly. That caused my phone to overheat. Battery life was terrible.
Try to hook your phone up to your computer and open "ADB shell" and type "top -m 10" - you will see the top 10 processes that cause CPU utilization. If there is a process that hogs your CPU you know where to look closer. I found out that a corrupt MP4 video file was the culprit. After deleting it and a reboot my phone was fixed and felt lie new. Hope that helps...
I used ADB Shell too show the processes.
Here is the result:
Code:
Load: 3.33 / 3.59 / 3.64
CPU usage from 51297ms to 39789ms ago (2020-05-13 12:06:18.533 to 2020-05-13 12:06:30.042):
0.9% 2504/kworker/u8:10: 0% user + 0.9% kernel
0.6% 2599/system_server: 0.2% user + 0.4% kernel / faults: 58 minor
0.5% 53/ksmd: 0% user + 0.5% kernel
0.5% 7125/kworker/u8:11: 0% user + 0.5% kernel
0.5% 8893/kworker/u8:0: 0% user + 0.5% kernel
0.4% 16/ksoftirqd/2: 0% user + 0.4% kernel
0.2% 2426/gx_fpd: 0% user + 0.2% kernel
0.2% 3238/com.android.systemui: 0.2% user + 0% kernel / faults: 7 minor
0.1% 42/smem_native_rpm: 0% user + 0.1% kernel
0.1% 2963/thermal-engine: 0.1% user + 0% kernel
0.1% 6642/com.google.android.webview:s: 0.1% user + 0% kernel
0.1% 7323/kworker/0:2: 0% user + 0.1% kernel
0.1% 7703/kworker/2:5: 0% user + 0.1% kernel
0% 20/ksoftirqd/3: 0% user + 0% kernel
0% 34/kworker/0:1: 0% user + 0% kernel
0% 348/cfinteractive: 0% user + 0% kernel
0% 464/servicemanager: 0% user + 0% kernel / faults: 1 minor
0% 614/[email protected]: 0% user + 0% kernel
0% 635/healthd: 0% user + 0% kernel
0% 3390/com.android.phone: 0% user + 0% kernel / faults: 4 minor
0% 7695/kworker/3:4: 0% user + 0% kernel
0% 8940/kworker/2:1: 0% user + 0% kernel
1.3% TOTAL: 0.1% user + 0.8% kernel + 0% iowait + 0.3% irq + 0.1% softirq
Code:
[H[JTasks: 580 total, 1 running, 573 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3633324k used, 227632k free, 117192k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 2%user 1%nice 7%sys 390%idle 0%iow 0%irq 0%sirq 0%host
[7m PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS [0m
2551 system 18 -2 2.5G 284M 186M S 5.0 7.5 0:26.34 system_server
6370 shell 20 0 11M 3.0M 1.7M R 4.0 0.0 0:01.31 top -n 10
6068 root 20 0 0 0 0 S 0.6 0.0 0:00.21 [kworker/u8:12]
464 logd 30 10 24M 4.6M 1.4M S 0.6 0.1 0:03.44 logd
347 root RT 0 0 0 0 S 0.6 0.0 0:01.27 [cfinteractive]
895 root 20 0 0 0 0 S 0.3 0.0 0:01.05 [kworker/u8:10]
622 system RT 0 86M 3.3M 2.3M S 0.3 0.0 0:01.36 android.hardwar+
287 root 20 0 0 0 0 S 0.3 0.0 0:00.26 [kworker/u8:9]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.40 [ksmd]
47 root RT 0 0 0 0 S 0.3 0.0 0:00.55 [irq/263-cpr3]
6354 shell 20 0 13M 1.0M 776K S 0.0 0.0 0:00.04 adbd --root_sec+
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.79 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.54 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
[?25h[0m[1000;1H[K[?25h[0m[1000;1H[K0.0 0.0 0:00.00 [kworker/u8:14]
Code:
[H[JTasks: 577 total, 1 running, 570 sleeping, 0 stopped, 2 zombie
Mem: 3860956k total, 3630552k used, 230404k free, 117216k buffers
Swap: 1048572k total, 0k used, 1048572k free, 1886212k cached
400%cpu 1%user 0%nice 4%sys 395%idle 0%iow 0%irq 0%sirq 0%host
[7m PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS [0m
6385 shell 20 0 11M 3.0M 1.7M R 4.3 0.0 0:00.63 top -n 10
6354 shell 20 0 13M 0.9M 788K S 0.3 0.0 0:00.06 adbd --root_sec+
6068 root 20 0 0 0 0 S 0.3 0.0 0:00.60 [kworker/u8:12]
622 system RT 0 86M 3.2M 2.3M S 0.3 0.0 0:01.72 android.hardwar+
347 root RT 0 0 0 0 S 0.3 0.0 0:01.38 [cfinteractive]
54 root 25 5 0 0 0 S 0.3 0.0 0:00.67 [ksmd]
12 root 20 0 0 0 0 S 0.3 0.0 0:00.66 [ksoftirqd/1]
7 root 20 0 0 0 0 S 0.3 0.0 0:01.33 [rcu_preempt]
6194 system 20 0 2.1G 39M 19M S 0.0 1.0 0:00.06 com.zte.emode
6132 u0_a30 20 0 2.1G 59M 34M S 0.0 1.5 0:01.81 com.android.mms
6128 root RT 0 0 0 0 D 0.0 0.0 0:00.65 [mdss_fb0]
6120 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/3:5]
6104 system 20 0 2.1G 43M 23M S 0.0 1.1 0:00.11 zte.com.cn.alar+
6087 u0_a115 20 0 2.1G 38M 18M S 0.0 1.0 0:00.10 com.qualcomm.ti+
6077 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:16]
6076 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:15]
6075 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:14]
6069 root 20 0 0 0 0 S 0.0 0.0 0:00.16 [kworker/u8:13]
6066 root 20 0 0 0 0 S 0.0 0.0 0:00.00 [kworker/u8:11]
6045 root 20 0 0 0 0 S 0.0 0.0 0:00.02 [kworker/1:5]
It seems alright to me...
Morning all.
I'm trying to debug and restore a Mi TV stick that is stuck in a boot loop. It happened after I switched it on, its video got stuck in xiaomi logo, and after power cycling it never worked again.
The LED doesn't switch on and have no video signal on the hdmi, so I disassembled it and connected to its serial port pins and saw the following trace, in loop:
Code:
GXL:BL1:9ac50e:bb16dc;FEAT:BDFD71BC:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;0.0;CHK:5E6;READ:0;0.0;0.0;CHK:0;
TE: 444948
BL2 Built : 10:47:30, Jan 14 2019. gxl g152d217 - [email protected]
set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 7
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - FAIL
DDR3 chl: Rank0 @ 912MHz - FAIL
DDR3 chl: Rank0 16bit @ 912MHz - FAIL
DDR4 chl: Rank0+1 @ 912MHz - FAIL
DDR4 chl: Rank0 @ 912MHz
bist_test rank: 0 21 03 40 2b 12 44 1f 02 3d 32 1a 4a 20 00 40 2b 14 43 26 08 45 27 0d 41 660 - PASS
Rank0: 1024MB(auto)-2T-18
AddrBus test pass!
eMMC boot @ 1
sw8 s
emmc switch 3 ok
BL2: rpmb counter: 0x00000020
emmc switch 1 ok
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 1
aml log : R1024 check pass!
New fip structure!
Load bl30 from eMMC, src: 0x00010200, des: 0x01700000, size: 0x0000d600, part: 1
aml log : R1024 check pass!
Load bl31 from eMMC, src: 0x00020200, des: 0x01700000, size: 0x0002b400, part: 1
aml log : R1024 check pass!
aml log : SIG CHK : 231 for address 0x01700000
Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000, part: 2
emmc switch 2 ok
I assume that perhaps when I power cycled it was updating and its emmc got corrupted?
Is their a way of reflashing the firmware on these devices? I've seen this post here at XDA but wasn't able to enter in USB mode as described. I was able to find the 2 pins but after shorting them nothing happens.
Any tips on how to recover this device?
Thank you!
Did you try to change the charger and/or the cable?