Database Users

Too many issues so few roms

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?

[Q&A] [ROM][Official] CyanogenMod 11

Q&A for [ROM][Official] CyanogenMod 11
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

i have lag on multitasking for this rom anyone have lag same as me ? can i fix that ?
sorry for my bad english

Unable to flash CM11 onto Moto XT905 (moto_msm8960_jbbl)
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice

timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
Does your XT905 have official KitKat? If not, please fall back to moto_msm8960_jbbl and use a different recovery (made for JB BL).
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

timhowes said:
Hi all
Frustration... I've spent all day trying to get my Moto XT905 to run the CM11 builds which I'm told will work on it.. Followed the instructions on the "Install_CM_for_moto_msm8960" wiki using the ADB sideload method and had also tried flashing direct from recovery. Tried with CWM and TWRP but no success. Wiped system and data before each attempt.
The final error message from CWM read as follows:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset. E:Error in /tmp/update.zip
(Status 7)
Installation aborted"
Can anybody point me in the direction of where I'm going wrong? Desperate to get off stock as my battery performance is miserable
Thanks in advance, very grateful of any advice
Click to expand...
Click to collapse
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.

I have installed the 11-20141008-SNAPSHOT-M11-moto_msm8960_jbbl after doing a rsd lite flash of VRZ_XT907_9.8.1Q-94-1_CFC.xml with the downgrade script provided in another topic. I have noticed that the WiFi has had severe bandwidth issues regardless of whether bluetooth is enabled etc. Optimization is off and i also tried setting the frequency to 2.4GHz only.
I have done multiple clean reflashes incase it was an underlying bootloader bug but I haven't had any luck. Any help would be greatly appreciated.

kabaldan said:
The error message is quite clear. When installing ROM (e.g. CM11) signed with keys different from what is currently running on your device (stock Motorola firmware), you have to wipe data / factory reset.
Click to expand...
Click to collapse
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.

timhowes said:
Thanks for this kabaldan. However on every attempt I wiped system, data, cache and did factory reset (data & cache I believe) before flashing CM11 and got the same error message. Do you know why this would be? In each case, recovery said the wipe had been successful.
Click to expand...
Click to collapse
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
See what I said and check if that's the reason. I'm not so sure because I don't own a XT905.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?

timhowes said:
Thanks. Apologies but I am still a little confused... I don't have official KitKat. My system version is 98.21.7.XT905.Retail.en.AU.
I'm not sure what you mean by "fall back" to moto_msm8960_jbbl - I thought these were the CM11 ROM images I can't install. And how do I know if my recovery is for JB bootloader? I have a JB bootloader and have successfully flashed versions of TWRP (currently v2.3.2.3) and CWM. Would these even flash if they weren't compatible with my bootloader?
Click to expand...
Click to collapse
You're now on JB BL and *should* flash moto_msm8960_jbbl instead of moto_msm8960, as the latter is KK BL-only.
Dhacker29's site used to have a copy of TWRP 2.7.0.0 for JB BL, but seems like the site is down, so I uploaded a copy: http://d-h.st/MSe , grab this and use it to flash CM11 JB BL mentioned above.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

Hi, so my wife's Razr M is on the official Kit Kat Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?

bofis said:
Hi, so my wife's Razr M is on the official Jelly Bean Bootloader, and I even did a factory reset and fresh install of the M11 build. Everything seems okay, and stable, but WiFi and Bluetooth refuse to turn on. I'll tap the "on" switch, and it'll say the radio is turning on, and then after a few seconds, returns to the off position. Is this known or common on this ROM, because I swear Bluetooth used to work.
I can try to see if I can pull a logcat or something if this is not common or understood yet, this this the right forum for this now?
Click to expand...
Click to collapse
Did you turn on your Wifi, bluetooth, etc... before installing CM? I didn't have any issue on the test phone at work with the JB BL after installing the latest CM build. Kit Kat on the other hand... well that's why my main phone is on the stock rom until they can fix that issue.

Okay, I take it back, she's on the Kit Kat bootloader, and running CM11 now. I did a full wipe and installed the M11 build, which I believe only works under the Kit Kat Bootloader now. As I wiped, it should not matter how I had set WiFi or Bluetooth before. So my question is, under the KK Bootloader, does WiFi or Bluetooth work for anyone? Because they do not turn on for me.

I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?

TwoBuells said:
I've been running CM11 for a long time.
took the 10/25 update Whisper Push, Hangouts and Goggle Play services, I'm getting "Unfortunately, Hangouts has stopped" error msgs
same with the 10/26 update, what's up?
Click to expand...
Click to collapse
I too have been having issues with the latest nightlies. I set an alarm from the Clock app and it will skip the first couple alarms I set, then notify me an hour later that I missed my alarms. Also I am constantly getting errors that systemui.process has stopped whenever I try to turn off an alarm and during normal operation. Other things such as random reboots, and web pages not loading, which makes me refresh the page for it to actually load.
I think I'll revert back to around 10/16 because that was when I was having problems at all.

I restored a good running backup from 9/26 and everything is running great.
the 10/27 update was posted, I updated to the 10/27 nightly and seems to be ok so far.

Wifi, Bluetooth, Microphone
Hi,
I have had the following issues with multiple versions of CyanogenMod on the KK bootloader (unlocked).
Wifi only works on 5 GHz
Bluetooth does not connect to any device
Microphone only works when I am on speaker phone
Ear speaker is not very loud
Have to press the power button 2 or 3 times before my phone turns on
Is there something missing from my phone? I know some people have had issues with wifi and bluetooth. I could not find a fix that worked; unless I missed something. I'm going to try installing a stock rom now to see if it works. I don't know what else to do.
If anyone has any fixes or ideas, I would really appreciate it. Thank you.
*EDIT*
No luck with stock. Same issues with wifi and bluetooth
Microphone works

Razr M Telstra xt905 dimmed screen CM11 Snapshot M11
Quote:
Originally Posted by Rufus
... and add this to my build.prob and it seems to fix the 'sleep of death' - JBBL:
ro.mot.ds.fastdormancy.disable=true
Works for me for months on end like that, have to edit after each flash tho.
Although it has only been a few minutes since I rebooted. Not only has the above setting appeared to have stopped the 'sleep of death' (which I took as where the phone takes a number of attempts to wake it up), but it also appears to have fixed the issue with the screen coming back on, overly dimmed!
Of course, now that I have written this, it will all start to behave as it did before, but here's hopping it continues like this."
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers

inter111 said:
I have just flashed CM11 snapshot M11 JBBL on my Australian Telstra XT905 Razr M. It's all working well so far except for two issues. The first is listed above where the phone screen will sometimes come on dimmed. How do I enter the above into build.prob to fix this issue. (I'm an amateur)? Is it through the terminal window? Detailed instructions would be great please.
The other thing I've noticed is the battery seems to be draining faster then the Telstra stock 4.1.2 rom. Any feedback would be appreciated especially from Australian Telstra users.
Cheers
Click to expand...
Click to collapse
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]

AndyYan said:
I've tried adding that line to my CM11 Nightly build already, no effect, screen still dimmed after a quick wake in dark places. You can try anyway, but BACK UP BEFORE YOU PROCEED!
Since you don't look like you're familiar with doing this, I think using Root Explorer's inbuilt editor should be a bit easier. Go to /system and find build.prop. Long press and open it in a new window. At the bottom of the file, press enter for a new line and enter the above. Save and reboot.
Stock usually have better battery life than custom ROMs, that's normal.
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Thanks for the reply. I had the same result as you. The screen is still dimmed after waking sometimes. I guess I'll just have to put up with it.

I've somehow done something obscure with my phone (Error Code 7) partition problem?

Hi Folks,
I've been lurking and getting great advice form this forum for many years but have finally come up with something I can't fix myself.
I was running a few custom roms but somehow when trying out a few of them I have managed to do something so that I can't flash any custom roms any more.
TWRP which gives an error 7 message (which seems to suggest that my phone no longer thinks it is a moto x play). At present I can install stock roms using ADB but that seems to be about it. I have tried to roll back using a stock rom from the motorola website (LUX_RETLA_DS_LPD23.118-6.1_cid12_lux_retla_ds) but that didn't fix it.
I also can't seem to root my current stock rom (XT1562_LUX_RETEU_6.0.1_MPD24.107-52) but am sure I was able to before i had this problem.
I can't help but think I probably should be grateful that whatever i did didn't brick my phone but I've been trying every idea I can find that over the last few months and nothing has helped. I get the idea it might be some kind of low level partition issue but that is just a desperate hunch. From time to time I've got what seem to be partition errors when try various roms to fix this but they've usually worked their way out.
Any hints or suggestions on how to rectify this would be most welcome.
N

Help - With every room I get stuck on setup at "just a sec..."

Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!

tompere96 said:
Hi everybody. Today I flashed ops beta6 coming from Resurrection remix. Since I've tried, I couldn't get past the screen on Google setup saying "just a sec.." . Seems like I'm the only one having this problem, cause I can't find any similar post/thread.
Please help me!
Click to expand...
Click to collapse
Hello, why not posting your question in the related thread https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 and search for answers?
You did not mention which steps you take, sounds for me you coming from ressurection remix and just flash the ob6 rom without wiping etc? But I'm sure you did not, so please give exact steps to reproduce the issue.
And read some pages back in the linked pages thread, it's been discussed partially

why not posting your question in the related thread https://forum.xda-developers.com/one...-oreo-t3710003 and search for answers?
Click to expand...
Click to collapse
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.

tompere96 said:
Hi, I didn't post on the rom's thread because now it's a "every rom i try" problem. It happends every time i clean flash a new rom (I've tried xXx, OOS stock beta 6, OOS stock stable and crDroid), and I've never got past the langage selection screen.
My steps are:
- Boot to Recovery, currently twrp clockworkx 3.2.1
- Wipe: Data, Dalvik & ART cache, Cache and System
- Install Rom
- Install Gapps (if needed)
- Install magisk (I've tried not to, nothing changes)
- Reboot
I'm really confused, a problem behaveing like this, seems related to the phone it self rather than to the single roms.
What would you suggest?
OT. If you find that this post it's not getting anywhere, I might follow your advice and post on OOS beta thread.
Click to expand...
Click to collapse
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.

tompere96 said:
I solved my problem formatting the whole phone from twrp. I'm still confused on what caused this problem. Thanks anyway.
Click to expand...
Click to collapse
You got it. It's mostly cause of the internal storage you did not format. That's a common problem.

Stuck with 'Just a sec' after Factory reset
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.

Facing same problem
lakshmla said:
Hi All,
I have an One Plus 5 phone. I am getting it exchanged for One plus 6T. The delivery is scheduled today. I did a factory reset and when I reboot - I got stuck with this 'Just a sec' screen after language. It doesn't get past this. I tried ' Recovery boot' and 'Fast boot' Nothing is working. I searched all over internet. I can get the calls but cannot do any other thing. I am stuck with this ' just a sec ' screen for a like one hour now. Please please please help me out.
Click to expand...
Click to collapse
i had this same issue solved by flashing nano or pico gapps
try this
Facing same problem with my htc 10 (pme)

Bootloop and radio issues

Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance

motoplayguy said:
Hey there,
Ever since flashing a new rom I've been experiencing a few issues. First, my phone refuses to boot to system, I've had to go through the bootloader to get it started every time.
Second it would appear that my radio is off as the phone won't connect to the network and thinks its in aeroplane mode. I haven't been able to get it working yet.
The Rom I flashed was the nougat update. , I've tried several others since as well as restoring through twrp. No dice, but I'm currently on lineage 15,1
I've yet to find a solution to either of these issues in a week of searching so I'm looking for any sort of guidance.
Thanks in advance
Click to expand...
Click to collapse
You should return to a pure stock configuration (including recovery) and start over, preferably using RDS Lite. It won't be easy as there are no giudes written explicitly for the G4P. You will have to derive the procedure by reviewing other threads.
A less comprehensive approach is detailed in the following thread but it may not solve your radio issue.
https://forum.xda-developers.com/g4-play/how-to/guide-return-to-stock-firmware-recovery-t3551797
As for not booting to system that's likely due to a procedural error when twrp was first flashed. Check the TWRP threads for corrective action.