Related
I'm running JF ADP1.5 and followed these instructions to get my apps to SD. For normal apps this works fine, but as far as I can tell protected apps (such as Abduction World Attack or Calorie Counter) get messed up. Installation seems to be working fine, but the apps have no icons, are called au.com.phil.abduction (or similar names) and forceclose on startup.
I don't believe I did something wrong with the apps2sd process, the symlinks are looking good:
Code:
# ls -al /data
drwxrwx--x 1 1000 1000 2048 May 3 11:19 .
drwxr-xr-x 12 0 0 0 May 7 10:36 ..
drwxrwxrwx 1 1000 1000 2048 May 3 11:20 anr
lrwxrwxrwx 1 0 0 14 May 3 11:33 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 May 3 11:33 app-private -> /system/sd/app-private
drwxrwx--x 1 1000 1000 2048 May 3 11:19 dalvik-cache
drwxrwx--x 1 1000 1000 2048 May 3 11:19 data
drwxrwx--x 1 2000 2000 2048 May 3 11:19 local
drwxrwx--- 1 0 0 2048 May 3 11:19 lost+found
drwxrwx--t 1 1000 9998 2048 May 3 11:19 misc
drwx------ 1 0 0 2048 May 3 11:19 property
drwxrwxr-x 1 1000 1000 2048 May 3 11:20 system
system/sd/app contains various apps, /system/sd/app-private is empty.
Does anyone here have a clue what's going wrong?
Could be a bad sdcard because I'm running that same exact paid app with no problem.
Try to reformat SD card, I've had some problems with my old card this is what I did:
killed all partitions
remake parts, formatted, still problems.
killed all partitions again, made one big part
dd if=/dev/zero of=/dev/sdcard1
remake 2 parts
mkfs.vfat /dev/sdcard1
mkfs.ext2 /dev/sdcard2
filled it up again.
I had the same problem when I got apps2sd, but wat I did was went to the market and all my paid apps said "update availabe", so I "updated" them even though they were already updated, but yea try that
I was wrecking my head all night cause I had the same problem. I lastly decided to format the old ext2 partition, refilled sdcard and presto, I did my happy dance.
Hi,
Go into apps on your phone and uninstall each paid app.
Then go to the market and reinstall.
They should work fine now.
That fixed this problem for me.
Apps on SD and ADP 1.5update
bsander said:
I'm running JF ADP1.5 and followed these instructions to get my apps to SD. For normal apps this works fine, but as far as I can tell protected apps (such as Abduction World Attack or Calorie Counter) get messed up. Installation seems to be working fine, but the apps have no icons, are called au.com.phil.abduction (or similar names) and forceclose on startup.
I don't believe I did something wrong with the apps2sd process, the symlinks are looking good:
Code:
# ls -al /data
drwxrwx--x 1 1000 1000 2048 May 3 11:19 .
drwxr-xr-x 12 0 0 0 May 7 10:36 ..
drwxrwxrwx 1 1000 1000 2048 May 3 11:20 anr
lrwxrwxrwx 1 0 0 14 May 3 11:33 app -> /system/sd/app
lrwxrwxrwx 1 0 0 22 May 3 11:33 app-private -> /system/sd/app-private
drwxrwx--x 1 1000 1000 2048 May 3 11:19 dalvik-cache
drwxrwx--x 1 1000 1000 2048 May 3 11:19 data
drwxrwx--x 1 2000 2000 2048 May 3 11:19 local
drwxrwx--- 1 0 0 2048 May 3 11:19 lost+found
drwxrwx--t 1 1000 9998 2048 May 3 11:19 misc
drwx------ 1 0 0 2048 May 3 11:19 property
drwxrwxr-x 1 1000 1000 2048 May 3 11:20 system
system/sd/app contains various apps, /system/sd/app-private is empty.
Does anyone here have a clue what's going wrong?
Click to expand...
Click to collapse
After I did the update I had a similar problem. I would install apps but no icons would appear. They would show up in settings as installed and I could uninstall them but no matter what I tried the icons would not show up. If I tried running them through settings, they would force close or say they weren't installed.
I copied everything off my fat32 partition onto my pc and used the trial version of Paragon Partition Manager to reformat the fat32 and ext2 partitions. Once reformatted, I used Lucidrem's 1.5 update as he had nice simple scripts for the apps2sd stuff. Copied that over to the fat32 partition, put it back into the phone and before applying the update I did a wipe Alt W and then did the update.
After the update I used terminal to enter the scripts (the apps2sd scripts) and started re-installing all my apps. True it was a bit of a pain to start over but the phone has been running great with virtually zero problems. Apps that were giving problems are running fine now.
The update over 1.42 or 1.43 seems to cause this for some of us. Who knows why it happens but it does. One advantage to "re-doing" everything is that you can get rid of all those apps that you never use anyway. Trying to figure out why your having the problem will probably take longer than simply starting from scratch.
Good Luck!
I finally got around to doing this. Pulled the app/ directory from the ext2 partition, first reformatted the whole sd card to one big partition (probably unnecessary but wth), then back to ext2/fat32 and cp -p'd the app/ dir back. All seems to work great now, and no need for a wipe! Thanks guys!
Hi.
Where is Dalvik-cache placed here ?:
Code:
# ls -al
total 256
drwxr-xr-x 23 root root 4096 Jun 24 10:08 .
drwxr-xr-x 23 root root 4096 Jun 24 10:08 ..
drwxr-xr-x 2 root root 4096 Nov 20 2011 .config
-rw-r--r-- 1 root root 147816 Jun 24 10:08 .readahead
drwxr-xr-x 2 root root 4096 Jan 5 08:16 bin
drwxr-xr-x 3 root root 4096 Nov 20 2011 boot
drwxr-xr-x 18 root root 4400 Jun 24 10:10 dev
drwxr-xr-x 118 root root 12288 Jun 24 10:08 etc
drwxr-xr-x 4 root root 4096 Nov 20 2011 home
drwxr-xr-x 22 root root 12288 Jan 5 08:16 lib
drwx------ 2 root root 16384 Nov 20 2011 lost+found
drwxr-xr-x 3 root root 60 Jun 24 10:10 media
drwxr-xr-x 2 root root 4096 Oct 25 2011 mnt
drwxr-xr-x 4 root root 4096 Dec 27 17:24 opt
dr-xr-xr-x 164 root root 0 Jun 24 2012 proc
drwx------ 27 root root 4096 Jun 24 10:25 root
drwxr-xr-x 21 root root 680 Jun 24 10:27 run
drwxr-xr-x 3 root root 12288 Jan 5 08:17 sbin
drwxr-xr-x 2 root root 4096 Oct 25 2011 selinux
drwxr-xr-x 4 root root 4096 Nov 10 2011 srv
drwxr-xr-x 12 root root 0 Jun 24 10:07 sys
drwxrwxrwt 18 root root 4096 Jun 24 10:25 tmp
drwxr-xr-x 12 root root 4096 Nov 10 2011 usr
drwxr-xr-x 15 root root 4096 Oct 1 2011 var
It is normally /data/cache/dalvik-cache
You have no data on there though....
I'm sure you are right.
Many thanks for your reply
# ls -al data/
total 96
drwx------ 3 Lajka users 32768 Jun 23 08:37 .
drwx------ 17 Lajka users 32768 Jan 1 1970 ..
drwx------ 2 Lajka users 32768 Jun 23 18:24 com.keramidas.TitaniumBackup
Click to expand...
Click to collapse
Its /data/dalvik-cache/
Send from my LG GT540 Android 4.0.3 Polishblood PreRC CM9
Thanks, and means, that I have no dalvik-cache ?.
Why?
hmm where did you get this and what are you trying to do? You dont have a recovery?
Hi.
What do you mean ?.
I have accessed the GT540 from my linux box, and can't see it.
I would delete the dalvik-cache.
No recovery available.
What's a way to get it ?.
Maybe there is a way but ... get a recovery
Please advice me to make a recovery, thanks!
aalested said:
Please advice me to make a recovery, thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1224747 just follow this
Indeed this was a nice link. Many many thanks :laugh:
Does this mean to be done when the telephone starts up ?
Next put your phone in Fastboot mode by rebooting then holding Camera+Power
Click to expand...
Click to collapse
aalested said:
Does this mean to be done when the telephone starts up ?
Click to expand...
Click to collapse
to go in fastboot mode turn your phone off. then press power on and at the same time hold the camera button
@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
From this thread:
http://http://forum.xda-developers.com/showthread.php?t=1224747
There stands:
Now, installing custom ROMs. Pick any ROM you'd like from the ROM Development section, if you can, get the recovery version, it is much easier to install. Determine if it is a recovery backup, or update.zip
Click to expand...
Click to collapse
Which one can I use for my GT540 with Android 2.1 ?
aalested said:
@andreas__
Thank you. I tried it, and the screen gets black and warm, nothing else.
Why that ?.
Which one can I use for my GT540 with Android 2.1 ?
Click to expand...
Click to collapse
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.
Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow
andreas__ said:
you did it correct if its black.
you now have to setup fastboot for your PC.
If you installed the drivers and have the needed files on your PC you can flash recovery.
Easy Fastboot tool by Junwei178:
http://forum.xda-developers.com/showthread.php?t=1729020
If you have recovery installed, you can flash any ROM you want.
Click to expand...
Click to collapse
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you
-Grift- said:
Yep if you use the tool get the original version. first use the repartition tool (for more app space) (select the 150Mb)then when that is done flash a recovery then flash a system followed by a boot. the on screen instructions should be easy enough to follow
Click to expand...
Click to collapse
Ok, but where is the "the tool get the original version" ?
Link ?.
aalested said:
Thanks for your reply.
But which ROM can I use for my GT540 with Android 2.1 ?
Link please, thank you
Click to expand...
Click to collapse
as -Grift- gave full instructions for the fastboot tool you now should have android 2.3 installed on your GT540.
IF you REALLY want back to 2.1 (maybe because of battery life)
check this:
http://forum.xda-developers.com/showthread.php?t=1368013
@andreas__
Manny thanks, great!
I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.
re: byte for byte
waypoint.delta said:
I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.
Click to expand...
Click to collapse
You would need to develop or find a developer who knows
how to create a very specific & special application to do that.
At the present time there is no applications that can do it.
You would be way better off to simply copy whatever good
files are in your internal memory to your computer because
any other way would result in many unusable files since
you said that the partition is all messed up.
By creating a byte for byte image of your internal memory
you would simply end up with a lot of unusable files since
your partitions are messed up.
Good luck, have a great day!
Thanks for the response Mr Junky. I can tell you I am fairly determined, short of hopping the NSA fence and demanding justice. Anyways, The partitions only matter so much since they do not define the files, the 1's and 0's do. There's tons of recovery software already, so no need to go that far, just need to get the data off my phone so it can be analysed. Square one is I grabbing a quality snapshot of the Internal Memory and putting it on my PC. At that point I can rebuild my phone without concern.
Misterjunky said:
. . .
Click to expand...
Click to collapse
Does anyone know if the partition/sector offsets ever change, or are they static? I ask because I ran "Repair or Change File System" on /data which shares a mount with /sdcard (i think). If they are static, it wont matter that the partition table was rebuilt, the lost data should still reside there. I can simply use DD to capture /dev/block/sda18 to a file. As a side note, I'm really glad i had busybox installed.
Code:
~ # ←[6n[COLOR="DarkGreen"][B]busybox fdisk -l /dev/block/sda[/B][/COLOR]
Note: sector size is 4096 (not 512)
Found valid GPT with protective MBR; using GPT
Disk /dev/block/sda: 62464000 sectors, 2336M
Logical sector size: 4096
Disk identifier (GUID): 52444e41-494f-2044-4d4d-43204449534b
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 7807994
Number Start (sector) End (sector) Size Code Name
1 1024 2047 4096K 0700 BOTA0
2 2048 3071 4096K 0700 BOTA1
3 3072 8191 20.0M 0700 EFS
4 8192 10239 8192K 0700 PARAM
5 10240 20479 40.0M 0700 BOOT
6 20480 32255 46.0M 0700 RECOVERY
7 32256 34303 8192K 0700 OTA
8 34304 45055 42.0M 0700 RADIO
9 45056 45311 1024K 0700 TOMBSTONES
10 45312 45567 1024K 0700 DNT
11 45568 45759 768K 0700 PERSISTENT
12 45760 45823 256K 0700 STEADY
13 45824 48127 9216K 0700 PERSDATA
14 48128 1148927 4300M 0700 SYSTEM
15 1148928 1200127 200M 0700 CACHE
16 1200128 1238527 150M 0700 HIDDEN
17 1238528 1239807 5120K 0700 CP_DEBUG
[COLOR="Red"][B] 18 1239808 7806719 25.0G 0700 USERDATA[/B][/COLOR]
~ # ←[6n
C:\adb>
C:\adb>adb shell
/dev/block/platform/155a0000.ufs/by-name # ?[6n[COLOR="darkgreen"][B]ls -l[/B][/COLOR]
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOOT -> /dev/block/sda5
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOTA0 -> /dev/block/sda1
lrwxrwxrwx 1 root root 15 Jan 2 12:45 BOTA1 -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 2 12:45 CACHE -> /dev/block/sda15
lrwxrwxrwx 1 root root 15 Jan 2 12:45 CPEFS -> /dev/block/sdd1
lrwxrwxrwx 1 root root 16 Jan 2 12:45 CP_DEBUG -> /dev/block/sda17
lrwxrwxrwx 1 root root 16 Jan 2 12:45 DNT -> /dev/block/sda10
lrwxrwxrwx 1 root root 15 Jan 2 12:45 EFS -> /dev/block/sda3
lrwxrwxrwx 1 root root 16 Jan 2 12:45 HIDDEN -> /dev/block/sda16
lrwxrwxrwx 1 root root 15 Jan 2 12:45 OTA -> /dev/block/sda7
lrwxrwxrwx 1 root root 15 Jan 2 12:45 PARAM -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 2 12:45 PERSDATA -> /dev/block/sda13
lrwxrwxrwx 1 root root 16 Jan 2 12:45 PERSISTENT -> /dev/block/sda11
lrwxrwxrwx 1 root root 15 Jan 2 12:45 RADIO -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 2 12:45 RECOVERY -> /dev/block/sda6
lrwxrwxrwx 1 root root 16 Jan 2 12:45 STEADY -> /dev/block/sda12
lrwxrwxrwx 1 root root 16 Jan 2 12:45 SYSTEM -> /dev/block/sda14
lrwxrwxrwx 1 root root 15 Jan 2 12:45 TOMBSTONES -> /dev/block/sda9
[COLOR="Red"][B]lrwxrwxrwx 1 root root 16 Jan 2 12:45 USERDATA -> /dev/block/sda18[/B][/COLOR]
/dev/block/platform/155a0000.ufs/by-name # ?[6n
I created the dd image of the USERDATA partition and saved it to the external SD card using the following command
Code:
dd if=/dev/block/sda18 of=/external_sd/dev/block/sda18.dd bs=4096
I then ran it against photorec which only returned 2 elf files. I will run it against testdisk as well, but I'm thinking either the data is gone or I did not use DD correctly.
In TWRP, when you go to "Wipe" -> "Advanced Wipe" you see a list of partitions, among them are "Data" and "Internal Storage". I wiped the "Data" partition as I thought "Internal Storage" would be untouched (since it was listed seperatly). Nope. Apparently they map to the exact same partition
Code:
/dev/block/sda18 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/sda18 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
I used "Change File System" on "Data" in order to make it usable again, I must have destroyed all the data I was trying to recover. Had I build the image before I fixed the data partition, I would probably have recovered most everything.
Thanks go out to Samsung for enabling auto update by default and for thoroughly testing the update which blew up my phone! Great job guys : )
waypoint.delta said:
I am looking for a way to create a perfect, byte for byte, image of my internal memory so that I can recover data from the image in a safer way and from a copy where I cant destroy the original. I am really just looking to recover files I had under the /sdcard (USERDATA mount) however, since my partitions are messed up, I want to broaden the scope and capture everything. Can anyone point me in the right direction?
Help is greatly appreciated.
Click to expand...
Click to collapse
You need to use photorec directly on the block device, not a copy. Copies don't copy detached inodes, even with dd.
Sent from my SM-G935T using Tapatalk
Everything I've read online negates that statement. however, I've yet to recover anything from the images I've copied, but I believe it may be due to hardware error. As a test, I put an photo on my /system mount and deleted the image. then I cloned the system block device and attempted recovery using photorec. this test failed to recover the file. so either DD is not copying the raw bytes or I am doing something incorrectly. I will try the same test using scalpel and also on another android phone.
toastido said:
You need to use photorec directly on the block device, not a copy. Copies don't copy detached inodes, even with dd.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
wonderfulme said:
It's been released in Europe for quite some time and from what I'm hearing it's about to hit the American market as well. Doen't seem to get any love yet on XDA.
Lovely little thing, from my three days with it. S625/64GB/4GB RAM/SD Slot/LTE. Comes with Android 7.1.1 stock.
Looks likes something that could finally replace the N7 2013, provided the community picks it up. I'm honestly surprised there's been little to no chatter about it whatsoever.
Did anyone manage to compile TWRP for it yet or root it otherwise?
Click to expand...
Click to collapse
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
matshias said:
I don't own the device so I cannot help you there. But what you can check is if the device can be bootloader unlocked in developer settings. That's a requirement for TWRP and also what you need is a kernel/boot image to build TRWP. Since there don't seem to be factory images available for this yet it will be difficult to retrieve a boot image from the device. Also Lenovo hasn't released any source code for this yet even though they are obliged to do so. Shame on them! I suggest you complain in the Lenovo forums about it. It's clearly a GPL violation.
Click to expand...
Click to collapse
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
matshias said:
Are you sure you are in fastboot mode? Can you try adb reboot bootloader and then connect with fastboot again?
Also you should check that in developer settings you have an option OEM unlock.
Well you don't need the kernel source for TWRP. What you need is the following:
* kernel image somehow extracted
* partition layout. If cat /proc/partitions works via adb then this is sufficient.
* extracted /system/build.prop and output of mount command
This should be enough to get it booting. Decrypting the data partition is another step, but for root it's not needed.
Extracting the kernel image is the hard part as long as there is no factory image available. But first check if the tablet can be unlocked otherwise it's not worth the effort.
Click to expand...
Click to collapse
There was indeed an option for "OEM unlock" in dev settings which I somehow missed. Works as intended now.
So here's the output of fastboot:
Code:
F:\AndroidSDK\platform-tools>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.054s]
finished. total time: 0.054s
Guess we're out of luck here?
I also did an "adb shell" and /proc/partitions as well as /system/build.prop are readable, "mount" works, however I have no idea where the kernel is stored. There's a "/firmware" dir but it's unaccessible, I'm thinking maybe that's where:
Code:
2|TB-8704X:/ $ uname -a
Linux localhost 3.18.31-perf-g40dd5c6-dirty #1 SMP PREEMPT Fri Jul 7 02:02:41 CST 2017 aarch64
TB-8704X:/ $ id
uid=2000(shell) gid=2000(shell) groups=2000(shell),1004(input),1007(log),1011(adb),1015(sdcard_rw),1028(sdcard_r),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats),3009(readproc) context=u:r:shell:s0
TB-8704X:/ $ ls -ld firmware
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
TB-8704X:/ $ cd firmware
/system/bin/sh: cd: /firmware: Permission denied
Also, FWIW, here's a list of files/dirs in / in case I missed something of note. I'm not really comfortable with Android internals.
Code:
130|TB-8704X:/ $ ls -l
total 4232
dr-xr-xr-x 61 root root 0 1970-03-08 03:34 acct
drwxr-xr-x 2 root root 40 1970-01-01 03:00 bt_firmware
drwxrwx--- 7 system cache 4096 2017-08-10 16:42 cache
lrwxrwxrwx 1 root root 13 1970-01-01 03:00 charger -> /sbin/healthd
drwxr-xr-x 2 root root 0 1970-03-08 03:34 config
lrwxrwxrwx 1 root root 17 1970-01-01 03:00 d -> /sys/kernel/debug
drwxrwx--x 43 system system 4096 1970-03-08 03:34 data
-rw-r--r-- 1 root root 995 1970-01-01 03:00 default.prop
drwxr-xr-x 15 root root 3500 1970-03-08 03:34 dev
drwxr-xr-x 3 root root 4096 1970-01-01 03:00 dsp
lrwxrwxrwx 1 root root 11 1970-01-01 03:00 etc -> /system/etc
-rw-r--r-- 1 root root 186677 1970-01-01 03:00 file_contexts.bin
dr-xr-x--- 4 system system 16384 1970-01-01 03:00 firmware
-rw-r----- 1 root root 1578 1970-01-01 03:00 fstab.qcom
-rwxr-x--- 1 root root 1246704 1970-01-01 03:00 init
-rwxr-x--- 1 root root 1846 1970-01-01 03:00 init.carrier.rc
-rwxr-x--- 1 root root 3295 1970-01-01 03:00 init.class_main.sh
-rwxr-x--- 1 root root 1156 1970-01-01 03:00 init.environ.rc
-rwxr-x--- 1 root root 1730 1970-01-01 03:00 init.mdm.sh
-rwxr-x--- 1 root root 29161 1970-01-01 03:00 init.msm.usb.configfs.rc
-rwxr-x--- 1 root root 7054 1970-01-01 03:00 init.qcom.class_core.sh
-rwxr-x--- 1 root root 12035 1970-01-01 03:00 init.qcom.early_boot.sh
-rwxr-x--- 1 root root 3775 1970-01-01 03:00 init.qcom.factory.rc
-rwxr-x--- 1 root root 37960 1970-01-01 03:00 init.qcom.rc
-rwxr-x--- 1 root root 2029 1970-01-01 03:00 init.qcom.sensors.sh
-rwxr-x--- 1 root root 12173 1970-01-01 03:00 init.qcom.sh
-rwxr-x--- 1 root root 2962 1970-01-01 03:00 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 97623 1970-01-01 03:00 init.qcom.usb.rc
-rwxr-x--- 1 root root 10950 1970-01-01 03:00 init.qcom.usb.sh
-rwxr-x--- 1 root root 26676 1970-01-01 03:00 init.rc
-rwxr-x--- 1 root root 9584 1970-01-01 03:00 init.target.rc
-rwxr-x--- 1 root root 12058 1970-01-01 03:00 init.usb.configfs.rc
-rwxr-x--- 1 root root 5715 1970-01-01 03:00 init.usb.rc
-rwxr-x--- 1 root root 411 1970-01-01 03:00 init.zygote32.rc
-rwxr-x--- 1 root root 684 1970-01-01 03:00 init.zygote64_32.rc
drwxr-xr-x 10 root system 220 1970-03-08 03:34 mnt
drwxr-xr-x 2 root root 40 1970-01-01 03:00 oem
drwxrwx--x 13 root system 4096 1970-01-01 03:00 persist
dr-xr-xr-x 518 root root 0 1970-01-01 03:00 proc
-rw-r--r-- 1 root root 11549 1970-01-01 03:00 property_contexts
drwxr-xr-x 3 root root 60 1970-01-01 03:00 res
drwx------ 2 root root 40 2017-07-06 21:00 root
drwxr-x--- 2 root root 160 1970-01-01 03:00 sbin
lrwxrwxrwx 1 root root 21 1970-01-01 03:00 sdcard -> /storage/self/primary
-rw-r--r-- 1 root root 1957 1970-01-01 03:00 seapp_contexts
-rw-r--r-- 1 root root 90 1970-01-01 03:00 selinux_version
-rw-r--r-- 1 root root 285602 1970-01-01 03:00 sepolicy
-rw-r--r-- 1 root root 17999 1970-01-01 03:00 service_contexts
drwxr-xr-x 4 root root 80 2017-08-12 15:57 storage
dr-xr-xr-x 16 root root 0 1970-03-08 03:34 sys
drwxr-xr-x 21 root root 4096 1970-01-01 03:00 system
lrwxrwxrwx 1 root root 16 1970-03-08 03:34 tombstones -> /data/tombstones
-rw-r--r-- 1 root root 14131 1970-01-01 03:00 ueventd.qcom.rc
-rw-r--r-- 1 root root 4857 1970-01-01 03:00 ueventd.rc
lrwxrwxrwx 1 root root 14 1970-01-01 03:00 vendor -> /system/vendor
-rw-r--r-- 1 root root 524 1970-01-01 03:00 verity_key
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
That's quite sad.
Just got it and been playing with it for a couple days now. Device itself seems to be fine, but not having root is PITA.
wonderfulme said:
So are we out of options yet unless a new Linux kernel exploit eventually comes along OR Lenovo decides to release the firmware? I don't believe dirtycow would work here, considering July 2017 security updates have been applied.
Click to expand...
Click to collapse
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
matshias said:
The firmwares just showed up on the Russian Lenovo forums. So we can build TWRP if you post all the prerequisites mentioned a few posts earlier (partition layout, mount output, ...)
Click to expand...
Click to collapse
Here's the output for the TB-8704X LTE version.
Mount points:
Code:
TB-8704X:/ $ mount
rootfs on / type rootfs (ro,seclabel,size=1705664k,nr_inodes=426416)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1811380k,nr_inodes=452845,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
none on /config type configfs (rw,relatime)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime,discard,data=ordered)
/dev/block/bootdevice/by-name/cache on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/persist on /persist type ext4 (rw,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/dsp on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/bootdevice/by-name/modem on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,size=1811380k,nr_inodes=452845,mode=755,gid=1000)
adb on /dev/usb-ffs/adb type functionfs (rw,relatime)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)
/dev/fuse on /mnt/runtime/default/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /storage/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/read/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
/dev/fuse on /mnt/runtime/write/emulated type fuse (rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other)
Partitions:
Code:
TB-8704X:/etc $ df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.6G 4.7M 1.6G 1% /
tmpfs 1.7G 652K 1.7G 1% /dev
tmpfs 1.7G 0 1.7G 0% /mnt
/dev/block/dm-0 3.6G 3.2G 336M 91% /system
/dev/block/bootdevice/by-name/cache 248M 744K 242M 1% /cache
/dev/block/bootdevice/by-name/persist 27M 512K 26M 2% /persist
/dev/block/bootdevice/by-name/dsp 12M 4.9M 6.4M 44% /dsp
/dev/block/bootdevice/by-name/modem 84M 74M 10M 88% /firmware
tmpfs 1.7G 0 1.7G 0% /storage
/dev/block/dm-1 52G 14G 38G 27% /data
/dev/fuse 52G 14G 38G 27% /storage/emulated
TB-8704X:/ $ cat /proc/partitions
major minor #blocks name
254 0 524288 zram0
179 0 61071360 mmcblk0
179 1 86016 mmcblk0p1
179 2 1 mmcblk0p2
179 3 8 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 2048 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 256 mmcblk0p10
179 11 256 mmcblk0p11
179 12 16384 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 1536 mmcblk0p14
179 15 32 mmcblk0p15
179 16 32 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 16 mmcblk0p18
179 19 15360 mmcblk0p19
179 20 1024 mmcblk0p20
179 21 1024 mmcblk0p21
179 22 65536 mmcblk0p22
179 23 65536 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 3984588 mmcblk0p25
179 26 262144 mmcblk0p26
179 27 32768 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 512 mmcblk0p29
179 30 32 mmcblk0p30
179 31 262144 mmcblk0p31
259 0 32 mmcblk0p32
259 1 512 mmcblk0p33
259 2 1024 mmcblk0p34
259 3 32768 mmcblk0p35
259 4 512 mmcblk0p36
259 5 4096 mmcblk0p37
259 6 128 mmcblk0p38
259 7 128 mmcblk0p39
259 8 256 mmcblk0p40
259 9 256 mmcblk0p41
259 10 256 mmcblk0p42
259 11 256 mmcblk0p43
259 12 256 mmcblk0p44
259 13 256 mmcblk0p45
259 14 256 mmcblk0p46
259 15 256 mmcblk0p47
259 16 8 mmcblk0p48
259 17 65536 mmcblk0p49
259 18 204800 mmcblk0p50
259 19 55492071 mmcblk0p51
179 32 4096 mmcblk0rpmb
253 0 3922408 dm-0
253 1 55492055 dm-1
/system/build.prop, just in case: https://pastebin.com/raw/jQn9N8nc
Kindly let me know if I missed anything.
Also, that Russian site lists the model number as TB-8704X_S000026_170707_ROW_QFIL, while my version of build.prop contains TB-8704X_S000026_170707_ROW (withot the "QFIL"). I'm not entirely up to date on Lenovo's naming conventions, but could that possibly suggest a slightly different model or should we disregard it altogether?
Edit: Nevermind, QFIL seems to be the name of the Qualcomm firmware update software.
Thanks!
I also hope that rooting or later a LineageOS will be available. I bought my one from Amazon in Germany 64GB/4GB/WiFi and it has following build number TB-8704F_S000024_170706_ROW. I came from Nexus 7 (2012).
Bought mine via Lenovo in the UK for £280 and loving it. I've been looking for a decent 8" tablet which wasn't stupidly expensive and this ticks all the boxes.
4GB /64GB + SD card
1920x1080 screen
Good audio with those front facing speakers
Decent battery life so far
Would love to be able to root and install Lineage as I use on my OPO as well, that would be perfect.
Love it so much I've ordered one for my old man as well.
wonderfulme said:
Thanks, I actualy did just that - asked about the kernel source on their official forum. Don't expect any major breakthroughts though (see https://forum.xda-developers.com/showthread.php?t=1555099, for instance).
As for whether the bootloader is locked or not, I have honestly no idea. Neither the "long phone number" method nor the "fastboot oem device-info" works. I have Android SDK installed and it works just fine when I plug in my N7 2003. The USB debugging is enabled and allowed for my desktop. Still, zero results. The Lenovo one doesn't even show up when running "fastboot devices".
Yet the "Lenovo Moto Smart Assistant" whatever it's supposed to do identifies the tablet when connected with USB just fine.
So I guess it's a safe bet to say that we're a long way from rooting this one. Or, more likely, I'm doing something wrong. Never had adb/fastboot issues with N7 though.
I'll just sit and wait till it hits the US market and generates some deserved interest because on the surface it's not a bad tablet at all. The battery life, the screen, the price/performance ratio, the SD slot and LTE capability all make that for a good web browser/book reader. It's not that bad looking either. Although I have yet to find a proper case unless resorting to Alibaba or something. It's even got a half-decent camera.
Overall, it's totally worth the $300 or whatever you end up paying. Comes with next to no bloatware, doesn't overheat. Even has that Dolby thing and a fingerprint scanner for some reason. Only wish it could be rooted and ran LineageOS or something.
Click to expand...
Click to collapse
I have the tab 4 8" and you can unlock the boooader know developer mode.
Anonwatch said:
I have the tab 4 8" and you can unlock the boooader know developer mode.
Click to expand...
Click to collapse
Already figured as much. You might want to take a look at matshias's thread at https://forum.xda-developers.com/thinkpad-tablet/general/twrp-root-tab-4-plus-tb-x704l-f-tb-t3664407
He's got TWRP working on both 8 and 10+.
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Vicky khan said:
Hey guys. I own Lenovo tab 3 8 plus (TB-8703F) and there are ads popping out everywhere when I open playstore or chrome etc? How to get rid of this?
Click to expand...
Click to collapse
Wrong thread for your device - but install an ad-blocker
Many thanks for your great work. Everything has worked as described and I am super happy with this new tablet, replacing my Nexus 7.
I am surprised that there is so little activity around the Tab 4 here on XDA, but I am confident that once people understand that this is a really cool tablet and practically the only one with modern specs that comes close to the N7, there will be Custom ROMs and more. It's a beautiful piece of hardware and even without Custom ROM, the Lenovo Android is surprisingly lean and without bloatware (except for Microsoft Office).
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Just had my memory card (128GB Samsung Pro) 'eaten' by my tablet - while on holiday with no computer access and it had my videos and music on it.
I've seen reports of this on other sites as well, and am fuming right now as this is an almighty ****-up if it's a regular occurrence, makes the tablet basically useless to me.
Edit: Took the card out of the tablet and stuck it in my Honor 9, no errors and all files work perfectly. Put it back in the Lenovo, so corrupt and won't let me do anything other than format it. Bloody Lenovo
jimmy19742 said:
Hi,guys!Just bought it from Amazon for $118(16GBROM)!
It's wonderful and I speak Russian, Macedonian, Bulgarian,German,a bit Serbian!
If you need help for Russian, just message me!:
Click to expand...
Click to collapse
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
magoo5289 said:
Hate to say it, but sounds like you bought the Tab 4 8 and not the Tab 4 8 Plus. If it is the Plus, you got a steal!
Click to expand...
Click to collapse
Yup 8504X not 8704X!
I saw this but am skeptical by nature and don't read Russian.
http://proshivkis.ru/?p=lenovo-tab-4-8-plus-wifi-lineageos-14-1
My samsung A205 fails to initialize FMP, the smatphone with the bootloader unlocked.
I tried various kernels like Rippler, Eureka and physwizz versions in TWRP.
And several Roms
I can always see the same error in dmesg:
Code:
[ 2560.206443] [2: mmc-cmdqd/0: 1799] exynos-fmp fmp: exynos_fmp_config: Fail to work fmp config due to fips in error.
[ 2560.206474] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_prep_tran_desc: failed to configure crypto engine. ret(-1)
[ 2560.206485] [2: mmc-cmdqd/0: 1799] mmc0: cmdq_request: failed to setup tx desc: -1
[ 2560.206535] I[2: ksoftirqd/2: 22] mmc0: mmc_blk_cmdq_complete_rq: txfr error: -1
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206630] [2: kworker/2:2: 3612] =============== CQ RECOVERY START ======================
[ 2560.206630] [2: kworker/2:2: 3612]
[ 2560.206784] [2: kworker/2:2: 3612] [CQ] mmc0: SW RESET: 250
[ 2560.206794] [2: kworker/2:2: 3612] ----- cnt_recovery: 2743
[ 2560.206803] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_pass: 2743
[ 2560.206812] [2: kworker/2:2: 3612] ----- cnt_recovery_halt_fail: 0
[ 2560.207055] [2: kworker/2:2: 3612] [CQ] mmc0:----- REQUEUE: tag 0 sector 32770, nr 2, retries 1
[ 2560.207181] [2: kworker/2:2: 3612] [CQ] mmc0: Enable after SW RESET
[ 2560.207198] [2: kworker/2:2: 3612]
While a well-functioning team shows:
Code:
[ 2.047718] [7: swapper/0: 1] exynos-fmp fmp: Exynos FMP Version: 1.3.2
[ 2.048316] [7: swapper/0: 1] exynos-fmp fmp: Found partno 32 for FMP test
[ 2.053900] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-xts passed
[ 2.058193] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP aes-cbc passed
[ 2.058212] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for FMP sha256 passed
[ 2.058246] [6: kworker/u16:3: 251] [SENSOR] stk3x3x_prox_cal: read_value = 10, (0xc0)
[ 2.058263] [7: swapper/0: 1] exynos-fmp fmp: FIPS: self-tests for UFSFMP hmac(sha256) passed
[ 2.058269] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: self-tests for FMP passed
[ 2.058751] [7: swapper/0: 1] FIPS(do_fmp_integrity_check): Integrity Check Passed
[ 2.058758] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_fips_init: integrity check for FMP passed
[ 2.058868] [7: swapper/0: 1] exynos-fmp fmp: exynos_fmp_probe: Exynos FMP driver is proved
Documentation about FMP and FIPS:
Document 2016
Document 2020
What could i try?
because of that mistake cannot access the flash memory properly so it cannot start a full android system just start in TWRP.
tried compiling a kernel with FIPS options disabled, and it works I can see the capabilities of all partitions by starting TWRP in read-only mode. when I do it in read write mode it works unstable and restarts.
Exploring in the kernel source code I could see
arch/arm64/boot/dts/exynos/dtbo/exynos7885.dts
Code:
fmp_0: fmp {
compatible = "samsung,exynos-fmp";
exynos,host-type = "mmc";
exynos-host = <&dwmmc_0>;
exynos,block-type = "mmcblk0p";
exynos,fips-block_offset = <5>;
Mount the partition mmcblk0p5 (CPEFS) and I found it to be of type ext4 and empty.
Could someone give me a copy of that partition or show me what files it originally has inside?
Upgrade:
I discovered that the partition mmcblk0p4 (SEC EFS) is corrupt.
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
In mmcblk0p4 (SEC EFS) I have:
Code:
Battery
FactoryApp
TEE
adp_token
afc
cpk
imei
lost+found
lpm
lpm_boot.log
nfc
nxp
pfw_data
prov
prov_data
recovery
sec_efs
ssm
tee
umc
wv.keys
./Battery:
batt_capacity_max
./FactoryApp:
Sensorinfo
asoc
batt_after_manufactured
batt_cable_count
batt_discharge_level
batt_temp_charge
cisd_data
cisd_wc_data
factorymode
fdata
gyro_cal_data
hist_nv
keystr
max_current
max_temp
rtc_status
test_nv
./FactoryApp/Sensorinfo:
Accelerometer
Barometer
Gyroscope
Light
Magnetometer
Proximity
./TEE:
./adp_token:
./afc:
./cpk:
./imei:
factory.prop
mps_code.dat
omcnw_code.dat
./lost+found:
#27
#28
#29
#30
#31
#32
#33
#35
#36
#39
#40
#41
#42
#43
#44
#45
#46
#48
#49
#50
#51
#52
#53
#54
#55
#56
#57
#58
#59
#60
#61
#62
#63
#64
#65
#66
#67
#72
#74
#75
#76
#81
#82
#92
#93
#94
#95
#98
./lost+found/#40:
./lpm:
./nfc:
./nxp:
./pfw_data:
./prov:
issued.log
libdevkm.lock
./prov_data:
./recovery:
extra_history
history
prev_tmp_recovery.log
./sec_efs:
!SVC
SVC
SettingsBackup.json
nfc
skpm_FACTORY_OCF_ECC_P256
skpm_OTA_WB_TA_Downloader_RSA_2048
skpm_sk.dat
skpm_supported_list
ucm_ca_cert
./sec_efs/nfc:
./sec_efs/ucm_ca_cert:
./ssm:
./tee:
./umc:
BulkEnrollmentProfile
From what I see in lost+found I know I have lost files.
Unfortunately e2fsck does not repair my partition. I made a copy using dd and tried to repair that image from my Salckware on my desktop pc but without success.
It would be great if someone published a complete backup of the partitions obviously without MAC, IMEI, Serial Number, and Bluethoo address.
Who can help me:
I need a copy of the sec_efs partition
To do this, I had to run:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img bs=4096
or at least the listing
Code:
ls -R -l > /external_sd/secefs.lst
I've been looking for a backup on the web for days but I haven't been successful so far. If you see any dumps of that paticion on the web, the download link will do me good.
Thanks
Cant you just install stock firmware using odin
physwizz said:
Cant you just install stock firmware using odin
Click to expand...
Click to collapse
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it was on screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of testing with different roms. On February 4, immediately took advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I am able to mount some partitions.
After that I started to read the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
Checking the other partitions I discover broken SEC_EFS.
I made a backup of what I could using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
format it with the same original parameters and restore the files you rescue from backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
sercari said:
Hello,
do not
This phone came with an error in which when turning on it showed a blue screen where it said update, then it failed and it showed on the screen:
Code:
E:[libfs_mgr]
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
and entered the recovery stock. where it said it couldn't mount / cache
if I put wipe cache it threw other errors and it was not corrected.
If I chose to start from the system it would be in a loop.
Initially it was with BIT 1 I updated it to BIT 8 using odin but the error persisted, I continued with the loop but (from what I search the web nobody solved it)
After a week of trying different roms. on february 4 it turned on immediately take advantage of activating oem and unlocking the bootloader. When rebooting it did not turn on again but I was able to finish unlocking the bootloader and install TWRP 3.5 from physwizz.
When entering TWRP it does not allow multidisabler-samsung-3.1.zip
giving me an error. I could not mount the vendor partition nor any other. What's more, everything accused 0 MB
Using TWRP 3.3 in combination with the Eureka kernel I managed to mount some partitions.
After that I started reading the system logs to explore dmesg and there I realized that what is wrong is the FMP system
Reading the source code of the linux kernel I see that this works using the partition mmcblk0p5 (CPEFS).
Regarding CPEFS, note that in the PIT file it does not declare which file should be written to that partition.
checking the other partitions I discover broken SEC_EFS.
I made a backup of what I pure using tar and another with dd
and I tried to repair it using e2fsck but it was badly damaged
Format it with the same original parameters and restore the files you rescue from the backups.
Currently if I install an original rom with odin I get the same scenario.
loop and if I started I recovered the error:
Code:
E:[PDP] lstat /c____/pdp_b__ : 0 - No PDP scenario
NOTE: Now I am looking for a merge file. I understand what the factory uses. but I only found up to BIT 7 and my phone is in BIT 8.
Thank you
Excuse my english
Click to expand...
Click to collapse
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
physwizz said:
Go here
Crash Recovery for the Samsung Galaxy A20
Crash Recovery for the Samsung Galaxy A20 1. Be Prepared Most of us will suffer from a crash at some time. If you know how to fix it, you will have a lot less stress. There are certain files you need to keep in readiness. Always backup boot...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you, this guide is very good, unfortunately it does not solve my case. Disable_Dm-Verity_ForceEncrypt didn't work either.
The problem of my phone is with FMP = Flash Memory Protector
It fails to start FIPS because a file is probably missing or corrupt. I think that what would help me would be to see the list of files of those partitions to know their name and weight.
It would help me if you can create a text file on your external memory card and paste this content inside:
Code:
mkdir /secefs
mount /dev/block/mmcblk0p4 /secefs -o ro
cd /secefs
ls -a -R -l > /external_sd/secefs.lst
mkdir /efs
mount /dev/block/mmcblk0p3 /efs -o ro
cd /efs
ls -a -R -l > /external_sd/efs.lst
mkdir /cpefs
mount /dev/block/mmcblk0p5 /cpefs -o ro
cd /cpefs
ls -a -R -l > /external_sd/cpefs.lst
Or with this other you can make a backup:
Code:
dd if=/dev/block/mmcblk0p4 of=/external_sd/secefs.img
dd if=/dev/block/mmcblk0p3 of=/external_sd/efs.img
dd if=/dev/block/mmcblk0p5 of=/external_sd/cpefs.img
(suppose the file is called mkbl.txt)
finally run it from the TWRP terminal:
Code:
/external_sd/mkbl.txt
with that I would generate files in /external_sd/
NOTE: If you generate backup files, keep in mind that they contain IMEIs and addresses that are private to you. You could make a copy of the .img file, mount it from linux in a folder and edit the files that contain personal information. Or you can trust me and I can erase that personal information to make the files public.
On the other hand, in the case of the lists with ls, it does not include any personal information, only file names and weights
sercari said:
In mmcblk0p5 (CPEFS) I have these two hidden files:
Code:
.nv_core.bak
.nv_core.bak.md5
Click to expand...
Click to collapse
Confirmed cpefs that is mounted in / vendor / cpefs contains only these two files normally.
Code:
-rwx------ 1 radio radio 546304 feb 4 20:51 .nv_core.bak
-rwx------ 1 radio radio 32 feb 4 20:51 .nv_core.bak.md5
drwx------ 2 radio radio 4096 ene 1 2019 lost+found
I would only need to find out the content of the partition /dev/mccblk0p4 (sec_efs) which I think is not mounted anywhere when the system is running. for which it is necessary to mount it to be able to list its content. I wait if someone can help me.
Thanks to TBM13 from the telegram @Galaxy_A20_official group who shared with me the list of files and directories on their sec_efs partition.
Thanks to TOP who shared the list of files on his cpefs partition. Thanks to this I can continue investigating.
mmcblk0p4 (sec_efs):
Code:
.:
total 180
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 .
drwxr-xr-x 30 root root 0 2021-02-24 17:24 ..
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 Battery
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 FactoryApp
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 TEE
drwxr--r-- 2 system system 4096 2019-01-01 12:00 adp_token
drwx------ 2 system system 4096 2019-01-01 12:00 afc
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 cpk
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 imei
drwx------ 2 root root 16384 2008-12-31 15:00 lost+found
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 lpm
-rw-rw---- 1 root system 256 2020-12-15 23:19 lpm_boot.log
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 nxp
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 pfw_data
drwxrwx--- 2 system system 4096 2019-06-29 17:22 prov
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 prov_data
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 recovery
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 sec_efs
drwxrwx--- 2 system system 4096 2019-01-01 12:00 ssm
drwx------ 2 system system 4096 2019-01-01 12:00 tee
drwx------ 2 system system 4096 2019-08-31 01:46 umc
-rw-r--r-- 1 system system 168 2019-06-29 17:22 wv.keys
./Battery:
total 20
drwxrwxr-x 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 system system 4 2021-02-21 02:58 batt_capacity_max
./FactoryApp:
total 132
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 28 2019-06-29 08:37 HwParamBattQR
-rw------- 1 system system 4876 2019-06-29 17:22 HwParamData
-rw------- 1 system system 824 2019-06-29 17:22 HwPartInform
drwx------ 2 system system 4096 2019-01-01 12:00 Sensorinfo
-rw-r----- 1 system log 3 2019-01-01 12:00 asoc
-rwxr--r-- 1 system system 1 2019-01-01 12:00 baro_delta
-rw-r----- 1 system system 2 2020-12-15 22:43 batt_after_manufactured
-rw------- 1 system system 4 2021-02-23 14:39 batt_cable_count
-rw-r----- 1 system system 6 2020-12-15 22:57 batt_discharge_level
-rw------- 1 system system 62 2021-02-24 17:10 batt_temp_charge
-rw------- 1 system system 1 2019-01-01 12:00 cable_detect_count_octa
-rw-rw---- 1 system system 195 2021-02-23 15:31 cisd_data
-rw-rw---- 1 system system 20 2019-01-01 12:00 cisd_wc_data
-rwxr--r-- 1 system system 13 2019-01-01 12:00 control_no
-rw------- 1 system system 2 2020-11-28 14:37 earjack_count
-rwxr--r-- 1 system system 2 2019-06-29 17:22 factorymode
-rwxrwxr-x 1 system radio 4 2019-01-01 12:00 fdata
-rw------- 1 system system 30 2021-02-24 13:06 gyro_cal_data
-rwxrwxr-x 1 system radio 0 2018-12-31 17:00 hist_nv
-rwxr--r-- 1 system system 2 2019-06-29 17:22 keystr
-rw------- 1 system system 5 2019-10-12 21:38 max_current
-rw------- 1 system system 4 2020-01-19 20:53 max_temp
-rwxr--r-- 1 system system 5 2019-06-29 17:29 mdnie
-rw------- 1 system system 1 2019-06-29 17:29 mdnie_ver
-rwxr--r-- 1 system system 5 2019-01-01 12:00 prepay
-rw------- 1 system system 1 2019-06-29 17:22 rtc_status
-rwxr--r-- 1 system system 11 2019-06-29 17:22 serial_no
-rwxrwxr-x 1 system radio 2000 2018-12-31 17:00 test_nv
./FactoryApp/Sensorinfo:
total 40
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 3 system system 4096 2019-08-31 03:09 ..
-rw------- 1 system system 21 2019-01-01 12:00 Accelerometer
-rw------- 1 system system 4 2019-01-01 12:00 Barometer
-rw------- 1 system system 17 2019-01-01 12:00 Gyroscope
-rw------- 1 system system 4 2019-01-01 12:00 Light
-rw------- 1 system system 19 2019-01-01 12:00 Magnetometer
-rw------- 1 system system 31 2019-01-01 12:00 Proximity
./TEE:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./adp_token:
total 16
drwxr--r-- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./afc:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./cpk:
total 20
drwxrwx--x 2 radio system 4096 2019-06-29 17:29 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-r--r-- 1 radio radio 920 2019-06-29 17:29 h2k.dat
./imei:
total 40
drwxrwxr-x 2 root radio 4096 2020-04-29 04:04 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 96 2021-02-21 03:41 factory.prop
-rwxrwxr-x 1 radio system 3 2020-12-15 23:26 mps_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code.dat
-rw-rw-r-- 1 radio root 3 2020-12-15 23:26 omcnw_code2.dat
-rwxrwxr-x 1 system radio 14 2019-06-29 17:22 prodcode.dat
-rw-rw-r-- 1 system system 4 2019-12-29 20:07 total_call_time
./lost+found:
total 28
drwx------ 2 root root 16384 2008-12-31 15:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./lpm:
total 20
drwxrwxr-x 2 system system 4096 2020-12-15 23:19 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw-rw---- 1 root system 85 2020-12-15 23:19 lpm_info.log
./nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./nxp:
total 16
drwxrwx--- 2 system audio 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./pfw_data:
total 16
drwxrw---- 2 oem_5279 oem_5279 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./prov:
total 20
drwxrwx--- 2 system system 4096 2019-06-29 17:22 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw----r-- 1 system system 559 2019-09-01 00:28 issued.log
-rw-rw---- 1 system system 0 2019-01-01 12:00 libdevkm.lock
./prov_data:
total 16
drwxrwx--- 2 radio system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./recovery:
total 24
drwxrwx--x 2 radio system 4096 2020-12-15 23:25 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 root root 257 2020-12-15 23:25 extra_history
-rw------- 1 root root 2529 2020-12-15 23:25 history
./sec_efs:
total 76
-rw------- 1 system system 569 2020-12-15 23:12 !SVC
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rwx------ 1 root radio 0 2019-06-29 17:07 .ffw
-rw------- 1 system system 569 2020-12-15 23:12 SVC
-rw------- 1 system system 6655 2020-12-15 23:32 SettingsBackup.json
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 nfc
-rw------- 1 system system 1517 2019-06-29 17:22 skpm_FACTORY_OCF_ECC_P256
-rw------- 1 system system 983 2019-09-01 00:29 skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
-rw------- 1 system system 4104 2019-08-31 02:43 skpm_OTA_WB_TA_Downloader_RSA_2048
-rw------- 1 system system 3941 2019-08-31 02:43 skpm_sk.dat
-rw------- 1 system system 4711 2019-09-01 00:29 skpm_supported_list
drwx------ 2 system system 4096 2019-01-01 12:00 ucm_ca_cert
./sec_efs/nfc:
total 16
drwx------ 2 nfc nfc 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./sec_efs/ucm_ca_cert:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwxr-x 4 radio system 4096 2020-12-15 23:32 ..
./ssm:
total 16
drwxrwx--- 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./tee:
total 16
drwx------ 2 system system 4096 2019-01-01 12:00 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
./umc:
total 20
drwx------ 2 system system 4096 2019-08-31 01:46 .
drwxrwx--x 21 system radio 4096 2019-08-31 01:46 ..
-rw------- 1 system system 1 2019-08-31 01:46 BulkEnrollmentProfile
Observing the list compare weight, permissions, owner and group of each file in /lost+found and I was able to deduce which file was and give it the corresponding location and name.
The only file I am missing is: /sec_efs/skpm_OTA_WB_FIDO_Bound_FP_ECC_P256
Someone has any idea about this file, apparently it is a key but I don't know if the phone should generate it automatically or how to get it.
I add that you do not know that the skpm_sk.dat file is blank. if I have it with a hex editor it is full of zeros
Thanks
Finally and mysteriously I boot into twrp allowing me to see all the partitions. (Only TWRP with full memory access would not start the system) Take advantage and I made a copy from partition 1 to 25 to and 31. Unfortunately I discovered that I have the partitions boot0, boot1, boot3, m9kefs, m9kefs2, m9kefs3, nad_fw, nad_refer blank.
UPDATE:
1- Get a copy of m9kefs1, 2 and 3 and I have them ok.