At this point, I'm assuming I did something with my phone. I've easily tried twenty combinations between different ROMs and gapps packages. I used TWRP, and didn't make a backup because I'm dumb.
None of my installations (if I can get past Google crash notifications) have usable wifi, and on one occasion, the flashlight wouldn't work. Bluetooth is able to be turned on, but I haven't tried connecting anything.
Any advice? I've been trying the whole process on Mac. My Windows machine isn't even recognizing the drivers I've downloaded. At this point, I'd settle for the stock ROM again.
Any help would be GREATLY appreciated.
colderphone said:
At this point, I'm assuming I did something with my phone. I've easily tried twenty combinations between different ROMs and gapps packages. I used TWRP, and didn't make a backup because I'm dumb.
None of my installations (if I can get past Google crash notifications) have usable wifi, and on one occasion, the flashlight wouldn't work. Bluetooth is able to be turned on, but I haven't tried connecting anything.
Any advice? I've been trying the whole process on Mac. My Windows machine isn't even recognizing the drivers I've downloaded. At this point, I'd settle for the stock ROM again.
Any help would be GREATLY appreciated.
Click to expand...
Click to collapse
Sorry for the late reply. Sounds like a persist partition issue. Flash stock ROM .
Hi!
Following up on that - had the same, flashed different Pie roms and none would have functioning wifi. And yes, i did flash stock rom via Emma few times.
Any ideas?
Maybe there is something in flashing process? I had other phones (HTC, Samsung) and flashing them was never a problem....
Additionally - tried hard to get xposed to work via Magisk, but all i got was bootloop. Any advice how to get Xposed to work ? I have XA2.
Thanks!
mjaxa said:
Hi!
Following up on that - had the same, flashed different Pie roms and none would have functioning wifi. And yes, i did flash stock rom via Emma few times.
Any ideas?
Maybe there is something in flashing process? I had other phones (HTC, Samsung) and flashing them was never a problem....
Additionally - tried hard to get xposed to work via Magisk, but all i got was bootloop. Any advice how to get Xposed to work ? I have XA2.
Thanks!
Click to expand...
Click to collapse
Flash latest rom via xflasher and everything working fine
Well, i have no problem with flashing factory ROM. I had problems with custom ROMs.
Anyway - managed to get it. I guess it has to do with dual boot partition, so that one should restart via recovery, and only then restart system.. Or something like that
I had the same problem after flashing custom ROMs. It seems that you have to enable Wi-Fi in stock rom before flashing any customs.
Related
I fall into weird problem. Once I unlocked bootloader and installed custom rom. But when I revert back to stock I lost my 3G. I tried flashing ROMs to get it solved but I failed. It was 5-6 month ago.
Recently, I again flashed custom ROM because stock was too slow. After flashing CM9-KangBang ROM, which, I thought would be good as it was mentioned stable. I found SD card not mounted but 3G worked magically which didn't happened for other custom ROMS. Weird problem is I couldn't install any ROM after that. Because after connecting via usb my computer says, "USB DEVICE NOT RECOGNIZED". So I couldn't install kernel which is required after flashing ROM. Another problem is when I install Ignorance ROM, which doesn't require installing kernel separately, also not working after boot. Stuck on boot animation.
I don't know what to do. Can't find my way. My mobile is off for 3 days. Now its urgent for me to make it run.
Please help me. I never felt so helpless like this because somehow I solved my problem.
N.B - I tried flashing ROM on other computer but same result. USB DEVICE NOT RECOGNIZED. Funny thing is CM9-KangBang works fine without SD card.
So I took out my age old xperia M(single sim) a couple of days ago and installed cm 12.1 on it. The only issue I'm facing with it is that if I keep the phone on standby for a while the phone completely and silently shuts itself off. When this happens it doesn't turn on with the power key as well so the only way to turn it on after this happens is by removing and re inserting the battery and then pressing the power button. (phone boots normally then)
This problem only appears when the phone is in standby. I could use it 2hrs straight and the phone would keep functioning normally as long as I don't keep it on standby for a long period.
I've tried tons of different cm12.1 roms and factory reset the phone multiple times but the problem is there with every single rom. Haven't tried any rom that isn't based on 12.1 yet.
Strange thing is that this standby dead thing doesn't happen when there is a music app that's playing some song while in standby. Even if the phone is on silent and media volume is 0. So the temporary fix is to keep playing some song and keep media volume at 0. I would be really happy if someone comes up with a permanent solution though. Thanks. Any help would be greatly appreciated
Was the problem present on the stock ROM?
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
kurtbvb said:
I have the same problem with CM based roms, went back to stock and it doesn't have this issue, could it be something to do with ambient display/doze?
Click to expand...
Click to collapse
No, I don't think so. Which version did you come from? I would suggest flashing 15.4.A.1.9 first because most custom ROMs use it as base and doesn't offer full compatibility with older versions.
elmkzgirxp said:
Was the problem present on the stock ROM?
Click to expand...
Click to collapse
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
RagzyB said:
Nope. My sister had been using this phone on 4.3 since 1yr now. I decided to use it as a secondary media device when she got a new phone. When I first unlocked my bootloader after rooting the device went into bootloop. So had to restore it to stock 4.1 Indian (couldnt find 4.3 indian ftf) using flashtool (took 2 days and tons of researching to get the drivers working). Then I rooted it again and flashed twrp and cm 12.1. Have been facing this problem ever since.
It's driving me crazy now. Might go back to stock if it doesn't get fixed
Edit - also just checked the sim slot isn't working either. Tried multiple 12.1roms but it won't get detected. Didn't realise this before as I'm using this as a media device and don't need sim card working anyway.
Click to expand...
Click to collapse
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
elmkzgirxp said:
Do what I said to @kurtbvb too, as it may just be base incompatibility. Flash everything except the TA partition (if present) and wipe /data and /cache.
Click to expand...
Click to collapse
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
RagzyB said:
So do I flash stock 4.3 using twrp or do I need to flash the ftf file using flashtool ?
Click to expand...
Click to collapse
Flashtool. Some files are required which custom recoveries can't flash.
Just flashed the above mentioned ftf file and then rooted the phone, installed twrp and then cm 12.1 based rom. Everything runs perfect now. No random shut downs and Sim card works as well.
Thanks you so so much
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.
So I can't connect my phone to the car bluetooth connection in my car. It's ONLY a custom ROM problem. If I use FreedomOS or stock it works fine. I have changed to literally every firmware in existence, still no fix. I can connect to some devices, but I also have problems with Android Wear.
This is a big deal as I bought this phone for a custom ROM. Anybody know what's the fix?
I have read more threads about this, but nobody ever seems to have an answer that isn't "flash xyz firmware ZIP in TWRP" which I've already tried. Please, anybody willing to help, please do!
So you can't pair your phone i assume?. If so I had the same problem.
It was a real issue in earlier aosp roms but now alls I do is clean flash the rom, set up and connect my BT and then if using a theme it goes on last!!!!.
No, it pairs fine, but then never connects as a phone. Only media works. I never dirty flash roms, so that's not the issue at all.
I will try this, then report back. Haven't tried this yet.
Which option in the toolkit should I use? There seems to be no options to revert stock specifically. You mean the OP3 Unified Toolkit, or is there specifically a "unbrick tool"?
Tried it. Not fixed. Used 4.1.3 zip after the reflash of stock using the Qualcomm tool. Should I try a 6.0.1 zip like 3.2.8 OOS or something?
I have built several custom ROMs with a BT fix that gets rid of the "no phone" issue. This sounds like the same issue I had so this should work.
Got my OP3 hard-bricked recently. I followed Naman Bhalla's unbrick guide and flashed down to OOS 3.x. Everything works fine except the WiFi, Bluetooth, and GPS.
The GPS toggle activates when I click on the icon, but it never calibrates my actual position.
The WiFi toggle doesn't activate, no matter how much I try.
The same goes for the Bluetooth option as well.
You can see the problem for yourself here
If I try to flash a new version of OOS, the phone freezes mid-boot and keeps restarting.
Any suggestions?
rahulkulhalli said:
Got my OP3 hard-bricked recently. I followed Naman Bhalla's unbrick guide and flashed down to OOS 3.x. Everything works fine except the WiFi, Bluetooth, and GPS.
The GPS toggle activates when I click on the icon, but it never calibrates my actual position.
The WiFi toggle doesn't activate, no matter how much I try.
The same goes for the Bluetooth option as well.
You can see the problem for yourself here
If I try to flash a new version of OOS, the phone freezes mid-boot and keeps restarting.
Any suggestions?
Click to expand...
Click to collapse
What happens when you try to activate these from Settings?
Flashing OOS later versions may solve the issues. What method did you use for flashing the later versions, adb or TWRP? Try adb.
I didn't face any such issues when I used the Unbrick Guide.
@rahulkulhalli
Do you have op3 or op3t ? This is for op3 .
If you have op3t use this guide
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
mar.ur said:
@rahulkulhalli
Do you have op3 or op3t ? This is for op3 .
If you have op3t use this guide
https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Click to expand...
Click to collapse
OP3
tnsmani said:
What happens when you try to activate these from Settings?
Flashing OOS later versions may solve the issues. What method did you use for flashing the later versions, adb or TWRP? Try adb.
I didn't face any such issues when I used the Unbrick Guide.
Click to expand...
Click to collapse
I tried, but I run into the same bootloop.
I used TWRP touch.
Could you tell me what steps you took after flashing to OOS 3.x?
rahulkulhalli said:
I tried, but I run into the same bootloop.
I used TWRP touch.
Could you tell me what steps you took after flashing to OOS 3.x?
Click to expand...
Click to collapse
I simply flashed the then latest version of TWRP and then clean flashed the later version of OOS and then clean flashed custom ROM coupled with flashing of proper firmware after a couple of days, all using TWRP.
Which version of TWRP do you use? After the OOS 3.x boots up, flash TWRP 3.2.3 official and then try using that for the further ROM installations. If this also fails, use adb to install the ROM. Don't go straight to a custom ROM since you seem to have firmware issues.
You haven't said what happens if you try to enable wifi, BT etc from Settings instead of from Quick Setting tiles.
What I think is you need flash the latest wifi and bluetooth drivers. Just download them from this link and flash using twrp
http://forum.xda-developers.com/oneplus-3/how-to/radio-modem-collection-flashable-zips-t3468628/amp/
You may need to reflash the OS after installing the firmware. Don't directly try to install custom roms after flashing the firmware. First flash latest stable build from official oneplus site, boot into OS and then you can do whatever you want with your device.