So im wondering if im on nk4 firmware (bootloader and all), and flash the prev Ne5 firmware via odin (bootloader and all) i will definitely brick rule still applies, becuase im coming from a gs3, and that's how it was(becuase of knox and all), hopefully you guys know what I'm trying to say i don't know if knox changed but hopefully you guys can help me
It's safe to switch between bootloaders on the G900p Sprint S5.
Related
I have a 920W8 S6 originally from Bell but unlocked and being used on FIDO. It is currently running 5.1.1 Stock Bell firmware I recieved an update notification for 6.0.1 from bell, however after unlocking the phone and inserting my FIDO simcard the update no longer appears. I downloaded the new 6.0.1 Stock FIDO firmware from sammobile, would flashing this via Odin trip KNOX? Would switching from Bell -> Fido stock FW trip KNOX? I keep reading conflicting advice online about whether or not flashing stock carrier firmware is safe. Also is there any way I can tell for sure if the image I downloaded from sammobile is signed?
Thanks!
No, It won't.
thanks! Also does Odin do any checks if the image is signed or not? If not, is there any way I can be sure it wasn't tampered with?
Use firmware from Sammobile and compare Md5 Sig
No it won't trip knox.
After you install 6.0.1 don't forget to do a factory reset to clear out all the bugs during update. I mean its not necessary but good practice when upgrading firmwares. Data will be erased!
I'm thinking no, but wondering if it is OK to flash a stock Odin fw that is different from the device's carrier? Has anyone tried this? From what I recall from other Samsung devices, worst case is it would fail but not brick the phone. But still want to see if there's any feedback for this phone.
Have a SM-N915V here (SIM unlocked) in Canada and would like to flash a Rogers stock fw onto it if possible.
I guess NO
Reason : both the device have different partitions(that is the only thing i guess). if partitions can be matched it can be tried as hardware is more or less same.
Still i would suggest take a full Nandroid backup including the efs, and flash the firmware, even if you brick you can recover.
Thanks. I assume this is where .PIT's come in - but I understand the danger of force-flashing a PIT of one model to another model. Too scared to brick. Will stick with Verizon firmware ;D
I'm still on Bootloader 2. I can freely flash between G930P PE1, G930V PF2, and G930U PEH.
Would G930T PG1 be a good option? If not, what would you recommend?
T-mobile detected I was rooted and on an unknown firmware (Echoe), and there's several network issues here and if I want their Engineering team to investigate, I need to go back to stock and confirm root doesn't conflict with service.
edit: After further research, it appears the lowest T-mobile bootloader version is 3?
I recently received a T-Mobile Galaxy S6, and it was rooted and had a custom kernel, which was a complete mess (the person who owned the phone previously clearly did not know what they were doing) so I just wanted to restore it back to full stock.
I am decently experienced with ODIN, rooting, custom firmware etc, but I have just done one of the biggest rookie mistakes I have ever done. I had accidentally downloaded the most recent firmware for my G920T, not realizing that the file was not for T-Mobile. It was the (XAR) carrier (I believe that is C-Spire but i could be wrong) and the latest was PK1.
It flashed perfectly and all seemed fine until I decided to unlock the device. The T-Mobile S6 requires the use of the "Device Unlock" app and since I had flashed the wrong ROM, the phone thinks the Device Unlock app is not compatible. When I put a different GSM SIM card in the phone, it prompts me to use the Device Unlock app.
I do not have a previous NANDROID backup from the original T-Mobile ROM, and now that I am on the lastest Bootloader for XAR, it will not let me downgrade. I have tried flashing pretty much every MM bootloader and TWRP for both T-Mobile and XAR and none will work (except for what is currently on the device of course) I always get the error "Device: 5 Binary: 4" (sometimes the binary is 3, depending on which version of MM rom or BL I try)
To sum it all up, I am on PK1 (latest for XAR) and I need a way to get back to the official T-Mobile ROM (latest is PD1). Is there a magic method to get this figured out or am I pretty much stuck with what I got until T-Mobile releases an update that is PK1 or higher?
Thank you in advance to all of you that take your time to help (and I am sincerely sorry if I am posting in the wrong section)
So both my phone and vzw branded phone are same model, and android 11 firmware is out for verizon and my phone received the G715U1UEU7BUC3 ota 11. Is the latest Odin software and verizon G715USQU7BUC1 firmware what i need to get it done?
Also, do i need to do the full flash or can i get by with just one file that includes all the vzw bloatware. From what ive read i can get by with flashing just the userdata file. Once complete ive also read i need to do a factory reset and that it can be done i DL mode. Is that true? Finally can i leave my sim in for this or should it be out
?
?
Anybody??
Not even a response from Europe where they must hand these xcover pro's out with every gas tank fillup.
I have the latest version of odin installed and downloaded the verizon ota firmware G715USQU7BUC1 and am ready to give it a shot. I would just like a little confirmation im on the right track. Bootloader versions are the same. (bootloader is still locked) Even a grunt would do..........