Hi,
I am trying to fix a broken SM-T710 which is stuck in a boot loop. I have been working on this for the last 24 hours and I have not gotten very far. I would be very grateful if someone could tell me what else I can try.
First, here are the symptoms:
Holding the power button while the tablet is not plugged in will cause it to show Samsung Galaxy Tab S2 powered by android, then it shuts off.
Plugging in the tablet starts a bootloop, flashing the same message as above, shutting off, and repeating
I have not been able to get the tablet into recovery mode
I can get the tablet into download mode (home+vol down+power)
In download mode it says:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-T710
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Secure Download : Enabled
KNOX WARRANTY VOID: 1
RP SWREV: B:2 K:0 S:0
What I have tried so far is connecting the tablet into my PC and running Samsung Smart Switch. I did the emergency recovery and initialization within that software. After entering the model and serial numbers, it downloaded the software update and initialized it on the tablet, I could see the progress bar on the tablet during the initialization phase. It successfully resets the tablet but then the boot loop begins again.
I also tried downloading the firmware from Sammobile and flash in Odin. The file I have tried flashing is T710XXU2BPB1_T710XAR2BPB1_HOME.tar.md5. ODIN flashes the files and resets the tablet...back into a boot loop. I have not tried checking re-partition when I do this, as I do not know what to do about the PIT file
Is there anything else I should be trying? Thanks
Just flash using your original firmware.
This tablet came from eBay so I do not have any idea what the original firmware is. Everything I know about the tablet is in the first post. I assume that Samsung Smart Switch downloaded the original firmware since it required the model # and serial #. I am guessing that the tablet is from the USA but I do not even know that 100%
asty said:
This tablet came from eBay so I do not have any idea what the original firmware is. Everything I know about the tablet is in the first post. I assume that Samsung Smart Switch downloaded the original firmware since it required the model # and serial #. I am guessing that the tablet is from the USA but I do not even know that 100%
Click to expand...
Click to collapse
It's a hardware failure. Several others have had the same issue. Main board needed to be replaced.
I have the same issue here. It's a T715C which I bought in Singapore (distress purchase, rather than bargain hunting) and brought back to the UK.
Given that it's more than a year old, but a known fault, does anyone have any alternatives to taking it to the local recycling centre?
gswarbrick said:
I have the same issue here. It's a T715C which I bought in Singapore (distress purchase, rather than bargain hunting) and brought back to the UK.
Given that it's more than a year old, but a known fault, does anyone have any alternatives to taking it to the local recycling centre?
Click to expand...
Click to collapse
Try NAND erase while installing the firmware with odin.
I'd also try installing kitkat firmware if you can find it. Sometimes a downgrade fixes issues. You can then upgrade as normal.
Thanks. I'll have a Google and work out what that means. All my (many) Android devices have always been unrooted and only upgraded OTA!
gswarbrick said:
Thanks. I'll have a Google and work out what that means. All my (many) Android devices have always been unrooted and only upgraded OTA!
Click to expand...
Click to collapse
Hang on I had a bit of a brain freeze there. The earliest firmware will be Lollipop.
Try the Hong Kong firmware. Instructions to install are on the page.
https://updato.com/firmware-archive-select-model?record=E4B33EF21DCD11E6949E0CC47A44B7B2
Worth a try, I guess. Used Odin to flash the oldest Lollipop firmware I could find - with the NAND Erase All option - and it all seemed to work, but came back in the same state - six seconds of the boot splash screen followed by a second of black screen and repeat...
(Tried Marshmallow ROMS, too - no luck)
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
leprkon said:
I am wanting to flash the TMO firmware onto the Verizon Note 8 that I have. I can't do without the Wi-fi calling and tethering that TMO provides, which is why I am wanting to do this. I was looking at the firmware available and didn't see one for SM-N950T, but I did see that under SM-N950U there was a listing for a version with the TMO carrier, more specifically, this one from sammobile. Is this particular firmware the same as one would find on the TMO variant? Or do I need a different firmware? Also, are the flashing instructions provided at the bottom of the sammobile page sufficient for flashing the firmware properly (as in, are there further instructions or files that I need?) Thanks ahead of time!!
Click to expand...
Click to collapse
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
Thanks for the prompt reply! I am downloading the file right now from sammobile. Let's hope it has everything needed! Thanks again!
Please let me know what worked, didn't. I may be doing the same very soon.
Jrockz said:
That is correct. You will find it under "SM-N950U". Then, just choose the tmobile variant which you already did. As long as it has the USERDATA file, you will be good to flash.
Click to expand...
Click to collapse
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
leprkon said:
I am encountering a slight problem and was wondering if you'd be able to assist me. I've downloaded all of the necessary files and made sure to change UMS to 1 in Odin settings so that I can flash the USERDATA. After adding all necessary firmware files to their corresponding sections in Odin, everything seems to flash just fine. However, when I boot up the phone, it still shows the Verizon logo. Additionally, after the initial set up of the phone, it still shows the Verizon apps (Verizon app folder) with the TMO apps installed. It is as if the phone is still Verizon branded but with additional TMO apps. Are there any steps that I am missing or overlooking? Thanks ahead of time for the assistance.
Click to expand...
Click to collapse
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
BlueFox721 said:
If you boot into recovery and factory reset then select boot into bootloader (download mode) the phone will be in download mode without any of the script showing...connect to Prince Comsy's Odin and load the tmobile firmware, bl to bl, ap to ap, cp to cp, csc to csc, USERDATA to UMS...(no home_csc)...see if that works better
Click to expand...
Click to collapse
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
I failed to mention that you needed the modified Odin. I think it is normal for it to stop at 32% and then start erasing. It did the same when I went from unlocked variant to vzw. Keep us updated on your progress.
leprkon said:
Thanks for the reply!
I did as instructed and did a factory reset. However, it didn't bring me directly to an option to boot into bootloader, so I turned the phone off before it boot into the set up screen. Anyways, I added the firmware files via Comsy's Odin but the flash would fail with a Model dismatch fail error.
EDIT -
I noticed something that would occur after my flashing attempt with the normal Odin. After the flashing process, it would bring me to a screen that has a prompt to the effect of 'System Updating' or something like that (sorry, I should have written down what it said exactly, but I am typing this in a hurry). It will then go to a progress bar and the updating process will begin but it will stop at 32% and then the progress bar will disappear and the word "Erasing" will appear for a few seconds and then the phone will reboot.
Nonetheless, I experience the same results each time in regards to the phone still being branded as a Verizon phone with the Verizon bloatware. However, there are the additional TMO apps that would come with a TMO branded phone.
EDIT 2 -
I found another thread where someone was having the same issue. I'll make further attempts when I get home. I should have done a more thorough search before making this thread. I apologize.
This is the thread I found where there was a similar problem with an S8.
Click to expand...
Click to collapse
The boot to bootloader is In the main recovery menu, but yeah...you need to use the modified odin
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
Support SINGLE-SKU
Supported API: 3
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
-- Installing package...
Finding update package...
opening update package...
Verifying update package...
Update package verification took 1.1 s (result 2).
Installing update...
Successfully installed package.
-- Resizing data...
E:failed to mount /data (Invalid Argument) can't mount '/data', rc = '-1'(Invalid Argument)
E:failed the resizing-data-- omc_binary_download...
-- Deleting selective files
Successfully deleted files selectively
-- Deleting RSU selective file
Successfully deleted RSU selective file
-- amazon_symlink_vze...
-- Deleting VZW's apn file
Successfully deleted VZW's apn file
Successfully verify for dmverity hash tree.
Click to expand...
Click to collapse
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
leprkon said:
Here is a quick update from what I have gathered thus far -
using the Modified Odin did not work at all and only spat back the Model dismatch fail error.
Using the unmodified Odin, if I install the AP and Bootloader or AP by itself, then it removes the Verizon splash on boot and brings me to the home screen upon boot saying that I have to power off the device and insert the provider UICC, which is the SIM card. I could easily do just that, but I want to get the TMO firmware installed.
Next, I flashed the CP and let the phone boot and this is where I was able to see two TMO apps, T-Mobile TV and Visual Voicemail.
From here, I got the phone back into download mode and flashed the CSC and let the phone boot. This is where it went to the blue 'Installing system update' screen but stopped at 32% with an error - No 'erasing' step. From here the phone automatically went to the recovery menu with the following lines at the bottom:
I let the system reboot, and this is when the Verizon flash screen returned. The Verizon apps returned as well, but they weren't in a Verizon folder and the icons were part of the main pull up for the app list. Additionally, the message popup prompting me to insert the provider UICC no longer came up
I had encountered this once before and after flashing the USERDATA, the Verizon apps were placed in a Verizon folder in the app menu. So, I decided to flash the phone again, but this time without the CSC and with the USERDATA.
The results:
The phone went to the blue 'Installing system update' screen but stopped at 32%, stopped, and then the word 'Erasing' came up. From here the Verizon boot up splash came up followed by the initial set up. The TMO T-Mobile TV and Visual Voicemail apps were present. The Verizon apps were placed in a Verizon folder.
I am not too sure what is going on, but I am going to attempt to repeat this process but with the N950U1UEU1AQI5 - SM-N950U1 TMB firmware instead.
I will post an update with my results as soon as I finish.
Click to expand...
Click to collapse
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
BlueFox721 said:
Did you somehow get your downloaded files mixed up? Also...u1 is unlocked, regardless of att, tmb, spr, or usc designation....the complete carrier Firmware is from the u version only...It seems that you are trying to combine files from unlocked, Verizon, and tmobile....I suggest the SM-950U t mobile as that is the full one...forget the rest... unless you want unlocked firmware...here is the complete tmobile....Here is your link: http://updato.com/firmware-archive-select-model?record=F15026309A7911E7963AFA163EE8F90B
And do it all at once...recovery, factory reset, main menu of recovery to select boot to bootloader can't hurt either...when you open Prince Comsy's Odin, make sure you run as administrator
Click to expand...
Click to collapse
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
leprkon said:
Nope, no way I am getting my files mixed. I am being very meticulous with this. The reason why I did one file at a time was to try and troubleshoot to see what was happening. I also know about the difference between U and U1 and again, I was just trying to troubleshoot. As for combining files, I'm actually not. I am sticking with files from one firmware throughout. If you read through my troubleshooting process, somehow the TMO apps are overlayed with the Verizon apps. From what I have been reading, this was also an issue with Verizon Galaxy S8's and 8+'s. They had a solution, but that solution isn't working with the Note 8 - or rather it isn't working when I try it.
Click to expand...
Click to collapse
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
BlueFox721 said:
I see...no worries...I hope that it all comes together...I noticed that several devices have been off from the norm...I hope the major update released next resolves a lot of issues...good luck
Click to expand...
Click to collapse
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
leprkon said:
Thanks! I am going to try my luck with an earlier TMO firmware. If that doesn't work, then I am going to install the Factory Stock Firmware for the “Unlocked” Note8 and then try to flash the TMO firmware after that. I am still very perturbed as to why the Verizon and TMO apps are both appearing.
Click to expand...
Click to collapse
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
BlueFox721 said:
I hear ya...that is odd..I have been flashing a lot as well but have had 0 issues on Sprint, but I have not tried other carrier firmware...I have a few friends from other carriers, though, I might try to get them to let me borrow a line to test ...
Click to expand...
Click to collapse
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
leprkon said:
To be honest, I think that the sammobile upload of N950USQU1AQI5 - SM-N950U TMB USA (T-Mobile) might be bad?
Click to expand...
Click to collapse
Good to know....I try to use updato when available...how is that one?
BlueFox721 said:
Good to know....I try to use updato when available...how is that one?
Click to expand...
Click to collapse
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
leprkon said:
That's the one that I have been trying to get to work all day. Doesn't work with modified Odin and flashes TMO apps with Verizon apps. Bootsplash is also Verizon. When I did it with a carrier free firmware, I didn't have this issue. No carrier bloat and no carrier boot splash animation.
I am going to try N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) and see if that works for me.
-Edit - I am getting the same problem with N950USQU1AQH7 - SM-N950U TMB USA (T-Mobile) as well. It still shows as a Verizon phone for some reason and the TMO firmware won't take. But two of the TMO apps install - T-Mobile TV and Visual Voice Mail. I must be messing up somewhere or this isn't working for another reason. I have done just about everything suggested here. Anyone else have any suggestions?
Click to expand...
Click to collapse
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...sorry I didn't think of it sooner...hope it helps.
Looks like we need factory binary and Canadian firmware...
BlueFox721 said:
What version Odin?
---------- Post added at 03:55 PM ---------- Previous post was at 03:27 PM ----------
Ok so what I found is that the csc code of the device may need to be changed. For instance, my unlocked is XAA. Flashed to Sprint is SPR/SPR/XAA. Flashed to Verizon is VZW/VZW/XAA. If brand csc needs to be changed to be, for instance, SPR/SPR/SPR to get only Sprint files and settings...then I would need to follow the carrier switching part if the S8+ thread, with our files of course... Look here: https://forum.xda-developers.com/galaxy-s8+/how-to/snap-guide-flashing-standard-fw-carrier-t3627255
Do you think that Verizon files and settings are being enabled because of the device code, TMB/TMB/VZW? If so, try the instructions in the carrier switching area to change it to VZW/VZW/VZW...The settings may not show it when all are the same...
Click to expand...
Click to collapse
I've done version 3.12.7 and PC 3.12+
I'll try the carrier switching instructions again, but I couldn't get it to work properly. I'll let you know how it goes.
Edit -
It looks like those instructions require a factory binary firmware flash. Is there a way of doing it without that?
I'm not at all experienced with Android or mobile devices in general, and I have an old T813 WiFi (2016) that I needed to root.
I flashed twrp-3.5.0_9-0-gts210vewifi and that worked fine. Except, TWRP couldn't see the download directory where I dropped the magisk zip. I didn't seem to see any internal storage besides the root FS (tab has 60 gig and no sd card).
So on the advice of the internet, I used TWRP to wipe and reformat, resulting in not being able to boot. It gets stuck at the pulsing Samsung logo forever.
I did a factory reset with TWRP and no change.
I then tried to flash stock 6.x firmware using Odin but it failed with an Auth error, I believe due to the device not permitting "downrgades".
So then I used Odin to flash the closest thing to a stock 7.0 ROM that I could find, which was T813XXS2BSJ3_T813XAR2BSA2_XAR from www.sammobile.com. That flashed successfully, the tab rebooted to the stock recovery and loaded the new image, but on the next reboot we were back to same old pulsing Samsung. I left it for a couple of hours, then tried rebooting again, but no change.
I hope it's just that that firmware was for the cell version of the tab, an. d I need the WiFi version. If anyone knows where I can find the right 7.0 firmware for the SM-T813 (2016) it would be greatly appreciated.
I would also welcome any other advice for dealing with this thing.
I'm from the US, and I still have boxes for 3 of my 4 T813s. The part numbers all end in XAR. That being said I went through my filers, and the last ODIN file I used was a XAC file. Looking at Sammobile, just looks like XAC is Canada, XAR is celluar south.
I'm assuming if TWRP couldn't see the directory, you had an encryption issue.
I know I'm still running Akipe's beta TWRP, found in this post. I know it's an "older" version, but I've never upgraded as it had a bunch of fixes that the official one didn't have. Not sure if that ever got corrected or not at this point. That's a question I will ask actually.
OhioYJ,
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
I couldn't find the stock 7.0 version for WiFi anywhere, so I ended up flashing Lineage instead. The tab works now, rooted, so all is well.
I also used the modified TWRP version linked on the Lineage site, which allows MTP in recovery mode so I could dump files where TWRP could find them.
I do wish I could find the stock ROM for the WiFi tab, just in case.
bascc said:
I have the WiFi version, so it has no sim and no LTE radio, I assume. I'm pretty sure the XAR file is for cellular tabs. I did try it, and it did flash OK via Odin, but it wouldn't boot.
Click to expand...
Click to collapse
All the T813s in my house are wifi too, no LTE. Those boxes end in XAR, it's like that even on my newer Tab S5e. So I don't think cellular south necessarily refers to LTE. That being said, the one I have saved on my PC is XAC (Canada), and there are still plenty of XAC firmware files that site.
Either way glad you got it working.
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
how do I do this?
I can get into the boot menu and have tried all options as in:
Wipe cache partition
Wipe data/factory reset
reboot system now
still stuck in boot loop (1st power on screen)
brokenbrain939 said:
Hey bro I am not a pro either at this but doing this since quite a time now,
Your first attempt failed because you tried to install an older version of android whereas your device had a newer version installed previously....SAMSUCK does not allows you to downgrade your android model...
Your second attempt resulted in a bootloop , I will suggest you to reboot the phone into recovery and format it once, it might work.....
Click to expand...
Click to collapse
Greeny308 said:
MY skill with Android flashing: 3/10
Phone Problem: Boots to the very first screen with the phone model and then turns off itself, vibrates, and relaunches..... (repeat repeat). It did use to reach the Samsung screen before my (what I thought was) successful FW flash!
Hey, so im having a mare trying to flash some firmware on my friends Note 8 using Odin3 and pretty much guessing at firmware to fix this phone. I downloaded the latest version that seems to be available.
The phone Model number is not known exactly but its a single sim, UK spec (Carrier: 02) so am assuming it is the SM-N950F
Im slowly downloading fw files to try and get this phone to reboot - but no such luck! is there anyone with enough patience to try and help me install the "correct" firmwares?
I tried with my first attempt and it fails in odin with a message: SW Check boot loader 14 binary 13 (or something along those lines - which I tried a search for here in the forums and was something to do with the compatibility of the bl and fw not being correct)
My second attempt was a success through Odin (Cleared and Pass!) but now it only gets to the very first screen and reboot loops straight away without getting to the Samsung screen.... so not really a success my end!
Can anyone help a Android noob?
Not looking to keep any data what so ever Just want a full factory reset.
Phone last worked properly on 23/24th December last year and my friend hasn't bothered with it since when it bricked.
Click to expand...
Click to collapse
What did you flash in your second attempt?
stonedpsycho said:
What did you flash in your second attempt?
Click to expand...
Click to collapse
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Greeny308 said:
Like all four options it gives you in Odin. The bl, ap, cp, csc....... using the latest one I could find on SamMobile for 02 carrier U.K. -
Click to expand...
Click to collapse
It should boot after flashing that, it could be a hardware problem preventing a successful boot :-( Probably worth trying different filmware though, you could try BTU (UK) or XEU (UK & Ireland)
Bro i will advice you to just get over this stock rom and install some custom rom.
You can install a custom recovery like twrp through odin and then using that recovery install some custom rom made for your device.
All these you might find in your device's xda forum.
Brp i just checked and found that galaxy note 8 has plethora of custom roms available just install the one which you like.
You can see the installation process on youtube.