I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Did you root?
Sent from my Moto G (5S) Plus using Tapatalk
tbiwalkar said:
I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Click to expand...
Click to collapse
I assume you flashed a custom ROM because I have experienced it too. I have IMEI = 0. If you find a solution, please do share. We need someone who will share us a working EFS partition.
Thanks and best regards,
Geb
tbiwalkar said:
I have faced imei = 0 on 3 phones till date and hence I'm **** scared of it.
How to backup imei ?
I mean how to backup the following-
1. EFS partition
2. Modemst1 (imei 1)
3. Modemst2 (imei 2)
Also is there any solution as of now to imei=0 if there is no backup saved? Also will a twrp backup of all available partition help?(because it didn't help on OnePlus 2)
Click to expand...
Click to collapse
I am new to this device but i know modemst1 and modemst2 is not IMEI thing and you cannot backup it, or it is not needed..
And also don't know if which partition is correct for backup of IMEI. But you can try restoring all partitions.
gebcruz06 said:
I assume you flashed a custom ROM because I have experienced it too. I have IMEI = 0. If you find a solution, please do share. We need someone who will share us a working EFS partition.
Thanks and best regards,
Geb
Click to expand...
Click to collapse
Have you tried flashing stock firmware ?
For your information, EFS contains backup of IMEI for individual devices, so why do you think someone will give you their IMEI ?
I have got this device before 2 days, i will see what i can do for you guys, but after 5th February.. Wait till, and try to flash stock...
____Mdd said:
I am new to this device but i know modemst1 and modemst2 is not IMEI thing and you cannot backup it, or it is not needed..
And also don't know if which partition is correct for backup of IMEI. But you can try restoring all partitions.
Have you tried flashing stock firmware ?
For your information, EFS contains backup of IMEI for individual devices, so why do you think someone will give you their IMEI ?
I have got this device before 2 days, i will see what i can do for you guys, but after 5th February.. Wait till, and try to flash stock...
Click to expand...
Click to collapse
I did. Tried so many times even with different versions of the stock firmware, to no avail. Thanks for your kind intention. Please share with us if you have found a way. thanks.
same problem here bro!!
i am able to see efs partition in twrp but wat to do to restore imei
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Sri Datta said:
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Click to expand...
Click to collapse
Which version/ build date of the validus rom? Thanks.
Sri Datta said:
I'm so happy I finally managed to restore my imei .I just flash validus rom 8.1 beta and imei was back
Click to expand...
Click to collapse
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
Bro r u an indian,if yes then despite restoration of imei jio sim won't work.also can u tell me which version of firmware is for Indian varient??
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
jio users must run these commands after flashing validus(run only if jio is not working,and run after 1st boot.)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
volte doesn't work with this method
Sri Datta said:
volte doesn't work with this method
Click to expand...
Click to collapse
You surely wait for official android 8
In G5 plus thread I searched fix imei And also volte doesn't work
Sent from my Moto G5S Plus using XDA Labs
gebcruz06 said:
Thanks, bro
Doing this recovered my IMEI
Bro, I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. Make TWRP backup of your EFS partition
3. Re-flash stock ROM
4. Re-install TWRP and restore your EFS backup
Special thanks to @Sri Datta, @premaca and GZOSP/ Validus devs
Click to expand...
Click to collapse
bro my SIM CARD its dead (i think i have the same problem you had) can you help me please ? i tried roms 7.1.2, 8.0, 8.1
also when i flash stock rom all comands works but ERASE CLOGO AND ERASE CUSTOMIZE FAILED and the phone restart but no sim card
i found a old backup and restored with twep now i have IMEI thank you so much!
Draaaven said:
bro my SIM CARD its dead (i think i have the same problem you had) can you help me please ? i tried roms 7.1.2, 8.0, 8.1
also when i flash stock rom all comands works but ERASE CLOGO AND ERASE CUSTOMIZE FAILED and the phone restart but no sim card
Click to expand...
Click to collapse
Have you tried popping your sim in another phone? Please check imei, *#06#. If it is 0 then your phone will not be recognized by any network. Clogo and customize may show failure msg but it doesn't do anything. I suggest you try first the flashing of stock rom for your variant. Remove sim before flashing and pop it after 1st boot. Check your imei at once. If the above link I mentioned didn't work, try the latest lineage 15.1 build. It has updated rild libs. You can also get signal there and your imei. Once booted in it, reflash modem, clear modemst1 and modemst2, then reboot. Take an efs backup in twrp after.
gebcruz06 said:
Have you tried popping your sim in another phone? Please check imei, *#06#. If it is 0 then your phone will not be recognized by any network. Clogo and customize may show failure msg but it doesn't do anything. I suggest you try first the flashing of stock rom for your variant. Remove sim before flashing and pop it after 1st boot. Check your imei at once. If the above link I mentioned didn't work, try the latest lineage 15.1 build. It has updated rild libs. You can also get signal there and your imei. Once booted in it, reflash modem, clear modemst1 and modemst2, then reboot. Take an efs backup in twrp after.
Click to expand...
Click to collapse
thanks my SIM worked perfect in other device and my IMEI was "0"
so i flashed stock 26.116-64 then restored efs from a old backup now all good :laugh::good:
My jio call service is not working however my internet connection is just fine.(no VoLTE). Can someone help me
Gimmmi said:
My jio call service is not working however my internet connection is just fine.(no VoLTE). Can someone help me
Click to expand...
Click to collapse
Apparently there is no solution for this go to service centre m only they can fix
Sri Datta said:
Apparently there is no solution for this go to service centre m only they can fix
Click to expand...
Click to collapse
never mind
Hola Devs,
Currently I own Mi 5 in which I used to have Lineage os 14.1. But after the recent update i.e Lineage-14.1-20180110 nightly gemini, all of the sensors got pissed of except fingerprint sensor.
Initially I thought it may a hardware problem, but after brown through the root files, I got to find that all my sensor related files are missing from the Persist partition. So I downloaded the fastboot rom the official website and flashed through Mi Flash Tool in both Fastboot and EDL mode. still the problem remains as it is. While flashing, the tools is not even considering the Persist.img file. BTW I even tried to flash through Fastboot cmd, and it is showing error as the partition is write protected, neither the partition is erasing nor is flashing
Can I get any kind of solution??
Or can you provide me the persist flash bat file formatting or flashing the persist Img file.
Or can you guys provide me sensor related files to be placed wherever it is necessary..
BTW wifi Bluetooth nfc fpc all are working except Gyro sensor and Proximity sensor. And also it is not at all showing in Engg mode too(*#*#6484#*#*)
thank in advance
It's the persist partition problem.
You could refer to this thread
http://www.miui.com/thread-6788019-1-1.html
Unfortunately, the language is Chinese. Please use the translator if you can't read it. Of course, you could ask me how to do it too.
Sorry, I am a Chinese, so I may have made some mistakes in grammar. Hope you could understand what I am saying ?
Ask someone to backup him persist with zcx recovery, then restore yours with it and problem solved.
I had exactly the same problem as you and that fixed mines.
Greetings
Hello!
Suddenly my Accelerator and Gyroscope stopped working and i cant figure out why. I downloaded another file persist.img and succesfully flashed via recovery but after reboot, those sensors arent still working. Every other sensor works (light sensor, proximity etc...) and ad this point i dont really know what to try, do you have any suggestion?
Persist if I remember only can be flashed using TWRP and mounting persist partition.
Are you done the flash in that way?
rocalino said:
Persist if I remember only can be flashed using TWRP and mounting persist partition.
Are you done the flash in that way?
Click to expand...
Click to collapse
I have flashed trough recovery selecting persist.img and checking persist box
Check out my thread, I fixed there light sensor problem.
Make sure you take your persist.img file from latest fastboot rom.
Light sensor stuck after QMMI mess
I recently bricked my RN10s and then had to flash stock ROM using the SP flash tool now the sensors are not working properly.
The device turns its screen on and off because it thinks it's being picked up.
The sensors used by google maps show that I'm rotating constantly.
I am new while flashing on A/B partitions and thus ended up bricked, any help will be highly appreciated. I was trying to flash pixel 4 android 13 GSI A/B and also tried dot os but it seems like my device's flash memory after the brick is not working properly because it does not boot into custom twrp by the command Fastboot boot TWRP.img.
looking forward.
flash stock rom and done
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
dequr said:
I flashed the stock ROM using sp flash tool and tried with the mi flash tool but same results.
Click to expand...
Click to collapse
I think it might be due to corrupted persist partition, I never custom romed a device but have been researching for my RN10s and I read that persist contains the sensor data control and l1 certification that's why you need to back it up in case it corrupts. Sadly you can't flash persist from the internet since it's unique to every phone if you flash it you loose l1 certification forever but get back sensor functions (I am not sure about sensor functions returning)
Also there is a tool to fix corrupted persist so do research it but whatever you do make sure you are 100% certain it's what you want changes to persist are permeant (except if you backed up persist before the brick in which case just flash the persist backup)
V.I: as I said I never flashed a device and don't know much about it this is what I read through reddit and research, take it with a grain of salt and do your own research aswell
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
dequr said:
alright so I did some research and re-flashed the persist file from the Fastboot IMG and got the z-axis moving again of the gyroscope and some other started working properly but still the rotation sensor according to google maps and compass is not working properly it's just rotating clockwise while the magnetic sensor is a pass in CIT.
Click to expand...
Click to collapse
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Okay will try this now truly appreciate the support thx. Tho the phone is working quite better by time apart from the sensors.
The degree sensor or smt like that is just increasing to 360 and then will start from 0 again
killer_v41 said:
This is because persist is unique to each phone and each sensor, you should have searched for the tool that fixes corrupted persist first. Anyways there might be another issue to this as flashing official tom through mi flash tool should fix any corruption in persist anyways try finding some solutions on reddit you might find something there
Click to expand...
Click to collapse
A
tutibreaker said:
you flashed miu 13 rom with android 12? if does, the problem is the rom itself has many bugs in sensors, you must flash miui 12.5.16.0 with miflash and select flash_all to wipe all partitions and rewrite them
Click to expand...
Click to collapse
Any suggestions form where to download because there are lot of sites available
This is the sensor data and as you can see Orientation sensor along with the rotations third value and the z axis of gyroscope and accelerometer isn't working well so ill re-flash with the first miui this phone had and apply updates on it hopefully it will fix the errors.
Your browser is not able to display this video.
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
alright so I was going thru the images and I couldn't find any persistence in both 13.0 and 12.5 but now as I am now the question is how are the x and y axis keeping their value correct while z isn't so will tho ask for a persist file but just curious how is it detecting sensors then ??
dequr said:
Alright so the result is the same rn I'm running miui 12.5.2 (android 11) now what I saw after reading the results from the command fastboot getvar all that there is written no after persist I was thinking if any of the redmi note 10s users could upload a back up of their persist.img and I could try flashing as it would help in knowing what is going on phones model M2101K7BG tho the point to be noted is that the mi flash said successful while phone booted on fastboot and had to use twrp to flash the recovery and again it showed some errors but after booting the phone is working
Click to expand...
Click to collapse
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
killer_v41 said:
That is the issue my friend each persist is made specifically for that phone it is unique to a phone not a model so if you do flash persist of a back up from a phone of same model see sensors will either not work at all or be extremely wrong
Click to expand...
Click to collapse
Yea I discovered the fastboot ROM didn't have persist.img and I've stopped trying because the gsi has detected it and some how some things have been fixed I've also seen. File named gsi_persist_data in /data nvr opened it but gyroscope while gaming doesn't stop and raise to wake works.