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
Related
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Spartiata said:
Hi, i've a stock + root + xposed google nexus 5 with a TWRP recovery; yesterday i've installed and used successfully MultiRom dualbooting CM11 M8 and a CM11S port for my device. Then i've tried to flash both CM11 M8 and CM11S (port) and i'm still getting some problems with the boot:
-if i turn off the device and then start it again the system boots normally and without problems, but if i try to reboot from within the ROM it doesn't work properly, i only see a black screen and, if i reboot to recovery, i'm unable to restore the backup because the recovery is "unable to mount data".
-The only solution is to shut down again the N5, turn it on, shut down again and then boot directly into recovery mode.
NOTE:
before you ask, i performed a full wipe (the default wipe of TWRP that wipes data, dalvik and cache) and then flashed the ROMs
Any idea of why i'm not able to install custom roms without issues? any help would be appreciated
Click to expand...
Click to collapse
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Lethargy said:
I doubt it, but could it be because you have Snapshot M8 installed twice? ("CM11S" is not a port, it is Snapshot M8 with CM11S apks placed into the zip). I would try with two different ROMs.
Click to expand...
Click to collapse
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Spartiata said:
i've full wiped the device before flashing the ROMs, and i've uninstalled all the MultiRoms installation before flashing the new ROM
Click to expand...
Click to collapse
Not sure what to tell you except try another ROM first.
Lethargy said:
Not sure what to tell you except try another ROM first.
Click to expand...
Click to collapse
i'll try with paranoid and let you know
Paranoids works fine, seems like a CM problem .-.
Spartiata said:
Paranoids works fine, seems like a CM problem .-.
Click to expand...
Click to collapse
CyanogenMod will always be CyanogenMod
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.
Hey, so I just bought a Moto G LTE and got very excited about the amount of dev going on here (coming from an LG Optimus F6 which has almost none). Right way I unlocked the bootloader and rooted. So far so good. Then I flashed TWRP recovery and everything seemed fine. I downloaded the ParanoidAndroid ROM and flashed it, and the phone got stuck in a bootloop (with the PA boot animation). I then went back into recovery, did a reset and flashed BlissPop. Same issue (bootloop is now in the BP boot animation).
So now I'm not sure what to do. I can still get into recovery. I selected factory reset through recovery, and on the top of the screen it says "Factory Reset Complete", but on the log it says "Updating partition details..." and just stays like that. Rebooting just takes me back to the bootloop (still with the BlissPop animation).
Anyone have a clue what could be wrong here? Is there a way to check if there's anything I messed up along the way?
Thanks in advance for any help!
magnoidgoat said:
Hey, so I just bought a Moto G LTE and got very excited about the amount of dev going on here (coming from an LG Optimus F6 which has almost none). Right way I unlocked the bootloader and rooted. So far so good. Then I flashed TWRP recovery and everything seemed fine. I downloaded the ParanoidAndroid ROM and flashed it, and the phone got stuck in a bootloop (with the PA boot animation). I then went back into recovery, did a reset and flashed BlissPop. Same issue (bootloop is now in the BP boot animation).
So now I'm not sure what to do. I can still get into recovery. I selected factory reset through recovery, and on the top of the screen it says "Factory Reset Complete", but on the log it says "Updating partition details..." and just stays like that. Rebooting just takes me back to the bootloop (still with the BlissPop animation).
Anyone have a clue what could be wrong here? Is there a way to check if there's anything I messed up along the way?
Thanks in advance for any help!
Click to expand...
Click to collapse
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.
Pupet_Master said:
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.
Click to expand...
Click to collapse
Hey, thanks so much for the reply!
I'm not sure which exact version it is, is there a way to check without having to boot the phone?
I did the advanced wipe, however now when I click reboot it says "No OS Installed! Are you sure you want to reboot?" Now that I wiped the internal storage how do I flash the ROM (it was saved there and is now deleted)?
Thanks again.
magnoidgoat said:
Hey, thanks so much for the reply!
I'm not sure which exact version it is, is there a way to check without having to boot the phone?
I did the advanced wipe, however now when I click reboot it says "No OS Installed! Are you sure you want to reboot?" Now that I wiped the internal storage how do I flash the ROM (it was saved there and is now deleted)?
Thanks again.
Click to expand...
Click to collapse
You must always put the OS flash zip on a MicroSD card.
How ever you can put the USB cable on the PC at TWRP and it should reconize your phone so you can make a file transfer
YOu have done a nanobackup on a micro SD of your KitKat?
If you can't put the rom on a microSD Card (but i really advise you to do) or your PC wont see your phone on TWRP to copy the ROM there...
There is ADB Push
http://www.themobimag.com/install-rom-using-adb/
Good idea to use a microSD, don't know why I didn't think of that. I re-flashed from the SD and now everything works! Thanks so much for your help, really appreciate it!
magnoidgoat said:
Good idea to use a microSD, don't know why I didn't think of that. I re-flashed from the SD and now everything works! Thanks so much for your help, really appreciate it!
Click to expand...
Click to collapse
No problem m8, hope you enjoy the device
On an unrelated note: the one thing I love about my old phone is the stock music app. Is it possible to port it onto this one? I got the APK but when I try to install it it just says "Application not installed". Does this mean it's not possible to use it?
Pupet_Master said:
Hello welcome, i think you will like this device.
First off, what exact version is it? the XT1039, XT1040?
Anyway. To flash a custom ROM you will need to:
Go to TWRP. Select Wipe and then Advanced wipe.
Then you check:
Dalvik Cache
Cache
Data
System
Internal Storage
Usually afrer come from Stock KK to any CM12 based or AOSP ROM from android 5.x you will need to wipe Internal Storage, something that factory Reset just wont do.
Then you will flash/install
Your Prefered ROM (Paranoid Android is great, BlissPop as well. I'm using Euphoria, another great ROM)
Flash the GAAPs (preferable the one who the dev of the ROM you have chosen say to)
And done. Reboot your device.
Click to expand...
Click to collapse
Sence 7.0 ROM not working on Desire 820 Dual Sim
I followed one post on Dev ROM on this forum.
I tried installing the Sence 7.0 ROM on HTC Desire 820 Dual Sim and it installed without any problems but at the end when it asks for Reboot, phone restarted and got stuck in Bootloop.
Could you please help me resolve this problem?
You help will be really appreciated.
magnoidgoat said:
On an unrelated note: the one thing I love about my old phone is the stock music app. Is it possible to port it onto this one? I got the APK but when I try to install it it just says "Application not installed". Does this mean it's not possible to use it?
Click to expand...
Click to collapse
Prob it is not possible, you can try to make a titaniumbackup with said app, of this app and restore the backup on the new phone
---------- Post added at 04:56 ---------- Previous post was at 04:55 ----------
martin_kry said:
Sence 7.0 ROM not working on Desire 820 Dual Sim
I followed one post on Dev ROM on this forum.
I tried installing the Sence 7.0 ROM on HTC Desire 820 Dual Sim and it installed without any problems but at the end when it asks for Reboot, phone restarted and got stuck in Bootloop.
Could you please help me resolve this problem?
You help will be really appreciated.
Click to expand...
Click to collapse
This is not the HTC desire forum section, so i can't. Sorry
After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.
Dush4711 said:
After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.
Click to expand...
Click to collapse
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.
ethicalhacker365 said:
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.
Click to expand...
Click to collapse
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.
Dush4711 said:
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.
Click to expand...
Click to collapse
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.
ethicalhacker365 said:
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.
Click to expand...
Click to collapse
Thanks
Will try after 2 days as I am currently out of town.
Reply you later
Please don't mind.
U are not doing it correctly.
Goto-twrp-wipedata-advanced-check(dalvik/art,Data & Internal Storage) dont check system.
After it Flash with any Custom Rom
Then Wipe-dalvik/art,Data & Internal Storage) uncheck system
Flash Gapps
Again Wipe-dalvik/art,data & internal storage)
Reboot to System
Wait Aleast (10-15)-For me After Flashing 6.0.1 Cyanogenmod from Official Website.
Finish(You have no problem of bootloop)
Hits thanks if you solve this way.
None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.
dh.y said:
None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.
Click to expand...
Click to collapse
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....
ankitdhimancr said:
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....
Click to expand...
Click to collapse
Yap it boots but problem is battery discharged within 1 hour
Yeah..phantom kernel will work but on other hand this kernel eats up battery and take to much time on charging usually 3-4 hours
Try censium kernel
Everytime I try and use Google Maps either flashed with gapps/bean or installed later from play store all reboot my phone. Stock does not have any issue.
Tried:
ASOP-CAF
ASOP-EX
MOTOPURE
Lineage
TESLA
I just wonder why if the stock maps app works on 6.0 why not on 7.0?? The only thing I can think of is the GPS.
Any tips or suggestions?
Thanks!
Tried nano, pico and full for ARM and Android 7
open_gapps-arm-7.1-full-20170523
open_gapps-arm-7.1-nano-20170511
open_gapps-arm-7.1-pico-20170513
also BeansGapps-Full-7.1.x-20170509 BeansGapps-Mini-7.1.x-20170509
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
grantdb said:
Ok I have found that other maps reboot the phone too. Tried a GPS test app from play store and soon as I allowed it to access my location it rebooted. So it seems to be definately a GPS issue.
Click to expand...
Click to collapse
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
acejavelin said:
Return to stock by fastboot the lastest images available, flashing everything including the wipes (of course, skip gpt.bin and bootloader.bin if necessary), then take the lastest OTA's, verify operation of GPS... After that install TWRP, backup everything, and flash a ROM and Gapps, do not restore anything and test again.
I can't see how GPS would work with stock and not with ANY custom ROM...
Click to expand...
Click to collapse
Thanks for helping me, do you mean bootloader.img?
Ok done reflash stock, OTA's and checked gps is fine now backing up... going to use the PureNexus rom or ASOP-CAF
ARRRRRGGGGG Same damn issue... Maps crashes the phone.... so frustrating I am going to give up soon and stick with stock.
Going to try an get a logfile maybe someone can take a look at it
Thanks
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
grantdb said:
ok after phone crashed the first time I rebooted a couple times and its working!!!!!!!!
Thanks to @acejavelin and @Vikas Tewatia for trying to help me with this issue.
I think one of the problems was the way I was wiping after stock to install a custom ROM, instead of just standard TWRP wipe I was using individual selections?
Anyways I am going to further test and then report back. I will close this thread once I am sure everything is working.
Thanks
Click to expand...
Click to collapse
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
grantdb said:
I started a bug report (interactive) when I tried to use the maps again but thats when it started working properly. lol
If you know of a way to get logs from the first crash off my phone I would be more than happy to send it to you.
I did a twrp standard wipe this time rather than each partition under advanced wipe, I didn't install anything other than a ROM and either gapps or bean depending on the ROM creators suggestion and that's it!
Click to expand...
Click to collapse
You can use ADB to get real-time logging of the crash on your PC... Use Google to find the command.
acejavelin said:
The recommended way to wipe before installing a ROM is to manually wipe system, data, caches, and internal storage (kind of optional, make sure to move TWRP backups and other info to SD card first), then flash ROM and Gapps. Some people say flash ROM, boot, then shutdown and flash Gapps, but I have never had to do that.
I would be curious to see a logcat of the crash... this is not normal. Are you installing ANYTHING else besides the ROM and Gapps at this point?
Click to expand...
Click to collapse
Sent you logcat via pm thanks again!
Well I started getting random reboots in Pure Nexus ROM and so tried LOS and right away I had the reboot from Maps. I give up, staying with stock.
Thanks
Seems like one of my problems could be ASOP-CAF ROM as the version I was flashing uses a custom Kernel that has known issues with 7.1.2 and causes bootloops and crashes. The UltraDev kernel changes some things in the modem and could be why any roms I tried after flashing ASOP-CAF would not change the modem and were 7.1.2 based.
Anyways...
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
grantdb said:
Well I think I have tried almost every 7.x ROM I can find and every single one has a problem with any gps app on my phone.
Click to expand...
Click to collapse
Check out this bug report. It might be your APNs... https://jira.lineageos.org/browse/BUGBASH-248
By messing with my APN settings as per above bug report I can use maps and have no more random reboots. Woop woop