Related
I am completely new to Android and all of this flashing stuff. This is my first tutorial hope it helps some out there. I really couldn't find one tutorial that helped me completely so I put stuff I used from many into one.
MAKE SURE YOUR ESN IS CLEAN AND NOT A STOLEN PHONE. IN MY CASE IT WAS A CLEAN ONE.
What you need:
1. QPST 2.7 Build 323 (Look it up yourself and download it)
2. ADB and DIAG drivers here
3. The 60650.prl from this site http://www.corolada.com/prl/
Here are the steps.
1. Make sure that your Evo's drivers are all installed. By that I mean the ADB and HTC DIAG drivers.
2. Dial ##3424# which will put your phone in Diag mode, and enable usb debugging.
3. You can follow this to install the DIAG and ADB drivers.
http://forum.xda-developers.com/showthread.php?t=697487&highlight=cdma+workshop
4. Once done installing the DIAG driver make sure you're still on device manager.
Make sure you see this below:
Now right click on HTC USB Modem and click properties, and something like this will come up:
take note of the port # on the top, in my case COM4
5. Now open CDMA workshop in Administrator mode. Right click Run as Admin. This will come up:
6. Click on connect on the bottom right, on the bottom left it should say "Connected to (your COM name) port successfully" in my case COM4
7. Click on other and make sure it says NAM1 for the first flash. Click write and browse for the 60650.prl and select it press open. Something like the second image should pop out, just press ok the prl has been flashed.
8. Now where it previously said NAM1 press the arrow down and click NAM2. Click write and browse again for 60650.prl do the same as step 7.
9. You are done. Close CDMA workshop. Reboot your EVO.
10. Go to update your PRL
11. Punch ##3282# hit edit type your MSL pass, go to Data Profile, hit menu and hit RESET.
12. Reboot once more and youre good to reactivate your EVO.
Sources:
http://forum.xda-developers.com/showthread.php?t=937652
http://forum.xda-developers.com/showthread.php?t=898628
http://forum.xda-developers.com/showthread.php?t=737594
http://forum.xda-developers.com/showthread.php?t=697487
http://www.corolada.com/prl/
REMEMBER FLASHING IS AT YOUR OWN RISK AND I AM NOT HELD RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE (IM NOT SAYING THAT ANYTHING BAD IS GOING TO HAPPEN). I JUST SAY THIS TO PROTECT MYSELF. THIS WORKED FOR ME, I HOPE IT WORKS FOR YOU.
My proof:
Today in my room at 11AM with Metro PCS prl (Look at the bars XD)
Today at 7PM in my room with Sprint prl (Look at the bars)
But people need to be reminded, if You bought a *STOLEN* Sprint evo (one that has been reported) it won't work on Sprint.
So make sure you check the ESN with Sprint before hand.
Yes ill edit that into the post thanks bro.
Sent from my PC36100 using XDA App
i posted this in the wrong section is there a way this can be deleted or reposted in the development section?
hey, do you think this will work for the evo shift?
EDIT:
I followed your instructions which are pretty simple to the letter, after rebooting, im still stuck with metro prl. I tried updating it with using wifi, but no luck.
EDIT2: Whats weird i that the "sprint zone" msg comes up, so some kind of progress was made..... to be continued upon further discoveries!!
Edit3: Ok, it finally took after resetting the phone a few times, and it does show the new prl. But now, it takes forever to update the prl. The only other prob is I cannot find my msl code, neither thru msl reader or cdma workshop, they both tell me its 6 zero's. Boy oh boy!!!
Hello pediz123
I have couple questions on your tutorial.
1. Is it possible if I use DEMO-CDMA Workshop with your tutorial? I went to the link they gave me the demo version.
2. In your tutorial, I dont see when you run "QPST 2.7 Build 323". What is it for?
Thanks
inw
Sometimes when you flash a new radio, or you mess around in QPST you can break your data. Whats behind the breakage you may ask? Its your AAA and HA shared secrets.
A little background information:
The HA key is what gets you 1x data on your carrier. This is carrier specific, however is NOT phone specific. This could be google'd if you really required it.
The AAA key:
This IS device specific, you cant google it. Its connected to your account, and the way to get it is not what some consider easy. This is what gets you EVDO speeds, with out it you are stuck on 1x. If you call your carrier they will not give it to you either.
Continuing on to more information...
We will need a few tools to backup the keys, some free some not.
Team BlueRidge Sense 2.1 (it contains proper apps for using DM PORT)
QPST (free find it online)
CDMA Workshop (the demo should be fine, you could also borrow it)
HTC DIAG drivers (Just google it and find the installation guide)
Time
A hex editor
Now for the fun.... (If something seems too vague, google it)
First, we must get msl, use the app MSL Reader in the market.
Now, dial ##PORT# on the you will get a menu, hit enable, and then
go ahead and enter your MSL.
Now, lets open QPST, set up the phone, and go to EFS in the services tab of QPST
Now in EFS, make a folder called "open sesame door" without quotes all lower case in the root directory of the file system
reboot your phone
Now---- Open CDMA workshop and connect to the com port of your phone
Lets do memory read here, see where stuff is
Readable area from: 013D:0000
Unreadable area from: 01EA:0000
Readable area from: C000:0000
Process is stopped at: C0F1:0000
That says, we can read 013D:0000 and C000:0000 Ill save you time and tell you we need to dump 013D:0000 however (for all vm ive seen)
So now, lets go back to cdma workshop (should be there already) and choose to read Memory, make sure eeprom is not checked
Start address will be 013D:0000 (what i mentioned earlier)
size 99999999
This will scan the phone and dump everything into a .bin
Lets get a snack while this dumps... It will take a while
_________________________________________________
Okay, now the thing is dumped, lets call this scan1.bin
Open this in hex now, and hit ctrl+f
search for the word "secret" No quotes of course
now (for vm) you will see vmug33k that is your HA key, the first one showed under secret is ALWAYS HA key
look down one line, whalla, your aaa key is right below. (BACK THIS UP email it to yourself take a picture, ect, DONT LOOSE IT EVER, YOU WONT GET IT BACK)
so now you have your keys backed up, i cant tell you what you can or cannot do with them, it is up to you the end user, however i cannot endorse flashing phones or any illegal activity. In the mannor I am providing this, it is to ONLY save your aaa key incase of a bad radio flash, if you ever find a leaked radio.
You're right Simon, you will not get that AAA secret back, better hope you have warranty if you lose it (i know from experience). Thanks for this.
On another note, do you know if their is a way to increase max speaker volume through qpst on this phone?
Does it allow you to write also?
What do you mean write?
To another device
Sent from my HTC_A510c using Tapatalk
You can but I can not say how as it's illegal in some cases. If you, the end user choose to, it is up to you. I can not endorse it, however, I can say, qpst is your friend
Sent from my HTC_A510c using Tapatalk
You say line below but that's a bit vague seeing as you don't say what offset length your using. Are you using 8, 10, 16 offset or what?
How long is the AKEY?
I'm a bit confused. I had it with QXDM but it doesn't work under Vista so I can't look it up the easy way.
Any help would be appreciated.
QXDM runs on Win7, don't know why it wouldn't on Vista... [the key is one must run it in XP compatibility mode]. That being said, the above tutorial references a tool in QPST [which doesn't require compatibility mode] called EFS Explorer; then switches to CDMA ware. It works as prescribed; no QXDM needed [QXDM didn't work for me attempting the easy way; doesn't display second set of info].
On specific question, if you open the dumped file in a hex editor [like HxD], you can visually see your aaa key after searching, as the tutorial suggests you do. I didn't need to put any offsets in my hex editor. You will find the aaa key to be 10 characters I believe for our phones [or more [[double that]] in binary].
Hope that helps; thanks for the tut Simon.
Rob
Sent from my PC36100 using Tapatalk 2
I have been trying rigorously to flash the Galaxy Nexus until I stumbled onto urhaxable's script! I didn't find any simplified versions of it so I thought I would post a tutorial to help other like me. BTW this is my first post so please take it easy on me
If you have been trying to flash the Galaxy Nexus CDMA with no donor to PP look no further. ** Wont work with Verizon with bad ESN. If you are trying to flash to 3G with donor checkout primes tutorial http://forum.xda-developers.com/showthread.php?t=1696621.
1. Root your device and Install the toroplus AOKP ROM because it's easier to change PRL and get into DIAG:http://goo.im/devs/aokp/toroplus/aokp_toroplus_jb-mr1_build-5.zip
2.Download drivers for the Galaxy Nexus 32bit: http://www.mediafire.com/?c21e22x75a9ocpb 64bit: http://d-h.st/v3n
3.Download the programming software called ETS, because the Galaxy Nexus has a VIA chip set not a Qualcomm : http://www.digzip.com/files/1PAPNCQU/homework.html
4. After you have done all the above change you PRL download :http://www.howardforums.com/attachment.php?attachmentid=79544&d=1331322180 then rename the file to test.prl and put it into your the root of your phone. After you've done that go to setting>sprint tools>roaming and click old school.
5. The phone must restart, after it restarts you will still see sprint on the phone but don't freak out the PRL is modified for Sprint.
6. Enable debugging by going to developer if you don't have you can enable it by going into about phone and scrolling all the way down to build number and clicking it six times until it tells you that Developer is enabled. After doing that go to developer and enable debugging.
7. Enable USB DIAG by going into setting>sprint tools> Advanced and checking USA DIAG mode.
8. Open up ETS determine what COMM your phone is plugged into and go to ETS and bring down debug>COMM>USB and select the COMM your phone is plugged in. If it's the right one you should see the it's connected to make sure it is connected go to debug>start up commands.
9. When everything is ready to go go to ETS>Utilities>Script utility and copy this script that is provided by urhaxable go send him a thanks!
Script:http://gogreeninyourhome.com/go-green-files/PagePlusFullFlash.srp copy the script and paste it in script utility and follow the instructions on the script!
10. If it doesn't work then maybe you didn't put MIN in the right place. To put it manually call *#*#your MSL#*#* then go to edit put in your MSL and click MSID and change it to your MSID to the MIN that was provided by PP or dealer.
If you it still doesn't work try and try again and if tried and tried shoot me a PM!
Credits: autoprime, urhaxable, and pclover
.
So does the No Donor script allow 3G access or do you have to have a donor?
I've got mine working with a DInc donor, but would like to do away with the whole donor thing, due to grey legal area.
N3M3515
I'm sorry you need to have a donor to get 3G working. Even if though it says you have 3G you don't. And it's not illegal to copy info from a donor phone as long as you own both phones, so don't worry about that
Sent from my Galaxy Nexus using xda app-developers app
Mercy300 said:
I have been trying rigorously to flash the Galaxy Nexus until I stumbled onto urhaxable's script! I didn't find any simplified versions of it so I thought I would post a tutorial to help other like me. BTW this is my first post so please take it easy on me
If you have been trying to flash the Galaxy Nexus CDMA with no donor to PP look no further. ** Wont work with Verizon with bad ESN. If you are trying to flash to 3G with donor checkout primes tutorial http://forum.xda-developers.com/showthread.php?t=1696621.
1. Root your device and Install the toroplus AOKP ROM because it's easier to change PRL and get into DIAG:http://goo.im/devs/aokp/toroplus/aokp_toroplus_jb-mr1_build-5.zip
2.Download drivers for the Galaxy Nexus 32bit: http://www.mediafire.com/?c21e22x75a9ocpb 64bit: http://d-h.st/v3n
3.Download the programming software called ETS, because the Galaxy Nexus has a VIA chip set not a Qualcomm : http://www.digzip.com/files/1PAPNCQU/homework.html
4. After you have done all the above change you PRL download :http://www.howardforums.com/attachment.php?attachmentid=79544&d=1331322180 then rename the file to test.prl and put it into your the root of your phone. After you've done that go to setting>sprint tools>roaming and click old school.
5. The phone must restart, after it restarts you will still see sprint on the phone but don't freak out the PRL is modified for Sprint.
6. Enable debugging by going to developer if you don't have you can enable it by going into about phone and scrolling all the way down to build number and clicking it six times until it tells you that Developer is enabled. After doing that go to developer and enable debugging.
7. Enable USB DIAG by going into setting>sprint tools> Advanced and checking USA DIAG mode.
8. Open up ETS determine what COMM your phone is plugged into and go to ETS and bring down debug>COMM>USB and select the COMM your phone is plugged in. If it's the right one you should see the it's connected to make sure it is connected go to debug>start up commands.
9. When everything is ready to go go to ETS>Utilities>Script utility and copy this script that is provided by urhaxable go send him a thanks!
Script:http://gogreeninyourhome.com/go-green-files/PagePlusFullFlash.srp copy the script and paste it in script utility and follow the instructions on the script!
10. If it doesn't work then maybe you didn't put MIN in the right place. To put it manually call *#*#your MSL#*#* then go to edit put in your MSL and click MSID and change it to your MSID to the MIN that was provided by PP or dealer.
If you it still doesn't work try and try again and if tried and tried shoot me a PM!
Credits: autoprime, urhaxable, and pclover
.
Click to expand...
Click to collapse
I think your homework link is messed up. Takes you to another page where you have to click on another link to click on another link to get no where but a bunch of pop-ups.
jemcon said:
I think your homework link is messed up. Takes you to another page where you have to click on another link to click on another link to get no where but a bunch of pop-ups.
Click to expand...
Click to collapse
Which link are you talking about? I checked them and there's nothing wrong?
This works forThe sprint galaxia nex?
Or I need other tutorial? Thanks
Sent from my XT910 using Xparent Red Tapatalk 2
maniacopr said:
This works forThe sprint galaxia nex?
Or I need other tutorial? Thanks
Sent from my XT910 using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
Yes it will work for toroplus
VZW Galaxy Nexus to Pageplus%^&*()
Mercy300 said:
I have been trying rigorously to flash the Galaxy Nexus until I stumbled onto urhaxable's script! I didn't find any simplified versions of it so I thought I would post a tutorial to help other like me. BTW this is my first post so please take it easy on me
If you have been trying to flash the Galaxy Nexus CDMA with no donor to PP look no further. ** Wont work with Verizon with bad ESN. If you are trying to flash to 3G with donor checkout primes tutorial http://forum.xda-developers.com/showthread.php?t=1696621.
1. Root your device and Install the toroplus AOKP ROM because it's easier to change PRL and get into DIAG:http://goo.im/devs/aokp/toroplus/aokp_toroplus_jb-mr1_build-5.zip
2.Download drivers for the Galaxy Nexus 32bit: http://www.mediafire.com/?c21e22x75a9ocpb 64bit: http://d-h.st/v3n
3.Download the programming software called ETS, because the Galaxy Nexus has a VIA chip set not a Qualcomm : http://www.digzip.com/files/1PAPNCQU/homework.html
4. After you have done all the above change you PRL download :http://www.howardforums.com/attachment.php?attachmentid=79544&d=1331322180 then rename the file to test.prl and put it into your the root of your phone. After you've done that go to setting>sprint tools>roaming and click old school.
5. The phone must restart, after it restarts you will still see sprint on the phone but don't freak out the PRL is modified for Sprint.
6. Enable debugging by going to developer if you don't have you can enable it by going into about phone and scrolling all the way down to build number and clicking it six times until it tells you that Developer is enabled. After doing that go to developer and enable debugging.
7. Enable USB DIAG by going into setting>sprint tools> Advanced and checking USA DIAG mode.
8. Open up ETS determine what COMM your phone is plugged into and go to ETS and bring down debug>COMM>USB and select the COMM your phone is plugged in. If it's the right one you should see the it's connected to make sure it is connected go to debug>start up commands.
9. When everything is ready to go go to ETS>Utilities>Script utility and copy this script that is provided by urhaxable go send him a thanks!
Script:http://gogreeninyourhome.com/go-green-files/PagePlusFullFlash.srp copy the script and paste it in script utility and follow the instructions on the script!
10. If it doesn't work then maybe you didn't put MIN in the right place. To put it manually call *#*#your MSL#*#* then go to edit put in your MSL and click MSID and change it to your MSID to the MIN that was provided by PP or dealer.
If you it still doesn't work try and try again and if tried and tried shoot me a PM!
Credits: autoprime, urhaxable, and pclover
.
Click to expand...
Click to collapse
Thank you for this. I have managed to make a pageplus call but and Everything is fine until I reboot!! All the values reset to unknown.. any help is appreciated.
So I hope this thread isn't too useless. I've been researching how to restore my imei after losing 4g signal when my phone randomly (just sitting there on the desk, not touching it), decided to get stuck in a reboot loop.
Here's my specs:
Network: AT&T
ROM: CyanogenMod 11-20141112-SNAPSHOT-M12-d2lte
Modem: UCUEMJB
Recovery: ClockworkMod 6.0.4.3
Device Model: SAMSUNG-SGH-I747
Product Code: Not Active
PDA Version:
Baseband Version: I747UCUEMJB
CSC Version:
Kernel Release: 3.4.104-cyanogenmod-g9f57632
Kernel Version: #1 SMP PREEMPT Tue Nov 11 22:15:56 PST 2014
ROM Build: d2uc-user 4.3 JSS15J I747UCUEMJB release-keys
Android Version: 4.4.4
BusyBox Version: 1.22.1
SU Binary Version: 2.40:SUPERSU
So here's what I've learned. My IMEI was lost due to a weird Samsung backup procedure that backed up my /efs folder with essentially a blank copy of important information. I have my IMEI, but writing it to the phone is very difficult. From this tutorial I learned to download QPST, and somewhere else I heard about EFS Professional.
So I tried to use EFS Professional first, and have been able to connect my phone (Had to install adb first via the official android sdk). I was able to make a backup of my efs folder. I was also able to change the usb settings to DIAG + MODEM + ADB. Then I launched the Qualcomm NV Tools. From there, by unchecking "Send SPC" and "Read Phone" I was able to connect to the phone, but any other button I pressed didn't accomplish anything except disconnecting the phone again.
This is when I turned to QPST. I knew from EFS Professional which COM port my phone was using each time, and I added the COM ports to the QPST Configuration program for listening. But my phone was never listed as available in the ports tab, nor was it listed in my device manager under COM ports. I tried using the RF NV Item Manager anyway, entering in my IMEI "backwards" with an 8 in the first line and an "a" after the first real number in my IMEI, but my phone was never really connected, so of course nothing happened.
I learned this was probably because I have no IOTHiddenMenu / Qualcomm USB Settings Menu / whatever you want to call it with USSD codes, because I'm using an AOSP ROM (Cyanogenmod). This thread and this thread were useless in enabling DIAG mode, because of broken links and scripts that no longer work on newer versions of CM.
My next plan is to change ROMs to a TouchWiz ROM, but I haven't found a good one yet, especially considering I've upgraded my bootloader and I know that if I flash a ROM with a downgraded bootloader, I'll definitely brick my phone. So is there a ROM I can use with an upgraded bootloader that won't brick my phone and will allow me to enter DIAG mode so that I can connect to QPST via a COM Port, use the RF NV Item Manager, and put in my old IMEI? Or am I just going about this all wrong?
You do have to be on a TW ROM with a stock dialer for ussd codes to work. Based on everything you posted you should be on the mjb boot loader, but confirm that first. Enter this into a terminal or adb shell:
Code:
getprop ro.bootloader
If you are on an mjb bootloader, then this ROM should work for you http://forum.xda-developers.com/showpost.php?p=47816011&postcount=18. It's a rooted deknoxed at&t stock mjb.
Good luck.
---------- Post added at 12:04 PM ---------- Previous post was at 11:57 AM ----------
You probably already discovered this in your research, but just in case. When you get your imei problem solved, before flashing something other than a TW ROM, enter this in a terminal or adb shell:
Code:
su
reboot nvbackup
That will fix Samsung's whoops and give you a working efs backup partition instead of a blank one.
Thanks! I'll try this and get back.
alexalexalex09 said:
Thanks! I'll try this and get back.
Click to expand...
Click to collapse
You were right about the bootloader - when I looked up the ro.bootloader property, it spit back what I thought was my modem identifier, I747UCUEMJB - so yes, MJB. I'll get a chance to flash the new ROM tomorrow or the next day and see how it goes.
So, two steps forward and three steps back. I did install the new ROM. Initially, it appeared to work, because I was able to dial *#7284# to access the service mode menu and change UART to MODEM, and then dial *#0808# to access the USB Settings menu and change that to RMNET+DM+MODEM. After that, the phone showed up under COM5 in the Device Manager. I opened up QPST Configuration and added COM5 (labelled it "COM5") under ports. However, the phone never showed up (Phone column read "No Phone").
I then tried EFS Professional, but it was unable to detect the phone. I opened up the command line and tried an adb shell, but it didn't connect. Of course, the phone was in RMNET+DM+MODEM mode, not and ADB mode. I then went back into USB settings, changed it to DM+MODEM+ADB, and reconnected the phone. The phone wasn't detected by the computer, and hasn't been since.
I've restarted the phone and the computer multiple times (Windows 7 32 bit), uninstalled the phone drivers, reinstalled them in two different versions, uninstalled and reinstalled QPST (removing the relevant registry entries in between installs), and went through a number of combinations of settings on the phone. I tried with UART set to MODEM and PDA, with USB settings set to DM+MODEM+ADB, RMNET+DM+MODEM, MTP, and MTP+ADB. I made sure superuser was installed correctly and that developer mode was enabled. I still have not gotten the phone to charge in that USB port or show up in Device Manager in any way, even though the USB port on the computer still functions (can access flash drives from it). I plan to do some more googling and troubleshooting about this, but I haven't had the time to yet. On Wednesday I'll hopefully have a minute to try using my work laptop to access the phone. I think once I get the phone to be recognized via USB again I'll be able to have QPST Configuration recognize it, then I'll be able to use that RF NV Item Manager to enter in the new IMEI.
Also, in potentially unrelated news, my install of Titanium Backup is unable to recognize any apps I backed up, even ones that have been previously restored. It sees them in the backup folder (backup folder location says this folder contains 52 backups), but no apps wee listed in the backup/restore tab. Maybe this has something to do with the mount namespace separation setting in SuperSU? I'll test that later.
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
audit13 said:
Some newer ROMs will install but not give you cell service without the newest bootloader and modem.
Try flashing the last release of CM11. I would not touch the bootloader, modem, or EFS folder until you try an older ROM.
Click to expand...
Click to collapse
Thanks for chiming in, but I don't understand how this applies. I was on CM11 when my IMEI was removed. When you lose your IMEI, the main symptom is that you can't connect to 4g anymore, and you're stuck on EDGE, which is what happened in my case. I can in fact make calls and send texts, and even load web pages without wifi. It's just slow and prone to call dropping.
As for your advice to install an older ROM, I just flashed a stock ROM, the one linked above. It didn't cause my current lack of USB connection, because I had a USB connection for a while until I changed the UART and USB settings.
I definitely will not touch the bootloader - I've been warned about the dangers of downgrading from an MJB bootloader. I'm not sure what you mean by not touching the modem, but I'm going to assume it's as scary/difficult as the bootloader, so I'll be sure to stay away from changing that too.
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
alexalexalex09 said:
As far as not touching the EFS folder, as far as I see it, that's my only way out of this hole, because my end goal is to replace the IMEI that I randomly lost last week, and that's part of the EFS folder in some way that hasn't been explained to me (although I know it has to do with NV settings, maybe some file called nvdata.bin that I've never found, or the /EFS/IMEI folder?). So I think I have to ignore that bit of advice, unless you can give me a good reason to change my goal in all this.
Click to expand...
Click to collapse
I should note that I took a look at my EFS folder while writing this last post, and it's completely empty now. So that's fun.
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
audit13 said:
I suggested flashing back to an older ROM because you made some changes since your original post.
I suggested not touching the bootloader, modem, and EFS because flashing an incompatible bootloader/modem combination can hard brick the phone.
Since your bootloader and modem match, I'm out of suggestions other than perhaps visiting a repair shop to have it fixed.
Click to expand...
Click to collapse
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
alexalexalex09 said:
Thanks for the clarifications. I did visit a shop to see if they could fix it, and all I got were blank stares and people who don't want to deal with IMEI repairs. So back to my own attempts! I realized a couple days ago that my problem in connecting to the computer is that I've developed a crack on my phone's USB port. Also, I think my home desktop's messed up. So with a nice, sturdy cable I installed all the necessary program on my work laptop (Samsung Drivers, ADB, ES Professional, and QPST just for fun). I tried ES Professional first and by using the Qualcomm NV tools I was able to restore my IMEI! I rebooted the phone and now by dialing *#06# I see my IMEI followed by "/ 17".
So now onto the next problem: Still no 4g signal. Under Connections > More Networks > Mobile Networks, there are some errors. I only have one APN, named "ATT Phone" with an APN of "phone" and an MMSC of mmsc.mobile.att.net, and under network operator it simply says "Default Setup". Some research later, I realized this is a common problem, and I guess it has to do with my NV Data being messed up. Obviously, item 550 (0x226) is correct, which I was able to verify using a program called NV-items-reader-writer, but something else is screwed up. Peoplearmy has released a tool that can restore a backup up QCN file, which of course I don't have, so I'm in the process of seeking help from a generous soul who has an app that might help me. Apparently I could also use someone else's NV Items backup, replacing their IMEI with my own. But, I don't have one, so I'm stuck waiting on someone to be nice to me
I did try the method posted here: http://forum.xda-developers.com/showthread.php?t=1808408&page=16
But it didn't work. This thread and this thread and this thread were helpful to me for research.
Click to expand...
Click to collapse
I got it! Problem solved!!
So what I realized after going back over those research threads quickly was that I was using Peoplearmy's QCN generator incorrectly. Here's how I fixed it.
1. Opened QPST, followed directions here to connect my phone and start up QPST Software Download.
2. Having already injected my IMEI, I used the backup tab to make a backup.
3. I opened Peoplearmy's SG3QCNGenerator and imported the QCN file that QPST just created. I left "inject IMEI" unchecked, since I already had my original IMEI. I clicked Save As to set the directory and name of the new file, and clicked the Verify IMEI button that appeared to verify that it was correct.
This was the step I had missed - because I never had a valid QCN file to import, I never was able to create a new QCN file. My error in thinking was that, since my current QCN file was obviously messed up, I couldn't use it to make a new QCN file, but that's the whole point of this software.
4. Once I had the new QCN file, I went back to QPST's Software Download program and used the Restore tab. The QCN file generated by Peoplearmy's tool didn't match my model number, but I approved it anyway. It restored the QCN file correctly, but it had an error when it tried to reset the phone.
5. I rebooted the phone manually, and I now have 4G signal!
So, to summarize the difficulties I had:
1. I didn't make an nvbackup before I flashed CM a year ago, and it didn't hurt me until now.
2. I lost my IMEI and couldn't restore it because 1) I was on CM, which stopped me from putting my phone in DM + MODEM + ADB mode and 2) The computer/cable I was using to work on my phone, for whatever reason, were being stupid.
3. I didn't understand that in order to fix my phone I needed to restore my IMEI and repair my nv items (.qcn file)
4. I didn't realize that I could use Peoplearmy's tool to take a messed up nv items qcn file, fix it, and restore it to my phone.
All the tools I ended up needing: Samsung Drivers, ADB, ES Professional, QPST, and Peoplearmy's SG3 Data Restorer. Hope this helps someone else out there.
:good: thanks for posting fix.
"all i can really do , is stay out of my own way and let the will of heaven be done"
Great job. Thanks for posting your solution back here so others can find it.
OOPS!
You were following guides on XDA, and throwing random commands in ADB from the posts under the guides (DON'T DO THIS!) and now your slick new ROG phone 2 doesn't have mobile data, calls, wifi, or bluetooth. You quickly find out that flashing the phone with any firmware old or new, doesn't help you, as this issue is directly linked to your chip in your phone.
I quickly found that I needed a QCN file from someone with a rog 2 phone, however I could not get any help here on XDA except from the user Greatuser123, who did not want to give out his QCN file (understandably), but did send me some notes to try and help with other tools.
With nothing working, and no QCN file, I ordered another ROG 2 and waited for it in the mail. After it got here, I quickly extracted the QCN file, replaced the IMEI's in it, and used QPST to restore my phone.
I am simply writing this guide with the generic QCN file with my info masked out of it, so no one has to go through what I went through.
Common issue
This most commonly happens with ROG 2 Phones from the commands:
DO NOT RUN THESE COMMANDS UNLESS YOU KNOW WHAT YOU ARE DOING!
(spaced command to ensure no one runs this!)
fastboot erase modem st 1
fastboot erase modem st 2
Click to expand...
Click to collapse
On most phones, on a reboot, these partitions would be restored on reboot, but not on most ROG's.
Prerequisites
Rooted Phone
QPST
Qualcomm USB drivers
IMEI Converter
Platform Tools
The Fix
Follow the above root linked video, or find the root thread for your phone here on XDA, and root your phone. This will not work unless you are rooted, although I do not know how you would get into this mess without having your phone rooted already.
Install QPST tools
Install Qualcomm USB drivers
Download the attached zip "good_qcn.zip" and extract the .QCN file anywhere on your machine
Open the .QCN file with any Hex Editor (I used HxD) and search for the Hex-Values: 08 3A 85 99 99 99 99 99 99
NOTE: There will be TWO locations with this value. This is where your IMEI_1 and IMEI_2 will go. Your IMEI_2 goes into the FIRST occurrence, while your IMEI_1 goes in the second.
Download the IMEI Converter app and type in your IMEI_1 and click "Convert", place the converted hex output into a notepad or similar
Do the same for your IMEI_2 and place it in the same location
Now that you have the HEX version of both your IMEI's, paste your IMEI_2 in the FIRST occurrence of the fake IMEI in the QCN file
Paste your IMEI_1 in the last occurrence of the fake IMEI and now save your new .QCN file.
Ensure your device is in USB Debugging Mode.
Download and extract the Platform Tools if you do not have them already.
Plug your phone into your computer using either port
Navigate to your extracted Platform Tools and in a Command Line type "adb devices" to ensure your device is visible.
Run a shell with "adb shell" and elevate your permission with "su"
Now it is time to enable Diag mode by running "setprop sys.usb.config rndis,diag,adb"
At this time, if you installed the Qualcomm Drivers, your device manager should have a port similar to "Qualcomm HS-USB Diag". If not keeping trying to re-enter diag mode and ensure the drivers are correct.
Open up "QPST Configuration" which was installed earlier. You should see your phone listed under "Active Phones". Click "Start Clients" -> "Software Download"
The Port field of the QPST Software Download should list your phone, if not something is wrong.
Click "Restore", and in the xQCN field, click "Browse", change the file type from XQCN to QCN, and select your newly made QCN file
Click "Start", and once the process is done, restart your phone
Conclusion
If all went well, your phone should now have all its bells and whistles again. Sometimes it may require a Factory Reset, and this should always be the practice anyways. If you have mobile data, but only H+ or EDGE, dial *#*#4636#*#* on your phone and ensure LTE is provisioned.
Good luck guys!
Special thanks to: Greatuser123 for helping when no one else would, and HomerSp for his many useful guides that some tools and knowledge was borrowed from.
Hi bro, Nice to meet you and I did my best to help you out, as I spent some stress on this when I was one of the first people that suffered with this issue. And gladly you solved it, bro you misunderstood badly about I did not want to give you the qcn, I was going to give you my qcn file but first I was asking to you for some proof , photo of same phone as me and the package to know that you are not going to change or edit badly ( doing mischievousness) as you never sent the proof I did not send the qcn file.. you can re check again your messages. Bro
Thank you very much for this, life saver.
My wifi and bluetooth works fine but I cannot get my mobile to power back on. When I go into the menu mobile power is just not there :/
Do you have the global or the cn version?
BlazingBullets said:
Thank you very much for this, life saver.
My wifi and bluetooth works fine but I cannot get my mobile to power back on. When I go into the menu mobile power is just not there :/
Do you have the global or the cn version?
Click to expand...
Click to collapse
This QCN came from a global device, but I imagine this could be used to recover the mobile at least temporary to fully fix the device, no matter the origins.
Sorry for the delay.
Greatuser123 said:
Hi bro, Nice to meet you and I did my best to help you out, as I spent some stress on this when I was one of the first people that suffered with this issue. And gladly you solved it, bro you misunderstood badly about I did not want to give you the qcn, I was going to give you my qcn file but first I was asking to you for some proof , photo of same phone as me and the package to know that you are not going to change or edit badly ( doing mischievousness) as you never sent the proof I did not send the qcn file.. you can re check again your messages. Bro
Click to expand...
Click to collapse
No no, please do not think I meant you by that. It was other users (understandably) that questioned my motives before you. I absolutely would have taken you up on your offer if I did not already have the phone on the way Either way, I really appreciate your help during this, and I hope you continue to help other users the same way you did for me.
decrypterfixer said:
This QCN came from a global device, but I imagine this could be used to recover the mobile at least temporary to fully fix the device, no matter the origins.
Sorry for the delay.
Click to expand...
Click to collapse
After a lot of heart ache and even making an EDL cable I could not get cell network back. I"ve sent it into ASUS to get fixed. I have made a few backups and will diff them when I get my device back so hopefully I can see what they have fixed so others don't have to experience this.
BlazingBullets said:
After a lot of heart ache and even making an EDL cable I could not get cell network back. I"ve sent it into ASUS to get fixed. I have made a few backups and will diff them when I get my device back so hopefully I can see what they have fixed so others don't have to experience this.
Click to expand...
Click to collapse
I can help u
Well done mate you will be a hero someday haha good job ?
Leevii2208 said:
I can help u
Click to expand...
Click to collapse
Please provide your support ouvertly here and not via social media!
I've edited your post; please refer to https://forum.xda-developers.com/oneplus-5t/how-to/telegram-chat-channels-forward-t3765018
not work
ty but not working or i did wrong. i wrote (change my imei, two way u and other program) and post new "good.qcn" (i see finished in QPST Software). i restart phone but nothing change. i think phone in document just "read-only".
I want redmagic 3 qcn file
good job bro
Is it works for rog phone 3?
I can't find that hex
hello friends 08 3A 85 99 99 99 99 99 99 no found please help me
Hi, perfect post friend. Im try backup qcn to my Rog Phone 3, but when try said Satuts: Memory Backup Failer and Errors: Disr Error while write to file, any solution to this? I appreciate your help.
decrypterfixer said:
OOPS!
You were following guides on XDA, and throwing random commands in ADB from the posts under the guides (DON'T DO THIS!) and now your slick new ROG phone 2 doesn't have mobile data, calls, wifi, or bluetooth. You quickly find out that flashing the phone with any firmware old or new, doesn't help you, as this issue is directly linked to your chip in your phone.
I quickly found that I needed a QCN file from someone with a rog 2 phone, however I could not get any help here on XDA except from the user Greatuser123, who did not want to give out his QCN file (understandably), but did send me some notes to try and help with other tools.
With nothing working, and no QCN file, I ordered another ROG 2 and waited for it in the mail. After it got here, I quickly extracted the QCN file, replaced the IMEI's in it, and used QPST to restore my phone.
I am simply writing this guide with the generic QCN file with my info masked out of it, so no one has to go through what I went through.
Common issue
This most commonly happens with ROG 2 Phones from the commands:
DO NOT RUN THESE COMMANDS UNLESS YOU KNOW WHAT YOU ARE DOING!
(spaced command to ensure no one runs this!)
On most phones, on a reboot, these partitions would be restored on reboot, but not on most ROG's.
Prerequisites
Rooted Phone
QPST
Qualcomm USB drivers
IMEI Converter
Platform Tools
The Fix
Follow the above root linked video, or find the root thread for your phone here on XDA, and root your phone. This will not work unless you are rooted, although I do not know how you would get into this mess without having your phone rooted already.
Install QPST tools
Install Qualcomm USB drivers
Download the attached zip "good_qcn.zip" and extract the .QCN file anywhere on your machine
Open the .QCN file with any Hex Editor (I used HxD) and search for the Hex-Values: 08 3A 85 99 99 99 99 99 99
NOTE: There will be TWO locations with this value. This is where your IMEI_1 and IMEI_2 will go. Your IMEI_2 goes into the FIRST occurrence, while your IMEI_1 goes in the second.
Download the IMEI Converter app and type in your IMEI_1 and click "Convert", place the converted hex output into a notepad or similar
Do the same for your IMEI_2 and place it in the same location
Now that you have the HEX version of both your IMEI's, paste your IMEI_2 in the FIRST occurrence of the fake IMEI in the QCN file
Paste your IMEI_1 in the last occurrence of the fake IMEI and now save your new .QCN file.
Ensure your device is in USB Debugging Mode.
Download and extract the Platform Tools if you do not have them already.
Plug your phone into your computer using either port
Navigate to your extracted Platform Tools and in a Command Line type "adb devices" to ensure your device is visible.
Run a shell with "adb shell" and elevate your permission with "su"
Now it is time to enable Diag mode by running "setprop sys.usb.config rndis,diag,adb"
At this time, if you installed the Qualcomm Drivers, your device manager should have a port similar to "Qualcomm HS-USB Diag". If not keeping trying to re-enter diag mode and ensure the drivers are correct.
Open up "QPST Configuration" which was installed earlier. You should see your phone listed under "Active Phones". Click "Start Clients" -> "Software Download"
The Port field of the QPST Software Download should list your phone, if not something is wrong.
Click "Restore", and in the xQCN field, click "Browse", change the file type from XQCN to QCN, and select your newly made QCN file
Click "Start", and once the process is done, restart your phone
Conclusion
If all went well, your phone should now have all its bells and whistles again. Sometimes it may require a Factory Reset, and this should always be the practice anyways. If you have mobile data, but only H+ or EDGE, dial *#*#4636#*#* on your phone and ensure LTE is provisioned.
Good luck guys!
Special thanks to: Greatuser123 for helping when no one else would, and HomerSp for his many useful guides that some tools and knowledge was borrowed from.
Click to expand...
Click to collapse
I tried it till finish, but when I check, I lost my wifi mac address (status unavailable) and my imei still unknown. And now I wanna retry, I stuck at QPST Configuration application at step 17, it sometimes detected the phone, sometimes don't, it make me can't continue to click "star clients", (check in device manager, nothing wrong). can you help me?
sure which device rog 2 or 3?
gjkhan said:
sure which device rog 2 or 3?
Click to expand...
Click to collapse
uhhg that's a issue just download visual c++ redistributable 2010 sp1 x86 and it should be fine
gjkhan said:
sure which device rog 2 or 3?
Click to expand...
Click to collapse
Rog2. The port keep blinking when in QPST Tools, sometimes it detected, sometimes don't, so I can't copy the qcn to the phone. And also I don't know what's wrong with the qcn, I had follow the instruction, but it not works
hmmm use another pc or cable.
gjkhan said:
hmmm use another pc or cable.
Click to expand...
Click to collapse
Try itt but problem still persist