Develop Bugs

Question for Shadowmite or anyone who knows

Greetings,
Am rooted, unREVOked, Clockwork recovery, s_off, froyo ROM and 2.XX radio and all of that working well. A couple of days ago my internal speaker blew, not sure why but is is all a buzz now and a replacement will be here in the morning. I am all clear and set with putting the old unit back to stock, but with a NANDROID backup, Titanium backup, and contacts backups all ready, can I just run unREVOked on the new one and do a NANDROID restore and all will be back, radio, s_off, and all ???? Or perhaps a good step by step so I do not break the new one ??? Thanks ;-)

no. you still have to run unrevoked, soff, and the 2.15 radio...after that, you can do anandroid restore

All done Grazi ;-)
I thought so,,,,all done flawlessly ;-)

Please report back
Sorry about your speaker ... I had to return 1 incredible over speaker issues myself.
I note that you ran S-OFF. I have avoided doing so for the exact reason that you are now experiencing ... blown speaker = warranty; S-OFF = no warranty; and one had NOTHING to do with the other.
There is some debate out there as to whether Verizon will figure out you ran S-OFF. Can you please report back and let us know if Verizon denies your warranty?
Thanks!

I would advise against restoring tha nandroid of the first device. There's a good chance that your old phone is going to be repaired and given out as a FRU. As such, both devices would share the same device id.
http://androidforums.com/all-things...05-warning-do-not-share-nandroid-backups.html
adrynalyne said:
Even if your apps aren't there, and no personal information has been entered on a fresh wipe.
If someone asks for a stock Nandroid backup, kindly tell them to get lost
contagous and I learned the hard way. I sent him a completely tweaked and clean nandroid, with none of my personal info or anything like that. He has been using it and it works great.
Until AppBrain fast web installer is used. See, it IDs your device by the Android_ID, which is unique to every phone, or is supposed to be.
Nandroid backups will record this device ID, and clone it onto another device. Well, when contagous installs an app using the web installer, I get it. Without a prompt or nothing.
While I can do the same thing, and it was fun sending him pron apps and sexy men wallpapers, it has a real potential for a security nitemare. I trust contagous, but let this serve as a warning to everyone. Its also not so simple as installing another ROM and factory reset. So far as I can tell, as long as you stay on the same build OS, you will keep the same ID. The only thing that changed my ID to something else was going back to 2.1.
So friends, don't let friends share nandroids. If you do, play it smart, and delete all but the system and boot images and recalculate the md5.
Click to expand...
Click to collapse

Nope
najaboy said:
I would advise against restoring tha nandroid of the first device. There's a good chance that your old phone is going to be repaired and given out as a FRU. As such, both devices would share the same device id.
http://androidforums.com/all-things...05-warning-do-not-share-nandroid-backups.html
Click to expand...
Click to collapse
While I do not intend to get into a debate about facts (facts are facts), the above is false.
I am on Incredible # 3. Each time I have nandroid restored on my new device. Each time I did so, I got a ton of FORCE CLOSES from Mobile Defender, which had to be uninstalled and reinstalled. Why? BECAUSE THE DEVICE ID WAS DIFFERENT.
If i log into Mobile Defender now, I see all 3 of my Incredibles all 3 with different device ID. Please understand, that's 3 phones, all of which used the same Nandroid, and all showing DIFFERENT Device IDs.

Ok steering my own thread, is that ok ????
Sort of still on the same tack but to address the above, I hope that the device ID thing being cloned by nandroid is false because I did not even think of it happening and I hope that I do not get whacked because of it. My old one was visually perfect so I hope they just replace the speaker, do a magic factory flash of some sort, which will hopefully S_ON the thing, and send it back out. An interesting thing is that I think some 3rd party company does the refurb because the box has a return label sending it to some other company, so maybe if they are not on the lookout then they will not check, just pass it thru like cattle on to the next customer. I will report back if VZW gives me any grief later on. If they do not honer warranty and charges me full price for the new one then they better send me my old one back and I will find the speaker myself from HTC and do an ESN swap with my old TP2.
On another note, steering my own thread yet again, when I did my restore I lost my pictures because I did not set the camera to store to SD card, but I assumed that they would be contained in the NANDROID backup, but they are not back in the new phone. I have serceral backups I could look thru but does anyone know how or what to use to open an .img file and which one they would be in ???? Thanks ;-)

Removed Carrier IQ / CIQ, phone won't boot

You've probably heard about the Carrier IQ fuster cluck by now and, if you're like me, are up in arms and want it gone if you have it on your phone. I would suggest that you don't use the removal tool yet...
I am rooted using the "stock" method here: http://forum.xda-developers.com/showthread.php?t=1342728 and just downloaded the tool from http://forum.xda-developers.com/showpost.php?p=17612559&postcount=110 to check for CIQ on my phone (it was there) and purchased the license to remove it, which I also did. I then rebooted the phone as instructed but can't get past the SGS2 splash screen.
Can someone please help me... if I have to flash a new rom, fine - I can accept that. I should have been thinking before I did anything but I had only rooted up to this point and didn't have any Nandroid backups or anything and that's my fault. However, I used the internal phone storage or SD as my primary file location and need to access it to grab my files. Is there any way to do this if my phone isn't booting up?

I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
I'm disappointed because according to Caulkin's ROM CIQ is removed, but I used the tool you are speaking about as well and it states that CIQ still exists. I was going to pay the .99 and have it removed since that tool supposedly works for Samsung devices, but after reading that other thread and now yours - I'll pass.
I'd recommend re-ODIN'ing your phone, not from experience with the issue but just from what I read from the other thread - you aren't going to have much of another option.
EDIT: Here's the link to the thread with your exact questions pretty much and the answers you can expect - http://forum.xda-developers.com/showthread.php?t=1360988

Ugh. Thanks for the reply... this is so annoying. If I go that route, it's going to wipe all of my internal SD memory, too? I've already lost access to the items on my external card because I had that encrypted... but I used my internal for primary storage and have a LOT of items on there of great importance...
Starting from scratch I can deal with - losing all my files I can't.

What package are you on? It works on EG30, but not on EK02. Framework is different.
Worked find on my EG30. Waiting for it to be updated to the EK02 package. Should be around soon.

Not trying to nitpick, but you should always have at least two backups of your internal and external memory. That's at least what I do, usually I backup all my files once a week and do a NANDroid once a week. Saves the headaches from ever happening.
You could try three-fingering to see if you can get into recovery and see what you can do from there, but I don't think you are really going to be able to do much. This method has been tried and proven to soft-brick your phone.
I was going to attempt this method this morning and then did a simple search on XDA and found it had soft-bricked that guys phone I linked you too. That's all it would have taken...
Good luck.

I have some backups, as well as Titanium Media Sync running and Google+ uploading photos, but there are always gaps. Unfortunately I haven't done a 'hard' full drag and drop back up for a couple of weeks, and you can generate a lot of data in that time.
To tell you the truth I'm a little unsure about how or what it takes to have the ability to do a Nandroid backup. I've done plenty of them in the past but what I mean is that since I just did the stock root method I don't know if I needed to install CWM or something like that to get the ability to do a Nandroid. I just haven't had the time to research that fully so I hadn't done one yet.
For what it's worth, the ****storm about the CIQ thing just really exploded in the last 24 hours or less so I didn't think there was anything to look up about the removal tool. I guess I was so distracted about the BS that is Carrier IQ and just wanted it gone, so I ran the tool without thinking there was a database of information on it already. It was my bad.

In the automated rooting thread, you could choose Option C and select a kernel+CWM to install EG30+CWM and EG31+CWM are provided.

update: Fixed. Whew. Thanks for the suggestions, especially, sfhub. Did as you said over in the other thread http://forum.xda-developers.com/showthread.php?t=1342728&page=26 ... will post followups there but basically flashed the stock rom in odin and phone booted back up like nothing ever happened. Well, the only difference really was the media scanner took a considerable time longer than usual on that first clean boot. Thank you so much, again, and see you over in the other thread w/ a few more questions...

dbaybay said:
I read another thread (can't seem to find it now I was on my mobile device), where another person did the same exact thing as you and had to ODIN to stock and start from scratch. The phone isn't bricked, but it's not going to boot now.
Click to expand...
Click to collapse
Unfortunately, that was probably me. I freaked out too but just Odin the stock tar and all is well.....other than now being on E31 and now can't get any ek02 goodness.
Sent from my SGSIIE4GTuvwxyz....should I touch my nose or walk a straight line now?

Lost IMEI, service, etc, issues - working on a fix. Need some input

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

[Q] Rom deleted EFS, is there any hope? Please Help! Will pay for results!

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.

Essentially getting a new phone right?

So, i had a problem with my phone and i ruined my EFS partition, by erasing everything and flashing multiple stuff without researching, yay me
the only solutions were very limited
1.3rd Party
2.A box
3.Replacement
Essentially, the perfect method restoring your backup of the EFS and etc but...i didn't have mine...no knowledge lol
anyways
I chose replacement and i'm getting my phone tomorrow as a brand new same s6 , if i were to upgrade its 25$ extra for that or service.
I know for sure this time to keep a safe and sound NANDROID Backup as well as the EFS Backup from an app. Im going to to just backup everything lol
any other recommendations links, apps, and lectures/advice is more than welcome to me c:
my phone keeps thinking its tmobile or at&t but they dont know that haha
when the tech discovered about it they just said it couldnt boot past the bootloader after an hour and i got a replacement claim that would've cost me 75$ but since i got insurance for it im lucky i guess?

See that's the funny thing i ended up doing just that lol x) but as odd as it seems i flashed a stock international rom,that wasnt meant for my phone is for the edge. and then after wards flashed a ported kernel but then yeah. Its not a huge problem to me. so i flashed the stock tar under koops name in the forums the lateast PB6 not PD2 and it just bootloops but after i flash a custom kernel thats meant for my phone a.k.a skyhigh port.. it boots but i didnt show sprint that like what no lol definetly great advice tho seriously. Thank you man c: definetly. i will now look for more apps like the EFS one and Nandroid and TWRPS internal backup stuff just incase C:

Hey theres a new app FLASHFIRE i used just for a extra backup of the efs partition. That's as far as i went because wasnt sure about that app but pulled that backup and named it efs flashfire backup i got it put up in a safe spot for now lol same with twrps also use md5checks from now on like @koop1955 says only takes few extra seconds and can save alot of misery.

Flashfire, developed by Chainfire, the dev responsible for SuperSU and CF-Auto-Root, was first released in Beta in April of 2015. Not exactly a new app, but to your point, very useful. One of the key features is the ability to have and use remote backups, like on an OTG drive or on your PC. If you only keep backups on your phone and you hose your phone, you might be able to get to the backup.
http://forum.xda-developers.com/general/paid-software/flashfire-t3075433

i have an OTG i'd definetly back itup and OH btw i got the replacement and as funny as it is , the baseband or rom was on OI1 not OL1 or anything but OI1 lol and then udpated to PD2 just now...so now looking forward to go through etc steps