My brother has this rom on his phone, he was running 2014-04-01 build, but Maps didn't work for him so I told him to update to latest nightly, which was 2014-25-01. Now his WiFi doesn't work. He cleared the cache, dalvik cache, but WiFi still doesn't work. Is there any way to fix this without clearing data? it's not S-Off so i guess the new kernel didn't install.. He's hboot 2.15
WIPE everything, then fastboot flash boot boot.img after that chose the apropiate zip in recovery to install it. No issues are officially for dirty installs
Thanks, it show only the following lines between plugging in and rebooting:
D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb8f83188 identifier _disdev value Speaker D/alsa_ucm( 255): disdev: device Speaker not enabled, no need to disable D/alsa_ucm( 255): snd_use_case_set(): uc_mgr 0xb8f83188 identifier _enadev value USB PROXY Rx E/alsa_ucm( 255): No valid device USB PROXY Rx found
He is S-ON. As stated previously, download Flash Image GUI from the Apps forum (or buy in Play Store to support great app). Use it to flash the boot.img which you are not flashing properly now.
He can try flashing boot.img using flash image GUI, that worked fine for me when I was still s-on.
Sent from my HTC One S using xda app-developers app
Download bubba kernel and flash as you did the ROM in recovery
Will bubba kernel flash in recovery still work even though it's s-on? I thought you needed a computer for that.
Also, has anyone tried using flash image GUI while s-on? I'd rather know for sure instead of jeopardizing losing his phone for 2 weeks..
That's not the place but... I have S-ON too, it has to be off? I install any release with twrp recovery and sometimes i get status 7, and with the roms that install fine, it wont boot..
I have GPS related reboots while play Ingress... :/
No, if S-ON, you just have to manually flash the boot.img (for those who are S-OFF, it is done automatically)
If you have boot or wifi issue, that would most likely fix it.
Not sure I said that exactly, but I think that support for our device is definitely a low priority since our maintainer was hired by CM and likely spends most of his time on tasks that bring in revenue. As it stands now, it doesn't seem we will ever get a stable release, so will be stuck here in xda purgatory complaining back and forth about the same things until we can afford to get a pure AOSP device and give up the crack flashing life.