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

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

Sudden Boot Loops - I'm Lost

I've been using my Galaxy Nexus for a month or so, with the official JB ROM (JR30C or whatever, deodexed and rooted) and today I opened Gmail.
That's it. I opened GMail, switched accounts, and my phone has been bootlooping ever since.
I wiped everything in CWM multiple times and reflashed it, and I can't get the phone to do anything else.
Any clues?

Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y

Xfanatic said:
Do you have a working nandroid? Have you tried flashing a different ROM?
Allons-y
Click to expand...
Click to collapse
I do not have a working NANDROID. I wasn't sure about the Internet policies at work, but it looks like I can at least make it on here, I'm not sure I'll be able to download another ROM.
I'm confused though, I mean I know it would help to try as many options as possible (to fix it) - but this ROM has been working for weeks. And the phone died randomly, not due to a recent file change or a botched program. The only boot loops I've experienced before were on the Nexus One, and it was always due to a buggy/bad flash or a corrupted ROM download - this one just developed epilepsy on its own...

Here's my plan, since these are the only things I can manage to download due to restrictions on Internet usage at work.
Factory 4.1.1 takju image from here : https://developers.google.com/android/nexus/images#takju
Modified ODIN software here: http://forum.xda-developers.com/showthread.php?t=1586807
ODIN won't rewrite my bootloader, recovery, or userdata, since I already OEM unlocked, but will reflash a stock image.
EDIT: ODIN won't do anything with my device. Trying this ROM instead:
http://forum.xda-developers.com/showthread.php?t=1801664 was using bigxie OTA before.

is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.

Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2

simms22 said:
is your (sd)storage recognized? thus is a similar symptom to when the stirage goes bad.
Click to expand...
Click to collapse
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
infazzdar said:
Hook the phone up to adb, boot it, and let logcat run. Maybe that will turn something up.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I'm at work, and I only have my work computer. Group/secpolicy won't allow me to install anything, no admin rights, etc.
Would it even do anything? The phone barely makes it through one second of the boot animation before it loops.

sheik124 said:
Hmm, you know, I'm not able to find the option to mount to USB in CWM...and just in case I forgot where that is, when I plug it in, I get the "hardware failed" noise from Windows and not the usual friendly "plug in" sound.
Click to expand...
Click to collapse
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
Oy. Then how do I get another ROM on here? fastboot/adb?

sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Adb push.
Sent from my Galaxy Nexus using Tapatalk 2

Zepius said:
you cant mount the sd card. there is no USB mass storage period. not in recovery or booted normally.
Click to expand...
Click to collapse
sheik124 said:
Oy. Then how do I get another ROM on here? fastboot/adb?
Click to expand...
Click to collapse
Got more than one additional ROM on there via adb/recovery - my clue that CWM hasn't actually been able to do anything since the phone start looping is I'm still getting my custom boot animation.
I'm using the toolkit to reflash a stock image now. What a mess.
Even reflashing a stock image via fastboot did nothing. WTF happened to my phone? Won't stay on long enough to get a logcat

I'm having the same problem as this guy:
http://forum.xda-developers.com/showthread.php?t=1827685&page=2
I just got finished trying to flash 4.1.1 using ODIN. It still shows me the custom animation from bigxie's ROM (which has supposedly since been overwritten 2-4x times).
Screw you Samsung...this phone is a month old, I flashed -once- to rooted Jelly Bean, and the phone dies when I open the GMail app.
EDIT: WTF - I write screw you Samsung, it boots to the Welcome screen! Just long enough for me to see that my files aren't on it anymore, then it bootloops again. And again. Now it's re-stuck in a bootloop.
And now I'm at the homescreen. I can't rely on this thing like this...is my flash dying or something?

Nobody?
It worked long enough for me to re-enter all of my different Google account information and now it's dead again. Now it only flashes the boot animation for a split second for bootlooping.

I'm thinking of a hardware defect.
Beamed from my Grouper

Mach3.2 said:
I'm thinking of a hardware defect.
Beamed from my Grouper
Click to expand...
Click to collapse
Mee too. As you can see from my signature, I gave up and bought a One S yesterday night from Craigslist. Feels like a true successor to the Desire / N1. It's nice to finally have an AMOLED screen that actually seems color calibrated after the ugly mess that was my RAZR and my less than perfect GNex. It's a damn shame how much more painless flashing a recovery was on this thing.
Sent from my HTC VLE_U using xda app-developers app

Constant Reboots!! PLEASE HELP!!!!

Hi guys,
I am using a Sony Ericsson Xperia Arc and am having a lot of trouble with the device constantly crashing and rebooting.
when this first happened these are the steps i took.
i completely wiped the device (factory reset, wipe dalvik cache, wipe cache partition, format system)
i then flashed Baseband 77 using flashtool
i then flashed fxp149 using flashtool
i then flashed Baseband 77 libs using CWM
i then flashed AOKP JB M1-R1 ROM using CWM
i then flashed gapps using CWM
i the reloaded all apps from the market and not applied any backups and yet it still rebooted all the time.
Since then i have tried using
Fusion 3.8
Fusion 3.9
Fusion 4.0
FXP 148
FXP 150
Stock Kernel inside ROM .zip file.
I have also tried putting it back to Baseband 72 but it made no difference.
None of these make any difference to my issue and yet before i had the issue, I had used all of these kernels except FXP 150 and they all worked fine with no issues at all.
I then decided to go all the way back to stock firmware as it is out of the box.
so I used flashtool and flashed LT18i_4.1.B.0.587_(1254-2716).ftf
I reloaded my applications and monitored the device only to see that by the next day, the problem had returned.
I am now at the end of my tether and do not know what else i can possibly do to figure out the issue.
the device has not been dropped or damaged in any way so there is no reason for a hardware fault.
i desperately NEED this device to be working as i use it on a daily basis for my business and cannot live with out it.
IF THERE IS ANYONE OUT THERE THAT COULD PLEASE PLEASE PLEASE HELP I WOULD BE FOREVER IN YOUR DEBT!!!!!!!

i also have a logcat that i was running in the background when one of the reboots happened
not sure if that can tell anyone anything but i have it if it does

First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before

have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay

Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.

XperienceD said:
Could be a loose battery, try a bit of paper between the battery and the cover and see if that helps.
Click to expand...
Click to collapse
thanks for the suggestion but my battery is not loose and i have tried your method but with the same results.
weaselmetal said:
have you tried not to restore your apps? Maybe one of them causes the problem. I'd try to stick with the clean (stock) rom an check if it still reboots. If it does I guess your device is ready for ebay
Click to expand...
Click to collapse
hmmm i thought if that were the case there would be others experiencing it too.
i will take your idea and post results.
thank you very much
rod555 said:
First flash stock kernel (587), after flash the rom compatible with kernel. Remember full wipe before
Click to expand...
Click to collapse
i tried this, unfortunately i had the same issues occurring.
thank you for your suggestion

Needs a trip to the Service Centre then by the sounds of it.

XperienceD said:
Needs a trip to the Service Centre then by the sounds of it.
Click to expand...
Click to collapse
yes i am starting to think that may be my next move
will i have an issue with getting it repaired since i have unlocked my bootloader, flashed different kernels and roms and rooted the device?
if so, is there any way i can get it back to official "out of the box" state?

Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium

tangosierra_ said:
Flash a stock ftf and get the bootloader relocked. Having it rooted is fine
Sent from my lt18 using xda premium
Click to expand...
Click to collapse
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?

plastic_prophet said:
any chance you could explain a little about how to do that or possibly provide links to downloads or pages of instructions?
Click to expand...
Click to collapse
Here:- http://forum.xda-developers.com/showthread.php?t=1324703
Sent from my LT15i using xda premium

i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always

plastic_prophet said:
i have come across something quite interesting.
i had someone look at the logcat i had running live when i had a reboot and it showed that the last thing to function before the reboot was wifi scanning. they suggested i try turning off wifi and running the live logcat again to see if any reboots occured.
it has now been just over 48 hours and i have not had a reboot at all. i know is because my terminal session is still running the live logcat.
is there anyone that could suggest why this may be happening?
i mean, i know its wifi that is causing the problem, but would that be a hardware issue that could be fixed under warranty? or something else?
any suggestions are appreciated as always
Click to expand...
Click to collapse
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.

lalek said:
i don't think i can help, i just wanna say that i had (have) the same problem. I said had/have because probably I still have the issue, but i don't notice it that often. Before, I had my phone set to ask for pin code, but now I have removed it to avoid being unreachable if a restart occurs. I have raised the issue long time ago, but really didn't find any answer. Other ppl had same problem with their phone (look at the thread i started about this issue http://forum.xda-developers.com/showthread.php?t=1765537)
I also have HTC desire in daily use with CM7.2, that also reboots quite often. So I don't think the phones are broken. More likely it's kenel or rom or app issue, or some combination of those.
If you can tell me how to monitor things, I can do it on both phones, maybe we will figure out what's going on.
Click to expand...
Click to collapse
if you open a terminal session and type:
su
cd sdcard
logcat >> logcat.txt
it will create a .txt file and put the live logcat info into it.
you need to leave the terminal running in the background to make sure it continues to update
then when you see a reboot just get the logcat.txt file from the sd card and open it in wordpad or something. (notepad doesnt display properly)
have a look at the last thing that happened before the reboot and see what it tells you
mine had info about wifi scanning and showed that it had seen ssids
next step was to turn wifi off to see if the problem stayed or resolved.
good luck!! id love to hear how it goes

Random Reboot and Random Black Screen

Lately I have been getting random reboots and random black screens. The phone will either reboot itself show the galaxy s3 screen then go to complete darkness or vibrate and go straight to complete darkness. This seems to be random and usually starts happening a week or so after flashing a rom or kernel. Right now I am using my own TW rom (in dev section) with kt kernel and team kernalizer scripts. But the kernel doesn't seem to matter as this happens regardless. Does anyone know whats going on? Also this started happening after I ran aokp 4.2.2 for awhile, then odin back to stock and issues started. I've also been having less battery life since then.
Someone please help

anyone?

aamir123 said:
anyone?
Click to expand...
Click to collapse
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.

Aerowinder said:
Running stock Odin may be an option, but here is what I would do first.
Flash the LJC firmware from the second firmware link in my signature. It's in the OP, but isn't immediately obvious. Just scroll a bit and you will see it.
Stop using KT and tkmod for now. These, simply put, are variables that you don't need to deal with right now. There is also a good chance it's a bug in your ROM.
Click to expand...
Click to collapse
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?

aamir123 said:
Before I went to aokp I was using my rom very stably for a good while and others have been using it without problems, but I agree going to least common denominator (stock rom/kernel) sounds like a very good idea. I'll also flash the ljc firmware even though I haven't really had any problems with the 4.1.2 one.
Btw why ljc and not md5?
Click to expand...
Click to collapse
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.

Aerowinder said:
Because it's somewhat likely the MD5 firmware is causing your problems. I can't use it on my phone, just kills battery. Maybe your phone has a more severe reaction to it.
Click to expand...
Click to collapse
ok I guess I'll go back but I don't see why the md5 firmware would be a problem now after I was using it with no problem for a while.

Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app

DocHoliday77 said:
Unless you are running 100% md5, it has been known to cause some issues. Seems a lot was done on that update from 4.1.1 - 4.1.2, and it doesn't always like to be mixed with older fw.
Sent from my SGH-T999L using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well I flashed the LJC fw and so far it's been pretty stable, only having trouble with excess heat but will probably get better with time. Also I'm having trouble getting a logcat app running (catlog etc). The app opens I give it root permissions, then I get a black screen with loading ring. No log whatsoever, is that normal? tried on both fw btw.

just got another random reboot on ljc fw. any other ideas?

aamir123 said:
just got another random reboot on ljc fw. any other ideas?
Click to expand...
Click to collapse
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.

cboss718 said:
Just a heads up, my phone was doing this for about 3 days, and then completely crashed. Check out my thread. Stock Rom, but rooted. Hope it doesn't happen to you.
Click to expand...
Click to collapse
Idk what the issue is I'm gonna go stock for a while without recovering and see if that will fix anything, if not maybe tmobile is the way to go. Btw I tried taking a log cat but get error saying that dev/log/main doesn't exist.

Ok I was doing good for a few hours after flashing stock and not restoring Google account until I got a random reboot just now. I was able to get a log cat tho so I'd anyone can look at it and help.
Sent from my SGH-T999 using xda app-developers app

anybody? Does anyonehave any ideas?

aamir123 said:
anybody? Does anyonehave any ideas?
Click to expand...
Click to collapse
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.

Aerowinder said:
That logcat contains 30 seconds of information. Looks like you pulled it after the device rebooted. It's probably going to be the kernel dmesg that we need. You get that one after the device reboots, but not the logcat.
Click to expand...
Click to collapse
ok I will try to get that the next time it reboots. Hopefully it's a simple fix, but just not sure what the problem could be.

So I went all these days without a random reboot and finally got one today, but was unable to pull a dmesg as it said does not exist. What can I try to get a dmesg now?
Also the phone feels like it never shuts down, even when I choose to shutdown in the menu it ends up restarting itself then bootlooping or just restarting. I've also noticed that holding home and power to turn phone on works most of the time to get it back to the os only to have it crash shortly after. I press home and power until I see the white splashscreen then let power button go. but staying in os for more than a few mins right now is impossible.