Related
After restore to original stock 6.2.2 from TWRP, my KF is stucked in Kindle Fire logo. ADB on but always face exec system/bin/sh failed so I already made factory cable and put KF into fastboot successfully.
I tried to install TWRP again successfully but when I tried to upgrade FFF to latest version by running
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
I got the message FAILED, partition does not exist.
To make clear my partition is ok or not, I repeated TWRP installation and let it stay in Install Complete phase to go to recovery with ADB.
I run the command
Code:
adb shell
~# parted /dev/block/mmcblk0
And the result is
Code:
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted)
next I enter
Code:
print
but nothing happen and it seem that print command stuck.
Anyone please kindly advise what I should do next in order to recover my bricked KF ? Thank you very much
maybe this helps:
http://forum.xda-developers.com/showpost.php?p=22401099&postcount=2
follow the links also ...
good luck !
Thank you for your advice, I tried to follow the link and tried to run
Code:
fastboot -i 0x1949 boot bootloader u-boot.bin
I get failed, cannot load bootloader
but if I run
Code:
fastboot -i 0x1949 boot u-boot.bin
The result is
Code:
C:\kfu\tools>fastboot -i 0x1949 boot u-boot.bin
creating boot image...
creating boot image - 219136 bytes
downloading 'boot.img'... OKAY [ 0.128s]
booting... OKAY [ 0.000s]
finished. total time: 0.128s
And when I tried to run oem format, it stuck.
Code:
C:\kfu\tools>fastboot -i 0x1949 oem format
...
I have no experience how long the re-partitioning takes, still wonder whether cancel this command or let it run T_T
would try the format command without -i 0x1949
the initialization is'nt needed with u-boot.bin ver.1.2 and the command is'nt designed to work with initialization
I tried to run command but failed. <waiting device>
you have allready the hot booted fff loaded ?
give -i 0x18d1 a try at the format command
bradys had a simmilar problem:
http://forum.xda-developers.com/showthread.php?t=1369405&page=10
follow the next 2 sites ...
hope this helps
you have allready the hot booted fff loaded ?
Click to expand...
Click to collapse
I guess not because fastboot -i 0x1949 boot bootloader u-boot.bin did not work and fastboot -i 0x1949 boot u-boot.bin either because after that command finishs, the fastboot oem format return <waiting device>, it means that fff 1.2 is not loaded successfully.
give -i 0x18d1 a try at the format command
Click to expand...
Click to collapse
tried but <waiting device>
bradys had a simmilar problem:
http://forum.xda-developers.com/show...369405&page=10
follow the next 2 sites ...
hope this helps
Click to expand...
Click to collapse
Thank you for your prompt support.
Not really, the symtoms are similar but in his case, the partition table still able to read but mine couldn't be. And he also has chance to rebuild partition mannually but I do not; I cannot run parted /dev/block/mmcblk0, this command return nothing as i mentioned above. T_T
yeutinh said:
I guess not because fastboot -i 0x1949 boot bootloader u-boot.bin did not work and fastboot -i 0x1949 boot u-boot.bin either because after that command finishs, the fastboot oem format return <waiting device>, it means that fff 1.2 is not loaded successfully.
Click to expand...
Click to collapse
your right about that - have also read it in an other thread - loads but don't reload itself
are you able to issue mklabel, mkpart and the other commands like here:
http://forum.xda-developers.com/showpost.php?p=20880465&postcount=58
maybe give eldarerathis a pm - he's the guru on partitioning:
http://forum.xda-developers.com/member.php?u=2676559
are you able to issue mklabel, mkpart and the other commands like here:
http://forum.xda-developers.com/show...5&postcount=58
Click to expand...
Click to collapse
Tried but failed, command stuck
maybe give eldarerathis a pm - he's the guru on partitioning:
http://forum.xda-developers.com/member.php?u=2676559
Click to expand...
Click to collapse
Thanks for advice, already PM him.
Code:
cat /proc/partitions
major minor #blocks name
179 0 7553024 mmcblk0
All partitions gone T_T
Got your PM. I haven't seen anything quite like this before, so all I can really do is take something of an educated guess here. What it looks like may have happened is that the partition table got corrupted or erased, so parted can't read the partition list (again, just a bit of a guess).
Try doing this and post the output that you see:
Boot into recovery
Use adb shell to connect to your Fire
Run "fdisk -l /dev/block/mmcblk0" (that's a lowercase "L")
If (3) doesn't seem to work, try "fdisk /dev/block/mmcblk0". It should give you a little prompt kind of like parted does. Type "p" and hit enter at the fdisk prompt (then use "q" to quit).
If fdisk gives you something sane then your partition table is okay. If it blows up or throws back an error then it's toast, but you might be able to use fdisk to create a new (blank) partition table and then re-create the correct partition layout. Either way, it should get you some more information about what's actually going on with your disk.
Thank you for your support, I appreciate that
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
fdisk: can't open '/dev/block/mmcblk0': I/O error
~ # fdisk /dev/block/mmcblk0
fdisk /dev/block/mmcblk0
fdisk: can't read from /dev/block/mmcblk0
it means the filesystem on eMMC was accidentally broken down, correct ? But I wonder what make FS down because I did not do anything that impact to partitions, I think
and when I run mount, the result is
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
Click to expand...
Click to collapse
Already checked whether eMMC dead or alive http://forum.xda-developers.com/showpost.php?p=13895268&postcount=48
Code:
~ # cat /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/name
cat /sys/devices/platform/mmci-omap-hs.1/mmc_host/mmc0/mmc0:0001/name
M8G2FA
Returned name of eMMC
Code:
~ # cat /proc/kmsg | grep mmc0
cat /proc/kmsg | grep mmc0
<6>[ 2.438171] mmc0: new high speed DDR MMC card at address 0001
<6>[ 2.456115] mmcblk0: mmc0:0001 M8G2FA 7.20 GiB
it means that my chip still alive Need your help to clear the messed FS
The I/O error from fdisk is concerning, and kind of makes it sound like the hardware up and died somehow. I was thinking you might be able to use fdisk to create a blank MSDOS partition table, then use parted to switch it to a GPT one (the Fire uses GPT and fdisk doesn't support that), but if it can't even read the disk then that won't work. The fact that FFF's 'fastboot oem format' isn't working also kind of lends to the hardware possibility, but I don't know exactly how it performs the format (you could try PM'ing pokey9000 and see if he'll explain it to you, maybe).
To be honest, I don't think I've seen a lot of recovery options for this sort of thing. The only stuff I can think of are all kind of Linux-geared, and Android is unfortunately lacking in some of the tools that it has available. For instance, one option on a Linux box would be to attempt to zero out the whole disk and then try to re-create everything, but I don't know how you'd handle things like the MBR on Android (or if you even need to). It still may be a possibility, but I have no idea if it would work and your data would all be lost. Worst case you'd end up with a permanently unbootable drive if the MBR/partition table are zeroed out and you can't re-create them, but I guess that's kind of what you have now, in't it?
I think you are right T_T. Will look for workaround solution if any and after that will return to Amazon T_T
You might as well try it.
dd if=/dev/zero of=/dev/block/mmcblk0
Immediately flash a complete system image after this (complete with everything from xloader to media).
If this command says can't open '/dev/block/mmcblk0': I/O error, the chip is probably toast. Unless it's some silly partition abstraction layer caused by twrp or something, in which case you can try to flash a cwm image via fastboot...
If even that fails, you can try to pin-mod that flash -- resetting it. But opening your kindle is probably the last thing you'd want to do if you have the chance to return it, heheh...
I tried dd command already, it returned I/O error also.
Will consider pin-mod method, but could you pls advise more details hehe. It's better than return it to Amazon
This afternoon I tried to play with KF again. I put it to recovery and
Code:
~ # echo /dev/block/mmcblk0 > /sys/dev/devices/platform/usb_mass_storage/lun0/file
echo /dev/block/mmcblk0 > /sys/dev/devices/platform/usb_mass_storage/lun0/fi
le
And come back to Windows to check whether OS can detect the usb_mass_storage of KF.
And when I open HP USB Format Tool, it can detect the usb_mass_storage of KF as Amazon Kindle Fire 0001 (7376MB). I tried to format it but the error return that write protected device. Anyone can explain me what is the problem of my eMMC ?
And when using with GParted
Device information : Amazon Kindle
Size: 7.2 GiB
Path: /dev/sdb
Partition Table: msdos
Head 255
Sectors/track 63
Cylinders 940
Total sector 15106048
Sector size 512
Click to expand...
Click to collapse
what about mk2fs command via adb shell?
my mke2fs /dev/block/mmcblk0p11 brings to mk2fs: short write - what it could be?
Did you fix it yet? If fix, please intro for me. I have problem the same.
a similar problem, someone has already solved it?
Project thread created..
http://forum.xda-developers.com/showthread.php?t=2627255
install-or-mount-v0.8-gui.zip
Use this thread for help
Device List
Change Log
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
ONDR4SH3K said:
Sony Xperia P - CM11 4.4.2
Error with
Code:
handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
Needed another command.
Click to expand...
Click to collapse
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
userdelroot said:
I figured that was gonna be an issue.
There are so many variants when it comes to device / busybox, I tried to get around that by including my own binary but fail on my part i guess...
Anyways.
Fix this line
Code:
LINE: 310 handle_error mke2fs -qF -t $fs_type $IMGLOC/$IMGNAME
to
Code:
handle_error mk2fs.ext2 $IMGLOC/$IMGNAME
Click to expand...
Click to collapse
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
ONDR4SH3K said:
I rewrite with mke2fs -F $IMGLOC/$IMGNAME this working well.
But another problem with debootstrap. See attachment. So it's end of testing, isn't it?
Click to expand...
Click to collapse
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
Click to expand...
Click to collapse
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
ONDR4SH3K said:
Yes, it print Linux. I try another deboostrap. You use VERSION='1.0.40~ubuntu0.4'. So I find new one.
EDIT: New debootstrap with the same error.
Click to expand...
Click to collapse
Yea, it has to do with the line above I believe.
userdelroot said:
hmm...
I had that error initially also and I corrected it, probably should of documented what I fixed...
in the terminal type
uname
Is that a valid command?
change install-or-mount
Code:
LINE :333 handle_error debootstrap --no-check-gpg --extractor=ar --arch=armhf --foreign $DIST $MOUNT $MIRROR
to
Code:
handle_error debootstrap --no-check-gpg --extractor=ar --arch armhf --foreign $DIST $MOUNT $MIRROR
Click to expand...
Click to collapse
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
ONDR4SH3K said:
Sry, not working, but I deleted line with checking architecture and I got new error. See attachment.
EDIT:
I use:
sh install-or-mount -i -n linux.img -m /data/local/chroot -l /data/local -o precise -0
Rewrited mk2fs line in install-or-mount file to: mke2fs -F $IMGLOC/$IMGNAME
Deleted if [ -z "$ARCH" ] || [ -z "$HOST_OS" ]; then error 1 WHATARCH "Couldn't work out current architecture" fi line in deboostrap file
I think if I deleted this line, chroot not mounted correctly and bootstrap can't continue. So we need figure out, how fix architecture error.
I found this: http://uyirpodiru.blogspot.cz/2012/08/debootstrap-error-e-couldnt-work-out.html
Click to expand...
Click to collapse
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
userdelroot said:
All the errors you are getting I did get at one point, I forgot how I fixed them, cause I was working on another project..
Ill do some testing, as I am working on the code right now.
Ill post when I find a solution to those..
Also before continuing I wanted to just let you know.
the debootstrap requires 'ar' archiver which I do not believe comes with CM.
busybox ar
That is why I included my own version.
I may have some work arounds tho so give me a few..
Click to expand...
Click to collapse
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
is it normall ubuntu for desktop or Ubuntu phone version?
desktop
JFizDaWiz said:
desktop
Click to expand...
Click to collapse
I'm confused
Does touch work? Or do we need OTG cables
milestoneman said:
I'm confused
Does touch work? Or do we need OTG cables
Click to expand...
Click to collapse
You need root, and an android device.
No OTG cables..
It build's a chroot image on the device, with android running in the background.
You can run X windows (only LXDE currently because it is lightwieght) on the device and then vnc into it from anywhere, even a desktop...
There are other tools out there for this however, they require you to download the images. Which are usually between 1gig - 4gigs.
Instead of downloading the images, this creates the image and only downloads approximately 200megs for the packages.
Thanks for the explanation, sounds great
Sent from my Nexus 7 using Tapatalk
ONDR4SH3K said:
New vesion 0.2 in attachment. Is on the way.
EDIT: I put busybox from /sbin to /system/xbin and it looks like deboostrap working, but you have error with Release. Attachment no.3.
Thanks for helping.
Click to expand...
Click to collapse
Yea, crap, that was my bad, I should check where the system busybox is installed. It should default to /system/xbin
But some roms I guess put it in /system/sbin ? Possibly a typo on the rom developers part? LOL
Anyways, I will add code to correct this.
EDIT: How did you fix image 2?, as it should stop at the error in image type every time.
At any rate, image 2 error is because it can't find sh. in the install-or-mount/bin directory type this..
ls -l bin/
Make sure sh is symlinked to /system/bin/sh or /system/xbin/busybox if not that is causing the error in picture 2
it should look like this...
ls -l bin/
sh sh -> /system/xbin/busybox
If you don't see that do the following:
cd /data/local/install-or-mount
busybox touch bin-configs/sh
rm -rf .bin-configs-done
if you have something like that it should be ok, however to be safe since you moved you your busybox
from inside install-or-mount
rm -rf .bin-configs-done
Yes there is a DOT in front of bin-configs-done
I receive a permission denied error with debootstrap as well
Edit: crap I didn't see all the replies up there
Sent from my GT-N7105 using Tapatalk
Will it works on my armv7 single core tablet?
I fix it other way:
mount -o remount,rw /system
cp busybox /sbin /system/xbin
mount -o remount,ro /system
I hope that commands are fine.
I has no solution for fetch Release error, yet. I tried rewrite URL, but unsussesful.
Its in scripts folder line mirror_styles Release
Sent from my Xperia P using xda app-developers app
---------- Post added at 01:06 AM ---------- Previous post was at 01:00 AM ----------
Already testing on armv7 device dual core. OP must fix a few errors but you can try it.
Sent from my Xperia P using xda app-developers app
*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.
@empies
Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?
Shadoworion said:
Recovery must be unlocked? Can I flash it on CM12.1 or must be only Flyme?
Click to expand...
Click to collapse
I found this tutorial on channel official of developing. I care yes just flash the recovery.
Naphtha said:
I found this tutorial on channel official of developing. I care yes just flash the recovery.
Click to expand...
Click to collapse
Can you give me link of this original tutorial? Have you ever tried it?
Shadoworion said:
Can you give me link of this original tutorial? Have you ever tried it?
Click to expand...
Click to collapse
Nope. I can't give you the link. I have an Mx4 32 gb with ubuntu touch, if i flash it is useless
Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.
Danj1 said:
Hi,
my build.prop values are:
ro.product.name=cm_mx4
ro.build.id=LMY48Y
ro.product.device=mx4
Do I have to change these before flashing?
Thanks in advance.
Click to expand...
Click to collapse
yes change it first
Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?
Shadoworion said:
Code:
2015/11/24 18:21:33 Device is |arale|
2015/11/24 18:21:33 Flashing version 7 from ubuntu-touch/stable/meizu.en channel and server https://system-image.ubuntu.com to device arale
/home/david/.cache/ubuntuimages/ubuntu-touch/stable/meizu.en/arale/version-7.tar.xz
/home/david/.cache/ubuntuimages/pool/device-a8a0e27cb5670a0ccb9dacd2b12dc80b2df8fe776235cf9a0f7478ef7aa934a4.tar.xz
at this moment the terminal is in slowdown status. what do I need to do?
Click to expand...
Click to collapse
only, wait
2015/11/24 20:49:43 error pushing: failed to copy '/home/user/.cache/ubuntuimages/pool/device-ABCDEF.tar.xz' to '/cache/recovery//device-ABCDEF.tar.xz': No space left on device
Click to expand...
Click to collapse
Any idea how to get more space. What can safely be deleted?
~ # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 946.3M 128.0K 946.1M 0% /dev
/dev/block/platform/mtk-msdc.0/by-name/cache
106.2M 53.2M 50.8M 51% /cache
Click to expand...
Click to collapse
/cache # du -h
4.0K ./lost+found
53.1M ./recovery
4.0K ./backup/1/_full
4.0K ./backup/1/_delta
12.0K ./backup/1
16.0K ./backup
53.2M .
Click to expand...
Click to collapse
Danj1 said:
Any idea how to get more space. What can safely be deleted?
Click to expand...
Click to collapse
you do wipe? you insert "--wipe"?
Naphtha said:
you do wipe? you insert "--wipe"?
Click to expand...
Click to collapse
The command I used:
ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --wipe
Naphtha said:
*****WARNING!!! All your actions with the phone is at your own risk. The author are not liable. This is just your choice. ******
You need an MX4 Android version and an PC with Ubuntu, phablet-tools and adb-fastboot installed.
$ adb devices
$ adb shell grep ro.product.name /system/build.prop
ro.product.name=arale
$ adb shell grep build.id /system/build.prop
ro.build.id=KOT49H
$ adb shell grep ro.product.device /system/build.prop
ro.product.device=arale
$ ubuntu-device-flash query --device=arale --list-channels
$ wget http://people.canonical.com/~alextu/tangxi/recovery/recovery.img
$ adb reboot-bootloader
$ fastboot flash recovery recovery.img
$ fastboot reboot
From recovery:
$ ubuntu-device-flash touch --device=arale --channel=ubuntu-touch/stable/meizu.en --developer-mode --password=1234 --wipe
You can change you build.prop from another way: Root Browser.
Click to expand...
Click to collapse
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-
bobslesbricoleurs said:
Seriously? You said stupid and you make a tuto exactly same as i said ?? -_-
Click to expand...
Click to collapse
btw it's not same be changed something and he already tried without changing device name etc.
damn WHY always after i brick phone
---------- Post added at 02:47 PM ---------- Previous post was at 02:45 PM ----------
@Naphtha is after ubuntu installation preloader unlocked ?
Partition resize of mx4 for flash ubuntu touch : http://forum.xda-developers.com/meizu-mx/general/meizu-mx4-partitions-table-help-resize-t3256902
Well. This Tuto is not complete, right? No need to re-size or anything?
hi this ways woks ? any issue ?
makakiel said:
hi this ways woks ? any issue ?
Click to expand...
Click to collapse
Nope don't work. If you flash ubuntu touch with this tutorial is full brick.
actualy what is missing ?
I see a other on wit ubuntu desktop this one work ?
Hi! I have a question... How i can relock the bootloader of ze500kl? I use the unofficial unlock, i never use the unlock app for ze500kl.
There is a method for do this?
Thanks in anvance
I am italian.. i can't speak english... Sorry...
Flash this .zip file on TWRP and flash stock recovery on fastboot
*Mod edit: attachment is removed. Please do not provide false solution.
This script below only does a print job, nothing related to relock, I suppose.
#!/sbin/sh
OUTFD=$2
ui_print() {
echo -n -e "ui_print $1\n" > /proc/self/fd/$OUTFD
echo -n -e "ui_print\n" > /proc/self/fd/$OUTFD
}
ui_print "Relock Bootloader..."
dd if=/dev/block/bootdevice/by-name/abootbak of=/dev/block/bootdevice/by-name/aboot
ui_print "Done!"
Click to expand...
Click to collapse
Thanks
Does this work even when you use the official bootloader unlocker from Asus?
EDIT: the answer is yes.
Does anyone know how to disable tcpdump on the latest MIUI 11 rom with out root? It creates quite large log files quite quickly.
The other day, noticed that this guy is doing it:
Code:
system 10516 2161 0 21:58:31 ? 00:00:00 com.huaqin.diaglogger
root 10541 1 1 21:58:31 ? 00:00:05 tcpdump -i any -W 2 -C 2 -s 134 -w /sdcard/MIUI/debug_log/common/tcpdump.pcap
try to disable/uninstall that app and see if that resolves it. In my case made phone run faster..
stormy1777 said:
The other day, noticed that this guy is doing it:
Code:
system 10516 2161 0 21:58:31 ? 00:00:00 com.huaqin.diaglogger
root 10541 1 1 21:58:31 ? 00:00:05 tcpdump -i any -W 2 -C 2 -s 134 -w /sdcard/MIUI/debug_log/common/tcpdump.pcap
try to disable/uninstall that app and see if that resolves it. In my case made phone run faster..
Click to expand...
Click to collapse
Thanks man, I got rid of that but can't shift the finddevice logs and unfortunately you can't uninstall it or the device goes into a bootloop.
not sure what you mean 'shift' the logs, on my device, the com.xiaomi.finddevice is in DISABLED state, and no bootloop, maybe if you UNINSTALL it goes into that loop, then managed to delete the files in that location..