Related
Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
DDJ75 said:
Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
Click to expand...
Click to collapse
Also I'm wondering, deleting those .img files from the .tar will delete also some additional rom languages? As I said I want to try an Asian rom (like Malaysia) in the hope that I can find Chinese language on it... that's the only thing I need otherwise the italian firmware would be fine.
DDJ75 said:
Ok so I bought this Samsung S6 Edge here in Italy for my wife (the phone model is SM-G925F, carrier free). Yesterday I downloaded and flashed with Odin the last firmware available for my country (5.1.1) but unfortunately this firmware doesn't have the Traditional Chinese language in it (my wife is from Taiwan). So I tried to downloaded a firmware of another country hoping that I could get more languages (I downloaded the Malaysian firmware 5.1.1, *maybe* that could have more asian languages in it). Anyways, I tried to flash this firmware with Odin but near the end it failed on the "hidden.img" file (luckily, flashing again the italian firmware recovered the phone, no brick). Searching on this Forum I read some people suggesting to delete the "cache.img" and "hidden.img" files from the firmware archive and this should solve the "hidden.img" error on Odin. But before doing this I need some clarification:
- Why do we need to delete those files from the (official) firmware archive? What are they for and why they are there if we can delete them safely? Should I delete both files or just the "hidden.img" file (I ask this because some people said to delete both files, other people said to delete only the "hidden.img" file, I want to be sure of what I'm doing before having another near brick experience...).
- In case I need to delete those files, is it better to use Total Commander (like someone said) or the Unified Android Toolkit? Will this "custom" .tar firmware trip KNOX on my phone (I read some people had this problem)?
Thanks!
Click to expand...
Click to collapse
Hi, i´m not an expert in dev or codes, but recently I soft bricked my phone, and I did a lot of research here, and tried almost everything to solve my problem.
In my case, my S6 was stuck on android 5.0.2 with bootloader in 5.1.1 and the stock firmware 5.1.1 for my specific device wasn´t released yet. So I couldn't turn on or get the emergency recovery from Smart Switch.
When I flash the firmware from other variants, the process always fails. So I´ve tried everything to flash a 5.1.1 firmware.
First I removed the hidden, then I try to remove the cache... with more research, One guy said to remove the sboot.bin e cm.bin. I try this and fails too...
Than I remove all the files, (hidden, cache, sboot e cm.bin) and works!
Even if fails in Odin, this doesn´t mean that the file is the problem... Maybe the cable is in bad conditions, or the PC itself... Try more than 2 times to flash the same .tar before discard that solution.
- Why do we need those files? Good question, don´t know either.
You can try to delete 1 and flash, try both and flash. A lot of variables are in this situation.
- I advise you to use Total Commander, very easy and fast.
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
rafaelrgm said:
And man, why don´t you simply try to download the language package? For sure you have this option somewhere, or someone knows how to.
Click to expand...
Click to collapse
Well, on Google Play there's an app called "MoreLocale2" which adds more system languages. Problem is that this app needs root access and I want to avoid that...
simply delete hidden img from framework
How to delete a file from framework pls explain how to acces
Please help! I have the galaxy s6 sprint variant and I can not get this to work. The stock firmware does not have any hidden.img files it hasy system,cache,boot,cm,modem,sboot, and rocovery.img.tar.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hello Everyone,
I've dug myself into a pretty big hole and am hoping to get some direction to dig myself out of it.
I recently moved to a new apartment, and internet service won't be set up until Tuesday evening. In my infinite wisdom, i decided to "take a crack" at installing a custom ROM on my Verizon Galaxy S4 in order to use the tethering option for free.
I used the instructions at this thread to install Safestrap. So far so good.
I then downloaded CM12.1 from this website. (Please note that this is an external link). This is mistake #1, though I did not know that CM12.1 was not compatible with Safestrap.
When I booted into SafeStrap recovery, I was also unaware that the default ROM slot is the stock slot, and I installed CM12.1 in the stock slot. This is mistake #3. What was mistake #2, you ask? Well, I didn't make any backups.
When I tried to boot into the system in the stock ROM slot, I got an error that SafeStrap was disabled. I then installed CM12.1 in a new slot, and I no longer get that error, but after SafeStrap's boot screen, I get an error that says "Secure Fail: Kernel" and "System software not authorized by Verizon Wireless has been found on your system."
So, I can still boot into SafeStrap recovery, I can still boot into Odin mode, and that's about it. I have heimdall installed on my Mac OS X, and I have a Linux computer as well that I can use to fix this problem.
I also wrote down this information before trying to get tethering for free:
ODIN MODE
PRODUCT NAME: SCH-I545
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
eMC BURST MODE enabled
ANDROID VERSION: 4.4.2
BASEBAND VERSION: 1545VRUFNC5
KERNLE VERSION: 3.4.0 [email protected] #1 FRI MAR 29 13
BUILD NUMBER: KOT49H.1545VRUFNC5
SE FOR ANDROID STATUS: ENFORCING
SECURE BOOT STATUS: TYPE SAMSUNG
SECURITY SOFTWARE VERSION MDF V1.0 RELEASE 2
So again, this has been a series of errors on my part. At this point, I'd like to "Unbrick" the phone.
Thank you!
I think the best course of action is to odin NC5 from this forum if you want a chance to have your data back if not just download the nc5 tar (just search for it) and find a guide on how to use odin.
Edit: Nvm forgot you used heimdall find a guide to use heimdall but the same files work.
I'd have to agree with whowatchlist. Hands-down, a bootloader-mode (as in Odin) flash will absolutely be your best bet. If you give no ****s about data, or you happen to keep the important stuff on an ext. SD, then just flash your appropiate stock TAR file (NC5 if I recall the OP) via Odin or Heimdall.
Data recovery may or may not be possible, I really couldn't say without more information. Whowatchlist's link/method should be first and foremost. If that's a no-go just come on back and we'll go from there and get you all sorted.
Or since you are already on a locked bootloader, why not consider upgrading to Lollipop? And if you're still set on safestrap, you can try out stang50liter. Just something to ponder. The phone is by no means 'bricked', at least not in the traditional sense, just comes down to where you wanna go from here.
The rest of this post is probably going to be largely irrelevent and/or not needed, but seeing as I'm still new to posting on XDA rather than just lurking around, I'm attempting to be extra super duper helpful to build my rep/credibility and show i'm not just another window-licker with my helmet on backwards...so I wouldn't blame you for skipping the rest.
As I'm not all that knowledgable when it comes to Safestrap due to my faith in the BL being unlocked/exploited someday, take this as more of a general reference if you would.
Judging by your terminology and that ever-so-fun phrase "i'm gonna take a crack at it", I'm going to assume that this (android modding) is a relatively new field in which you've wandered? If so allow me to touch on a few key points. If not, disregard etc. etc.
Every bootloader EXCEPT for the original one the device released with, MDK, are all locked. This includes ME7, MI1, MJ7, MK2, NC5, NG6, NK1, OC1, and OF1. In general, if you attempt to flash over it, even with a stock kernel that's been tampered, tweaked or altered in any way, your phone/ODIN will give you the finger. But kernels boot the system (e.g. the "ROM"). TouchWiz (courtesy of Samsung) roms are very different from AOSP-based roms. Of course Cyanogenmod is AOSP-based. Because a Kernel that will boot CM cannot be flashed, trying to flash and boot a CM rom will only end in gnashed teeth, swearing and possibly holes in walls.
Safestrap is a middle man. Because it lies on the /system partition, it avoids poking the Kernel-bear, but it boots before the 'ROM', allowing you to select whatever ROM you want to boot.
So if you ended up replacing your stock rom slot with CM12, I can only imagine you essentially ended up attempting to flash your actual partitions instead of a safestrap container, and following that, the locked BL NOPE'd at the Kernel in the zip, and made you quite the unhappy camper. That's my current theory anyway.
If so, there are options. There's always options!
Anyway if you need help or clarification on anything, or have any other questions just hollar back! Thread or PM works (so I don't clutter the forums with walls-of-text like this.) Hell, I'm in a good mood today, I'd even do a Skype step-by-step walkthrough or something lol.
@whowatchlist / @Atomicmuffin, thank you both for the helping hand.
First, I'm glad to hear that the phone is not bricked in the traditional sense.
Secondly, I don't care about the data. I would just like the phone back to a working state and, if possible, I'd still like to flash something on it.
Thirdly, @Atomicmuffin, that "wall of text" was incredibly helpful.
I'm going to try some of the links that you guys pointed me to, and see what transpires.
My apologies for not getting back on this thread sooner. Unfortunately, there were a lot of changes at the startup I work for this week so it's been a rough ride.
Thank you both - I'll be back with updates.
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Stvnx7 said:
It's alive! Hey everyone. I just wanted to let you know that the phone is back in operation.
And, the thread that you linked me to (http://forum.xda-developers.com/showthread.php?t=2776189) also helped me understand that I need to use Safestrap, and then only with certain ROMs. Thank you both! I'm going to give this another try, now that I know better. Hopefully all goes well, but if not, I know how to press the reset button.
Click to expand...
Click to collapse
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Atomicmuffin said:
Hey that's awesome man, glad to hear it and i'm glad my ramblings helped you out! Haha, sometimes I tend to over-ramble and don't know where the line is between helpful and annoying, but what I do know however, is the feeling of being stuck in a spot like that. Weren't no wall-o-texts in my early days. Would have saved me a lot of stress (like when I got cocky and accidentally flashed the wrong firmware, leaving me hard bricked.) All I ask is to just pay it forward!
And Read! Read! Read! Thankfully most people who release stuff on XDA care enough to post massive textwalls that dwarf mine with instructions to keep you on track. So even if you've read enough to recite whatever it is in your sleep....keep reading til you can do it backwards. In a foreign language. And in sign language. Simultaneously. Then you should be good to go!
As a general rule of thumb, I'd suggest sticking with reputable websites like XDA and AndroidFileHost at least until you get familiar, to help avoid blunders like this. There's a lot of misinformation out there in the world beyond, and even more window-lickers who do a one-click root and think they're hot stuff enough to take take their helmet off and start teaching other window-lickers, haha. But I digress...
Safe travels man! And If you got questions just let us know! Oh I almost forgot, so what'd you decide? Gonna stay NC5 and SafeStrap it again?
Edit: A GREAT starting resource is http://xda-university.com
Click to expand...
Click to collapse
Thanks for that awesome resource @Atomicmuffin. I haven't decided what route to take now that I've got the phone working. My baseband now reads NG6, so and all I really want is the ability to use the phone's hot-spot feature. I'll look into that a bit more.
xxxxxx
link5505 said:
I've been trying to put the stock nc5 file on my s4 with odin but it keeps failing, what gives?
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __XmitData_Write
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What does the phone display when this happens?
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
android2819 said:
Hello. Having read a bunch of threads for this matter, i haven't yet encountered a solution for my particular problem. It may be impossible altogether.. but i thought i'd hopefully ask anyway.
My device is the Samsung Galaxy S6 Edge(SM-G925F, international variant, not carrier branded). I have MM 6.0.1 running on it, with the latest security patch and bootloader that is available in my country, that is:
S6 edge SM-G925F ROM Romania - G925FXXS5DQC1 - downloaded and flashed via ODIN 3.12.3 from sammobile
However, recently i wanted to downgrade to LP 5.0.2(or 5.1.1 - and from there my target is 5.0.2), as i like the look and feel of it more. But, as i have said, upon researching around the forum and on the whole internet i haven't found a positive solution, and i decided to make an account on here and hopefully get lucky.
I've tried multiple ODIN versions, multiple 5.0.2 and 5.1.1. ROMs found on the internet for different countries, but the end result is always the same: download mode says SW REV DEVICE 5 BINARY 1(or 2,3,4)
As for ODIN:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It doesn't matter to me if i have to root, flash custom roms and custom recoveries all over, i just want to know if there is a way to get my phone on the old bootloader and flash stock 5.0.2 rom.
Any info/advice is appreciated. Thank you all!
Click to expand...
Click to collapse
The only answer for your query is unfortunately no. You can not downgrade from mm to lp. It is impossible. Sorry its not the news you wanted.
I suppose the only way it could be done is to buy a new motherboard that is on lp firmware and replace the full board.
Other than that there is no way.
Understood. Thanks for the info!
For simplicity sake, NO discussion of the leaked "D" builds. This thread is ONLY for the official beta z builds.
Before posting questions, please read this whole thread, including the OP.
This thread is for the US models, ONLY. For discussion about the International N950F Pie Beta, please go to @henklbr thread: https://forum.xda-developers.com/galaxy-note-8/how-to/galaxy-note-8-sm-n950f-official-oneui-t3890126
UPDATE February 19th, 2019: Samsung released beta 2, N950U1UEU5ZSBB
Huge thanks to @Nickitt and @jester450 who were so kind to provide the ZSBB update zip!
Just download and flash over ZSAB from SD Card:
https://www.androidfilehost.com/?fid=1395089523397901568 md5:1cadf77f8d7a565c64f3b28940f9fc85
UPDATE: March 12th, 2019 - Samsung released US Beta #3 N950U1UEU5ZSC2
If you haven't received it yet, be sure to do a manual check for updates in settings. If you can't get the OTA, you can download it from the following link and sideload it in Recovery:
https://firmware.science/download?url=00000/0000/SS-N950U1UEU5ZSBB-to-EU5ZSC2-UP
WARNING: If you use ATT, then sideloading an OTA will force a factory reset. It's an ATT thing. This is only if you sideload it.
On January 24th, 2019, Samsung silently released the One UI public beta for the US Unlocked Note 8 (N950U1). This followed weeks of speculation after beta builds were seen on the Samsung FOTA testing site, and following the release of the official beta for the international N950F. The US beta build is currently N950U1UEU5ZSAB. To register for the beta, make sure you have the most recent version of the Samsung+ app installed. You will need the beta version of Samsung+. You can either sign up for the beta version in the Google PlayStore and wait for it to update, or you can download it directly from apkmirror at this link: https://www.apkmirror.com/apk/samsu...elease/samsung-11-6-0-0-android-apk-download/
This beta is only open to the Unlocked N950U1. Carrier branded models are not currently eligible, but there is a work around. The beta only requires that you be running the N950U1 firmware. It does not check to see if your device was originally a carrier branded model. You must be running N950U1UEU5CRL2 for the N950U1. No other firmware version will work.
NOTE: If you flash the N950U1 firmware, you will lose carrier features such as Video calling from the stock dialer, RCS (enhanced) text messaging, WiFi calling, and VoLTE. The exception is with T-Mobile, you'll still maintain WiFi calling and VoLTE. Visual voicemail for your carrier will have to be downloaded from the PlayStore, if possible.
To register for and install the official Z Beta on your Factory Unlocked N950U1:
This guide is assuming you are already on the most recent build CRL2 for the N950U1, and you have ADB, Fastboot, and Samsung drivers set up and working on your PC.
Step 1.
Open the Samsung+ app, and there should be a banner in the center of the screen for the One UI experience. If it doesn't appear, clear the cache for the app, force stop it, and restart your phone.
Step 2.
If the banner appears, click on it, accept on the next page that opens. It will go back to the Samsung+ home screen and the banner will be gone. But you'll see a brief toast message thanking you for signing up.
Step 3.
Then go into settings and perform a manual check for software updates. If it doesn't appear, reboot into recovery, clear cache, and restart the phone. Check for the update again and it should appear.
Step 4.
Let the update download and install. This will not wipe your device, since it's an official OTA; however I personally recommend a FDR when moving up to a new version of Android. YMMV
Step 5.
DONE.
Step 6.
As of February 19th, 2019, Samsung pushed beta 2. Manually check for a software update to N950U1UEU5ZSBB. If it doesn't appear, you can download it here: https://www.androidfilehost.com/?fid=1395089523397901568 md5:1cadf77f8d7a565c64f3b28940f9fc85. Sideload it over N950U1UEU5ZSAB in Recovery. It is an OTA so it will not wipe your data.
WARNING: If you use ATT, then sideloading an OTA will force a factory reset. It's an ATT thing.
Before you ask. Yes you can flash N950U1 firmware on your (whatever US carrier) device. You can also flash it on the Canadian N950W!! They are all the same device hardware wise. No it will NOT trip Knox. No, you can NOT flash this on a N9500. No, you can NOT flash this on a N950F (You already have your own beta, why are you in this thread? )
To flash the N950U1 firmware on your N950U or N950W and register for the official beta:
This guide is assuming you already have ADB, Fastboot, and Samsung drivers set up and working on your PC.
Step 1.
This will wipe your device, so perform a back up.
Step 2.
Download the latest N950U1 firmware, version CRL2 using this link:
https://www.androidfilehost.com/?fid=1395089523397886161 MD5: dc5acb4ab31c6fc22e595a47e6e0b3c5
Step 3.
Extract the zip file you just downloaded into a folder where you can find it easily.
Step 4.
Download patched ODIN v. 3.13.1_3B https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Step 5.
Open Patched ODIN and fill in the slots with the corresponding files you just downloaded from SamFirm. Use CSC_OYN, not HOME_CSC. ODIN will lock up when you load up the AP file. Just wait it out. Trust me.
Step 6.
Put your Note 8 in Download mode and attach to your PC.
Step 7.
If ODIN say "ADDED!" in the log window, it recognized your phone. Hit START and go have a cup of coffee, or a beer. This will take a while.
THIS WILL WIPE YOUR PHONE. You did a backup, right?
Step 8.
Once ODIN completes and says "PASS," let the phone boot up and go through the setup wizard.
Step 9.
Follow the steps above to get registered for the official beta.
Step 10.
DONE
If for some reason you can't get registered for the beta, don't fret! There's a work around for that too!!
Step 1.
Follow the steps above to make sure you're on N950U1 build CRL2.
Step 2.
Then go to https://firmware.science and download the ZSAB update zip. Just choose Note 8 N950U1 as your model, and CRL2 as your current build.
Step 3.
Once it's downloaded, either flash it in recovery from SD Card, or sideload it via ADB.
Step 4.
DONE
Step 5.
As of February 19th, 2019, Samsung pushed beta 2. Manually check for a software update to N950U1UEU5ZSBB. If it doesn't appear, you can download it here: https://www.androidfilehost.com/?fid=1395089523397901568 md5:1cadf77f8d7a565c64f3b28940f9fc85. Sideload it over N950U1UEU5ZSAB in Recovery. It is an OTA so it will not wipe your data.
WARNING: If you use ATT, then sideloading an OTA will force a factory reset. It's an ATT thing.
Before you ask, no you cannot just flash it from CRK1 or any build other than CRL2. And no it won't work if you're on carrier branded firmware. It has to be done from CRL2 for the N950U1.
NOTE: If you decide to downgrade back to Oreo, you will need to do a factory reset first. Otherwise you'll get a bootloop after flashing Oreo.
Thank you to @Nickitt and @jester450 for the ZSBB update zip!
A special thanks to @henklbr for the idea for this thread. His discussions for the international Note 9 and Note 8 betas are a source of great information, and I hope this thread will be the same for the US Note 8!
Also thank you to @Mike15678 and @BlueFox721 for their detailed carrier switching threads. I"ve been following their threads since the S8+, and have used that foundation of information on my Note 8 and Note 9. Without them, I would not know how to switch to the U1 firmware on my carrier device and would not be able to teach others how to do it and get on this official beta.
For simplicity sake, NO discussion of the leaked "D" builds. This thread is ONLY for the official beta z builds
Here is a guide I made that helps you figure out which version of Android you're running or downloading
You can tell what version of Android it is just by the build number. You can also tell if each update just contains the updated security patch, or if new features were added or updated.
The first part of the build number never changes. It will start with your model number (N950U or N950U1) followed by a region code for your model number (UE for US unlocked or SQ for US carrier models). After that, there is a 5 character build number that changes with each version.
The first character (S or U) tells you if it's a security patch or a feature update. S = Security Patch and U = Feature Update (features added or changed)
The second character (a number) tells you bootloader version. This is important to know when upgrading and downgrading OS versions. You can NOT downgrade the bootloader. 1 = Bootloader V1, 2 = Bootloader v2, etc...
The third character tells you the Android version. This is different for each Galaxy device. A is the Android version that device was released with. (For the Note 8 A=Nougat; B=Nougat with updated bootloader/carrier switching; C=Oreo, D=Pie) Z is for official Samsung BETA program builds.
The fourth character is the year of the build (R=2018, S=2019). This is the same across all Galaxy devices.
The fifth character is the month of the build. This does not indicate what security patch it contains, only what month it was built. (A=January, B=February). Again, same across all Galaxy Devices.
The sixth character is just the sequence of builds that month (1-9, then A-Z)
So, official Oreo build S5CRG9 is:
S - Security Patch
5 - Bootloader V5
C - Oreo
R - 2018
G - July build
9 - 9th build in July
and leaked Pie build U5DRL7 is:
U - Feature update
5 - Bootloader V5
D - Pie
R - 2018
L - December build
7 - 7th build in December
and official Pie beta build U5ZSAB is:
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
So let's break down my current build number, N950U1UEU1ZSAB
N950U1 - Build is for the Factory unlocked U1 model
UE - Region code US Unlocked
U - Feature update
5 - Bootloader v5
Z - Official Samsung BETA program build
S - 2019
A - January build
B - 11th build in January
Always make sure you know what bootloader version comes with each build before you flash it. This is especially important with the leaked builds. If you flash a leaked Pie build, and it is already updated to bootloader V6, you will be stuck there, which will really suck if its a buggy build.
As of right now, if you update to either the leaked Pie builds, or the official beta build, you can easily downgrade back to Oreo using patched ODIN. Just repeat the steps in the OP. But once Samsung updates the bootloader to V6, most likely after the official release of Pie, you won't be able to downgrade.
NOTE: If you decide to downgrade back to Oreo, you will need to do a factory reset first. Otherwise you'll get a bootloop after flashing Oreo.
I will try to keep this post updated with the current bugs, and fixes for those bugs as Samsung releases new builds.
The OP may change and evolve as I try to update and streamline it. Always check there for the most recent information first. Just also understand I'm not on here 24/7, so it may take some time for me to update it. Full time job, 5 kids, and a couple hours in the gym each day, my day is fairly full, LOL.
Bug Fix #1:
Even though I said no discussion of the current LEAKED D builds, I will point out one thing. Netflix and some other video services did not work on DRL6 or 7 (just showed a black screen). Netflix DOES now work properly on the official Pie beta.
Bug Fix #2
Not so much a but, but an annoyance. AdHell 3.1.1.254 now works perfectly. Not sure if it's because AdHell was updated, or something was fixed between the leaked D builds and the Official beta. But it now works!
Bug Fix #3
In the previous leaked Pie builds, AR Emojis didn't work in the stock camera. They are now working as intended.
BUG #4:
Gear wearables, such as the Gear S3 and Galaxy watch won't connect. It says to check for an update. Solution - go to apkmirror.com and download the gear s plug-in.
BUG #5:
When using either DeX or screen mirroring mode, Nerflix shows a black screen, but audio works. Netflix video works just fine on the phone, but doesn't show on the TV screen. Tried with both a DeX Pad and a DeX cable.
Hello,
Asking as a better safe than sorry...using SamFirm to download the CRL2 firmware, I have a N950U purchased from Samsung on T-Mobile. In the Model field I have entered SM-N950U1, for the region would I use XAA or should I use TMB since my SIM is a T-Mobile Sim?
Thank you for this write up!
baz2a said:
Hello,
Asking as a better safe than sorry...using SamFirm to download the CRL2 firmware, I have a N950U purchased from Samsung on T-Mobile. In the Model field I have entered SM-N950U1, for the region would I use XAA or should I use TMB since my SIM is a T-Mobile Sim?
Thank you for this write up!
Click to expand...
Click to collapse
Use XAA. Do it exactly as I have in my picture. I am also using T-Mobile, just FYI.
Mr. Orange 645 said:
Use XAA. Do it exactly as I have in my picture. I am also using T-Mobile, just FYI.
Click to expand...
Click to collapse
Thank you for the reply and clarification! My apologies, completely blanked and skipped over screenshots since your write up read so clearly.
baz2a said:
Hello,
Asking as a better safe than sorry...using SamFirm to download the CRL2 firmware, I have a N950U purchased from Samsung on T-Mobile. In the Model field I have entered SM-N950U1, for the region would I use XAA or should I use TMB since my SIM is a T-Mobile Sim?
Thank you for this write up!
Click to expand...
Click to collapse
I clarified this in my guide. Thank you!!
You mentioned most models, What about N950W? can I flash the CRL2 than update with SS-N950U1UEU5CRL2-to-EU5ZSAB-UP on a Canadian model (SM-N950W).. Thank you
saroot said:
You mentioned most models, What about N950W? can I flash the CRL2 than update with SS-N950U1UEU5CRL2-to-EU5ZSAB-UP on a Canadian model (SM-N950W).. Thank you
Click to expand...
Click to collapse
I can confirm, I'm using a SM-N950W (Videotron) and it works, the only "pucker moment" was when I updated to Pie from the SD card, it wouldn't automatically do it in recovery, so I had to wait for the menu then manually flash it from the SD card. The only hiccup so far is I have a persistent "Sprint OMADM" notification that ti's checking the device status. I'll probably flash my carrier CSC so I can get rid of that, and also get wifi calling and VOLTE back; it's what I did on the leaked betas.
EDIT: I flashed my carrier CSC using the patched Odin. after everything settled down. On reboot the install froze at 32% (which happened on the closed betas also) reboot and voila! My carrier services are back. No more OMADM either.
saroot said:
You mentioned most models, What about N950W? can I flash the CRL2 than update with SS-N950U1UEU5CRL2-to-EU5ZSAB-UP on a Canadian model (SM-N950W).. Thank you
Click to expand...
Click to collapse
Yes! This will work for Canadian models as well. Thank you for bringing that up!
Jowhee said:
I can confirm, I'm using a SM-N950W (Videotron) and it works, the only "pucker moment" was when I updated to Pie from the SD card, it wouldn't automatically do it in recovery, so I had to wait for the menu then manually flash it from the SD card. The only hiccup so far is I have a persistent "Sprint OMADM" notification that ti's checking the device status. I'll probably flash my carrier CSC so I can get rid of that, and also get wifi calling and VOLTE back; it's what I did on the leaked betas.
Click to expand...
Click to collapse
That's normal and not a hiccup because if the update was downloaded over the air from the carrier or Samsung it would have flashed on it's own because it would have downloaded it to the /data folder something that we don't have access to without root and if we did we could make it automatically flash on a reboot but because we don't have access we all have to do it manually.
followed your instruction but keep getting stuck at get PIT for mapping
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 6326 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
punkcell said:
followed your instruction but keep getting stuck at get PIT for mapping
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Added!!
<ID:0/010> Odin engine v(ID:3.1301)..
<ID:0/010> File analysis..
<ID:0/010> Total Binary size: 6326 M
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/010> Removed!!
Click to expand...
Click to collapse
Delete the .md5 off the files so you see just .tar and set the PIT file yourself it's inside of the CSC file just extract it first. Edit: Hopefully you downloaded the patched odin too.
thank you very much, that did the trick along with switching to another usb port.
punkcell said:
thank you very much, that did the trick along with switching to another usb port.
Click to expand...
Click to collapse
Welcome.
Glad MrMike helped you out. I've never ran I to that problem.
When you download CRL2 with SamFirm, make sure you have the option check to automatically decrypt the download. It's on the right side of the SamFirm window.
And sometimes USB 3 and/or Windows 10 can cause issues.
UPDATE: MrMike2182 way worked but caused a couple issue where my t-mobile device had sprint settings for some weird reason so the banner wouldn't appear, the CSC had some mismatch, so this morning redid the entire process like in the original post and everything went fine, banner came up and currently installing the beta. So I beleive the USB ports i was using before caused the issue.
thank you both for your help .
Jowhee said:
I can confirm, I'm using a SM-N950W (Videotron) and it works, the only "pucker moment" was when I updated to Pie from the SD card, it wouldn't automatically do it in recovery, so I had to wait for the menu then manually flash it from the SD card. The only hiccup so far is I have a persistent "Sprint OMADM" notification that ti's checking the device status. I'll probably flash my carrier CSC so I can get rid of that, and also get wifi calling and VOLTE back; it's what I did on the leaked betas.
EDIT: I flashed my carrier CSC using the patched Odin. after everything settled down. On reboot the install froze at 32% (which happened on the closed betas also) reboot and voila! My carrier services are back. No more OMADM either.
Click to expand...
Click to collapse
Thanks, same thing exactly happened to me. got that "Sprint OMADM" , flashed XAC csc, faild at 32%, restarted and all good Thanks again
This is some great work! I am thinking about doing this for my Tmo Note 8.. But question.. Does snapchat video work? Also, are there any phantom vibrations? Or "application error" vibrations more specifically. Thank you!! ((I'm on DRL6)
My phone is the N950W and I flashed the N950U firmware. I downloaded the Samsung plus app and clicke don the register banner but it just kept going back to the main screen and nothing happened. I reinstalled the app several times, rebooted several times and waited several hours but nothing happened. I am now planning to flash the firmware.science zip to update. If I flash this, will I get further OTA updates or will I have to flash them manually? How would I transition to the official pie once it releases?
Extremely sorry to post this thread again - actually I referred all the threads in XDA Developers Forums but though a few of them matched my requirement but it was closed since 2013 - hence reopening again...
I have a Samsung GT-P1000 - Made in Korea (I don't live there - live in India though) - FCC ID: A3LGTP1000 - S/N: R2DB129469E
I will provide complete details to make it coherent to you...
CURRENT STATUS -- Soft Bricked (Symbol: A mobile - A yellow triangle with exclamation - A desktop) - (The only thing I see in the tab now!!!)
BEFORE -- Android 2.3.3 Gingerbread, no mods (no root, no custom boot-loader, etc...) -- Complete Original Tablet
What I tried to do --
Install Android 6.0.1 Marshmallow (Following this guide: https://www.droidthunder.com/galaxy-tab-gt-p1000-android-marshmallow-rom/) but soon failed in the rooting step itself, precisely, while installing cwm13...
Now, what I want to do --
After some research, which I must have done earlier, not sure, but maybe people are trying to say that installing Android 6.0.1 Marshmallow is not possible... I did not go deeper...
Anyway, I thought we will revert back to what it was... to Android 2.3.3 Gingerbread...
The problem I face doing this --
To install Android 2.3.3 Gingerbread back I used,
-- Odin3_v1.83
-- And the PIT, PDA, and Phone files are here (https://drive.google.com/drive/folders/1CLrfcUdk-oZ1N6ZZ90LbDCdMW5KYkHnV?usp=sharing) - (I got these while referring to a YouTube video:
)
-- And also installed the USB drivers (updated)
And then, following the above YouTube video, I came up with this, (After connecting the device with the PC - after around 15 mins the brick screen appears - It shows a yellow color port in odin - and I start), And stops after this log,
Code:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
Then I switched the ports aswell, and the only difference from the above error is the id changes from 7 to 6...
Also, tried with Odin_v3.07, Odin_v3.13.1, Odin_v3.09, Odin_v3.12.3, but the same logs...
And then, started researching this error but no answer was up to my requirement (there are same threads in this forum but the answers for them did not work for me)
Any help would be highly appreciated,
Thank You
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
It_ler said:
My father once had this tablet. But he never flashed a custom rom to it.
Maybe the partitions were changed for flashing the custom rom. To install a stock rom again, you have to flash the original pit file in order to get partitions into the state for fitting the stock firmware. In Odin, there are separate partition options that you have to set.
Have a look here about repartition using Odin:
Thread 'Re-Partition in Odin, what is it for?' https://forum.xda-developers.com/t/re-partition-in-odin-what-is-it-for.860432/
Click to expand...
Click to collapse
Thank You for replying @It_ler , this was my 1st question in this forum and waiting since a month or more, I am glad you put your precious time in this thread.
I am new to this forum, and I see you are pretty experienced in here, I would really really appreciate if you can help me gather more minds into this. I have memories linked with this tab, and all these days I have been eagerly waiting for a reply.
As you said, to check the re-partition in Odin, I see that it automatically gets checked once I start flashing, but the logs remain the same...