Related
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
yes its a kernel issue. what version of software are you running?
I had the wifi error issue, and i flashed the kernel on top of the rom and it works now
Depending on the ROM you flashed, it may or may not display "Flash Kernel after." In which then you flash it. This'll take care of all Bluetooth and Wi-Fi Issues!
If you're having issues let me know.
I had the same issue I was using stock kernel for tmobile version 1.36.531.6 on mine which I had over the air updated to 1.43.531.3. This created the wifi error and bluetooth issue, I had to try different kernels to try to figure this thing out...It will posted in my read me page when I get a chance
It's a kernel issue, there are actually three different kernels, not two, I posted this in xboarders thread, but He hasn't updated his page.
kernels
1: for tmobile software stock 1.43.531.3, this is not available anywhere on the amaze forums, i had to personally extract this from the rooted stock rom that xboarder provided
2: for tmobile software stock 1.36.531.6 and 1.36.531.5 and lower, this stock i believe is the one xboarder has up as the original boot.img
3: faux's custom kernel, this kernel will work with all versions i believe
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
andy55 said:
no luck, flashed faux kernel 3x's and still same problem.
Any other ideas on what it could be?
I get a signal for the phone, no 4g icon, same error with wifi, and nothing with bluetooth or network.
Click to expand...
Click to collapse
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
andy55 said:
I posted a couple days ago about some issues with rooting my phone, which I solved, but now I have some new issues. When I went to turn on bluetooth, it wouldn't turn on, just try to turn on for a couple seconds and then nothing. I tried turning on wifi, and it would go straight to showing 'error' under wifi. So, I tried a different rom beast 2.3, and being at work, I can't connect the phone to my comp (encryption issues) so I only had a copy of the rom, not a kernel. Once I had beast installed I lost my network too! so I couldn't connect to my provider's network. I wiped everything, brought back AR 1.1, and am currently without bluetooth, wifi, and network. When I scan for networks my telus network shows up, as well as bell, rogers etc.
Is this a kernel issue? As soon as I get home that's the first thing I'll be trying out
Click to expand...
Click to collapse
I told you rooting is not for you but you thought I was attacking you. But seriously if you do not know what you are doing you will mess up the phone. you still havent because there still is no s-off so pretty much your phone is kinda locked
seansk said:
you need to help me help you. I ask you again what software version are you on???? go to settings>about phone>software information and look at software version, let me know which you're on.
second: what rom are you running?
you have to answer these two questions
Click to expand...
Click to collapse
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
Aren't your 2 questions the same? Just asking because when you go into software information there is no listing for software version, only software number which displays the name of the Rom you are running. Which would make it answer to both of your questions.
To the Op, are you sure the kernel flashed correctly when you flashed fauxs kernel? Did you use the EFK to flash it or did you try and flash it through CWM? Go into software information and tell us what it says under kernel
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
seansk said:
Yes you are correct I'm just trying to make sure what he's running so I can provide him the right kernel file to flash!
Click to expand...
Click to collapse
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
yes lets wait, with people with lets experience, I tend to dumb things down when asking questions...I am not doing it to demean them, but It's the only way to get any real good answers and being able to help them. Then over time they'll learn
sean, I was running the android revolution 1.1, and tried a couple different kernels and nothing
But I ended up fixing the issue finally. The super wipe zip file I downloaded with AR 1.1 was corrupt, and wouldn't load properly, so I was installing a rom without doing a wipe every time. So, I put a working copy of the zip on the sd card, and did a manual wipe of the caches, re-installed AR 1.1 and all is well.
So, even though I was following all necessary steps, I failed to realize that the wipe zip was faulty, and really messed everything up, and when I changed the rom again to beastmod, I didn't install the correct kernel with it, so yet more issues.
Happy to say that it's all over, and I have a much faster phone with alot less bloat on it. Thanks to everyone!
aj_2423 said:
lol ok. but the thing is, is that he said he flashed faux's kernel and the stuff still didn't work, which it should no matter what rom hes running, unless of course he was running a sense 3.5 rom which im sure hes not from reading his posts. this is why i'm assuming he did not flash the kernel correctly... wouldnt u agree? we'll see when he finally posts what it says in his software information for what Rom hes running and what it says his Kernel is.
sent from my Bulletproof Amaze w/faux .008 kernel
Click to expand...
Click to collapse
Flashed the kernel as xboarder showed in his thread and video.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
flyinjoe13 said:
Not sure which forum this should be in so i'm asking it here. Apparently, I can't activate my new sim card for the 4G unless i'm stock, unrooted, locked bootloader. I guess I jumped the gun after I got my phone, but before I got the sim card and rooted, unlocked, etc. I think I know the steps to take to get it back to compltely stock, but I want to make sure.
I think I need to run the script and relock the bootloader, then flash the stock RUU file.
Is that correct? Is that the correct order? Am I missing any steps?
Thanks a bunch for any speedy repsonses because i'm in a bind right now and have to get this resolved by morning.
Click to expand...
Click to collapse
I'm pretty sure being unrooted is not a requirement. Just install this ROM and boot the phone with your SIM inserted. It should activate fine.
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
flyinjoe13 said:
OK. I will try that because I am having a heck of a time getting activated on my CM rom. Even had a Verizon tech trying to help me for over an hour.
I see that ROM requires me to flash a new boot.img. When I rooted, the directions said to flash dirtyracuns Hboot. Will flashing this one effect anything? If I change ROMs, do I need to flash DR hboot again?
Thanks for the info...
Click to expand...
Click to collapse
Boot and HBoot are two very different things. Flashing different boot images will not affect your engineered hboot.
You definitely don't want to talk to vzw reps if you're running cm. The more tech support requests they get from users running non-official builds, the less likely they will be to ever allow phones with unlocked bootloaders on their system.
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
LTE/CDMA should be fine
simlar problem
flyinjoe13 said:
Turns out my problem was from a borked radio. Being new to this, I didn't even know that could happen. Saw mention of it in another thread when I was just browsing around. Thought maybe that might be my problem so I followed the directions for fixing a borked radio and got connected right away. Boy this forum is helpful. Thank you.
BTW, what is the best network setting to use if I am in the US only, Global, LTE\CDMA or GSM\UMTS?
Click to expand...
Click to collapse
I am having a similar activation problem. What did you do to fix the radio? My problem started a few days ago.
I found the RUU for just the radio and applied it. No change. I get a LTE signal but the phone doesn't know it's own number and thinks it is roaming.
I followed the steps in this thread to restore my radio: http://forum.xda-developers.com/showthread.php?p=45476579#post45476579
Unfortunately, I never was able to get the radio to work with any of the CM based ROMs so I have ended up using a stock based ROM. ViperLTE. It is an excellent ROM and works great, but I got the phone recently so that I could run CM ROMs. Had I known I was going to have so many problems, I would have waited until February when my upgrade date came up and got one of the newer phones. I guess I still can, but I'd hate to waste the money I paid for this phone so soon.
sim issue
Turns out my SIM was actually bad. When you looked in the about, the SIM id number didn't show up. It had worked under 10.2 stable for several weeks before it stopped working. It had gotten worse over a week or so. At first a reboot would fix it. I did a clean flash of CM 11 at this point. After replacing the SIM the id number showed up but still couldn't make calls.
The problem went away after restoring a CM 10.2 back that had worked. I then did a dirty flash of CM 11 over it, with the kit kat gapps. It all worked out fine. I am speculating that a clean flash of CM 11, might not work.
Hello everybody, i have been fighting with my htc for a few days now and there is no way i can make it work. I have the at&t version, i have managed to root, install custom recovery and customs roms. All i want is to have a rom that doesnt have all the at&t thrash and that lets me share mobile network(phone is gsm unlocked). I have installed the custom rom, but for my surprise the WiFi didnt turn on, no matter what a I did. Already tried with a lot of roms.
I have:
-Unlocked bootloader
-TWRP
-Software number: 1.58.502.1
-S-ON.... Firewater wont work to turn it off.
Any ideas? I just want to install a stock rom with working wifi thanks
This has been discussed in many threads. Your firmware is outdated for the ROMs you are trying.
Try older ROMs. Or else s-off with sunshine and update your firmware.
What hboot and radio baseband?
@worms45
http://forum.xda-developers.com/showthread.php?t=2752956
AT&T HTC ONE M8
@redpoint73
wich one? i have tried a lot really. My hboot: 3.16.0.0000 radio: 1.16.21331931.LA11G
@jball
just installed that one, didnt work, every sencond got popups saying: "nfc stopped working" for example, everything stopped working, thanks god i had a backup.
Will this one work? http://forum.xda-developers.com/showthread.php?t=2702074
Thanks
I suggest staying on 4.4.2 version of roms, you have to flash the boot image manually I believe with s-on. revert back to stock 1.58.502.1 system and recovery relock your bootloader and flash the 2.23.502 ruu
worms45 said:
@redpoint73
wich one? i have tried a lot really. My hboot: 3.16.0.0000 radio: 1.16.21331931.LA11G
Click to expand...
Click to collapse
Your hboot and radio correspond to 1.x software, or Android 4.4.2, so you should stick with ROMs based on that, as also mentioned by Wonders_Never_Cease.
worms45 said:
@jball
just installed that one, didnt work, every sencond got popups saying: "nfc stopped working" for example, everything stopped working, thanks god i had a backup.
Click to expand...
Click to collapse
Weird. It should work. Were you sure to do a full wipe before flashing (wipe data, Dalvik and cache in recovery)?
worms45 said:
Will this one work? http://forum.xda-developers.com/showthread.php?t=2702074
Click to expand...
Click to collapse
It should.
I installed this one http://forum.xda-developers.com/showthread.php?t=2702074 a few hours ago, everything worked fine... But the music wont work, at first it worked fine, but now it doesnt sound, its pretty weird. No error, it plays the music but its like muted, everything else works, videos, ringtones, etc.
So i just have to install 4.4.2 based rom?
Any rom you guys would recommend? All i see are 4.4.4 or 4.4.3... I need a 4.4.2! Thanks for your help
worms45 said:
I installed this one http://forum.xda-developers.com/showthread.php?t=2702074 a few hours ago, everything worked fine... But the music wont work, at first it worked fine, but now it doesnt sound, its pretty weird. No error, it plays the music but its like muted, everything else works, videos, ringtones, etc.
So i just have to install 4.4.2 based rom?
Click to expand...
Click to collapse
Harmon Kardon audio causes audio bugs if the correct HK firmware is not installed.
Go to post #4 of the Skyfall thread and there you will see a link to a flashable zip to disable HK.
Or try GoldenEye. I was on this for a long time when the phone first came out: http://forum.xda-developers.com/showthread.php?t=2705640
redpoint73 said:
Harmon Kardon audio causes audio bugs if the correct HK firmware is not installed.
Go to post #4 of the Skyfall thread and there you will see a link to a flashable zip to disable HK.
Or try GoldenEye. I was on this for a long time when the phone first came out: http://forum.xda-developers.com/showthread.php?t=2705640
Click to expand...
Click to collapse
Oh thanks mate, disabling the HK made my audio work, but speakers sound terrible :S. Any way to be able to install the recent roms on my phone? Do i have to pay for sunshine?
And im downloading goldeneye rom, i hope it works fine! Will tell you as soon as i have it installed
worms45 said:
Any way to be able to install the recent roms on my phone? Do i have to pay for sunshine?
Click to expand...
Click to collapse
You can return to stock ROM and recovery, and install the 4.4.4 OTA when it comes out (rumor is mid-November, so possibly any time now). This will update your firmware.
Great, i have a backup of the original rom the phone came with so i will update it when the OTA rolls out