Related
good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..
I have the AT&T Samsung Galaxy S4 i337 with MDL firmware and I needed to flash back to the stock ROM to bring to AT&T to fix an unlocking issue. I googled and found two top guides and a video where they all did the same thing so I thought it was safe to follow it--the guides did not specify that I needed to use a specfic firmware even if it's an AT&T variant (I assumed all AT&T variants had the same firmware and so did the guides apparently) so I think I used the wrong PDA on Odin 1.85 and now I get the issue "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I can no longer boot the device even to my custom ROM.
How do I fix this and then be able to flash back to stock so I can return it to AT&T? Some guides required a PIT file along with the PDA, some required both PIT and bootloader along with the PDA, and some just required PDA. Which ones am I required for my purpose and where do I get them? (I went to several sources after googling and they offered different ones).
Here's my Odin 3.07 output:
<ID:0/007> Firmware update start..
<ID:0/007> sbl2.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
I will be checking back on this thread every chance I can get--this problem needs to be fixed by Monday because I desperately need it for work. Thank you!
I'm going to try to help you out. Bear in mind that I do not currently have this phone, and have very little actual experience with it.
I don't know you experience level. Did you perform a wipe data/factory reset from within recovery before the first time you flashed the stock firmware? If not, can you now enter recovery? If so, perform a wipe data/factory reset and see if the phone will then boot into system. If you can boot into recovery, but the wipe data/factory reset does not resolve the issue, please make note of the details of the recovery. It will tell you which version and we need to know that.
The MDL firmware is the second stock firmware distribution on the SGH-I337 (MDB was first) and was able to be cracked with Loki, by-passing the bootloader to allow installation of custom kernels. All subsequent stock firmware distributions, MF3, MK2, MLD, NB1, NC1, NI1, NJ4, or OC3 are locked, allowing only the stock kernel. So the first important question is what exactly did you flash onto the phone on the first try?
If you flashed the stock MDL firmware, it would be something like I337UCUAMDL, then your boot loader is still by-passable. However, if you flashed any of the subsequent stock distributions, then you will have a locked boot loader. So it's very important to know exactly what was done so far so that the recovery attempt can be done correctly.
I'll need this information, and anything else you can think to tell me, to give you further advice.
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
DarkVamprism said:
Okay so to keep it brief, I am on alliance rom v5.3, running kitkat 4.4.2 on my Samsung S5, recently Lollipop has come out and I would like to update.
this was my first custom romming so needless to say I'm kinda scared, I am pretty sure I can find out how to flash to another custom rom but how would I go about getting to the default so that I can accept normal update? or is there a custom rom that is usually kept updated? (I am a sucker for having the latest version of things)
Also is there anything I should know about going from one custom rom that is rooted to another? or is it exactly like going from stock to custom?
Click to expand...
Click to collapse
just look for stock lollipop rom for your phone ( sammobile)/and flash with odin, just make sure to do a full wipe before flashing the stock rom
Thanks for the quick reply, will this allow me to get future updates? like hotfixes released and stuff? I saw somewhere that once you flash it does something to the kernal which makes updates possibly brick the phone.
Just factory reset the custom, then use ODIN to flash the Stock ROM
Flashing the stock ROM will allow OTA updates so long as you don't root or flash anything else custom like recovery - it needs to stay 100% stock for OTA
But you can still root, and each time an OTA arrives, grab the new ROM from sammobile dot com and use ODIN to flash it, that will update your phone, leaving everything in tact, all your data and images etc will be fine, only thing you'll need to do after updating is root the phone again
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
DarkVamprism said:
Thank you both, I have found my phone model on sammobile but the list of firmwares there is no Australian firmwares(Im Australian) or even any US firmares, the only primarily english firmware that I can see on the list is for the united kingdom? are those what I use or am I missing something? Sorry if I should know this =\
Edit: it shows that I have the G900F under Model number in the settings.
Click to expand...
Click to collapse
Try a UK firmware, the latest version BOE5 is in my sig link on MEGA, much faster than Sammobile
There is also samsung-updates dot com you can check out
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
DarkVamprism said:
Sorry to bug you but im getting errors when trying to use odin, im getting "Secure check fail : aboot" on my phone and the following on odin
Code:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
Looking up the codes I see stuff about having the wrong boot loader and to flash a different boot loader and modem and that its impossible to get with others saying its possible but should never be done, then others saying that I need to turn off reactivation lock.
At this stage I have factory reset it(it automatically booted after so I turned off) and I downloaded your G900FXXU1BOE5_G900FOXA1BOE5_G900FXXU1BOE5 file and put that in the AP section of odin.
Click to expand...
Click to collapse
Are you sure you had the phone in Download Mode?
Volume DOWN & HOME & POWER (Then volume up when asked)
And yes, disable Reactivation lock before flashing anything or you'll end up with major problems requiring a massive mess on to fix
Using ODIN 3.10.6 ?
think you need pitfiles with the rom
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
ad0dh67 said:
think you need pitfiles with the rom
Click to expand...
Click to collapse
Yea I was wondering the same
Try this OP
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Load it into the PIT section along with the ROM in the AP section together and try again
---------- Post added at 19:14 ---------- Previous post was at 19:12 ----------
DarkVamprism said:
Yea it was in download mode and I have never heard of this reactivation thing :S the instructions I read had nothing like that in there, any other settings I should change? luckily it booted fine so ill look into changing that.
Edit: Using Odin 3.09 Also I checked and reactivation was disabled.
Click to expand...
Click to collapse
Here's the latest ODIN
https://mega.co.nz/#!Exo3yADS!y7pFS5-9RVhp4vDxTRAQARAwkjyQAB_9mDZWfXkLqko
There is no pit section inside of Odin 3.10?
Edit: Nevermind I found it but it says not to use it unless im an engineer, how badly will this screw me up =\ Im kind of scared to.
DarkVamprism said:
There is no pit section inside of Odin 3.10?
Click to expand...
Click to collapse
There is on the lower left log / options / PIT section, although clicking that says to load it into the CSC section
Try using the PIT file with your 3.09 version of ODIN first as Im not sure where 3.10.6 wants the PIT file loaded into, it's not very clear
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
DarkVamprism said:
Okay in 3.09 there is a pit up the top where I can put it but but there is also a csc? which one am I supposed to put it in?
Click to expand...
Click to collapse
Put it in the PIT section
I'm just reading up on what 3.10.6 means with that engineer warning
Make sure you load the stock ROM into AP together with the PIT file in the PIT section before flashing
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
DarkVamprism said:
I tried using the rom in the AP and the pit inside the PIT but now its saying secure check fail : pit =\
attempted with odin 3.09
Click to expand...
Click to collapse
Are you running ODIN as Admin? (Right click > Run as Administrator)
Using a native PC running Windows? All Samsung drivers installed?
It almost sounds as if your bootloader is locked, but you managed to flash custom recovery and root right?
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
DarkVamprism said:
Yea I do have custom recovery and a custom rom and had rooted it. although inside the about device section it said I was using G900F I noticed the download mode said G900I so I searched for my old box and on the box it says it is a G900I so I assume the rom I used modified the model number, could this be screwing with anything?
Click to expand...
Click to collapse
Looks like you need to grab the G900I ROM and PIT
I'd try with just the ROM first, hopefully ODIN saved you from bricking when it realised it was for the wrong model phone
Get the G900I ROM, stick it into ODIN like you originally tried, see how you go from there
EDIT - Now it makes sense why there was no Australian ROM for your G900F, there is for the G900I
Okay, good news is sam mobile had the correct firmware now that im using the correct model number(doh) and the phone still boots fine, will update when I have downloaded and tried it, thanks for sticking with me.
Hi. I'm having some trouble when I tried to flash my Note 3 with CM13 but it seems like can't associate with gapps because it will crash. My note 3 is currently on CM13 but without any gapps. I decided to flash it back to original stock rom but ODIN fail.
it says:
<ID:0/003> Added!!
<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> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the download mode, it says:
SECURE CHECK FAIL : aboot
I don't know what to right now. Help me. TQ
Download another copy .
JJEgan said:
Download another copy .
Click to expand...
Click to collapse
Another copy of STOCK ROM?
Yes and odin
Sent from my GT-N8013 using XDA-Developers mobile app
Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.
audit13 said:
Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.
Click to expand...
Click to collapse
Already try another copy of Stock ROM. But it keeps failing. So how to solve the out of dated bootloader?
Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Will try to download the KK ROM since the file is too big. But then where to find the OEM unlock option?
Isn't the oem unlock option available on the nexus 5x and 6p?
Try take out your battery 1st, then use 3 button combination to go to download mode.
Also try another usb cable as well..
I have never seen the oem unlock option on a cm rom. Doesn't the oem unlock relate to the bootloader? The n9005 has never had a locked bootloader.
With a locked bootloader, cwm, twrp, and ROMs not based on a Samsung kernel could never be flashed to the phone.
The inability to cross flash firmware is due to security checks built into the bootloader to ensure that the ROMs being flashed via Odin is made for the particular phone and not because it is locked. Think of it more as a safety feature.
In some of the Samsung phones, older firmware can't be flashed as the bootloader on the phone cannot be downgraded.
Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho
aruruuuu said:
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho
Click to expand...
Click to collapse
Try the Sprint forum .
What is the exact model # of the phone shown in download mode? Was the phone new or used when you got it?
Arobase40 said:
Did you buy your GN3 to Sprint ? lol
Click to expand...
Click to collapse
It is an import version. It is unlocked when I first buy it. And now it relocked after I flash back to Stock ROM
In the S8 firmware Samsung are now providing 5 files.
Here is how to install an S8 firmware
Phone preparation:
1. Download and install Odin on your PC
2. Download firmware below
3. Download and unzip your firmware (do not use WinRAR as it can give errors)
4. From your download put these files into Odin:
BL
AP
CP
CSC (not HOME_CSC)
5. Now look at the Odin Settings (for this select Options)
F.reset time
Auto reboot
6. Installing another country CSC or a network CSC will need the system partition size changing.
For this select Options and add this setting
Re-partition
7 Put phone into Download Mode and connect to PC .
When the Odin ID:COM box changes color press START
Download link: https://drive.google.com/open?id=1-I2ZyNfyN4JCdcRO_ugkrxJ_sh-088z8
I download the official firmware from Samsung directly using this software (samfirm _v0.3.6) and use the most recent ODIN-v3.13.1, newest firmware for my Sprint S8 is G950USQS2BQL1 from January which my phone updated to G950USQS2BRB1 which must not be in a full firmware yet, just an OTA update it seems.
I got 6 files in this downloaded file(SM-G950U_1_20171206185327_w3c9ywqj6i_fac.zip.enc4) which are:
AP_G950USQS2BQL1
BL_G950USQS2BQL1
CP_G950USQS2BQL1
CSC_OYN_G950UOYN2BQL1
HOME_CSC_OYN_G950UOYN2BQL1
USERDATA_SPR_G950USQS2BQL1
What I learned is (HOME_CSC) does not wipe your data, but the (CSC) will just like a factory reset, so with this in mind
If your just upgrading your stock firmware and want to keep your Data,
then just flash these 4 files....
BL (bootloader)
AP (System)
CP (Radio)
HOME_CSC (Region)
To Wipe your phone and bring it back to Stock like brand new out of the box first time powering it up.
Flash all the above but replace (HomeCSC) with (CSC) and add in the (USERDATA_SPR) file too..
ALWAYS ALWAYS ALWAYS backup your stuff first.. I use Smart Switch to backup all my Samsung devices.
Does it lock my phone to sprint
MindTrix said:
I download the official firmware from Samsung directly using this software (samfirm _v0.3.6) and use the most recent ODIN-v3.13.1, newest firmware for my Sprint S8 is G950USQS2BQL1 from January which my phone updated to G950USQS2BRB1 which must not be in a full firmware yet, just an OTA update it seems.
I got 6 files in this downloaded file(SM-G950U_1_20171206185327_w3c9ywqj6i_fac.zip.enc4) which are:
AP_G950USQS2BQL1
BL_G950USQS2BQL1
CP_G950USQS2BQL1
CSC_OYN_G950UOYN2BQL1
HOME_CSC_OYN_G950UOYN2BQL1
USERDATA_SPR_G950USQS2BQL1
What I learned is (HOME_CSC) does not wipe your data, but the (CSC) will just like a factory reset, so with this in mind
If your just upgrading your stock firmware and want to keep your Data,
then just flash these 4 files....
BL (bootloader)
AP (System)
CP (Radio)
HOME_CSC (Region)
To Wipe your phone and bring it back to Stock like brand new out of the box first time powering it up.
Flash all the above but replace (HomeCSC) with (CSC) and add in the (USERDATA_SPR) file too..
ALWAYS ALWAYS ALWAYS backup your stuff first.. I use Smart Switch to backup all my Samsung devices.
Click to expand...
Click to collapse
If I FLASH with CSC USERDATA_SPR does it mean my phone will be locked to the sprint network? because it currently works with all networks. I'm just not clear
hello Guys, i got a G955U that camed with the firmware G955USQS3CRE2 from sprint, I flashed a Combination file (build number G955USQU4CRE1) via ODIN, phone boots well, no problem at this point, but when I try to return to Stock I place the original firmware (build Number G955USQS3CRE2) and all the files correspondig to its slot at ODIN, when I start te flashing proces I get normal message of intilializing, after a few secconds the program says Failed.
Ive tryed diferent firmwares but they dont work, phone remains with the Combination Firmware. Im stuck at combination Firmware.
Im using Odin3_v3.13.1 version. Here is teh Log
HTML:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1301)..
<ID:0/008> File analysis..
<ID:0/008> skip file list for home binary
<ID:0/008> apdp.mbn
<ID:0/008> msadp.mbn
<ID:0/008> persist.img.ext4
<ID:0/008> userdata.img.ext4
<ID:0/008> Home Binary Download
<ID:0/008> Total Binary size: 4744 M
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> abl.elf
<ID:0/008> FAIL! (Auth)
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any suggestion?
A will atatch a image of what is displaying the devices after it fails.
bullracing said:
hello Guys, i got a G955U that camed with the firmware G955USQS3CRE2 from sprint, I flashed a Combination file (build number G955USQU4CRE1) via ODIN, phone boots well, no problem at this point, but when I try to return to Stock I place the original firmware (build Number G955USQS3CRE2) and all the files correspondig to its slot at ODIN, when I start te flashing proces I get normal message of intilializing, after a few secconds the program freezes and the progress bar never camed up.
Ive tryed diferent firmwares but they dont work, Im stuck at combination Firmware.
Im using Odin3_v3.13.1 version. Here is teh Log
HTML:
Added!! Odin engine v(ID:3.1301).. File analysis.. skip file list for home binary apdp.mbn msadp.mbn persist.img.ext4 userdata.img.ext4 Home Binary Download Total Binary size: 4744 M SetupConnection.. Initialzation.. Get PIT for mapping.. Firmware update start.. NAND Write Start!! SingleDownload. abl.elf FAIL! (Auth) Complete(Write) operation failed. All threads completed. (succeed 0 / failed 1)
Any suggestion?
Click to expand...
Click to collapse
The 5th number from the end in firmware/combination files is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Quickvic30 said:
5the number from the end is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks for your reply.
Sorry I dont get it at all, Im trying to understand. Let me see. The combination file I installed its BL4, so the stock firmware must be BL4 or above to allow the Firmware to be flashed on the device?
How can I know the BL#number# of the firmware?
---------- Post added at 10:14 PM ---------- Previous post was at 10:08 PM ----------
Quickvic30 said:
The 5th number from the end in firmware/combination files is the bootloader version aka BL, they must be equivalent and or higher than your current bootloader. So you cannot flash BL 3 firmware are you flashed BL4 combination file, you must resource BL4 firmware or above to and you will be good to go.
Sent from my SM-G955U using XDA-Developers Legacy app
Click to expand...
Click to collapse
Ohh I got it "The 5th number from the end in firmware/combination files"
Thanks! So I will get the right firmware. :highfive:
Ive just downloaded the G955USQU4CRE9 firmware, I deploy it on ODIN to my device, but im getting the same error. I see that this firmwares that have de BLL4 are not from Sprint, there is a alternative to dowgrade my device BLL#number# to go back to Stock Sprint? like install from TWRP the firmware, that will be secure?
bullracing said:
Ive just downloaded the G955USQU4CRE9 firmware, I deploy it on ODIN to my device, but im getting the same error. I see that this firmwares that have de BLL4 are not from Sprint, there is a alternative to dowgrade my device BLL#number# to go back to Stock Sprint? like install from TWRP the firmware, that will be secure?
Click to expand...
Click to collapse
Sounds like the partitions are different with the file you flashed and the stock sprint firmware. I sometimes tell Odin to re-partition to get back to stock along with the nand erase option checked as well. Just a thought... its how I get a screwed up flash back to stock, but you need a stock sprint firmware not a combo file. if you have twrp then your not stock at all and flashing a stock firmware will replace it back to original.
MindTrix said:
Sounds like the partitions are different with the file you flashed and the stock sprint firmware. I sometimes tell Odin to re-partition to get back to stock along with the nand erase option checked as well. Just a thought... its how I get a screwed up flash back to stock, but you need a stock sprint firmware not a combo file. if you have twrp then your not stock at all and flashing a stock firmware will replace it back to original.
Click to expand...
Click to collapse
Thanks for the Reply.
I sove it with the G955USQS5CRF5 file from Verizon, seems that it its compatible with the Spint firmware. I flashed with Odin, and make a FactoryReset at Recovery menu. That fixed it!
Good evening,
None of this worked. I followed the steps to a T. Put all files in and received this error? What am I doing wrong? I tried rooting my Sprint G955U and that failed. Didn't trip knox, which says 0x0 currently, but disabled fingerprint id, face recognition, samsung pay - says device has been rooted. In about section, specifies "official". Also, a new update just came out a few days ago in August, 2018. I tried to update and that failed as well. I put all these files in odin and it failed pretty quickly. Please help me restore my phone. Please see attached photos. Currently, running Android Oreo.
Serious help!
Alright so bare with me guys I’ve been an android user for a very long time (don’t kill me) but i recently moved to iOS yes I know ? lol point is I bought my girl a s8+ (well she did with my money lol) and of course being a female she got played and bought a locked device meaning frp and since I haven’t been in the Android scene in a Lil I did some diggin but came up with nothing really the phone is on G955USQS5CRF5 but I can’t find a combination for it so is she/we screwed?
kiddPREMIERE said:
Alright so bare with me guys I’ve been an android user for a very long time (don’t kill me) but i recently moved to iOS yes I know ? lol point is I bought my girl a s8+ (well she did with my money lol) and of course being a female she got played and bought a locked device meaning frp and since I haven’t been in the Android scene in a Lil I did some diggin but came up with nothing really the phone is on G955USQS5CRF5 but I can’t find a combination for it so is she/we screwed?
Click to expand...
Click to collapse
You're gonna wanna check out jrkruses thread which as an frp remove flashable zip through safe strap
https://forum.xda-developers.com/verizon-galaxy-s8+/development/rom-t3771206
bullracing said:
Thanks for the Reply.
I sove it with the G955USQS5CRF5 file from Verizon, seems that it its compatible with the Spint firmware. I flashed with Odin, and make a FactoryReset at Recovery menu. That fixed it!
Click to expand...
Click to collapse
Do you have the Combination file for G955USQS5CRF5? Can you provide a link to it?
CLKeenan said:
Do you have the Combination file for G955USQS5CRF5? Can you provide a link to it?
Click to expand...
Click to collapse
Sorry I didnt saw your reply, do you still Need it? I erased it from my computer but I can get it for you if you need it
i have just installed rooted frimwire in my galaxy s8 plus g955u and trying to get back in fectory frimwire i have searched on google but nothing found but today i have seen this post for get back in recovery am downloding file thank you so much for the post have a nice day :laugh:
---------- Post added at 12:19 PM ---------- Previous post was at 12:14 PM ----------
Dear ' sir i have s8plus sm-g55u snapdragon with locked bootloader and i have installed a rooted frimwire in my phone pda is also G955USQS2BQL1 is that possible to use this file is done to get back in stock frimwire ?