• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

is close good enough

`I want to root my SM-G930V, but the software to root it is "built id NRD90M.G930VVRU4BQC5" and my phone is built id NRD90M.G930VVRU4BQA4. I'm just learning so I thought I would ask first. Thanx Guys
 
G930VVRU4BQA4 is the stock firmware for your phone (Verizon) released 3-27-17, G930VVRU4BQC5 is also for your phone and was released 4-25-17 so I would guess it's just the next security patch level. Do the instructions to root say you must match the patch level exactly? I would assume that if you are flashing the entire ROM with an insecure kernel to get root, then it should be okay in this case. If you want to proceed you should have a copy of the stock firmware on hand, just in case. https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/

Be advised I do not have that model phone and have never flashed a Verizon device. Remember that you do this at your own risk and that i cannot say for certain it will work.
 
G930VVRU4BQA4 is the stock firmware for your phone (Verizon) released 3-27-17, G930VVRU4BQC5 is also for your phone and was released 4-25-17 so I would guess it's just the next security patch level. Do the instructions to root say you must match the patch level exactly? I would assume that if you are flashing the entire ROM with an insecure kernel to get root, then it should be okay in this case. If you want to proceed you should have a copy of the stock firmware on hand, just in case. https://www.sammobile.com/firmwares/galaxy-s7/SM-G930V/

Be advised I do not have that model phone and have never flashed a Verizon device. Remember that you do this at your own risk and that i cannot say for certain it will work.

So I need to find the firmware that ends in the A4 flash that onto the phone then I can root safely, correct
 
Flashing a verizon device somewhat expert here, you have to find the correct firmwear to falsh it.
Still you could be i think a few coding off , and still works. Not so sure because I have not flashed in a full few years ago.
 
lol that's exactly the link I'm working off of

So I need to find the firmware that ends in the A4 flash that onto the phone then I can root safely, correct

According to what you said in your first post, your phone already has firmware A4 installed. So no, that is not correct. You need to install the one ending in C5 that lunatic59 linked you to.

I copied the following directly from the guide which answers the questions you've asked...

Code:
[*] Warning: The above tutorial only works for Android 7.0 with the built id NRD90M.G930VVRU4BQC5.
[*] If your device isn't running on the same built id NRD90M.G930VVRU4BQC5, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method.
 
According to what you said in your first post, your phone already has firmware A4 installed. So no, that is not correct. You need to install the one ending in C5 that lunatic59 linked you to.

I copied the following directly from the guide which answers the questions you've asked...

Code:
[*] Warning: The above tutorial only works for Android 7.0 with the built id NRD90M.G930VVRU4BQC5.
[*] If your device isn't running on the same built id NRD90M.G930VVRU4BQC5, then you need to download and flash the firmware based on the same build id then after try to root your device from the above method.
yes, I'm with you and on the same page, literately, if I got the two flipped I appoligize, I easily might have but knew I needed to flash to the theirs to match. Now this is where I get confused, I thought rooting was required to unlock the phone so you could change the firmware, chicken and egg thing. What am I missing
 
I thought rooting was required to unlock the phone so you could change the firmware, chicken and egg thing. What am I missing

No, you don't need to be rooted to flash stock firmware. You don't even need to be rooted to flash a custom rom. You do need to unlock the bootloader if you intend to flash a custom recovery like TWRP, but that's different and it's still not root (but sometimes you have to flash a custom recovery to install an insecure kernel to achieve root).

I sign in but when I go back to the link I'm signed out.

That's odd behavior. If you go to the home page for sammobile and you login, does it show you as logged in or not? Perhaps there is a confirmation email waiting for you that you missed?
 
No, you don't need to be rooted to flash stock firmware. You don't even need to be rooted to flash a custom rom. You do need to unlock the bootloader if you intend to flash a custom recovery like TWRP, but that's different and it's still not root (but sometimes you have to flash a custom recovery to install an insecure kernel to achieve root).



That's odd behavior. If you go to the home page for sammobile and you login, does it show you as logged in or not? Perhaps there is a confirmation email waiting for you that you missed?

First of all thanx for sticking with me. I think I solved the problem, I went ahead and updated the phone and when I checked the build presto it was an identical match for the firmware, Q5 and all. But alas, it failed me or more likely I failed the the phone or Odin something. Now before I tried the root I went into developer options and unlocked the OEM, turned on the USB bugging and I didn't disabled the secure boot in Settings> lock screen, because didn't find verbatim wording. Followed the direction and this happened...well there was stuff before but just before failure 3 lines above (you ask I'll give you all 20 lines) SingleDownload>recovery.img>cache.img.ext4>FAIL! (Auth)> >Complete(Write operation failed. it still boots fineIve tried it 3 times same result, what did I do wrong?
 
First of all thanx for sticking with me. I think I solved the problem, I went ahead and updated the phone and when I checked the build presto it was an identical match for the firmware, Q5 and all. But alas, it failed me or more likely I failed the the phone or Odin something. Now before I tried the root I went into developer options and unlocked the OEM, turned on the USB bugging and I didn't disabled the secure boot in Settings> lock screen, because didn't find verbatim wording. Followed the direction and this happened...well there was stuff before but just before failure 3 lines above (you ask I'll give you all 20 lines) SingleDownload>recovery.img>cache.img.ext4>FAIL! (Auth)> >Complete(Write operation failed. it still boots fineIve tried it 3 times same result, what did I do wrong?
It feels so close
 
First thing to try, with the phone booted and USB debugging enabled, plug the phone into your PC. You may get a security warning asking if it's okay for the devices to communicate. If you do, then accept it and try again. The other thing is to try a different USB cable/port on your PC. Samsung phones are notoriously fussy with USB connections.
 
First thing to try, with the phone booted and USB debugging enabled, plug the phone into your PC. You may get a security warning asking if it's okay for the devices to communicate. If you do, then accept it and try again. The other thing is to try a different USB cable/port on your PC. Samsung phones are notoriously fussy with USB connections.

I did reinstall the USB drivers just to cover bases, but negative on the communication, I get prompted with what do I want to do import...ect, on the phone I picked transfere software? I think it was called, something to do with update like, but not pictures or videos or charge and usb cord, trying now...amd dupicate fail. Odin recognizes the phone says Added
 
I did reinstall the USB drivers just to cover bases, but negative on the communication, I get prompted with what do I want to do import...ect, on the phone I picked transfere software? I think it was called, something to do with update like, but not pictures or videos or charge and usb cord, trying now...amd dupicate fail. Odin recognizes the phone says Added

even picked a different usb port
 
I don't think so. OTA update require 80% charge, but odin should work even with a low charge. It might be worth a shot to charge it up anyway.
 
Back
Top Bottom