Database Info

[Q] G2x, Bricked ? Help please (tried NVflash)

So, I bought a g2x ,Rooted with a flashed rom (not sure which) .
Would have random reboots one day battery died and it never woke up after.
I used to be able to get into cwm (v. 3.0.5 flashed) Now it just hangs at the LG logo and does nothing. I tried calling the guy who sold it to me to get some info of Recoverys and roms he doesn't answer.
1. A custom Recovery was flashed, but don't know which and how it was flashed.
2. A Custom rom was flashed but don't know which.
3. It will connect to my win7 pc and shows up in Device manager. (Battery out, vol up + vol dwn)
4. NVflash finds it, but never succeeds.
5. One-click finds it, but never succeeds.
Ive tried using NVflash, followed the instructions : Battery out, hold down vol up + dwn, plug in usb, run command. It loads Fastboot, then thedownload of the bootloader is sucessfull but just hangs there never send the img file. Then it just gives NV error. One-click does the same no matter what recovery I try to flash, ext or int.
When I was able to get into Recovery I would give error about not eing able to mount cache and such, even when I tried to go back to a stock rom. Now I'm not bale to get into any Recovery, Vol dwn + Pwr. Only LG logo.
What I think I need is to Repair the internal Memory and partitions. From ADB, only problem is I can't turn the phone one to get my pc to recognize and install the adb drivers.
Any help would be great!

NO HELP ?

Hi, I'm pretty new myself to the g2x device. However, I'm able to install recovery and flashed to a different custom ROM before. so I have some experience in this area. When reading your post, I'm not fully understanding what you're saying. Are you able to turn the phone on at all? Or you stuck at the LG logo?
Are the battery able to charge with the phone off? Just to be sure we have to isolate the battery to determine whether it is the problem. Is there anyone around you that have the g2x. The problem I think is that your phone is unable to install the driver into your computer. You need to use someone device to install the NV driver. Once you install the NV driver.
Attempt to turn it on first. If it still won't boot. Then we can try to reflash the Recovery to the 4.02. If you able to do all this and get to the recovery screen, then I think we are set... The goal is to get to the recovery screen.
I hope this help...But anything more technical, we have to wait for others to help..Best of luck

I'm not exactly new either, I've used NVflash at least once before to flash a recovery onto a Streak. I've rooted and Flashed recovery to a few MYtouch4g's.
But this G2X is just proving to be a problem.
To answer some of your questions.
When The phone does power on, it just hangs at the LG screen.
I tested the voltage of the battery with a meter and shows 3.8-3.7 volts of power, and is able to light a tiny light bulb. I also checked the charging port and power is running to the prongs which would touch the battery to charge. I did put the battery into another G2X and it worked. I no longer have access to the other G2X so do further testing.
I was and can still get the PC to recognize the phone via battery out, Vol up + Vol dwn & connect usb wire. PC recognizes beeps and phone shows up in device manager as "Android usb recovery mode" or something simular. So the APX driver is installed
When I try to NVflash (while keeping vol up + vol dwn) CWM 4 or Stock recovery its the same result, Loads bootloader and just hangs until it spits out an NV error (i'll post the result). (S/W Upgrade screen does show up on phone)
I cannot boot into any recovery via holding Vol dwn + Pwr.
Ieven tried the One-click recovery, no go, errors out.
I did find a Zip file with a recovery which is supposed to load the phone the factory supposed to format partitions and load original files. Uses NVflash, its just a bat file which runs the NVflash commands. found here. But this loads some files then when it gets to the formating partition it errors out. i'll post what it does. link > android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/
Code:
C:\Users\Alan\Desktop\recover>.\nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR
-0DM_300MHz_final_emmc_x8.bct --setbct --odmdata 0xC8000 --configfile android_fa
stboot_emmc_full.cfg --create --bl fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x02804081423f7117
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: SOS
creating partition: EB4
creating partition: UDA
creating partition: EB5
creating partition: UDB
Formatting partition 2 BCT please wait.. |
I think what needs to be done is to fix the internal partition I think they got damaged somehow?

Wow, you doing really good. Unfortunately, I think this problem is out of my league. The worst you can do is call T-mobile. Tell them your device is defective and they can send you a new one. But since your phone is rooted, if they found out then we can run into some problem. Most likely they will charge you 99 dollars for damaging the phone. I hope you'll find a way to fix your device because the G2x rock...
PS: I think the previous might have flash a lg optimus 2x Rom, which could explain why the phone is damage...If your phone is in fact a Optimus 2x and we flash the wrong recovery, that could also explain why we can't install the recovery...
android.modaco.com/content/lg-optimus-2x-2x-modaco-com/335474/25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15-03-2011/

WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -H 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...

casper200519 said:
WARNING: This can destory your internalSD card partitions. If it's not broke don't fix it!
ALL COMMANDS ARE IN RED
I am not responsible for any damage you do to your phone.
I did this same thing to my phone... I was still able to get into recovery though. You can repair the internal partitions through ADB if you can still get into recovery.
Steps to recreate partitions.
Boot into recovery
from your PC open cmd prompt
change to your ADB directory
run adb shell
fdisk -h 1 /dev/block/mmcblk0
once in the fdisk of ../mmcblk0 you might as well delete all the partitions if you believe that they are corrupted
d
1
repeat for partition 2-8
one all of your partitions are gone you now have a blank internal SD and will need to execute the following to restore all the proper partition sizes
Partition 1
n
p
1
First Cylinder start 129
First Cylinder stop 55168
We will repeat this for partitions 2 and 3
Partition 2
n
p
2
Start 55169
Stop 63360
Partition 3
n
p
3
Start 63361
Stop 63616
On to partition 4 which will be extended (this is the last partion you will choose primary or extended)
Partition 4
n
e
4
Start 63617
Stop 975424
Now onto partition 4-8 which are automatically selected as logicall partions (no option is given)
Partition 5
n
Start 63681
Stop 64704
Partition 6
n
Start 64769
Stop 65088
Partition 7
n
Start 65153
Stop 261760
Partition 8
n
Start 261825
Stop 975424
Once you have done this the partitions are ready to be written to the internalSD
I would recommend choosing the command p to verify that all of your start and stop blocks are correct.
From this point you have the option to either quit without saving changes or to write the partition table itself. Once you are sure that you have entered all of your partitions correctly you can choose the command w
At this point you have recreated all the partitions on your InternalSD card. If you have a nandroid backup at this point you should be able to restore it without a problem once you copy it over to the internal or external (depending on which CWR you are running).
If I've forgotten any steps please feel free to comment and include them.
Thanks to TeamWhiskey for helping me resolve this issue when I had it...
Click to expand...
Click to collapse
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock

I love you. Thanks for putting up the instructions.

chulun9999 said:
Can you help me with a video easier to work !!!!!!!! hopefully my phone will return to stock
Click to expand...
Click to collapse
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help

casper200519 said:
I will try to get some video on it when I get time... If you get stuck on any of the instructions just ask and I'll check back often to try to help
Click to expand...
Click to collapse
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed

chulun9999 said:
you can guide me. I really do not understand to be able to work with it. I do not know where to start
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
failed executing command 14 NvError 0x120000
command failure: partition download failed
Click to expand...
Click to collapse
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?

casper200519 said:
The how-to that I wrote is on recreating the partitions... I understand your error is with allowing nvflash to create them. Are you still trying to put an O2x image on a G2x?
Click to expand...
Click to collapse
yes . i try to put an O2x image on a G2x . and now it happen this status . how do i repair my mistake .please help me

I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???

crosses fingers and prays
hope someone figures this out soon, i have been in many weird spots but none more than this g2x, it always worked fine and one day after reinstalling the cm7 nightly it never booted, just the LG boot screen and no more! windows even recognizes the phone but as fastboot only, NV flash says it worked but i never get further than LG screen, CLK Recovery wont pop up! hope someone solves this cus i love this phone!!

tylermauthe said:
I am experiencing the same issue. Any luck resolving this????
I have CWM as my recovery system... So I cannot use ADB -- it won't connect.
Any ideas???
Click to expand...
Click to collapse
ADB works in cwr recovery.if you find my other post labeled [REF]Repair internal SD in the dev area it has some q&a from others
Sent from my LG-P999 using XDA Premium App

Sorry for reviving this post!
This has been so helpful!
My phone was not able to boot in normal mode, but only in CWM! Thanks KAsp3rd!

need help with lg p999
hey am new here but am having the same problem and i need som help because i accedentaly used usde an nvflash tool for a lg p990 on my lg p999 and now am having problems with my baseband, sim,audio and my ime # is gone but the phone works but those are the problems that am having. so if any 1 help please assist

[A510][EXPERIMENTAL][DON'T USE] CWM Recovery 6.0.1.0.

Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Edit: since also pawitp bricked his device i highly recommend to NOT USE ANY CUSTOM RECOVERY until we have found out what causes this bricks!

mearoth said:
Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Click to expand...
Click to collapse
Hi mearoth,
My recoveries (see other thread in this forum) are build exactly like that, in my case I used the Dees-Troy fstab file. But... be really, really careful. If you do it this way, backup/restore and format stuff may brick your device. We've had one guy that had a simple FOTA bricking his device, so again... be really really careful...
Regards,
Nika.

just as a comparison :
fstab from dees-troy :
Code:
/system ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p10 length=-1048576
/cache ext4 /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/flexrom ext4 /dev/block/mmcblk0p6
/sdcard vfat /dev/block/sda1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p2
/aboot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/flex ext4 /dev/block/mmcblk0p6
/sdc vfat /dev/block/mmcblk1p1
fstab from the current cwn for a700:
Code:
# mount point fstype device [device2]
/sdcard vfat /dev/block/mmcblk1p1
/emmc datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768 # TODO: verify
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
can it be only a problem of partition size that cause the crash of data partition ?
Reminder for comparison (credit nikagl ) :
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data

BENETNATH said:
just as a comparison :
can it be only a problem of partition size that cause the crash of data partition ?
Click to expand...
Click to collapse
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.

mearoth said:
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.
Click to expand...
Click to collapse
it might be a good option to ask to pawtip how he found this value then, can you check with him ?

Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...

I just heard he also bricked his device
---------- Post added at 10:25 AM ---------- Previous post was at 10:09 AM ----------
paugustin said:
Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
Haha.. sorry, using my test account to see whether I can respond to dev-threads which works fine and also now say you already responded...

paugustin said:
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
I hear you and I think you are right. I will try digging a bit deeper into the whole flashing issue. Perhaps we can also investigate further in getting the sbk in order to enable us the APX flashing. I will try contacting Acer Europe once more.
Sent from my MB526 using xda developers app

For my knowledge, can you explain me how you get the mength value for the fstab ??
because the recovery you have created was with "length=-32768"

The "length=-32768" was just a value I have taken over by the nexus i think. however.
I just had a deeper look at the raw content of the mmc (dd if=/dev/block/mmcblk0 of=/data/mmcblck0-40000 count=40000) and have found something like a partition table at offset 0x30.00.00 . Since I believe it is not a regular partition table (nothing I know yet to be honest) I have not found out the sizes and offsets of the partitions. What I have found out though, is the fact that there are far more partitions than we know. Here comes the list in the order as they are in the RAW:
BCT <- (EDIT: Boot Config Table - contains HW timings etc. .. first siginficant offset in raw at 0x10 00 00)
PT <- (Partition Table - only a guess but the data is in the second significant offset at 0x30 00 00)
EBT <- EDIT: first Bootloader - when finished -> loads either LNX or SOS to go on in boot chain
EKS
DE1
GP1
-- Then comes the ones we already know:--
SOS
LNX
APP
CAC
MSC
FLX
AKB
USP
DE2
UDA
-- And one more we do not know:
GPT <- This could be a second partition table. this would not be unusual to have the table doubled at beginning and end. but I have not checket yet.
And here comes a possible explanation for the bricks: could it be since we do not have this in our fstab and the lengh value of UDA beeing probably incorrect that at some point when flashing the system overwrites bytes of this partition destroing the PT ? --> brick because bootloader can not determin right partition sizing any more. also this could happen at some point only when bytes are written to the GPT without us knowing. so flashing might work several times until it happens to strike this partition.
What do you think?
I will definitly investigate a bit more on that matter.

thanks for this
might be useful..
we need more gurus on that point, who can we reach to help us ? koush ?

I just got a reply from pawitp via pm:
pawitp said:
My brick is not due to formatting /data (The CWM I built does /data format using rm -rf), and I'm actually not sure why it bricked. The GPT at the end is the one read by linux.
Click to expand...
Click to collapse
So my guess was wrong. -> back to start.
I will nevertheless have a look at those hidden partitions. Some guru might really help but I don't know enought people here due to having been inactive for a long time.

good to know too.. strange

hi, any news for building the new CWM?

Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app

mearoth said:
Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app
Click to expand...
Click to collapse
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...

nikagl said:
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...
Click to expand...
Click to collapse
You are right. I got a version of nvflash running on my ubuntu machine but since our device is in APX secure mode the secure boot key is needed in order to do anything usefull with it. As long as we do not have this key we can really only ask acer to give it. There might even be a chance to get it since i heard the a200 sbk was also released. That's what i am currently on. Finding out whom to contact to get the sbk..
Sent from my A510 using xda developers app

e2fsck command on cleanly formatted partition?

Last night I started to run e2fsck on my /data partition to do a bit of investigation to see if had any corruption (again)
Anyway I unmounted /data in TWRP and went to the terminal and issued the following command:
e2fsck -fvyD /dev/block/mmcblk0p8
12 hours later and it was still running mainly reporting "Clone multiply-claimed blocks? Yes" Yes is because I have y flag turned on to answer yes to all questions.
So I killed it as it has never run this long before (previously 3 hours max).
I then formatted data which I thought would make it unnecessary and ran the command again after unmounting data and it is doing the same thing.....
Why?
Code:
.
.
.
(
inode
#
869248
. mod time
Sat Aug 25 18:23:27 2012
)
Clone multiply-claimed blocks? Yes
It appears to be doing this for many (if not all) inodes
Over and over.
This makes it seem like my /data partition is very corrupted and also Aug 25 is when I bought the device in 2012 so it has gone right back to the start.
I suspect it is somehow related to turning data journaling off whilst testing hunds kernels.
What is the definitive command to ensure data journaling is on please?

sbdags said:
I then formatted data which I thought would make it unnecessary and ran the command again after unmounting data and it is doing the same thing.....
Click to expand...
Click to collapse
That's strange - after formatting a partition, e2fsck must run in seconds and without errors, and it should definitely not bring up anything related to the old data. How did you format it?

_that said:
That's strange - after formatting a partition, e2fsck must run in seconds and without errors, and it should definitely not bring up anything related to the old data. How did you format it?
Click to expand...
Click to collapse
I formatted it using the big format data button in TWRP but yes I agree it doesn't appear to have done what would call a format? Maybe the equivalent of a quick format? How do I properly format the mmcblk0p8 partition?
If I just issue e2fsck -n /dev/block/mmcblk0p8 it comes back with clean. It is only when I force a scan that it finds all these errors.
Just reformatted and run again and it is dong the same again. ??
Btw what is the command to turn data journaling on? Or once formatted does journaling reset itself?

sbdags said:
Just reformatted and run again and it is dong the same again. ??
Btw what is the command to turn data journaling on? Or once formatted does journaling reset itself?
Click to expand...
Click to collapse
Can you find the following line in your recovery log? This would be the command that TWRP used to format.
Code:
make_ext4fs command:
Normally, formatting ext4 with default options enables the journal.

_that said:
Can you find the following line in your recovery log? This would be the command that TWRP used to format.
Code:
make_ext4fs command:
Normally, formatting ext4 with default options enables the journal.
Click to expand...
Click to collapse
It reports the following:
Code:
make_ext4fs -l -16384 -a /data /dev/block/mmcblk0p8

sbdags said:
It reports the following:
Code:
make_ext4fs -l -16384 -a /data /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Looks plausible. And look what I've found:
http://sourceforge.net/p/e2fsprogs/bugs/292/
You could try running the make_ext4fs command manually with the "-w" (wipe) option added - if I understand the code correctly, that should issue discard requests for all blocks, similar to fstrim.

sbdags said:
I formatted it using the big format data button in TWRP but yes I agree it doesn't appear to have done what would call a format? Maybe the equivalent of a quick format? How do I properly format the mmcblk0p8 partition?
If I just issue e2fsck -n /dev/block/mmcblk0p8 it comes back with clean. It is only when I force a scan that it finds all these errors.
Just reformatted and run again and it is dong the same again. ??
Btw what is the command to turn data journaling on? Or once formatted does journaling reset itself?
Click to expand...
Click to collapse
I mentioned this during the fiasco we had in the cromi thread awhile back, but I think it got lost in the rush of comments, let me know if you get it fixed, would love to be able to complete a check.

faustus1005 said:
I mentioned this during the fiasco we had in the cromi thread awhile back, but I think it got lost in the rush of comments, let me know if you get it fixed, would love to be able to complete a check.
Click to expand...
Click to collapse
Yeah something is not quite right with running fsck on the TF700. Oddly on my prime it runs without issue. I wonder if Asus has changed the way inodes are mapped. I know Samsung do this. I wonder if contributes to any lag as well?

_that said:
Looks plausible. And look what I've found:
http://sourceforge.net/p/e2fsprogs/bugs/292/
You could try running the make_ext4fs command manually with the "-w" (wipe) option added - if I understand the code correctly, that should issue discard requests for all blocks, similar to fstrim.
Click to expand...
Click to collapse
Let me do another backup and try the -w command as well. It's quite frustrating as I wonder if being able to run fsck correctly would help solve some of the lag issues we see.

_that said:
Looks plausible. And look what I've found:
http://sourceforge.net/p/e2fsprogs/bugs/292/
You could try running the make_ext4fs command manually with the "-w" (wipe) option added - if I understand the code correctly, that should issue discard requests for all blocks, similar to fstrim.
Click to expand...
Click to collapse
Adding the -w command fixed it (I think) e2fsk now completes in about a minute with no errors
Problem is now when I check if data journaling is on with a mount command there is no indication that it is - how to turn it off?
This is the command issued that turned it off I believe it's the "-O" that turns the journaling off:
Code:
run_program("/tmp/tune2fs.ext4", "-O", "^has_journal", "-c", "1", "-i", "1d", "-m", "0", "-o", "^journal_data_writeback", "/dev/block/mmcblk0p8");
is it as easy as issuing the same command without the "-O", "^has_journal" to get it back on?
OK I found some info looks like I need to issue this command in the installer?
Code:
run_program("/tmp/tune2fs.ext4", "-O", "+has_journal", "-c", "5", "-i", "5d", "-m", "0", "-o", "^journal_data_ordered", "/dev/block/mmcblk0p8");
I'll try that out now
Thanks for all the help @_that - I'm slowly getting there I think. :good:

sbdags said:
Last night I started to run e2fsck on my /data partition to do a bit of investigation to see if had any corruption (again)
Anyway I unmounted /data in TWRP and went to the terminal and issued the following command:
e2fsck -fvyD /dev/block/mmcblk0p8
12 hours later and it was still running mainly reporting "Clone multiply-claimed blocks? Yes" Yes is because I have y flag turned on to answer yes to all questions.
So I killed it as it has never run this long before (previously 3 hours max).
I then formatted data which I thought would make it unnecessary and ran the command again after unmounting data and it is doing the same thing.....
Why?
Code:
.
.
.
(
inode
#
869248
. mod time
Sat Aug 25 18:23:27 2012
)
Clone multiply-claimed blocks? Yes
It appears to be doing this for many (if not all) inodes
Over and over.
This makes it seem like my /data partition is very corrupted and also Aug 25 is when I bought the device in 2012 so it has gone right back to the start.
I suspect it is somehow related to turning data journaling off whilst testing hunds kernels.
What is the definitive command to ensure data journaling is on please?
Click to expand...
Click to collapse
You can try this.
tune2fs -l /dev/block/mmcblk0p8
You should see your system mounting has a "has_journal".
If it is not there, then your journal is off.
To turn it on.
tune2fs -O +has_journal /dev/block/mmcblk0p8
You should use the data_write for your journal to improve performance.
If you do a clean installation for your rom, the e2fsck should run less than a minute if you have a minimal apps installed. However, if you restore a nandroid backup for your system, it will take forever even though you don't have any app. I don't know why it does that with the nandroid backup..
I think that when you use e2fsck with a nandroid restore from your backup, the e2fsck is trying to convert your ext4 system to ext3 system.. It is just my guess. Maybe you and _that can figure why it does that.. Good luck...:fingers-crossed:

LetMeKnow said:
You can try this.
tune2fs -l /dev/block/mmcblk0p8
You should see your system mounting has a "has_journal".
If it is not there, then your journal is off.
To turn it on.
tune2fs -O +has_journal /dev/block/mmcblk0p8
You should use the data_write for your journal to improve performance.
If you do a clean installation for your rom, the e2fsck should run less than a minute if you have a minimal apps installed. However, if you restore a nandroid backup for your system, it will take forever even though you don't have any app. I don't know why it does that with the nandroid backup..
I think that when you use e2fsck with a nandroid restore from your backup, the e2fsck is trying to convert your ext4 system to ext3 system.. It is just my guess. Maybe you and _that can figure why it does that.. Good luck...:fingers-crossed:
Click to expand...
Click to collapse
Interesting, however, restored a nandroid and reran e2fsck and it finished in 30 secs with no errors Installed my ROM and ran it again and same again so it seems my problems are resolved for now
Thanks for the tips on data journaling.
BTW can you reup or send me the latest ET please - ready and confident to test it again now

sbdags said:
Interesting, however, restored a nandroid and reran e2fsck and it finished in 30 secs with no errors Installed my ROM and ran it again and same again so it seems my problems are resolved for now
Thanks for the tips on data journaling.
BTW can you reup or send me the latest ET please - ready and confident to test it again now
Click to expand...
Click to collapse
Haha, I found out that when I restore a good backup from nandroid and have more than 50% of problem with e2fsck.
I am still on a business trip. Let see if my thumb drive has the latest ET. Otherwise, I have it on my personal laptop at home. I will let you know in bit..

[Q] I think Internal Flash memory of my Android Device has some allocations dead

Greetings dears XDA members!
I read out many many many of posts before postings, and also used "search" feature in order to find a topic like mine, but with no success.
Well, I start to explain my problem..
====
A few days ago, my Samsung Galaxy Tab 2 (10'1)'s tablet caused some reboots without really beings really very common, but now .. reboot frequency has greatly increased since yesterday day.
A quick check using the "Reboot Checker" (you can find it through the Google Playstore: https://play.google.com/store/apps/details?id=jp.chau2chaun2.rebootchecker), and I can see that reboots are really common now as showed by the log reports showed in "RebootCheckerLogReports.png"'s file attachment to my post.
So.. What I do of specials before reboots are produced??
Hmm.. Really nothing, really:
I always deactivate the "AutoUpdate" for Apps from Google Play
Before reboots are encountered, I not installed any applications
I never install applications and Games out of Google Play official market
I just play to few games (like usually I do): Fantasica, Rage of Bahamut, Legends of Cryptids, Arcana Magic, DarkLords, Bingo Blitz, Chaos Drive, and that's all..
All applications I install from Google Play are recommanded/unlocked by AppGratis (and other websites like this)..
I never rooted my system (And I see now, I'll have to do on Day 1 of the purchase of the tablet ... since no-rooted an Android System doesn't permit recovery things at an advanced state..)
So, due to that reboot, I firstly thought that was a memory storage issue like, not enough diskspace. (with all that AppGratis applications, I have less disk storage memory indeed xD).. Then, I uninstalled some apps which I installed some months ago and I less used..
Bad Tought: Reboots hasn't been discontinued... ** sigh **
I think then it was update of Google Apps (like Google+, Google Talkback, Google Mail, Google Youtube etc..), so I updated them from Google Play..
Again, Bad Toughts: Reboots still here.. ** big sigh **
Well.. my hope was then at this state ported to Internet...
So I read many topics on "Unattended Reboots"..
And I finally found something of VERY useful.
On here: http://android.stackexchange.com/qu...-determine-the-cause-of-random-device-reboots
Glad I find that StackExchange question, I now that the "su" (Linux SuperUser if I well understand my Linux course), is not possible under a non-rooted Android (that a stupid behavior for an Operating System that.. But.. Well.. I continue)..
So, I started to think how I will be able to catch this file... and save in a readable folder..
Hopefully, 1 year ago I installed an app named: "ES Explorateur de fichiers" (find out this here: https://play.google.com/store/apps/details?id=com.estrongs.android.pop)
And this great apps was letting me accessing to the wanted file: /proc/last_kmsg
(I shared it to my DropBox linked account, and then I was able to open it on my Windows 7 Computer).
I then provide the log here: https://www.dropbox.com/s/u9ble2ui30io5x8/last_kmsg
So.. In the meantime, I started to analyze the log, and visiblely, my main (and sad) problem is that my Internat Flash Drive is dead.. Since I/O errors are the only main reason to Kernel Panic and reboots..
Well.. My warranty is void since months now.. (well well.. well..)
I then can't RMA the product (the tablet if I understand well).
I don't want wipe datas/cache and anything before try some new XDA tricks.. (I don't expect do much like that, but hey.. Hope is Hope.. my datas aren't important, it's true, it's mainly Game Saves and Unlock keys for AppGratis recommanded applications, but then, if I wipe datas, I will lose ALL of theses free unlocked apps.. This is a thing I doesn't really want, if you mean what I want mean..)
... so... I started to think what we can do for fix bad sectors on Linux (since Android is based on Linux and Dalvik if I (again) understanded well).
I hink that fixing bad sectors allocations it will fix the problem, since if I analyze my Internal storage (called sdcard0) there is sometimes the scan is finished without reboots!
So I was directed on XDA-Developers (which I know that you are famous for your system hacks and morever) here by Google : http://forum.xda-developers.com/google-nexus-5/help/reboot-due-to-kernel-panic-t2553949
I saw this post: http://forum.xda-developers.com/showpost.php?p=48250638&postcount=3
And then a quick search on Google again on the words "Android + fsck the filesystems through adb shell" redirected me to that excellent post: http://forum.xda-developers.com/showthread.php?t=2165870
This is a great information, but... I don't know how to go in recovery mode from my Galaxy Tab 2. So.. I searched on the web for it, and found that: http://forums.androidcentral.com/sa...ing-into-recovery-mode-galaxy-s2-s3-tab2.html
So.. I started blink my eyes, and go for hard work, and since I already in the past installed the Android SDK (for develop personal mobile apps with Titanium Studio, Adobe Cordova, PhoneGap), and do all update especially installed adb..):
Once plugged to my PC and booted in recovery mode, I was able to access to the famous recovery mode
(This was so exciting due to the fact I like the way of it look: especially the Android bot unfixed in the background ^_^).
So, on my PC I started to open a command line in the folder: C:\SpecialAppDevelopper\Google Android SDK\platform-tools
(this is where I installed the Android SDK)
and typed this:
Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb devices
This showed me that:
List of devices attached
c16073dc82dc68f recovery
Click to expand...
Click to collapse
So it worked! My device was successfuly attached to ADB !! What an excitation !
I then continued typing other commands:
Code:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb shell
This output that:
[email protected]:/ $
Click to expand...
Click to collapse
Good. Now In this shell access I typed :
Code:
mount /system
Not good here since all I get is a USAGE warning with options recommanded. (like a return of a MAN command..)
[email protected]:/ $ mount /system mount /system Usage: mount [-r] [-w] [-o options] [-t type] device directory
Click to expand...
Click to collapse
Well.. tryied the next command in order to listing report file system disk space usage:
Code:
df
all I got as output was occuped space, not the path of the mounted images...
Well...
Now, I started to reanalyze my last_kmsg log in order to find which path they are..
I found it!
[ 94.965454] C1 [jbd2/mmcblk0p10]
So... I started to return to my ADB commandline window and typing:
Code:
ls -l /dev/block/mmcblk0p10/
This outputed that:
/dev/block/mmcblk0p10/: Not a directory
Click to expand...
Click to collapse
So as it looks a good path, I started typing this:
Code:
e2fsck -n /dev/block/mmcblk0p10
And even if it is the right path (one of the right path, I don't tryied with others...), I got this output:
e2fsck -n /dev/block/mmcblk0p10
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Permission denied while trying to open /dev/block/mmcblk0p10
You must have r/o access to the filesystem or be root
Click to expand...
Click to collapse
Yeah... I'm not root, cool, even in a Recovery Mode on a non-rooted Android Operating System (Logic in a way, but very difficult to fix problems then occuring then )..
Ok.. So, My mind blinked in an idea when looking at this: You must have r/o access to the filesystem or be root
So.. This is not needed to be root for executing a e2fsck command in Recovery Mode, but in that case I need having access to the filesystem in a READABLE mode. OK.
So, Hope started to bringed back, and I made new Google research, on "mount an android filesystem in recovery mode"
I was then directed here:
- http://forum.xda-developers.com/showthread.php?t=1396864 - Very complex for me, I don't want brick my system.. So I skipped.
- http://androidforums.com/droid-all-...tem-when-trying-adb-push-app.html#post6347416 -
So.. For being root in recovery mode, I can also type the simple command: adb root
Ok... What I do..
And, as expected it doesn't worked for me:
C:\SpecialAppDevelopper\Google Android SDK\platform-tools>adb root
adbd cannot run as root in production builds
Click to expand...
Click to collapse
Ahaha.. Well starting to be hopeless now.. I'm finally just an user of my OWN tablet.. How it's ridiculous.
This is a bit tedious, because all my future Google research in order to find how to simply "mount" a filesystem as readable (and then replace it as it was after the process..) aren't really efficient, I founded nothing of useful..
Nothing usefull but that: http://android.stackexchange.com/a/69307
So, it seems I will be able to mount as readable a filesystem through Production Recovery Mode (the one I'm forced to use then..)..
BUT..
Well.. Now, since I don't know what I can type for mounting my filesystem... as readable just for make a e2fsck... Seriously..
Help me dear gurus, i'm completely lost because my Linux knowledge stop here !

New informations..
I tryied an another method in order to list devices symlinks names:
Another way to check is to use adb to view the devices file system.
Related to this thread: http://forum.xda-developers.com/showthread.php?t=1463756
Thanks to it (even if it isn't how mounting in RW)
So, when plugged in Recovery Mode I typed:
Code:
adb devices
adb shell "ls -R /dev/block"
The -R is because I want have the realpath of each items listed
Well, this was the output:
/dev/block:
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
/dev/block/platform:
omap
/dev/block/platform/omap:
omap_hsmmc.1
/dev/block/platform/omap/omap_hsmmc.1:
by-name
by-num
mmcblk0
mmcblk0boot0
mmcblk0boot1
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
/dev/block/platform/omap/omap_hsmmc.1/by-name:
CACHE
DATAFS
EFS
FACTORYFS
HIDDEN
KERNEL
MODEM
PARAM
RECOVERY
SBL1
SBL2
/dev/block/platform/omap/omap_hsmmc.1/by-num:
p1
p10
p11
p2
p3
p4
p5
p6
p7
p8
p9
Click to expand...
Click to collapse
Also, I read from here: http://forum.xda-developers.com/showpost.php?p=44328873&postcount=10
That E2FSCK will better be secure when executed on a named partition, can you confirm me it or no?
Now, I think..
Since, I know on my Windows when a sectors in corrupted or broken state, I can simply tell to the OS (Windows so) that I want it IGNORE it !
How I can do the same things to my Galaxy Tab 2?
It certainly fix my problem like that no?

Well well..
It is not better than it was, I really need advices and moreover help to know what I can do with the "mount" command and plus..
I was at 4'th page of the forum, so I think my thread just goes skip from your eyes, this is why I want up it..
Anyway, I read somewhere there is a lot of commands available.. due to the fact I'm not aware suffisely with Linux, and due to the fact Android recovery commands (and moreover the System) is based on Linux.. I prefer ask here..
So please, please.. answer me

[SOLVED] Help to mount userdata in linux or repair userdata.img

After an Update of Two magisk modules, my Ulefone Armor 11 5G staied stucked on boot logo, I can only enter in recovery or fastboot.
I try to build a TWRP, but it is not able to mount userdata.
I was able to download with the help of mtkclient all the partition on my phone, even userdata , it took 7 hours.
I wanted to load the image in linux but using mount disk imag or using the command sudo mount -o loop userdata.img ~/Armor_11_5G doesn't do anything not even an error message.
I'm wondering if the filesystem was corrupted during the update.
Is it possible to repair the fylesystem like in Windows?
Thanks

did you previously disable encryption and factory reset long time before the modules updates failed?
what do you mean mount doesn't do anything not even an error message? either it give error message or it succeed.

I didn't disable encryption before updating the modules, I already updated this modules many times.
what do you mean mount doesn't do anything not even an error message? either it give error message or it succeed.
Click to expand...
Click to collapse
That is the problem, it doesn't succed and I don't have an error message. The file is 256 Gbyte big, I don't know if it plays a role. I'm using Ubuntu 22

if phone is encrypted that's just 256G garbage. post the output of
Code:
$ parted <file> unit B print

Here are the results of parted
Code:
Error: /home/*****/Public/userdata.bin.img: unrecognised disk label
Model: (file)
Disk /home/osboxes/Public/userdata.bin.img: 249208733696B
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
Thanks

You may try https://www.cgsecurity.org/wiki/TestDisk_Download
I'd be glad for your feedback.

sorry thought it's whole disk, but it's only 232G file therefore parted won't print partition table
does apply to FDE only
assuming this file is dump of single userdata partition, open with HxD editor. if the partition image is not encrypted, you will see lot zeros within first 1024 bytes.
in that case you can check for file system type is ext4 or f2fs.
Code:
$ xxd -l 1080 dump.img | grep 53ef
$ xxd -l 1024 dump.img | grep 1020.f5f2
But most likely the userdata partition is encrypted, therefore no way to recover data offline.
The easiest way not to load Magisk modules is, not to load Magisk. Flashing stock boot.img will solve it.
Beware, in case you disabled encryption beforehand, booting stock boot.img will force encryption. This may take long time without notice.

I never disabled encryption, I don't know if Magisk do it without informing. I used this phone for an year without a problem.
After the update I left the phone on for one night but nothing happens. I tried to reflash the stock boot image, and again a whole night wait, but again nothing happens.
Reading the fstab the file system should be ext4.
The file is the dump of the whole userdata partition of my Ulefone Armor 11 5G.
I did a backup of the whole system before doing any experiment so if the partition table is corrupted maybe if I reflash back the userdata partition with a working partition table I have again access to the datas.

there is no partition table in userdata partition, I just gave you wrong advise. because the phones total storage is 256G, I made wrong assumptions (you can view partition table from file pgpt.bin)
full 1:1 backup is impossible for FBE encryption because encryption keys are stored in TEE. once you factory reset device backup of userdata + metadata becomes useless.
fstab doesn't tell you what file you just have dumped. if you can't find ext4 super magic (#7) it's impossible to loop mount that file (and impossible to decrypt on linux PC)
if you can't fix boot-loop by stock boot.img then it's unrelated to magisk modules. you can however enable adb in default.prop and capture adb logcat during boot-loop for further analysis. you could also inject own script that deletes some files (only DE encrypted files, CE encrypted files requires lock screen credentials aka pin/pattern)

boot this TWRP and get log from adb
Code:
$ fastboot boot recovery.img
$ adb shell twrp decrypt '1234'
$ adb pull /tmp/recovery.log
https://twrp.me/faq/openrecoveryscript.html

full 1:1 backup is impossible for FBE encryption because encryption keys are stored in TEE. once you factory reset device backup of userdata + metadata becomes useless.
Click to expand...
Click to collapse
With mtk client I was able to do the backup of tee1 and tee2 and also of gpt_backup and gpt_main.
$ xxd -l 1080 dump.img | grep 53ef
$ xxd -l 1024 dump.img | grep 1020.f5f2
Click to expand...
Click to collapse
Doesn't produce any results.
I have immediately the command prompt.
you can however enable adb in default.prop
Click to expand...
Click to collapse
How can I do that? Which value should I change in default.prop?

so your "backup" is encrypted. please note Trustonic Kinibi is TEE OS running in secure memory one can't access or backup with mtkclient. the tee partitions in phone storage do not contain any encryption key (none of the partitions does, secure memory is not even a partition). the only crypto related partition is metadata used for keydirectory of metadata encryption (on top of FBE encryption) but it is useless for backup purposes.
yes you can modify default.prop in boot.img, ro.secure=0 should give root access.
https://forum.xda-developers.com/t/...hone-with-broken-screen.2965462/post-85905033
Code:
ro.secure=0
ro.debuggable=1
persist.service.adb.enable=1
in case the default.prop modification is not sufficient, you need additional command to be executed as root.
Code:
# settings put global adb_enabled 1
as you installed magisk, you could use magisk overlay.d/sbin/ for running startup script.
https://forum.xda-developers.com/t/...ithout-losing-your-data.4383255/post-86934375
aIecxs said:
boot this TWRP and get log from adb
Code:
$ fastboot boot recovery.img
$ adb shell twrp decrypt '1234'
$ adb pull /tmp/recovery.log
https://twrp.me/faq/openrecoveryscript.html
Click to expand...
Click to collapse
How about this TWRP? it should be able to decrypt userdata. if decryption failed, provide recovery.log

Until tomorrow I cannot do a logcat and I cannot find my view logcat on my laptop.
I unpacked boot.img with Carliv Image Kitchen and there is no default.prop, that is present in the recovery as prop.default.
Is there a way to backup secure memory of Trustonic?
How about this TWRP? it should be able to decrypt userdata. if decryption failed, provide recovery.log
Click to expand...
Click to collapse
I already tried that version but it cannot decrypt, that' why I'm trying to build my own version of TWRp with the help of the creator of that version of TWRP, but I'm stucked.

oh, you know how to build TWRP with proper FBE + metadata encryption support? have a look at other Oppo devices how they did... good luck.
regarding default.prop in boot.img (it's a symlink to system unfortunately) you can do it the other way
use magisk overlay.d/sbin/
create a boot script that does the thing with resetprop -n <prop_name> <prop_value>
don't use outdated Carliv Image Kitchen! use osm0sis AIK from link above.

oh, you know how to build TWRP with proper FBE + metadata encryption support? have a look at other Oppo devices how they did... good luck.
Click to expand...
Click to collapse
I'm learning.
I try to integrate the decryption service following the suggestion of ADeadTrouser on Github, but the service doesn't want to start and I don't understand why.
I never checked Oppo, I will take a look at them also, thanks for the suggestion.

I think I figured out now the adb logcat at least. hope that helps
https://forum.xda-developers.com/t/accessing-my-phone-with-a-dead-screen.4542763/post-88016019

I tried your script butr nothing happens, the telephone is not listed when I type
Code:
adb devices
and if I type
Code:
adb logcat
I receive the message waiting for device

you might follow the thread

wenyendev said:
You may try https://www.cgsecurity.org/wiki/TestDisk_Download
I'd be glad for your feedback.
Click to expand...
Click to collapse
I run the software on the image and it identify the contents and can read the encrypted and not encrypted part, that means that all the files are there, but I cannot mount in Linux or in TWRP

The fact that I cannot mount in Linux or TWRP the userdata image/partition can be that is corrupted the partition or the file index?
That would also explain why the script for Magisk provided by aIecxs is not able to copy the adb_key from the cache in the data partition.