Hi All,
I need the persist.img file for Mi Pad 4 plus to flash on my device. Can anyone make a backup of the image file and share it to me? I could not find the image file from the Mi Pad 4 fastboot rom. I need the file to possibly fix my touchscreen issues.
Please help
Thanks ~
File persist
Hello, any solution? I also need the file. I have a problem with the automatic rotation on the MI Pad. It rotates in the wrong direction. Need help
You'll have to revert to stock to get a proper pwrsist.img again. Maybe you can extract the persist partition from the stock firmware file, bit I'd do a complete revert to stock, make sure everything works and then flash your custom rom again (if any).
Related
Hola Devs,
Currently I own Mi 5 in which I used to have Lineage os 14.1. But after the recent update i.e Lineage-14.1-20180110 nightly gemini, all of the sensors got pissed of except fingerprint sensor.
Initially I thought it may a hardware problem, but after brown through the root files, I got to find that all my sensor related files are missing from the Persist partition. So I downloaded the fastboot rom the official website and flashed through Mi Flash Tool in both Fastboot and EDL mode. still the problem remains as it is. While flashing, the tools is not even considering the Persist.img file. BTW I even tried to flash through Fastboot cmd, and it is showing error as the partition is write protected, neither the partition is erasing nor is flashing
Can I get any kind of solution??
Or can you provide me the persist flash bat file formatting or flashing the persist Img file.
Or can you guys provide me sensor related files to be placed wherever it is necessary..
BTW wifi Bluetooth nfc fpc all are working except Gyro sensor and Proximity sensor. And also it is not at all showing in Engg mode too(*#*#6484#*#*)
thank in advance
It's the persist partition problem.
You could refer to this thread
http://www.miui.com/thread-6788019-1-1.html
Unfortunately, the language is Chinese. Please use the translator if you can't read it. Of course, you could ask me how to do it too.
Sorry, I am a Chinese, so I may have made some mistakes in grammar. Hope you could understand what I am saying ?
Ask someone to backup him persist with zcx recovery, then restore yours with it and problem solved.
I had exactly the same problem as you and that fixed mines.
Greetings
Hi everyone,
Just got the nokia 1 - TA-1060
Would anyone be interested in me creating a stock system flasher for twrp? (may be able to flash the files via fastboot as well)
I already captured the system.img, so boot.img and vendor.img should be easy to capture.
let me know if you guys want this and Ill build a recovery zip
sooti said:
Hi everyone,
Just got the nokia 1 - TA-1060
Would anyone be interested in me creating a stock system flasher for twrp? (may be able to flash the files via fastboot as well)
I already captured the system.img, so boot.img and vendor.img should be easy to capture.
let me know if you guys want this and Ill build a recovery zip
Click to expand...
Click to collapse
Yes its very much required... The Q&,A forum is filled with people with no booting ROM... You'd be doing them a huge favor...
sooti said:
Hi everyone,
Just got the nokia 1 - TA-1060
Would anyone be interested in me creating a stock system flasher for twrp? (may be able to flash the files via fastboot as well)
I already captured the system.img, so boot.img and vendor.img should be easy to capture.
let me know if you guys want this and Ill build a recovery zip
Click to expand...
Click to collapse
Is the processor of TA-1060 and TA-1066 the same i.e MT6737M?
No stock flashable rom with pc use?
Really?
This device has very poorly built OS. It cant even handle even 1 background app. seriously?!! I have used 1 GB ram phones before but wasn't expecting this blunder from Nokia.
I tried to backup TA 1066 rom with Mtkdroid tools and but somehow the backup option was grayed and it says that "- Unknown ROM structure, backup NOT possible! ". Don't know whats wrong with this. Maybe go edition has different rom structure.
Let me know if there is any other way to take backup.
So I have bricked my phone here. It's on the boot loop. Wanted to enable camera2api but some how messed up. Now when i was trying to flash the stock ROM it was coming up with this error "can not found file flash_all_except_storage.bat . Now how can i deal with this?
Unzip your flash file directly on to the desktop and do not let it create another file with the same name.
of course ... it has been double copied(wrong) the archive.... you do not see it?
sry for english
Hello! I would like to root my Realme c25s [RMX3195_11_A.19] phone. I can not find the necessary files to install twrp. Named Vbmeta.img and Recovery.img (Recovery is the TWRP firmware itself, but I couldn’t find the Vbmeta.img file ANYWHERE on the Internet that matches my firmware version). As far as I understand, both files must be of the same version (A.19 in my case), otherwise it is possible to turn the phone into a brick. If you have experience flashing this device of the same assembly as mine, or if you know how to do it, please attach ALL the files that you used to flash. Thank you!
Metro1919 said:
Hello! I would like to root my Realme c25s [RMX3195_11_A.19] phone. I can not find the necessary files to install twrp. Named Vbmeta.img and Recovery.img (Recovery is the TWRP firmware itself, but I couldn’t find the Vbmeta.img file ANYWHERE on the Internet that matches my firmware version). As far as I understand, both files must be of the same version (A.19 in my case), otherwise it is possible to turn the phone into a brick. If you have experience flashing this device of the same assembly as mine, or if you know how to do it, please attach ALL the files that you used to flash. Thank you!
Click to expand...
Click to collapse
your vbmeta can be found in the firmware file (ofp)
I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!
Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.
newboihere said:
I have bricked several times the phone trying to install lineageOS 20. every time I manage to recover the phone using mtk and then a clean and full reset to stock images from Mi Flash.
I have tried flashing the GSI rom through fastbootD (after installing TWRP) and also via TWRP>install>image>myGSIROM
Any idea about how could be flashing the system partition causing the NV data corruption? Any other possible cause of the corruption?
Thank you!
Click to expand...
Click to collapse
I was able to boot other GSIs as well.
but I'm using the evo x custom rom published on the telegram group.
There are plenty of smarter people out there than me, so I encourage you to take a look there too.
kousuke5555 said:
Hello.
I was able to install it without any problems.
light version lineage-20.0-20230417-UNOFFICIAL-gsi_arm64_gN.img
nvdata mac address is also fine.
Installing GSI is very simple.
Install without TWRP.
Please use the latest SDK Platform Tools.
Click to expand...
Click to collapse
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)
newboihere said:
Thank you!
I have been checking the issue at the lineage thread and I think the reason for losing the mac and sometimes also end up with a vndata corruption is that I changed the size of super partition but did not updated the scatter file at MiFlash, so all the flashing resets afterwards might be compromised (although MiFlash does not complain). Another reason is that when I changed the size I might have also changed some flags or something like that, I will check later.
By the way, I would really appreciate if someone could share the original gpt table (to be restored with gdisk or gparted)
Click to expand...
Click to collapse
I don't know what your situation is.
It seems that it can be solved by flashing the firmware with sp flash tool using the auth bypass tool.
Isn't gpt table a scatter file in the firmware? I think you can get it by extracting the .tgz.
If you use the sp flash tool, be sure to select "Download Only Mode". Do not choose anything else.
There seems to be an error in "combo_partsize_check" when flashing with miui13rom. Please rewrite the corresponding part in the scatter file to false with Notepad etc.
There seems to be a tool that makes bypassing and flashing easier, such as "act unlock tool", so use whatever you like.
If the situation cannot be resolved with sp tool
I can't solve it with my knowledge level.