So i'm trying to run the 3.16 update and everytime i download it it says the update is corrupt would you like to try again? Trying again and its the same results over and over. I'm on a stable wifi connection. I googled the issue and the only thing i could find was toggling the wifi setting of DLNA auto-IP as a fix but it didn't work for me. Anyone else have any trouble with updating or know of a fix?
Phone specs
S-ON
Relocked (previously stuck at 3.15 with bad radios from ruu issues, has since been solved)
Bro do yourself a favor and get S-OFF and you will NEVER have to take another OTA
i've done all that stuff before. I got sick of having a phone that only functions at 90% because gps is not working on this rom or lte isn't working on that rom. No offense to anyone here but i just don't think the process of loading custom roms is worth the risk especially when i only have one phone and essentially only use the wifi tether feature. i just want to know if theres any fix to obtain this update.
Related
German o2 Flyer - routed + S-OFF
I went back to stock
RUU_Flyer_O2_DE_1.40.207.5_Radio_20.35.30.089BU_38 09.04.04.21_M_release
But the OTA 2.27.207.1 (Android 2.3.4) never appeared. (I only used WIFI cause i wont be able to use gsm/3g connection the next days)
Waited a wole day + rebooted...
manually trying to update its telling me, I have the latest version.
What am I doing wrong? (Or isnt it working over WIFI only - will get GSM/3G monday again)
Or could somebody please upload the OTA File?
Or maybe the complete new ROM
I need this, cause I want to check if some FCs are rom related or App problems
Any suggestions?
Or can somebody upload the latest OTA
Or maybe even the whole new RUU
Thank you
wait i guess. HTC doesn't want anything to do with the Flyer, so they're holding off on updates..
I wiped... reinstalled...
only the H-Boot ond S-OFF are left.
still Not getting an ota update
I have the same problem; I went back to stock, s-off and I have got OTA update notification, I downloaded, installed, reboot and stuck in recovery.... it seems to be unable to update once you s-off the device.....sad but true !
ovigt71 said:
I have the same problem; I went back to stock, s-off and I have got OTA update notification, I downloaded, installed, reboot and stuck in recovery.... it seems to be unable to update once you s-off the device.....sad but true !
Click to expand...
Click to collapse
wait a minute... i dont even get to the Part with the download notification.
Have read about the problems, but seems most of the guys managed to get it working after several reboots... so I'm gonna risk it,too.
have you been connected to WiFi or 3g?
I have only WIFI. my SIM card is expired, so I'm not gonna renew for a while !
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.
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
benny6812 said:
Hi,
I have a major issue with my WiFi and reboots.
Background: I am using an ATT phone within the UK on T-Mobile network.
Randomely, the other day, the WiFi turned off and when I turned it back on, it says Error....
I have tried everything I can think of; wiping and reinstalling rom, erasing everything in fastboot, updating the radio (further question on that) and also kernels! Finally I tried FruitCake to get back to stock, still no luck!!
Radio: Are radio's carrier specific, i.e. could I flash a radio meant for Europe to replace the ATT one? (I am on .36)
What can I do now, please. Thanks
Click to expand...
Click to collapse
If it helps, i accidentally formatted the PDS partition a while back and the reason for reboot is AP KERNEL PANIC
Any help would be greatly appreciated.
I am having similar problems. Just last night my phone started rebooting frequently after having turl's v8 build of cm9 for probably a week and it was working great. However, now I have tried wiping everything, putting on different cm7 or cm9 builds and what I have come to the conclusion is anytime I turn the WiFi on, it reboots.
It is not even connecting to anything, just turning it on makes it reboot. I was on the .36 radio with this issue, I tried using the .37P radio and it did not fix it.
Does anyone have any other ideas to try and fix?
Benny,
Do you get the option to turn it on? I'm on cm9 and it'll show up like the attached after it reboots.
No. I dont have that screen. It just says wifi error and Bluetooth crashes as well....
Sent from my MB860 using XDA App
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
bassmarkie said:
From the other threads I have read, I think we are boned. It seems like the Broadcom WiFi/Bluetooth chipset is borked and the only fix other people have gotten is through an actual repair. I hope you are under warranty - I'm going to revert to stock and hope they accept it.
Click to expand...
Click to collapse
But, how come whenever I flash a new rom, the WiFi will work temporarily, i.e. it would connect, obtain IP etc for a few minutes then just not work until I reflash?
Surely that is not hardware?
Bump
Sent from my MB860 using XDA App
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Drakonas said:
Did you use Titanium Backup, and restore apps like Maps, Music, and YouTube? People are saying this can cause issues.
Also did you restore call logs after flashing? I experienced my wifi and mobile networking dying after doing that on only some of the new roms out there lately. It's a bug with one of the base roms, that a lot of custom roms are based off of. It was fixed with a new base rom version, but some of the custom roms have yet to officially update. Updates are under way though. Try out Morrison's 0.7 and see if you get the same result. It's been updated.
Although, you could be having a completely different issue. If you mean you can just leave it running after flashing and the wifi dies, I don't know what to say.
Click to expand...
Click to collapse
Tried all of the above and still nothing unfortunately. Just want to update on symptoms of the phone if that helps:
Everything eventually gets more and more buggy, even recovery is really laggy and slow
Data will stop after a few days use, and only fix that i know of is to reflash
WiFi does not work, it connects for about 30 seconds after a reflash, but then nothing.
Logcat says - Failed to Load WiFi Driver (after reporting WiFi HUNG)
The phone can crash when I plug in the MicroUSB to charge, when it restarts it says AP KERNEL PANIC.
I have tried everything except for flashing via RSD lite, do you think that could work?
Thanks
BUMP,
Any help at all with this unique situation would be very helpful.
Thanks
***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.
So ive run out of ideas on this problem. I no longer can update my prl and profile. I was on freeza's not3 2.2/2.25b rom had some issues with slow data and other hiccups. Flashed stock debloated and got tired of its blandness so i moved back to freeza's hoping for a better experience now that it had some time. After flashing back to it ive run into these issues.
Poor network signal, unable to update prl or profile with error code 6602. Ive gone stock tar nh7 and reflashed the modem too with no solution. Ive regained network connection after losing it entirely for a bit but still cant update prl or profile. Everybody else is talking how theirs is working great....i havent done anything different. Hope to get some input. Thx ahead of time.
Reminder at this point everything is stock flashed on odin. Twrp recovery latest version. Odin 3.09
Jataadroid said:
So ive run out of ideas on this problem. I no longer can update my prl and profile...
Click to expand...
Click to collapse
I had similar PRL/Profile problems, 'tho I was getting error code 6500. Network connections remained strong and through-speeds were very good. But the failure to update Prl/Profile really pissed me off. I also tried return to stock, other ROMs, but same error 6500. I just lived with it and did the occasional battery pull to good effect.
Then I installed Sacs_Note4 _Ported_apps_Rom_V2.
As part of the installation instructions, I updated PRL & Profile and was shocked when they worked!
Then I set up the phone as I like it, and back to error code 6500.
I turned-off the various Wanam mods and presto, no 6500 error code.
I then added them one at a time, (stuck with a few less this time) and still no error code 6500.
Good luck!