Related
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.
well Ive been looking for the 1st bootlogo for awhile.
Im on softbank364, and they have custom logo but I cant seem to find it.
I have dont think initlogo.rle is used much, I think i managed to change it (in streakmod recovery.img), but it only displays for a split second before strekmod loads.
Ive managed to get a logcat of boot, on line 349 (first reference ive seen for bootlogo it calls for logo.rle{which i havent been able to find either}, but is unable to load it. Im looking at the whole thing as I type this.
log is very large, split into 2 .txt files, best viewed with notepad++
thanks guys..
and NOOOOO you cant have a transparent bootlogo! just kidding!
dmesg log
adb shell dmesg log
may not even be here, but on another note Ive been looking into the qdl tool files, and trying to get QPST (qualcomm diag tool) to recognize streak in diagnostic mode not just download mode. probably a bit overboard, but I just want to rip into tjis to see what I can find, and learn in the process hopefully without screwing anything up beyond repair.
after flashing 364 softbank from 354(and 344 system.img), I then nandroided back to sd191, and still have softbank boot logo, hmm... so it looks like its in the update.pkg and not in nandroid anywhere. Im willing to bet if I qdl tool, ill get dell logo back. some of those files just cant be opened though and are encrypted and have algorithms etc.
fell free to bury this thread looks like it may be packed away in RC_us.IMG or one of the bootloaders.mbn 's , either way I think its low-level that will take reverse engineering and decrytping RSA's and algorithms. brain cells fried just looking at it.
Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.
Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though
I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2
download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck
Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359
What where you trying to flash?
Anyone tried succesfully?
These are the Folders & Files I used in the DE-HARD-BRICKING of the Verizon variant of the LG G4. The word out on the streets is that plenty of infected Qualcomm tools have been floating around, so I decided to share with the XDA community, as far as I know, the most recent and infection free versions that really work. I can feel for the ethical hackers out here that need to get things done with the peice of sound mind that there is nothing involved that may risk their machines security or waste time with tweaked versions that wont work for some reason or other. About the Firehose, Raw, & Patch... These are THEE ones for vs986 & ls991. I DO NOT KNOW if they will work with any other variants, although, I SUSPECT that they may work with all G4's. On the other hand . . . they very well may not. AGAIN, I DO NOT KNOW. Only vs986 & ls991 are confirmed. I am looking for HardBricked G4 owners to use these with non-confirmed variants to establish a consensus of statistics to universally root the G5 using Qualcomm Utilities. I know, Iknow. eMMc & UFS are different, Bro. BLAH! Blah! BlAh! I'm only asking for volunteers whom have a G4 in the 9008 coma and have nothing to loose. If somebody knows something that I don't, that can convince me I'm wasting my time, I am open to "practical reason". or if somebody knows that these DO WORK for all G4 models on all Android LP & MM, then this I'd also like to know also. Misdirection shan't be tolerated. MY un-bricking method is posted here
DriverPack>https://drive.google.com/file/d/0B41ACD_ESYnHQU1qSnVlVXhORjA/view?usp=sharing
G4BootRepair>https://drive.google.com/file/d/0B41ACD_ESYnHQy1sY0paaWYwQUU/view?usp=sharing
method>https://forum.xda-developers.com/g4/help/lg-g4-vs986-super-hard-brick-unbrick-fw-t3666784
QPST>https://drive.google.com/file/d/0B41ACD_ESYnHemxoOEdGVFVOVUE/view?usp=sharing
QFIL>https://drive.google.com/file/d/0B41ACD_ESYnHRG4ta2ZZMFVtcW8/view?usp=sharing
Driver Enforcement>https://drive.google.com/file/d/0B41ACD_ESYnHWWY4Rm1GelZZZ2c/view?usp=sharing
I'll be putting together a more detailed tut. if I feelm it's needed. but for now I'm assuming most of us are pretty far along. A big thank You to TheMadScientist for being the first volunteer of the G5. MODs , if this needs to be moved feel free.
CAN'T FORGET TO MENTION THIS GREAT WORK OF ART https://forum.xda-developers.com/showthread.php?t=2600575 & * USE BOARD_DIAG-2.99 FOR TOTS
There are things which are important when it comes to using this method
first of all there are no infected files out there. at least none I'm aware of and you can believe me I know a little about this topic.
the next thing is that it highly depends on what files you are using because they are device specific! I don't say they would not work though but they will make your phone a different one.
there is NO universal one package available to unbrick all device models with the same files! This is just imposssible.
There is one method available which is able to convert any G4 and for this just check my PoC thread in the G4 forum.
It's not possible to make all this without device specific files because you flash parts of the bootloader stack and those are always device specific.
I haven't looked into your files here yet but when they work for both device models then your files are converting ones which means either it will convert to ls991 or it will convert to vs986 depending on what files you have. I strongly believe you have those for the ls991.
I can say that I have all of them and I investigated then in deep.
There are some rare for ex for the H815 which work without converting and without blowing the fuses. But there some named as h815 but containing converting to ls991.
Keep in mind that converting a device this way may be irreversible depending on the files used.
If you blow efuses you're lost and its not possible to have your previous device model back again. Well ok when you buy a new mainboard then.. But that's the only way.
I just want to warn users especially bc I'm working on a safe way for converting a device forward and backwards.
When you have a vs986 and used that method: you should bring your device in fastboot mode. Check the serial. Does it starts with LGLS991....? Then you converted the device.
sfX
Sent from my LG-H815 using XDA Labs
Well put.I agree with every thing you mention. Although the end result I'm achieving is download mode to flash the correct FW that matches the board. This is why I only use the files related to laf and take notice that I am not including the boot.IMG because that would essentially be a game changer like you said. I personally am not interested in converting carrier variants.
I'd like to add, I have personally used these firehouse ,raw, & patch on both sprint and Verizon g4's to handle 9008 bricks. I just don't have in my possession an AT&t or TMO to try these files with. If anybody has an AT&T or TMO G4 that is 9008 bricked and would like to attempt something they have not tried yet. Do Not include any boot.IMG in the created recovery folder that is to be flashed. We are achieving download mode. That's it. To be able to use LGUP TO FLASH kdz or tot.
ls991 "Download Mode" recovery image
I have taken this https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing and simply relaced sprint stuff with verizon stuff. maybe I should rename my thread from "unbrick " to "recover download mode".
If when
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
gratefuldeaddougie said:
If when I flash the ls991 recovery folder to vs986 in QFIL, fastboot is acheived and the command prompt window report back as my verizon with the correct serial number. maybe this info can be useful to you, I hope. Because I change carriers more than I change devices and the crossover is a major PITA.
Click to expand...
Click to collapse
What do you see in fastboot? Can you make a pic for me?
Sent from my LG-H815 using XDA Labs
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
gratefuldeaddougie said:
I can not today. As I have sold the vs986 but am receiving 2 more bricked vs986's this week. I will post a pick. Pic of phone or PC cmd window? Which is of interest. Just curious although I'll post both.
Click to expand...
Click to collapse
no just a photo of the fastboot screen is enough. thx
btw: the download you link in your OP does not contain any image files - only the XMLs and the firehose?! or do i miss something here?
thx
sfX
I wanna jump on the hard brick train
Just everybody remember improper use or jumping the gun can lead past hard brick to totally unrecoverable device seen it happen a many times.
Ready Set Go
Before I begin, In reference to infected files, there are many discussions such as this https://forum.xda-developers.com/g4/help/mbn-msm8992-qpst-2-7-430-unbrick-g4-t3292097 Today I received a vs986 that as of first connection does not appear in device manager. I'm gonna be reviving it regardless of what it may needs. It's 98% cosmetically and I got it for $29 and I love doing this. the process will be documented and posted. And most of all I'd like to thank TheMadScientist & steadfasterX for their inspiration or I wouldn't be doing this. Let's cross are fingers and hope for a 9008 brick. I'll force QDloader mode with test points and screenshot the device manager and go from there. If a hardware issue is present then I will deal with that deck of cards first. Until then. . . . . . . . .. .
@ steadfasterX
Maybe I assume too much. I imagine that those who have made it this far are aware of the fact that they should have a copy of the firmware version they bricked on. At least as the bare minimum to get started with. Be back tomorrow with the results.
Having trouble?
https://drive.google.com/file/d/0B41...ew?usp=sharing Extract folder / Move folder into QFIL folder as a folder not as individual files / load the firehoseprogrammer, patch, & raw / Flash / Remove battery / insert battery / hold volume up and plug in at same time until "download mode" appears on device / wait for drivers to install ? flash vs98627C.kdz with LGUP.
This will only work if the device bricked on 27C or earlier. If you know what FW version you bricked on the extract that FW and replace the appropriate files in the recovery image folder. (for ls991 sprint>https://drive.google.com/file/d/0B41ACD_ESYnHa3pIQlFLYUttdzg/view?usp=sharing
i have my g4 on 28a so it means is not possible yet with mine ? :S
This guy figured it out back in May. Exactly the method I used. Here is his guide> http://forum.gsmdevelopers.com/showthread.php?t=28897&highlight=VS986+REPAIR I can now confirm this works only with the files from the version of FW that the device bricked on. .
28a kdz mega link
gustax said:
i have my g4 on 28a so it means is not possible yet with mine ? :S
Click to expand...
Click to collapse
https://mega.nz/#!blN0UCRB!OqJbq776ePL_PNBjzzooGU8kwTPWLAHNyXQz52TxovI
I HAVE TRIED TO EXTRACT THE FILES FROM FW 28A WITH WindowsLGFirmwareExtract-1.2.5.0, I CAN EXTRACT THE DZ FROM KDZFILE BUT WHEN I TRY TO EXTRACT THE FILE FROM DZ, THE SOFTWARE CRUSHED, I HAVE TRIED WITH WINDOWS 10 AND WINDOWS 7 AND THE SAME ISSUE. THE KDZ IT IS OK BECAUSE IT IS THE ONE I USED TO UPDATE MY PHONE
COULD YOU HELP WITH THIS
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
gustax said:
i downloaded the fw 27c and tried to extract the dz and happened the same issue, so i guess the problem is te software, but i dont know what a i need, any advice?
Click to expand...
Click to collapse
I will try the extraction on my PC. I have learned something about this method this weekend. This is a one time shot. After the second attempt the device blows a fuse. I believe the firehose programmer is the same, but, the raw & patch files are specifically for the sprint. I think I may have permanently bricked a device attempting to re-create the scenario in which I was successful with during the first go at it. I'm gonna look at the 27C.kdz real quick
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.