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
Related
Solved! ODIN'd back to stock and LTE kicked in immediately. Back to flashing =) Thanks guys!
Original Post:
============================================================================
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
hednik said:
Running galaxymod right now and in DFW area with great LTE coverage and never had the issues you had or any for that matter. Somehow in the flashing, I'm going to get real technical here right now , something got borked that isn't affected by flashing a new ROM. We could give to several things to try but honestly flashing back to factory out of the box and starting from there is the only fail safe way to do it. probably faster too. That's I would do
Click to expand...
Click to collapse
Thanks for the reply. I just downloaded root-injected stock and am flashing as we speak. If this doesn't work, I'm going to flash back to bone-stock and see how that goes. I'll report back and let everyone know =)
RPelham said:
Hello everyone,
I need some immediate help please. I flashed GalaxyMod TouchWiz ROM (coming from Vanilla RootBox). I flashed because I was looking for a more stable ROM and started having the following issue:
After the flash I only get 3G for roughly 5-10 minutes. After about 5-10 minutes LTE finally activates. This persists through ROM flashes. This happens after every reboot and after toggling airplane mode.
I have since flashed Task650's AOKP and CM10.1 and the above issue is still present. I have checked my APN settings, which are on PTA. I also checked my preferred network and this is where I noticed an oddity. It is stuck on WCDMA preferred for the first 5-10 minutes and then finally changes by itself to LTE / GSM/WCDMA.
Steps I've taken so far:
1.) Flashed the LTE fix (while still on GalaxyMod ROM) which was provided in the GalaxyMod thread. This made no affect on the issue at all.
2.) Flashed new modems, no affect at all.
3.) Wiped Cache, Dalvik Cache, Factory Reset, System, Internal Memory and Data, reflashed a new ROM, no affect.
I never had any delay in connecting to LTE prior to flashing GalaxyMod, and now I get it on every ROM I flash thereafter.
What can be causing this? I am thinking the only thing I can do is Triangle Away, ODIN back to Stock and send it to Samsung.
If you have any suggestions at all, please let me know. I am desperate to get this working.
At the time of this post I'm running TWRP 2.4.1.0, CM10.1 and the packaged CM Kernel that comes with the ROM.
Click to expand...
Click to collapse
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
peaster3 said:
Did you check to see if your IMEI is missing?
I had the same issue on GalaxyMod. I had to do a clean install of the ROM, apply KT's kernel, and apply the LTE fix BEFORE I rebooted. I could not tell from your post if you did a clean install of GalaxyMod. Then I checked my IMEI and it was missing, so I performed the fix found here http://forum.xda-developers.com/showthread.php?t=1801997 and repeated the steps above. Worked for me as I get LTE speeds now on GalaxyMod.
Click to expand...
Click to collapse
I'm getting LTE speeds, problem is after toggling airplane mode or rebooting the phone it takes up to 10 minutes for LTE to activate. I fresh installed GalaxyMod, wiped everything possible in the wipe menu of TWRP with the exception of external SD.
I also applied the LTE fix before I booted GalaxyMod, but I did not flash KT747. I prefer to not flash that kernel because it has the updated BT/WIFI drivers and had a warning that I would need to back those drivers up if I ever wished to revert. I don't really feel like going through all of that lol.
Solved. ODIN'd back to stock =) Thanks hednik!
RPelham said:
Solved. ODIN'd back to stock =) Thanks hednik!
Click to expand...
Click to collapse
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
hednik said:
Glad it worked.... these phones are almost fool proof as you can start with a clean slate if all else fails. Glad it worked
IMEI was still intact ?
Click to expand...
Click to collapse
Yupp I haven't yet lost my IMEI since I got the phone back in July. Guess I'm lucky so far, see posts all the time where people lose it, and I'm a flashaholic lol.
Sent from my SGH-I747 using xda app-developers app
So, yesterday I unlocked my OnePlus 3, rooted it and flashed a custom recovery. So I managed to install MIUI 8, and fingerprint scanner didn't work, so I flashed 3.2.4 firmware. Then I realised that I couldn't get my native language and I installed CM14, but before I flashed 3.2.6 firmware. As far as Nougat is still not ready for my daily usage, I restored OOS 3.2.6 from my entire backup.
I couldn't unlock the device. The pattern was not recognised as correct, even if it was. So I flashed cleaned data, cache and dalvik, and from here my problems started. I had no IMEI, no baseband, no wifi, my phone constantly randomly rebooted, so I tried to flash EFS twrp restore. Nothing. I tried with 3.2.6 firmware. Nothing. I decided to return "original". I copied JUST the EFS and Boot backup from TWRP folder to my pc, locked bootloader, flashed original recovery and OOS 3.2.7. Still the same problems, plus at the beginning I couldn't even complete my first setup. My actual condition is:
OnePlus 3 A3003, locked bootloader, unrooted, stock recovery, oem unlocked, debug enabled, efs partion (at this point I think so) messed up, efs backup doesn't work. Any help would be appreciated. Thanks in advance
EDIT: As the user @_ekis_ suggested me via private message, I flashed OOS, performed a "Fastboot erase modemst1;
Fastboot erase modemst2", and I got back IMEI, baseband (most important thing for me) and SIM. And no more random reboots. But there is still a problem: the wifi. It seems it disabled. Whenever I activate it, I cannot see any wifi, I cannot refresh the WIFI list etc. I already backed up my EFS, and I will perform a new OOS installation via fastboot. I hope for the best
EDIT 2: And yes, it worked! Now everything is back. A real thank you to @_ekis_ for his support and all the OnePlus 3 Telegram group.
Try flashing a modem package and it might help the imei. Theres a thread on the modems around here somewhere.
NZnewbie said:
Try flashing a modem package and it might help the imei. Theres a thread on the modems around here somewhere.
Click to expand...
Click to collapse
I don't mind about IMEI. The only thing I want back is just the baseband. I'm trying to flash OOS 3.2.6 now.
If it will not work, I will perform a modemmst erase
LuckyNuke1310 said:
EDIT 2: And yes, it worked! Now everything is back. A real thank you to @_ekis_ for his support and all the OnePlus 3 Telegram group.
Click to expand...
Click to collapse
Heya! Got the same problem couple days ago, would you be so kind and share how you managed to get your WIFI working again? It will save a tonn of my nerves.
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
What model?(network)
aclays said:
So I followed the instructions here: http://galaxynote4root.com/galaxy-note-4-root/how-to-root-unlock-bootloader-on-galaxy-note-4/
Everything was great at first, but it slowly degraded. At first it was only occasional hangs, then it got worse and worse. I reinstalled with the retail cpa1 5.1.1 install, which removed root, and again everything was fine for a bit, then it got worse again. I'm on call for work and away from my computer for the day so I let it take the 6.0.1 OTA hoping it would fix the freezing problems, but nothing has changed.
What can I do differently to fix these freezing problems? I completely redid the instructions on that website hoping it would fix the issues, but the same thing happened again. Amazingly fast at first, then slowly degrading into frequent hanging or freezing. Thanks!
Click to expand...
Click to collapse
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
ziggy71 said:
What model?(network)
Click to expand...
Click to collapse
Verizon SM-N910V retail
weard1212 said:
go install a custom rom like jasmineROM or EmotionOS, straight up stock can sometimes be unstable when you are rooted.
Click to expand...
Click to collapse
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
aclays said:
Verizon SM-N910V retail
I can't even get it stable on full stock. I Odin'd in the Full Firmware for CPF3 in this thread: [Firmware] [Official] Firmware / Kernel / Modem / Recovery [N910VVRU2CPF3] by hsbadr which overwrote TWRP and seemingly removed all traces of rooting, yet the instability is still there.
It occasionally is giving me the error "System process stopped", occasionally is rebooting entirely, there have been a few times where it wouldn't boot up at all. I had to pull the battery and leave it out for 5-10 minutes to get it to boot. I'm running out of ideas on what to flash over to fix it. Is it possible that the Kernel I installed while rooted is causing problems? The full firmware for CPF3 should have overwritten it, correct?
Click to expand...
Click to collapse
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
ziggy71 said:
I've had some issues myself. I originally used paul pizz PJ2, which is an awesome rom. Gives you stability of stock, but feel of custom. I then went to PL1 and EmotionOS. After a few days, I noticed, reduced connectivity, camera wouldn't focus, and button reassignments. So, I just wiped cache and Dalvik, stuck in boot loop. I downloaded the newest EmotionOS. Wiped everything, installed it. boot loop. So I did a another wipe and installed the deodexed Ricks ROM V2. So far so good, but it has only been a day. If you do a full retail firmware flash, that should fix your issues. If you did a full firmware, then yes, it would be overwritten. Try going back to 5.1.1 PA1 full firmware flash. Then you could allow the phone to take the OTA if you wish. But, that should fix the issue. If not let me know. And I will keep you informed of the new rom. Also, if you have a card reader, check your sd. Take anything that you want off of it, and wipe it as well. These Notes are finicky.
Click to expand...
Click to collapse
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
aclays said:
So I did actually go back to stock 5.1.1 and successfully take the 6.0.1 OTA, the issue didn't resolve. At that point I flashed the full stock CPF3, still no changes.
A new thing has popped up too. When I try to boot into recovery it says it's installing an update, then after about 5 minutes it goes to a black screen and nothing happens. I end up having to pull the battery to restart it. Discovered that when I tried to go clear all the caches and such before flashing CPF3, and it is still doing the same thing after flashing CPF3. I thought that by flashing the full firmware for CPF3 it would solve that.
Click to expand...
Click to collapse
So you are full stock? Does the update issue happen on the stock recovery?
ziggy71 said:
So you are full stock? Does the update issue happen on the stock recovery?
Click to expand...
Click to collapse
Yep it did. So I think I've actually fixed it now. I thought that flashing the full firmware would also flash the boot loader and modem, but I Odin'd both of those in and so far so good! It did the whole updating thing again just like before this time, but when it was done it actually loaded up recovery like it was supposed to. So at that point I wiped the cache, factory reset, then used Odin to flash in the boot loader and modem for CPF3 that I found in that thread.
I've been using my phone and installing things for a couple hours now and haven't had a single hang. Before I did this, it would hang very quickly. Maybe I'll get brave and try rooting and whatnot again later, but for now I'm just going to back off for a bit. Thanks for the help!
And so much for that. It was more stable than it had been in ages so I started installing all my apps and whatnot, now it's just as unstable as it used to be, just took a couple days to happen. I'm running out of ideas
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.
Hi all, I have a note 2 shg-i317 that was originally on Bell in Canada. It was unlocked and the aws mod done to it, I use freedom mobile, aka T-mobile in the states.
I was running a Rom for the past 3 years Slimfast 4.4 and liked it. I had tried Nugat on another phone, thought I would try the [ROM][7.1.2][OFFICIAL] LineageOS for N7105
I did the upgrade, broke the root, could not get a few things working, so I decided to restore the Slimfast backup I had just made (complete including modem etc) and everything works except the GPS.
GPS for me is huge, I use it a lot. I cannot lock on to 1 satellite now. Before i was able to lock onto a minimum of 16 in about 30-45 seconds, if outside.
I really dont care if I can get to 7.1 at the moment. I need my GPS back - any troublshooting for getting GPS to work on this phone?
James
I would try to flash the original stock for your phone and country from sammobile. com
Gps should work normaly then. If not your hardware is broken. If it works you can always flash your data back from your Slimfast rom.
Verstuurd vanaf mijn SM-N910C met Tapatalk
Crap, I am posting here, because I did it again. Again not sure how. I tried to run Reserection, and I guess that messed up the GPS.
To put the original stock rom on.. I have to do that through ODIN? I dont remember how I fixed this last year.. Sorry.
Hope somone can help I need the GPS.
James
ps. Used odin 3.09 to flash the original rom... still no GPS
You flashed the latest 4.4.2 room?
audit13 said:
You flashed the latest 4.4.2 room?
Click to expand...
Click to collapse
The Rom that I flashed to try and restore the GPS was I317MVLUDNF1_I317MOYADNF1_BMC (mine was an originally BELL phone)
But that did not repair the GPS from me flashing resurection.. I THINK did it. I flashed an android 6 and an android 7 rom. (Mokee) but tried to go back to my Slimfast.. and the GPS was now broken.
Basically what I did a year ago.. somehow I fixed it then.. but cannot remember at all how I did it.
James
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
audit13 said:
The note 2 sold by Rogers, Bell, and Telus are exactly the same model and stock roms from these carriers can be cross flashed.
Try flashing the stock ROM twice in Odin with a factory reset in between each flash.
Click to expand...
Click to collapse
Do you mean boot up the rom.. run the reset in the rom? or flash.. - load TWRP back in.. WIPE.. then FLASH again with odin?
Thanks for helping btw.
James
I have backups (complete all partitions) of my rom.. Slimfast 4.4 from 2-3 days ago.. when I tried this. SO.. if I can get the Factory rom to restore the GPS.. how can I restore the backup.. I saw somewhere that the EFS partition could be left out and that might help? dont restore the modem? how??
James
I meant flash with Odin, boot into stock recovery, factory reset, flash again with Odin, boot into stock recovery, factory reset, and boot into the stock ROM.
Nope, still no GPS lock.. I have the flashing circle (always had) and it will not lock.. I read about where people go into a service mode and rebuild the NV? .. I assume this is something that Mokee or Reserection did.. not sure how.
Any other ideas?
James
what about using Odin or TWRP to put different modems in? does the modem effect the GPS?
tried this.. does not seem to. grrrrr wish I knew how I fixed this.
James
I assume there are no loose wires. Does it get a lock when using wifi? Not sure what else to suggest.
Not sure about rebuilding NV.
No.. I broke it with playing with custom roms.. Liniage was last year.. I did not try that this year.. but tried both android 6 reserection and android 7 Mokee.. and I am pretty sure they messed it up.. I am also pretty sure there was something I did .. easy like load an old STOCK rom and it fixed it.. I was then able to put my slimfast 4.4 back over it and it was fine. Unfortunatly .. not enough people still using this device.. I will have to have patience I guess.
James
So I have tried differenct stock roms, but I think the issue is ODIN will not restore code from a rom image that is HARDWARE based. I wanted to use Samsung smartswitch but they disabled the part of it that allowed you to factory reset the phone, this seemed to work for several people. Many have also reported entering a code and going into a service mode.. there you can do to a menu that will rebuild hardware modules back to default. But I have not been able to get into that mode because it seems to be a touchwiz only option, and I cannot find a factory rom that is touchwiz based for this model.
What needs to be done is a true FACTORY ROM image.. that would revert all software and hardware back to original, but I cannot seem to find that anywhere.
James
The only factory roms that I know of come from places like sammobile.com and they are all based on TouchWiz which is Samsung's launcher.
So guess what? put Ressurection back on.. and the GPS is back.
I cannot get it to work in any KitKat based rom.. but now anything Marshmellow up.. works.. HMMMMMM
James