Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
BreatheHT said:
Tried different ROMs & kernels, tried wiping everything and re-flashing, tried flashing the latest RUU(including firmware), changed recovery, did everything I can, the dialer still FCs when I try to make a call.
Driving me crazy.
I used different recoveries as well. TWRP & CWM & Stock after RUU flash.
I do remember using CWM recovery though, but it is the official one.
Click to expand...
Click to collapse
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Mister J said:
Well, I don't think a kernel could have anything to do with it. I think you need to backup your ROM. Then go into recovery and wipe system. Then flash the stock AT&T rooted ROM with nothing else, then try.
Click to expand...
Click to collapse
i've tried everything like mentioned in the original post.... EVEN RUU
BUT AOKP roms works fine.
I'm started having the same problem this morning on every single sense ROM that I tried. I finally had to flash CM because I needed to call someone. RUU, wiping everything, different radios and different recoveries, nothing worked.
Sent from my One X using xda app-developers app
tried everything possible -_-
NobodY??????
I'm going to try a few other things when I get a chance, hopefully tomorrow. I would like to get this solved.
Sent from my One X using xda app-developers app
BreatheHT said:
NobodY??????
Click to expand...
Click to collapse
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
area51avenger said:
If you ruu and the problem still exists then its hardware related
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
sweeterman said:
If it's hardware related then why does the dialer work perfectly with CM?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yep it can't be hardware.
Have you checked HTC for a bug update? I know they have had these problems in the past. Might not hurt to check.
Sent from my HTC One X using xda premium
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing... And I don't really have a good backup...
redpoint73 said:
This sounds a heck of a lot like the issue that cropped up with the old hacked (unofficial) version of CWM, way back last summer. It seemed that going from CM to CleanROM using CWM was the root cause (although I don't think the exact cause was ever discovered), and the oddest thing is that flashing different ROMs and even RUU didn't solve the issue. It was pretty much the event that got most of us to swear off the unofficial CWM, until it finally went official this month.
I think (but this is digging deep in my memory banks) some folks were able to resolve the dialer FC issue by going back to a known good CWM nandroid, then I think going to TWRP after that, and flashing a new ROM. But you might use the search function to find the specifics.
Might be something different going on here. But the persistent dialer FC (even after RUU) combined with CWM and CM10 is looking a bit suspicious.
Click to expand...
Click to collapse
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
BreatheHT said:
Should I flash CWM again? Because last time for some reason CWM Touch(official) stopped working for no reason(cannot get into recovery, screen flashes and reboots) so I flashed TWRP again, and I think that's when the problem began to show.
Click to expand...
Click to collapse
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
BreatheHT said:
Should I flash CWM again?
Click to expand...
Click to collapse
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
BreatheHT said:
Yeah I've read threads and posts having the same problem.... But I've never used unofficial CWM that's the weird thing...
Click to expand...
Click to collapse
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Good to know...I was thinkin bout flashing CWM, but I guess if I haven't had issues with TWRP, "don't fix what ain't broken."
Sent from my now S-Off HTC OneXL
redpoint73 said:
I'd say it worth a try.
---------- Post added at 10:35 AM ---------- Previous post was at 10:33 AM ----------
I don't think it was ever properly discussed whether whatever caused this bug in ythe "old" hacked CWM was resolved (or not an issue) with the "official" CWM. Not trying to knock CWM, and those that worked hard on it. Its just been a lingering question in my mind since it went official. But I'm also a skeptic by nature.
Click to expand...
Click to collapse
Thanks bro
sweeterman said:
I installed the latest CWM and flashed the rooted att 3.18 rom the dialer now works now. I don't know if there is a bug that once you use CWM, you can't use TWRP. It seems very odd though.
Click to expand...
Click to collapse
Will try, thanks bro!
elfysrfr said:
Maybe try an older version of TWRP, if youre on one of the newer versions. I've heard a LOT of ppl having issues with the 2.4.x.x versions.
Sent from my now S-Off HTC OneXL
Click to expand...
Click to collapse
I'm using 2.3.x.x haha 2.4.x.x is so bad... Or not compatible...
Related
hello,
i've been trying to get my mt4gs to turn wifi on in ics. when i turn it on it says, "turning on" but just goes back to "off". i tried turning it on via settings and via the panel. i do a full wipe every install -reset data, clear cache, wipe dalvik cache. also not sure if it's related adb cannot detect device when booted but works fine in recovery when in ics.
i've read and tried the various .zip files for various radio/kernel posted by football but still no go. i may be overlooking a step when flashing but here is my device info:
CWM Recovery version 5.5.0.4 also used 5.0.2.7
Baseband: 11.59.3504.00U_11.16.3504.20_2
HBOOT: Unlocked
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.0013
RADIO-11.16.3504.20_4
Nov 21 2011
it works using gingerbread - tried OTA Stock, as well as bulletproof and it connects ok, but i need to turn wifi off first if i need to reboot otherwise i get the same issue, wifi won't turn on.
sorry for the long post, and forgive me if i missed an already existing thread. thanks for reading. any help is greatly appreciated.
well what rom are you using
I had the same problem with certain ROMs. Sometimes it would even say instead of switching back to off it would just say error. I used Dark Raider for Vivid and had that problem. I did everything and gave up. I downgraded my vivid to GB and rooted it. WiFi is an essential to me so I have to stay where I can switch it on. I hope there's a fix for this soon.
Sent from my HTC PH39100 using XDA
xmc wildchild22 said:
well what rom are you using
Click to expand...
Click to collapse
i tried your rom, |-ROM-|-4.0.4-|-AOKP-B38-|-CM9-|-6/9/12-|-BETA-|-WildchildIcE-v0.8-|-Nightlies-|
this,
[ROM]MyTouch4G Slide CyanogenMod 9 Alpha 4 (06/08) - 4.0.4
haven't tried anything else, unless you have any recommendations.
Chavisca1 said:
I had the same problem with certain ROMs. Sometimes it would even say instead of switching back to off it would just say error. I used Dark Raider for Vivid and had that problem. I did everything and gave up. I downgraded my vivid to GB and rooted it. WiFi is an essential to me so I have to stay where I can switch it on. I hope there's a fix for this soon.
Sent from my HTC PH39100 using XDA
Click to expand...
Click to collapse
that's what i've encountered with ics, on gb, if i forget to turn wifi off before rebooting, my wifi will just say error. so i end up having to master reset too.
thanks for the reply.
when you flash a rom, are you restoring a backup in titanium or something?
i have never had this problem and i have tried every rom on xda and rootzwiki
I've had this happen too. I've fixed it by using fastboot and flashing the boot.img from the ROM or Kernel update that I had last installed. My phone is s-on so I have to do that everytime I apply a ROM or am update that has a boot.img in it.
xmc wildchild22 said:
when you flash a rom, are you restoring a backup in titanium or something?
Click to expand...
Click to collapse
no backup, i'm doing the install fresh
mattlowry said:
i have never had this problem and i have tried every rom on xda and rootzwiki
Click to expand...
Click to collapse
and i wish i was in your situation, since it looks like a mixed bag for mt4gs owner, some get it some don't.
txmtb said:
I've had this happen too. I've fixed it by using fastboot and flashing the boot.img from the ROM or Kernel update that I had last installed. My phone is s-on so I have to do that everytime I apply a ROM or am update that has a boot.img in it.
Click to expand...
Click to collapse
i tried doing that as well, my phone is S-OFF.
It was really frustrating for a while. It was the exact symptom you have described. I kept trying by flashing the kernel with fastboot, then flashing the ROM, and then flashing the kernel again with fastboot. It seemed that whenever I changed something, I had to use that sequence to get it to work again.
txmtb said:
It was really frustrating for a while. It was the exact symptom you have described. I kept trying by flashing the kernel with fastboot, then flashing the ROM, and then flashing the kernel again with fastboot. It seemed that whenever I changed something, I had to use that sequence to get it to work again.
Click to expand...
Click to collapse
i think i will try this method. i'll try with the previous roms i've posted first. i'll post my results later today.
Update
Wifi still no go using ICS. Is there a recommended radio version when using ICS ROMS?
Any stock GB Rom version wifi is ok. Using Bulletproof 1.1 works fine as well. Tried v0.9b WildchildICe and update4 of unofficial cm9 and still no wifi. Gonna stick with WildChildIce rom for now and try different Radio combinations.
d0nat0 said:
Wifi still no go using ICS. Is there a recommended radio version when using ICS ROMS?
Any stock GB Rom version wifi is ok. Using Bulletproof 1.1 works fine as well. Tried v0.9b WildchildICe and update4 of unofficial cm9 and still no wifi. Gonna stick with WildChildIce rom for now and try different Radio combinations.
Click to expand...
Click to collapse
U got the problem solved? I have exactly the same issue each damned time
When you flash, try mounting system and data in recovery prior to the flash. There used to be an error where wifi would hang as described if those were not mounted upon flashing. Couldn't hurt to try.
Hastily spouted for your befuddlement
tugushi said:
U got the problem solved? I have exactly the same issue each damned time
Click to expand...
Click to collapse
Try this. Go HERE. Go down to the 3rd post. Look for GanOptimizer & follow the instructions. No promises but sometimes that will lock it on in ICS.
Greetings guys. I'll skip the bs and tell you what my problem is. I just rooted 2.20 like everyone else and everything has been mostly fine but when I flash any JB ROM my WiFi doesn't work. I've tried flashing different stock ROMs in which the WiFi does work then wiping from recovery and reflashing jb but no dice. I've also tried fixing permissions and every other solution I've found via search.
Making a thread is a last resort as I know you guys are being flooded but any help would be much appreciated.
Try the 10/25 experimental nightlies CM10. Have heard this fixed wifi issues with most people
Any jb Rom? Are you having the same issue on aokp or miui
Sent from my HTC One XL using xda app-developers app
Does it say error? When I'm on jb I have to try to connect it like fifteen times than it finally does
Sorry about the delayed response. Was posting from work.
area51avenger said:
Try the 10/25 experimental nightlies CM10. Have heard this fixed wifi issues with most people
Click to expand...
Click to collapse
Ill try that out. Thanks
absolutelygrim said:
Any jb Rom? Are you having the same issue on aokp or miui
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Honestly I haven't tried those yet. That was probably gonna be my next step. I was just set on jb because you know, butter.
omario8484 said:
Does it say error? When I'm on jb I have to try to connect it like fifteen times than it finally does
Click to expand...
Click to collapse
I don't get any errors. It just doesn't pick up my router. Although when I disable all security on the router it picks it up just fine. A totally unlocked router is out of the question though.
StarGuitar said:
Sorry about the delayed response. Was posting from work.
Ill try that out. Thanks
Honestly I haven't tried those yet. That was probably gonna be my next step. I was just set on jb because you know, butter.
I don't get any errors. It just doesn't pick up my router. Although when I disable all security on the router it picks it up just fine. A totally unlocked router is out of the question though.
Click to expand...
Click to collapse
Are you sure you don't have SSID disabled?
try it using WPA/WPA2 security
absolutelygrim said:
Are you sure you don't have SSID disabled?
try it using WPA/WPA2 security
Click to expand...
Click to collapse
Yeah. I spent a good long while tinkering with my router and even factory reset it as well as tried every security type, changing ssid, hiding it, the works. My old iPhone picks up the router just fine, as does my laptop. This leads me to believe the problem lies with my phones ROM. I'm gonna try to flash a couple of the ROMs suggested to me once my phone charges.
So Ive flashed the experimental CM nightly released on the 25, MIUI v4, AOSP Nocturnal Dirty Rom 4.1 as well as AOKP JellyBean. Still nothing. Im sure I'm forgetting a couple too.
Don't really know what else I can do at this point. Ive tried different gapps packages too just in case that could be it. I might have to abandon all hope of running project butter right now. :crying:
Damn shame too, I really really like AOKP JB
StarGuitar said:
So Ive flashed the experimental CM nightly released on the 25, MIUI v4, AOSP Nocturnal Dirty Rom 4.1 as well as AOKP JellyBean. Still nothing. Im sure I'm forgetting a couple too.
Don't really know what else I can do at this point. Ive tried different gapps packages too just in case that could be it. I might have to abandon all hope of running project butter right now. :crying:
Damn shame too, I really really like AOKP JB
Click to expand...
Click to collapse
Are you on 2.20 firmware?
Did you wipe System and Factory Reset, then flash the Boot.img, then the ROM?
absolutelygrim said:
Are you on 2.20 firmware?
Did you wipe System and Factory Reset, then flash the Boot.img, then the ROM?
Click to expand...
Click to collapse
Yeah, that's the standard protocol Ive been taking with every ROM I flash, even ones of the same kernal type. Reboot to recovery>Factory reset>flash boot.img for that ROM>reboot to recovery and install.
I did a complete wipe system and everything just now and still nothing.
StarGuitar said:
Yeah, that's the standard protocol Ive been taking with every ROM I flash, even ones of the same kernal type. Reboot to recovery>Factory reset>flash boot.img for that ROM>reboot to recovery and install.
I did a complete wipe system and everything just now and still nothing.
Click to expand...
Click to collapse
And while on JB your phone doesn't see the router, or just unable to connect?
absolutelygrim said:
And while on JB your phone doesn't see the router, or just unable to connect?
Click to expand...
Click to collapse
It doesn't recognize it at all. Unless I completely disable any kind WPA/WPA 2 security. Back on stock unrooted Sense it would pick it up just fine though.
StarGuitar said:
It doesn't recognize it at all. Unless I completely disable any kind WPA/WPA 2 security. Back on stock unrooted Sense it would pick it up just fine though.
Click to expand...
Click to collapse
that sounds like a legit issue, you should probably report that to h8rift in the cm10 thread and see if anyone else has the issue.
out of curiosity what type/brand of router do you have ?
Update: Now running Cleanrom and everything seems to be working properly. I'm gonna stick with it for a little while until I can figure out how to run JB with wifi.
Crappyvate said:
that sounds like a legit issue, you should probably report that to h8rift in the cm10 thread and see if anyone else has the issue.
out of curiosity what type/brand of router do you have ?
Click to expand...
Click to collapse
That's a good idea for sure, I'll do that.
My router is a D-Link.
StarGuitar said:
Update: Now running Cleanrom and everything seems to be working properly. I'm gonna stick with it for a little while until I can figure out how to run JB with wifi.
That's a good idea for sure, I'll do that.
My router is a D-Link.
Click to expand...
Click to collapse
It probably won't help.. But have you tried updating the firmware?
I had an old D-Link and wifi worked fine on JB based ROMs for me.
a WBR-2310A to be exact
I've had the same issue in every aosp ROMs however on my phone i do get the WiFi to work. It takes me a while but I eventually get it. What I do I turn WiFi on and off, leave it off for a minute or so, re start my phone, after phone starts I turn WiFi on and most of the times it does it, you have to have patience
Sent from my One X using xda premium
Depending on ROM an kernel, WiFi scan intervals are up to 5 minutes apart.
Just saying.
WR
Sent from my One X
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Unrelashade said:
Hi guys,
I'm trying to find a Android 4 ROM/ Kernel that doesn't randomly reboot my MT4GS. So far no luck with CM 9.1 from scverhagen r8, r9b, r7b and the experimental 10a3, AOKP 4.2, CM 10 has been most stable of all so far but drains battery soo fast and also got me random reboots or shutoffs sometimes... The other ones usually reboot very fast after flashing. About 10 minutes after that, at least if the phone sits idle. Maybe when the phone is going to sleep or deep sleep? (Don't know what that is exactly)
Since these ROMs seem to be very stable with a lot of you guys, maybe I'm doing something wrong? I always wipe and format data and system and wipe battery stats and dalvik cache before flashing and don't use the phone for 7 minutes after rebooting... I have the newest radio I could find in the forums which is Radio 11.59.3504.00_11.16.3504.20_2
As always, your help means a lot to me and is greatly appreciated.
Click to expand...
Click to collapse
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
mattlowry said:
Are you still-off?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
demkantor said:
*s-off
mattlowry is getting at if you are s-on be sure to flash appropriate kernel after rom flash, also take a look into what apps you install, some are poorly coded and can lead to results similar as your own
Click to expand...
Click to collapse
Thanks guys! Fastboot says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
Click to expand...
Click to collapse
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Unrelashade said:
Thanks guys! Fastboot says:
That means I did everything right and phone is s-off, right?
And yes demkantor, I know some apps are problematic and cause reboots/ instability, however I recently tested without installing any apps to be absolutely sure, even without gapps and it still crashed/ rebooted.
I am still without a clue, even you guys don't have another idea? Haha I don't get computer stuff even after all these years...
Oh I got another idea. Maybe my battery is broken and because most kernels optimize battery use and undervolting etc, maybe this results in my phone crashing or rebooting? Also, maybe a reboot means a problem with the rom/ kernel and a crash (instant shut down) means higher propability for a battery problem?
Man I'm really desperate hahaha
Click to expand...
Click to collapse
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
mattlowry said:
Is it only with the experimental kernels or does this happen on stable kernel as well?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
demkantor said:
Most kernels probably wont have undervolting built it, and yes as your rev soff you dont need to flash the kernel seperate.
Battery could be a culprit but not a common cause, maybe pull a last_kmsg next time it happens
Sent from my HTC MyTouch 4G Slide using xda premium
Click to expand...
Click to collapse
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
WeekendsR2Short said:
You're having problems with every single 4.X series ROM you flash? Even with the original kernel that is supplied with that ROM? That just sounds SO weird! Almost as if you have a secured bootloader. Even with S-Off, that would keep it from flashing with the ROM. You haven't flashed a different bootloader sometime have you?
Click to expand...
Click to collapse
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
-Revolutionary-
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.44.1107
MICROP-0353
RADIO-11.16.3504.20_2
eMMC-boot
Jun 27 2011, 14:08:29
Click to expand...
Click to collapse
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Sent from my HTC MyTouch 4G Slide using xda premium
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Sent from my myTouch_4G_Slide using xda app-developers app
Unrelashade said:
Stable kernels as well. I went all the way back to the absolute basics to try to make things stable.
I'm going to research how to do that... Is there a thread that introduces readers to pulling logs? I'll go looking for one.
Exactly! Even with the original kernel of each ROM. I bought the device used, so I can't rule out the possibility that the last user installed a secured bootloader. Here is what my bootloader says:
This information could of course be fake But if you guys say battery is probably not the problem then it seems to be a good idea to flash a bootloader from the forums...
And again thanks for your help, I am kind of moved haha
Click to expand...
Click to collapse
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
WeekendsR2Short said:
Well, it was just an idea. From that info there, it would seem that you have the proper bootloader. That's exactly how mine reads.
Click to expand...
Click to collapse
Thanks for the info.
demkantor said:
If you try to flash a new bootloader the only way to get soff again would be via the wire trick, more complicaed then the revolutionary method but better, at the same time not neccesary.
If you know how to pull logcats last_kmsg is easy, if not its still easy and a quick google search will tell you how
Click to expand...
Click to collapse
Ok, right now I'll not try flashing bootloader since everything seems to be normal.
What I did to get last_kmsg:
Code:
Open terminal app
Enter "su" to get root privileges
Enter "cat /proc/last_kmsg > /sdcard/last_kmsg.txt" to save current log.
Close terminal app.
I attached the last_kmsg.txt. What do I do with it now? I don't have knowledge to understand it.
mattlowry said:
Do you have this issue on stock also?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
I can't remember using a ROM that never crashed, but I'll try a stock ROM if nothing else works. However an old kernel of scverhagens CM 9.1 seems to work flawlessly if battery is not about < 15%. The newest r10 kernel on the other hand always immediately crashes when the phone is not charging. When charging I haven't experienced a crash yet. That's strange and makes me suspect my battery is the problem.
mojoffdawal said:
A fresh battery wouldn't hurt. Before I rooted, my phone would have random reboots and shut offs once the battery went below 60 percent or so. I did factory resets and tested with different apps installed and only a new battery fixed it. Best of luck!
Click to expand...
Click to collapse
Thanks! I guess I'll try an Anker since I have seen so much users here using it.
virtuous rom works great! when i had mine, i was running 4.0.3 overclocked to 1.5ghz. super stable too! daily driver for sure.
Sent from my SGH-T999 using xda app-developers app
Thanks, but the problem is I'm pretty sure that something's wrong with my phone...
I'll try virtuous ROM and a new battery though.
hope it works
Sent from my SGH-T999 using Tapatalk 2
So, I'm reviving this thread, because I stopped writing only because my phone was broken. Now it's back and I'm facing this problem again.
I've tried a lot of the 4.x ROMs here from the forums, but all of them rebooted or shut down after 5 - 10 minutes after flashing. I also tried some without flashing gapps even, but still the same symptoms. Also tested it with my new battery, nothing changed. Even the scverhagen CM 9.1 ROM rebootet shortly after flashing that worked longer previously (guess that was just by chance)
Now I've tried the original image and it works! Ugh. So what can be wrong, any ideas?
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
bit1 said:
I was having this issue as well and it ended up being my battery. I had ordered those gold ones and luckily had kept my stock. Plugged the stock one in and my reboots went away. Not sure if that's your issue. My brother had this issue and we updated his CWM that was older to the latest TWRP and that fixed his reboots. Hope either of those suggestions help
Sent from my MyTouch 4G Slide using xda app-developers app
Click to expand...
Click to collapse
It happened with both stock and new battery (Anker).
Thanks, update to latest TWRP had been my next try, if it didn't work now. But it does! Yeaaah so happy Thanks to everyone again. Almost three hours uptime and not a single issue so far!
To conclude: What I did:
Revert completely back to stock with BlueIX6's stock image (except that phone was still s-off and sdcard not wiped).
Then followed instructions to unlock bootloader, flash CWM recovery and finally flashed ROM (see sticky thread). Works like a charm!
In hindsight maybe radio made my phone unstable... I think it's the only thing that's different from now.
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good: