Related
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.
goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)
Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.
I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).
Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.
Can be done but not recommended.
adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6
What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.
Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.
Good to know. Thanks for the info!
Just received the n6 today and there was a notification to update to 5.1. I downloaded and updated it and now it is in an infinite bootloop- keeps on saying optimising 125 apps. (BTW this was completely stock- I didn't even sign in to my Google account) . I tried recovery mode wipes and endless reboots but nothings working- help please?
Btw I am a complete noob who doesn't know anything about root etc so I really don't know what to do.
Anyone
Anyone here
Dry Bones said:
Did your phone die mid installation?
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
heres a thread that could help you if factory resetting or wiping the dalvik/cache isnt working.
Click to expand...
Click to collapse
It didn't die,no. I want a way of fixing the bootloop- without voiding my warranty
Derp12340 said:
Anyone
Click to expand...
Click to collapse
Derp12340 said:
Anyone here
Click to expand...
Click to collapse
Greetings,
Please refrain from bumping a thread until at least 24 hours have passed. XDA Assist is a very busy forum and the Assist RC's have lives outside of XDA as well.
Regards,
The_Merovingian
Forum Moderator
look up how to flash a factory image.. because as i see it, you only have two choices, flashing a factory image, or getting an exchange from wherever you bought your n6.
Did you ever let it finish optimizing apps? Any time an OTA is installed the first boot takes what seems like forever aka 10+ mins depending on number of apps installed. If you interrupt the process I guess it's possible to corrupt something.
Otherwise like @simms22 said install the factory image to reset it entirely or take it back to in for repairs.
If you'd like to run the factory image install yourself follow Google's instructions and download 6.0.1 image for shamu (Nexus 6) at https://developers.google.com/android/nexus/images.
And also I did not enable developer settings nor did I root my device (it is completely stock) so my bootloader is locked and USB debugging is not enabled
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.
janjanrex said:
Go ahead and enable usb debugging and unlock the bootloader.
Once you have everything updated and you don't plan to root or want to do manual installs or take back ups just relock the bootloader when you're done and turn off usb debugging.
Click to expand...
Click to collapse
I think you missed the point... The device is bootlooping = impossible to enable USB debugging and unlock the bootloader.
Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
I think you need to go with option 3 - get a new phone under warranty, which shouldn't be a problem.
With your new phone, before doing anything else, unlock your bootloader. That will save you a lot of headache.
Edit: Did you try doing a factory reset in recovery? Check this link for instructions: http://www.digitaltrends.com/mobile/use-recovery-mode-android/
The Final Answer
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image
pr0ndigy said:
If you aren't going to replace the phone under warranty, then this is your only option.
1. Download Nexus Toolkit. http://www.wugfresh.com/nrt/
2. Use the toolkit to download the latest factory image.
3. Boot into Bootloader
4. Flash factory image
Click to expand...
Click to collapse
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:
simms22 said:
well, he has multiple options to choose from.. the other option being flashing the factory image the right way :silly:
Click to expand...
Click to collapse
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:
These little spats are what keep the community interesting, and I enjoy them when they happen. As Dame Edna Everage said: "I have the fortunate gift of being able to laugh at other people's misfortunes." But personally, I go with experience.
simms22 32,086 posts Thanks Meter: 25,801
pr0ndigy 79 posts Thanks Meter: 22
But hey, what do I know...?
As it happens, I'm a big fan of NRT, having praised, recommended and contributed to it a number of times, but I don't rely on it solely. And I would not go so far as to say "My way is the right way".
Just saying...
Its not a boot loop if you were able to get to the "optimizing apps" message. and the fact that it got to the "optimizing apps" message means your system partition is functioning properly.
Ive had optimization run for 35+ minutes before booting when i took my first official update. You may have messed the phone up if you forced Reboot/power off while it was optimizing.
try and let it boot, if you get the optimizing message then plug it up and let it sit overnight if you have to, i promise IT WILL BOOT.
worse comes to worse, just google "nexus 6 back to stock". your boot loader doesnt have to be unlocked, and usb debugging does not have to be enabled to return to stock
Derp12340 said:
Guys these are my options
1) sideload an ota through root toolkit
2)
Wipe data and reset using nexu
S root toolkit
Thing is, my bootloader is locked and USB debugging is disabled.
Click to expand...
Click to collapse
https://www.youtube.com/watch?v=0nDLvy8F5qk
Using ADB mode, you can flash latest factory images: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
https://developers.google.com/android/nexus/images?hl=en
pr0ndigy said:
My way is the right way!
How do i know?
Because i've done it, and it works.
So take your **** talk somewhere else kid :good:
Click to expand...
Click to collapse
LOL. you have no idea who you're taking to
Sent from my Nexus 6 using Tapatalk
Seems I solved the problem myself. I used the rootkit- I basically just unlocked the bootloader and then reset it and flashed marshamallow 6.0.1 and I'm gonna relock the bootloader tomorrow. It was easy enough even for a noob like me.
I wonder how you did it. I can't imagine that such toolkit is able to unlock a bootloader when "OEM unlocking" wasn't enabled in your rom. Or did you enable that before?
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Andysmith71 said:
Trying to compile as many users who have faced the same issue and to get some data to find a work around.
SM-N950F - Australian (TEL/TEL/TEL) post paid Telstra Note 8.
Waited one week for 'Allow OEM to be unlocked' to appear in Dev Settings.
This is my experience and now have the official binaries issue.
I also got the OEM unlock after one week, this is what happened when trying to install TWRP and Magisk on Stock ROM.
I tried to flash TWRP lost night and that was okay. I decided to hold onto stock and just have TWRP and Magisk at this stage until other roms are a little less buggy. Flashed TWRP. flashed Verity / Magisk, setup phone again and then decided to do a backup in TWRP. When trying to go into TWRP got the message 'Only official released binaries are allowed to be flashed' and then went into a soft brick. Had to restore phone to stock and now OEM unlock has disappeared again, In download mode FRP and OEM lock are both OFF. Tried to reflash TWRP and get the same message - 'Only official released binaries are allowed to be flashed'.
So the plot thickens.
Click to expand...
Click to collapse
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week(oem unlock was there), flashed SuperSU 2.82. When I was configuring an app to modify host(to disable ads), the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed' [emoji33]
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
zhengsmall said:
We are on the same boat bro,
Mine is SM-N950F/DS Singapore (XSP), got on Sep 9th via preorder from Singtel.
But I did not notice if oem unlock option was there when I got the device. Then I tried to flash TWRP last week, flashed SuperSU 2.82. When I was configuring an app, the phone rebooted itself before I was able to flash dm-verity, and went into the bootloop with the same msg 'Only official released binaries are allowed to be flashed'
Click to expand...
Click to collapse
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
It's good we're getting to a point where we can collect data and try different approaches. It was a much darker time when we were all sitting around wondering if/when the OEM Unlock toggle would show up!
Yes, I did a wipe/format prior to flashing Magisk. One thing I haven't been doing is clearing the cache/dalvik following successful flash... is that important? I recall doing that back when I rooted my S7 Edge, but I've not seen or heard about anyone doing it since.
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Thanks mate, been reading up there and seen the posts. Looks like Renovate has had most success so far with that method. Looks promising, fingers crossed. I've got another few more days in jail before I get the OEM unlock back.
I don't think anyone has reported a failure yet doing it that way. Still a ways to go on the testing though, It appears folks aren't all that anxious to screw up a good thing once they get up and running. The good news is if ordinary dumbassez like us can get in the smart guys should get something figured out sooner rather than later. Anyhow, good luck, if it's any consolation mine showed up in 5 days...
Andysmith71 said:
Hey mate, maybe you can try the method a few users are going to do now, after another week and when OEM re appears then redo the process but this time don't boot the device. However I see what happened in your case the phone restarted itself when configuring SuperSU.. I've not hear that happening before. Maybe try Magisk if your looking at trying again? Strange it rebooted by itself. Good luck and let us know how you go.
Click to expand...
Click to collapse
Thanks for the suggestion mentioned, but what do you mean by redo the process? Or just switch off and then on the oem unlock toggle when it reappears in 7 days after the first flash(twrp and supersu) followed by a reboot(as only via reboot can I judge if it works)?
In addition, in my case the phone restarted itself when I tried to modify host to disable the annoying ads, not during configuring SuperSU.
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
AndiF85 said:
Just ended up in the same boat as OP. same version same carrier etc.
hopefully soon the smart ones can figure this out. off to find stock rom and try to get back a working device
Click to expand...
Click to collapse
Hey mate, try the below mentioned method and see if it works.
thegreenthief said:
Alright, here's where I'm at after some experimentation.
I received my phone on the 19th, and when I looked in "Developer options" for the "OEM Unlock" option it was not present. A week (7 days) goes by and I look in "Developer options" again and I see that "OEM Unlock" is there. I enabled the toggle that day, and then in the evening I successfully flashed TWRP and noverity. After this I rebooted according to the instructions and I encountered the "Only official released binaries are allowed to be flashed" message along with a soft brick. Reflashed stock firmware to get out of it and "OEM Unlock" has vanished from "Developer options"
Now, a week goes by after this (7days again) and I check for "OEM Unlock" on the 26th. Just like clockwork it's there. This time I flash TWRP, skip noverity, and flash Magisk. I'm able to successfully root and I boot into the system -- I check "Developer options" for "OEM Unlock" and the toggle isn't there. For whatever reason after a while I decided I would reboot and see what happens. I go into a soft brick with the same "Only official released binaries are allowed to be flashed" message. I'm kind of kicking myself, because now I need to wait another week for the toggle to show up so I can make another attempt.
Next week I am going to flash TWRP, flash Magisk, and then let the phone sit there for another week while I wait for the "OEM Unlock" toggle to show back up. Once that happens I am going to see if I can reboot freely or if I encounter another soft brick situation. If I soft brick again I'm fresh out of ideas as a phone that is rooted but can never be rebooted without flashing back to stock is a non-starter.
Click to expand...
Click to collapse
Andysmith71 said:
I'm doing the same as you, I'm still a few days away from week 2. So I'll do the same, flash TWRP and Magisk then try my hardest not to have the phone restarted for any reason for another week. No reports yet of this work around as it's still early in the peace but I know there are a number of users who will try this method. Good luck and I'll post how I go or if someone else posts sooner! BTW did you do a wipe/format before flashing Magisk out of interest? Cheers.
Click to expand...
Click to collapse
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
krabman said:
You might want to check the huge thread on this thats about three posts from here. Short story it seems if you stay in recovery and install a rom with knox disabled you are good to go. Read more there...
Click to expand...
Click to collapse
Well I got out of Jail yesterday after getting back the OEM unlock for the 2nd time. This time I decided to 'play it safe' until the smart people figure out what the issues are. This method worked perfectly for me and I've now been flashing Viper, flashing extra fonts, doing backups in TWRP and generally using the phone as normal again. The current Renovate release (r95) has most of the issues fixed and is a good daily driver, also the facial recognition is all fixed and Magisk is working with no issues, I've been able to use my banking apps for over the counter purchases again, tested and all working. Here is the method that worked for me -
How to flash Renovate and not stuff up. Remove SIM card before starting (I got this from Krabman's posts so I was not going to tempt fate at this stage by leaving in my SIM card, this is just a playing safe method for now).
1. Install TWRP (I trust you all are okay with everything up to this part)
2. In TWRP, swipe right and go into menu.
3. Wipe / Format Data / Yes
4. Reboot into RECOVERY
5. Flash DM-Verity
6. Wipe / Factory reset (by swiping)
7. Flash Renovate - I chose to root with Magisk cause it works for my banking apps.
8. After flashing Renovate, allow it to boot into System.
9. Do your basic setup and then reboot.
10. Now insert SIM and continue to setup your phone, Ti and all that good stuff. Phone is now rooted and working, TWRP is all working and safe to use as normal. This is the part that I did Ti restore and flashed Viper4Android etc etc.
11. Happy days for now, until we work out exactly what the issues are.......
The only thing I did not do was to try and flash the XSA firmware (Australia Unbranded) with the S8 CSC firmware installer. Apparently another user used it and it worked for them on the Note 8, however I did not want to chance it for now. The only drawback is on Volte and WiFi calling is missing but that's not a deal breaker. I might research a bit more before I try to flash the CSCSelection_S7_S8 zip.
AndiF85 said:
I will give it a try once oem unlock returns. Hopefully this can be resolved soon. Being in jail sucks. I've tripped Knox so lost Samsung features and no root still so dont have root advantages.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
I was in the same boat as you - if Renovate floats your boat then check out my last post, I've installed Renovate and all working nicely again... Waiting for one week then in jail for another week sucked hard!
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
AndiF85 said:
Great to hear it worked for you. I was thinking of using Renovate as well as it looks like the best option we have at the moment. Now you have confirmed it's all good I'll be doing it the day I'm released from OEM jail. When I flashed stock firmware I tried the note 8 xsa to see if it was any better than the Telstra version but instead just lost features and gained new things in settings which didn't even work so went back and flashed Telstra version.
I know it's wishful thinking but does Samsung pass work for you? I don't care for Samsung pay and health but Samsung pass was a nice feature.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Just tested that out for you, unfortunately that is the only one that does not work (Well we know Samsung Pay won't work due to KNOX being tripped). It goes through all the setup okay, then on final authentication it says "Samsung Pass is temporarily unavailable, please try again later". So that's a bit of a bummer.. I've tested Android Pay, all good, and I also use NAB pay and works with no issues as well as long as you set it up correctly with Magisk (there is a bit of a method to follow but I found a way to make it work - in case your with NAB at all).
I might make a suggestion to mwilky to see if that could possibly be fixed in the ROM as I agree it's a great feature.
Edit - That question was already asked by another user, mwilky says that it does not work the moment TWRP is flashed and not likely able to be changed. Bummer.
Soft brick
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
bwallis said:
How do you get out of the soft brick? I have the SM-N950F/DS but I do not know what REGION I need to download for the official firmware. Thanks for any help!
Click to expand...
Click to collapse
Use Samsung Smart Switch for that. it will tell you the region code for your phone. It could restore for you, or you could use http://fw.updato.com/, or SamFirm, to download appropriate ROM
Alright finally I'm out of jail.
About to download everything then going to attempt tonight.
Andsmith71 how have you found the rom over the past week?
Any issues?
still holding Root?
Does Bixby Voice still work?
Sent from my SM-N950F using Tapatalk
Hey everyone!
First posting here, long time reader. So, I just f***** up big time. I tried to install the YT Vanced modules for my X4, realized I had to get rid of the stock YT app first, installed Terminal Debloater and at that point my device stuck during boot. To make things infinitely worse, I then proceeded to re-lock the bootloader cycling through the last commands issued. That was dumb, yeah.
Now I get the "device corrupt" message when I try to boot normally and fastboot won't let me flash again saying I need to enable USB debugging, which I can't because the system won't let me boot.
I have a severe feeling I'm screwed with nobody but myself to blame, but I'm also aware of the godlike knowledge in these boards so... can anyone point me in a direction here? Damn I like that phone and have zero funds for a new one right now :/
I can still get into the Power+Down menu, the stock recovery gets me nowhere though. Oh, and it's the Euro Model, Motorola Moto X4 XT1900-05, running the Oreo OTA update.
Cheers people,
grslbr
You need to flash the original official firmware that came loaded on your device but good luck trying to find a copy of that. With the bootloader locked, you're screwed.
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
FI stock roms seem to be located at https://firmware.center/firmware/Motorola/Moto X4/Stock/ Have not tried them myself and not sure you can flash with a locked bootloader.
You should be able to flash a stock ROM pretty easily. From what I've seen, you should be able to install any retail stock rom without unlocking the bootloader.
grslbr said:
Thanks for answering. Yeah, since I locked the bootloader in my infinite wisdom I think I am screwed for good.
Could Lenovo have some magic tools to re-flash the stock ROM? I mean I know I voided my warranty but I liked that phone and am all out of options at this point. :/
Click to expand...
Click to collapse
Hold Vol+ and Power buttons. Phone will try to reboot several times and then boot normaly. Go to developer options and tick allow factory unlock and USB debugging. Then you just unlock bootloader as usual.
This procedure helped fix the same issue with my xt1900-7 reteu.