Oneplus 8 pro Efs Deleted - OnePlus 8 Pro Questions & Answers

My Oneplus 8 pro 2023 Efs complete deleted and phone not recoginize sim card. how i can recover this phone ? or its garbage now ?

Send pick with details
*#06#
And how you deleted and why you deleted efs?
These phones are protected and not able to delete or wipe efs

msm tool deleted it i think. imei and baseband null

hulyahulya said:
msm tool deleted it i think. imei and baseband null
Click to expand...
Click to collapse
Smt ?

i used this tool. Downgrade android 12 to android 10
MSM Download Tool (All Version) 2023 New Update
MSM Download Tool All Latest Version 2022 is a flashing tool for Oppo and Vivo all android flash tool offline Tool 2022 New Update
www.officialroms.com

who can fix that ?

Related

Downgrading to stock from 8.1

Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser: [url]http://xda.tv/post75619905[/URL]
Please delete the EFS file, restoring another phone's EFS is illegal, sorry.
i lost my voLTE after flashing twrp based stock rom ( nov patch) on pixel experience feb build... now i cant use my jio sim for calls ... No VoLTE support...
if you have a backup of your EFS , can you please send me the file...
sir,what is your baseband version when the volte is working.?(if your current rom has volte working then what is your current baseband version.?)
IMEI shows 0 again after Restore your EFS file
Restore his efs file after flashing pixel experince 8.1,
Just go into twrp,
Flash pixel experince 8.1
And afther that restore his efs partition from twrp .
You will able to get your imei back,
But problem is after doing this way I still not able to get volte.
M8953_02.03.07.08r
Can you tell us what version of baseband do you see when you enter in boot loder.?
Because in my boot loder I see M8953_02.03.07.08U.
thedr34m13 said:
Admin Note: This is a special Q&A-formatted thread. Please follow this link to view it in your browser:
Click to expand...
Click to collapse
Persist backup may help to get volte back..please share if you can
yes,can you share the whole backup of pixel experience rom 8.1 (with volte working),by restoring that backup i think we may able to get volte.
i found this really helpful on another post,
what i did was deleting these files
fastboot erase modemst1
fastboot erase modemst2
from the fastboot comands before flashing back to stock
that works perfectly for me and i got back my signal &4glte.

XT1602 Need Help With Bootloader

Hello,
I flashed nougat rom then tried to revert back to MM rom and lost the IMEI and now the bootloader is updated to a new version with january 2018 security patch. So now I cant perform downgrade as it doesn't fix the IMEI.
I tried blank flash and many other ways possible but either the device is not detected and even if I manage to install the qualcomm HS USB drivers still it install the driver efficiently and RSD Lite doesnt detect anything in anyway.
I did the twrp backup but its of no use as restoring doesnt fix the IMEI and still shows 0. So I was wondering if I can edit the boot.img and other files to revert to stock marshmallow by updating bootloader info and files. Please help if its possible. Somehow it seems possible through QPST but the driver configuration plus I dont have the qcn backup. And I dont know much about QPST for this variant.
So kindly help

Baseband: Not found/Unknown, imei 0... Let's find a definitive solution

XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
mohitzr said:
I lost imei and signal....somehow I don't have my efs backup....tried every combo of ROM to get signals ie. something 2g/3g but nothing happens...
However my baseband is intact
Am on 1686 Indian varient
Q. Will moto z Oreo modem work?? Am planning to give it a try
Click to expand...
Click to collapse
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
barbaroja said:
XT 1806 here. Well, not long ago I posted about thinking I found a way... well... nothing. followed every single thread on hoy to restore basemand/imei to no avail.
So far what I know is that I was running fine, while trying to make cerberus a system app. The phone rebooted and bam. No more baseband.
Before that, I had done the trick of installing an oreo rom (Validus) and going back to stock. It worked and I got back Baseband on bootloader and then in the OS.
I have backups from my EFS from TWRP and PartitionsManager (modem, modemst1, modemst2 and persist) within the OS. Restoring those was no good. It worked before but not now.
I have bootloader C2.06. Before, I had C2.07. Installing the latest update from https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ , being it SANDERS_NPSS26.116-61-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml did nothing to update the bootloader or writing the modem.
So far I have a theory and is that, the phone is not taking flashing to the bootloader and or the modem as it should. I am using a high quality USB cable. Changed cables, too. Also, I think something weird is happening with the bootloader or chip programming. It is the first time I face something as weird as this.
I also think it does not like when you start the phone and reboot it quickly. Forgot its Baseband.
Let's be detailed and share experiences to find a cause and then a solution. I have more than 30 hours spent trying to fix this and it is getting to a scary point.
Click to expand...
Click to collapse
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
barbaroja said:
Any ideas on what happened when you lost the imei?
Please start in bootloader and see what it says in baseband.
Click to expand...
Click to collapse
i get baseband
[email protected] said:
You can start with this
Code:
https://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-xiaomi-mi5-imei-and-baseband-repair-fix/
and it's sister article part 2. I wrote a how-to on using QFIL to back-up and restore qcn files, and my research started there. However, after seeing how many cannot follow basic instructions to use adb/fastboot and even sometimes twrp, I am not going to post it. Let's just say you can edit the proper baseband components, but it is not going to be download and click to install. You will need the following to get started:
Code:
1.[QPST] https://www.androidbrick.com/download/download-latest-qualcomm-flasher-qfil-qpst-2-7-460/
2.[Qualcomm drivers]https://gsmusbdrivers.com/download/android-qualcomm-usb-driver/
3.[hexeditor]http://www.mitec.cz/hex.html
4.[IMEI convertor]https://androidfilehost.com/?fid=962021903579482959
5.Motorola USB drivers [you probably already have these, if you have used adb/fastboot]
You will also need a knowledgeable donor who is willing and able to donate a working backed up qcn file, of the same make/model, and bootloader must be in same state as yours. Although this will have the IMEI , it can be edited to 0 out all but the first digit of the IMEI and thus be safe for posting without fear of someone cloning it. This method has been done with other qualcomm chipsets, and the ultimate goal would be to get the proper working qcn file disassembled and compared to the faulty ones to see exactly where the basebands are being corrupted by the Oreo roms.
Click to expand...
Click to collapse
Thanks for sharing. Very interesting, indeed.
In my particular case, it happened for no apparent reason. Quick reboots being a suspect here. It seems some got baseband and no imei, others no baseband at all... Any ideas on this?
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
This a dump of an untouched XT1686 92-8 firmware.
rachitrawat said:
This a dump of an untouched XT1686 92-8 firmware.
Click to expand...
Click to collapse
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
akshu2697 said:
Can you provide me twrp flashable rom 92-8.?
Because I can't find it anywhere.
Click to expand...
Click to collapse
There isn't one as there is no 92-8 firmware out there.
Sent from my Moto G5 Plus using XDA Labs
did it worked ? .. im having the same problem .. cant get my network signal and imei
akshu2697 said:
Thank you so much.
Can you tell me what is your model no.?
And build no ?
And is this backup is from stock rooted rom.?
Is your device bricked yet,or have you loose IMEI in past.?
Click to expand...
Click to collapse
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Repiix said:
im having the same problem with my XT1686 indian version .. can we get it back with other efs backups ?
can we import backups from other mobiles and get the job done ?
Click to expand...
Click to collapse
I haven't tried it yet,
I will tell you if this work.
rachitrawat said:
dev here.
I've been looking into this problem for quite a while now.
Can anyone briefly summarise the problem? Like what all you flashed?
From my understanding:
efs = modemst1 & modemst2 = baseband cache = created on the fly
important baseband related partitions: modem, fsg, persist
Additionally I'm sharing potter retin (march) firmware files: (Download)
Try flashing this (on stock 7.0):
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash persist persist.img
Click to expand...
Click to collapse
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
I'm on an oreo rom(no volte). Will i be able to flash stock when the oreo rom is officially released? And hopefully get volte?
Arunxyz said:
1. my device is xt1686 retin and i lost my imei and volte after reverting back to twrp flashable stock nov security patch from pixel experience oreo rom ....
2. i recovered my imei using #castell93 guide ....
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
3. then i flashed twrp flashable stock jan security patch but no volte yet....
4. then i got my volte back thanks to akshu2697 guide... and backed up my efs
https://forum.xda-developers.com/g5-plus/how-to/solved-volte-fix-lost-flashing-stock-rom-t3773524
5. for a while i used custom oreo roms... and today i flashed twrp flashable stock jan security patch again and i lost imei =0 .... i have my efs backup so i recovered my efs and got my imei and volte working again..
6. today i downloaded #rachitrawat's twrp system backup file and formatted every thing using twrp and restored the system file and reboot... now i am on stock march security patch and i didnot loose my imei and volte .....
Click to expand...
Click to collapse
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Arunxyz said:
Extract twrp backup system img zip file and it contains system_img folder...
Copy that folder to twrp backup and then restore...
After restore you don't need to fastboot system..
I didn't try to flash fastboot system
Click to expand...
Click to collapse
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
akshu2697 said:
Can you help me how to flash this file..??
Because the non-hlos.bin is of 100 mb while in stock ROM it is of around 75 mb,
So can you describe the method to restore this.
Click to expand...
Click to collapse
Code:
fastboot flash modem NON-HLOS.bin
akshu2697 said:
Which system backup did you restore.???
There are two system backup zip in that folder.
And what if you again flash system with fastboot after restore that backup.????
Is IMEI still there.??
Click to expand...
Click to collapse
system.img is a bit perfect backup of /system which will not break dm-verity.
akshu2697 said:
What if you fastboot flashing and again IMEI goes to 0,..??
Can you try.?
Either flashing system via fastboot or flashing stock ROM with twrp.
Click to expand...
Click to collapse
you can restore via twrp or fastboot flash
Edit: fastboot won't work. Need to compress into sparse chunks. Try motofastboot

Expert advice on restoring someone's efs?

hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
No help here?
??????????????????????????????/
i don't think so people are helpful here or either not expert as nobody is replying lol
No idea. Sorry
taran181 said:
hi all, as people are posting tutorial to downgrade from pie to oreo with the help of restoring boot and efs folder uploaded by them,, is it safe to restore from someone's else twrp backup i mean efs folder??
as per my knowledge efs is backup of imei right?
so restoring from someone's else efs won't affect mine imei?
Click to expand...
Click to collapse
4-6 months back there was thread why we should not restore efs of someone & proper tutorial for people who messed up their mac address with some kernel.
Now this tutorial on downgrading pie to oreo. I have no idea. Someone's efs would mess your IMEI, wifi mac, Bluetooth mac, thats what i think. But there are tutorial how to edit imei using some Qualcomm tool.
Ask @CosmicDan. He's the expert.
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
I was having an issue since using custom rom with december fw btw.
and I was mistaken flashing november fw back to solve some calling issue, so I ended up with no signal which should be came from I didn't restore dev's efs backup.
So I start from flashing full clean stock november and ended with bootloop on it, which is something I still curious what cause it.
At that times, I'm on locked bootloader and can't even enter edl to reflash the rom and can't unlock bootloader since the rom still not booting to enable oem unlocking option.
I don't remember what I have done to it, but at times my phone can boot with no signal, 0 imei on sim1 and null on sim2.
So I start to rewrite the imei then everything is back to normal.
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
fhsd22 said:
Downgraded using the method of restoring boot and efs... Nothing changed for me, imei is the same as in the box of my mi a1. ? Maybe people did something before doing the downgrade that messed up something.
Click to expand...
Click to collapse
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
taran181 said:
@CosmicDan no flashing just oreo doesn't help, phone gets stuck in bootloop, so people has posted tutorial about flashing their efs and boot etc through twrp to get out of bootloop.
Eg: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Click to expand...
Click to collapse
Well you can try it I guess, just backup the EFS partition and other stuff with my backup tool and you can always go back if worse comes to worst.
CosmicDan said:
Just flash Oreo on fastboot, with full wipe. Why doesn't that work?
Click to expand...
Click to collapse
Xiaomi put out a message on their forum that after the Pie update, the phone should not be rolled back. Its for all Android one models. When users flash an older roms, bootloops occur.
https://www.fonearena.com/blog/271177/xiaomi-pie-oreo-downgrading-disabled-android-one-devices.html
taran181 said:
but my question why use someone's else efs while downgrading, as efs contains imei and modem backup ..
Click to expand...
Click to collapse
But what he is saying is that he did downgrade EFS, but IMEI didn't change. This suggests that EFS isn't the original source of IMEI after all. Or maybe the bootloader can re-write IMEI and stuff on boot, who knows... Surely others have actually confirmed that EFS cross-flash = IMEI change, right? Not just assumed?
...point is, you can backup your EFS via EDL mode so there should be no risk. If you made a full EDL backup of your own device when you were still on Oreo then you would be golden, as EDL has full access to all partitions.

Xiaomi A3 efs backup and restore tool

Xiaomi A3 efs backup and restore tool
to backup
EFS_persist_backup_g0dsend313
to restore
EFS_persist_restore_g0dsend313
download:
http://s4.picofile.com/file/8372556150/a3_efs_tool_by_g0dsend313.rar.html
pass:6969
XDA:DevDB Information
Xiaomi A3 efs backup and restore tool, Tool/Utility for the Xiaomi Mi A3
Contributors
mlm1102003, mlm1102003
Version Information
Status: Testing
Current Stable Version: 0.0.1
Created 2019-09-16
Last Updated 2019-09-16
Exactly what requirements do you need to be able to use this tool, I mean having root and twrp, modifications to the system risk the brick
Andres88z said:
Exactly what requirements do you need to be able to use this tool, I mean having root and twrp, modifications to the system risk the brick
Click to expand...
Click to collapse
Ideally you should have TWRP and Root. Frankly, you don't really need this tool, when TWRP will backup and restore EFS without any issue.
Worst case there is also the option of using QPST, there are also many tools available on Google play for backing up you partitions as long as you have root.
For example: Partitions Backup & Restore
Need qcn of efs backup
please you can post your EFS backup or QCN file from Mi A3, i`m without signal, but IMEI ok. i search on web but i cant find file.
i allready restore full stock ROM with fastboot method, but not fix the problem. After search on web about it, i finded on XdA and mi forum a case of Redmi Note 4 identical and the only method work is the restore with QCN file. please you can post the QCN file from Mi A3?
edson29jr said:
i allready restore full stock ROM with fastboot method, but not fix the problem. After search on web about it, i finded on XdA and mi forum a case of Redmi Note 4 identical and the only method work is the restore with QCN file. please you can post the QCN file from Mi A3?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1899786940962589872

Categories

Resources