Hi every1
I got opo form swappa but since the day 1 I had a problem. This phone continuously lost signal for 2-8 sec. I tried everything from go back to stock flashing different ROMs and now I am on Android ice cold project 7.1 but nothing works for me.
Any help would greatly appreciated thank you so much.
Flash 44s modem. https://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
bablu048 said:
Flash 44s modem. https://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734
Click to expand...
Click to collapse
Thanks for the respond. Do I need to go back to stock (CM 13)? I'm currently running AICP 7.1
androidarmy said:
Thanks for the respond. Do I need to go back to stock (CM 13)? I'm currently running AICP 7.1
Click to expand...
Click to collapse
no, just flash the modem on any rom, should work. If not go back to CM.
Thanks I'll try these
Unfortunately none of them worked for me
Any other solution???
Related
Greetings, im using
GOOGLE EDITION 4.4.4 by Danvdh, Kryten2k35 & Ktoonsez
Previous version working fine, now after a fresh build.. my phone is locking up and rebooting every 5-10 minutes. Not sure if its a bad rom, or a bad installation and just needs to be redone again ?
Any ideas guys. ???
agentdangermouse said:
Greetings, im using
GOOGLE EDITION 4.4.4 by Danvdh, Kryten2k35 & Ktoonsez
Previous version working fine, now after a fresh build.. my phone is locking up and rebooting every 5-10 minutes. Not sure if its a bad rom, or a bad installation and just needs to be redone again ?
Any ideas guys. ???
Click to expand...
Click to collapse
I had the same problem with Samsung Galaxy S2 and SentinelROM. After flashing another rom (AOSP NeatRom) the problem was gone. So I think it's bad rom or bad installation. If reflash won't help, try another rom.
varespuuotsas said:
I had the same problem with Samsung Galaxy S2 and SentinelROM. After flashing another rom (AOSP NeatRom) the problem was gone. So I think it's bad rom or bad installation. If reflash won't help, try another rom.
Click to expand...
Click to collapse
I actually tried the latest PAC ROM 4.4.4 and i had massive issues also, i was getting some sort of ACORN errors on first boot up i couldnt even get to the desktop.
Lucky for me i had a nandroid backup of my 4.4.3 of my build i was using so im back to that and all good again.
I think ill wait for a couple weeks till a new build of my rom is out with some bug fixes.
Hey,
So I got my Oneplus One few days ago. It was running Cyanogenmod 11s front facing camera was working fine by then. Then i figured to switch to resurection remix did that, and when i tried to access the front facing camera the program just froze and crashed. Then I went for AK Kernel, still crashing, went for Paranoid Android now with default kernel still nothing, tried multiple camera programs, nothing seemed to solve this problem.
So does anyone know what's up ? Why it doesnt work ?
Any help is highly apreciated.
Sprint3er said:
Hey,
So I got my Oneplus One few days ago. It was running Cyanogenmod 11s front facing camera was working fine by then. Then i figured to switch to resurection remix did that, and when i tried to access the front facing camera the program just froze and crashed. Then I went for AK Kernel, still crashing, went for Paranoid Android now with default kernel still nothing, tried multiple camera programs, nothing seemed to solve this problem.
So does anyone know what's up ? Why it doesnt work ?
Any help is highly apreciated.
Click to expand...
Click to collapse
Try to factory reset
Sent from my Oneplus One using XDA Free mobile app
thedao said:
Try to factory reset
Sent from my Oneplus One using XDA Free mobile app
Click to expand...
Click to collapse
What ?
I mean i do it everytime i reinstall/install new rom.
I even installed Oxygen OS Same problem, nothing fixed i did it as cleanely as posible Formated every possible section i could. Anyone to help ?
bump
Did you updated also the firmware? Or just ROM?
Nah just the rom, dont know what you mean by firmware
I mean i installed the cm12.1 newest nightly first, then went for Resurection Remix and so on
And you left the firmware on cm11s? How did you manage to install 12.1? Did you read the installation instructions, cause every Rom I tried states update your firmware. You'll find a link to the latest one somewhere near the ROM download.
**** maybe i dont understand something what do you mean by firmware, can you explain more in depth ? Because i did everything that paranoid android tutorial shows and see nothing changed, I tried instaling a rom it came with it was cm 11s 44r still same stuff nothing changed.
Do you mean i should flash CM 12S first, then go for other roms ?
Edit : So newest 12.1 Nightlies dont have newest firmware itself ?
Sprint3er said:
Do you mean i should flash CM 12S first, then go for other roms ?
Edit : So newest 12.1 Nightlies dont have newest firmware itself ?
Click to expand...
Click to collapse
Firmware is included in the nightly
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure
Hello everyone this is a purely stock flashable official marshmallow ROM for the nexus 7 2013 Flo version! It is based on the stock latest official 6.0.1 RAZOR MOB30X build and image for our nexus 7 2013 edition with nothing modified or removed in the ROM. I was trying to look for something like this but could not find it so i decided to make it myself. This ROM is always compatible with multirom also! The ROM base is not mine it belongs to Google and ASUS those are the people who made the ROM and the device. Hopefully this ROM can benefit you in some way so i hope you enjoy
Link to official nexus firmware here:
https://developers.google.com/android/images
If someone could link me to the rom and kernel sources that would be great thanks
ROM Details:
Completely Stock
Unrooted
Unmodified
Pure Stock Official Latest 6.0.1 RAZOR MOB30X
Flashable through twrp or other recovery such as cwm or philz i hope
Of course you can flash latest supersu and xposed
Download build here: https://www.androidfilehost.com/?fid=818222786056029535
Please give thanks if you can
reserved
Thanks I was having issues with my Nexus randomly going to the lock screen and running slow. Hopefully this will resolve the issues. Try telling a toddler to swipe up while watching YouTube LOL
Thanks for this it could come in handy one day. I just downloaded its only a 149mb zip file is this correct?
Tmzdroid said:
Thanks for this it could come in handy one day. I just downloaded its only a 149mb zip file is this correct?
Click to expand...
Click to collapse
No it should be over 400 megabytes so your download is corrupt
rachelm920 said:
Thanks I was having issues with my Nexus randomly going to the lock screen and running slow. Hopefully this will resolve the issues. Try telling a toddler to swipe up while watching YouTube LOL
Click to expand...
Click to collapse
No problem I hope everything goes well for you
thanks. was looking for this. wanted to go back to stock but didn't want to lose twrp and have to redo everything if i want to try back custom roms.
can we get a re-upload? Doesn't seem to have a mirror for it anymore.
metalblaster said:
can we get a re-upload? Doesn't seem to have a mirror for it anymore.
Click to expand...
Click to collapse
just keep trying eventually you will get the download link to appear from quebec canada on androidfilehost See screenshot. I dont need to reupload it downloads fine for me
rachelm920 said:
Thanks I was having issues with my Nexus randomly going to the lock screen and running slow. Hopefully this will resolve the issues. Try telling a toddler to swipe up while watching YouTube LOL
Click to expand...
Click to collapse
No problem glad this worked out for ya
r.sorujlall said:
thanks. was looking for this. wanted to go back to stock but didn't want to lose twrp and have to redo everything if i want to try back custom roms.
Click to expand...
Click to collapse
Your welcome
I haven't messed around with rooting for about 2 or 3 years so forgive me if my question sounds noobish. My N7 is on Stock 5.1.1 rooted. with TWRP for Recovery. The USB port does not work so i cant run any fastboot commands to restore or flash any stock firmware. Would I been fine flashing this with TWRP since I'm coming from 5.1.1?
Hello JT1510365 ... I am a Nexus 7 noob, so please excuse my ignorance. Can you please tell me what flo/deb are when referring to ROMs? TIA
Edited because I jumped the gun and input the wrong information. i thought flo was the google codename for the device but it's now.
DarkMan_X said:
Edited because I jumped the gun and input the wrong information. i thought flo was the google codename for the device but it's now.
Click to expand...
Click to collapse
Thank you DarkMan_X ... coincidentally, I was just looking at the factory images page that you originally linked to & have since worked out that FLO refers to the WiFi Only model (razor) whereas DEB seems to refer to the LTE model (razorg). I'm still curious about where flo & deb come from though =)
mikaere66 said:
Hello JT1510365 ... I am a Nexus 7 noob, so please excuse my ignorance. Can you please tell me what flo/deb are when referring to ROMs? TIA
Click to expand...
Click to collapse
Based on this https://forum.xda-developers.com/showthread.php?t=2745189
It seems like FLO = the 2013 WiFi version and DEB = 2013 LTE Version
work your magic with deb
Hey,
Now that you are getting loads of practice doing various builds, is there any way you could please do a DEB version of this rom for me. I would love to have this available should i ever wish to go back to stock without having to go the official route meaning i can no longer flash other roms easily afterwards.
:fingers-crossed:
~C
i dont know whats the difference compared to stock MOB30X?
thx
amkaos said:
i dont know whats the difference compared to stock MOB30X?
thx
Click to expand...
Click to collapse
no differences its just a flashable unmodified rom if you wanted to go back to the stock rom but you didnt want to restore the rom using your computer instead you can just flash this rom and it will return your nexus 7 back to stock
JT1510365 said:
no differences its just a flashable unmodified rom if you wanted to go back to the stock rom but you didnt want to restore the rom using your computer instead you can just flash this rom and it will return your nexus 7 back to stock
Click to expand...
Click to collapse
oh ok...thats more betterer...thx
Hello. I have an issue that shows up on every ROM that is based on AOSP. Right now I'm on Lineage OS 16. When I'm calling to someone or if someone calling to me I can't hear the person on the second side. What can I do (expect flashing official ROM).
Thanks in advance.
I have happened like that before, what I did was reflash
seyrarms said:
I have happened like that before, what I did was reflash
Click to expand...
Click to collapse
Yeah I did it several times and decided to stay on stock..