Develop Bugs

[Q] MIUI causing desire to reboot?

I would like to know if anyone else has experienced similar issues using any of the MIUI roms?
If you have experienced this how did you remedy the situation?
So here is the story:
I was never keen on using MIUI roms as i am a fan of sense, but lately i have been growing tired of sense and have been looking for greener pastures.
My device is rooted(S-On, pvt-3, 0.93 hboot) and i have been running plenty of custom(sense based) roms with no trouble. Last night i flashed Pays MIUI rom and the phone was rebooting evey few minutes ... so i decided to call it a night and went to bed ... then this morning i went to the MIUI site and downloaded the latest 0.12.24(or something) and the phone was running smoothly the whole day without any hicups ... or reboots ... yes you guessed it ... now its rebooting again!
I dont think its the hardware on my device as i havnt experienced any problems with any other roms, and i perform a full wipe each time i flash.
Any advice would be greatly appretiated, thanx in advance!

Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.

Lennyz1988 said:
Try flashing this kernel:
http://forum.xda-developers.com/attachment.php?attachmentid=472705&d=1293232742
it could be that the HAVS kernel is causing your problems. This is a SVS kernel and should be more stable for some people.
Wipe dalvik cache after you flashed the kernel (same way as flashing rom). Disable verfication before flashing.
Click to expand...
Click to collapse
Thank you for the reply ... i also thought it might have something to do with the kernal, will flash after the phone has charged ... will post results!

[Q] Problem: WiFi Error

Hi everyone,
After flashing a new ROM (MildWild 3.2) and using it without problems for a few days i got a problem with my WiFi.
When I try to Activate the Wifi I got the word Error, instead of activate or something else! And when i go to the wifi settings can't select any networks... It seems that the wifi cannot work at all...
After that i did a wipe Dalvik Cache, erase data and cache partitions, wipe the battery stats, and flashed a new Rom (MildWild 3.3).
But it didn't solve the Wifi Error problem.
Does anyone knows how to make it work??
I have a desire with:
Android version - 2.3.7
Radio - 32.56.00.32U_5.17.05.08
Kernel - 2.6.35.14_r3-stable [email protected] #1
ROM - MildWild V-3.3
Thanks!

Just to cheer you up: I had the same problem once. (I cannot remember how I solved it though).
There are some results that it might be strangely related to the sd cards. Maybe give it a try.
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
Just to add that: I can't remember needing to use a RUU, but I guess it would be a possibility.

abisconsin said:
After that i did a wipe Dalvik Cache, erase data and cache partitions, wipe the battery stats, and flashed a new Rom (MildWild 3.3).
Click to expand...
Click to collapse
Did you every tried a Full System Wipe? From your description, you never wiped the system partition. I bet a fresh flash of the rom would fix it. Also, have you installed any new app that involves changes/controlling your wifi connection? You can try and replace the wifi supplicant file on your phone with the one inside the attached Mildwild Rom.

It's back!
Well guys,
After two weeks without wi-fi (Wifi Error), I just lost my hope.
And yesterday I tried to turn it on, and it worked!!
So... I tried everything, full wipe, changing ROM, changing Sd Card, and nothing really worked. Only after two or three weeks without caring about, it just came back!
Really weird.
So, if you have the same problem (Wi-fi Error) keep your hopes and have some patience, when your phone wants to come back it will.

You probably switched the kernel in between. The problem is due to incompatible/missing kernel module. If you flashed a kernel, it got solved.

[Q] CM11 snapshot/nightly stuck at boot... now can not even rollback to 10.2

Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )

nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot

Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version

nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31

Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either

i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!

nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?

I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks

[Q] Battery drainage because of mobile data

Hi Guys,
I am new to this forum and got a small question. My girlfriend has an Oppo Find 7a. You guys probably know that the stock ROM is ColorOS. In my opinion it's crappy as hell, lots of bugs and issues, so I decided to flash Dirty Unicorns 5.02 on it. I did that yesterday and all is working fine so far, except that the battery drained from 100% to 64% last night (in 8 hours). See the photos attached. According to the photos it seems clear that the issue is the mobile data usage. I've checked the settings and it seems mobile data loses connection, connects again and loses connection everytime. Probably this is the cause of the battery drainage. Somewhere on this forum I read something about flashing Alucard 1.1a kernel on it to fix this issue. I want to try this in the evening, but does anyone know the correct type of this kernel as I found different alucard 1.1a download links?

Can someone please help me out with this? Yesterday evening I just flashed the Alucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?

GRDD_ said:
Can someone please help me out with this? Yesterday evening I just flashed the Elucard 1.1a kernel via the custom recovery. I also removed dalvik/cache and rebooted after that. The Oppo boot logo appeared, but it stayed like this for 20 minutes. I'm not sure if I have to wait any longer to make it work or if the phone is just not booting up anymore with this kernel. Any advice?
Click to expand...
Click to collapse
before flashing DU did you flash proper modem and trustzone firmware?

treacherous_hawk said:
before flashing DU did you flash proper modem and trustzone firmware?
Click to expand...
Click to collapse
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?

GRDD_ said:
Nope, actually I didn't. I wasn't aware of the fact that this was necessary. I had ColorOS 2.0.0i on it and flashed DU directly on it.
Can you maybe tell me what the proper modem and trustzone firmware is? And can these still be installed now even if DU is already flashed on it?
Click to expand...
Click to collapse
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
https://plus.google.com/+BoskoTrkulja/posts/CENAM1a7Zob
you can get the modem and tz firmware here:
https://www.androidfilehost.com/?fid=95916177934529695

Sir, have my thanks! You are my hero of today. Thanks a bunch. I'm going to try this

treacherous_hawk said:
well you can do a clean flash again but this time you have to follow this for how and why to flash modem and TZ firmware:
you can get the modem and tz firmware here:
Click to expand...
Click to collapse
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?

GRDD_ said:
So, one more thing If I may ask. What is the best thing to do from here on:
1. Flash modem, flash firmware, flash DU (directly over the DU rom that is installed now without doing a factory reset / wipe)
2. Flash modem, flash firmware, perform a factory reset / full wipe and then flash DU.
And will the newly flashed modem and firmware stay on the phone when i do a full wipe?
Click to expand...
Click to collapse
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
Alright, I will do it in that order then. Thanks again. Much appreciated.

treacherous_hawk said:
do a clean wipe, then flash modem, then firmware (in bootloader) and then rom along with gapps.
Click to expand...
Click to collapse
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?

GRDD_ said:
It's been a few weeks, but I finally had the time to do this. I've done a full wipe in TWRP and then flashed the modem on it. This showed succesful. It took about 10 minutes before the phone booted up afterwards. After that all seemed fine, so i've put the phone in bootloader via a command in cmd and installed the firmware. This also went succesful, but now I still have the same issues on the Oppo regarding the provider issue as mentioned earlier. The data connection is still being lost very often and it still seems to be draining battery (although less than before). Is there something else I can do to fix this ?
Click to expand...
Click to collapse
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.

treacherous_hawk said:
If you have recently done a clean install, give it some time to settle down. For Data connection issue, make sure to check your APN and also try a different sim or this sim in some other phone, could be signal reception issue.
Click to expand...
Click to collapse
I will give the battery thing some time to settle down then. About the data connection issue; This was not an issue on coloros, but I will check apn and try another sim. Thanks again!

I've changed the APN settings, as they stood on some kind of roaming setting. It's now been set to live.vodafone and seems to be functioning better already . If I still run into some issues I'll let it know. Thanks for helping me out

GPS is not working after flashing Lineage 14.1

GPS is not working after flashing Lineage 14.1
I tried (GPS Status) but still says "Looking for GPS location..." and nothing happened.
Also, I wiped cache and dalvik many times.
Device : HTC One M8

Now, I tried "Venom Roms" and the same issue nothing fixed!
Is some file missing when I rooted or Rom?
Any help will be appreciated..

GPS is working now
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860

mhb3000 said:
I fix it :good:
1* Flashing stock RUU.zip . (reLock bootloder, Flash RUU,....etc).
2* Unlocking again, Installing last updated TWRP ,and then I backup the RUU ROM.
3* Flashing Lineage 14.1 and installing updated SuperSU.
4* GPS is working now..
Thanks for:
https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Good to read here to take some steps:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?

Gara91 said:
Can you explain a little more precisely why do we have to do that to get the gps work again... I am now on the latest lineage and can't get the GPS lock. Is there any way to do that without the RUU flashing thing..?
Click to expand...
Click to collapse
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.

GeoFisher said:
I too would like a little more detail on the GPS issue.
I cannot get a GPS lock either. I've tried a whole lot of a whole lot , and nothing seems to work. My phone is a HTC One M8 / verizon model. I know verizon has some flakey stuff going on, and that may be my issue.
Lots of posts talk about editing the /etc/gps.conf configuration. On verizon phones, that looks to be a symbolic link to another file..Maybe not, my linux kind of SUCKS, but it is weird.
At any rate, when I edit the /etc/gps.conf and uncomment the first 3 lines as stated, my phone goes into a boot cycle, and I have to restore from a backup.
Any help would be greatly appreciated........
Details:
HTC One M8
verizon
7.1.1
crDroidAndroid-7.1.1-20170328-m8-v2.5
Build NOF27B
Again, any help would be greatly appreciated.
Click to expand...
Click to collapse
I do have a gps lock now on the lineage os...i just followed the steps from guy above... My mistake was when i install a lineage os i allways do the bootloder unlock, then immediately i flash twrp and than a full phone wipe (system, data, cache, internal memory). This time i relocked the bootloader, installed the ruu, then unlocked the bootloder again, after that i let the stock system to fully boot... I go through the first set up and after all that i flashed the twrp, and installed the lineage os but this time without a system wipe, just data, cache and internal memory (internal memory is not a must, but i love when i install a new rom to get totally fresh and clean install).
I don't have a clue why this works but it worked for me and maybe it can work for you...
My HTC M8 is European model but it doesn't matter, because if you do all this step with the stock ruu (Verizon ruu in your case) the files for the gps will be there... Good luck..
Edit: I am using the Navigon Europe and my gps locks instantly like on the stock android 6.0.

Hello, I've got an almost the same issue with GPS, it seems, the "assisted" function isn't work correctly. When I switch on the GPS, I have to wait 3-5 minutes to start working. After a few minutes there is no any issue with that, but a little bit annoying if I want to navigate from an unknown place and I have to drive "blind" for 5 minutes. I use the latest nightly build on my M8. I've started use the previous unofficial build, but currently I always upgrade to the latest nightly. Any idea?
Thanks in advance!

This fixed the GPS for me.
I'm was on LOS nightly 14.1-20170413 when i removed # in gps.conf. (use total commander app)
When phone start bootloop, i use the right quickpulldown to GPS and only 1 touch to disable. In current nightly, it's 2 touchs to disable GPS so have to be even faster before the bootloop or otherwise tap the airplane mode instead to stop bootloop. Also make sure you have screen lock = off or swipe.
now restore # in gps.conf and GPS is working.
/system/blobs/
This might help.
https://www.reddit.com/r/LineageOS/comments/5z8zju/gps_not_great_on_htc_m8/

Hi,
I recently went into the same issue with GPS on my m8. It was not working at all. I spent couple of days trying to flash different stock roms, RUU, factory reset, editting gps.conf file, even the solution described here: https://forum.xda-developers.com/htc-one-m8/general/gps-harware-fix-teardown-t3023999. Nothing helped. No matter what I did, I couldn't get GPS working. I mean there was no signal at all.
Finally I wiped MISC partition and it solved the issue. It turned out that some wrong data was held on misc partition that stopped GPS from functioning correctly. One important notice - I was on stock firmware when I wiped MISC partition. Stock firmware managed to reinitialize it properly. If you are on custom FW, I am not sure it will work. You can try and if it will not work, it mean you should be on stock FW.
And just few commands for those who don't know how to do it:
With fastboot:
Code:
fastboot erase misc
If the above gives you "not allowed" error you can do it through adb:
Code:
su -
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Obviously you should be rooted or you can do the same through TWRP shell.
Hope it will help someone.