Develop Bugs

Request for Virgin Mobile Stock

Hello all,
So I bought my HTC Wildfire S Virgin Mobile on black friday like everybody else. I waited a few days and then rooted. And then I had the brilliant idea to try installing the CM 7.1 Mod for it. And well, I didn't do a Clockwork Backup, and well, it didnt work very well. The phone got stuck on the HTC screen. So finally I installed a different ROM, JikantaruROM, and I managed to get past the bootscreen but I can't use my carrier anymore. So I was wondering if anybody could either tell me how to flash CM 7.1 Unoffical release to my phone, or if anybody knew a way I could get back to the original Virgin Mobile software. It seems that you have all the other stock roms, so I would REALLY appreciate if someone could share the Virgin Mobile rom too.
Thanks in advance,
Wieland959

Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.

thesnaz said:
Seconded. Although I think mine is in a slightly worse case; I kept flashing roms and ended up in a state where it turns on, screen remains black, then the phone vibrates three times and evidently does nothing. So Wieland959, I'd advise you to stop flashing until someone posts the ROM.
And if someone could let me know how to recover from my current state, I'd very much appreciate it.
Click to expand...
Click to collapse
Your in the same boat I was just in. My solution was to go back to radioshack with the receipt and tell them it just turned off and wouldnt turn back on. Just doing the 3 vibrations. I did spend hours trying to search about how to fix it, but I dont think theres a way unless you use a jtag hookup and some sort of fancy programmer.
@Wieland959, If you want. I just tried to do the OTA update through the settings on the phone itself. It would let me download the file(I believe it should be flashable through the cwm recovery), but when I tried to let the phone install the file, I would get the android with the exclamation mark after the reboot. Ill try to post here, if it will upload. But......
DISCLAIMER!!!!
I take no responsibility for anyone damaging their phone using the file here. This file, as far as I know, should only work with the Wildfire S Virgin Mobile USA CDMA model A510C as this is the phone the file was downloaded from.

Thank you for the file, but I couldn't flash it. What might work though, if you are willing is, if you have rooted your phone, to make a cwm backup and upload that here. From there I should be able to recover and then factory wipe my phone. But thank you anyways for the file. I will keep kicking until the phone doesn't boot.

How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...

thesnaz said:
How are you planning on restoring from backup if the phone doesn't even boot?
Sorry, I'm new to this...
Click to expand...
Click to collapse
from the recovery, by holding down the vol down button and power button. then select recovery.
also, im in the same boat as OP haha

Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.

VM USA Stock Clockwork Backup
Well, I don't know much about stuff like this, but here is my clockwork mod recovery backup. It's just the stock VM USA w/HTC Sense. I have realized that I deleted the bloatware, so that's the only thing that isn't 100% stock. Hope it helps.
*Unzip the file before placing on you sd card. (Contains the clockwork folder, which contains the backup folder,and then the folder that contains the backup itself.)*
**!! Disclaimer! Please run the activate application upon installing as when you call voicemail, it will call my number. !!**
http://www.mediafire.com/?le6b07dwr865017
---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------
Wieland959 said:
Okay. I managed to boot my phone and am able to send/receive texts. The rom I used? http://forum.xda-developers.com/showthread.php?t=1367701] It seems to work pretty well. However, I would still like to have the original rom if someone could still upload it.
Click to expand...
Click to collapse
Is this a good rom? I'm looking for some senseless roms that will work with our version of the WFS. will you post if you are able to go back to the Stock Virgin backup that I have posted? Also how much memory is on the rom that you posted?

With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c

BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD

BigChillin said:
With the a2sd enabled, you get 150 to 175. It's nice.
Sent from my HTC_A510c
Click to expand...
Click to collapse
I tried it and found my phone only had 75mb of internal storage available!!! Weird!!
Nevermind I figured out the problem. Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?

Is anybody else having mms issues with the experimental ROM?

brandonhun said:
Can I easily switch back to the stock rom via my backup? How do I install it. Sorry that i'm such a newbie. xD
Click to expand...
Click to collapse
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.

@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.

Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Just a heads up wieland, when you get a voice mail and you try to check it from the notifications make sure it's your number, because I ended up giving brandonhun a call. Going through the activation app and rebooting fixed the problem.

djsquiggly said:
Thanks for the backup! It worked perfect for me!
would you mind if i posted the link on another forum? i know of a couple people looking for a backup aswell.
You should be able to switch back with the recovery no problem. Correct me if I'm wrong, but to install boot into recovery, install from SD, select specific, and select the zip of the rom. Also, I don't have my phone on me so the wording might be a little different.
MMS is a known issue with the rom from what I've read. I don't have it installed personally.
Click to expand...
Click to collapse
You can post it wherever you want. I'm glad I could help a couple of you!

ScottPomroy said:
Ok. Just one question is there anyway I can get the nice clock back from the stock ROM?
Click to expand...
Click to collapse
I haven't done this ROM change but if its the stock HTC Sense go to personalize and get HTC widgets (perhaps its get more HTC widgets) and you should find an update to the clock widget. That should give you the original clock plus a bunch more new ones.
Sent from my Transformer TF101 using Tapatalkd

Take another peek
Wieland959 said:
@brandonhun, Thank you so much. You're a life saver. As far as the rom goes, it still have sense on it and there are tons of MMS errors. So just wait and eventually something will pop up.
Click to expand...
Click to collapse
Guess what just popped out of the Betty Crocker oven? As close as I could get to stock. Enjoy.
Rob

[Q] Possible brick? Any ideas?

Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!

munson11 said:
Hey guys, I think I screwed up here and I'm wondering if anyone else has had this problem:
Basically, I had a rooted E4G Touch with a custom ROM installed. I went to install ANOTHER custom ROM THROUGH ODIN, as this previous ROM (I believe it was a Calkulin variant) did NOT have CWM recovery. During the ODIN process, something went wrong, and my computer/ODIN...basically, everything froze up while doing the MODEM portion. NOW I can't do anything.
- CWM was able to install on the thing...but it does not recognize my external SD card now. Every time I try to mount it, I get a "Error mounting /emmc".
- I'm still able to get into download mode on the phone, however the phone is not recognized on any computer I've tried. I've attempted multiple computers/USB cords and nothing picks it up.
I'm running out of ideas here. I picked up a USB jig that should be here soon, so I'm going to try that and reset the counter....which leads me to my next question: If I use that, can I take the thing back to Sprint and get a replacement? I have the insurance plan and everything, so if they won't take it back because of the custom software I guess I could always smash it or something...
Any help would be appreciated!
Click to expand...
Click to collapse
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?

assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium

barnacles10 said:
The ROM you flashed through ODIN was for this phone, right?
What custom ROM are you referring to that was available through ODIN?
Click to expand...
Click to collapse
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
JohnCorleone said:
assuming you flashed the right ROM, start with the basics..if you can get into download mode then try a simple reboot of your computer. Sometimes Odin won't recognize after it has been run
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
Click to expand...
Click to collapse
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.

barnacles10 said:
The only odin component involved with flashing CM9 is flashing a gb kernel with a CWM recovery. I haven't seen a cm9 tar, this is why I'm confused. Finding out exactly what you flashed will help in understanding what the problem is.
To flash cm9 you need to odin a gb cwm kernel and then boot to recovery and install cm9. However, that's not a tar, its an update.zip.
Click to expand...
Click to collapse
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.

munson11 said:
It was the CyanogenMod 9 rom that is out there right now. IN the post (I'm having trouble finding it as I'm not at that computer right now) they had an ODIN variation for people such as myself, where you were to flash that and then go back through to update it to the latest version.
I attempted this as well Went through and rebooted the computer with the phone plugged in. Rebooted with it not plugged in. Plugged the phone in with ODIN on the screen and started it up. Started it up unplugged, went into download mode on the phone, and then plugged it in. Still nothing.
And I just realized I posted this in General and not Q&A...and chance I could get this moved since I am clearly out of my mind right now?
Click to expand...
Click to collapse
Maybe you should post the link to exactly what you were flashing...

http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium

munson11 said:
Yeah it was definitely a tar.md5 file, which leads me to believe I was incredibly dumb and possibly flashed a ROM for a different model phone. I'm having difficulty finding the post now which is very strange. This could be one of those moments where I take a good hard look in the mirror and figure out just what the heck I was thinking.
I'll keep looking for what exactly I did wrong, but in the mean time is there anything else I could attempt or look for short of attempting that USB jig and making a trip to Sprint? I'm feeling like a huge idiot right now. I've done this how many times now and when I finally make a mistake, it turns out to be huge.
Click to expand...
Click to collapse
Well ultimately you can try uninstalling / reinstalling drivers. But you say this issue exists across multiple pcs so that likely isn't it.
You can try another cable and see if you have any success with that.
Other then that, it kinda really depends what is in that tar you flashed. Once you find it, post the link, and that will help troubleshoot your issue.

playya said:
Maybe you should post the link to exactly what you were flashing...
Click to expand...
Click to collapse
lballer69 said:
http://www.addictivetips.com/mobile/cyanogenmod-9-galaxy-s-ii-download/
Please tell me this isnt what you flashed.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(

munson11 said:
Haha I am a freaking idiot. How in the heck did I manage to do this...I definitely flashed this: http://forum.xda-developers.com/showthread.php?t=1419102
I do not know what was going through my head last night...but it was not any sort of smart thoughts. A rope and a sturdy tree are what I require at this point, correct?
Whatever insults you guys would like to throw at me, I will take. I clearly deserve them :'(
Click to expand...
Click to collapse
Did you flash the bootloader from that device? ie did your steps include this? \/
Make sure you're running ICS bootloaders lower than LPH: Download (flash as PDA with odin or extract and $ sudo heimdall flash --primary-boot boot.bin --secondary-boot Sbl.bin)
Click to expand...
Click to collapse

barnacles10 said:
Did you flash the bootloader from that device? ie did your steps include this? \/
Click to expand...
Click to collapse
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.

Ha ha that's the first one for this method......look up jtag they may fix it for u if u don't have USB .... About 60 with shipping
Sent from my SPH-D710 using Tapatalk 2 Beta-5

munson11 said:
Negative, I started right at the "Using the noob-proof ODIN method:". It said noob-proof and I decided that would be the easiest. It turns out it is very easy...if you're flashing to the correct phone Plus, I'd used ODIN before and felt comfortable with it.
Click to expand...
Click to collapse
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.

barnacles10 said:
I just downloaded the tar to have a look at whats included.
After flashing this you'll have a bootloader for the intl. sgs2. This is a problem many ran into when original SGS2 leaked tars started surfacing as well.
JTAG might be able to fix it, I'm not sure whether people with this issue were successful or not with JTAG repair as the intl gs2 flashing boat seems to have sailed now. However, a jig will likely do nothing, unfortunately.
Click to expand...
Click to collapse
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.

munson11 said:
Ok thank you for your help on this. You don't think a jig will reset the counter or anything so that I can take it back to Sprint? If not, I'm not above "dropping" it on the ground and using the insurance I have on it for a replacement.
Click to expand...
Click to collapse
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.

barnacles10 said:
I don't foresee it working only because your phone isn't recognized by your pc and the problem doesnt lie on the pc side.
The problem is instead with the port on the phone which leads me to believe it won't recognize a jig either.
A jtag if successful will leave you with more money in your pocket and a non-returb. Something to consider if you've got a backup phone you can use for a few days.
Click to expand...
Click to collapse
I don't see sprint replacing it with cm9 On it .... And u will need mobile Odin to get back to stock but with it not mounting the Emmc probably can't do that .... That is your hope to get back to stock using mobile Odin someway .... Triangle away app will reset Odin count but with no radio you need to get apps to do it and no sd from what u said ...maybe tell insurance u lost it and get it replaced
Jtag should work also since there is no emmc failure like the blue light of death bricks ...
Sent from my SPH-D710 using Tapatalk 2 Beta-5

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

[solved] Does T999UVDMD5 lag on your phone?

It all started here:
http://support.t-mobile.com/thread/44716
I griped on the T-Mobile forums about the struggle I've had in finding a smooth ROM for my T999. And I made an off-handed comment in another thread that got me pointed in the right direction hopefully. I'm looking for other T999 owners that have this problem.
The problem on DMD5 is all related to (apparently) intensive tasks. Playing games, mostly. Temple Run 2 and Fruit Ninja, neither of which are all that intensive, were nigh-on unplayable. Other games like Scramble with Friends would lag and stutter a bit, too. So after a lot of searching, I reverted to a pre-rooted T999UVDLJC with the matching baseband, so that way my phone doesn't try to update itself OTA. And performance is pretty good. But I'd like to think that I'm not alone, and I found I'm not alone in this thread:
http://forum.xda-developers.com/showthread.php?t=2326763&page=33
At the bottom of this page and the top of the next one, I found at least one kindred spirit that has a rev0 phone and has the same issue with DMD5.
NO other ROM has this issue. I've tried all of the official Samsung ROMs and I have tried official CM10.1 nightlies and the official 10.1 stable release and performance is very good on all of them. But it took a huge serious nosedive on T999UVDMD5.
So I'm curious about two things:
Does DMD5 run well on your phone? Particularly with games - that's where it was most notable, but even TWLauncher is laggy for me.
How old is your phone? According to the box for my phone it was built 6/30/2012.
If you are affected, could you help us all out on the T-Mobile support forum, and post a message in my thread at the top of the page? If we can get T-Mo and/or Samsung to look into it maybe we won't get left behind. I plan on using this phone for another year or more and I'd rather get the official updates in the future, too.
Update July 6, 2013: I found out thanks to help from people in this thread that I can run mismatched modem firmware/ROM and with the JLC modem on MD5 ROM, my phone runs fantastic. Or at least it has for about 2 hours - usually issues have shown themselves by now, and since they haven't cropped up I'm calling this resolved.

When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium

Please do not check "yes this is a question" if it is "info gathering" as all Q's are moved to Q&A. I will edit the title for you.
FNM

DocHoliday77 said:
When you were on MD5, how did you update to it? OTA? Odin? Recovery flashable ROM?
And how much data have you been carrying over? (When did you last wipe data/factory reset, without restoring backups?)
Sent from my SGH-T999 using xda premium
---------- Post added at 01:03 AM ---------- Previous post was at 12:50 AM ----------
Btw, I'm on MD5, completely stock right now. Hw is Rev. 0
I get very little lag, if any, ever. Simple games or even intensive games run very fluidly for me.
For example, I just got Man of Steel when it went on sale and it works almost perfectly. Disney, Gameloft, EA games have all worked just fine.
The only MD5 issues I've seen around here seem to occur when someone is using a mixed build with the MD5 radio. And then its only been reports of heat issues and slight battery issues. Haven't seen much of anything regarding poor performance.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I've tried all of the above. I even let Kies install it once. I've used TriangleAway and Odin to install 4.0.4 and let it do all the OTAs. Iv'e done factory resets and I've told setup not to restore my data to the phone and started from scratch. I used a flashable ZIP with the pre-rooted ROM, and when I did that I also got the DMD5 modem flashable ZIP to go along with it. I've tried not rooted. I've tried custom kernels, and I've tried stock. Odin completely stock and flashable zip totally customized. I've played with custom DMD5-based ROMs with the v6 script and I've tried not. I'm way out of ideas right now.
Sorry, @kennyglass123, I didn't realize I'd checked that box.
Starting to think all of them have "rev 0" for the CPU identifier, so that may not be the way to tell who has what.

Just to be clear, did you ever Factory Reset, then Odin flash MD5 (not mobile odin btw), and factory reset again to ensure internal sd was cleaned out too? If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Don't get me wrong. I'm not trying to argue against your point, just to make sure not only that you've covered all angles, but that anyone who wants to back up your claim has also done the same.
As for the revision number, it may still be relevant as mine would have been among the first built too. We would need to find at least several others with the same, and different, to know for sure if it matters here.
Its always possible too that you got the unlucky pick of the hardware. (Just as possible though that I got a lucky pick)
Anyway, if you really are having that bad of problems with it, you may want to check if its still under warranty. I don't believe its the norm though.
Sent from my SGH-T999 using xda premium

Yeah I'm pretty sure, but I'm willing to do anything at this point. I'll do it again. I've stashed the Odin tar.md5 file on my backup hard drive, so I'll back up my working config and flash it again. Worst case scenario is that I re-root it, re-install recovery, and then restore my backup. Should take an hour max.

Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Use the root66 version of the firmware. Its pre rooted and is what I am running right now. Root alone won't have any negative effect, but will allow for much better troubleshooting.
Aside from that, keep it as clean from restored data as possible. Even a single corrupted contact entry can cause services to hang and eat up resources. I wouldn't even flash a recovery until you're ready to restore something.
(I use Mobile Odin Pro and it almost completely replaces the need for cwm or twrp. The only thing it can't do yet is make a nandroid backup.)
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.

Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
DocHoliday said:
If for MD5, you only flashed the Rom and Modem, you would have been on a mixed build. Also, many devs suggest waiting an hour before starting with any testing or reconfiguring. I'm not convinced this is always necessary, but they do usually kno more than me!
Click to expand...
Click to collapse
There is no possible way it could be necessary. Proof or it's placebo.

DeerSteak said:
So the root66 is an Odin image? I assume you're talking about this: http://forum.xda-developers.com/showthread.php?t=1771687
I've got it downloading now. Thanks for all your suggestions. I've not heard of Mobile Odin Pro, is it a custom recovery?
Click to expand...
Click to collapse
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
DeerSteak said:
Whoops - found the Mobile Odin thread on XDA and got the lite version and the T999 flashing kernel. I'll give it a go.
Click to expand...
Click to collapse
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Yes, root66 is basically just 100% stock firmware, only rooted. Itll download as a .7z file. Just extract it and use the .tar.md5. You have the correct thread.
Mobile Odin is one of my all time favorite apps. Its from Chainfire if you are familiar with him. (SuperSU)
Its not a recovery exactly. What it does is reboots using what's called a flash kernel. This allows it to flash firmware like PC Odin, but also can flash roms that are made for recovery flashing. It doesn't replace the stock recovery like cwm/twrp either, so it also won't trip the flash counter. (I know that doesn't really matter with Triangle Away available (also by Chainfire)).
The only two drawbacks, (minor imo) are that it can't create nandroids, and it doesn't flash the FULL firmware (this is by design though).
I wouldn't bother with it right now, but definitely check it out after testing all this. Theres a free, lite, version here on xda. Ill send more info from my computer later.
Sent from my SGH-T999 using xda premium
---------- Post added at 11:51 AM ---------- Previous post was at 11:49 AM ----------
Don't use Mobile Odin for testin right now. It doesn't flash the full firmware.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.

Aerowinder said:
Regarding The AOSP MD5 issues: the same thing is happening to me on stock. Have to use LJC or the battery sucks. What are your reboot habits like?
There is no possible way it could be necessary. Proof or it's placebo.
Click to expand...
Click to collapse
I don't reboot unless the battery dies, or I was rebooting a lot when I was on MD5 trying to get stuff to work well. Generally I try not to mess with a good thing.

DeerSteak said:
OK awesome, I will check it out. I think what I'm going to do right now is just reset the flash counter, flash the Odin image, and then factory reset and set it up as a new phone. Does that sound reasonable? If I reboot into CWM after triangle away, it trips the flash counter again, at least that's what it seems to do, so I can't do anything other than reboot to download after Triangle Away.
Click to expand...
Click to collapse
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
That sounds fine. Remember, if you factory reset with stock recovery installed, it will wipe internal sdcard.
As long as you have cwm or twrp, the flash counter will always be at 1. I wouldn't worry about that for now though. It won't affect overall operation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
OK, I won't mess with it too much then. I've backed up my internal storage already and I've backed up my SMS using SMS Backup and Restore. That thing has been very handy keeping copies of my texts while I screw with this.

Cool, sounds like you're good to go! Good luck! And let us know how things seem to be acting after flashing.
Don't forget to factory reset after flashing md5.
:thumbup:
Sent from my SGH-T999 using xda premium

OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.

DeerSteak said:
OK I got as far as the factory reset and then it was time to paint. My daughter's bedroom wasn't going to paint itself. I finally came back to the phone and it was patiently waiting for me to log in. I logged in and installed just a couple apps while I ate lunch, and then it sat until we were done painting and cleaning up. Logged into Facebook and Twitter, set up Google Now and updated Samsung apps. Once all that was done, I fired up Temple Run 2 and it was OK at first, but within 3-4 minutes it was choppy and laggy again. The phone never got warm to the touch. It just ran poorly. I exited out and killed all apps with the built-in task manager, and went back to the game. Not really any better. It's just super choppy. I even turned down all the graphics options in the settings for the game and that made zero difference.
Eventually I gave up. Restored my 4.1.1 backup, fired up some stuff, performance was great. It's just the combination of my phone and that software. No idea what it is at this point. I do appreciate all the assistance you guys have lent me.
Right now I'm on T-mo and was waiting out the 60 days before I ported my wife's number in to my account. Now that that's over, I'll eventually port in her number. She's extremely happy with her iPhone 4s and insists she's not interested in an iPhone 5, so what I'll probably do is use the ability to get new hardware as an excuse to get a Galaxy S4. WHen I first came to T-mo I just got a SIM and bought the phone used - found out later on that I should have just bought a phone through T-mo because I can't get a new phone on a payment plan for a year unless it's as part of a new line. She'll be a new line, so I'll get a phone.
This hasn't put me off on Samsung or even on the GS3 - it's just my phone has a weird issue of some sort. And the people here have been super awesome. Thanks tons for all your advice. In the meantime I'll run JLC and leave well enough alone.
Click to expand...
Click to collapse
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.

Aerowinder said:
Before you give up, try debloating your install. I will PM you a link to the one I made. Backup first.
Click to expand...
Click to collapse
OK i'll give it a go. Thanks.
Should I re-flash the MD5 modem?

I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.

Aerowinder said:
I'd flash the LJC firmware, Third firmware link in my sig. LJC link is buried in the OP.
Click to expand...
Click to collapse
OK I see it there. So I should use the LJC modem/firmware with the DMD5 debloat ROM you're going to PM the link for to me? Will they work if they're mismatched? I assumed (not that I'd bothered asking before) that they'd all have to be the same.

[Q] Factory reset in CM12 now stuck in recovery boot loop

So I'm just getting into the whole ROM thing and I'm pretty sure I've messed up here. I encountered a problem after installing CyanogenMod 12 Unofficial (trltespr NIGHTLY) where I could receive text messages but not send them. I could still load pages and apps over lte and call people but I couldnt send messages. I gave up with the idea of finding a solution after browsing forums and decided to preform a factory reset through settings. The phone was rooted but not after I installed the rom. after rebooting it went into recovery mode and began to loop showing the Team Win screen then going black only to do it again. I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.

diehlkj said:
I removed the battery and booted the phone into download mode and it is now sitting here connected to my computer with Odin up ready for whatever it is that I need to do to fix it. I have absolutely no idea what to do. Help is very much appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.

xxSTARBUCKSxx said:
http://forum.xda-developers.com/note-4-sprint/general/stock-n910pvpu1anie-stock-tar-t2944867
Go there and download the BOB7.tar and flash that.
Click to expand...
Click to collapse
I went and followed the instructions and odin said it failed due to auth. Any other ideas?

diehlkj said:
I went and followed the instructions and odin said it failed due to auth. Any other ideas?
Click to expand...
Click to collapse
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.

xxSTARBUCKSxx said:
A couple but i dont think i can throw my laptop that far.
Youre an OE1 victim and Good Luck in your endeavors until a .tar comes out.
Search The Q&A threads pertaining to OE1 and see if you can manage to come out with a successful gathering of info and get back your phone.
Click to expand...
Click to collapse
Is there any way I can remove or reinstall/repair TWRP so i can properly wipe the system or just get another rom working?

Solved
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Then you can flash notarize rom per that threads first post... Until an updated tar that will work in Odin.
http://forum.xda-developers.com/showthread.php?p=60506568

diehlkj said:
Ok so I did some searching and didn't find any definitive answer as to how to fix this. Finally, figuring I couldn't mess this up any further I went into odin and re-ran the CF Auto Root. It rooted successfully and the moment it rebooted it loaded me back into Cyanogen. None of my settings were changed and everything was how I left it. As for my message problem they still wont send but at least I got my phone back. Thanks for the help as I'm now going to restore to factory settings so long as my recovery is working.
The reason rooting it fixed the problem is because it restored the factory recovery and I can now reinstall TWRP
Click to expand...
Click to collapse
Yep, the trend seems to be pointing to CF Auto Root after trying to flash stock tar over OE1 build. Although I'm thinking the stock recovery is from way back unless CF updates his build.
About the text sending issue, did you apply the fix found in link below? Check under the spoiler.
http://forum.xda-developers.com/showthread.php?p=57613217
If you want to get back to TW, Noterized is a good OP option. (As mentioned above)
Sent from my SM-N910P using Tapatalk