[Q] Unable to use T-mobile Network since restoring from network suspension. - T-Mobile Samsung Galaxy Note II

Due to error on my part I believed my phone to be lost or stolen. To safeguard my self I used android device manager to remote wipe my phone. I did find my phone and of course it wiped the phone when I turned it back on. At the time I was running a recent Pac-Man rom and since restoring I'm unable to connect to my network. I've used odin to flash a stock rom with root access but no matter what I've wiped or reset I am simply stuck with no cell service. Any ideas or solutions would be greatly appreciated. Thank you for your time

Have you reported the phone as lost/stolen to T-Mobile? (Has someone else? No offense, but I'm covering my bases should your story be full of it.)
PAC-man ROMs normally don't contain any modems and attempting to flash an incorrect modem through Odin fails before any real harm is done.
This eliminates most possibilities of you having messed up the NV items or IMEI; and the Google Android Device Manager doesn't go further than user data to the best of my knowledge.

I actually left it at work and forgot where I left it. Yes I did report it lost or stolen but also had them un-suspend my line. I also remember possibly switching my external memory with my internal memory and when the device manager wiped my phone it wiped both storage's. Thank you for responding. Any leads on where to start to restore service to my phone?

Sounds like they black listed the imei which renders the phone useless. I would call them again to all them if the black list has been lifted.

Also yes call them and ask. If they blocked the phone as stolen then you'll probably need a new sim or the likes.
Thats what customer service is for, to answer your questions. "I reported my phone stolen, but then I found it, now it doesnt work."
Hopefully its as simple as that.

Related

[Q] EFS Problem, need help, input from someone in the know!!!

Okay, I have spent hours upon hours searching the subject and it becomes a bit hard to find a correct procedure as there are tons of hearsay and perhaps singular examples because no one really seems to fully grasp the concept of the issue. So I guess different fixes work for different people.
But here is my issue:
I have a Wind T889V. Was working fine, done lots of ROM ranges, big geek, ETC.
Well, I made a mistake and I flashed T889UVBMD1 Radio. For whatever reason I flashed it since thanks to so many ROMs flashed I forgot that I have a T889V and not a T889.
So that killed my radio. No 3G, no data, IMEI and Baseband, Mobile Network type say "unknown." I tried flashing proper radio immediately after and my phone WOULD bootup but then would reboot about 3-5 minutes into it. The reboot cycle was so short it would hardly let me do anything with it.
Then I read that booting up to an early version of stock might bring IMEI info back. Did not work. In fact, my phone boots up minutes after being being turn on unless I flash the T889UVBMD1 Radio. So I think I am stuck with it. T889V radios I have tried boots the phone up sometimes and sometimes it does not, or it cycles right at the Samsung screen.
Yes, I did a EFS backup when I first rooted. However the process only g=created a IMG file which I kept safe. Which is 20 megs in size. However, when I try to open it with a 7.Zip to look inside it appears to be empty!! I have done a restore multiple times and nothing happens. Even though the process seems to go without errors.
I check the EFS folder on my phone as it is still in there. However I do not see any .bin files. And under IMEI, there is only one file:
mps_cod.dat which when open only has the words GLW in it. That is it. So needless to say, that is not the way it should be.
I have tried to install T889VVLALJ4 (which is the original ROM through CWM) and it soft loops, even though members have said that it has magically saved their phone it sounds to me like perhaps in those cases the EFS folder still had the data and the flashing of the rom simply just rediscovered the info.
I have been reading about a member who was able to inject the IMEI info the folder but I have not been able to get in touch with him or find the exact procedure how it was done.
My last resort would be to try to restore to original, soft looping and all and take it back to the service provider see what they say.
Thoughts? And Thank you.
Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Okay.
For those in the same issue as me, the problem with trying to solve it KIES is that it will look to see if your phone is factory everything. If you are like me, and you go the FACTORY ROM/RESET route then your phone will reboot every 30 seconds to every 2 minutes. So KIES will never have time to recognize your phone, assuming that your phone boots at all.
Then if you go back to the issue I had... which was to put the T889 Modem which stops your phone from rooting, then KIES will tell you the phone is not suitable for an update. So there goes your option.
The best way for the time being is to use the AWS QCN (Google this) route. Which enables the AWS on your phone and allows you to at least to connect to your provider. As of this writing and three days of doing work, I have found a fix, that sort of fixes the phone. I have tested with a few people and they hear some background noise on Wind. So it is not a full fix, but it is a round about way to have your phone sort of back.
The biggest issue I have found after doing in-depth search on this issue and most so-called fixes is that most users have no bloody clue what the issue is so for some it is easier to fix than for others and as such you get a lot of false negative fixes.
The fact is I have found so far is that there is no 100% that I have found.
You first need to know if the issue is with the Modem, your IMEI getting fudged, your EFS folder messing up and whether once it got fudged whether your EFS info still remains on your phone. Different fixes fix different issues.

N7105: No ROMs work properly (IMEI null or 0.0B storage)

Hi!
I bought a used Galaxy Note 2 LTE (N7105) a few weeks ago. The device ran CyanogenMod when I bought it, but I installed WanamLite V1.3 which worked like a charm. When the 4.3 update for the Nordics appeared on SamMobile I flashed it using Odin, thinking it should work with my Nordic (Swedish) SIM card. Being quite used to flashing ROMs from recovery I stupidly mistook the "NAND erase all" for being the equivalent of "Wipe Data / Factory reset" in revovery, and ticked it.
I suspect my problems are all related to this, and I definitely know that it was a stupid box to tick, so please don't waste both yours and my time by telling me that.
The problem:
When the 4.3 stock ROM booted, I had no network and the SIM was not detected. If I type *#06# the IMEI is null and if I type *#1234# in the dialer there is no CP entry. Baseband and IMEI are Unknown in "About Device". I have tried flashing several modems, including the one in the ROM, nothing seems to help.
I flashed CWM using Odin and installed WanamLite (Android 4.1) again. Here the IMEI is intact and I can get mobile data, but the device says the internal storage is 0.0B. Applications still install fine, it's just the storage of other files that won't work at all. Since the storage works on the 4.3 stock ROM I suspect the error could be related to the new mount point for storage in Android since 4.2 (/data/media/0). I made an EFS backup in a number of different ways, and backed up the nv_data info.
I then flashed the Lion ROM, which is based on the 4.3 stock ROM, and the issues of the original one persisted (no IMEI, device does not detect SIM). Storage is still fine. Doesn't matter whether I come from WanamLite or stock ROM, tried both to no avail.
Tried CyanogenMod 10.1 stable and 10.2 nightlies according to instructions - 10.1 boots properly but has no baseband/IMEI and no storage, 10.2 gets stuck at CM boot logo.
I have tried restoring EFS partition using several different methods, but none of them do any difference. When I open the Qualcomm utility to restore nv_data it does not recognize the device properly.
I have spent two weeks Googling, searching XDA and other sites, and I have read through every thread I found without finding any solution. Has anybody managed to solve the null IMEI / baseband issue or the 0.0b storage issue, or will I have to choose between phone calls and storage?
The 4.3 partition for usb storage has moved to new partition.
If u r saying with wanam evrything is ok except the storage problem, have u tried to use super mega wipe script?
Wipe evrything on ur usb storage, make it clean, then flash back wanam.
It might works. Because if u never format ur usb storage, the partition of ur internal storage is still to storage/emulated/0, whereby wanam 4.1.2 was pointing to storage only.
Good luck.
Sent from the corner of this rounded earth (N7105 v4.3, powered by LionROM)
You have a damaged NV-Ram on the 7105 this can show as 0 bytes of internal storage
loss of IMEI / Baseband as unkown
the NV-Ram backup you made on most models was a good thing but your phone now cannot be connected to to
restore the NV-Backup
2 options are open for you
1/. get a replacement mainboard from an online auction site
2/. send the item to a Samsung Service Center
when the 7105 model gets to the point you are at it is a tough one to get back and there isnt much online to help you
sorry to bring bad news
fibreoptix said:
You have a damaged NV-Ram on the 7105 this can show as 0 bytes of internal storage
loss of IMEI / Baseband as unkown
the NV-Ram backup you made on most models was a good thing but your phone now cannot be connected to to
restore the NV-Backup
2 options are open for you
1/. get a replacement mainboard from an online auction site
2/. send the item to a Samsung Service Center
when the 7105 model gets to the point you are at it is a tough one to get back and there isnt much online to help you
sorry to bring bad news
Click to expand...
Click to collapse
I can't more agree with you. NV_Data on N7105 is the most important, and so far I tried to backup and restore is only 1 tool can do it, and that one as I mentioned on other thread, I tried only on 4.1.2. Have never tried it on 4.3 ROM, and I don't intend to try yet
@Akerskuuug :
So, if really you can't get back your nv_data, the best is you bring it back to Samsung, and I think they will charge you for that, as normally only those who like to "modified" ROM phone will have this type of problem.
But if as you said, you can get it back with Wanamlite (your IMEI / nv_data), most probably you do like what I post earlier might work. Not 100% guarantee, but might work. Because on your earlier post, you mention everything is ok, only the storage is unable to be read properly (this one is due to change of usb storage folder on 4.3 ROM).
Sent from the corner of this rounded earth.
fibreoptix said:
You have a damaged NV-Ram on the 7105 this can show as 0 bytes of internal storage
loss of IMEI / Baseband as unkown
the NV-Ram backup you made on most models was a good thing but your phone now cannot be connected to to
restore the NV-Backup
2 options are open for you
1/. get a replacement mainboard from an online auction site
2/. send the item to a Samsung Service Center
when the 7105 model gets to the point you are at it is a tough one to get back and there isnt much online to help you
sorry to bring bad news
Click to expand...
Click to collapse
The thing is that, except for on CM10.2, the problem is that either the storage is 0 or the IMEI is null - on 4.1 ROMs the IMEI is intact and correct, modem is working properly.
I still suspect that I'm going to have to send the phone to a service center, though, if nothing else just to get some peace of mind without having to do any more work.
antique_sonic said:
I can't more agree with you. NV_Data on N7105 is the most important, and so far I tried to backup and restore is only 1 tool can do it, and that one as I mentioned on other thread, I tried only on 4.1.2. Have never tried it on 4.3 ROM, and I don't intend to try yet
@Akerskuuug :
So, if really you can't get back your nv_data, the best is you bring it back to Samsung, and I think they will charge you for that, as normally only those who like to "modified" ROM phone will have this type of problem.
But if as you said, you can get it back with Wanamlite (your IMEI / nv_data), most probably you do like what I post earlier might work. Not 100% guarantee, but might work. Because on your earlier post, you mention everything is ok, only the storage is unable to be read properly (this one is due to change of usb storage folder on 4.3 ROM).
Sent from the corner of this rounded earth.
Click to expand...
Click to collapse
I tried the mega wipe and super wipe, but unfortunately they didn't work. I strongly suspect I'm going to have to send the phone to Samsung or just use it without the possibility to save other things than applications to the internal storage. I have a micro SD card, and the Note is just my secondary phone.
Going to check for service centers near me, thank you for your help!

I'm an idiot and I got some crazy malware. Help please.

OK so I smashed my s5, am a UDP verizon guy and hooked on the open bootloader, so i searched far and wide for another one with the 15 chipset...which I didn't find but I found a note 4 with it.
I bought it and unlocked it and loaded on a rom I loved. (5.0.1 og5). Well...no sense lying here...I was trying to do some less than kosher things regarding my ex's Facebook account with it. In the process I wasn't smart enough to cross check MD5s (a precaution I learned all too well) and opened an app that has me baffled.
It basically hijacked admin on my device completely. No Antivirus program can touch it, though many detect it. "Unknown sources" in my security folder is stuck permanently enabled, and I can't take over as admin on my own brand new note4.
I have tried flashing twrp and titanium backups to no avail, and also tried the safe stock og5 firmware through Odin but it never completes. I am stuck. I have logcat records and all the tools I would think might help, but I can't get rid of it...it seems to have used root and embedded itself into every facet of the device.
I am willing and ready to do anything including a full unroot and stock rom, I just don't want a locked update. Can anyone help me please?
As of now, no roms break it, only the stubborn malware CM app tries to get rid of it, but only identifies it as "suspicious file". My user admin and unknown sources are both locked, and a gaggle of bizarre log events happen constantly, forcing my device into crazy lag. As soon as it happened I received a couple random number-link blank text messages, but I never opened them. I don't have the numbers saved as I've flashed the phone like 30 times since trying to rid myself of this. Aside from the lag and locked unknown sources and admin, and an inability to clear trusted credentials, the phone seems to run normally, though I am scared to use it to log on to pretty much anything. The malware didn't come from a text, but from an app that I knowingly permitted thinking it was something else and I feel like a moron for it. It doesn't seem to have a name. It installed as an untitled app and I couldn't delete it with the root system app deleter, because it put a green bar over the check box in the app. I got rid of it with titanium, but to no avail. It still lurks.
Thanks in advance, and let me know of any screens hits or logs or tests I can provide to help.
At that point, I would recommend using Samsung's Smart Switch for PC program to do an emergency firmware upgrade & initialization. This will download a full copy of the stock firmware for the device (including a few bits that you won't find in stock firmwares available for download through sites like SamMobile) and will erase everything on the device and restore your phone to stock firmware.
If you are in the US and have a Best Buy nearby, you can see if one of their Samsung reps can perform a factory recovery using their SMART tool (which will do the same thing that Smart Switch's emergency firmware initialization will). Officially, rooted devices are not supported and they may rightfully refuse to do this, but it's worth asking if you don't have a computer to use for Smart Switch or don't want to wait.
You will need to redo the developer conversion, but that's the only thing I can think of that will definitely completely restore your phone to stock and eliminate all traces of whatever you installed.
thanks. that solved my problem and got it back to stock, rid of the malware completely. unfortunately, when i tried to return to the rom i had used, everything fell apart for me :/.

Sprint galaxy s3 e:failed to mount /es (invalid argument)

Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here
issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?
Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again
update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..

lost phone how secure is the s9?

i lost my phone late Tuesday night, i called it and rang a few times tried calling it again a few minutes later and went to answer machine,
either battery went or someone turned it of, ive checked on find my phone and it was last synced about 1 yesterday so guessing it was turned on briefly then , been no activity on it since, so its looking like the likelihood someones found and keeping it, so how secure is it? it has a 5 digit pin code, finger print and face to unlock the phone and i have stuff stored in secure folder as well which includes a picture of series of words to get into my crypto wallet.
For every android security is pretty much the same,
if someone don't know your password they can enter the phone by doing hard reset via the recovery,
but if you're rooted or using custom rom, then all they need to do is full wipe from twrp, which is not included Internal Storage and flash other custom rom and they might get into your personal data on your phone's storage.
also I believe if you enable device manager as administrator before, you have an option to reset your phone on Find My Device
i never did root this phone i wanted to keep the credit card option, device manager is on and im keeping my eye on find my phone but not wiped it in the hope it might come back to me yet, ive got a year and a half of pictures on there and hoping the phones secure enough to keep people accessing the info.
on find my phone it still hasnt synced since the 29th 1.08pm so still unsure to put the wipe message on there,
I want to get a new sim card today so the sim in the old one will deactivate , do you know if this happens will find my phone still work? thanks
There are 2 possibilities for the fact that your phone still hasn't synced since the 29th.
- It could be the phone is still hasn't turned on
- Or it could be that your phone is already reset from the recovery, if this happen then you don't have any control of your phone anymore
also I remember that you can lock your phone from find my device, I don't really know what will happen to your phone is it still be able to access the recovery to reset the phone or not.

Categories

Resources