Related
I'm running low on options for what is wrong with this kindle fire, so maybe someone can point out something I am missing. My friend flashed google apps on it after they rooted and somehow something was botched and I've been playing doctor to it remotely over VNC and running commands on adb. Anyways, it's stuck at the splash screen and not booting and this is everything I've tried and all the information I've gathered:
1) reflashed the last updated boot.img from amazon in fastboot
2) reflashed the recovery.img in fastboot
3) verified the md5sum and permissions on every file & directory in /system (all check out okay).
4) Verified there are no files missing or added to anywhere in /system
5) cannot get it to rerun the update after pushing the update to /sdcard/kindleupdates (it ignores it despite it being there, either because of the condition of the tablet currently or the fact it's already updated).
After doing the above, the state of the device doesn't change a bit. Same errors, same slash screen.
Only idea I might have to what is wrong (but I have no idea how it would have happened) is the boot image (mmcblk0) is corrupted somehow (not to be confused with boot.img which has the kernel and ramdisk [mmcblk0p2]). If it is that, then flashing u-boot.bin might solve it, but I'm not sure how to do that exactly and would want to be sure since it could really screw things up.
Issues:
1) Stuck at the load splash screen
2) su will not work (says segmentation fault, etc), however running the temp root exploit manually will give back root for things I need and allow me to mount/unmount, etc.
3) lots of errors in log cat see the link (started at boot and ran a min or so): http://pastebin.com/LcXU3cxz
root method was zergRush : http://rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
partition sizes (from running cat /proc/partitions ):
179 0 7553032 mmcblk0
179 1 128 mmcblk0p1
179 2 256 mmcblk0p2
179 3 10240 mmcblk0p3
179 4 196608 mmcblk0p4
179 5 16384 mmcblk0p5
179 6 65536 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 5120 mmcblk0p8
179 9 524288 mmcblk0p9
179 10 1164288 mmcblk0p10
179 11 262144 mmcblk0p11
179 12 5254144 mmcblk0p12
Click to expand...
Click to collapse
If anyone can shed any light on what might be wrong or what else can be done, let me know.
Some problems I see.
I'm not as much an android expert as a linux one, but I went over your paste bin and here's a few of the lines that were of concern.
298: E/AndroidRuntime( 1397): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread
Fatal exceptions are never good. After that, until line 334, you are getting error after error.
550 E/System ( 1443): Failure starting core service
568 E/SystemServer( 1443): Failure starting Input Manager Service
580 E/AndroidRuntime( 1443): *** FATAL EXCEPTION IN SYSTEM PROCESS: ConnectivityThread same error again as the first.
It looks like something is crashing dalvik, and right after that all loaded apks die.... I don't have a kindle yet, that's why I'm surfing these forums so I'm not sure if you can with the recovery. Is it possible to wipe the dalvik cache?
If you have fastboot setup run fastboot -w .. it takes a long time.. I guess you could cancel it halfway safely. It'll be enough to trigger the kindle recovery on reboot which will wipe your dalvik cache.
Actually if you can get root (without the broken su) try deleting /data/dalvik-cache then reboot
transfuntioner said:
If you have fastboot setup run fastboot -w .. it takes a long time.. I guess you could cancel it halfway safely. It'll be enough to trigger the kindle recovery on reboot which will wipe your dalvik cache.
Actually if you can get root (without the broken su) try deleting /data/dalvik-cache then reboot
Click to expand...
Click to collapse
wiping in fastboot took care of everything and did a reset on it. thanks!
How to fastboot with wipe?
Can you share with how to fastboot and wipe for factory reset (effectively)?
knitterb said:
Can you share with how to fastboot and wipe for factory reset (effectively)?
Click to expand...
Click to collapse
I mentioned to my friend they should write it up and post how to do it since it would be easier for them to describe the steps in more detail since they actually physically have a kindle fire and I do not; so I think they will be later. It's rather easy to do though once you have the steps (basically a handful of steps and the rest is waiting).
It should provide a recovery for anyone that bricks their tablets though.
EDIT: link for unbricking is up now: http://forum.xda-developers.com/showthread.php?t=1356257
yareally said:
I'm running low on options for what is wrong with this kindle fire, so maybe someone can point out something I am missing. My friend flashed google apps on it after they rooted and somehow something was botched and I've been playing doctor to it remotely over VNC and running commands on adb. Anyways, it's stuck at the splash screen and not booting and this is everything I've tried and all the information I've gathered:
1) reflashed the last updated boot.img from amazon in fastboot
2) reflashed the recovery.img in fastboot
3) verified the md5sum and permissions on every file & directory in /system (all check out okay).
4) Verified there are no files missing or added to anywhere in /system
5) cannot get it to rerun the update after pushing the update to /sdcard/kindleupdates (it ignores it despite it being there, either because of the condition of the tablet currently or the fact it's already updated).
After doing the above, the state of the device doesn't change a bit. Same errors, same slash screen.
Only idea I might have to what is wrong (but I have no idea how it would have happened) is the boot image (mmcblk0) is corrupted somehow (not to be confused with boot.img which has the kernel and ramdisk [mmcblk0p2]). If it is that, then flashing u-boot.bin might solve it, but I'm not sure how to do that exactly and would want to be sure since it could really screw things up.
Issues:
1) Stuck at the load splash screen
2) su will not work (says segmentation fault, etc), however running the temp root exploit manually will give back root for things I need and allow me to mount/unmount, etc.
3) lots of errors in log cat see the link (started at boot and ran a min or so): pastebin.com/LcXU3cxz
root method was zergRush : rootkindlefire.com/kindle-fire-root/how-to-root-kindle-fire/
partition sizes (from running cat /proc/partitions ):
If anyone can shed any light on what might be wrong or what else can be done, let me know.
Click to expand...
Click to collapse
It says you flashed the boot.img and recovery.img, I believe I have problems with those two areas on my kindle, are you able to give any tips on flashing those?
I'm jumping and starting to develop for this device and just got the mount points. This is for anyone else that cares :silly:
lrwxrwxrwx root root 2012-10-03 20:37 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2012-10-03 20:37 bootloader -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2012-10-03 20:37 cache -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2012-10-03 20:37 crypto -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2012-10-03 20:37 dfs -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2012-10-03 20:37 dkernel -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2012-10-03 20:37 efs -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2012-10-03 20:37 idme -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2012-10-03 20:37 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2012-10-03 20:37 recovery -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2012-10-03 20:37 system -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2012-10-03 20:37 userdata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2012-10-03 20:37 xloader -> /dev/block/mmcblk0p1
Click to expand...
Click to collapse
timmytim said:
I'm jumping and starting to develop for this device and just got the mount points. This is for anyone else that wants that cares :silly:
Click to expand...
Click to collapse
Not to pick nits here, but those are actually the partition names -> device names. I hope you don't mind if I hijack your thread temporarily, but I think the following information is related.
Earlier this evening, a friend of mine let me borrow her KFHD for a few days with a "you break it, you bought it" proviso. Naturally, I've been playing around with it a bit.
I've also been looking at the way the storage space has been laid out on the KFHD. I think the most interesting change for most people will be the way the userdata partition is being used. I haven't seen this information posted anywhere, so I just wanted to share for the curious.
On the original KF, there are separate userdata and media partitions. The userdata partition gets mounted on /data and it's used mostly to store apps, settings, etc. The media partition gets mounted on /sdcard and that's used to store movies, music, books and other large files.
For the KFHD, the media partition is gone and the bulk of the storage space has been allotted to the userdata partition. That partition still gets mounted on /data, but /data now also contains a media directory. The KFHD then uses /data/media as the root for a virtual filesystem that gets mounted on /sdcard.
There have been at least a few users who mentioned repartitioning the original KF to get more space for apps by sacrificing space on /sdcard and vice versa. No such tradeoffs are required on the KFHD, because all of the user's files now get stored on one filesystem. As a result, the storage space gets a chance to be used more efficiently. I just thought that was a very tidy solution and an upgrade to the way things were done in the original.
Now, to get somewhat back on topic, here are the partition table details for the KFHD...
Code:
# parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 590kB 65.5kB idme
4 590kB 606kB 16.4kB crypto
5 606kB 608kB 2048B misc
6 1049kB 11.5MB 10.5MB dkernel
7 11.5MB 213MB 201MB ext4 dfs
8 213MB 230MB 16.8MB ext4 efs
9 230MB 238MB 8389kB recovery
10 238MB 246MB 8389kB boot
11 246MB 1175MB 929MB ext4 system
12 1175MB 1857MB 682MB ext4 cache
13 1857MB 15.6GB 13.8GB ext4 userdata
I dont mind at all. I've always referred to those as mount points but thinking about it now I realize I was wrong, lol.
Thanks man
kinfauns said:
Not to pick nits here, but those are actually the partition names -> device names. I hope you don't mind if I hijack your thread temporarily, but I think the following information is related.
Earlier this evening, a friend of mine let me borrow her KFHD for a few days with a "you break it, you bought it" proviso. Naturally, I've been playing around with it a bit.
I've also been looking at the way the storage space has been laid out on the KFHD. I think the most interesting change for most people will be the way the userdata partition is being used. I haven't seen this information posted anywhere, so I just wanted to share for the curious.
On the original KF, there are separate userdata and media partitions. The userdata partition gets mounted on /data and it's used mostly to store apps, settings, etc. The media partition gets mounted on /sdcard and that's used to store movies, music, books and other large files.
For the KFHD, the media partition is gone and the bulk of the storage space has been allotted to the userdata partition. That partition still gets mounted on /data, but /data now also contains a media directory. The KFHD then uses /data/media as the root for a virtual filesystem that gets mounted on /sdcard.
There have been at least a few users who mentioned repartitioning the original KF to get more space for apps by sacrificing space on /sdcard and vice versa. No such tradeoffs are required on the KFHD, because all of the user's files now get stored on one filesystem. As a result, the storage space gets a chance to be used more efficiently. I just thought that was a very tidy solution and an upgrade to the way things were done in the original.
Now, to get somewhat back on topic, here are the partition table details for the KFHD...
Code:
# parted /dev/block/mmcblk0 print
Error: Can't have overlapping partitions.
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.6GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 262kB 524kB 262kB bootloader
3 524kB 590kB 65.5kB idme
4 590kB 606kB 16.4kB crypto
5 606kB 608kB 2048B misc
6 1049kB 11.5MB 10.5MB dkernel
7 11.5MB 213MB 201MB ext4 dfs
8 213MB 230MB 16.8MB ext4 efs
9 230MB 238MB 8389kB recovery
10 238MB 246MB 8389kB boot
11 246MB 1175MB 929MB ext4 system
12 1175MB 1857MB 682MB ext4 cache
13 1857MB 15.6GB 13.8GB ext4 userdata
Click to expand...
Click to collapse
hello,
excuse me,i have a question: how have you got that? What's command have you write?
-> adb shell
-> su
-> parted
?
Android (Linux) Command Parted - Example
magikstar said:
hello,
excuse me,i have a question: how have you got that? What's command have you write?
-> adb shell
-> su
-> parted
?
Click to expand...
Click to collapse
magikstar,
The command is: parted here is examples on how the command is used:
Connect a Android Device to the PC USB, then reboot into recovery
At the command prompt type the command: adb shell
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open parted with the command: parted/dev/block/mmcblk0
To see The list of partitions and the capacity on the sdcard, type the command: print
The above example was not the Kindle, it is just to be used as an example.
---------- Post added at 07:15 PM ---------- Previous post was at 07:12 PM ----------
timmytim said:
I'm jumping and starting to develop for this device and just got the mount points. This is for anyone else that cares :silly:
Click to expand...
Click to collapse
timmytim,
Thank you for posting these Partition names, this is helpful.
How do I pull the 9, 10, & 11 blocks to a Windows 7 hard drive for future flashing?
timmytim said:
I'm jumping and starting to develop for this device and just got the mount points. This is for anyone else that cares :silly:
Click to expand...
Click to collapse
Is there a way using ADB to pull the boot, recovery, and system partitions to my hard drive for flashing if needed?
bobcat131 said:
Is there a way using ADB to pull the boot, recovery, and system partitions to my hard drive for flashing if needed?
Click to expand...
Click to collapse
Yes there is, see STEP 1. here - http://forum.xda-developers.com/showthread.php?t=2128848
Or this:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Credit to Hashcode :good:
Backup
Thanks for this quick answer. Where will these images be found - on the sdcard or on the hard drive?
bobcat131 said:
Thanks for this quick answer. Where will these images be found - on the sdcard or on the hard drive?
Click to expand...
Click to collapse
I think they are first saved to the SD Card then can pulled from there to your Hard Drive with the adb pull commands.
backup
Thanks again. I'll try on my KFSOWI today.
Backup/Restore
Gilly10 said:
I think they are first saved to the SD Card then can pulled from there to your Hard Drive with the adb pull commands.
Click to expand...
Click to collapse
I dumped them and pulled them to my hard drive okay. However, when I flashed them, all went well, until the system.img. I got this error when flashing the system img. "Invalid sparse file format at header magi"
How do I fix this?
If you are on the 2013 that makes more sense, the system image on a 2013 model you pull can't fit in fastboot's buffer so it would be useless, though I don't get why it thought it was sparsed, it shouldn't have been. I do recall seeing that error at one point while we were researching a way to restore the 2013 model when it gets bricked.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
If you are on the 2013 that makes more sense, the system image on a 2013 model you pull can't fit in fastboot's buffer so it would be useless, though I don't get why it thought it was sparsed, it shouldn't have been. I do recall seeing that error at one point while we were researching a way to restore the 2013 model when it gets bricked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Is there a way to increase fastboot's buffer size?
Sent from my 2013 Kindle Fire HD
Backup/Restore
stunts513 said:
If you are on the 2013 that makes more sense, the system image on a 2013 model you pull can't fit in fastboot's buffer so it would be useless, though I don't get why it thought it was sparsed, it shouldn't have been. I do recall seeing that error at one point while we were researching a way to restore the 2013 model when it gets bricked.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Yes, it is the 2013 edition. Now it is stuck at the boot logo (color Kindle Fire). It has ADB and fastboot recognition and I have a factory cable.
Any suggestions on how to unbrick this device using fastboot ??
Mineturtle33 said:
Is there a way to increase fastboot's buffer size?
Sent from my 2013 Kindle Fire HD
Click to expand...
Click to collapse
There are 2 reasons we can't do this, one is because even if we adjusted it we have no way to sign the new uboot so the device would hard brick upon flashing. The second reason is the buffer the file gets stored on is the devices ram. In this case the system image is around 1.3 GB, while the kindle only has 1gb of ram so there's a physical limitation.
bobcat131 said:
Yes, it is the 2013 edition. Now it is stuck at the boot logo (color Kindle Fire). It has ADB and fastboot recognition and I have a factory cable.
Any suggestions on how to unbrick this device using fastboot ??
Click to expand...
Click to collapse
Good news is this was recently developed: http://forum.xda-developers.com/showthread.php?t=2685090
It should restore it as long as you can get it into fastboot. Because of the fastboot buffer limitation, this pushes a partial resized system image that has just enough file to boot up, then pushes a amazon update to the device and forces it to update the system partition to a full os. Its really clever.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
There are 2 reasons we can't do this, one is because even if we adjusted it we have no way to sign the new uboot so the device would hard brick upon flashing. The second reason is the buffer the file gets stored on is the devices ram. In this case the system image is around 1.3 GB, while the kindle only has 1gb of ram so there's a physical limitation.
Good news is this was recently developed: http://forum.xda-developers.com/showthread.php?t=2685090
It should restore it as long as you can get it into fastboot. Because of the fastboot buffer limitation, this pushes a partial resized system image that has just enough file to boot up, then pushes a amazon update to the device and forces it to update the system partition to a full os. Its really clever.
But how to restore, if system.img is unflashable. I tride but still stuck at boot logo. HELP!:crying:
Click to expand...
Click to collapse
His system image is flashable because of some modifying he did, though I'm not sure if he included the matching boot image and recovery that goes with it, I'll check on it in a bit.
Sent from my Amazon Kindle Fire HD using Tapatalk
stunts513 said:
His system image is flashable because of some modifying he did, though I'm not sure if he included the matching boot image and recovery that goes with it, I'll check on it in a bit.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
I'm scratching my head, either i'm its not there or i'm stupid, i don't see the utility to download to fix the problem on the gdrive. Am i missing something?
I have Kindle Fire HD7 2012. After including of my kindle device(press the power button) is showing the Kindle Fire logo and then is showing the coloured inscription of "Provisioning Fail"
I been looking but to no avail... Is there a problem with backing up all 12 partitions and maybe making a zip file for otheres to use in KFFAide or is it gonna contain information thats personal to device and to user?
Hello,
I managed to break my fingerprint reader. I don't think the problem is my /persist because all sensors work fine. But unfortunately, I had never backed up the rest of the sensitive partitions: vbmeta, vbmeta_system, keystore, keymaster, odm, core_nhlos, secdata, abl, cmnlib, cmnlib64, devcfg, dsp, hyp, xbl, xbl_config, tz, rpm, aging, aging_mod.
Could someone on a TMO 7t Pro 5G McLaren (with a working fingerprint reader preferably running the latest 10.0.35 software, please pull and post these partition img files? If you don't know how, it's very simple, please ask.
I point to this because my previous phone, Essential PH1, had similar issues, but at least Essential had posted all of the firmware images on their website every month, and flashing the above partitions would fix it. 1+ doesn't provide anything and even the MSM doesn't restore all of these partitions.
Thanks so very very much in advance!
Edit: If possible, could one extract all partition img files from 10.0.35 in addition to those requested above?
EDIT2: ODM partition has 1st priority for anyone who can help.
Edit3: odm is fine. After looking through some logs,
I need keystore, keymaster (_a or _b, whichever is your current slot), vbmeta (a or b), and vbmeta_system (a or b). None are very large I think.
You're making me want a backup. I thought MSM was supposed to be that for us. Irritating.
A couple of those look like they could have sensitive data. Anyone know of a reason not to post them? Looks like they are all available via /dev/block..
ttabbal said:
You're making me want a backup. I thought MSM was supposed to be that for us. Irritating.
A couple of those look like they could have sensitive data. Anyone know of a reason not to post them? Looks like they are all available via /dev/block..
Click to expand...
Click to collapse
If you don't already have a backup of every partition, please please please do so urgently. Or an RMA will most likely be in your future. That should be in huge bold print with a link to instructions at the very top of the root and bootloader unlock threads.
I've never had a device with these issues before. It's starting to get ridiculous.
Edit: If you didn't take backups before unlocking the bootloader, Widevine L1 support (being able to watch Netflix in HD instead of 480p crap on our giant beautiful screens) is lost forever (except for RMA). And just flashing a "bad" canary version of magisk was enough to kill the fingerprint sensor. Of course I didn't learn any of this until it was too late.
MSM will get your phone back to life but not fully heal it. Basically all the MSM is guaranteed to do is get the phone to boot. No sensors, no fingerprint, no Widevine L1, no IMEI and wifi Mac address fix (if one is really screwed). And 1+ didn't take any measures to protect the sensitive partitions once bootloader is unlocked. It's all just a clusterf**k
Same issues on 7T and 8 and 8pro if that makes you feel any better ¯\_(ツ)_/¯
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
ttabbal said:
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
Click to expand...
Click to collapse
Yeah, system, vendor, product, and odm are stored in super.img on Android 10. But u found it. Find out what slot you are on, running 10.0.35, and you'd want the _a or _b files that match your current slot.
ttabbal said:
Well, that's irritating. WTF wouldn't you have a recovery tool for all those? Interestingly, I don't seem to have odm in there at all. Ah, scratch that, it's in /dev/block/mapper and there are 3. _a, _b, -verity.
It's rpm I don't seem to have. 10.0.35.
Click to expand...
Click to collapse
I think you are right. Rpm doesn't exist possibly on this phone. Don't have time to research right now.
But I noticed in /dev/block/mapper, I only have _a and _b. No -verity file. For system, vendor, odm, nor product. Could you post the -verity file(s)?
What files/file sizes do you have in /odm/ ?
starcms said:
I think you are right. Rpm doesn't exist possibly on this phone. Don't have time to research right now.
But I noticed in /dev/block/mapper, I only have _a and _b. No -verity file. For system, vendor, odm, nor product. Could you post the -verity file(s)?
What files/file sizes do you have in /odm/ ?
Click to expand...
Click to collapse
Doesn't look really interesting to me, but here's the ls output.
Code:
OnePlus7TProNR:/sdcard/img # ls -l /odm
total 20
drwxr-xr-x 4 root root 4096 2008-12-31 17:00 etc
drwx------ 2 root root 16384 2008-12-31 17:00 lost+found
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc
total 12
-rw------- 1 root root 2735 2008-12-31 17:00 build.prop
-r--r--r-- 1 root root 0 2008-12-31 17:00 fs_config_dirs
-r--r--r-- 1 root root 0 2008-12-31 17:00 fs_config_files
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 selinux
drwxr-xr-x 2 root root 4096 2008-12-31 17:00 vintf
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc/selinux/
total 728
-rw-r--r-- 1 root root 733547 2008-12-31 17:00 precompiled_sepolicy
-rw-r--r-- 1 root root 65 2008-12-31 17:00 precompiled_sepolicy.plat_sepolicy_and_mapping.sha256
-rw-r--r-- 1 root root 65 2008-12-31 17:00 precompiled_sepolicy.product_sepolicy_and_mapping.sha256
OnePlus7TProNR:/sdcard/img # ls -l /odm/etc/vintf/
total 16
-rw-r--r-- 1 root root 5300 2008-12-31 17:00 manifest.xml
-rw-r--r-- 1 root root 1369 2008-12-31 17:00 manifest_ese.xml
-rw-r--r-- 1 root root 622 2008-12-31 17:00 manifest_noese.xml
I can try, but my upstream sucks. It might be faster for someone else to grab them.
-rw-r--r-- 1 travis travis 816K Jun 4 15:40 img/odm-verity.img
-rw-r--r-- 1 travis travis 1.3G Jun 4 15:41 img/product-verity.img
-rw-r--r-- 1 travis travis 2.2G Jun 4 15:40 img/system_root-verity.img
-rw-r--r-- 1 travis travis 884M Jun 4 15:43 img/vendor-verity.img
After looking through some logs, you can ignore most of that.
I need keystore, keymaster (_a or _b, whichever is your current slot), vbmeta (a or b), and vbmeta_system (a or b). None are very large I think.
Thanks for all of your time @ttabbal. Sorry if I'm driving you crazy Been driving myself crazy trying to fix this for 2 weeks now lol
My /odm seems to be fine. Matches yours. I was mainly concerned about those 2 files with 0 size. But I don't have any of the -verity.imgs from /dev/block/mapper. I'm pretty sure they are supposed to be created and mounted at boot (from super.img and by verity/vbmeta). I'm hoping those 2 vbmeta partitions will fix things up. If not, then I'll try keystore and keymaster. And then I'll have to send it in...
Edit:. Just curious, I'm assuming you are bootloader unlocked and running Magisk? Just confirming since you have those -verity.imgs
ok.. Hope it helps.
https://drive.google.com/file/d/1a9FTbvdEM2n12wjc4SL7kNMu3SAtfuAY/view?usp=sharing
https://drive.google.com/file/d/15Ssumik6iMY7kWgldHfFajsbyNdh9aTz/view?usp=sharing
Yes, I am unlocked and rooted with Magisk.
ttabbal said:
ok.. Hope it helps.
https://drive.google.com/file/d/1a9FTbvdEM2n12wjc4SL7kNMu3SAtfuAY/view?usp=sharing
https://drive.google.com/file/d/15Ssumik6iMY7kWgldHfFajsbyNdh9aTz/view?usp=sharing
Yes, I am unlocked and rooted with Magisk.
Click to expand...
Click to collapse
Well, not exactly lol.
Flashed your two images via fastboot, still broken fingerprint and still missing -verity files from /dev/block/mapper/ , went to flash my backups of vbmeta and vbmeta_system via fastboot, got into a bootloop, and after a couple hours of screwing with it, finally got back where I started from...except using your images.
I don't understand. vbmeta and vbmeta_system are NOT device specific. One from my phone, one from your phone, one from anyone's phone running 10.0.35 should be exactly the same.
What exact method did you use to pull the images? dd to a tmp dir on device and then adb pull img? dd directly to computer? or adb pull the partitions themselves direct to computer? Shouldn't all 3 methods return the same results?
I swear, after the RMA I really don't know if I am going to risk unlocking the bootloader again (this is coming from someone who has had s-off/bootloader unlock/root/su/Magisk on every single android device ever owned over the past 10 years...without ever having any problem I couldn't fix by myself)
It should all be the same img, but I did "dd bs=1M if=/dev/<partition> of=/sdcard/img/" and adb pull them to the computer. Pretty much the same dd command I use for most image work. I am on 10.0.35.
One of the biggest reasons I gave this device a shot was the ability to reflash back to stock. Now I hear that doesn't work. That's really annoying. This is something Oneplus should just provide as a backup. They don't even have to keep it up to date. We can OTA our way to the latest. They have to have something like that to flash the phones before shipping them out. I guess they could flash to storage chips before installing them on the PCBs.
I was also hoping to see some development, I didn't realize that the A/B thing or A10 was going to cause so many problems. Not the devs fault, just one more thing to shake my head at. Sadly, I think root stuff is going to start phasing out. I don't mind no support for modified software, but I hate that I don't own my devices.
ttabbal said:
It should all be the same img, but I did "dd bs=1M if=/dev/<partition> of=/sdcard/img/" and adb pull them to the computer. Pretty much the same dd command I use for most image work. I am on 10.0.35.
One of the biggest reasons I gave this device a shot was the ability to reflash back to stock. Now I hear that doesn't work. That's really annoying. This is something Oneplus should just provide as a backup. They don't even have to keep it up to date. We can OTA our way to the latest. They have to have something like that to flash the phones before shipping them out. I guess they could flash to storage chips before installing them on the PCBs.
I was also hoping to see some development, I didn't realize that the A/B thing or A10 was going to cause so many problems. Not the devs fault, just one more thing to shake my head at. Sadly, I think root stuff is going to start phasing out. I don't mind no support for modified software, but I hate that I don't own my devices.
Click to expand...
Click to collapse
What is the need or result of the "bs=1M" in the command? I've never seen that before in other threads. I'm assuming it means block size equal to 1MB. Is that definitely required to get a good pull? Same bs for any/all partitions?
If you have persist and both EFS images backed up, you should be okay. The MSM tool can restore I think everything else. I'd keep a backup especially of any partitions that don't end in _a or _b. The MSM tool definitely takes care of the rest (those ending in _a and _b). I just hate using it because there's no way to make it not wipe userdata. And without being able to make a nandroid backup due to no fully working twrp due to A10, it's just a giant pain.
And unfortunately we can't just OTA our way to the latest, at least not by manually downloading an OTA from 1+. Only way to update is with a real OTA update from T-Mobile.
The A/B partitioning isn't the problem with development. That's been around since Android 7 or 8. It's the new dynamic partitioning format that all phones that launch with Android 10 (or newer) have. Even the Pixel 4 doesn't have fully working twrp yet. It's coming soon though...
Edit: Also, for the dd commands, did you use /dev/block/actual_partition or /dev/block/by-name/friendly_name_of_partition? Again, should it really make a difference?
Edit2: All of these issues have a root cause from Android 10. The new required partitioning system for any phones that launch with it. That's why unlocking the bootloader wipes reserve.img. Because it's in userdata (cause of A10) and 1+ forgot about that and didn't rewrite the algorithm used when the bootloader is unlocked. It's also their negligence (combined with A10) which causes persist (and other key partitions) to become so easily corrupted. Virtually all devices launched since Android 7 use "fastboot flashing unlock" and then "fastboot flashing unlock_critical" to allow changes to device specific partitions. For some reason 1+ still is using the antiquated "fastboot oem unlock" command which unlocks literally everything, even some stuff that unlock_critical doesn't, and which in the old days, didn't matter. A10 especially should not ever be used with fastboot oem unlock. Google says so lol.
If it makes you feel better, this isn't unique to this phone. It's a problem on every device 1+ has launched with A10 and still is (OP7T/TPro/OP8/Pro). Because of A10 partitioning combined with the use of an antiquated bootloader that only supports "fastboot oem unlock"
The block size doesn't matter for the pull and doesn't change the image at all. It just reads in chunks, making it faster.
Yes, I used by-name and it shouldn't matter if you use that or the sd# names.
It's your persist and it's unique. The rest of your sensors won't care. If you didn't back it up, you're screwed. An MSM restore doesn't fix this.
LLStarks said:
It's your persist and it's unique. The rest of your sensors won't care. If you didn't back it up, you're screwed. An MSM restore doesn't fix this.
Click to expand...
Click to collapse
The issue is I had a backup of my unique persist. And restoring it doesn't fix the dang fingerprint. That's why I was thinking the issue had to be elsewhere
Good evening everyone!
I recently bought a Junsun V1 head unit for my Golf 7. I specifically chose it because of the AC8227L SOC, which is a renamed MT8127. It includes a few more peripherals that are useful in car infotainment systems, but the core is identical.
I'm in the process of creating a new firmware from scratch, to replace the chinglish, buggy stock one. However, I have not succeeded yet.
What I have done so far is create a TWRP image for it, completely from source, using the prebuilt kernel. It's available here (any mirrors will be appreciated and linked in this post):
https://mega.nz/file/1Gp2gJ5S#gAxcP1WK8nwXivYTpAlyEsWNoWwNZBZ8VTs3fm57gEc
I have also dumped the firmware from the 2GB + 32GB version: https://mega.nz/file/hXhEjTab#AowvrX36nn9rXIkeu_zgnGmLyDxtiSUSWswwmXcN46k
To install install TWRP simply put it on the "RECOVERY" section in SP Flash Tool using the scatter and preloader provided in the firmware dump. Uncheck everything else and press flash.
You'll need a type-a to type-a USB cable connected to the 4-pin USB connector (not the 6-pin), and then give power to the unit.
Any other information about the device, serial communication between android and the MCU, decompiled apps, modified apps, etc are also welcome!
I hope this is useful for somebody.
UPDATE 07-01-2021:
I've been reverse engineering the MainUI apk for a week now. I've extracted the MCU communication protocol, now I'm trying to extract the DSP protocol, and CAN will be next.
The touch buttons on the left side of the unit is managed by this .apk as well, and that has already been reverse engineered, only the implementation has to be done with the available API I wrote.
All help is welcome. You can find the source code in github. The important work is being done in native libraries, the java stuff is useless right now. https://github.com/Iscle/MainUI
root
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
root
......see attachment
maxou2 said:
hi, i think i have a HU similar to yours ( se e attached pucture ). Btw did you manage to root the original fw? what about your development, it sounds interesting...
Click to expand...
Click to collapse
maxou2 said:
......see attachment
Click to expand...
Click to collapse
If you can install TWRP then you will be able to root.
iceblue1980 said:
If you can install TWRP then you will be able to root.
Click to expand...
Click to collapse
magisk?
maxou2 said:
magisk?
Click to expand...
Click to collapse
Anything you want but I would really recommend SuperSU as Magisk doesn't work as intended on these units. Also make sure you run SuperSU v2.79 and no higher. As for TWRP, only version 3.0.2 is stable in my experience.
I'm stuck unlocking the bootloader, the command "fastboot oem unlock" works and the unit ask to confirm by pressing vol+, unfortunately the touch on the panel does not work... tried to put a wireless keyboard dongle on the other USb but it doesn't work....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Magisk works just fine, I actually recommend it over SuperSU, as SuperSU is practically obsolete nowadays.
Also, no need to unlock the bootloader, just flash the recovery image as I explained on the first post.
Just made a deep study and tests on this unit, here my results, thoughts, mods and other considerations hoping this will help.
Being scared to brick the unit I used a conservative approach by making step by step mods rather than flash the firmware at the first post.
Here's my changment pattern:
Firmware : Before rooting I updated to the last version of the firmware the vendor gave me ( the latest OEM firmware ).
It's an OTA update ( use the "five fingers screen touch & move" method ) after putting the the files .bin and .upd in a USB key connected to a USB port when you powerup the unit.
I enclose a link to download it.
OTA update
I've made a DUMP of the partitions ( by using the SP tool Readback feature, you can find a lot of tutos on the internet how to use it ) and with the WwR tools i managed to have a full flashable original FW backup.
Another interesting method is to retrieve the partition content on a "live" system by use a shell and the dd unix command :
Enable the developer option on the system and connect the 4 wire USB port to a PC ( by using a 4 wire male to male USB cable ).
If you have an ADB command environment installed on your PC you can just fire a "adb shell" command,
followed by an "su @#zxcvbnmasdfghjklqwertyuiop1234567890,." to have a shell with superuser rights.
Now you can navigate trought your file system as root.
Anyway here's the partions table :
/dev/block/platform/soc/11230000.mmc/by-name # ls -l
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ANDROID -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 Dec 3 14:26 ARM2 -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Dec 3 14:26 BOOTIMG -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Dec 3 14:26 CACHE -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Dec 3 14:26 DKB -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Dec 3 14:26 EXPDB -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Dec 3 14:26 FRP -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Dec 3 14:26 KB -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 Dec 3 14:26 LK -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Dec 3 14:26 LOGO -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Dec 3 14:26 METAZONE -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Dec 3 14:26 MISC -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 20 Dec 3 14:26 NVRAM -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 21 Dec 3 14:26 ODMDTBO -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_F -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PROTECT_S -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Dec 3 14:26 PRO_INFO -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Dec 3 14:26 RECOVERY -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Dec 3 14:26 SECCFG -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 Dec 3 14:26 SEC_RO -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE1 -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Dec 3 14:26 TEE2 -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Dec 3 14:26 VENDOR -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Dec 3 14:26 forfanzone -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Dec 3 14:26 tszone -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Dec 3 14:26 userdata -> /dev/block/mmcblk0p26
Just use the dd unix command to dump every partitions content to a /sdcard directory where you can easily copy to an external USB stick or PC via adb pull.
E.g: dd if=/dev/block/mmcblk0p10 of=/sdcard/TWRP/boot_from_dd.img
Luckily I didn't have to use these datas to unbrick my system...
TWRP : I used another version ,it's a v3.3.1, works well. Flashed with SP Flash tool and the scatter contained in the .zip firmware at first post. I enclosed it so someone can tell what's the best option amongst these.
ROOT : Flashing magisk zip from TWRP worked flawlessy, but in my case i experienced an additional delay at boot ( let's say between 20-30 sec ), now a cold boot takes about 1 minute whereas with no root it was about 35 secs. I suspect this is due to the magisk modification to the boot process .
HW mods, temp controls and other infos will follow.
Any questions, just ask.
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
jabatillo_2001 said:
this is the last firmware that junsun send to me https://drive.google.com/file/d/1OjZcB0yqVQsu8O63l58VrMneZBmr25p5/view?usp=sharing
Click to expand...
Click to collapse
jabatillo_2001 said:
I have v1 1ram 16rom with ac8227l, but when I tried to update my radio I was only able to with an update-ty.zip with a manual process like this:
What I can do????
Click to expand...
Click to collapse
Your update process is very different from mine, probably you should tick every checkbox ( the most dangerous could be the MCU IMHO ) and start the update process. You should check first with the vendor, but it seems the correct procedure if the files he sent you match your Head Unit.
BTW take some picture of the MCu version, FW revision etc... of your unit.
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
maxou2 said:
Actually the compressed file they sent you contains BOOT, SYSTEM, TEE AND VENDOR updated partitions, and .bin update file ( usually the mcu update are .bin file but in my experience are really smaller then the one contained in the zip so it's diffucult to know what is for ).
So probably you should tick the "Sistema - > update_ty.zip" ONLY and start the update process....
Click to expand...
Click to collapse
jabatillo_2001 said:
The update only works with this name of file update-ty.zip, others don't work. My problem is bluetooth, It Connects and disconnects all the time. I'm crazy with this, I think the problem is bttool.apk or MTK but I'm not sure.I'm not allow to call or answer calls, either I can't dial by numbers.
I need to try some other firmware to resolve the problem.
Perhaps you can give me one idea or some trick to help me.
Thanks a lot.
My Android mobile XDA app don't work properly, after I'll attach you photos of my radio characteristics.
Click to expand...
Click to collapse
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
maxou2 said:
Keep in mind that generally on these chinese HU the BT is not managed by the android system as with cellphones, it's the MCU and dedicated apk that usually do that ( you do not have any BT option in the android system settings ).
So:
1) Did you try with a system reset?
2) Can you reach an advanced system option menu ( a little bit tricky in my unit ) where you can interact deeply ( BE VERY CAREFUL ) with several options, here you can set some BT systemwide parameters.
3) Maybe an MCU update could also help
Click to expand...
Click to collapse
maxou2 said:
Need to be sure that the firmware in this thread match your unit first, take pictures of your system infos. BTW your unit is only 1 GB RAM right?
Can you post the link where you bought it? ( Probably aliexpress... )
Click to expand...
Click to collapse
The firmware I posted on the first post was also extracted with SP Flash Tools + WwR tools. I sent it to a friend who uploaded a dump made with dumpyara here: https://git.rip/dumps/ffkj/ff-5000
This way we can navigate the filesystem easily, and grab anything we need.
I'm in the process of creating a kernel source for this SoC, I don't know if it will work, but if it does, the first thing I'll do is overclock it haha
jabatillo_2001 said:
1) yes
2)Wells, only development options of Android, the firmware not contains BT options. If you turn off BT, It turns off automatically. BT music only works if you play by mobile, neither by radio.
3) Perhaps, but it's the same problem, to update MCU I need a file named m51_update. You can see in image.
I have a A2 Lite of Xiaomi, but I try in a note 6 pro and the same problem.
What can I do?
I don't know what I can modify native MCU, but I like to probe another compatible ROM.
All my test, without rooting, are around Android 8.1 BT problems..
Bttool.apk don't work properly, disconnects for example, when I try to syncronize the contacts.
I'm afraid to brick It installing by flashing.
Click to expand...
Click to collapse
You should check your HU Hardware parameters, so you can figure is this thread is for you.
System "About device" - see picture.. Take a picture of the values on the screen.
After that touch the Gear icon on the top right of the screen a popup menu will appear, digit 8888 and ok.
An advanced system setting menu will appear, choose "others", scroll down and you'll see some BT options ( see picture ), try to change them.
Save and reboot.
If your system doesn't have such as menus I strongly recommend you to check elsewhere because probably your HU is different from mine.
Hello.
I have an old Samsung GT-I9060 (not sure if I should name it “Galaxy Grand Neo” or “Galaxy Grand Lite”) ; this is definitively not a ”Samsung Galaxy Grand Neo Plus”, but no such thread like ”Samsung Galaxy Grand Neo/Lite” without “Plus” seems to exist here.
I am trying to explore it using tools like adb or heimdall, I have Windows (10, 8, 7 , Vista and XP) AND Linux (Debian) computers in order to do this. Also Android Studio on Windows but I'm quite beginning on it, I'm more used on Microsoft Visual Studio and web languages.
I would like to understand how it works if I want to root it, or if I try to create my own firmware, either from existing ones or even eventually from source code.
I would like to avoid using any existing hack without completely understand any underlying handling.
So I got the corresponding stock firmware, and tried to explore it (by un-tarring in a Linux environment).
As a result, I get the following files :
total 1458620
-rw-r--r-- 1 root root 18087936 1970-01-01 01:00:00 BcmCP.img
-rw-r--r-- 1 root root 5472768 1970-01-01 01:00:00 boot.img
-rw-r--r-- 1 root root 30626024 1970-01-01 01:00:00 cache.img
-rw-r--r-- 1 root root 2440 1970-01-01 01:00:00 dt-blob
-rw-r--r-- 1 root root 7430328 1970-01-01 01:00:00 hidden.img
-rw-r--r-- 1 root root 614400 1970-01-01 01:00:00 param.lfs
-rw-r--r-- 1 root root 6935040 1970-01-01 01:00:00 recovery.img
-rw-r--r-- 1 root root 645244 1970-01-01 01:00:00 sboot.bin
-rw-r--r-- 1 root root 1422287488 1970-01-01 01:00:00 system.img
Click to expand...
Click to collapse
Now I would like to understand all of them.
I can find utilities for going deeper and explore inside most .img files for example.
But one of the most mystifying seems to be BcmCP.img. Googling it doesn't help me.
What is exactly in this file ?
Getting and analyzing the PIT using heimdall, I can see it is likely a partition contents.
But I can't identify any filesystem.
How can I go deeper into this ?
Gingko