I've read on another thread that to use hsdpa 1700 on an AT&T phone that you need to flash the baseband/radio from a Tmobile model. I've done something similar to this on the Note 3. Would I need to flash the whole firmware, seperate the radio from bootloader?
The reason I need to do this is because I am on Wind and the network isnt lte.
Tried flashing Tmobile modem. Stuck on AT&T logo now. Will restore stock when I find a computer without restrictions. I flashed with a modded CWM and there was no option to wipe cache. Multiple factory resets have not fixed it. Really loathing living in Canada right now.
This would prove almost impossible without a recovery.
How did/are you trying to install this?
TonyStark said:
This would prove almost impossible without a recovery.
How did/are you trying to install this?
Click to expand...
Click to collapse
There's a locked bootloader CWM somewhere. It was made for the Verizon model but worked on my AT&T. Backup and flashing was successful but clearing cache was not and unfortunately since it is locked bootloader it is one time use.
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 have korean S7 G930L, and are having some questions:
-(I'm NOT looking for troubleshooting, just want to know if anyone have the same problem) I still don't know why, but I tried many Nougat custom ROMs (Touchwiz based, like Batman, Superman...) and kernels for my G930L, things work fine, except for the back and recent touch button NOT working (press it, no response, no backlight or vibrate). I tried all kind of setting inside the rom, using button remap app, no good. Only way for them to work again is to flash back to stock firmware through Odin. Even if I just flash the custom kernel over the stock firmware those button stop working right after that. So anyone having korean S7 model, do you have the same problem as me? I've posted the issue on the rom forum, but seem like there won't be any fix now.
-Since F/FD model also are Exynos variant, I was hoping I could flash F/FD firmware through Odin to my L, but maybe it's not possible (too afraid of bricking my phone to try). I read somewhere that's because of the different partition size, and I don't know if re-partition option in Odin can help, because that maybe unsafe to do so. Your opinions?
-I also read that you can replace the CSC file with your country CSC file when flashing, while load the BL, AP, CP file of the current model. Can I do that? I also read that I have to tick the re-partition box in Odin, and my fear of bricking my phone stop me from doing so, because my country sold the FD model and I'm having L model, if I also have F/FD model then I would have gave it a try.
Only thing I can think of is if you selected on screen buttons when installing the ROM. Those will disable hardware buttons.
Not sure about 930F/D compatibility with S/L/K
As for Odin, I've always read that you leave all options default and don't manually check/uncheck anything. You should be able to flash whatever CSC you want so long its CSC within your models variant, but again not sure with 930F/D compatibility. There is a flashable CSC utility that supports S/L/K you can do after the fact: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
Beanvee7 said:
Only thing I can think of is if you selected on screen buttons when installing the ROM. Those will disable hardware buttons.
Not sure about 930F/D compatibility with S/L/K
As for Odin, I've always read that you leave all options default and don't manually check/uncheck anything. You should be able to flash whatever CSC you want so long its CSC within your models variant, but again not sure with 930F/D compatibility. There is a flashable CSC utility that supports S/L/K you can do after the fact: https://forum.xda-developers.com/galaxy-s7/development/utility-flashable-csc-selection-30-t3392949
Click to expand...
Click to collapse
Do you have Korean S7? I want to know if it's a common problem with korean model or is it just me who have it.
For S8 ported ROM, I'm sure I uncheck the on-screen button first, but those buttons didn't work. It also happen with S7 stock-based ROM like Superman, or even just flash another custom kernel over the stock ROM, all the time the same problem.
I'm currently using the CSC selection and it works fine, but it also means I have to root the phone. I want a way that I don't have to root but can use CSC feature, so I can have OTA update or apps that require unrooted phone to use. It's clear that using custom ROM or kernel are the easiest way but not an option for me.
I'm on a 930F. Sounds like there must be a difference with the S/L/K buttons that F/D ROM's don't account for, can't think of anything else.
I would guess flashing CSC should be fine on any Exynos variant, but that's just a guess. I've got nothing tangible to base that on. I also imagine worst case scenario you'd still be able to get into download mode and flash again if it goes wrong.
Have you tried Marshmallow? Just to see if it works?
Beanvee7 said:
I'm on a 930F. Sounds like there must be a difference with the S/L/K buttons that F/D ROM's don't account for, can't think of anything else.
I would guess flashing CSC should be fine on any Exynos variant, but that's just a guess. I've got nothing tangible to base that on. I also imagine worst case scenario you'd still be able to get into download mode and flash again if it goes wrong.
Have you tried Marshmallow? Just to see if it works?
Click to expand...
Click to collapse
Don't know if I can downgrade to Marshmallow (I remember I've read that it's not possible), but for now I want to stick with Nougat. That's why I want to hear opinions of another Korean model users and how they deal with the problem.
I've gone between N and MM and back a few times waiting for Xposed N
So long as you flash all 4 files that belong to MM with Odin it's fine. You just shouldn't flash a zip to downgrade, since that's doesn't downgrade everything and will cause problems.
Beanvee7 said:
I've gone between N and MM and back a few times waiting for Xposed N
So long as you flash all 4 files that belong to MM with Odin it's fine. You just shouldn't flash a zip to downgrade, since that's doesn't downgrade everything and will cause problems.
Click to expand...
Click to collapse
Good to know that. Maybe someday I'll give it a try. But if I can have Nougat ROM without problems like those it would be best. Those Korean model have limited SMS length, and cannot mute camera shutter sound which pretty annoying, not to mention those bloatware. And my phone have already tripped Knox, or else I might just live with it and stay stock.
MrShock said:
I have korean S7 G930L, and are having some questions:
-(I'm NOT looking for troubleshooting, just want to know if anyone have the same problem) I still don't know why, but I tried many Nougat custom ROMs (Touchwiz based, like Batman, Superman...) and kernels for my G930L, things work fine, except for the back and recent touch button NOT working (press it, no response, no backlight or vibrate). I tried all kind of setting inside the rom, using button remap app, no good. Only way for them to work again is to flash back to stock firmware through Odin. Even if I just flash the custom kernel over the stock firmware those button stop working right after that. So anyone having korean S7 model, do you have the same problem as me? I've posted the issue on the rom forum, but seem like there won't be any fix now.
-Since F/FD model also are Exynos variant, I was hoping I could flash F/FD firmware through Odin to my L, but maybe it's not possible (too afraid of bricking my phone to try). I read somewhere that's because of the different partition size, and I don't know if re-partition option in Odin can help, because that maybe unsafe to do so. Your opinions?
-I also read that you can replace the CSC file with your country CSC file when flashing, while load the BL, AP, CP file of the current model. Can I do that? I also read that I have to tick the re-partition box in Odin, and my fear of bricking my phone stop me from doing so, because my country sold the FD model and I'm having L model, if I also have F/FD model then I would have gave it a try.
Click to expand...
Click to collapse
Hey buddy. I am also very much thinking of the re-partition thing. Do not have the courage to brick my phone. Have you done anything since the post is quite old.
After flashing a stock android 7.0 firmware with Odin my phone boots up normally without any problems, however it doesnt detect my network.
The firmware I used was from argentina, which is not my country but uses the same 4g bands so i figured it wouldnt matter.
is there a way to fix this? or i just have to flash to my old firmware (which I totally forgot which one was it).
I would appreaciate any help, Im a novice when it comes to this stuff.
back to stock
After the root to the stock firmware, did you a factory reset?
Sometimes it will help after you put your phone back in stock firmware.
nathanxpl said:
After flashing a stock android 7.0 firmware with Odin my phone boots up normally without any problems, however it doesnt detect my network.
The firmware I used was from argentina, which is not my country but uses the same 4g bands so i figured it wouldnt matter.
is there a way to fix this? or i just have to flash to my old firmware (which I totally forgot which one was it).
I would appreaciate any help, Im a novice when it comes to this stuff.
Click to expand...
Click to collapse
Call your provider and ask them to reprovision your device on their end. That helps often.
I have a sm-g715u1 with latest android 11 firmware and flashed the verizon G715USQU7BUC1. Both are latest ota firmware.
Odin (3.141) showed a succesful flash with all 5 bl,ap, cp,csc and userdata put in. The csc file was non home. However, I dont see any verizon apps installed. There were changes and it does show the U version software installed but no verizon apps. I saw no errors in odin and flashed it twice but no change. I did a factory reset from phone app before flashing a second time.
Not sure what i did wrong . I left the SD card in but dont think that matters.
It has verizon splash screen on startup but thats it. The phone is functional but no different than U1
Is this version (3.14.1) of Odin ok for U1 to U flashing?
Should i have factory reset before flashing? Flash from recovery and not the phone software?
Any ideas will be appreciated.
GMANNOT said:
I have a sm-g715u1 with latest android 11 firmware and flashed the verizon G715USQU7BUC1. Both are latest ota firmware.
Odin (3.141) showed a succesful flash with all 5 bl,ap, cp,csc and userdata put in. The csc file was non home. However, I dont see any verizon apps installed. There were changes and it does show the U version software installed but no verizon apps. I saw no errors in odin and flashed it twice but no change. I did a factory reset from phone app before flashing a second time.
Not sure what i did wrong . I left the SD card in but dont think that matters.
It has verizon splash screen on startup but thats it. The phone is functional but no different than U1
Is this version (3.14.1) of Odin ok for U1 to U flashing?
Should i have factory reset before flashing? Flash from recovery and not the phone software?
Any ideas will be appreciated.
Click to expand...
Click to collapse
I see that i can no longer access special menus via the dial pad like I did before the flash. Its like a partial install of the userdata file or something.
So things i noticed after the vzw flash: I didnt get the full verizon bloatware and lost some of the samsung unbranded advantages. I have the vzw 4G icon and Hd voice icon during calls and had the video call option. Video calling didnt work and had to call vzw tec support to get it turned on. A ticket was opened to have it done and its now working fine. Before the flash i was told it couldnt be done so flashing to vzw must have helped here. One thing i have noticed is reception in fringe areas after flash in terrible by comparison. It now enters extended network or no signal at all where before it stayed on lte even with 1 bar and could text and call. This must be a PRL difference or something. The unlocked, unbranded version is way way better for fringe areas. In town i noticed no difference.
At this point i could try to enter recovery and wipe then direct to flash the vzw firmware again to see if i get all the bloatware but to be honest the poor signal and tower handoff with the vzw firmware has convinced me that the U1 firmware is better for me overall even if i lose the video calling after switching back.
At least with the U1 version its a little easier to experiment to see what works best.