Related
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
mikeboballen said:
http://forum.xda-developers.com/showthread.php?t=2972693 I don't know if this can help you or not I'm assuming you've already seen it
Click to expand...
Click to collapse
That was the guide I was following, which led to this somehow.
I'm thinking about re-locking and un-rooting now so I'll have a shot at the warranty claim.
Good luck man hope it all works out for you
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
JulesJam said:
On this Nexus 6 thread some people had success flashing back to stock modems/baseband - these would be the commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
http://forum.xda-developers.com/nexus-6/help/imei-repair-t3000420
Then if that doesn't work then this:
http://forum.xda-developers.com/showthread.php?t=1960918
Then there is this:
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
ccarrionc said:
Thanks, but nothing worked. I'm starting to wonder if it might be a hardware issue...
Click to expand...
Click to collapse
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
JulesJam said:
Did you try this method using QPST?
http://forum.xda-developers.com/showthread.php?t=1960918
Click to expand...
Click to collapse
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
ccarrionc said:
I did, but I couldn't get the software to recognize my phone, it does seem kinda outdated (2012). Used QPST 2.7.
Click to expand...
Click to collapse
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
JulesJam said:
Sounds like you need to get a warranty replacement. It could be a hardware problem but even if it is not, they really need to make these phones less easy to eff up.
The IMEI is on the efs partition that we cannot even flash so I don't know how they can get messed up by the consumer but obviously they do. Someone on the N6 thread was saying it is a Qualcomm issue.
Click to expand...
Click to collapse
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
ccarrionc said:
If I can't get the unlocked bootloader warning to go off, then I'm done for I think.
Click to expand...
Click to collapse
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
---------- Post added at 03:49 AM ---------- Previous post was at 03:46 AM ----------
ccarrionc said:
Unless people at the support center don't bother restarting it or anything... fingers crossed.
Click to expand...
Click to collapse
They will know b/c you got an unlock code to unlock it.
ccarrionc said:
Plan B is to hardbrick it somehow so no one can turn it on and see my mess, haha.
Click to expand...
Click to collapse
I would check the warranty status online. Even if the warranty is void, they may be able to repair the phone for a reasonable price if you don't hard brick it.
JulesJam said:
That is possible - there are plenty of threads on how to do that.
But even once you relock, your status code will be locked 2, not locked 0 so they can tell from the device. Also, you had to get an unlock code directly from them so if your device didn't qualify for bootloader unlock with maintaining your warranty, then they will know from that too.
Also, your qe will likely show 0/1 even though you unrooted. You can see the qe in stock recovery.
Click to expand...
Click to collapse
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
ccarrionc said:
So the only way is getting the phone to not be able to turn on at all? Is there any known way to get off with it?
Click to expand...
Click to collapse
No, they have you in the database as having requested an unlock code.
ccarrionc said:
So I unlocked my moto X, made a change from XT1097 to XT1095 and installed stock 4.4.4 Pure edition firmware. So far it worked perfectly, then I got an OTA update to 5.0, installed it and after that I had no carrier signal (IMEI was gone and Baseband too).
I have the IMEI number and serial for my device, but I didn't do the backup of the EFS folder. What can I do to fix this?
Click to expand...
Click to collapse
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Steve-x said:
You need to flash an image from your original provider and it will work fine again. Right now you have an incompatible modem and as a result you will have no IMEI/mobile data or wifi as the radio portion of the phone is disabled.
Click to expand...
Click to collapse
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
JulesJam said:
That is what I said above but he said he tried it and it didn't work.
OP - you need to make sure you are flashing the right files - you need to flash the modem/baseband files for your device (XT1097).
Click to expand...
Click to collapse
I am 100% sure the files used were not the correct ones.
juliospinoza said:
As someone post above. You need the stock modem of your phone model, but in your case any xt1097 will work just flash using the Fastboot mode steps and everything will be fine. I have a post on the general section "guide to convert 1097 to 1095" there you can find all the possible scenarios.
Good luck.
Click to expand...
Click to collapse
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
ccarrionc said:
I was following your guide, everything was fine until the OTA update came up. Is there anyway to get back to the xt1097 firmware I had before? It was 4.4.4 with Telcel.
Click to expand...
Click to collapse
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Steve-x said:
What was the exact version you had before? For future reference you shouldn't flash firmware from another provider unless you have original firmware to reflash if you experience an issue.
Click to expand...
Click to collapse
Found a firmware from my original provider, everything is back to normal (except now I have the different status code in the fastboot screen).
For future reference, I just installed the previous firmware through fastboot (with mfastboot, of course). IMEI was recognized again and baseband too.
so I was trying to update to EMUI 9 using Beta Flashy and I forgot to reflash stock recovery after flashing root via TWRP to get Flashy to work, so after the update, it couldn't reset, and when I checked bootloader, FRP was locked and now its stuck in bootloop. can anyone provide me with a method to fixing this issue without requiring me to pay the absurd amount that FunkyHuawei and DC Unlocker charge for restoring?
thank you
edit: solution here
Try Dload method and go back to EMUI8
majidamiri15300 said:
So I was trying to update to EMUI 9 using Beta Flashy and I forgot to reflash stock recovery after flashing root via TWRP to get Flashy to work, so after the update, it couldn't reset, and when I checked bootloader, FRP was locked and now its stuck in bootloop. I read this guide https://forum.xda-developers.com/showpost.php?p=73556776&postcount=24 saying that restoring the oeminfo partition should get it to work (don't worry, I still have my bootloader unlock code), but I can't find any images for the Mate 10 (ALP-L29).
Can anyone provide me with one? If not, can you provide me with a method to fixing this issue without requiring me to pay the absurd amount that FunkyHuawei and DC Unlocker charge for restoring?
Thank you
Click to expand...
Click to collapse
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
ante0 said:
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
Click to expand...
Click to collapse
It supposedly went fine, but its still as is so. im downloading the Oreo update i was on, hopefully it works. of course the download speed isnt of much help
ante0 said:
Have you tried factory reset from stock recovery?
Flashing someone elses oeminfo will not help you. All it will do is lock bootloader and change your unlock code. (that thread is for Mate 9 on Nougat where oeminfo can be flashed without breaking anything. On Oreo and higher it uses oeminfo to calculate unlock code. But it also uses the imei that's embedded in oeminfo to calculate it. If you flash someone elses oeminfo your imei in oeminfo will not be the same and unlock code will change)
You most likely didn't do anything wrong. Updating stock firmware will replace your recovery with stock recovery. If it got that far in installation that is?
FH should work but it cost a lot. DC does not work since June so don't bother with it.
Else you can try service firmware from androidhost.ru.
Click to expand...
Click to collapse
i tried but got an "Software install failed" error.
majidamiri15300 said:
i tried but got an "Software install failed" error.
Click to expand...
Click to collapse
Which build and cust are you trying to install?
ante0 said:
Which build and cust are you trying to install?
Click to expand...
Click to collapse
128, C185
majidamiri15300 said:
128, C185
Click to expand...
Click to collapse
Wait, you were on B128?!
That's from December 2017/January 2018. And that's the reason why it won't downgrade. It has old bootloader, and you are now on new bootloader. (Since Pie has new bootloader and it flashed).
Try a more recent build, like B139 or B140
You can also try downloading from androidhost.ru using JDownloader, it seem to ignore the limit.
ante0 said:
Wait, you were on B128?!
That's from December 2017/January 2018. And that's the reason why it won't downgrade. It has old bootloader, and you are now on new bootloader. (Since Pie has new bootloader and it flashed).
Try a more recent build, like B139 or B140
You can also try downloading from androidhost.ru using JDownloader, it seem to ignore the limit.
Click to expand...
Click to collapse
does it matter though? because i cant even flash Pie. it's like its not accepting anything.
majidamiri15300 said:
does it matter though? because i cant even flash Pie. it's like its not accepting anything.
Click to expand...
Click to collapse
But it did update before bootlooping, no?
ante0 said:
But it did update before bootlooping, no?
Click to expand...
Click to collapse
i think so, yes. im downloading and trying anyway cuz what do i have to lose here.
edit: B135 didn't work, B139 still downloading...
majidamiri15300 said:
i think so, yes. im downloading and trying anyway cuz what do i have to lose here
Click to expand...
Click to collapse
It's just that B128 has old bootloader, and Pie (Including Oreo firmware from June and forward) has new bootloader. You can not downgrade from new bootloader to old bootloader.
So that's most likely why it fails to flash B128.
And you would only be able to update Pie using NoCheck recovery/TWRP, which is impossible to flash as you are FRP locked.
ante0 said:
It's just that B128 has old bootloader, and Pie (Including Oreo firmware from June and forward) has new bootloader. You can not downgrade from new bootloader to old bootloader.
So that's most likely why it fails to flash B128.
And you would only be able to update Pie using NoCheck recovery/TWRP, which is impossible to flash as you are FRP locked.
Click to expand...
Click to collapse
yeah i get that. ugh why does Huawei have to make everything so hard?
majidamiri15300 said:
i think so, yes. im downloading and trying anyway cuz what do i have to lose here.
edit: B135 didn't work, B139 still downloading...
Click to expand...
Click to collapse
majidamiri15300 said:
yeah i get that. ugh why does Huawei have to make everything so hard?
Click to expand...
Click to collapse
B135 should be able to install. It's new bootloader.
Check the instruction pdf that's included in the firmware, it will show you the directory path to use. And if you need to use microsd or USB OTG to SD adapter or something.
ante0 said:
B135 should be able to install. It's new bootloader.
Check the instruction pdf that's included in the firmware, it will show you the directory path to use. And if you need to use microsd or USB OTG to SD adapter or something.
Click to expand...
Click to collapse
i tried B139 and it didnt work. what the hell is going on???
edit: nevermind, nevermind, im just a giant idiot. ive been extracting the UPDATE.APP and using that instead of the full image. its flashing now.
majidamiri15300 said:
i tried B139 and it didnt work. what the hell is going on???
edit: nevermind, nevermind, im just a giant idiot. ive been extracting the UPDATE.APP and using that instead of the full image. its flashing now.
Click to expand...
Click to collapse
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Todesdoktor said:
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Click to expand...
Click to collapse
Which model and cust are you on? (ex. BLA-L29 C432)
Pretoriano80 said:
Which model and cust are you on? (ex. BLA-L29 C432)
Click to expand...
Click to collapse
ALP-L29 C636 But my build says ALP-LGRP2-OVS
Todesdoktor said:
Hi. Have you solved the problem? I'm stuck on Android pie beta too and I can't rollback to Oreo. I'm frp locked too.
Click to expand...
Click to collapse
yeah i did, it was relatively easy. just go to https://androidhost.ru, download the version for your phone, and when you unzip, you'll find a folder with instructions on how to flash. easy process, although keep in mind, this process will relock your bootloader (if you already unlocked it).
if you did unlock and it relocked, firstly, check your email if you still have the unlock code buried somewhere in your deleted emails, and if not, then check out this guide, should help you find your unlock code. it worked for me, and only cost $5 or so.
majidamiri15300 said:
yeah i did, it was relatively easy. just go to https://androidhost.ru, download the version for your phone, and when you unzip, you'll find a folder with instructions on how to flash. easy process, although keep in mind, this process will relock your bootloader (if you already unlocked it).
if you did unlock and it relocked, firstly, check your email if you still have the unlock code buried somewhere in your deleted emails, and if not, then check out this guide, should help you find your unlock code. it worked for me, and only cost $5 or so.
Click to expand...
Click to collapse
Thank you. So, for confirm, this works on frp locked? And yes, I'm unlocked and I have my code and my OEM file backup.
Hi guys, for developing unlock of Sprint v40, we need EFS backup from unlocked model V405QA (to compare some things between models).
You can do it by QFIL and QPST tools (to eliminate possible bugs)
Turn on Diag mode: In dialer *#546368#*405#, type 000000 in service code, then press SVC menu -> Port Check Test -> Enable.
Manual for QPST: https://forum.xda-developers.com/redmi-note-3/how-to/guide-qpst-tool-backup-imei-nvram-t3455297
Manual for QFIL: Start QFIL. Open Tools -> QCN Backup Restore. Click Browse and save it in cozy place. Press Backup QCN.
After finish you should see: «Done downloading the qcn file: C:\temp\00000000.qcn» and «Finish Backup QCN».
Manual for NV-items_reader_writer: Set port, click checkbox right after 000000, click Connect, Click Read button right after Connect button, click Read in main window.
Dont forget to turn off Diag mode after.
Many thanks! Your help for community will be greatly appreciated.
Hi.. i was wondering if we backup EFS from Sprint unlocked and restore it to Sprint locked will unlock the network for worldwide sim card?
Would it do any harm or changes to Sprint locked v40's IMEI?
I currently owned a Sprint unlocked LG v40.. bought it from Ebay, put in my Indonesian simcard and works perfect.. 3G/HSPA+/LTE great
zlebors said:
Hi.. i was wondering if we backup EFS from Sprint unlocked and restore it to Sprint locked will unlock the network for worldwide sim card?
Would it do any harm or changes to Sprint locked v40's IMEI?
I currently owned a Sprint unlocked LG v40.. bought it from Ebay, put in my Indonesian simcard and works perfect.. 3G/HSPA+/LTE great
Click to expand...
Click to collapse
Probably yes, with crossflashing unlocked firmware it can be big win for locked sprints.
IMEI will not change, we are searching only for items that locking network to sprint.
Im away till 11 march, but if I can contact you and help with backup, it will be great.
edited
if I backup EFS from Sprint unlocked and restore it to Sprint locked, will this method unlock the locked one?
I can get the efs from an unlocked sprint lg v40 can also get the locked one if you need it
zlebors said:
if I backup EFS from Sprint unlocked and restore it to Sprint locked, will this method unlock the locked one?
Click to expand...
Click to collapse
You cant restore it to sprint locked
But we get method, how to do it.
If restoring items dont make brick from my V40, we will release something big
e46_nexus said:
I can get the efs from an unlocked sprint lg v40 can also get the locked one if you need it
Click to expand...
Click to collapse
Yes, it will be great.
strk3r said:
Yes, it will be great.
Click to expand...
Click to collapse
*#546368#*405# this code does not work for the phone
e46_nexus said:
*#546368#*405# this code does not work for the phone
Click to expand...
Click to collapse
Check PM please
strk3r said:
Check PM please
Click to expand...
Click to collapse
So the job is to get both sets of efs locked and not locked then compare and take what makes the phone unlocked and copy that info into the locked efs then write back?
awireless said:
So the job is to get both sets of efs locked and not locked then compare and take what makes the phone unlocked and copy that info into the locked efs then write back?
Click to expand...
Click to collapse
This is only one from bunch of steps that can may lead us to unlock (or brick/no IMEI)
strk3r said:
This is only one from bunch of steps that can may lead us to unlock (or brick/no IMEI)
Click to expand...
Click to collapse
What about nv items? Just like samsungs j727p is unlocked nv items will be easier then doing the whole efs system.
I can test anything you want not afraid to brick
awireless said:
What about nv items? Just like samsungs j727p is unlocked nv items will be easier then doing the whole efs system.
I can test anything you want not afraid to brick
Click to expand...
Click to collapse
Already edited, no luck. If you know, what exact NVs may help I can test it.
strk3r said:
Already edited, no luck. If you know, what exact NVs may help I can test it.
Click to expand...
Click to collapse
enabling port check test does not turn on diag mode on my
2019-02-20 07:13:17: parsing V405UA10j
2019-02-20 07:13:17: parsing S
2019-02-20 07:13:17: parsing LMV405UA1AT-01-V10j-310-410-OCT-18-2018-ARB00+0
LM-V405UA
only LGE Mobile USB serial port
So are there any further instuctions on how to connect it to QPST?
strk3r said:
Probably yes, with crossflashing unlocked firmware it can be big win for locked sprints.
IMEI will not change, we are searching only for items that locking network to sprint.
Im away till 11 march, but if I can contact you and help with backup, it will be great.
Click to expand...
Click to collapse
strk3r said:
Hi guys, for developing unlock of Sprint v40, we need EFS backup from unlocked model V405QA (to compare some things between models).
You can do it by QFIL and QPST tools (to eliminate possible bugs)
Turn on Diag mode: In dialer *#546368#*405#, type 000000 in service code, then press SVC menu -> Port Check Test -> Enable.
Manual for QPST: https://forum.xda-developers.com/redmi-note-3/how-to/guide-qpst-tool-backup-imei-nvram-t3455297
Manual for QFIL: Start QFIL. Open Tools -> QCN Backup Restore. Click Browse and save it in cozy place. Press Backup QCN.
After finish you should see: «Done downloading the qcn file: C:\temp\00000000.qcn» and «Finish Backup QCN».
Dont forget to turn off Diag mode after.
Many thanks! Your help for community will be greatly appreciated.
Click to expand...
Click to collapse
Will KDZ for V405QA help?
You can get it from http://pkg02.lime.gdms.lge.com/dn/d...5AUX0E144JMD/V405QA711e_00_NAO_US_OP_0118.kdz
yvoznyuk said:
Will KDZ for V405QA help?
You can get it from http://pkg02.lime.gdms.lge.com/dn/d...5AUX0E144JMD/V405QA711e_00_NAO_US_OP_0118.kdz
Click to expand...
Click to collapse
No.
I have crossflashed v40 with QA firmware, but EFS is not changing while flashing firmware. Network lock is located somewhere in EFS.
strk3r said:
No.
I have crossflashed v40 with QA firmware, but EFS is not changing while flashing firmware. Network lock is located somewhere in EFS.
Click to expand...
Click to collapse
How did you crossflash?
Also i believe when cross flashing a v30 it doesn't touch the efs system either it just bypasses the lock its still there but because of the new firmware it tricks it into working thats what i was under impressions.
strk3r said:
No.
I have crossflashed v40 with QA firmware, but EFS is not changing while flashing firmware. Network lock is located somewhere in EFS.
Click to expand...
Click to collapse
If you have a functional LGUP version and DLL for crossflashing V40, please share, this would be a huge help for many folks here.
I have extracted the DLL from the latest LM-V405EBW KDZ but haven't been able to locate a version of LGUP which will successfully flash the device.
onslaught86 said:
If you have a functional LGUP version and DLL for crossflashing V40, please share, this would be a huge help for many folks here.
Click to expand...
Click to collapse
LGUP was not used to crossflash.
What help you want to receive?
Well I have been modding phones for a while, and I've been able to avoid anything this catastrophic so far, but yesterday while using Qfil, I clicked on erase entire flash.
So far I have recovered everything except my IMEI so my phone is not connected to my network. My question is can anyone help recover or restore my IMEI to my ATT Locked LG V40 with unlocked BL and Unlocked Rom?
Willym88 said:
Well I have been modding phones for a while, and I've been able to avoid anything this catastrophic so far, but yesterday while using Qfil, I clicked on erase entire flash.
So far I have recovered everything except my IMEI so my phone is not connected to my network. My question is can anyone help recover or restore my IMEI to my ATT Locked LG V40 with unlocked BL and Unlocked Rom?
Click to expand...
Click to collapse
probably my guess is a no, you can get those back by flashing a kdz or using qfil unbrick method see if they restore imei
Willym88 said:
Well I have been modding phones for a while, and I've been able to avoid anything this catastrophic so far, but yesterday while using Qfil, I clicked on erase entire flash.
So far I have recovered everything except my IMEI so my phone is not connected to my network. My question is can anyone help recover or restore my IMEI to my ATT Locked LG V40 with unlocked BL and Unlocked Rom?
Click to expand...
Click to collapse
Not long enough obviously, one of the first things suggested before flashing anything is to backup the IMEI partition, EFS for Samsung, to avoid having an expensive paper weight like the one in front of you..
Might need to find someone with a box now.
Talysdaddy said:
Not long enough obviously, one of the first things suggested before flashing anything is to backup the IMEI partition, EFS for Samsung, to avoid having an expensive paper weight like the one in front of you..
Might need to find someone with a box now.
Click to expand...
Click to collapse
Really I've never heard that before...I only backup what's tickable in TWRP .-. I think IMEI might be one of those options...
We need a donor nvram. All you need is files: nvram.bin, nvdata. img, persist. img, nvcfg. img, protect1. img, protect2. img, as well as pc. Goal: We will not take your imei. The most important thing for us is to understand what imei format miui accepts. Thanks.
Background:
NVRAM flew off by my mistake. Here I am with a friend trying to restore the imei. We're close to a solution. But we need donors to finally solve the problem. The loader is blocked
Please tell me I'm off topic. New guy.
Demeff said:
We need a donor nvram. All you need is files: nvram.bin, nvdata. img, persist. img, nvcfg. img, protect1. img, protect2. img, as well as pc. Goal: We will not take your imei. The most important thing for us is to understand what imei format miui accepts. Thanks.
Click to expand...
Click to collapse
Firstly, NOBODY should give anybody NO ONE of these files: nvram.bin, nvdata.img, persist.img, nvcfg.img, protect1.img, protect2.img.
If you have educational purpoises, here is not the place for collecting that.
Well, IMEI is present in NVRAM and NVDATA only.
NVRAM is the permant storage.
NVRAM is never formatted.
NVDATA is the variable storage.
NVDATA is formatted when data is formatted.
Nvdata is mounted at boot:
/dev/block/platform/bootdevice/by-name/nvdata /mnt/vendor/nvdata ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
This is the file containing the IMEI: /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI/LD0B_001
We have been trying to restore the imei for 6 days. We restored the imei only in engineering. Made a backup of nvram. Then we sewed miui. And there we restored the imei, but it gives this error:
So we thought that miui accepts these imeis in a different format.
IMEI for Slot1 will not be accepted on release versions.
Go back to engineering and erase the IMEI for slot1.
It needs to be empty.
Keeps only IMEI for slot2.
And then, it will works perfectly.
Only Xiaomi Centre can recover IMEI for slot1 if you lost it.
The fact is that we used the program sn write tool to restore imei 1 and 2, bt and wf. Then, to remove the first imei, I had to use the Modern Meta program. And with the help of NVRAM editor, we removed imei 1. We launch the phone, we see that there is a second imei. But the SIM cards don't work.
If your SIM card requires the imei it works in slot2 only.
Yes, we know that the SIM card requires an imei. We made imei 2. Then after that we flashed miui (not format all and download) and after flashing miui, imei 2 flew off
You said:
Demeff said:
The most important thing for us is to understand what imei format miui accepts.
Click to expand...
Click to collapse
But I think it is NOT specific to xiaomi/miui.
NVRAM and NVDATA structures present in MIUI, are same to other brands, models and newer android versions.
If I don't have an imei of 1. Can I link my account to mi unlock if I only have imei 2?
VD171 said:
You said:
But I think it is NOT specific to xiaomi/miui.
NVRAM and NVDATA structures present in MIUI, are same to other brands, models and newer android versions.
Click to expand...
Click to collapse
I need miui with imei 2 to unlock the bootloader, and then continue to live in peace
Demeff said:
Yes, we know that the SIM card requires an imei. We made imei 2. Then after that we flashed miui (not format all and download) and after flashing miui, imei 2 flew off
Click to expand...
Click to collapse
If you wipe data, flash using format all or flash using firmware upgrade, you will lose your imei again.
Read carefully:
1. Erase IMEI for slot1.
2. Write IMEI for slot2.
3. Backup NVDATA.
4. Flash anything you want or wipe your data if you want.
5. Restore NVDATA.
Done.
Keep the backup of NVDATA secure and if you need, just restore it back.
Demeff said:
If I don't have an imei of 1. Can I link my account to mi unlock if I only have imei 2?
Click to expand...
Click to collapse
Demeff said:
I need miui with imei 2 to unlock the bootloader, and then continue to live in peace
Click to expand...
Click to collapse
Yes, my friend.
Don't worry.
Only IMEI2 (slot2) is enough to bind your mi account and unlock your bootloader
VD171 said:
Yes, my friend.
Don't worry.
IMEI2 (slot2) is enough to bind your mi account and unlock your bootloader
Click to expand...
Click to collapse
Thank you for the information. Still, it's very good that it accepts another imei 2, otherwise it would be tin...
Demeff said:
Thank you for the information. Still, it's very good that it accepts another imei 2, otherwise it would be tin...
Click to expand...
Click to collapse
If you want to restore the state of unlocked bootloader, everything you need to do is unlock bootloader first and then backup the SECCFG partition.
If you lock bootloader again, just restore the backup of SECCFG and bootloader will be unlocked again.
VD171 said:
If you want to restore the state of unlocked bootloader, everything you need to do is unlock bootloader first and then backup the SECCFG partition.
If you lock bootloader again, just restore the backup of SECCFG and bootloader will be unlocked again.
Click to expand...
Click to collapse
I followed your advice. I managed to restore the imei 2! Thank you very much, my friend
Demeff said:
I followed your advice. I managed to restore the imei 2! Thank you very much, my friend
Click to expand...
Click to collapse
Good job, my friend.
You are welcome
VD171 said:
Good job, my friend.
You are welcome
Click to expand...
Click to collapse
I'm trying to link an account with mi unlock, and it says that I couldn't connect to the server. Try again later. What to do?
If you click a lot on "link account to device", I will get an error in the request parameter in error
I dont know why you cant unlock bootloader without IMEI i still can
CrisTV said:
I dont know why you cant unlock bootloader without IMEI i still can
Click to expand...
Click to collapse
No, you can't.