I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
Did you try an older radio.img, some people use the boot.img from the previews. If You check the thread search from any Oreo thread you'll see you're not alone.
I believe if you flash boot.img from developer preview 4 can fix this issue.
Exodusche said:
I believe if you flash boot.img from developer preview 4 can fix this issue.
Click to expand...
Click to collapse
Where might one obtain this?
idbl_fanatic said:
I just fresh flashed stock 8.0.0 (OPR6.170623.019, Sep 2017) and I keep getting "No SIM" it started yesterday 2 times, and 4 times so far today, before this build I had 8.0.0 (OPR6.170623.013, Aug 2017 and started getting the same thing, then it wouldn't boot at all, so I full wiped and installed 8.0.0 (OPR6.170623.013, Aug 2017 again, which was updated to Sept build right after the first boot, the phone has been fine for about a week, now it's giving my the SIM error again GRRRRRR
Any ideas? While I was down before the full wipe I was using my old Nexus 5, and never got the error, so, to me that rules out a bad SIM
Click to expand...
Click to collapse
It might not be anything you did, when I installed the OTA for september and Oreo update I also got a no sim message a few times. Completely stock / unrooted phone. I restarted and it went away but popped up once since. This phone is brand new (just got it as a 6P replacement through a google store RMA) so I know my phone hasn't been messed with, I think they might have a bug in the build. You on projectFi by any chance?
Bounty44 said:
You on projectFi by any chance?
Click to expand...
Click to collapse
No, I am on AT&T
idbl_fanatic said:
No, I am on AT&T
Click to expand...
Click to collapse
Ah alright. Well I just wanted you to know you aren't alone at least lol. Hopefully the october update will include some fixes.
Related
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Chavezlaw93 said:
Purchased my Nexus 6P a couple of weeks ago from Project Fi and it is still stuck on MM 6.0.1 and Dec. 1, 2015 security patch. Google support says to just wail longer for ota to update but will not offer up any time frame for update to arrive before I should assume that update system is simply stuck. Thoughts on whether phone just stuck on MM or whether it will update shortly. Most concerned about 2015 security patch! Thanks.
Click to expand...
Click to collapse
I agree with @5.1. The fastest, least hassle-free way to get to 7.1.2 is to just flash the full April image. You could also try borrowing a SIM from somebody on a different network and popping that in. Let the phone start up and wait for their cellular network to be displayed in the notification bar. Then power down and put your SIM back in. Works, but you are liable to set yourself up for a series of updates. I would also recommend you leave your bootloader unlocked and USB debugging enabled.
5.1 said:
Hello,
I would just sideload latest 7.1.2 N2G47H OTA from Google here: https://developers.google.com/android/ota
There is an easy tutorial explaining the process. If you're not sure, let me know...
Otherwise you can wait till you have an update notification. Though there's no time frame as to when it will come to you.
Good luck...
Click to expand...
Click to collapse
Hi! New to the 6p (completely) but not to flashing/mods/etc. Can this be flashed with TWRP or only via ADB? Anything I should be aware of on an unlocked/rooted nexus w/ProjectFi? Assume I will have to re-root - is this correct?
Thanks!
Hi guys,
I have received an OTA update for android nougat. I was rooted and have xposed framework. So I have flashed stock firmware so that system status is changed to Official. I have received OTA updates after flashing till January 2017 security patch. After this update, even if i manually check for update, it just says "Your device's software is up to date".
Not able to get OTA for nougat when everyone else in India are receiving it. I received update for the same device when I had root and Xposed. Please help. Currently I'm on stock firmware without root & xposed.
Update:
Received the OTA update again. sharing the link here. Just extracted it from /data partition. Its unmodified.
Nougat OTA Link: https://drive.google.com/file/d/0B6DJKZBTXr7MNGlmUmtmLVJ4aUk/view?usp=sharing
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
May be we'll get it in a couple of days!
Sudarshan Q700S said:
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
Click to expand...
Click to collapse
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
swaggy123 said:
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
Click to expand...
Click to collapse
I have downloaded it once, but not able to find it in the cache partition. Then flashed stock firmware and no more update notification for Nougat. Even I'm wondering what really is happening.
Maybe Motorola might be pushing the update randomly. I see that many others are reporting the same issue at XDA. I hope we would get the update in a couple of days.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
Sure I'll tell you if i got it
Can you got update notification
Yes, I did get an update notification
nitingarje24 said:
Can you got update notification
Click to expand...
Click to collapse
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Lord of Hell said:
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Click to expand...
Click to collapse
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
when you got 7.1.1
[email protected] said:
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
Click to expand...
Click to collapse
These are the current stock ROM details.
Lord of Hell said:
These are the current stock ROM details.
Click to expand...
Click to collapse
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Tried it few days back, didn't work!
[email protected] said:
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
Click to expand...
Click to collapse
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
when you got nougat update please provide date if you remember
4th Oct
nitingarje24 said:
when you got nougat update please provide date if you remember
Click to expand...
Click to collapse
I got the update on 4th Oct. Tried it again on 5th, it disappeared!
When did you get the update?
Lord of Hell said:
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
Click to expand...
Click to collapse
May be they rolled back the update due to issues.
I got the update on 3rd October 2017.
I don't have any issues but yes Nougat battery is not as much effective than MM.
But its not draining like other people reporting.
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
nitingarje24 said:
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Click to expand...
Click to collapse
Kindly select based on region.
Updates will come based on combination of country & IEMI number.
If you are not from India and flashed the Indian version then it don't update further.
So make sure while flashing the ROM.
After flash check, should have stock recovery and ROM than only you will get the same.
Guys! I have received the OTA update today again. Not sure where to capture the OTA. Last time I didn't find it in Cache partition. This time I was able to pull the OTA zip file from data partition. Will upload it this evening if anyone wants the OTA zip file.
yes
thanks
Hi, I have a NOKIA model TA-1025 00S0_3_28A (with Lockscreen Offers & Ads AMAZON) but it stayed in the security patch of June 2017, I would like to know if someone else happens to you? or just mine, Thanks.
PLEASE, VERY GRATEFUL I WILL BE, IF SOMEONE HAS THE LINKS OR PAGES FOR DOWNLOADS THE UPDATES, THANK YOU
Kind of related; I've got a TA-1025 (Amazon no-ads variant) and mine's still stuck on the August 1st update.
RIP timely updates.
c0ldzer0 said:
Kind of related; I've got a TA-1025 (Amazon no-ads variant) and mine's still stuck on the August 1st update.
RIP timely updates.
Click to expand...
Click to collapse
Same as you, without Ads and i have September update
I have the version with Amazon Ads and same here, no October update!
Same here, I'm stuck on 7.1.1, security patch from July, is there any way to update this device?
I have the TA-1025, Amazon-ads variant
Thanks
No update
jorgeren said:
Same here, I'm stuck on 7.1.1, security patch from July, is there any way to update this device?
I have the TA-1025, Amazon-ads variant
Thanks
Click to expand...
Click to collapse
I'm stuck too in 7.1.1, no November update ? ta-1025 Amazon adds
The same happens to me I have the ta 1025 and i am still on august security patch
I finally managed to update it using the instructions on this post. I had to pull out the SIM card, do a factory reset, install Turbo VPN and try the update again.
I'm waiting for the December patch but otherwise I'm on 7.1.2 with November patch.
Kincadium said:
I'm waiting for the December patch but otherwise I'm on 7.1.2 with November patch.
Click to expand...
Click to collapse
Me too. I'm with 7.1.2 but with November patch, TA-1039. Maybe we don't get the December patch and directly get Android Oreo
Gonz19 said:
Me too. I'm with 7.1.2 but with November patch, TA-1039. Maybe we don't get the December patch and directly get Android Oreo
Click to expand...
Click to collapse
Supposedly we'll be getting the Oreo beta "soon." I'm wondering if they'll finish the beta phase for the Nokia 5 before they start the 6.
Although the phone is "unlocked" from Amazon the moment you put in a sim card it becomes tied to that cell carrier and thus no OTA unless pre-authorized by your carrier.
Follow the instructions posted by @kaykhoso96 and do a factory reset without your sim, rise and repeat process each month to get the latest update.
Additionally, for slightly less work, use the DDLs posted by @qwertysmerty and update from SD card each month.
Not without effort, but at least Nokia are sending out monthly updates. :victory:
I have the Nokia 6 from Amazon ads and I am no receiving any OTA so my phone is still on August security patch how can I fix that
Enviado desde mi TA-1025 mediante Tapatalk
As per my post above you:
1. Try a different brand sim – OTA is locked by carrier authorization.
Still not working? Then:
2. Remove sim card and factory reset with sim removed, leave sim out and use a VPN set to USA and let the updates rain.
I also have a TA-1025, I've factory reset my phone 4 times now. From November onwards I've successfully SD loaded the DDLs posted by Qwerty, saving monthly factory resets.
The fault doesn't seem to lie with Amazon but with whoever your cell carrier is.
c0ldzer0 said:
As per my post above you:
1. Try a different brand sim – OTA is locked by carrier authorization.
Still not working? Then:
2. Remove sim card and factory reset with sim removed, leave sim out and use a VPN set to USA and let the updates rain.
I also have a TA-1025, I've factory reset my phone 4 times now. From November onwards I've successfully SD loaded the DDLs posted by Qwerty, saving monthly factory resets.
The fault doesn't seem to lie with Amazon but with whoever your cell carrier is.
Click to expand...
Click to collapse
I had same issues as OP, it was fixed when i added in the "fota" in the apn settings, i guess it stands for "firmware over the air" and all of a sudden here comes my December patch. This was on T-Mobile just FYI.
@twinturboz suggestion above could be another option (since it's so simple it would be worth trying it before trying 2.).
I've just added fota to my carrier APN, will see if the carrier pushes updates. Do you know if it requires you to have sufficient mobile data or will it still work over WiFi with mobile data turned off?
c0ldzer0 said:
@twinturboz suggestion above could be another option (since it's so simple it would be worth trying it before trying 2.).
I've just added fota to my carrier APN, will see if the carrier pushes updates. Do you know if it requires you to have sufficient mobile data or will it still work over WiFi with mobile data turned off?
Click to expand...
Click to collapse
ASFAIK Nokia has firmware updates strictly WiFi only, i don't have home internet so all i did is use my iPhone SE as a hotspot and got everything installed that way.
Nexus 6P angler Feb update which one to chose?
I am currently on Nexus 6P
8.1.0 (OPM3.171019.013, Jan 2018)
I see 41 MB update. Since my device is rooted therefore I cannot directly update OTA being notified.
However i see on googles developer images that there are two images :
8.1.0 (OPM3.171019.014, Feb 2018) And
8.1.0 (OPM5.171019.015, Feb 2018)
Which one I should update from my current build.
Also any ways to successfully update on rooted Nexus 6P without wiping data?
Kindly help
Thanks in advance
sunandoghosh said:
Nexus 6P angler Feb update which one to chose?
I am currently on Nexus 6P
8.1.0 (OPM3.171019.013, Jan 2018)
I see 41 MB update. Since my device is rooted therefore I cannot directly update OTA being notified.
However i see on googles developer images that there are two images :
8.1.0 (OPM3.171019.014, Feb 2018) And
8.1.0 (OPM5.171019.015, Feb 2018)
Which one I should update from my current build.
Also any ways to successfully update on rooted Nexus 6P without wiping data?
Kindly help
Thanks in advance
Click to expand...
Click to collapse
I flashed OPM5 and everything is working fine..if you dont want to lose data unzip factory image and flash manually system, vendor and boot.img..no need for radio and bl because they are the same as january...
Since you are currently on OPM3, I would go with OPM3.171019.014. That's what I used and all is good. As far as updating without wiping data, you can also flash the full factory image using Flashfire - as long as you're not rooted with Magisk.
newkydawg said:
Since you are currently on OPM3, I would go with OPM3.171019.014. That's what I used and all is good. As far as updating without wiping data, you can also flash the full factory image using Flashfire - as long as you're not rooted with Magisk.
Click to expand...
Click to collapse
Thank you for your help. I am unfortunatelty rooted with magisk.
Hello.
I bought a used G935FD. It was on Android 8.0.0 August 2018 (?) patch.
I updated it to February 2019 and then factory reset it.
Now I can't get my SIM to work with it. Whenever I try to make a call, it says "SIM not registered". It can't receive calls either.
Calls were working fine before the factory reset.
EDIT: I wasn't able to resolve the issue and ended up returning the phone.
moso11 said:
Hello.
I bought a used G935FD. It was on Android 8.0.0 August 2018 (?) patch.
I updated it to February 2019 and then factory reset it.
Now I can't get my SIM to work with it. Whenever I try to make a call, it says "SIM not registered". It can't receive calls either.
Calls were working fine before the factory reset.
Click to expand...
Click to collapse
What if you flash latest stock rom again?
gupt07ash said:
What if you flash latest stock rom again?
Click to expand...
Click to collapse
How do I do that? Using Smart Switch?
Sorry but I have no experience with Samsung devices.
moso11 said:
How do I do that? Using Smart Switch?
Sorry but I have no experience with Samsung devices.
Click to expand...
Click to collapse
*Deleted*
Mods, please close this thread.