Need help unbricking my Galaxy S7 edge SM-G935P phone - Sprint Samsung Galaxy S7 Edge Questions & Answers

I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.

Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
bothambhai said:
I flashed the firmware from here https://forum.xda-developers.com/tmobile-s7-edge/how-to/6-8-t-mobile-935u-firmware-qe2-t3619151 along with the Tmobile radio via Odin 3.13.1, it failed in Odin and now the phone is stuck on the samsung logo. I used the BL and the AP from the zip, the CP I used from the separate tmobile download link. For the CSC I first tried the CSC that is in the package and when that failed I tried the HOME CSC even that failed. the User data I kept blank both times.. Then I tried it a third time same as above except in the CSC I put the CSC file from the zip and in Userdata I put the Home CSC file, it failed again. Am i doing something wrong ?
Update: I have been trying to flash the stock firmware from samobile, but I am unable to do even that. It keeps failing. I downloaded the firmware from here https://www.sammobile.com/firmwares/...S5BRA1/206887/, extracted it, added just the AP and as per instructions went in to download mode, clicked on start and it keeps failing. In Options only auto reboot and f reset is clicked.
I would really appreciate any help to unbrick this device, it is stuck on an exclamation mark saying " An error has occurred while updating the device software. Use the emergency recovery function in the smart switch PC software". Smartswitch is not recognizing this device saying it's an unsupported device so emergency restore software wont work from there. I can get it into download mode but as I said flashing the firmware via Odin is not working. I can also get it into recovery mode but it keeps endlessly trying to update, fail and loop back to trying to update.
Thanks in advance.
Click to expand...
Click to collapse

just checking... are you using the edited princecomsy odin? http://d-h.st/gsDA or use the link here https://forum.xda-developers.com/att-s7-edge/help/princes-odin-t3545104
find the correct rom here https://forum.xda-developers.com/sprint-s7-edge/how-to/odin-stock-nougat-firmware-s7-edge-t3569834
just use files from one rom at a time. get good at that first. maybe you are careful but it really looks like you were guessing what goes where at the end of your post.
i just have tips on what helped me. passing along the info and the link.

epikroms said:
Firstly I would check your use cable, I have a bunch and not all of them work. Secondly, make sure that your phone is being recognized on PC, hence the cable check. and third, make sure you are flashing the correct firmware. You said TMB, but I see you are flashing 3 different company files. Hi back to full G935P firmware , you front need to flash TMB on t, it should be fine cause I have a g935p with TMB sim in it
Anything else I'll be glad to help
Click to expand...
Click to collapse
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.

bothambhai said:
What is your APN settings ? With the sprint firmware I could either get LTE data or calls and text not both at the same time.
Thanks.
Click to expand...
Click to collapse
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS

epikroms said:
Im actually on the G935U rom from jrkruse. If you are on the latest firmware just skip the flashing of the stock U firmware. Just flash eng boot, root it, and follow his process in his t-mobile thread for flashing in flashfire. When aroma starts it asks you what kernel to flash just choose tmobile and it works instantly. But fo APN settings whatbi had was this:
Name
T-Mobile US LTE
Apn
fast.t-mobile.com
Mmsc
http://mms.msg.eng.t-mobile.com/mms/wapenc
Apn Type
default,supl,mms or Internet+MMS
Click to expand...
Click to collapse
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?

bothambhai said:
I managed to flash back the Sprint firmware. I feel the problem is Sprint is probably the only one with an upgraded baseband due to their last update. Both the TMO and U firmwares are based on the 4 baseband G930TUVS4BRA1 and the last Sprint update put it on a 5 baseband G935PVPS5BRA1. That is what is causing for it to fail, I feel. Do you think if I follow the eng.boot method I should be able to overcome the problem ?
Click to expand...
Click to collapse
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it

epikroms said:
Okay the problem you are having is that you are actually on bootloader 5 not baseband 5. So that number represents the bootloader and there is no way of downgrading as of yet. Samsung does this thing with fuses on the phone being blown as the bootloader upgrades, well as far as i know from the s8&s8+. So your problem you are having is that you are trying to flash a previous bootloader which isn't going to happen. Flashing the QK5 or the BRA1 firmware will work. Cause it's on bootloader 5. I'd you do what I said a couple posts ago you'll be fine I'm still running the U series tom with tmo kernel installed and I have actually had 0 issues so far. It's been completely solid and everything works, data, sms, Wi-Fi calling, etc...... it works after flashing and boot. With the Sprint tom I got headache after headache and the activating thing is annoying. Just do what I said and you'll see a that what jrkruse then did is probably going to be the only best thing the Sprint variant gets. Try it
Click to expand...
Click to collapse
Thanks for your reply. If it is not too much can you please break down the steps a bit more because I don't want to guess and mess it up again and also if you could please kindly point me to the other thread as well so I can download the appropriate stuff from there and read a bit more about it. I am right now unable to use the phone with the sprint firmware on it on TMo, it's super annoying.
Thanks in advance.

https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375

Did you get it sorted out? Hopefully you are on the rom and haven't bricked your device. I attached a picture so you could see that I am on what I say I am on.

epikroms said:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3572739
Don't mind all the instructions there .
1. Download the flashfire zip file and place it in your phone.
2. Download the Ufirm_multi_carrier.zip and unzip it and place the AP or TaR on your phone(the file that's inside the zip)
3. Make sure to use the eng boot and the root provided in this thread and root your phone.(root is a pain but it's worth doing for this room.)
(Note, if you have flashfire stuck on enumerating partitions you can try rebooting or Google flashfire latest app or flashfire 0.73 app and download and install it)
4. In flashfire allow root permissions and select zip and choose flashfire flashable.zip and select mount system read/write,
5. In flashfire select firmware and select the AP or TaR that you downloaded and it should have all partitions checked. Leave it and press the check mark.
6. Make sure that SuperSU is not injected. MNow click on wipe and select dalvik/cache format cache .
7. The order should be firmware then zip then wipe in flashfire.
8. Click the flash tab at bottom in flashfire.
9. In aroma, select the wipe SuperSU image, I think it's selection 2, and the rest of it is entirely up to you for what carrier you are on and so forth.
There is no need to download the Ufirmware stock for Odin because it won't stick because if the new software you have on your phone. Please make sure you know what you are doing to apply these things. These instructions worked for me and if you choose to do otherwise that's on you. I claim no responsibility for bricked devices or what you create . Flashing is a risk that we all take and it's entirely up to you.
Any more questions I'll be glad to answer. Trying to get the oreo working but having issues.
---------- Post added at 10:49 AM ---------- Previous post was at 09:58 AM ----------
May have been the wrong link sorry here is the correct one:
https://forum.xda-developers.com/tmobile-s7-edge/development/rom-t3637375
Click to expand...
Click to collapse
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?

bothambhai said:
First up, thanks a lot for your help. After a lot of tries I managed to root the phone or so I thought and that's what the phone said after I ran the root.bat file on the computer and the phone rebooted. I downloaded the flashfire app but when I turned it on it says "root access could not be acquired, are you rooted ?".
After I ran the root.bat file and the phone rebooted the phone clearly said it was rooted. How do I go ahead now ?
Click to expand...
Click to collapse
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help

thats pretty interesting being on the binary 5 baseband and binary 4 rom. to clarify, you were on the binary 5 rom and reverted? or were you on the baseband 4 and upgraded just the baseband? thanks for the info.

epikroms said:
Get the root from the thread in the link I provided .
In the file there should be something OS something flash the bat file in there it kills all Sprint stuff. Then do the root.batch file and don't worry when it removes all the SuperSU, flashfire, and so on, it's normal okay do on to the painful part......
In the command screen or terminal, it'll say to press a button when your phone has registered on the PC., this is probably where you are messing up. Watch your computer screen until the s7 pips up and watch your phone when it says Allow, MAKE SURE YOU TAP ALLOW! wait for your phone to click off on the PC and then click back on( it takes a while) then press whatever button you like and watch the terminal, if it has errors then it's not rooted if it is rooted then the terminal will close and your phone will reboot. Then proceed to flashfire and do it's thing. For good measure when your phone is booted open SuperSU app first and you'll know if your rooted. Let me know if you need more help
Click to expand...
Click to collapse
I odined the AP_Nougat_S7_Edge_EngBoot.tar.md5 then ran the root.bat file from Nougat_S7_Root_2_82_All_Carriers_V2 , I chose the options to install the fingerprint fix and install the root without any gpu tweaks. I watched the whole process complete and the cmd prompt close, my phone never asked my permission to ALLOW anything, everything was on the computer. I ran the root.bat from cmd as an administrator and the program ran evidently because it asked me about the fingerprint fix and root with or without tweaks etc. I noticed the phone reboot and there was a notification, the phone was rooted but no SU and flashwire says no root access. I tried it back from square one a couple of tries more right back from flashing stock sprint firmware and trying the whole rooting process again, same results except the next two times the phone doesn't reboot after running the root.bat file. I notice now when the phone boots up there is a sign saying "CUSTOM" beneath the samsung logo on the screen. I don't know where I am going wrong in the process though. I don't know if it is because I am on the binary 5 however I also read somewhere that people have been successful in rooting their binary 5 sprint S7 edges. I have rooted many devices before and installed roms etc, this has been, by far, the most perplexing phone in every which way.

Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.

epikroms said:
Fownt know what to say,but, you are saying that you are on binary 5 and have successfully downgraded bootloader's by flashing stock vzw firmware which is on binary 4? I don't think downgrading is possible yet?? The way I explained it to you is exactly how I did mine numerous times. I can no longer assist you though because, I kinda bricked my s7edge,
Here's something for everyone to note on a DONT DO!!!!
Do not flash the latest ENG_BOOT AND COMBO FIRMWARE.
I think it was the binary 5 QK1 eng boot and combo I forget, but after flashing back to stock firmware you will get a SBL ERROR in upload mode and let me tell you....... It is not fun at all. I had all the files necessary for unbricking, the complete restore files, I tried the z3x box, I tried octoplus, and I tried the uni-android tools and nothing flashes it over. It's insane. But I ended up sort of destroying the body of the phone but not the internal, so I now have a skeleton phone and no screen or mid frame.
So I wish you luck and probably a final goodbye to Samsung and their insaniy with phones.
Click to expand...
Click to collapse
Bummer about your phone. On a glad note I managed to root and flash my phone and everything works great now. I was taking the hard nerdy way to do it by running cmd as an administrator and having that run the root.bat file. I read somewhere else you could just double click the file and it worked for me . From there on the aroma part was pretty straightforward. I am grateful to you for pointing me in this direction and breaking it down for me, I seriously doubted me being able to achieve this on my binary 5 phone but it turned out to be smooth.
I do wish you the best and thanks once again.

Related

[Q] Firmware upgrade encountered an issue

It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
apel69 said:
It looks like I got myself in a pickle. I have a GS4 running 4.2.2. I picked up my phone today and successfully rooted it with instructions from DroidView using files from chainfire. I then installed CWM recovery with ROM Manager and backed up my ROM with it. I decided to replace chainfires SU with the one fom CWM like I had on my S3. After rebooting from recovery mode I noticed I had lost root so I used the same method to root it again because I thought it had reset itself. Before the reboot occurred there was option to prevent the possibility of the ROM flashing itself to stock. I went to select the Yes option but bumped the power button which selected No. While trying to reroot and failing, the phone displayed the message "Invalid percent of drawing download progress bar." On reboot the error “Firmware upgrade encountered an issue“ along with a cone and a couple of other pics. I have tried to get into recovery mode several times but repeatedly get this error. I can get into download mode and have tried to flash the stock ROM for this phone but it fails in Odin 3.0.7. Odin sees my phone and verifies the md5 but fails very quickly upon clicking start. I tried this with KiesPDLR running in the background and disabled. I have not tried anything else out of concern for messing it up further. Attached are screenshots and log from ODIN along with the text that is being displayed in download mode. (I will have to post these later as the attachments option will not work properly on my wife's S3).
Two other notes. 1) I used ODIN 1.85 to root as that was what was included in the chainfire download. But I used ODIN 3.0.7 to try and unroot because that's what the DroidView directions said. Would it make any difference to use ODIN 1.85 to try and flash the stock firmware? It sees my phone as well but the F. Reset Time option is unchecked and grayed out and the directions says it needs to be checked. Don't know if that really makes a difference. 2) My phone is actually with US cellular but there is not a forum for this carrier. I chose this forum because my previous phone the Mesmerize had an identical model number as the Fascinate. Please do not pass over my request for help because of this as I am in dire need.
Click to expand...
Click to collapse
Try odin 1.85 I use that to odin back to stock and dont worry about the other ones just make sure auto reboot is checked.
Also are you sure the phone you have is the sprint gs4 sph l720 jfltespr?? Cause odin a tar file not for the phone could potentially brick the phone.
Sent from my SPH-L720 using xda app-developers app
I would try to download the stock rom from a different source if you can. These tar files are so large for this phone that the possibility of a bad download is pretty high. Also, make sure you don't have to extract the actual .tar file first from the archive you download. Lots of these stock roms are repackaged into a zip file and you need to extract the tar file for use in Odin before installing.
I am back in business. I have my phone and home internet back now. Yeah. I used the same stock ROM I had since it was the same as sammobile which was also a zip file and I already had it on my system. I just used Odin 1.85 instead. I guess I could have done this earlier and prevented a near stoke but everything else I had done seemed to get me deeper in a hole. These large zip files have always made me a bit nervous but I haven't found where to get one otherwise.
I have some follow up questions.
1) Why would it flash with Odin 1.85 and not with 3.0.7?
2) Is CWM's SU not compatible with the S4? Everything was working fine until I switched this from chainfire to CWM using ROM Manager.
3) Is there a good source with unzipped ROM's?
Chainfires SuperSU is much better with JellyBean than cwm SU. For some reason most people that try to switch to SU from SuperSU have the same problem you had.
Sent from my icrap 2 using Tapatalk HD
Okay. I decided to go with chainfires after this fun little ordeal. The few small things I preferred from CWM is not worth it. Besides it looks like chainfire made some upgrades since I last looked at it. I guess I was lucky with my S3 because I converted several times.
Thanks for all the help everyone.

[Q] Please help w/ getting back to stock.

I don't want this post to be too long but I need some help here, let me sum it up.
I purchased a secondhand Note3 off Ebay to replace my Note2. I got it an it appears to me that it's been "modified", I see this SafeStrap thing at startup and a SuperSU App. Once I saw this I decided to hold off on putting my sim card in and have just been using it on wifi. I used the "RootChecker" app to see if it's rooted and it tells me yes. System info tells me the phone is running 4.3. I know not much of this rooting, flashing, roms, kernel scene. So:
- My goal is to get this phone back to stock setting, no SafeStrap or root of any kind if it's there, so the phone operates and is just as it would be if purchased new from Verizon. What is the easiest way to go about doing this?
From there I might actually think of trying my hand at rooting this thing since it's a secondhand device, but I first want to eliminate any modifications made to the phone by the previous owner, and if I do root I want to start from ground zero and do it myself.
I apologize for my ignorance in this but could really use the help and hopefully learn more about this world along the way since it seems everyone who roots swears by it, I must be missing something but for now my objective is a clean slate with this device
Thanks in advance.
mgftp said:
I don't want this post to be too long but I need some help here, let me sum it up.
I purchased a secondhand Note3 off Ebay to replace my Note2. I got it an it appears to me that it's been "modified", I see this SafeStrap thing at startup and a SuperSU App. Once I saw this I decided to hold off on putting my sim card in and have just been using it on wifi. I used the "RootChecker" app to see if it's rooted and it tells me yes. System info tells me the phone is running 4.3. I know not much of this rooting, flashing, roms, kernel scene. So:
- My goal is to get this phone back to stock setting, no SafeStrap or root of any kind if it's there, so the phone operates and is just as it would be if purchased new from Verizon. What is the easiest way to go about doing this?
From there I might actually think of trying my hand at rooting this thing since it's a secondhand device, but I first want to eliminate any modifications made to the phone by the previous owner, and if I do root I want to start from ground zero and do it myself.
I apologize for my ignorance in this but could really use the help and hopefully learn more about this world along the way since it seems everyone who roots swears by it, I must be missing something but for now my objective is a clean slate with this device
Thanks in advance.
Click to expand...
Click to collapse
You're basically going to use Oding to flash the MJE software. Everything you need for instructions and files can be found HERE.
airmaxx23 said:
You're basically going to use Oding to flash the MJE software. Everything you need for instructions and files can be found HERE.
Click to expand...
Click to collapse
Thanks so much. Following this will remove safestrap, unroot, and basically undo any changes made to the phone and bring it back to 4.3 out of the box from Verizon status? If so, I'll give this a go tomorrow.
mgftp said:
Thanks so much. Following this will remove safestrap, unroot, and basically undo any changes made to the phone and bring it back to 4.3 out of the box from Verizon status? If so, I'll give this a go tomorrow.
Click to expand...
Click to collapse
Yes it will.
And since you're new to this, even tho it is a straight - forward procedure, read and make sure you understand what you are doing before proceeding. Ask additional questions if necessary. And let us know how it goes!
《 #VerizonLovesYou 》
airmaxx23 said:
Yes it will.
Click to expand...
Click to collapse
LeftyGR said:
And since you're new to this, even tho it is a straight - forward procedure, read and make sure you understand what you are doing before proceeding. Ask additional questions if necessary. And let us know how it goes!
《 #VerizonLovesYou 》
Click to expand...
Click to collapse
Thanks guys, hopefully I can find some time tomorrow to tackle this.
One question just reading through the guide quickly, for step 2, downloading the stock image, I assume I want 4.3 for retail? IF so, I see 3 options: Official VRUBMJE 4.3, Official VRUBMJ7 4.3, and Official VRUBMI9 4.3. Does it matter which one? I am assuming they are just different releases of 4.3 but not sure, or if I could pick one that would work better than another.
I'll copy and paste the info below if you don't know off-hand what I am referring to.
Thanks again! :good:
Section 1: How to return to Stock Android 4.3 and recover from a Soft Brick.
Take Note If your Retail Locked N3 took the OTA update, you can not revert back to older firmware. Verizon now has Samsung blacklist the older firmwares bootloader after each update. If you try and flash older firmware the device will softbrick.
Step 1: Download and install Odin to a Windows based PC- http://forum.xda-developers.com/show....php?t=2189539
Step 2: Download a stock Odin image and Pit file to the PC. If Odin does not recognize the file then extract it with a program such as 7zip.
RETAIL Locked N3 Restore Files
Official VRUCNC4 4.4.2- http://samsung-updates.com/details/2...0VVRUCNC4.html(Only use this if you took the OTA or do not mind being stuck on stock...there is currently no root method available yet!)
Official VRUBMJE 4.3- http://www.androidfilehost.com/?fid=23269279319196106(Retail locked N3 only)
Official VRUBMJ7 4.3- http://d-h.st/IEW(Retail Locked N3 ONLY)
Official VRUBMI9 4.3- https://docs.google.com/file/d/0B26p...LWs/edit?pli=1(Retail Locked N3 ONLY)
Developer Edition N3 Restore Files
DE_VRUBMJE 4.3-http://www.androidfilehost.com/?fid=23269279319196402
-------------
HLTE_32gb.PitFile- http://www.androidfilehost.com/?fid=23159073880936457(works for bothe DE and Retail devices)
Step 3: Power device off, hold the volume down/home/power keys until you see a yellow triangle, then press the volume up key to access "odin or download mode".
Step 4: Open Odin and connect the oem usb cable from pc to device. The driver should automatically install( it did for me on windows 7 64bit). There should also be a "comport number" in upper left hand corner of Odin indicating communication between the pc & device.
*If the drivers do not automatically install, then manually install the drivers in link and proceed to the next step. http://forum.xda-developers.com/show....php?t=2038555
Step 5: Click on the Pit function of Odin and select Pit file you downloaded in Step:2.
Step 6: Click on the AP/PDA(depends on Odin version) function of Odin. Select the stock 4.3 image you downloaded in step 2, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Step 7: Your device should boot back up into factory stock 4.3 Android! However, these stock Odin files do not wipe data. To wipe data, power the device off, press and hold the volume up/home/power buttons until the samsung logo appears. The device will boot into recovery and from there you will need to wipe data/factory reset, then reboot.
Click to expand...
Click to collapse
The mje should do fime. It's the latest jb stock firmware. Once you boot up into that, your phone should promt you to accept the new kk update.
I know you do not want or care about root, but I'll say this anyways. Once you've accepted the new ota update, there's no way to root and there's no way to get back to jb. Like I said, probably not a concern of yours... just throwing it out there.
《 #VerizonLovesYou 》
Hey guys, in the process to this and stuck at these steps:
Step 5: Click on the Pit function of Odin and select Pit file you downloaded in Step:2.
Step 6: Click on the AP/PDA(depends on Odin version) function of Odin. Select the stock 4.3 image you downloaded in step 2, then select start. This operation should take less than 8 minutes before Odin will say pass/reset.
Click to expand...
Click to collapse
Following step 2 gave me one file, which I believe is the 4.3 image ( the file is 1.28GB). What exactly is the Pit file I am missing and how do I get it?
Thanks
u shouldnt need it. I think its a fix for a bootloop. I've returned my note 3 to stock many of times and havent had the use for a pit file
Sent from my SM-N900V using Tapatalk
mike7728 said:
u shouldnt need it. I think its a fix for a bootloop. I've returned my note 3 to stock many of times and havent had the use for a pit file
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
So essentially I just skip step 5 in that guide and proceed?
Thanks for the response.
mgftp said:
So essentially I just skip step 5 in that guide and proceed?
Thanks for the response.
Click to expand...
Click to collapse
Correct. The pit file is really only needed to fully wipe and reparation the phone.
《 #VerizonLovesYou 》
Thanks guys, giving this a go now... will report back.
Another hangup, clicking on AP in Odin it doesn't seem to recognize the image file I downloaded. It seems to be looking for .tar, .md5, .smd, .gz, and .tgz . The file I got from the guide is .7z
Am I doing something wrong?
mgftp said:
Another hangup, clicking on AP in Odin it doesn't seem to recognize the image file I downloaded. It seems to be looking for .tar, .md5, .smd, .gz, and .tgz . The file I got from the guide is .7z
Am I doing something wrong?
Click to expand...
Click to collapse
You need to download a program called 7zip and use that to extract the md5.
ouch1976 said:
You need to download a program called 7zip and use that to extract the md5.
Click to expand...
Click to collapse
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..
mgftp said:
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..
Click to expand...
Click to collapse
So 30min later no change, I feel as if it's frozen but scared to power down phone or try to exit application :/
mgftp said:
Thanks!
-
Now how do I know if Odin is working? It doesn't seem to be doing anything that I can tell. Last message is "D:0/004> Odin v.3 engine (ID:4)..
Click to expand...
Click to collapse
Sounds like you're all set to go. Just add the md5 to the PDA section and click start.
mgftp said:
So 30min later no change, I feel as if it's frozen but scared to power down phone or try to exit application :/
Click to expand...
Click to collapse
Across the top of odin, there's a series of boxes. Are any not blank?
《 #VerizonLovesYou 》
ouch1976 said:
Sounds like you're all set to go. Just add the md5 to the PDA section and click start.
Click to expand...
Click to collapse
I clicked start and I am 99% sure it's frozen, I don't see anything that would indicate that it's working and it's nearly 1 hour later.
Is it safe to try and power down the phone and/or exit Odin and try again or could that screw something up?
mgftp said:
I clicked start and I am 99% sure it's frozen, I don't see anything that would indicate that it's working and it's nearly 1 hour later.
Is it safe to try and power down the phone and/or exit Odin and try again or could that screw something up?
Click to expand...
Click to collapse
If you haven't run anything then you're safe to reboot it.

Samsung Galaxy Note 3 (SM-N900) - Rooting failed (Odin stuck), need to recover

Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?
GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots

[Guide] How to Convert BACK to 100% Stock T-Mobile from 950U1 Firmware

Hi everyone,
If you've clicked on this thread you are probably just like me. You have a T-Mobile Galaxy S8 (950U) and wanted to try the unbranded/unlocked firmware. Maybe you thought it would SIM unlock your phone (Nope) or maybe you thought you'd like it but just don't. I was unable to find anyone who successfully reverted back to fully stock T-Mobile. My phone stayed XAA/XAA/TMB no matter what I did. Well, now I'm TMB/TMB/TMB and here to hopefully help you do the same.
I mostly followed this post: https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487. Here's the instructions:
1. Download Factory Binary, EngBoot, and the G950W firmware.
2. Turn off phone
3. Hold down on Bixby button + power + volume down
4. open Odin v3.12.7
5. add the Factory Binary to the AP section of Odin.
6. Plug your phone into your computer (NEEDS TO BE WINDOWS) with Odin open
7. Make sure your device is connected and recognized by Odin.
8. Click start.
9. One the phone reboots run the ADB command, adb reboot bootloader
10. Open PrinceComsy (modded) Odin and flash the EngBoot
11. Click start
12. Once the phone reboots type the command adb reboot bootloader
13. Put the HOME_CSC of the G950W firmware into the CSC part of Odin 3.12.7 (NOT PrinceComsy)
14. Click start
15. Open IME setting on Factory Binary
16. Type in *#243203855#
17. Select XAC
****NOTE ABOUT 15-17: A bunch of system processes kept saying they were force closing, but I just kept saying OK until I could successfully type the code into the dialer and select XAC. It worked, even with those processes supposedly failing.****
18. Click install
19. Wait for phone to reboot
20. Once it does open terminal and type in adb shell
21. Then type in echo "TMB" > /efs/imei/mps_code.dat
22. Type in exit into adb shell
23. Type in adb reboot bootloader
24. Flash the G950U T-Mobile firmware without Userdata. Also make sure to flash the non-home CSC.
25. Enjoy your reverted back to T-Mobile 100% stock phone.
Files you will need:
Factory Binary: https://www.androidfilehost.com/?fid=745425885120727548
Eng-Boot for 950U: https://drive.google.com/file/d/0B4NKFp9A7CsoSmpzeEFMSldhRlU/view?usp=sharing
Combination (950W) firmware for the Home_CSC: https://updato.com/firmware-archive-select-model?record=0465B78C273A11E7963AFA163EE8F90B
PrinceComsey Odin: https://www.androidfilehost.com/?fid=24588232905724860
Odin 3.12.7: https://mega.nz/#!UtI02CbY!XnmV7scm-HJq-lBUP5nOyDzs3Uwwmt17ldrfcl-9xoM
T-Mobile Stock firmware: https://updato.com/firmware-archive-select-model?record=4F86A80C2FA111E7963AFA163EE8F90B
Great work, bro
This was all mine. I did all of this. Why does nobody say anything about me doing it. It is in the EngBoot + Root thread. I mean really, thank the people that actually DO the work.
mweinbach said:
This was all mine. I did all of this. Why does nobody say anything about me doing it. It is in the EngBoot + Root thread. I mean really, thank the people that actually DO the work.
Click to expand...
Click to collapse
Agreed, I used your guide to help me get back to TMo version. You will find variation of your work here and there. But I agreed that OP should be credited.
mweinbach said:
This was all mine. I did all of this. Why does nobody say anything about me doing it. It is in the EngBoot + Root thread. I mean really, thank the people that actually DO the work.
Click to expand...
Click to collapse
Happy to give you credit man. I spent days asking on four or five threads if anyone had converted their T-Mobile S8 back to 100% stock. I found no one. One guy mentioned he got his Verizon S8 back to stock.
I found the carrier switch thread ...which gave great instructions, but didn't tell you anything about where to get these files. So I searched around to get the files and spent a good two hours trying and failing until it worked. I figured a thread with not only the instructions, but also all the files you need...would be helpful.
I'm on XDA a few times a year when a new phone comes out. I could literally care less about "credit." However, I can tell you do...and I am thankful for your instructions. I would honestly have no problem with me deleting this thread, having you copy the text, and then you can post the same thing again only with your name as the thread maker. Let me know.
dharmastation3 said:
Happy to give you credit man. I spent days asking on four or five threads if anyone had converted their T-Mobile S8 back to 100% stock. I found no one. One guy mentioned he got his Verizon S8 back to stock.
I found the carrier switch thread ...which gave great instructions, but didn't tell you anything about where to get these files. So I searched around to get the files and spent a good two hours trying and failing until it worked. I figured a thread with not only the instructions, but also all the files you need...would be helpful.
I'm on XDA a few times a year when a new phone comes out. I could literally care less about "credit." However, I can tell you do...and I am thankful for your instructions. I would honestly have no problem with me deleting this thread, having you copy the text, and then you can post the same thing again only with your name as the thread maker. Let me know.
Click to expand...
Click to collapse
I just care that people know who came up with what. If you dont want to add credit, fine. But dont delete this because some people might not know where to go for info.
mweinbach said:
I just care that people know who came up with what. If you dont want to add credit, fine. But dont delete this because some people might not know where to go for info.
Click to expand...
Click to collapse
Can you copy the instructions (and the files I gathered in this thread) and make your own post? I will delete this if you do. Because it does no one any good to have the comments on here being about people wanting credit. Why don't you just re-post this under your username?
All I care about is helping people.
dharmastation3 said:
Hi everyone,
If you've clicked on this thread you are probably just like me. You have a T-Mobile Galaxy S8 (950U) and wanted to try the unbranded/unlocked firmware. Maybe you thought it would SIM unlock your phone (Nope) or maybe you thought you'd like it but just don't. I was unable to find anyone who successfully reverted back to fully stock T-Mobile. My phone stayed XAA/XAA/TMB no matter what I did. Well, now I'm TMB/TMB/TMB and here to hopefully help you do the same.
I mostly followed this post: https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487. Here's the instructions:
1. Download Factory Binary, EngBoot, and the G950W firmware.
2. Turn off phone
3. Hold down on Bixby button + power + volume down
4. open Odin v3.12.7
5. add the Factory Binary to the AP section of Odin.
6. Plug your phone into your computer (NEEDS TO BE WINDOWS) with Odin open
7. Make sure your device is connected and recognized by Odin.
8. Click start.
9. One the phone reboots run the ADB command, adb reboot bootloader
10. Open PrinceComsy (modded) Odin and flash the EngBoot
11. Click start
12. Once the phone reboots type the command adb reboot bootloader
13. Put the HOME_CSC of the G950W firmware into the CSC part of Odin 3.12.7 (NOT PrinceComsy)
14. Click start
15. Open IME setting on Factory Binary
16. Type in *#243203855#
17. Select XAC
****NOTE ABOUT 15-17: A bunch of system processes kept saying they were force closing, but I just kept saying OK until I could successfully type the code into the dialer and select XAC. It worked, even with those processes supposedly failing.****
18. Click install
19. Wait for phone to reboot
20. Once it does open terminal and type in adb shell
21. Then type in echo "TMB" > /efs/imei/mps_code.dat
22. Type in exit into adb shell
23. Type in adb reboot bootloader
24. Flash the G950U T-Mobile firmware without Userdata. Also make sure to flash the non-home CSC.
25. Enjoy your reverted back to T-Mobile 100% stock phone.
Files you will need:
Factory Binary: https://www.androidfilehost.com/?fid=745425885120727548
Eng-Boot for 950U: https://drive.google.com/file/d/0B4NKFp9A7CsoSmpzeEFMSldhRlU/view?usp=sharing
Combination (950W) firmware for the Home_CSC: https://updato.com/firmware-archive-select-model?record=0465B78C273A11E7963AFA163EE8F90B
PrinceComsey Odin: https://www.androidfilehost.com/?fid=24588232905724860
Odin 3.12.7: https://mega.nz/#!UtI02CbY!XnmV7scm-HJq-lBUP5nOyDzs3Uwwmt17ldrfcl-9xoM
T-Mobile Stock firmware: https://updato.com/firmware-archive-select-model?record=4F86A80C2FA111E7963AFA163EE8F90B
Click to expand...
Click to collapse
Where would I check if I'm TMB/TMB/TMB? I went from XAA firmware back to stock TMB firmware using official Odin 3.12.7 and all seems fine. I don't see any issues at all but I do wanna confirm everything is good to go.
Sent from my SM-G955U using Tapatalk
Rydah805 said:
Where would I check if I'm TMB/TMB/TMB? I went from XAA firmware back to stock TMB firmware using official Odin 3.12.7 and all seems fine. I don't see any issues at all but I do wanna confirm everything is good to go.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Settings / About phone / Service provider SW ver.
yusssi said:
Settings / About phone / Service provider SW ver.
Click to expand...
Click to collapse
Figured it out after I posted but thanks for confirming. ??
Sent from my SM-G955U using Tapatalk
Is there any way to go to the TMobile firmware, just without the Tmo splash screen?
Zorn_ said:
Is there any way to go to the TMobile firmware, just without the Tmo splash screen?
Click to expand...
Click to collapse
G950U1 firmware is the closest I have seen.
mweinbach said:
G950U1 firmware is the closest I have seen.
Click to expand...
Click to collapse
If you follow all the steps to change the CSC to TMB, then at the very end flash the unlocked G950U1 firmware, does the phone still identify as TMobile? And would you be able to get the TMobile updates (like the 6/7 update)?
Zorn_ said:
If you follow all the steps to change the CSC to TMB, then at the very end flash the unlocked G950U1 firmware, does the phone still identify as TMobile? And would you be able to get the TMobile updates (like the 6/7 update)?
Click to expand...
Click to collapse
Nope, the systems are different. The updates are also different. The G950U1 ones come from samsung the others come from TMobile.
mweinbach said:
Nope, the systems are different. The updates are also different. The G950U1 ones come from samsung the others come from TMobile.
Click to expand...
Click to collapse
Gotcha. Thanks for your replies. Main reason I'm worried about staying on the unlocked firmware is Samsung's horrible reputation for updates last time around. I'm afraid we won't get the updates on this firmware until 6 months after the carrier versions.
Can I use this ROM and instructions to switch from Verizon S8 to Tmobile S8 Rom?
Thanks
---------- Post added at 07:25 PM ---------- Previous post was at 07:19 PM ----------
rider4ever said:
Can I use this ROM and instructions to switch from Verizon S8 to Tmobile S8 Rom?
Thanks
Click to expand...
Click to collapse
Found this: https://forum.xda-developers.com/galaxy-s8/how-to/switch-to-carrier-firmware-100-t3609487
Help
When I try to flash the home_csc in the CSC spot odin then click 'start' odin says Fail!SHA256 is invalid.
I thought if we just flashed 950u1 firmware we could just flash straight back to the tmobile stock firmware in the same method.
So this whole thread is about 950U1, which is the S8, what about S8+? I have a T-Mobile S8+, flashed the unlocked version firmware, wanted to go back, but this instruction only deals with 950U1, what about 955U1?
Ok, i can say if you just flashed the 950u1 or 955u1 firmware with modified odin. All you have to do is flash the tmobile firmware with official odin and then do a data reset from the bootloader menu.
I was able to go right back to official tmobile firmware and get OTA updates.

Stock bootoloader for Samsung Galaxy S7 SM-G930V

Hi community
I have a Samsung Galaxy S7 SM-G930V with Android 7.0. I tried to get root but first I had to unlock bootloader. I flashed the "Engineer Bootloader" (a file named Samsung_G930x_QC_Rooted_BOOT.TAR) with Odin for engineering bootloader and no problem then the phone reboot. There comes the problem, the phone is on a bootloop, it shows the screen "Samsung Galaxy S7" and restart again, over and over.
People suggest to go to recovery mode and wipe data and factory reset, I already did that but it didn't work.
I'm sure that flash the complete ROM again will solve the problem but the ROM is 2.50 GB and my Internet connection is very very slow so I can't download it. Maybe flashing just the custom boot.img the problem gets solved, can somebody bring me just that file? Please I need it really much.
Thank you very much.
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
dude, THANK YOU VERY MUCH!!! you saved my life. I don't understand why people post tutorials with wrong files. THANK YOU VERY MUCH AGAIN.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Wow... I have searched high an low for this. Thank you.
CVertigo1 said:
From the way the file name is written, it looks like the Marshmallow kernel, which is not the correct one for Nougat. Try flashing this in the AP slot in Odin. This is the correct root kernel for Nougat. The phone may bootloop a couple times after flashing this before completely booting.
Note: We are talking about engineering kernels, not bootloaders.
Click to expand...
Click to collapse
Is there a version of this that's just stock, no root or special engineering version?
ItsKipz said:
Is there a version of this that's just stock, no root or special engineering version?
Click to expand...
Click to collapse
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Scottie32583 said:
Hi I was just experimenting with the Verizon Recovery Utility tools on windows 10 on the computer and noticed it was temporary copying ALL BL, AP, CSC ext. Well I selected it and copied in another folder before it could erase the files when done flashing my S7 verizon back to stock. It worked! I got all the files straight from Verizon's official tool. Since windows will throw a error message to anything trying to delete files in use, when verizon tool tried to erase the temp stock files, it denied it since the file was in use by me. Aka copying to another folder as the verizon tool downloaded the files I was right there copying the files mid download and the computer let the files finish download complete and it ended up being I got the files. Im proud of myself. Lol! Being new at this.
So someone just tell me what I do to get you all a copy. They are the most current stock files from verizon. I uploaded them all into Onedrive already so files are safe just waiting for the moment someone needs them and tells me how to upload them. I see androidhostfile or something site. Can I use that one? Even though Im new at this?
Here is my screen shot of my new files.
Click to expand...
Click to collapse
This is what the file looks like I have...

Categories

Resources