Greetings;
I've been wrestling with EFS & DM-Verity problem on my SM-T713 for a week now to no avail!
I've tried almost every solution/info from Google search to no avail.
My Tab can get to "Download & Recovery(Custom or Oem) mode with no problem
but any Firmware flash from odin wind up with "Samsung" bootloop!
And if I flash stock firmware, it ends up at Recovery mode with the following error:
"failed to mount /efs (invalid argument) dm-varity verification failed"
Any help is much appreciated.
Thank you.
Just factory reset in recovery. does that help?
Lightn1ng said:
Just factory reset in recovery. does that help?
Click to expand...
Click to collapse
Hi and thank you for replying.
BTW, I enjoy your rom bro, thanks for all the time you put in man.
I tried everything to no avail. I think I know how to resolve it but my know how
is probably limited to work it through! If that make any sense!
I first need to know the exact name of the "EFS Partition" on SM-T713. Then I
need to use the terminal/command line to format it and re-mount it, that should
do it if nothing else is a problem.
If you do own the T713, maybe you can help or anyone else reading this and
Thank you for your help.
samteeee said:
Hi and thank you for replying.
BTW, I enjoy your rom bro, thanks for all the time you put in man.
I tried everything to no avail. I think I know how to resolve it but my know how
is probably limited to work it through! If that make any sense!
I first need to know the exact name of the "EFS Partition" on SM-T713. Then I
need to use the terminal/command line to format it and re-mount it, that should
do it if nothing else is a problem.
If you do own the T713, maybe you can help or anyone else reading this and
Thank you for your help.
Click to expand...
Click to collapse
Wiping your EFS is a bad idea, it contains stuff that should truly NEVER be deleted.
I'm going to bed now. I'll try to continue helping in the morning.
This is important: is TWRP working?
Lightn1ng said:
Wiping your EFS is a bad idea, it contains stuff that should truly NEVER be deleted.
I'm going to bed now. I'll try to continue helping in the morning.
This is important: is TWRP working?
Click to expand...
Click to collapse
Ok I'll hold till you get back to me and Yes TWRP working and I have root
but of course I cannot boot to Android. I'll talk to you Tomorrow if you have time
and appreciate your help brother.
samteeee said:
Ok I'll hold till you get back to me and Yes TWRP working and I have root
but of course I cannot boot to Android. I'll talk to you Tomorrow if you have time
and appreciate your help brother.
Click to expand...
Click to collapse
Sounds like an easy fix. Will post the links tomorrow. Cya!
samteeee said:
Ok I'll hold till you get back to me and Yes TWRP working and I have root
but of course I cannot boot to Android. I'll talk to you Tomorrow if you have time
and appreciate your help brother.
Click to expand...
Click to collapse
OK. I'm going to start with a simple fix. Flash the stock firmware, then flash TWRP. Within TWRP, go to Wipe, then tap Format Data. Now, type yes and hit enter. After that, go to Reboot>Recovery. Now, flash this zip by @ashyx:
https://www.androidfilehost.com/?fid=24591000424951049
Reboot and tell me if it works or not
Lightn1ng said:
OK. I'm going to start with a simple fix. Flash the stock firmware, then flash TWRP. Within TWRP, go to Wipe, then tap Format Data. Now, type yes and hit enter. After that, go to Reboot>Recovery. Now, flash this zip by @ashyx:
https://www.androidfilehost.com/?fid=24591000424951049
Reboot and tell me if it works or not
Click to expand...
Click to collapse
Unfortunately I did this yesterday but just to be 100% sure I did it again just
now and got the same result. Right after flashing the stock firmware with odin, it winds up in android
recovery with the following error:
"E: failed to mount /efs (Invalid argument"
" E: DM-Verity failed"!
samteeee said:
Unfortunately I did this yesterday but just to be 100% sure I did it again just
now and got the same result. Right after flashing the stock firmware with odin, it winds up in android
recovery with the following error:
"E: failed to mount /efs (Invalid argument"
" E: DM-Verity failed"!
Click to expand...
Click to collapse
Yes at that point reboot back into download mode and flash twrp, then continue
Lightn1ng said:
Yes at that point reboot back into download mode and flash twrp, then continue
Click to expand...
Click to collapse
Done! Stuck at "Samsung Blinking" !
samteeee said:
Done! Stuck at "Samsung Blinking" !
Click to expand...
Click to collapse
Can you do this from a terminal in TWRP:
cat /proc/last_kmsg > /sdcard/kmsg.log
And send me kmsg.log from your internal storage please
Lightn1ng said:
Can you do this from a terminal in TWRP:
cat /proc/last_kmsg > /sdcard/kmsg.log
And send me kmsg.log from your internal storage please
Click to expand...
Click to collapse
How did you want me to send it to you?!!!
samteeee said:
How did you want me to send it to you?!!!
Click to expand...
Click to collapse
Copy it via USB.
Here you go...........
B - 530547 - VSENSE CX: Vol1=900000,Code1=98, Vol2=1000000,Code2=123
B - 536830 - VSENSE APC0: Vol1=900000,Code1=97, Vol2=1000000,Code2=121
B - 543327 - VSENSE APC1: Vol1=900000,Code1=96, Vol2=1000000,Code2=120
D - 58712 - vsense_init, Delta
B - 565134 - clock_init, Start
D - 640 - clock_init, Delta
B - 565897 - @@ pm power on reason[0x200000080]
B - 569526 - @@ Reset status @sdi[0x7f6e24db]
B - 573979 - @@ Reset status @sbl1[0x0]
B - 579195 - boot_fota_restore_partition, Start
B - 583068 - FOTA restore magic no matching
D - 4148 - boot_fota_restore_partition, Delta
B - 593743 - Image metadata authentication, Start
D - 17598 - Image metadata authentication, Delta
B - 613324 - Load all segments into memory, Start
D - 23454 - Load all segments into memory, Delta
B - 639890 - Hash verification of all segments, Start
D - 11102 - Hash verification of all segments, Delta
D - 63409 - QSEE Image Loaded, Delta - (660012 Bytes)
B - 658281 - Image Load, Start
D - 793 - SEC Image Loaded, Delta - (2048 Bytes)
B - 666699 - sbl1_efs_handle_cookies, Start
D - 884 - sbl1_efs_handle_cookies, Delta
B - 674416 - VSENSE codes wrote into SMEM
B - 678503 - boot_fota_close_hdev, Start
D - 0 - boot_fota_close_hdev, Delta
B - 688842 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 708423 - Load all segments into memory, Start
D - 2775 - Load all segments into memory, Delta
B - 716079 - Hash verification of all segments, Start
D - 1098 - Hash verification of all segments, Delta
D - 39925 - QHEE Image Loaded, Delta - (99056 Bytes)
B - 731390 - RPM loading is successful.
B - 737551 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 757254 - Load all segments into memory, Start
D - 6466 - Load all segments into memory, Delta
B - 766800 - Hash verification of all segments, Start
D - 6740 - Hash verification of all segments, Delta
D - 41937 - RPM Image Loaded, Delta - (192712 Bytes)
B - 783270 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 802882 - Load all segments into memory, Start
D - 49684 - Load all segments into memory, Delta
B - 855616 - Hash verification of all segments, Start
D - 24796 - Hash verification of all segments, Delta
D - 103120 - APPSBL Image Loaded, Delta - (1508364 Bytes)
B - 887977 - QSEE Execution, Start
D - 61 - QSEE Execution, Delta
B - 894687 - SBL1, End
D - 593743 - SBL1, Delta
S - Flash Throughput, 25000 KB/s (2465934 Bytes, 94911 us)
S - DDR Frequency, 931 MHz
S - Core 0 Frequency, 800 MHz
device type 1 = 0x0
device type 2 = 0x0
microusb_clear_register() - reset start
microusb_clear_register() - reset end
device type 1 = 0x0
device type 2 = 0x0
device type 1 = 0x0
device type 2 = 0x0
device type 1 = 0x0
device type 2 = 0x0
Initialization_routine: Already F/G initialized(version:0x1)
device type 1 = 0x0
device type 2 = 0x0
BOOTLOADER VERSION : T713XXU1APG1
check_pit_integrity: invalid pit magic code.(0x0)
B - 509472 - VSENSE CX: Vol1=900000,Code1=99, Vol2=1000000,Code2=123
B - 515755 - VSENSE APC0: Vol1=900000,Code1=98, Vol2=1000000,Code2=121
B - 522312 - VSENSE APC1: Vol1=900000,Code1=97, Vol2=1000000,Code2=120
D - 58682 - vsense_init, Delta
B - 544028 - clock_init, Start
D - 640 - clock_init, Delta
B - 544821 - @@ pm power on reason[0x2000000081]
B - 548542 - @@ Reset status @sdi[0xfb6e24db]
B - 552904 - @@ Reset status @sbl1[0x0]
B - 558211 - boot_fota_restore_partition, Start
B - 562115 - FOTA restore magic no matching
D - 4148 - boot_fota_restore_partition, Delta
B - 572790 - Image metadata authentication, Start
D - 17598 - Image metadata authentication, Delta
B - 592310 - Load all segments into memory, Start
D - 23881 - Load all segments into memory, Delta
B - 619272 - Hash verification of all segments, Start
D - 11102 - Hash verification of all segments, Delta
D - 63775 - QSEE Image Loaded, Delta - (660012 Bytes)
B - 637663 - Image Load, Start
D - 793 - SEC Image Loaded, Delta - (2048 Bytes)
B - 645990 - sbl1_efs_handle_cookies, Start
D - 884 - sbl1_efs_handle_cookies, Delta
B - 653828 - VSENSE codes wrote into SMEM
B - 657824 - boot_fota_close_hdev, Start
D - 0 - boot_fota_close_hdev, Delta
B - 668255 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 687866 - Load all segments into memory, Start
D - 2806 - Load all segments into memory, Delta
B - 695552 - Hash verification of all segments, Start
D - 1098 - Hash verification of all segments, Delta
D - 40016 - QHEE Image Loaded, Delta - (99056 Bytes)
B - 710802 - RPM loading is successful.
B - 717055 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 736666 - Load all segments into memory, Start
D - 6588 - Load all segments into memory, Delta
B - 746335 - Hash verification of all segments, Start
D - 6832 - Hash verification of all segments, Delta
D - 42090 - RPM Image Loaded, Delta - (192712 Bytes)
B - 762927 - Image metadata authentication, Start
D - 17507 - Image metadata authentication, Delta
B - 782538 - Load all segments into memory, Start
D - 50599 - Load all segments into memory, Delta
B - 836218 - Hash verification of all segments, Start
D - 24766 - Hash verification of all segments, Delta
D - 104066 - APPSBL Image Loaded, Delta - (1508364 Bytes)
B - 868548 - QSEE Execution, Start
D - 61 - QSEE Execution, Delta
B - 875289 - SBL1, End
D - 595573 - SBL1, Delta
S - Flash Throughput, 25000 KB/s (2465934 Bytes, 96617 us)
S - DDR Frequency, 931 MHz
S - Core 0 Frequency, 800 MHz
device type 1 = 0x4
device type 2 = 0x0
device type 1 = 0x0
device type 2 = 0x0
device type 1 = 0x0
device type 2 = 0x0
device type 1 = 0x0
device type 2 = 0x0
Initialization_routine: Already F/G initialized(version:0x1)
device type 1 = 0x0
device type 2 = 0x0
BOOTLOADER VERSION : T713XXU1APG1
check_pit_integrity: invalid pit magic code.(0x0)
AST_POWERON
device type 1 = 0x0
device type 2 = 0x0
RUSTPROOF : Power on Status 0x0000002000000081
device type 1 = 0x0
device type 2 = 0x0
Gimme a second to decypher that.
---------- Post added at 08:38 AM ---------- Previous post was at 08:35 AM ----------
Hmm... This is very weird - I don't see anything abnormal in that kmsg, just booting.
Are you sure you attempted to boot, then rebooted recovery to get the log?
@ashyx?
Lightn1ng said:
Gimme a second to decypher that.
---------- Post added at 08:38 AM ---------- Previous post was at 08:35 AM ----------
Hmm... This is very weird - I don't see anything abnormal in that kmsg, just booting.
Are you sure you attempted to boot, then rebooted recovery to get the log?
@ashyx?
Click to expand...
Click to collapse
I'll do it again......And send you the log!
Sorry tried twice to paste it here but the
XDA system won't allow me to do it, "Too long", it's 512 kb!
Can I email it to you??
samteeee said:
Sorry tried twice to paste it here but the
XDA system won't allow me to do it, "Too long", it's 512 kb!
Can I email it to you??
Click to expand...
Click to collapse
Yes. Email to [email protected] please thanjs
Lightn1ng said:
Yes. Email to [email protected] please thanjs
Click to expand...
Click to collapse
Sent....
samteeee said:
Sent....
Click to expand...
Click to collapse
Received. Looking over it now.
Hello,
i have a real hard problem. I got a new phone and to sell my old one, the HTC, i resett it. It worked, but i read about data restoring on the phone, so i resett it again. And here on the process i had must do something wrong. Because in the end the phone was i a bootloop until the lock screen.
Ok, not a big deal i thougt. The phone was rooted, so go on and flash a new FW. I found SPFlash tool. But it was hard to find a stock firmware for this modell. I followed a link here in the forum to Mega and with this one, it worked.
BUT, it came out as a HTC Desire 320!!!!! And i got a message on start up that the CID is wrong.
So i looked for a correct FW for the 626g, and i think i found one. I run the SPFlash Tool again with this one and i got a GO. But the phone still dos not start. So i run a Memory test with the FlasTool and got
this and on the end a failure message
============ Memory Detection Report ===========
Internal RAM:
External RAM:
Type = DRAM
Size = 0x40000000 (1024MB/8192Mb)
NAND Flash:
ERROR: NAND Flash was not detected!
EMMC:
EMMC_PART_BOOT1 Size = 0x0000000000400000(4MB)
EMMC_PART_BOOT2 Size = 0x0000000000400000(4MB)
EMMC_PART_RPMB Size = 0x0000000000400000(4MB)
EMMC_PART_GP1 Size = 0x0000000000000000(0MB)
EMMC_PART_GP2 Size = 0x0000000000000000(0MB)
EMMC_PART_GP3 Size = 0x0000000000000000(0MB)
EMMC_PART_GP4 Size = 0x0000000000000000(0MB)
EMMC_PART_USER Size = 0x00000001d2000000(7456MB)
UFS:
ERROR: UFS was not detected!
============ RAM Test ============
Data Bus Test:
[D0]
[D1]
[D2]
[D3]
[D4]
[D5]
[D6]
[D7]
[D8]
[D9]
[D10]
[D11]
[D12]
[D13]
[D14]
[D15]
[D16]
[D17]
[D18]
[D19]
[D20]
[D21]
[D22]
[D23]
[D24]
[D25]
[D26]
[D27]
[D28]
[D29]
[D30]
[D31]
OK!!
Address Bus Test:
[A1]
[A2]
[A3]
[A4]
[A5]
[A6]
[A7]
[A8]
[A9]
[A10]
[A11]
[A12]
[A13]
[A14]
[A15]
[A16]
[A17]
[A18]
[A19]
[A20]
[A21]
[A22]
[A23]
[A24]
[A25]
[A26]
[A27]
[A28]
[A29]
OK!!
RAM Pattern Test :
Writing ...
0x44332211,
0xA5A5A5A5,
0xA5A5A500,
0xA500A500,
0xA5000000,
i found out that i was flashing the wrong chip type. My phone´s details are now that i have a MTK 6582 chip. But in the 626g is usually a MTK 6592 chip. So, i cant flash the original firmware with SPFlash tool because of the wrong chip.
Is there a chance to fix it? Maybe change something in the scatterfile?
69 times viewed and nobody have any idea?