Database Develop

[Q] Solved Help - Baseband version - unknown

A little background. A few months ago I purchased a Samsung Galaxy S4 Active SG-I537 from a person on Craigslist after my HTC One M7's microphone died. Anyway, I thought the phone was fully stock. I started to become suspicious that this was not the case when I checked for software updates from AT&T and the updates began to fail repeatedly. I downloaded a root checker from the Google Play store and, confirming my suspicions, I had root access. I didn't really like finding this out this way, but it was my own fault for not asking. Having installed CyanogenMod on both a Galaxy S1 Fascinate and an S2 Skyrocket, I knew something about these things and decided to just live with it as the phone seemed to work otherwise.
Recently I tried playing video on my DirecTV app and found that the app would not function on a rooted phone. That coupled with the fact that I am hearing that Android 5.0 Lollipop will soon be released for the S4 Active made me want to return the phone to a stock firmware. So I began reading. The problem I have is that I have no idea whatsoever how the phone was rooted. I know that the firmware was 4.2.2 UCUAMF3. So I downloaded ODIN and the full ODIN package of UCUCNE3 and then followed the below guide to a T.
Everything seemed to work, I got a pass green light from ODIN. But I have a circle with a line thru it where the AT&T wording usually appears. The 'about device' page in the settings also says 'Baseband version' is unknown. and I have no cell abilities. I can do everything from the smartphone end via WiFi. But I have no cell phone capabilities. Can't make calls, etc. What I need now is someone to point in the proper direction of where to look for the knowledge on how to fix this problem. Any help would be greatly appreciated.
Thanks.
Code:
Quote:
MF3 to MF2 (Official: Released 2013-06-21)
Quote:
MF3 to MF3 (Official: Released 2013-06-21)
Quote:
MF3 to MI2 (Leaked: Released 2013-09-25)
Quote:
MF3 to ML2 (Official: Released 2014-01-07)
Quote:
MF3 to NC9 (Official: Released 2014-04-16)
Quote:
MF3 to NE3 (Official: Released 2014-06-06)
Download the NE3 Full Odin Package from the i537 Firmware Thread.
Extract SGH-I537UCUCNE3_v4.4.2_ATT_ALL.zip using a program such as 7-zip.
Download the Windows program Odin. For more information about what Odin is and where to get it, please read the Odin section in the first post.
Open the version of Odin that you downloaded (preferably Odin v3.07)
Once opened, you need to load the files for the Bootloader, PDA, Phone, and CSC. The required files are located in the Odin Files folder. It should look exactly like the screenshot below with the appropriate checkboxes checked.
Next put your phone in download mode. For more information on how to put your phone in download mode, please read the download mode section in the first post.
Once your phone is in Download Mode, connect it to your computer using the cable that came with your phone. IMPORTANT: Odin and Samsung phones are very finicky when flashing firmware, the only usb cable that is guaranteed to work is the cable that came with your phone. You may use other usb cables, but Odin may not detect your phone. If Odin does not detect your phone try connecting to a different usb port or a different computer.
If your phone has connected properly it should show up properly in the Odin window similar to the following picture:
Once Odin has detected your phone, hit Start. It will take a long time to flash the package to your phone and will completely wipe your phone. DO NOT DISCONNECT THE CABLE OR TURN OFF YOUR COMPUTER. If the process is abruptly interrupted you risk permanently bricking your phone, so be careful.
When the program has finished it is safe to disconnect everything and reboot your phone. Your phone will be completely stock, unrooted and you will have to setup your phone from scratch again. If you wish to root the NE3 firmware, please visit the towelroot website.

tried asking the person you bought it from?
I've heard that installing a firmware/rom twice in a row can help things. try that! good luck!

If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692

O-T said:
If IMEI is null (check by dialing *#06#) and similar situation like this?
http://forum.xda-developers.com/showthread.php?p=56473692
Click to expand...
Click to collapse
Wow, I spent 7 hours on this yesterday and couldn't find that thread. I guess my search skills aren't what I thought they were. A huge thanks, O-T. I'm back up and running. I flashed the MF1 modem to get the service menu back up and selected the correct option. I was then able to reflash the NE3 firmware and now I have baseband and IMEI properly identified and working. Took another couple of hours but I'm there. Again, mucho thanks.

[How-To] Update to I537_OC7 - 5.0.1 and KeepRoot

**You can begin the following process from 4.4.x Build/ROM or higher but you must already have Root Access**
**Required** FlashFire - Play BETA - PREVIEW
**Caution!** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Download:
- I537_OC7_Stock_Rooted_ROM
- I537_OC7_Stock_Rooted_Deodexed_ROM
Pevious Builds:
- I537_OC6_Stock_Rooted_ROM
- I537_OC6_Stock_DeOdexed_ROM
Set your screen timeout setting to 10 mins before beginning!
1. Place the ROM onto your device (use either internal or ext-sdcard).
2. Open the FlashFire app and "Agree" to the Terms and Conditions.
3. Press "(+)" twice to bring up the "Actions" menu.
4. Select "Flash Zip or OTA" and locate and select the ROM. Leave "Auto-mount" unchecked under the "Options" menu and press the checkmark to continue.
5. From the main menu Uncheck all options under "EverRoot" and set "Reboot" setting to "Download."
6. Press the lightning bolt then "Ok" to begin the flash.
7. Once the flash is complete and the device reboots into "Download" mode, flash the I537_OC7_Bootloader using Odin's PDA/AP slot.
The screen will turn black then display the contents of your system before beginning the flash. FlashFire will pause for about 1 minute while flashing the "system" partition. Once complete your device will reboot and pause on the AT&T splash screen for 1 - 2 minutes (15 - 20mins for DeOdexed version) before completely rebooting. Done!
Tip: for blazing fast speed turn off animations from Developer Options and reboot!
Known Issues:
- None!
Optional - Enable Native Tethering:
- I537_OC7_TetherAddOn
- I537_OC6_TetherAddOn (Flash using FF's "Flash zip or ota" option.
Notes:
1. The above process will not affect your Knox Warranty Flag.
2. The process will update your Modem, Non-hlos, System, Kernel, and Stock Recovery.
3. No need to wipe prior to flashing! The ROM will automatically perform a factory data reset.
4. To learn more about FlashFire's capabilities on locked bootloader devices see here: http://forum.xda-developers.com/showpost.php?p=60070810&postcount=2
Credits:
@thisisapoorusernamechoice - for capturing the ota update and for his system dump.
@Chainfire

muniz_ri said:
**You can begin the following process from any Build/ROM but you must already have Root Access**
**Attention** The following process is only for the I537 AT&T S4 "Active" variant. Use on any other device may result in a hardbrick!
Instructions:
Click to expand...
Click to collapse
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix

thisisapoorusernamechoice said:
First of all, thank you thank you thank you so much for this. Yeah I grabbed you the OTA's but thanks to you (and of course Chainfire & his FlashFire) we can go from KK to LP with root. And on day one of the OTA. Awesome. :good: So down to business, and I hope I'm not getting ahead of myself or barking up the wrong tree, but hear me out on this one. @Joe-Tech was generous enough to port his regular S4 Google Play Edition (Pure Nexus) 4.4.4 Rom over to our phone. Could we repeat that for this OC6 build, using say, this rom as a base (or another if that turns out to be incompatible for whatever reason)? I doubt I have the expertise to pull that off but if it would help I'd get to work on another masterpatch and speaker phone fix
Click to expand...
Click to collapse
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon

Joe-Tech said:
I have an LP 5.0.1 base, ported using that ROM that you mentioned, but we all know safestrap is not compatible yet with 5.x and FlashFire can only flash TW base rom from my experience, and it still on beta phase, so let just cross fingers, i know something coming soon
Click to expand...
Click to collapse
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option

thisisapoorusernamechoice said:
You're the man. Thanks for this info. I'm going to make a masterpatch, hopefully it'll be needed soon. Obviously I'll be happy to test anything if and whenever something like this does happen. If I can do anything at all to help that along just let me know. I was not aware FF could only flash TW base roms, shoot
Still loving your 4.4.4, I'm torn on taking the update if it means going back to touchwiz with no current AOSP option
Click to expand...
Click to collapse
Only way im thinking to boot the new LP ROM, is to use @muniz_ri method so we can upgrade and keep root. So now we going to be on the OC6 kernel and baseband, since the gpe can boot without flashing the kernel. Then we can flash the GPE 5.x ROM, either with safestrap or FlashFire, and we can also use Odin to flash the stock kernel/partitions. But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.

Joe-Tech said:
But too bad none of them worked for me after the upgrade, FF will sit there for ever try to get root permission.
Click to expand...
Click to collapse
Were other rooted apps able to get root permission?

thisisapoorusernamechoice said:
Were other rooted apps able to get root permission?
Click to expand...
Click to collapse
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.

delete
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

Joe-Tech said:
Nope I even tried root checker, the su app is there on the app drawer, i was able to updated from the play store, but still wasn't working though.
Click to expand...
Click to collapse
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question

thisisapoorusernamechoice said:
Just had a thought, probably nothing. When doing the kitkat to lollipop update to keep root with flashfire, would it help anything to convert flashfire to a system app before doing the update? Sorry if this is a stupid question
Click to expand...
Click to collapse
I don't think it will make any difference.

@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.

Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
Extract the tar from the rar. Leave the zip as is. Copy the tar and the zip to your phone's internal memory or external SD card, somewhere it'll be easy for you to find

Devo7v said:
@muniz_ri: This is great, thanks for all your work on this. As I understand it, this method will update you to OC6 with root if the original firmware was already rooted. So my question is then, if a user has already taken the OC6 update and would like to root afterwards is it currently impossible? Is the only way to root OC6 to downgrade back to NE3, root, and then follow your instructions to update to OC6 with root?
I'm guessing a root vulnerability hasn't been found for the Samsung 5.0 firmware yet, but I just wanted to check.
Also, I posted this in the other thread, but has anybody actually downgraded from OC6 to NE3 successfully? I don't want to give people wrong information.
Click to expand...
Click to collapse
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.

mikelets456 said:
Okay, I need some help here. I'm not quite understanding this:
1. Extract the I537_OC6_Stock_Rooted_Firmware.tar from the .rar and place it and the I537_OC6_Stock_Partitions.zip onto your device (use either internal or ext-sdcard).
Place what where? I used WinRAR to extract the file? What is the OC6 stock partition?
Click to expand...
Click to collapse
If all of the above is beyond your level of understanding I strongly suggest you reconsider attempting to modify your phone.

muniz_ri said:
Correct, you will need to go back to NE3 then use towelroot before starting this process. And yes, the aboot qfuse counter determines whether or not you can downgrade. I checked it and it does allow for downgrading.
Click to expand...
Click to collapse
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.

Devo7v said:
Great thanks, one more question: Would it be possible to use something similar to W0lfdroids method of rooting? So on stock OC6, flash the NE3 kernel (since downgrading is possible), root with Towelroot, the flash back to the OC6 kernel. Just thinking about it I'm guessing it wouldn't work because you wouldn't be able to boot 5.0 with a 4.4.2 kernel, but I figured I'd ask.
Click to expand...
Click to collapse
Did not bother to try since it has not worked on any 5.0 release so far.

muniz_ri said:
Did not bother to try since it has not worked on any 5.0 release so far.
Click to expand...
Click to collapse
Any chance I can implore you to try it since there will inevitably be a bunch of people already on the OC6 firmware asking how to root it and will get pissed when they find they have to wipe their phone? Or maybe you could just provide the stock OC6 kernel and I can convince @thisisapoorusernamechoice to give it a shot?

For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.

bobbylx said:
For what it's worth, just went through the process in post 1. Everything went fine, but after the Galaxy S4 boot screen, it goes black and stays. I can boot to download mode and stock recovery, so it's not a major issue, and likely something I did. I'll mess with it a bit more then Odin back to stock and start over.
Click to expand...
Click to collapse
A couple questions:
What firmware were you coming from?
How long did you wait?
Did you have Xposed enabled?

Downgrade AT&T Samsung Galaxy S5 G900A from 5.0 to 4.4.2/4.4.4

Few days ago I bought the Samsung Galaxy S5 G900A unlocked. There was Android 5.0 preinstalled whith baseband vOC4! I tried to make the downgrade to 4.4.2 because of the root, and always gettin the brick. Saw the post about flasjing G900A_OC4_Stock_Partitions and it helped me a lot with unbricking! I tried all the ways of downgrades: recovery ZIP update (including OC4 firmware w/ OA1 bootloader) , ODIN flashing different stock roms, custom roms, kernels etc. Can I make a downgrade with that baseband? I've read somewhere that it's impossible to do in this case...
Really confused now after all this.

No need for confusion. There is no way known to humanity that will allow you to downgrade from 5.0 to anything else.
Sent from my SAMSUNG-SM-G900A using Tapatalk

RK said:
No need for confusion. There is no way known to humanity that will allow you to downgrade from 5.0 to anything else.
Sent from my SAMSUNG-SM-G900A using Tapatalk
Click to expand...
Click to collapse
Ah, that's a shame..... Any chances of developing the 5.0 root for g900a?

Im in the same situation let me know if anything changes im about to return mine and hopefully get one still on kitkat or get a tmobile version
Sent from my SAMSUNG-SGH-I537 using XDA Free mobile app

ODIN back to OC4 to unbrick and remember; if you can't root you, can't do anything but wait for root or buy a different model phone.

ODIN back to OC4?
There is no way at this time to ODIN back to OC4, OA1, or whatever.
There is only a ".exe" file for OC4.
https://drive.google.com/file/d/0B2QQ1ShKpLTtYjU0aDJCLVFFSFk/view

similar situation
Hello guys,
my situation is quite similar to the posters one. i've bought the S5 active (AT&T) with some custom TMS5 rom, when i boot i sie unlocked lock icon.
the version is 5.0: the kies is showing info like: G900FXXU1BOC7/G900AATT3BOC4/G870AUCU1BOC5/G900FXXU1BOC7 (ATT)
the question is can i get somehow to the STOCK firmware? maybe upgrading to the 5.1.1 will get rid of this "custom stuff"?
if so, what's the best way to do it?

I purchased a new G870A Galaxy S5 Active this week, which was preloaded with OC5 (5.0, Lollipop) firmware. I was able to root the device by downgrading to 4.4.2; the guide here was very helpful: http://www.droidviews.com/update-att-galaxy-s5-active-to-lollipop-root-it-and-enable-wifi-tethering/
The exact procedure I used:
1. Flash NE4 firmware with Odin (The latest heimdall from git didn't work; I had to boot Windows 7 and install Odin & Samsung USB drivers)
2. Reboot the phone in recovery (power+volume up+home). Use the options to clear cache & reset to factory default
3. Reboot the phone normally. It might appear bricked & take up to 5 minutes to get past the AT&T logo.
4. Root with Towelroot
5. Follow the instructions on the linked page to install pre-rooted OF3 (Lollipop) firmware and the OC5 bootloader.
6 (important). Kill OTA updates by renaming /etc/security/otacerts.zip & /system/priv-app/wssyncmldm and then rebooting. Delete anything in /data/fota for good measure. (Use your favorite root-enabled file explorer or shell.)
Note that this will not work if the phone has received OTA updates beyond OC5. See this thread: http://forum.xda-developers.com/att...w-to-update-to-g870aoc5-5-0-keeproot-t3083841

Update to newest os

I am looking to update to lollipop but I can not use the built in updater because im on cricket and not ATT.
Can anyone help me with a guide or a safe way I can get the update? Please and thank you

Trem Fantasma said:
I am looking to update to lollipop but I can not use the built in updater because im on cricket and not ATT.
Can anyone help me with a guide or a safe way I can get the update? Please and thank you
Click to expand...
Click to collapse
Is your phone the SGH-i537 (AT&T USA version) or the GT-i9295 (international version)? If it's the former I can most likely give you the file you need, but I'd need to know what firmware version you're currently on: settings > about device > baseband version. If it's the latter I can still probably point you in the right direction.
Oh, also, if you do have the i537 let me know if you're rooted or not currently and if you wish to be rooted once on lollipop

I have the SGH-i537 one and i am at I537UCUCNE3 4.4.2

Trem Fantasma said:
I have the SGH-i537 one and i am at I537UCUCNE3 4.4.2
Click to expand...
Click to collapse
If you just want to update and don't want root (and aren't already rooted), download this file and save to your external SD card (not internal storage):
https://www.androidfilehost.com/?fid=24052804347793671
Power your phone off. Boot into stock recovery (hold vol+ and power), choose install update from external storage, and navigate to where you saved that file and select it. It will probably take up to five minutes to install, so make sure you have plenty of battery (50%+)
When that is finished, repeat the exact same process with the following file (it's the version of lollipop with the stagefright patch, i.e. an important security fix), but has to be installed after the preceding file:
https://www.androidfilehost.com/?fid=24052804347793660
If you're already rooted, the above process will not work. Even if you're not already rooted, but think you might want to be once on lollipop, there is no way to root lollipop directly, so a different update method is required. If you're at all thinking about messing around with root, and especially if you are already rooted, you need to use the following method to update:
http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355

Thank you so much

SM-N920R6 Firmware anyone?

Attempted to root, no rooted kernels currently working for this model. now attempting to get back to stock. Anyone seen the SM-N920R6 firmware?

try rooting it with kernel for the n920p model. that worked for me

Mr.niceguy09 said:
try rooting it with kernel for the n920p model. that worked for me
Click to expand...
Click to collapse
Does this really work? for the n920r6?

DEATHoWAR said:
Does this really work? for the n920r6?
Click to expand...
Click to collapse
It worked for me. Be very careful tho. once you root it, you can,t go back since there is no stock firmware for these model.

Mr.niceguy09 said:
It worked for me. Be very careful tho. once you root it, you can,t go back since there is no stock firmware for these model.
Click to expand...
Click to collapse
Why did your phone throw the custom binary by frp lock? Did you do OEM unlock first?
Sent from my SM-N920R6 using XDA-Developers mobile app

SM-N920R6 stock firmware
I grabbed firmware for the SM-920R6 from SmartSwitch so I can probably help you out. I know how you feel, it's sad how hard it is to find anything for this phone! If you need the firmware I'll have to upload it to google drive or something this evening...

Successful un-brick and root of SM-N920R6
Using the software SamFirm and manually entering in all of the information for my phone I was able to download the correct SM-N920R6 firmware.
Here is what I had to type in the SamFirm program:
Model: SM-N920R6
Region: LRA (This really isn't a "region" it's a sales code which is why it took me forever to figure out - it can be found in System/csc/customer.xml but will be the same for all Cellcom customers)
*SELECT MANUAL CHECK BOX AND ENTER THE FOLLOWING*
PDA: N920R6WWU1BPD3
CSC: N920R6LRA1BPD3
Phone: N920R6WWU1BPD3
***MAKE SURE YOU CLICK "Decrypt automatically" (check box on right side) before you download so you get the usable zip file as well (you won't need the .enc4 file it also downloads (that is the original encrypted file)).
***You'll also want to click the "Check Update" button before downloading the firmware, but you'll get the prompt to do this by the SamFirm program.
Once you have the firmware unzipped just place it in the "AP" section on the Odin program, hit start, and you're all set!
Happy un-bricking, Cellcom customers!!
Note: After your phone reboots with the stock firmware if it hangs on the screen that has a Samsung logo dimming in and out just reboot into download mode (hold power, volume down, and home button simultaneously), and then restart the phone from the download mode menu (i.e. don't go to "continue" on the download mode screen). I tried the above recovery method a few times and it only hung on this screen once, but I was able to get out of it using the method I just described without issue.
**********************CONTINUE READING**************************
If you were frantically looking for the firmware as I was you may be telling yourself, "I'm never going to try to root this thing again!" But wait! You now have the ultimate "Un-rooting" tool at your disposal (the stock firmware!).
That being said I went further in search of achieving a successful root and..was successful! (The root achieved was using CF Auto Root which leaves the stock firmware alone. Unfortunately no custom kernels exist as of this post for this phone so this is as best we can do at the moment.
I used the file "CF-Auto-Root-nobleltespr-nobleltespr-smn920p.tar.md5" (as users pointed out above to start this thread - the "p" version works for the SM-N920R6). You just need to download that file and flash it the same way as you flashed the firmware (i.e. put it in the "AP" section of Odin and hit start. It takes a few minutes and after it's done showing all of its text as it installs the program on your phone your phone will have a black screen - don't worry it just needs to be turned on and you're rooted!

mcfasa09 said:
The root achieved was using CF Auto Root which leaves the stock firmware alone. Unfortunately no custom kernels exist as of this post for this phone so this is as best we can do at the moment.
I used the file "CF-Auto-Root-nobleltespr-nobleltespr-smn920p.tar.md5" ...
Click to expand...
Click to collapse
This trips knox, right? Can you still use Samsung Pay?

It does trip KNOX and as a result you cannot use Samsung Pay on the device (Even if you flash stock back Samsung Pay will forever be disabled on the device).

Its been a week since i got my note 5 sm-n920r6 , the person i bought it from told me to of a issue with it. He told me ever since update to naugat 7.0 the back button stop working so am seeking from anyone who can help me to get marshmallow 6.0 to downgrade to 6.0, please.
If someone who might still be on 6.0 on their note 5 SM-N920R6 can extract it from their phone or other means ,it would truly appreciated.
I use the samfirm to get the 7.0 firmware so i could flash to stock when i want, here is a link of the firmware for the SM-N920R6 if anyone might want it: https://mega.nz/#!IJYFEa5T
To access the firmware use this key: !e94lEjxPChsStdqniA2R6DwPe0s3bgvdDvvOLHmtRlM

desmond462 said:
Its been a week since i got my note 5 sm-n920r6 , the person i bought it from told me to of a issue with it. He told me ever since update to naugat 7.0 the back button stop working so am seeking from anyone who can help me to get marshmallow 6.0 to downgrade to 6.0, please.
If someone who might still be on 6.0 on their note 5 SM-N920R6 can extract it from their phone or other means ,it would truly appreciated.
I use the samfirm to get the 7.0 firmware so i could flash to stock when i want, here is a link of the firmware for the SM-N920R6 if anyone might want it: https://mega.nz/#!IJYFEa5T
To access the firmware use this key: !e94lEjxPChsStdqniA2R6DwPe0s3bgvdDvvOLHmtRlM
Click to expand...
Click to collapse
Does SamFirm trip knox? I hate being stuck on Marshmallow

aXnumeric said:
Does SamFirm trip knox? I hate being stuck on Marshmallow
Click to expand...
Click to collapse
I cannot say because i didn't notice whether it was trip or not, not that it bother me if it did. But i did manage to find the marshmallow firmware and flash back to marshmallow from naugat successfully, even though it didn't fix back button and now am back on naugat firmware.
---------- Post added at 04:02 AM ---------- Previous post was at 03:48 AM ----------
For those of us who are using this model N920R6 , i have being able to flash custom roms from the Sprint section without any issues. When i flash custom roms for other models i find i must flash the twisted kernel v2 for sprint model or your own stock kernel but even with that i have no data, so i don;t use those roms. But as for the sprint custom roms they run faultless with normal bugs that might be in a custom roms.
At first when i get this model i was piss because their is actually no support for this model until i try the sprint custom roms,it was awesome and now bit more happy.