Related
So after trying Xiaomi EU, MiGlobe Rom and Android Q Beta
I decided to flash back to MIUI 10.3.8 via fastboot
Somehow my front camera won't open properly, it kept saying "Can't open front camera, please calibrate".
And when I press Calibrate, popup cam goes up and down 3 times in a row and says "Can't calibrate".
Any idea how to fix this?
EDIT: Must be the fastboot rom I downloaded. Other rom's front cam worked fine...
I am having same issue. Initially I thought it was hardware problem.
But I noticed it seem to be related to software.
Took few restart of camera app and sometime phone restart, for it to work
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
LogicalMaverick said:
same problem here
just came from Android Q beta from Mi Global Home, and I decided to go back to MIUI china. The problem occurs after flashing the v10.3.15 china ROM.
Any ideas to solve this?
Click to expand...
Click to collapse
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Robbo.5000 said:
Did you install a fastboot ROM or go straight to the latest recovery ROM. If you went for the recovery, then I suggest installing the most recent fastboot ROM, then upgrade to the latest recovery ROM.
Click to expand...
Click to collapse
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
What's LR?
degeaba1981 said:
I've got same issue, coming from Android Q beta. I've put the Indian rom and I thought that this is the issue.
---------- Post added at 08:53 PM ---------- Previous post was at 08:50 PM ----------
What's LR?
Click to expand...
Click to collapse
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Robbo.5000 said:
It's referring to the LR.Team TWRP
https://forum.xda-developers.com/k20-pro/how-to/lr-team-wzsx150s-twrp-status-phh-gsis-t3939325
Click to expand...
Click to collapse
Problem solved! I flashed via miflash the Chinese rom, in fastboot and the front camera was working. Then I've put the Indian global version and front camera is working fine now.
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Ekalous said:
Once done!! My device can't use rom (EU, Miglobe, Indian fastboot rom) except China Stable !! Boot is used for the first time, reboot the device it will stuck into TWRP (eu, miglobe), Mi Recovery. Format data can re-enter the system but continue to reboot the device and it will be similar. Go to the log section of TWRP, the whole message is unable to find crypto footer , erros opening data/data.... !! I do not understand which step I made wrong !! Sr for my bad Englosh
Click to expand...
Click to collapse
I have the same problem. I'm trying to solve it but nothing for now!
LogicalMaverick said:
I wiped all partitions via LR. Team TWRP, and flashed the most recent fastboot ROM. Still doesn't work
after analyzing for like 3 hours, I noticed that all sensors are also not working (Gyro, Accel, Proximity, etc). I googled it and found the solution. Here it is:
by flashing persist.img (from the extracted latest fastboot ROM) to persist partition via LR. Team TWRP, all sensors are working fine. Even the camera's calibration now works perfectly
Click to expand...
Click to collapse
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
topaloglu321 said:
How did you manage to flash persist.img file? Just one file from the ROM or like in the link below?
I'm getting the same problem with my Redmi K20 (Not Pro) here
http://en.miui.com/thread-478922-1-1.html
Click to expand...
Click to collapse
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
znsvs123 said:
what if there is no "persist" partition in selection menu. how to make those partition, ive tried using adb terminal by using dd command, but bear no fruit.
thanks for the answer
Click to expand...
Click to collapse
You can't show them up. The only way is to change TWRP, hoping that is supported
thelegoboy said:
In L.R TWRP, we can flash other kinf of partitions (like persist, for example)
I always used the "persist.img" file of the stock ROM (installed via fastboot). I trasfered it from my computer with ADB. The command is:
Code:
adb push [I]the_path_where_you_stored_the_persist_file[/I] /sdcard/
To to that, go on "Install"->"Install image"->Now choose the persist.img file-> Choose the "persist" partition -> "Flash image" -> Reboot
Then just wait for the MIUI to tell you to calibrate the camera, now it should work!
Click to expand...
Click to collapse
I'll try this thank you.
thelegoboy said:
You can't show them up. The only way is to change TWRP, hoping that is supported
Click to expand...
Click to collapse
thanks, not all of twrps are built equally. :good::good::good:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
i fixed that problem just flashing chinese.rom via miflash and.camera pop up working again
sagar.anits said:
Facing issues with camera pop up calibration and sensors (proximity) after reverting back to stock miui v10.3.3 (Raphael India through fastboot & zip) after flashing android Q Eu rom.
when flashing persist.img through fastboot it gave write protected error. Through LR TWRP, it didnt show any errors but problem is not solved.
I couldnt flash chinese rom through fastboot, faced error saying expected device is Raphael not Raphaelin.
Click to expand...
Click to collapse
Same problem here
RAJIB AHMED0077 said:
Same problem here
Click to expand...
Click to collapse
try flashing 10.3.16 chinese rom via fastboot yesterday i flash that rom and it fix that problem in my k20 Pro
Hello!
Suddenly my Accelerator and Gyroscope stopped working and i cant figure out why. I downloaded another file persist.img and succesfully flashed via recovery but after reboot, those sensors arent still working. Every other sensor works (light sensor, proximity etc...) and ad this point i dont really know what to try, do you have any suggestion?
Persist if I remember only can be flashed using TWRP and mounting persist partition.
Are you done the flash in that way?
rocalino said:
Persist if I remember only can be flashed using TWRP and mounting persist partition.
Are you done the flash in that way?
Click to expand...
Click to collapse
I have flashed trough recovery selecting persist.img and checking persist box
Check out my thread, I fixed there light sensor problem.
Make sure you take your persist.img file from latest fastboot rom.
Light sensor stuck after QMMI mess
Hi guys
Sorry for my bad English
My device was running Android 10
miui 11
After I accidentally used an application to raise the screen frequency to 84Hz
The devics did a reboot and then stopped on the fastboot logo
I tried to enter recovery mode but was back to fastboot mode
I tried to flash twrp via adb and fastboot but the method did not work and the device returned to fastboot mode
Finally I downloaded the ROM file global Version Android 9
miui 11 and when i flashed the system via "xiaomi flash tool " the operation was successful until it reached the end of the process it showed me an error and the flash failed
I restarted the process and noticed that the flashing process gives me the error when the download arrives at "flashing boot"
I searched a lot for the version of Android 10 miui 11 but I did not find
What is the problem!
Can anyone explain what the problem is?
Thank you very much
Edit : solved With the help of my friend and brother @tsongming thanks bro
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
tsongming said:
You likely damaged the phone, myself and others have posted numerous warning about flashing mods to increase the refresh rate.
I would recommend trying the Flashall.bat method.
Follow my instructions here : https://forum.xda-developers.com/showpost.php?p=80825243&postcount=2
Click to expand...
Click to collapse
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
ahmadbasher said:
When i flash device with edl mod in xiaomi mi tool i got these error
What i can due
Click to expand...
Click to collapse
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
tsongming said:
See this thread : https://c.mi.com/thread-2121755-1-0.html
Also, I read about some people getting past these recent issues by using a USB hub extender. These decrease the amount of power to the port which may be causing a conflict. Try other ports and only use a usb 2 port. Further, I would recommend temporarily disabling firewall and antivirus if all else fails. Worst case use another computer.
If this helps come back and let us know what finally resolved it.
Click to expand...
Click to collapse
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
ahmadbasher said:
I solved and my device life agin
I flash these rom http://bigota.d.miui.com/V9.5.11.0....EACNFA_20180703.0000.00_8.1_cn_64c55c8438.tgz
With mi flash tool older version (2016)
In fastboot mode
But now i need back to global rom and after i flash latest global rom in fastboot the device bricking again
And stay in fastboot
What is the problem
Click to expand...
Click to collapse
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
thanks for replay bro i will tri it
tsongming said:
You still have encryption on your device, use the tool all in one and install TWRP ( You may need to use a different/maybe older computer, I think possibly windows 10 is part of the issue. ( Because I have had this exact issue that you are having)
Install the tool, and update ADB but not the tool itself, there will be a popup, asking to update. ignore it or the update will be flagged a sbeinga virus ( Actually a Windows issue) However, yes the program is unsigned.
Use all in One tool to remove encryption from device and flash TWRP
Boot to recovery, immediately flash root, Flash Su if you must.
Reboot to recovery, then flash a recovery rom. the boot to system , may take up to 10 minutes.
use ports from the back of the PC and you may need to use a usb hub.
Click to expand...
Click to collapse
I tri it and no change
Again reboot to fastboot
ahmadbasher said:
I tri it and no change
Again reboot to fastboot
Click to expand...
Click to collapse
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
tsongming said:
While its possible that you have a hardware issue. Unless the phone has been exposed to moisture, or exposed to a great deal of force I doubt that you have a hardware problem. Again, I too have had a similar issue, it's just took a while to finally get it working, in my case my computer was part of the problem, since you have fastboot the number one goal at the moment should be with getting TWRP recovery installed, and then root.
Did you happen to make any TWRP backups?
Hopefully so, specifically if you have a TWRP backup that includes the persist image files, you need to try flashing those to the persist partition. If you can successfully restore the persist image then try the flashall.bat method again.
Another option is to use QPST, but try the above first.
Edit
Finally, After re-reading you initial post. I had forgotten that you attempted to improve the refresh rate of the display. If all you can get is fastboot after following all of the steps that I have mentioned than I am certain that you have a burned chip. Ignore the people who claim that you can't fry the chip they have no idea what they are talking about. The chip can absolutely be fried. It's still worth trying a few more times, you could have just simply corrupted partition images. When you flash the stock rom, or even when using the flashall.bat method not every partition is over written.
@ahmadbasher
When you flashed the file to increase the refresh rate you likely overwrote a partition called DTBO, See if you can flash a Mi8 DTBO image to the DTBO partition. If you have the full recovery backup, you can extract the file from there. i need to research exactly how that file works and I will try to help you will getting the image if you don't have it in a backup.
Click to expand...
Click to collapse
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me ? But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Is it possible that this is part of the problem..!
I can't check it
@tsongming
ahmadbasher said:
All thanks to you my friend, I do not know how I can give all thanks and gratitude to you for helping me But my friend unfortunately I do not have a backup of it Will wait for you
Thanks again
Click to expand...
Click to collapse
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
ahmadbasher said:
Is it possible that this is part of the problem..!
I can't check it
@tsongming
Click to expand...
Click to collapse
No that is just encryption, if the issue was related to encryption the flashall.bat method would have resolved it.
If you had a persist issue, you would see specific messages about not being able to mount the persist partition.
tsongming said:
No problem, after reading some various post on GitHub, CNX, and source android.com, I found out that the Mi8 DTBO is in the boot. Image.
So you should be able to flash a boot image, root, and then recovery and hopefully boot to TWRP.
If that doesn't work then send me a pm and I will share my personal dtbo with you privately. But again you shouldn't need mine since dtbo is nothing more than the device tree and the boot image should suffice, because it has the exact same file.
ADB command : fastboot flash boot c:\boot.img
Click to expand...
Click to collapse
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
ahmadbasher said:
Thank you I will now try to do this
Yesterday I flashed the pixle rom on the device and I took off the device without problems but every period of time the device was doing a reboot, I do not know if it is the problem of the ROM or there is something wrong with the device
I tell you so that you know only that
Now I will flash the latest version of miui 11 android 9 global version, and flash the boot.img and then Root and finally Recovery True ?
Click to expand...
Click to collapse
Hey sorry for the delay in getting back to you, I sent you the link for the file via PM.
Also, I would strongly suggest using the stock miui initially. Just until you know it's resolved. Also while Miui is installed make a full TWRP backup and save it to your desktop. This way you always have a full backup to resolve any serious issues.
Then once you know everything is working as it should then go back to what you prefer..
For the record this issue was solved. Anyone reading this, make sure that you have a full working TWRP backup of your working device, it will save you a lot of headaches. The solution for the refresh rate is issue is restoring stock DTBO, and then flashing Miui Stock.
I recently bricked my RN10s and then had to flash stock ROM using the SP flash tool now the sensors are not working properly.
The device turns its screen on and off because it thinks it's being picked up.
The sensors used by google maps show that I'm rotating constantly.
I am new while flashing on A/B partitions and thus ended up bricked, any help will be highly appreciated. I was trying to flash pixel 4 android 13 GSI A/B and also tried dot os but it seems like my device's flash memory after the brick is not working properly because it does not boot into custom twrp by the command Fastboot boot TWRP.img.
looking forward.
flash stock rom and done
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
dequr said:
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
Click to expand...
Click to collapse
I think it might be due to corrupted persist partition, I never custom romed a device but have been researching for my RN10s and I read that persist contains the sensor data control and l1 certification that's why you need to back it up in case it corrupts. Sadly you can't flash persist from the internet since it's unique to every phone if you flash it you loose l1 certification forever but get back sensor functions (I am not sure about sensor functions returning)
Also there is a tool to fix corrupted persist so do research it but whatever you do make sure you are 100% certain it's what you want changes to persist are permeant (except if you backed up persist before the brick in which case just flash the persist backup)
V.I: as I said I never flashed a device and don't know much about it this is what I read through reddit and research, take it with a grain of salt and do your own research aswell
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
dequr said:
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
Click to expand...
Click to collapse
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Okay will try this now truly appreciate the support thx. Tho the phone is working quite better by time apart from the sensors.
The degree sensor or smt like that is just increasing to 360 and then will start from 0 again
killer_v41 said:
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
Click to expand...
Click to collapse
A
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Any suggestions form where to download because there are lot of sites available
This is the sensor data and as you can see Orientation sensor along with the rotations third value and the z axis of gyroscope and accelerometer isn't working well so ill re-flash with the first miui this phone had and apply updates on it hopefully it will fix the errors.
Your browser is not able to display this video.
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
alright so I was going thru the images and I couldn't find any persistence in both 13.0 and 12.5 but now as I am now the question is how are the x and y axis keeping their value correct while z isn't so will tho ask for a persist file but just curious how is it detecting sensors then ??
dequr said:
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
Click to expand...
Click to collapse
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
killer_v41 said:
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
Click to expand...
Click to collapse
Yea I discovered the fastboot ROM didn't have persist.img and I've stopped trying because the gsi has detected it and some how some things have been fixed I've also seen. File named gsi_persist_data in /data nvr opened it but gyroscope while gaming doesn't stop and raise to wake works.
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.