Database Users

[Q] "Downloading.... Do not turn off target!" after TWRP

Can I get a little help here? I have a rooted, otherwise stock i337 that I just used the TWRP root app. I wanted to make a backup of my phone before I flashed a new rom. It downloaded jflteatt and I verified and installed it to /dev/block/mmcblk0p21. then i tried to make a backup, and i'm stuck at "Downloading.... do not turn off target!!!" In the upper left corner there's a "Could not do normal boot. ODIN Mode.
I found the post "[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3" but am hesitant to use it, as I am not sure that is what I need to do. I also found some other similar posts, but for different devices so I am again hesitant to rely on those.
I tried pressing home, power and volume down, but it just resets back to this screen. Also, I originally posted this request on the TWRP page, but I think it should be here. If so, I will delete it there.
Please help?

@kamikazees
If you could give more detail that would also help other to help u....such as what firmware that u are running before bricked...... well seem to me that u are either MF3 or MK2 firmware and u installed TWRP ...... u can only install safestrap recovery if u are on MF3 or MK2 firmware. ....Follow my thread http://forum.xda-developers.com/showthread.php?t=2621279 it should get u back to MK2 firmware. .....goodluck
Swyped From MK2 Dark Venom SS Edition

Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.

kamikazees said:
Thank you for the quick response. I have a small update since my first post. I found a poster in another section who got his phone rebooted by trying to send it to download mode, then cancelling out. I did that (pressing power, home and vol down), then when the phone "buzzed" I let off those keys and pressed them again. The phone rebooted, apparently normally.
So now I can check my firmware. Checking firmware is on the "baseband version" right? If so, then that info on my phone is I337UCUEMK2," which I guess is the MK2 firmware.
I deleted the TWRP app, but I'm not sure now if I've even got a recovery (if TWRP failed to install, maybe I'm still on stock?). Do I need to go ahead do the full ODIN tar file unbrick from where I am now? The phone appears to be operating normally.
If not, should I just go ahead and install safestrap recovery? I am trying to eventually get rid of all the bloated samsung junk and get to CM or another ROM. The S4 seems a bit more touchy than some of my previous phones.
Click to expand...
Click to collapse
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.

DeadlySin9 said:
Your stock recovery is probably broken, and so it would be best to at least reflash the stock recovery. However, you should be just fine if you want to only install Safestrap and leave recovery broken. I just wouldn't recommend that.
Click to expand...
Click to collapse
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.

kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
The first one is in img format and won't work through ODIN, but you can use those commands from terminal emulator to flash it if you download it. Otherwise, the TAR files do work just fine.

kamikazees said:
Ok, I want to fix the recovery. Can I use ODIN for that? One post I found said I cannot: http://forum.xda-developers.com/showthread.php?t=2576291. It was several months ago, however, so I am not sure if it still holds true.
If I can use ODIN, I see that the stock recovery file is in ted77usa's post #3: http://forum.xda-developers.com/showthread.php?t=2621279. After putting my phone in download mode and connecting it to ODIN, in which slot would I put that file? Some older posts say to put it in the PDA slot, which appears to be the AP slot.
Thanks for your patience. I really don't want to mess this up again.
Click to expand...
Click to collapse
If you are rooted and can actually boot the phone then I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery. I've been using Safestrap and TWRP since I was on MF3. I have also successfully flashed the tar files through Odin to get to MK2 with no problems. If you are rooted then its a really good idea to use Safestrap with TWRP for a recovery. Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable. The stock recovery on this phone is pretty much useless.

megamanDJ said:
...I would install Safestrap for MK2 and install TWRP 3.71 to use as the recovery... Afterward you can find a list of compatible roms that are specific for Touchwiz on MK2 that for the most part are pretty stable.
Click to expand...
Click to collapse
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!

kamikazees said:
This is exactly what I did. I flashed the stock recovery in Odin (yes, it goes in the AP slot), which fixed my first problem. Then I installed Safestrap, then made a ROM slot and installed Goldeneye v. 21 (the 4.3 version for MK2). That removed all of the AT&T bloat (yay), and I did not have to flash the MK2 kernel (which I think would also have gone in the AP slot) because it has it already.
Then I flashed the GE add-on that removed a bunch of Samsung bloat (yay #2). Rebooted and turned off the rest of the Samsung stuff I didn't want. Got the phone up and running beautifully.
What a picky phone! The locked bootloader really causes a lot of trouble to inexperienced flashers like me. I unfortunately have about 5gb of "wasted" space because I understand I cannot flash over the "stock" rom, but I am at least running another ROM that I chose. My phone, my choice. Shame on Samsung!
Thank you very much!
Click to expand...
Click to collapse
There is actually a way to flash a rom to the stock slot, but I haven't done it. Somewhere in the Safestrap threads explains how to do it. I think you can even get it back to normal if you change your mind.

[Q] Note 3 error message while trying to flash stock firmware.

This was the first time ever trying to flash a rom onto a note 3. I downloaded safestrap and installed it, made a back up of my current stock rooted firmware and tried to flash cynogenmod 11 with gapps 4.3. It sent me into a bootloop. i panicked.... I booted back up into recovery and quickly wipe/factory reset. Now my safestrap was gone. So i downloaded what i believe was the stock firmware for my phone and tried to flash through odin but i kept getting an error message that said fused 3 binary 1. I have spent more then 24 hours checking the depths of the internet trying to find the solution to the problem. i will never try to flash anything ever again. This is my last ditch effort. Any help will be greatly appreciated. Please forgive me if this is not in the right place, I RARELY post on here. Thanks everyone.

fused 3: you have kitkat installed
binary 1: Bootloader failed Software Revision Check
usually this error comes when you're trying to downgrade or the flash is corrupt. check your android version and make sure root is good.

Dravekx said:
fused 3: you have kitkat installed
binary 1: Bootloader failed Software Revision Check
usually this error comes when you're trying to downgrade or the flash is corrupt. check your android version and make sure root is good.
Click to expand...
Click to collapse
i cant check the android version my phone doesnt boot up past the Samsung screen.

dylancam90 said:
i cant check the android version my phone doesnt boot up past the Samsung screen.
Click to expand...
Click to collapse
You're going to have to get the latest then, at least 4.4.4 and flash via Odin. You can NOT flash full ROMs except Verizon ROMs on the verizon note 3. Its bootloader is locked and can't be unlocked so only official kernels can be loaded.
Sent from my Note 3 via Tapatalk

donc113 said:
You're going to have to get the latest then, at least 4.4.4 and flash via Odin. You can NOT flash full ROMs except Verizon ROMs on the verizon note 3. Its bootloader is locked and can't be unlocked so only official kernels can be loaded.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
ok i will flash 4.4.4 and report back

dylancam90 said:
ok i will flash 4.4.4 and report back
Click to expand...
Click to collapse
Don't get 4.4.4 if you go there there is no root and no way back you can check the bootloader and android version by going into download mode if you are very lucky you will have nc4. If your on nc4 or earlier you can root. If your on new your at the mercy of some dev finding root on a 2 year old device I'm not saying development is dead on the note 3 but it certainly does not have the life it had.

mirrin said:
Don't get 4.4.4 if you go there there is no root and no way back you can check the bootloader and android version by going into download mode if you are very lucky you will have nc4. If your on nc4 or earlier you can root. If your on new your at the mercy of some dev finding root on a 2 year old device I'm not saying development is dead on the note 3 but it certainly does not have the life it had.
Click to expand...
Click to collapse
I just want to update this so if anyone else stumbles upon it they can have some closure. I flashed 4.4.2 but I payed attention to the build number and was almost positive it was NC4 build. Odin took it and it tooke about 10 minutes to download and install, then it booted me to the Verizon screen and it just froze there. So I flahed the NC4 kernel thinking I might have made the mistake of flashing the NC2 kernel and it finally booted up completely and I was able to use my phone again. Also I took your advice by not flashing 4.4.4. I wanted to though because I was sick of getting update reminders every hour, so I figured out if you freeze SDM 1.0 the reminders stop. So thank you for all the help.
Sent from my SM-N900V using XDA Free mobile app

softbricked.. sorta note 3, need help.. 4.4.4 ROM and BL, on n900w8, need to install

So, first,
Thanks all in advance.. You are amazing.. I, and so many others have learnt so much from you and your support.
Now,
I have a Canadian n900w8
http://www.mrcrab.net/viewstockrom/10688-sm-n900w8.html
I was so happy at that ROM,and was playing around.. Learning.. And ran into problems..
I made a stupid mistake, really.. Now I don't know how to get out..
I installed a 4.4.4 boot loader.. And flashed with Phil's, back to my 4.4.2 fine, was testing.. So ten I tried a 4.4.4 ROM, and the boot loader.. Worked.. And then some how I lost my recovery, now no matter what I do I can't get a recovery to load.. I have the ROM working, except the modem does work.. Its rooted.. And I can flash a little with flashify, or Odin.. But there are only att2 recoveries.. For 4.4.4 and any TLS recoveries are for 4.4.2..
Any help would be appreciated.. Thanks all in advance..
I already know I'm a noon, no sence reminding me, that's why I'm here..

as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..

GhostCyber said:
as far as i know i can still odin back to my normal firmware,
is that correct?
it's been 3 days, i've been trying to download the right one, but most of the mirrors are brokens..
I'm currently Downloading at 35k from one.. so if it's just that simple,
I'll post back so people know..
There seems to be allot of confusion about bootloaders...
as far as i understand though, the one i flashed witih wasn't locked, so..
I think I can still odin to stock..
Click to expand...
Click to collapse
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.

Thanks.
Joku1981 said:
1. Download and unzip the latest firmware for your device: HERE.
2. Remember untick autoreboot in ODIN. Wait till the flash finish. Reboot your device in Recovery Mode and Wipe data/Factory reset your device. Reboot now normally.
3. Install this APPhttps://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en and take a look the part that tells "BOOTLOADER" for clarify things then.
Click to expand...
Click to collapse
Thanks,
Like I said I have been trying to do that, but i apreciate you conferming it will work..
unfortunately, samMobile has just broken links to the rom...
I'm on my forth attempt, downloading froma source with 45k...
Why sammobiles got broken dl's I don't know, but it really has made this experience draw out.
Thanks Again,
Peace.

thanks man. everything worked out, thanks for the reassurances, bricked stuff is scary...
for everyone else with a telus note...
i spent 3 days trackingn the stock firmware, so i'm uploading it to a site, and will post it here sometime soon..

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