Related
All,
I blew it while trying to flash my Sprint-based Samsung Galaxy SII. In any case, right now, I'm not getting a carrier (No Service) as it appears the phone doesn't know my MIED? Also, my "home" and "menu" buttons don't work while the phone is booted (although I can get into diagnostic modes, etc., so they do work in the strictest sense). It also appears that my wireless isn't working..
I've tried to do a factory wipe/reset, but it didn't solve these problems.
Here are the specifics from Settings->Phone Info
Model number: SPH-D710
Android Version - 2.3.4
Baseband version - unknown
Kernel version - 2.6.35.7.I9100XWKJ3-CL647431
Build Number - GINGERBREAD.EG39
Hardware version - Unknown
Is there any way I can just slam the stock Sprint kernel back on here to get this back to some sort of a baseline. Also, I guess there's the MEID issue.. I think I can get that from Sprint or on the phone, right?
Thanks in advance..
Maybe start searching for threads about losing your EFS folder??
Hope this helps
I didn't find anything specific to Sprint... maybe it doesn't matter? I dunno. I'd appreciate a little more guidance if possible.
When I try to go into About phone->Status to see this stuff, I get "The process com.android.phone has stopped unexpectedly."
Hi, I'm no expert, when I saw that your phone could not find the SIM my first thought was that you had lost your EFS folder (which is really BAD), however on looking again at your first post I see it says baseband unknown - maybe you need to reflash the modem?
Sprint doesn't use SIM? So I think this might not (?) be an issue.
I will begin to look for how to reflash the modem--if you know of a thread that is better than another for this, I would appreciate it if you could post it here. Thank you, in advance.
Yeh, sorry should have typed carrier rather than SIM.
AFAIK to flash a modem with Odin, you can use the firmware for your phone selecting only 'Phone' .
You would probably be safer to search first or you could reflash your firmware and take your phone back to baseline as you put it.
I can't find a Sprint baseline ROM, could/should I try this one?:
samsunggalaxysforums.com/showthread.php/4692-Full-Guide-How-to-Debrand-your-Samsung-Galaxy-S2
There is a site called www.sammobile.com which used to be www.Samifirmware.com it was always a good source of up to date firmwares.
Unfortunately I am at work and we only have IE6 (I know), so I can't search the site for you.
Hey guys.
I bought this phone today from a friend (who bought it from someone online a few days ago) and it was working fine. I went down to Meteor in Ireland and got a new micro sim. Everything was perfect, I was able to call and make texts no problem.
The trouble was that it was stuck on 4.0.4 and would not update. After a while I figured out it was jailbroken with clockworkmod.
Keep in mind I have no idea what I was doing at this stage.
I wanted to unroot the phone completely.
After looking online I downloaded a program called Odin and downloaded a "stock image file" for Ireland. The file seemed to indicate generic Ireland.
Using Odin I flashed this file onto the phone, it completed.
Everything seemed fine, it was version 4.1.2.
Then I discovered I could not make calls or texts. I got the error "Not Registered on Network". I also got the "No Service" message in the toolbar.
I searched available mobile networks through the phone and set it to meteor. The "No Service" message went away but it was still listed as "Not Registed on Network".
I had nothing backed up before I did this.
Am I completely screwed?
I am completely furious with myself for doing this...
My last resort is downloading a new stock image file for "Meteor (Ireland)" and possibly flashing that to the phone. But it currently has a 3 hour download time.
Any tips?
Does the IMEI and serial number under the battery match the ones given in settings, about device, status?
boomboomer said:
Does the IMEI number under the battery match the one given in settings, about device, status?
Click to expand...
Click to collapse
No it does not match.
I also have no idea if it matched before I did this update.
I really hope there is a way out of this otherwise I just flushed away a lot of cash!
You can try flashing a modem that might enable the imei to be read again:
http://forum.xda-developers.com/showpost.php?p=43946365&postcount=15
But if that doesn't work then you'll need to take it to a service centre for a repair.
boomboomer said:
You can try flashing a modem that might enable the imei to be read again:
http://forum.xda-developers.com/showpost.php?p=43946365&postcount=15
But if that doesn't work then you'll need to take it to a service centre for a repair.
Click to expand...
Click to collapse
I will give that a try thank.
I downloaded the zip file from the thread. Not sure what to do with it though (not joking when I said I had no idea what I was doing lol).
Do I need to flash it through Odin again?
Thanks!
Figured out how to modem flash.
Still no luck...
Absolutely nothing else I can do?
Not without a backup of the phone's original efs folder no, sorry.
Try having a read of this thread, which explains better;
http://forum.xda-developers.com/showthread.php?t=2393289
boomboomer said:
Not without a backup of the phone's original efs folder no, sorry.
Try having a read of this thread, which explains better;
http://forum.xda-developers.com/showthread.php?t=2393289
Click to expand...
Click to collapse
Oh my...
Can't describe how annoyed at myself I am.
My IMEI number actually looks like a proper number but it just doesn't match.
If I bring it to a generic phone repair shop down town do you think it can be fixed?
Is the phone basically useless? :-/
I have the same problem but my imei and serial are ok. Can't connect to the network.
alan3002 said:
Oh my...
Can't describe how annoyed at myself I am.
My IMEI number actually looks like a proper number but it just doesn't match.
If I bring it to a generic phone repair shop down town do you think it can be fixed?
Is the phone basically useless? :-/
Click to expand...
Click to collapse
Probably, the S3 support is quite common.
alan3002 said:
Oh my...
Can't describe how annoyed at myself I am.
My IMEI number actually looks like a proper number but it just doesn't match.
If I bring it to a generic phone repair shop down town do you think it can be fixed?
Is the phone basically useless? :-/
Click to expand...
Click to collapse
Yes cost about 25 punts .
jje
Hello everyone here on XDA !!!
First i want to say sorry if there is another thread with this particular problem, searched the forums but i didn't find something related to my problem
Here's the thing:
A friend gave me an Atrix 4G for free, with no baseband and no IMEI number. All i know about the device is that he used OTA update and went wrong.
Here is what i know about the device
Stock 2.3.4 no ROOT and no Bootloader Unlocked
System version
45.31.0.MB860.Retail.en.GB
Build number
4.5.2A-74_OLE-31
(i think the phone was not on any UK Carrer because the system version, i saw that those who are branded have carrer name not retail, altough i don't know what "retail" comes from, maybe the phone is unlocked by factory)
What i tried to do to solve problem
Searched internet , found something about radio issue, flashed different radios via fastboot with no luck.
Found a stock image on internet with the same build nr. and system version. it's .sbf.gz file.
i used RSD even tough i read it can brick my device for good but i said wtf (turned off the phone and enter RSD mode with Power+Vol. Down button)
1 used the file as it is XXXXX.sbf.gz and rsd unpacked it and flashed it.RSD said "passed" the phone booted up with "insert SIM" message.Rebooted to insert sim but again no baseband and no imei number
2 i unpacked the archive with 7zip to get the XXXX.sbf file, RSD said passed the phone booted up with "insert sim" message, rebooted and again no baseband and imei...
in both cases my baseband number is N_01.100.00R ( i don't know if these are correct, i think this imei number is the one from witch device was .sbf extracted or something like that and after reboot the data from ROM is not the same as the data from NVRAM)
Mod Edit: Don't post your IMEI on a website full of hackers, silly
I also found something about NVRAM and it's data that could possibly be corrupted but nothing about how to restore it, and messing around with the NVRAM could lead to a dead device
This is not the first time in android world my friends have smartphones and ask me to root and instal custom roms on them and every time they have problems with their devices i help, but i do not own a smartphone because i can't afford one and that's why i want so bad to make this atrix work
Again i'm sorry if this is a duplicate thread but i searched around xda and google but didn't found the answer , maybe i'm too dumb....
EDIT: well guys i did it, if someone encounters this problem, here is how i fixed it:
1. RSD the apropiate .sbf for atrix, and let it boot for the first time
2. reboot or pull the battery out and start the phone.enter fastboot mode and flash a radio or the same radio as in your .sbf file
done! now the phone will have imei and baseband after reboots
edit 2: guys today my phone rebooted and i have no baseband and imei, the phone worked for a day and a half, rebooted twice, but today was the 3'rd reboot and went band, i flashed the radio but nothing, please help me
real cool guys....
you guys are great, a lot of views not one single reply, about anything, for other stupid questions around here is somebody to post an answer, for my question nothing, not a single tought...nice
junk33 said:
you guys are great, a lot of views not one single reply, about anything, for other stupid questions around here is somebody to post an answer, for my question nothing, not a single tought...nice
Click to expand...
Click to collapse
First, CALM DOWN.
Now that we are all cool, this is a forum, not a help desk. If no one has posted anything is either this has been answered before or that no one has an proper answer.
This has been in fact, discused a few days back and we reacghed the conclusion that there was nothing we can possibly do to fix it, other than take it back to motorola's rma
Console
well thank's for the answer, one more question, can i acces a debug console or whatever it's called, i mean there is an error after first reboot and it's keept somewhere in a tex file i guess, how can i access the "guts" of this device?, since i don';t have any idea where to take it in my country, and no GSM Service was unable to help me with an answer i want to mess around with it and learn more about android
junk33 said:
well thank's for the answer, one more question, can i acces a debug console or whatever it's called, i mean there is an error after first reboot and it's keept somewhere in a tex file i guess, how can i access the "guts" of this device?, since i don';t have any idea where to take it in my country, and no GSM Service was unable to help me with an answer i want to mess around with it and learn more about android
Click to expand...
Click to collapse
I guess it can be accesed somehow, but never researched enough. On hte developemnt subforum are a few post discussing somethin similar to this, perhaps their op can help you out
It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
iBolski said:
It appears a lot of people have had this issue where the imei is wiped after flashing back via the TOT method. Not sure about KDZ method, but I wanted to use the TOT method since it's apparently a valid release, so it can take any of the OTAs as they come.
How come this is never identified in the instructions? I would think that would be a very important piece of information. Just curious.
I never backed it up. I do have the original IMEI number from the box, the receipt plus on the barcode sticker in the battery compartment.
I guess I'll have to see how to do it manually, but I'm just curious, why isn't this a warning that something like this could happen? Or, is it because I did something wrong? I know on the first try, in the LG Flash Tool, the instructions in the Verizon forums didn't state to switch from Upgrade DL to Board DL. If I do Upgrade DL, I get the big red 2 instead of the big red 3, so I searched and saw instructions saying to go to BOARD DL instead. That seemed to fix it, but now my IMEI is all messed up with zeroes.
Any ideas as to what else I might have done that could have done this? I've flashed back to 10b twice now.
Thanks!
Click to expand...
Click to collapse
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
startswithPendswithOOH said:
I don't know why it happened during your restore, but there is a G2 IMEI restore method if you'd be willing to try it on your G3: http://www.droidviews.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
It looks like a QPST tool and an IMEI converter zip file, but nothing says "LG G2" anywhere so it may work for the G3. But I've never used it though, so if you're up for a gamble...good luck
I don't envy your situation I hope you get it fixed up and if you do please fill us in how you did it. I doubt you'll be the only one this happens to.
Click to expand...
Click to collapse
UPDATE:
First off, if you EVER lose your IMEI number, then you MUST flash back to 10B. Reason being is, anything later than 10B no longer gives you access to Modem mode which is the only way I've been able to make this work.
Recently, I was TOT flashing 10b to my phone to downgrade it from MM so I could flash a custom ROM. Once again, the IMEI got lost. But I found that QPST wasn't working anymore! I even KDZ flashed back to 48A and still, QPST wouldn't work. I tried 35B, nothing. I then went back to 10B. I don't know HOW many times I did this yesterday, but my phone was out of commission all day.
Finally, this afternoon, I found this article that I wrote up and read, and re-read what I posted below and it was step 2 that stood out to me. I noticed I couldn't find Modem mode anywhere as it was listed. But, because I saw that I flashed to 10B, I decided to try it once more. So, I TOT flashed back to 10b. I still couldn't find modem mode. Then it dawned on me. I selected "Internet Connect" and viola! There it was! Once I had that, QPST worked again and I was able reprogram my IMEI.
So, if you happen to flash anything, whether it's 10b or later, and you find that your IMEI is gone, you must flash back to 10b. QPST will not work on anything later (at least, 47/48A for sure). I've also tried 35B and it won't work. You MUST have 10b so that you can select modem mode. I was unable to get it to work on any other version.
I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
LG USB drivers
IMEI-Converter.zip [mirror link]
QPST_2.7_378.zip
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b). To do this, you need to ensure your phone is connected. Go to the notifications area and select "USB Connected". From there, select "Internet connect" and then select "Modem". You must do this or QPST will not work.
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically...
Cool. Good info to know. And congrats
Click to expand...
Click to collapse
I have the same problem of vanished imei. I was trying to write the IMEI using RF NV Manager but when I click write I get error NvManager :write to phone- unable to write NV_UE_IMEI_I to phone(parameter is write protected and thus read only).
Somebody please help to bring my phone alive.
---------- Post added at 10:47 PM ---------- Previous post was at 10:16 PM ----------
Well setting the phone USB connection mode to ethernet solved the problem .
Settings>storage>usb pc connection>internet connection>ethernet. Need to be in the 10B version to be able to do this.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Siylar said:
Thnks so much i mean so much, my imei is erased after using the LGFlashtool and imagined the worst, even i think sell it in parts, but I followed your instructions and my IMEI is back in my cell. Now my question is, did he do that was erased, now I'm in stock room 10b and want to put Lollipop, but after this experience and it scares me. at all, especially if I'm in another country and I can not take it to be repaired so easily with Verizon.
Anyway, thnks again works for me into Verizon Wirless Vs985 from México
My English was sponsored by Google translator
Click to expand...
Click to collapse
If you are not rooted yet, then you can take the OTAs all the way to LP. If you do root, you can only get to 12b. You won't be able to go to LP, so you would have to flash back to 10b again. There is a 12b KDZ somewhere that will also allow you to upgrade to LP if you want to go that route. The only thing that has me a little worried about it (and it's probably nothing) is that when you flash back to 12b stock via KDZ, it states the software is modified, but it still will take the LP OTA, so go figure! LOL!
As for the IMEI being wiped again, that shouldn't happen if you are taking the official OTAs. For me, when I did the TOT flash back to 10b, that was the first time I did it and who knows what I did. I probably did something wrong because the second time I flashed back to 10b (so I could upgrade to the official LP OTA), my IMEI wasn't wipe, so I have to think I did something wrong the first time.
In any case, taking the official OTAs should not wipe your IMEI so you should be good to go.
Worse comes to worse, if it does get wiped, just do the steps outlined above and you'll be back in business.
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
swimmerhair said:
So I had a replacement phone sent to me and this phones ieme is wiped due to a similar experience to yours. My question is, do I HAVE to use the ieme that came with my phone? Or can I use the one that is on my replacement phone right now?
Click to expand...
Click to collapse
You could use either imei as long as they are both for the same model of phone. I have 2 LG G2s. The imei on one got swapped to an imei for some other model. It sort of worked but I kept getting mobile network disconnections (on straight talk). I couldn't update software because the imei wasn't an LG G2. I didn't have a record of my imei for that phone, so I used the imei of my other Lg g2 which was inop with a cracked screen. Once I put a valid lg g2 imei on it everything worked correctly again and I could update software. Still on straight talk with no more network problems.
Awesome! I have been dealing with Big Red for a week now because their Fraud Prevention is meddling in my business. This will make things a little easier in the meantime. Thanks again! I will post and let everyone know how it goes.
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
nagi_007pk said:
Sorry for reviving an old thread but if I tot back to 10b from the xdabbeb version of 35B, will that be the way to go about it? Am I at a risk of hard brick?
Click to expand...
Click to collapse
Yes to the first question, and every time we do something with our phone that LG and Verizon don't intend for us to do with our phone we risk either soft or hard bricking.
iBolski said:
Thanks for the link. That was actually what I found and used. LOL!
In any case, it DOES work. I was able to fix it. Basically, I was able to find my IMEI on my receipt which is stored in my MyVerizon documents section of my account. But, it's also located on the label in the battery compartment, so if you no longer have your box or receipt, open up the G3 and remove the battery and you'll see the IMEI number on the sticker there.
Basically, I skipped the entire portion of the Backup and Restore EFS on LG G2 section. No reason for that since I wiped the IMEI for some reason during the restore.
Next, I followed the steps in the Restore Lost IMEI on LG G2 section as follows:
Here are the files to download:
After downloading all the files (IMEI-Converter and QPST_2.7_378.zip. Didn't install drivers as I already had them) and installing the QPST tools, I followed the directions. I didn't attempt to backup the IMEI since it's gone.
First, I put my phone into debugging mode and switched it to modem mode (on 10b)
Connected device to PC and ran QPST configuration and added the new port. Mine was already on port 41 due to the TOT restore, so Ieft it at that.
Skipped all the steps on backing up. I would do this AFTER I restored the IMEI.
Ran the C:\Program Files (x86)\qualcomm\qst\bin\RF_NV_Manager.exe program.
Went to Setting->Comport and set it to 41.
Clicked on File->Read from phone and navigated down to the 550 line which showed the IMEI was blank, which we already know is true.
Clicked on File->Read supported RF NV items.
Ran the IMEI Converter.exe (after extracting it) and typed in my IMEI number for my phone. This converts it into 9 groups of hexadecimal numbers.
In the RV_NV_Manager program, selected the 550 line and put a check mark in the hex check box.
Taking each hex value from the converter program, I entered the numbers into the 9 text boxes. The left-most set went in the first text box, and so on.
Clicked the "Write NV" button to write the values back to the phone.
Clicked File->Read from phone and verified that item number 550 contained my correct IMEI number.
Disconnected the phone from the USB cabled, rebooted and all was golden. Verified on my MyVerizon page that my phone was no longer an unsupported device anymore.
Click to expand...
Click to collapse
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Darkblaze1 said:
So I tried the steps inside of here. There was issues with it reading my phone. I am in the process of getting back to 10b so that I can try from there but I am not sure that will help. PM me for screen shots cause I can't attach yet. hxxp://tinypic.com/r/2j5o20o/9 hxxp://tinypic.com/r/2ivz7up/9 hxxp://tinypic.com/r/29ngqoy/9
Click to expand...
Click to collapse
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
thank u ................................................)(
Darkblaze1 said:
So I solved my own issue. Didn't mean to revive an old thread. I am doing kdz to 5.1 then the upgrade to 35b for stock. (Needing to keep stock for work reasons and for Airwatch Agent (unless anyone knows how to make it work on AOSP))
Click to expand...
Click to collapse
While you're on 10b, root, install twrp, and backup your efs. This will make it painless to restore your imei should you lose it again. I wish I did this the first time.
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
hamillp said:
I realize that this is an old thread but I am hoping that someone can help. I went back to 10b and, in doing so, I lost my imei. I have tried to follow the steps in this guide but I keep getting an error in step 7 when I try to read from the phone in RF NV Manager.
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
If I skip step 7, I can do all the steps until 12. When I try to write to the phone, I get the following error message.
NvManager:::writeToPhone( const string comPort) - QpstServer:::initialize - Unable to attach to the QPST server.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
iBolski said:
Make sure you are back to 10b. You cannot use the tool to fix your IMEI after 10b. It won't find the phone. I wiped my IMEI a few months ago and followed my own directions (since I'm the one that posted this lol) and completely forgot that you had to do it in 10b. I wiped my IMEI, flashed back to 47A and attempted to fix my IMEI that way. Nope. Won't work. The tool requires you to be on 10b in order to be found.
If you are on 10b, make sure you select the correct port. It SHOULD be 41 since that's what was last used when you flashed the 10B tot. Remember, you must also be booted into your phone, not in download mode. Once you hook the phone up, be sure you've selected the correct mode. My G3 has died since then so I can't remember it off the top of my head, but it SHOULD be in here explaining how to get to that mode. I think it's Modem mode.
Then hook up the phone and the software should find it and allow you to fix your IMEI number.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I am on 10b. I did use port 41. I was in modem mode. I even tried to do it in ethernet mode as well but that didn't work. It shows an unknown phone connected in the QPST configuration tool. It shows com 41 and that it is enabled. Everytime I get to a step where it has to interact with the phone, however, I get an error.
Anyone know what this error means:
NvManager::getNvItemsFromPHone (const String comPort) - QpstServer::sendSyncImpl - Bad response from phone (DM Packet commants 19 - 24)
More importantly, anyone know how to fix it?
Its been a long slog but ive got the os - I thought id open a new thread. I cant seem to register on the phone network. Its not the sim as ive tried another on (another provider) and that's the same and its also been a problem across all (even the stock images) that ive tried. Ive read on another thread is there a folder that I could have formatted which holds network or radio information....?
Just a thought....
Cheers.
ok - I believe its something to do with me imei number being forgotten....found a tool called the ARIZA patch but for some reason my cm13 build isn't rooted. Ive installed superuser but I still don't get root access (needed for ARIZA to work) I assumed the cm13 build would already be rooted....and idea's - I'm probably missing something...
Edit: just found the root slider - ariza patch doesn't work though - error is "phone not proper"
ComfySofa said:
ok - I believe its something to do with me imei number being forgotten....found a tool called the ARIZA patch but for some reason my cm13 build isn't rooted. Ive installed superuser but I still don't get root access (needed for ARIZA to work) I assumed the cm13 build would already be rooted....and idea's - I'm probably missing something...
Edit: just found the root slider - ariza patch doesn't work though - error is "phone not proper"
Click to expand...
Click to collapse
You could try this guide
Yep - looks like that's what happened - my imei number currently is that....well, at least I know now how to get it to a custom rom so ill have to reflash back to stock first - thanks for the link, that's a great help....ill report back in a bit...thanks again.
Nope - no luck so far....but that's definitely the problem.....lost the imei....ive never had the issue before - ive flashed mine loads of times (Note 3) and never had a problem so I never thought to back it up....if anyone has any other option I can try that'd be great....
Cheers
Ive followed the walkthrough but its not 100% clear - I might run through it a few times....
Supersu does not work on CM13, yet.
You need to turn on developer options in settings.
Well, all the stuff ive tried so far hasn't worked....I think id be looking at a manual entry (the imei is under the phone) so will try to find something along those lines....
I did try going back to a stock rom but seemed fruitless. ive gone back to cm13 as it seems the system is more open (obviously). It looks like the imei changer programs will work if xposed framework is installed....which I'm currently trying to work out how to do....easier said than done...
I think I'm done - I cant see any way of getting the imei back on there....think the phone has had it....my first loss...the xposed framework does not support the s2's architecture (that I can see)
ComfySofa said:
I think I'm done - I cant see any way of getting the imei back on there....think the phone has had it....my first loss...the xposed framework does not support the s2's architecture (that I can see)
Click to expand...
Click to collapse
I had a similar problem when I switched from ICS to JB, tree years ago. My phone would not register on any network no matter the SIM I put in (I tried 3 different operators). The only way I could solve it was with an apk called "Galaxy S2 Sim Unlock" - I had to work with that a little but after a little headache I could solve the problem. Since then, everything is ok - I can register on any network. My personal lesson from that experience is: "Never do a Factory Reset when upgrading Android (eg. ICS to JB, JB to KK, KK to LP and so on)." But that's only my experience. Now I'm on MM 6.0.1 (Cyanogen 13).
Ok- ill go take a look now....thanks for the link - I was hoping that someone could offer (something like this) so ive got another way of tackling it...cheers.
Edit - just gone looking and I cant see an app with the exact description....do you have the authors name (to narrow it down a little??)
Just to add this phone wasn't actually sim locked in the first place...are you saying that the side affect of using the sim unlocking software will insert the imei back in??
ComfySofa said:
Just to add this phone wasn't actually sim locked in the first place...are you saying that the side affect of using the sim unlocking software will insert the imei back in??
Click to expand...
Click to collapse
I bought my phone unlocked in 2011 - brand new, official release, so on.
I rooted it right away and started experimenting, installed tons of unofficial/official ROMs, playing with kernels, tweaking and everything, upgrading as soon as a new unofficial version would show up, from Stock Android 2.3.3 to... to X ... to Y... up to MM 6.0.1 (CM13) now.
I had few bricks over the time but I solved them in few hours to two days. But this problem with network registering was the longest of all and the scariest - it happened as I described it in the previous post. My understanding on that time (as I remember) was that the Factory Reset wiped my EFS.
That (Galaxy S2 Sim Unlock) apk gave me few codes I could use. Below is a note I made on those days (pretty confusing for me now, but it might help you):
-- Introducing "SIM network unlock PIN" didn't help me. I restart the phone and when it asked me the "SIM network unlock PIN", I introduced first the "Unfreeze code" but the network didn't unblock and then I introduced "SIM network unlock PIN" and the network unblocked."
As I searched now on Google Play I could not find "Galaxy S2 Sim Unlock" anymore. There is something called "GalaxSim Unlock" (by Spocky) - updated on december 2015, with support for Android 6.0.
Strange as mine I believe is the same as yours....unlocked generic phone. Ive not had any messages atall regarding "sim unlock" - my issue is theres a dummy imei in there - that's it although ill go and look now....any more information you have would be great...
Its the little things that help sometimes....I couldn't get the partitioning done atall then petrolcan mentioned a user and his script...then from that little bit of info I had a flashable zip that did everything for me...so everything helps.
I'm just not sure on the correlation between the sim unlock software and the imei missing....
ComfySofa said:
I'm just not sure on the correlation between the sim unlock software and the imei missing....
Click to expand...
Click to collapse
Again, I'm not a specialist, but If I remember right, the EFS has to do with the IMEI, and on that time I have lost my EFS, and, I guess, my IMEI....
My S2 was usable (apks, games, wifi...) but not as a phone (for calling and receiving calls & SMS).
Or, you may want to try finding some ways of restoring EFS/IMEI....
yes, the efs folder holds the file which the imei is in (a bin file) but from what I read if you remove the efs folder completely the os will generate a new one....once you've got a new file then effectively you "should" be able to inject the imei into that thus renabling your phone (and therein lies the problem - getting the imeil back in) - yes, mines the same....everything works bar the phone access to the network...
ComfySofa said:
... inject the imei into that thus renabling your phone (and therein lies the problem - getting the imeil back in) .....
Click to expand...
Click to collapse
Just guessing: Maybe "GalaxySim Unlock" injects the IMEI??? Check the description on Google Play:
"Detects errors like lost imei / serial in nv_data caused by third party apps"
You can give it a try with the free version - see what it founds on your phone.
I did try it....just gave me an nv_data error....nothing more than that...
ComfySofa said:
I did try it....just gave me an nv_data error....nothing more than that...
Click to expand...
Click to collapse
I'll check about that tomorrow as I found few threads on XDA and I have to go now.... Hopefully you'll be "up and running" by the time I come back!
Heh - I hope so but I doubt it - spent about 5 hours Friday night, a good 12 yesterday and 12 the day before....any information you have would be great! thanks very much.
After looking around I think my best bet is the NV-items reader writer v1.0. but, I cant get it connected to the phone.....anyone got any clues on that one?? once connected it looks like you can edit the nv file and add the imei back in....