Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
can you access bootloader mode and reflash with flashtools? i assume you dont have a backup? as far as i know the first partitition is responsible for the connection through USB so as far as i know if im not wrong you could reflash these partitions. dont know much however over these mtk devices
---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------
freezes and shutdowns, even in lenovo stock recovery are a common problem i have found out. this has nothing to do with partitions in this case however dont know if this can be valid in your case. however in my example it is a fault within some lenovo stock roms. hope anyone can help you with more information
I do can flash with flashtool, at least thats how I flashed the stock rom, but I dont have a backup. Is it possible to use my IMEI with a different backup?
with my limited knowledge over the subject. preloader is the recovery since you can get a connection, what is safe to try without tinkering to much is flashing the latest vibe 3.0 45 dev rom over at needrom.com, since this rom also affects other partitions. once you have done this completely wipe every partition manually sometimes in TWRP i have seen some partitions dont function fully until you change partition format from ext4 to f2fs and back to ext4 and then wipe and repair in my case it has been for example.
as for the IMEI i havent been handson with these subjects so it is better for someone else to inform. This tip can be tried without risk as hopefully the dev rom will restore partitioning, at least it is worth a try.
---------- Post added at 02:56 PM ---------- Previous post was at 02:50 PM ----------
i cant answer your question on the IMEIs since lack of experience on the subject. however what i can say is that freezing and shutdown in stock k3 notes is a common problem and it is not hardware related. Does this problem also occur with a custom rom such as AOSP
Just to give you my total view on fixing the issue hopefully what i would try is:
1. flashing twrp
2.through twrp flashing the latest dev rom
3.reformatting every partition (meaning cache,dalvik cache,system,data,internal storage)
4.flashing a rom such as androim through twrp
5.trying the lost IMEI patch, input your info
6.to be sure use xposed framework uninstaller cause of performance gains
7.eventually using some tweaks such as l speed to get your device optimal
If the issue of freezing and random shutdown was of the same nature it should be solved 100%
http://forum.xda-developers.com/and...ed-thread-lenovo-k3-note-k50-t3158522/page117 latest dev rom
Damn, the official roms are unusable, they keep crashing after like 2-3mins.
Thanks for the link to the rom! I was looking for it for some time. Well, it installed without further complications, now I just need to find out how to restore my IMEIs... Hope at least one of all the methods will work this time.
I've found the answer to all my problems. I need a backup from another K3 Note, manually overwrite the IMEIs with mine and voila, it's supposed to work, at least works on other MTK phones.
If anybody here is willing to help me out please contact me, if you're afraid of sharing your IMEI numbers I can send you mine with an instruction on how to overwrite them, you could save me my phone and some money.
https://www.reddit.com/r/lenovok3no...ei_is_gone_after_installation_of_phoenix_rom/
http://forum.xda-developers.com/k3-note/general/organized-thread-lenovo-k3-note-k50-t3158522
refer this
Hi all,
My lenovo also having same problem..
anyone have a working solution..
pls help..
TQ
invalid imei number problem solved
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Nechoya said:
Hi guys, I got a big big problem with my K3 Note, I think I went too far with wiping partitions before installing a new rom, here are the folders I wiped:
data, cache, system, protect_f, protect_s, dalvik cache.
After reboot my phone worked just fine but it didn't see the simcard, I thought it's the OS issue and wiped and flashed several times more.
Now when I got into the issue I noticed *#06# returns "invalid imei", after a little bit research I found out it's a common issue with MTK phones and found multiple possibilities for solving the problem, none of which worked for me though, for no known reason ;( What I've tried so far is: chamelephon app, MTK Engineer mode commands, flashable ZIP with the IMEIs, writing it with SN write tool and another program named something like Mauri? if I remember correctly, all done on the stock rom flashed with flashtool, now I'm retrying all of above on a custom rom.
I read somewhere that missing basebands can be an issue for MTK engineer mode, but I couldn't find any more info on the topic
I don't know if it is connected but the stock rom worked much worse than I remember when I first got the phone, it freezes completely(doesn't react to power button, keeps the led light after unconnected from charger, completely no response, I have to take out the battery each time) about once every 3-5minutes.
Another thing is, does anybody have any idea what the protect_f and _s folders are? I think I shouldn't have wiped them...
Any help would be much appriciated, I don't need another bricked phone... ;(
Click to expand...
Click to collapse
Himanshu Gusai said:
1. flash new stock rom in ur device.
2. now you have two options
a. you can update your device. ( do all the updates of lollipop but don't upgrade it to marshmallow )
b. you can use the current rom that you have got after flashing.
3. root your device using kingroot app that you can easily find on net.
4. after rooting install chamelephon app on your device from play store.
5. remove the battery and note down the imei numbers written on back of the device.
6. plugin the battery and switch on your device.
7. open chamelephon app.
8. enter the imei numbers.
9. Hit apply new imei option.
10. wait for 1 min.
11. switch off your phone and then switch it on.
12. your sims are ready to work.....
Note ( do not update the device to marshmallow as kingroot app is not able to root lenovo vib marshmallow updated devices.)
Click to expand...
Click to collapse
hi himansu,
can you tell me which stock rom you use.
i try already your solution, but still not working for my phone.
Please help
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Try lord Arcadius' method.
somyaverma1891 said:
Dear Nechoya,
I got the exact same problem as I followed your footsteps of wiping too much.
Now my K3 note has NO IMEI and sim says NO SIM CARD INSERTED. I have tried all the usual methods mentioned on various threads but nothing is working for me. Can you please clarify what worked for you with some details. I am not a pro and anything from your side or any of the members reading it will be of immense help.
Thank you.
PS I Dont have any kind of backup
Click to expand...
Click to collapse
Never mind... I eventually found LordArcadius method here- https://forum.xda-developers.com/android/help/guide-how-to-fix-unknown-baseband-t3096927
And it is so simple working method that solved this IMEI problem.
Thanks.
Related
I wrote a brief thread regarding my phone before...
I'll just give the details:
I'm the second owner, phone died while updating.
Phone was bootloader unlocked, and with TWRP recovery.
As such, baseband and IMEI info are missing, I have the original IMEI but, no efs backup or anything.
Any ideas? I've tried to re-install factory stock via both Skipsoft Toolkit and another Toolkit [Yes, I realize this is no help, now]
I've heard restoring another EFS from another phone may work...? I don't know though, I have two Nexus 5's and I can pull an EFS just to try to get back my original IMEI or I've read EFS Pro could help but, again I'm quite lost and just need a hand here.
Thanks.
Ive been an active user on this forum and the rules is that you cant discuss changing the imei here, because its illegal in many countries
Skickat från min Nexus 6 via Tapatalk
No changing!
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
RedHazy said:
I'm not discussing changing anything, I just want to repair my missing imei!
It was lost and I can't get a signal on any carrier without one.
I have my original IMEI and just want to restore it.
Click to expand...
Click to collapse
here's a silly question.. how did you lose your imei? its not an issue on the n6 like earlier nexus phones, people just dont accidentally lose their imei, or their efs., unless they are restoring a nandroid from another phone, that has their efs backed up also..
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Sidenote: I did mess around with Titanium Backup but, I don't see that erasing my IMEI.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
If know the IEMI for your device there are threads on XDA that may restore it. If don't know the original IEMI you are dead in the water from the get go.
RedHazy said:
In all fairness, I don't know the fine tuned point at which the IMEI was lost but, it was shortly after the bootloader unlock and installation of TWRP. At two points, errors were made:
First: Phone died during an update
Second: I hard reset the phone after the update during which the phone loading and I was stuck in a bootloop, when really it just takes a while to load after a full wipe and install.
Yes, I realize that my actions were novice and especially not backing up my EFS or doing a NANDROID backup. In all fairness, I only backup my EFS or NAND on a handful of phone usually ones I frequently flash or my daily driver.
There's a few threads regarding the same issue but, no one is really assisting much in solving it...
I'm not a criminal here, I just want to get my phone back to it's original awesomeness!
Thanks
Click to expand...
Click to collapse
i dont think that you are a criminal, seriously. i was just curious, as on the n5 and n4 that happens often. it really does happen very rarely on a n6. i think the phone dying while updating might of done it. if your bootloader is still unlocked, flashing the factory image might help you. but you will have to do it right, via fastboot while youre in the bootloader. dont use any toolkits, seriously!
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
RedHazy said:
I do appreciate the help, I'm going to try flashing the factory image right image see if that helps. Fingers crossed, I'll update with my results. prdog1, you wouldn't happen to know of those threads at all, in case of failure with my factory image.
Thanks, I do appreciate the suggestions. I want to fix this for me and whomever has any issues in the future.
Click to expand...
Click to collapse
heres some instructions, dont lock tbe bootloader after, just follow the flashing the factory image instruction. and if tou run into trouble, let us know, so we can help you http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
RedHazy said:
Some VERY curious thoughts! I wasn't paying much attention until after losing my IMEI but, I've noticed a few things! For anyone that has lost an IMEI on your Nexus 6 in you scroll through your bootloader and go to "Barcodes" option, your IMEI is there! Anywho, back to my dilema.
I'm on 5.0.1 LRX22C
Now when re-flashing stock I noticed it would end up failed every time, with flash all or individually flashing items.
I noticed that my bootloader is 71.08 and 5.0.1 is 71.05 can anyone tell me which is 71.08 as there are three 5.1.0 stocks and I want to have the right one that corresponds to 71.08 bootloader.
For further help my full baseband on my phone is D4.0-9625-02.55.04 which incidentally belongs to 5.0.1, I'm thinking this mismatch may be one of my issues.
And thanks, simms22 for the guide, I'm downloading 5.1.0 right now. I'll keep consistent updates!
Click to expand...
Click to collapse
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Fingers crossed!
simms22 said:
flash 5.1.1, its the latest. and when you flash a factory image, itll replace the bootloader with whats included in the factory image. oh, btw, do not use flash-all, it wont work, its broken. flash the separate image files individually.
Click to expand...
Click to collapse
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
RedHazy said:
Flashed 5.1.1, fingers crossed. It's been about 27-ish minutes and it's still loading the first boot!
UPDATE: I'm at an hour now, waiting for first boot. Doesn't seem to be a bootloop, any ideas
UPDATE: An hour and a half, still booting.... may need to try something else.
Click to expand...
Click to collapse
wipe the phone, factory reset i mean
(sorry for getting back so late)
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
droid4lif3 said:
The same thing just happened to me, I had Cyanogenmod 12.1 on my phone, it was a nightly that I did on the 27th of last month. Like two days ago around noon, the phone was charging and it just lost all signal so I rebooted the phone and still the same thing, on the top it said that the phone had no sim card inserted. So I powered off the phone and removed the sim card and started the phone then I powered off and inserted the sim card and nothing, I updated to the newest nightly and nothing. Then I wiped the whole phone and flashed the newest nexus 6 factory image for t-mobile and still nothing. The thing that sucks is that I did backup my efs partition but I just updated the pc to windows 10 and I deleted the old.windows files so I am out of luck. I'm planning on taking it to T-Mobile and hopefully I can get a new one or get this one fixed. I hope you find a fix.
Click to expand...
Click to collapse
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
graydiggy said:
That doesn't mean your IMEI is broken or missing. You made no mention of checking it in the about phone section or in the dialer by input *#06#. It's likely that your SIM card is just broken. The IMEI doesn't just wipe itself out.
---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------
The same goes for the OP. I see few people claiming that root, TWRP or failing an install of a ROM wiped out their IMEI. Yet none take into account that maybe their SIM is broken, or the phone may be flagged, etc. Especially when one is not the first owner of the device.
I'm telling you guys that literally none of those things mess with the IMEI and all things stated lead me to believe that it is not an issue.
Click to expand...
Click to collapse
The IMEI is stored in the CID partition. The CID is a small datablock containing the processor UID, Channel ID (different CID), a bootloader unlock flag, and IMEI. The CID is unique to each device, and controls several aspects of the device. This datablock has a signature on it so that your device information cannot be modified. Should you corrupt this partition, you will lose your IMEI, and the ability to unlock your bootloader. This is the only likely scenario in which you lost your IMEI. If you boot into your bootloader, you may see an error similar to
Code:
CID Datablock Error! 0xDEAD
otherwise I'm going to assume that is still intact. The IMEI has not been stored in the EFS for many years now. Check your CID on the device and make sure it's not 0xDEAD.
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
Click to expand...
Click to collapse
Did you seriously just ask an iPhone question? ???
Seriously though, bring it back to T-Mobile.
Lol, no, I knew I shouldn't of put that she had a iPhone 6S, now I will never be helped. I am just saying that I used a different sim card to make sure that it wasn't the sim card that was messed up.
droid4lif3 said:
Hi, my wife has an iPhone 6S and I put her sim card into my sim slot and it still showed as no sim card after booting it up. Is there something else I can do? I am the first owner of this phone, I bought it from T-Mobile. I did try to go into the dialer and it force closes the app after I input *#06#.
---------- Post added at 05:35 AM ---------- Previous post was at 05:29 AM ----------
Hi how can I check if the CID has been corrupted? I recently locked my bootloader luckily I had a custom recovery and was able to flash a rom and get into the developer settings to enable oem unlock and I unlocked it again.
Click to expand...
Click to collapse
You can check by running the command
Code:
fastboot getvar all
in fastboot/bootloader mode.
You should see something like this:
Code:
(bootloader) cid: 0x00DE
(bootloader) channelid: 0x00
The CID should be 0x00DE if it is not corrupt.
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
BlackStorm94 said:
My phone was bricked and I restored it following this tut ( http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138 ). Now the phone is turned on normally, but I have this strange thing:
My phone number
Unknown
IMEI
0
IMEI SV
00
I have also this warning: Current version is not available for user. Can't find matched cust for NT-code mcc/mnc, subset.
How to fix?
Click to expand...
Click to collapse
Same thing happened to me after I unbricked my device using the exact same tutorial. However, even with IMEI 0 I can still make and receive calls and text messages. But I'm not sure if I should leave my device like this. If someone has any solution to provide I would be very grateful! I hope it doesn't involve flashing any ROM again cause I'm really afraid that I may brick my phone again ...
Hey guys, I had exactly the same problem. I tried different things including flashing various Roms and Bootstack, but nothing seemed to work. Since I’ve been searching for a solution quite a while, I now have the honor to help you out and everyone with an L90, who stumbles upon the same issue.
First of all, I made a backup of my EFS, so that I could restore the state my phone was in (IMEI=0, but working baseband). You can do that easily with TWRP (thx to shoxxy . By the way, this is something which we all should have done beforehand. It would have been much easier to restore our IMEIs.
But don’t worry, if you follow the instructions in this video (https://www.youtube.com/watch?v=nwzgs1Cmr9k) you should be able to get your IMEI working again. For those, who feel more comfortable following written instructions I copied the following procedure using this thread (http://forum.xda-developers.com/showthread.php?t=1960918) as a model and edited them a little to the way it just worked for me.
Do this on your own responsibility! And better double-check with the video our other threads.
Before you start:
Download this package (http://www.mediafire.com/download/figdbxb75j5kyry/package.rar), it belongs to the user who made the video on youtube (PremiumRepair).
Make sure your phone is rooted and USB-Debugging is enabled (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Procedure :
Install Drivers. Either you use LG Support Tool or download them directly. For me the LGUnitedMobileDriver+3.14.1_ML_WHQL.exe worked just fine. Don’t forget to uninstall old drivers or you could run into problems.
Install QPST v2.7.378. Microsoft Visual C++ 2005 Redistributable is a prerequisite, just confirm it.
Plug your device into your PC (USB port)
Run QPST Configuration from your Windows Start menu. Switch to the second tab ("Ports") and choose "Add new port" (bottom left button). You should see a COM port associated with "USB/QD Diagnostic". Select it, then press Ok. You can close the QPST Configuration window now.
Open Windows Explorer and browse to "C:\Program Files\Qualcomm\QPST\bin" (or wherever you installed QPST) and launch RF_NV_Manager.exe. In RF NV Manager, Go to "Settings / Comport". You should see your COM port in the dropdown box. Select it, then press OK.
Go to "File" and choose "Read from phone". RF NV Manager will read all NV items from the phone. Now if you see item #550, you will be able to alter it (see below). If you can’t find it, go to “File” and choose “Read supported RF NV Items”. If you still can't find it, there is a way to create it. Take a look at the thread I linked to.
Now comes the critical step of altering the IMEI. Select item #550 and you'll see 9 boxes on the right, a "Write NV" button and an "Hex" checkbox. Check the "Hex" checkbox.
Now, you'll have to enter the IMEI in the 9 boxes in a very specific way. The easiest way is to use the IMEI converter (for other method see linked thread). Put your IMEI in, convert it and put the digits in the boxes (two number per box).
Now you can then press "Write NV" to write the IMEI value to your phone.
Once done, unplug the device, and reboot it. Now you IMEI should be changed. If it’s not your number, take a look at the step seven again and check the video.
Please give a feedback, if it worked for you (incl. Details about your device, ROM, etc.) so that other users can profit from it. Thanks
Edit: @ BlackStorm94 - Don't worry about the warning. It will vanish if you install a different ROM.
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Lazgeor said:
I'm stuck at step 6. When I click Read From Phone, I get an error which says that my phone is not present. Also, on QPST Configuration, even tho I have set the Port to the one my phone appears, under Phone it says No Phone ... I guess my phone isn't recognized for some reason. Do I need to root it before I do this? I hope not because I don't really want to mess with it after the hard brick
Click to expand...
Click to collapse
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
mhikel said:
Yes, your phone needs to be rooted. This solution for rooting works great for me: http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951
Click to expand...
Click to collapse
So, I rooted the phone successfully, but the phone is still not recognized by QPST Configuration or RF NV Manager. My pc recognizes the phone and I can do everything properly, but these programs say that there is No Phone ... I don't know what to do ...
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
mhikel said:
mhh, that sounds like a problem with the drivers. Did you uninstall all the drivers (incl. Qualcomm drivers) from your PC? And have you installed the official LG drivers for our devices (for example from the link in this post: http://forum.xda-developers.com/showpost.php?p=62405939&postcount=138) Try another PC if it still doesn't work
Click to expand...
Click to collapse
I'm going to try on a new computer tomorrow afternoon and I'll let you know how it went. I uninstalled all drivers associated with my phone on my computer and after reinstalling them I still got no results. I guess I may have confused it So that's why I'll try on a new one. Thanks for your help
Hello, sorry for the late reply. I just wanted you to know that even though I tried with another computer, my phone was still not recognizable. It doesn't really matter tho, cause even with the IMEI 0 I still have service and it works normaly for about a month now. If you have any solution then I would like to try it, but if not then it's okay. Thanks for your time
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
[/COLOR]
mhikel said:
No worries! You do have USB-Debugging enabled, have you!? I mean you probably needed to do this for rooting. But if you haven't done it yet, that's probably the problem. Enable USB-Debugging like this (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (copied from http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951)
Click to expand...
Click to collapse
Yeah yeah, I had USB Debugging enabled every time I plugged my phone into both of my PCs. But I don't think that's the reason this tutorial isn't working on my phone. When I unbricked the device, I had to use the L90 D405 loader.img in order to reflash the bootloader and recovery. But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n. I hope you understood this cause I know it's a bit weird I see options to activate NFC but I never use it so I can't tell you if it works. However I can activate it properly. Anyway, about the IMEI, as I told you, it basically works without problems even with 0 because I think that my service provider doesn't block anybody except someone reports the device as stolen. If you have any further solutions then let me know but if not the don't worry, I'm okay!
Lazgeor said:
But my phone is the d405n model, and that's the ROM I installed to it. So the phone now thinks that it is the D405 but the ROM I have installed is the one for d405n.
Click to expand...
Click to collapse
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
mhikel said:
Ah, that makes sense. Flashing the right bootstack as described here (http://forum.xda-developers.com/lg-l90/development/bootstack-kk-l-l90-t3118632) could maybe help you (I haven't tried the one for D405n myself but it's supposed to stable). On the other hand: You probably installed a .kdz (ROM) with the correct Bootstack for your D405n included. ...So I don't think it'll bring back the IMEI or change anything. I'm running out of ideas, sry!
Click to expand...
Click to collapse
It's okay I don't want to bother you any further. I'll buy a new phone soon anyways and since I'll give this one to my small brother, I don't think he'll really worry if his IMEI is 0 If at some point this device gets blocked by a service provider then I'll start searching for ways to fix it again. That bootstack page you mentioned seems useful. I'll try that if I do have any problems. Thank you very much for your help
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
mhikel said:
That sounds reasonable! You are really welcome If you still need help just post here again. Although I have no other ideas at the moment someone else might. If you felt supported here I'd really appreciate the thanks! button. Yeah, you are right, the bootstacks supplied by Xemidra are of great value for our LG L90.
Click to expand...
Click to collapse
Update: I actually fixed it I know I told you that I would leave it as it is for now, but today I had nothing to do, so I decided to try my best and fix it. What I did was, as the post you told me said, I had to install the Kit Kat bootstack and the easiest way to do that is by flashing the Kit Kat rom. So I downgraded to android 4.4.2 using the stock rom I found on another post, and then I used your tutorial on the Kit Kat version. This time I was able to pass step 6 because my phone was getting recognized properly. I also didn't needed root access after all, since the new rom was just installed and it worked. After finishing the tutorial and restarting the phone, my IMEI was back! Then I upgrated my phone to the lollipop version, and when the upgrade finished, my IMEI was still there. So now I'm in lollipop with a working IMEI. I'm so thankful to you now, thank you very much for helping me and providing me these useful tutorials. I really appreciate it
Wow, that's just great!=) congratulations, you can be proud! Happy for you, that was quite an issue. You are welcome=) Well, someone from this forum helped me out, when I seeked for help and I am happy to give something back. Thank you for sharing your solution! That should be helpful for the next one stumbling over this problem. Enjoy your completely restored phone!=)
For the past half a year, I have been using Carbon rom on my Lenovo K3 Note, and it was fine, until it started slowing down. So, I decided to change it to another rom (Nexus), and the next thing I know, my SIM card is no longer detected.
Turns out, the IMEI was wiped.
How would I go about restoring this?
The things I have done:
MauiMETA = Never detects my phone. Places it into meta mode, but the light never turns yellow. Tried on 3 computers, and had no success on getting it to work. For two of the three, I couldn't find drivers for mt65xx and CDC.
MTK Droid Tool: The option to change the IMEI remained permanently greyed out, and was never given the option to change it.
Official rom: Didn't work. Currently using it, and still the same error (Null). Tried factory resetting it, no change.
Engineering mode: Always gave me an error when trying to enter command, never accepted it.
IMEI.EXE: Everything worked, except the IMEI's never changed in my device.
Have tried multiple roms, multiple wipes, SPFlash, CWM (Even ended up installing it again because I wiped my entire phone with SPFlash), and pretty much every trick I could find.
I need this think working in 12 hours.
EDIT: Problem was resolved with trying "official" roms until one allowed me to update within the rom. The Update that was installed via Lenovo's bootloader fixed it. The finished product was that of an untouched phone; I had to reinstall a bootloader, root, and a new rom.
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Darth said:
If flashing stock doesn't help, and you have no kind of backup of where the imei resides, you likely need a service center to hopefully help.
But know that any talk of manually inputting imei numbers is not allowed on XDA, as its illegal in most areas.
Good luck!
Click to expand...
Click to collapse
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
RocketPenguin1 said:
So it isn't as simple as entering the two codes under my battery into some location, and rebooting?
I'm currently in Europe, and have no idea how any of that works (Studying abroad).
Click to expand...
Click to collapse
That talk is not allowed, as I said. Inputting numbers falls under tampering and is illegal in most areas, as I said.
So try flashing stock, if you can. But without some sort of backup, you may be out of luck unfortunately.
Please keep number inputting talk off XDA, or I will need to close this thread. :good:
UPDATE: So, I flashed another "official" rom, which initially didn't work. However, it did give me the option to upgrade, which I did. With that upgrade, the IMEI is back, and my SIM card works.
Thing is, the ROM is almost entirely in Chinese.
How would I change my rom without wiping the IMEI?
Please post the link to download the ROM you used.
I have the same issue and even service centers failed to attempt this.
Thanx and regards
Raju
Chennai
You can easily rewrite imei number using snwriter tool, google it.
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Chouiyekh said:
hello guys,
my phone is xiaomi mi 8, and has a wifi issue ( mac address 02 00 00 00 00 )
when the phone was on china version the wifi and bluetooth work only when i sign in to mi account and if i sign out the wifi ...ect stop working
when i flash my phone with global version the bluetooth back to work only when i sign in to mi account and the wifi stop working even if i signed in or out to mi account
please help
Click to expand...
Click to collapse
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
tsongming said:
You need to use the correct firmware for your device.
Here is a website that has firmware for the Global and the Chinese version of the Mi8
Here is the chinese Firmware link
https://xiaomifirmwareupdater.com/#stable#dipper
If you continue having an issue after upgrading the firmware, you will need to use QPST to repair your IMEI
Click to expand...
Click to collapse
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Chouiyekh said:
that what do now, download a lot of chinese and global roms and try them and hoping to find one working
but you wrote if problem continue i have to use QPST to repair IMEI but i don't have problem on IMEI !!
Click to expand...
Click to collapse
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
tsongming said:
Yes I misread and was thought that you were also having cellular connection issue, in addition to WIFI, BT etc. You did not provide very much information
Did you try the most basic steps with resolving your issue.
Such as, fully resetting/or forgetting your Network and then resigning back into your WIFI?
Did you rule out the issue being with your router, or duplicate IP address, did you power cycle the router?
Did you fully wipe your device before switching to a completely different rom?
Your issue is probably an encryption issue, did you first fully wipe your device, including formatting user data? If not that very likely the issue and formatting resolves will absolutely resolve encryption based issues.
In fact, the more that I think about this issue and how the issue improves when able to sign into Mi-Cloud, I am certain that encryption is the problem. So back up your memes, and fully wipe and FORMAT ( not wipe) user storage ( type yes) reboot to recovery, then reinstall your rom and you should be back to using the phone without issues.
Click to expand...
Click to collapse
i tried every single thing you wrote above, nothing helpful
I also have the same problem someone could already solve it?
Chouiyekh said:
i tried every single thing you wrote above, nothing helpful
Click to expand...
Click to collapse
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
sear01 said:
thanks, I speak spanish and try to install the persist for a while the detail is that in a week I turned the wifi out of nowhere and now that the rom Pixel Experience was updated, the wifi again failed. Excuse me you could detail the steps I already made the flash of several rom both of China and global by Miflash but until now I do not expect anything to understand my desperation.
Click to expand...
Click to collapse
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
thank you very much it is global version Vipper use rom pixel.
thanks for your time
sear01 said:
thank you very much it is global version Vipper use rom pixel.
thanks for your time
Click to expand...
Click to collapse
Click
Okay then, here's the cliff notes.
I have good and not so good news, Keep in mind that repairing Mac address issues, Imei, QCn issues is the same for all Qualcomm processors, it doesn't matter if a post said this is for the Redmi 10, in fact I can't find the link at the moment but Qualcomm themselves published a guide with similar steps across the spectrum of chips. ( Just make sure that you only flash driver ( firmware images ) for your Global Mi8 and not the proprietary files from the links. Otherwise the instructions are the same, various versions of QPST will work, PC drivers, android drivers will also work. If will only benefit you to use the latest version of any of those files. If language is a issue, use chrome with the translator plugin .
I made copies of my personal persist files and spent the time to create the main files that you need and posted them Get the files here : https://mega.nz/#F!0NAXEK7S!Bj_hTKSz2_hMKDjOEocNrg
Install the version of TWRP that is on the link above, Create a folder called restore or whatever you want and place the downloaded files from my Megalink inside of that folder, make sure that they are not compressed. Next, place the folder inside the Twrp/Backup/ <<<< Place your folder there.
Boot to Twrp, click restore, and you should be able to restore the persist image.
If it doesn't work then use ADb to push to your phone. Google it, the steps are listed a billion times on countless sites, and I do not have enough server space to upload a complete recoveries, and plus I will not share my EFS or QCN
If that doesn't work read this post : https://forum.xda-developers.com/mi-8/how-to/how-to-fix-mi8-sensors-t3844551 ( Note the persist image, present. But also much older. However, it's still worth trying.
Worst case QPST, should absolutely resolve the issue
If what I listed above fails go here: https://forum.xda-developers.com/redmi-note-4/how-to/guide-how-to-change-mac-address-mido-t3773026
(Again, be sure to only use Mi8 files) DO NOT use a QCN from another device.
Here is another guide that has illustrations, again use your own files for your device, Otherwise the steps are identical, I have completed these steps myself on other devices : http://en.miui.com/thread-348525-1-1.html
One last final option that I would suggest trying before using QPST
Did you happen to make a recovery of your phone, after initially installing TWRP for the first time?
If no, search the web for a full stock recovery
tsongming said:
I am not sure if possibly English is your second language so I will give you the benefit of the doubt, a friendly tip, and another thing to try.
If a stranger on XDA is spending their personal time attempting to HELP YOU, with YOUR issue and providing you with a plethora of things to try, you may want to use your good manners and thank them for spending their time trying to help you, instead of briefly stating, I tried everything and it did not work. You would be amazed with how many doors simple appreciation can open for you. Next, It's called troubleshooting, If I had a definitive answer, with a definite solution I would have told you.
With that in mind here is another idea of something you can try,
It's pretty much all that is left to resolve, at least AFAIK.. So either this works or it's probably a hardware issue. Or an issue that requires using QPST as I stated originally, regardless of your IMEI. There are a million sites that describe step by step QPST steps if needed, I recommended.
Any of the steps below, you do at your own risk.
My last guess is that you probably wiped your persist partition by accident
You will need to restore your persist image and then you should be back in working order.
Important: you need to locate the correct persist image from the correct fastboot rom for your device. You can manually extract the file from the stock fastboot rom for your specific model and then push it to your device via ADB
As mentioned, you can find the rest of the additional steps with Google
@sear01
If you tried everything else, this post is probably the solution that will work for you as well.
Again at your own risk
Click to expand...
Click to collapse
I'm very sorry my friend ?, I'm just angry of that problem that's why i forgot to thank you, and I appreciate everything you did and you will. Yes English is not my first or second language, it's my third.
I've tried to flash persist.img through TWRP that what i got (image attached) and when i try to flash it through adb i got write failed
tsongming said:
Yes, I am getting ready to go to bed right now. Tomorrow, I will put together some instructions for extracting what you need from a fastboot rom.
I need to know if you have a Global of Chinese device.
If you have a global device, I can make a TWRP flashable file for you, which I will send to you via PM, I am happy to help people who appreciate my time.
Click to expand...
Click to collapse
Please don't be upset of me, and please accept my apologies
Chouiyekh said:
Please don't be upset of me, and please accept my apologies
Click to expand...
Click to collapse
No worries, it's all good Thanks.
You may not have seen the post I made earlier here: https://forum.xda-developers.com/showpost.php?p=79802367&postcount=11
If these things do not work come back here and report what happened and I will stay with you until we resolve the issue, there is always something else to try.
I have successfully solved similar issues on other devices, the issue here is possibly a permissions issue due to encryption, Read the post above and make sure that you use the version of Twrp that is linked on my Mega drive. That version has no problems with encryption, while many versions of Twrp have issues with decrypting. Plus, that version allows the option to select and restore each partition ( There is a lot!)
Check this post later, I am going to edit this post, and add a link to the Persist Image from the latest Global stable Rom. This will be an alternative and maybe better solution than using the persist images that I uploaded to my Mega drive.
UPDATE EDIT
Okay, I created a folder on the Mega Link called Method with a TWRP flashable persist image >>> Install the Official Xiaomi EU TWRP English version ( The one on my Mega Drive) Boot to TWRP, Mount the persist partition > Choose Restore and install to persist> Forget you WIFI and rejoin, it may and will probably work for you.
Three Options if it does not
One
First Option requires fully wiping your device, so back everything up
Assuming that your Device is a Global Device
Download this Fastboot Rom : http://en.miui.com/download-346.html Download the Full Stable fastboot version and not the Recovery version.
Unpack the Rom, place your phone into EDL Mode - This Rom comes with the Fastboot flashall script, it will fully restore your phone to the a Stable Rom and Overwrite every partition., this is as good as using Qfil to unbrick. In fact I recommend this over Qfil. This should definitely work, as long as your issue is software, and I am certain that it is.
Two
You are too afraid to wipe the phone and would rather try something else first, since you would need WIFI to restore your Google Services and Mi-Cloud.
No worries, here is a QPST alternative that has worked for many people, you basically create a new Mac address by following the steps in this thread, read the comments, it has worked for many people and it may save you time, and its not as difficult as it may seem.
This method has worked for people with WIFI Authentication issues.
https://forum.xda-developers.com/showpost.php?p=70408778&postcount=9
Use this tool to generate a Mac address to use for the above linked steps.
Three
IMEI Repair
http://en.miui.com/thread-260943-1-1.html
Note although, you may not have issues with data or with calling, this solution ay still be relative. But definitely try everything else first, and leave this as a last resort.
Let me know, if it works, and if it does work , change the name of the OP "Solved" at the end. this way others can benefit from the thread
Update,
I just found another, much easier method of restoring the persist partition
Use Google translator and follow instructions here Then go thank the_virus_ua
Note you do not need to download the files on the link the file that I shared on the earlier post will suffice
@Chouiyekh @sear01
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Chouiyekh said:
@tsongming thank you so much for keeping in touch, i've read your solutions, but i still didn't apply them yet, because i was sick these days and now it's time to sleep i will try tomorrow then tell you the result, ( when i was trying to flash persist.img through twrp, i find the persist partition, so the partition not missing? )
Click to expand...
Click to collapse
Okay, no worries. Just use that last step first.
That one is the easiest and absolutely worked for another person that I was helping. He had exactly the same issue.
Sent from my Xiaomi MI 8 using XDA Labs
tsongming said:
I never heard back to hear if your issue was resolved. if you are still having issues, this solution just fixed the issue for someone with a similar issue
https://forum.xda-developers.com/showpost.php?p=79824537&postcount=2
Click to expand...
Click to collapse
hello dear, i'm sorry for the delay, i had some urgent work out of my country that why i late to answer, now i'm in my country and i started to apply what you wrote, but when i tried to flash twrp the on your reply i got black screen can't boot to twrp ( i think i made something wrong because i extracted the zip file and flash only twrp img through cmd fastboot ) please correct me or give another twrp img .
i read some comments on google that there is a risk to lose imei or something else, if that right how can we making a back up just in case
i hope to get your answer soon, and thank you sooooo much
anyway, i tried at my own risk, that's what i got in twrp ( see image ) then reboot to system but still have the problem ! no wifi no bluetooth !
** i tried factory reset too, not helping.
Hi ALL
I have problem with my Mi 8.
No imei, baseband.
So I can't use my SIM and can't use wi-fi
I tried QPST , IMEI writer but failed
Someone help me please ((
Huynd1094 said:
Hi ALL
I have problem with my Mi 8.
No imei, baseband.
So I can't use my SIM and can't use wi-fi
I tried QPST , IMEI writer but failed
Someone help me please ((
Click to expand...
Click to collapse
Have you simply formatted ( Note that I said format and not wipe) the phone and reinstalled stock?
If yes, then QPST is the only option, and if you used it correctly it will usually work, unless you have a hardware issue. Do you have any recovery backups that you can restore?
These QPST instructions are all over the web, but the steps are always the same. I have repaired IMEI twice but on a different device.
If not you will need to find a donor QCN and retry QPST. ( QCN's can be found here on XDA and on Xiaomi forums) Make sure that you get all of the correct files for your Mi8 ( Your version of the Mi8)
and you can follow the instructions here: https://medium.com/@shekhawatkoki/f...-snapdragon-devices-xiaomi-mi-a1-2ed533548d32
Although these steps are for a A1 the steps are standard across Qualcomm devices. Just be sure to use the correct files.
I included the IMEI rebuilder tool and a QCN attached below. I keep these in case I ever needed it for myself and I have no idea where I got them. Use Google and research the issue heavily before starting. Be sure to try formatting and restoring the full stock Rom via ADB first before doing anything else.
Good Luck.
tsongming said:
Have you simply formatted ( Note that I said format and not wipe) the phone and reinstalled stock?
If yes, then QPST is the only option, and if you used it correctly it will usually work, unless you have a hardware issue. Do you have any recovery backups that you can restore?
These QPST instructions are all over the web, but the steps are always the same. I have repaired IMEI twice but on a different device.
If not you will need to find a donor QCN and retry QPST. ( QCN's can be found here on XDA and on Xiaomi forums) Make sure that you get all of the correct files for your Mi8 ( Your version of the Mi8)
and you can follow the instructions here: https://medium.com/@shekhawatkoki/f...-snapdragon-devices-xiaomi-mi-a1-2ed533548d32
Although these steps are for a A1 the steps are standard across Qualcomm devices. Just be sure to use the correct files.
I included the IMEI rebuilder tool and a QCN attached below. I keep these in case I ever needed it for myself and I have no idea where I got them. Use Google and research the issue heavily before starting. Be sure to try formatting and restoring the full stock Rom via ADB first before doing anything else.
Good Luck.
Click to expand...
Click to collapse
@tsongming Hi Sir! Hey im back with my mi8 problem and i decided to try editing the imei as a final attempt and i got stuck midway. May i request some advice from u?. Im stuck at QPST somehow not transmiting data into my phone. attached picture below. Thanks for your service sir!! will hit thanks
And as a side note. are website that provide downloadable stuff such as https://androidmtk.com/ safe from your years of use? cause they share the same format as https://qpsttool.com/ and just look fishy...
Theevanz said:
@tsongming Hi Sir! Hey im back with my mi8 problem and i decided to try editing the imei as a final attempt and i got stuck midway. May i request some advice from u?. Im stuck at QPST somehow not transmiting data into my phone. attached picture below. Thanks for your service sir!! will hit thanks
And as a side note. are website that provide downloadable stuff such as https://androidmtk.com/ safe from your years of use? cause they share the same format as https://qpsttool.com/ and just look fishy...
Click to expand...
Click to collapse
Sorry for the delay, I have downloaded and used files from this site a few times the past and had no issues whatsoever. However, that was a long time ago and it now looks like a completely different site. But they have an up to date security certificate. However, I would suggest that if you decide that you must use QPST, that you create a developer account with qualcomm and download the qpst tool from them directly. This way you are getting the most up to date tools, and you can get support from their forums.
FYI: you need to enter Diag mode before you can use the QPST tool for IMEI manipulation. Also, the tool will only affect Sim card 1... well that is what I have heard in regard to Xiaomi phones. Beyond those suggestions, as I have mentioned numerous times, on various threads, I do not support QPST with the Mi8. Because I have no experience using it with this device so I can not provide help based on experience.
The last time I used it years ago, and it was for the sake of experimentation. and once you change the IMEI it is difficult if not nearly impossible to restore the phone back to it's originally IMEI unless you have your original QCN backed up.
To go on, I made the post above almost a year ago, and frankly forgot about it. My perspective has changed, I would strongly suggest not using QPST or the QCN file to fix your phone. and to instead attempt to manually repair your phone using the steps suggested on my persist thread. if you have already tried everything on that that thread there is not much more I can offer, it's too risky and I don't want to be involved with permanently damaging your device. Online IMEI Repair services exist, and that may be your best option if the phone restoration route doesn't work.
Another option is using a UMT Box, and following an online tutorial. They cost about $50.