Related
Hi all,
A week ago I bought a brand new Desire S and installed latest CM 7.1 stable following the guide on cyanogemod Desire S Wiki using revolutionary 0.4pre4. Everything was smooth and nice, I flashed ROM and GAPPS and my phone is working absolutely perfectly... but there is one little problem...
I am using Desire to fetch my mails from 2 mailservers using IMAP every 30 mins. But when the phone is switching between network modes i.e. HSDPA -> EDGE or EDGE -> GSM or any other way, I am disconnected from operator network for about 10 seconds until the network mode changes and everything is fine after that, until there is another network mode switch.
This happens for me about 10 times a day, so my phone sometimes appears that It is turned off for people who want to call me. Immediately after connecting to network I get a missed call SMS from my operator.
Interesting thing is, that when I disable email fetching, disable background data transfer and disable network data, the phone works fine without "blackouts".
Can someone help me with this problem? Maybe a radio issue?
Some more info:
ROM: Cyanogenmod 7.1.0 Desire S
Recovery: Revolutionary CWM v4.0.1.4
HBOOT: 6.98.1002
Kernel: 2.6.35.14-cyanogenmod+ [email protected] #1
Radio: 20.28I.30.085AU_3805.06.02.03_M
There is a newer radio-file online.
Maybe it's solving your problem.
I'm using MIUI and never had such problems, but i'm interested in flashing CM, so please report if the problem is gone by flashing newer radio!
Which radio version are you using?
Today I am testing 2G only switch so I am on EDGE data only.
Flashing radios is safe......, but a bad radio flash will instantly brick your phone.
You are using 1.47.401.4 radio, try updating to the 2.10.401.5 one.
Thanks for reply.
Shoud I flash something else with the radio?
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Another I have is ftom OTA update zip file OTA_Saga_S_HTC_Europe_2.10.401.8-1.47.401.4_release_225210fmxlt12djw1sr7y5.zip where is one radio.img in formware.zip file too - version unknown
So Which one to flash?
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
MyroLM said:
Shoud I flash something else with the radio?
Click to expand...
Click to collapse
no need
MyroLM said:
I have 20.4801.30.0822U_3822.10.08.04 downloaded from cmw.22aaf3.com
Click to expand...
Click to collapse
this file is what ur looking for! check md5-checksum before flashing!
MyroLM said:
and if so, which method should I use to flash radio? The Android SDK one or the ZIP + Bootloader one?
Click to expand...
Click to collapse
Both will work, i'm using method by using bootloader normaly
Strangely I had the same issues as you on Endymion.
Then I updated radio to the latest.
It worked well.
Then I went to CM7. It was fine for a while, but now I'm losing signal with no 3G bars and its not switching automatically to 2G like it should when It has no 3G signal!
EDIT:
After really reading your post, I realise my issue is no way like yours! Yours seems really bad. Update your radio.
-------------------------------
Sent from my HTC Desire S
So, here we go with the results
I flashed 20.4801.30.0822U_3822.10.08.04, md5sum checked OK, update sucess, but phone with no signal...
I flashed 20.48.30.0822U_3822.09.08.20, md5sum checked OK, update sucess, but phone with no signal again...
I flashed 20.28I.30.085AU_3805.06.02.03 back, md5sum checked OK, update sucess, but phone with no signal again...
... what now ... ?
After each flash wiped cache and Dalvik...
in your telephone-info there is shown the new radio after every flash?
do you have removed the batterycover, because there is integrated the antenna of your device!
mouzzza said:
in your telephone-info there is shown the new radio after every flash?
Click to expand...
Click to collapse
Yes, correct number every time.
mouzzza said:
do you have removed the batterycover, because there is integrated the antenna of your device!
Click to expand...
Click to collapse
No, the cover is at its place where it should be. Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now.
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
MyroLM said:
Somehow I did the trick and I am back online with 20.28I.30.085AU_3805.06.02.03 on 2G only for now
Click to expand...
Click to collapse
in your area 3g is actually available?
may it helps to go outside, to find your net for the first time!
did you set an accesspoint for 3g?
may you have to set automatic settings, rather than 3g/2g-only?!
MyroLM said:
I read somwhere in the forum that ENG HBOOT is required for new radios... Are you sure I dont need to flash eng hboot it before new radio ??
Click to expand...
Click to collapse
using same hboot as you, never had problems on flashing radio-files!
yes, in my area there is 3g, when I turn off 2g only switch there is a problem described in my first post, so i am on 2g for now just to keep phone connected to network.
main problem is when i am driving and the phone is switching network modes.
so I give 20.4801.30.0822U_3822.10.08.04 today another chance, try to flash if again.
but i am woried about stucking on HTC logo after flash :-( and brick it.
MyroLM said:
but i am woried about stucking on HTC logo after flash :-( and brick it.
Click to expand...
Click to collapse
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
I have the same or a very similar problem. I have the stock rom.
I already had 3 different desire s motherboard's and 2 different display's.
The first Desire S i had, with android 2.3.3, had a excellent signal. Due some problems i had, the phone bricked and had to go to HTC to repair.
HTC replaced the motherboard and update the version of the android to 2.3.5 and ever since the signal caption, the signal switch was working very bad.
The phone went to a second repair because of this, new phone, and again with android 2.3.5. The problems persisted.
I also tested with different SIM cards, from different mobile operators.
So, my conclusion is either android 2.3.5 or this new versions of Desire S have problems with signal caption and signal switch.
So as you, i need some help with this issue!
mouzzza said:
i already had the problem for several times, and i also pulled out the battery (you shouldn't do that)!
only had to boot into bootloader, start recovery, wipe all partitions, flash rom and was having fun again with my device
this thread could help you, if really stuck on HTC logo
For your real problem on loosing the signal, did you ever tried out using actual stock rom, or another custom one like MIUI?
i used MIUI from 2010-08 till yesterday, now trying out CM7.1 for some days
Click to expand...
Click to collapse
But when I reboot to recovery it will flash the radio again I think.
i hate stock roms, and dont like MIUI design That is why I am using Cyanogen
Anyway if I use 2G only switch, the phone is stable as rock both calls and data transfer.
EDIT: OK, flashed 20.4801.30.0822U_3822.10.08.04 sucessfully, signal OK, I will see what happens whet metwork mode switches
@Green Hawk:
give us more information about your device please, which radio you're using? Did they flash actual radion also?
@MyroLM:
report if the problem is still there or it's gone with flashing the rom
I am still testing new radio, but looks good Give me some days let you know...
Hi All,
I have a similar problem with the latest CM7.1 nightly builds (Reaper, jorgen2009). I never saw this with older CM7.1 versions, e.g. Nexx version, ICS, MIUI oder Endymion.
I have WLAN on and leave my house. Phone switches to 2G/3G..., so far so good. When I return home, The WLan sign in the status bar appears again, everything seems to be fine, but I have no connection. I get no data via WLan until I swicth WLan off and on again.
Radio is the latest from 2.10.401.5.
Best Regards
Wrapp
Had similar problems, upgrading to the latest radio helped. I got stuck on the HTC screen and I went through flashing RUU's and unlocking bootloaders back and forth... when the only thing that needs to be done is to wipe the cache.
Learned a lot about bootloaders though. But my warranty got void because i did the htcdev unlock... (Sorry for OT)
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
EDIT: wifi was not working about half a hour...but than...voila!!! It is for no reason back working the phone was just liyng on the table, than i took it and just set wifi on, "what if"... that´s really strange, but. But great! Now go back root, s-off and some awesome custom rom
lord5619 said:
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
Click to expand...
Click to collapse
Have you tried to restore the stock ROM?
http://forum.xda-developers.com/showthread.php?t=1529941
I agree I would recommend flashing the full ruu to take you back to stock Rom I did the same thing to get rid of my problem and flashing the full ruu did the trick I'm now s off Revolutionary style and flash 4ext custom recovery and su file and custom Rom the correct way
Sent from my HTC Sensation 4G using xda premium
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
lord5619 said:
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
Click to expand...
Click to collapse
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
malybru said:
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
Click to expand...
Click to collapse
will try your patch, thx
EDIT: it says -Revolutinary- and HBOOT is 1.27.1100 Thanks!
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
lord5619 said:
will try your patch, thx
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
Click to expand...
Click to collapse
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
malybru said:
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
Click to expand...
Click to collapse
I am afraid, even this is not working. Pins definetly have some resistance and resting to its place. :-/ when i return from vacation, i´ll take my precious Sensation XE to a doctor, he will know perhaps.
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I honestly don´t know, i thought, wifi is (almost)only kernel related, but now i see, that it is not :/ It is almost exactly my problem, i was using ViperS and changed kernel...but it didn´t suit me, so i restored the previous one...than i woke up and wifi is gone i cant solve it for now, i don´t have any freetime at this moment for making full stock condition.
i have tested stock rom with stock kernel, with some other HBOOT but still the same.
bhma said:
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
Click to expand...
Click to collapse
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
lord5619 said:
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
Click to expand...
Click to collapse
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
bhma said:
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
Click to expand...
Click to collapse
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
lord5619 said:
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
Click to expand...
Click to collapse
Originally Posted by Zeustopher
Wanted to update on my progress. I solved the issue on my phone:
I was messing around with it today while waiting for a meeting to start and I found where the wifi settings, etc are stored. It ended up being a corrupt/invalid wpa_supplicant.conf file. All I had to do was pull that file out from the directory and turn on wifi and *poof* it worked again. When I turned wifi on it created a new file and everything has been great so far this afternoon.
In case anyone wants to give it a shot who is having wifi issues you can find the wpa_supplicant.conf file in /data/misc/wifi/ directory on your phone. Simply cut/rename the file and put it somewhere else. If you have wifi passwords you want to save, you can open the original file using a text editor and copy the settings over to the new file.
I believe the cause of my issue was actually Titanium Backup. Looking at the last time it backed up my wifi settings was back when I wasn't running ICS yet. Yesterday I did restore an app using it and must have accidentally restored that old backup. Their formats are different from Gingerbread to ICS apparently and it was causing errors.
i found this on another post dont know if it will help but it could be the problem with the ota update from gb to ics
now the silly noob question how do you access the directory ????http://forum.xda-developers.com/images/icons/advanced/sign.png
i got into the directory but it doesnt seem to work in another thread someone got it to work with a virtuous rom
ill try that on thr weekend
enjoy your vacation
hmmm thats iteresting, but if you do full-wipe and flash some rom and kernel, these files are rewriten...but because i am curious i tried it and!!! it is not working for me :-/
And how to get into this directory?Simply... download dome file manager from Play Market(i lika Total Commander), but you can use whatever you like, set in options "root function everywhere" and allow superuser. than you can go in any directory and read/write/change
EDIT: ou, now a see whole post, ignore my instruction i am mega-sleepy
alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
Yank v2.52? hmmm that´s kernel by Faux?
lord5619 said:
Yank v2.52? hmmm that´s kernel by Faux?
Click to expand...
Click to collapse
yep
alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
No help for me still the same "turning on"
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
jaker.the.skater said:
I searched around and couldn't find a definitive answer. The problem I'm having is connecting to wifi at all.
After getting a phone replacement, I unlocked the bootloader, flashed CWM recovery, rooted, flashed CM 10 nightly 09/29 and GApps but when I booted, I could not connect to wifi at all...I can't even turn on wifi because the toggle is greyed out. I have tried reflashing several times and even tried a different rom. but still no luck. Anyone else have this problem or know how I can fix it? I rely heavily on wifi because of ****ty data in my dorm. Any help would be much appreciated!
Click to expand...
Click to collapse
Hello,
What was the version of software on you phone before rooting, was it a T-Mobile phone? The newest version for T-Mobile has created is issues for roms that aren't the same version.
Rsotbiemrptson
Sent from my Nexus 7 using xda premium
Yep, just found out that was the issue. kinda sucks because I'd rather have jelly bean! Oh well guess I'll deal with no wifi till a fix comes out.
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
YousufWalton said:
why does the Ruu not work anymore i want to take my phone back to where the wifi works..... i have a cwm backup from before the update but that did not even fix the problem
____EDIT____
Well i got the wifi back. ( and the OTA update ? again )
Relocked the phone boot loader
I opened the RUU
took the Rom.zip from the folder.
took the stock recovery img
flashed the stock recovery img
start the phone back up
downloaded the update again. ( 4.0.4 )
did all the waiting etc
phone powers down reboots applies the updates to it self.
powers back up updating completed
WIFI WORKING.
go to try and do the ruu.exe again but no it says error 140( i think ) wrong bootloader version.
This update changes the bootloader to version 1.14___ So now the phone is non tamperd and says relocked so back to stock ( YAY )(((for now))))( i think lol )
Most importantly the Wifi is working.
If anyone wants i can take and give the files from the RUU ( not the whole zip but what ever img's you want from it ) Just send me a PM i will mail it to ya.
Click to expand...
Click to collapse
So did you use the 1.84 ruu? And you did this after applying the tmobile ota?
I have a problem on my M8 that nobody seems to be able to solve. My M8 doesn't connect to 3G, only to 4G and 1x. This gets carried over from Rom to Rom. My SOD is running Viper and she connects to 3G no problem while I'm stuck with 1x.
I have posted multiple times about this but nobody seems to know whats going on.
Would going back to S-ON and Unroot possibly fix this problem? Would I need to revert my firmware.
I just don't know what to do.
I'm not the one to help you but I can say with confidence that turning s-on will only limit your options for fixing you problem.
mentallo said:
I have a problem on my M8 that nobody seems to be able to solve. My M8 doesn't connect to 3G, only to 4G and 1x. This gets carried over from Rom to Rom. My SOD is running Viper and she connects to 3G no problem while I'm stuck with 1x.
I have posted multiple times about this but nobody seems to know whats going on.
Would going back to S-ON and Unroot possibly fix this problem? Would I need to revert my firmware.
I just don't know what to do.
Click to expand...
Click to collapse
What ROM are you currently running ?
You may have to revert back to a stock ROM and then build back up. Before that I would wipe everything but your external card in recovery, flash the firmware twice with fastboot, and then flash the ROM.
Good luck.
mentallo said:
I have a problem on my M8 that nobody seems to be able to solve. My M8 doesn't connect to 3G, only to 4G and 1x. This gets carried over from Rom to Rom. My SOD is running Viper and she connects to 3G no problem while I'm stuck with 1x.
I have posted multiple times about this but nobody seems to know whats going on.
Would going back to S-ON and Unroot possibly fix this problem? Would I need to revert my firmware.
I just don't know what to do.
Click to expand...
Click to collapse
Have you tried using factory reset from hboot while on a stock recovery? Stock recovery resets parts used by the radio that custom recovery can't touch.
Have you also verified you have your network settings set to global and not lte only?
Whatever you do....do not turn s-on to trouble shoot this.
So I would need to unroot to use a stock recovery right?
mentallo said:
So I would need to unroot to use a stock recovery right?
Click to expand...
Click to collapse
No just flash the stock recovery just like you would a custom recovery. If you go to the android development section you should find the download for the stock recovery. Make sure to flash the correct one, such as the 4.4.4 stock recovery if your on the latest firmware or the stock recovery for 4.4.3 if your on that firmware and so on.
It never fails, every time I see somebody ask if they Should go back to S-On for any reason other than Warranty/returning phone, I cry a little on the inside..... ?
mentallo said:
I have a problem on my M8 that nobody seems to be able to solve. My M8 doesn't connect to 3G, only to 4G and 1x. This gets carried over from Rom to Rom. My SOD is running Viper and she connects to 3G no problem while I'm stuck with 1x.
I have posted multiple times about this but nobody seems to know whats going on.
Would going back to S-ON and Unroot possibly fix this problem? Would I need to revert my firmware.
I just don't know what to do.
Click to expand...
Click to collapse
Whatever you do, Don't go S-0n. It will only make your life more complicated.
What you need to do is run Dottat's FUU to make your whole thing stock.
Then do a factory re-set with stock recovery & kernel, and voila(!) your radios will be fixed.
Then put whatever rom you want on it.
Thanks for the help.
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
iFrostyy said:
Hello, sorry if this has been asked before but my phone has been having trouble connecting to LTE for some reason. I'm assuming it has something to do with my radios or something along those lines. My friend is able to connect just fine and he is on the same rom as I and he also has the same phone.
If someone could point me in the right direction that would be awesome!
Thanks!
Click to expand...
Click to collapse
Are you stock? S-off? Which firmware are you on?
brholt6 said:
Are you stock? S-off? Which firmware are you on?
Click to expand...
Click to collapse
I am s-off and I am on a GPE 5.0.1 ROM.
iFrostyy said:
I am s-off and I am on a GPE 5.0.1 ROM.
Click to expand...
Click to collapse
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
dottat said:
Did you flash the custom firmware with it too? If so that's likely the problem. Been hearing of a lot of radio issues from L gpe roms lately.
A factory reset in stock recovery (stock vzw recovery) usually fixes it.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
LibertyMonger said:
The custom firmware seems to cause the issue worse than the 4.4.4 firmware. Most everyone seems to be having this issue but overlook. It also makes loading web pages really slow. Flashing the stock RUU and factory reset did not change anything, it seems the firmware is not right for Verizon phones.
Click to expand...
Click to collapse
If you flashed the vzw ruu you are no longer on custom firmware.
dottat said:
If you flashed the vzw ruu you are no longer on custom firmware.
Click to expand...
Click to collapse
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
LibertyMonger said:
That was just to start over, I then tried the custom firmware a few more times on multiple ROM's with the same results. Constant signal loss and slow data speeds.
Click to expand...
Click to collapse
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Croak said:
OP, your best bet is to flash a stock Verizon RUU (this one works great and is for S-OFF devices), then once it is fully flashed, go into stock recovery and then do a factory reset (this is an important step, this is where you get your proper Verizon radio settings/files back!).
After that, you can go ahead and flash back to DH GPE without using custom firmware and you should be fully functional again with LTE.
And to repeat, you MUST do a factory reset from stock recovery, don't skip this step!
Click to expand...
Click to collapse
Think that horse was beat dead already lol
Sent from my SM-T320 using Tapatalk
dottat said:
That custom firmware should not be flashed to a vzw phone. I have no idea why he posted that firmware to be flashed. You can tell by the info.txt file that it was not.
The included wcnss was never intended to be used on a vzw phone for cdma/lte access.
Wireless connectivity networking subsystem.
Click to expand...
Click to collapse
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
LibertyMonger said:
Now I am lost lol. Why is it even posted in the Verizon Forum? Too many carriers in that thread i can't keep up with it all I work too much.
Click to expand...
Click to collapse
It was made for the gpe version phones. They weren't sold for vzw.
dottat said:
It was made for the gpe version phones. They weren't sold for vzw.
Click to expand...
Click to collapse
Yeah I think most who are using it are either lucky or do not care or notice the dropped, weak signals. I've tried everything more than once to get it working right and the results are always the same, it acts like it's the wrong firmware, cause it is lol. Some claim to have the same issues but ignore them. I need my phone to work no matter what ROM it is. Thanks for all your help bro I see you are willing to help us when in need, that is greatly appreciated. I hope users send donations your way, I sure will once i get ahead again.
Have you set your APP correctly.
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
kj13569 said:
So I just tried this and cannot get back into stock recovery to wipe data. Had to factory reset from hboot, that worked but not sure if it does the same thing as the one in stock recovery, please advise. Then tried to flash the stock recovery and it's still taking me to the darn red triangle with an exclamation point. I am going to continue and install LiquidSmooth 4.0 1-02 nightly after I flash custom recovery. I have searched but cannot find anything on our variant. Thank you all in advance.
Click to expand...
Click to collapse
When you get the red triangle, you press volume up and power to enter stock recovery. Keep practicing.
LTE drops on and off
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Flylowguy said:
I think I have the same issue as OP. However, I'll go further and note that I notice this on ALL AOSP roms as well as the GPe rom. It's not so much that the connection is bad, it looks good. But it drops on and off randomly. I followed the instructions here to factory reset the firmware using the 4.4.4 ruu. It definitely seems to be better but I still have this issue in DH's GPe (stock kernel). Any further ideas?
Click to expand...
Click to collapse
That signal drop off issue happens to me on gpe ROMs. So far all the cm12 ROMs out there have had a perfect signal with good speeds for me. I think the signal drop off issue is something to do with the gpe ROMs.
Currently running blisspop newest nightly with 4.4.4 straight from RUU.