Related
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
crawlgsx said:
With all of the forums merged it was so hard to get a read on the real amount of IMEI Problems by AT&T Users.
So a quick poll / count. Who has lost their IMEI on AT&T.
Click to expand...
Click to collapse
I lost my IMEI on my first Sgs3, went flash happy (only AT&T ROMs) but still had data and cell. Not sure where I lost it, but I noticed when I was flashing back to rooted stock from early CM10 preview (official) is when I noticed.
So far with my new phone, I've done the same and still have it. I'm now running Aokp jellybean.
I've had no problems as of today but the fear of losing my imei has definitely caused me to not experiment as much as I would like to! I've rooted, installed CWM-Touch, flashed Ktoonsez Kernel, and flashed back to the AT&T Kernel. I'm honestly afraid to try CM as it seems that ALOT of the people who have lost their IMEI had flashed CM10 or CM9. I bought a Galaxy Tab 2 7" a few months back and it's become my tinker toy to flash ROM's and mess with. I don't want to screw up my $500 Galaxy S3, I like it too much!
I voted as flashed a few, but really it is probably closer to many. Only AOSP based ROMs though. CM9, CM10, and AOKP plus updates for each. Also both Faux and Ktoonsez kernels at various times. IMEI still present.
I do make sure that I flash the EXACT same way every time though since it has worked so far. Only thing I have changed now is moving from latest non-touch CWM (installed through ROM Manager) to latest TWRP (through Goo Manager).
If I end up losing my IMEI without adding variables to my flash process, I will start to believe it is a random occurrence. Until then I have to think partial user error coupled with a bad update script or recovery.
I ALWAYS download the file straight to my phone via WiFi.
Reboot into recovery. Wipe>Factory reset.
Flash ROM.
The last couple days since moving to TWRP I have felt more ballsy and did things a bit differently.
For the first time, I also wiped cache and Dalvik before flashing JB AOKP last night
Still no issues.
Today I decided to flash the ktoonsez JB kernel. I usually only download via WiFi at home (just to keep minimal variables in flashes) but today I did it at work via WiFi. Still have IMEI.
I have NEVER done a Format System so not sure if that might break something.
My process has been if it isn't breaking, try to keep the process as consistent as possible. If something does go wrong, I can say what I did differently. I also haven't had any trouble with the ROMs I flashed despite only doing factory reset then flash.
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
spacecasespiff said:
How do I know if I have any issues with this. What do I look for. I found out and mines good.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I know you found out, but when it happens you will know.
In some cases it seems as though you only get Edge at your maximum speed, in others your mobile data completely died. Generally speaking, there was a lot of confusion and some issues with clarity regarding the issue.
It's possible that there are several different (but vaguely related) issues going around, now that we have our own carrier based forums that should actually help clear it up in my opinion.
Hopefully we will all reach a general consensus on the acceptable recovery (my vote is TWRP!) and method of flashing. The only thing I've personally considered is that it might be an issue with the files transferring via MTP (only because I've never used a phone with MTP instead of mass storage).
I don't think people should be THAT afraid to flash though. If your flash counter is at 0, Samsung should do a warranty swap for you. In addition, it seems like 2 in 25 people (read: NOT FLASHES, but people.) seem to get the issue based only off of the very small number of people in this poll so far.
The reason the issue is so feared is because those that do get it will inevitably be far more vocal than those that don't as they try to find a solution and vent their frustration. Most of the people in the major thread about it didn't have the issue, but were afraid they might lose their IMEI.
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
I'm about to root and cwm what's your guys input on the best ways
Sent from my SAMSUNG-SGH-I747 using xda premium
yokken said:
I flashed the stock rooted tar that doesn't trip your counter, then injected CWM with dd. I've flashed everything with CWM since then, CM10 included (once) and I still have my IMEI. I'm running AOKP JB now.
Click to expand...
Click to collapse
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
As always, check your apn before freaking out! It may have gotten deleted while flashing a rom. It happened to me
Yes, I freaked out.
Sent from my SGH-I747M using xda premium
tyshemi said:
What's this dd you speak of sir
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
yokken said:
If you read the thread I mentioned (How to root without tripping flash counter) it mentions "injecting" CWM using a tool called dd.
Click to expand...
Click to collapse
Yea I have read that many times there guy thanks for input just solidifying it all
Sent from my SAMSUNG-SGH-I747 using xda premium
ppl who scared to flash
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
I have to use Odin for root initially don't I ? Then use it for cwm or u recommend Rom manager ? Im just wanting stock Rom like yours for now
Sent from my SAMSUNG-SGH-I747 using xda premium
bravomail said:
Go for nontrip flash root + CWM topic - worked for so many people without issues.
The only way to screw up IMEI with these ROMs is via Odin, I think. Odin is a scary tool without much documentation, and in past used to be buggy.
Once you get CWM - do not use Odin.
Click to expand...
Click to collapse
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
codycorexxx said:
Odin is a scary tool indeed. Someone in the IMEI thread said if I was feeling feisty to flash stock nonrooted OTA ROM via Odin straight from JB AOKP. IMEI is still intact after all that I have done. :laugh:
EDIT: Also, anyone who reads this. Try out TWRP. We need more people flashing with TWRP, if an IMEI goes missing while using it we can rule out CWM being the problem as some have suggested.
Click to expand...
Click to collapse
Ive done this, not once but twice. Once coming from Aokp and once from cm10. Imei still intact :good:
Lmao, funny thing is i was deathly scared of the imei issue and very well versed on it, and i never knew it was "dangerous" till i read your post just now.
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Is it supposed to use T999 firmware?
Only odin flash T999L firmware. I dont see it released yet at samsing-updates.com though.
Maybe samfirmware.com? I can look later.
Sent from my SGH-T999 using xda premium
re: sure fix
newidforu said:
I bought a T-Mobile Galaxy S 3 LTE with model number SGH-T999L. I used Odin V3 1.85 to flash TWRP recovery and CyanogenMod 10.0.0.
Everything went well but my camera doesn't work. On launching the camera, I get a "Can't connect to camera" error and it quits. The same behavior is observed when using other camera apps. I tried the instructions in this thread(http://forum.xda-developers.com/showthread.php?t=2239414) but it did not fix my problem. I now want to go back to my stock ROM. I successfully downloaded and flashed stock recovery using Odin. However, Odin fails when I try to flash the stock ROM obtained from the samsung website. It gives me a "write failed" error and stops. Any tips or suggestions to help me out would be appreciated. Thanks
Click to expand...
Click to collapse
Why not reflash the stock ODIN flash rom and make sure it all works ok for you, that will tell you exactly what the problem is.
If the stock rom is working properly, then there is only one thing left which is the culprit and that is the CM10/AOKP/AOSP
or PORTED roms which many people seem to like flashing.
The CM10/AOKP/AOSP and ported roms are excellent if you are a developer or if you like to do a lot of experimentation with your phone.
So the thing to do now is reboot your phone to recovery mode, do a "Factory Reset", "Wipe Cache", "Wipe System" and "Wipe Dalvik".
When that's done Open Odin and put the stock rooted T999 Tmobile Jellybean 4.1.2 into Odin's PDA slot, go into download mode
and once you see Odin is connected to the phone start the flash. Have patience for the phone to boot after its done flashing.
Here is the stock rooted Odin flash T999 Tmobile Jellybean 4.1.2 rom that you can download if you like: T999_UVDMD5
Official JB Firmware - Latest JB 4.1.2 Firmware
My suggestion to you is to only flash Samsung T999 Tmobile stock based Jellybean 4.1.1 or 4.1.2 roms in the future.
But who am I to say whats best..... This is just my personal opinion...... Which usually is not worth a dime. LOL
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sorry, but untill we know more about it, I would not flash T999 firmware onto the T999L.
Its only been out a day and tgey are different model phones with different hardware.
If you decide to try anyway, please post your results
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I am a newbie. I thought the T999 was the same as the T999L. That would explain why Odin doesnt flash stock T999 onto my device. Can anyone here post a link to the stock SGH-T999L ROM?
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Just did a quick check and I dont see that the firmware has been made available for download yet.
If you want stock I would flash one of the stock based custom roms via recovery for now.
Out of curiosity, what is your current baseband version?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
newidforu said:
Baseband version is T999LUVAMB7. Still waiting for stock ROM to be released on samsung-updates or sammobile.
Click to expand...
Click to collapse
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Actually now that I think of it, they prob wont release the original firmware. Seems like the first build is never available, only when an update is released do we get firmware we csn download.
I am working with another member on getting something going for the T999L, but right now we are stuck until a verified safe method of rooting is found. (Dont want to flash a recovery or cf autoroot w/o knowing it wont screw something up)
Itll happen, but we just gotta be patient.
Just reread the op and see that you say you flashed TWRP. So you were able to initially gain root without any problems?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I used Odin to flash Clockwork Mod recovery first. I did not like Clockwork Mod's interface and reflashed with TWRP. I had no problems to gain root with either of these methods. I also tried Cyanogenmod stable 10.0.0 and then 10.1 RC2 without any problems. As far as I can tell, all apps work except for the camera. One word of caution though. As you can see from my posts, I am new and dont know what I am doing. I might have just gotten lucky since my device is still unbricked. I had only one "scary" moment during the entire process. I used TWRP to wipe my phone clean and was stuck with no OS install file. ADB sideload did not work since it could not recognize the device at that point. Luckily, I had a micro SD card lying around and was able to put in a new OS install file using my laptop and then TWRP was able to handle it.
tsticge aye
faytx1 said:
I had the same issue with the same phone. Got it 2 weeks ago haha. Did you happen to make a backup first using CWM Recovery? If so, you can just restore that backup and you'll have your camera functionality back. It's pretty annoying switching back and forth from CM10.1 back to stock just to take pictures but Rom manager makes it pretty quick and effortless.
Click to expand...
Click to collapse
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
newidforu said:
Wish I had made a backup! Could you zip up the files contained inside "/system/cameradata/" folder and post a link here? It would help me and anyone else with the same problem restore the camera's functionality. In case you want to try it out, follow the instructions in this link but using the files from your stock backup
http://forum.xda-developers.com/showthread.php?t=2239414
Click to expand...
Click to collapse
Here is the cameradata folder from the T999L.
http://d-h.st/Ciy
Good Luck!
How did you get Cyanogenmod installed on the t999l every time i try it aborts with status 7
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Beefstew said:
Mine was failing with this same error. I reverted back to stock, re rooted, then downloaded the flash directly to the phones internal storage. Worked like a champ. I think in my case, there is an issue with the SD card, its kind of old.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
You reverted to stock on the T999L? please exspain how that was done
Re flashed stock ROM using Odin. I believe I got the file from Samsung's website, but I'm not positive of that. I do know its huge, over 1 gig. If you need help with the re flash I know there are already how to's on here about that, so I won't go into it here.
Sent from my SGH-T999 using xda app-developers app
You must be using a T999 as your sig indicates, not a T999L. Am I correct?
Sent from my SGH-T999 using xda premium
Don't I feel like a tool now. Yes Doc, plain old t999 here. Now that I read back through the whole thread here I see that I was being a bit redundant. Now I will return to my closet under the stairs.
Sent from my SGH-T999 using xda app-developers app
No worries! We all do stuff like that from time to time!
Sent from my SGH-T999 using xda premium
Before you guys read this thread, let me just go ahead and say that i AM in fact a XDA noob... so dont hate. I didnt come here for that, but i came for help. Now, i did notice that there were alot of people having similar problems as i was. And yes, i did read all those threads. BUT, the only difference was, they got that error while trying to unroot. I was trying to root mine. I simply tried flashing CWM (and yes i made sure it was the correct flash as well) and it failed. Tried rebooting the phone, and i got that error. I am honestly freaking out right now as to if i have lost my phone or not, so i wouldnt appreciate hate in the comments, that would not help. So please help if possible... Is there a way to fix this?
We're you on stock Rom. How did you try a put CWM on your phone?? Odin??
Best way to install a recovery is Odin or goo manger!!
If you can get the phone into download mode then you can just flash back to your stock firmware...
Unless you flashed the wrong recovery on your phone. Then your in store for brick city.
Start here: http://forum.xda-developers.com/showthread.php?t=1980644
TWRP thread: http://forum.xda-developers.com/showthread.php?t=1981198
All in ONE thread:
http://forum.xda-developers.com/showthread.php?t=1987541
Good luck with your problems.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Bajanman said:
We're you on stock Rom. How did you try a put CWM on your phone?? Odin??
Best way to install a recovery is Odin or goo manger!!
If you can get the phone into download mode then you can just flash back to your stock firmware...
Unless you flashed the wrong recovery on your phone. Then your in store for brick city.
Start here: http://forum.xda-developers.com/showthread.php?t=1980644
TWRP thread: http://forum.xda-developers.com/showthread.php?t=1981198
All in ONE thread:
http://forum.xda-developers.com/showthread.php?t=1987541
Good luck with your problems.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks, i was actually on odin. But i think i found the solution. You see, when i was trying to find a solution on my own, i accidentally ended up installing a verizon rom on my phone which is att. (i didnt know it was verizon) The rom works, but i cant use mobile data, because its not a verizon SIM card. However, i managed to install TWRP recovery with goomanager, and from that i will attempt to install the JediXP14 custom rom. Strangely, it seems the phone is rooted even though i was told it failed. I will let you know on the progress, should be done in an hour or so.
Oh boy..... I smell brick city.. You better be careful what ur doing with Odin... If u are flashing stock firmware in Odin it flashes the radio with it....
Ok guys, i SOMEWHAT resolved the issue. But there are alot better ways of doing it, i was just forced to do it the following way:
The only flash rom i could get to go in through odin was a Verizon rom. It was basically the stock Note 2 rom for verizon.
Now the only problem with this, is that obviously, my phone is ATT and this is a Verizon rom, but it WILL work, but with an exception. Wifi and all will work, you can call and receive messages, but you cannot access the internet via mobile data. So that was another issue that popped up. I tried flashing an att stock rom through odin, but it stayed stuck at "Setup Connection" so that didnt work. The only solution i could think of was to unlock the rom, so i could use data with my ATT sim card. Strangely, the phone thought that it was a Verizon phone when it was an ATT phone, so that was the only option. It required a root but that wasnt a problem. I installed Hidroid off the play store and unlocked it that way, and now everything works fine. There is still an error message in the status bar saying "Non-Verizon SIM" but despite that message, everything still is in working order. If anyone knows what to do once you first get that error message, you could post it below for anyone else having the same problem. And if there is a way to change it back to the normal ATT stock, that would be appreciated as well. Thanks
Nintendoassasin64 said:
Ok guys, i SOMEWHAT resolved the issue. But there are alot better ways of doing it, i was just forced to do it the following way:
The only flash rom i could get to go in through odin was a Verizon rom. It was basically the stock Note 2 rom for verizon.
Now the only problem with this, is that obviously, my phone is ATT and this is a Verizon rom, but it WILL work, but with an exception. Wifi and all will work, you can call and receive messages, but you cannot access the internet via mobile data. So that was another issue that popped up. I tried flashing an att stock rom through odin, but it stayed stuck at "Setup Connection" so that didnt work. The only solution i could think of was to unlock the rom, so i could use data with my ATT sim card. Strangely, the phone thought that it was a Verizon phone when it was an ATT phone, so that was the only option. It required a root but that wasnt a problem. I installed Hidroid off the play store and unlocked it that way, and now everything works fine. There is still an error message in the status bar saying "Non-Verizon SIM" but despite that message, everything still is in working order. If anyone knows what to do once you first get that error message, you could post it below for anyone else having the same problem. And if there is a way to change it back to the normal ATT stock, that would be appreciated as well. Thanks
Click to expand...
Click to collapse
Maybe you just need to flash att modem with ril for your device. Scroll down and dload the one for att then flash using cwm or twrp. After flashing modem try flashing att rom again via Odin.
http://forum.xda-developers.com/showthread.php?t=2016575
Sent from my SAMSUNG-SGH-I317M
Ok guys I resolved the problem. But it took more steps than it needed. This is for people who accidentally flashed the wrong type of recovery to your phone (example, gt-1700 version of cm what on sgh-I317) I'll be renaming this thread if I can. So here's all the steps I took. Now keep in mind that I didn't exactly know what I was doing so I kind of learned on the way, like I said in the beginning of this thread, I am a noob, and I admit such.
1. Install any rom that is in md5 format (preferably with your carrier modem but anything will do) I used a verizon rom. I can't exactly provide a link given my user status though, but I will when I can.
2. If you don't have wifi and downloaded rom under incorrect modem, then download hidroid on the play store and unlock it. It should be simple once getting the app. This will allow you to use mobile data. You'll need it.
3. Download goomanager
4. Press menu button
5. Install open recovery script
Now you should have TWRP installed on your device.
6. Install any custom rom compatible with your device, but make sure it comes with the correct modem as your phone originally had.
7. Flash it through TWRP (make a backup first)
You should be done from there. Now I don't recommend this. There has to be an easier way, so it would be great if anyone could provide that below. But the steps above are the steps I took. Thanks
Sent from my SGH-I317 using xda premium
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
cnote74 said:
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Agreed. ..g
Sent from my SAMSUNG-SGH-I317 using XDA Premium HD app
but where o.o
cnote74 said:
Easiest is flash att rom thru odin then reboot into recovery factory reset then let phone boot up.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Umm guys, i ran into a similar problem. Where would i find the att rom to flash from odin?
Hi xda, I hope your Friday is going well.
EDIT: My calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody? I don't even hear a dial tone if I am the one dialing out, the call still goes through though.
Everything below was my original post which has been resolved, didn't want to start a new thread though.
-----------------------------------------------------------------------------------------
TL;DR: My T-Mobile Samsung Galaxy S 4 (SGH-M919) is unable to boot stock rom, and I am unable to enter recovery. I get seandroid messages trying to do either. Fortunately, the phone can enter download mode. What do I need to do or flash to get this phone booting again? Thank you in advance for taking the time to read and help out.
Below is the long story with details:
1. The phone was given to me running stock Android/TouchWiz. Unfortunately, I do not know what version but I assume it was whatever was the latest version as of late April.
2. I rooted the phone using Odin and CF Auto Root.
3. I created a backup of this newly rooted stock rom.
4. I flashed Cyanogenmod 11
5. After a while I discovered that I could answer calls but I could not hear nor be heard during the call.
6. I restored to the stock rom using the backup I made in step 3.
7. The calling issue continued, so I figured I would just unroot and go back to like-new factory settings. This way I could take the phone in to be repaired or whatever.
8. Following this thread: http://forum.xda-developers.com/showthread.php?t=2336392, I attempted to flash k0nane's UVUAMDL Official Tar
9. Odin got stuck connecting to my device, I believe it was because I did not run Odin as admin. I pulled the battery and repeated this step while running Odin as admin.
10. The flash was successful, however during the phone's first boot it got stuck on the T-Mobile splash screen for about 30 minutes or so. I pulled the battery again.
11. Anytime I put the battery back in the phone, it will attempt to boot and hang at the T-Mobile screen, I believe this is a boot loop?
Looking online, people suggest going into recovery and wiping but I cannot enter recovery. I just get the seandroid not enforcing messages. I'm very hesitant to keep looking through the forums and trying things because I feel like I'm on the edge of bricking the phone if I haven't already.
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
serio22 said:
I don't think the flash was successful because it wouldn't give you those messages, and you would need to flash either 4.3 or 4.4.2 not 4.2.2 (MDL) Try flashing a newer firmware version.. If it was updated to the newest then I would try 4.4.2
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
Ok so I flashed the wrong rom then. I hate to ask but where could I find a 4.4.2 stock rom? I just found a rom I believe will work but the file is titled "M919UVUFNB4_M919TMBFNB4_TMB" not sure if this is 4.4.2 or newer?
You download the stock 4.4.2 ROM from sammobile:
http://www.sammobile.com/firmwares/
Sent from my SGH-M919 using XDA Premium 4 mobile app
Android_Monsters said:
You download the stock 4.4.2 ROM from sammobile:
[link removed]
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
THVRSDAY said:
This is where I obtained the rom above that I wasn't sure was the newest.
I flashed this rom and everything worked, thank you both.
Any ideas on what happened with the phone call issue? My friend that gave me the phone said it was working just fine when she had it, so I assume somehow the rooting or CM11 screwed something up? Weirdly, calling through WiFi works just fine.
Click to expand...
Click to collapse
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
PanchoPlanet said:
The only thing that can foul up your phone like that would be a bad cm flash or preflash, it's super important to read and read again, check the thread for support from members and resolutions to problems before you consider the build for your phone. Ask questions and double check everything before you take the plunge.
I assume that the calling problem is fixed, a corrupt modem may cause that and re flashing the modem will correct this.
Pp.
sent from my bluetooth controlled toaster that also takes pictures.
Click to expand...
Click to collapse
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
THVRSDAY said:
The calling problem was not fixed. I reflashed 4.4.2 NB4 Modem (twice to make sure it stuck) and the calling still does not work. Did something just completely fry when I had CM11 on this thing? Any ideas anybody?
Click to expand...
Click to collapse
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
serio22 said:
Did you flash the NB4 firmware twice? Firmware, not modem
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
THVRSDAY said:
No, I only flashed the NB4 modem bin found here: http://forum.xda-developers.com/showthread.php?t=2678774. I need to flash the whole NB4 tar twice as well?
Click to expand...
Click to collapse
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
serio22 said:
Well modem didn't work so try the firmware
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
THVRSDAY said:
I flashed the NB4 tar from sammobile twice, calls still not working. I feel like I'm not flashing the correct thing or something.
Using the Android System Info app, every entry has something in it except for Radio. It just says "Radio: unknown". Does this have anything to do with anything?
Click to expand...
Click to collapse
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
serio22 said:
That is a problem.. How did you get this device?
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
New term for CM, "complicated maneuver" ,.
Reflashing firmware may do it. Can't hurt either.
Pp.
Sent from my SGH-M919 using XDA Premium 4 mobile app
THVRSDAY said:
My friend gave the phone to me. She got an S5 and didn't want to bother with selling this S4 so she just gave it to me. It was completely pure and stock, with calls working. Something screwed up during the CM11 flash I guess.
WiFi calls still work, everything works except calls.
Maybe I'm doing something wrong? I flashed the sammobile NB4 tar twice via PDA in Odin as usual. For the modem, I flashed the modem bin via Phone in Odin twice. Thank you for your help, by the way.
Click to expand...
Click to collapse
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Sent from my SGH-M919 using Tapatalk
serio22 said:
I think something definitely went wrong.. Try flashing this firmware, it flashes better for most people http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip after that, factory reset and if that still doesn't work then you have a bigger problem.. Good luck!
Click to expand...
Click to collapse
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
THVRSDAY said:
I flashed both Fenny's firmware and a baseband he also provided. Did both twice, and calls are still not working.
I was doing some research on this whole "Radio: Unknown" thing and I started seeing threads talking about flashes corrupting the phone's EFS partition. I never made a backup of mine, so I have nothing to restore to. Is it possible that I could use someone else's EFS backup and then use it to restore my phone's EFS partition? Does it work like that?
Click to expand...
Click to collapse
No it will not work, this is device specific afaik.. Like I said earlier, I recommend you call T-Mobile for a replacement
Sent from my SGH-M919 using Tapatalk
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Skipjacks said:
Flashing modems and such with a custom rom installed often fails. Did you try doing a restore to full stock using Odin?
It sounds like the phoen has Android 4.4 on it already so you will need to flash the full 4.4 package (can't go back to 4.3 or 4.2)
Try and, boot hte phoen without modifying it, and see if calls work then.
The EFS thing is about the IMEI number. Does your device show an IMEI number in settings? If it does, your EFS isn't the problem. If it doesn't....well then yeah. Problem is pretty much narrowed down.
Click to expand...
Click to collapse
I have restored the phone to full stock and have been using it that way since I started this thread. Everything is just like fresh from the factory (except for the knox counter being tripped obviously). Calls still didn't work. An IMEI number still shows up the phone's settings. Using WiFi calling hasn't been that bad at all, but I'm screwed in the case of a real emergency with this thing.
Hi guys, sorry if this is stupid. I've flashed ROMs to 3 or 4 phones before this one and didn't have any issues with them, but this time around it doesn't seem so easy. My phone is a virgin mobile galaxy s2 (d710)
My phone has been rooted for a while and my stock ROM started randomly freezing up on me 4-5 times/day, so I finally decided to flash a ROM. The stickied post says to use odin mobile to flash to GB - EL26 Stock w/ CWM then to flash the ROM I want. Any ROM I tried flashing gave a status 7 error and aborted, EXCEPT for one ROM, and on that one I didn't even have working 3G? I believe this thread implied doing it any other way would be a hard brick.
I finally ended up using samsung's official upgrade tool in download mode to flash back to stock ROM, but it would be nice to get a custom on now that I've put time into it.
Can anyone point me in the direction I need to go?
Thanks
EDIT: I'm currently on the 4.1.2 stock ROM
http://forum.xda-developers.com/showthread.php?p=50070702
I'm guessing you're trying to flash a KitKat ROM? Using Mobile Odin and EL26CWM will work when flashing 4.2.2 (and under) ROMs, but not KitKat. You'll need the last Blasphemy 6.6 kernel (just for the updated ClockworkMod), located in Original Development, for that.
In your case, you'll probably want to flash FJ12 or FL26 (if you can find it) modem zips, as you're on Virgin Mobile, and those are ICS Virgin Mobile modems, which you'll need to have working data/internet on Any AOSP ROM (JB modems won't work).
And this guide is assuming you're completely stock JB firmware, not rooted.
Sent from my SPH-D710 using Tapatalk
It looks like I'm on GB28 stock. I think agats caused a soft brick. I'm reflashing back to stock again now....I don't know what's going on with this phone.
Edit: Retried, got it to work this time. Thanks.
Is there a reason why you have to flash one recovery just to move onto another one? Would any recovery work installing any ROM? I'm a bit confused by all these different recoveries, since my last phone only needed one.
InfamousMyzt said:
It looks like I'm on GB28 stock. I think agats caused a soft brick. I'm reflashing back to stock again now....I don't know what's going on with this phone.
Edit: Retried, got it to work this time. Thanks.
Is there a reason why you have to flash one recovery just to move onto another one? Would any recovery work installing any ROM? I'm a bit confused by all these different recoveries, since my last phone only needed one.
Click to expand...
Click to collapse
On this device, recovery comes bundled with the kernel. When you flash a ROM or kernel, the recovery that was on gets overwritten by the recovery that comes with the ROM/kernel you're flashing.
The reason everybody started using EL26CWM (gingerbread kernel) was due to a bug in the stock ICS firmware that was causing some people's devices to be permanently bricked when doing a factory reset.
Status 7 error when flashing is usually due to using a recovery that's too old.
So to answer your question... No, there is no "be-all, end-all" recovery for this device. Sorry [emoji20]
Glad you got it working though
Sent from my SPH-D710 using Tapatalk
Thanks for the help. Now that I'm running CM11, I don't have visual voicemail and it looks like I can't receive MMS.
Serious props to the people that use custom ROMs that aren't driven insane by bugs, I'm irritated by it already.
Know of any fix?
I don't know about visual voicemail... I'm flashed to Cricket and just use the built-in voicemail statusbar notification. Have you tried pushing the apk manually? I'm pretty sure I've seen Virgin Mobile fixes here in the d710 forum.
As far as MMS goes, have you tried messing with the APN's? I don't think MMS will work as-flashed, out-of-the-box for you without modifying them for Virgin.
If you're getting annoyed by bugs, have you given stock, rooted deodexed GB28 a try? When i get the TouchWiz itch, I run deodexed GB28, along with Agat's 1.3 kernel, TD's AIO mod, and Missing Link mod (both found in Themes and Apps of this forum).
I'm currently running Slimbean build 7 (4.2.2) as it's super lightweight, stable, and has good battery-life.
Sent from my SPH-D710 using Tapatalk
Do you know where I could find the voicemail apk?
Also, where can I mess with the APNs/what would work there?
The only reason I want a custom ROM at all is to be on KitKat. It honestly disgusts me a bit that google hasn't standardized versions....I don't get why every phone needs it's own ROM and never gets updated....
Thanks man.
Edit: I did find a MMS fix and visual voicemail all in one zip, but flashing it screwed the phone and I had to restore in recovery.
As far as editing APN's, I use Nova Prime launcher to create a shortcut on my homescreen to access them. Create shortcut to Activities/Settings/APNs and make your edits there.
Have you tried extracting the contents of the zip and manually applying those changes? Sorry but I wouldn't know anything else about configuring for Virgin. Maybe you could ask in that respective ROM thread, as I'm sure there are Virgin Mobile users there that have everything working.
Sent from my SPH-D710 using Tapatalk
Thanks for the ideas, I'm a bit slow sometimes when it comes to android/linux. I pulled the apk out of the zip, installed it, that's working fine. I just need to find a fix for my MMS. I can send but not receive.
Edit: I found a way to open the APN settings using voice dialer, but it's blank and choosing to add one, it does not save.
InfamousMyzt said:
Thanks for the ideas, I'm a bit slow sometimes when it comes to android/linux. I pulled the apk out of the zip, installed it, that's working fine. I just need to find a fix for my MMS. I can send but not receive.
Edit: I found a way to open the APN settings using voice dialer, but it's blank and choosing to add one, it does not save.
Click to expand...
Click to collapse
I had that issue too on cm11. They appear just fine on Liquidsmooth 4.4.4
Sent from my SPH-D710 using Tapatalk
Just for clarification, if I want to flash a new ROM when I'm already on a custom, do I need to use odin mobile to flash back to that GB rom with CWM before I flash the recovery and new ROM? Or can I just wipe and flash new recovery from the one I have now?
InfamousMyzt said:
Just for clarification, if I want to flash a new ROM when I'm already on a custom, do I need to use odin mobile to flash back to that GB rom with CWM before I flash the recovery and new ROM? Or can I just wipe and flash new recovery from the one I have now?
Click to expand...
Click to collapse
If the new recovery you are talking about is safe to flash from...and the one you are currently using is safe to flash from...then you can just reboot recovery and wipe cache and dalvik, then flash new recovery and then reboot recovery. Now you will be on the new, safe, recovery. So do your wipes ( data, cache, dalvik cache and format system ) and flash the rom.
If you want to go the mobile odin way..in case the recovery you currently have cant flash the new recovery you need, in order to flash the rom of choice..which im assuming is kitkat. As it needs the most up to date recovery to flash properly.
Then i have a simple guide you can follow to flash a safe kernel/recovery, in which you can then flash the newer recovery for flashing the rom you have choosen.
Link to guide. Post 5 is what you need to read.
If this sounds complicated or confusing..please post a link to current rom you wish to install and i will read the op and point you down the correct path.
Thanks, I was looking to use either of these. I've had issues with ROMs so far because I'm on Virgin Mobile and lots of stuff is buggy. Not sure which of these will work best:
http://forum.xda-developers.com/showthread.php?t=2298221
http://forum.xda-developers.com/epic-4g-touch/orig-development/rom-liquidsmooth-v3-1-t2803683
I'm not normally confused by rooting/flashing, but I don't understand the whole "safe recovery" thing.
I'm currently on this ROM: http://forum.xda-developers.com/showthread.php?t=2540250
InfamousMyzt said:
Thanks, I was looking to use either of these. I've had issues with ROMs so far because I'm on Virgin Mobile and lots of stuff is buggy. Not sure which of these will work best:
http://forum.xda-developers.com/showthread.php?t=2298221
http://forum.xda-developers.com/epic-4g-touch/orig-development/rom-liquidsmooth-v3-1-t2803683
I'm not normally confused by rooting/flashing, but I don't understand the whole "safe recovery" thing.
I'm currently on this ROM: http://forum.xda-developers.com/showthread.php?t=2540250
Click to expand...
Click to collapse
I see. Im not too familiar with what works with virgin mobile.
But if you can flash a virgin modem and set your apns after a flash.. That will get your data working. I'm at work.. But let me refewsh my memory later about virgin mobile on this device and I'll hit ya back.
Fyi.. I think jdsingle made a virgin mobile rom a while back.
Gil81 said:
I see. Im not too familiar with what works with virgin mobile.
But if you can flash a virgin modem and set your apns after a flash.. That will get your data working. I'm at work.. But let me refewsh my memory later about virgin mobile on this device and I'll hit ya back.
Fyi.. I think jdsingle made a virgin mobile rom a while back.
Click to expand...
Click to collapse
Thanks, I looked for jdsingle and only found posts for 3D Evo I believe; no activity since 2011?
InfamousMyzt said:
Thanks, I looked for jdsingle and only found posts for 3D Evo I believe; no activity since 2011?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39371960
It was made for JB but it's a start
Sent from my SPH-D710 using Tapatalk
Yeah, I tried that one, it continually crashed my launcher every 3 seconds, had to reflash the ROM. It did give me the voicemail apk I needed though! Really if I could just get flash instructions for going from one rom to another, I'd be set probably.
Have you tried applying the changes and setting permissions in the zip manually, like with Root Explorer?
Sent from my SPH-D710 using Tapatalk
Surj138 said:
Have you tried applying the changes and setting permissions in the zip manually, like with Root Explorer?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
No, I'm honestly not sure how to do that. Linux's file structure is confusing to me. Granted I'm also having wifi problems on this rom too, it disconnects all the time.
InfamousMyzt said:
No, I'm honestly not sure how to do that. Linux's file structure is confusing to me. Granted I'm also having wifi problems on this rom too, it disconnects all the time.
Click to expand...
Click to collapse
It honestly isn't too difficult at all. All I see in the zip is a new apns-conf.xml (permissions are rw-r-r), 2 build.prop edits, and the deleting of telephony.db located in /data/data/com.android.providers.telephony/databases
Sent from my SPH-D710 using Tapatalk