Related
3rd thread, about 4th rom flashed
constant issues with builds. have gone from stock to:
cm 6.1.3 -apps crashing, random crash notices i.e "phone book has crashed force close" - "the process com.android.phone has stopped unexpectedly"
cm 7 - random reboots, opening browser caused power cycle, wifi issues, lag (thread posted, no solutions at the forefront)
currently on tripnraver pre release. now another issue. no signal what so ever.
original baseband on this xperia x10a is .55. it is suggested to use with bands 52 or 49.
loading either of these basebands. which ive done. doesn't seem to fix the no signal problem. the description states should be backwards compatible even if appropriate bb is not installed on device. yet no luck.
attempting to flash either baseband fails to resolve this problem. currently trying to flash back to stock and try another full reinstall and baseband flash in flashtool.
any ideas would be a great help. having to flash x number of times between roms is getting quite time consuming
thanks everyone.
if you want to stay on the miui rom, you can flash the baseband patch located here and stay on whatever baseband works best for you (I'm on .55 and find it fantastic), then when you load the rom, go to dev tools>bad behaviour>crash the system server.
http://forum.xda-developers.com/showthread.php?t=1011608
Otherwise, I would recommend wolfbreaks cm 6.1.3, as it is the most stable. You must have done something wrong during installation as I never had an issue with his roms.
The only issue I have ever had with any rom is MiUi and thats because I used the wrong baseband. You must be doing something wrong for you to be having problems
if you want, try this flash, it's trips miui pre-final with the baseband patch implemented.
http://www.multiupload.com/KCKE9K2WKN
worked with my .54 baseband
thanks so much for the links to the baseband patches. i remember coming across a thread that posted it but unfortunately forgot to book mark. so im definitely going to go ahead and try with the patch installed. hopefully all works well
each rom ive flashed has been done properly according to instructions. cache wiped, dalvik, and full reset as per menu options in xrecovery.
one way or another i experienced lag for the most part, and as mentioned some random crashes. never had reset on wolfs rom just error messages at times. trips rom worked excellent, smooth and quick. hopefully with the patch implemented everything will work flawlessly
thanks you guys
*Updated
Flashed over rom with baseband patch. signal working. everything running smooth.
except for when using camera zoom. zoom default displays 0x. as soon as the option is selected it spawns an immediate force close
any patches? or similar outcome for anyone else?
i will outline my steps below so everyones up to speed on how i performed this flash.
- flashed back stock in SEUS
- root with one click (success)
- installed busy box (market)
- installed xrecovery apk
- booted into xrec
1. full factory reset
2. wipe cache
3. wipe dalvik cache
4. wipe battery stats
5. install custom zip from sd card
6. selected trips rom with bb patch implemented
5. reboot
Camera zoom doesn't work in most ROMs yet and the lag you were experiencing was likely just the FW "settling" it can take a little bit and a couple reboots sometimes for the phone to calibrate itself properly.
Sent from my X10i using XDA Premium App
thanks cmoney. maybe ill try my luck with cm7. give it a few reboots and hope for the best. great rom. im really loving trips iphonesque style
clean smooth and quick. everythings working great. hoping the zoom may get fixed soon enough. only other inquiry i have with regards to this rom is the apps2sd.
this feature is essential to myself personally. and it is not working as ive noticed on this rom. ive read a thread with regards to a fix for the last release. i checked the settings for an enable option in case the feature requires being manually set as active but nothing listed. within sd settings state reads as unavailable. if anyone has an answer as to whether this fix will function with the current pre release. ill be going ahead with completeling the flash and reporting what i find back on this thread.
thanks again everyone
Try Wolfbreaks rom. It's very very stable for me. It has cam and everything upto date.
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
thesoundofsilence said:
im going to flash back to wolfbreaks updated 6.1.3 unless anyone can point me in the direction of a fix for trips rom.
the smooth and fluid feel of trips rom was brilliant. i am hopeful someone has directions for an apps2sd fix as i have flashed the build twice and the same issue has occured.
Click to expand...
Click to collapse
works for me on trips newest....
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
thesoundofsilence said:
i just downloaded the new version 1.0
this is ridiculous. without the baseband patch. crash system server. no signal
now apps to sd is saying "apps2sd is not supported on this device"
this is an xperia x10, so obviously there must be something wrong here.
can anyone elaborate on exactly what to do about this because im going to attempt to flash back the rom, flash the bb patch right after, reboot. i assume this will only solve my signal issue. but this apps to sd is getting extremely frustrating and i can not figure out why it is not showing an enabled status.
- Flashed 1.0 with baseband patch - network signal resolved.
- apps to sd is STILL not working. and i really dont know what to do about this. everything else on this rom is perfect. is there something im missing? i came across a patch for apps2sd fix but this was for a previous version. would it be needed here? is there a setting that must be enabled first in order to start apps to sd as a service.
- as mentioned previously within the main menu, under sd card settings. message states "apps2sd is not supported on device" and on previous build would display "apps2sd unavailable". its simply impossible that the phone doesn't support it. as with every other rom the feature has worked. froyo would support it. the question is how do i go about enabling said feature?
Click to expand...
Click to collapse
I dunno man, it works fine for me, but I copied data from my 0.3.2 xrecovery image, so that might be why. try flashing that apps2sd fix for 0.3.2, should work fine
damn it. i just found that thread. found the links to the fixes. so far ive tried miui32_a2sd_fix.zip. and flashed that over with xrec prior to reboot. which did nothing.
there are two more links so im going to try those two flashes as well and hope that one of them will do the trick. if its working when utilizing .32 patches then ideally the bloody thing would have to work here. thanks for the input though dtox. much appreciated
I don't know what else to suggest man
From the feedback I see in the miui thread, everyone else is reporting it working!
Did you factory wipe, wipe cache partition, and wipe dalvik cache before install? then flash the miui 1.0.zip, and flash immediately the baseband patch then reboot into the rom.
Remember not all apps allow apps2sd so use something like android system info, go into the applications tab click on one, click manage and then see if the option "move to sd" is highlighted. Like I said check a few though, not all apps can be moved
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
thesoundofsilence said:
i just replied in the dev section lol but yes i have gone ahead and checked the applications menu. specifically downloaded a file i have moved to sd on a previous occasion from the market.
nothing
the "apps to sd" selection is completely greyed out. no matter what application i click on or download. i did a full wipe, full install, and selected the apps2sd fix immediately after rom and bbpatch flash, prior to rebooting. issue still remains.
we'll see i guess. thanks again dtox
Click to expand...
Click to collapse
Try it again but without the fix...
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
thesoundofsilence said:
i did that to it doesnt work i get the same message displayed
i tried with fix and without. another thing to note is that the rom itself says it should work with a different baseband as it has elements of unified. (which it doesn't) i had to flash the bb patch to get signal.
im not sure whats up with this but until i figure it out for a certainty ive flashed back over to wolf breaks rom. hopefully something will surface and i can give trips rom another go.
Click to expand...
Click to collapse
No idea man, like I said it is fine for everyone else so I'm so no big development will arise that will make it function with your phone....
maybe it has something to do with 10a. i dont know. but the point is it shouldn't even be doing this regardless. hypothetically if its froyo and it has apps2sd built in. it should work. its not the way ive flashed. the phone supports it. so my only conclusion the rom must not be as compatible as stated. and from reading different posts about the prev builds sometimes the patches worked at other times they didnt. and also the fact that the rom is claimed to work without the need for a bbpatch. yet without the patch instaled phone caught no single. i guess certain unexplainable glitches can be bound to happen at times but any how ill give it one last go.
if nothing comes out of that then im giving up on that build because it seems relatively hopeless.
lol I'm using an x10a...
Still man you're the only person reporting this. Don't you find that strange? What baseband are you using anyhow?
Hi I got problems with my lux on every cm based rom. On every cm rom I get no reception of my carrier. I don't know if it's a device tree issue or just apn trouble. Since there are no aosp roms, I'm a little hung up. Stock rom works fine. I own the xt1562 operating on German carrier o2. Sometimes I get a few seconds of reception on cm roms, but it's leading just to no signal after a few seconds again. I nearly tired everything, flashed a different firmware etc. When I've flashed a rom I get the information that no sim card was found. After I restart the device he's asking for a pin. Also tried another sim card with the same result. Really could need some help.
flash the original fimrware from ur carrier or region
flash twrp
install cm and see if works
if not,flash only the radio modem from original firmware
Already did. Didn't work. Flashed the new cm12.1 from h2o64. This one is working.
I have the exact same problem with my XT1562 I bought from Germany through Moto Maker.
I installed h2o64's CM build from 10-10 after a full wipe (everything except internal data), and never got any proper signal. I tried squid2's CM build 10-12 as well, to no avail. Installing the XT1562 EU stock firmware following the linked explanation in the stock firmwares thread I had good, working signal, but then installing h2o64's CM build 10-14 with a factory reset rather than a full wipe resulted in the same issues described in this thread again.
I've read about these issues in different threads, mostly resolved somehow by installing the stock firmware, sometimes by selecting LTE as the preferred network type. I've tried these suggestions, but haven't had any success, and I don't know how to proceed.
Did I install the right stock firmware? (I would think so as it worked while it was installed.)
Did I forget to do something (like wipe, fix permissions, reboot the phone three times, howl at the moon,...)?
I use OpenGApps rather than tkruzze's since they're available in x64 as well so I can use them on all my devices. But that surely can't be it?
I'm at a complete loss at the moment, which is rather frustrating. Can anyone provide any help?
Gesendet von meinem Nexus 9 mit Hilfe von XDA Forums Pro.
I managed to install h2o64's CM build 10-14 and getting proper signal now.
I flashed the RETASIA firmware from XMoDuLeSx's Official stock firmwares added for xt1562,xt1563 thread following the instructions linked in the first post, and then after a wipe of system, data, cache, dalvik-cache I installed [ROM][lux][5.1.1] Cyanogenmod 12.1 - 2015-10-14 [UNIFIED].
Keep in mind that I have ordered my Moto X Play from Germany, so it shouldn't require a RETASIA firmware. I'm not advising to install this, as it was nothing but a shot in the dark that surprisingly didn't brick my phone. Still, I wanted to share that I got it working after all, simply to follow up my previous post properly. Should the signal break again, I'll update this thread; if I haven't, assume that it's still working.
Either way, though: If you decide to go down this road and install a firmware that isn't right for your phone and brick it, don't come to me. I'm advising against doing this.
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Mafaldine said:
Seems i'm having the same issue...
I did all the wipes and clean installs but I can't connect to my carrier.
Although my phone only supports one sim card, settings shows two. The first one is the one i'm using and it is displayed correctly. The quick settings tile though tells me that there is no sim card inserted.
I came from stock, unlocked, flashed TWRP from squid2's kernel page, rooted, flashed CM(squid2), kernel(squid2) and OpenGApps.
Did I do something wrong?
Is there any news on how to fix this problem or do I have to try again and again an hope to hit the spot?
Click to expand...
Click to collapse
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Lennyz1988 said:
You need two more posts before you can post this in the CM thread from squid2. Squid2 is always fast with bugfixes. So make 2 other post and then explain your problem to him.
Click to expand...
Click to collapse
Thanks for your reply!
I will do that
Meanwhile I managed to get a connection to my carrier by flashing h2o64's CM build 10-14 and then squid2's on top without wiping anything...
RR Lux 5.5.8 didn't work Wifi, after 2 clean instalation, wifi turn on and off then
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
Below is my original post; however, I've since solved the problem. In an effort to help others with the same problem, I've written a Guide, which should explain exactly what to do if your WiFi is suddenly "broken" due to flashing issues.
Here's the link: OnePlus 5 WiFi Fix
Many thanks to everyone who offered help, especially subaash and hallo dare, who put me in the right direction.
--------------------------------------------------------------------------------------------------------------------------------------
Greetings, everyone.
Sadly, for specific reasons unknown, my WiFi appears to be completely broken.
Over the last few days I've gone "flash happy" by trying several Oreo ROMs for my OP5. Some worked while others just froze at the boot animation.
Unfortunately, shortly after flashing the xXx-NoLimits Oreo ROM, which got me to the initial set-up screen, my WiFi would not connect. So, I then bypassed the WiFi part and finished the set-up. Everything seemed to be working very well, but I could not get WiFi to work.
Yes, I could engage the Wifi slider to the ON position, and there would be a list of SSIDs; however, oftentimes even my 2 SSIDs would not display. When they did, and I tried to connect, I would see the connection attempt, but it would not complete the connection. Only the word "saved" would be shown under the SSID name. Then it would automatically try to reconnect, but without success.
I've tried virtually everything I can think of to solve the problem, but I can't connect to WiFi.
All other communications work, i.e., Bluetooth, Data, making and receiving calls. It's ONLY the Wifi that's not working.
Yes, I completely wiped my device and re-installed the original OxygenOS (4.5.14), but that didn't work. I also tried completely wiping the device and then installing that latest OxygenOS v4.5.15, but that didn't solve the problem, either.
I went back and flashed all the previous custom ROMs in an attempt to see if any of them would work, but nothing. I tried NitrogenOS, HalogenOS, Liquid Remix, xXx NoLimits, and they all could not connect to WiFi.
I even tried a few WiFi Fix apps on Google Play, but they didn't work, either.
Oh, yes … I even checked my router. It's perfectly fine. I can get WiFi on my laptop without a problem. Furthermore, when I went to a local coffee shop this morning that provides free WiFi, my phone could not connect, just like at home.
Does anyone have ANY suggestions?
Thank you,
Peter
I would say this is to do with your firmware/modem.
I did have this issue on a non Oreo ROM and in the end I just did a dirty flash and it worked.
dladz said:
I would say this is to do with your firmware/modem.
I did have this issue on a non Oreo ROM and in the end I just did a dirty flash and it worked.
Click to expand...
Click to collapse
I've tried flashing both the 4.5.14 and 4.5.15 firmware, with no luck; however, I accidentally deleted my modem nandroid about a week ago.
Do you know where I might find a flashable modem file?
Thanks,
Peter
Addendum: I found the following site for Firmware & Modems:
https://www.jamal2367.com/?dir=OnePlus 5/Firmware + Modems/Android 7.1.1/OxygenOS
I'll try flashing them and report back.
Addendum 2: NOPE! Didn't work. I flashed a few different firmware & modems, 4.5.13, 4.5.14 and 4.5.15, but WiFi is still broken. Yes, I first flashed the appropriate OS version before flashing the firmware and modem. In other words, I always matched the OS version with the firmware & modem version, but no success. Everything works except WiFi. Hmm, still stumped.
PeterGuru said:
I've tried flashing both the 4.5.14 and 4.5.15 firmware, with no luck; however, I accidentally deleted my modem nandroid about a week ago.
Do you know where I might find a flashable modem file?
Thanks,
Peter
Addendum: I found the following site for Firmware & Modems:
https://www.jamal2367.com/?dir=OnePlus 5/Firmware + Modems/Android 7.1.1/OxygenOS
I'll try flashing them and report back.
Click to expand...
Click to collapse
Careful with modems mate. There's a thread here on XDA containing modems and firmwares..just make sure you get the right one.
dladz said:
Careful with modems mate. There's a thread here on XDA containing modems and firmwares..just make sure you get the right one.
Click to expand...
Click to collapse
Thanks! I'm quite aware of the need for caution with modems. Sadly, though, it didn't solve the problem.
yea my freind in idia s 1p5 was flasing anything and his oneplus 5 got weird but turns out ok googles cousin hey google had a hangover, i cleared her cache and threatened her with king root & she slowed her role, i asked her why her cousins voice is so shot out,she said ok google has a hi and low voice cuz she burnt out but now ok google took my vpn and dipped to inda for some oneplus christmas party. what ever just watch out for hey google, cuz if you got volte 5g and a vpn they b will go offline and dipp with your vpn to india. i guess india likes oneplus. hold up this is the be delighted thread?
Did you get this sorted, having the very same issue
hallo dare said:
Did you get this sorted, having the very same issue
Click to expand...
Click to collapse
Sadly, no. I've tried absolutely everything I can think of, all without success. It's very frustrating because absolutely everything else works, except WiFi.
All I can do now is wait for suggestions from others, or take the phone to a repair shop (which I'm hesitant to do).
Peter
Thanks for replying. If you happen to get it sorted, please let me know. I will do likewise if I manage to fix it. Thanks
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
ab7casper said:
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
Click to expand...
Click to collapse
Done that already, tried old roms of OOS and Oreo, but still no joy. Heads wrecked with it.
hallo dare said:
Done that already, tried old roms of OOS and Oreo, but still no joy. Heads wrecked with it.
Click to expand...
Click to collapse
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Thanks, i'll give that a go
---------- Post added at 07:36 PM ---------- Previous post was at 07:02 PM ----------
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Ok I done that, and now, wifi is still doing the same thing and under the network i pick it just goes to saved and then says disabled under it.
hallo dare said:
Thanks, i'll give that a go
---------- Post added at 07:36 PM ---------- Previous post was at 07:02 PM ----------
Ok I done that, and now, wifi is still doing the same thing and under the network i pick it just goes to saved and then says disabled under it.
Click to expand...
Click to collapse
Same problem but only on my 5GHz network and dont know how to fix
PeterGuru said:
Greetings, everyone.
Sadly, for specific reasons unknown, my WiFi appears to be completely broken.
Over the last few days I've gone "flash happy" by trying several Oreo ROMs for my OP5. Some worked while others just froze at the boot animation.
Unfortunately, shortly after flashing the xXx-NoLimits Oreo ROM, which got me to the initial set-up screen, my WiFi would not connect. So, I then bypassed the WiFi part and finished the set-up. Everything seemed to be working very well, but I could not get WiFi to work.
Yes, I could engage the Wifi slider to the ON position, and there would be a list of SSIDs; however, oftentimes even my 2 SSIDs would not display. When they did, and I tried to connect, I would see the connection attempt, but it would not complete the connection. Only the word "saved" would be shown under the SSID name. Then it would automatically try to reconnect, but without success.
I've tried virtually everything I can think of to solve the problem, but I can't connect to WiFi.
All other communications work, i.e., Bluetooth, Data, making and receiving calls. It's ONLY the Wifi that's not working.
Yes, I completely wiped my device and re-installed the original OxygenOS (4.5.14), but that didn't work. I also tried completely wiping the device and then installing that latest OxygenOS v4.5.15, but that didn't solve the problem, either.
I went back and flashed all the previous custom ROMs in an attempt to see if any of them would work, but nothing. I tried NitrogenOS, HalogenOS, Liquid Remix, xXx NoLimits, and they all could not connect to WiFi.
I even tried a few WiFi Fix apps on Google Play, but they didn't work, either.
Oh, yes … I even checked my router. It's perfectly fine. I can get WiFi on my laptop without a problem. Furthermore, when I went to a local coffee shop this morning that provides free WiFi, my phone could not connect, just like at home.
Does anyone have ANY suggestions?
Thank you,
Peter
Click to expand...
Click to collapse
So first of all the reason why it is broken is because of the oreo firmware that you flashed earlier. Now what you should do is flash stock recovery and flash the oreo build and boot it up and running. Once you've done that flash the rollback rom (which suppose to downgrade your oreo firmware to nougat firmware). Once you've done it basically it fixes you're wifi issue.
PeterGuru said:
Thanks! I'm quite aware of the need for caution with modems. Sadly, though, it didn't solve the problem.
Click to expand...
Click to collapse
There's a button for that son..
Also the firmware / modem will be the problem, either upgrading or rolling back..either way it'll be the cause.
ab7casper said:
Try reflashing the rom. Not sure why, but that happened to me and reflashing the rom fixed it.
Click to expand...
Click to collapse
Eric214 said:
Do you have a full rom backup? I mean of the last working rom you had before all the flashing? If so, from a full stock rom (1.53gb or close) of the same build as the backup (ie... 4.5.14) wipe and flash that rom, then wipe and restore the backup you have if the last working rom. If they doesn't work I think you're likely looking at a hardware issue.
Click to expand...
Click to collapse
Dimontiman said:
Same problem but only on my 5GHz network and dont know how to fix
Click to expand...
Click to collapse
Okay, let me first answer a couple of questions. Like I said in my first post, I DID flash the original ROM, as well as other OEM OxygenOS ROMs, all without success. Yes, I used the exact same ROM that was working perfectly before the problem. Yes, I also had a FULL Nandroid of the working system, but restoring that also did nothing to solve the problem.
Okay, with that out of the way, I went to a repair shop this morning to try and solve the problem. It was unsuccessful. The technician said it's unlikely to be hardware related because I can still get the phone to recognize all local SSIDs. I simply can't connect to any of them. Just like hallo dare said in his post a few back, when I try to connect to my SSID, it tries to connect for a second or two, and then it just shows "saved" and wifi is disabled.
So, for now I'm still completely stumped.
Peter
subaash said:
So first of all the reason why it is broken is because of the oreo firmware that you flashed earlier. Now what you should do is flash stock recovery and flash the oreo build and boot it up and running. Once you've done that flash the rollback rom (which suppose to downgrade your oreo firmware to nougat firmware). Once you've done it basically it fixes you're wifi issue.
Click to expand...
Click to collapse
dladz said:
There's a button for that son..
Also the firmware / modem will be the problem, either upgrading or rolling back..either way it'll be the cause.
Click to expand...
Click to collapse
Okay, I will do exactly what subaash said and report back. I, too, agree that it's probably software related, which is why I'm actively attacking this issue.
Be back as soon as I can.
Peter
P.S. "Son?" Hmm, I have a sneaking suspicion that I'm older than you (will be 60 in March).
Success ... maybe?
Well, well. It appears the previous suggestions were correct. So far it's successful, but I haven't quite finished the initial set-up. All I can say is that WiFi is working, and I'm grateful for that.
However, it was a frightening ordeal. At one point I thought my device was bricked, and I didn't know what to do. However, with some thought, I was able to solve the problem.
Good news, though, is that I DID NOT have to revert back to Nougat. I'm now running Oxygen Oreo 8.0.0 Open Beta 2.
I will provide a detailed instructions of what I did a bit later. I simply want to get everything up-and-running, which could take a few hours.
Here's an abbreviated version:
Downloaded Oxygen Oreo 8.0.0 Open Beta 1 from here:
http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_openbeta_1/
Downloaded Stock Recovery from Post #2 here:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Copied both files above to root of device internal storage
Reboot into TWRP recovery
Flashed stock recovery in TWRP
Reboot into stock recovery
COMPLETELY Wiped the entire system ... absolutely everything ... including internal storage. This is where I had the initial problem. I did not wipe everything, including internal storage, and I ended up with a mixture of jumbled numbers and letters when looking at the file structure.
Using ADB Sideload within the stock recovery, I "moved/flashed" the ROM ZIP to the device
After successful sideload, I said yes to installing the ROM
The ROM then installed and, voila, I'm at the initial set-up screen.
Okay, that's all for now. I'll be back later.
Peter
Format data resolves the problem (at least with me...)
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
but the last 3 days since...
Phone calls Go right to my voicemail box they dont even ring on my phone....
And my [defualt]texting app constantly shows a little cloud crossed out saying no service
Anywheres I had 4gLTE Is now 3g ONLY and i can only do things on the internet thats it, but its slow as a dog.
Airplane mode on-off doesn't work I dialed that *#*# .. (insertnumbers) #*#* for testing and
switching how my phone recieves signal didn't work,
Factory reset from inside my settings + Hard reset from recovery made 0 difference.
Ill recieve all my texts but cant reply to them by rebooting my phone they all come in at once when my phone turns on but them my message app stops working again
-----------
Called my provider (TOTAL WIRELESS,) They said everything fine on thier end nothing they can do. So I called Huawai, and Verizon... got no where.
So im thinking... Its the update patch, or i need a new sim card.. So where / how Do I get the Nexus 6p's STOCK ROM So I can reinstall and how do i do that?
Should i try that? wait for another patch? or request a new sim.... Because as of right now my phones a brick and i use it for work.
Fluttershy_plays said:
Hey' y'all Color be crazy but....
About 3 days ago I checked for updates OTA, and got a new sequrity patch.
my phones a brick and i use it for work.
Click to expand...
Click to collapse
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Could you help me find that? not sure 100% on navigation of this website but ill try.
Exodusche said:
Your not alone my friend I had the same issue with Aprils update. Just randomly during the day I would stop receiving texts and phone calls. I just assumed I was in some kind of bad zone even though had never happened before. Wasn't until my favorite stock build SuperXe got updated to Mays that I switched and haven't had the problem since. Right now I'm on Lineage 15's June build and wow it has come a long way pretty solid no issues. You will have to do some research on unlocking your bootloader and flashing stock images. You can find them if you search "Google API Nexus 6p." Check out Hiesenbergs tutorials on XDA on returning to stock on the flashing procedure. Its the same for flashing stock images of any month you choose. I got simple fastboot 1.4.3 from XDA as well instead of installing Google's fastboot .
Click to expand...
Click to collapse
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
--EDIT--
Fixed by going back to stock and starting over.
Fluttershy_plays said:
Found his guide but..
I got to step 6 in his guide, rooting. and now my phone wont boot past google logo
Click to expand...
Click to collapse
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Exodusche said:
Ok first you want to boot up and finish initial setup before rooting. Second you want to root with Magisk 16.0 zip. You don't have to root unless your planning on modifying system files or using a special app. You can fix or unroot by reflashing just the boot.img from the firmwarwe or Rom you are currently running .
Click to expand...
Click to collapse
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Fluttershy_plays said:
well i got up and running (8.0 no updates yet) and my 4g lte / Texting capabilities ARE BACK!!!!.
Also, Can i still root, APP side? or does it have to be through flash?
thanks for pointing me in the right direction!
Is there a way to report this issue to google so they can fix it?
Click to expand...
Click to collapse
I'm sure there's a way to root with app but just as easy to flash TWRP and install Magisk. Which has nice easy feature of hiding root and passing safety net. That way you get a certified playstore and still use android pay to name a few. If your interested let me know I can explain the process after flashing Magisk.