Looking for some input...
Im on .8 and s-off. had no issues. A couple days ago I updated to the .11 radio from one of the zips in the dev section. No problems. Then yesterday, my wifi died. I get either an endless "turning on" or a "error' when trying to use it. Ive used the firmware packages in the dev section to rewrite firmware, reflashed the .11 radio, and also tried reflashing the stock kernel. Nothing... No Changes.
Anything I am missing here? Ive been an avid flashaholic since the original EVO days, so Im no novice.
HTC is really screwing us all over without a damn working RUU
Related
Lets see if anyone can help....a lot of this talk of rooting and flashing is over my head...My atrix is running 2.3.4. It was like this when I got it. The wifi won't turn on at all. It only shows error. Is there anyway that I can put it back to 2.2? Or is there anyway to fix the error. Someone told me the kernels may be different??? Is putting a different ROM on the phone very difficult?
Where did you get it from?
yes it may be over your head a little but no means to stop reading up on it and remember to search before your post - there is another thread of this that was recently posted.
http://forum.xda-developers.com/showthread.php?t=1180494&highlight=wifi+error
none the less. we would need more details. what rom you are using, what version of the device you have (US or Intl) key would be going through the thread you got it from. but more than likely the cause is you flashed a kernel/rom that doesn't work with your device it will be an easy fix once the details are given.
I had this issue too... I tried a few different methods to remedy it but the only one that worked was flashing a new ROM.
okay it is a US Version...4.5.91
kernel version....2.6.32.9 ( then below that is says [email protected] #11)
ok so you used an at&t rom on an at&t device? and i assume u kept the same kernel.
No...the phone came like this...I didn't do any of the updates or anything.
I had the same issue after I restored once. Could not fix it...had to reflash a ROM and the problem was fixed.
sent from my unlocked MB860 via Tapatalk
okay so is reflashing the ROM difficult? Is there any thread on here or somewhere else that I can read up on that would be of help doing this. I don't wanna brick this phone but I need the wifi or my data plan is screwed...
I hate to revive this thread but I have a wifi error I can't resolve. I first got it on 1.8.3 and flashed to 2.3.4 and it was gone. Then when I tried to install the new adroidmarket.apk, I got the wifi error and it won't go away no matter how many roms I try to or how many times reflash 2.3.4.
Essentially, wifi says there's an error and any time it tries to turn on, it reboots the phone. I've tried Alien, and Ninja and neither of them worked. I haven't tried piCrust yet.
I rooted my phone using this guide. I wanted CM7 on here, so I flashed the MR2.5 radio. My phone came with MR1. It flashed properly, but now I have no signal and it shows me as having no baseband.
What did I screw up? From my knowledge of radios from my DInc, I can't flash 2.5 again or it'll brick (can't flash the same radio twice in a row).
Would I be able to flash MR2, then MR2.5 again? Basically, wtf do I do, and why did this happen?
you flashed the wrong cm7...there are two versions...one for the mr1 radio and another for the mr2 radios
I didn't even flash CM7. I said I flashed the MR2.5 radio.
When this happened to me I made a backup of my ROM, flashed the file found here, http://forum.xda-developers.com/showthread.php?t=1082114, loaded my backup, and tried again with a different download of the MR2 radio. My theory on why the no baseband thing happened to me was a bad download... I've since started checking MD5 sums every time I flash anything through HBOOT which I should have been doing all along.
I'll try that. It shows me as no baseband, no phone number, no anything. Crap.
if you didn't flash a rom then its normal. You can't flash a 2.0+radio with an mr1 rom and have signal. Nothing is wrong just flash an mr2 rom.
Sent from my HTC ThunderBolt using XDA Premium App
Alright I'll try flashing CM7 then. I hope this works. This is a lot more involved than my Incredible, haha.
Edit: Yup, that's definitely it. I flashed my original MR1 ROM and radio and I'm fine.
Thanks guys!
If you have the MR1 rom, the MR2.5 radio will not work for it due to the new RIL.
And I have flashed radios twice in a row before and nothing has happened...but if you take my word for it it's on you
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
pspkicks316 said:
Yeah it was just something I heard when I was working with radios on my incredible. No clue how true it was, but it's not worth the risk.
I got everything sorted out, thanks guys!
Click to expand...
Click to collapse
Bricks like that don't happen on the thunderbolt if you flash the radio twice in a row, but I still wouldn't recommend it
Well here is the issue, I bought the HTC Thunderbolt awhile ago. I then rooted my phone but left the original ROM on it since the custom roms were not stable. I noticed verizon was pushing me some update and I just ignored them. I woke up today to see my phone rebooted with the screen on an exsclamation point. And then my Thunderbolt keeps rebooting itself now. I tried going into ROM Manager to download a Custom ROM but the phone just reboots before I can do it. I just installed Liquid Gingersense v1.6 rom with the MR2 OTA Radio which said it installed just fine after installing the Liquid Gingersense rom. I went through setting up the google account fine and after it booted to the main screen now my phone boots all over again, get stuck at htc screen for a bit then loads the phone fine then boots again. I am really not sure what the heck is going on. I am new to the MR2 OTA Radio since I cam from the Droid 1. So I hope it was not the install order I did it. I Have turned off the phone booted it with still same rebooting over and over issue. If anyone has idea's please let me know. Much appreciated. Thanks
I'm in the same boat. I have wiped the SD card and done a factory reset on the phone. It is no longer rooted, as I can't install and run apps requiring root permission. The update fails every time it tries to install, I also get the exclamation point android screen when the update tries to install. I'll take the update, I don't care. I just want a reliable phone again.
I'm seeing this issue come up a lot. Some of you folks seem pretty upset by it, and reasonably so. Search through the threads and you'll find you solution.
For those who are STILL running that antique and wildly obsolete ROM that the jcase rooting process leaves you with, I'd like to set a few facts before you. First of all, that ROM wasn't provided as a long-term daily driver. It's OLD and it's not very efficient with the battery. Second, simply because it's stock doesn't mean it's inherently stable. It's probably less stable than the custom ROMs out there. Third, the only ROMs really struggling with stability were the 2.01 RUU gingerbread builds. That build is obsolete, but not nearly as obsolete as the ROM that the rooting process leaves you with. The stability issues with the second OTA had nothing to do with the ROM, but rather, the radio that came with the RUU. In short, it's foolhardy to believe that custom ROMs are somehow inherently dangerous or unstable.
I'd like to suggest to whoever might be running the rooted ancient ROM the rooting process leaves you with to abandon it at your earliest convenience. Flash an MR2 radio, and if you like stock, use the stock rooted debloated ROM based on the 1.70 RUU. If you decide not to do this, and your phone auto-accepts the update, you'll probably lose everything on the phone trying to get it working again. Save yourself that hassle. Flashing ROMs isn't hard and people do it everyday.
I have two rezounds, just got the second one. I forgot to restore the stock recovery before doing the OTA, but it seems to have installed OK. However, when I go into Software Information screen, the PRI Version is older than the one on my first Rezound. Everything else is the same on both phones. Did the update fully install? Thanks!
Edit: Wifi isn't working...definitely think something may have went wrong.
Not all phones are on the same PRI. Mine did not change with the OTA, I'm still on an earlier version than some people. I've seen three different versions posted.
As to the wifi... try flashing the 2.x stock kernel from the OTA and see if that fixes it. You're still on stock ROM?
I wonder if different PRI could account for the variable battery drain people seem to be having?
Thanks guys. Wifi is working now and everything looks OK.
***Pre warning***
Turning your phone s-off gives you a chance of bricking your phone. I am not responsible if you try these steps and have problems. Also you will loose all your data as you will be wiping your phone multiple times. Make sure to backup all your data (I used Titanium backup) OK?! :good:
I had done a ton of research trying to fix the GPS on my HTC Jewel and never found a solution that worked. Issue was the GPS would not lock. I was originally running MeanRom, then JellyBam, and finally switched to CM10.1 nightly builds, all with no GPS. Last night though I finally fixed it and wanted to post this for anyone else having this problem.
Prior to last night here is how my phone was setup:
S-On
Hboot 1.19
Radio 1.12.11.0890
CM10.1 20130224
I saw that HTC released a new update, and started digging on how to update when on a custom ROM. I realized that I needed to go s-off which I had tried last year with LazyPanda, but it failed.
Last night I was able to go S-Off following directions from FacePalm: http://forum.xda-developers.com/showthread.php?t=2163013
It was a lot easier than DirtyRacoon and I'm running Win7x64 which DirtyRacoon says is not supported by them.
Once I was s-off I downloaded the latest Radio 1.12.11.1210 from: http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection
I confirmed that the radio upgraded successfully and rebooted. I was then prompted to activate my phone, and when I tried to activate it gave me the error that I was not authorized! With some help from the FacePalm IRC channel I was pointed to having to flash stock to be able to re-activate and then flash again back to your custom ROM.
I downloaded and flashed with Stock_Rooted_Deodexed_2.13.651.1 found here http://themikmik.com/showthread.php?14585-ROM-Kernel-2-13-651-1-Stock-Rooted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Booted and re-activated, and confirmed GPS working! Then I re-flashed with CM10.1 20130228 and GPS was still working!
I hope this helps others as I have seen a lot of forums with people complaining about the HTC Jewel GPS and saying it's faulty hardware, unfixable, or their fixes are all in app software related.
Thanks!
One thing that I would like to add is if you go stock, do NOT turn off your GPS after you get a lock. I usually have GPS turned off to save battery, but it was the reason why the new ROMs couldn't get a signal.
So to recap
1. Go back to stock
2. Get any old signal even for just a second
3. Immediately flash your new ROM without turning off GPS
4. Enjoy
This indeed works.
I don't like Sense-Based ROMs, so the first thing I did after getting my Jewel was S-Off, and I'm running AOKP. The GPS was driving me crazy, and I couldn't figure out how to get it working.
I updated my radio, flashed a sense-based ROM, locked GPS, then reverted back to AOKP, and it works flawlessly!
This method works!
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
The way I fixed the problem before was to flash back to sense, clear maps data and flash back to CM10.1. Voilà
I use waze
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
The only reason you have to go back to stock is to re-activate your phone.
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
pbedard said:
I use waze
Click to expand...
Click to collapse
So do I, but before I did this waze just searched for GPS signal.