Related
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Check the op of the OTA update thread in this very section
Sent from my HTC One S
ultimul said:
hi there,
I have Hboot 1.08, is there any flash-able zip files to update the radio?
Click to expand...
Click to collapse
The answer is yes, so do as Pheroh says
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
I dont want the OTA update, anyway the phone is rooted and using custom rom so dont think ota will ever work.
where can I find the latest radio, zip files flashable thru recovery or fastboot?
touch of jobo said:
Try to either flashing through recovery or manually dd-ing the image files.
Don't take an OTA or run an RUU, as that will update your HBOOT.
You want to stay on 1.08.
-Jobo
Click to expand...
Click to collapse
ultimul said:
I dont want the OTA .. where can I find the latest radio, zip files flashable thru recovery or fastboot?
Click to expand...
Click to collapse
This is the thread Pheroh was referring to: OTA Update to Android 4.0.4 for S4 is Out! You can extract the images from the OTA .zip or use any of the methods explained in post #1.
I used the one by Dima901 and flashed thru twrp
https://www.dropbox.com/s/zvi1a70n41yy2ri/radio_OTA_19072012.zip
rugmankc said:
I used the one by Dima901 and flashed thru twrp
]
Click to expand...
Click to collapse
10x a lot;
flashed thru recovery in no time.
hope will solve the few little problems with data and Bluetooth I had.
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
rugmankc said:
It has helped many from reading posts. I am not sure I gained anything though.
But, always nice to have latest anything--
Click to expand...
Click to collapse
I can only hope will improve something. I have a problem with data switching from G to 3G to H for few seconds when I first start every session, I dont know it has impact on actually speed;
most annoying is the Bluetooth dropout from time to time, even at (very) short distances, my earpiece has no problem cause i tested with my other phones.
Anyway, if things goes wrong I still can go back to 0.16 radio I had before ( I hope at least )
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
rugmankc said:
Yes, flashing radios is Rom independent. Just don't upgrade to hboot .13 or higher. Or, you will have issues flashing radios. Hope new radio helps.
Click to expand...
Click to collapse
for the moment I use trickdroid 6.0, probably I'll change in the future if support and updates stop;
from what I know, changing rom's shouldn't change the hboot, only ruu upgrade will change it. true?
correct-
radios and hboots stay unless flashing a ruu
if/when we get s-off then hboot can be changed and we will be able to adjust partition table sizes for more data size
first day of testing, results are confusing
the data icon stays now mostly at 3G, think this is the real provider network; the differences in speed are not noticeable
for the bluetooth, the same thing, earpiece disconnect after few minutes even if with the phone in my hand; something is wrong here; I'll have to look for my older earpiece to try it. maybe plantronics 520 is not fully compatible with htc one s
should I try a custom kernel? any chance will help?
I had the Bluetooth disconnect issue . Haven't flashed a radio yet but flashing the Sensisimo Rom has seem to have fixed the Bluetooth disconnect. Fix could have something to do with the Rom being based off the latest update available (2.21 or something like that). I'm having data disconnect issues, does new radio fix it?
T-MobileUS HTC One S
I would try it, no harm done
looks like bloetooth disconnect is a small bug in trickdroid 6.0; tried another 2 earpieces and all are doing the same;
just flash trickdroid 7.1.0, I'll try it tomorrow and came back with feedback.
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
1.06, flash the new radio seperately once your on 1.06.
usaff22 said:
1.06, flash the new radio seperately once your on 1.06.
Click to expand...
Click to collapse
Thanks for the info, which radio is that though?
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
alexskin said:
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
Click to expand...
Click to collapse
Alright I'll try it out. thanks!
byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Kamilr97 said:
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Thanks,
Yikes! Now I see why a lot of people don't even attempt this
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
fjjfrank said:
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
Click to expand...
Click to collapse
I downgraded from 1.14 to 1.06 too, installed 1.53 RUU and then experienced wifi issues on Trickdroid 8.
I had to flash "extra partitions" to make it work. Seems to be some partitions required for wifi to work on versions based on latest sense kernels.
I flashed extra partitions 2.35 and wifi did not work. Then I flashed 1.84 and wifi on Trickdroid 8 would connect, but from time to time (very frequently every 15 seconds on average) disconnect and reconnect, randomly (was annoying and killing my battery). I moved to trickdroid 7 TMOUS version and wifi works perfectly, never disconnects.
(My phone was from T-Mobile)
Here are the links, taken from this post: http://forum.xda-developers.com/showthread.php?t=1657831&page=271
2.35 Extra Partitions
https://www.dropbox.com/s/7gtuvbynr3...rtitions.zip?m
1.84 Extra Partitions
https://www.dropbox.com/s/mmjcqisgoo...rtitions.zip?m
NOTE: On CM rom I never had issues even without flashing extra partitions, and even when I was on hboot 1.14.
Hope this helps,
Regards,
Diego
---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------
And regarding the topic from this post, hboot is like the BIOS of the phone. You gain nothing from upgrading it, only gain restrictions from 1.13 and above. So as far as I read it is better to stick to 1.06
Regarding the procedure to downgrade, for the one that asked, it can make you panic on the step when you upload hboot 1.06. For me, it failed 3 times, and I had to go to work after third time with a "bricked" phone -.-
But I came back, tried from my laptop instead of my PC, and worked on the first attemp!. Seemed to be my PC USB not working properly or not being fast enough/not having enough power, who knows.
It seems scary but is fairly straight through, the procedure is perfectly detailed. Did it from an Ubuntu 12.04 live image.
Regards,
Diego
HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
byliu88 said:
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
Click to expand...
Click to collapse
oke thanks
i am from the netherlands and i have got a unbranded one s
witch hboot can i install without updating my bootloader
Hey Guys! I recently picked up the HOX after three solid years on the Captivate. The rooting/flashing experience has been more difficult thus far but the device is pretty friggin' sweet. I unlocked and rooted with minimal issues and went to the latest CM10 nightly out of the gate. No issues were encountered at least during boot up. Once up and running however, the only network available is EDGE. I searched around and found posts in other device forums stating this is due to corrupt/missing IMEI. Did not see anything about this for the dual core HOX. I checked the ATT APN details and they matched what people were posting around. The IMEI is correct in the about phone->status info. Available networks shows ATT and US only. If I try to manually select ATT, it states it cannot reach this network at this time. So it appears I am lost at the moment. Should I reflash CM10? or start over at stock? Any feedback would be greatly appreciated.
do you have at&t branded evita? what radio, hboot and base is on your phone?
DvineLord said:
do you have at&t branded evita? what radio, hboot and base is on your phone?
Click to expand...
Click to collapse
Yes, it is AT&T branded. This is the info listed on the bootscreen:
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
About phone lists the Baseband as: 0.19as.32.09.11_2_10.105.32.25L
radaghast196 said:
Yes, it is AT&T branded. This is the info listed on the bootscreen:
HBOOT - 1.14.0002
RADIO - 0.19as.32.09.11_2
About phone lists the Baseband as: 0.19as.32.09.11_2_10.105.32.25L
Click to expand...
Click to collapse
i have same. i see ups and downs from build to build and rom to rom sometimes specially lately with 4.2.x. usually i toggle airplane mode and it fixes the problem for awhile, but i've never been stuck on edge unless it was a build my phone really didn't like. what gapps are you using? are you using stock kernel? are you s-off?
DvineLord said:
i have same. i see ups and downs from build to build and rom to rom sometimes specially lately with 4.2.x. usually i toggle airplane mode and it fixes the problem for awhile, but i've never been stuck on edge unless it was a build my phone really didn't like. what gapps are you using? are you using stock kernel? are you s-off?
Click to expand...
Click to collapse
I flashed a gapps-jb-20121212-signed version. Stock CM kernel and left it s-on. The instructions I was following did not mention adjusting this, so I left it alone. Would it be a potential starting point you think? I tried the airplane mode after each reboot, but EDGE only sadly. I tried different APNs, but again EDGE only.
radaghast196 said:
I flashed a gapps-jb-20121212-signed version. Stock CM kernel and left it s-on. The instructions I was following did not mention adjusting this, so I left it alone. Would it be a potential starting point you think? I tried the airplane mode after each reboot, but EDGE only sadly. I tried different APNs, but again EDGE only.
Click to expand...
Click to collapse
try gapps-jb-20121130-signed.zip
DvineLord said:
try gapps-jb-20121130-signed.zip
Click to expand...
Click to collapse
Done. Still no joy though. It did take several minutes before it found a network but still living on EDGE.
well, by now i'd say try another rom. or ruu back to stock and see if your phone has issues. or you might need a new sim.
I don't really have a solution for you but you're not alone. I was having a lot of issues with my phone dropping its data or telling me there's not SIM in it.
DvineLord said:
well, by now i'd say try another rom. or ruu back to stock and see if your phone has issues. or you might need a new sim.
Click to expand...
Click to collapse
Understood. I think I'll RUU back to stock. Just to be clear, I came from 2.20 firmware. Do I need to fallback to the same version coming from CM10? Or can I use 1.85?
Found a thread on RUUs, looks like it recommends staying at your version minimum. Grabbed a copy of the 2.20 RUU but my comp won't even run the thing. Locks the joint up before it even prompts for step 1. Bad download maybe?
it takes awhile for ruu to load. i use winxp and don't bog my computer down with crap like "most" people.
those are the download links and md5 sums for 1.85 and 2.20
http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe 63d903db858667b82b5186456d0039c1
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe a40cd830e8c57109d140e1e68e2d1328
DvineLord said:
it takes awhile for ruu to load. i use winxp and don't bog my computer down with crap like "most" people.
those are the download links and md5 sums for 1.85 and 2.20
http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe 63d903db858667b82b5186456d0039c1
http://dl3.htc.com/application/htc_one_x_RUU_2.20.502.7_att_us_08022012.exe a40cd830e8c57109d140e1e68e2d1328
Click to expand...
Click to collapse
Turned out the issue was hard drive space. Dumped a buncha old albums onto an external drive and the RUU completed its run successfully. Sadly there was no change in the issue. The device remains on EDGE and I'm stuck with crummy Sense. Very deflating.
if you have an at&t evita and you are on at&t i think your problem is your sim card.
I'll attempt to get a new sim tomorrow. The office did do a "reset" on the sim but there was no change to the service. I did notice in the boot menu the S/N is different than what is listed on the sticker located on the back of the phone. Is this usually the case? or a sign of a potential conflict?
Tried a couple of different SIM cards at the office and remained on EDGE at all times. Tried the same card in a new HOX and it gained access to the 4G network with alacrity. So issue appears to be device related. Almost as if the ATT network denies the phone access to the HS networks. Possible conflict somewhere?
Having an issue where calls default to speaker phone. Only major things I done have been update to 2.15, and flash 4.2 rome such as scotts clean rom, and viper rom. Happens in any rom regardless if you wipe out all partitions or not. The thing about it is that it doesn't happen at first when you install the rom. For example i went to sleep and the issue didn't happen after testing it a dozen times before sleep. I had fix it by doing a reset after installing the rom. After the phone is fully charged I noticed the issue came back this morning. Issue happens in safe mode as well.
Have you tried running an RUU?
Sent from my Evita
timmaaa said:
Have you tried running an RUU?
Sent from my Evita
Click to expand...
Click to collapse
No Which RUU should I use for htc one x? I always run my rom installations from Team Win Recovery. Is there a mod out there to disable the dock feature of the htc one x? I heard this can also be due to a bad dock connector. If it makes any sense I never had this issue in 4.1 at all.
An RUU isn't a ROM, nor is it installed like a ROM is. You'll find RUUs at androidruu.com, I'd strongly suggest getting s-off first though if you don't already have it.
Sent from my Evita
cessna784 said:
No Which RUU should I use for htc one x? I always run my rom installations from Team Win Recovery. Is there a mod out there to disable the dock feature of the htc one x? I heard this can also be due to a bad dock connector. If it makes any sense I never had this issue in 4.1 at all.
Click to expand...
Click to collapse
RUU links are listed on my Index thread, like everything else useful for our device: http://forum.xda-developers.com/showthread.php?t=1671237
If it shows up only on Sense 5 ROMs, its probably a software issue, not a hardware issue. I wouldn't assume the dock connector only, as there are other actions which also activate speaker phone, such as flipping the phone face down (possibly try to deactivate that feature in Settings to see if that helps).
timmaaa said:
Have you tried running an RUU?
Sent from my Evita
Click to expand...
Click to collapse
redpoint73 said:
RUU links are listed on my Index thread, like everything else useful for our device: http://forum.xda-developers.com/showthread.php?t=1671237
If it shows up only on Sense 5 ROMs, its probably a software issue, not a hardware issue. I wouldn't assume the dock connector only, as there are other actions which also activate speaker phone, such as flipping the phone face down (possibly try to deactivate that feature in Settings to see if that helps).
Click to expand...
Click to collapse
I have an HTC at&t version with 2.15, what RUU do your recommend running. The att one listed in the thread?
cessna784 said:
I have an HTC at&t version with 2.15, what RUU do your recommend running. The att one listed in the thread?
Click to expand...
Click to collapse
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.
redpoint73 said:
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.
Click to expand...
Click to collapse
I am S-OFF
redpoint73 said:
Are you s-off or s-on? With S-off, you can run any RUU meant for EVITA. I would start with the AT&T version. But be aware it will replace hboot with 2.14 as well as the radio and other modules. So you will need to flash 2.15 firmware again, if you want to use Sense 5 ROMs.
If S-on, do not flash any RUU until you are s-off. SuperCID (which I assume you have) and s-on will brick the phone if you run a Jellybean RUU.
Click to expand...
Click to collapse
Gonna run RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe
Device is stuck on landscape mode right away on the ruu that I installed. I put in the usb connector to charge and it goes back to normal. So it may mean that the micro usb port went bad and is causing my phone to get stuck in dock mode.
cessna784 said:
Device is stuck on landscape mode right away on the ruu that I installed. I put in the usb connector to charge and it goes back to normal. So it may mean that the micro usb port went bad and is causing my phone to get stuck in dock mode.
Click to expand...
Click to collapse
That would appear to be the case. There are apps available on the Play Store that disable dock mode, you can try and see if that helps.
redpoint73 said:
That would appear to be the case. There are apps available on the Play Store that disable dock mode, you can try and see if that helps.
Click to expand...
Click to collapse
any permanent way to disable dock mode without an app?
I don't think so, other than having it repaired.
Sent from my Evita
cessna784 said:
any permanent way to disable dock mode without an app?
Click to expand...
Click to collapse
With root, I would think so. But I don't know how to do it, off hand. Maybe try to freeze the process "Car" with Titanium?
Freezing with Titanium is my preferred way of tinkering with such things, as its easily reversible if you find it leads to undesirable wonky behavior.
Do you have a case on your phone? My daughter always drools on my phone and the pogo pins get wet and cause dock mode. Take your case off and check
Sent from my VENOMized HoxL
Hey all, so i decided i wanted to try out some radios (was running viper xl)
and tried flashing a few different radios
from this thread and
http://forum.xda-developers.com/showthread.php?t=1694012
this section
"These are radios for flashing in Sense OR CM 10.x builds after 7/15 nightly!!!. They don't include the RIL files."
anyways, now i have been problems, phone randomly thinks sim card is being removed/inserted.
and having random reboots
tried flashing the 3.18 ruu
and flashed viper again,
and am still having these problems
so what else can i do?
any suggestions would be great
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
timmaaa said:
Well for the latest version of Viper you need to upgrade your firmware. Which build of Viper are your running?
Sent from my Evita
Click to expand...
Click to collapse
4.2.0
which firmware do i need to upgrade to ?
(i do belive my hboot was 2.15 before) but i cant seem to remember which ruu that would be
edit:
think i just found it
http://forum.xda-developers.com/showthread.php?t=2517148
is that the correct version?
Yeah that's the one you need.
Sent from my MID-1040
Thanks it had been forever since I'd run an ruu , completely forgot about the firmware upgrade
Sent from my HTC One XL using Tapatalk
No problems.
Sent from my MID-1040
timmaaa said:
No problems.
Sent from my MID-1040
Click to expand...
Click to collapse
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
deepsouth06 said:
To add to this thread so a new one doesnt need to be created, I to am having problems with my Sim card. I have tried flashing different radios, I have done the 2.15 firmware upgrade. I am about ready to give the 5.18 RUU a run and then go through the process of re-flahsing viper.
Click to expand...
Click to collapse
Please post your bootloader details, your recovery version, your current ROM and kernel, and the exact problem you're facing.
Sent from my Evita
timmaaa said:
Please post your bootloader details, your recovery version, your current ROM and kerncontinuehe exact problem you're facing.
Sent from my Evita
Click to expand...
Click to collapse
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
timmaaa said:
I believe the radio is your problem, you need to make sure you have one of the radios that came bundled with Sense 5 releases installed. They'll be the ones that are 1.31 and upwards.
Sent from my Evita
Click to expand...
Click to collapse
Ok, I read something similar to what you are saying and I did flash a radio 1.31 from this link with is 2.15 firmware. http://forum.xda-developers.com/show....php?t=2517148. However the same problem was still happening. After flashing the current radio (from the above attachment), what I have noticed is that the No Sim icon only seems to happen when I have WiFi turned on for an extended time, this was just a brief observation from last night and this morning.
I am about to flash a stock RUU (possibly the 5.18) to 1) get the phone up to date with the latest firmware and 2) to see if this will help with my Sim Card problems. Or should I use a different RUU to start from Stock again?
Also When looking at the Radios thread I dont see any radios that are 1.31 and up for ATT. All of them seem to begin with 0.xx. The thread i am looking at is http://forum.xda-developers.com/showthread.php?t=1694012
The latest RUU is probably your best bet.
Sent from my Evita
timmaaa said:
The latest RUU is probably your best bet.
Sent from my Evita
Click to expand...
Click to collapse
With S-Off and my CID all 1s I wouldnt have to worry about doing the root again? After the RUU i should be able to install TWRP again and then a custom rom?
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
deepsouth06 said:
Hboot details are in the screen shot. TWRP 2.7.0. Viper 4.2.0. Kernel is beastmode 3.4.10.
So my problem that I am having is that my phone continues to loose all data and voice service due to the phone telling me that there is no sim. I have tried different Radios with no differnce. sometimes the phone will start reading the sim if I toggle the phone into airplane mode.
Click to expand...
Click to collapse
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
timmaaa said:
Your bootloader will remain unlocked, your CID will remain as 11111111, and your s-off status will survive the process. It's as simple as flashing TWRP afterwards and then the ROM of your choice.
Sent from my Evita
Click to expand...
Click to collapse
Much thanks. I will be trying this out.
---------- Post added at 10:06 AM ---------- Previous post was at 10:04 AM ----------
redpoint73 said:
Did the issue start after flashing the ROM, or any other mods. Of did it just randomly start happening? Have you tried the stock kernel?'
Have you tried the trick of simply putting Scotch tape on the SIM (don't cover the contacts) to "fatten" it and force it to make better contact in the SIM tray? Loose SIM tray is known to cause the same issue.
Click to expand...
Click to collapse
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
deepsouth06 said:
To my best knowledge the issue started happening randomly. Phone was working fine for some time while I was one Viper. I believe but not 100% I started noticing this after a drop so a loose tray could very well be the problem. Also this issue was present with the stock kernel as well.
Click to expand...
Click to collapse
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
redpoint73 said:
Those answers (randomness, possible dropped phone) to me point to loose SIM tray. Also, have you tried taking the SIM out, and putting it back in, to make sure its seated properly (if dropped, it could have loosened it)?
If none of the suggestions work, you might also try to get a new SIM from your carrier.
Click to expand...
Click to collapse
No i havent tried taking it out. I will try that out tonight. If all else fails I may end up going for a referb phone, but now with 5.18 I might hold off for as long as i can.
Thanks for your help as well.
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Sorry for the long post.
deepsouth06 said:
To all, would disabling Google play services have any affect on the SIM card. I ask because after I flashed the 5.18 RUU I flashed a recovery and the flashed Viper. Phone was up and running about 1pm yesterday. Phone ran good with no problems the rest of day. This morning I unplug the phone from charger and within an hour or so I'm already at 87 percent battery. Looking up what is keeping the phone awake the culprit Google play services ( getting very annoyed of this app) so I force stop and disable play services and within one minute I get that icon of no SIM card. So with my story does google play services have any affect on the SIM cards? And how can I limit the wake locks of Google checkin.
Click to expand...
Click to collapse
I doubt that Google Play would have that effect on the SIM. I think its just a coincidence (red herring).
deepsouth06 said:
Sorry for the long post.
Click to expand...
Click to collapse
No need to be sorry. More detail is almost always better. Its the short posts that I have a problem with; where people ask for help and don't give any specifics or details. Makes it much harder to help.