Database Develop

[Q] Unlock Bootloader B609 + recovery

Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated

JellyFox said:
Hi everyone
I recently updated to B609 and (as expected) my phone was un-rooted.
I decided it would be better for me to just install a ROM instead of waiting for a new way to ROOT every time a new OTA comes out. (I have seen some very interesting ones that include Xposed)
This would be the first time i install a ROM on one of my phones but i do know how to use custom recovery's and i will always keep a copy of a backup close so i can flash back when something goes wrong.
A problem i have with starting all of this: I can't seem to find a way to unlock the Bootloader on my phone.
I have looked online but i always get links for older versions/other phones/German stuff.
Second problem: The recovery. As far as i understand, there is no working TWRP for EMUI3.0. BUT there should be a working CMW recovery. Should i go fot CMW?
Third problem: Which ROM? There are 3 that grabbed my attention. Se7en-Rom (But it seems like it hasn't been updated in a while), My-RoM (which seems the most interesting for me at the moment) and Miui (which i just found out about). Which should i go with or should i use another one? I can already say that i want my phone Rooted and Xposed is something i would love to have back (since i used to have it on my previous phone).
Any advice and help would be appreciated
Click to expand...
Click to collapse
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!

arthios said:
I have a P7-L10 with B609. I was able to successfully root it with RootGenius. When you root it, the bootloader is unlocked at the same time. As far as I can tell, the root is 100%. As for CWM, you can get it from here:
http://forum.xda-developers.com/ascend-p7/development/mods-tweaks-kernels-recoverys-emui-2-3-t2966670
TWRP doesn't work with B609/emui3.0.
My L10 has faulty flash memory and won't accept a custom recovery, so I can't test CWM or any custom ROMs. Perhaps others can advise. Good luck!
Click to expand...
Click to collapse
RootGenius was the first thing i tried. It went up to 66% then i got an error but that was a fully Chinese version.
I just tried it again with the one i found by using Google and it goes up to 72%, then tells me that the root has failed.
Which version did you use?

This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers

ibeqa said:
This is what I used and it worked fine (root genius): http://forum.xda-developers.com/showthread.php?t=2789337
As for bootloader, as far as I know from, starting with firmware 133 (Emui 2.3) all devices have unlocked bootloader
CWM is the only custom recovery for the moment;
Did not try any custom ROM (I'm happy with stock ROM for the moment).
Cheers
Click to expand...
Click to collapse
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.

JellyFox said:
That's the first one i tried out. The first few times it ended in an Error. I tried it again today and when my phone reboots during the process, RootGenius loses contact with my phone.
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.

arthios said:
Hmmm, strange problem. Assuming you have the latest version of HiSuite installed and your drivers are current, all I can suggest is trying again with RootGenius (I used version 1.8.7) with your firewall and antivirus disabled or perhaps trying with Vroot. If you do decide to try Vroot it probably won't work unless you disable your firewall and antivirus.
Click to expand...
Click to collapse
I disabled my firewall and antivirus and gave RootGenius another try. Normally it goes up to 71% and gives me the error. Now it went to 71%, rebooted and then it gave me the error. The weird part is that right before i get the error, it says the installation is complete.
Moved on to Vroot (which is called Iroot now apparently) . It took a while longer but it wasn't able to do it either.

JellyFox said:
And there is a bootloader-ish thing, but the only options i have is reboot, factory reset and cache wipe.
Click to expand...
Click to collapse
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.

update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208

Z!L0G80 said:
update to b615 and flash or just flash this >> http://forum.xda-developers.com/ascend-p7/development/b615-unlocked-boot-img-t3050926 and use rootgenius remove inmutable etc...
btw there is twrp for emui 3 which mostly work fine http://forum.xda-developers.com/showpost.php?p=59340975&postcount=208
Click to expand...
Click to collapse
I still didn't get the OTA for B615 yet but thank you for the recovery.
ibeqa said:
Get in bootloader mode, if your bootloader is unlocked, it will be written and highlighted with red color. I will point out again, starting with firmware B133 (Emui 2.3) all bootloaders for L10 version (I don't know for Chinese versions) are unlocked
Cheers.
Click to expand...
Click to collapse
You were right! (not that i every doubted you). I found the problem i had: For some reason, i couldn't boot in bootloader trough my phone BUT i was able to do it with 'adb reboot bootloader'. After making some idiotic mistakes and having to re-flash the stock ROM, I finally was able to install My-RoM v3.3, its rooted, i have Xposed so i am happy
So thank everyone for the help!

[Q] Phone rooted but stuck on bootloop

Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.

cowboyv said:
Hi, I tried searching for this here (I remember reading something about the bootloop problem) but can't seem to find the thread, so any help will be greatly appreciated.
I have successfully rooted my Z3c using this guide all the way to the very end, however I noticed that the wifi wasn't working. I figured it was simply because I hadn't flashed the 23.1.A.0.690 firmware yet, but once I did, my phone is stuck in a bootloop; the sony logo appears and the phone resets over and over. I'm still able to go into fastboot but my question is, how can I put a stop to the boot loop? should I flash the newest FW (D5803_23.1.A.1.28_Customized_US.ftf), go back to the one the phone was shipped with (D5803_23.1.A.0.726_Customized_US.ftf), or reflash the root exploit one (D5803_23.0.1.A.5.77_US.ftf)>
UPDATE: I flashed D5803_23.0.1.A.5.77_US.ftf and the phone booted up without a hitch and kept rooted.
Click to expand...
Click to collapse
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.

Revontheus said:
Bootloops on Android devices can be caused by multiple factors. I suggest Flashing the .93 Kitkat firmware from there Root and if I am not mistaken there are flashable ( .zip) Pre-Rooted Roms which are Lollipop found in the Android Development Section of this Area.
Just make sure to flash the FW corresponding to your Model Number either D5803/833
If you prefer the harder way you can always use Flashtool to flash the Stock 4.4 FTF it came with and upgrade from there.
Click to expand...
Click to collapse
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?

cowboyv said:
Yeah, what I did was reflash the .77 FW without wiping system, and then, from there I flashed this 5.02 image, however now I am encountering a different problem: a persisting notification stating that I need to update google play services, even when I'm using the 7.5.73 version for 036. Has any one else encountered this problem? Is there a solution to this?
Click to expand...
Click to collapse
You can always download GAPPS manually, and flash it via Recovery if you think the Google Play Services that comes with your FW is bugged

[SOLVED] SM-N9200 Chinese help needed

Hi,
First post on here. I have bought the SM-N9200 in China after my Z3 screen broke for the second time. I live here (china) at the moment but did not realise that you would be unable to install google play services and therefore google play on the phone. I have a fair few apps purchased on GP and would like them on my phone.
I have read that I would need to have root access prior to being able to install GP but I am running into problems. I have never rooted before even though I was aware of the process etc but have so far been unsuccessful using kingoroot and I cannot seem to find a root method for the Chinese n9200. I saw today that the spaceX kernel supports N9200 so I thought that I would flash twrp with odin and then consider flashing spaceX. However when I try and flash TWRP it fails and the phone displays a message in Chinese that I cannot read as my Chinese is not that great still.
I am not in a hurry to install a custom rom at the moment and mainly just want to be able to get my apps. Can anyone suggest a method? is it possible to install HK Rom onto Chinese n9200 for example?
Many thanks

DarthJ said:
Hi,
First post on here. I have bought the SM-N9200 in China after my Z3 screen broke for the second time. I live here (china) at the moment but did not realise that you would be unable to install google play services and therefore google play on the phone. I have a fair few apps purchased on GP and would like them on my phone.
I have read that I would need to have root access prior to being able to install GP but I am running into problems. I have never rooted before even though I was aware of the process etc but have so far been unsuccessful using kingoroot and I cannot seem to find a root method for the Chinese n9200. I saw today that the spaceX kernel supports N9200 so I thought that I would flash twrp with odin and then consider flashing spaceX. However when I try and flash TWRP it fails and the phone displays a message in Chinese that I cannot read as my Chinese is not that great still.
I am not in a hurry to install a custom rom at the moment and mainly just want to be able to get my apps. Can anyone suggest a method? is it possible to install HK Rom onto Chinese n9200 for example?
Many thanks
Click to expand...
Click to collapse
To flash in Odin you need to enable OEM unlock in Developer Settings.
I tried installing Chinese on HK and it failed (Cache.img)

OEM unlock and USB debugging are on. Odin was run as Admin.
If you try flashing the wrong TWRP (i.e not for your phone) will it fail or will it still flash. I was trying to TWRP for the DUOS version which i am assuming is my phone as DUOS is the dual sim variant?
I will get a chinese friend to tell me what the message is and take a photo of what happens.
Essentially i boot into DL mode and then attempt to flash when the bar fills up the odin still says recovery but the screen on the phone gives me warning (triangle with exclamation) and some information including a the web address for samsung.com/cn

I can help with that Chinese message. There are some problems for you to use GP in China. First, you can use Odin to install HK (TGY) Rom( remember to backup before u do so). After you install HK Rom, you need to connect to a VPN and then go to Google settings.
Hope these info would help you.

Possible solution found in another thread. it seems that the bootloader is locked on some devices and therefore you cannot flash anything.
http://forum.xda-developers.com/not...ote-5-root-t3214234/post63073600#post63073600
One question. What would be the difference between the HK and Chinese versions of N9200 other than some restrictions. Is it safe to use guides like the one linked for a chinese version?

cxhugh said:
I can help with that Chinese message. There are some problems for you to use GP in China. First, you can use Odin to install HK (TGY) Rom( remember to backup before u do so). After you install HK Rom, you need to connect to a VPN and then go to Google settings.
Hope these info would help you.
Click to expand...
Click to collapse
So i can simply flash stock HK rom onto my N9200? sorry for my ignorance, i am very new to this. what is TGY?

DarthJ said:
So i can simply flash stock HK rom onto my N9200? sorry for my ignorance, i am very new to this. what is TGY?
Click to expand...
Click to collapse
TGY is the name for HK ROM. You can find it on samsung-updates. Both Mainland and HK variant share the same specs, which is N9200.

SUCCESS!
So after much stress I have a rooted, TWRP'd, Romd N9200 Chinese version. I say stressed as I had some problems when i flashed TWRP in that it would not let me boot back into the stock rom. this leads me to one unanswered question. When flashing TWRP with ODIN is it a requirement to flash a new rom?? I say this as I had the following problem. When I first flashed twrp the phone booted into stock so I rebooted into recovery only to find stock recovery and no twrp. I checked that the KNOX counter had been tripped (it had) but I was confused. I read on twrp website that on some devices if you let phone reboot into stock after twrp flash rom it overwrites custom recovery. I eventually flashed twrp and quickly pressed key combination for recovery and I had twrp but then I could not boot into stock rom (bootloop).
After spending the afternoon in a state of panic I reflashed the stock rom from Sammobile and was back in business. crisis over and a bit of confidence gained.
I am now using SpaceX kernel following this thread:
http://forum.xda-developers.com/note5/development/kernel-spacex-pure-edition-stock-t3236317
so far no problems so thanks to @Manh_IT
Here is my step by step if anyone finds themselves in same position:
1) unlock OEM and USB Debugging and backup everything using SmartSwitch (this replaced Kies I believe)
2)download CROM apk from Samsung appstore to unlock bootloader
3)Download SpaceX, SuperSU.apk, Gapps and twrp and place all except twrp onto phone memory
4)Flash TWRP with ODIN and reboot into recovery using method described above if need be.
5)factory reset in twrp
6)flash SpaceX and Gapps
7)reboot system and install SuperSU
I hope this helps someone.:good:

Anyone rooted in n9200 with latest OKA firmware?

actually you don't need to root your device...
just make sure OEM unlocked and find a HK version stock ROM and install it with Odin

vhxlyt said:
actually you don't need to root your device...
just make sure OEM unlocked and find a HK version stock ROM and install it with Odin
Click to expand...
Click to collapse
Can i ask sir how do you do that? Thanks

rcsiccion said:
Can i ask sir how do you do that? Thanks
Click to expand...
Click to collapse
well if you use N9200(CN)...you can follow the steps to get gapps
Once you use Crom.apk, you lose your warranty , so DON'T use CROM to unlock the phone
Make sure OEM unlocked
Reset to factory in case of some issues
Turn off the phone
Take the sim out of the phone
Get into download mode
Plug to PC and use ODIN to flash the HK stock ROM.
gapps will be install , no root, and you wont lose you warranty , but the battery saving is not as good as CN version.

I have gapps on my note 5 n9200

DarthJ said:
SUCCESS!
So after much stress I have a rooted, TWRP'd, Romd N9200 Chinese version. I say stressed as I had some problems when i flashed TWRP in that it would not let me boot back into the stock rom. this leads me to one unanswered question. When flashing TWRP with ODIN is it a requirement to flash a new rom?? I say this as I had the following problem. When I first flashed twrp the phone booted into stock so I rebooted into recovery only to find stock recovery and no twrp. I checked that the KNOX counter had been tripped (it had) but I was confused. I read on twrp website that on some devices if you let phone reboot into stock after twrp flash rom it overwrites custom recovery. I eventually flashed twrp and quickly pressed key combination for recovery and I had twrp but then I could not boot into stock rom (bootloop).
After spending the afternoon in a state of panic I reflashed the stock rom from Sammobile and was back in business. crisis over and a bit of confidence gained.
I am now using SpaceX kernel following this thread:
http://forum.xda-developers.com/note5/development/kernel-spacex-pure-edition-stock-t3236317
so far no problems so thanks to @Manh_IT
Here is my step by step if anyone finds themselves in same position:
1) unlock OEM and USB Debugging and backup everything using SmartSwitch (this replaced Kies I believe)
2)download CROM apk from Samsung appstore to unlock bootloader
3)Download SpaceX, SuperSU.apk, Gapps and twrp and place all except twrp onto phone memory
4)Flash TWRP with ODIN and reboot into recovery using method described above if need be.
5)factory reset in twrp
6)flash SpaceX and Gapps
7)reboot system and install SuperSU
I hope this helps someone.:good:
Click to expand...
Click to collapse
Hi great to heard that you have managed to resolved this issue. I have the same problem ( I bought my Note 5 in Beijing recently), so please can you explain what I need to do? I can do point 1 & 2 but stuck on point 3 and the rest. Where do I get all these files from?
Many thanks

Android 7.0 Call Problem

Hi
I have installed many of the Android 7.0 ROMS for Shamu and all of them have this annoying problem:
When I dial out I cannot hear the ring or the other person.
When I receive a call I don't often hear the other person but they may hear me.
Yes I've installed the N6 boot loader and radio and do not load any other mods, custom kernels.
I just can't figure this out. Any ideas? Is there a Android 7.0 firmware that I need to install to prepare my Shamu for Android 7?
Thanks
Aussie

I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it

Flashing Stock 7.0
aroy97 said:
I had this same problem, I had to re flash stock 7.0 and the problem was gone. No idea what caused it
Click to expand...
Click to collapse
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie

aussie1234 said:
Did flashing stock 7.0 re-lock bootloader? Were you able to unlock the phone?
Thanks
Aussie
Click to expand...
Click to collapse
Flashing stock does not relock the bootloader.

Didn't work
Ok I flashed stock 7.0 using Wugfresh's tool.
But still when I use the phone I can't hear who is on the other end.
Really odd!
Anyone have any suggestions?
Thanks
Aussie

I'm having the same issue on a stock Nougat phone as well. The problem appeared a few days ago out of the blue. The only band aid fix I've found is the sound about app and force assigned the mic and earpiece functions.
Sadly, this doesn't address the main issue in the first place.

none
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
---------- Post added at 07:53 AM ---------- Previous post was at 07:50 AM ----------
USMC retired said:
Why are you using Wugfresh? Plug the phone in the computer and when it communicates with the phone tap the menu bar that says it's charging, when you open that tick allow files/folders, the second option. Then put your files on the root of internal storage, wipe the entire system then flash your rom, you don't need Wugfresh.
If you lose your data who cares, just set the phone up again and you should be good to go, this is much more dependable as I use to use Wugfresh, you do know how to get into recovery and install that way? You will want to do a full wipe, then flash
Click to expand...
Click to collapse
If you need anything else you can PM me

I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.

stevew84 said:
I didn't realize there was a thread on this already.
I'm using Pure Nexus and the other end would go silent for about 5 seconds and then come back...so that's a bit different than what you guys are experiencing.
Click to expand...
Click to collapse
have you tried reflashing your radio? Maybe try flashing a MM radio as well

Just wanted to chime in, I think this is actually more of a VoLTE/HD issue. It happens to my N6 that's still on MM. Sometimes the dialtone/ring is there, other times it's not. Would love to know of there's a fix!

Found a fix..
Hello all.
I found a fix to Shamu+Nougat ROM problem when I am called I do not hear the other person and vice versa.
To install Factory Nougat from Google: https://developers.google.com/android/nexus/images
FIRST backup your phone (contacts, files, pics, movies etc) as this will totally erase EVERYTHING!
When you are on the Factory Images for Nexus Devices page click "backed up to your Google Account" then go click 'back' on your browser and click on 'Acknowledge' to see the list of Factory Nougat ROMS for Shamu come up on the right.
Download the Android 7.0 Factory ROM for Shamu/Nexus 6.
Do not flash this stock ROM using Wugfresh's tool. Instead follow precisely the 'Flashing Instructions' on the page https://developers.google.com/android/nexus/images. Allow the phone to reboot and fully set up. Restart the phone again.
Then use Wugfresh to Root the phone and also to install custom recovery (I already have unlocked bootloader).
Now, nothing against Wugfresh Tool (I do not know why the flashing method above works better) as Wugfresh has saved my phone many times.. Its just that Googles recommended flashing instructions worked best.
Now I use the phone and not only do I hear the caller and they hear me I have much better reception (Australia). Yes I did previously flash latest radio but the above method seemed to improve my Shamu 100%.
What I have not done yet is flash a custom ROM in case the problem re-appears. But my phone is rooted and unlocked so I can install other mods that work with Nougat.
Hope this works for you.
Cheers
Aussie

Another Fix Part 2
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie

aussie1234 said:
Hi
I stumbled on another method that has seemed to work:
Ensure you have unlocked bootloader.
Flash Tupacs Android 6.0 MOB31H ROM from http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
(*Note I used his MOB31E Android 6.0 ROM so I am presuming current MOB31H will work).
Credit to this ROM goes to tupac4u as I am not a Developer.
I then flashed SuperUser but did not flash a custom kernel.
Setup the ROM as usual.
Selected Settings - About Phone - System updates and let the phone install the Android 7 OTA update. Be aware its a 878Mb download.
Let the update download and fully install. I had TWRP recovery and the update still installed fine.
After installation fully completed I enabled Developer Options and USB Debugging.
Then using WugFresh's excellent tool http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452 I applied Root and Custom Recovery.
I also flashed Radio 5.39R which I found works best.
Now my phone works very well and (for now) now I can hear the caller and they can hear me.
Cheers
Aussie
Click to expand...
Click to collapse
Has there been a listed fix for people who haven't rooted their nexus?

Note 8 soft bricked

Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.

This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock

ZeroXO said:
This msg Only official released binaries are allowed to be flashed cause of the new security patch lock which called RMM or KG and since u were rooted before then u got this error that's cause you flashed a new BL to your device or you were connected to internet before editing kernel to prevent samsung to add the new lock to your device anyway a normal flash through odin will solve your problem and your device will be ready to use it again without any problems but also without any custom files like TWRP and Magsic which means u will not be able to root your device before editing kernel to remove the new security patch lock
Click to expand...
Click to collapse
Okay I was thinking I might of missed something. The patch for oem issue I thought covered that.
Is the unknown (bat) firmware the one I need to flash to stock?
Sent from my OnePlus6T using XDA Labs

TheLogicalGamer said:
Salutations everybody. I haven't had a phone from sammy in a while. Finally invested in a SM-N950F note 8. It's oreo. Tried to root earlier today using the pinned guide in the Guides forum. After going through the process, and flashing twrp. Then formatting data. And rebooting it to twrp (which I did a couple of times) (May been where I messed up,but it doesn't seem likely to me) I flashed the oreo n950f oem issue zip and rooted with magisk. Upon rebooting & enabling dev options. The oem toggle was missing. The guide didn't say what to do in the event that it was missing. Just that it was safe to reboot if it was there, and enabled.
Me being rushed for time rebooted anyway, and now when I try to boot up I get only official released binaries may be flashed, and the phone shuts off.
I'm aware I can restore to stock via odin. But I have a couple of questions.
A. Can I use the same odin version I used for the root process to return to stock, or do I need a different one?
And
B. There are loads of options for country and carrier on sammobiles site. I bought the phone used and have no idea of its country of origin. There is a version that says unknown for country and (bat) for carrier. Is that one safe to use, and is there any difference between the firmwares other than carrier setting being preinstalled (would be my guess of the only difference.)
Thanks in advance for any help you can provide.
Click to expand...
Click to collapse
Using odin 13.1.3 is recommended.
As you have the N950F, it is part of the multi OXM CSC, so you can flash the filmware for you country and carrier if desired (N950F)
If you want to root, I suggest just flashing a custom rom or kernel, as they have been patched for the RMM KG state issue.