Database Users

[STOCK ROM]Use for going back to stock before flashing a custom ROM with minimum risk

\\\\\\\\\\\\warning///////////
It seems that phones batch 1010 and newer dont like this method of going back to stock. If you're caught in a boot loop try flashing the official froyo for Captivate. One source can be found here
\\\\\\\\\\\\warning///////////
Disclaimer: Anything you do with the content found in this thread and the content that this thread links to, is your own choice and you are fully responsible for what happens to your phone.
This method is for ATT Captivate ONLY!
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
The purpose of this thread is to give flash addicts/custom ROMs users a more secure way to go back to stock - JF6 - without risking bricking their devices.
Do not use this if you want to send your phone back to ATT or Samsung for warranty!
Use this if you want to go back to stock before flashing a custom ROM.
Use this without worries if you changed your boot screen image or if you flashed the secondary boot loader which allows you to enter download/recovery with key combos.
This package contains NO BOOTLOADERS and NO PARAM.LFS!
Download the package from here
Download Samsung Kies and install it. It will install the latest Samsung drivers.
How to:
Remove sdcard and SIM card from the phone
Extract JF6_secure.zip somewhere.
Boot in Download Mode (see below)
Run Odin3 v1.3.exe
Click on the button PDA
Choose JF6_secure.tar.md5
Click start.
Wait and do not unplug cable until it is finished
How to boot in download mode:
There are 3 methods:
Method 1: (ADB) - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons
Plug in the USB cable and continue holding both Volume buttons
Method 3: (JIG)
Link
If moderators believe this does not belong in development, I have nothing against to moving it to General. However, I think the community would appreciate if it would remain here.

Works fine
I used this to flash the latest Continuum 3.5 and everything worked fine. Thanks!

you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered NO BOOTLOADERS! @@ YAY

Yep, updated, thanks!

Thanks for this and I appreciate all your work.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

Success !!
Just used this to go back to stock prior to flashing another ROM. Worked with no problems and only took about 5 minutes. Will use this from now on to avoid the possible brick.
Again, really appreciate you providing this for us.

Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???

sircaper said:
Still not sure why one would use this over the DG Odin? Maybe someone can clarify?
Here is my scenario. I'm currently on Cognition 3.04 which I flashed from stock. It was my first ROM so I didn't have to go back or do anything with Odin. Now, if I want to flash a new ROM, I plan on using Odin, jut not sure which one???
Click to expand...
Click to collapse
Here you go again, is in the OP
We all know that there is a very often used method of going back to stock found here. The problem is that the ODIN OneClickDownloader contains both boot loaders and param.lfs.
These files, if not flashed correctly or if the connection between phone and PC drops while flashing them, can brick your phone for good. The reason why would this happen is because of unreliable USB drivers.
Click to expand...
Click to collapse

on top of the read phail, i would add that you dont need to flash stock between roms, you only need to do it after a failed flash or a "no wipe" rom that depends on original files, **which they dont do anymore**. All the good full roms do a wipe before flashing. so there is no point going to stock! hope that clearifies!

icezar1 said:
Here you go again, is in the OP
Click to expand...
Click to collapse
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?

sircaper said:
I did read it, just thought there was something I was missing.
I thought there was more to it than people having bad usb ports. You're saying if one does have a bad usb port and flashing gets interrupted, their phone would be bricked with the DG Odin, but with this Odin it would somehow be ok?
Click to expand...
Click to collapse
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?

icezar1 said:
If you own a computer you definitelly heard about BIOS and you heard that if the BIOS gets screwed (CMOS chip burned or bad BIOS update) you can pretty much throw the motherboard.
Well, imagine that your phone has 3 BIOSs
primary bootloader - boot.bin
secondary bootloader - sbl.bin
hidden partition for system images - param.lfs
and that they are dependent on each other and if one of them gets screwed you wont be able to get to recovery and download mode.
The one click downloader contains all these 3. My package does not.
Get the point?
Click to expand...
Click to collapse
Makes sense. Is there ever an instance where those files need to be wiped, though?

sircaper said:
Makes sense. Is there ever an instance where those files need to be wiped, though?
Click to expand...
Click to collapse
Not really. Only if you flashed a boot loader from a different SGS model.

icezar1 said:
Not really. Only if you flashed a boot loader from a different SGS model.
Click to expand...
Click to collapse
Thanks. Appreciate you clearing things up for me.

Trusselo said:
you may want to include the info "FOR ATT i897" phones.
as, well... check my sig!~ i got the rogers i896 covered
Click to expand...
Click to collapse
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.

Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.

WickedNite said:
Oh yea, I forgot to use this a while ago. Next time I'll use this, I promise. Lol. Btw, is it okay to change the text on the .ini file? I somewhat changed the title to my liking.
Click to expand...
Click to collapse
Yes, is OK

Has anyone flashed the three button fix? I really want to. just wanna verify its ok.

likiud said:
Does that mean your stock rom doesn't include the boot loaders and param.lfs either? I've been dying to try that one when I switch roms. I hate seeing the ATT logo pop up everytime i turn it on.
Click to expand...
Click to collapse
take a look here

double RL said:
Has anyone flashed the three button fix? I really want to. just wanna verify its ok.
Click to expand...
Click to collapse
You dont have the 3 button fix?
EDIT: yes, is OK, I tested it. Make sure you run a md5 checksum after putting it on your sdcard

[Q][9001]Telephone can't power on

....

What do you mean with "I've locked my screen on my sgs+ with CM9 by arco".
Explain what you did.
Have you flashed his recovery.img before you tried to install the zip within CWM? If so, which command did you use?
What was the last thing you did/saw on your phone?

——

VinceBoxx said:
the rom was ok.. I've put the new recovery with cwm. The last think that I've done with my telephone is lock the screen... Whent I've pressed the hold button to use the telephone and the screen don't respose. So I've tryed to remove and reinsert the battery and power on, but it don't do anything
Click to expand...
Click to collapse
Try to connect your phone with your computer with your usb cable. Does it recognize your phone / does it charge?
If not pull your battery out/put in again and try again.
Some people already explained that they phone would suddenly reboot or shutdown when beeing too long in standby but they can turn on their phoone normally.
I'm afraid your phone is bricked when nothing helps.
Please describe every step you did.
Which ROM and recovery did you use before flashing Arco's Recovery.img?
How did you installed the Recovery.img, did you use Adb shell or the Odin package?
Did you wiped your data and cache?
Have you tried to restore something from your GB ROM with eg Titanium backup?
And so on.
Edit:
I'm pretty sure Arco isn't reading this forum section. Please gather all information and post your detailed problem in
http://forum.xda-developers.com/showthread.php?t=1336253&page=126

——-

VinceBoxx said:
I've flashed recovery with a cwm packege posted in the cyanogenmod porting 3rd.
Click to expand...
Click to collapse
So you installed the recovery.img (CWM package) through Feamod Recovery? Was that CWM package uploaded by Arco?
It's always your risk to flash a custom ROM and you should lose your warranty officially (at least that's what they say and want u to believe). Give them the information that this problem appeared while flashing an official update with KIES.

—/

[Q] Bootloop and Can't flash new rom

Hi,
I have a Milestone 2. It was running CM10. I decided to put CM7. I was already rooted of course, so I just downloaded new gaaps and CM7 and reboot into the recover menu. There I installed both zip files and wiped data, cache and dalvik. Reboot the system and now I'm stuck on bootloop. Don't even see the cyanogen mod screen, only Motorola logo. Rewipe data doesn't work either.
So I thought I could flash a new rom, the retail rom but RSD Lite don't recognize the phone.
I cannot install any rom because when I press X and power up, what I get is the official boot loader, which doesn't accept any install from zip card that is not signed.
So what now? Throw this phone at the wall? Almost going to windows phone anyway. Please help, I have no money to buy another phone right now.

douglasrac said:
Hi,
I have a Milestone 2. It was running CM10. I decided to put CM7. I was already rooted of course, so I just downloaded new gaaps and CM7 and reboot into the recover menu. There I installed both zip files and wiped data, cache and dalvik. Reboot the system and now I'm stuck on bootloop. Don't even see the cyanogen mod screen, only Motorola logo. Rewipe data doesn't work either.
So I thought I could flash a new rom, the retail rom but RSD Lite don't recognize the phone.
I cannot install any rom because when I press X and power up, what I get is the official boot loader, which doesn't accept any install from zip card that is not signed.
So what now? Throw this phone at the wall? Almost going to windows phone anyway. Please help, I have no money to buy another phone right now.
Click to expand...
Click to collapse
Why doesn't RSD get your phone? Is the cable fine? What about both your pc and the phone's usb ports? What about battery, and drivers? What version of rsd are you using?
X and volume up is stock recovery, not bootloader mode...

Lean946 said:
Why doesn't RSD get your phone? Is the cable fine? What about both your pc and the phone's usb ports? What about battery, and drivers? What version of rsd are you using?
X and volume up is stock recovery, not bootloader mode...
Click to expand...
Click to collapse
Hi. Thanks for the reply.
It does work. I didn't know I had to put on bootloader screen (Vol Down + Camera and Power button).
My problem now is that I want to go back to stock rom or at least CM7. My firmware is 4.5.2-51_ML2-27 with Android 2.3.6 from a creepy spanish rom (the only one that works on my phone).
With this firmware I cannot have CM7. My question is why I cannot have any other either.
At this page: http://sbf.droid-developers.org/umts_milestone2/list.php
I tried the Retail Brazilian that starts with M2L_U6_4.5.2_51-27. Isn't this one using the exact firmware I have? Why it doesn't work?
When I apply this one or even the original from my phone (Tim Brazil) all I get is a black screen, not even the M logo.
I'm afraid to downgrade as others said it will brick the phone.

douglasrac said:
Hi. Thanks for the reply.
It does work. I didn't know I had to put on bootloader screen (Vol Down + Camera and Power button).
My problem now is that I want to go back to stock rom or at least CM7. My firmware is 4.5.2-51_ML2-27 with Android 2.3.6 from a creepy spanish rom (the only one that works on my phone).
With this firmware I cannot have CM7. My question is why I cannot have any other either.
At this page: http://sbf.droid-developers.org/umts_milestone2/list.php
I tried the Retail Brazilian that starts with M2L_U6_4.5.2_51-27. Isn't this one using the exact firmware I have? Why it doesn't work?
When I apply this one or even the original from my phone (Tim Brazil) all I get is a black screen, not even the M logo.
I'm afraid to downgrade as others said it will brick the phone.
Click to expand...
Click to collapse
Because you ARE downgrading.
I think this "creepy spanish rom" you describe is the one from Movistar Latinamerica (which is true, it sucks as a carrier) and it's BL=4, but retail brazilian is BL=3, that's the problem.
And yes, you can have CM7. Root with Cydia Impactor, bootstrap recovery, and flash CM7.

Lean946 said:
Because you ARE downgrading.
I think this "creepy spanish rom" you describe is the one from Movistar Latinamerica (which is true, it sucks as a carrier) and it's BL=4, but retail brazilian is BL=3, that's the problem.
And yes, you can have CM7. Root with Cydia Impactor, bootstrap recovery, and flash CM7.
Click to expand...
Click to collapse
isn't cm7 based on froyo bl? when he comes from cm10.1 he has to have gb bl, right? so to get cm7 he has to downgrade with endless7s downgrade methode or use cm7.2 (gb based), hasn't he? please enlight me as well, lean946

lulli1 said:
isn't cm7 based on froyo bl? when he comes from cm10.1 he has to have gb bl, right? so to get cm7 he has to downgrade with endless7s downgrade methode or use cm7.2 (gb based), hasn't he? please enlight me as well, lean946
Click to expand...
Click to collapse
Yeah, you're right, I forgot.
Still, he has endless' CM7 http://forum.xda-developers.com/showthread.php?t=1239778 or somebody could make a 2ndboot version of CM7 one day...

douglasrac said:
Hi,
RSD Lite don't recognize the phone.
Click to expand...
Click to collapse
I came across this same problem, I have a Windows 8.1 64.
The solution was found quickly:
1. RSDLite6.1.5
2. Only USB 2.0, either in the same slot USB 3.0 device is not detected

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

Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!

GST_Diandre said:
Hi all,
So I've decided to root my Exynos International Galaxy Note 3 (SM-N900) using Chainfire's CF-Auto-Root. All went well until Odin got stuck at cache.img, then fails after a couple of minutes. I unplug the phone and restart it, it then displays "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again" whenever I try to boot. I can access download mode again, but not recovery. My phone is stock 4.2.2.
It's the first time I have such a problem, I flashed a couple of phones before without any trouble. I searched XDA for a solution and tried other Odin versions, different cable/ports, even tried on another computer: Same issue. Stuck at cache.img. I can't get my phone to work again. Some people suggested it might have something to do with USB debugging, but I can't remember if I left it enabled or disabled.
I didn't back any of my data (I didn't expect the root to fail...) and retrieving my phone, rooted or not, is of the utmost importance. Please avoid posting solutions that involve data loss.
Feel free to ask about anything I might have left out.
Thanks!
Click to expand...
Click to collapse
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.

Journyman16 said:
I think you'll have to flash an official Sammy Firmware to get past the error, although if you look in the Note 3 Android Development, I recall seeing some deodexed, rooted firmware that is supposed to work from Odin. Not sure if any of them are for exynos version though.
Data? I keep everything I can on the extSD for exactly this reason. You should be able to remove the card and put it in a card caddy and read it in a PC and copy out your media etc. The root process shouldn't have overwritten anything you need.
For rooting, maybe DL the SuperSU zip file Chainfire's website and flash it in Recovery once you're up and running? I use TWRP but Philz or CWM recoveries will do it.
Click to expand...
Click to collapse
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !

GST_Diandre said:
I see. So in newbie terms, if I flash the official firmware I have from SamMobile, I should have my phone back running with all my apps & data? Also, any hint about why rooting didn't work in the first place?
After this tragic experience with Odin, I'm gonna forget root for now, maybe update to Lollipop then think about rooting again.
Thanks for replying !
Click to expand...
Click to collapse
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.

Journyman16 said:
Did the official firmware work when you did it? If so, download Phone INFO Samsung from Play and use it to check what hardware you actually have.
I have had issues with CF-Auto root recently so I flash Stock, then the TWRP md5 file (in Odin 3.09) then I boot into Recovery and flash SuperSU. That gives me Recovery and root. You normally have to run SuperSU when you start so it can update.
U[pdating to LP is a good idea - most of the things going on in Dev are now LP versions.
Click to expand...
Click to collapse
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.

GST_Diandre said:
I didn't flash the official firmware ever. Before trying to root with Odin and getting it stuck, I never flashed or modified anything internally on this phone.
Obviously, I can't use Phone INFO because my phone is stuck at BSOD.
I will upgrade to Lollipop, once I can get my phone working as it was. For now I'm still hesitating to flash the official firmware. I don't know if that would wipe the apps or just get back the phone as it was.
Click to expand...
Click to collapse
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!

Journyman16 said:
It will wipe Apps and Data - it makes your phone like you just bought it.
I didn't realise it was stuck in that mode - just thought that happened whenever you tried to flash something.
First thing. Turn phone off. Take back off and remove battery for 10 secs or so. Turn it on holding down Vol Down + Home + Power - release when DL screen shows and press Vol Down. If that gets you into the phone, spend some time saving your data to extSD.
I use Call Logs Backup & Restore, SMS Backup & Restore, I export my Contacts to ext storage. I use TiBu to backup all my apps to a folder on extSDCard. If you are on Stock ROM, you should be able to set your camera to save to extSDCard but you need a file explorer (I use ES File Explorer) to copy your current DCIM folder across - other than that, look for music, documents and video folders on internal memory)
If it doesn't open the phone for you, & your data is important, take card out and use adapter to save data onto a computer.
Go to Sammobile and download the proper official firmware for your phone - note you need to set up a free account before you can DL.
Download Odin 3.09 Run Odin
Then repeat the phone process but this time press Vol Up when at the DL screen. It is important to have the phone Off and electrically flat before attempting a firmware update.
Connect phone to PC - Odin should recognise it. If it doesn't you probably need the Samsung USB Drivers so get them and install them.
Then connect phone again. Click AP and find your DL from Sammobile. Wait for it to load then press Start. Wait... it will reboot and usually sits on the logo for quite some time.
Set up your phone, and restore or reinstall your apps.
Rotsa Ruck!
Click to expand...
Click to collapse
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !

GST_Diandre said:
Thank you, I just tried going into download mode and pressing vol down, still get the same BSOD. I guess that means phone cannot be recovered as it is...
I'm backing up my stuff now. I have no problem backing up contacts/SMS/etc.., but can you tell me whether I can still back up applications and restore them as they were using Titanium Backup on PC ? I know this should have been done before even soft-bricking my phone, but since it inaccessible to run the app on it...
I already have the official firmware waiting to be installed, just need to be sure about TiBU and that I backed up everything correctly Thanks for answering !
Click to expand...
Click to collapse
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.

Journyman16 said:
That depends... TiBu can only recover what you've saved (obvious I know...) and only if it didn't get wiped in the new firmware flash. (which it will if you didn't choose extSDCard for the backups)
Other than that, once your phone is set up and your Google account active, Play Store will DL all your apps.
Click to expand...
Click to collapse
Okay great So where exactly do I get TiBu for pc?

GST_Diandre said:
Okay great So where exactly do I get TiBu for pc?
Click to expand...
Click to collapse
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.

Journyman16 said:
Unfortunately it's a Play Store app, so first you have to get your phone working.
You could try the attached from Recovery but I have no idea if it would work as it's from my rooted CM12.1 system.
Click to expand...
Click to collapse
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/

GST_Diandre said:
Recovery isn't working for me... The only thing I can access on the phone is Download mode.
I guess it's lost? :/
Click to expand...
Click to collapse
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?

Journyman16 said:
The only other thing I can think of would be using ADB over USB but I don't know if that would work with DL mode or if it is only for Recovery. You'd have to search and learn how to use it.
So maybe time to just get the phone working and make sure for future you have backups?
Click to expand...
Click to collapse
SOLVED. I can't believe how easy it was. I was about to flash it over from scratch but then it struck me.
Chainfire ships Odin with all its root bundles, a version where you cannot untick "Auto Reboot". Because of Auto Reboot being ticked, Odin freezes at "cache.img". It might not freeze for some people but for me, having Auto Reboot activated causes the freeze
Downloading a different version of Odin (any version, I used 3.09) that allows changing parameters and LEAVING EVERYTHING UNTICKED BUT F. RESET TIME works like a charm.
Don't forget to reboot your phone after Odin displays PASS or RESET (Long press power).
I'm going to PM Chainfire about this, and tell a max of people about it.
Thank you for your support
EDIT: Also going to NANDroid my phone. I'm tired of panicking over failed roots

[SOLVED] Cannot flash bootloader or modem/baseband (won't stick!)

I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!

You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C

Thorned_Rose said:
I'm on an N9005. I did not know about Knox when I first got it (came from an S3) and flashed TWRP and Cyanogen (unofficial v13 MM). Funnily enough I tripped Knox 0x1. Since then the phone comes up as custom, etc. and no matter what I do it stays that way, even on completely stock ROM. I have tried Triangle Away but it made no difference (stock rom, rooted with CF Auto Root).
I'm on Arch Linux so I flash everything via Heimdall. Everything else flashes fine, but the bootloader and modem flashes will not stick. I have tried on a Windows PC with Odin as well and didn't work with Odin either. I have tried the trick of flashing and then booting straight back into DL mode and flashing again, but that did not work either.
I have tried flashing the BL/BB on multiple different ROMS, didn't work. I even experimented with flashing the stock rom but with the updated BL/BB files - didn't work and bootlooped so I had to reflash stock. I've tried a different kernel, no difference.
It keeps the original original BL/BB no matter what I do. This phone was originally bought in another country and thus far I have only been able to flash it with the stock rom of that country. If I use my own country's (New Zealand) stock rom, it boot loops.
Could it be refusing this particular BL and BB build? Should I try an older build and see if that works? Or is this a problem related to something else? How can I fix this?
Thanks in advance!
Click to expand...
Click to collapse
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience

Rosli59564 said:
You need to power off the phone completely before flashing them. If doesn't work remove battery for a few seconds then retry. Do not flash with reboot into download mode from rom's power menu.
Sent from my SM-N920C
Click to expand...
Click to collapse
vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering

Thorned_Rose said:
Thank you!!!! Pulling the battery was the missing piece!
I was powering off the phone fully before booting into D/L and then flashing (twice over). Removing the battery beforehand has finally made it stick. Thank you muchly! This was driving me nut so really appreciate you taking the time in aswering
Click to expand...
Click to collapse
I am glad it worked. Cheers

vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!

hackintosh5 said:
Do you know if this still takes effect on new(er) phones? I have an S5 Mini. I'm flashing with Debian heimdall (just param.bin, i'm trying to change the bootlogo). I took out the battery before booting to D/L, and flashed twice (removing battery between flashes). Heimdall reports success, and if I pull the partition with root+dd, I can see my changes. It just doesn't change the logo.:crying: This is driving me crazy,
Thanks in advance,
Hackintosh5
P.S. Please tell me if you think this should be a separate thread!
Click to expand...
Click to collapse
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.

vishnu vijay said:
Instead of booting into the OS have you tried booting into recovery.
Volume home and volume plus combo
Usually there are some patches so the OS doesn't overwrite the Recovery.
Click to expand...
Click to collapse
No, you've misunderstood. I'm trying to flash a bootlogo to the PARAM (.bin) partition, not recovery. Should I try to make an odin package?

I would ask in your phones forum.
Most of Notes cannot modify param.bin

vishnu vijay said:
Flash bootloader twice without reboot.
Don't let the phone get into OS.
Remove the battery and flash the boot loader twice. It will stick.
Telling from experience
Click to expand...
Click to collapse
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?

titan-computer said:
i have the same problem just for bootloader. cp is ok.
i've turned off my phone n9005 and pull out battery and turn on n download mode and flashed BL file in BL section twice without reboot and my bootloader didn't change. any suggestion?
Click to expand...
Click to collapse
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.

Mohamedkam000 said:
Use Odin 3.04,
Maybe the BL you tryna stick is older than the one you already have?
Flash, reboot & pull off the battery when it begins to load bootanimation.
Do it again for 3 times at least.
I could downgrade to KitKat bootloader this way.
Click to expand...
Click to collapse
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.

titan-computer said:
doesn't work.
yeas. it's older than my current bootloader.
i did all things with odin 3.04 but didn't change the bootloader.
in odin 3.04 it has an option "phone bootloader update", do i need to check this? default is unchecked.
Click to expand...
Click to collapse
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).

Mohamedkam000 said:
Of course you need to check it.
Other than that, is the bootloader packed with NON-HLOS.bin or just the *.mbn files?
I mean, is it ~7 MB in size or ~1.7 MB?
You may need to flash a modem file as well to enforce the BL?
If all that didn't work, there's one proved way that will work, use a box (software).
Click to expand...
Click to collapse
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?

titan-computer said:
no it's just mbn files almost 1.7 MB.
i've checked boot loader update and didn't work again. modem got update at the first time but BL doesn't.
what is this? box software?
Click to expand...
Click to collapse
Windows software, named Z3X Box, download it and update your bootloader with, it will definitely success.