Related
I have the T-Mobile OnePlus 8. SIM/BL unlocked, converted to international firmware. FP worked the whole time during the conversion. Had issues with the modem, but that's a given an was sorted out.
I heavily rely on Google Pay because I'm lazy and rarely carry my wallet with me. I ended up installing EdXposed to see what has changed since the last time I used it years ago. There was a XStadia module that came in handy so that I could use Stadia on my data connection instead of WiFi. After using it for some time, I decided that having Xposed wasn't worth breaking SafetyNet over, so I uninstalled. Well for some reason, it didn't uninstall probably or something happened along the way that SN was still broken. So I figured the only way to fix is to factory data reset. Bad idea. These devices nowadays aren't like what they used to be. Ended up with multiple CrashDump screens. Ran into a crap ton of issues so I ended up used my the MSM tool to go back to the stock T-Mobile firmware, using the 10.5.7 fastboot ROM to go back to international, etc.
When I went back to international again, I noticed that my fingerprint sensor wasn't working so I followed the guide found here: https://forum.xda-developers.com/oneplus-8/how-to/guide-fix-persist-img-loss-finger-print-t4126455 The only thing I wasn't able to do was downgrade to an earlier OOS like 10.5.4 mentioned in the guides OP due to the phone not letting me. I tried the MSM 10.5.4 tool, and the 10.5.4 fastboot ROM. Both didn't work and gave me errors (I'm guessing because it's a branded device and certain critical partitions can't be overwritten). So I ended up pulling my broken persist from the T-Mobile stock rooted firmware, fastboot flashed 10.5.7, and went from there.
After some time, I finally had a working FP. Thanks again @antnyhills. When it was working, I thought that every time I used the FP, it gave me more errors than it actually unlocked the phone. So, I thought I'd be a little curious and see if doing the FP tests again would fix it. IT DID NOT. I ended up breaking it so bad, that now I get an error saying "fingerprint hardware not present". When I go to setup a new fingerprint, it says "enrollment was not completed. Fingerprint sensor error, please try again". If I go back to dismiss the error, the FP is still present, and when I press on it, the circle lights up, it just doesn't vibrate or register anything.
So, I followed the guide again. Again, nothing. Now I'm sitting here and nothing works. Camera doesn't work (black screen when opening), flashlight doesn't work, and I'm sure there's a few other things, just didn't mention. What do I do now? Get a hold of OnePlus and see if they'll replace my device? Is there a way to erase the Persist.img from the device and reflash it again somehow?
TL;DR: FP sensor broken, camera broken, after following broken persist.img guide.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
If you get it working again, the FP sensor just as accurate as it was out of the box because you are using the factory calibrations.
When you set up your fingerprint it is not accurate at first but over time in learns you fingerprint even more and becomes more accurate and fast.
antnyhills said:
Make sure you are using your original persist.img from your backup the first time you did this guide to transfer the two folders. If that fails. Flash your the same original back up persist.img and start the guide again.
Click to expand...
Click to collapse
I did, multiple times to no avail. How do I go about flashing the persist.img? There are only a few options in TWRP. Two super, recovery, and boot.
I know, I remember reading somewhere that it learns every time. I should've just left it alone and let it do its thing, but of course I had to go and mess things up.
Is my flashlight and camera not working because of persist files?
When I got it working again using your guide, when I started tinkering around, even though my FP was working, when I rebooted, it said"fingerprint hardware not present". Now all of the apps that use FP don't even ask me if I want to use FP like it's not even there .
TheKnux said:
I did, multiple times to no avail. How do I go about flashing the persist.img?
Click to expand...
Click to collapse
Go to the bootloader.
Code:
fastboot reboot fastboot
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Code:
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
Example:
Code:
fastboot flash persist C:\user\example\desktop\persist.img
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
antnyhills said:
Go to the bootloader.
This will take you to fastbootd. It will look like your recovery. You must have stock original recovery installed. TWRP will not work.
Example:
Make sure you are flashing the persist.img from your original time you performed this guide. This will take you back to were you where before you ever performed the guide.
Then follow the guide one more time, follow it VERY CAREFULLY as there is a lot to go wrong.
Best of luck!
Edit: Also, I would assume your camera/flashlight broke because of your persist partition. Hence Why we are going to start from scratch with your original broken persist.img
Click to expand...
Click to collapse
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
TheKnux said:
I'm not a noob at rooting/ROMing. I'm just new at doing this kind of stuff. Messing with critical files in the root directory. I appreciate you chiming in and helping me with this. I'll do what you said and report back. Appreciate everything you've done, including you helping me with this.
Click to expand...
Click to collapse
No worries. Eager to hear your update.
antnyhills said:
No worries. Eager to hear your update.
Click to expand...
Click to collapse
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
TheKnux said:
target reported max download size of 805306368 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.703s]
writing 'persist'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.718s
That is my error I get when following your instructions.
Click to expand...
Click to collapse
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
antnyhills said:
Make sure you do
Code:
fastboot reboot fastboot
Like I mentioned it should look like the stock recovery. When you do that does it take you to your stock recovery?
If you have discord, I'll PM you a link, might be easier to communicate.
Click to expand...
Click to collapse
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
antnyhills said:
Boot phone
Put persist.img on the root of your 'sdcard'
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
reboot
Click to expand...
Click to collapse
Okay, that seems to have worked. I did that while on T-Mobile firmware. I just fastboot flashed the 10.5.7 international firmware, updating to 10.5.9 via OTA now, when it reboots, I'm going to install TWRP and Magisk, and push the persist.img again using the command you gave me once more for good measure then fix FP using your guide. On the flip side, once I pushed the persist.img using your command, my flashlight and camera works again, just not FP, yet. I'll report back after following your guide. Thank you again.
TheKnux said:
So to my knowledge, stock recovery is the screen with the OnePlus logo, some chinese words, and English and Fastboot is the screen that says the SoC name, device state, etc.
I even tried "fastboot flash persist_critical persist.img" and it didn't work. Also, fastboot reboot fastboot doesn't do anything. Fastboot reboot bootloader sends me to fastboot. Using Windows 10/PowerShell.
I do have Discord but it runs like crap on my PC (old laptop) and since my phone is down currently, this is the only way to talk.
Click to expand...
Click to collapse
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
starcms said:
You need to have the latest version of adb and fastboot from Google on your PC for "fastboot reboot fastboot" to work and be able to access fastbootd.
https://developer.android.com/studio/releases/platform-tools
Fastbootd is something new and different from bootloader. It allows flashing to all partitions (required due to dynamic partitioning in Android 10). However, it looks very similar to stock recovery (it actually uses stock recovery which is why it won't work with TWRP flashed). "fastboot reboot bootloader" sends you to bootloader, which is no longer the same as fastboot.
However, the instructions posted by @antnyhills will also work perfectly fine for restoring persist. That's the method I use (personally I try to avoid fastboot flash at all on this phone)
Your problem is you completely corrupted your persist.img. That's why you have a backup . Or now you'd be without sensors, camera, flashlight, etc until someone posted theirs but then you would never be able to fix fingerprint.
Once you have fingerprint working again, take a new backup of persist. Then no need to fix it again in the future if it gets messed up. Simply restore it.
Click to expand...
Click to collapse
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device. ?
TheKnux said:
I tried Googling for the latest adb/fastboot drivers but I already spent half the day restoring my persist and fixing my FP. I thought there would be a flasher like the 1.4.2 drivers but it wants me to install the sdk and install it through there. Not my top priority right now, next time I'm on my pc though I will for sure. The method @antnyhills told me to do to push the persist worked great, followed his guide again, fixed FP, and backed up persist with FP and all sensors working. Stored it in two places so I don't accidentally delete them lol. The updated drivers you're mentioning, that'll allow me to flash critical partitions in case I mess something up again next time?
Huge thanks to @antnyhills for coming in here and helping me out, and to you for giving me your two cents as well. I was so tempted to be a Karen and get T-Mobile and OnePlus on the phone to RMA my device.
Click to expand...
Click to collapse
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
starcms said:
It's not updated drivers. It's an updated version of adb and fastboot that fully supports all the new commands needed (such as "fastboot reboot fastboot"). I had provided a link. Just download and unzip to your adb directory on your PC and select replace all files when copying.
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Where would the adb directory be if I used the "adb and fastboot installer for windows" (or whatever it's called) found here on XDA? I'm guessing it's years old. I think it said version 1.4.2 or something.
Also, are you or @antnyhills on Telegram at all?
what was the final of this, i have the oneplus8 tmobile, and i want to convert to globla, but this issue scared me
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Kollachi said:
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Click to expand...
Click to collapse
Thanks but I can't do this, as i can't access system settings. Will it work with Oxygen updater app ?
EDIT: Oxygeon updater, also uses system settings...
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Thanks. Will try this if the above method doesn't work first.
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Benfran said:
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Click to expand...
Click to collapse
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Qnorsten said:
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Click to expand...
Click to collapse
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Benfran said:
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Click to expand...
Click to collapse
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Qnorsten said:
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Click to expand...
Click to collapse
No luck.
I flashed all the .img and rebooted correctly. As before, everything works fine , except System settings (icon doesn't even appear). So i can't even check what version i have installed...
There was one issue flashing in fastboot though...only with 3 of the .img files :
reserve.img
xbl_config_lp5.img
xbl_lp5.img
With these 3 i got an error, the same one for all 3:
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Any idea as to why i'm getting this error and do you think this is related to the settings error ?
Thank you for all the help !
It finally worked !
I disabled the only magisk module i had active, and again flashed all the .img (still got the same 3 errors as above) and rebooted, and the system settings finally appear.... Although under a weird name.
The settings app is now called "Set data limit".
Also the characters of the clock app name are in Chinese now...
Besides these 2 things, the rest seems to be working fine now with 11.0.6.9
Thanks Qnorsten !
Hi there.
After flashing some custom roms (lineage and Arrow, both for like 5 minutes xD) (from zip files via Orange Fox), I wanted to go back to MIUI (don't ask xD).
After flashing a stock rom via miflash, I started getting errors about device storage being corrupted, the device being unsafe and my sensors stopped working (like all of them, proximity, light, gyroscope, etc.)
THIS I FIGURED OUT:
I figured that my persist partition is broken and I restored it from persistbak. (dd if=/dev/block/mmcblk0p%% of=/dev/block/mmcblk0p$$)
But even after doing so, my proximity sensor does not work.
Moreover, it does not work in the most annoying way: In CIT it shows as permanent 0.0 no matter if sth is close to it or not. So whenever I light up the screen I get the message about not covering the earphone area(the one you can override by pressing vol +) and my screen is PERMANENT OFF during calls which does not let me use speakerphone, mute microphone, etc. Does anyone have any idea on how to fix it? Yes, I've seen the post with the tasker solution that disables the sensor in "screen permanent on" mode. It does not satisfy me (I'd much rather have a fully functional phone), will try that if nothing else works. Also, the phone is under warranty, I pray to God for if I maybe flash back stock, lock the bootloader and say to them "my proximity sensor does not work" they'd fix it under warranty. Or maybe someone knows which part of software is responsible for the proximity sensor and is able to provide a dump for me?
You f....up your "persist" partition !
If you haven't already did a backup with TWRP, then there is only one solution !
This is how to restore it :
- download the latest .tar and .zip firmware (the same version+++) from here ... according to "your phone region" [mandatory]
- don't choose an old version : always the latest one, don't mix the numbers
- don't use xiaomi.eu in any case
- extract persist.img from .tar
- you need to flash it with TWRP/OF (use my twrp.zip)... yes this will reset the whole "persist" partition.
- flash now the whole MIUI firmware .zip in TWRP/OF
- flashing .tar in MiFlash Tool is bugged and a high risky business
- format /data (type yes)
- reboot to fastboot from TWRP/OF
- extract stock recovery.img from .tar +++
- flash it :
fastboot flash recovery recovery.img
- you need now to lock the bootloader to restore the original state of your phone, and this is the only way to rewrite again "persist" partition from scratch by the bootloader !
type :
fastboot oem lock
fastboot reboot
- Later you can still restore your DRM Keys again in MIUI ... don't worry about them !
See you
Restore stock using fastboot files through miflash. The fastboot files should contain everything and therefore restore everything.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Lu5ck said:
Restore stock using fastboot files through miflash. The fastboot files should contain everything and therefore restore everything.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
Click to expand...
Click to collapse
You are misleading this guy ....
Restoring persist partition doesn't work like that.
It is always ignored by default in the bat/sh scripts... and can't be flashed through fastboot !!!
Furthermore, as i said, MiFlash Tool is bugged and he can hard brick his device +++
Don't say things that you don't understand. very well !!!
gringo80 said:
You f....up your "persist" partition !
If you haven't already did a backup with TWRP, then there is only one solution !
This is how to restore it :
- download the latest .tar and .zip firmware (the same version+++) from here ... according to "your phone region" [mandatory]
- don't choose an old version : always the latest one, don't mix the numbers
- don't use xiaomi.eu in any case
- extract persist.img from .tar
- you need to flash it with TWRP/OF ... yes this will reset the whole "persist" partition.
- flash now the .zip firmware in TWRP/OF
- flashing .tar in MiFlash Tool is bugged and a high risky business
- format /data (type yes)
- reboot to fastboot from TWRP/OF
- extract recovery.img from .tar
- flash it :
fastboot flash recovery recovery.img
- you need now to lock the bootloader to restore the original state of your phone, and this is the only way to rewrite again "persist" partition from scratch by the bootloader !
type :
fastboot oem lock
fastboot reboot
- Later you can still restore you DRM Keys again in MIUI ... don't worry about them !
I will post later the zip to flash persist.img with TWRP/OF ... as i'm now in the bed.
Don't take any action now by yourself ... just wait for tomorrow !
See you
Click to expand...
Click to collapse
Dunno who you are or where you live but if your solution works, I owe you a beer. You're my savior! XD I'm at work now, will try your solutions in the evening/on the weekend
gringo80 said:
You are misleading this guy ....
Restoring persist partition doesn't work like that.
It is always ignored by default in the bat/sh scripts... and can't be flashed through fastboot !!!
Furthermore, as i said, MiFlash Tool is bugged and he can hard brick his device +++
Don't say things that you don't understand. very well !!!
Click to expand...
Click to collapse
My bad.
You are right that the .bat file does not contain commandline to flash persist despite the img being in the file.
I just downloaded to check.
On the other hand, miflash is just a one click fastboot UI to flash base on commands indicated in the .bat files so I don't know why your instructions imply it can flash things like recovery can.
@Guzior2137
With that said, OP would need to flash the persist.img to persist partition. Given that despite the .img is in the fastboot zip but not in the .bat command can only suggest that the fastboot does not accept "fastboot flash persist persist.img" which means you will need a recovery that can do that. I would recommend using orangefox to do that as orangefox is tailored for xiaomi devices and on a bonus side, it doesn't get replaced during official MIUI ota like others do.
Guzior2137 said:
Dunno who you are or where you live but if your solution works, I owe you a beer. You're my savior! XD I'm at work now, will try your solutions in the evening/on the weekend
Click to expand...
Click to collapse
(.zip) added : extract and put persist.img in firmware-update forlder and re-zip again.
- read carefully the guide up
- don't skip any step / add extra-step
- don't use MiFlash Tool
- don't flash xiaomi.eu
gringo80 said:
You f....up your "persist" partition !
If you haven't already did a backup with TWRP, then there is only one solution !
This is how to restore it :
- download the latest .tar and .zip firmware (the same version+++) from here ... according to "your phone region" [mandatory]
- don't choose an old version : always the latest one, don't mix the numbers
- don't use xiaomi.eu in any case
- extract persist.img from .tar
- you need to flash it with TWRP/OF (use my twrp.zip)... yes this will reset the whole "persist" partition.
- flash now the whole MIUI firmware .zip in TWRP/OF
- flashing .tar in MiFlash Tool is bugged and a high risky business
- format /data (type yes)
- reboot to fastboot from TWRP/OF
- extract stock recovery.img from .tar +++
- flash it :
fastboot flash recovery recovery.img
- you need now to lock the bootloader to restore the original state of your phone, and this is the only way to rewrite again "persist" partition from scratch by the bootloader !
type :
fastboot oem lock
fastboot reboot
- Later you can still restore your DRM Keys again in MIUI ... don't worry about them !
See you
Click to expand...
Click to collapse
Wait. Could you please explain to me: what is the file you attached used for? Is it TWRP? if I then have already OF installed, no need to use it?
Guzior2137 said:
Wait. Could you please explain to me: what is the file you attached used for? Is it TWRP? if I then have already OF installed, no need to use it?
Click to expand...
Click to collapse
it's a flashable zip :
. open it
. put persist.img in fimware-update folder
. rezip and flash
. then flash your miui firmware in twrp
. format /data
...
Crap. Once again, just to confirm: I should:
-put the persist.img in the empty folder firmware-update of your persist-twrp-reset.zip
-flash your zip that I just modified using OF
-flash the zip I downloaded from xiaomifirmwareupdater.com using OF
-format /data in OF (type yes)
-extract stock recovery.img from .tar +++
- flash it : fastboot flash recovery recovery.img
-lock bootloader: fastboot oem lock fastboot reboot
Right? (sorry, better to confirm a dozen times and not screw anything up I think xD)
- use fastboot to flash the recovery.img and not TWRP/OF
- fastboot oem lock
- fastboot reboot
well, nope, did not help, my proximity sensor still does not work
Guzior2137 said:
well, nope, did not help, my proximity sensor still does not work
Click to expand...
Click to collapse
are you using a screen protector with black edges ??? like this one ???
Nope. Stock plastic screen protector that was applied from the factory when I got the phone in September. Worked just fine until now. Also, if I point another phone's camera at the earpiece, I can see the blinking infrared LED while I run the proximity sensor test in CIT, which leads me to think that hardware is ok...
If the sensor is red and blinking ... that means it works +++
Now, run a proximity test in Device Info HW
You should know that the proximity sensor works only when the earpiece is used in phone call ... when you switch to the speaker, the sensor goes off.
That's normal !
gringo80 said:
If the sensor is red and blinking ... that means it works +++
Now, run a proximity test in Device Info HW
Click to expand...
Click to collapse
It's 0,0 cm in your Device Info HW app. No matter if I put sth by the earpiece or not...
I think I'll turn the phone up for a warranty fix. But then, so that they don't know like RIGHT AWAY that the phone's been tampered with, do you know a way for it to pass safetynet test? It currently errors out at CTS profile. I've heard that installing this from link: https://github.com/kdrag0n/safetynet-fix/releases/tag/v1.0.2 via magisk and turning magisk hide on will fix the problem. But then the phone will be rooted which also obviously means it's been played with. Gringo80, any suggestions?
You will laugh, but at first all the sensors stopped working for me too. I flashed persist and they worked, but the proximity sensor always showed zero, and now it always shows the maximum.
Your browser is not able to display this video.
I can't figure out what's going on. Yes, the sensor works, where in 1 case out of 100 it shows 0 instead of 5, but even through the service menu I can't calibrate it, it just always shows 5
Guzior2137 said:
...to pass safetynet test? It currently errors out at CTS profile. I've heard that installi...
Click to expand...
Click to collapse
I have the same problem. I've tried installing different firmware, modules, instructions, but I get this.
So I've been pulling hair for 2 days. I can flash everything fine recovery boots fastboot. But it consistently says no OS on either slots. Tried flashing stock to both went all the way through loading lineage and same thing. I'm at wits end. Also not a single password I put in decrypts data.
Also Metro/Tmob variant xt2131-1 bootloader unlocked.
Have you tied fastboot -w? It sounds like the partitions are messed up.
I have. I've done all of the above just still a persistent boot loop.
Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Currently retrying to flash stock firmware with a Motorola flashing program. Will let you know here in about 2 min.
Fandroid Tech said:
Have you tied fastboot -w? It sounds like the partitions are messed up.
Click to expand...
Click to collapse
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Spedwardo said:
Yep. Again boot loop. Says no OS. Stock recovery says last installation failed. Flashing the service flash package to see if that makes a difference. Hopefully because it says it reflashed my bootloader and stock recovery.
Click to expand...
Click to collapse
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
No nothing of the sort. I did a factory reset because I was gonna try out lineage and this is where I'm at now. Still no OS. Even after flashing 3 times. I did have a remote access trojan that rewrote my partition data and resized one and added one and used the root hidden partition to store the data in while it was being transferred.
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
sosthenisRR said:
This drive folder has the system, system_ext, vandor and product of the xt2131-1 that can be flashed in twrp or orangefox. Make sure you make the partitions rw in twrp or OF using 100 rw zip (search for it) then mount as rw in terminal. Flash these images or image,whichever you believe to be needing. Then try and reboot. If all else fails then download the firmware from LMSA and use tinyfastboot tools to flash it. Always worked for me. Let me know how it goes. Heres the link to the files.
XT2131-1_Denver-Osaka_04-2022_RRE31.60-47-2-2 - Google Drive
drive.google.com
!!!!!Make Sure you have verity and verification disabled before trying to flash these. Hence the 100 rw zip is necessary. And must be flashed correctly. 73 error can be flashed with Ubuntu!!!!!!!!
**Edit**
Make sure you always
Fastboot -w then
Factory reset in recovery then format data for a full clean install. This vendor build is made for the boost mobile variant but it is universal. The firmware is incremental based as well so it knows which build to install or activate on the tmo/metro variant. I have all the apps and files for all carriers that have this model.
Click to expand...
Click to collapse
If this doesnt work you can try a blankfile flash via edl, if that does not work nothing will.
Fandroid Tech said:
The motorola program formats the partitions before flash unlike an automated fastboot flash. The only issue I can see is a physical issue with the UFS/EMMC 5.1 chip, maybe even the ram(very unlikely). Had there been any warning signs such as the phone rebooting randomly or freezing? Motorola has a one year warranty for all devices.
Click to expand...
Click to collapse
Not at home. Staying the night at my mom's. Get home early tomorrow and I will try the advised steps. I went through my previous flashing steps and am now just missing the persist partition. I'll report back as for the edl mode and I have 2 blank flash files just cannot get into edl mode. Have qfil rsd and motoflashpro
Spedwardo said:
just cannot get into edl mode.
Click to expand...
Click to collapse
What have you tried thus far? Have you tried fastboot commands to get into edl, I think it may also also a boot menu option in twrp but I don't remember. Also now that I think about, after flashing the firmware(to both lots as you say) have you tried fastboot set_active a (or) b? Also where did you find the firehose file for it, I could not find one on other forums?
So far im downloading the files and will try what you suggested now. I'll let you know in 30 min. But I've tried factory reset. Flash. Formatting then flashing. Blank flash. Formatting then flashing. I've also used fastboot --force -slot=all flash ***. *****. Etc. Tried flashing. Flashing the copy partitions and tried flashing a gsi an aosp. Got to lineages recovery but still the same issue. Some partition are unmountable. At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Spedwardo said:
At this point now it refuses to charge while off.. and if I do plug it in while off it continues to boot loop from the battery/charging screen.
Click to expand...
Click to collapse
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Fandroid Tech said:
Sorry to tell you this but the phone is definitely ****ed on a hardware level, no amount of reflashing the firmware will fix that. The partition issue is likely caused by the EMMC/UFS malfunctioning, however the charging issue is definitely not caused by software as the battery has a separate controller. Your best bet would be to replace the motherboard, your phone's warranty is however void anyways since you unlocked the bootloader so you would have to do it yourself.
Click to expand...
Click to collapse
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Spedwardo said:
How do I disable anti-rollback???? Might be the issue with it not flashing vb* files. Assuming those control vendor persiste etc
Click to expand...
Click to collapse
You can't, the manufacture prevents you from doing so due to "security issues". Make sure you get the latest firmware at https://mirrors.lolinet.com/firmware/moto/denver/official/. This will restore all partitions including vendor and persist as it generates from the modem partition, also android 11 and up does not use regular persist partitions anymore, it is now in the "super" images so don't worry about it. When you extract the latest firmware from this site there will be an XML file, go to https://forum.xda-developers.com/t/...e-with-motorola-devices.4042039/post-82186933 and follow the instructions, before flashing made sure to select slot A, after you are done flashing slot A set it to slot B and flash again, then reboot regularly. To set the slot run the fastboot command before flashing, for example fastboot set_active a, flash firmware, fastboot set_active b, flash firmware, reboot.
Hello Dear XDA Community.
I removed persist.img file falsely on my device and it stucks at "No valid slot to boot." screen and it stucks even though by using flash android website for return the OS to stock.
Therefore, i need to get persist.img file in order to flash it for rescue the device.
You can run this:
Code:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
on the adb shell for get copy of persist.img.
For your help.
Thanks.
NOTE: Device succesfully boots the latest AOSP-MASTER-WITH-PHONES build which i tried on flash android website (unfortunately, no any sounds and even sounds of ringtones and no sensors on device); but does not boot factory images, which causes "No valid slot to boot." on the fastboot screen.