Hey,
I just installed lineage os using trwp, and found that the wifi doesn't turn on. Whenever I try to turn it on, it turns itself back off. When I reset the phone using trwp, I get the error: unable to mount storage. Does anyone know how to fix this?
Thanks.
mindmash said:
Hey,
I just installed lineage os using trwp, and found that the wifi doesn't turn on. Whenever I try to turn it on, it turns itself back off. When I reset the phone using trwp, I get the error: unable to mount storage. Does anyone know how to fix this?
Thanks.
Click to expand...
Click to collapse
Did you format system, data, and internal storage before flash LOS??
try flashing again, but with a previous version of LOS, I think I read that problem in last release.
Were you on nougat firmware? Oreo is latest firmware that works, or you could flash the oreo dsp file from leedroids thread..
miffymiffy said:
Were you on nougat firmware? Oreo is latest firmware that works, or you could flash the oreo dsp file from leedroids thread..
Click to expand...
Click to collapse
I have flashed back the stock firmware, and found that the wifi was working. I am currently upgrading the stock rom to Oreo, then I'll try flashing Resurrection Remix using twrp. Hopefully I won't find any issues with the internal partitioning.
mindmash said:
I have flashed back the stock firmware, and found that the wifi was working. I am currently upgrading the stock rom to Oreo, then I'll try flashing Resurrection Remix using twrp. Hopefully I won't find any issues with the internal partitioning.
Click to expand...
Click to collapse
It worked!
Thanks.
Related
OK I am having a problem, when i rooted and followed the direction to install both OxygenOS or CM12 nightly I am unable to receive any SMS or phone calls except after a reboot. Once i reboot any saved messages come through and then once the phone sleeps it stops. I have rolled back to CM11S for the time being. Any steps or tricks to follow to get this issue resolved.
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
abhibnl said:
"followed the direction to install both OxygenOS or CM12 nightly" does it mean you are using Multiboot?
Click to expand...
Click to collapse
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
pkp190 said:
No just flashing either one I have this result. Not sure if I am doing something wrong in the process.
Steps:
Wipe all but internal
Flash Rom (then gapps if CM12)
Flash SU
Reboot
Click to expand...
Click to collapse
Well all i could suggest it, also please flash the CM12 firmware once. In theory oxygenOS and CM12 firmwares are compatible. So flash like this:
Install CM12 fimrware zip
Wipe System, Data, Cache, Dalvik etc without Internal memory
Flash Rom Zip
Flash Gapps
Flash SuperSu
and then let it boot and settle down. Before restorign apps or data, check for any issues again
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
pkp190 said:
seems to be sitting stable at the moment, will keep testing. but thanks for the input.
Click to expand...
Click to collapse
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
abhibnl said:
Great! Let me know if the bug persists. And be careful with firmwares. For CM12 roms, just flash the firmware once and you're good to go for all of then.
Click to expand...
Click to collapse
spoke too soon, after letting the phone sit ideal for a few hours and testing incoming calls\sms nothing came through. restored a backup of CM11S, for the week to have a working device. will keep trying to get to a root cause later in the week. will also open a help ticket with OnePlus to see if there is something I am missing as well since this happens with OxygenOS as well.
I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.
uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance
I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?
same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?
uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance
So I was on sultan cm13 rom and decided to flash RR v 5.8.3 today.
I was having multirom installed, but uninstalled it before continuing.
After flashing RR the "android.media has stopped" popup started to come up and there was nothing in music library or gallery.
But in explorer i can see my files intact.
Tried flashing halogenOS still same result..
Tried pure lineage OS build still same result..
Can anyone help on this issue?
I am back on pure stock rom for now..
rrgreatvijay5 said:
So I was on sultan cm13 rom and decided to flash RR v 5.8.3 today.
I was having multirom installed, but uninstalled it before continuing.
After flashing RR the "android.media has stopped" popup started to come up and there was nothing in music library or gallery.
But in explorer i can see my files intact.
Tried flashing halogenOS still same result..
Tried pure lineage OS build still same result..
Can anyone help on this issue?
I am back on pure stock rom for now..
Click to expand...
Click to collapse
Which recovery you were using and what flashing steps you exactly followed?
Mr.Ak said:
Which recovery you were using and what flashing steps you exactly followed?
Click to expand...
Click to collapse
Recovery: twrp-3.1.0-K1-bacon.img
Steps i followed:
1. Uninstalled multirom by flashing the multirom_uninstaller.zip
2. Flashed this recovery "twrp-3.1.0-K1-bacon.img" previously i had multirom recovery
3. Then reboot to new recovery.
4. Wiped Data,System,Cache,Dalvik-cache.
5. Flashed halogenOS build:20/04
6. Flashed Gapps 7.1 arm nano.
7. Rebooted
Then the error popup started coming after the setup wizard.
I looked at music, it showed no music found, same with gallery no photos found was coming
I thought maybe ROM bug so i clean flashed RR latest build(downloaded today)
Same problem in RR ROM also.
So i clean flashed lineage Rom, i thought maybe it was some firmware issue, still same problem!!!
So now i am back to full stock(flashed all the fastboot images of stock rom cos13)
rrgreatvijay5 said:
Recovery: twrp-3.1.0-K1-bacon.img
Steps i followed:
1. Uninstalled multirom by flashing the multirom_uninstaller.zip
2. Flashed this recovery "twrp-3.1.0-K1-bacon.img" previously i had multirom recovery
3. Then reboot to new recovery.
4. Wiped Data,System,Cache,Dalvik-cache.
5. Flashed halogenOS build:20/04
6. Flashed Gapps 7.1 arm nano.
7. Rebooted
Then the error popup started coming after the setup wizard.
I looked at music, it showed no music found, same with gallery no photos found was coming
I thought maybe ROM bug so i clean flashed RR latest build(downloaded today)
Same problem in RR ROM also.
So i clean flashed lineage Rom, i thought maybe it was some firmware issue, still same problem!!!
So now i am back to full stock(flashed all the fastboot images of stock rom cos13)
Click to expand...
Click to collapse
Did you tried without flashing GApps?
Mr.Ak said:
Did you tried without flashing GApps?
Click to expand...
Click to collapse
Yes, with Lineage OS
rrgreatvijay5 said:
Yes, with Lineage OS
Click to expand...
Click to collapse
Did you tried using third party Gallery and Music apps? Also,is there no issue like this on Cos13.1.x and Sultan's Cm13?
Mr.Ak said:
Did you tried using third party Gallery and Music apps? Also,is there no issue like this on Cos13.1.x and Sultan's Cm13?
Click to expand...
Click to collapse
No for both questions..
rrgreatvijay5 said:
No for both questions..
Click to expand...
Click to collapse
Then try using third party gallery and music apps.
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
valvze said:
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
Click to expand...
Click to collapse
Isn't "Android is starting" a normal process? Or was it just stuck there?
Which twrp you're using?
Did you flashed just the ROM or also the gapps?
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Try flashing without gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Mr.Ak said:
Try flashing without gapps.
Click to expand...
Click to collapse
Ok I'll try that, thanks
sethu surya teja said:
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Click to expand...
Click to collapse
Ok I'll try that as well, thanks
thus I don't have OS anymore, so I can't boot into download mode.
I have TWRP, I think the only thing I can do is just get stock .zip ROM. But I can't find it for my G930F, I downloaded some but they are all prepared for odin, not for recovery.
Could please anyone give me a download link for a flashable stock rom?
Or any other ideas?
Thanks
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Beanvee7 said:
You had TWRP but didn't make a backup?
Technically it doesn't have to be a stock ROM, you could just flash a custom ROM and once you've got system back then you can flash back to stock with Odin.
Click to expand...
Click to collapse
So I do have LinkeageOS 16 installed now, but every restart, I can't mount /data in TWRP, I have to wipe it over and over. Why is that?
Another thing is that phone doesnt detect my SIM card (on stock recovery it did detect).
iirc that's something to do with encryption, but I've never experienced it so can't be sure.
Can you tried a stock Odin flash since installing Lineage?
Are you using the most recent TWRP?
Droiderat said:
Are you using the most recent TWRP?
Click to expand...
Click to collapse
I flashed newest stock ROM and updated twrp and everything seems to be working now
Weird, I didn't have to reflash LOS.
But yeah, I will write here if the problem still persists later.