No Mobile Signal After Flashing 6.0.1 - OnePlus 2 Q&A, Help & Troubleshooting

I've just tried to flash marshmallow but it didn't go so well, I had no service and the home button wouldn't work. After reverting I can't get any service anywhere, just emergency calls only / no service. When searching for networks 3 UK comes up but won't let me connect. It says 4G but I know it's 3G+. Any help greatly appreciated!

6.0.1 is only available as Custom OS at this time, best direct this question at the page where you found your Custom OS.

Start twrp connect to your pc.
Make sure you see your phone in Explorer.
Do a full whipe. (this will erase everything be aware)
Then copy a build of grarak or Seraph08 and copy gapps to your phone.
Or off course copy a full Ota of oos
Installed this many times and it never goes wrong.
If you flash a rom always read the topic if a modem flash is needed.
With grarak or Seraph08 this is included for CM.
Verstuurd vanaf mijn ONE A2003 met Tapatalk

Related

No cellular network after installing CM12.1 on Straight Talk SM-G900F (klte)

I recently installed TWRP and then the latest snapshot of CM12.1 for my phone described in title. The android version was upgraded from KitKat (4.4 I believe) to 5.1.1. Everything works fine with the install except I have no network whatsoever. Can't text, can't call, can't use data etc. I made a post on the CM subreddit but didnt get a lot of help (can't post link) . Here is what I have tried: changing APN settings (which I have heard should at least let me call and text if incorrect); flashing various modems such as BOE3, BNL9, and BOD3 (all of them get a FAIL! (auth) in ODIN); restoring my KitKat backup (makes the phone unusable); trying to flash the default L rom for the phone (Also fail to flash in ODIN and TWRP). So at the current time I am basically stuck on CM12.1 and all of its amazingness with no phone functions, I basically have a small tablet at the moment lol.
Here is some information from the about of my phone, if it is helpful at all.
Model: SM-G900F
CM Version: 12.1-20151204-NIGHTLY-ktle (Installed the nightly after the snapshot didn't work, same problem persists)
Android version: 5.1.1
Baseband version: S902LUDU3AOG2
Carrier: Straight Talk
If any more info is needed, just let me know. I appreciate any help, as I am pretty much at square one still. I have googled for days to try to fix this, and haven't come up with anything. It seems no one has had this specific problem before.
If I can't fix this issue, is there any way I can downgrade back to what I had to begin with?
y tried with another sim card !!!
ty *#06# to verify imei
popmpopm said:
y tried with another sim card !!!
ty *#06# to verify imei
Click to expand...
Click to collapse
I only have one other sim card on me, and its through verizon. It didn't work on the phone either. I would definitely just buy a new sim card if that would mean it would work. The whole IMEI thing worked, but I am not sure what to do with that information.
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
*Detection* said:
(Definitely a G900F? Check what it says in download mode)
Checking the IMEI was to make sure you haven't wiped/corrupted the EFS partition, which contains the Radios needed to make and receive called, along with the IMEI (Hopefully you researched enough to back that up before messing with the phone)
Try flashing another stock ROM with ODIN 3.10.7, go for a different Lollipop ROM from sammobile. com
Some stock ROMs fail to flash, some work, (Phone dependant it seems)
Then boot into recovery and factory reset > try to boot
Click to expand...
Click to collapse
I have tried 2 separate L roms for the G900F. It says in download mode the phone is a SM-S902L and I read somewhere to get the true model of the phone you look at the FCC id under the battery. Well the FCC id says it is a G900V. at one point in trying to fix it, I tried a stock L rom for the G900V and TWRP told me that it was intended for a kltevzw device and that mine is a klte, so that is why I assume that it is in fact a G900F. I have been using ODIN 3.10.7 to flash everything as well. (Have't tried TWRP for the most recent tries since it takes longer to setup and I doubt it would work but it's worth a try I suppose.
I looked on Sam Mobile for the SM-S902L and there is only one firmware for it, which is 4.4.2, the same one it was installed with when I got it. From my understanding SM-902L is the straight talk branding of the G900V, and trying to flash that firmware didn't work either. Every time I try to flash something it terminates with a FAIL! (auth). What I also understand is that Straight Talk has not released an official version of L for the phone. So it seems my options now are to somehow get the modem to work right in CM12, try to somehow downgrade to 4.4.2, or wait for Straight Talk to release an update for my phone which is not really an option. I just got this phone and I really don't want to have to buy a whole new one just because of software problems. In my mind there HAS to be some way to fix this.
EDIT: my bad, I should have mentioned when I tried to flash the G900V rom it was also CM12, not a stock.
EDIT AGAIN: I seem to have fixed this problem. I have no idea how I did it, but I finally got it to restore to the stock 4.4.2 rom. I seriously have no clue how it worked but it did. Texting and data once again work, but i am now having a problem where I can't make or receive calls. Call immediately ends/goes straight to voicemail. I don't suppose you know anything about that, if you do that would be awesome. I'm gonna call ST in the morning and see if they can tell me anything from their end. But otherwise, I guess my problem is solved. Lol.
I know it sounds simple or may sound stupid but have you tried entering your APN? I have to do that with most of the custom Roms I flash or I won't have service. Also, make sure the correct modem is flashed and up to date.

Need Instructions to avoid almost bricking again

Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
CritKlepka said:
Hi guys. I very narrowly (somehow) managed to recover from almost bricking my phone.
I successfully S-Off'd my phone, and previously successfully installed TWRP. I tried to install this ROM:
https://forum.xda-developers.com/ve...m-perfumewl-m60-dev-edition-unlocked-t3442969
When I tried the to flash the ZIP for firmware and for the ROM, the firmware wouldn't install. I tried some other stuff and basically almost bricked my phone. Some how got it to suddenly start being able to use the htc_fastboot commands (????????) and was able to start installing the zip for stock... but it ran an error, I ran it again and it froze... then I forced my phone to reboot and somehow I'm back to having a stock system. No clue what I did.
My question is, can I take a software update on my phone normally (to 7.0) , and then install just that ROM? Or so I need to flash the firmware separately with a command line command? I just don't want to give myself another heart attack tonight. Current firmware version is 1.82.605.6, not rooted, don't believe my recovery is TWRP right now (but I know how to install that one).
I'm just looking for root access and the ability to remove pre-installed Verizon crap (VZW Messager, My Verizon, etc). Thanks guys.
Click to expand...
Click to collapse
I recommend you install this one instead:
https://forum.xda-developers.com/ve...m-1-85-605-9-aroma-root-root-debloat-t3529732
Follow instructions in OP...or:
1)fastboot flash FW w/o Boot w/ TWRP (htc_fastboot oem rebootRUU, fastboot flash zip...)
2)htc_fastboot reboot-bootloader
3) Finally, go into recovery-- backup and flash ROM (choose root w/ Magisk and debloat)
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
CritKlepka said:
Thanks, I figured out why it wasn't working before. Used official TWRP, thats why it wasn't working. Wouldn't have thought that'd made that much of a difference.
New problem though; something I really would like to use the Google versions of contacts and dialers. Trying to flash those just made my phone app unusable. So I turned to LineageOS but it REFUSES to boot. Hangs on their little vertical line with a moving circle. Found out AOSP roms don't like VZW firmware? Flashed global firmware, updated through WiFi as much as possible, and then ran into issues with radio, even though I flashed the VZW one. So I reverted those changes, am going through with what you said above to have a working phone (after not having one all day), but any advice on getting Google dialer and contacts? I'd like to use LineageOS but I couldn't get it work at all.
Click to expand...
Click to collapse
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Antny6 said:
You've got to read OPs, search threads, etc. Some ROMs work w/ our phone, and some do not. Check out the latest versions of ice and leedroid. Your most likely want to grab the SVN versions is the official versions may not yet support Verizon N firmware
Click to expand...
Click to collapse
I have been doing a lot of searching, but I've found so many different, conflicting sources of information. For example, one website told me to install LineageOS, was to be on latest Verizon OTA and just normally flash it; that obviously didn't work.
So from what I can see, our choices are Viper, Ice, LeeDroid, NuSense and the one you linked. I'm going to try out LeeDroid... out of curiousity, is there any reason, for example, LeeDroid or Ice haven't posted in this Verizon section with links to their ROMs?
*Edit Two* Dialer wouldn't work out of the "box" so to speak, so I had to go to Phone settings at the bottom, there is a menu called Calling Accounts. Had to go there and tap Receive Incoming Calls... why is that disabled in the first place..? But that seems to be an issue going even as far back as the Nexus 5. But that's how you find the option in the HTC 10 for anyone who comes across this issue too...
Not sure why your having issues with the flashing. Are you doing a full wipe? Not just factory reset. Going from stock to lineage requires a complete format of internal SD card. On the stock roms, most will ask if you are still on marshmallow firmware & are working fine. Again, we need more info on what firmware version your on, version of twrp& how your wiping your device. Most AOSP roms work, but no advanced calling
LOS ROMs will work without issue IF you have flashed the US unlocked firmware at some point in time. This is the only information that we have found from a VzW device with LOS booting and VzW device without. We started a thread awhile ago and is the only known method we currently know of to get LOS booting. Also works for Sprint users.
https://forum.xda-developers.com/verizon-htc-10/how-to/how-to-cm-booting-vzw-vzw-firmware-t3500900

Galaxy s7 edge exynos wont flash stock files HALP

Im using a Galaxy s7 edge exynos and I have been trying ALL day to return to stock firmware. (was aiming for 6.0, but when that didnt work I started trying 7.0 with slightly more success...) I was previously rooted via magisk using TWRP. I am not able to flash all 4 files at once via odin, (BL, AP, CP, CSC) I quickly get an error on both the device and odin (decive says binary 2 device something... Odin stops at either Param.bin or cm.bin depending on which CSC I use) the BL file seems to be the one that refuses to flash (from any of the 4 versions of odin i have and using different firmware versions that previously worked on the phone)
I am able to flash just the AP, CP, and CSC but when android loads up my mobile data doesnt work and many other things dont work correctly as well ...
I am so confused as to what I can even possibly do now. Im sitting here with a phone that wont correctly software update that I cant correctly root and has no mobile data. No full 4 files will correctly flash without odin error. TWRP gives me crap now too. I have wiped and formatted all the data many times hoping id missed something.
Send help
also
I try to manually update and it says "registering device" for a sec and then "Process failed" Like android 7.0 is running but not how it was before. I did update to newest update via the phone before i decided to try to revert to android 6.0 again because I was having issues connecting my pokemon go+
Hmmmm I still have problems with 5ghz and mobile data but i got magisk to install... luckily im not using this for phone purposes. this is the best i can do without help
What is yohr phone model ?
G935f
G935f
Currently running g935fd
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
riseofsand said:
Did you flash and Oreo rom by anychance?
"Maybe", i say maybe if you did thats why you cant go back to a < 8.0 version
Click to expand...
Click to collapse
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
I'd still like to try to get my 5ghz and cell signal (just in case something happens to my main phone) but I'm scared to soft brick my phone for the 1000th time in 2 days when I managed to get it semi working.
CactuarKing said:
I didn't try anything with oreo until like 10 hours of failing everything and reading everything I could find. It was unofficial and apps wouldn't install or update correctly. So actually what I got to semi work was 7.0 again. Build G935FXXU1DPLT. It doesn't show cell tower signal or work with 5ghz anymore but I got magisk installed and I can run apps off of wifi. (Same as before 8.0 but got magisk working this time)
Click to expand...
Click to collapse
Last time something like that happend to me, is because i was flashing the wrong stock rom (same model but wrong original carrier) sometimes it does matter, sometimes not
I was worried I might have messed it up for good as well luckily I'm not completely stuck but I still dont understand why I couldnt just 100% flash my OS via odin like I always do. Although I got cocky and started without following instructions up on the computer this time. Just my luck
double check mod #it can change with different roms my s5 tmobile g900t originally now its grown into g935f S7 edge

Converting n910p to n910f - need help

Hello,
I have a problem converting samsung note 4 n910p to n910f. At the beginning I dowloaded TWRP and flash it by Odin. I made a backup of everything then downloaded the rom for samsung galaxy n910f Pixel Experience. When installing rom I get a message "ERROR 7". It occurs when installing each custom os example: ViperOS, HAVOCOS rom. All the time there is the same problem. On the xda forum I found a user manual how to flash the baseband firmware. I flashed OK1 - nothing has changed then PE2 - the same, "error 7" is still there. I also tried the Trex888 user manual to install T-mobile OS + ramkernel + datafix and the phone stops while loading - bootloop and the teelphone temperature is rising that I cant touch it when I leave it on the bootloop.
Do you have any verified way to install custom rom to n910p? It's hard to find a clear instruction on what to change to flash a custom rom on n910p
I restore backup and have a bootloop on the sprint logo
I ll try to instal Dr Keaton rom with H-vitaminkernel, maybe this ll help...
see
https://forum.xda-developers.com/showpost.php?p=68967827&postcount=2
and subsequent posts in that thread
I will check the method described in this post again, but I did it before :crying:. All new roms with android 9 like for example havocOS have written that they also work with trtlespr. This is written in the information when installing the rom in twrp. So why does error 7 pop up for?
I did the first method by installing the PE1 baseband from this topic:
https://forum.xda-developers.com/note-4-sprint/development/basebandsbootloaders-ok1-pc1-pb5-t3358357
Then, according to the instructions, I installed the system, krnel and datafix.
"Try this rom this will work flash rom and dartafix and kernel all together
Download rom
https://www.androidfilehost.com/?fid=385035244224381907
Download data fix
https://mega.nz/#!qcdnySyB!55DemVnZN...a0u4_V60fn5mKo
Download kernel
https://www.androidfilehost.com/?w=files&flid=117985 "
The system doesn't start, it stays on SAMSUNG screen and gets bootloop. The phone heats up very strongly within a few minutes, it is possible that even the processor temperature is higher than 80 * C.
By installing firmware and baseband PE1 from the above link in Odin shows that everything is ok ( success). But can it be that, despite everything, the baseband did not get in, therefore it does not accept this rom or any other?
The same example, when after flashing TWRP by Odin, if we do not disconnect the battery, TWRP will not install. Is this possible with baseband and frimware for PE1?
Ok, I tried everything that was in the post you linked. I flash my phone to PE1 firmware, then install dedicated rom, datafix, kernel from links and phone stuck on samsung loading logo. This situation i s always when i try any rom. When I do a restore backup phone stuck on Sprint logo...
Can anyone help with this?
Has anyone ever installed a customrom with android 9 on n910p?
I have sm-n910f as a backup and I can do anything on it.
Are these n910ps somehow handicapped?
n910p that I ave is in very good visual condition, without scratches. If I can't do anything with flashing new rom on n910p phone, can I buy a motherboard from n910f or n910c and install it inside instead of n910p board?
MN1352K0 said:
I have sm-n910f as a backup and I can do anything on it.
Are these n910ps somehow handicapped?
n910p that I ave is in very good visual condition, without scratches. If I can't do anything with flashing new rom on n910p phone, can I buy a motherboard from n910f or n910c and install it inside instead of n910p board?
Click to expand...
Click to collapse
Yes, but it must have the cameras included.
The Restless Soul said:
Yes, but it must have the cameras included.
Click to expand...
Click to collapse
Thanks, for the reply. maybe I ll try to once again install the customrom before I order the board form China :cyclops:
Can someone explain me how to install example HavocOS ( android 9 ) on n910p? This is possible because when I install it in TWRP there is information about compatible version of phones and there is "trtlespr". So it must be possible to install HavocOS on n910p
Why I need to change the rom in this phone? I live i Europe so Sprint stock rom dont want to connect with my Red Bull Mobile or T-mobile operators...
Ok, I install Dtux Rom on Standard PK1 Sprint rom. Working, but I hv problem with T-mobile network. Everything is working on the GSM module but without internet. When I go to settings and then network -> change to CDMA or LTE I hv information "Searching for service" and no signal. So how to activate mobile data - internet connection on this rom? I know thath LTE is not working in EU with Sprint N4 but even CDMA is not working

Wifi is unusable

My new OP8Pro is not connecting to ANY wifi networks.
And if it manages to connect it drops connection after 15 seconds.
I'm on OOS 10.5.13 and only using magisk.
What variant do you have?? US? EU? Global? Chinese?
Not sure if safe mode allows WiFi but boot to safe mode and see if the same issue occurs.
If a family member has a mobile, create a hotspot then connect to that and see if it has the same issues.
If say update to 11 as it may be a software issue.
If updating is an issue as you have no WiFi, you may be able to download it from the internet on a pc then copy the firmware over.
Have you tried a factory wipe?
Does removing the magisk modules help?
When you rooted did you extract the boot.img from your own firmware or did you obtain it from someone else, I'd always recommend obtaining your own.
Think there was someone who had issues in the xXx thread, might be worth searching threads to see what was the outcome.
I think they were on a US device, T-Mobile IIRC.

Categories

Resources