I everyone, i have a problem with GPS. Now i am on CM12, baseband 1.15, but i tried also Liquidsmooth and CM11, with baseband 1.20. With every ROM the same problem: GPS finds me, but it freezes me in the position; and Google Nav (or Waze) finds the itinerary but then it doens't move the cursor.
How can i resolve? Reflashing the 2.16 firmware?
Thanks in advance.
No one?
Kin93 said:
No one?
Click to expand...
Click to collapse
Are you using the latest version of TWRP? One person here had issues with GPS, and solved reflashing the rom after updating the recovery. I had issues with GPS which were gone once I moved to CM11. I have 1.15 baseband and hboot 2.15.
Fiabeschi said:
Are you using the latest version of TWRP? One person here had issues with GPS, and solved reflashing the rom after updating the recovery. I had issues with GPS which were gone once I moved to CM11. I have 1.15 baseband and hboot 2.15.
Click to expand...
Click to collapse
Yes, 2.8.1.1.
Maybe i would try to downgrade hboot and see if something will change.
Related
I just updated my rom from vipers1.0.1 to version 1.1.0 and i lost my wifi functions, i reinstalled the rom with a full wipe and still no luck? what do i do
ThizizKenny said:
I just updated my rom from vipers1.0.1 to version 1.1.0 and i lost my wifi functions, i reinstalled the rom with a full wipe and still no luck? what do i do
Click to expand...
Click to collapse
Same issue was there for me in ARHD ROM. Got fixed after upgrading to 3.33 firmware and changing the kernel to faux 008b8 (latest is 008b9)
Try turning off fast boot first. Then flash another kernel. And please report back as you are not the only one.
if SON ..enable smartflash in 4EXT just before flashing the ROM/kernel (SON causes wifi issues too)
ganeshp said:
if SON ..enable smartflash in 4EXT just before flashing the ROM/kernel (SON causes wifi issues too)
Click to expand...
Click to collapse
THANK YOU SO MUCH! YOURE A GOD lol.... This worked perfectly first time, i love you<3
Is it possible to update the baseband only without reflashing the entire ROM. Can I update to a newer baseband without using an RUU package?
Thanks,
K
lasteveruser said:
Is it possible to update the baseband only without reflashing the entire ROM. Can I update to a newer baseband without using an RUU package?
Click to expand...
Click to collapse
Absolutely. Just flash a radio image. Most ROMs (other than RUUs and possibly stock ROMs), in fact, do not come with a radio image so your radio image will persist between ROM flashes.
See this thread: "[Radio][RIL]Flashable Radios with RIL files, Map, and AROMA Installer (Updated 8/13)" http://forum.xda-developers.com/showthread.php?t=1694012
Thanks
denversc said:
Absolutely. Just flash a radio image. Most ROMs (other than RUUs and possibly stock ROMs), in fact, do not come with a radio image so your radio image will persist between ROM flashes.
See this thread: "[Radio][RIL]Flashable Radios with RIL files, Map, and AROMA Installer (Updated 8/13)" http://forum.xda-developers.com/showthread.php?t=1694012
Click to expand...
Click to collapse
It worked perfectly. I was able to update to the 2.20 att baseband on CM 10
Thanks,
K
I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
digitalmonkey said:
I tried out the NOX sense 5 rom and then reverted back to stock , but my wifi doesn't work at all. During the first NOX release I upgraded the radio image and I'm guessing I need to downgrade it back to the stock x920d radio to get wifi working again.
I don't suppose anyone has the stock radio image for the x920d?
Cheers in advance.
Click to expand...
Click to collapse
I have the same problem just now. It's because we need the stock boot.img file before we can return to stock. The problem I encountered was I restored my original ROM from TWRP backup. I tried flashing the stock boot that another user gave but it doesn't work, then I remember the KillX kernel which comes with its own boot.img file and Flashed that. Now my wifi is work but the kernel is no longer stock.
Hey,
right now I'm on CM 10.1 (2013 03 12 nightly) and I want to update to the latest CM 10.2 nightly.
However after flashing the nightly I get a bootloop. I found out that CM started using a new kernel which I have to update first. And in order to do so, I need to update the firmware as well. http://forum.xda-developers.com/showthread.php?t=2322755
It says that the new firmware is 2.15.0000. But when I enter the bootloader it displays that I am already on 2.15.0000:
http://abload.de/img/img_68993jl4l.jpg
Note: I haven't updated the firmware or anything yet. But it appears that I'm already on the new firmware, right?
But then: why am I getting bootloops when flashing the new nightles? Do I have to flash the new kernel manually in fastboot? Or does TWRP does it all by itself? Do you think I can try flashing the kernel because HBOOT is 2.15.0000 or do I have to do the tutorial?
Sorry, I'm kind of new to this whole flashing thing, so pleas be patient with me..
Oh btw: the model is ville
Thank you guys.
//Oh I just remember that I did the htc sense jb update when it came out _before_ flashing CM. And that jb update should include the new firmware right? So I can just proceed with flashing the new kernel in fastboot?
Your hboot is fine for the ROM. You're S-On so you need to flash boot.img after flashing the ROM. That's your problem.
Sent from my One S using xda app-developers app
abracadabra11 said:
Your hboot is fine for the ROM. You're S-On so you need to flash boot.img after flashing the ROM. That's your problem.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Okay, I just did that and it seems to work.
There were some problems with the CM account and a lot of crashes but after that it seems to work just fine.
Thank you
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
I'm having exactly the same issue with my one s, when it bootloops the only way to recover it is to boot into recovery, power off & reboot. Tried multiple CM/AOKP roms with the same issue.
As far as i know i'm on the latest firmware (how do you check in CM or is it baseband?) as it was RUU'd to 3.16.xxx then s-off'd, i'm not superCID currently as I had to change it back to HTC__001 to run the RUU. Hboot: 2.15, baseband: 1.11.50.05.28_10.27.50.08L
Its a European (UK) phone with the S4 if that makes any difference
Annoyingly I cant seem to get it to do it when I have a PC with ADB set up on it nearby!
Is there any more info that might be helpful that can be provided?
I also experienced the same thing. Hope senior member help us. :crying:
MadMan29729 said:
everytime i flash an android 4.3 based rom my phone will bootloop... install it works for a few.. then crashes then back into bootloop then works... reboot.. bootloop...
doesn't happen when i installed the cm 10.1.3
any ideas?
Click to expand...
Click to collapse
aosp 4.3.x need a hboot >= 2.15.x
have the ville with hboot 2.15, S-OFF, SuperCID, latest firmware (afaik)
Sent from my One S using Tapatalk
Which version of HTC one S? The Villec2 or Ville?
Kerjifire said:
Which version of HTC one S? The Villec2 or Ville?
Click to expand...
Click to collapse
the ville
I am having the same problem with my s4 ville hboot 2.15, S-ON, latest frimware
Any solution guys?
I spend the whole day running RUU's, re-locking, unlocking the phone, flashing different 4.3 AOSP ROMs but every time I boot the same thing happens: Sometimes I can't even get the rom to boot, but if it does, it usually crashes back to the splash screen after a couple of seconds. I am out of ideas. Any help?
I flashed the JB firmware as per the firmware thread and it has mad my current rom (beanstalk, couple of builds ago) slightly more stable, however flashing anything else results in a bootloop.
Incidentally as well, starting maps navigating, hitting home, then going back into maps again results in bootlooping
Edit
Attached a logcat of the phone bootlooping caused by the maps issue above, did have one of it happening in maps but I fat fingered my cmd prompt and overwrote it. I'll grab another once its recovered
Reading through it it doesn't seem to have captured the actual bootloop, i used 'adb logcat < file.txt' to record it, or is there a better method of capture, using the -f flag as per the dev website gave me a read only error either 'adb logcat -f file.txt' from a path i have write access to or 'adb logcat - f <filepath>file.txt' can I get adb to continue writing between device reboots?
Just flashed the awesome kernel cleaner script and then flashed bubba kernel so far it seems to be working, will report whether it worked or not after i test it more...
UPDATE: crashed into a bootloop