when I used unlocker programme for D600 on Gene, three-color screen turned on when started. Help！
ERROR [300] : INVALID UPDATE TOOL
This error message will appear when you use the incorrect RUU version to upgrade.
already hard reset,but it doesn't work.
what should i do next?
InMTTY I did this as follow:
type: password BsaD5SeoA
Cmd>password BsaD5SeoA
BML_Open errornErr=0x800A0000)
BML_Open errornErr=0x800A0000)
Pass.
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDInit - SD ver1.0
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
CMD55 failed
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDCmd8 Command response time-out. MMC_STAT = 80
SDInit - SD ver1.0
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
SDCmd55 Command response time-out. MMC_STAT = 80
CMD55 failed
BML_Open errornErr=0x800A0000)
GetDeviceCID: Error - InitDecoder
g_cKeyCardSecurityLevel = 0
Type (0x1)(Operation mode flag): cOpModeFlag=(0x0).
Type (0x2)(Back color flag): cBackColorShowFlag=(0x1).
Type (0x5)(Background color value): g_wBColor=(0xC618) (0xC0C0C0).
RUURUN fail
HTCSF
然后Cmd>resetDevice
Invalid command : resetDevice
For a help screen, use command ? or h
Cmd>ResetDevice
重启无效
I am getting similar error message. Kindly let me know if you get any solution.
i think there may be some possible solution to jump directly to os register and /or write the block about device details to remove error. Only geeks / senior memeber can help us.. pary for the solution..
Related
i use this tool http://forum.xda-developers.com/showthread.php?t=2292828
Code:
ECHO is off.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 4d0acb808f8060e968124bfd5362668a7f7f66fd
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
[COLOR="Red"]FAILED (remote: partition does not exist)[/COLOR]
finished. total time: 0.207s
sending 'u-boot' (1024 KB)...
OKAY [ 0.521s]
writing 'u-boot'...
[COLOR="Red"]FAILED (remote: partition does not exist)[/COLOR]
finished. total time: 0.528s
Done
Press any key to continue . . .
gsmxgsm said:
i use this tool http://forum.xda-developers.com/showthread.php?t=2292828
Code:
ECHO is off.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 4d0acb808f8060e968124bfd5362668a7f7f66fd
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.201s]
writing 'x-loader'...
[COLOR="Red"]FAILED (remote: partition does not exist)[/COLOR]
finished. total time: 0.207s
sending 'u-boot' (1024 KB)...
OKAY [ 0.521s]
writing 'u-boot'...
[COLOR="Red"]FAILED (remote: partition does not exist)[/COLOR]
finished. total time: 0.528s
Done
Press any key to continue . . .
Click to expand...
Click to collapse
What happened ?
Sorry to say it but usually "partition doesn't exist" means hardware problem
Lelus said:
What happened ?
Sorry to say it but usually "partition doesn't exist" means hardware problem
Click to expand...
Click to collapse
I have the same issue... in my case, was after I try to create a second partition using an app called Aparted.apk
I need help, pĺiz
Solved?
Hidetsugu said:
I have the same issue... in my case, was after I try to create a second partition using an app called Aparted.apk
I need help, pĺiz
Click to expand...
Click to collapse
I'm with the same problem
Partition does not exists... Anyone solved the problem?
Hidetsugu said:
I have the same issue... in my case, was after I try to create a second partition using an app called Aparted.apk
I need help, pĺiz
Click to expand...
Click to collapse
zanzzinghy said:
I'm with the same problem
Partition does not exists... Anyone solved the problem?
Click to expand...
Click to collapse
Same exact problem, used program called Aparted to create a partition in my SD, ended up formatting my phone .
I get the same error. Just have to find a way to reformat the portion we deleted . P769
Bump .. Found I guy who had the same problem and created a guide on how to fix it, here is a link http://forum.cyanogenmod.com/topic/71825-hard-brick-to-hell-and-back-guide-to-recovery/.... Now if we can just find a way to apply the same method to our LG L9, then maybe we could fix the phone.
Hi guys,
I really hate that my z2 screen is too sensitive and after searching online for ages I didn't find any solution to it, so I started experimenting myself.
Long story short I managed to find a file under /system/usr/idc/max1187x_touchscreen_0.idc
I opened it as text and it seems to have something to do with the touch screen, but I'm not sure what those things are exactly for. Could anyone please give me some advice on this? Thanks!
The content of the file:
# Device Type
touch.deviceType = touchScreen
# Touch Filter
touch.filter.level = 2
touch.filter.path = /system/lib/touchfilter/tftype4.so
touch.filter.tftype4.Enabled = 1
touch.filter.tftype4.AssumedDelayFactorA = -11.71
touch.filter.tftype4.AssumedDelayFactorB = 12.53
touch.filter.tftype4.AssumedDelayFactorC = -0.81
touch.filter.tftype4.MaxSpeed = 0.036
touch.filter.tftype4.PositionFactorA = 0.2
touch.filter.tftype4.PStablePositionFactor = 0
touch.filter.tftype4.DirectivePriorityFactor = 0.95
touch.filter.tftype4.LatestSpeedWeight = 0.9
touch.filter.tftype4.GapResolver = 0.8
touch.filter.tftype4.OrgSize = 8
touch.filter.tftype4.AccSize = 8
touch.filter.tftype4.AddInitialAcc = 1
touch.filter.tftype4.DefaultInitialAcc = 0
touch.filter.tftype4.DragRangeSize = 3
touch.filter.tftype4.NoAccDistanceMin = 15.0
touch.filter.tftype4.NoAccDistanceMax = 580.0
touch.filter.tftype4.NoAccRate = 0.3
# Glove Mode
touch.gloveMode.deflatePressure = 1
pointercontroller.touch1.filename = /system/somc/touch/images/big_touch.png
pointercontroller.touch1.hotSpotX = 310
pointercontroller.touch1.hotSpotY = 310
pointercontroller.touchsplash1.filename = /system/somc/touch/images/splash.png
pointercontroller.touchsplash1.hotSpotX = 40
pointercontroller.touchsplash1.hotSpotY = 40
Sent from my D6503 using XDA Free mobile app
Q&A for [FASTBOOT][RECOVERY] omap4boot for P940
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
milaq said:
1.3 - Initial release
Click to expand...
Click to collapse
The file seems to be unavailable.
Milaq can you do something about that?
Thanks
Hi Milaq, the omap4tool seems to be unavailable for download. Can you help me with that?
Thanks
Still Stuck in < waiting for device >
I have done this step a lot of times, but it stays stuck in:
--------------------------------------------
OMAP4boot for P940/SU540
--------------------------------------------
by wkpark <[email protected]>
modified by milaq <[email protected]>
[1] p940 - Prada 3.0 (P940)
[2] su540 - Prada 3.0 for asian market (SU540/KU5400)
[x] exit
-------------------------------------------
Select your device: 1
p940 selected
****** plug in usb with the phone powered off and the battery NOT inserted ****
**
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 86fc18680b8fc8c812852decc918bcd922c5fcd3
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
****** insert battery NOW ******
looking for attached fastboot devices...
===============================
===============================
is your phone displaying the lg logo (fastboot v0.5) and did your device show up
above? (Y/n) ?y
do you want to flash a custom recovery? (y/N) ?y
****************************
< waiting for device >
Did you do samoething diferent to pass this?
Hello xda,
tldr: i can only use fastboot right now, what do i flash to get a working recovery/sw upgrade mode/rom/something?
I got a LG P760 a year ago from a friend to have as backup phone and I tried then to root and put a custom rom but something went wrong and got the security error. After some more tries with fastboot the phone wouldn't even turn on so i gave up on it.
Now my main phone died and i wanted to fix and use this lg for a while but i can't seem to get anywhere after many many hours of trying.
As i said in title there's nothing appearing on screen at any point, no recovery, no lg logo, no fastboot text (as i've seen in some screenshot around here), no sw upgrade screen. The most i got out of it was the back/menu buttons to light up when using the omap4boot with option "[2] p920 - Optimus 3D (P920)" from here.
The only consistent answer i get is when using omap4boot with option " [3] p940 - Prada 3.0 (P940)": i can see my device for about 5-10 mins in fastboot devices list and can flash stuff with it.
Code:
//fastboot devices correct:
C:\omap4boot>start_fastboot.bat
--------------------------------------------
OMAP4boot for P920/P720/SU540/SU760/SU870
--------------------------------------------
by wkpark at gmail dot com
[1] cx2 - Optimus 3D Cube (SU870/P720)
[2] p920 - Optimus 3D (P920)
[3] p940 - Prada 3.0 (P940)
[4] su540 - Prada 3.0 (SU540/KU5400)
[5] su760 - Optimus 3D (SU760)
[x] exit
-------------------------------------------
Select device and <ENTER> 3
p940 selected
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 211795482064db2dd4c70281fb39c14018973f30
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-seconds...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
------------------------------
Please remove USB cable
and wait until LG Logo on
then reconnent USB cable again
------------------------------
fastboot devices (y/N) ? and press <ENTER> n
ls: resigned/p940-MLO*.bin: No such file or directory
Do you want to replace u-boot (y/N) ?n
ls: cwm/p940-*.img: No such file or directory
Press any key to continue . . .
01608CBF0800A01E fastboot
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\omap4boot>
C:\omap4boot>fastboot devices
01608CBF0800A01E fastboot
C:\omap4boot>
Using the lelus's fastboot zip i can get as far as sending "u-boot", where it freezes both on option "2. P760 - Flash ICS xloader and uboot" and "6. P760 - Flash JB xloader and uboot (p765 and p768 compatible)":
Code:
//lelus fastboot for p760:
//option 2
ECHO is off.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 211795482064db2dd4c70281fb39c14018973f30
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.199s]
writing 'x-loader'...
OKAY [ 2.840s]
finished. total time: 3.040s
sending 'u-boot' (1024 KB)...
//after 2 mins i disconnect phone
FAILED (status read failed (Too many links))
finished. total time: 114.895s
Done
Press any key to continue . . .
///option 6
ECHO is off.
Plug USB cable
wait 4 seconds and put battery back in.
waiting for OMAP44xx device...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
reading ASIC ID
usb_write 4
usb_read 81
[*] read 0 bytes
NumOfSubblocks: 0x5
Subblock ID: 0x1
Subblock Size: 0x5
CH enabled: 0x7
ROM revision: 0x4
Checksum Subblock: 0x15
CHIP: 4430
IDEN: 211795482064db2dd4c70281fb39c14018973f30
MPKH: 5f4092eccddf90fa43f546adf89508b31b9c74795e9516194c0ea6412fdcb7f6
CRC0: 9c669ad9
CRC1: 682adccf
sending 2ndstage to target... f0030002
usb_write 4
usb_write 4
wait 5-lelelel...
[*] msg size = 4
usb_write 21552
[*] data size = 21552
usb_close
Reopen usb...
Device descriptor:
bLength = 18
bDescriptorType = 1
bcdUSB = 528
bDeviceClass = 255
bDeviceSubClass = 255
bDeviceProtocol = 255
bMaxPacketSize0 = 64
idVendor = 451
idProduct = D00F
bcdDevice = 0
iManufacturer = 33
iProduct = 37
iSerialNumber = 0
bNumConfigurations = 1
waiting for 2ndstage response...
usb_read 4
usb read = aabbccdd
accepted 2ndstage response
sending image to target...
size = 246272
usb_write 4
usb_write 246272
** Done **
< waiting for device >
sending 'x-loader' (384 KB)...
OKAY [ 0.200s]
writing 'x-loader'...
OKAY [ 2.840s]
finished. total time: 3.041s
sending 'u-boot' (1024 KB)...
FAILED (status read failed (Too many links))
finished. total time: 49.719s
Done
Press any key to continue . . .
So right now i need help for the next steps, most of the guides i've found require sw upgrade mode or recovery to continue after fastboot phase but i can't get into anything. I don't even know what rom/kernel/recovery i had last time, what should i search and flash now? (boot/kernel/rom/recovery/??).
Dead main board
dany123i said:
Hello xda,
tldr: i can only use fastboot right now, what do i flash to get a working recovery/sw upgrade mode/rom/something?
I got a LG P760 a year ago from a friend to have as backup phone and I tried then to root and put a custom rom but something went wrong and got the security error. After some more tries with fastboot the phone wouldn't even turn on so i gave up on it.
Now my main phone died and i wanted to fix and use this lg for a while but i can't seem to get anywhere after many many hours of trying.
As i said in title there's nothing appearing on screen at any point, no recovery, no lg logo, no fastboot text (as i've seen in some screenshot around here), no sw upgrade screen. The most i got out of it was the back/menu buttons to light up when using the omap4boot with option "[2] p920 - Optimus 3D (P920)" from here.
I had the same happen to my first p769. The service manual I have, has board level troubleshooting lists a few places(test points) to test voltage on the main board, if any are not to specs. it says to replace the main board.
Click to expand...
Click to collapse
Thanks, but that's a bummer, i was looking for a software only solution. The price of a replacement motherboard (used) is very close (10-20$) to a full used phone so it's not really worth it.
Hi All,
I have LineageOS 14.1-20180302 on my rooted Samsung Galaxy S5 (SM-G900F, klte).
Code:
Linux localhost 3.4.113-lineageos-gb020661 #1 SMP PREEMPT Fri Mar 2 13:43:58 CET 2018 armv7l
I use adopted SD card. Some time ago I had a problem after update (and next, after each reboot) – SD card was not available.
Link /sdcard returns error. I went by many symbolic links and there was empty /mnt/user/0. I just typed after each reboot:
Code:
ln -s /mnt/expand/22b48691-7d4a-41ee-8643-b78f7197bfb2/media/0 /mnt/user/0/primary
And it looked that worked.
Last time I found some error message on flashing. TWRP complains that can mount /system. Update process want up to 70..90% and hanged.
Wipe /system was not enough, I changed FS type to ext4 again, it creates new partition I guess. I flesh everything (ROM, OpenGapps, and su addon).
Now I have no SD card visible. Android shows „SD Card not inserted”. Many apps just crash. There is no /storage/emulated.
Surprise, /mnt/expand/UUID is mounted and it is working. I have access to all files in shell (adb). The same in TWRP.
I've tried to create symbolic links:
Code:
mkdir /storage/emulated
/storage/emulated/0 -> /mnt/expand/[I]UUID[/I]/media/0
It doesn't help. Android (apps) doesn't see it.
Only Total Commander show "Unknown SD" and can display SD data.
In another system (SM-9100) I see /storage/emulated is mounted via fuse. I've read fuse is used to access the sdcard while the OS is using the sdcard as well and for manages permissions.
I don't know hot to force my G900F Android to mount /storage/emulated via fuse.
Some more details...
sm list-disks, sm list-disks adoptable show nothing
sm list-volumes all shows only private mounted null
Code:
# cat /proc/partitions
...
179 64 60751872 mmcblk1
179 65 16384 mmcblk1p1
179 66 60734447 mmcblk1p2
253 0 60734447 dm-0
# mount | grep expand
/dev/block/dm-0 on /mnt/expand/[I]UUID[/I] type f2fs (rw,seclabel,nosuid,nodev,noatime,background_gc=on,user_xattr,acl,inline_data,flush_merge,extent_cache,mode=adaptive,active_logs=6)
Some logs:
Code:
03-30 21:44:51.168 302 306 D vold : private:179_66 passed filesystem check
03-30 21:44:51.060 302 306 V vold : /dev/block/dm-0: UUID="UUID" TYPE="f2fs"
03-30 21:44:51.403 302 306 V vold : Starting restorecon of /mnt/expand/UUID
03-30 21:50:27.941 302 306 V vold : Finished restorecon of /mnt/expand/UUID
03-30 21:50:29.434 302 307 D vold : e4crypt_prepare_user_storage for volume UUID, user 0, serial 0, flags 3
03-30 21:50:29.441 302 307 D vold : Preparing: /mnt/expand/UUID/user_de/0
03-30 21:50:29.441 302 307 D vold : Preparing: /mnt/expand/UUID/media/0
03-30 21:50:29.441 302 307 D vold : Preparing: /mnt/expand/UUID/user/0
03-31 10:46:21.454 302 7262 D vold : Starting trim of /mnt/expand/UUID
03-31 10:46:28.011 302 7262 I vold : Trimmed 0 bytes on /mnt/expand/UUID in 6556ms
Code:
03-31 20:43:53.209 781 1016 I chatty : uid=1000(system) MountService expire 2 lines
03-31 20:43:53.281 781 1016 I chatty : uid=1000(system) MountService expire 2 lines
03-31 20:44:53.883 781 1016 I chatty : uid=1000(system) MountService expire 2 lines
03-31 20:52:15.993 781 1016 I chatty : uid=1000(system) MountService expire 1 line
03-31 20:52:20.990 781 1016 D MountService: Thinking about init, mSystemReady=true, mDaemonConnected=true
03-31 20:52:20.990 781 1016 D MountService: Setting up emulation state, initlocked=false
03-31 20:52:21.003 781 1016 D MountService: Thinking about reset, mSystemReady=true, mDaemonConnected=true
03-31 20:53:21.040 781 1016 W MountService: Failed to reset vold
03-31 20:53:21.040 781 1016 W MountService: com.android.server.NativeDaemonTimeoutException: command '45 volume reset' failed with 'null'
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.NativeDaemonConnector.executeForList(NativeDaemonConnector.java:490)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:401)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.NativeDaemonConnector.execute(NativeDaemonConnector.java:396)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.MountService.resetIfReadyAndConnected(MountService.java:898)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.MountService.handleDaemonConnected(MountService.java:981)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.MountService.-wrap7(MountService.java)
03-31 20:53:21.040 781 1016 W MountService: at com.android.server.MountService$MountServiceHandler.handleMessage(MountService.java:616)
03-31 20:53:21.040 781 1016 W MountService: at android.os.Handler.dispatchMessage(Handler.java:102)
03-31 20:53:21.040 781 1016 W MountService: at android.os.Looper.loop(Looper.java:154)
03-31 20:53:21.040 781 1016 W MountService: at android.os.HandlerThread.run(HandlerThread.java:61)
03-31 20:53:21.052 781 1016 W MountService: No primary storage mounted!
03-31 20:53:21.055 781 1016 I chatty : uid=1000(system) MountService expire 3 lines
03-31 20:53:21.234 781 1016 W MountService: No primary storage mounted!
03-31 21:00:16.167 781 818 W MountService: No primary storage defined yet; hacking together a stub
03-31 21:00:16.168 781 3615 W MountService: No primary storage defined yet; hacking together a stub
03-31 21:00:16.395 781 2841 W MountService: No primary storage defined yet; hacking together a stub
Anybody knows how to fix it? I want to my adopted SD cards back in Android. And I want to understand how it works in the best case.
Now even TitaniumBackup doesn't see /sdcard and I can't make a backup before I make full factory reset.
Regards,
rysson