Related
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.
Ok, Ladies and Gentleman I need some deep thought processing here for some help with a Motorola Nexus 6. In brief here is what the problem is, a while back when flashing Pure Nexus rom, I experienced a loss of my IMEI. I can restore my IMEI but if and when I do, I lose any 4g and LTE connectivity. The phone functions in 3g with data and phone etc... just slow as molasses but if I restore my IMEI to the one that doesn't show up my IMEI correctly I get back LTE/4g and all works fine also. I've tried going all the way back to the original firmware which was saved to computer and restoring it. Same thing, I have IMEI but no LTE/4g. restore bad efs and get LTE/4g back. I've tried going through all the factory firmware's and flashing by ADB and or TWRP and nothing firmware wise will allow me to restore the IMEI and have LTE/4g signal. If I restore the bad efs and get OOOOOOOO for IMEI when using the *#06# on any firmware version, I regain LTE/4g functioning! I am using Pure Nexus 7.1 now and can still see the 00000000 as a IMEI, if I restore my efs and get IMEI back showing correctly, no LTE/4g signal! My phone can only function as it should as long as the IMEI doesn't show correctly! I have tried just flashing base bands and other segments of any rom and still the problem persist! I have even tried restoring an EFS from another nexus 6 and still no help. It's not the sims because I've tried AT&T sims and Verizon sims from other phones and it does the same thing! I've tried flashing with a sims in the phone and without. Any ideas??? It's like somehow a correlating segment of a file is not being recognized when the correct IMEI is present, like some thing some where in the efs, IMEI, and radio are not taking to each other so to speak, unless it shows the zero's! Brain waves come on and help me out here!!
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
jbaumert said:
Have you tried doing a fresh install of a complete factory nexus image? (i.e. entirely wiping the device)
Click to expand...
Click to collapse
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
TheWacoKid said:
Thanks, and Yes, about 30 different times, using Google developer site original factory firmware, using ADB and or TWRP all the way back to original image, which I have saved as I said in the original post! I don't have a problem restoring IMEI it's just if I do, the phone will not connect to LTE/4g no way no how. I have to have a "0" IMEI for the phone to function as it should actually function and the LTE/4g radio to work, something strange is a miss!
Click to expand...
Click to collapse
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
jbaumert said:
Alrighty, no need to yell.... The factory image is flashed with "fastboot" NOT adb or TWRP. Just wanted to clarify how you were returning the phone to stock.
Click to expand...
Click to collapse
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Dixon Butz said:
Try this:
1) Install "Change APN" app from Google store
2) Open ChangeAPN and click the "option" ( the 3 vertical dots) in the upper right-hand corners.
3) click "reset to default"
4) exit the app
5) perform carrier reset ##3282#
6)If needed: after the phone reboots, perform PRL/Device config update. That's it and you should have LTE data.
Click to expand...
Click to collapse
Thanks! Ok, Itried that, restored my IMEI, "reset APN to default" Tried Carrier reset ##3282# and it says "NO Cellular Network" even though I am showing my network and 3G. So, I rebooted and same thing, went to PRL and tried to update and it says "update error" but it will refresh!
TheWacoKid said:
Yes I said thanks because I was yelling! Jezz, get a grip THIS IS YELLING! ADB/Fastboot both tools are used to flash, extract etc.. with your computer, so obviously one cannot flash/restore etc... without using the proper tools via computer!
Click to expand...
Click to collapse
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
admiralspeedy said:
You clearly don't know the difference between a recovery, the bootloader and the operating system.
ADB is used when the phone is on and is not how you flash a factory image. Fastboot is used in the bootloader and is the proper method of restoring to factory.
Click to expand...
Click to collapse
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
TheWacoKid said:
No, I guess not, that's how I've been flashing, restoring and unbricking cells for years, I just don't understand anything!
Click to expand...
Click to collapse
You know some magic we don't? There is no way you've flashed a ROM with ADB...
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
dahawthorne said:
@admiralspeedy
I was very gratified when I noticed that I'd overnight become a Senior Member - until I realised that it had nothing to do with the wisdom I'd imparted in my posts, but only that I'd posted 100. So seniority doesn't imply knowledge, which I think you're beginning to demonstrate in this thread as well as in another where I've seen this same strange unnecessarily belligerent attitude.
TheWacoKid is asking for help, which I'd be happy to offer if I had any ideas. I feel absolutely no desire to tell him that he has no idea what he's doing. And nor should you.
Stop trolling and become a properly-active member of the community.
Click to expand...
Click to collapse
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
admiralspeedy said:
You know some magic we don't? There is no way you've flashed a ROM with ADB...
Click to expand...
Click to collapse
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
TheWacoKid said:
Look, I came on here to discuss a situation and or problem, which is what I thought this web site was known for, which I havent run into before, in that way not only do I get some help and or suggestions which might help me but help others at the same time who might have the same problem and or will have in the future and find possible solutions! If you don't have anything positive to add to the conversation/situation/problem at hand you are wasting my time, others time and most of all just making a fool out of yourself being childish and immature. Most on here come for solutions not looking to nitpick and try and belittle others like they know everything, which you don't, otherwise you would have given a solution! So you can continue to act like a troll or just leave the situation be and by the way, you ever hear of ADB Sideload??
Click to expand...
Click to collapse
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
admiralspeedy said:
Actually, I wouldn't have jumped on him like that if he hadn't come out swinging with snarky comments when people tried to help him.
Click to expand...
Click to collapse
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
rignfool said:
Time for you to go back and read some more...
You can flash a ROM with adb... Now unless you can help him... Shaddyup
Click to expand...
Click to collapse
No, you can use ADB sideload to flash a ROM which requires you to be in the recovery. Standard ADB cannot be used to flash a ROM.
admiralspeedy said:
I'm "belittling" you because your first two replies to someone who tried to help you were snarky and rude. In your own words, get a grip.
Click to expand...
Click to collapse
Amazing to any one with half a brain how you a Troll can think from typed response that someone is yelling, swinging, snarky and rude but your the one with an attitude that is all the above because like I said your a childish troll! I can't believe this site would even allow someone like you to be a member paid or otherwise! Your attitude is all your own and based on your own weak assumptions! Now go back to playing with your legos!
drmuruga said:
Use method 2 , you will get everything definitely
https://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
TheWacoKid said:
Thanks, I've used both of those methods, I have even tried just flashing individual parts all by themselves to see if just one part would give an error of some kind while flashing, no errors on any flash of any kind, the only difference being that if I read them correctly that on those methods it said to wipe data factory reset in recovery, before reboot, the Flashall bat file reboots automatically into image just flashed, I usually reboot as last command, if that makes any difference, I've even tried wiping then just flashing the new bootloader after a wipe, because it basically acts like a security checkpoint and partition manager, then rebooting and flashing the rest of one of the google firmware versions for the nexus 6.
Click to expand...
Click to collapse
So was there a solution? The thread just ended. I also have this problem but I'm no where as technical as thewacokid.
But I do know how to follow steps
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.
I ignored the warnings... I know, idiot.
But I went ahead and it completed.
But now the phone has a black screen and nothing else.
When plugged in, my computer recognises it as Qualcomm 9800 port 30.
Still nothing on screen though.
Anyway to get it back? Or get it to stock rom? Really don't want tmobile bloat all over it if possible.
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Double post.
What is it about the T-Mobile version that makes it so different to the others.
NGOwner said:
Your only hope would be to get someone who has a T-Mobile v40 to dump all partitions from their phone, and make those partitions available to you.
You would then use 9008 mode to upload partition after partition to your phone. And I'm not even sure that would work.
Enjoy your paperweight / doorstop / skipping stone / table leveler / shim.
[NG]Owner
Click to expand...
Click to collapse
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
shawnmos said:
From what I have seen on some other posts is that can cause the IMEI to return as 0. It may only be if you overwrite the modem partition though, so don't do that. You may only need the T-Mobile bootloader.
Click to expand...
Click to collapse
It's not the modem partition, it's the ftm (and maybe some others too)
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
Why would you want to flash a T-Mobile stock ROM?
Ainz_Ooal_Gown said:
Why would you want to flash a T-Mobile stock ROM?
Click to expand...
Click to collapse
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
aw2a said:
I'd really like to get Android 10 on my V40, but I don't seem to get OTA updates since AFAICT I have an ATT variant that has been crossflashed to US Cellular (I got it on eBay). Unfortunately the only (stock) Android 10 ROM I can find is for the T-Mobile variant, so I figure I'd give it a go; I know that the T-Mobile variant is a bit different from the others but I thought I'd try anyway since I was curious. In the end, aside from some panic (and a missing S/N and MAC address) no harm was done and I learned a lot, so that's nice. And, hopefully, I can use what I learned to help other people in a similar situation now (even though I'm far from an expert).
Click to expand...
Click to collapse
Ahh I see well we do have Android 10 in the flavors of LOS 17.1 and Havoc OS 3.5..
No firehose loader for the T-Mobile one so you can't fix in 9008 mode. It is a paperweight. You need to replace the motherboard.
Bump? Any way to revive it?
slebeau1988 said:
Bump? Any way to revive it?
Click to expand...
Click to collapse
You could try asking tmobile for help and see how much they'll charge you. You may get lucky if the phone is still in warranty
aw2a said:
I was in a similar situation two days ago; I tried crossflashing my V405UA to T-Mobile and got stuck with no signs of life other than 9008 mode. After a few hours of panicking I was able to figure out how to use QFIL and got things back up and running. I did accidentally wipe my serial number and MAC address in the process from the looks of it, but my IMEI is still intact.
So, I know the V405TA is different from the V405UA and other variants, but I think you can probably get it back through 9008 mode. Feel free to send a PM if you'd like to talk more about it, just keep in mind that I'm far from an expert on any of this. The steps I took were basically:
- Get QFIL and the programmer from here: https://forum.xda-developers.com/lg-v40/how-to/unlock-lg-v40-via-9008-root-t-mobile-t4042207
- Backup the necessary partitions (I didn't do this and now I don't have a S/N or MAC address although my IMEI is fine; I'm not sure which partitions you need to save but definitely look into that).
- Grab a copy of https://github.com/ANEP-ET/kdztools, it's a fork of kdztools that can generate rawprogram*.xml files.
- Get a KDZ from somewhere and use the tools to extract it and generate rawprogram*.xml files.
- You might need to edit rawprogram1.xml through rawprogram6.xml; IIRC I had to add "B." to the start of all of the filenames in rawprogram1.xml, "C." to the start of all of the files in rawprogram2.xml, and so on. I didn't have to change rawprogram0.xml.
- Add all of the rawprogram*.xml files in QFIL, I don't think you need a patch.xml (I clicked "Cancel" when asked for a patch file and everything still worked).
- Flash and you should hopefully be good to go.
Keep in mind that I don't really know what I'm doing so be careful and use common sense, this is just what worked for me. Feel free to PM if you want to discuss or have questions and good luck!
Click to expand...
Click to collapse
hey bro, how did you make a rawprogram.xml file, i've searched everywhere on the internet but no luck so far.