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] ODIN stuck at Initialization step

hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..

awesim said:
hi all.. im a beginner at installing custom roms.. i own a Samsung Galaxy S4 i9500.. a few days ago, i updated it to CyanogenMod c-11 (kitkat 4.4.4 based) ROM, then to CyanogenMod c-12 (lollipop based) ROM, so try out its new features.. however, since yesterday, my phone is not booting up.. neither is it able to go into recovery mode.. (the boot logo displays endless).. i can only go into the download mode..
so i downloaded ODIN.. and tried flashing I9500XXUFNI2_I9500ODDFNI1_INS.zip onto it.. however, no matter what i do (removing battery, restarting PC, restarting ODIN), i cannot go past the "initialization" step.. no matter which ROM i try, it never goes past the "initialization" step.. please help..
Click to expand...
Click to collapse
Did you try to unzip the stock ROM to receive the .tar file for ODIN?

Joku1981 said:
Did you try to unzip the stock ROM to receive the .tar file for ODIN?
Click to expand...
Click to collapse
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..

awesim said:
yes i did.. the .zip file contains two files:
- SS_DL.dll
- I9500XXUFNI2_I9500ODDFNI1_INS.tar.md5
according to instructions in different online threads, im putting this .tar.md5 in the PDA/AP slot..
Click to expand...
Click to collapse
Change USB cable/port, other pc or close Kies 3 on the task bar.

It sounds more like a hardware failure.

Joku1981 said:
Change USB cable/port, other pc or close Kies 3 on the task bar.
Click to expand...
Click to collapse
Ive already tried changing USB ports.. I dont have Kies installed in the first place.. I'll try repeating the procedure on a different system though..

i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..

awesim said:
i certainly hope it is not a hardware failure.. i literally slept with the phone on charge and woke up to a dead phone.. the phone boots up into the bootloop.. the recovery mode ends in the bootloop as well.. only the download mode ends up in the correct "downloading.. do no turn off target" screen.. and odin detects the phone just fine.. but upgrading any firmware via odin gets stuck on the "initialization" step.. i can answer more questions if required.. at this point i dont care which ROM works for my phone.. or if i lose data.. i just wanna revive my phone..
Click to expand...
Click to collapse
did you solve your problem?

jkamz said:
did you solve your problem?
Click to expand...
Click to collapse
I am also facing the same problem. Were you able to solve it.

no

Buy another motherboard.that solved my problem.There is no other work around

I'm also facing same issue

Bro's, gotta start somewhere, right!
The fact that you're phones are boot looping is actually a good sign - it means that they're not totally useless but salvageable.
Question: Are you able to boot into your custom recoveries, e.g. TWRP? If yes, please reply.
If no, kindly uninstall your old samsung driver, reboot pc, install new driver, put your phone into "Download mode", connect phone to pc, run Odin & hope for the best! If you can get passed this step, then it's smooth sailing...

jkamz said:
no
Click to expand...
Click to collapse
I'm having this issue with mine today, anyone able to resolve this without going true warranty?

Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.

audit13 said:
Is the phone recognized by Odin? Post a screenshot of the Odin error or post the Odin error.
Click to expand...
Click to collapse
i'm facing the same problem with mine,any Fix??need help guys:crying::crying:

Odin is not working because the phone was not assigned a com port.

audit13 said:
Odin is not working because the phone was not assigned a com port.
Click to expand...
Click to collapse
He is right should be blue in com port is it latest Odin 10.7
Sent from my SM-A720F using Tapatalk

The obligatory obvious question here. Do you have the Samsung driver installed?

Just repartition the eMMC chip using .pit file with odin that it is suitable for galaxy S4 i9500.
If anyone has tried, please tell us, that it is work or not.
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Thanks!

[RESOLVED] [Q] SM-G900W8 Stuck at boot screen after editing build.prop

Okay, I've searched the forum for several hours but there's just too much here to make sense of.
My phone is a SM-G900W8 brought home June 19 this year.
Stock Lollipop 5.0 pre-installed.
Code:
Baseband version: G900W8VLU1BOC1
Kernel version: 3.4.0-4100894
Build number: LRX21T.G900W8VLU1BOC1
SE for Android status: Enforcing, SEPF_SM-G900W8_5.0_0002
KNOX version: 2.3
Rooted using CF-Auto-Root (this file), Custom recovery is Philz Touch 6.57.8 klte.
Both of these were in place early on and haven't caused any problems.
Everything was working perfectly fine until last night, when I tried this trick (in first post), rebooted, and now I'm stuck at the splash screen.
Nothing gets me out except a battery pull.
I've tried:
Button combo volup - home - power to go to recovery; this does nothing from the splash screen (actually even pressing and holding down power does nothing), and after a battery pull it won't boot into recovery either.
Booting into download mode (success! yay!) and using Odin to re-flash Philz recovery. Reboot doesn't go into recovery, as stated above.
Just waiting, at various points in the process (while in splash screen, while turned off) to give a chance for things to happen if they just needed time.
So now I'm able to get into download mode and use Odin but from there I don't know what to do next. Flash the bootloader? Okay, but there are so many links...which one do I use? Of all the specs I've gathered, why didn't I find that out?
Can somebody help me please?
[EDIT: Solution and links, for SM-G900W8 users who might be looking for help]
I finally managed to boot into recovery by leaving the USB cable connected to the computer while pressing volup+home+power, a last-ditch trick found in deanr1977's very helpful thread "Read before flashing a Rom (Tips for new & old)"
Links to the firmware for this specific model can be found here, or if you just need a piece:
G900W8_OC1_Stock_Partitions.tar.md5
G900W8_OC1_100%_Stock_Rooted_ROM.zip
Stock_G900W8_VLU1BOC1_Kernel.zip
G900W8-LP-VLU1BOC1-MODEM.tar.md5​

PushyPhoenix said:
Okay, I've searched the forum for several hours but there's just too much here to make sense of.
My phone is a SM-G900W8 brought home June 19 this year.
Stock Lollipop 5.0 pre-installed.
Code:
Baseband version: G900W8VLU1BOC1
Kernel version: 3.4.0-4100894
Build number: LRX21T.G900W8VLU1BOC1
SE for Android status: Enforcing, SEPF_SM-G900W8_5.0_0002
KNOX version: 2.3
Rooted using CF-Auto-Root (this file), Custom recovery is Philz Touch 6.57.8 klte.
Both of these were in place early on and haven't caused any problems.
Everything was working perfectly fine until last night, when I tried this trick (in first post), rebooted, and now I'm stuck at the splash screen.
Nothing gets me out except a battery pull.
I've tried:
Button combo volup - home - power to go to recovery; this does nothing from the splash screen (actually even pressing and holding down power does nothing), and after a battery pull it won't boot into recovery either.
Booting into download mode (success! yay!) and using Odin to re-flash Philz recovery. Reboot doesn't go into recovery, as stated above.
Just waiting, at various points in the process (while in splash screen, while turned off) to give a chance for things to happen if they just needed time.
So now I'm able to get into download mode and use Odin but from there I don't know what to do next. Flash the bootloader? Okay, but there are so many links...which one do I use? Of all the specs I've gathered, why didn't I find that out?
Can somebody help me please?
Click to expand...
Click to collapse
factory reset. Then flash stock rom. if you cant boot into recovery try the latest twrp. It works if its still not working then flash stock firmware from SAMMOBILE with odin. it will work then

Thanks for the reply. The problem I'm having is knowing where to download the files I need to flash - because there are so many threads here for so many different models of this phone. Believe me, I've looked, and keep turning up everything BUT W8
I'm tired and frustrated and need my phone functional - can you point me to a post or a thread with the latest version of TWRP that I can flash with Odin?
[edit] Sorry about that - I found the thread. I'll give that a shot and see what happens.

PushyPhoenix said:
Thanks for the reply. The problem I'm having is knowing where to download the files I need to flash - because there are so many threads here for so many different models of this phone. Believe me, I've looked, and keep turning up everything BUT W8
I'm tired and frustrated and need my phone functional - can you point me to a post or a thread with the latest version of TWRP that I can flash with Odin?
Click to expand...
Click to collapse
EDIT: THESE TOOLS ARE FOR 900F MODEL
Latest twrp from https://twrp.me/
Philz recovery from https://mega.co.nz/#!oVNz0T6C!VII47M...MpQIN2b-PEUYN8
Best Stock firmware 5.0 BTU from http://www.sammobile.com/firmwares/download/44413/G900FXXU1BOC7_G900FOXA1BOC7_BTU/
Enter download mode and Flash either one of the recoveries and Clear dalvik cache, clear cache, format system, format data and then factory reset. After that boot into odin mode directly and flash the Stock Firmware.
note: in Odin uncheck "auto reebot option" and after flashing recovery when the odin shows its done wait 1 minute disconnect usb and pull out battery then turn it on if your phone says "Recovery is seandroid enforcing" wait for 3-4 seconds it will go away and recovery will boot up.

dork997 said:
Best Stock firmware 5.0 BTU from http://www.sammobile.com/firmwares/download/44413/G900FXXU1BOC7_G900FOXA1BOC7_BTU/
Click to expand...
Click to collapse
Now, I just want to check: this is for the G900F; will it make a huge difference to my phone? Can I restore my data directly from the backup? I thought what I needed is the exact stock rom that was installed on this phone when I got it so I've been looking everywhere for the G900W8 firmware. I do intend to play with tweaked ROMs in future, but today's not that day.
Finally managed to boot into recovery after flashing TWRP - read a tip somewhere about doing the keypresses while connected to PC via USB. Currently running a nandroid backup before moving on to all the wiping/formatting steps - at least then if something else goes wrong I've got the latest data. :victory:

PushyPhoenix said:
Now, I just want to check: this is for the G900F; will it make a huge difference to my phone? Can I restore my data directly from the backup? I thought what I needed is the exact stock rom that was installed on this phone when I got it so I've been looking everywhere for the G900W8 firmware. I do intend to play with tweaked ROMs in future, but today's not that day.
Finally managed to boot into recovery after flashing TWRP - read a tip somewhere about doing the keypresses while connected to PC via USB. Currently running a nandroid backup before moving on to all the wiping/formatting steps - at least then if something else goes wrong I've got the latest data. :victory:
Click to expand...
Click to collapse
i am sorry the tools i mentioned are for 900f model. Here http://www.sammobile.com/firmwares/database/SM-G900W8/ you can find firmware for G900W8. Just factory reset format dalvik cache, cache , data and system and flash your stock firmware in recovery. There are many different firmwares available with the exact bootloader and modem but they are carrier specific. I don't know which carrier you are on (if any) so just go through the list and download the firmware you were on, flash it. I will highly recommend you to backup your EFS and modem folder aswell just incase anything goes wrong and u flash the wrong firmware.

Oh! Oh! I found it! The stock ROM, as well as the kernel and the modem! So, next question - should I flash all three or just the ROM?
(God I feel like an amateur right now...Thanks so much for helping me out here dork997. :highfive: )

PushyPhoenix said:
Oh! Oh! I found it! The stock ROM, as well as the kernel and the modem! So, next question - should I flash all three or just the ROM?
(God I feel like an amateur right now...Thanks so much for helping me out here dork997. :highfive: )
Click to expand...
Click to collapse
no prb, Okay if you download the rom from sammobile it should be in a .zip format extract it once and it will give you a .tar.md5 file which you have to flash in odin (this file has bootloader+firmware+modem) if you have 7zip or other such programs it will give you option to re-extract the .tar.md5 file but you dont need to do that just extract the downloaded zip once. and flash it in odin (make sure you factory reset and do the formating steps before flashing it....flashing rom over an old rom has caused some issues for me in the past so i always factory reset before but people also flash without factory reset or formating, choice is urs.

And I believe you've just answered my question. I'll hold off on flashing kernel and modem but I did back up everything, just in case. Wiping/formatting now; crossing fingers that things will go fine from here.
(My carrier is in my userinfo under my name, btw. )
Edit 'cause we keep posting at the same time: Hells yeah, I know how to flash, I've done it tons of times, just never run into this problem or had a device with so many variants so I'm just not used to asking so many questions, is all. I sincerely appreciate you guiding me through, and hope this will help others with this device in the future.

PushyPhoenix said:
And I believe you've just answered my question. I'll hold off on flashing kernel and modem but I did back up everything, just in case. Wiping/formatting now; crossing fingers that things will go fine from here.
(My carrier is in my userinfo under my name, btw. )
Edit 'cause we keep posting at the same time: Hells yeah, I know how to flash, I've done it tons of times, just never run into this problem or had a device with so many variants so I'm just not used to asking so many questions, is all. I sincerely appreciate you guiding me through, and hope this will help others with this device in the future.
Click to expand...
Click to collapse
cheers, if it does help you just try to give it back to the community.....i ve had similar issues and people here on xda helped me out. So i am doing the same.

FYI - It worked like a charm and now Lexie (I name my phones ) is up and running again almost like nothing happened. Thank goodness!
In case anyone else winds up needing them, I'm adding links to the stock firmware I downloaded.

att s5 wont factory reset,

hi so i have a sm-g900a that i put the twisted lollipop rom (android 5.0) on, my camera failed so a tried to reflash the rom and it bricked so i attemted to do a factory reset using odin but to no avail. it still shows custom on the boot screen and freezes.
im not good with this kind of stuff i hope i didnt really screw up these things are expensive lol. thanks in advance

how did you install the rom in the firstplace? did you use safestrap? The ATT S5 has a locked bootloader, so it's usually not so easy to install a custom rom.
Anyway, can you get into the recovery menu and do a factory reset?

mike-y said:
how did you install the rom in the firstplace? did you use safestrap? The ATT S5 has a locked bootloader, so it's usually not so easy to install a custom rom.
Anyway, can you get into the recovery menu and do a factory reset?
Click to expand...
Click to collapse
ya i used safestrap, ive tried to reset it from the recovery but it still freezes when it boots and still says that its custom at first start up

You'll have to download the stock rom from sammobile and flash it with Odin. Your phone definitely isn't bricked.

just tried that and its still doing the same thing. is it because it was updated to 5.0?

wouldnt clicking on repartion in odin reset everything?

bump, come on guys no ideas?

Swimguy14 said:
You'll have to download the stock rom from sammobile and flash it with Odin. Your phone definitely isn't bricked.
Click to expand...
Click to collapse
hey ive tried this method 5 times and its still freezing at the boot screen, idk what to do i really dont want to have to buy a new phone

Flash the PIT file at the same time as the stock ROM, with ODIN

*Detection* said:
Flash the PIT file at the same time as the stock ROM, with ODIN
Click to expand...
Click to collapse
thanks for the reply, so i just tried it and odin said :
nand write start!!
, fail! (auth),
,
complete(write) operation failed
im going to try downloading the firmwares elsewhere and see if it helps
btw nand erase all and re-partion were both checked

nevermind i got odin to work, i added the "bl" md5 and had to remove it since att has the boot loader locked (i have the feeling the bootloader somehow got altered and is causeing this problem) . so the phone is still doing the same thing i get the screen that says "galaxy s5 (showes a open lock) custom powered by android" then goes to the screen with the animated samsung boot image and freezes halveway though screen goes black and the blue led comes on even though it isnt pluged in

Bump

come on there must be something i can do. ive tried probably 20 times with odin doing the factory reset. im completely lost on what to do. could at&t do a full wipe and reflash?

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