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
Hi there,
I have a Samsung Galaxy Tab A6 (SMT-580) which I bought today. I followed this tutorial to install twrp, ultimately to root the device:
dottech .org/200476/how-to-install-twrp-recovery-on-samsung-galaxy-tab-a-sm-t580/
Everything worked fine and I was able to boot and reboot fine. Until I signed in with my Google Account. After trying to reboot, I get a black screen with the Samsung logo and a text in red saying: Custom binary blocked by FRP Lock. I went back to the store and they advised me to install Samsung Smart Switch to try and restore. In the Smart Switch program I get an error saying that the device is not supported by Smart Switch.
I can get into download mode, not into any other mode. The tablet doesn't start up at all. On the download mode it also says FRP Lock ON.
When I go back into ODIN and retry to install the from above TWRP image, it says operation failed.
Can anybody please advice? I am at a complete loss. Am I supposed to flash the original boot file? Where can I find that for my device? Will my tablet accept that, since ODIN didn't even want to flash my current TWRP image a second time?
P.S. I only read later that you are supposed to change the OEM setting. I didn't. Is that the cause of this issue, and if so, can I do something about it?
Thanks
Hi. Have you got it fixed yet? You need to download and flash stock firmware for your model and flash it in odin. Once it's done you have to enable oem unlock before you flash twrp. Let it be enabled as long as you you have twrp, root or anything custom.
Skickat från min SM-A310F via Tapatalk
ok, I read this is the place for noobs, so, I too got myself into a FRP LOCK on my Galaxy Tab A6 sm-T280. I use the tablet strictly for flying my drone for surveillance around the rural location where I live. It was having some connectivity problems, so I rooted it to hopefully get enough horsepower to run the DJI Go app. That didn't work so I did a wipe/factory reset, had a problem with the password, and here I am.
I am researching, and gathering the required tools to fix it.
I finally found some guides that are basic enough for me to understand.
I found numerous sites to download the stock rom, but not sure which ones are safe. Suggestions? Also, I am not sure about the country code for the firmware. I am in the USA, and I don't see it listed anywhere. Does it matter? This android stuff is all new and confusing to this old man. I am determined to get this tablet fixed, and would appreciate any and all advice. Thanks, Gary
edit: Will this rom work? : T280XXUOAPL1 using XAA for theCSC? Is xaa the default/generic for U.S.A. ?
My Fried gave this phone to me (SM-N915G) which is stuck at Powered by Android, and told me to fix it.
He said that when he update to MM from LP without KIES or Odin, the phone suddenly restarted and stuck there getting HOT
He had no experiece to repair it so he asked me to fix it.
So for 3 days lately, i have tried many ways to fix it but wihout any progress, as follow :
1. Flashing Official MM wby using Odin -> still stuck
2. Downgrading Flash Official LP using Odin -> still stuck
3. Installed TWRP, and flasing CFW Micky387_MM_V3.0 for 915F/FY/G (flashing Bootloader and modem as required) -> still stuck with set warranty bit : kernel
4. After Flashing Micky CFW and Failde, i try to flash Emotion Kernel -> still stuck with Kernel is Seandroid Enforcing
5. Redoing Flash Micky CFW with other CSC -> Still Stuck (even i tried with 915F and 915FY as in the aroma installer)
6. Never failed during flash procedure with Odin or TWRP, everything is smooth
7. When stuck, the device is getting Hot slowly but and when left as long as 15 minutes, the HH is getting HOT (TWRP read 72 degree at most)
**Update
8. Tried using Official SmartSwitch sucessfully but the result is still the same -> Still Stuck and getting hot as usual T.T
Last Download Mode status is :
Odin Mode (High Speed)
Product name: SM-N915G
Current Binary: Samsung Official
System Status: Official
Reactivation Lock: Off
Knox warranty void: 0x1 (2)
Quallcomm secureboot : Enable (CSB)
RP SWREV: S1, T1, R1, A1, P1
Secure Download: Enable
UDC START
I am now thinking, should i flash another Kernel or PIT or Bootloader? but i still cant decide what to do next to revive this Phone
Please help, any suggestion is greatly appreciated, thank you.
Please give some help, thank you.
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
wingz17 said:
Help Please anyone?
This is Hard Brick or Soft Brick?
Any suggestion or Opinion please
Thank you
Click to expand...
Click to collapse
Have you tried a reinstall using KIES?
The Radius Kid said:
Have you tried a reinstall using KIES?
Click to expand...
Click to collapse
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
wingz17 said:
Yes i have try to recover but not using KIES, but using smartswitch...
Is it diffrent by using KIES or SmartSwitch?
Thank you.
Click to expand...
Click to collapse
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Thank you for the suggestion,
I will try that one out and let you know.
wingz17 said:
Thank you for the suggestion,
I will try that one out and let you know.
Click to expand...
Click to collapse
The Radius Kid said:
I can tell you that Kies and NOT Kies 3 was what worked for me when I downloaded/installed Marshmallow from Samsung's website.
Figure that one out.
That was also using a 64 bit version of Windows 7 Pro.
Click to expand...
Click to collapse
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
wingz17 said:
Sorry For the long response, i have tried flasing using KIES but still stuck on the android, and no progress.
Right now i am run out of option, please help, thank you.
Click to expand...
Click to collapse
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
The Radius Kid said:
I'm going to guess that you've tried installing MM using Kies directly from Sammobile?
If so,have you tried turning off your computer's antivirus when you download/install?
It sounds like the bootloader is looking for something and can't find it.....kind of like what happened to me when I totally ripped KNOX out of my phone.
Restore time!
Good thing I did CWM backups.
In your case,your computer's anti virus could be seeing something in the download and ripping it out.
I've seen my browsers do that when I download stuff....pain in the....
Have you tried a different battery?
Maybe a search of the forums to see if anyone else has had this problem and solved it?
I kind of remember seeing something like this a while back.
Click to expand...
Click to collapse
Thank you for the response,
I was using KIES 2.64 that downloaded from Samsung website to fix the phone as your suggestion (tools->firmware upgrade and initialisation) but still fail to fix it.
Nope, the antivirus still active when KIES download the FW and Flash it into the phone, but it is new to me that antivirus will intercept ongoing dowloaded files, if so i think the antivirus will give some notification or warning about the content of the file that being downloaded and in my case, my antivirus is still cool and no notification whatsoever.
The bad thing is i do not have any cwm backup and since this is my friend phone and not mine, well... we dont have any backup for this phone.
Regarding the battery, i admit that i havent try other battery, since i dont see any connecton between it, in my opinion, the phone works well, the charging animation working, and no sign of weak battery... but i will try to do it if i can get some other battery
I have surfed many forums and websites, but almost 90% can be fixed with simple flashing from odin or just by clearing up cache and data from recovery.
Other that that, wither, no one respond to the problem, or just some discussion without conclusion, really frustrating.
I even go further to read about android booting sequence to identify whats wrong with the boot sequence, but still confused...
But i have some question if you would to answer :
1 . Stuck at Android logo, bootloader or kernel problem?
2 . Is it possible that one of the mainboard chip that have some part in booting process is malfunctioning? But if so, the phone will be dead bricked right?
3. How about the booting process is halted due some hardware failure? ex : some chip (other than chip that have part in booting process) is bad and so the bootloader init is halted
4. The Worst guess, is it possible that the phone is fake? (the serial number behind the baterry is accepted by kies though)
Thank you very much, you are the only one who still response to my problem. :good:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Bordo_Bereli51 said:
As it seems you use the wrong Bootlaoder. Is his phone N915P or N915G? When you flash N915G Bootloader to N915P, it will not boot but the bootloader will work correctly. Try to flash the N915P bootloader.
I have N915FY phone but did not know first if I had N915F or FY. I flashed the N915F bootloader version, which flashed successfully, but was not booting. Bootloader said that my phones model is N915F. After flashing the FY Bootloader version, it successfully booted to system.
Click to expand...
Click to collapse
Thank you for the Response,
First, his phone is N915G (according to the box and the information in the battery compartment)
(Really sorry for the mistake i made at the thread title)
And regarding bootloader, that is also my concern at first, i think maybe i was flasing wrong region and bootloader, and so i search the way to find out the real version of the phone, but after trying many ways described on the net (by imei or serial number) , i still cannot found out the way.
But one instance when i try using KIES, and KIES asked for the version and serial number when device upgrade and initialisation, i entered the exact version and serial number that is found behind the phone in battery compartment. KIES immediately confirms that the version and serial number is valid, (i still wonder though, is KIES check it online at Samsung server or there are some serial number database embedded in the KIES) and continue to run trough the official fw download and installation by KIES but at the end still no success.
Is it possible that the version and serial number is wrong ? if so, how to determine the correct one?
and is it safe to try flasing another bootloader?
Thank you very much
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Bordo_Bereli51 said:
Hello, there is no bootloader related to serial number or something. There are different bootloaders for different models and android version. When you flash MM-Version, you need to be sure that you use the right bootloader and baseband files for MM. If you flash different region-locked firmware/bootloader, it will not affect btw. not solve the boot-stuck problem.
http://samsung-updates.com/device/?id=SM-N915G Try to flash 6.0.1 firmware that is related to your region if you still want to try to flash different region-firmware.
Maybe download the XSA 6.0.1 Firmware with the pit file XSA http://gsm-firmware.com/index.php?a=browse&b=file-info&id=15892.
Then flash XSA 6.0.1 and TBLTE_SEA_XSA.pit together in odin. Under Odin 3 V3.12 ticke the re-partition at option-tab and select TBLTE_SEA_XSA.pit under pit-tab.
Click to expand...
Click to collapse
Thanks for the reply!
Although there is no bootloader related to serial number, but if we put the serial number in KIES, it will identify what CSC and region, which can be use as a guide to choose the correct FW or let KIES do the Flashing according to the inputted serial number, and as long as the serial number is correct one, that is my opinion but please CMIIW.
When flashing MM, if i use the MM that has been downloaded, the bootloader and baseband is included in the MM image right? or shouuld i flash it separately?
i have tried your suggestion but with no sucess, i have dowloaded the PIT and the FW, flash it trough odin which was sucess, but still stuck.
I do not tick auto restart at Odin, so i manually restart the phone, but i encounter an event which at 20% installing system update (below the greed droid guy) the progress bar is vanished and replaced with erasing, and after that the phone stuck again at the same spot.
Do you have any idea why?
Thank you very much.
Just thinking, should i erase the NAND in ODIN?
If so, how to restore it?
I think that if i backup the NAND using custom recovery and restore it later, it just bring back the same problem, if the NAND causing all this.
Do anyone have some NAND backup that i could use? or any other suggestion?
Thank you
Can you boot to recovery? if yes, try to wipe data and cache.
If it still not working, try to backup your efs with a custom recovery (ex. TWRP), or better the entire System like data, system, boot, efs, modem and save it to your computer.
After saving the backup, try to flash the firmware with pit file while checked NAND erase all.
When its finished and your device boots up, you can flash back your custom recovery and recover only the efs-partition.
If its not working, then there is maybe problems with your eMMC. But be aware using nand erase all. It is the last riskfully option left after trying several things.
I have a backup of my resurrection rom. If you want it I can upload it.
Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
KeithSherley said:
Hello, My Sprint S7 was frp locked and I wanted to sim unlock it. I downloaded odin v3.12. ADB does not see the phone. I flashed with a firmware file. It is now in a boot loop where it says system install. At one time it came up and said it failed and to use Smart Switch emergency repair. I downloaded smart switch and it says unsupported device. I can put the phone in download mode. I have searched and gotten firmware. Everything I try fails in odin. Is it bricked for good or is there a way to fix it? Are there reputable companies that can unbrick it for a small fee? This site is tough to navigate and everytime I search it seems I come up with another place. One had a link to download firmware to flash and fix bricked phone but when I tried to open it my antivirus said it was full of adware. The phone is SM-G930P running 7.0. I was going to flash to a universal one or at&t. I can try odin and screenshot the results if I need to. I am willing to try about anything. Thanks in advance for any help. I have another one (they came as a pair) it is not frp locked but is simlocked. Not blacklistedd but it does show an unpaid balance. I cannot get a hold of the person I bought them from. I know what to check now though. Lesson learned.
Click to expand...
Click to collapse
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
kpwnApps said:
If its stopping on sboot.bin install samfirm and download latest firmware then flash again
Click to expand...
Click to collapse
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
KeithSherley said:
Hey. Thanks for responding. I downloaded samfirm. It says device not supported. I have been searching around to make sure I try to flash the correct software. At this point I am not as concerned about sim unlocking as just getting it to boot up again. Is it possible I tried to go further back and an older bootloader bricked it? Thanks
Click to expand...
Click to collapse
Install firmware from updato.com and try again
kpwnApps said:
Install firmware from updato.com and try again
Click to expand...
Click to collapse
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
KeithSherley said:
Hey. I have been trying to download from updato. I guess the free download is not very good. It says 2 days and keeps disconnecting. Fianlly aborted when about halfway through. I have found another site to give a shot. Maybe I just did not have the correct file the first time. Thanks for checking in. I appreciate any input or ideas.
Btw, the other s7 I have is working. It is sim locked from Sprint. It is not listed as stolen or lost. To flash to Sprint would I just use the latest download? Thanks
Click to expand...
Click to collapse
The saga continues. I did download stock firmware. It still failed when trying to flash with Odin. I can get it to load the recovery menu and the download menu now. Before the recovery menu would not load. on the log the last two things say
xbl.elf
FAIL! (Auth)
I tried Kies and Switch, neither support the device. I am currently downloading a stock rom from SamFirm, once I figured out the exact way to type on model and region code. I will try that in a little while and search for odin auth fials for the s7.
Thanks again for the help. I have learned quite a bit and it is fascinating. Any thoughts on the fail would be greatly appreciated. I hope after I get the stock rom back I can find the correct process to unlock it.