[SOLVED] Cannot flash bootloader or modem/baseband (won't stick!) - Galaxy Note 3 Q&A, Help & Troubleshooting

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.

Related

[Q] WiFi not working after update via Kies from 4.3. to 4.4.2

Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
SDA1979 said:
Hi there,
i have a rooted S4 i9505 with cwm installed.
yesterday i did an update from stock rom 4.3 to 4.4.2 (I9505XXUEMKE) via KIES.
the problem now....I cant turn on the wifi anymore. whenever i try to use the on/off switch for the wifi it instandly switches back to off.
is anyone else experiencing the same problem? has someone already a solution for that, before i will do a factory reset.
Click to expand...
Click to collapse
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
Its correct
SDA1979 said:
ok just to be sure and not bricking my phone..
i went into download mode and it says:
odin mode
product name gt-i9505
current binary custom
system status official
knox kernel lock 0x0
knox warranty void 0x1csb-config-lsb 0x30
write protection enabled
eMMC burst mode enabled
now if i understood right, i have to download
Wifi fix/NON-HLOS - I9505_XXUFNB8_WiFi_FIX
and flash it with odin with the instruction above....
is that correct?
i also found XXUFNB8.... should i rather use this one?
Click to expand...
Click to collapse
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Jimsilver73 said:
you are on the new bootloader so you can flash the complete package - it has everything in it all in one package! - you won't brick your phone even if you flash the wrong modem, that is unless you did some thing real dumb like flash i9500 modem and even then I think its recoverable not that I suggest you try!!
depends where you are in the world - I used NB8 and it worked well for me in the UK - I'm on NB9 now and that seems nice also.
so to be clear flash this:
Combined package
For NewBootloader
GSM_Modem_XXUFNB8_and_LTE_Modem_XXUFNB8
https://mega.co.nz/#!3dR30JiT!cP5WrUCfz9L4h8doY7KTTV6fq4pFL85EkJBG6T-Gqhc
Click to expand...
Click to collapse
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
SDA1979 said:
hey guys, thank you!!!
the Wi-Fi is working again.
Nonetheless i still have one problem remaining, which i thought it would have been fixed as well.
but, when GPS is turned on, it tries to find the GPS position and the icon on the status bar continues appearing and disappearing permanently (every half of a second).
Beside the fact that it is really annoying having this icon flashing all the time it also causes the display to freeze.
Especially when scrolling from top to the bottom to open the notification area.
It sometimes also lets the system crush completely.
any idea what this could be?
thanks for your effort so far.
Click to expand...
Click to collapse
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
EDIT: don't wipe system unless you planning flashing a different ROM through recovery!
Jimsilver73 said:
hmmm......... thats not right!
Suggest you find a stock sammy ROM and flash anew in odin - then root using cf root, then flash recovery - (TWRP is very good :good then go into recovery and wipe cache, dalvik, system and data - reboot and see what happens on nice new shiny sammy stock - if all is good pick the ROM/kernel you want (if you want) and go back to odin to reflash modem.
The only other thing I can think is that you have an app that is messing with gps?? Do the above though and you should be golden :good:
Click to expand...
Click to collapse
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
speedwayfan75 said:
Hi, right way to flash the stock Samsung package, but after flashing a custom recovery, do not wipe system. There's no ROM after that so phone will not boot. And the newest modem is integrated in the stock package, so no need to flash it again.
And another advice: NEVER use Kies to update your phone. It has bricked 3 of mines.:cyclops:
Click to expand...
Click to collapse
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Jimsilver73 said:
Oops, well spotted! Yes, don't wipe system unless you have another ROM to flash through recovery. 3 phones bricked from kies huh? I never used it SVD don't think I ever will lol. Good old Sammy stock stuff, tbh that's why I steer well clear of anything stock Sammy unless absolutely necessary and last resort - I look at the farce they have made by forcing us to accept Knox pox!
Click to expand...
Click to collapse
my thought was to go into recovery mode and wipe everything and start from beginning in order to exclude that it could depends on some wrong settings or any software already installed....
I updated to 4.4.2 using Mobile Odin and my wifi was borked too.
I did notice after the update that there was a mismatch between my Baseband version (still the old 4.3 XXUEMKE) and the Build number XXUFNB8, and I recall seeing some message during the flashing process that security had blocked the kernel update and Triangle Away might help solve it.
I therefore ran Triangle Away to reset my flash counter, and then used Mobile Odin to have a second go at flashing just the Kernel, Recovery and Modem parts.
This was successful and I now have matching Baseband and Build, both XXUFNB8.
And my wifi now works again...
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
SDA1979 said:
ok.. after making a factory reset wifi and gps are working fine again.
guess there was some missconfigured third party app...
but now, with a fresh system i do not understand why i am not able to assign a PIN for my lockscreen...
everything is greyed out except PIN and Password.
but even though setting up a PIN, the screen lock is always set to use Swipe......
damn, i shouldnt have updated to 4.4.2.... until now.. only problems with this new build....
Click to expand...
Click to collapse
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Jimsilver73 said:
Try slimkat 3.2 from here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/909-jfltexx remember to download gapps and flash after you have flashed ROM. You won't be disappointed
Click to expand...
Click to collapse
hey thanks for your suggestion. but i want to keep using the stock rom. sufficent for my needs....
anyway.. finally i was able to get everything working after flashing the rom with odin again.
Jimsilver73 said:
hmm - shouldn't really be a problem if you flashed stock, but broken wifi is a symptom reported when flashing old modem on new bootloader, if you have new stock sammy 4.4 then you will surely have new bootloader (check though by putting your phone into download mode and then check for KNOX references - if you got them you got new bootloader, if no then you are on the old one)
Click on the link in my sig for modem - that will take you to a thread that has all the newest modems - have a look through the most recent last 3-4 pages and you will find packages for modems for new bootloader, flash one of these and see what happens - BTW you need to flash in odin with 'reboot' unchecked, then when its finished power off your phone manually then put back into download mode and flash again, then repeat the procedure but this time tick 'reboot' and that should be done. BTW - the tar file goes into 'phone' not csc. You may need to unzip the modem package to get the tar file.
Let us know how you got on
Click to expand...
Click to collapse
I feel compelled to express my gratitude for the post. Two days ago i updated from 4.3 to 4.4.2 on my rooted gt-i9505 via KIES and just like that no more wifi. This solution works like charm!!!
:good::good::good::good::good::good:

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

Flashing custom COJ5 firmware to 910C

Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
kurkovda said:
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
Click to expand...
Click to collapse
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
http://forum.xda-developers.com/note-4/development/n910c-spacex-kernel-v0-1-auto-root-t3192875
http://forum.xda-developers.com/note-4/development/kernel-suemax-kernel-lite-v1-0-t3221865
dicksteele said:
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
Click to expand...
Click to collapse
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
kurkovda said:
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
Click to expand...
Click to collapse
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
kurkovda said:
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
Click to expand...
Click to collapse
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
dicksteele said:
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
Click to expand...
Click to collapse
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
kurkovda said:
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
Click to expand...
Click to collapse
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
kakkooran said:
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
Click to expand...
Click to collapse
Will be able to try this out later this evening, thanks!
kurkovda said:
Will be able to try this out later this evening, thanks!
Click to expand...
Click to collapse
I'm not sure what that will accomplish. The bootloader gets flashed during the stock ROM install I posted.
That's the sboot.bin file that gets flashed in ODIN not the boot.img that is the kernel with TWRP. Big difference.
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
HalloSpencer said:
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
Click to expand...
Click to collapse
I'm not sure you are speaking about MY problem
Flashing by ODIN causes no problem, they start after flashing ane custom COJ5 ROM via TWRP.
And I use "hardware" method every time I need to get to ODIN mode
Just wanted to make clear that you flashed COJ5 bootloader using "hardware method".... I actualy cant remeber were I read that flashing otherwise can cause problems (without odin failure)....
And yes I was speaking about your problem
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
They did
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
The bootloader was not the issue in this thread. It was flashing ROMs.
Samsung obviously realized we had way to much freedom our phones and has tightened down the sboot.bin (COJ5 bootloader file)
You will notice in your ODIN flashes when trying to downgrade, that's the file it barfs on.
Which surprises me, that why I bought the 910C to get away from the locked down crap from ATT.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
kurkovda said:
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Click to expand...
Click to collapse
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
kurkovda said:
They did
Click to expand...
Click to collapse
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
dicksteele said:
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
Click to expand...
Click to collapse
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
kurkovda said:
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
Click to expand...
Click to collapse
All the ROMs work great, and there's great support. It all depends on what you looking for in a ROM.
I think there's a little too much expectation from people that think jamming (porting) features from other phones (N5 and S6) is supposed to work perfectly on a Note 4.
A lot of work goes into trying to make it work. But if they want the features that are on that phone to work perfectly, buy that phone.
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
amidsal said:
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
Click to expand...
Click to collapse
I have read someone suggesting doing a NAND ERASE ALL in ODIN during the firmware flash. That should wipe the hell out of everything.
I'm waiting to hear back if he's done that on the OJ5 bootloader.
I've had my phone from a month, I'm not willing to take that chance yet.

Huh, i really bricked it! (SM-910F, endless recovery loop)

Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Rajada said:
try to flash only the stock recovery.
If it fails, flash the last stock with pit file + factory reset on recovey, if wou're again in bootloop
Click to expand...
Click to collapse
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
iRoNX said:
I did the same thing on my note 10.1
"your partition is corrupt. Would you like to factory reset your device?"
it is still here in bootloop..
Click to expand...
Click to collapse
How do you know the partition is corrupt? I think i already did a factory reset by repartitioning with the pit file. Corrupt partitions i tried to fix by nand erase in combination with repartitioning... this did not help.
I have the same problem, only problem I got some text with red+blue+yellow color, what I did was flash a stock ROM ( SAME ROM I HAD BEFORE ROOT FAIL) and it worked (like)
rionline said:
Do you have a recent stock recovery flashible with odin or do you know where to find?
I did flash the recent stock with pit files/repartitioning,...does not help.
Click to expand...
Click to collapse
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Rajada said:
any flagship Samsung is bricked if you can get into download mode.
if you want to try, above you have the recovery from the last S1CPC1, flash it at odin:
Click to expand...
Click to collapse
thank you very much. i do not understand your first sentence......btw. i can get into download mode...(just if you meant "can not")
Update: I have virtually flashed every rom > 5.0. No success, no difference. Everytime the odin flash procedure is successful (in all variants, with pit, with nand erase, etc...), but the phone loops everything (normal start, recovery) besides the bootloader.
only new thing i noticed: allthough binary status is official, the device status is and stays custom not matter what i flash.
anyone? anything?
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
sunniebeta said:
Did you try to flash the stock recovery yet?
Also, what did you exactly flash to cause this?
Click to expand...
Click to collapse
yes i tried stock recovery already. not sure what caused this. i do remember that i had some problems with 4.8 debloated and then i wanted to flash the hole corresponding stock package as clean base. somewhere in the middle this happenend. i am not quite sure, but maybe, maybe flashed cf-autoroot to this march update. but i am not sure if this was before, after or initially.
however,...what really bothers me, is that there is absolutely no indiciation for an error during the flash process. odin and kies, everything completes just fine, just booting does not work. that's why i fear, that this is just an ugly coincident and the problem is caused by some failing hardware.
maybe and immensly undclocked kernel (odin flashable) could start my phone. because something is still working, when the bootloader and the nand writing is working just fine.
does anybody know how to get a really granpa speedy kernel, or how to make it?
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Used to happen to me all the time. What I used to do was, after flashing the rom, connected it again to odin, flashed the cwm recovery 5-6 times and then used to give it a try. Also ,after trying this, flash the bootloader-modem file and pretty sure your phone will boot(This is optional)
rionline said:
Hi folks,
i have had many devices and virtually customized every one. Now i have really done it, i bricked my phone.
I did happily flash the new march updates for the 910F, some dr. ketan, just the usal stuff. However, now my phone boot loops in and out recovery. To be precise, it starts after successfully flashing with odin (does not matter if repartition with pid files or full nand erase...):
- it tries to enter recovery (blue text at the top)
- it fails (nothing happens), then it goes black, it vibrates two times and
- restarts with trying to enter recovery (endless loop)
No getting out. Removing battery and starting normal does not work.
Download mode and flashing via Odin and Kies "does" work, but changes nothing....
Does anyone have ever had similiar issues and or fixed this?
All thoughts are welcome.
Greetings from germany...
Click to expand...
Click to collapse
Greetings from Hamburg ☺
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
android freek said:
Greetings from Hamburg
I was having also huge bug with dr.ketan rom at first was working flawlessly and 1 month later my phone wouldn't charge at all or recognise any charging cable.
Good thing is you can enter download mode (odin )
That means your phone is only soft bricked.
Flash SM-910F pit file + Latest stock firmware in odin mode all together in 1 flashing process...dont forget to mark repatriation in odin when using pit file.
When you got pass on odin and phone reboot and you see Samsung logo...fast take battery out and wait 1 min , put battery back and hold combo to enter stock recovery and do factory reset.
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks guys. I tried yesterday some stuff, nothing was working and i finally got it dead as a stone! Nothing was working anymore. However, i took it to the samsung service center. They were irritated, that they can't get it on at all! ... However, i am curious, how they handle it and how much they want for a repair attempt/or replacement.
Just for info. I did all the things you proposed. Nothing worked. I think this was just a coincidental hardware failing. If you flash all the time, there is a chance that you do it, while something is dying!?
i keep you updated! Thanks for now...
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
ithehappy said:
Corrupted eMMC? Probably! Please let us know what the service centre said ultimately and how much they charged you.
Click to expand...
Click to collapse
So i am back with a fresh note 4 mainboard. they changed it no questions asked, no fee, no problems. i like!

What firmware files do I need to complete reflash my Note 4 SM-N910F?

I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.
nekrosmsk said:
I got a bricked Samsung Galaxy Note 4 (910F) vodafone branded.
it's totally broken I can't start it, can't go into recovery (the hardware buttons are OK).
I can only go into download mode.
tried flashing everything with odin back to stock. followed many different instructions and now I'm lost.
can someone tell me what exact files I need?
I think I have the right firmware downloaded BUT what about the bootloader? on sammobile under germany-vodafone there are so many different versions which one shall I choose?
AND: Do I need CSC? if so which one and where to find? Couldn't find it on sammobile.
And am I right with putting the bootloader under BL, the firmware under AP, the CP (whatever this is) under CP, the csc under csc?
repartition unchecked as I read somewhere.
I still don't understand what this "pit" file is for and I'm not sure if I have the right one.. never had a phone with sooo many different firmware files..
I'm used to flash via fastboot "recovery.img, boot.img, system.img" odin is a new thing for me
HELP PLEASEEE :'(
the reactivation lock is on.
Click to expand...
Click to collapse
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip
aaron74 said:
I believe it should still flash with lock. If it isn't flashing something is wrong.
If you can't get Odin to flash that firmware try this and see what happens.
Download TWRP and flash it. Can you boot into recovery then? If so download a custom rom and flash it and see what happens.
TWRP: https://eu.dl.twrp.me/trlte/twrp-3.2.1-0-trlte.img.tar
Do you have Samsung drivers installed on PC? http://developer.samsung.com/common/download/check.do?actId=698
Do you have a good Odin? https://dl.sammobile.com/Odin3-v3.13.1.zip
Click to expand...
Click to collapse
I have the right latest samsung drivers installed yes.
I have the Odin version you just sent a link of. ( I also tried different older versions but no success).
I can't boot into recovery doesn't work. the hardware buttons are 100% working as I have to press vol+ to confirm to go into download mode.
I tried flashing TWRP and CWM both didn't work "custom recovery blocked by A/L error".
I can successfully flash firmware with Odin. It says "PASS" and then the phone reboots and is stuck on Samsung Logo. and sometimes it just shows blue text "recovery booting" but is stuck. nothing happens.
nekrosmsk said:
This reactivation lock doesn't matter I found a solution how to bypass it when the phone is set up running android.
my question is, is it possible to flash firmware to the note4 at all with reactivation lock on? Or is that just an android thingy?
And yes please that would be nice if you show me the right firmware.
My model:
N910F GSMH
I believe it is vodafone branded because when it once worked it showed a vodafone logo while starting up.
my country is Germany.
I hope thats enough info :/
Click to expand...
Click to collapse
Hey sorry the link you've sent doesn't work :/
aaron74 said:
The note 4 firmware is usually only 1 file that contains all you need. It contains the bootloader and CSC that you pick during download. Just pick the CSC for your country.
This is unless you get a 4 file repair firmware, which contains separate bootloader, system, and CSC files.
The pit file is only needed to repartition your device.
But with all off that aside, you state that your activation lock is activated. These means the phone was password protected.
If you tell me your country, I can at least point you to the correct firmware. So at least you'll know you got the correct one.
But as far as the activation lock, I can't help with that. "Google"
Edit. I now see you mentioned Germany Voda.
So here's the most current firmware for your device.
https://fws03.updato.com/GALAXYNOTE4/SM-N910F/TCL/SM-N910F_1_20171228192640_l5rw6mqv67.zip
Download and unzip.
Then if it's just 1 file that's .md5 then you put it in AP slot.
If it's 4 files put them in appropriate slots.
Click to expand...
Click to collapse
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?
nekrosmsk said:
hey thanks in advance, but this link doesnt work it says "hotlinking is not cool". anyways I searched the firmware for my model number on this site and applied the "germany vodafone" filter. but there are still soo many different entries which one shall I choose? The latest date?
Click to expand...
Click to collapse
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.
aaron74 said:
Here's webpage
https://updato.com/firmware-archive-select-model?record=58770125168D11E89F15FA163EE8F90B
After you flash, how long are you waiting for it to boot?
Sometimes it takes awhile.
Click to expand...
Click to collapse
Thanks for the link I'm downloading.
After flashing odin says PASS and my note 4 reboots. then there are 2 cases which in my view appear randomly. Either it shows the samsung logo and is stuck.
OR it shows the samsung logo and a blue little text in the upper left corner saying "recovery booting" and is stuck. I waited like 5 minutes. shall I wait longer? :/ hm..I'll try
OH and sometimes the screen just goes black idk if it really turns off after getting stuck on samsung logo.
Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other
stylemessiah said:
Pull the battery, leave it out for 10+ minutes
Put battery back in
Boot to download mode (Power + Vol Down + Home)
Then try (re)flashing stock ROM via odin, i would try the earliest you can find to have the best chance, you can always flash a later one if you get it running
Better range of ROMS from sammobile, i never use updato for that reason: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910F/VD2/
If none of that works, then its likely you have a hardware fault ...emmc or other
Click to expand...
Click to collapse
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.
w41ru5 said:
Try the Samsung Smart Switch for PC - like this : https://www.youtube.com/watch?v=9QhJngOuLQ4&t=337s
Good luck, maybe it will work - for me it did work for the 910C.
Click to expand...
Click to collapse
doesnt work. I tried several versions of smartswitch AND samsung kies. nothing works it always says my model is not supported. I reinstalled drivers. tried on another pc. tried another usb port. yes I'm using the original stock usb cable. model not supported. But I've also read that in other threads that the 910F model seems to be unknown by kies or smartswitch. I'm rly starting to hate samsung now. I have never ever had so many problems with flashing and so on.
nekrosmsk said:
So I tried flashing. after flashing OH WONDER it said recovery booting and then it showed this green android logo thing with a rotating icon in it "you know what I mean" but then it stopped and just turned off.. I could freak out really.. I tried flashing again. same issue. I could then press the recovery mode key combo to get into this rotating android logo screen but everytime it just freezes and turns off. yes the battery is fully charged before I started flashing this firmware now. I flashed the one u said the earliest. So Now I tried the one the other guy here showed me. didn't work either. it just gets stuck at samsung logo. I found a repair firmware for my model containing (pit, bl, ap, cp, csc and odin) I flashed all but odin fails "write error". I then tried odin v3.0.7 but then it got stuck while flashing the system image. I waited like 1 hour. nothing. tried it again. nothing it freezes on the same position. I then tried the same on the latest versions of odin v3.12.3, 3.12.7 and on 3.13.1 but it also freezes on system.img.ext4 image flashing..
Click to expand...
Click to collapse
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...
stylemessiah said:
afaik the "repair" fimeware is no better than flashing a stock ROM in one file...
its startng to sound like a hardware error, if it cant even write to the dvice theres really not many (probably any) options left.
ive purposely bricked a phone and recovered it (not recommended of course), ive never had or never saw as much effort youve put in to try and recover a phone...
Click to expand...
Click to collapse
me neither.. can't believe this.. how can a phone be physically damaged by flashing? paid 70 bugs for a note 4 with a software issue.. as I often do. recovered dead phones from sony, xiaomi, wiko, asus, lg, huawei etc... adb, fastboot and u good to go. odin is killin me.. gonna sell it as bricked.
Cleared caches?
R0B3RTF1SH3R said:
Cleared caches?
Click to expand...
Click to collapse
HOW? If I can't boot into recovery mode?

Categories

Resources