Related
i know this isnt a Q& A section so ill try to structure this without a question
recently my 3Geuroxoom has been having trouble with the following process
""the process com.android.phone has stopped unexpectedly"
Does anyone see this on a stock ROM? i havent actually done anything to make it say this, could someone look into this and find out why it may do this.
I have a feeling it may have a link to the dialler storage as ive seen this before, but would it also possibly involve something we could look at restoring / fixing if its becoming a problem for other xooms as it meas you cant use 3G under any circumstances?
or can someone at least do a backup of there dialler storage APK and send the back up my way, without the data of course xd
can someone direct me to a way that i can extract my google information from a data.img so that i can put that in my newer rom that gives me a "cant establish connection with server" because i cant seem to get things working when i flash new...and when i do an advance restore and choose the data.img from my old account, my google works perfectly with great connection but my youtube or anything with videos dont work....
or someone atleast kno a more active community? i have asked so many questions here and there isnt really anyone active or they probably dont care..
First of all, that question isn't entirely clear. You've tried only restoring data through recovery and it works, but videos don't? Do you have flash installed?
Try backing up your accounts with Titanium Backup then restoring. The problem is most likely with your rom or with Google.
Also, less than two hours without a response doesn't make this an unhelpful community. You're welcome to find a new one, but with that attitude people won't want to help you.
Next time, give more information so people can help you. What rom is giving you issues, which rom are you coming from? There's a thread somewhere about extracting data from nandroid backups. I'm not sure what you'll find there or if it'll answer your question, but you can try reading that.
Sent from my PC36100 using Tapatalk
i understand what your saying , and if its abbrasive the way it sounded i assure you it was not. reason i said that comment is this...i been a member since 2007 and lately i asked the same question in different forms on other threads. as far as what your saying, i flashed mainly all roms and nothing..omj, cynogen, but will try the titanium backup thanks.
***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it. Also, I would recommend this be posted in the dev section as this is where people go to install ROMs, not the QA section. People go to QA after they have an issue. This is meant to be preventative, not a fix for an already broken device.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers
posting a link to youtube would be an awesome way to show us noobs how to Exactly go about it also..when i had my captivate i flashed a rom called cognition,super easy following the guy on the video
What about other ROM's?
Can you show us how to flash ROM's from another carrier such as AT&T? There are a couple of ROM's I am really interested in trying out but have no luck doing so because of me not knowing what the heck I'm doing or how to do it. If you could post instructions that would be really nice.
Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested
Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.
techn0crat said:
Interesting!
Next time I flash a ROM, I will wipe thrice, as you say.
But do you know why it is important to wipe thrice? Does the extra two times really do something additional to scrub the disc?
I am truly interested, and I would like more insight on *why*
Also, the dev for the Jedi ROM suggests fixing permissions after the first boot.
In my experience, this has led to better performance on other devices in addition to the GNII - perhaps that is also worth mentioning.
Click to expand...
Click to collapse
There has been debates forever about the wiping more than once theory. I have always done this out of habit. You could compare it rinsing a dish in the sink that has some food on it... you wash it once really quick... you see nothing on the dish... you throw it in the cabinet. Later you see some small smudging on it and end up cleaning it again. Same idea. Just being thorough. As I said in the OP I have always done it this way simply to be thorough. And I have never once been the rogue user with an isolated issue.
To answer your q about permissions, if the ROM dev suggests that for his ROM, do it. It is not always required. But if instructed to do so, it should be done.
Is there a reason why it suggests to wipe three times?
I think it may go back to floppy disk days, or hard disks possibly leaving "footprints" on it, old images or data but im not sure. Just a theory.
G●Note~2 {Jedi X5}
Yes please add a section to the OP about flashing roms from other carriers. The steps are identical, except you flash a modem. We onky have the one availabke now so its very easy. Keep in mind n7100 roms will not work, and n7105 roms need minor porting. But you can take any rom from the us variants and flash it. Reboot, let it sit a bit, etc, flash modem. Its very easy and the att forum seems to be getting more love anyway
Sent from my SGH-T889 using Tapatalk 2
I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.
krayzielilsmoki said:
Since I'm already rooted I can't make a video on how to root but ill make a how to flash a rom once you're rooted for the note 2 if you guys are interested
Click to expand...
Click to collapse
you could unroot and then do a step by step vid. this guy is so good at explaining it,for example,,http://www.youtube.com/watch?v=MsafJ-9uRqk yeah i know its for the captivate,but i didnt know anything at all about rooting and flashing . i just followed him and iwas a happy man after being stuck on eclair cause at$t was so slow to update,,,any how just an idea,seems like alot of work but i think it would kill off many questions,i know i ask enough now as it is..lol
cobraboy85 said:
I don't promote people flashing ROMs that are not built for that specific device so I will not do it. Sorry.
Click to expand...
Click to collapse
I have to agree with this. If you need flashing instructions, flashing ROMs meant for other devices is probably not the best idea at this point.
G●Note~2 {Jedi X5}
This is great advice about the MD5 verification. Everyone should check before flashing, it will ensure you have a good download with 100% confidence. If the MD5 doesn't match, don't flash it! And if a developer doesn't provide an MD5 with each download, ask them to.
However, wiping three times (or any other number of times except one) is nonsense. Would you format a USB thumb drive 3 times? An external hard drive? Android partitions are no different.
If it makes you feel better to wipe multiple times, go ahead, it won't hurt anything. You're just wasting time.
^kind of agree with you there. I would ask anybody here why they wipe dalvik cache when flashing a kernel then, considering the /data/dalvik-cache/ partition is nothing more than dex opted files of all your apks. I will also say that recently I have gotten in the habit of never wiping dalvik when flashing a kernel and it has not made a single difference in stability.
... point I am trying to make is what you said here, if it makes you feel better, do it lol. Doesn't hurt anything.
Indeed, cache wipes are seldom needed too. In fact, a lot of flashable .zip files have scripts which wipe the appropriate partitions automatically anyway when you install them. I guess old habits die hard...
I would also add that after flashing a ROM and you reboot that ROM, for use, you should wait at least 10 minutes before doing ANYTHING with your phone. That will allow the phone to fully and properly build cache and dalvik cache.. after a flash I let my phone just sit for 20min. Doing this has saved me from lags and bugs.
First I just wanted to say great job to the OP on creating this thread. I also strongly believe that this type of post really should be in the Development section, and you definitely nailed the reasoning for it. I've always considered writing up a thread like this myself, but I never got around to it unfortunately (<--Procrastinator ). There's just a few thing's I'd like to chime in with because I really believe they can help people who are new to the world of rooting. First and foremost (imo) I strongly believe that insecurity plays a huge role in determining whether or not you'll be successful with rooting and Android in general. I completely understand that statement can be applied to almost anything in life, but there's a very good reason why it's especially true when it comes to rooting. It simply boils down to people not wanting to feel (or look) stupid, and it seriously impacts the way a person handles different situations. My advice is to be comfortable with saying "I don't know what I'm doing" and "It's most likely not working correctly because I missed something or I didn't follow the directions exactly". I am not saying that to be ignorant or joking whatsoever, because if you have little to no experience when it comes to this stuff, it's nothing more than the hard truth. It doesn't make you stupid if you don't know how to fly a jumbo jet if you've never done it before, so why would it make you stupid for not knowing how to root a phone if you've never done it before? It doesn't and that's the entire point. If you try flashing a rom and it doesn't boot up or something isn't working correctly, 99.999998 percent of the time it's because you messed something up along the way. Especially when you see tons of posts in the thread like "awesome rom" or "it works great", because it's WAY more likely that you messed something up, versus you happening to have the one messed up phone out of thousands that are working perfectly. That's not saying you're stupid or incapable of doing it, again it's nothing more than the hard truth. It's also not impossible for that to happen either because it has, but it's few and far in between whereas making mistakes or forgetting something is a frequent occurrence for all of us. I can't tell you how many times I've seen people complaining about how something didn't work right, when the vast majority aren't having those issues (or just the known issues). Those types of posts are another example of what you should never do, because in reality you're blaming everybody else since you're apparently incapable of making mistakes. You'll be surprised how many times a problem you're having will turn out to be from forgetting something, even though you were absolutely positive you've done everything correctly. Anyway I really think that accepting the fact that you don't know what you're doing (yet), can make it WAY easier to learn in the long run. One last thing that I'd recommend especially if you're new to this whole rooting world, is to get in the habit of making nand backups (especially before you flash anything) because the 5 minutes it takes to do one can save you hours of frustration. Hope this helps somebody anyway
Paragraphs man. They make reading easier by separating thoughts.
I'm sure what you have to say is insightful but a megablock of text is tough to get through.
Don't sell yourself short by making your posts impossible to ponder.
Hastily spouted for your befuddlement
True in most cases but in our case every lte note two in the world regardless of carrier is identical. the only differences are minor software ones.
Sent from my SGH-T889 using Tapatalk 2
I also think wiping three times is a waste of time. These devices are digital not analog (the plate analogy is much more fitting in the analog world). A wipe is a wipe, doing it more than once seems like voodoo to me .
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.
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