Related
Okay, so I called Cricket to get the MSID/MIN but i get an answering machine that says that they do not offer customer service at this time...is their any other way of obtaining this?
Technically, if you have a phone that's already on Cricket that you have the drivers for on your Windows computer, and you can get it to work in QPST, you could find all of the settings.
But it's not really worth all that trouble if you don't.
Just call *611 from a Cricket phone. Maybe they don't have Customer Service on Sundays?
Or go into an actual Cricket store, if they are open, because they will help you get the numbers too!
sorry to bother, I've been looking at different threads but can't find how to set those numbers on the eris
Realm said:
sorry to bother, I've been looking at different threads but can't find how to set those numbers on the eris
Click to expand...
Click to collapse
You need QPST and the Eris drivers. Go to this thread for instructions on how to use QPST. You could also do it with EPST on the handset itself (##778).
http://www.howardforums.com/showthr...an-HTC-Droid-Eris-to-Metro-PCS-(Tutorial-v2.0)
If you're on an Eris-based SenseUI ROM, you don't need QPST at all (in fact, I never heard of it the first time I put my ex-gf's phone on Cricket).
Just dial ##778
If you're on a different ROM, then yes. You may find it best to flash a SenseUI ROM anyway if that Froyo ROM doesn't have ##DIAG (whatever the numbers that line up with d-i-a-g are, I forget).
Put your phone in ##DIAG mode, open Device Manager in Windows, make sure the driver is installed, then in Device Manager, change the COM port of the diag device to like COM1 or COM3 or something low enough for QPST to see it.
Then in QPST, open up your FFA Surf (whatever it's called) phone, and edit all of your settings there.
WAY EASIER to just boot into recovery
make a nand backup
wipe data/cache
flash Ivan's Eris_Official 1.0 or Plane Jane (or something)
Boot up just enough to dial ##778
Put in your settings and PRL file
Reboot the phone
Make sure calls and texts work (after you tell Cricket your serial number)
Boot back into recovery, do a NAND RESTORE of your Froyo rom
stay in recovery, flash the cricket v10 flash
reboot
profit
I work for cricket mon-fri 2pm - 7pm, if you ever need help with your account/features feel free to pm me
I got it! Thanks guys
ok i made a dumb decision i had my epic with a clean esn flashed to metro pcs and i plan on getting back with sprint asap but my problem is my epic is still under metro i already flashed the phone back to stock 2.1 and i unrooted but when i dial *2 it takes me to metro customer service ive seen a few post on other sites on how to get it back to sprint but i trust xda for help
You need to fix the radio programming. SID, NAM, etc.
It really isn't "flash" at all. They haven't modified firmwares on modern phones. All it is is simple network parameter programming.
atmk4shh said:
ok i made a dumb decision i had my epic with a clean esn flashed to metro pcs and i plan on getting back with sprint asap but my problem is my epic is still under metro i already flashed the phone back to stock 2.1 and i unrooted but when i dial *2 it takes me to metro customer service ive seen a few post on other sites on how to get it back to sprint but i trust xda for help
Click to expand...
Click to collapse
just sent you a PM. It's not the easest thing in the world to do. I just hope you have your epic's original info to put back on to your phone. good luck.
when the store did it they rooted it and put another rom on it but i unrooted it and put the stock rom back on it but how do i fix the radio programming. SID, NAM, etc.
delawaresace said:
just sent you a PM. It's not the easest thing in the world to do. I just hope you have your epic's original info to put back on to your phone. good luck.
Click to expand...
Click to collapse
Hey delawaresace,
I'm in the same situation as atmk4shh, where i want to flash my phone back to Sprint from Metro. Could you copy and paste that PM to me also by any chance? Your help would be much appreciated!
What I have done so far:
- I flashed it back to DK18 stock for sprint
- Selected "wipe data/factory reset" and "wipe cache partition" 3 times.
- Added my phone ESN to sprint plan and ported number over successfully.
- Did the ##786# reset
I believe the problem is probably has to do with my QPST settings and when i open Service Programming i still see the metroPCS info. And me being the idiot i am, didnt save the original settings, so I was wondering if anyone could post that info? Or am I barking up the wrong tree here? Also, i was wondering if i need to change anything else to get my phone working on sprint again? Do I need to do PRL stuff on CDMA? Thanks again!
breakinyoankelz said:
Hey delawaresace,
I'm in the same situation as atmk4shh, where i want to flash my phone back to Sprint from Metro. Could you copy and paste that PM to me also by any chance? Your help would be much appreciated!
What I have done so far:
- I flashed it back to DK18 stock for sprint
- Selected "wipe data/factory reset" and "wipe cache partition" 3 times.
- Added my phone ESN to sprint plan and ported number over successfully.
- Did the ##786# reset
I believe the problem is probably has to do with my QPST settings and when i open Service Programming i still see the metroPCS info. And me being the idiot i am, didnt save the original settings, so I was wondering if anyone could post that info? Or am I barking up the wrong tree here? Also, i was wondering if i need to change anything else to get my phone working on sprint again? Do I need to do PRL stuff on CDMA? Thanks again!
Click to expand...
Click to collapse
Most likely you need to load a Sprint PRL to connect to Sprint towers, latest one is 60674. If i remember correctly, QPST and cdma ws can upload a prl file.
Go here, http://forum.xda-developers.com/showthread.php?t=898628
LordLugard said:
Most likely you need to load a Sprint PRL to connect to Sprint towers, latest one is 60674. If i remember correctly, QPST and cdma ws can upload a prl file.
Go here, http://forum.xda-developers.com/showthread.php?t=898628
Click to expand...
Click to collapse
Thanks lord for the suggestion, but sadly I have already tried that and no luck. I think it might have do to with the NAI, Tethered NAI, UM, AM settings
Update: got the voice and sms to work, but data arrows arent showing still
Have you tried samsung's dialer code for factory resetting? I belie it restores the programming to factory as well. The just update prl/profile
Sent from my SPH-D700 using XDA App
trobertson said:
Have you tried samsung's dialer code for factory resetting? I belie it restores the programming to factory as well. The just update prl/profile
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Yeah, i believe thats what the ##786# reset is: the factory reset. That hasnt allowed the data arrows to show, let alone push through. I also have updated the prl to, but it wont let me update the profile without network connection. Thanks for the suggestion though!
UPDATE: Brought it in to the sprint store. They couldn't fix it. Gave me a replacement. I tried to save it...i really did lol. Thanks for all the help though!
Hi Folks, please bear with me. Before some screams google/search for it, I have already, and I have a very small window of time to continue to search thru hundreds of threads.
Mods: Because of the circumstances, I have to double post here and in the evo shift section. Main reason for posting here is because there has been more success here and more attention/traffic is paid to the evo, whereas since the shift is the evo child, I figured its harmless to double post. Sorry if Im bending/breaking the rules.
I have an evo shift that at the time of purchased was already flashed over to METRO. My shift has a clean esn and I would like to flash it back over to sprint. Yes, there are guides here, but the only guide I found was how to flash the EVO 4G over to METRO but I dont recall reading how to flash back to sprint. http://forum.xda-developers.com/show...50#post8395950
Then I went here: http://forum.xda-developers.com/show...3#post14282143 to acquire the qpst tool. The link there is an empty torrent, so no luck.
But the reason I am posting is because I know there are others who want to flash their evo shifts over to metro, and I already have an evo shift on metro. So before I start tinkering around and potentially BRICK my shift, I'd like someone to walk me thru the process of saving a dump of everything on my phone so others can learn how it was flashed or check certain settings in it, or just have whatever rom that it is on. So basically, so the next set of ppl can benefit from it.
All I want to do is go back to stock/sprint so I swap my epic off and shift on. Im curious about the insane overclocks 1.7+ghz, so i can determine which phone I want to sell. Thats it. Hope someone can help me out. Thanks in advance.
Ok, since this is the SHIFT forum, does anybody think this will work?
!) http://forum.xda-developers.com/showthread.php?t=937652
2) http://forum.xda-developers.com/showthread.php?p=14283345#post14283345
Im still scouring the net for the damn qpst tool.
Qpst at x-drivers.com
Look under phone tools and qpst is for qualcom devices
Sent from my PG06100 using XDA Premium App
All you should need to do is run the stock RUU to take it back to the original setup. After running the RUU you should be back to Sprint original. No ROOT. Just like it came out of the box. Check either of the links below to get back to the STOCK RUU. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=909554
http://forum.xda-developers.com/showthread.php?t=971550
Thanks guys, but I guess the other prob is how do I make a full back up so others can flash if they switch from sprint to metro?
Or should I not concern myself with that because its a matter of qpst programming (among other tools)?
lilgrass71- thanks for the link, but i believe i need version 2.7.366,
at x-drivers, they have 2.7.323, which I assume will be slightly outdated to use for the shift. any other ideas as to how to acquire 2.7.366,
i googled it, downloaded a few, and just waaaayyyyy tooo many viruses. I understand majority of AV's will throw a false positive, but I feel much much safer getting whatever app from a trusted source and not just some random file hosting spot where as anyone could have tampered with it. Hell, dont even mind the tampering, as long as someone who is "well known" does the tampering for OUR BENEFIT.
That version will work... I used it on my shift and it works fine. What are you trying to do with it? Just a backup of provision data? Or mess with the memory data?
Sent from my PG06100 using XDA Premium App
If someone can benefit from my backup then I would like to make a complete backup of everything on the phone. If my backup cannot be used, then I will skip that process and flash back to sprint. But yea, thats the only reason why I would do a backup, just to help out the next set of ppl.
Also, since you have used this tool before to revert back to sprint, did you have to flash the ruu that pr posted? or u just used qpst only and flashed whatever rom? im asking because I really dont want to tamper with qpst as that may be a lil more dangerous than just flashing a stock rom.
I believe there's a bit more involved to flash over to Metro PCS. I would suggest just running the RUU and calling it good.
lol, pr, Im not trying to flash OVER TO METRO, im trying to flash BACK to sprint.
Ive tried using the .zip that goes on the sd card, that does not work.
Ive tried using the ruu stock flash utility, i keep getting "cant connect" error. Im running win 7 x64, i've installed the htc diag driver correctly, verified it works, it was on port 8, i changed it to port 9 to see if i would have better results, that didnt work, changed usb ports, that dont work, shut off phone and pc, that didnt work. Im at my wits end. right now, im still browsing thru a bunch of other threads to see what might work.
I have not tried lilgrass qpst way yet, thats my last resort, but I will if i get TOOOO frustrated.
I know that. By RUU I meant back to Sprint. That's what the links I posted are for. Connect to computer with USB cable ( HTC cable, not generic ) . Then launch the RUU from your computer. Should prompt you through the process. The reason I said about the HTC cable is because I've had issues with the generic cables in the past.
If u want to revert back to sprint, made sure the your meid matched the one on the serial number.
Hook up your phone to its com port, open qpst and connect to the phone. Leave that open. Then goto qpst programming and clear out the username and passwords for profile 0 and profile 1. Make sure you write it to the phone.
Then your gonna want to just run thr ruu to get yourself back to stock and run a epst profile update and it will update all your phone programing over the air.
I didn't go back to stock. I use the programs for higher process hexidecimal memory editing but that should do the trick. All the cdma phones work just about the same way when they connect to the network. Don't buy into the you need to buy into the primier data/the phone won't work without this plan bs they give you at the store.
Sent from my PG06100 using XDA Premium App
prboy- last night i did use the ruu, i flashed it, it worked, but still had the sprint banner there, but now i have even bigger problems, i will explain a lil later tho.
lilgrass-i did not use the qpst method yet, i used prboy links, but after trying to root my phone, i bricked it, which i now have to start a new thread. boy oh boy, problems after problems.
oh, the meid does match on the box and phone itself.
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
ayoshidage said:
Hey guys
I was wondering if someone here is still on the V6 version of the security update, if you are you can make the TOT file out of the V20 Sprint model. Whoever has the Z3X box for LG, follow these steps:
1. Start the LG Tools
2. Select H918
3. Select the Port 1 in Workspace, in connection put it to: AndroidNet USB Serial Port
4. Search phone button will find the LS997 model.
5. Select the Firmware Maker on the bottom of the right box
This will make the firmware of the version 6, the one that has the hidden menu for the unlock, since we cannot downgrade, maybe we can try it this way, it creates a TOT file that is flashable through the Z3X software
Does anyone have the box with this version, before it was updated. Because I lost that in the hidden menu the unlock function and now I cant even get signal, having issues wanna downgrade.
If someone has this LS997V6, create the firmware so we can flash it and maybe we can go back to that security update before it was patched, been looking around for it. But I dont have that version or else would have created the file to share.
Click to expand...
Click to collapse
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
hyelton said:
But didn’t antirollback change? If so firmware or not you cannot downgrade
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
ayoshidage said:
Yes, but I am currently working on it, but I need that firmware version to see what I can do, because I dont have that, I need someone to make a copy of that from their phone using the methods I have provided for me to do the work on it.
Click to expand...
Click to collapse
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
hyelton said:
If antirollback did change, there’s no physical possible way to downgrade. It’s not possible, there’s no way around antirollback.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
ayoshidage said:
There is always a way for everything, keep in mind Samsung did the same thing to prevent downgrading the firmware, I have found a way to downgrade that to the first version installed on the device even if you are on the latest version, but took me a very long time to find the exploit for it. So trust me, when I tell you there is always a way. Would I share that, no I wont, because its my business and my hard work alone. But I am willing to share my work for this project.
What is there to lose, you have a person here willing to work for free, and work on this project to share with the community.
Click to expand...
Click to collapse
Yeah nothing to loose .
Here’s a good post on it. https://forum.xda-developers.com/showpost.php?p=73206763&postcount=3
Here is a post from another thread:
“In short: the ARB is implemented in the bootloader and to be more clear in the certificates within. There is 100% no chance to change this other then when you break the signature algo or find a bug in the implementation”
Good luck, If you get anything be sure to post updates!
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
runningnak3d said:
Without being able to inject code between the CPU and the NAND, it can't be done. I would LOVE to be proven wrong, but here is a quick overview:
The PBL is located in QFPROM on the CPU. ARB is located in QFPROM on the CPU. The RSA key is located in QFPROM on the CPU.
When you power on the phone, the PBL loads XBL and checks the ARB version. If it is less than what is burned into the CPU, it goes into 9008 mode. It also use the RSA key to verify the signature of XBL. If it is modified -- 9008 mode.
When a phone successfully loads XBL that has a greater ARB version than what is burned into the CPU, it immediately burns the greater ARB version into the CPU.
So there are a couple of attack vectors:
1 - Have some cool hardware that can read the RSA key from the CPU and try and brute force the RSA cert with the key and the sig.
2 - Have some cool hardware that can do a MITM attack on the CPU and NAND replying with a valid return so that the CPU will boot no matter what is on the NAND.
Good luck, I will be following this closely....
-- Brian
Click to expand...
Click to collapse
Hi Brian
Thank you for all the information and all the input, I am gonna try to see what I can do from my end, my issue is this, before the update was patched from the hidden menu. This is the problem that has occured. Before the update, when I got this phone, was running on V6, I believe that was the last version that supported the HiddenMenu.apk, that you were able to change production to lab mode. Now since the mistake I did in updating the security software that has been patched and because of it. I have very weak signal and now also the 4G is gone. Before the update, I had full signal bars and 4G service. Now the bars come and go with the data connected. The phone was unlocked this method (temp method) and then was unlocked using Octopus after the update.
These are the issues:
1. The signal bars goes up and down to 0 and goes up again, I am in a very strong signal area.
2. The 4G was working but not the greatest speeds, was doing like 4-8MB a sec down and 0.1Kbs upload. Which is terrible.
I tried Resetting the Security via box and now the 4G is gone and data. Calls are working but same signal issues.
The issue is I know sprint uses the CDMA technologly, and where I am its GSM network, but my service uses WCDMA because it runs on the AWS network 1700/2100. The problem is this. I can get the HiddenMenu to work again, but that special section in the old version does not exist anymore because it has been patched in the new security update.
I am also able to get in to the band selection, AWS and all other bands are there, but the issue is if you select AWS it says FAILED to connect on any band except on AUTO, so this is why I wanted to have the old version extracted on the version 6, so that I could work on it, since Sprint does not have firmware files you can flash.
So this is the problem. Very stupid the way they did this firmware method OVER THE AIR method. The funny thing is that the it supports all the bands that the GSM supports here and the UMTS.
I just want to get this phone back to full bars with the data restored and have the full speed I had when I did the temp fix, but real solution. I know maybe I can flash a custom rom, but I dont know how reliable that is and if it will resolve the issue.
Whats your input on all of this?
Those issues your having are typical issues of using a sprint device on another carrier. Only fix is flashing a different model firmware which won’t ever be possible for the Sprint model. Never rely on a sprint device unless your using it on sprint.
Sent from my iPhone using Tapatalk
Yes I'm aware of these things of Sprint after finding out. But the weird thing is I never had an issue after that fix for the hidden menu patch that unlocks it when out into lab mode and specifying the APN. Never had a dropped signal once or data. This issued occured after the update. This is my first time owning an Sprint phone so I didn't know there were no firmware which is why I wanted to work on this project.
They say the workround is flashing a DirtySanta ROM. But then again if you fladh that rom would u have those old options back in hidden menu and would it fix the issue. That's the real question.
I am also aware that since you unlock the bootloader and lock it again you can brick the device. Luckly I have made a tot of my whole system firmware image latest version.
What's the best approach to getting this back to working state. My network runs on WCDMA that's why AWS is needed.
Just want to know how to get this working...
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
elijah420 said:
> would i share that, no i wont, its my hard work alone ...
>i need someone to ...
I see a hiccup in the reasoning here.
Best of luck. Development on this device came to a screeching halt when ARB hit.r
Click to expand...
Click to collapse
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
ayoshidage said:
That's phrase is for the Samsung exploit. Not LG two different phones and companies.
If nobody cares to share that firmware version to extract no worries I won't work on it. Worst comes to worst I'll sell the phone that's all.
Good luck finding a way to do it yourself then. Dont questions others people work when you don't know what skills they have in the mobile field.
Thanks for everyone else for their input.
Click to expand...
Click to collapse
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
elijah420 said:
Well thank you, but you fail to understand something very basic here. While there may have been a question mark in there somewhere, in no way was your request a request. It was rather demanding. You demanded someone do something for you, with no reciprocity from you. I think attitudes like that tend to rankle rather than disarm.
As far as the last bit of your snarky comment - bear this in mind - I'm not the one looking for a 'way to do it myself'.
Again, best of luck.
Click to expand...
Click to collapse
Thanks for you reply, but I dont think you understood the meaning of what request means? Request means " an act of asking politely or formally for something" I think you should understand what the meaning of request means before commenting no sense. Also I didn't demand someone, I was asking if someone had a dump file or if someone could create a dump file for me to work on the project. I am here to help people out to find solutions, you are here for the purpose of starting rant on the forums. By no means, this was demand or any sort of order in bossing people around. But its all good, I dont have the phone anymore, so no need to work on it anymore, have a great day.
Thanks.
Hi sorry for bad english
I had to edit my thread and put more informations, so, after i revert to stock rom (i used the self reverter rom in zte site), my imeis got doubled and with same 000039485642710 in both sim 1 and sim 2. For what i have research, its a commom bug that happends. If you search in google this imei, you will see that a lot of ZTE users got this problem. I tryied almost everything, but with no sucess. I have all original itens with original imei on the back of the phone box. The imeis was all right before. Now i have no data on sim slots since the imei have changed. Can anyone please help me to repair/revert to my original imei ? I cant buy other phone. Thanks
@brunojborges: No, custom ROMs dont change the IMEI. Sometimes my IMEI appeared as 0 when swapping SIM cards, but 4G LTE still worked.
I no longer own an an A7, but i did have to send it in for repair, i did notice that the IMEI had changed on the returned device. So i called ZTE and they confirmed that the device had been swapped with a different refurbished A7.
However, it is rare but possible that flashing firmware can corrupt the EFS, which is where the IMEI is stored.
Where did you buy your device? And how long ago? If you got it off Craigslist or from some shady site online, it is possible that previous owner reported the device and so the carriers blocked the IMEI.
And, if your IMEI really is blocked, you will need to contact your carrier. Have the IMEI ready, have them check it to see if it is blocked. If so, then by who and when. Try to get details. Depending on the details, you can explain your situation and they might unblock it. Or, they can advise on who to contact. Tough luck with this though, once an IMEI is blocked it will be very hard to get it off the blacklist, esp if it was reported stolen/lost. In that case, you have nothing more than a wifi phone.
AnonVendetta said:
@brunojborges: No, custom ROMs dont change the IMEI. Sometimes my IMEI appeared as 0 when swapping SIM cards, but 4G LTE still worked.
I no longer own an an A7, but i did have to send it in for repair, i did notice that the IMEI had changed on the returned device. So i called ZTE and they confirmed that the device had been swapped with a different refurbished A7.
However, it is rare but possible that flashing firmware can corrupt the EFS, which is where the IMEI is stored.
Where did you buy your device? And how long ago? If you got it off Craigslist or from some shady site online, it is possible that previous owner reported the device and so the carriers blocked the IMEI.
And, if your IMEI really is blocked, you will need to contact your carrier. Have the IMEI ready, have them check it to see if it is blocked. If so, then by who and when. Try to get details. Depending on the details, you can explain your situation and they might unblock it. Or, they can advise on who to contact. Tough luck with this though, once an IMEI is blocked it will be very hard to get it off the blacklist, esp if it was reported stolen/lost. In that case, you have nothing more than a wifi phone.
Click to expand...
Click to collapse
thanks to your answer friend!
So, i purchase this phone used, on sale site. With box, manuals, and all itens, and a import doc. I never had any problem with him (using 1 month or more). Everything was working ok. Just after i change the rom, in the same moment, my sims stop to work. So i decide to check the imei, and i realize that is different from the imeis on the back of the box (not shure but i guess, before the imeis was the same). The seller is from here (brazil), was the first owner, and the imei block is from argentina (the phone has never been there). So i just want to know if there is a software or something that i can use to insert the original imeis on the back of the box to the phone.
One more thing, the both imeis are exactly the same. I guess this makes no sense :laugh: :laugh:
@brunojborges: Well the issue is that you bought it used, which implies there was a previous ownee. Probably the online seller you bought from knew it was lost/stolen, but sold it anyway. There is a good chance that the phone IS from Argentina, probably where the previous owner lives. Everything may have seemed to be working OK, and was, up until it was reported, then it becomes blacklisted.
As already stated, changing custom ROMs doesnt mess with the IMEI. However, flashing firmware might. It is also entirely possible that your device is legit, legally speaking, and that whatever you did messed up the IMEI.
It is possible to restore the original IMEI/EFS with QFIL/QPST. I did so once on a friend's ZTE Blade and it worked. You can find instructions online. However, this program can do more harm than good, it is relatively complex to use, and so you must be careful and follow instructions to the letter.
I would still contact your carrier first.
AnonVendetta said:
@brunojborges: Well the issue is that you bought it used, which implies there was a previous ownee. Probably the online seller you bought from knew it was lost/stolen, but sold it anyway. There is a good chance that the phone IS from Argentina, probably where the previous owner lives. Everything may have seemed to be working OK, and was, up until it was reported, then it becomes blacklisted.
As already stated, changing custom ROMs doesnt mess with the IMEI. However, flashing firmware might. It is also entirely possible that your device is legit, legally speaking, and that whatever you did messed up the IMEI.
It is possible to restore the original IMEI/EFS with QFIL/QPST. I did so once on a friend's ZTE Blade and it worked. You can find instructions online. However, this program can do more harm than good, it is relatively complex to use, and so you must be careful and follow instructions to the letter.
I would still contact your carrier first.
Click to expand...
Click to collapse
thank a lot. i will try to learn what is this qfil and fix this issue, as i said, the both sim 1 and sim 2 are with the same number so something must be wrong with the device. and i remember to have flashed some firmware when installing any of the 10 or more roms. thanks.
Do you have the correct modem installed
Predatorhaze said:
Do you have the correct modem installed
Click to expand...
Click to collapse
yes i have. saddly, modem files dont chance imei numbers i guess. the key to my problem is the fact that the 2 numers are the same (and start with 0000xxxxxxxxxxx). Sould be different, but isnt. why? im very very sad coz im loosing nights trying to change this imeis and put the originals wrhiten in the back of the box. Xposed work, says ok saved and must restart, but when i do, there is no change at all. Tried softwares on pc in adb mode then shell then su, the program says ok but dont change. Dont know more what to do
any help please?
i want to thank everyone that knows how to solve this problem but didnt help me. Know that after 1 week of no sleeping and trying thousand things, i finally changed the both imeis to originals from the box. Im not a chief, i have buyed this phone legally, i have all original itens and documents and just got a bug. I hope i could continue to help people here with what i know, and never do what they did to me (or did not).
Did you try this guide here: https://www.******.com/repair-imei-snapdragon-device/
It's what I used to repair my IMEI in 2016 when I had a similar problem.
KwesiJnr said:
Did you try this guide here: https://www.******.com/repair-imei-snapdragon-device/
It's what I used to repair my IMEI in 2016 when I had a similar problem.
Click to expand...
Click to collapse
i tryied. A lot of things. A thousand tutorials and guides indeed. What worked was using a program to backup the partitions, then find, inside the binary file, the codified imeis, then change them to original imeis (using another program to change imei to binary) and save the file, then erase modem partitions in the phone with twrp, and then flash back the edited backup file with the right imeis changed.
edit: ofcouse nobody told me that, i had to try almost all possibilities on whole web and get little informations from thousand topics about thousand different things and put the pieces together.
brunojborges said:
...
edit: ofcouse nobody told me that, i had to try almost all possibilities on whole web and get little informations from thousand topics about thousand different things and put the pieces together.
Click to expand...
Click to collapse
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Gachmuret said:
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Click to expand...
Click to collapse
This forum has the most expert phone users in the world together, i can shure u at least one or two that knew how to solve, did read this thread but say nothing. But no problem my friend, was the very most hard thing i ever did, i will try make a simple steps and try to guide who need this to the right way. Just a moment.
Gachmuret said:
Great that you solved your issue on your own... What I was asking myself is if you're seriously blaming others here for not providing a solution? Here people share what they now and their experiences... And I'm sure that all who read about your issue shared what could help you if they knew anything at all (and it didn't involve stuff forbidden from XDA Forum rules).
If you should really except, that folks here owe you to provide a solution then better look out for ZTE customer support (and be glad if you get any [surely useless] answer at all...) ... Although even they are fine out if device's software was modified...
But what I ask you do is to give a good example and provide your solution in a handy guide as you're the first one that I know of that actually found a solution for the lost IMEI issue, that happend only to very few persons before you here on XDA.
Click to expand...
Click to collapse
Fist: This can potentially screw up your phone rendering it the equivalent of a paper weight IF not done correctly. So pay attention to each step. I am not responsible for lost baseband's, lost IMEI's, bricked phones and nuclear war. Proceed with caution and via your own will.
the phone must be rooted and with twrp.
in my case, i had the imei numbers on phone settings, but was invalid numers and they was the same on sim1 and sim2. Im saying that because we will make a backup of the partitions where are the wrong imeis, then find this numbers in binary inside the backup file (we will use other program to open and edit this file, and there is a tip to find this numbers in binady, so i dont know how to find where line is the imeis stored if they are erased or 0), then change this numbers in the file to the right ones using another program to change the right imeis to binary (so you must have the box of the phone with the original imeis or know them from somewhere as in any photo, text backup, etc), then erase this partitions on phone (after that my phone got crazy, hot, and with a lot of strange lines on system>about phone>imei information), then flash full stock with miflash (so then the imeis will show as 0 as the partitions will back but erased), then reflash any other rom with root and magisk and twrp, and then flash back the backup partitions file with right numbers changed. Then voalaa
most of the files to do this are here https://forum.xda-developers.com/general/general/guide-repairing-imei-qpst-qualcomm-t3856968
steps:
WRITE DOWN YOUR IMEI SOMEWHERE SAFE! IF you don't have it don't worry as your IMEI most likely is false / null. Whole reason we're here right? Ok. Now you want to connect your phone to your PC, enable diag mode on your phone, Install QPST Tools then open QPST Configuration. Allow debbug on developer options in phone, and when conect to pc, open adb prompt, and type:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
if this did not work, your phone has no root, or are not in debbug mode.
if was all right, you can proceed. remember if QPST.2.7.437 (version i used) did not recongnize your phone, maybe you must go into devices in windows and change driver to the one "qualcom" and with "901D" in the end.
Next open QPST Software Download and navigate to the Backup tab.
Make sure your com port is still showing and you are connected. Next click to the right of where it says xQCN file the "Browse" button and set a location and name your backup file something like coolpad_original_qcn.qcn . Save it as .qcn format not xQCN.
Now you are ready to open up MiTeC Hex Editor(program name) and load up your QCN file. So do this. Once loaded you will want to search for 088a to find your IMEI within the file. Why? Thats how it is stored in hex format. The 08 will be what stays but the 3rd letter "8" is what your IMEI starts with so make sure you replace it.. e.g. IMEI 762429035623741 would be 087a.. and if it started with 6 086a etc.
You should have located the string now that shows 087a then following will be the rest of your IMEI just reversed. Should look like this which is from our example IMEI in step 3, "087A 2624 0953 2673 1400". This translates out to 7 skip the first 08 and the A then 62429035623741 so 762429035623741.
Open the last tool called IMEI Converter. Input your phones new (factory original) IMEI in the first box and take the output and replace "087A 2624 0953 2673 1400" with this string you just created. Save your .qcn file and MAKE SURE you do not overwrite your original QCN backup.
now i had to erase the partitions on phone. what was in this tutorial i found, did not work. but this did: fist i had to go into twrp, so i go into console and typed this 3 lines, pressing enter after each line separately:
dd if=/dev/zero bs=16384 count=1 of=erase_modemst.bin
fastboot flash modemst1 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
fastboot flash modemst2 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
after that, reboot your phone. mine got very hot, a little crazy, and with strange infos in imei options. so i thought if i restore to stock, the software would make partitions back again but erased. and this is what happend. i flashed full stock nougat with miflash (no need links here, is easy to find stock nougat for your device as miflash software), and boot phone. all ok and imeis "unknow".
so then, i used edl tools to flash a eld package oreo with twrp after (my goad was only install twrp, but i only know do this with this method, any other doesnt work for me). https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 (dont forget to read and get required files)
so with twrp, i did flashed a newer twrp and a rom slim aroma that has inbuid options to root and install magisk https://forum.xda-developers.com/axon-7/development/rom-slm7-dfnr-t3896486 (dont forget to read and get required files)
now, i enabled again debbug mode, and all this lines again in adb through pc:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
now for last, Open up QPST Software Downloader and goto Restore tab. Select your file we saved in the last step (.qcn file with imeis changed) and write it. Now reboot your phone. Check to see that your new imei is showing. Mine was back and i coudnt belive, only thing is that as the imeis was doubled, i didnt know how to change first so the imei 1 in my box is the imei2 on phone and imei 2 on box are imei 1 on phone. Not a big deal. I will not do all this again, no way.
tips: if your phone has stuck in DFU mode, just plug on pc and open edl tools, it will reboot to edl mode for you.
if your phone has stuck in edl mode, you will have to disassembly and disconect/connect battery flat. Is a bit easy, as you dont have to do nothing with the screen. or wait any days to drain the battery.
this is what i did after 1 week trying thousand tutorials. there was a lot of threads that i take some parts from one, ones from another, so i cant give the credits coz the truth is that i dont remember all them. I created nothing here, and 90% of what is here are not my words. all i did is put the pieces together. Really sorry for my bad english.
brunojborges said:
Fist: This can potentially screw up your phone rendering it the equivalent of a paper weight IF not done correctly. So pay attention to each step. I am not responsible for lost baseband's, lost IMEI's, bricked phones and nuclear war. Proceed with caution and via your own will.
the phone must be rooted and with twrp.
in my case, i had the imei numbers on phone settings, but was invalid numers and they was the same on sim1 and sim2. Im saying that because we will make a backup of the partitions where are the wrong imeis, then find this numbers in binary inside the backup file (we will use other program to open and edit this file, and there is a tip to find this numbers in binady, so i dont know how to find where line is the imeis stored if they are erased or 0), then change this numbers in the file to the right ones using another program to change the right imeis to binary (so you must have the box of the phone with the original imeis or know them from somewhere as in any photo, text backup, etc), then erase this partitions on phone (after that my phone got crazy, hot, and with a lot of strange lines on system>about phone>imei information), then flash full stock with miflash (so then the imeis will show as 0 as the partitions will back but erased), then reflash any other rom with root and magisk and twrp, and then flash back the backup partitions file with right numbers changed. Then voalaa
most of the files to do this are here https://forum.xda-developers.com/general/general/guide-repairing-imei-qpst-qualcomm-t3856968
steps:
WRITE DOWN YOUR IMEI SOMEWHERE SAFE! IF you don't have it don't worry as your IMEI most likely is false / null. Whole reason we're here right? Ok. Now you want to connect your phone to your PC, enable diag mode on your phone, Install QPST Tools then open QPST Configuration. Allow debbug on developer options in phone, and when conect to pc, open adb prompt, and type:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
if this did not work, your phone has no root, or are not in debbug mode.
if was all right, you can proceed. remember if QPST.2.7.437 (version i used) did not recongnize your phone, maybe you must go into devices in windows and change driver to the one "qualcom" and with "901D" in the end.
Next open QPST Software Download and navigate to the Backup tab.
Make sure your com port is still showing and you are connected. Next click to the right of where it says xQCN file the "Browse" button and set a location and name your backup file something like coolpad_original_qcn.qcn . Save it as .qcn format not xQCN.
Now you are ready to open up MiTeC Hex Editor(program name) and load up your QCN file. So do this. Once loaded you will want to search for 088a to find your IMEI within the file. Why? Thats how it is stored in hex format. The 08 will be what stays but the 3rd letter "8" is what your IMEI starts with so make sure you replace it.. e.g. IMEI 762429035623741 would be 087a.. and if it started with 6 086a etc.
You should have located the string now that shows 087a then following will be the rest of your IMEI just reversed. Should look like this which is from our example IMEI in step 3, "087A 2624 0953 2673 1400". This translates out to 7 skip the first 08 and the A then 62429035623741 so 762429035623741.
Open the last tool called IMEI Converter. Input your phones new (factory original) IMEI in the first box and take the output and replace "087A 2624 0953 2673 1400" with this string you just created. Save your .qcn file and MAKE SURE you do not overwrite your original QCN backup.
now i had to erase the partitions on phone. what was in this tutorial i found, did not work. but this did: fist i had to go into twrp, so i go into console and typed this 3 lines, pressing enter after each line separately:
dd if=/dev/zero bs=16384 count=1 of=erase_modemst.bin
fastboot flash modemst1 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
fastboot flash modemst2 erase_modemst.bin (not shure if this lines did anything, but i did it anyway)
after that, reboot your phone. mine got very hot, a little crazy, and with strange infos in imei options. so i thought if i restore to stock, the software would make partitions back again but erased. and this is what happend. i flashed full stock nougat with miflash (no need links here, is easy to find stock nougat for your device as miflash software), and boot phone. all ok and imeis "unknow".
so then, i used edl tools to flash a eld package oreo with twrp after (my goad was only install twrp, but i only know do this with this method, any other doesnt work for me). https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759 (dont forget to read and get required files)
so with twrp, i did flashed a newer twrp and a rom slim aroma that has inbuid options to root and install magisk https://forum.xda-developers.com/axon-7/development/rom-slm7-dfnr-t3896486 (dont forget to read and get required files)
now, i enabled again debbug mode, and all this lines again in adb through pc:
adb devices (to check if the phone is identified correctly)
adb shell
su
setprop sys.usb.config diag,serial_tty,serial_smd
now for last, Open up QPST Software Downloader and goto Restore tab. Select your file we saved in the last step (.qcn file with imeis changed) and write it. Now reboot your phone. Check to see that your new imei is showing. Mine was back and i coudnt belive, only thing is that as the imeis was doubled, i didnt know how to change first so the imei 1 in my box is the imei2 on phone and imei 2 on box are imei 1 on phone. Not a big deal. I will not do all this again, no way.
tips: if your phone has stuck in DFU mode, just plug on pc and open edl tools, it will reboot to edl mode for you.
if your phone has stuck in edl mode, you will have to disassembly and disconect/connect battery flat. Is a bit easy, as you dont have to do nothing with the screen. or wait any days to drain the battery.
this is what i did after 1 week trying thousand tutorials. there was a lot of threads that i take some parts from one, ones from another, so i cant give the credits coz the truth is that i dont remember all them. I created nothing here, and 90% of what is here are not my words. all i did is put the pieces together. Really sorry for my bad english.
Click to expand...
Click to collapse
Great to have that here. Thanks for putting it together, impressive.