Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
komninoskom said:
Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
Click to expand...
Click to collapse
Have you tried flashing a imei/baseband repair file
maybe your phone's baseband IC (hardware) was damaged, same like me after splashed by rain
Allehandro said:
Have you tried flashing a imei/baseband repair file
Click to expand...
Click to collapse
What is that file?
komninoskom said:
What is that file?
Click to expand...
Click to collapse
Since a certain firmware version, the IMEI just disappeared...I thought it was a bug in the firmware. There was a file that fixes it
Allehandro said:
Since a certain firmware version, the IMEI just disappeared...I thought it was a bug in the firmware. There was a file that fixes it
Click to expand...
Click to collapse
i try that file but nothing works
Jayke770 said:
i try that file but nothing works
Click to expand...
Click to collapse
Yeah I've heard from others that it didn't wirk for them but it works for me. New firmware versions from Samsung still don't fix the issue but I use the file and it always works
Allehandro said:
Yeah I've heard from others that it didn't wirk for them but it works for me. New firmware versions from Samsung still don't fix the issue but I use the file and it always works
Click to expand...
Click to collapse
it works because your binary is U1 not U2
Jayke770 said:
it works because your binary is U1 not U2
Click to expand...
Click to collapse
Yeah that's what I heard others saying...don't know what it means though
The firmware loses its baseband version from around the July update
anyone know where the file can be found?
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
But this person (I founded in Samsung Community) he updates his A12 to binary 2, and the signal is working, and no bug after he updates his A12
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
I'm on binary 2 now, cant downgrade or anything so basically goodbye to my phone.
At least for now is there a way to make phone don't shutdown because of missing imei/baseband?
Jerffelly said:
I'm on binary 2 now, cant downgrade or anything so basically goodbye to my phone.
At least for now is there a way to make phone don't shutdown because of missing imei/baseband?
Click to expand...
Click to collapse
Did you fix it now because mine has also the problem after i update to u2 version febuary update
Sheepmister said:
Did you fix it now because mine has also the problem after i update to u2 version febuary update
Click to expand...
Click to collapse
not yet.
Holidi16 said:
But this person (I founded in Samsung Community) he updates his A12 to binary 2, and the signal is working, and no bug after he updates his A12
Click to expand...
Click to collapse
Knox 0x0 this problem is for now in 0x1 devices
MauriJ2001 said:
Knox 0x0 this problem is for now in 0x1 devices
Click to expand...
Click to collapse
Ooh I see
MauriJ2001 said:
Unfortunately is a common problem on MTK Ax2 Family phones I see in the Argentinian samsung forum's and the galaxy A32 has the same problem once you trip the Knox warranty all newer firmware updates whit the secure by Knox splash will not get signal anymore (Baseband corruption idk) and the another problem is the binary once you update to binary 2 say bye bye to your signal (for now if some can patch this bug)
Click to expand...
Click to collapse
It's actually because rooting said phones with certain MTK chipsets, it's been around since 2020.
Deleted member 12039295 said:
Hello after rooting my device i seem to have lost imei on both slots.Baseband version says unknown i tried some threads i found on the xda site but no luck.Also i removed rooting/relocked bootloader and reflashed latest firmware for my device nothing seems to work.
Click to expand...
Click to collapse
knox_warrenty_void at 0x1 means warrenty is voided. 0x0 means enabled which then translates to warrenty is valid. 0x1 switched on because of running custom firmware (you're magisk modifications).
Issue that you are expiriencing is pretty normal and is pritty much nothing new. Can you provide some info on what firmware are you running and what method of rooting have you followed. I would recommend to grab the "IMEI repair file" which you can find on the forum (works as a modem file). Either do that or downgrade to a older firmware version, to something more stable like BUF9. I've made planty of guides and threads where I have allready explained all of this.
If none of what I've said has worked for you, be sure to ask furter questions without any fear xD.
Have a good day,
Krypton
LAST_krypton said:
knox_warrenty_void at 0x1 means warrenty is voided. 0x0 means enabled which then translates to warrenty is valid. 0x1 switched on because of running custom firmware (you're magisk modifications).
Issue that you are expiriencing is pretty normal and is pritty much nothing new. Can you provide some info on what firmware are you running and what method of rooting have you followed. I would recommend to grab the "IMEI repair file" which you can find on the forum (works as a modem file). Either do that or downgrade to a older firmware version, to something more stable like BUF9. I've made planty of guides and threads where I have allready explained all of this.
If none of what I've said has worked for you, be sure to ask furter questions without any fear xD.
Have a good day,
Krypton
Click to expand...
Click to collapse
I used to use the IMEI repair file but when I was flashing the new BVE3 Firmware, I got an error "SECURE CHECK FAIL: md1img.img" "SECURITY ERROR. THE PHONE HAS BEEN FLASHED WITH UNAUTHORISED FIRMWARE AND IS LOCKED"
I think it's because of the U2 Binary, so now I can't downgrade to BUF9 since it's U1. So now IMEI is missing and the only fix is to delete the NVD_IMEI folder which requires root. I am unable to root my device since the OEM Unlock option is missing from the developer options and I can't login to my samsung account as I get a meesage "IMEI(or MEID) is empty". So I don't know how to get the OEM Unlock option to show so I can root the device and use the NVD_IMEI Fix
Related
Hello!
I just bought my new tablet and I wanted to make sure I have latest version for my device, but I got a message saying that my device has been modified, ok so then I installed kies and it told me I had the latest version avaliable, then I went into download mode and I saw system status:Custom, I tried to wipe both partitions but still the same problem.... I bought this tablet today feels very strange that my system is custom. On my note 3 it is says official
Are you using a MicroSD? If yes, take it out, then reboot and check again. It's a known bug.
Same on mine. No micro sd rebooted many times
Sent from my SM-P905 using Tapatalk
If you rooted you've tripped the knox security sistem and samsung won't update a rooted device. At least that's what Ithink happened on my device...
alexan92 said:
Hello!
I just bought my new tablet and I wanted to make sure I have latest version for my device, but I got a message saying that my device has been modified, ok so then I installed kies and it told me I had the latest version avaliable, then I went into download mode and I saw system status:Custom, I tried to wipe both partitions but still the same problem.... I bought this tablet today feels very strange that my system is custom. On my note 3 it is says official
Click to expand...
Click to collapse
ShadowLea said:
Are you using a MicroSD? If yes, take it out, then reboot and check again. It's a known bug.
Click to expand...
Click to collapse
Hello
I have the same problem. Is custom but Knox is 0x0. I try everything, including Odin, but NO result. In Odin don't start the process, in Kies it shows that is the last firmware, and OTA "the device is modified".
This is a common issue with the SM P905 variant, I had the same problem myself. The only way to sort it out is to send it to Samsung for repairs or take it in to a service centre. I'm pretty sure all they'll be doing is reflashing the firmware but you might not want to void the warranty by doing it yourself.
FreshlyBrewed said:
This is a common issue with the SM P905 variant, I had the same problem myself. The only way to sort it out is to send it to Samsung for repairs or take it in to a service centre. I'm pretty sure all they'll be doing is reflashing the firmware but you might not want to void the warranty by doing it yourself.
Click to expand...
Click to collapse
sorinin said:
Hello
I have the same problem. Is custom but Knox is 0x0. I try everything, including Odin, but NO result. In Odin don't start the process, in Kies it shows that is the last firmware, and OTA "the device is modified".
Click to expand...
Click to collapse
Hello
I solve the problem by using another laptop with WinXP. But please make an IMEI backup. I don't make it, and now my IMEI is /01 and I don't have Phone acces. ..
Now is possible to use my computer (Odin). I make update at last BIOS for my laptop. But still I can not find my IMEI, and in this way can't use the phone...
sorinin said:
Now is possible to use my computer (Odin). I make update at last BIOS for my laptop. But still I can not find my IMEI, and in this way can't use the phone...
Click to expand...
Click to collapse
Wait simply for the update via KIES or OTA. It will be available soon or is still available for a lot of countries.
Status will pass from modified to Official.
check this thread : http://forum.xda-developers.com/showthread.php?t=2710004
Hi,
You first have to check if this particular update (not the stability update BUT this "modified status bug" update is available for your country.
Check it here http://live.samsung-updates.com/inde...device=SM-P905
Have a good Sunday.
Fabien
cracou111 said:
Wait simply for the update via KIES or OTA. It will be available soon or is still available for a lot of countries.
Status will pass from modified to Official.
check this thread : http://forum.xda-developers.com/showthread.php?t=2710004
Hi,
You first have to check if this particular update (not the stability update BUT this "modified status bug" update is available for your country.
Check it here http://live.samsung-updates.com/inde...device=SM-P905
Have a good Sunday.
Fabien
Click to expand...
Click to collapse
No Problem with mine SM-P905
i have a galaxy s6 (SM-G920F)and it failed in an update and got stuck in a bootloop,i tried reflashing stock rom (6.0.1),ive tried smartswitch but nothing is working I cant get into recovery either,when I tried reflashing stock rom with odin it came up with sw rev check fail device 5 binary 4,any ideas what this means? as far as I can tell its a bootloader problem
god1980 said:
i have a galaxy s6 (SM-G920F)and it failed in an update and got stuck in a bootloop,i tried reflashing stock rom (6.0.1),ive tried smartswitch but nothing is working I cant get into recovery either,when I tried reflashing stock rom with odin it came up with sw rev check fail device 5 binary 4,any ideas what this means? as far as I can tell its a bootloader problem
Click to expand...
Click to collapse
Use smartswitch emergency recovery , samsung have put in place some issues with the Bootloader, moreso if you're on a newer bootloader then you cannot install a firmware which has a lower bootloader
sofir786 said:
Use smartswitch emergency recovery , samsung have put in place some issues with the Bootloader, moreso if you're on a newer bootloader then you cannot install a firmware which has a lower bootloader
Click to expand...
Click to collapse
ive tried smartswitch and it just says SM-G920F does not support initialization please contact customer services
same problem here, any luck finding a solution?
god1980 said:
ive tried smartswitch and it just says SM-G920F does not support initialization please contact customer services
Click to expand...
Click to collapse
When you downloaded your firmware for odin, was it the very newest update? Or an old one, I've noticed some older firmwares fail to flash due to being on a newer bootloader
bogdanserban said:
same problem here, any luck finding a solution?
Click to expand...
Click to collapse
I have same issue, all the stock software out there seem to be dated where can I new stock firmware? I have Samsung S 6 from tmobile SM-G920T1.
This is my problem:
device: galaxy s6 edge tmobile
system status: custom
sw rev. check fail. device:5, binary: 2
what should I do?
i solved same problem. Just flash full nougat 7.0 via odin, don't flash MM 6.0.1.
rezstrk said:
i solved same problem. Just flash full nougat 7.0 via odin, don't flash MM 6.0.1.
Click to expand...
Click to collapse
from where to download?
dohcvtec said:
from where to download?
Click to expand...
Click to collapse
here! have fun!
For 920F
https://drive.google.com/file/d/0B0b2ginGifb-U2VzdUtzRmJTYm8/view
rezstrk said:
here! have fun!
https://drive.google.com/file/d/0B0b2ginGifb-U2VzdUtzRmJTYm8/view
Click to expand...
Click to collapse
thanks. I'll get back to you and let you know what happened. thanks again!
dohcvtec said:
thanks. I'll get back to you and let you know what happened. thanks again!
Click to expand...
Click to collapse
I also had the same issue on SW REV DEVICE 5 BINARY 4
I downloaded the Nougat 7.0 United Kingdom/Ireland and flashed using Odin and now my S6 is up and running. You can try it too.
I had tried other versions with no success.
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
dohcvtec said:
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
Click to expand...
Click to collapse
Yo, did you get it fixed? My phone for tmobile cant get passed flashing
vandres1975 said:
Yo, did you get it fixed? My phone for tmobile cant get passed flashing
Click to expand...
Click to collapse
Hey, nope. Didn't manage to get passed it. Nothing so far. Really looking for some help on that issue but no luck so far. If I come up with a solution, I will post it here.
Dang that sucks, idk what I'm going to do to unbrick it.
dohcvtec said:
Hey, nope. Didn't manage to get passed it. Nothing so far. Really looking for some help on that issue but no luck so far. If I come up with a solution, I will post it here.
Click to expand...
Click to collapse
Hey, so I have the bootloader problem too and I think we have to wait for the nougat update for the type of phone you have. I have a galaxy s6 tmobile so I think I have to get nougat and flash that when it comes out for tmobile. You have to do the same I think but for now Im gonna send it to samsung and act dumb. Hopefully maybe they fix it and send it back. Do you think they will accept my phone though? It was rooted and had nemesis rom. for nougat port from s7 edge. Also current binary is: Samsung Official. System Status is: Custom. They can see knox is tripped since the counter is void: 1.
vandres1975 said:
Hey, so I have the bootloader problem too and I think we have to wait for the nougat update for the type of phone you have. I have a galaxy s6 tmobile so I think I have to get nougat and flash that when it comes out for tmobile. You have to do the same I think but for now Im gonna send it to samsung and act dumb. Hopefully maybe they fix it and send it back. Do you think they will accept my phone though? It was rooted and had nemesis rom. for nougat port from s7 edge. Also current binary is: Samsung Official. System Status is: Custom. They can see knox is tripped since the counter is void: 1.
Click to expand...
Click to collapse
Hey, it depends if you have warranty on the phone or not. If you have warranty, it will not cover your expenses because it's void after unlocking bootloader and rooting. If you don't have warranty and you are paying them anyways, they should have no trouble accepting it. Who would deny taking money. I hope they can fix it for you and I'm sorry we couldn't figure out how to. What you said about Nougat is true. I have checked that information as well. There is no Nougat for TMobile yet. We just have to wait. Again, in the mean time if I fix it, I will post my solution here.
dohcvtec said:
Hey, it depends if you have warranty on the phone or not. If you have warranty, it will not cover your expenses because it's void after unlocking bootloader and rooting. If you don't have warranty and you are paying them anyways, they should have no trouble accepting it. Who would deny taking money. I hope they can fix it for you and I'm sorry we couldn't figure out how to. What you said about Nougat is true. I have checked that information as well. There is no Nougat for TMobile yet. We just have to wait. Again, in the mean time if I fix it, I will post my solution here.
Click to expand...
Click to collapse
Alright.
dohcvtec said:
Do you know wjere I can find Nougat for s6 edge, USA T-Mobile? Thanks
Click to expand...
Click to collapse
Try the first one from the top from here http://updato.com/firmware-archive-select-model?q=sm+g920t&exact=1
with Odin v3.12.3
Hi guys, I bought a Vodafone-branded unlocked S7 here in Ireland.
Never used it with Vodafone and I've never received any updates for it.
OTA, Smart switch and Updato they all say my device is up to date but I can see there are more recent firmwares for my CSC.
Here are my details:
PDA: G930FXXU1DQEI
CSC Version: G930FVFG1DQE3
BASEBAND Version: G930FXXU1BPJJ
CSC Code: VDI
Am I missing something or is it possible that under VDI there are more update channels and my phone is not supposed to receive the other updates?
It's working fine and everything, I'm only concerned about security patches to be honest.
Hope you can give me a hint.
Cheers guys.
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
*Detection* said:
Boot into download mode and double check it is definitely the G930F
If it is, then just flash the latest firmware with ODIN 3.12.3 or newer
Click to expand...
Click to collapse
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
alediaferia said:
It is definitely G930F. Would I be safe using HOME_CSC in order not to lose any data?
Also would you have any idea on why this is happening?
Thanks!
Click to expand...
Click to collapse
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
*Detection* said:
If the device is showing as "Custom" system status it won't OTA
Otherwise no idea, and yes just use HOME_CSC, it'll update it as if you got an OTA
Click to expand...
Click to collapse
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
alediaferia said:
Thanks for your help. I guess I'll end up flashing the firmware manually. System status is showing as original BTW.
Any chance I might have screwed up accidentally denying an update once and losing the "updateability" of my device forever? Although it's weird Updato is detecting my device as up-to-date too. This story is really weird to me.
Thanks again anyway!
Click to expand...
Click to collapse
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
*Detection* said:
Actually it's usually the other way around, people trying to deny the updates and asking for help to permanently disable them, so it's unlikely you broke it
Possibly just a bug of some sort, or the firmware you think you are on is not the actual firmware?
What security patch does it state in settings > about > software info > scroll to bottom
The updato app is getting extremely bad reviews lately so I wouldn't trust that anyway
A lot of people update manually, this isn't the first case I've seen with your problem either so I wouldn't worry too much, just flash it yourself
Click to expand...
Click to collapse
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
alediaferia said:
Security patch level is May 2017.
The firmware the phone says I'm on in the software update section reconciles with what Phone INFO detects which is the firmware released for VDI the 2017-06-11 on sammobile.
Click to expand...
Click to collapse
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
*Detection* said:
Yea definitely a strange one, should be seeing an update
Could be anything though, some change within the OS that's not reporting something to the update servers correctly
The flash should fix it, if not, backup and factory reset for the next OTA, or just keep flashing manually
Click to expand...
Click to collapse
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
alediaferia said:
Sorry for going back to this. I just want to clarify another doubt I have. My phone is Vodafone-branded but I've always used it with another carrier. Is this affecting my ability to receive either OTA or updates at all using smart switch ?
Thanks!
Click to expand...
Click to collapse
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Aashish.007 said:
You can test this by borrowing a Vodafone sim.
Or better just backup and flash an unlocked stock Rom to your device.
Click to expand...
Click to collapse
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
I guess if the boot loader is unlocked then you're good to go.
---------- Post added at 10:14 PM ---------- Previous post was at 10:11 PM ----------
alediaferia said:
Hi, I'm finding it hard to get someone with a Vodafone sim. Anyway, do I risk anything flashing an unbranded firmware? Knox tripping, custom status showing up or other not-so-nice things ?
Click to expand...
Click to collapse
And Stock firmware won't trip Knox.
For the sake of completeness, I have explained my solution in here: https://forum.xda-developers.com/galaxy-s7/help/wrong-modem-cp-version-t3743284
Thanks everyone for your help
If you own a Galaxy A7 (2018), open the Samsung Members app and go into the Notices section. A notice for the beta program should be in the list. Tap that, then use the Register button to enroll into the beta. Once you’ve registered, you should be able to download the first Pie beta from the
This is only for India. In Europe is not available for now.
Sent from my SM-A750FN using Tapatalk
When it will be released in Europe?
download File update please?
Any news about the camera quality? is it improved?
Life Companion said:
If you own a Galaxy A7 (2018), open the Samsung Members app and go into the Notices section. A notice for the beta program should be in the list. Tap that, then use the Register button to enroll into the beta. Once you’ve registered, you should be able to download the first Pie beta from the
Click to expand...
Click to collapse
Download file beta? for Odin?
Please
@Cronus @um009 @lifecompanion @suyash1629
andrea1402 said:
Download file beta? for Odin?
Please
@Cronus @um009 @lifecompanion @suyash1629
Click to expand...
Click to collapse
I'm unable to find its file at the moment, I think the only way is through Samsung Members app. However, I will try my best to find the file and post it as soon as I find it.
um009 said:
I'm unable to find its file at the moment, I think the only way is through Samsung Members app. However, I will try my best to find the file and post it as soon as I find it.
Click to expand...
Click to collapse
If you downloaded file using Samsung Update, it will be stored in root/data/fota folder
Erecik said:
If you downloaded file using Samsung Update, it will be stored in root/data/fota folder
Click to expand...
Click to collapse
Will get my hands on the phone and do this.
um009 said:
Will get my hands on the phone and do this.
Click to expand...
Click to collapse
thank you very much I look forward to you
Even if we have the ota file, it can be flashed via AP section of Odin and would it void warranty ?
Pr0Ankit said:
Even if we have the ota file, it can be flashed via AP section of Odin and would it void warranty ?
Click to expand...
Click to collapse
Most likely no because it's an update. But maybe it will be released as separate system installation with ODIN images. And flashing CUSTOM recovery (boot image too) will trip knox, flashing stock should be fine
Pr0Ankit said:
Even if we have the ota file, it can be flashed via AP section of Odin and would it void warranty ?
Click to expand...
Click to collapse
Update.zip file will be up asap..it can be flashed from stock recvry by sd card method..
Erecik said:
Most likely no because it's an update. But maybe it will be released as separate system installation with ODIN images. And flashing CUSTOM recovery (boot image too) will trip knox, flashing stock should be fine
Click to expand...
Click to collapse
I know that flashing custom recovery trips knox but will the beta image void the warranty ? I have flashed stock images using odin many times and never tripped knox but idk about beta images.
This ROM is only for India A750F and not for European A750FN so far.
I think as long as there is no European A750FN Pie version via Beta Programm, there won't be any flashable Roms as well !!!
If you have the pie update let us know if there is any improvement in the camera, cause right now it's a real let down. (Capture of any type of foliage turn into a color blob)
Can someone post this firmware for download?:fingers-crossed:
Yes
Pr0Ankit said:
Even if we have the ota file, it can be flashed via AP section of Odin and would it void warranty ?
Click to expand...
Click to collapse
I asked samsung care and they said it would. They said even flashing stock firmwares using sammobile or etc, will void the warranty, i.e. any kind of flashing will. I think its a little odd that It would void it, but if they said then its possible. And all this is for India, I don't know about any other countries' policies.
Yes they say it but as long as your knox is not tripped (which wont trip if you flash stock firmwares) you will get the warranty as long as you didnt mess upduring flashing.
Pr0Ankit said:
Yes they say it but as long as your knox is not tripped (which wont trip if you flash stock firmwares) you will get the warranty as long as you didnt mess upduring flashing.
Click to expand...
Click to collapse
Correct , only if Knox is tripped Samsung can and actually will refuse to repair phones with warranty taking over costs.
In EU this is kind of behavior is not supported by the jurisdiction, but Samsung charges you for everything that is normally covered up by warranty anyway, if you have Knox tripped, means custom bootloader installed once.
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
snaksalot said:
i got the latest security update via OTA and an now running the G930UUEU9CSA3 firmware, ive tried flashing the eng boot img i originally used to root from here "https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616" but odin fails every time, i'm pretty sure its because the new security update updated the bootloader also... to version 9. now i guess my question is are there any eng boot files for the v9 bootloader available yet? or any other usable root methods available?
Click to expand...
Click to collapse
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
kpwnApps said:
Get magisk.zip from internet , move to a sdcard insert sdcart to s7, Flash twrp for s7 then format data then click install magisk.zip reboot after finish and done.
Click to expand...
Click to collapse
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
cooltt said:
That wasn't very clever was it.
Should never update branded unless it's to fix a major bug. Any loophole which allows root or flash is closed on an update until someone figures out how to root on the new boot loader.
I think the best advice to anyone on US networks is to flash unbranded and go from there.
Click to expand...
Click to collapse
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
snaksalot said:
No it most definitely was not very clever at all and unfortunately I'm stuck : / Also is the G930UUEU9CSA3 firmware not unbranded?
Click to expand...
Click to collapse
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
cooltt said:
Yes it is I didn't read properly. Anyway what odin are you using to flash? The modified one?
We are talking about a qualcomm device yes?
Click to expand...
Click to collapse
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
snaksalot said:
Yes I'm using the modified Odin and all my previous attempts at flashing the eng boot files via Odin on the v8 bootloader have been successful, it wasn't until after the OTA that I started having issues.
And yes this is Qualcomm : )
Click to expand...
Click to collapse
Hmmm so it may be that loophole is now closed, what you need to think about is if you deffo need root? Or is it just nice to have. I'm sure a dev will get round it soon.
snaksalot said:
I'm fairly certain that the only twrp for the s7 is a temporary one because there is no unlock for the bootloader, and even still the temp twrp is only compatible with the v4 bootloader and I am currently on v9.... that is unless I'm mistaken if I am then please someone correct me and point me in the right direction because I'd love to be running magisk on my s7 : )
Click to expand...
Click to collapse
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
kpwnApps said:
Twrp will work certainly, i did on my own s7 qualcomm variant with this https://www.google.com/amp/s/forum....de-how-to-root-android-8-0-oreo-t3840271/amp/
Click to expand...
Click to collapse
Okay I was completely unaware of TWRP being an option or the possibility of Magisk with a locked bootloader, now to clarify I'm running the latest unbranded US Region firmware for the US T-Mobile version of the Qualcomm Galaxy S7 "(TMB) G930UUEU9CSA3" that being said I have a few questions about how to specifically to proceed if you don't mind helping me?
First is the version of Odin available from the post provided above inst the modified version I've been required to use for all my previous flashing "Odin3_v3.13.1_3B_PatcheD" should I use this one or the version provided in the post above "Odin3_v3.13.1"?
My next question is that all the different versions and variants of TWRP available for my device the Galaxy S7 and the S7 Edge are either for Exynos Canada/International or Korea or the Chinese Qualcomm variant of each. Should I download and use the TWRP for the Chinese Qualcomm S7?
The sammobile link in the original post for "Android 8.0 Oreo Stock Rom" provides me with a list of the latest and up to date international versions of firmware for the Galaxy S7 Edge "SM-G935FD" I'm assuming I should just use the stock firmware image for my device "SM-G930U" instead?
The link for the no-verity-opt-encrypt-6.0 is dead but I don't think its needed because of something someone said in the original post about this method failing after latest security update "the one I'm on" https://forum.xda-developers.com/showpost.php?p=78115895&postcount=18 he said he solved it easily with information and another flash able zip from this post https://forum.xda-developers.com/showpost.php?p=77000849&postcount=47 and the zip from here https://forum.xda-developers.com/showpost.php?p=76564735&postcount=37
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
snaksalot said:
All that being said I haven't attempted anything yet, I'll try the above method as I understand it later this evening and I'll post my results
Click to expand...
Click to collapse
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
I'd be interested to know how this turned out if the device with V9 bootloader could be rooted with temp TWRP method.
Can i actually flash magisk on my 930u?
Is there any way to root my g930t ?
I'm on v9 bootloader, and i don't care about knox tripping.
Did developpers really failed to break the security of this little old device ? Or no one worked it ?
cooltt said:
Hello there, i deleted most of your post because i didn't want my post to be huge. So if i just give you some guidelines hopefully you can have a look around for the files you need.
1. For Qualcomm / snapdragon devices you must always use the patched version of Odin you already have. Now this version of Odin can be dangerous if you don't flash the correct firmware for your device because it ignores device mismatch and other safety measures the normal Odin checks for before flashing. Which brings me to.....
2. Anything for G935 will not work for G930 including TWRP, you must always use firmware, patches twrp which specifically says it for G930 Qualcomm/snapdragon devices.
3. The China/ Korea Qualcomm/snapdragon devices are exactly the same as the US devices, anything working on the China / Korea devices will work on the US device.
Now i know you want to root unbranded on V9 but as you are on the T Mobile network it may be easier to flash and root T Mobile Oreo for the time being until there is a workaround root for V9 unbranded.
All of the threads you linked to were for G935 devices and i've mentioned you can't use those patches BUT the process and step by step instructions you follow are the same for your device. So you can follow those guides as long as you are using the patches for your device.
There is a Snapdragon section on this forum so thats a good place to look.
I've had a quick look for this specific firmware and can't find anything about rooting the U9 version yet.....
I'm just checking this firmware G930UUEU9CSA3 your running did have either XAA or USC code next to it when you downloaded? I've noticed Verizon, AT&T and Sprint are using the same firmware VZN, ATT, XAS.
Click to expand...
Click to collapse
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Toolmighty said:
Would this info be applicable to edge models as well? Pretty sure our moderator has moved on as he is disgusted with samsungs persistance in blocking root with new bl versions. Im on an unlocked tmo s7 edge with the u firmware as well.
Click to expand...
Click to collapse
Yes same hardware
cooltt said:
Yes same hardware
Click to expand...
Click to collapse
Can't get twrp to flash. Tried w rom as is, tried factory reset tried reinstall w/o auto reboot. All get same error
what about jruze root?
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
nm it uses flashfire
Toolmighty said:
what about https://forum.xda-developers.com/verizon-s7-edge/how-to/root-s7-s7edge-oreo-nougat-t3819616 then flash from safestrap, format data, decript script?
Click to expand...
Click to collapse
Yes by using 1st and #1623 post number it can be rooted easily. I already have done that on both G930P and G930U.