Hovatek Forum DEVELOPMENT Android No Name Mate 39 recovery help? MT6580 3.10.72
Can't login? Please, reset your password.
Hovatek is recruiting! Apply Now


No Name Mate 39 recovery help? MT6580 3.10.72

No Name Mate 39 recovery help? MT6580 3.10.72

Pages (2): Previous 1 2
Bitsurah
Bitsurah
Bitsurah
Enthusiastic Member
13
11-04-2020, 12:29 PM
#11



(11-04-2020, 09:32 AM)X3non
(10-04-2020, 03:42 PM)Bitsurah Yeah I replaced all the mount points and all the directories with the correct ones and now I have an unable to find crypto footer error. I can't get into the recovery anymore. It can't mount the data partition. And it just keeps rebooting into twrp, twrp runs the openrecoveryscript, fails because it can't mount the data, reboots again and again. I'm pretty sure if I could format the data partition I could break the encryption and get in but the fastboot command doesn't work. I tried unpacking the system.bin that I made a backup of but I can't. Not sure if it's corrupted or if AIK just doesn't work with it. Any ideas?

report twrp using the mtk porting tool
Now I can boot into recovery again but it can't mount anything. It always prints out "Failed to mount '/partition' (Invalid Argument)". And it just repeats that error with all the partitions. Not just /data. And it still can't even detect that they're present so still no wiping or repairing "E: Primary block device '/dev/block/platform/mtk-msdc.0/11120000.MSDC0/by-name/userdata' for mount '/data' is not present". Also checked if all the mount points were correct and they seem to be and using the File Manager on TWRP I checked the directories and they all seems to be correct and I found the partitions under them.
This post was last modified: 11-04-2020, 01:04 PM by Bitsurah.
X3non
X3non
X3non
Recognized Contributor
22,062
11-04-2020, 07:19 PM
#12
(11-04-2020, 12:29 PM)Bitsurah Now I can boot into recovery again but it can't mount anything. It always prints out "Failed to mount '/partition' (Invalid Argument)". And it just repeats that error with all the partitions. Not just /data. And it still can't even detect that they're present so still no wiping or repairing "E: Primary block device '/dev/block/platform/mtk-msdc.0/11120000.MSDC0/by-name/userdata' for mount '/data' is not present". Also checked if all the mount points were correct and they seem to be and using the File Manager on TWRP I checked the directories and they all seems to be correct and I found the partitions under them.

what's the current mount points within fstab in this new twrp?
have you tried changing it to https://www.hovatek.com/forum/thread-329...#pid190136
Bitsurah
Bitsurah
Bitsurah
Enthusiastic Member
13
11-04-2020, 09:31 PM
#13
(11-04-2020, 07:19 PM)X3non
(11-04-2020, 12:29 PM)Bitsurah Now I can boot into recovery again but it can't mount anything. It always prints out "Failed to mount '/partition' (Invalid Argument)". And it just repeats that error with all the partitions. Not just /data. And it still can't even detect that they're present so still no wiping or repairing "E: Primary block device '/dev/block/platform/mtk-msdc.0/11120000.MSDC0/by-name/userdata' for mount '/data' is not present". Also checked if all the mount points were correct and they seem to be and using the File Manager on TWRP I checked the directories and they all seems to be correct and I found the partitions under them.

what's the current mount points within fstab in this new twrp?
have you tried changing it to https://www.hovatek.com/forum/thread-329...#pid190136
Tried copying and pasting the code again into fstab and now I'm back at https://www.hovatek.com/forum/thread-329...#pid190169

Reporting using MTK Auto Porter didn't work
X3non
X3non
X3non
Recognized Contributor
22,062
13-04-2020, 09:19 AM
#14
(11-04-2020, 09:31 PM)Bitsurah Tried copying and pasting the code again into fstab and now I'm back at https://www.hovatek.com/forum/thread-329...#pid190169

Reporting using MTK Auto Porter didn't work

get the mount points of your device using the guide @ https://www.hovatek.com/forum/thread-11203.html
then apply those mount points into etc/*.fstab in your twrp
Bitsurah
Bitsurah
Bitsurah
Enthusiastic Member
13
13-04-2020, 10:37 PM
#15



(13-04-2020, 09:19 AM)X3non
(11-04-2020, 09:31 PM)Bitsurah Tried copying and pasting the code again into fstab and now I'm back at https://www.hovatek.com/forum/thread-329...#pid190169

Reporting using MTK Auto Porter didn't work

get the mount points of your device using the guide @ https://www.hovatek.com/forum/thread-11203.html
then apply those mount points into etc/*.fstab in your twrp
Okay I did that and it reduced the amount of errors I'm getting. It seems to be detecting all the partitions now. I've attached the 4 errors that I'm still getting as an image file. The first one will probably be fixed once I reset the data partition but yeah. Can you help me with the rest? It always starts the script and reboots after this log instead of booting into twrp and then does it again
This post was last modified: 14-04-2020, 12:43 AM by Bitsurah.
Attached Files
.jpg
IMG-20200413-WA0000.jpg
Size: 95.57 KB / Downloads: 5
X3non
X3non
X3non
Recognized Contributor
22,062
14-04-2020, 10:12 AM
#16
(13-04-2020, 10:37 PM)Bitsurah Okay I did that and it reduced the amount of errors I'm getting. It seems to be detecting all the partitions now. I've attached the 4 errors that I'm still getting as an image file. The first one will probably be fixed once I reset the data partition but yeah. Can you help me with the rest? It always starts the script and reboots after this log instead of booting into twrp and then does it again

zip and upload the twrp then post the link
Bitsurah
Bitsurah
Bitsurah
Enthusiastic Member
13
14-04-2020, 12:58 PM
#17
(14-04-2020, 10:12 AM)X3non
(13-04-2020, 10:37 PM)Bitsurah Okay I did that and it reduced the amount of errors I'm getting. It seems to be detecting all the partitions now. I've attached the 4 errors that I'm still getting as an image file. The first one will probably be fixed once I reset the data partition but yeah. Can you help me with the rest? It always starts the script and reboots after this log instead of booting into twrp and then does it again

zip and upload the twrp then post the link
Here is the currect recovery:
https://drive.google.com/open?id=1Dm4JuA...cfFhi1QMKZ
X3non
X3non
X3non
Recognized Contributor
22,062
14-04-2020, 07:24 PM
#18
(14-04-2020, 12:58 PM)Bitsurah Here is the currect recovery:
https://drive.google.com/open?id=1Dm4JuA...cfFhi1QMKZ

not sure how you got the twrp to keep looping that script, might be due to allowing twrp to modify system partition. but most of the errors on that screen if not all seem to come because userdata isn't mounted
two things, either reflash this same recovery and when prompted by TWRP whether to leave system partition unmodified, tick keep readonly OR retry using the twrp you got from the v1.4 tool with the newly found mount points

BTW in the fstab you modified, there's a lot of mistakes, mostly from the mount points (it'll surely lead to errors if you ever tried to backup or restore). too many to list so i'm leaving an edited one here. you can compare to find out what was changed
This post was last modified: 14-04-2020, 07:27 PM by X3non.
Attached Files
.txt
recovery.fstab.txt
Size: 1.96 KB / Downloads: 18
Bitsurah
Bitsurah
Bitsurah
Enthusiastic Member
13
14-04-2020, 07:47 PM
#19
(14-04-2020, 07:24 PM)X3non
(14-04-2020, 12:58 PM)Bitsurah Here is the currect recovery:
https://drive.google.com/open?id=1Dm4JuA...cfFhi1QMKZ

not sure how you got the twrp to keep looping that script, might be due to allowing twrp to modify system partition. but most of the errors on that screen if not all seem to come because userdata isn't mounted
two things, either reflash this same recovery and when prompted by TWRP whether to leave system partition unmodified, tick keep readonly OR retry using the twrp you got from the v1.4 tool with the newly found mount points

BTW in the fstab you modified, there's a lot of mistakes, mostly from the mount points (it'll surely lead to errors if you ever tried to backup or restore). too many to list so i'm leaving an edited one here. you can compare to find out what was changed
Yeah that's a dead end. TWRP isn't even giving me a prompt to modify the system partition. It just runs the script and then reboots. And that recovery already was from the v1.4 tool. I think that's enough. All this work isn't worth it for a phone that's trash anyway. But I thank you so much for your time. I've learned a lot. Like never buying a phone without a brand again. You've been very kind to help me. I won't ask anymore of your time. Maybe I'll work on it some other day just for fun.

Thanks again. You're awesome
X3non
X3non
X3non
Recognized Contributor
22,062
15-04-2020, 09:54 AM
#20



(14-04-2020, 07:47 PM)Bitsurah ...And that recovery already was from the v1.4 tool...

oh my mistake
true that it's from the v1.4 , i actually meant to try a different one like from the v1.0 tool i.e if you're still up for it
Pages (2): Previous 1 2
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram