About a week ago I flashed the newest ARHD ROM and newest firmware. Everything worked great until this morning when my Data doesn't work. I can still receive calls and WiFi works, just no LTE signal. Any ideas?
I had the same problem with that Rom, restoring stock backups didn't fix it either, the only way I could fix it in the end was to download the guru reset Rom and flash that, then install a more up to date custom Rom after that.
Unfortunately his site seems to be down at the moment, but when it's back up and running you will need to find the ruu zip Rom for your device in the list, mine was 161 which is Vodafone UK, so I had to download 2.24.161.1 for instance and flash that, radio and recovery too which is included in the Rom.
Www.htc1guru.com
sp191 said:
About a week ago I flashed the newest ARHD ROM and newest firmware. Everything worked great until this morning when my Data doesn't work. I can still receive calls and WiFi works, just no LTE signal. Any ideas?
Click to expand...
Click to collapse
what about your APN settings?
alray said:
what about your APN settings?
Click to expand...
Click to collapse
I didn't check that. That's the only thing I didn't check. I ended up re-flashing(Dirty) and that did it. The only thing I had changed since the first flas was I added Apex Launcher. Doubt that was it and all is fine after the re-flash.
Related
I am running cm10.1 nightlies. Flashed the firmware with no problem from this thread. Then booted back into my stock rooted cwm recovery backup tried profile and prl update and they failed. Downloaded the stock rom from that same thread booted into that and tried in there same thing. Is anyone else having this issue?
I was having trouble the last two days on new firmware. I just tried it now and it works.
mxl180 said:
I was having trouble the last two days on new firmware. I just tried it now and it works.
Click to expand...
Click to collapse
I too have been having issues. I just tried again and both worked.
D
Yep seems to be working now must have been something weird on sprint's end.
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working​
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
=====================================================================================
SOLVED!
Well, after my vacation, took my One and did a bit of research. I know everything about this problem now.
The problem is only in GE ROMS. Why? 4.3 GE hasn't listed my MVNO yet (known error by Android and by 'Pepephone'). So, as soon the mobile goes on, Android tries to connect to the SIM, but as it's not listed amongst the companies, the phone crashes. I had to flash a file with the APN, then add it manually. Ta-Da! It works.
Attached the ZIP file to flash in Recovery.
- Install 4.3 GE Rom.
- Flash the Fix.
- Start and complete the Install Wizard.
- Inside the APN config, manually introduce Pepephone's APN
o NAME: Pepephone
o APN: gprsmov.pepephone.com
o MCC: 214
o MNC: 06
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
raulongo said:
Sorry to bump the thread, but currently I have a HTC One with no phone and it's really important for me to solve this asap. I'm going on vacation tomorrow and I need my phone
Click to expand...
Click to collapse
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
dgtiii said:
Are you using a custom kernel that matches, exactly, the 4.3 custom rom you are using? If it is a GE 4.3 based rom, you need a GE 4.3 custom kernel (check out ElementalX). If it is a Sense 4.3 base rom, well that update just came out yesterday and there are no custom kernels for it yet.
Click to expand...
Click to collapse
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
raulongo said:
It happens with EVERY 4.3 GE Rom, stock kernel. I was in 4.2.2 GE (Android Revolution) and Installed 4.3 and gave me that error all the time without upgrading the Kernel... I'm pretty lost.
Click to expand...
Click to collapse
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
dgtiii said:
It sounds like there is an incompatibility with the new base. I would reflash the rom, doing a full wipe in the process
Click to expand...
Click to collapse
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
raulongo said:
Full wipe means to wipe/factory reset in ClockWork Recovery before flashing? I already did that like dozen times, but still, same error I don't know why I'm the only one with this problem...
Click to expand...
Click to collapse
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
dgtiii said:
The Roms I've used have an option for full wipe during the install in Aroma, but I guess doing it in CWM does the same thing. Are you theming the phone app by any chance? Something isn't playing nice with the 4.3 base, that's what you have to track down. Maybe go back to 4.2 while you sort it out
Click to expand...
Click to collapse
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
raulongo said:
Yup, did it inside the installer and outside it, but always same result. I'm back now into 4.2.2 Sense AR Rom and the phone works great, but I hate Sense.
Could it be the baseband firmware?
Click to expand...
Click to collapse
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
dgtiii said:
Firmware could be the case, was just thinking that.
My advice tho, you have a working phone, and with your vacation tomorrow, I would leave it as is for now
Click to expand...
Click to collapse
Thank you for your help. I will investigate a bit more as soon as I'm back.
raulongo said:
Thank you for your help. I will investigate a bit more as soon as I'm back.
Click to expand...
Click to collapse
Sounds good, you're welcome. Enjoy your vacation!
I have the exact same problem. I've literally tried everything. I have S-Off-ed my phone and installed a custom kernel but even that does not fix the problem. All custom 4.3 Google Edition Roms crash after I install them. It works fine if I use the Stock 4.3 ROM.
Kernel
Sent from my HTC One using XDA Premium HD app
dgtiii said:
Sounds good, you're welcome. Enjoy your vacation!
Click to expand...
Click to collapse
A little update. I've got Cyanogen 10.2 working perfectly in my phone. It's running 4.3, so now, I understand even less. Why CM works and the other ROMs doesn't?
The night is long... Hahah.
CM 10.2 works flawlessly "without" bugs. I don't understand why CM 10.2 (JB 4.3) works and the other 4.3 GE does not. Something is not right, or maybe I'm missing some step, but it's really strange...
raulongo said:
Hello everyone,
Yesterday I decided to flash an updated ROM of 4.3 to my One. After flashing it (happens with new ROM, or after flashing a new custom kernel... logo2menu, you know), a message appears ALWAYS on-screen:
com.phone.android has stopped working​
This message repeats a hundred times. I can't type anything without the message popping up. I reached the launcher, but I have no Phone signal and the WiFi is not working. It's like the phone wants to wake up the Phone Antenna but it crashes to do it.
I've read that I had to flash the boot.img from the ROM I wish to flash, and I don't know if that causes the problem...
Any help would be perfect.
Thank you in advance.
Click to expand...
Click to collapse
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
kibmikey1 said:
If you simply need a working phone, return to stock for your vacation, and then start from scratch re-flashing the GE firmware, kernels and rom. If anything is sense on the phone, incompatibility issues will happen.
Click to expand...
Click to collapse
Finally found a solution to the crash. It was related to a weird combination between GE 4.3 and my mobile network operator, Pepephone. Known bug by Android and Pepephone.
Solution at the first post.
I just bought a HTC One last week and went through the process to convert it to a fully stock Google Edition before even using the phone. Everything went without a hitch.
Coming from a Nexus 4 (And Note II prior to that), I've noticed my Wifi and Data signals to be very weak compared to my previous devices.
For example, in my bathroom I get no Wifi Signal but my previous devices had no problems getting one here. I noticed at work the same thing - no Wifi in places I used to get it. It stays connected in both examples, but is just super super slow and shows little to no signal.
Within good range it works fine.
I have a Bell Mobility HTC One 32GB (Canada), I unlocked bootloader, S-OFF'd, Changed CID to the Google One and flashed the Google Edition RUU (Pre-rooted) Everything seems to work fine except the Wifi/Data signals are weaker than previous devices. I already received a 15MB update from Google that updated fine too.
Is Wifi/Data signals generally weak on this phone? Any suggestions?
bigystyle84 said:
I just bought a HTC One last week and went through the process to convert it to a fully stock Google Edition before even using the phone. Everything went without a hitch.
Coming from a Nexus 4 (And Note II prior to that), I've noticed my Wifi and Data signals to be very weak compared to my previous devices.
For example, in my bathroom I get no Wifi Signal but my previous devices had no problems getting one here. I noticed at work the same thing - no Wifi in places I used to get it. It stays connected in both examples, but is just super super slow and shows little to no signal.
Within good range it works fine.
I have a Bell Mobility HTC One 32GB (Canada), I unlocked bootloader, S-OFF'd, Changed CID to the Google One and flashed the Google Edition RUU (Pre-rooted) Everything seems to work fine except the Wifi/Data signals are weaker than previous devices. I already received a 15MB update from Google that updated fine too.
Is Wifi/Data signals generally weak on this phone? Any suggestions?
Click to expand...
Click to collapse
What radio are you using?
You could experiment with different radios which can be found here: http://forum.xda-developers.com/showthread.php?t=2419699
Newest may not always be the best, so try different ones. Also, I think the Radio_4T.20.3218.03 (leak) is strictly ATT and doesn't have the international stuff.
nkk71 said:
What radio are you using?
You could experiment with different radios which can be found here: http://forum.xda-developers.com/showthread.php?t=2419699
Newest may not always be the best, so try different ones. Also, I think the Radio_4T.20.3218.03 (leak) is strictly ATT and doesn't have the international stuff.
Click to expand...
Click to collapse
Is Radio the baseband version? It says "4A.18.3263.15_10.38h.1157.04L"
Its whatever comes in the RUU for Stock 4.3 Google Edition rom
I've never really had to play with Radio's much in the past.
I assume I would need to flash a Custom Recovery again to flash the radio, then flash back to stock so I can continue to get updates. Probably should do this anyway so I can make a backup of my phone while I'm at it.
bigystyle84 said:
Is Radio the baseband version? It says "4A.18.3263.15_10.38h.1157.04L"
Its whatever comes in the RUU for Stock 4.3 Google Edition rom
I've never really had to play with Radio's much in the past.
I assume I would need to flash a Custom Recovery again to flash the radio, then flash back to stock so I can continue to get updates. Probably should do this anyway so I can make a backup of my phone while I'm at it.
Click to expand...
Click to collapse
Yes it's the baseband.
And yes also for the custom recovery. You can only flash these radios using custom recovery. Don't know if it's worth the hassle for you though?
nkk71 said:
Yes it's the baseband.
And yes also for the custom recovery. You can only flash these radios using custom recovery. Don't know if it's worth the hassle for you though?
Click to expand...
Click to collapse
It's easy enough to do as long as I can find the Latest Stock recovery to flash back on the phone.
The signal is noticeably weak in a lot of spots it wasn't an issue with before, so I'm willing to try.
Anyone else with a North American based phone that did this conversion experience these issues?
bigystyle84 said:
It's easy enough to do as long as I can find the Latest Stock recovery to flash back on the phone.
The signal is noticeably weak in a lot of spots it wasn't an issue with before, so I'm willing to try.
Anyone else with a North American based phone that did this conversion experience these issues?
Click to expand...
Click to collapse
I have a similar problem with my stock rogers phone. I think it started after the 4.3 ota update. My wifi connectivity constantly keeps turning off and on lasting only a minute or two. Watching videos has become too much of a hassle. i've seen other recent threads with the same issue regarding wifi connectivity. We need this problem fixed asap!
Has changing the radio fixed your wifi issues?
same here I the conversion to GPE nonroot and not unlocked but s-off. My wifi and data signals are horrible in places that were fine when I was running 4.3/htc sense5. My base band is 4A.18.3262.15_10.38h.1157.04L. Hope this gets fixed with 4.4.
am thinking about radio flash but to what? I have never done the procedure and sounds like a hassle...I would have to unlock and install custom recovery like twrp, dont have to root correct? Install the radio (also install new firmware?) then I would have to reflash the stock recovery? and relock phone to get OTA?
Hi,
at first i try to post in the related thread, but i havn't enough posts to do this.
http://forum.xda-developers.com/galaxy-s3/development-i9305/rom-beta-t2535996
After flashing the latest ROM my phone can't get a network connection. Wifi works. I used CWM 6.0.4.7, SlimKat Build 3.6 and the latest gapps from SlimRom (Build 3). I can't receive baseband, network, phone number or IMEI in the settings. All is unknown. Also when the phone starts, it doesn't ask for my PIN.
Re-install doesn't work. Another SIM doesn't work, too. CM 10.1.3 works fine.
Model: GT-I9305
Provider: Vodafone
Baseband: I9305XXUEMK1
Some ideas?
That is not a rom problem, for sure.. What can I say, you are doing everything right, but I might recommend using Philz recovery, I've never had any problem with it. Reboot recovery, full wipe and then flash
Try to flash with Odin latest stock 4.3 kernel and then try again with wiping everything before.
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Druffbold said:
Hey guys,
thanks for your advices. I wasn't at home, so I couldn't response or even try it.
Today I flashed the new SlimKat 3.8 (still with CWM) and it works Maybe it was a problem with the ROM.
Thanks anyway :good:
Click to expand...
Click to collapse
For sure it was problem with ROM. Actually with radio ROM, not the Android itself.
Make a backup of your ROM and save radio image from it.
Then you can flash some other ROM you like and flash this working radio image after that.
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
emmittobie said:
I have an unlocked bootloader and rooted Nexus 6. I usually run custom ROMs but I have had some issues when I install them for about the past week or so. I use Straight Talk CDMA which uses the Verizon towers. If I flash an official firmware such as LMY47I (5.1) or LMY47Z (5.1.1) then I have no issues with LTE connecting from the very beginning of the setup screen. Everything works fine including voice, data, and texting. When I install a custom ROM the signal will not connect and there is an exclamation point (!) next to the signal icon. I did have to exchange my phone and Motorola sent me a new one but I was able to use custom ROMs without issues on this phone until sometime earlier this week.
I know that people have been having some issues recently with connection problems and there are various threads on them. I have tried several of these workarounds but it just seems odd that I never had these issues before.
Any help or suggestions would be great. Don't mind running stock firmware but would prefer to be able to use custom ROMs again.
Thanks in advance.
Click to expand...
Click to collapse
Try a different radio. I've read that the radio from the M test build is fixing some issues.
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
emmittobie said:
I've tried flashing a few of the newest radios but not the Android M version. Will give it a try.
Thanks for the reply.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
You can even flash an older radio if need be.
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
emmittobie said:
So I tried installing two different custom ROMs and both times I got the same signal icon with an (!) next to it. There is no working connection. I tried flashing the radio from the Android M preview and also installed the radio from LMY47D (Verizon 5.1.0) since I am on Straight Talk CDMA. Neither one seemed to help. After flashing these radios I went back to restoring a TWRP backup based on just a stock firmware. From what I understand the radio is separate from any particular ROM you flash and thus independent of each other. I am able to get an LTE signal when I revert back to the backup.
So now I'm stumped. It doesn't seem to be based on the radio. None of the custom ROMs that I was able to use less than a week ago are able to find an LTE signal after a clean install. I can only seem to use official firmware versions.
Any other possible ideas? Could the phone be defective? It was an RMA replacement and I think it was new and not refurbished.
Thanks in advance.
Click to expand...
Click to collapse
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Evolution_Tech said:
Really sounds like an APN issue. I have flashed a few ROMs and have had that problem. Most recently Exodus ROM. I changed the APN and all is well.
Click to expand...
Click to collapse
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
emmittobie said:
Let me take a look at the APN settings on the stock firmware and then see how they compare when I use a custom ROM. In the past, I never had to set the APN settings as I thought they were set automatically on CDMA sim cards. I'll take a look.
Thanks.
Click to expand...
Click to collapse
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Evolution_Tech said:
Even if there's another APN with the same name as the one set by default, try switching to the other. That's what worked for me on Exodus.
Click to expand...
Click to collapse
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
emmittobie said:
Thanks for the advice. I was able to compare the APN settings on a stock firmware and enter these settings into the APN settings of a custom ROM and able to get it to work. Just strange that I have to enter these settings manually when I never had to do it before. Thanks for all your help. Much appreciation.
Click to expand...
Click to collapse
No problem, glad you got it straight. :good: