Hello!
My issue is that every so often (once every 20-30 minutes or so) my cell service just completely drops to absolute nothing, the drawer saying "NO SERVICE" at the bottom. Then about 20-30 seconds later, the connection is re-established and everything works fine again. Rinse and repeat. This has been going on for weeks now.
It seems very similar to an issue I noticed some other forum members had when d2att ROM builds were unified into d2lte. The fix was to Odin back to the stock 4.3 TW firmware and then start the custom ROM install process over again. However, I've already done this a few times and nothing has worked for me yet. CM, PA, Omni, Nameless, etc., I tried them all with no luck. The issue even happens on stock TW after I get through the Odin flashing process.
I recently upgraded to the newest UCUFNE4 bootloader/modem combo, thinking that a modem upgrade would do the trick. No dice. And now it sucks because I can't go back to 4.3 without bricking my phone (unless there's a 4.4 stock firmware for Odin floating around somewhere?).
My carrier is AT&T (well, it's actually an MVNO called StraightTalk), and I've contacted StraightTalk multiple times asking what might be going on. They seem to think it's a local cell tower malfunctioning. But I've waited and waited and am now assuming they simply don't know.
So I'm basically out of ideas. Help me, XDA. You're my only hope. Movie reference aside.
Is there perhaps a log I can provide or tool/app I can run that shows what I'm experiencing in more detail?
Thanks!
i have seen some custom rom OP instructions mention if having wifi issues to flash a custom kernel. dont know if that would help. BUT remember to double check compatibility and do a backup.
err on the side of kindness
Thanks for the reply.
The Wi-Fi is running great. It's only the cell radio that's causing problems.
Also, I'm usually running BMS kernel, but I've tried many variations and they all experience the same problem.
reflash ne4 modem? double check apn settings?
err on the side of kindness
Re-flashed NE4 modem.
APN settings look good, and I /do/ get LTE coverage. When the connection isn't cut out, of course.
Still no luck.
If its happening on every rom including every stock build youve tried its most likely hardware or the carrier. Ive heard of similar issues recently where we narrowed it down to those two as well. Im starting to think it may be straight talk.... No good way of knowing that im aware of though.
thank you mr huckleberry. my thimble of ideas was o-u-t. :thumbup:
err on the side of kindness
Thanks guys.
I might as well ask: is there any way to Odin back to the stock 4.4 firmware? I'm pretty sure only OTA is officially available, but has anyone perhaps made an unofficial .tar.md5? Seeing as how I can't go back to 4.3...
enewman17 has a stock 4.4.2(NE4) thread. maybe that?
http://forum.xda-developers.com/showthread.php?t=2788357
err on the side of kindness
I saw that thread/post earlier. But they look like recovery zips to me, not Odin .tar/.tar.md5.
my bad. yup, zips. will keep searching
err on the side of kindness
---------- Post added at 09:09 AM ---------- Previous post was at 08:55 AM ----------
what about... http://sammobile.com/firmwares
err on the side of kindness
I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.
crap.:banghead:
err on the side of kindness
JJohnson1988 said:
I did find this post:
http://forum.xda-developers.com/showthread.php?p=53756950
But I'm not trusting an arbitrary post I found when I haven't seen anything similar from DocHoliday or anyone else working on the 4.4 release.
EDIT: The SamMobile site only has old firmwares available.
Click to expand...
Click to collapse
I must have missed that. No idea if itll work though. I did try to make an Odin package a while back but couldnt get it to work. Ive got a couple more ideas to try when ive got the time to focus on it, but i know that doesn't help now.
Its not for Odin, but i do have the firmware in a recovery flashable zip. Combined with enewman17's rom, it would almost accomplish the same thing. I think he has the stock recovery in that thread too which would be the last piece needed to get full stock.
Both threads are in the development section.
Well. Good news, guys. I finally solved the problem, mere hours after I became frustrated enough to start a post on XDA.
I ended up flashing to stock 4.4 via the recovery method, hoping to see a difference. Start using the phone for a few minutes, then the cell radio drops out as always. Wonderful.
So then I started thinking about what's common between all the ROM installs I've done. Was there something being left behind that wasn't being cleared properly? That's when I developed a crazy idea.
I remember reading about how there's a special area that's normally inaccessible where information like the phone's IMEI is stored. This is the /efs partition. Now, my IMEI was listed correctly in the phone information, but I decided to tinker around with some things as I was pretty desperate. I eventually got to the debug service menu by dialing *#27663368378# (I looked at a big list of codes online) and looked at what options I had.
The solution? Apparently an NV rebuild! I found this option in the service menu under UMTS >> COMMON >> NV REBUILD. I thought it was a long shot, but the longstanding problem I've had instantly fixed itself after a reboot!
So now my question is: HOW did the /efs partition become "corrupted" in the first place? And how was the phone actually able to make calls correctly and get working LTE data with the downside of service dropouts every so often? Shouldn't it... you know, either work or not work at all?
Anyways, thanks for the help guys. Looks like I don't need to send a nasty letter to StraightTalk after all (awww!).
glad to here you got it fixed. i wouldnt have a clue how it got corrupted, although docholiday77 might know (a WHOLE bunch smarter about this stuff than me), anyway :victory:
might want to hit doc's 'thank button'
err on the side of kindness
It may not have been the EFS partition that was the problem. Not much network related data is stored there. Much is on other partitions such as modemst1 and modemst2.
No one knows why flashing roms has the ability to mess up the NV Data. I suspect that when the system boots for the first time (after a rom flash, for example) it writes something to the NV Data and this is when things can get hosed. Thats just a theory though. Many have had problems with losing their IMEI because of this.
My theory on the IMEI is that after the new flash and boot something gets corrupted. These devices check for corruption during boot and will attempt to automatically restore from an on-device backup. The problem is the backup was never created, and it ends up restoring a null or blank value, causing the IMEI to become 0.
Something similar, but a little different may have happened here. Some data that is used by the carriers network to authenticate your device may have become corrupt or lost.
It wasnt an all or nothing type scenario because the device isnt constantly sending this info, probably only at certain times or intervals. But when it does, the network would not be able to authenticate your device and then block access, which would explain why it would happen every 20-30 minutes. Again, this is purely a theory.
The method you used to solve the problem has actually been around for a couple of years now, believe it or not! But its usually used to fix issues with GPS not being able to establish a lock. Whatever is used to authenticate for GPS, must be similar to what is used for the network in that it uses device specific info (such as the imei or s/n) to create a hash value that is then used in this process. When you chose NV Rebuild, it probably recreated these, thus fixing any issues due to the corruption of those values.
I hope all of that made sense! I am not positive that what i just wrote is 100% accurate, but it does make sense to me.
Now, i am guessing you never created the on-device backup i referred to, so this is how....super easy to do!
You do need to be running rooted stock.
Install and open Terminal Emulator and enter the following:
Code:
su
reboot nvbackup
Thats it! The device will reboot and create its backup. (Youll see blue text flash at the top, similar to when you boot recovery)
The backup is written across several partitions that are never touched by flashing, making it permanent. Flash all you want and itll remain intact unless you deliberately do something you shouldnt, or flash something not for your device.
As i stated before, every time the device boots up, it checks the NV Data for any corruption, and if detected it will auto restore from the backup. Youll never even notice anything was wrong!
Afaik, no one who has done this backup has ever lot their IMEI which is proof enough to me that it works!
SSL! Im glad you figured out a fix for your problem btw! Good work on that!
thank you mr huckleberry. never new how to backup this. guess i should read up on 'terminal emulator commands for newbs'
on it now.!:thumbup:
err on the side of kindness
You wont find the reboot nvbackup command. Its a Samsung specific one. But by all means learn more about the terminal if you can. It can help when writing scripts and troubleshooting all sorts of things!
samsung galaxy s3 i747 ?
err on the side of kindness
Related
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.
I am posting this as a new topic because I don't have enough posts to post my concern in the thread of the ROM I use.
I have been using PATB ROM for a while now without any issues. Since updating to the newest version I have run into severe issues trying to flash anything besides doing Restores. Every time I try to flash something new it fails immediately and this includes trying to flash a new recovery. I did some reading and thought I had found the answer in restoring the system to stock firmware via Odin. However after trying this a short while ago the process failed as well as soon as Odin showed Recovery in the process bar. This screwed my phone pretty bad, but I was able to Odin a new Recovery on to the phone which seems to have taken it back to functioning normally. I am still unable to flash anything and the only stuff I can do inside Odin is to put different Recovery zips on the device. But even after doing that I am unable to flash anything, and it jumps to Failed right away.
I am not much more then slightly experienced when it comes to rooting and flashing but I have never come across anything like this before. I was using Xposed Framework and I unistalled it because I thought it might be causing the issue. But still no luck. This is driving me crazy. Any help with this would be greatly appreciated because I would like to try out some new ROMs. By the way my flash count reads as only 4 when taken into download mode even though I am pretty sure I have flashed more then that; unless it only trips when completely changing ROMs which would make it a correct count. So I am hoping somebody out there has seen this before and knows how to help me get past this. Thanks to those who are able to help.
Have you tried flashing the full MK4 firmware? IIRC you can't go backwards. Try this out: http://www.mediafire.com/download/7viivd985s7cp8l/L900VPUBMK4_L900SPTBMK4_HOME.tar.zip
Use Odin 3.07. If it fails go with 3.09. Please let me know if it works or not. Your partitions may be corrupt but that's a LONG shot. Let's just stick with you're trying to downgrade and the bootloader isn't letting you
Sent from my SPH-L900 using xda app-developers app
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
dragonrider6218 said:
After pouring over countless articles, threads, and posts about the same problem I finally got it to work. I used Odin to put the newest TWRP Recovery on to the device and from there I attempted to flash a stock rooted deodexed MC2. After it failed 3 times I unchecked zip verification as a long shot and it took, flashing the stock ROM. At first I was a little concerned because of how fast it flashed but for the most part everything worked fine. My only problem after this was my baseband was stuck on lj1 which was easily remedied by flashing a modem zip. After that I was having issues with calls dropping almost instantly. I could have a full bar reception and as soon as the call connected it would drop and say I was outside of service area. Thinking back to something I read elsewhere I went into applications/phone and deleted the data (after backing it up) and now things seem to be running very nicely. So needless to say it has been a stressful couple days but diligence and studying got me where I needed to be (hopefully).
By the way no I have not gone to MK4 yet because of there not being any custom ROMs with additional features that make it worth it for me to do so. I will do so either once a custom ROM drops with the N3 air view features added and fully functional or when I purchase my Galaxy Gear. Until then I am going to run the MK4 modem which I have read improves reception and data speed. Thanks for the advice.
Mod this problem is officially solved and this thread can be closed and/or deleted.
Click to expand...
Click to collapse
If you decide to go to MK4 be sure to install Philz Cwm Recovery or your problems will start all over again
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Fingerless said:
Hey guys, long time browser, first time poster, but not a reason for celebration, alas.I come to you guys out of frustration after hours of being unable to solve my issue cruising the interwebs, and the thread title kinda says it all.
To start from the beginning, I recently delved into the rooted world by means of towelroot (kitkat 4.4.2), installed xposed framework, got the modules XBlast and XPrivacy, and you might have guessed, fiddled around with each. Everything was fine and dandy until I was having issues receiving/making calls through an app (LINE, if you know it), and so I attempted to figure out what the issue was, very much assuming XPrivacy to be the culprit. Couldn't get it to work, which is when I decided to restore my backup I made using Clockwork. Should have been nice and smooth sailing, but...
Upon having it "restored" I booted on into it, which is when I got smacked in the face; as soon as I'm booted, most, if not all, my apps are reporting that they have stopped working by a bombardment of error messages in endless succession, making just browsing the home screens almost impossible. Also with this barrage came the lack of cell service, a nice white n' slashed out circle in what should be my bars of signal. I tried again to restore my phone from my backup. Same issue, but I did notice during the recovery it made mention of something like "secure_android" missing? This sent me on my hours of head banging, turning up *possible* resolutions, which didn't work. I've tried flashing the stock bootloader, gapps, and nothing. Now, my data and apps are all still there and I can get into recovery without issue, it's just the pain of not being able to actually using any of it.
I have debugging switched on on my phone, but do not have some sort of adb app installed on it, nor could I access any market place to try. I'm not so sure I would be able to install anything on my phone given my current circumstances, anyway.
Please, if any of you out there have some idea as to what is going on, I'm all eyes (as ears on a forum don't work so well)! If there are any details I may have omitted and so on, just let me know and I'll supply it--
Thank you all so much in advance for any possible steps that may resolve this issue!
Click to expand...
Click to collapse
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
BWolf56 said:
Sounds like your backup was a downgrade (old version).
I would suggest doing a factory reset, test it. If that doesn't do it, use Odin to flash stock firmware (which can be found in the general section stickies).
Click to expand...
Click to collapse
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Fingerless said:
Thanks for responding! I did try a wipe data/factory reset via CWM, then restored from there. Didn't work. I'm not sure if there is a particular order in how it should be done such as "factory reset, reboot phone into recovery, restore" or if I should be able to get away with "factory reset, restore", the latter being what I did. I also got a hold of a bootloader file and modem base band for build I747UCUFNE4, if those would be useful in any way.
If it's of any help, I somehow got the Unofficial Omni ROM 4.4.4 to work without any issue, but not quite happy enough with the overall interface of it, yet slowly adapting having installed a touchwiz launcher just to hold me over.
I've tried locating the backup CWM created on my phone so that I could store it on my computer and generate another backup as from what I read, the unpaid version only allows you one at a time, but had no luck digging through my directories. I'm currently investigating this online nandroid backup thing to see if there's anything to it.
I've also come across some file labeled "I747UCUFNE4_Stock_Rooted_Deodex" which is a zip, but I'm reading ODIN uses tar as it's compression of choice? Does this mean I should flash this file via recovery, or? Also, the file size is a whopping 920MB or so... that normal? (Edit: this is where I found the file http://forum.xda-developers.com/showthread.php?t=2788357 which says to flash in recovery)
Thanks again for your response! I was really thinking my problem would just be glanced over.
Click to expand...
Click to collapse
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
BWolf56 said:
I meant factory reset without restoring.
But now that you're back up and running, there's no need for it (unless you flash another ROM). You could flash NE4 if you wanna get back on the official ROM but there are also tw custom ROM which you can look into (you're currently using an aosp one).
As for the 920mb, yeah.. That's Sammy at its best, bloating their ROMs.
Click to expand...
Click to collapse
You think it would be safe to do a factory reset and try to restore just the data from my recovery? Or is it possible that the data is somehow the issue with everything going wonky?
I'm very new to the ROM thing, Omni was easy to get up and running, but actually playing with a ROM was more of a last ditch effort to see if the problem would be resolved that way and give any sort of indication as to what the issue was (still haven't the sllightest). It's currently not rooted (at least according to my root checker) and the towelroot method doesn't seem to work on it. I kinda need to be rooted if I wanted to make a nandroid, I really want to make a back up of what I currently have set in case I screw the pooch trying to get things back to "normal", yet I'm afraid of overwriting my only recovery and losing whatever data is embedded, though I'm not too deeply saddened by the thought of not having chat histories and whatnot, it would just be nice to have. Perhaps you have thoughts, or anyone else out there, on the matter? I know my first step would be to at least root my current ROM, then back up, I found this as a means to root Omni (http://forum.xda-developers.com/showthread.php?t=2672160), but how do I determine whether I'm using an ARM based or x86 based device?
Good to know the file size for the stock ROM is considered normal. I didn't even consider carrier/Samsung bloat to have such a huge impact.
Thanks, yet again!
Hello XDA forum patrons, if I am out of terms for stating that I will pay for help, I apologize as I am just that desperate for concrete help and or affirmation of being screwed. I am not a new person to this forum but I made this account specifically for this problem. If I have offended anyone to this point I apologize. So if I am allowed to offer monetized reward for real results then please allow me to continue and hear my plight.
I have an AT&T Galaxy Note 2 Model - SGH-i317, while I have successfully and easily rooted and flashed custom roms for over 10 different phones, this one has ultimately made me a fool either in personal error or erroneous rom damage. So in that allow me to explain what I have done and maybe, hopefully, someone reading this can help me get my phone in a usable state as the stress of my girlfriend ( it's her phone ) is slowly killing me and this is consuming every waking hour trying to fix. #firstworldproblems
I digress.. lets jump in.
5 Days ago after realizing that the new rolled out 4.4.2 update disabled tethering and hotspot creation from 3rd party apps such as Foxfi, ( i live in an area where the only options for internet is cellular, dial-up, satellite) I became enraged and decided to root and install a rom for it so I could bypass and circumvent what I felt was crap, and or my impatience to wait for FoxFi to be updated to bypass these changes. So I backed up my rom, installed CWM and supersu 2.1 with no problems, I then installed LiquidSmooth Rom 4.4.4. with no problems everything worked fine, well almost. Silly me I had forgotten to take in account that LiquidSmooth was a very fast, clean android experience without any hint of touchwiz and pen usage.. well I hadn't really cared nor wanted those features but my girlfriend damn sure did. "How am I to take quick pen notes now?
etc... so I decided to switch to DN3 V5.2, well CWM wouldn't allow me to install so I tried Philz to no avail, so I installed TWRP and sure enough it flashed and installed fine. Well there was the problem (at least I am guessing) as DN3 V5.2 is based on 4.4.2, so as much I know with roms is you can go up but never go back... if I am wrong please correct me, So after booting up, my sim card was not being read, so I was like WTF? Turns out I installed the rom for n7100, instead of for n7105/sgh-i317... doh, so I thought well that's no big deal, I will just go ahead and flash the correct one, well I did same problem... so then I got panicked and plugged my phone up to my computer, my internal storage was cleaned out, my titanium backup folder with all my progs and other useful things was removed.. so yah, I think my .efs got wiped. I have never up till this point had this type of problem so never have backed up an efs exclusively, I have always made rom backups but never efs. I guess that is my folly as well, so here is my question am I borked or does someone know what to do here?
Things I have tried:
1.wipe/format/dalvik try to reinstall Liquid smooth to no avail TWRP says failed.
2. Restore rom, TWRP doesn't find the file, I guess it doesn't recognize backups from CWM? that are not made in TWRP? so tried Philz, Philz says "Error while restoring /system!", so I reinstalled CWM and CWM installed it, however after getting to the AT&T splash logo the phone stays there in bootloop.
3. tried different things utilizing steps 1 and 2 with liquid smooth
3. From there reinstalled DN3 5.2 successfully, still no service or data.. and that is the last step I have taken.
My questions are as follows:
1. Does a back up typically save .efs data or is that gone for good?
2. Is there a recovery or a prog that can allow the phone's internal memory to be read like a flash drive or a standard drive on a pc so that I can possibly try to use data recovery software to try to find useful files?
3. Can I get a set of efs backup files from this phone from someone else and perhaps edit the file and enter my IMEI information through notepad or another program?
4. Can a stock rom recovery install what I need?
5. If no to the previous 4 is there any online services or companies that could possibly fix this?
6. or am I completely f***ed?
Please if you have no constructive criticism, thoughts, things to try, or have had any experience in dealing with this issue please move on, I have kicked the **** out of myself enough to bypass trolling.. for all those who want to genuinely help and have some understanding of what I am asking/have done, please help and I will do what I can to reward you in turn. THank you so much to any and all! -j
I'm going off the top of my head so bear with me...
In the case of the Note 2, you cannot downgrade bootloaders. The rest works, aside from some Wi-Fi issues with the early bootloader recent ROM combo.
1. I think TWRP does; but if your internal SD has been corrupted and you don't have anything to restore from... Corrupt internal SD might warrant flashing with the appropriate .pit file and the (usually strongly advised against) "repartition" box checked.
2. I don't think so, but there's no harm in copying the entire 16GBs of the phone's memory to an image in order to try said recovery. There's a few threads out there with step-by-step instructions. It involves using netcat to forward your dd or cat command's output to the computer, since you (obviously) don't have enough space on the phone.
3. There's NV items backups with the IMEI removed that have been posted, notably for the AWS mod, these are probably your best shot. Take a look at EFS Professional which has a very educative thread as well.
4. I doubt it.
5. Some guys with "boxes" that do SIM unlocks, JTAG repairs and the like might be able to help. Maybe.
There should be other threads about people inadvertently flashing their T889 or N7105s with the wrong ROM, maybe they've got some interesting findings.
For your and your couple's sake, general rule is that you shouldn't tinker with your SO's device. The same holds true for friends and family. Otherwise you'll risk blame for every "tech" problem, from the printer running low on ink to the latest spyware they unconciously install.
Good luck,
Darkshado
Darkshado said:
I'm going off the top of my head so bear with me...
In the case of the Note 2, you cannot downgrade bootloaders. The rest works, aside from some Wi-Fi issues with the early bootloader recent ROM combo.
1. I think TWRP does; but if your internal SD has been corrupted and you don't have anything to restore from... Corrupt internal SD might warrant flashing with the appropriate .pit file and the (usually strongly advised against) "repartition" box checked. What is a pit file? My internal SD is not corrupted it's just wiped.. there are files and folders present, but my originals folders and files that included my Titanium backup files and such are gone.. how do I know if my .efs files are present at all?
2. I don't think so, but there's no harm in copying the entire 16GBs of the phone's memory to an image in order to try said recovery. There's a few threads out there with step-by-step instructions. It involves using netcat to forward your dd or cat command's output to the computer, since you (obviously) don't have enough space on the phone.why do I not have enough space on my phone? i have 30 gigs free between internal and external storage? But copying files to attempt a recovery is not the same thing, data recovery software has to be able to access the device to read the nand in order to recover any files correct?
3. There's NV items backups with the IMEI removed that have been posted, notably for the AWS mod, these are probably your best shot. Take a look at EFS Professional which has a very educative thread as well. WHere can i find these NV items? do you have any links? I have efs professional installed but i am still pretty clueless and I keep getting errors trying to access my device.
4. I doubt it.
5. Some guys with "boxes" that do SIM unlocks, JTAG repairs and the like might be able to help. Maybe.
Do you know of any websites or links? i have been unable to find anything to help.
Click to expand...
Click to collapse
There should be other threads about people inadvertently flashing their T889 or N7105s with the wrong ROM, maybe they've got some interesting findings.
For your and your couple's sake, general rule is that you shouldn't tinker with your SO's device. The same holds true for friends and family. Otherwise you'll risk blame for every "tech" problem, from the printer running low on ink to the latest spyware they unconciously install.
Trust me I know, but she said it was okay plus I have never ran into any problems like this before ever, I do all those little pc repair tasks for all my family because I did just that.
Good luck,
Darkshado
Click to expand...
Click to collapse
THanks for your help, I will paypal for any positive results I swear it!
Generally a wrong rom means a trip to the JTAG guy at www.mobiletechvideos.com and you pay $50 and wait a week.
rangercaptain said:
Generally a wrong rom means a trip to the JTAG guy at www.mobiletechvideos.com and you pay $50 and wait a week.
Click to expand...
Click to collapse
This...^^^^^...
And data recovery is also possible...along with EFS RESTORE services...
I used them for a bootloader downgrade service last month...
Josh can fix you up....g
We gave you your solution --- pay up!
No longer desperate for help.
Well, unfortunately for you all, and I should make a thread that states this very thing, that I resolved the issue on my own w/o 3rd party help. Where I had thought it was my efs, it wasn't, it just happened to be my modem was deleted. So from a wi-fi connection and from the DN3 7100 rom I downloaded the appropriate rom for 7105 and a stock recovery to try first, flashed a new version of CWM touch, deleted and wiped everything except int. storage. I then tried the stock rom to successful boot, just still no baseband, no service, no sim recognized, so after thinking and trying a few other things, I thought maybe it was just my modem, sure enough, after flashing the modem UCAMH3, my baseband, connection, and everything came back, after that I rewiped and installed DN3 for 7105 and boom, everything is right with the world. Many thanks for your previous suggestions, but as I did not use them.. you have my gratitude.
Er, you can't actually delete the modem - it's a binary file that flashes a chip. You can replace the firmware with other firmware. Possibly you flashed a corrupted file.