Hi, I currently have problems getting my WiFi to work. Every ICS ROM/Kernal I've tried (includes KingCobra, mwakious,Coolexe, Viper3D) my WiFi has been dysfunctional. It would be grayed out saying "Turning on..." or "ON" and the toggle won't work at all. I have tried WiFix as well. It worked once for me and WiFi problems start happening again over night. Does anyone have a solution to my WiFi problem?
HTC EVO 3D GSM (Rogers)
S-OFF using CWM
HBOOT: 1.49.1107
RADIO: 11.25.3504.04_M
n3ik said:
Hi, I currently have problems getting my WiFi to work. Every ICS ROM/Kernal I've tried (includes KingCobra, mwakious,Coolexe, Viper3D) my WiFi has been dysfunctional. It would be grayed out saying "Turning on..." or "ON" and the toggle won't work at all. I have tried WiFix as well. It worked once for me and WiFi problems start happening again over night. Does anyone have a solution to my WiFi problem?
HTC EVO 3D GSM (Rogers)
S-OFF using CWM
HBOOT: 1.49.1107
RADIO: 11.25.3504.04_M
Click to expand...
Click to collapse
I don't know about any of the roms u listed off the top of my head, but a lot of roms need the latest RADIO to work as intended, which I believe is:
11.25.3504.06_M.
i have the same problem. im s-off, rooted. tried updating the radio, adb pushing boot.img, flashing stock rom, clean wipe and flashing custom rom, gui kernel flash... nothing worked to fix my wifi problem.
is my wifi really dead? do i have to send it to HTC for repairs?
any help is welcome.
eddyz said:
i have the same problem. im s-off, rooted. tried updating the radio, adb pushing boot.img, flashing stock rom, clean wipe and flashing custom rom, gui kernel flash... nothing worked to fix my wifi problem.
is my wifi really dead? do i have to send it to HTC for repairs?
any help is welcome.
Click to expand...
Click to collapse
Run a RUU... that way u eliminate software as a factor if it still doesn't work, it's hardware
Sent from my Evo 3D GSM using xda app-developers app
what do you mean by run a RUU?
eddyz said:
what do you mean by run a RUU?
Click to expand...
Click to collapse
I believe RUU are ROM's that come with the original phone itself. Theres a thread with all of them here http://forum.xda-developers.com/showthread.php?t=1208485
dessolator666 said:
Run a RUU... that way u eliminate software as a factor if it still doesn't work, it's hardware
Click to expand...
Click to collapse
And thanks for the suggestion, I haven't tried that yet :cyclops: I'll keep an update on how it went
oh. i did try that, but bumped into an error using the ruu.exe.
i'll give it a shot again.
Does anyone happen to have the Rogers ICS RUU in a different link? The one on the thread always has "connection time out" halfway through the download
eddyz said:
oh. i did try that, but bumped into an error using the ruu.exe.
i'll give it a shot again.
Click to expand...
Click to collapse
Did you do fastboot oem lock? (Do not do this with custom hboot like revolutionary or jopunutbear or you will have a very expensive paperweight)
dessolator666 said:
I don't know about any of the roms u listed off the top of my head, but a lot of roms need the latest RADIO to work as intended, which I believe is:
11.25.3504.06_M.
Click to expand...
Click to collapse
Thanks for the suggestion, I just updated the radio and reflashed some of the rooms with Full wipe. Still having the same issues
n3ik said:
Thanks for the suggestion, I just updated the radio and reflashed some of the rooms with Full wipe. Still having the same issues
Click to expand...
Click to collapse
My guess would be that the actual WiFi antenna died for some reason... I would try to flash a RUU just to be sure, but likely a hardware problem so you will likely be sending it for repair which is a problem in and of itself as htcdev unlock doesn't work with phones with a replaced motherboard. Bottom line, try the RUU it might work
dessolator666 said:
My guess would be that the actual WiFi antenna died for some reason... I would try to flash a RUU just to be sure, but likely a hardware problem so you will likely be sending it for repair which is a problem in and of itself as htcdev unlock doesn't work with phones with a replaced motherboard. Bottom line, try the RUU it might work
Click to expand...
Click to collapse
Okay, thanks! :cyclops: and would you happen to have a mirror for the Rogers ICS RUU? :crying: the download keeps timing out
Been having the same issue for awhile too. Running PredatorUnity Rom. Used flashgui image to flash the ANA v7 kernel and after it rebooted the WiFi was working no problems at all. Then after about 30min it stopped. What started happening was it would say that it was on but would not show any WiFi hotspots only the previously connected showing it out of range. Then completely stopped giving me the grayed out turning on error. Really weird stuff. Been trying to get it working again since Sunday
Sent from my HTC EVO 3D X515m using xda app-developers app
soliditalstud said:
Been having the same issue for awhile too. Running PredatorUnity Rom. Used flashgui image to flash the ANA v7 kernel and after it rebooted the WiFi was working no problems at all. Then after about 30min it stopped. What started happening was it would say that it was on but would not show any WiFi hotspots only the previously connected showing it out of range. Then completely stopped giving me the grayed out turning on error. Really weird stuff. Been trying to get it working again since Sunday
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
Have you tried removing your SIM card? I tried that before and it actually ended up working. My thought was it was the WiFi Reigional problem, however, after trying out the WiFix it did the trick but after that I still ended up where I started. Now that method no longer works for me. Maybe it might for you?
n3ik said:
Have you tried removing your SIM card? I tried that before and it actually ended up working. My thought was it was the WiFi Reigional problem, however, after trying out the WiFix it did the trick but after that I still ended up where I started. Now that method no longer works for me. Maybe it might for you?
Click to expand...
Click to collapse
Hey bud! took your advice and removed the simcard and reflashed that kernel that initially worked. at first was giving the same issues.but after rebooting back into recovery and doing another wipe dalvik/cache now wifi turns on and off no problem anymore .which is good..bad thing is , doesnt see any wifi connections still..looks like we are close
soliditalstud said:
Hey bud! took your advice and removed the simcard and reflashed that kernel that initially worked. at first was giving the same issues.but after rebooting back into recovery and doing another wipe dalvik/cache now wifi turns on and off no problem anymore .which is good..bad thing is , doesnt see any wifi connections still..looks like we are close
Click to expand...
Click to collapse
I just flashed my original Rogers RUU.. WiFi worked only for a bit, then it froze and crashed. Now I am stuck with a Locked Unrooted bootloader and the same grayed out wifi button. I have no more ideas left to try:crying:
EDIT: I actually got WiFi to work! after flashing the RUU rom using the P86IMG technique, I ran the RUU.exe and everything went well. Now my WiFi is fully functional. I'll let you know how it goes when I leave it over night. I might have solved the problem
n3ik said:
I just flashed my original Rogers RUU.. WiFi worked only for a bit, then it froze and crashed. Now I am stuck with a Locked Unrooted bootloader and the same grayed out wifi button. I have no more ideas left to try:crying:
Click to expand...
Click to collapse
i did the same thing. I flashed the ICS Rogers RUU and same issue.. but now im on hboot 1.5* UNLOCKED via htcdev.com and rooted as well actually. flashed my backed up recovery.img file so now on STOCK ROM ..this blows
i got my 3d from europe. should i flash the EU ruu or the rogers will work as well?
eddyz said:
i got my 3d from europe. should i flash the EU ruu or the rogers will work as well?
Click to expand...
Click to collapse
Europe would be preferable, you would prolly fail the CID check on the Rodgers one
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe
just to make sure, this is the one i plan on downloading and running.
Related
hi im having strange issues, i though was the rom i was using, but i change from rom and my issue persist, when i leave iddle my phone, suddenly or reboots or shutdown :S i guess this its since i update radio to latest, anyone have this issue? i want update all firmware but i read from some, the cellphones are bricked.
im using in mexico.
any help? thanks a lot
Im having this same issues and its getting really annoying . I had a htc screen loop problem so i re locked the phone and ruu'd back to stock of the latest update (or rather flashed the PGIMG86 file or whatever) and the phone literally now reboots its self whenever it feels like , most noticeable if i leave it alone for a little while or press the power button to turn the display off. I re rooted and am now on freshrom and its still doing it occasionally. I think it might have been doing it before i ever did that relock though, too. Is this a problem with the new firmware? Is there anyway to downgrade , like an odin type of application?
this sounds like a kernel issue. the first guy (OP) i assume you are on GSM being out of the united states... i'm not sure i can provide you a whole lot of help there because i am not familiar with the GSM version of the EVO 3D. however, random rebooting can usually be attributed to a few general things, so either of you can trouble shoot and start here....
bad download of boot.img (files were corrupted somewhere)
-you should try flashing another kernel/ROM combo where users are NOT reporting
any issues whatsoever. also, try re-downloading your existing .zip just to make
sure the one you are using is not corrupted.
remove your micro SD card...
-most people don't think of this, but a bad SD card can cause random reboots. it is
a disk, and if your device is getting errors or something when trying to read it, it
will reboot to check the disk. start by moving apps OFF the SD card, then removing
the SD card entirely. if the reboots go away, that was your issue, and time for a
new SD card. i had this same issue when i first got my Evo, thought it was the
phone, turned out it was a bad card.
that's a good place to start. come back with questions/results.
i just deleted everything off of the sd card and it happened again afterwards. also it was happening before re - locking of the bootloader , and across several roms and kernels. totally lost. i also had it happen earlier today with no sd card in the phone , too. It was even happening on complete stock.
was it happening when you first got the phone? if so, time to take it to sprint
Sent from EVO 3D using XDA premium
its a replacement from asurion , im all out of insurance claims with them , lol . it was my gf's and she wanted a shift so she purchased one off of craigslist and gave me the 3d because my sgs2 has a damaged usb port. as soon as she got it in the mail she imeediatley gave it to me and i rooted it right away , lol , so im really not sure. id like to return it to factory stock before the ota update ,as i have a strange feeling it has something to do with it . i had it for a couple hours completley stock no nothing , then took the ota update and proceeded to root. i dont recall a reboot before that.
cobraboy85 said:
this sounds like a kernel issue. the first guy (OP) i assume you are on GSM being out of the united states... i'm not sure i can provide you a whole lot of help there because i am not familiar with the GSM version of the EVO 3D. however, random rebooting can usually be attributed to a few general things, so either of you can trouble shoot and start here....
bad download of boot.img (files were corrupted somewhere)
-you should try flashing another kernel/ROM combo where users are NOT reporting
any issues whatsoever. also, try re-downloading your existing .zip just to make
sure the one you are using is not corrupted.
remove your micro SD card...
-most people don't think of this, but a bad SD card can cause random reboots. it is
a disk, and if your device is getting errors or something when trying to read it, it
will reboot to check the disk. start by moving apps OFF the SD card, then removing
the SD card entirely. if the reboots go away, that was your issue, and time for a
new SD card. i had this same issue when i first got my Evo, thought it was the
phone, turned out it was a bad card.
that's a good place to start. come back with questions/results.
Click to expand...
Click to collapse
I'm using CDMA as well, my carrier has CDMA, and this it's new I tried other roms,I was thinking maybe ROM, but I'm using mean ROM that uses stock kernel, so I noticed this happens only when I'm not using my phone, and start happens since y flash new radio (coincidence maybe? ) but it's annoying I will check if it's happen again I'm this ROM, only happens once in this(turn it off)
.......................................................
Sent from my loved EVO 3D ;D
zen kun said:
I'm using CDMA as well, my carrier has CDMA, and this it's new I tried other roms,I was thinking maybe ROM, but I'm using mean ROM that uses stock kernel, so I noticed this happens only when I'm not using my phone, and start happens since y flash new radio (coincidence maybe? ) but it's annoying I will check if it's happen again I'm this ROM, only happens once in this(turn it off)
.......................................................
Sent from my loved EVO 3D ;D
Click to expand...
Click to collapse
exact same situation as me man , it mostly happens when i let the phone go idle , although it just happened when i was trying to edit the bookmarks widget on my home screen , and it seems to have happened after i updated the radio except i didnt flash i took the ota update.....for me its every rom , rooted or unrooted too
Ok happens again with different ROM, so I guess it's the radio, bit the weird thing is turn off the phone, no just reboot
So anyone knows how to revert to .9 radio? Or any solution? Thanks
.......................................................
Sent from my loved EVO 3D ;D
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
I was having the same issues. Random reboots and random shut downs. Really getting frustrating. So I figured I would unroot my phone and take it into Sprint. I followed scrosler's guide to unroot but I used the latest PG86IMG.zip from Mr. Esp's thread. Of course this brought me up to hboot 1.5 but the random restarts and shut downs have stopped.
reaper24 said:
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
Click to expand...
Click to collapse
I'm on hbot 1.4 I don't want lose s-off and if I upgrade I will do it but safe since I read some files was causing some bricks that's why I only update radio
.......................................................
Sent from my loved EVO 3D ;D
you can always go back to your previous radio too man.
also, flashing from 1.4 hboot you will not lose s-off with freezas all in one zip... I just did it today, no issues at all.
Sent from EVO 3D using XDA premium
cobraboy85 said:
you can always go back to your previous radio too man.
also, flashing from 1.4 hboot you will not lose s-off with freezas all in one zip... I just did it today, no issues at all.
Sent from EVO 3D using XDA premium
Click to expand...
Click to collapse
thanks i will try perhaps i read in freeza all in one some dudes get bricked
zen kun said:
thanks i will try perhaps i read in freeza all in one some dudes get bricked
Click to expand...
Click to collapse
no no... the ones that were bricked were the ones that tried to flash parts of TrevE's package. nobody had issues with freezas if I remember correctly... but... you should read before you flash it
Sent from EVO 3D using XDA premium
reaper24 said:
If you guys are both cdma and hboot 1.5 already.. Why don't you wipe everything in recovery just not your SD cards...
Hboot 1.5 S-ON
Then relock your phone run the RUU 2.17 exe and let it do it's thing then update your profile and so on.
Then just unlock your phone again with the unlock code should fix you guys up....
How are you guys flashing also? What recovery do you use?
Click to expand...
Click to collapse
I did everything you suggested here , down to a tee . I re locked the phone , except for i used the PG86IMG.zip file for 2.17 and loaded it in the bootloader to go back to stock after re locking. I let it sit for a day and then got bored and unlocked and rooted again and am on FreshRom. My original recovery was clockwork but now im on TW , hoping that itd help. Guess im gonna have to re-lock again and RUU back to an older base instead of 2.17. I waanna see if that fixes this problem.
cobraboy85 said:
no no... the ones that were bricked were the ones that tried to flash parts of TrevE's package. nobody had issues with freezas if I remember correctly... but... you should read before you flash it
Sent from EVO 3D using XDA premium
Click to expand...
Click to collapse
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
twister99403 said:
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
Click to expand...
Click to collapse
oh right "crosses finger", they must be flashed on recovery??? i have the "touch" clockworkmod recovery
zen kun said:
oh right "crosses finger", they must be flashed on recovery??? i have the "touch" clockworkmod recovery
Click to expand...
Click to collapse
NO!! lol put the zip file on the "root" of your sd card and reboot into BOOTLOADER will ask to update, click yes...
make sure to take it off your sd card after updated...
twister99403 said:
i'm also hboot 1.4 and flashed freezas and everything went perfect, just do it man
Click to expand...
Click to collapse
Ya I remember the mess with that it caused for folks that screwed something up they didn't read the directions....
I am having random reboots. Evo 3D CDMA s-off hboot 1.4 . On all roms I go to. Cannot be fixed by just changing the battery. Can anyone please help
I've had "random" reboots, CDMA S-ON hboot 1.5. They only happen if the screen is turned off when it is not charging. If it is charging, no reboots. If it is not charging, the screen must stay on or it will reboot. Besides the rebooting it functions very well. These reboots happened before and after I
rooted. I tried Mean ROM, it still rebooted. Went back to stock and OTA to ICS, and it still rebooted.
I don't know if this is related to your reboots, but I would appreciate assistance with my reboots too.
I experienced some random reboots on my old htc hd.i had to use to warranty to repair it.
Sent from my HTC EVO 3D X515m using xda app-developers app
So no other helpful posts???
I had the same issue with reboots. I flashed the turn up to date 2.17 firmware bits. Now I'm on the newest firmware bits by freeza. Works great.
Can anyone link me to the freeza firmware? Everybody seems to say it helps them.
I'm totally stock. Updated to ICS OTA and got non stop reboots and freezing. Took the sd card out and phone runs flawlessly. Reformatted and reloaded all backed up folders to sd card and random reboots started again. For me, something on my sd card isn't playing nice with ICS. I'll have to re install my apps slowly to see what's causing it.
Jimlarck said:
Can anyone link me to the freeza firmware? Everybody seems to say it helps them.
Click to expand...
Click to collapse
Here you go: http://forum.xda-developers.com/showpost.php?p=21374142&postcount=131
Save the Drama for your Mama with Tapatalk 2
Jimlarck said:
I am having random reboots. Evo 3D CDMA s-off hboot 1.4 . On all roms I go to. Cannot be fixed by just changing the battery. Can anyone please help
Click to expand...
Click to collapse
I think that this is a software problem. I had random reboots when the phone (GSM version) was running the original firmware (Gingerbread 2.3.4) and with some early unofficial ICS ROMs. After upgrading to KingCobra 1.2 and later the problem disappeared.
So no fix..?... I'm on CDMA and have confirmed it is a software issue.
Jimlarck said:
I am having random reboots. Evo 3D CDMA s-off hboot 1.4 . On all roms I go to. Cannot be fixed by just changing the battery. Can anyone please help
Click to expand...
Click to collapse
this happened to me all the time with the 1.06 radio. Never happened when I went back to .97. So far seems ok on the new 1.09
Jimlarck said:
So no fix..?... I'm on CDMA and have confirmed it is a software issue.
Click to expand...
Click to collapse
I think that if you upgrade your phone, as I did, the problem will go away.
After the original firmware I used only ICS custom ROMS. If you want to go custom, please choose one good ROM like CoolICS for CDMA
http://forum.xda-developers.com/showthread.php?t=1668918
and flash it on your phone (follow the instructions carefully to avoid problems).
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
hurrrtin said:
This happened to me randomly. Only thing that works is RUU back to stock and go through the motions. You won't lose S-OFF, so you can then come back.
Click to expand...
Click to collapse
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Bartikus said:
I need to RUU all the down to 1.15 correct? Then will I need to Moonshine again?
Click to expand...
Click to collapse
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
---------- Post added at 12:18 PM ---------- Previous post was at 12:13 PM ----------
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
It might take a little while for it to change from roaming back to normal. Just give it time after you RUU.
Bartikus said:
So I haven't really found anyone with as specific a situation I'm in so I figured I'd make a new thread.
I was running a CM10.1 build from late July, which still had some bugs but was bearable. I upgraded to CM10.2 to try it out, but it was buggier than the CM10.1 build. I saw that the bugs were fixed in the latest build of CM10.1 so I flashed that. Since then I've been stuck in Roaming and can't activate my phone.
Each time I flashed I restored my 100% stock backup (I have a nandroid from the day I got the phone). Every flash was a clean install wiping data/cache/dalvik. Was first roaming when I reverted back to CM10.1, but restoring my backup and even flashing CM10.2 again I'm roaming still.
Basically, once I was roaming, I haven't stopped regardless of ROM.
And I'm sure someone will ask, I have S-off.
How do I go about fixing this?
EDIT: I've tried a clean flash of the same ROM with the sim card removed and tried changing the subscription type after like I've seen in another thread, but this did not work.
Click to expand...
Click to collapse
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
PhantomApollyon said:
I'm having the exact same issue after doing the same thing you did, not sure where to go with it at this point, nothing is working
Click to expand...
Click to collapse
Did you try to RUU back to 1.15? I just tried running it and it crashed, not sure if it's my computer or what
hurrrtin said:
If you are S-OFF, then yes- RUU back down to 1.15. You won't need to moonshine again.
Click to expand...
Click to collapse
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Bartikus said:
I tried running the RUU from here http://forum.xda-developers.com/showthread.php?t=2017525
I ignored the first part about relocking since I assumed since I have s-off I don't need to, and I immediately tried to run the .exe as admin and it crashed.
UPDATE: I've relocked it now but the RUU still crashes before doing anything.
Click to expand...
Click to collapse
try grabbing the RUU from the blue link in my sig
.torrented said:
try grabbing the RUU from the blue link in my sig
Click to expand...
Click to collapse
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Bartikus said:
Downloading the RUU now. I've also tried flashing the 1.15 hboot and recovery, but they don't seem to have done anything. I'm still on 2.06... I unlocked my phone originally with moonshine, so my bootloader used to say moonshine s-off. now it says tampered/locked so I think hboot worked, but the recovery doesn't seem to have done anything.
UPDATE: The RUU ran it's course. Seems like the file for the other link was just bad (I had downloaded it twice). The phone is attempting to activate now, but it still can't get a signal. I know the signal at my house is usually pretty bad, but leaving it on the window sill usually does the trick. If worse comes to worse, could I at this point return it to Verizon without them knowing what's up?
Click to expand...
Click to collapse
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
.torrented said:
the point of the 1.15 hboot is so the RUU works... if you want to return to stock to take to vzw I would follow the restore guide, i believe its posted in the regular dev section and not the original dev section
edit* this one right here: http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Yeah the RUU seemed to work, I just still can't get a signal. Phone says no service and I can't get past the activation screen. I say "seemed" to work because I can't check in settings because I can't get past the activation... but the bootloader looks like stock again, whereas it said tampered before the RUU.
Thank you for the help by the way, I appreciate it.
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Reset the Phone
Bartikus said:
RUU worked, I'm on 1.15. However, it didn't solve my no service problem. Could this be as trivial as a SIM problem? Is there anything else it might be?
Click to expand...
Click to collapse
After RUU you must Reset the phone from STOCK recovery,
finanandroid said:
After RUU you must Reset the phone from STOCK recovery,
Click to expand...
Click to collapse
Worked like a charm, thanks!
Bartikus said:
Worked like a charm, thanks!
Click to expand...
Click to collapse
U welcome! Glad you finally back on business :good:
finanandroid said:
U welcome! Glad you finally back on business :good:
Click to expand...
Click to collapse
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
RUU to get back to Stock Recovery
chipymunk said:
Where can I find the STOCK recovery? I've been going crazy with this stock on roam thing.
Click to expand...
Click to collapse
In order to recovery or restore the original phone factory setting you have to do RUU and Reset Phone*** is the way to get back
Stock recovery(= reset phone) to work properly. Even if you are on a Stock Rom it has a custom recovery so doing factory reset wont
work to restore the original phone setting.
after RUU you must do a phone reset either from setting>back up & reset or from the bootloader factory reset is the same Stock Recovery.
I read somewhere that flashing this Rom Stock rooted fix a roaming thing so you can give it a shot http://forum.xda-developers.com/showthread.php?t=2471836
I've had my Evo LTE since launch. Ran many many ROM's. Was on CM11 for quite some time and then all the sudden in my pocket it went into a bootloop. But, not a normal bootloop. It will boot all the way into android, I can unlock the screen sometimes even use it for a while then reboot. Many times it will get to the lockscreen only and then reboot, it will do his cycle indefinitely. I know this type of bootloop usually indicates a kernel/ROM mismatch, but all the ROM's I've been using since this started are the kernel included with the ROM and no customizations. I've done the ViperUU, I've re-flashed firmware. Wiped absolutely everything, except external sdcard. Sometimes it will run for a few hours before it starts again, and sometimes it start rebooting immediately. I'm at the end of my knowledge of what other steps to take. Those of you with mad skills, I petition your expertise please!
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
numel007 said:
What version of cm were you using? Deck's build or nightlies?
Sent from my EVO
Click to expand...
Click to collapse
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
wolfclan68 said:
Decks!
After it glitched I tried PA, Omni, and stock. Same issue on all.
Click to expand...
Click to collapse
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
I didn't realize the HTC RUU was available. I thought ViperUU was the only one. I will give that a shot. Thanks guys! I will report the results.
jocarog said:
You might want to try a RUU for your current firmware... It might be time for a refresh for your phone, then unlock, root and s-off again...
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
FinZ28 said:
Agreed. I would RUU with the most recent OTA and go from there. If you're S-off you'll still be S-off once you run the RUU. Afterwards, I'd stay stock for a few days and see how the phone acts. If the issue persists you most likely have a hardware issue somewhere. If everything runs okay afterwards you can unlock your bootloader again, install a custom recovery and flash a ROM.
Here is the link to the 3.17 RUU:
http://www.htc.com/us/support/htc-evo-4g-lte-sprint/news/
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
wolfclan68 said:
Posting results as promised. The HTC RUU seems to have fixed the problem, haven't had a reboot since the RUU 3 days now. However during this process I was without a phone for 6 days, I picked up an LG G2. This phone kicks. Got it at Best Buy out the door for $48, CRAZY cheap for such a phone. I guess I'll be getting rid of my EVO.
Click to expand...
Click to collapse
I'll take it, lol. I need a working test device.
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
FinZ28 said:
I'd like to test and see if an older RUU works with the new Sense 5 ROM setup
Sent from my EVO LTE
Click to expand...
Click to collapse
Of course that would be the first thing I'd test . Just can't do it on my everyday/work device.
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Uzephi said:
Try flashing the recovery flashable radio?
Something could have borked the radio partition.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
badogg said:
Ok, I give up. I've tried everything I can think of, but I can't get 4G to stick on, and trying to run the 3.06 RUU gives me error 170.
Here's what happened. Yesterday I flashed Kickdroid 2.0 with the CDMA patch from: http://forum.xda-developers.com/showthread.php?t=2634126
- Everything seemed to install fine, and initially 4G was up. But within about a minute 4G disconnected and I no longer had any mobile data.
- So then I did a full complete wipe via TWRP - doing the factory reset, then using the advanced wipe on everything except internal storage - then restored my backup of BadSeed's Tranquil rom. It came up fine initially but then within about a minute 4G disconnected and I was put back at 3G.
- Re-wiped everything same as before, then flashed the Tranquil Rom from scratch. - Same problem. 4G connects initially then drops to 3G.
- Updated TWRP to the beta .6 version as suggested by the Kickdroid dev and re-flashed and did all those same steps again and still having same problem
- At one point last night I left the phone alone and after a long time with the kickdroid Rom re-flashed it asked me which carrier I had. I chose Verizon and then 4G stuck on for a while. Then, it lost it's connection again to 4G. This Rom never gave me any 'Service'. The lockscreen always said 'no service'
- This morning, I flashed the latest Viper and it too initially gives me 4G then about a minute later that drops and I'm stuck on 3G.
- I thought maybe it was my SIM card, so I put it in my rezound and it works just fine in that phone.
- I've been trying to RUU using the 3.06.605.4 RUU from: http://forum.xda-developers.com/showthread.php?t=2612740 but I keep getting error 170 saying that the device wasn't found and to plug in my usb cable.
I suspect that there is something in the CDMA patch that has done this. I say that in hopes to help narrow the problem down not to blame anyone, as I do accept the responsibility to what I have flashed on my phone, so please don't take it that way. I don't know what could remain after wiping and re-flashing but it seems as thought something has.
Anyhoo, I'm getting a little desperate at this point and hoping someone can help me out. Much appreciated...
Click to expand...
Click to collapse
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
badogg said:
Lol, of course the one thing I forgot to mention that I did. I flashed the radio from .torrented's thread as well.
I think at this point I'd like to just RUU it anyway. Could it be that my bootloader is still unlocked and I have TWPR as my recovery?
Thanks a lot guys...
Click to expand...
Click to collapse
Bootloader unlocked matter to RUU , TWRP nope.
finanandroid said:
Did you update HTC driver? then trying to RUU from bootloader, Fastboot usb, with the latest Hboot updated* (1.54.0000)= 3.06.605.4 version.
---------- Post added at 01:34 PM ---------- Previous post was at 01:23 PM ----------
Bootloader unlocked matter to RUU , TWRP nope.
Click to expand...
Click to collapse
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
badogg said:
I would expect a problem later on if it were the bootloader being locked still, not int he beginning and then saying that the device isn't found. Or am I totally wrong and should just re-lock the bootloader and try again?
Click to expand...
Click to collapse
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off Thanks to beaups
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
finanandroid said:
Well you mention error 170, usually its HTC Driver outdated, thats the reason that I suggest Driver update.
thought first have a working ADB/fastboot to see your phone. usb 2
you need to lock the Bootloader in order to run Ruu 3.06.exe (no problem because after RUU is done, Rumrunner unlock and S-Off
you need to update the Stock Hboot version to 3.06. thanks to Torrented
Here the link updated thanks to Phaded http://forum.xda-developers.com/showthread.php?t=2293919&highlight=flash+radio
Click to expand...
Click to collapse
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
badogg said:
I tried the updated drivers earlier and still get the error 170. I'm wondering if there is just something wonky with my work computer that isn't working right. I'll try locking bootloader and running RUU from a laptop and see what happens. Thanks for the assist! :highfive:
Click to expand...
Click to collapse
a pleasure
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Uzephi said:
Any other android devices hooked up to that PC? I had 170 error when having both Rezound and DNA plugged in. The program may be trying to look at the other device port instead of the DNA port.
Try with locked boot loader and stock recovery. After I got rid of error 170 I got an error in the 150's (not the one mentioned in the ruu thread). It was because of custom splash image and custom recovery.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Interesting, I don't have anything connected, but I'm sure I have drivers loaded for my nexus 7
Which drivers for HTC are you using? The ones from HTC sync or the ones from pdanet? I found the pdanet ones work better for everything but HTC sync (which, who honestly uses? Lol)
Sent from my DNA using my mind.
Well, I let htcsync update the usb drivers and now the RUU is updating the image now.
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
badogg said:
Ok, this persisted through the RUU. Rom booted up, got 4G initially, then went to 3G.
Click to expand...
Click to collapse
after Ruu you most do a factory reset* from stock recovery
All that is usually needed is to restore the NV partitions on the device.
To do this, flash a stock rom and stock recovery.
Perform a factory reset in stock recovery.
Your radio should then function normally again.
No need to RUU or any of that, just a stock rooted rom and stock recovery are sufficient.
The key factor is the factory reset in stock recovery.
So if you did the RUU already, and did not do the factory reset in stock recovery, then that's why you still have an issue.
finanandroid said:
after Ruu you most do a factory reset* from stock recovery
Click to expand...
Click to collapse
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
badogg said:
omg, duh!! I knew that, just forgot to do it.
That seems to have fixed it. +150,000 internets to you!!
Click to expand...
Click to collapse
glad :good: you got it !
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Sutko82 said:
@santod040 which stock rom do I need to flash and what is stock recovery? Do I have to do this with adb comands or use twarp like normal flash so I can get my radio working correctly again and 4g back? Any one that can point me to what I need to do here is greatly appreciated. Thank you!
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
My full odex stock Rom in the dev section is sufficient.
If there isn't a stock recovery posted anywhere I'll locate one for you.
Then you flash the Rom in your current recovery.
After you boot, reboot to hboot.
Then fastboot flash recovery nameoffile.img.
Then either factory reset from Recovery or from the roms settings option.
Sent from my HTC6500LVW using Tapatalk
Pls locate stock recovery as I am not sure which one to use. I am downloading your odexed stock rom as we speak. I appreciate this very much! @santod040
Sent from my HTC6435LVW using Tapatalk
---------- Post added at 11:48 PM ---------- Previous post was at 11:43 PM ----------
After boot type in command prompt reboot to hboot or can I just type adb devices and then flash recovery
Sent from my HTC6435LVW using Tapatalk