I don't know how, but persist partition apparently got damaged in my device after installing of custom ROM. So would anybody dump that partition and send to me?
Here is the way you can get it: boot into TWRP -> Advanced -> Terminal (or in rooted adb shell) run "dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img". The .img file will emerge in your root directory.
Upd: flashing other device's persist.img can't solve my problem, so I really don't know what to do
By the way my problem is missing of all sensors data (accelerometer, light sensor, proximity sensor...) after installing Pixel Dust ROM. I have flashed stock Q and P firmwares by several times, but it made no changes. However my persist partition looks fine to compare the one from device with working sensors
You can't just take someones persist. How do you know it's not hardware damage since sensors can fail after all? if you use someones persist, your using all their unique data. Have you tried downgrading to Android 9?
djared704 said:
You can't just take someones persist. How do you know it's not hardware damage since sensors can fail after all? if you use someones persist, your using all their unique data. Have you tried downgrading to Android 9?
Click to expand...
Click to collapse
Yes, I tried to downgrade to Pie, even to stock 7.1.2 image, but it still not got any use. And the strange fact is, that sometimes I can get data from proximity, light and pressure sensors, but it can suddenly disappear during one up time (I mean between reboots), and it means what at least two modules responsible for that sensors (TMD4903 and BMP2805) still can work fine... I guess
I assume, that weird behaviour can be related to some data which keeps untouchable during wipes or any firmware upgrade. Some data like PIN or something, and it were corrupted
Related
Hi all. This is by way of advice, information and a question.
I have a 7105 on contract and it got dropped. It was rooted but running stock 7.1.1 and was fine for months and months before I cracked its screen. My contract covers accidental damage so I got a new one. Thanks to the excellent guidance with various Android phones over the years from this forum I've happily rooted, hacked and generally mucked about with loads of HD2s and my 7105 and never had a problem.
Until now
When the new phone came I just dived right in. Rooted ok. Started to use Titanium backup to restore apps. All going well until I got to Flight sim game. In the middle of the restore, the phone rebooted and when it came back up it was in factory mode. You lot being by far the best source of advice I hunted this down in the forums and found a nice solution to fix it by modifying the keymgr and factorymode text files in the FactoryApp folder in efs. My problem was that I couldn't alter factorymode. It was in fact corrupt along with a number of other files. I'm sure you can imagine the panic! To cut a long story short. A day of intense hacking got me nowhere because I panicked and started flashing this and flashing that all to no avail.
After a sleepless night I turned to my own fledgling knowledge of Linux and using ADB I connected to the phone whilst it was in restore mode and used e2fsck to repair the efs partition. Once repaired I was out of factory mode! But the problems didn't end there.
I then ended up with what I would historically call video ram errors. Random crap appearing on the display. Coloured flashing lines across the screen etc. I couldn't fix this so I had to do the best I could to restore the machine to normal with TriangleAway. Unroot and generally get it back to factory condition before returning it as a faulty replacement.
So Advice: always back up your EFS folder. Even if you aren't flashing new roms! If you just root it then anything can happen!
Information: If your EFS folder is corrupt (this is from memory so forgive me if I'm not 100% right. Should be close enough though) start your phone in restore mode, connect with ADB, set permissions to root via su and then run e2fsck on the efs device. It's in /dev/block/something. if anyone really needs this I can probably dig it out of my current working phone
When using e2fsck there are two parameters you need. The first does the repair. the second important one is to force a repair even though the superBlock says all is well. For me this fixed factorymode file and several others.
My question is this: Could I have just been unlucky and genuinely had faulty hardware? The lines on screen and peculiar display behaviour in all screens from the bootup display right through to wallpaper in the shell were clearly indicative of video ram from experience but could a file in the EFS folder determine video subsystem parameters perhaps? So a corrupted file in the EFS file system was setting up the video hardware incorrectly?
Would be really interested to get some views on this
all the best to you out there and - as always - thanks for all the help and advice over the years.
HI,
I used to be more active in this forum, but honestly nowadays I can't found any reason to since everything has been smooth sailing for me without any problems—until this day, at least. Somehow I got my internal sdcard busted, it was pretty spontaneous, all I can recall is suddenly the system starts to reboot itself. Nothing much, I thought to myself, problem is the system keeps rebooting, it doesn't even last a minute. Naturally when faced with this problem one would do the usual procedure, namely completely format the thing to stock the rule out any possibility on the user side of things, but then this is the part when it starts to get interesting...
The thing refused to be formatted, seriously, it baffles me at first but it does
Things I've tried:
Fastboot, it hangs at writing system, whether I was doing it line per line manually or via the flash_all.sh script, I haven't tried the toolkit but I think it's safe to assume that It'll do the same thing. Even if it does go on (which it did, once) it doesn't do any sort of changes whatsoever to the system.
ADB, nope, not this one either. And since the system reboots faster before I can do anything worthwhile it's pretty much out of the question.
Recovery, multiple times I've tried nuking everything via CWM, nada. I've tried TWRP too, I have to boot it from fastboot since it apparently doesn't allow me to flash a new recovery either, it reverts back to CWM every time. Also tried to flash a different ROM (CM), that didn't work, it spits out an error message regarding some failure in changing metadata, thought it was a corrupted file or something, so I re-downloaded it, that doesn't work. Still convinced that it's corrupted I tried 4 different version of it without any luck. Even the one I had successfully flashed before. Interestingly enough, flashing the exact same ROM I'm currently using (ShinyROM) works, not that it seems to do anything.
Built-in data format from settings, now this doesn't work because I assume that it needs the stock recovery to work, which I couldn't flash because it wouldn't let me—in a sense that it flashes just fine on the command line—fastboot doesn't show up any error or anything—but it defaults back to CWM as soon as I reboot it.
Manually via terminal emulator/file manager, still nothing, curiously enough, Terminal Emulator indicates that the whole system is read-only (I tried making a file with it, it shows that exact message).
Grit my teeth, clench my fist and screams out every curse word that I know of, this somewhat reduced my stress levels, but ultimately yields nothing.
Which led to be believe that either my phone was either a) Haunted or b) Has a serious hardware problem, I'm leaning on the latter. A few quick lookup with my limited amount of Google-fu and I've found several threads that described the exact same issue:
http://forums.androidcentral.com/go...-factory-settings-no-matter-method-i-try.html
http://forums.androidcentral.com/go...eset-nexus-7-2102-using-multiple-methods.html
Both of which hints at it being a hardware problem. Which was my biggest fear since I can't really revert the phone back to stock now can I? Locking the bootloader doesn't seem to work either (the 'fastboot oem lock' command works just fine but just like every single thing I've tried, reverts back to my previous setup as soon as I did a reboot), plus this means I have to send it back with my private data still on it, and I can't say I trust Samsung, Google (or anyone really) with my private data. Not to mention some of the stories I've heard/read about Samsung and their policy regarding rooted devices (much less ones with an unlocked bootloader).
In case it helps, here's a few more details:
What state the device is currently in:
It boots up just fine, but nor for long, apps starts to hang and ends up with a cold reboot (sorry if it's not the right jargon, but it starts right from the Google screen).
Everything that doesn't require you to access the filesystem works fine.
Apps doesn't seem to be able to write anything to the filesystem, I tried backing it up with Titanium Backup, much to my surprise the backup files weren't made (although TiBu seems to indicate that they were).
What the device is running:
Variant: Maguro 16GB
ROM: ShinyROM 4.4.2
Kernel: franco.Kernel r395
Baseband: XXLJ1
Bootloader: PRIMED04
Also I don't know if this will affect things but for the record I'm running the latest Ubuntu and Debian.
So this post is pretty much a shot in the dark, since I think I know what I'm dealing with already; if anyone had this problem before in the past, or has it now and somehow managed to fixed it, please do tell. Or if anyone has any experiences RMA-ing your device with a condition like this I'd love to know.
Yep your EMMC is fried. Sorry man.. But you can go to warranty. They *should* accept it since it is a developers phone but they could make a lot of hassle about it being rooted..
Sent from my Galaxy Nexus using XDA Premium HD app
Hi
Since installing the December 2018 update to Android Pie last week my phone has become unusable. It freezes for 5-10s period all the time while using. Sometime, when it wakes back up again, there is a message on the lock screen that says 'you need to unlock using pattern after reboot' which makes me think the phone is crashing and rebooting itself while the screen stays frozen.
I have done a factory reset twice. In fact, directly after the December 2018 update, the phone got stuck in a boot loop and I had to factory reset then, as well.
Anyway I did some research on here and have run Androbench as people seem to be blaming poor write performance. See image.
Please - what can I do? Roll back to an earlier version of Android? The phone has worked perfectly for months until last week.
Many thanks.
you could try to reflash the latest pie rom with miflashtool. if you tick "flash all expect storage" you wont 't lose any data
download the latest rom from website, extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg . This will completely flash the whole phone without relocking the bootloader. I had exact same issue after using twrp to make a nand, its had something to do with accessing firmware while making backup, i think this will sort your phone out, dont use miflashtool its a total mess. Dont mess with flash order, ppl may say it doesnt matter what order its done, but it does matter. Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Brilliant - thanks for the reply. What you suggest is probably on the limit of my skills and experience, so I have a few questions if that is OK:
boe323 said:
download the latest rom from website,
Click to expand...
Click to collapse
So, this? https://en.miui.com/download-354.html
boe323 said:
extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg .
Click to expand...
Click to collapse
I assume just copy & paste this file into the main folder?
boe323 said:
Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Click to expand...
Click to collapse
Thanks, I will check that platform tools is in the system variables path. Maybe it will become clear, but I can't remember if the rom image needs to be stored on the phone or PC before I start?
Thanks
After fixing itself last time (with a factory reset), my phone's performance has gone absolutely again since the September update. It hangs constantly, takes 10 mins to turn on, and is generally unusable. Memory logs below.
This time nothing I have tried will fix it, I have tried: factory reset from bootloader, miflash to latest rom, using fastboot to flash latest rom, using the modified flash_all.bat from boe323 (thanks for your help last time).
Still the performance is dreadful.
Is there anything else I can try before I throw this phone away?
Thanks anyone for helping
Flash lastest stock (10.0.13.0) with no flash but use: fastboot oem edl , u can search in you tube how to do is easy
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
yeahdisk said:
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
Click to expand...
Click to collapse
If nothing helps , just use MiFlash , and don't use clear all , use clear all_lock.Relock your bootloader and test if everything is working ok. If it doesn't - then I hope you have warranty. Relocking and unlocking the bootloader is so easy , so you don't have to be worried about nothing. Then you will be sure , if the problem presists with totally stock firnware , then you have only one choice.
thanks - trying this now
Downloaded your app and tested it on my perfectly working device. No problems at all, no hangs, fluid, etc.
I attached the results.
If you flashed stock ROM and the speeds are that horrible... you should check if any apps are causing the hangs. Reboot in SafeMode and check the speeds. If the phone behaves normally in SafeMode, than something you installed/configured is causing the said problems.
The last solution would be... checking the NAND chip, I don't quite know if there are apps that could check the sectors in the NAND memory. Maybe you are experiencing a bad nand/multiple bad sectors slowing down everything... But from my knowledge this shouldn't be a problem in current technology, since Android has auto-trim and bad sectors should be ignored, not affecting performance.
From my experience August update fixed the problems and September brought a system speed-up. I feel the phone even more snappy now.
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
yeahdisk said:
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
Click to expand...
Click to collapse
Get an app like System Panel 2. Set it to monitor all apps/system activity and check where the hangs comes from. Maybe even AndroBench is the culprit in your case.
Anyway, get a system monitor app that can log all app activity individually and see which app has the most cpu usage and which app has the most disk usage.
But by the fact that your phone is running extremely slow after reflash, I suspect the back-up/restore system. Maybe it downloads some corrupt data and hangs the system. If that is the case, a new Google Account may fix the problem. Start fresh.
OMG I took the memory card out and everything is working fantastic again
yeahdisk said:
OMG I took the memory card out and everything is working fantastic again
Click to expand...
Click to collapse
If the SD was your problem, check out the solution I found here: https://forum.xda-developers.com/showpost.php?p=80172348&postcount=19
Step 1: Use the MSMTool to restore your device to 10.5.4.
Step 2: Root with Magisk Manager ( Try to use this image https://doc-0k-bo-docs.googleuserco...6963965&hash=okighskqqr3fv666mjfvlr07i771asga)
Note: Don't update the magisk manager after using this image. (Use only fastboot flash boot magisk_patched.img and reboot)
Step 3: Use Unlock Factory Mode *root* https://forum.xda-developers.com/t/guide-unlock-factory-mode-root.4118527/
Step 4: Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
Step 5: Swipe over to "Device Debugging"
Step 6: Select "Finger print test"
Step 7: Select "Finger print calibration test(Pure White - 90% Blue) (DOesnt matter whether you use your finger or not)
Step 8: Select "Reliability Test"
Step 9:Select Calibration result and check if there are multiple red error lines
Step 10: Download the persist.zip and Extract the file.
Step 11: Move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
Step 12: Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and Copy them at /mnt/vendor/persist/
Step 6: Reboot
It should Start Working .
kemesh said:
Step 1: Use the MSMTool to restore your device to 10.5.4.
Step 2: Root with Magisk Manager ( Try to use this image https://doc-0k-bo-docs.googleuserco...6963965&hash=okighskqqr3fv666mjfvlr07i771asga)
Note: Don't update the magisk manager after using this image.
Step 3: Download the persist.zip and Extract the file.
Step 4: Move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
Step 5: Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and Copy them at /mnt/vendor/persist/
Step 6: Reboot
It should Start Working .
Click to expand...
Click to collapse
You do know that the persist.img is device specific right? Meaning you need your own persist.img to restore it. You cannot use someone else's. That's exactly why there is a whole thread already covering this.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
FreshlyBaked 420 said:
You do know that the persist.img is device specific right? Meaning you need your own persist.img to restore it. You cannot use someone else's. That's exactly why there is a whole thread already covering this.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Click to expand...
Click to collapse
I did think that myself
But hey imagine it worked??
dladz said:
I did think that myself
But hey imagine it worked??
Click to expand...
Click to collapse
If it
dladz said:
I did think that myself
But hey imagine it worked??
Click to expand...
Click to collapse
If it does it would have saved me an RMA on my phone haha.
FreshlyBaked 420 said:
You do know that the persist.img is device specific right? Meaning you need your own persist.img to restore it. You cannot use someone else's. That's exactly why there is a whole thread already covering this.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Click to expand...
Click to collapse
It solved my FP problem .
kemesh said:
It solved my FP problem .
Click to expand...
Click to collapse
And where did you get the persist file? Was it yours? Or was it someone else's?
FreshlyBaked 420 said:
And where did you get the persist file? Was it yours? Or was it someone else's?
Click to expand...
Click to collapse
It from one the forum in here as mine also didnt work.
I have updated the steps once more try it . It worked for me 100%.
FreshlyBaked 420 said:
You do know that the persist.img is device specific right? Meaning you need your own persist.img to restore it. You cannot use someone else's. That's exactly why there is a whole thread already covering this.
[GUIDE] Fix PERSIST.IMG Loss Of Finger Print Sensor
New video guide below VIDEO GUIDE 1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device...
forum.xda-developers.com
Click to expand...
Click to collapse
Persist.img file is only a system file while is not technically a hardware . So as boot img and other image work for the others then obivously persist.img also should work like a charm as we are only using 2 folders 'DATA' folder and the 'ENGINEERMODE' . I have realized few things for some people this is not working as there are some file missing from their persist.img. Check the image for file comparision .
Well I'll be damned. Interesting.
kemesh said:
Persist.img file is only a system file while is not technically a hardware . So as boot img and other image work for the others then obivously persist.img also should work like a charm as we are only using 2 folders 'DATA' folder and the 'ENGINEERMODE' . I have realized few things for some people this is not working as there are some file missing from their persist.img. Check the image for file comparision .
Click to expand...
Click to collapse
If it works it works.
@bassamanator
Have a brand new guide that may help you buddy. Give it a shot.
Thanks to the OP if it does, it'll be a first I've seen if it does.
@kemesh he's got a borked fingerprint.
Should be a good test.
@kemesh @dladz This worked for me. I was able to register a fingerprint. (Side note: before I followed this guide, I did the fingerprint calibration and I kept my finger ON the sensor for the Black rubber test. The test failed as was the case when I followed the other guide, however, this time around I only had 2 red lines vs having pages worth of red lines. Did this play a role in making the fingerprint sensor work?)
In any case, I was hoping that fixing the fingerprint sensor may fix my Wifi and Bluetooth as well (both cannot be turned on). Unfortunately, Wifi and Bluetooth are still not working on my phone, buy hey, progress is progress!
bassamanator said:
@kemesh @dladz This worked for me. I was able to register a fingerprint. (Side note: before I followed this guide, I did the fingerprint calibration and I kept my finger ON the sensor for the Black rubber test. The test failed as was the case when I followed the other guide, however, this time around I only had 2 red lines vs having pages worth of red lines. Did this play a role in making the fingerprint sensor work?)
In any case, I was hoping that fixing the fingerprint sensor may fix my Wifi and Bluetooth as well (both cannot be turned on). Unfortunately, Wifi and Bluetooth are still not working on my phone, buy hey, progress is progress!
Click to expand...
Click to collapse
BOOOOOOM!!!
@kemesh
You!!
Are!!!
The!!!
Man!!!!!!
@bassamanator
AHH I'm gutted for you dude, I still believe that it can be fixed.
Have you backed up your EFS partition? Also now that you have a functional fingerprint reader get it backed up.
Perhaps reach out to OnePlus and see if there's anything that they can offer remotely.
Also my experience with RMA has been amazing from sending to receiving was 4 days.
I am based in the UK so it may vary but I'd imagine OnePlus would want to have a certain standard they'd like to adhere to, at least by reaching out you can get the information.
I'm at a loss in regards to WiFi and Bluetooth now.
It must be lower level but I've never heard of what it may be. Will look into it for you but I've drawn a blank offhand.
bassamanator said:
@kemesh @dladz This worked for me. I was able to register a fingerprint. (Side note: before I followed this guide, I did the fingerprint calibration and I kept my finger ON the sensor for the Black rubber test. The test failed as was the case when I followed the other guide, however, this time around I only had 2 red lines vs having pages worth of red lines. Did this play a role in making the fingerprint sensor work?)
In any case, I was hoping that fixing the fingerprint sensor may fix my Wifi and Bluetooth as well (both cannot be turned on). Unfortunately, Wifi and Bluetooth are still not working on my phone, buy hey, progress is progress!
Click to expand...
Click to collapse
Cheers
Does your wifi and bluetooth work after using the msdownload tool without fixing the finger print?
dladz said:
@bassamanator
AHH I'm gutted for you dude, I still believe that it can be fixed.
Have you backed up your EFS partition? Also now that you have a functional fingerprint reader get it backed up.
Perhaps reach out to OnePlus and see if there's anything that they can offer remotely.
Also my experience with RMA has been amazing from sending to receiving was 4 days.
I am based in the UK so it may vary but I'd imagine OnePlus would want to have a certain standard they'd like to adhere to, at least by reaching out you can get the information.
I'm at a loss in regards to WiFi and Bluetooth now.
It must be lower level but I've never heard of what it may be. Will look into it for you but I've drawn a blank offhand.
Click to expand...
Click to collapse
I am using a CN version with international rom and I'm currently residing in Australia so I dont have any support available sadly.
kemesh said:
Cheers
Does your wifi and bluetooth work after using the msdownload tool without fixing the finger print?
Click to expand...
Click to collapse
Wifi and bluetooth never work unfortunately. I've tried MSM to get me to 10.5.4 and 11.0.2.2, nothing helps. It might be a hardware problem. Taking a short break from all of this, I've done about 20-30 flashes/resets... in the past few days. It's tiring. Thanks for this guide, the other one didn't work for me.
bassamanator said:
Wifi and bluetooth never work unfortunately. I've tried MSM to get me to 10.5.4 and 11.0.2.2, nothing helps. It might be a hardware problem. Taking a short break from all of this, I've done about 20-30 flashes/resets... in the past few days. It's tiring. Thanks for this guide, the other one didn't work for me.
Click to expand...
Click to collapse
Few check if you dont mind :
Does your device show mac id for wifi and bluetooth? ( Settings>About Phone>Status)
If yes
I think you can test the hardware through the same *#808# mode
kemesh said:
Few check if you dont mind :
Does your device show mac id for wifi and bluetooth? ( Settings>About Phone>Status)
If yes
I think you can test the hardware through the same *#808# mode
Click to expand...
Click to collapse
Oh no problem, I'm absolutely open to new ideas. Unfortunately, I have no mac address/address for wifi/bluetooth.
Just because you mentioned it, I decided to go back in with *#808# and on the last page I found a test called Check CTSFingerPrint. At the top it says This check can only be performed after the CTS test is passed. There's a button below that reads CHECK CTSFINGERPRINT. When I click it, it immediately prints the following below the button: fingerprint check failed! it need connect to internet secure property check pass! I'll have another look but I couldnt' find this CTSFINGERPRINT Test, and also, I currently have a fingerprint registered. Anyone have any clues?
Thanks again for this guide! Fixed 1/3 of my problems.
I can't download the file for Magisk manager error code 403 for google docs. Can someone help me here? Tried some fixes on the net but none have worked. Thanks.
@GolfislikeLife Not sure what you need. What are you looking for? Magisk manager? https://github.com/topjohnwu/Magisk/releases
Hi well, when removing the pixel experience A12 rom and putting miui through miflash, I searched for wifis and called "nvram warning err 0x10" and managed to fix it by flashing the rom "Redmi Note 8 Pro ENG Firmware (Engineering Rom)" by typing the mac address manually (I took it out of the registry of my router) but I had a doubt, the imei is intact, the baseband also, the mobile model, everything seems to be correct, I just lost the mac address of the wifi that gave me a random and showed that error.
With everything I am telling you, have I been able to lose any function of the device? for example nfc, quality of the cameras or something important that I forgot, or I simply lost the mac address of the wifi and when fixing it it is as if nothing had happened?
I am concerned that something is corrupted in the background on the system and I don't know and in the future I have a brick when updating or anything else.
ps: factory reset phone from settings by reconfiguring google account and at this time it does not show nvram error.
Enteoria is all good, or have I been able to erase something else without my knowing it?
Greetings and thank you very much
The worst thing that would happen is losing your sensor calibration data (Which requires /persist and /nvdata to be corrupted too) which you can check by manually testing them using CPU-Z or MIUI's own testing app.
You said that your IMEI,Baseband etc. is intact so you should be good.
Also remember to back up your nvcfg,nvdata,nvram,persist,protect1 and protect2 partition.(use adb or dd to backup don't use TWRP)