Related
I have an ATT Galaxy S3, running cyanogenmod 10.0 (10.0.0-datt), installed via clockworkmod recovery (ROM Manager). Everything works beautifully except that I can neither send nor receive text messages.
Now before you yell at me, yes, I checked the other threads, and I'm aware of the wiki entry over at cyanogenmod's site (can't post the URL on account of newness). I did try to update the SMSC number. I get update errors with the bare number and the PDU number. The only option that appears to work is to use the standard ATT smsc number in quotes. That doesn't yield an update error, but on refresh, I see "+13123149810",145 . I have no idea where the trailing comma and 145 come from. They just show up. Don't know if it means anything.
Anyway, I have also tried various combinations of removing the SIM/rebooting etc, though I have not yet tried a full reset. I have also checked the APN stuff, and it appears sound.
Here is another wrinkle. I did at one time run a CM nightly to 4.2, so I have that '0' directory on my SDCard. I haven't observed it to cause a problem otherwise, but...
So the symptom is that if I send a text, it appears to send but never arrives at the receiver's phone. If I send an MMS, it flat refuses to send, saying the service is not activated on the network, which is odd since I have an unlimited plan.
I'm now at a loss, but I don't want to go back to stock, or to do another full reset. Any ideas?
I've run cm10 for a bit it was whatever, but I've never run into these issues your having and I use cwm too. The only thing I can think of right now is maybe something to do with rom manager its just a crappy app its buggy and always gave me problems so I never ever use it! Try downloading it directly from cm and wipe everything and flash again
Sent from my SGH-I747M using xda premium
thatsupnow said:
I've run cm10 for a bit it was whatever, but I've never run into these issues your having and I use cwm too. The only thing I can think of right now is maybe something to do with rom manager its just a crappy app its buggy and always gave me problems so I never ever use it! Try downloading it directly from cm and wipe everything and flash again
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Well I tried the full deal again. I booted to CWM Recovery and did the wipe/reset, then loaded, respectively, CM10 and GApps. I did not load everything back on the phone or otherwise restore data. No themed Messenger. Still the same deal. Text messages go nowhere and I get 'service not activated on network' for MMS. No difference.
Do I need to get a new SIM? Would that help? Is there a way to debug what's happening when I try to send a text? I have ADB and the whole SDK and am reasonably comfortable at the command line. I just don't have the standard XDA tribal knowledge.
jgoodleaf said:
Do I need to get a new SIM?
Click to expand...
Click to collapse
No, that won't really do you any good, UNLESS your sim wasn't provided with the device when you got it.
I would say to ODIN back to Stock, and see if things change back to what they should be. While in stock go ahead and remove that pesky folder you found.
Again see if that changes things.
If things have returned to normal, make your nandroid and then reflash the ROM you were using and see if things are still the same or if you have the ability to send again. If still the same then it's an issue with the ROM, probably in the APN.
MasterDecker said:
No, that won't really do you any good, UNLESS your sim wasn't provided with the device when you got it.
I would say to ODIN back to Stock, and see if things change back to what they should be. While in stock go ahead and remove that pesky folder you found.
Again see if that changes things.
If things have returned to normal, make your nandroid and then reflash the ROM you were using and see if things are still the same or if you have the ability to send again. If still the same then it's an issue with the ROM, probably in the APN.
Click to expand...
Click to collapse
I think I'd have tried ODIN by now, thinking along the same lines, except that I don't have any Windows machines in the house, or any immediate access. I have VMWare, but don't trust that where flashing is concerned. I've been trying to figure out if I could use Heimdall, but that looks like a non-starter at the moment. Maybe I'll have to see if I can borrow someone's Windows computer... And just when I thought I was rid of it.
So, over the past, well I don't know how long... ever since I started using my galaxy s III back in July, I have seen these threads pop up, and more so recently (to be quite honest this is a disheartening thing to see, and can easily be prevented, but we'll get into that) that say "hAlp ma service is teh failll I kant haz no moAr IMEI!!!" -__-
What is lacking in most of these threads, situations, occurrences, whatever you wanna call them - user error, lack of responsibility on this forum of the developers around here (myself included) to instruct people from step 1... BACK UP YOUR EFS PARTITION! There are many ways to do this, terminal emulator, the andromizer app, some handy tool I have seen floating around here where you connect your device to your computer, open it up, so on so forth. Everybody should be doing this. Everyone. But that is hardly the issue, nor the point of this thread - (pointing fingers).
Last night after seeing ANOTHER one of these threads where somebody had lost service to their device, costing them a good amount of $$$ now, it dawned on me that maybe, just maybe, the issue isn't that the partition is actually being corrupted, but maybe there is a problem occurring where the device doesn't actually read it - some type of failure or registry during booting. All of these instances have had one thing in common - the IMEI mysteriously disappearing and no service issue happen after boot up. And not necessarily after doing any 1 particular thing... granted yes, flashing a ROM, but that should have nothing to do with your IMEI not registering on a network unless said ROM has some kind of issue/bug whatever where it is simply not displaying such information in the status bar (unlikely, but who knows at this point, right?)....
Again, back to last night... I was curious to see if I could duplicate this issue that a user reported where they had flashed a kernel and their IMEI had disappeared. So, I picked some random kernel from asylum that carried the same 7500 device ID that my currently running kernel has of his (running asylumcore)...
Downloaded it, flashed it through cwm, booted up, BOOM! No IMEI. No service. Interesting. Didn't restore my backup of the efs partition which I had made a month ago, for obvious reasons stated - wanted to see if the partition was indeed corrupted, or if there was simply some kind of disk read error.
So I booted back into cwm, flashed back to my other kernel, booted up, and wouldn't you know it, IMEI and service was restored. So what does this mean... this means that the IMEI isn't, hasn't, never was, "lost" per say - there is simply an issue causing it not to be read properly.
So to troubleshoot this issue properly, I need people to pipe in who have "lost" (not really lost) their IMEI's. This is what I need to know:
what version of recovery were you using?
what ROM and kernel were you running right before this happened? Need the revision, android build (jelly bean, AOSP, whatever), everything, details please.
what did you flash or do to the device right before it was gone?
were you able to fix it? - a backup, reboot, reverted back to previous firmware? what?
This will help quite a bit. So far I have been able to duplicate a "lost" IMEI on my own device 4 times in a row, and been able to get it back without any kind of back up. I need some more information from some of you, however, to say 100% what is causing the issue.
Also, since we are already here. I will simply say that developers around here need to take more responsibility in their little "disclaimers"... seriously. If we all know that this is an issue, then we should be instructing people in our ROM threads to take measures to prevent this kind of thing from happening. Especially since at the moment it appears to be random, and especially since there are plenty of methods to be prepared for it. Just sayin.
Something as simple as this:
"Warning, certain users have an anomalous issue of losing their cell signal and having their IMEI not registering. It is highly recommended that if you intend on flashing ANYTHING to your device, that you read threads regarding this issue and furthermore that you make a backup of your EFS partition on your device to prevent permanent cell signal failure - in the event this anomaly happens to you, you will not be without a working device and out $600. Developers are looking into this issue and working on a fix, but as of yet, there is not definite fix. MAKE A BACKUP!"
Then how about a link to that thread for the andromizer app that is not stickied, not looked at ever? Not too hard to do. And would have been nice for those who were suddenly caught off guard by their device turning into a paperweight. Here is the link:
http://forum.xda-developers.com/showthread.php?t=1972757
I am working on a write up right now to fix IMEI issues.
Sticky this. Excellent work and ingenuity. Im subscribing to this thread.
Sent from my SGH-T889 using Tapatalk 2
From what I've gathered by reading here, lost IMEI issues due to kernel or ROM flashing can indeed be resolved by flashing back to whatever was working in the first place.
In the case of modem cross-flashing however, things aren't as cut and dry. I pulled an NV items backup (with NV_reader_writer) from my phone prior to restoring it to service with a backup from a working phone, and NV item 550 was returned as inactive, along with a bunch of others that shouldn't have been.
Very interesting write up here. I did actually had this happend to me on my GS3, that I purchased new from T-Mobile back in November. The first night I had it, my flashaholic itch kicked in. Before I knew it I was in the process of rooting the GS3....but all hell broke loose once I rooted. The Root kit at the time had a earlier version of CWM and it caused me to lose the IMEI# when flashing a CM10 rom.
So I did the whole process of reinjecting the IMEI# bla bla bla, I was able to retrieve data and IMEI. No issues what so ever after that. I even just in case did the whole QPST tool of backing up the IMEI# for just in case purposes.
Well a week ago, I was planning a installing a theme over the current Wicked Rom on my GS3. So I did the steps going into recovery, Wipe the caches and went to install the theme when I realized that out of my stupidness I never downloaded the theme. So I just did a simple reboot from TWRP 2.3.3.2 I believe if not it was 2.3.3.1. And once the my phone booted back to my home screen I had zero data.
So at that point I was utterly confused in what had happened. All I did was wipe the caches, I had no clue that the caches have ties with the EFS partion. Still till this day I have no Idea what happened.
I want to try other roms but I just so scared for this to happen to me again. What should I do to stop from having this happening to me again?
Thanks
So I knew the first thing to do is another reboot just to see if something might of hiccuped during the booting up process. But once it booted up again and back to the home screen still no data. Not even Edge, Had the Cancel symbol over my bars on the status bar. So I knew to check the IMEI# under phone status and sure enough it was not there just displayed Zero.
I knew I had a back up of the IMEI# so I tried to just reinject it, Since I knew it was basically a painless process. After doing so, Still no data, even though the IMEI# is showing CORRECTLY under phone status it still would not kick in even Edge. Eventually Edge would connect but it would be like Dial Up speeds.
So I Odin'd back to a Root66 stock rom and checked the status of the data and still no go. Everything is still showing under phone status at this point, so no loss of the IMEI# but no data at all.
So I Odin'd back to the T-Mobile Stock Firmware and same results and just for kicks I tried to reinject it once again and still nothing.
Ended up conducting the triangle away process, got it back to Samsung Official everything and even the Modified Status was set back to Normal status. Everything was back to stock at this point, Kernel, Modem, Rom, Bootloader, just everything was stock as if I just bought it. Still no data.
Conclusion I did a warranty exchange, got the new GS3 fully working ofcourse, gave it to the wife and bought me the N2.
Now I am terrified to do anything to this phone. I'm currently running MyRom Rev V2 and have a nandroid of the Stock firmware.
Sounds like the issue may have something to do with recoveries
same here !
My galaxy note 2 . I root the phone and put room T889_N7105ZHALJ4 it work fine for awhile but It have robot voice when calling .
and I try to boot another rom PhoeniX.ROM.v4.0.by.tamirda-signed this is big problem .
This rom make phone unable to connect network . after that I try to flash back old rom . It same thing . Make phone able to connect network .
My phone is now dead . only connect wifi . Try to call customer service . And now they have to send me another phone .
No idea after what 4 years of hacking android phones not once had that happened. Now I feel like a complete amateur because of that.
I'm literally terrified to do any thing else with my phone and I'm not at all that satisfied with the choice of rom I've selected either but it'll do till there is an answer for all the random issues people having with this generation of "Galaxy" series phones.
Sent from my SGH-T889 using Tapatalk 2
Im having the same issues with no service. I have a t889 and a original sim card which was cut to microsim form. I had no trouble getting service. I rooted successfully and still had service. At this point I performed nandroid backup and efs backup and attempted to flash jedi x. As soon as I did this I lost service...it has bars but no voice calls and no 4g. My IMEI still shows however. I ve tried everything from stock factory restore through ODIN to restoring efs, flashing stock radios/kernels restoring nandroid still cant get service, defintely need some step by step advice on how to get back my service. I feel like I followed all the appropriate steps to flash the room.
Sent from my SGH-T889 using xda app-developers app
amullins said:
Im having the same issues with no service. I have a t889 and a original sim card which was cut to microsim form. I had no trouble getting service. I rooted successfully and still had service. At this point I performed nandroid backup and efs backup and attempted to flash jedi x. As soon as I did this I lost service...it has bars but no voice calls and no 4g. My IMEI still shows however. I ve tried everything from stock factory restore through ODIN to restoring efs, flashing stock radios/kernels restoring nandroid still cant get service, defintely need some step by step advice on how to get back my service. I feel like I followed all the appropriate steps to flash the room.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Same problem I had I had imie showing but I keep having instability connection. So what I did is claim insurance and got my new note 2. I belive it must ben defect of the phone because I have no issue with my new phone running jedx9
Sent from my SGH-T889 using xda app-developers app
I paid full price for my phone so.. no insurance, and even if I could what if I experience the same problem with another Note 2? Then I just lost more money and time. I followed all steps correctly for T889, I feel like this should be reversable if I have nandroid backup and EFS backup. Hopefully developers can help us out with this to figure why this issue is occuring in some Note 2's and not in others.
Yes please trt figure out how to fix this issue yes I also notice people are hav8ng lost service or instability data due to this problem with flashing. I encounter this problem I and lucky fof me tmobile sent me a new phone due to claim it was defective.
Sent from my SGH-T889 using xda app-developers app
I can't believe all these pple are saying help me help me.
The OP has been kind enough to risk his note 2 and lose imei intentionally to try to find the cause and a fix.
He clearly says, to do this I need everyone's help who's lost imei (I need as much detail as possible. Rom, kernal, modem, version of jelly bean, version of twrp. Flash anything before lose? Mods,tweaks, themes, scripts if so what?)
That's all OP is asking for and not one person has been specific
And I don't think OP has replied to anyone. Who knows probably gave up trying to find a fix.
Haven't given up. Just don't have enough data to conclude what the issue is. All I know for certain is that when it is "lost" it isn't really lost, just not registering the info or reading it.
But yeah, not a whole lot of input.
Hey guys just fyi to let you know what I found with this issue. Just giving my input.
Well it looks like my imei is populating but my note 2 no longer gets service. Im probably going to warranty it so I can get service again I spent all of my weekend trying to fix. I think this issue may be related to something within the modem or radio being flash incorrectly and somehow corrupting the efs files. I searched forums about efs corruption and I think maybe it has something to do with a nv_data file missing? Not sure if that applies for sgn2 but I couldnt find or maybe I dont know WHERE to find it in root explorer. Maybe if we compare a working sgn2's efs file with a NON WORKING sgn2's efs file maybe that would help? I followed the steps in the t889 root guide step by step... and then as soon as I flashed Jedi X9 through cwm recovery BAAM...service was gone.
I tried reflashing, I tried reflashing stock modem\kernel and reverting back to stock via odin but no go.I did notice it was able to connect to tmobile for one to two sec because it would actually sync the time and date after turning on for the first time. But never again after that. My Imei and bars are showing ..but when I make a call it says "not registered on network" and no 4g either. I think this may be because the rom had included a different radio not sure which one defintely wasnt the canada ver. Flashing this rom somehow made my phone stop receiving service...Does restoring efs backup a guaranteed fix the lost imei/ service issues? Can flashing using earlier version of odin cause an issue? I used 1.84. Everything passed successfully however. Just throwing ideas to help. I definitely want to try to avoid the issue when get my note 2 back from repair.
Before I had this issue I had the latest stock firmware from tmobile the 889VALL4 modem and kernel 4.1.1 jellybean. No problem rooting the phone and still had service after root with chainfire method.
My guess is the phone doesnt have true root towards the efs/modem/nv levels with the current custom recoveries available... its like twrp and cwm arent messing with those files but when flashing certain roms those files are being mishandled.... therefore creating the restore ineptitude
Ultimately I have only used well known roms and kernals that others have tested without hitches (for all my android devices) like CM or Jedi... those "third party" roms arent trustworthy in my mind as to some devs "open source" often translates into "cut and paste" which can be problematic to say the least
With the GNII, i have used CWM (not sure on build but I can find out) and TWRP (only 2.3.3.2 never 2.3.2 or whatever was before)... and like I said "well tested roms/kernals" so cf_auto_root, then Teshxx lk8 stock, then Teshxx ll4 stock, then Jedi 9 with saber_7+, then Jedi Master 9 with Saber 10.2, and finally switched to the Perseus kernal 3.0.36 alpha 32...
Never any issues with connectivity, imei, anything...
Hope this helps and more importantly you find what is lacking and get the info to CWM and TWRP for updating (id say let the rom devs know too but by bettering the Custom recoveries, roms like all other devices, wont affect those files
Sent from my SGH-T889 using xda app-developers app
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
I will add no roms were ever flashed through CWM... only had it because I was use to it and new to TWRP... my Bro in law made the suggestion and it looks like its the best advise he could have given me to this point... that and my overall patience to not jump the flash gun... again I cant stress this enough, only use well tested roms/kernals/etc... I know CWM came by surprise as we all have grown to love it but its not perfect and even other recoveries were there before (RA, etc) and it wont be the last (TWRP)
Sent from my SGH-T889 using xda app-developers app
i got mine working
here is what i had... i lost my note and got a replacement.. then i found my note in my girls car.. no service i insert my sim no service my imei was blacklisted. so i googled ways to change my imei. no dice the terminal emulator way didnt work. i said i got a paper weight and i can **** with it so i did.. got in the service mode *#197328640# and toyed with everything in there.. lost all the network setting and signal and in the
umts /debugmode /common/ rebuild nv it said it will delete my efs part. so i did haha lost my imei bootloader serial number and everything that makes my note a phone. a few days later i was at it again but this time i was going to fix it hoorah! so read and read bout efs part and googled some more and more.. and found this..
http://forum.xda-developers.com/showthread.php?t=1801997
what i did was backed up my new notes efs/ nv files and used them in my other note.. now i have 2 notes with same serial number and imei i gave one to my wife and both are working like new.. but having 2 phones on same family plan with same ime/sderial numberi just wont cut it. so i decided to change the imei and foud this....
http://forum.xda-developers.com/showthread.php?t=1804123
the old imei is bad and wont work so i need a different one.. lucky i had a old samsung behold2 laying around the house .. turned it *#06# a new imei!! yay now i dont have a clone phone but more of Frankenstein monster.. cool huh when i log in to my tmo account it says samsung behold on the other line,,
^lol ....
maktucali said:
here is what i had... i lost my note and got a replacement.. then i found my note in my girls car.. no service i insert my sim no service my imei was blacklisted. so i googled ways to change my imei. no dice the terminal emulator way didnt work. i said i got a paper weight and i can **** with it so i did.. got in the service mode *#197328640# and toyed with everything in there.. lost all the network setting and signal and in the
umts /debugmode /common/ rebuild nv it said it will delete my efs part. so i did haha lost my imei bootloader serial number and everything that makes my note a phone. a few days later i was at it again but this time i was going to fix it hoorah! so read and read bout efs part and googled some more and more.. and found this..
http://forum.xda-developers.com/showthread.php?t=1801997
what i did was backed up my new notes efs/ nv files and used them in my other note.. now i have 2 notes with same serial number and imei i gave one to my wife and both are working like new.. but having 2 phones on same family plan with same ime/sderial numberi just wont cut it. so i decided to change the imei and foud this....
http://forum.xda-developers.com/showthread.php?t=1804123
the old imei is bad and wont work so i need a different one.. lucky i had a old samsung behold2 laying around the house .. turned it *#06# a new imei!! yay now i dont have a clone phone but more of Frankenstein monster.. cool huh when i log in to my tmo account it says samsung behold on the other line,,
Ok so what effects does the frankenstein have? Everthing works fine?? You should send the devs a copy of your beast for autopsy!
Anything you have to do differently trying to do this for the GNII?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
I "lost" IMEI lastnight, Just got the phone rooted with Exynosabuse. Then i Flashed CF-Auto root with mobile odin. Then I flashed Note2Core 7105 with Mobile odin.
When i woke up in the morning I noticed no signal, Baseband is unknown and so is IMIE. And I didn't back up EFS. :crying:
I booted into recovery and wiped still the same. I also re flashed the kernel.
Downloading stock rom hoping that will work :fingers-crossed: This is a N7105T ( I know this is a T-mobile thread)
Follow this guy he fix his lost imei and baseband I dunno it might work
http://forum.xda-developers.com/showthread.php?t=2145967
Nailed it!!!!!!!!! My 4g is back again
Sent from my SGH-T889 using xda app-developers app
I recently lost my IMEI and didn't have a backup. Stupid move on my part. Now I know I need to do a backup before flashing ROMs. Anyways, I just got off the phone with AT&T and I will have a replacement here in 2-3 days. As I'm sure most of you know I'll have 10 days to send my old one back. Before I return it to stock and send it back I am willing to help in the research of this problem and a potential solution. I have done a lot of searching on this forum and I haven't found a solid solution. If anyone has some theories they would like to try you have a few days to let me know and I'll see if I can be of help.
Here is the history of the phone as best I can remember:
-Bought brand new December 7, 2012
-Updated to Jelly Bean 4.1.1 through Kies. No noticeable problems
-Rooted with Odin v3.04 Team Epic Root from Recovery with CWM v5.0.4 and Super User I kept the stock ROM for awhile before flashing anything else (Made a Nandroid of this ROM) No noticeable problems.
-Flashed Drew Garen's Serenity 1.2 No noticeable problems
-Flashed Pure Motive's Galaxy Mod Rls 14.1 No noticeable problems
-Flashed Pure Motive's Galaxy Mod Rls15 (This is where the problems began) Did a full wipe (data, cache, dalvik) like I always did. Rebooted after flash and noticed that my service sucked and my data wouldn't connect. I checked the APN's and they were wrong. Changed the APN's and the data would connect but I still had poor service. The phone wouldn't even make a call. It took me a little while to figure out that the IMEI was missing. It just read 0. After some searching I found a method of injecting the IMEI: http://forum.xda-developers.com/showthread.php?t=1804117 I used this method and put the original IMEI back in. Of course that didn't fix my data or poor service issues.
-Then I tried Peoplearmy's method: http://forum.xda-developers.com/showthread.php?t=1801997 Actually I only did the make a backup part with QPST. I couldn't use the QCN Generator app because I only had Windows XP and the app requires Windows 7.
-I flashed my Nandroid backup. No help.
-Flashed Stock Jelly Bean I747UCDLK3. No help.
-Rooted the phone again, using the same method as above.
-At this point I became desperate (stupid) and tried a method for the GT-i9300: http://forum.xda-developers.com/showthread.php?p=30773406 This definitely didn't work and now I lost my serial number.
-Last night: Finally got access to a Windows 7 computer. Tried The SGS3 QCN Generator app. This time it worked and made a QCN. I injected it into the phone. No help. The QCN data I used was from after I lost IMEI and had manually put it in. I'm not sure if this is part of the problem of why it didn't work or not. The way I understood things it was supposed to repair the other parts of the QCN data. Someone please correct me if I'm wrong.
-I actually made an EFS backup on Galaxy Mod Rls14.1 using the Aroma installer. From what I've read this wouldn't necessarily help anyways because it doesn't contain all of the data needed to do a complete backup which is kind of beside the point because it's in tar format not in zip and it's a tiny file. 58 Bytes.
-I have installed Root Explorer and looked in the EFS folder and it doesn't contain any nv_data files.
I have already installed Triangle Away and cleared my flash counter.
So, if anybody who actually knows what they're doing (cause I obviously don't) would like to help, especially if my situation can be used to fix/prevent this from happening, and wants to use me and my I747 as a Guinea Pig let me know.
-Right as I was getting ready to post this I scrolled through settings>about device>status, and my correct Serial Number was back. What the ....? The only thing I've done to the phone is toggle airplane mode a few times, turn it off and on a few times, used wifi to get online, pulled the battery, booted up in CWM recovery. I haven't flashed anything to the phone. This is odd. Any help or feedback would be greatly appreciated.
Huh? There's a perfectly good solution and a fix. Not sure why itnwouldnt work for you. It works for everyone else.
http://forum.xda-developers.com/showthread.php?t=1801997
I tried that. Exactly step by step. I still don't have reliable data. It either doesn't connect or stays on Edge. Also the service sucks. Everyone else around me will have 3-4 bars and I'll have 1.
Opie Knievel said:
I tried that. Exactly step by step. I still don't have reliable data. It either doesn't connect or stays on Edge. Also the service sucks. Everyone else around me will have 3-4 bars and I'll have 1.
Click to expand...
Click to collapse
Changing your modem can fix that.
I was thinking of that but I read on here somewhere that someone had tried it without results. I am willing to try it though. Which modem would you recommend? I already have i747UCLG1 modem on my memory card, ready to flash.
Opie Knievel said:
I was thinking of that but I read on here somewhere that someone had tried it without results. I am willing to try it though. Which modem would you recommend? I already have i747UCLG1 modem on my memory card, ready to flash.
Click to expand...
Click to collapse
I can't really recommend a modem as they act completely different with your area/phone.
The only suggestion I can make is to use one from your carrier (AT&T). But it doesn't mean another one won't work better.
OK. I'll give that a shot and post the results in a few minutes.
Yeah I've used the IMEI injection tool to full effect. I have full data back. Using any other method to try to fix it would be just plain stupid. There is nothing else to test.
BAM1789 said:
Yeah I've used the IMEI injection tool to full effect. I have full data back. Using any other method to try to fix it would be just plain stupid. There is nothing else to test.
Click to expand...
Click to collapse
Did you get all the missing files back in your EFS folder?
Maybe I messed up somewhere. I don't have my full data or service back yet. I'm trying a few different modems to see what that does. It really doesn't matter if I get this fixed or not. I've already got a replacement on the way. I was just hoping that it could help somebody else out and I kinda like fixing things. The 2 modems I've tried so far aren't having any better results. I've got a couple more to try.
Would it be worth a try to redo the entire QPST, QCN Generator process?
I received my new Galaxy S3 today. That was Fast!! Lol Anyways, my research proved to be right. There's more going on than meets the eye when you loose and restore your IMEI. The original phone lost signal and would hardly ever connect to HSPA, only UMTS. The replacement phone automatically connected to HSPA as soon as I had it setup. I read on here somewhere that a lot of people were having the same problem when they re-injected their IMEI. I used the SGS3 QCN GEnerator app and still couldn't get good data connection. Actually I hardly had any connection at all. It would hardly pic up incoming calls and texts were sometimes an hour or more behind coming in. Flashing different modems didn't help either.
I'm going to do the proper backups this time before doing any flashing and if I have any more problems of this nature I'll have a good backup to fall back on.
Hi all,
I've recently rooted my phone as per mrRobinson's thread and used TWRP to flash Liquidsmooth 2.9 my phone. It worked beautifully for a night and then a day later, while I was receiving/typing a text, the phone went into ~2 cycles of reboot loop. Later during the day, while I was reading on the browser I would get random reboots after the phone seemingly freezes.
I tried reflashing the ROM after wiping everything (except for the internal storage) a few times.
Has anyone had this problem or experienced a similar situation? I tried searching a bit and reading the Liquidsmooth 2.9 thread but nothing about random reboots seems to occur... yet.
Thanks guys.
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Sure said:
Experiencing reboots as well, after upgrading from 2.8 to 2.9. Primarily only happens when plugging in my phone to charge. This wasn't happening when I was on 2.8.
Perhaps this would be a more appropriate thread for these entries?
http://forum.xda-developers.com/showthread.php?t=2346973
Phone: Samsung Galaxy S III SGH-i747
Previous ROM: Liquid-JB-v2.8-OFFICIAL-d2att.zip
Current ROM: Liquid-JB-v2.9-OFFICIAL-d2att.zip
Click to expand...
Click to collapse
Unfortunately when I was posting this thread I was (and still am) under the 10 post limit, lol. I've decided to just stick to CM10 for now. I might try to reflash 2.9 again. If that doesn't work, I might try different settings for the CPU (eg. on demand? mine was set to interactive). Additionally, I think the liquid team is moving towards 4.3 so I'm not even sure if this is going to matter to them...
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
_alp1ne said:
This didn't happen to me, but I upgraded from 2.3. Got a little behind on the releases lol. Also, which kernel are you using? With liquidsmooth the stock kernels don't like my phone so i have to flash another...
Click to expand...
Click to collapse
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
duketerm said:
Wait, are you saying the stock kernel that came with the liquidsmooth roms? Are you also using an S3? Lastly, which kernel are you using now (and did you change the CPU/performance settings)?
Click to expand...
Click to collapse
Well i meant the kernel that is automatically installed when you flash Liquidsmooth. I am using the ATT S3 at the moment. The kernel that came with liquidsmooth always caused random reboots and similar problems for me. Now i use the BMS kernel (here) and have no more problems. I didnt really mess with the CPU settings on the liquidsmooth kernel, just set max frequency to 1242mHz for some extra battery life. With the BMS kernel, I have it undervolted -105mV and again set max frequency to 1242mHz.
Sorry for the confusion.
equhmiduff
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
atteya.mohamed said:
Hey guys
Same Problem here, but first of all am not a developer and i know nothing about it i installed font installer to change font after rooting and bricked my XT925 and after long looong search i flashed Liquidsmooth 2.8 and 2.9 and the constantly reboots always happening i heard it is because of RAM and running apps, so i installed RAM booster app and problem still exist suddenyl launcher freezes and device reboots
Tried ROMs : CM10.2 - PAC Man
Device : Droid Razr HD
Current ROM : Liquid 2.9
Launcher Used : TSF Shell - Next Launcher
Bootloader : Unlocked
Recovery : oudhs recovery
Click to expand...
Click to collapse
Yes, I get the same problem: the phone freezes (eg. on browser, texting, etc.) and then reboots. I haven't tried reflashing it and changing CPU settings... Have you?
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
_alp1ne said:
I don't know what to tell you guys. I went ahead and flashed every version of liquidsmooth from 2.5 to 2.9 everyday the past week and used them for about a day each, and i have not had any problems. No reboots, crashes. Not all s3's are created equal i guess...
sorry i couldn't be of help
Click to expand...
Click to collapse
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
possible recovery issues--
duketerm said:
Hmm, the only thing I can think of now is maybe the type of recovery we use? I used TWRP 2.6.0.0. What about you?
Click to expand...
Click to collapse
I used clockworkmod, forgot which version. I will test different recoveries when I get home.
EDIT: I flashed it on cwm v6.0.3.1, which is not the latest version of cwm.
Sent from my SGH-I747 using xda app-developers app
Will test twrp 2.6 in a few minutes..... Will report back later if I can.
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
_alp1ne said:
well..... Tried to flash liquid smooth today. Just finished unbricking my device a few minutes ago. Soft brick due to an error flashing. Reinjected IMEI and restored must everything.... Will reflash via CWM later.
Click to expand...
Click to collapse
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
duketerm said:
Thanks for doing all of this. I have another question for you since you've told me you had to reinject IMEI... How did you back up your IMEI? I've been looking around but only the basic samsung thing worked for me since I'm already on CM10.
I tried to use this thread: http://forum.xda-developers.com/showthread.php?t=1804117 but I'm unsure how to run that gscript... Thanks for your help man.
Click to expand...
Click to collapse
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
_alp1ne said:
The thread you listed there confused me also... To use that USSD code you need to be on stock. I will try the gscript thing mentioned and tell you what happens. I also explained below what I did to backup.
Not sure what you mean by basic backup... but i will try explain everything anyway.
Method 1 -
This uses samsung's built-in NVRAM backup/restore function. I won't go into detail, but type in the following in a terminal-
Code:
su
reboot nvbackup
It will then boot into the bootloader, with some text telling you its copying the NVDATA to two partitions - fsg and backup .
to restore, type in
Code:
su
reboot nvrestore
DO NOT use the restore command without backing up first!! DOING SO WILL WIPE YOUR IMEI!!!
More Methods-
Method 2 -
.The devs of SynergyROM developed this - just download at the bottom of this post and flash in recovery.
This will generate some zips in sdcard/SynergyROM/backup. To restore, flash the one that begins with "keybackup".
-
There is a third way, called QPST. I would not use this unless you have balls of steel, and also it requires stock rom. Couldn't find anything about this, so i guess you could google it if interested.
Click to expand...
Click to collapse
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
duketerm said:
Yeah, sorry. What I meant, was I used Samsung's backup--was that enough for you? Just worried about flashing another rom. Interestingly from what I read, the new versions of the IMEI format (3?) isn't supposed to cause problems--I guess that was wrong?
Additionally, the SynergyROM didn't work for me because apparently my bootloader is locked? I'm on AT&T and I thought AT&T had unlocked bootloaders?
Click to expand...
Click to collapse
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
_alp1ne said:
Samsung's backup was enough for me, but I did the other stuff just to be safe. AT&T's bootloaders do come unlocked, otherwise you wouldn't be on CM10 From the errors it gave me in recovery that im assuming you got also said something about unlocked EFS. The EFS is where the NVItems are located, and it might require an unlocked device, as in you can use any carrier's SIM. I will unlock my GS3 (or atleast try) right now.
I will report back on that later.
EDIT: I need to go to the store right now, so it might be a while.
Click to expand...
Click to collapse
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
duketerm said:
Wait, so were you able to flash SynergyROM? And you did so without unlocking your device?
Thanks!
Click to expand...
Click to collapse
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
_alp1ne said:
Oh dear.
I believe there is some miscommunication
The bootloader has always been unlocked. I'm not talking about the actual ROM (synergyROM), I'm talking about the IMEI backup thing they created.
Now, when I said unlock my phone, I DID NOT mean the bootloader, I meant carrier unlocking it, so I can use any sim from any carrier. I'll try to screenshot it later.
Sorry for the confusion duke.
Click to expand...
Click to collapse
Sorry, I think I'm being vague and not specific.
I'm wondering which IMEI back up steps you took. From what you've told me, it appears that you were able to run the Samsung backup, as well as the other ones (including SynergyROM backup?"). If you were able to run the SynergyROM backup, how did you do it? I was unable to run it because I got an error message saying that something was "locked" so I'm not sure how you got around to successfully flashing the SynergyROM.
Thanks for all the help.
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Hi, you certainly have a challenge there. It sounds like you need to restore both the partitions and the stock OS.
If the phone is a 32 GB model, please see the whole thread at http://forum.xda-developers.com/sprint-galaxy-s6/help/operating-smg920p-t3263325
There is a PIT file linked at post 16, instructions for using it at post 22. Also a link for the latest stock TAR file.
Again, this would be for 32 GB model, but you want to flash first the PIT and then the TAR.
I think I may have done that already too but I'll look again once in home and see if maybe I did it in the wrong order. Thanks for the quick reply friend. ?
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
jbowman21 said:
Well i did as instructed but Baseband is still unknown and it is still rebooting over and over :/
Click to expand...
Click to collapse
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
elesbb said:
If he messed up the efs partition, like it's empty, without a backup. I'm pretty sure the phone is done.
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
1619415 said:
I recommend he brings it to Sprint, after they "diagnose" it and declear its broken they should be able to replace it. Just make sure its as close to stock as possible that way it does not seem rooted.
Click to expand...
Click to collapse
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
elesbb said:
That is about the only option left. There are other options to restore the efs (pretty much rebuild it from scratch) but that is not something an every day user can do. I had an efs issue on my S4. I was tinkering with things I shouldn't have, forget exactly what I was doing, it was on T-Mobile so I think I was trying to remove the data cap (was on prepaid). Was pretty much in the same boat as OP but was able to completely from scratch rebuild the stuff that belongs in the efs directory. Some stuff I never restored but didn't seem to affect the device.
Click to expand...
Click to collapse
Huh, if you remember, write a guide that way you can help people.
1619415 said:
Huh, if you remember, write a guide that way you can help people.
Click to expand...
Click to collapse
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
elesbb said:
This was many many years ago. What saved me was the fact that Notepad++ keeps a copy of the file you have open even when you close the program. I just had to remember what things needed to be reverted back and the edits undone. I guess I didn't really rebuild it from scratch lol.
Click to expand...
Click to collapse
Lol
1619415 said:
Lol
Click to expand...
Click to collapse
Yeah sadly I have no idea how the efs is populated. The second instance I get a new phone, dd is done on the efs partition and created into a .img file.
jbowman21 said:
So my friends Boss' son tried to be all "l33t h4x3r" and mess with his S6(sm-g920p). First he ruined his EFS section of the phone, the Baseband is Unknown, no IMEI number, Software Version is Unknown, and his radio wasn't working. I think he then tried to do some crazy **** in ODIN, "No Clue he doesn't remember". Well i've never ran into a constant reboot issue with any Android phones i've owned. I've had bootloops but this is throwing me for a loop. I've tried:
Loading TWRP wiping everything and trying a Custom ROM
Using Odin to Recover back to Stock
Honestly im not sure whats up anymore or if his phone is even fixable at this time.
Link to Probs: http5://youtu.be/QVLgYF_7tGU
Click to expand...
Click to collapse
Koop's firmware didn't work with my phone either. This version of it fixed mine for some reason. Try flashing it to yours
mediafire.com/download/c55xaeb7geq0i2d/G920PVPU3BOJ7_G920PSPT3BOJ7_SPR.zip
Now i got same issue i accidently restored efs and ah man ive tried every thing it reboots after 2 or 3 mins no matter what rom back up i have and i have efs and radio with all my back ups ive restored it also no luck. Guess im going to the sprint store tomorrow even after i flashed stock 6.0.1 i can get to about half way through wifi setup before it reboots no matter what 2-3 minutes phone reboots unless in twrp
Still no luck becareful and dont try to restore efs i suppose in twrp. Your phone may never stop rebooting ive flashed 2 different 6.0.1 builds one was the revo other was from sammobil both @koop1955 has them PB6 6.0.1 odin doesnt fix this.
YOYOYO
Well wtf or omg it completely died left it for a day. Now its working so far it hasnt rebooted in 30 mins LOL but dude sucks going to a phone with kitkat after using marshmallow and one of the fastest phones made for awhile. I did pull the sim card out and try it in a old boost maybe that reset something idk its working though.My problems were Rebooting constantly after 2-3 mins no matter what rom i had even stock.
---------- Post added at 12:31 PM ---------- Previous post was at 12:11 PM ----------
Saafir said:
Backed up my EFS before ever even rooting. Stuck that bad boy in Dropbox for safety. *pats self on back*
Last one of these topics I seen, end result was JTAG.
Click to expand...
Click to collapse
BEcareful if u restore that efs. i backed up too but once in twrp. Now all i did was check restore efs by accident just tried restoring a renegade rom system,boot, and data. Tell you what i wont be rushing through crap and am fine with stock for awhile. Probably will still take the replacement when it comes its white the black one i got is too blue.
Saafir said:
I've got a raw partition backup as well as one through TWRP. If you check md5/sha hashes for data integrity, and only install software instances specific to your device, aside from manually monkeyin around
Hey needless to say im researching full partition backups did you use a app by wanam partitions back up and restore? Or just simple adb commands. Last used adb on a moto e 2nd with success on unlocking. Once i got a new harddrive haven't needed it.
Click to expand...
Click to collapse
Theres similar issues happening on sprint note 5s as well and has a couple threads currently speaking about this problem. Strange strange. It happened to me after updating to mm and then rooting.
Well i did try the note rom right before and when i did hit restore efs it after wiping system data boot from moar MM rom phone rebooted for days then after few resets and odin flashes i let it die then a day later it worked.
Correct but have always preferred the 925p roms.
Well i helped another with the rebooting issue on any rom.
He tried everything then but let it die after battery died plug it in and bingo his worked to
IF CONSTANT REBOOTING.
LET THE BATTERY COMPLETLY DRAIN.
AFTER FLASHING STOCK.