[HOW TO] Restore lost Redmi Note 3 pro LTE after upgrade from custom vendor firmware - Xiaomi Redmi Note 3 Guides, News, & Discussion

After lots of dead ends I finally found a solution, flash global QCN on the Chinese version of the phone.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up as QCN, this is your original is anything goes wrong.
2.5 Make sure you have your IMEI written somewhere.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Alternate method:
Use RF_MV_Manager to restore IMEI directly to the QCN file, youll need to use the QPST from that thread, the other one doesn't have RF_MV_Manager.
Restore only QCN, LTE fixed.
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.

vkass said:
After lots of dead ends I finally found a solution.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up twice, once as QCN and once as XQCN.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.
Click to expand...
Click to collapse
Is there a QCN or XQCN with all US LTE bands unlocked yet?

LiQuiD_FeAR said:
Is there a QCN or XQCN with all US LTE bands unlocked yet?
Click to expand...
Click to collapse
I don't think there will ever be one.
You can unlock all the bands you need with http://forum.xda-developers.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774
If it doesn't work there might be a filter, which is a hardware mod.

vkass said:
I don't think there will ever be one.
You can unlock all the bands you need with http://forum.xda-developers.com/redmi-note/general/unlock-lte-bands-step-step-xiaomi-mi-t3084774
If it doesn't work there might be a filter, which is a hardware mod.
Click to expand...
Click to collapse
I tried to set my nv memory up for AT&T and my current values look like this:
sim0
00441 : 0xFFFF
00946 : 0xBFFF
01877 : 562950069289347
02954 : 131072
06828 : 2061719111903
06829 : 2061719111903
I get 4g in Europe where i am currently but i haven't been to America to try it on at&t yet

LiQuiD_FeAR said:
I tried to set my nv memory up for AT&T and my current values look like this:
sim0
00441 : 0xFFFF
00946 : 0xBFFF
02954 : 131072
06828 : 2061719111903
06829 : 2061719111903
I get 4g in Europe where i am currently but i haven't been to America to try it on at&t yet
Click to expand...
Click to collapse
Well I guess you'll find out if it worked when you get there.
If it doesn't it's probably hardware filter.

vkass said:
After lots of dead ends I finally found a solution.
1. Go here and go up to step 6 and STOP. Make sure you don't delete with ADB before you backup with QPST too (see step 2)
2. Go to QPST -> Start clients -> Software Download -> Backup --- Back up twice, once as QCN and once as XQCN.
2.5 Make sure you have your IMEI written somewhere.
3. Download QCN and XQCN + All you need for the guide , proceed with the guide until step 12 and then first restore the QCN, reboot -> restore edited XQCN, reboot
4. Enjoy LTE
5. Backup new QCN with working LTE.
Drivers:
Drivers
Bonus:
Using this guide, make sure you still have band 4, original value should be 2061584302303.
Click to expand...
Click to collapse
if not root can't?

@aried73 must be rooted

thanks I made everything as you wrote, LTE began to catch well! but now I established android 5.1.1 AOSP, I can establish CM13 and not lose the qcn control?

I still have the following issues after following the steps:
- 4Gs network are actually detected when doing network search, but it will be 3G after we select it anyway
- setting preferred mode to LTE Only will make things worse: can't search for network
- in 2nd sim 4G works fine
any help?
Edit: actually I also want to ask: should I first restore your QCN file (80DE5873_0), unmodified? (I did). What's the difference between XQCN and QCN

Hi just wanna ask if this tutorial actually are the method to repair IMEI for anyone that have invalid or blank IMEI after flash / upgrade from custom vendor ROM?
Mine updated from custom vendor ROM MIUI7 (version 7.1.9.0.0) to MIUI7 (7.3.2) the IMEI seems ok, both SIM have different IMEI, even after flash to MIUI8 dev, for unlocking bootloader purpose, the IMEI seems valid, still only SIM2 able to lock 4G.
P/S : Currently I'm on CM13 look like the IMEI still valid and okay and yet only SIM2 can do 4G,
BTW does the method above can be apply on CM13 or just under MIUI environment?

What you're doing here is flash default global qcn file.
If you got a phone with custom firmware it's probably the Chinese version and that's why LTE doesn't work.
@salzzz yes that right first qcn then xqcn, I don't know the default imei for the qcn so can't edit it, only with alternate method I posted after.
Which ROM and radio are you using?
Make sure you use adb commands from the guide to wipe everything related to radio.
@Kirk77777 flashing Roms has not affect on qcn.
@BaTaK_iCe like I said it flashes default global qcn, it will fix any issues with radio, whether it's Lte or imei. Works with any rom.
Basically like going back to global stock.

@ vkass
hello please say why on cm13 santoshi, and other customs, lte only on 2sim slot ?

Kirk77777 said:
@ vkass
hello please say why on cm13 santoshi, and other customs, lte only on 2sim slot ?
Click to expand...
Click to collapse
It didn't work for you.
You need to follow the guide completely step by step, wiping with adb is crucial.
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
reboot
Just restoring the QCN should give you LTE, but the IMEI will be different, that why you need to restore XQCN with your IMEI.
OR like I said in OP follow alternative method and edit IMEI in QCN directly.

It didn't work for you.
You need to follow the guide completely step by step, wiping with adb is crucial.
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
reboot
I DO THIS, its not working to me, i`m sad ((

I have tried it again:
I can't install the QPST from alternative method link, so I followed "the guide" (restoring imei), followed that dd-fill-with-zero, restore QCN.
I managed to restore imei using QXDM, yet LTE is still not working (before & after I restore imei)
I'm on CM13 1807 by Santosh, some days ago there's a radio.zip in that thread, and I flashed it, dunno which version, but baseband shows -8976_GEN_PACK-3.53308.1.57464.1
I'm not sure about imei, too, first time I bought the phone it comes with same imei, only 1 imei on box (which matches both sim imeis),
Phone comes with 7.19 rom. forgot whether the LTE was working/not though; after I flashed global rom, I just check that LTE is detected in both SIM1/2, but only works in sim 2

salzzz said:
I have tried it again:
I can't install the QPST from alternative method link, so I followed "the guide" (restoring imei), followed that dd-fill-with-zero, restore QCN.
I managed to restore imei using QXDM, yet LTE is still not working (before & after I restore imei)
I'm on CM13 1807 by Santosh, some days ago there's a radio.zip in that thread, and I flashed it, dunno which version, but baseband shows -8976_GEN_PACK-3.53308.1.57464.1
I'm not sure about imei, too, first time I bought the phone it comes with same imei, only 1 imei on box (which matches both sim imeis),
Phone comes with 7.19 rom. forgot whether the LTE was working/not though; after I flashed global rom, I just check that LTE is detected in both SIM1/2, but only works in sim 2
Click to expand...
Click to collapse
I really don't know, maybe check phone settings at
*#*#4636#*#* and make sure it's on LTE for sim1.
As you can see it works for me, I also have same imei for both sims.
AFAIK the radio zip is for official cm, maybe backup your rom and try flashing stock MIUI just to see if it works.

hi, just wondering how come i dont get the option to use xqcn in qpst?? it only allows me to restore qcn
[edit] updated version of qpst allows xqcn.
But now I'm getting this error when i try to restore xQCN after QCN
"The ESN of the phone does not match the ESN of this file containing RF calibration data"
What should i do?

I'm also getting. "No space on device" error when i run these commands
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16

Need to tick "allow file esn mismatch", restore anyway.
The error doesn't really make sense as it is used to delete.
Maybe the process needs to be done on stock MIUI.
Btw do you execute them one by one?

Dimmz said:
I'm also getting. "No space on device" error when i run these commands
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
Click to expand...
Click to collapse
according to this, it's just a false positive error, you can ignore it
@vkass LTE is on for sim 1 and 2 (if it isn't, it shouldn't have been detected when doing network search either)
Hopefully there'll be a solution for this soon. Btw, what's your baseband version?

Related

[FIXED] IMEI #2 = 0, due to fastboot erase modemst2

UPDATE (07-Jan-2017):
If your OnePlus 2's IMEI#2 = 0, (IMEI#1 is showing correct IMEI)
Because you run these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Then,
A fix has been made into this zip file.
https://www.androidfilehost.com/?fid=529152257862693598
Kindly thank Tony.L & Crystal.Z from OnePlus OOS team.
You have to be on OOS 3.5.6 (Clean-Flashed, non-rooted, from whatever ROM you are currently on).
I had TWRP Hybrid Recovery v3.4 installed.
IMEI#2 will come back again.
Now, Remember to backup EFS using terminal method.
& DONT erase modem ever again.
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
I would appreciate your help.
Click to expand...
Click to collapse
***************************************
lockmunk said:
mine have same problem..only IMEI2 shows "0"..my phone keep random rebooting until now
Click to expand...
Click to collapse
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Tunatje said:
Lesson for you guys. The first thing to do after flashing a custom recovery is to make a complete nandroid backup..
Click to expand...
Click to collapse
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Spannaa said:
FYI, a full nandroid backup doesn't backup the two EFS partitions even though EFS is an option in TWRP's backup menu.
You need to manually backup the modemst1 & modemst2 partitions
Click to expand...
Click to collapse
True. Done it myself through terminal. Forgot about the dual sim :laugh:
osr.arora said:
I will be really grateful, if anybody can help me recover/write IMEI#2 on my OnePlus 2.
IMEI#2 currently shows as "0", (IMEI#1 is showing correct IMEI)
I don't have a EFS backup.
Device is out of warranty.
OnePlus's L2 support team, flashed OOS v3.1.0 via Qualcomm recovery method via remote session, but still no fix.
Lastly (I think, some may consider this illegal, but I'm just trying to write the missing IMEI on my phone),
I searched for IMEI writer softwares ( WriteDualIMEI(W+G_eMMC), Read&Write_Tool_v1.3) on internet, but somehow, i couldn't make them work (Maybe incorrect Qualcomm drivers on my PC, or idk what )
*********How did this all happen*********
I read a blog, that In order to increase the download speed from the Jio SIM, preferred LTE Band should be switched (from 3 to 40).
So, I pressed *#*#4636#*#*, >> Phone Info page >> three dot menu >> select radio band >> SELECTED Band mode 40.
Immediately after that,
Vodafone Sim stopped working in any of the SIM-Slots, But Jio sim (4G) was working in both the slots.
*****
Then I ran these commands in fastboot mode:
"fastboot erase modemst1 "
"fastboot erase modemst2 "
"fastboot erase cache"
Immediately, Both the SIM slots stopped working.
*****
Then I flashed "new-modem.zip" from benschhold (https://androidfilehost.com/?fid=24407100847293158)
which makes SIM-Slot-1 work with both Vodafone & Jio,
But SIM-Slot-2 only detects the sim, but with 0 network bars i.e. "No service| Vodafone"
***************************************
I would appreciate your help.
Click to expand...
Click to collapse
Did you managed to get any info on that??
I also encountered the exactly same issue..
ashu01 said:
Did you managed to get any info on that??
I also encountered the exactly same issue..
Click to expand...
Click to collapse
No Fix, as of yet !
Somebody said, he flashed modem files from beanstalk Rom thread, & that fixed the missing IMEI issue.
I haven't tried it yet,
If you try it, & it fixes this problem, update me on thia thread !
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
Can u send me persist.img pls
My email is [email protected]
Would be better, if you upload persist file here.
pitrus- said:
Hi
Like I wrote in another thread, this is what I did to get working modem after testing out the unstable H2OS firmware
1. Ran TWRP backup of CM14 install
2. Restored OOS 3.1 OTA zip
3. Formatted modemst1 and 2 and persist partition using fastboot
4. Did factory reset and booted up OOS and powered down the phone
5. Powered up into fastboot and restored persist partition with the persist.img dump found in some thread in this forum
6. Restored back my CM14 install and now everything is working again (except for losing some configuration probably stored in the persist partition like button swapping and battery text on icon)
Best regards
Click to expand...
Click to collapse
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
pitrus- said:
Yes they did, after flashing the H20S firmware and going back to OOS firmware I was missing IMEI on both modems/incompatible modemst partitions. Formatting these and booting up OOS recreated these and after also restoring persist partition both IMEIs was reported and Cyanogenmod no longer bootlooped.
Click to expand...
Click to collapse
Before flashing H2Os firmware,
What was your OP2 running ?
Also can you list all links to files, which helped you.
Just an hour ago, i flashed "ResurrectionRemix-6.0-OOS-2.2.1-Modem.zip" on my OnePlus 2 (running Oxygen OS 3.1.0 with TWRP) & it went into bootloop.
So now i'm downloading @Spannaa 's "Oxygen OS 2.1.1 fastboot.zip" , to make my phone working again.
osr.arora said:
We are facing missing IMEI#2 issue,
Did your steps, fix this issue ?
Click to expand...
Click to collapse
I though my phone was fine, then I noticed my swedish BankID just didn't want to work. Turns out my SIM2 has null IMEI just like yours. Tried Qualcomm restore to OOS 3.0.2 but still IMEI2:0, so it looks like trying out the H2OS 2.5 beta firmware and going back was a real killer for my phone. I get signal on both SIM cards and strangely I can call using both SIM cards even though one is showing no IMEI
Update
After analyzing the nv data of my phone, I can tell that the IMEI for SIM card 1 is there, and there does not seem to be any address register for a second IMEI so the phone must figure this out itself. For me the first IMEI ends with a 99 and second with a 81 which means a difference of -18, perhaps second IMEI is always -18 hexadecimal from the first and therefore automatically calculated and registered by the modem firmware?
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
pryggi said:
@pitrus-
Do you have a European A2003 model? I remember that the difference between European and Chinese models was that the Chinese has only 1 IMEI. Maybe this H20S firmware changed your European model effectively to Chinese. FYI my IMEIs, untoutched by H2OS, differ by 8, 72 vs 64. You can check your original IMEIs from the red box that the phone shipped in, if you still have it.
To resolve this, Oneplus customer service recommends to replace the motherboard:
https://forums.oneplus.net/threads/those-who-lost-their-imei-please-read.475930/page-5#post-15427155
Click to expand...
Click to collapse
Yes, it's an A2003 European model. If only I had a dump of a working A2003 NV Data so I could find the difference between them. Whoever could give me this could just zap out 00550 NV Item (IMEI) so as not to share it with me. That would tell us which NV Items to change to swap between single och dual sim card modell.
@pitrus-
I have the IMEIs on my OP2 still intact, I have not flashed latest H2OS beta, nor have I used the fastboot erase/format commands. So I can analyse the /dev/block/mmcblk0p17 and /dev/block/mmcblk0p18 dd dumps. Could you tell me which tools to use, or how can I edit out my IMEIs?
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
osr.arora said:
Really confused, what to flash, what not to flash (to fix the IMEI issue) !!!
I restored my OP2 to OOS 2.1.1 with Qualcomm Restore Files (from OnePlus Forums) as @Spannaa 's fastboot file, didn't worked, idk why !
Click to expand...
Click to collapse
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
pitrus- said:
It doesn't mather what you flash, our nv data is incompatible with all modems other than the unstable H2OS 2.5 one. Only solution is to wait for a OxygenOS modem that uses the same nv data structure if you like me didn't make a dump of the nv data before flashing the H2OS ROM. If you do want to go back to CM14, just flash H2OS 2.5.x and then format system, data, cache and flash latest CM14. You will still get null IMEI on second SIM slot, there's no solution for this right now. (You could also Qualcomm restore back to OxygenOS 3.1, this will give you the TZ needed by CM14).
Click to expand...
Click to collapse
i also used fastboot erase command..and in the same situation of showing imei2 0.
do you think the oos update will have a fix for this issue??

How do I backup my IMEI?

I was told to backup my IMEI before fashing CM14.1. I looked at this guide and because I don't want to go through the hassle rooting my phone I decided to go with the twrp backup way because I was going to backup with twrp anyway. But when I go to backup it doesn't show the EFS partitition like in the guide. I have Boot, System, Data and Cache. Will I need to root my phone or is there an easy fix to this? Also my phone is a moto G4 and not a G4 plus but I thought I'd ask here because the non-plus forum is kinda dead.
Florensie said:
I was told to backup my IMEI before fashing CM14.1. I looked at this guide and because I don't want to go through the hassle rooting my phone I decided to go with the twrp backup way because I was going to backup with twrp anyway. But when I go to backup it doesn't show the EFS partitition like in the guide. I have Boot, System, Data and Cache. Will I need to root my phone or is there an easy fix to this? Also my phone is a moto G4 and not a G4 plus but I thought I'd ask here because the non-plus forum is kinda dead.
Click to expand...
Click to collapse
In my lg g3 i have this option in twrp, it was nice if we had also in our moto g4.But for now we do not have.
Sent from my Moto G4 using XDA Labs
1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)
velosa said:
In my lg g3 i have this option in twrp, it was nice if we had also in our moto g4.But for now we do not have.
Sent from my Moto G4 using XDA Labs
Click to expand...
Click to collapse
So do I need to root my phone or is the IMEI stored in any of the other partitions TWRP backs up? Also, can't I just write down my number from the about tab in Android?
Sent from my Moto G (4) using XDA-Developers mobile app
gabriwinter said:
1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)
Click to expand...
Click to collapse
Thanks I'll take a look at that.
gabriwinter said:
1. Backup all available in twrp
2. Follow this for root -> http://forum.xda-developers.com/moto-g4-plus/how-to/root-systemless-rooting-supersu-2-74-2-t3405772
3. Download Flashfire -> https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en_GB
4. Set selinux to permissive temporary:
Code:
su
setenforce permissive
5. Open Flashfire and select RAW partition backup.
(I would backup all, but for IMEI you only need modem partitions)
Click to expand...
Click to collapse
EDIT: I restored my backup and it's fine now. But I sure did almost have a heart attack. I am on nougat soak test which was causing issues.
I did the second step but now my IMEI doesn't show up anymore, my SIM isn't found, I can't find any networks, my IP address is gone, my mac address is reset. Do I restore the backup?
tl;dr: topic in the second step barely points out the fact it only works on marshmellow (small, non bold, normal size letters at the top of the topic), flashed it anyway, almost lost my IMEI while trying to backup... my IMEI
EDIT 2: sorry for being such a noob, but wouldn't it be better to go straight to CM, root it with CM's built-in rooting functionality and then do the backup? Would there be a higher chance of losing an IMEI number in the process of that than in the process of your instructions because for your instructions I need to go back to marshmellow, root, backup IMEI, flash nougat (people say CM has less issues if you flash nougat first), flash CM? How do you even 'lose' your IMEI?
I'm sorry I didn't realise you where using nougat.
Yes flashing CM and then using flashfire will work just fine.
You will be taking a backup of the soak version of your modem partitions.
You won't loose your IMEI flashing CM because it doesn't change the modem partitions.
The only way you can loose your IMEI is by using fastboot (or flashfire) and flashing the wrong version.
So you don't need to worry about losing your IMEI at this stage.
gabriwinter said:
I'm sorry I didn't realise you where using nougat.
Yes flashing CM and then using flashfire will work just fine.
You will be taking a backup of the soak version of your modem partitions.
You won't loose your IMEI flashing CM because it doesn't change the modem partitions.
The only way you can loose your IMEI is by using fastboot (or flashfire) and flashing the wrong version.
So you don't need to worry about losing your IMEI at this stage.
Click to expand...
Click to collapse
No problem, you couldn't have possibly known that. I should have mentioned it. Thanks for the help yet again.
Sent from my Moto G (4) using XDA-Developers mobile app
I may be asking a stupid question but how do you "lose" your imei? Isn't that the serial number to the device. I mean it's stamped on the back of the battery. I wouldn't think that is possible, isn't that how your phone gets blacklisted?
daverobinson88 said:
I may be asking a stupid question but how do you "lose" your imei? Isn't that the serial number to the device. I mean it's stamped on the back of the battery. I wouldn't think that is possible, isn't that how your phone gets blacklisted?
Click to expand...
Click to collapse
The phone cannot read what's stamped on the back of the battery. It needs something to tell it that the IMEI number is so-and-so. The IMEI number thus is stored in a particular partition of your phone, one that is usually never touched by the average user.

I9505 "no service" on custom rom

Hello,
there is something weird going on: If I flash a custom rom (cm13, cm14.1/Lineage14.1) the 9505 shows the "no service" notification and network service is actually not available. Wifi just works fine. I ve read about problems with the baseband and some IMEI problems but both seems to be ok.
What I habe done in overview:
Rooted the phone with Heimdall and CF Root by chainfire
installed TWRP via app
full backup of original firmware
full wipe
flash custom rom (CM13/CM14)
"no service"
If i wipe and restore the original firmware again, mobile network is just working fine!!!
So, what could be the problem? I was wondering if its a hardware problem but as described with samsung os it works. So please help me!
Thanks and best regards,
hibbert
Is the phone running the latest bootloader and modem?
Try flashing the Optimized Lineage ROMs, 13 or 14 doesn't matter.. Those are unified, so chances are that it will work on many Snapdragon S4 models.
audit13 said:
Is the phone running the latest bootloader and modem?
Click to expand...
Click to collapse
Bootloader and Baseband are: I9505XXUHOJ2
Where can I find an overview about the newest Bootloaders and Modems?
Br
Hibbert
You can compare the bootloader and modem to ROMs found at sammobile.com. The phone looks like it is up to date so I'm not sure why it is not connecting to your carrier.
Try using the IMEI Backup/restore tool by Antaresone:
https://forum.xda-developers.com/showthread.php?t=2975136
Start with a working firmware making sure you have installed the tool as directed in the above thread.
Using a terminal emulator type SU and grant root access.
Type imeibkp and hit enter. Allow it to create a backup.
Flash ROM of choice, Gapps, and the IMEI Backup.
Boot ROM and using WiFi reinstall a terminal emulator.
Run the IMEI backup/restore tool and restore your IMEI backup.
Reboot.
This method has worked for me in the past. Hope it helps.
Until now i cant fix the problem. The imeibkp solution did not work. Any other ideas?
Best regards
Hibbert
FernBch said:
Try using the IMEI Backup/restore tool by Antaresone:
https://forum.xda-developers.com/showthread.php?t=2975136
Start with a working firmware making sure you have installed the tool as directed in the above thread.
Using a terminal emulator type SU and grant root access.
Type imeibkp and hit enter. Allow it to create a backup.
Flash ROM of choice, Gapps, and the IMEI Backup.
Boot ROM and using WiFi reinstall a terminal emulator.
Run the IMEI backup/restore tool and restore your IMEI backup.
Reboot.
This method has worked for me in the past. Hope it helps.
Click to expand...
Click to collapse

Redmi 4 prime no service

I have a redmi 4 prime with no singnal in any slot. I flashed the global rom and the i had this problems. Imeis are ok and read sim but no signal. I read for redmi 4 a way to solve it flashing the modem again by twrp. Where can i find the modem for redmi 4 prime to flash???
Sorry for my english and thanks.
flashed all modems and no signal still. please help!!
Solved. If somebody have the same problem, send me a pm and i help him.
mek32 said:
Solved. If somebody have the same problem, send me a pm and i help him.
Click to expand...
Click to collapse
Reply here for future troubles.
First of all, i erased the modems with the phone rooted using adb commands (erased modemst1 and st2 on the their partitions).
Unroot the phone to open the diagg port typing on dialer *#*#13491#*#*.
Used the QFIL program to restore the phone using a qcn archive who send me a user which cotains their imes and baseband configuration.
Reboot and open the diagg port again.
Used the WriteDualIMEI_W_G_eMMC to rewrite my owns imeis.
Reboot and all wherw fine.
I ll create a qcn with fakes imeis to restore your baseband if you need. Then, you only have to rewrite the imeis with the WriteDualIMEI_W_G_eMMC program.
You will find the programs searching in google easly.
Good luck
mek32 said:
First of all, i erased the modems with the phone rooted using adb commands (erased modemst1 and st2 on the their partitions).
Unroot the phone to open the diagg port typing on dialer *#*#13491#*#*.
Used the QFIL program to restore the phone using a qcn archive who send me a user which cotains their imes and baseband configuration.
Reboot and open the diagg port again.
Used the WriteDualIMEI_W_G_eMMC to rewrite my owns imeis.
Reboot and all wherw fine.
I ll create a qcn with fakes imeis to restore your baseband if you need. Then, you only have to rewrite the imeis with the WriteDualIMEI_W_G_eMMC program.
You will find the programs searching in google easly.
Good luck
Click to expand...
Click to collapse
Thank you. It's a common way to solve that problems but good that sb wrote it.
mek32 said:
First of all, i erased the modems with the phone rooted using adb commands (erased modemst1 and st2 on the their partitions).
Unroot the phone to open the diagg port typing on dialer *#*#13491#*#*.
Used the QFIL program to restore the phone using a qcn archive who send me a user which cotains their imes and baseband configuration.
Reboot and open the diagg port again.
Used the WriteDualIMEI_W_G_eMMC to rewrite my owns imeis.
Reboot and all wherw fine.
I ll create a qcn with fakes imeis to restore your baseband if you need. Then, you only have to rewrite the imeis with the WriteDualIMEI_W_G_eMMC program.
You will find the programs searching in google easly.
Good luck
Click to expand...
Click to collapse
can you upload qcn files ?

Galaxy Tab A T-580 IMEI and NVRAM backup

Hi
I am new to this forum and flashing android devices. Today i just managed to root my T-580 using newest TWRP and Magisk versions. The root-checker says its rooted, SafetyNet passes so eveything seems to be OK.
Before flashing any custom ROM i wanted to backup IMEI and NVRAM but without success.
I have tried different approaches:
1. minimal adb and fastboot - after entering commands i get illegal number of block size
2. platform tools - gives me no such file or directory mesage
3. mtkdroid root tools - device info is not read and backup is grayed out. what is strange that the available free space is succesfully read but not any other info.
Check the attachments for the screenshots.
Could anybody help me how can i backup IMEI and NVRAM data? Without this step i cannot proceed in flashing custom ROM.
Thank you
EDIT: is backing up EFS in TWRP the same procedure as backing up IMEI-NVRAM? so it might be enough to backup EFS to secure IMEI-NVRAM?

Categories

Resources