deleted data partition - Sony Xperia M4 Aqua

hi, i had a hardware issue. but until i figure it out it was already too late.
i used fastboot -w without knowing what will happen.
is there a fastboot command to recreate those partitions that are deleted ?
please dont tell me to use flashtools. they are useless. im on linux.
the phone is the 2303 model
~EDIT: Problem solved. i asked in a thread here and got help already. Thank you.

Related

[Q] Wifi error and can't access bootloader.

Hi everybody.
Actually there are two issues to solve. I've read the thread "please, help!' related to WiFi error and saw a possible solution, but I can't perform any Bootloader command. I already done: Change Settings>Programs>USB Debbuging marked, (my device is unlooked and has a Diablo-version)
I think I wiped some else by mistake (even the original System), and I recover the system using Diablo ROM.
How Can I make bootloader works again?, and then fix the WiFi issue?
I am using TWRP access to install ZIP ROMs but none fixed WiFi...
you need to explain this part better: "but I can't perform any Bootloader command"
what can't you perform and what do u see when trying
guru_shastri said:
you need to explain this part better: "but I can't perform any Bootloader command"
what can't you perform and what do u see when trying
Click to expand...
Click to collapse
I mean "ADB" command. I was reading a lot about it and learning a bit more. I know now that ADB commands are use to copy, push, install and more from a Command Window. I didn't realize that those command can be done from a specific directory (Am I right?).
So, I copied ADB and two DLL files into a TWRP directory in my Device, and from this folder performed a few commands... and Voilá.. it worked.
But still can't make WiFi works and my System is still rebooting ramdomly when is not in use...
thanks for any Help ... any advice....
search the forum..you need to flash the wifi module to fix that.
as for the crashes, check on which kernel the device is running. the doomlord one is problematic
guru_shastri said:
search the forum..you need to flash the wifi module to fix that.
as for the crashes, check on which kernel the device is running. the doomlord one is problematic
Click to expand...
Click to collapse
Ok. stuck again. I've downloaded some ZIP and IMG files that I tried to "install" using fastboot or TWRP tools. in both cases FAILED.
there is someways to install usig fastboot commands to SEND (install) a ZIP directly to the device, but I am not sure how to do this.
Do you need to specify a Partition to install a ZIP file? Which one?
how to? [I mean Syntaxis of the command]
...
I m pretty upset with this device. I'm running El Diablo ROM pretty well, but Tetter (the game) and WiFi never worked...
Thanks in advance!

WIFI, Bluetooth and Baseband dead

Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
The Marionette said:
Hey guys.
My WIFI suddenly stopped working along with Bluetooth and no rom fixed it. So I tried flashing the modem of the Oreo OTA and I wiped the modemst1 by accident...
Long story short, WIFI/Bluetooth can't be enabled and even though the phone recognizes the SIM card, there's no signal and I can't make calls/send or receive messages ( the IMEI is 0 ).
I've tried going back to stock but the issue persisted.
I've heard that other SD820 phones used QPST but the Moto Z can't use the Diag Port so that one fell into the water.
Can anyone help me?
I just need to restore the baseband, even if it's from someone else's Z, and I can change the IMEI back to mine after restoring if the IMEI even gets duplicated.
EDIT
Fastboot getvar all showed that my IMEI is still present but I can't get it to appear in the OS...
Click to expand...
Click to collapse
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
hypafly said:
I don't thinking wiping modemst1 has to do with anything. I'd recommend you flash stock Oreo from here
https://forum.xda-developers.com/moto-z/development/stock-moto-z-8-0-firmware-t3805226
It should fix your problem.
I was on stock 7.1.1 with stock Oreo bootloader and had imei 0. But after flashing back to Oreo, I had my imei back. If it doesn't work, unlock bootloader and flash custom kernel. I recommend ElementalX Kernel 3.0.0 for stock OREO. Good luck.
Click to expand...
Click to collapse
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
The Marionette said:
The sad part is that I was on my AEX build and after I came back from college, everything was working untill the phone discharded and shut down. After a full charge, wifi was gone. Then I flashed the modem and some other parts on top of aex which caused the disappearance of the IMEI.
I did try flashing that exact firmware and nothing changed besides my baseband returning. The only guess I can make is to possibly try going to pure stock and relocking the bootloader ( other Moto phones actually got fixed that way )...
Click to expand...
Click to collapse
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
hypafly said:
I don't think it's possible to relock the bootloader. Have you tried full flash using the official firmware I recommended? Flashing some parts of it will not fix anything for you. Try full flash having it in mind that all your data will be lost.
Click to expand...
Click to collapse
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
So sorry to hear this.
My Moto Z has the WiFi bug too. But Bluetooth works though. It's very annoying because I've tried various fixes and different custom roms which didn't fix the problem. Maybe it's hardware? I wouldn't know. But I'm managing it for now until I get another phone.
The Marionette said:
I flashed everything in proper order besides the bootloader ( I already have that version, it would be rejected anyways).
I even tried wiping everything but it was still not helpful.
I have had it with this phone. I spent so much money replacing the battery and the motherboard and it suddenly craps out on me like this.
I've put it up for parts and my Xiaomi Mi 8 SE will arrive next week.
No more Motorola for me, a flagship phone shouldn't have this ****ty situations happening, especially when I didn't touch anything to begin with ( if I modified something myself, I would be okay with it, but this time it seriously died on its own ) .
Click to expand...
Click to collapse
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
How to Fix EFS over ADB
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
How to Fix EFS from Bootloader Mode using Fastboot commands
Setup ADB and Fastboot on your PC.
Enable Developer options & USB debugging on your Android device.
Connect your device to the PC and open a command window on the PC.
Issue the following commands one by one:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
How to Fix EFS from TWRP recovery
Boot into TWRP recovery.
From TWRP’s main screen, selectAdvanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
Edit: Those using twrp may experience efs restoration issues.
While creating the backup of EFS, you will end up with:
efs1.emmc.win (modemst1 partition raw data)
efs2.emmc.win (modemst2 partition raw data)
When restoring this EFS backup, what happened was the file name was not updated for restore, and you ended up with:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs1.emmc.win to modemst2
It should have been:
Restoring EFS…
Restoring efs1.emmc.win to modemst1
Restoring efs2.emmc.win to modemst2
Twrp issue, the steps above will restore your devices.
Click to expand...
Click to collapse
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
eLaDiio said:
try to flash this, that is my modem.bin file, i don't know what partitions is, but i did with this command "dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin", maybe can help you
here is the file: https://drive.google.com/file/d/18GGL9EAIM_fq8OCSOqsy8tsUcH9ipw1-/view?usp=sharing
---------- Post added at 11:59 PM ---------- Previous post was at 11:55 PM ----------
other possible solutions is this:
its from this forum of oneplus https://forums.oneplus.com/threads/restoring-efs.486667/
Click to expand...
Click to collapse
I appreciate the help but it sadly didn't fix anything. :/
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
eLaDiio said:
if you have acces to the fastboot commands, could you try to boot into twrp?, cause i have a backup, that can help you i guess
Click to expand...
Click to collapse
I have access to everything, everything besides the wifi, bluetooth and sim functions works.
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
eLaDiio said:
Mmm very weird, i have a full backup of my phone and sharing you, but i have the doubt if you restore it cause a hardbrick, if you wanna try, i can upload or share the link
Click to expand...
Click to collapse
I't not a hard brick, the phone boots. Wifi, Bluetooth and SIM functions are the only things that are dead. xD
Sorry, I expressed myself badly, what I wanted to say is that your case is a strange situation, by the way, I have a full backup of my phone and if you want, I can share it so you can try flashing it and see if you can recover the wifi, although I think it could end up in a hard brick so it is risky to try it. Tell me if you're interested in flashing my backup

[Q] [HELP] "IMEI = 0". No reception.

Greetings, fellow Moto E Surnia users,
I would appreciate some help on the matter, as mentioned in the title.
Here's the stupid thing I did
I wanted to clean everything on my phone as I was planning to give it to a sibling, so i found the stock files from Firmware Center and thought it would be a good idea to use the command
Code:
fastboot erase all
before beginning the restoration to stock process. It went off just fine, but when I booted up my device, I realized that there was no cellular reception on it, and my IMEI was 0.
It was only later that I understood that you NEVER use the
Code:
fastboot erase all
command on your devices. And I don't have an EFS backup because the phone does not have an EFS Partition.
Here's what I've tried so far
1. I sent the phone to a 3rd party cellphone repair shop, the person there tried something called a SigmaBox to try and repair the phone. No luck.
2. I brought it back and tried to use the Qualcomm RF/NV Editor and that too did not work.
3. A similar thread on another Motorola device's forum stated that they tried flashing the correct modem and firmware files to restore reception. I looked for the modem and firmware files of my particular model (XT1521) but I couldn't find it. Tough luck I suppose.
Another interesting thing that I found out is that the IMEI code is present on the device somewhere because when I tried
Code:
fastboot getvar all
i could see my IMEI0
I understand that I screwed up pretty bad. But is there anything else that I am missing that might help me rectify this error?
Thanks in Advance for all your suggestions.
TL;DR - Used
Code:
fastboot erase all
command and erased the IMEI code. Now left with no cell reception. My Surnia has basically turned into a tablet.
Yes...the old fastboot erase all command. This command, as you have just found out, literally erases all partitions, including your /pds, /hob and the /dhob partitions, which contain your unique device identifiers such as your MAC address, MEID, ESN, etc. This is an extremely tough dilemma to correct, and typically requires you to use Qualcomm's QFIL/QPST in order for you to manually rewrite the values to the device. Contrary to popular belief, it is not illegal to rewrite your MEID and other device identifiers, AS LONG AS you are not deviating from the device's original identifiers. In other words, you must restore the exact values which were erased in fastboot. This is a rather complex procedure, but if you are willing to undertake the job, I can get you some links to tutorials here on XDA that outline the process.
MotoJunkie01 said:
Yes...the old fastboot erase all command. This command, as you have just found out, literally erases all partitions, including your /pds, /hob and the /dhob partitions, which contain your unique device identifiers such as your MAC address, MEID, ESN, etc. This is an extremely tough dilemma to correct, and typically requires you to use Qualcomm's QFIL/QPST in order for you to manually rewrite the values to the device. Contrary to popular belief, it is not illegal to rewrite your MEID and other device identifiers, AS LONG AS you are not deviating from the device's original identifiers. In other words, you must restore the exact values which were erased in fastboot. This is a rather complex procedure, but if you are willing to undertake the job, I can get you some links to tutorials here on XDA that outline the process.
Click to expand...
Click to collapse
I'm game! Please help me out. I desperately need my phone to work.
EDIT - Just wanted to let you know that I've tried the QPST/QFIL program, I couldn't get it to work properly. Maybe I was doing something wrong. Maybe your links would help me out. Regards.
Hi @MotoJunkie01, any update on that links?
thanks in advance
piratedpanda said:
Hi @MotoJunkie01, any update on that links?
thanks in advance
Click to expand...
Click to collapse
I'm searching for a specific step by step tutorial. Soon as I find the one, I'll post it. I know it's frustrating having your partitions wiped clean. Been there before myself.
MotoJunkie01 said:
I'm searching for a specific step by step tutorial. Soon as I find the one, I'll post it. I know it's frustrating having your partitions wiped clean. Been there before myself.
Click to expand...
Click to collapse
Alright thanks mate, appreciate it.

NVME partition for ALP-L29 (backup)

Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
NVME
manager77 said:
Hi guys!
Can someone with Mate 10 ALP-L29 model to make a backup his phone's NVME and modem partition? I need this because l was hardbricked and l messed up with my NVME partition(lost). Thank you!
Please run this command with an external sd, and send me the resulting file:
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/external_sd/backup/nvme.img
####If you don't have external sd...
Please try something like:
(from computer with debugging turned on)
adb shell
su
(approve root request on phone)
mkdir /sdcard/backup
dd if=/dev/block/platform/hi_mci.0/by-name/nvme of=/sdcard/backup/nvme.img
@and for modem:
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_backup of=/sdcard/backup/modemnvm_backup.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_img of=/sdcard/backup/modemnvm_img.img
dd if=/dev/block/platform/hi_mci.0/by-name/modemnvm_system of=/sdcard/backup/modemnvm_system.img
OR,
Always with ROOT on mate 10 you can backup partition with Google Play market app : Partitions Backup & Restore 2.0.1 APK.
I need a all files NV:
Modemnvn_bakup
Modemnvm_factory
Modemnvm_system, etc.
I promise not to use your information or to make it public, and the file will be used only for my phone to make it work again
Click to expand...
Click to collapse
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
revjamescarver said:
So in other words you need all the information that would be required to clone someones phone. I doubt that a "promise" would be sufficient. Just using their backups would basically be cloning their device and using their information.
Click to expand...
Click to collapse
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol ????
Click to expand...
Click to collapse
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
ante0 said:
You would have to rewrite it using HCU, but that only works on firmware prior to June 2018. I have done this when I too messed with my NVME. NVME on Mate 10+ is encrypted and can't be edited without decrypting it first (I guess)
I have a mate 10 Pro and I don't think my NVME would be great for your phone
Click to expand...
Click to collapse
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
manager77 said:
HCU client works only with xloader01 firmwares. I am on xloader02 and for now nothing seems to be working. I tried today with sigma key too... but it doesn't work either. Chinese firmwares are all xloader01, Evan Android 8.1. (f''king chinese???)
About NV partition l think mate 10 and mate 10 pro should have the same one. I not sure it will work but l can give it a try if you help me( nothing to lose)
In fastboot mode after fastboot oem get-psid command.... it shows me in cmd my 2 imeis and serial number. But in normal mode l have 0000000 imei and with no services... and NCK prompt with sim!
Click to expand...
Click to collapse
Yep, I know that. But it didn't work on, for example, C432B145 either which was Xloader 01. So it was patched before the new bootloader was introduced
It may have the same NVME/modems. I flashed NV partitions from a BLA-L09 and mine is a L29. After this it turned into L09, and gained the IMEI/IMEI2 and serial of the donor phone. This was easily fixable in HCU though... But it's up to you. If you were up to no good it should only block the imei/imei2 on the network you use the phone on. And besides, I will probably switch to another brand soon. It seems Huawei patched something else now in latest Pie for C432 so you can't boot with a custom kernel (Built directly from their source without modifications, tried both COL and BKL source). It was fine on the build prior to this new one. I like disabling most of their kernel logging and **** which they seem to need for some reason. Can't disable all as kernel won't build then and I'm not in the mood of trying to completely remove it
Going to test signing it if avb is causing problems, it hasn't before but you never know with Huawei...
In fastboot it shows the info that's in OEMINFO. In booted mode it loads the info from modem.
But I will send you a pm in a bit.
NV partitions
manager77 said:
At first sight seems to be something like that... but is not my intention to have a functional phone which is a clone. If my phone will work again with NV partition from other same model l will continue to find a way to restore back my phone.... I am not a pirate lol
Click to expand...
Click to collapse
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
revjamescarver said:
The NV partitions contain the IMEI, ESN, and serial numbers along with other information, using those partitions to bring your phone back from the dead is cloning the phone, weather that is your intent or not. The only way to do it without "cloning" is to edit the information in the "donated" partition so that the information would be the same as the the information in your original partitions. You have to change the IMEI, ESN, serial number, and modem id numbers.
Click to expand...
Click to collapse
"edit the information in the "donated" partition "..... where is that?
manager77 said:
"edit the information in the "donated" partition "..... where is that?
Click to expand...
Click to collapse
It's encrypted. Or should be at least. Not sure if serial is
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
geogsm_1 said:
NV backup
https://cloud.mail.ru/public/Gv2o/aVrY2P5rz
Click to expand...
Click to collapse
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
manager77 said:
Thanks! I restored with Partition Backup and Restore all 3 partition that you upload here. But nothing is change for me... I mean l am in the same situation. I guess l need all modem partitions like in this pic:
Click to expand...
Click to collapse
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
ante0 said:
I was just checking my logs and I had to flash modemnvm_backup, modemnvm_cust, modemnvm_fw, modemnvm_img from BLA-L09 when fixing my device. But, after flashing those I would get No service. SIM was recognized. I had to restore my imeis/serial using HCU. After this it would switch between No service and my network rapidly. After this I did a factory reset in stock recovery and that solved it.
I'm not sure it was due to it being L09 modem and my device was L29 or something else, but HCU seems to be key to getting it back. I guess you could try downgrading partitions manually to pre-june firmware, all but xloader and fastboot. Downgrading xloader would only cause a brick and fastboot might too.
I guess you would also have to have a phone that boots to system, which I'm not sure yours does.
I could only use fastboot when this happened to me.
Click to expand...
Click to collapse
My phone works in all modes: normal, fastboot, erecovery, recovery. Only problem is 0000000 imei and no services
flash via fastboot then factory reset, it work for me.
code : fastboot flash modemnvm_system modemnvm_system.img

[HELP] UNABLE to mount /persist partition.

Hello, so, I got the following problem. My fingerprint is not working on any custom roms out there. I have tried reflashing stock, flashing different roms but with no luck. Everything else is working (GPS, WiFi, Carrier) but fp is not working.
When booting into the OrangeFox Recovery I've noticed that the /persist partition is not mount. When mounting the partition, I've noticed that there's a persist folder appearing in the root directory, so I'm assuming that because of this, I can't get the fingerprint to work. I've also tried making the system R/W but yet, I had no luck with the FP.
Maybe I'm wrong, that's why I'm asking for your help. Why can't I mount the /persist partition?
I have the same problem too .. tried unbricking my phone ,flashing custom roms and flashing persist.img but still no solution...
But i think the solution is to look for someone who has a working fp in realme 7 pro and ask him to backup his persist.img and upload it so we can download it and flash it.
I think that's all what we need so we can get our fp working again.
So if there's anyone who wants to help us... you can by backing up persist.img and uploading it for us so we can download and flash it.
I hope someone sees this.
Thanks in advance.
About that, someone already gave me a backup, after flashing I have the exact same problem...
make sure its backed up directly from a working realme 7 pro not extracted from an original rom ofp..
if it doesn't work then all we can do is to go to realme customer service.
They'll blame it on the motherboard and will ask to pay for replacing while the problem îs software-related. The fingerprint issue it's weird, I've only heard people complain about this issue on Realme devices, both Mediatek and Qualcomm SoCs. This is similar to Samsung's KNOX, once tripped there's no way back.
In my case, I have the european variant, but my guess is that somehow this issue is triggered by flashing another region's OFP. I had someone flashing the OFP for me via MSM Tools.
So, maybe If we find the original OFP for our device, we could probably fix our issue. We could ask customer service but it's unlikelt they'll give it to us, but I Guess it's worth the try.

Categories

Resources