Last night i tried installing Clockwork Recovery on my Tab (it's a US T-Mobile model). I got an error message in ADB, but i thought i had worked through the issues. Then i installed Rom Manager and tried to make a backup through Rom Manager. It rebooted my Tab, but it never made it to Recovery; it froze on the white T-Mobile screen. At this point, i can reboot, but it always gets stuck on the white T-Mobile screen. If i hold down volume-down and power, i get into download mode, and if i hold down both volume-up and volume-down with power i get some text (sorry, can't remember specifics b/c i'm at work w/o my Tab).
I'm not a total Android noob, but i am new to Samsung (i've had a Droid and a Droid X, and i am very familiar with SBF-ing Mototorla android devices... i assumed that Samsung devices used something similar but i guess i was wrong). I feel that since i can get into download-mode, i should be able to re-flash the stock firmware and resurrect my Tab, but i'm not familiar enough with Odin (which i gather is what i'll need to use) to know HOW to do this, let alone where to get the correct version of Odin. I have found a file on these forums: T-Mobile.zip, which i think is what i'll need to flash, but again, i don't know how to do it.
I'd appreciate if someone would take pity on me and help me through my problems!
-dave
Looks like i figured it out myself. Thanks to anyone who was contemplating a reply
-d
What was the fix?
Just out of curiosity, how did you resolve it?
As i said in my original post, i had found a T-Mobile.zip file on these forums. I originally tried using Odin to flash it to my Tab without success. Then, while scouring the web for answers, i found a blog post where someone flashed that same file to his semi-bricked Tab and it worked. The video showed the version number of Odin (1.7), which was different than the version i had tried using. Sooooo, i found v1.7 online, downloaded it, and used the PDA option to flash T-Mobile.zip to my Tab... and it WORKED!
I did have a lot of force quits of my apps after rebooting, and the guy on the blog said that if this happened, to do a factory data rest. So, success AND now i know how to flash back to stock which is even better! I hope this info is useful to others who get themselves into the situation i got myself into.
-d
impulse630 said:
As i said in my original post, i had found a T-Mobile.zip file on these forums. I originally tried using Odin to flash it to my Tab without success. ack to stock which is even better! I hope this info is useful to others who get themselves into the situation i got myself into.
-d
Click to expand...
Click to collapse
Hi impulse ..can you please point to post where is the t-mobile.zip file you are referring to...is this a complete t-mobile rom which can be flashed normally using odin ..or maybe other procedure needed ....my regards.
Here's the link to the thread: http://forum.xda-developers.com/showthread.php?t=855851
-d
This started as a beg for help thread, but since the GS4 is coming up on 3 generations old, help is quite slow, yet does still exist as of this edit (3-20-15).
None the less, I will try to explain what happened so that people searching for similar problems might find this thread and resolve their issues.
I soft bricked the phone flashing PacMan. ... The instructions CLEARLY stated that you need to flash the rom, then flash GApps. Well, I forgot to Flash Gapps because I was so excited that I had a successful root and new rom to test that I finger ganged the phone.... The phone booted just fine and worked just fine, but I did not have ANY google apps, and went into a panic... LESSON #1 DO NOT PANIC......
What I failed to realize is that Android Lolipop (at least PacMan's version) requires the user to select options in the developer section of the settings menu to enable you to boot into your custom recovery after you have flashed your custom rom.... I DID NOT KNOW THIS and the information was NOT readily available. So what happened was I panicked and tried to flash another recovery which was apparently NOT the correct recovery for my phone.. (the cascade of errors began here). My phone was soft bricked and NOTHING I did would get me out of it.
So, after at least 50 attempts using Odin to try and flash a good recovery, re-root the phone, whatever I could think of, I finally got out of soft brick, and back to a working phone, yet still no google apps, and no recovery (or so I thought).
By this time, I had asked ....no. begged for help on 2 or 3 different threads to no avail when what I thought was a brain storm came to me.... I googled and located the google play store apk, and google play services apk and thought that if I could just get these 2 things installed, I would be able to log onto the google play store and download the apps I need and all would be right with the world....... Yeah.... Remember the cascade of errors thing I mentioned a few lines up ^^^ ?
Once I installed those 2 apk's and rebooted the phone, I was in nag screen hell with no way out, no custom recovery (remember...or so I thought) and no way to access ANYTHING on the phone because literally the second I hit "ok" on the nag screen, it would immediately pop back up...This "nag screen" was the one that pops up and tells you that "google play services has stopped working".. I came inches away from launching the phone against the wall and buying another one... something... anything but a Samsung GS4.
So here we are, 14 hours (of actual face in the phone, Odin, XDA, Google, YouTube) frantically searching for ANY solution.....and NOTHING presented itself, when I decided to take a step back and walk away from it for a couple of hours.......
The next thing I tried was pounding my way through the nag screen... Literally hitting the "ok" toggle to clear the screen, while instantly trying to hit any other button on the screen to get me into the settings menu, because during my little self imposed time out, I had an epiphany.... of sorts..... What really happened is that I remembered seeing a "factory reset" toggle in the settings menus somewhere.....and I was determined to find it........ SO....... 13,386,329 clicks of the "ok" button later, I managed to engage the factory reset switch at the exact right moment, followed by another 4,388 presses of the "ok" button to get to the "confirm" button.......... and like a beacon from heaven...... My phone rebooted, and factory reset, and the #%g^7**&^|@# nag screen was GONE !!!!! Oh my GOD it was GONE !!!!!!! After recovering from my full blown conniption, catching my breath and feeling like a raver must feel after a good night of Molly and glow stick euphoria, I had a working phone again..... almost.
What I did next was go immediately to Odin, re-root the phone, install a DIFFERENT rom, and the latest version of TWRP and like another beacon from the gods I had a wonderfully functional phone with all of the google apps I needed.... and all was good with the world........Pretty much....
I am nearly certain that I cost myself 5 years of healthy living with the stress I imposed upon myself throughout this ordeal ---- The following are lessons learned. Hopefully they save you from madness...
(1) Do NOT use a USB hub to connect your phone to the computer. The phone MUST be connected directly to a USB port on your machine.
(2) Understand the workings of the rom you are going to flash BEFORE you flash it.
(3) DO NOT PANIC
(4) DO NOT randomly install apk's just because you think you are smarter than a 5th grader, and you are so mad your phone doesn't work, you are going to try anything regardless of how retarded it might be.
LAST BUT NOT LEAST and actually probably the MOST IMPORTANT thing to do is locate, download and CONFIRM GOOD a stock firmware for YOUR phone BEFORE YOU ROOT or flash a new rom..... If you get to brick he11 like I did, you will spend more time searching for the tools to get back to zero than you can imagine. You will be revved up, angry with the world, and your google fu will fail you......miserably I might add......
Get all of your ducks in a row BEFORE you root, and before you flash a new rom. That means finding the stock firmware and opening it up in Odin with your phone connected to CONFIRM you have a good firmware to go back to should you fail miserably.... Your very sanity could depend on it...
Team Scream said:
Does anyone have and is willing to share a stock Galaxy S4 rom so I can go back to stock on my phone? I am currently soft bricked and completely dead in the water...
I need to be able to flash the rom using Odin since that is the ONLY way I can communicate with this phone right now....I can flash whatever recovery I want using Odin, but I cannot boot into that recovery once successfully flashed with Odin. It boot loops and goes back to the completely useless PacMan 5.02 rom I flashed previously that repeatedly shows the "google play services has stopped working" screen.... and no number of attempts to clear it by hitting ok will get me to a working desktop
I bricked my phone by flashing PacMan and forgetting to flash GAPPS before rebooting, then trying to install google play services apk and google play store apk manually because I could not get back into recovery for whatever reason....
I have spent the ENTIRE day searching for a stock rom that I can flash with Odin so I can at least get back to zero with this S4 which is actually a brand new phone for me....
PLEASE do not link me to mediafire or rapidgator downloads because I have tried every one of those that google will reveal.. I need one that YOU know is good, and will work. NONE.... NOT ONE of the files I have been able to find online are legitimate .tar files... They ALL unzip with errors and I have tried them on multiple computers.....Multiple download attempts and NOTHING... I have literally been at this for 10 hours now and really need some love.
On a side note, if I can pull the stock rom from my wifes brand new S4 without screwing up her phone, PLEASE tell me how to do that. She literally picked up her brand new replacement S4 today...
Any help is genuinely appreciated... PLEASE.
Click to expand...
Click to collapse
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S4 (SPH-L720)/Stock ROMs
KennyG123 said:
http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung Galaxy S4 (SPH-L720)/Stock ROMs
Click to expand...
Click to collapse
Man thank you! THANK YOU! I really appreciate it... I woke this morning to find this reply after leaving my computer running all night for another corrupted downloaded image file.... I have my fingers crossed !!! THANK YOU
P.S. how do I know which one of those files I actually need? I have no idea what the difference is in each of those folders.... Forgive me for noob but I really am pretty noob at this.....
I just looked at the link to help you and noticed that Wilco stops at the NAE baseband. A lot of phones are on the NG2 baseband and if you have a 720T, it could be even a different baseband. Go to settings, "About Phone". Look for" "Baseband" and "Model Number". Write that information down. Once you have that, the last three characters are what is in the list in the link KennyG123 sent you. (For example, I have the original S4 so I have a SPH-L720 and my baseband is L720VPUFNG2 (or NG2 for short. Which was not on that list.) If it is not on the list, go to www.sammobile.com and search for your model number (For example, I am on the SPH-L720. If you just bought your phone from Sprint, you probably have the SPH-L720 or SPH-L720T). You can download the tar file from there. It is a little slow but it will get it done for you. The tar file for both phones are here in this forum if you want to search but going to Sammobile would probably be a little easier from the sounds of it.
dyandell said:
I just looked at the link to help you and noticed that Wilco stops at the NAE baseband. <snip>
Click to expand...
Click to collapse
Hey brother, thank you so much for the help and reply. I might have forgot to mention that I cannot get into the phone to read the model # or get any information from it at all. The nag screen telling me that google play services has stopped working is so persistent that I can't do anything with the phone once it boots.
Is there a way to brute force wipe the phone so that the only thing left when that process is done is a custom recovery like TWRP or Philz or anything other than stock?
If so, would you be so kind as to point me in the direction of a tutorial that would help me get through that process.... I am either not using the right search terms or I am just too old to be good at this and should have stayed home when the rooting lessons were being handed out...
Anyway, I genuinely appreciate your help... Thank you so much !!
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
<<<<<<<< EDIT>>>>>>>>>
I was also able to pound my way into the settings menu and do a factory reset which removed the google play nag. From there I was able to root around in the developer options folder where I discovered that in order to be able to boot into recovery, you need to select the "boot options" tab and allow the device to boot into recovery....
I know this device is old now and most people have moved on, and I am pleased that there are some people who stick around here to keep this device alive. I only wish that someone would have advised me to check the boot options selection when I indicated I could not boot into recovery... That would have saved me 2 days of manic obsessive he11....... This was complete he11...... But I am on the other side of it now, and have reflashed another rom... I am back among the living.
Team Scream said:
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
Click to expand...
Click to collapse
Sprint phones have always been able to downgrade and thinking that has not changed. You should be able to Odin the last one listed on the link I gave you...NAE...then your phone should boot...you can then take the Sprint OTA if you like then root and recovery as normal. Then you can get to the stuff on your SD and flash. The only issues I remember popping up these days is if you mismatch the modem and OS...which wouldn't be the case if you Odin'd NAE.
Team Scream said:
Ok I was able to pound my way through the nag screen to the settings menu and eventually got to the baseband and model #
baseband: L720TVPUBOA3
model #: SPH-L720
I have tried 3 times to download the only version I can find on the sammobile.com website using the baseband to search and the file fails to download after getting about 2/3 complete.... I have tried it on 2 separate computers from 2 different locations now...... This is horrifying ...... Every single force that can be working against me, is working against me.
Ugh...... If you have a link to a method I can use to force wipe the phone without a stock rom, but with a recovery I can boot into to flash a rom I have on my external SD card, I would love to see it...... im losing my mind here...
<<<<<<<< EDIT>>>>>>>>>
I was also able to pound my way into the settings menu and do a factory reset which removed the google play nag. From there I was able to root around in the developer options folder where I discovered that in order to be able to boot into recovery, you need to select the "boot options" tab and allow the device to boot into recovery....
I know this device is old now and most people have moved on, and I am pleased that there are some people who stick around here to keep this device alive. I only wish that someone would have advised me to check the boot options selection when I indicated I could not boot into recovery... That would have saved me 2 days of manic obsessive he11....... This was complete he11...... But I am on the other side of it now, and have reflashed another rom... I am back among the living.
Click to expand...
Click to collapse
Glad you got it fixed! I have had my phone for over a year now and never heard of a boot options tab. I guess you learn something new every day.
Also glad you got it fixed. But let's keep this open in case someone else has the same or similar issue.
KennyG123 said:
Sprint phones have always been able to downgrade and thinking that has not changed. You should be able to Odin the last one listed on the link I gave you...NAE...then your phone should boot...you can then take the Sprint OTA if you like then root and recovery as normal. Then you can get to the stuff on your SD and flash. The only issues I remember popping up these days is if you mismatch the modem and OS...which wouldn't be the case if you Odin'd NAE.
Click to expand...
Click to collapse
Well not being able to leave well enough alone, I locked my phone up again.
Because I was able to get out of soft brick without needing a stock firmware, I never bothered downloading NAE from the link you provided.
Turns out after 2 separate downloads (one using Chrome and one using Firefox) I have determined that the md5.tar files on that site http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs are worthless.... BOTH downloads failed in Odin before I could even get out of the gate....
They failed the md5 check that Odin performs and would not allow me to continue.... IS there something I am missing?
Team Scream said:
Well not being able to leave well enough alone, I locked my phone up again.
Because I was able to get out of soft brick without needing a stock firmware, I never bothered downloading NAE from the link you provided.
Turns out after 2 separate downloads (one using Chrome and one using Firefox) I have determined that the md5.tar files on that site http://www.rwilco12.com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S4%20%28SPH-L720%29/Stock%20ROMs are worthless.... BOTH downloads failed in Odin before I could even get out of the gate....
They failed the md5 check that Odin performs and would not allow me to continue.... IS there something I am missing?
Click to expand...
Click to collapse
Remove the .md5 extension at the end and try again.
KennyG123 said:
Remove the .md5 extension at the end and try again.
Click to expand...
Click to collapse
Sweet baby Jeezes please tell me that is not all I had to do.... I spent 4 hours staring at the screen downloading files last night .... I waited 4 hours and finally could not stay awake any more but I finally got the OA3 firmware from SamMobile downloaded successfully. I left the .md5 extension and it is now flashing via Odin as I type this.... I could have saved myself a few more hours of misery if I had known you can remove the .md5 extension..... This learning curve is hard on an old man like me hahaha!
Thanks Kenny
<edit> Ahhhhh.... the sweet smell of success !!! I am now booted back into a stock phone!!!
Man I hope this thread can help save someone else from the anguish I have put myself through with this thing....
Team Scream said:
Sweet baby Jeezes please tell me that is not all I had to do.... I spent 4 hours staring at the screen downloading files last night .... I waited 4 hours and finally could not stay awake any more but I finally got the OA3 firmware from SamMobile downloaded successfully. I left the .md5 extension and it is now flashing via Odin as I type this.... I could have saved myself a few more hours of misery if I had known you can remove the .md5 extension..... This learning curve is hard on an old man like me hahaha!
Thanks Kenny
<edit> Ahhhhh.... the sweet smell of success !!! I am now booted back into a stock phone!!!
Man I hope this thread can help save someone else from the anguish I have put myself through with this thing....
Click to expand...
Click to collapse
I am sure it will! Glad you got it working and glad I helped! Some versions of Odin don't care about the md5 extension and others barf it up. With the way your luck went....well...don't buy a lottery ticket this week...hahaha.
So I've been reading for a couple of weeks now post after post after post. I registered last night in order to ask a question as I just don't know whether I'm doing the right thing or not.
I have a Samsung S4, AT&T unlocked. I use the T-Mobile network though. I'd like to have Lollipop on the phone and from what I've read (lightly) over the past couple of months, the consensus is generally 'No AT&T SIM card, no update'. I've seen the odd poster who said they were able to get the OTA without an AT&T card.
I used the Samsung Kies a few months back, no luck. I called Samsung and they weren't able to assist but suggested the Best Buy Samsung center. They worked at it for a couple of hours, no luck. They know the only thing that's been done to the phone is that it was unlocked at the AT&T store so I could put my T-Mobile SIM in about a year and a half ago.
So I've been thoroughly reading about Odin, TAR, Apoplectic1's capture of the file, bootloader versions and so much more that I'm now stalled out.
I have three files downloaded to my laptop from this thread: http://forum.xda-developers.com/gal...ng-rooting-t2926642/post56453108#post56453108 Specifically the OC3 Lollipop section at the top.
However in staring at these three files (2400258.zip, ALL_ATT_I337UCUFNB1_505595_REV06_user_low_ship_MULTI_CERT.tar.rar & Odin+3.09.zip) I'm hesitant to proceed.
I don't care to root my phone. I'd just like to have the Lollipop update without having to sign up for an AT&T phone number. Heck, the guy at the Samsung Experience gave me an AT&T SIM just in case that's what I needed for the OTA download (again, no luck smacking that check for update button as many posts I've read said that my IMEI needs to be registered on the AT&T site in order for it to work). I've read in that post above that I can do Lollipop without root, again I'm okay with that.
There are also SO MANY posts that say "Hey! Here's how to do it in this many steps!" I've read the noob guide on XDA, I've tried to figure out how to determine what version my bootloader is (seriously I'm still unsure if I've found the right thing), and before I dive into watching videos (I did bookmark this page: http://forum.xda-developers.com/showthread.php?t=2337590) and You Tube ones, at this point I'm wondering if there's anyone in the Seattle area who does this that I could hire who does this sort of thing.
I've even searched the forums trying to find that but I must be using the wrong key search terms.
Thanks in advance for any advice.
I'm not in your area, but...
I think you can do this yourself if you have someone to advise you specifically what to do each step along the way, and to answer any questions you may have. I'm willing to help with that if you want.
I will not be able to be in the forum much during the day today, but I could help this evening, say after about 1:00 or 2:00 your time, up until about 8:00 your time.
First, use an archiving program such as WinZip, 7Zip, etc. to extract the Odin executable file from the zip archive to a location on your laptop. Make note of the location so you can start the program later. Also, extract the NB1 firmware file from the .rar file and make note of the location. The NB1 firmware file will have a .tar.md5 extension, and that is the file you will be flashing in Odin.
I assume you will be using the "Update to I337_OC3 - 5.0.1 and KeepRoot" by muniz_ri since you are not doing over the air updating. Let me know if you feel comfortable proceeding with help.
Hello,
First, let me preface this by saying that this is not for those who are already technically capable of flashing U firmware from U1 firmware. This will serve as a tutorial for those who are not sure how to go about doing so. This could at least be a means to access U One UI 3.0 firmware, as it will be posted here for for faster download and bypassing decryption process. I've already done that for you.
So I have a N986U(VZW) and wanted to get an early look at Android 11 One UI 3.0. So, I went through the process of flashing U1 firmware, enrolled in Beta Program, and OTA'd up to latest beta (beta 3). Then, I see that carrier locked devices (to date, ATT, TMB, SPR, VZW) have begun receiving the official One UI 3.0 firmware OTA. Now don't get me wrong, I love U1 firmware, no carrier bloat, more features, typically, than what carrier branded have, among so many others. Alas, carrier branded firmware is generally more safe for me.
So, if you are like me, I wanted to have a means to be able to convert back to U firmware, while still remaining on One UI 3.0. Many of us already know how to go about doing so, but some may not, so I figured I'll outline the steps to go from U1 One UI 3.0 to U Carrier Branded One UI 3.0. I've provided links to the firmware and Odin for easy access and I'm always around, in case any of you have questions or have issues with any links.
Now, we have to have the essentials:
1. Odin(3.14.1_3B Patched is what I used)
2. Frija, or at the very least the firmware to convert over to
4. An archive extractor (Winzip, Winrar, 7zip, etc.) I'll explain why we don't want to use Windows Archive Tool in this explanation.
3. Some form of technical aptitude to be able to download and flash firmware using a tool
After you've gathered all of these, we need to ensure that no fingerprints or other forms of security are on the device. The reason we do this is the avoid any FRP (factory reset protection) issues after flashing. The way we do this is by disabling fingerprint unlock from settings. Change your unlock preferences to Swipe No Security. Do not forget to do this, because if you do, you will need to have an internet connection to the device during initial setup to authenticate your google account.
1.Once you've done this, you want to power down your device. For those who have enabled side button power menu, this is pretty self explanatory. Those who haven't, swiping down from your notification tray will reveal your power button. You know what to do from there.
2.Next, you want to press and hold Vol+, Vol-, and plug a USB-C cable into your device and subsequently into an available USB-A port on your PC. Allow Windows a moment to setup your device if your haven't plugged your device into your PC while in Download Mode before. You should see your device boot into Download Mode, and you will be presented with a Vol+ and Vol- and Power option. You will need to press Vol+ to continue into Download Mode.
3.Then, you will need to open Odin. When you do so, you should see a blue bar indicating that your device is recognized (represented by COM). If you don't see this within Odin, try re-inserting your USB cable into your PC, either into another USB port or changing your USB cable for another.
4.Once you are successfully able to see the blue COM indicator in Odin, you are to choose the applicable partitions (BL, AP, CP, and CSC). These will be archived in the firmware downloaded by Frija or link I provided. Each partition is labeled by it appropriate partition. Clicking each label in Odin will direct you to Windows Explorer, where you can browse for the directory where the downloaded files are locally stored.
THIS IS IMPORTANT!!! IF YOU DO NOT HAVE A ATT, TMB, OR SPR, DO NOT CHOOSE A USERDATA PARTITION. THIS IS POINTLESS TO FLASH, AND IT WILL SERVE NO BENEFIT IN THE USE OF THE DEVICE AFTER SETUP.
5.In Odin, you will see three tabs under the COM blue bar, named Log, Options, and PIT. I want to direct your attention to the tab labeled PIT. You will need to apply a PIT file in this tab. This file is located in the CSC partition. I have uploaded this file as well. But, if you want to learn how to extract it from the CSC partition, use the aforementioned Archive Extractors to open the CSC partition, and it should be the second in the list of files. Right click this file and select Extract to... From there, you are able to choose the folder you would like to extract to.
The reason you want to use the extractors I mentioned rather than Windows embedded extractor is due to Windows not being able to handle .md5 or .tar files. You will get an error if you attempt to open these types of files with Windows Extractor.
6. Once you've chosen all the partitions in Odin, you will click Start. It may take some time to complete the flashing process, so be patient. Once it completes, you will see Success in the field above COM, and the COM field will change from blue to green. If it doesn't change to green, and instead changes to red, be sure to let it be known to the thread, so that I can assist in the best way I can.
7. At this time, your device may reboot to recovery. This is fine, it just means that you will need to factory reset. Use Vol- to select Factory Reset. Select the option using the Power button. Upon successfully doing so, your device will reset to the setup screen.
8.Your device will be an Out-of-Box state upon reboot. Setup the device as normal.
9.All done! You are now on U firmware One UI 3.0! Congratulations!
I understand that this is a very lengthy explanation and that some, if not all, of this will be redundant to some users. That is okay. Not all of the users on XDA are educated on how to flash firmware on Samsung devices. I hope that after following this guide, that may soon change.
Below are all the files needed in order to flash what is needed in this guide. If you have any issues with downloading them, let me know. I'll be happy to re-upload them on another file sharing client for you.
Update: I've also uploaded the CTL4 firmware for U1 for those who want the updated unlocked firmware, in case you want to switch back to U1.
Odin:
Odin 3.14.1_3B
Frija:
Frija 1.4.3
N986U One UI 3.0:
N986USQU1CTL2
N986U1 One UI 3.0:
N986U1UEU1CTL4
PIT File for Repartitioning:
PIT C2Q_USA_SINGLE.pit
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
NippleSauce said:
Just wanted to say "thank you" for posting this! I knew what to do already, however, I just didn't have any links for the zipped update that I needed!
I first had gotten a phone notification (Friday morning) that I could tap on to download the update OTA, however, I was at work so I had dismissed that notification... Unfortunately, after doing so, I was unable to get the update as no available updates even showed up in the settings... So I figured that I'd just need to manually push it through since OTA updates have consistently been skipping my device... Regardless, we're working now! So thanks again for the download links and I hope that you enjoy the holidays!
Click to expand...
Click to collapse
Thanks so much. Just wanted to provide a means for new users a detailed explanation on how to change firmware, preventing the needs for QAs on bricked devices. Even though it's bound to happen eventually.
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
j3ffm1ll said:
Just to verify, I have the verizon snapdragon variant and frija does not find the firmware, is the firmware you linked for the verizon snapdragon variant?
Click to expand...
Click to collapse
This version is for anyone who has N986U or N986U1 devices. Bear in mind that this firmware is CTL2, whereas Verizon locked firmware is CTL4. Can confirm that I have a Verizon N20Ultra and am on CTL2 and all features are working except RCS, but even users on CTL4 are having this same error.
Update: I've linked the CTL4 U1 firmware for faster access. When and if I come across U CTL4 VZW firmware, I'll be sure to upload to the file repository. Thanks! Merry Christmas and Happy Holidays!
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
sclarktay4 said:
I am curious as to why you say it is safe for you. I am currently on Sprint/Tmobile. I converted to U1 to get update because I am impatient. What would be the benefits of doing this for me? This is a honest question even though as I reread this, it sounds a-holish. My apologies if it sounds like i am being a jerk. I am not. I do want to know.
Click to expand...
Click to collapse
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
denson9874 said:
Sure thing. When I say safer, I mean that in an RMA lens. Based on your DID, Samsung knows what your devices CSC, model, and whether your device is U branded or U1 unlocked. There is a chance that your device can be deemed "tampered" with in the case where you send it for repairs and alterations have been made, like firmware. So, only spoken from that perspective. I've would've included this use case scenario, but as you and others can see, this post was extremely wordy to begin with
Click to expand...
Click to collapse
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
warriorvibhu said:
@sclarktay4 This is not true and incorrect info. I have personally Verified multiple times on multiple Samsung devices. I also have some insider info how they verify tampered devices but won't get into that. Even unlocked bootloader went through fine with RMA except once but flashing u1 on u will not cause RMA issues.
As far as this thread is concerned, this information is already posted so you wasted time in writing this wordy thread. Just saying cause no point wasting time in duplicating work and causing confusion to many here who aren't advanced users.
Click to expand...
Click to collapse
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
denson9874 said:
My dear friend, we meet again. I must disagree because I, being a former support technician for a vendor who handled RMA for carriers (Asurion), have seen devices regretted due non-carrier firmware being loaded on them. As a senior user on this forum, it is important to address all possibilities so that users are informed. As I stated in the beginning of my post, this is to serve as a means to educate users on the process, not for those who already know the process, like yourself. I, for one, respect all comments given, but those who come on to the forum to play repeat police, I can't waste time on that. Educating new users, I'll continue to waste my time on. Good holiday, sir.
Click to expand...
Click to collapse
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
warriorvibhu said:
Well then your process was unique at Asurion, even Samsung stores here in NYC dont know about that unique process of yours. All they care about is if there is rooting or water ingress/ physical damage. Your means to educate others is by posting duplicate threads? Please dont be suggestive by saying you respect all comments as if others dont. Repeat police?? LOL ..Stop repeating same things then.. go read and educate yourself bro, if someone is playing repeat police by urging you to not post something twice to avoid confusion that too in the same device forum, same subsection where it was already posted. You want to feel important find other ways (being senior member is not an achievement you are trying to show off here buddy) may be make efforts to help people by posting in cross device forums.
And if we meet again that means you are lucky. Happy Holidays to you too.
Click to expand...
Click to collapse
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
denson9874 said:
I prefer to stay in lane and educate on what I know rather than come half-stepped. It is clear we won't see eye to eye, which after our two encounters to this point, I'm glad for that. As long as forums will exists, there will always be users like you and I, quarreling over someone else's IP who make money on the both of us. All of this is beneath us. I wish you well, I truly mean that.
Click to expand...
Click to collapse
Very well said. Cheers to that. This is amazing and we both agree on. Moving on wishing you well too stay safe and have an amazing holiday season.
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
ethos7788 said:
Just wanted to say thank you for the easy to follow and use instructions and files. Took only 3 minutes to complete once all was downloaded and extracted as instructed. Cheers and thanks for taking the time to help those of us out who enjoy dabbling but don't really have the know-how to do these things without a great community of people! Thank you good sir and have a great holiday.
Click to expand...
Click to collapse
Glad to see that you were able to find the instructions useful and informative. I hope that you have a happy holidays as well!!!
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Geekser said:
I am curious about something and hope you can give me an explanation. This is regarding your instructions for flashing the PIT file.
I have been flashing Samsung devices for many years and in all the time I have flashed firmware, I have never extracted and then added the PIT file in Odin. Can you tell me the reasons it is necessary to do that based on the steps you outline? What does flashing the PIT file do that would not be done if you don't flash it that way?
I am not saying it is wrong to flash the PIT file, only that I would like to know the reasons it is necessary. If you can explain that I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
denson9874 said:
Sure, I don't mind providing an explanation. So, essentially, PIT files provide the table or map and allocation size for each partition that Odin require to have a more successful flash process. Think of it as the roadmap for the firmware. This file is included in the CSC file, so extracting is not completely necessary, as it will be accessed during the flashing process. The reason I suggest applying the PIT file along with assigning CSC is for redundancy. Also, for these reasons:
1. To avoid a "Get PIT for mapping" error when flashing.
2. Prevent "Invalid EXT4 image" issues
3. Re-partitioning/NAND Erasing
4. Avoid possible boot loops
5. Proper internal storage allocation (Ensure if you have a 512GB device, you don't end up with 128GB visible.)**
** This is only an issue if you elect to download a PIT file from the web, rather than extracting it from the firmware.
Click to expand...
Click to collapse
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Geekser said:
Thank you for an easy to understand and complete explanation. Your response is one of the reasons I love XDA - getting these kinds of answers help me and anyone else reading (who doesn't already know) to get a much better understanding of our phones and the way things work.
Thank you very much!
Click to expand...
Click to collapse
Well thank you so much. As long as I'm helping someone here, then this thread is serving its purpose. I care a lot about the why as much as I care about the what. This is the reason why I make lengthy post. Maybe a far amount of users don't really care about the details, I think it's important the understand the methodology. I hope that more and more people begin to share that same ethos.