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.
Please forgive me if this is in the wrong spot or if I broke some forum rule, I have never posted here but I have read a ton, thanks for all the help you guys have posted by the way.
First off I am not by any means an expert on computers and rooting but I have a decent understanding of the basics and can easily follow online instructions to root. I obviously have a d2att, I recently rooted it. I was happy with it unrooted for nearly a year but when samsung released the 4.3 update my phone really started sucking. Eventually I decided to root just to get a rom that functions better. I have been running gummy rom kit kat, I think its the nightly from march 10th, I have had no real issues other than some random reboots here and there. My mom begged me to root her d2att because she also was tired of the buggy samsung 4.3 update. I eventually rooted hers, even though I really didn't want to, knowing that I would get calls about every little issue and I would have to run and fix it... anyway
She has had issues that I have not had, she says that her phone randomly turns to silent periodically and causes her to miss calls, and she also says her bluetooth is intermittent. I don't use blue tooth at all so I wouldn't know but I have not had an issue with randomly going to silent. I have tried a lot of custom roms over the past 2 months since I rooted, including CM11, CM10 (all of them), AOKP, slimroms, of course Gummy, and a variety of others. All of them have had some major bug that is unbearable, from not connecting to wifi or not sending and receiving MMS, except for gummy which I have only had the random reboots.
Okay, so when I rooted mine originally I made a nandroid copy of the original rom after I rooted it, I didn't realize but somehow this nandroid file created to my internal memory instead of my sd card, so when I loaded a custom rom it was deleted. Like I said I'm far from an expert and that was a huge mistake. So anyway when I rooted my moms (same phone) I made a nandroid of her stock rom after the root and saved it to my computer, tablet, flash drive, external hd... etc.
Now that she is having problems with the absolute best ROM that I have found functionality wise, I thought I would restore her stock rom and debloat it, try my best to get it running better. I used her nandroid back up and restored my phone to it, only to get a ton of errors, everything was force closing. I kept getting the popups that "unfortunately ... has stopped" they were nonstop. Literally all I could do was hit ok and try to do the same with the next window, finally I get rid of those and the phone wouldn't run any apps or make any calls etc. So I rebooted to recovery and went restored my nandroid that I made earlier that day and all is fine with my phone again.
So here is my questions. First off when I made the nandroid of her stock rom I renamed the file STOCKROM, that way I would def know what it is and to not delete it. Will renaming a nandroid file make it not work correctly?
Also would a nandroid back up of her phone simply not work correctly on mine? I thought it would but it def does not. Maybe there is saved data that doesn't match my sim card.. I have no clue.
If I used this nandroid on her phone do you think it will work corretly?
If I messed up the file be renaming it, does anyone have a backup for stock that I can possibly use?
Last but not least, any recommendations for custom roms for d2att? I really just want speed, and no bugs
I am really sorry about the excessively long post, but I wanted to fill in the background info before I asked my questions, in case it was needed. Any help at all will be greatly appreciated.
Again please forgive me if I broke a forum rule or posted in the wrong spot, I don't typically post on any forums ever, I just tend to read the posts of others. THANKS IN ADVANCE FOR ANY AND ALL HELP, GREATLY APPRECIATED.
sdevans80 said:
So here is my questions. First off when I made the nandroid of her stock rom I renamed the file STOCKROM, that way I would def know what it is and to not delete it. Will renaming a nandroid file make it not work correctly?
Also would a nandroid back up of her phone simply not work correctly on mine? I thought it would but it def does not. Maybe there is saved data that doesn't match my sim card.. I have no clue.
If I used this nandroid on her phone do you think it will work corretly?
If I messed up the file be renaming it, does anyone have a backup for stock that I can possibly use?
Last but not least, any recommendations for custom roms for d2att? I really just want speed, and no bugs
Click to expand...
Click to collapse
If you decide to go back to stock 4.3, this thread should help. AT&T I747 UCUEMJB Stock Restore
I've never had to use a nandroid and definitely have not tried one on a phone different from where it was made, but from reading in the past I don't believe that renaming it is causing the problem. I believe it is probably due to either trying it on a different phone or the file structure may have been changed when you moved it to the pc. Hopefully someone more experienced will chime in regarding the nandroid on your phone. If it is still on her phone I think it may work.
thanks
Zdq4DDunit to the pc. Hopefully someone more experienced will chime in regarding the nandroid on your phone. If it is still on her phone I think it may work.[/QUOTE]
Thanks for the tips. I know its still on her phone and the name hasnt been altered. I wanted ti try a debloated touch wiz for her. I havr liked Gummy but loaded a carbon jelly beam tonight. So far so good. Any suggestions for custom ROMs for attd2? I have had a time finding one bthats useful. I'm glad I have my gummy on nandroid. When I finish screwing around for her that's where I'll head back to I'm sure. Unless I find a sweet bug free ROM through a reccomendation. I'll check the link in the AM thanks for the reply.
sdevans80 said:
I wanted ti try a debloated touch wiz for her. I havr liked Gummy but loaded a carbon jelly beam tonight. So far so good. Any suggestions for custom ROMs for attd2?
Click to expand...
Click to collapse
I have been considering Intergalactic, but I haven't tried it yet.
Any link for that?
sdevans80 said:
Any link for that?
Click to expand...
Click to collapse
[ROM] Intergalactic v4.1 [AllianceRom][UCUEMJB][4.3][1/8/2014]
question
You MUST have the UCUEMJB or UCUEMJ2 bootloader and the UCUEMJB modem installed before proceeding or this ROM will not work properly. Your data and wifi may be broken if you do not do this first. These are available here: Bootloader and Modem Options
sdevans80 said:
Any link for that?
Click to expand...
Click to collapse
Quick question. I have only rooted and flashed cm toms and aokp. I haven't done anything specifically to change my boatloadsoor kernel. I really don't have the knowledge absolute that. The first step says what's listed above. What does this mean? Can you help? Thanks for the time and tips.
Hey there guys!
So I'm having a bit of a situation with my Nexus 5. It is a first production run as I ordered it the hour it came out.
Today it started having HUGE issues. This is a few days after I downloaded Marshmallow 6.0. The device would shut down and then go into a boot loop for HOURS. Sometimes it'd start back up fine and be usable for a few minutes, but then shutting down and becoming unusable. Sometimes it'd start up and the "Optimizing Apps" screen would come up as if I had just made an Android upgrade, and it would complete after some minutes and become usable until it restarted again.
The phone "seems to be working" now OK. This thread is gonna be a bit multi-faceted, so sorry for asking so much :/ Just having a situation with my phone I want to remedy.
First, I'm looking for a good unrooted backup program I can use to backup the stuff on my phone to my computer or somewhere else. I want it in case I get the phone working again or I get a new android and want to transfer stuff over. Is it possible to move data from one backup to a new phone? Not sure. Either way, just looking for a good backup program I can use, if anyone can recommend me one.
Second, besides the obvious possibility of Marshmallow messing my phone up, a lot of people say it could have to do with a "stuck internal power button" and that "smacking the phone against a hard surface near the camera" could help. This seems mega sketchy, but at this point Im willing to do it after a backup. Does this solution have any merit or is it, as we say, "bulls***"?
Third, is there any possible way to remedy a bootloop software-side?
Thank you!
Since you are talking about downloading 6.0, and don't mention the N5X, I'm assuming you are in the wrong forum
That said:
You can run backups with adb (search for "adb backup"), without root. Just need adb debugging turned on in Android. This will also let you restore apps.
I've always used Titanium or a custom recovery myself, so I'm not familiar with the whole process.
I think you can clear the cache in the stock recovery too - might help? Fastboot & TWRP would offer more options, of course.
No idea on the stuck button theory - hopefully mods move this over so N5 veterans can you help out.
Thanks for the help!
To be perfectly honest, I didn't even know a Nexus 5X existed until now :$ Sorry for posting in the wrong forum, thought the X just stood for some production run number. My bad!