Database Info

[Q] Accidentally took OTA update and SVTP tether doesnt work

I have done flashing and rooting in the past on both a Samsung Charge, Nexus and S3, but it's been a while. Ive used Odin, and the TOOLKIT, and am somewhat familiar with both.
I have had my S3 for several years, STOCK, STOCK, STOCK, and liked it just the way it was. I had a WIFI tethering app, SVTP that worked, and didnt take updates for fear it would quit working, well I accidentally took an update, and now it doesnt work.
Id like to reflash the phone back to a previous stock software, I forget which one I had, but currently here is my phone info
SCH-I535
4.3
I535VRUCML1
KERNEL 3.0.31
build JSS15J.I535VRUCML1
hardware I535.10
I believe I had Jellybean, or a 4.0 firmware.
How should I flash this back, and where can I download the files and the correct version of ODIN?

So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?

Nitro169 said:
So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?
Click to expand...
Click to collapse
As long as your not on the NC1 or NE1 baseband/firmware you can indeed revert back to an older version. And you do indeed have to unlock the bootloader to revert to a previous version of Android
In my personal opinion your best bet is the casual root/unlock method which will do both for you
Sent from my Nexus 5

so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.

Nitro169 said:
so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.
Click to expand...
Click to collapse
Because your on a locked bootloader and downgrading now would brick your device
Sent from my Nexus 5

Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?

Nitro169 said:
Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?
Click to expand...
Click to collapse
Check swappa for that. I know brand new ones have the newest firmware, your better bet is swappa
And no they are locked down tightly, unlocking is nearly impossible
Sent from my Nexus 5

what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?

Nitro169 said:
what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?
Click to expand...
Click to collapse
No, you can't get around the locked bootloader. Your stuck on it
Sent from my Nexus 5

I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.

MrBrady said:
I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.
Click to expand...
Click to collapse
You are correct. I did a quick search and those who took the 4.3 ML1 OTA are indeed on a locked bootloader
Sent from my Nexus 5

S3 LTE issues (bootloader unlocked) Need new radio?

I have a Verizon Galaxy S3 that I've had for a couple years that I bootloader unlocked first thing when I first purchased it. The baseband says "NE1"
I am running a later release of Cyanogenmod 11 (official) with TWRP recovery and I may be having LTE issues; unsure if it is because of the area I am living or if it is my phone itself but I do run into a handful of LTE issues.
I figure my best solution is to install the latest radio that is compatible with my open bootloader firmware. I would love to stick with my open bootloader instead of flashing the latest firmwares and risk locking the bootloader.
I need to know where and which latest bootloader I should flash and which method to flash with. Someone that can point me in the right direction is greatly appreciated.
Thanks for reading.
EDIT: Could I also be running an old phone FIRMWARE? As far as I am aware, the only thing that I can update being that I am unlocked bootloader is my baseband/radio- is there anything else that I should check to update to flash via odin?

stevey500 said:
I have a Verizon Galaxy S3 that I've had for a couple years that I bootloader unlocked first thing when I first purchased it. The baseband says "NE1"
I am running a later release of Cyanogenmod 11 (official) with TWRP recovery and I may be having LTE issues; unsure if it is because of the area I am living or if it is my phone itself but I do run into a handful of LTE issues.
I figure my best solution is to install the latest radio that is compatible with my open bootloader firmware. I would love to stick with my open bootloader instead of flashing the latest firmwares and risk locking the bootloader.
I need to know where and which latest bootloader I should flash and which method to flash with. Someone that can point me in the right direction is greatly appreciated.
Thanks for reading.
EDIT: Could I also be running an old phone FIRMWARE? As far as I am aware, the only thing that I can update being that I am unlocked bootloader is my baseband/radio- is there anything else that I should check to update to flash via odin?
Click to expand...
Click to collapse
Post a screen shot of your about phone screen if you can
Edit: you can update to the newest modem, that should (don't quote me) fix your issue
Sent from my Nexus 5

SM-915A Aug. Update 5.0.1 Firmware Search...

I've been looking everywhere for the latest updated firmware for the SM-915A. Apparently my phone updated without my knowledge, (Thanks again AT&T) and I went to roll back to KitKat without looking at my FW version....now soft bricked. Does anyone know where i can find the latest version? Thanks.

Use kies. Under tools there is an option to initialize or something. There you put in your serial number an it will flash your phone with the latest os from your carrier. Think your phone must be in either download mode or the "firmware update had an issue, please connect to kies" mode.
Sent fra min SM-N915FY via Tapatalk

elfysrfr said:
I've been looking everywhere for the latest updated firmware for the SM-915A. Apparently my phone updated without my knowledge, (Thanks again AT&T) and I went to roll back to KitKat without looking at my FW version....now soft bricked. Does anyone know where i can find the latest version? Thanks.
Click to expand...
Click to collapse
Go to best buy they will refresh your phone. Kies are not working on At&t phones.
Sent from my SAMSUNG-SM-N915A using XDA Premium HD app

Thanks for the info

I had boot loop. Fixed it on my T Mobile Note Edge by booting into recovery and doing a factory reset. I am now on 4.4.4 native.

This is the AT&T variant...note edge SM-915A. We don't have an unlocked bootloader, hence no custom recovery to boot into and reflash

I didn't use a custom recovery. I would have mentioned that. I used Samsung's stock recovery mode and did a hard reset

Gotcha...yeah mine killed stock recovery too. We'll after being without a phone for a week, I tried best buy Samsung experience and they couldn't fix it. I ended up going to the Samsung service center storefront and they finally got it going again for free. Well looks like I'm stuck on LP though but at least I've got a phone again

Note 5 on TotalWireless won't update past PD4?

I bought a refurbished Galaxy Note 5 and have used it on TotalWireless for a few days before I noticed the Note 5 should be on BPF4. When I received the phone it was already on BPD4, my wife's phone upgraded from a 5.1.1 firmware and went through the full chain to BPF4 previously. Will an ODIN flash back to a 5.1.1 firmware allow my phone to pass where it is stuck currently?
Thanks

NeoandGeo said:
I bought a refurbished Galaxy Note 5 and have used it on TotalWireless for a few days before I noticed the Note 5 should be on BPF4. When I received the phone it was already on BPD4, my wife's phone upgraded from a 5.1.1 firmware and went through the full chain to BPF4 previously. Will an ODIN flash back to a 5.1.1 firmware allow my phone to pass where it is stuck currently?
Thanks
Click to expand...
Click to collapse
Why don't you just download BPF4 and flash via odin? I'd make sure you didn't receive a fake phone before you flash anything as long as the phones real you can just flash it yourself in odin and setup the network to use the right settings from Totalwireless. The only reason I mentioned a fake phone is because someone else wanted to do the same thing and ended up with a phone that he couldn't find the firmware for because it was fake and after trying to flash Verizon firmware which failed he had no way to go back!

It's definitely a genuine Note 5. I was trying to locate the PF4 firmware to flash via ODIN, but the only ones I could find were several 5.1.1 firmwares and the PD4 firmware I was already on, do you have a link to a full PF4 firmware? Must have had research failure or something, haha. I finally decided to try the Verizon Upgrade Assistant and it was able to update me to the latest PF4 firmware no problem.

Download Samsung Smart Switch for PC.
You won't get OTA updates unless you have an active Verizon sim card.
Using Smart Switch to update is much easier than Odin.

I'll try Smartswitch when the next OTA comes out. I was actually surprised how well the Verizon software worked to fix the issue. In the past I always ignored the software install portion of USB connection. Guess it serves a purpose now.

Someone HELP!!!

Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please

I had the some problem while playing with my handset I switched off OEM unlock for some reason under developer option..
Next time i reset my handset it stuck on that warning
You need to download combination file, flash it with odin, then unlock developer mode, toggle OEM unlock, than flash back your current firmware, or if you have full twrp back up restore it

JayMor81 said:
Hi all,
I'm having a nightmare of a time with my Galaxy S7... For some unknown reason I decided to root my phone about 2 months ago using CF Auto Root.. worked great.. This morning, was having bad lag issues, so I restarted the phone.. as soon as the Samsung logo came up, I got a red message at the top of the screen saying "Custom Binary locked by FRP".. kind of freaked out and booted the phone into Recovery mode.. wiped Cache and wiped phone (to go back to factory setting I guess).. restarted... since then, I had no boot.. it did loop for a while as I was trying to charge the phone.. but that's it.
Now, the only way the phone will power on is if I plug it into my computer in Download Mode. I am trying to flash the ROM, custom or stock, but Odin fails almost as soon as it starts the sboot.bin and the phone screen shows "SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 6, BINARY: 1".. Also, When I try to power on the phone, it HAS to be plugged in to my computer or charger cable and it just loops with a message at the top of the screen.
I can't do anything with this phone and cant find any solutions online... please help! :crying:
PM me for images of all screens please
Click to expand...
Click to collapse
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.

cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse
Dammit.. I tried to put as much detail as possible in there lol.. obviously I forgot some.. My mistake the Galaxy s7 that I am using is a Rogers Mobile (Canada) SM-G930W8. As for not signing out before modification, omfg, that makes perfect sense.. didn't even think of doing that before rooting.. I appreciate the help!! I will give this a go and see what outcome I get.. Thanks!

[/COLOR]That was nice of you to respond so helpfully, despite you having seen the scenario posted over and over.
cooltt said:
This problem appears on the forum over and over. Its a direct result of not understanding what type of S7 you have and what you need to do before modification.
The error you have in Odin means the firmware you are trying to flash is older than the bootloader file on your device. You can never downgrade a bootloader only upgrade.
In your case you need to flash a firmware version 6 or above for your device. So if you have a branded T Mobile for example you will need to download and flash T Mobile firmware version 6 or above. The firmware must also be for your region where you live.
The FRP lock is because you didn't sign out of, or remove the Google account on the device before modification. Its a security feature. It will still appear after you've flashed firmware but as long as you know the email and password the phone will start fine.
Click to expand...
Click to collapse

Can't make or receive calls
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:

Cesilina said:
Please I need help my I rooted my S7 (flat) flashed the original OS with odin Installed Twrp flashed Andriod 9 and since then I can't make or receive calls wifi seems fine. Someone please come to my rescue:crying:
Click to expand...
Click to collapse
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.

cooltt said:
The S7 didn't receive Android 9 so the ROM is a custom one. Any issues with custom ROM's should be asked on the ROM thread itself where you got the ROM from. It's quite normal for custom ROM'S to have bugs.
You can try flashing the ROM (Android 9 Pie) again to see if it works. If not there are several different A9 ROM's to choose from.
Click to expand...
Click to collapse
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail

Cesilina said:
Thank you for reply. I have tried atleast 4 different custom ROMs but to avail
Click to expand...
Click to collapse
Do you still have an imei number listed in settings?

Can't make or receive calls
cooltt said:
Do you still have an imei number listed in settings?
Click to expand...
Click to collapse
Yes please I still have an IMEI number