Database Users

Mobile Odin Pro Fails?

Hi,
I got the N7100 on launch day, and rooted using CWM, leaving my phone with a 'custom' recovery, which is noted on the download boot mode.
Now that triangleaway supports the N7100 I thought I would try and get it less dodgy looking which still rooted.
When I ran triangle away, it warned that a custom bootloader / recovery might leave the counter on 1 even after away'ing the triangle...
So I thought I would use mobile Odin Pro to flash stock rom, injecting SU and mobile odin (as i did many times on my note 1).
This failed (using rom N7100XXALJ1_N7100OXXALJ1_BTU) - it verified the MD5 ok, and rebooted into a screen ive never seen before, containing a large blue Android figure with a lightening bolt on his chest. I personally thought he looked a little unhappy as well...
Anyway, first time this happened, i used desktop odin to do a full flash, which fixed it (but increased my custom counter more since I rerooted with CWM+root).
Second time it happened, i fixed it by just re-flashing CWM.
Anyone else had success with Mobile Odin on the N7100 ??? do you think it was the CWM install that it didnt like ?
Im unsure how to flash just the recovery, and am a bit confused between the relationship between the boot image and the recovery one... i wouldnt have expected the recovery image to affect normal boot, but it does.
George
UPDATE - The blue android is actually the mobile odin pro logo... gonna try again and be a little more patient...

...you....fool

Left it 10 mins, and still stuck on blue android screen... gonna try flashing from sd card rather than internal card in case its that...
luckly reflashing cwm6-root-note2.tar from odin fixes it...
Also tried flashing from external sd, and that also failed.
Does anyone know how Chainfire likes issues to be reported?
thanks
George

You can get answer your some question here
http://forum.xda-developers.com/showthread.php?t=1930418

Is that blue android screen not doing anything at all?
I was the one who tested this app prior to its release (on behalf of chainfire who didn't have the phone at that time), I flashed from internal and external without issue.
What is it your flashing exactly? Your not listing it as a OTA/Update.zip are you?
Try to delete the Mobile Odin file off the root of your sd card and open the app again, it will then re-download the files it needs, try it then.

A few other users have reported the exact same problem, and I am pretty sure it will be related to the problem of Triangle Away not always booting up.
Something fishy is still going on with recoveries, and we're not sure what. I can't replicate the problem on my device - at all - so I can't fix it either.
Maybe it has something to do with bootloader version? It seems some people/firmwares have different bootloaders than others and can cause various problems.
What I find strangest is that the Mobile ODIN logo does show up ... that's just weird. Can you use the attached version of Mobile ODIN (its an older version that does not support the Note2) to create a dump file for your device, so I can compare it with the dump files from working devices? It may offer a clue.
EDIT: Download removed, dump made and received.

Dumping...
Hi Chainfire,
Thank you for the response im impressed by your commitment to making our devices better ...
Im doing a dump now [fnarr fnarr] and will make it available to you as soon as its done.
I presume it will be quite large if it takes 30 mins to upload - shall I pm you or email you the dropbox link where i plan to put it?
LennyUK - im flashing what is supposed to be (and in fact is) the latest official rom - i believe its the original shipped rom + an OTA that the UK got. Not sure if it comes from Samsung or its been hacked together from the OTA + original rom. It was downlaoded from sammobile (as i always did with my note 1). Its a tar file (.md5) containing a bunch o f.img files and modem.bin. Im not convinced the N7100 mobile odin flash kernel was corrupted - i would expect CF does a checksum of some sort... ill await his response to my dump.
ps. Why doesnt XDADevelopers email notification work
cheers
George
Chainfire said:
A few other users have reported the exact same problem, and I am pretty sure it will be related to the problem of Triangle Away not always booting up.
Something fishy is still going on with recoveries, and we're not sure what. I can't replicate the problem on my device - at all - so I can't fix it either.
Maybe it has something to do with bootloader version? It seems some people/firmwares have different bootloaders than others and can cause various problems.
What I find strangest is that the Mobile ODIN logo does show up ... that's just weird. Can you use the attached version of Mobile ODIN (its an older version that does not support the Note2) to create a dump file for your device, so I can compare it with the dump files from working devices? It may offer a clue.
Click to expand...
Click to collapse

Dump
Hi,
Here is the dump ...
thanks
George
EDIT: Dump received and removed, thanks.

had the same problem when trying to flash the exchange hack.
used pc odin to upload CWM and this made my phone boot again

Hi, for the record, i tried triangleaway, and ... it booted into it OK, and ran the procedure to reset the counter...
and its worked... I now get
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
im guessing the custom is due to CWM recovery...
cheers
g

Weirdness. It appears your cache partition is borked (its 10 MB instead of 1.5 GB ?!). This could explain the following problems people have reported:
- Mobile ODIN showing the logo but doing nothing else
- Triangle Away breaking recovery
Try flashing the attached cache file in (desktop!) ODIN, then try Mobile ODIN, Triangle Away, etc again. Problem should be solved then - please do let us know, several people are having this problem.
It's a ZIP file, extract once so you end up with a TAR file, put that in ODIN. If you end up with an IMG file, you extracted twice!
EDIT: Note: after flashing this image you will probably automatically boot into recovery - this is expected, just press power to reboot normally.

Hi,
Thank you... flashed the cache.zip, and it rebooted to the Galaxy Note II screen, then rebooted, over and over again...
so I reflashed the rooter, (cwm6-root-note2.tar) which DOES include flashing the cache, so maybe thats got a broken cache in it ? (the reflash fixed it)
odd...
Ive attached to rooting tar ive been using with the strange (but working...) cache file...
cheers
g
Chainfire said:
Weirdness. It appears your cache partition is borked (its 10 MB instead of 1.5 GB ?!). This could explain the following problems people have reported:
- Mobile ODIN showing the logo but doing nothing else
- Triangle Away breaking recovery
Try flashing the attached cache file in (desktop!) ODIN, then try Mobile ODIN, Triangle Away, etc again. Problem should be solved then - please do let us know, several people are having this problem.
It's a ZIP file, extract once so you end up with a TAR file, put that in ODIN. If you end up with an IMG file, you extracted twice!
EDIT: Note: after flashing this image you will probably automatically boot into recovery - this is expected, just press power to reboot normally.
Click to expand...
Click to collapse

Failed to upload..
at
https://dl.dropbox.com/u/279536/cwm6-root-note2.tar
thanks
g
ripnetuk said:
Hi,
Thank you... flashed the cache.zip, and it rebooted to the Galaxy Note II screen, then rebooted, over and over again...
so I reflashed the rooter, (cwm6-root-note2.tar) which DOES include flashing the cache, so maybe thats got a broken cache in it ? (the reflash fixed it)
odd...
Ive attached to rooting tar ive been using with the strange (but working...) cache file...
cheers
g
Click to expand...
Click to collapse

Yes, I confirm it is definitely the cwm6-root-note2 package that messes up your device. I've checked it out - its the cause for all the problems with Mobile ODIN and Triangle Away. It breaks the cache partition on your phone ( dr.ketan ... )
The reason flashing the fixed cache.tar didn't immediately fix your problems was because you still had a messed up recovery, so you also needed to flash a recovery, which you did now again with the cwm6 package. However, your cache is again broken. So now, *again* apply cachefix, and all should be good, and you should be able to use Mobile ODIN and Triangle Away.

Chainfire said:
Yes, I confirm it is definitely the cwm6-root-note2 package that messes up your device. I've checked it out - its the cause for all the problems with Mobile ODIN and Triangle Away. It breaks the cache partition on your phone ( dr.ketan ... )
The reason flashing the fixed cache.tar didn't immediately fix your problems was because you still had a messed up recovery, so you also needed to flash a recovery, which you did now again with the cwm6 package. However, your cache is again broken. So now, *again* apply cachefix, and all should be good, and you should be able to use Mobile ODIN and Triangle Away.
Click to expand...
Click to collapse
Sorry if it was asked before but will you release cf root with cwm recovery for note2? thx

I have no plans to release anything related to CWM ever again.

Chainfire said:
I have no plans to release anything related to CWM ever again.
Click to expand...
Click to collapse
Damn :/ btw what about your root? which wouldnt have issues with ta and mobile odin

EdgaBimbam said:
Damn :/ btw what about your root? which wouldnt have issues with ta and mobile odin
Click to expand...
Click to collapse
There might be a CWM-less CF-Root coming, indeed.

Hi.
That worked perfectly. I can confirm successful flash via mobile odin once I had fixed recovery and flashed that cache fix.
Many many thanks...
George

That wud be very nice.
Thank you..
Sent from my GT-N7100 using xda premium

[Q] I believe I have also soft bricked my Rogers (Canadian) S4 i337m

Hi all,
I think I have soft bricked my S4 i337m rogers Canadian variant.
I had rooted / unlocked the bootloader with motochopper successfully.
- I am using CWM
First thing I tried to do was backup the phone onto the external SD which would not work so I just went onto the next step.
I tried flashing a ROM onto the phone after doing phone restore and clearing cache. All installed correctly (apparently) and now when I boot up the phone the Samsung logo will appear for about 5 seconds then the phone will go black and try to boot up again.
The good:
- i have access the recovery mode still
The bad:
- no recovery made for the phone
- seems to be boot looping
As a side not I have tried installing a couple other ROMs which all result in the same issue.
Is there anything that can possibly be done?
I would happily put the stock ROM back on the phone.
All help would be greatly appreciated!
Rob.

9 times out of 10 a factory reset will get you out of a boot loop. Do that in recovery and reboot.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

Hi thanks for the reply. I have tried the factory reset and still does not fix the issue

Robby29 said:
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Click to expand...
Click to collapse
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin

kiru said:
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
Click to expand...
Click to collapse
Okay great I will try these. Does the kernel have to be specific to the ROM?

Robby29 said:
Okay great I will try these. Does the kernel have to be specific to the ROM?
Click to expand...
Click to collapse
The kernel is specific to your device. so you would use the i337M kernel.
So the procedure would be flash the rom of your choice, then before you boot flash YOUR i337M kernel, it will boot.
Good luck.

And make sure you do not flash a rom for the i9500 as you will hard brick

Also,
Make sure you choose the right i337m kernel. ie. a TouchWiz kernel for TW Roms and an AOSP kernel for CM10.1/AOSP Roms.
You should be able to:
remove your sdcard,
format it to fat32,
download the correct rom and kernel for you i337m to your freshly formatted sdcard,
put the card back into your phone,
boot into recovery,
install ROM zip from ext-sdcard,
install Kernel zip from ext-sdcard,
reboot.
phew....sounds like a lot of steps but not really I guess.

we good up in here....

Soft Brick S4
TheAxman said:
we good up in here....
Click to expand...
Click to collapse
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!

car154 said:
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
Click to expand...
Click to collapse
Thanks for posting this. I hope many people read it. Anyone who flashes needs to know how to return to stock before they start flashing roms. You will need it someday!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app

[Q] Bootloader - Keep rebooting

[Short Version] I've messedup my bootloader not sure how to sort it out got samsung s4 i9505 uk.
[bit lengthy?] i have gone through hell lots of stages to cut it short i spent 12 hours or so just sitting to flash stock rom back and didnt want to lose SU, i started with this thread http://forum.xda-developers.com/showthread.php?t=2250824 and after downloading 4.3 and 4.2.2 thought i'd try with 4.2.2 and after installing it, the wifi had problem so thought to go for the 4.3 tried installing and changing bootloader now its keep rebooting within bootloader and thought i'd ask for some help this being my cousin phone she'll kill me , she brought it to get it sorted ehm! and i ended up messing it up.
oh well here we go...
thanks for anyone trying to help in advance.
await....

Tell in more details what you actually did. Tell us step by step. Give as much information as possible. What files did you flash? In what order did you flash them?

supermaster said:
[Short Version] I've messedup my bootloader not sure how to sort it out got samsung s4 i9505 uk.
[bit lengthy?] i have gone through hell lots of stages to cut it short i spent 12 hours or so just sitting to flash stock rom back and didnt want to lose SU, i started with this thread http://forum.xda-developers.com/showthread.php?t=2250824 and after downloading 4.3 and 4.2.2 thought i'd try with 4.2.2 and after installing it, the wifi had problem so thought to go for the 4.3 tried installing and changing bootloader now its keep rebooting within bootloader and thought i'd ask for some help this being my cousin phone she'll kill me , she brought it to get it sorted ehm! and i ended up messing it up.
oh well here we go...
thanks for anyone trying to help in advance.
await....
Click to expand...
Click to collapse
Don't panic ... hopefully somebody can give you a helping hand :fingers-crossed:
BTW you might wan't to change your nickname after this LOL

supermaster said:
[Short Version] I've messedup my bootloader not sure how to sort it out got samsung s4 i9505 uk.
[bit lengthy?] i have gone through hell lots of stages to cut it short i spent 12 hours or so just sitting to flash stock rom back and didnt want to lose SU, i started with this thread http://forum.xda-developers.com/showthread.php?t=2250824 and after downloading 4.3 and 4.2.2 thought i'd try with 4.2.2 and after installing it, the wifi had problem so thought to go for the 4.3 tried installing and changing bootloader now its keep rebooting within bootloader and thought i'd ask for some help this being my cousin phone she'll kill me , she brought it to get it sorted ehm! and i ended up messing it up.
oh well here we go...
thanks for anyone trying to help in advance.
await....
Click to expand...
Click to collapse
if it reboot to bootloader it sounds like theres a bad flash
how did you flash it?
also i assume you tried to flash a older version of Samsung Firmware witch has Unsecured bootloader (which means sound,wifi etc won't work)
to make it work get Odin, boot into download mode
flash the 4.3 leak (or make it withing recovery if you have a custom one)
Instructions For Flashing Firmware:
- Extract (unzip) the firmware file
- Download Odin3 v3.09 (From here or here)
- Extract Odin .ZIP file
- Open Odin3 v3.09
- Restart phone in download mode (Press and hold Home + Power + Volume down buttons)
- Connect phone and wait until you get a blue sign in Odin
- Add AP_I9505XXUEMI8_1715731_REV06_user_low_ship_MULTI_ CERT.tar.md5 to AP
- Add BL_I9505XXUEMI8_1715731_REV06_user_low_ship_MULTI_ CERT.tar to BL
- Add CP_I9505XXUEMI8_1715731_REV06_user_low_ship_MULTI_ CERT.tar.md5 to CP
- Add CSC_OXA_I9505OXAEMI8_1715731_REV06_user_low_ship_M ULTI_CERT.tar.md5 to CSC
- Make sure re-partition is NOT ticked
- Click start button, sit back and wait a few minutes.
- If you encounter any issues with the firmware (Any FC, Bootloop etc)
- Boot into recovery mode (Home+power+vol up)
- Choose to wipe/factory reset. (THIS WILL ERASE ALL OF YOUR DATA INCLUDING YOUR INTERNAL SD CARD!)
- Then choose reboot and you should be good to go!
if you have reverted to older firmware and upgrading to 4.3 again make a full wipe in recovery, just make sure you backup all her data before

sounds like a soft brick.
i did that to mine trying to put a rom on it.
I needed the boot.img

[Q] SM-N900 Soft brick, unable to return to stock

Hi Guys,
This was my original FW:
AP: N900UBUBMI5
CP: N900UBUBMI2
CSC: N900UUBBMI2
Model: SM-N900 International version ( no carrier branding etc), FW version was from Uruguay
I flashed the wrong stock yesterday, and when I found the right one and tried to flash back it wouldn't work. I keep on getting a failed message in Odin in the system.img stage. Tried several different stock roms, tried to wipe data in recovery with no luck. Anyone know what I can do?

yoedba said:
Hi Guys,
This was my original FW:
AP: N900UBUBMI5
CP: N900UBUBMI2
CSC: N900UUBBMI2
Model: SM-N900 International version ( no carrier branding etc), FW version was from Uruguay
I flashed the wrong stock yesterday, and when I found the right one and tried to flash back it wouldn't work. I keep on getting a failed message in Odin in the system.img stage. Tried several different stock roms, tried to wipe data in recovery with no luck. Anyone know what I can do?
Click to expand...
Click to collapse
You have posted the same question twice: (original link) http://forum.xda-developers.com/showthread.php?t=2489935
I have provided you instructions with a process to ROOT, install TWRP and work with the appropriate ROM files to get things operational. You responded to my PM stating you already had a recovery ROM you tried but it still fails.
Unfortunately, I have a feeling your device is glitched which is why I recommended you follow each section and each step to the letter. I understand this is redundant steps as you would be ROOTING, installing TWRP and going through a similar process as before but it's what we call process of elimination with troubleshooting in case something happened during the ROOT or with the install of your TWRP software. I have provided you with the appropriate ROM file and TWRP files for your device which should hopefully do the trick but downloading them takes time as hotfile limits your download speed.
I'm being a bit direct but your situation is more of a troubleshooting matter which takes time and has no magical/quick answer. Rather than posting twice, please try what is suggested and respond with the outcome so we can further troubleshoot.
Thank you!

Hi,
I really do appriciate all your help but it seems something else is going on. Once you told me the first time I installed TWRP already and that didn't solve the problem. I always get stuck in odin in the flashing of the system.img. I already tried everything you said many times today but it didn't work
Maybe this phone is different than other phones.

yoedba said:
Hi,
I really do appriciate all your help but it seems something else is going on. Once you told me the first time I installed TWRP already and that didn't solve the problem. I always get stuck in odin in the flashing of the system.img. I already tried everything you said many times today but it didn't work
Maybe this phone is different than other phones.
Click to expand...
Click to collapse
I understand you have installed TWRP to try and do a recovery but this is what I'm saying... Maybe the ROOT went sideways and something is glitched in the device. If you follow my instructions which I provided via PM, this involves rooting the phone again, installing TWRP from scratch and going through each step as if it were a new device. It will take about 1 hour to do this process due to hotfile server speeds but once you've gone through this process, if it still hangs then another problem may be occurring. My thoughts are the ROOT itself or the TWRP recovery have become corrupt somehow causing you to get stuck during the flashing process.
Hope this helps!

cellrama said:
I understand you have installed TWRP to try and do a recovery but this is what I'm saying... Maybe the ROOT went sideways and something is glitched in the device. If you follow my instructions which I provided via PM, this involves rooting the phone again, installing TWRP from scratch and going through each step as if it were a new device. It will take about 1 hour to do this process due to hotfile server speeds but once you've gone through this process, if it still hangs then another problem may be occurring. My thoughts are the ROOT itself or the TWRP recovery have become correct somehow causing you to get stuck during the flashing process.
Hope this helps!
Click to expand...
Click to collapse
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...

yoedba said:
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...
Click to expand...
Click to collapse
OK, when you go into TWRP, from the touch base menus, click on format or wipe and within this menu, click on each option in a clockwise direction twice. This will wipe your device and hopefully come this time, you'll be able to ROOT the device again. Let us know how it works.

yoedba said:
You might be right, but when I tried to root my device again I got into a boot loop. My phone doesn't have a operational operating system so the root wouldn't work it just boot looped. After that I re installed TWRP and proceeded but again failed in the same place...
Click to expand...
Click to collapse
Issue has been resolved as indicated by OP in this thread: http://forum.xda-developers.com/showthread.php?p=46653062#post46653062

[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.