??
As far as I'm aware, msm tool doesn't touch persist partition, so it might be something else.
Unfortunately restoring someone else's persist partition doesn't fix the FP issue, it has to be your own persist backup sadly (This has been tested)
Only option is to RMA or hope OP can fix it in an update (I doubt they can do this though, I think they can only stop it from happening again in future and can't fix it if it's already broken OTA).
??
??
??
I have the same issue
Did you find a solution?
Related
I've had this whole dm verity failure issue from stock rom after OTA update to my Note 4, Samsung won't do squat because it's a India Variant N910G and from what they tell me out of warrenty so I said screw it and decided to Root it and ad a the TWRP bootloader to it and use stock all is fine, except the issues I was having with Lag, and WIFI not saving passwords and Private Mode not working still remain.
So am considering using the CyanogenMod Rom but will this make a difference in you opinion if the EFS is what the issue is, my IMEI is fine by the way so can't figure out what's up with this whole thing and I don't have a EFS backup from before this issue occurred only now I have one since I rooted.
Any help and advice appreciated from you awesome peeps here.
Thanks
So my GPS was acting up (losing signal like every 30 seconds) and I tried to fix it by deleting modemst1 and modemst2 via fastboot, but after I did that my phone no longer recognizes my SIM card.
I've seen other people have the same problem but their IMEI dissapears while mine is still intact, does anyone know how may I fix this? I don't have an EFS backup btw (I know, I'm a retard)
extraterra1 said:
So my GPS was acting up (losing signal like every 30 seconds) and I tried to fix it by deleting modemst1 and modemst2 via fastboot, but after I did that my phone no longer recognizes my SIM card.
I've seen other people have the same problem but their IMEI dissapears while mine is still intact, does anyone know how may I fix this? I don't have an EFS backup btw (I know, I'm a retard)
Click to expand...
Click to collapse
Never restore an EFS to a Moto device... It doesn't work.
Never heard of issues related to erasing modemstX partitions.
What system version and build?
acejavelin said:
Never restore an EFS to a Moto device... It doesn't work.
Never heard of issues related to erasing modemstX partitions.
What system version and build?
Click to expand...
Click to collapse
Right now I have 6.0 MPH24.49-18 (downloaded from here https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833) but when all of this started I had the latest crDroid 7.1.2 build.
I've flashed like 3 different ROMs but the issue persists.
extraterra1 said:
Right now I have 6.0 MPH24.49-18 (downloaded from here https://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833) but when all of this started I had the latest crDroid 7.1.2 build.
I've flashed like 3 different ROMs but the issue persists.
Click to expand...
Click to collapse
Flash 18-8 and OTA to 18-16...
There is no known software issue on this device with GPS, not sure how to help. Have you considered it maybe a hardware issue?
acejavelin said:
Flash 18-8 and OTA to 18-16...
There is no known software issue on this device with GPS, not sure how to help. Have you considered it maybe a hardware issue?
Click to expand...
Click to collapse
Do you know where I can find the flashable 18-8? Thanks in advance
Honestly at this point idgaf about the GPS Issues, I just want the radio to work again:crying:
extraterra1 said:
Do you know where I can find the flashable 18-8? Thanks in advance
Honestly at this point idgaf about the GPS Issues, I just want the radio to work again:crying:
Click to expand...
Click to collapse
All firmware images are flashable with fastboot... Check https://firmware.center
Hello, somebody could help me in a backup of the persist or efs folder for moto g5 xt1671?, this problem ocurred me when i flashed the original firmware and i forgot make a backup of that partition, please.
thank you very much for your attention.
Your device is a G5 (cedric), not a G5 Plus, right? If so, you're in the G5 Plus forums.
However, you do NOT want to flash any other device's persist, you will permanently cause damage to your phone. Instead, back up your persist and efs now, and then look at this thread:
https://forum.xda-developers.com/g5-plus/how-to/fix-persist-resolve-imei0-explanation-t3825147
The links in that thread are specific to potter, but the same principles apply.
I restored someone's else persist when i didn't know how bad it was... Im at imei 0 and only calls. is there any way to get 3g bacck?
Sorry man, but the best case is that you have an old backup of efs when it was working if you don't have your own persist.
Hey there folks,
here I am now too on the forum, trying to find a solution for an old sticky problem.
So far a some people here on the forum a while ago have had the problem that when they flashed a custom OS on their Zenfone 3 while data roaming was turned off in the stock rom, they could never get it working unless reverting back to the stock OS and switching it on there before reinstalling the custom OS. Until then only normal calls and SMS work.
I'm having the same problem now and trying to avoid going back to stock, so I wonder if somebody has found another solution by now? Any help would be really appreciated, and I think a lot of other EU people who will run into this problem in the future will be grateful too if this could be solved easier somehow :fingers-crossed:
Update: I took a look at the firmware partition and there is a folder image/modem_pr which seems to include the configuration how the phone connects to mobile networks. I don't claim to have any special knowledge about it but i would expect this is where the stock rom most probably makes its change about data roaming.
So maybe, as long as what the firmware partition contains is generic firmware, could somebody who has data roaming working on their Zenfone3 send a copy of their /firmware/image folder so I can compare the two and hopefully find the missing puzzle piece to get data roaming working?
I would of course post the solution here for everyone in case I figure it out! Would be great if we can solve it
I have the same problem. Please help.
So, here's an update:
After going crazy searching for a possible fix I gave up yesterday and re-installed the stock rom in order to turn on data roaming (since my TWRP backup won't boot that is something I had been trying to avoid, because the only way I found to do this was to either install a recovery from somewhere on the internet that is claimed to be the original Asus recovery but has no way to be integrity-checked for possibly including malware, or to install software designed to bypass Google's SafetyNet and other system integrity checks. Nah.)
Today I took a look at comparing a TWRP backup of the modem partition (contents identical to the one that mounts as "firmware"), and the persist partition. I wrote a script that would calculate the md5 checksum for each file and then compare for any changes.
On the modem partition, only binary files named Widevine changed, for whatever reason :silly:
And here is a list of the files that were changed on the persist partition:
persist/coresight/qdss.functions.sh
persist/coresight/qdss.log
persist/coresight/qdss.log.old
persist/data/gxflag
persist/data/gxfp/0_0/105885283
persist/data/gxfp/0_0/105885284
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxfeature_table
persist/data/gxfp/0_0/gxflag
persist/data/gxfp/1_0/gxfeature_table
persist/data/gxfp/1_0/gxflag
persist/data/gxfp/calibration_data
persist/data/gxfp/calibration_data
persist/data/gxfp/gxflag
persist/data/gxfp/mptest/gxflag
persist/data/gxfp/raw/0_0/gxflag
persist/data/gxfp/raw/0_0/tpl_index_table
persist/data/gxfp/raw/1_0/gxflag
persist/data/gxfp/raw/1_0/tpl_index_table
persist/data/ifaa_fplist
persist/data/ifaa_fplist
persist/data/widevine/UZT8uT7lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX
persist/data/widevine/UZT8uT7++lR1wsAoECBZWk4+aPFLDG92yRsy5vX3eX.bak
persist/data/widevine/widevine
persist/dmclient/dm_client_info
persist/dmclient/dm_client_token
persist/dmclient/hash_sn
persist/rfs/msm/mpss/server_check.txt
persist/rfs/shared/server_info.txt
persist/sensors/error_log
persist/sensors/sensors_settings
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
persist/.twrps
persist/sensors/sns.reg
persist/time/ats_1
persist/time/ats_12
persist/time/ats_13
persist/time/ats_15
persist/time/ats_16
persist/time/ats_2
Unfortunately, mostly binary files making it impossible for me to dig deeper into the changes. But maybe somebody spots something odd that could lead to the solution.
My next step will be to go abroad again in early March and see if the data roaming now works. If it does, I will restore a TWRP backup of all partitions I could back up before returning to stock. If it still works then, then the stock rom made its change somewhere on one of the partitions TWRP does not back up. If it stops working, then the answer lies hidden somewhere on the TWRP-backuped partitions.
Either way, I'm sure there must be a manual solution, what happens on the stock rom cannot be black magic
Will keep you updated.
Alright, it's the 1st of March and I'm back abroad! I finally have data roaming working and got a little further in my investigation: Restoring partitions one by one, i figured out that the change by the stock concerning the data roaming is made somewhere on the efs partition (which one of the two I can't say yet, as TWRP only lets me restore them both together). Now I haven't succeeded yet how to mount the efs.emmc TWRP backup or otherwise dump the contents of the efs partition, but if someone here knows I'll go dig deeper and track down the specific entry that is changed
Can you tell how to restore the original partition without flashing the asus rom? Thanks
If you ever had data roaming working and created a Nandroid (TWRP) backup at the time, you can simply restore the efs partitions from back then. Just be sure to use the latest TWRP version and make a fresh backup before you go, as there used to be a version some time ago that corrupted efs partition backups.
If you don't, well, as long as I can't read out my efs I can't tell you what to modify in there and how Maybe somebody
I think my only option is to flash the original Asus rom. It is waste time if only to turn on the data roaming.
It's a long story but in brief I have a KB2007 TMO which Network unlocked, Bootloader Unlocked ( Official method, with unlock_code.bin from TMO ). I used this device to do the testing of Custom ROM. One day, accidently I did a format all ( wipe all partitions ) on the device, then I had to use MSM Tool to recover it. Strange thing is, I can only use MSM for 9R Ported ROM for 8T to bring it back to life ( as the most recent ROM I tried before the accident is the 9R ported ROM ). Then, in order to bring it back to 8T OOS, I flashed the original param.bin then I can use normal 8T MSM to revert back to OOS.
But, since then, the device is not able to connect to Cellular network anymore, even it still recognize the SIM CARD inserted ( I also recover device's original IMEI, MEID...but NV Data, EFS from same variant 8T device of mine ). Tried all the possible methods that I know to make it connect to the cellular but so far no luck.
So if anyone have faced this situation or have information about it, please kindly share. Thanks
P/S: I upload 2 pics which briefly describe the situation of the network on my device now. If any other information may need to clear out the info, pls let me know
I corrupted the persist partition on my NordN10 awhile back, which f'd it up in a myriad of fun ways. I eventually cojoled someone into to dd'ing me a copy of persist from another tmo n10, which got the device into a sane condition to fix everything downstream of that.
I learned a couple things while trying to fix it before I had another persist partition; always backup persist/modem/efs partitions shortly after rooting a OnePlus, and to use bkerlers edl tool to make an advanced, engineer grade, backup. One that can unbrick the device without using msm/fastboot and avoids the hasle of finding a computer with windows on it.
I have a persist backup if you want to try that, and I'm going to make a carbon copy of the device with bkerlers edl soon. I did the impatient thing and converted to eu to get root while waiting for the unlock token from OnePlus. However a dump of the stock tmo rom with a locked bootloader is on my agenda.
I would recommend restoring tmo's modem/efs partitions (like twrp can handle) and/or nvram level things that edl tool can handle. Let me know and Ill dump whatever chunk of firmware my tmo 8t has. Just got it today, so it's far from settled into a daily user.
Here's the edl tool from GitHub (you may need to compile it)
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Edl tool is worse case scenario, I'll backup modem/efs on request in recovery or with good ol dd
Also there's an app called Network Mode Universal in playstore that brings up an otherwise obfuscated Network Menu.... I use it to select 5G on 12+ gsi roms for my n10. You'll figure it out soon, good luck
mrbox23 said:
I corrupted the persist partition on my NordN10 awhile back, which f'd it up in a myriad of fun ways. I eventually cojoled someone into to dd'ing me a copy of persist from another tmo n10, which got the device into a sane condition to fix everything downstream of that.
I learned a couple things while trying to fix it before I had another persist partition; always backup persist/modem/efs partitions shortly after rooting a OnePlus, and to use bkerlers edl tool to make an advanced, engineer grade, backup. One that can unbrick the device without using msm/fastboot and avoids the hasle of finding a computer with windows on it.
I have a persist backup if you want to try that, and I'm going to make a carbon copy of the device with bkerlers edl soon. I did the impatient thing and converted to eu to get root while waiting for the unlock token from OnePlus. However a dump of the stock tmo rom with a locked bootloader is on my agenda.
I would recommend restoring tmo's modem/efs partitions (like twrp can handle) and/or nvram level things that edl tool can handle. Let me know and Ill dump whatever chunk of firmware my tmo 8t has. Just got it today, so it's far from settled into a daily user.
Here's the edl tool from GitHub (you may need to compile it)
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Edl tool is worse case scenario, I'll backup modem/efs on request in recovery or with good ol dd
Also there's an app called Network Mode Universal in playstore that brings up an otherwise obfuscated Network Menu.... I use it to select 5G on 12+ gsi roms for my n10. You'll figure it out soon, good luck
Click to expand...
Click to collapse
Sorry for late reply bro. And yeah, one of the most stupid thing of me is that I do not have any critical partitions backup before playing with the 1+ devices ))) About EDL tool which you mentioned, I did tried it awhile back and it did helped to flash the GPT into the device so I can ( at least ) put the device into EDL mode to use MSM and bring it back to life.
And since I can't think of any worse situation for my 8T, so I would like to try any method we can think of which possibly to solve the situation. So, pls help to send me the backup of you, I'd love to give it a shot ( in fact, can't find a good persist backup anywhere even on some paid site which I was disparately purchased when trying to recover my 8T+ ))) )
i actually had this the other day when i had to have them change my sim card to a new one. there was no flashing i am on the global rom (11) after they did the swap in the system i had the same type of thing. they had to go in and reset everything and then re add the sim. yours may not be the same issue but it did fix this for me.
I think my situation is quite different since it caused by Format all ( wipe out all partitions ). Therefore the NVDATA is corrupted and persist is damaged. And since my device is fully Unlocked from TMO so I did tried many SIM CARDs, the issue remains (