Hi guys
So my battery had decided to swell a few days ago in my Note 2 GT-N7100, and suddenly my phone lost network and couple of days later, didn't go beyond the logo screen. I got the new battery (needed to tell my mother that it was NOT my fault that the phone died on me, and she insisted I use the old battery till the day phone dies so couldn't get the new battery before since I had no money and they are pricey stuff) but the problem persisted so I turned to recovery mode, which claimed that my /efs file was missing and could not be loaded. I did not have the slightest clue such a thing existed before this. Needless to say, /efs was NOT backed up. This was my first smartphone too, so I had no clue.
I did manage to get my phone running after installing the firmware by Odin and using CWRM to get to root and disabling factory mode, but it seems the IMEI and Serial number are still not right. The IMEI number starts with generic 0049XXXXXXXXXX and the Serial number is 4df7e1b53a26cfcd, which is not same to the S/N given behind the back of my battery. I really need help salvaging this; I want to avoid going to Samsung Customer Care since, well as I mentioned before, my mother has allergy on spending on anything which has 'Tech' written over it, and this will lead to me getting stuck with this phone without being able to really use it. Is there any way out? Please help!
Edit: I tried to flash a modem into it, and right now /efs is an empty folder and the IMEI and Serial number situation is unchanged. My mind is on a merry go round. Seriously need help here!!!!!
Related
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.
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.
So I got really cocky with my phone and thought I was a lot more tech savvy than I am... I rooted my LG G3 which went well, I changed a couple of settings in the build.prop to mess around with it, downloaded some mods, etc...
Then it all went down hill when I tried to flash a rom onto it that would get xposed working with Lolipop. The rom immediately bricked my phone, every time I boot it, factory reset, try pretty much anything it just shows a black screen with the words "[###] Fastboot Mode Started" on it. After reading countless forums I've found that I can flash the stock LG G3 D850 firmware onto the phone from the Download Mode/Firmware Update screen plugged into my PC to erase everyhing, but I can't even do that because I changed the model number in build.prop to the Galaxy s6 so a few apps had more up to date features. Now the phone wont accept the LG G3 stock firmware rom because it thinks its a Galaxy s6 but I can't change the build.prop back to D850 because I can't get into a bricked phone. Just wondering if ya'll had any suggestions.
Thanks guys and gals
Same Here. . Almost
So basically I have the same problem . . Well almost, so basically I had been messing with my build.prop and everything was going just fine the whole time through out. So after I was done modding pretty much, well I was testing out different settings I can input to change my Spring LS990 to work with the T-mobile carrier, including having to enter into a "secret menu" through the phone dial, but ended up bricking it. So after I was done therefore, I went and copy-paste the backup I made of the build.prop, straight into /system folder. After applying confirmations and letting it do it's job, I gave it a reboot for the copy to take effect and that's where I ran into the problem of having a boot loop on the LG logo screen and being able only to turn it off by removing the battery. Also I'm able to enter recovery, use ADB (kinda), but keep getting denied access/permission/privileges to use other functions in ADB except the "adb sideload" command, but even that results in mounting failure and signature+foot errors. Yes, I've been to numerous posts and forums, searching everywhere for info on my own repair and ended up here post this. Really appreciate your help, am willing to pay considerable amount for repair if extremely necessary and would also like to end up getting the phone to work with T-mobile if possible.
Thank you,
Blessings,
Dave.
Good evening you absolute legends!
After quietly reading along since 2013 and flashing a few phones over the years thanks to you, I'm now at a point where I can't think of anything to do with my problem.
So I bought my dad a used G960F for his birthday and wanted to install Lineage OS just as I did with mine a couple months ago. To make things short, in the meantime all ROMs I used where deleted, so I did the same procedure but with other ROMs, and well ... bricked the phone. After a week or so I finally got it working (didnt know about Samsungs bootloader hierarchy and couldn't flash a ROM with a lower BL), just to find out now that in the process the IMEI got deleted completely.
After seeing too many shady websites this is what I tried so far:
Flashing with a Pit-File + NAND Erase and Re-Partiton
Flashing stock rom (tried both Android 9 and Android 10)
Erasing everything or only parts of the efs/ folder, even though I only found that applied to other Samsung phones than mine
One ROM I tried back when the phone was bricked was from _alexndr, and I found one post where a user also lost IMEI after using it but got it back when he installed the ROM again. This one I will try out now.
So I have one G960F working but with empty IMEI. Not a bunch of zeros, its simply empty. I know one correct IMEI, since its printed on the OEM box three times. (Don't know why they dont print both numbers on the box....). I've seen a bunch of semi-(il)legal Apps that let you change the IMEI, but I dont feel like getting into that and it wouldn't help me with the second IMEI.
(Additionally, I have my own G960F completely working, if it helpes in any way.)
Does any of you have any ideas left or has experience with such a problem?
Either way, thanks for taking your time with me and everybody else!
Cheers Anthony
Hi guys!
I solved my problem and maybe my way can help some of you.
As I understood from _alexndr's thread [1] is that you can not only not go down a BL-Version when flashing, but you can't also go down in the CSC version. But while doing the first thing resolves in an error while flashing, the second one simply works but therefore can't detect the IMEI etc sometimes.
My solution in the end was to flash _alendr's kerlel, force my CSC module (maybe this parts isn't necessary) while flashing and and then installing the BL he provided [2].
Even though this thread stayed empty, I still wanna thank all of you for keeping up so much work!
[1] https://forum.xda-developers.com/t/...vbase-v7-4-encryption-support-may-09.3764822/
[2] https://forum.xda-developers.com/t/...support-may-09.3764822/page-151#post-84984391
Hello. If anyone has the opportunity and desire, help, please, solve the problem.
About 3 years ago, a friend bought this phone in a Vodaphone salon.
Once at work, he was discharged to zero and turned off. After trying to charge, I went into the bootloop. The logo appeared and the phone turned off and so on endlessly. He ditched it and bought a new one.
The phone lay until he decided to revive it in order to give it to the child.
They took it to the service, they just looked at the model and said that they would not even take it.
On some Indonesian resource, I found a global firmware and instructions. Everything was done, the phone started up, it was updated by air to 10 android. But with the firmware, the nvram file went away and imei.
If it is possible to make a full backup of the firmware for a flash drive with nvram or just a backup of nvram.bin, then I would be grateful.
Nowhere on 6750 mt I can not find a file database for recovering nvram and imei
Tried it using MAUI meta - it does not load the file, the modem does not detect it correctly, asks for a local db file. Have a change to relatives from the box. The main thing is that at least some program should determine it correctly.
Hello - it's not my upload, but I found the ROM here.