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.
Related
I really screwed this one up guys. I was trying to upgrade to the new 4.3 TW based roms and accidentally installed all the knox stuff and all that, but I'm not really worried about the warranty.
What I am worried about though is that now, no matter what I try I get stuck in a boot loop. I have formatted my external SD card, reinstalled official CWM recovery, wiped everything more often than I can count and tried TW based roms, official ROM, AOSP based ROMs and nothing works. In most cases this is what happens after install:
1. The boot animation comes up
2. It actually boots
3. Then immediately force shutdowns
4. Boot loop
I have tried everything. I even tried just going back to stock ROM but I got an error in heimdall.
ERROR: Failed to open file "system.img.ext4"
Click to expand...
Click to collapse
Does anybody have any solutions for me. I feel like i've done every tutorial on the internet for 2 days now and I just don't know what to do!
Pesvardur said:
I really screwed this one up guys. I was trying to upgrade to the new 4.3 TW based roms and accidentally installed all the knox stuff and all that, but I'm not really worried about the warranty.
What I am worried about though is that now, no matter what I try I get stuck in a boot loop. I have forformattedmatted my external SD card, reinstalled official CWM recovery, wiped everything more often than I can count and tried TW based roms, official ROM, AOSP based ROMs and nothing works. In most cases this is what happens after install:
1. The boot animation comes up
2. It actually boots
3. Then immediately force shutdowns
4. Boot loop
I have tried everything. I even tried just going back to stock ROM but I got an error in heimdall.
Does anybody have any solutions for me. I feel like i've done every tutorial on the internet for 2 days now and I just don't know what to do!
Click to expand...
Click to collapse
Ok Bro I had same problem.
Facts: if your stock is 4.2 that's why you can't flash - 4.3 forbids downgrade. Try this http://forum.xda-developers.com/showthread.php?t=2250824 and find XXUEMJ7 - you should be able to flash it. Did it today - writing from phone
socah said:
Ok Bro I had same problem.
Facts: if your stock is 4.2 that's why you can't flash - 4.3 forbids downgrade. Try this http://forum.xda-developers.com/showthread.php?t=2250824 and find XXUEMJ7 - you should be able to flash it. Did it today - writing from phone
Click to expand...
Click to collapse
Ah, thing is I'm on Linux now and can't use ODIN . But are you saying my problem is that I'm trying to flash 4.3 roms, that I have to have 4.2.2 roms? Or vice versa? Also, I must have ****ed up even further because now I can't even print-pit in heimdall.
EDIT: Well anyway, I get home in about 3 hours and then I'll have a windows machine. I'll try it then. Will update when that's done.
Pesvardur said:
Ah, thing is I'm on Linux now and can't use ODIN . But are you saying my problem is that I'm trying to flash 4.3 roms, that I have to have 4.2.2 roms? Or vice versa? Also, I must have ****ed up even further because now I can't even print-pit in heimdall.
EDIT: Well anyway, I get home in about 3 hours and then I'll have a windows machine. I'll try it then. Will update when that's done.
Click to expand...
Click to collapse
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
socah said:
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
Click to expand...
Click to collapse
Ah but I've been trying exclusively to install 4.3 roms. But I haven't yet tried it on Odin.
socah said:
I was saying that you probably tried flash 4.2 rom on 4.3 rom you have on phone - which is impossible due to Knox lock that will not allow to downgrade. Just download 4.3 rom and flash it, heimdall could do the job too.
Click to expand...
Click to collapse
Well, thanks guy. Flashing the stock rom worked perfectly FROM ODIN. For some reason it just would not work on my Linux machine using Heimdall. But I feel like I tried this yesterday... although that was at like 3:30 am so I might have hallucinated it.
Anyway, you are a god and I hope for all the luck in the world to you.
Just a quick update: I found out the reason I was stuck in the boot animation and it crashing was in fact because the battery is faulty. I thought it was because flashing the ROMS wasn't working, but it was because the battery was shutting down at random intervals no matter what the charge
Sent from my GT-I9505 using Tapatalk
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
Hi,
I have reported this thread to be moved to the right Q & A section where you might be able to get help quickly.
Good luck.
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Primal instinct said:
ok heres the issue....im not sure what i did wrong. i flashed a rom and got boot looped, so i said what the heck and went to odin thinking id flash stock firmware back...i did and still bootloop, then i deleted dalvik cache...still boot loop...so i flashed twrps and tried reflashing new rom...still bootloop.....wtf... so i tried odin again...bootloop...i need to fix this asap...any help..obviously this is serious if i cant get the bootloop to stop. recovery and download mode are working so no hard brick.
Click to expand...
Click to collapse
what version are you from the start before you flashed? please provide complete information
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
ankahuja said:
Its easy as anything
Download your phones official firmware from sammobile.com
Flash through odin in pda/ap tab
Click to expand...
Click to collapse
well ive done that like 3 times and it still wont come out of bootloop. its as if the phones bricked...turns on then tries to start up but turns right back off. it sometimes goes as far as saying android is starting and optimizes a few apps and shuts off
kerbiii said:
what version are you from the start before you flashed? please provide complete information
Click to expand...
Click to collapse
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
Trying going back to a 5.0.1 firmware
N910PVPU3BOF5 ( I pulled that from N910P) Didn't remember Sprint model number.
So if I'm wrong find the correct model of sammobile and download 5.0.1.
See what that does. Bootloader should not be locked so it should be possible,
Primal instinct said:
I originally was on android 5.1.1 cog5 build for sprint...then went to cm 12.1 remix by sabermod....when i used odin to flash back to original firmware, it kept bootlooping. anything helps
Click to expand...
Click to collapse
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
I was on the correct firmware. but for some reason even if I use odin to flash newer firmware coj6 it still doesn't boot up.
kerbiii said:
what version where you trying to get back?? if its lower 5.1.1 it might be impossible for now since the new bootloader wont let you downgrade,, if not just try wipe cache and factory reset
Click to expand...
Click to collapse
update: i can use cyanogenmod for a few minutes but then it shuts off again. my sprint sim card is not readable which is wierd since its a sprint rom cog5 baseband. any ideas :crying::crying:
deroyabun said:
You flashed a custom rom?
well did you check the bootloader and modem?
example: your old firmwara was based on a coh4 and the new custom is based on coj3.. then you get bootloops.
In this case please download the fitting bl & modem to your rom!
Click to expand...
Click to collapse
i downloaded and installed the correct bootloader and modem but still no bueno. i got cyanogenmod for trltespr to work and boot up but sim card not readable and it shuts down after a few minutes. thats really wierd considering its a sprint based rom. any ideas
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
I don't think another battery will do anything. I think it is all software. I can flash CM11 btw, so you should try that. But my system is extremely unstable... it works... but is beyond frustrating. my smart watch wont work.. have to restart phone throughout day.... so many problems I cant even list them all.
---------- Post added at 08:29 PM ---------- Previous post was at 08:28 PM ----------
Chasef254 said:
Have you tried a new battery yet?
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
A battery? How in the world would that help? That makes no sense... no offense, just sounds like you are asking someone to unnecessarily to spend $$$ when it is clearly software.
I'm having the same problems and want to know if op has tried it so I'll know if it's been ruled out of the problem thats why. Ok so it's software. You have the solution. No offense.
Sent from my iPhone using Tapatalk
d0p3t said:
me too, i also have a bootloop for a couple of months now. tried literally every single combination of bootloaders/modems/kernels/ROMs . i can't even get into recovery, but can get into download mode.
do you guys think trying another battery may seriously help? how could a new battery help getting out of a bootloop if download and/or recovery mode work fine?
Click to expand...
Click to collapse
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
amongunz said:
I having a similar issue for a few months now. Nobody seems to have a clear answer. I am not a noob and have flashed back to factory a million times on other phones.. I have spent hours trying everything with no luck. Sprint store will not help... pretty frustrating. Let me know if you find a solution.
Click to expand...
Click to collapse
The only solution i can find is to replace the motherboard or replace phone all together.
Primal instinct said:
I think this is a samsung issue. I am going to try and see if i can replace motherboard bc thats the only logical option. I can remarkably download and run (for a few minutes) cm12.1 but my sprint sim card is unrecognized (wierdly). I dont think its the modem or bootloader....ill update yall if i find a fix. Thanks P.I
Click to expand...
Click to collapse
Were you able to get it fixed? I'm probably going to go to a phonerepair shop this weekend or next week and see what they say or can do.
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.
Hi
i rooted my g935f and installed a custom recovery, all went wel
then i installed custome firmware , after that by mistake i disabled oem lock,
my s7 won't boot up, w'ont enter in recovery mod and won't accept odin flashes,
i'm I fu"ked ????
:'(
nouninou said:
Hi
i rooted my g935f and installed a custom recovery, all went wel
then i installed custome firmware , after that by mistake i disabled oem lock,
my s7 won't boot up, w'ont enter in recovery mod and won't accept odin flashes,
i'm I fu"ked ????
:'(
Click to expand...
Click to collapse
You don't give a whole lot of information as to the processes you tried or "custom firmware " you installed or can you get to download mode.
More information is needed
"And on that bombshell!"
Sent from my Echoe powered AEL driven G935F
i can get into download mode but i can't flash rom via it
Going to try help you here best as I can.
I ran into the issue. And basically it's a lock that prevents you from doing anything due to your phone running a custom rom. I don't know what triggers it but it is a security feature to prevent someone flashing a custom rom to get easier access to your data (Think back to the whole FBI vs Apple saga)
What you have to do is flash a completely stock ROM with Odin. Phone wouldn't allow a ROM other than a Samsung signed ROM. What I did was download the Stock ROM from here: http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
Now I flashed all the different parts of the ROM with Odin and your phone in download mode. They should flash as this is a Stock ROM.
Sadly I don't know enough to know which ones you have to do as I just did them all and allowed me to use my phone again but did lose any data that was on the device.
I do not know enough about this stuff and what I have said is from my experience with the exact issue are describing on my S7 Edge. Really hope it helps.
tanka8 said:
Going to try help you here best as I can.
I ran into the issue. And basically it's a lock that prevents you from doing anything due to your phone running a custom rom. I don't know what triggers it but it is a security feature to prevent someone flashing a custom rom to get easier access to your data (Think back to the whole FBI vs Apple saga)
What you have to do is flash a completely stock ROM with Odin. Phone wouldn't allow a ROM other than a Samsung signed ROM. What I did was download the Stock ROM from here: http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
Now I flashed all the different parts of the ROM with Odin and your phone in download mode. They should flash as this is a Stock ROM.
Sadly I don't know enough to know which ones you have to do as I just did them all and allowed me to use my phone again but did lose any data that was on the device.
I do not know enough about this stuff and what I have said is from my experience with the exact issue are describing on my S7 Edge. Really hope it helps.
Click to expand...
Click to collapse
thank you mate, it actually worked for me, now i can start my phone, sadly all the data was deleted
thanks for your answer
nouninou said:
Hi
i rooted my g935f and installed a custom recovery, all went wel
then i installed custome firmware , after that by mistake i disabled oem lock,
my s7 won't boot up, w'ont enter in recovery mod and won't accept odin flashes,
i'm I fu"ked ????
:'(
Click to expand...
Click to collapse
bro just flash the original firmware and not twrp as it requires oem unlocking and if it still doesn't work then try to use an older version of odin or a newer version of it and check if ur files are up to date and not corrupt
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Picture added
Pic 1
5.1.1 is better than 5.0.1 in battery and performance. You should have jumped to 4.4.4. ?
I did. I used the OG2 from Sam mobile which was the rent a center note 4 and after a few days the camera failed. Then I flashed dynamic kat and while in a call I used action memo and the system ui FC even after a reset. 5.1.1 battery on all the roms I used (which was all ) still had bleeding battery. Just for the record, you can use DaRTHSTALKER v1 on 4.4.4, but not v2. V2 has the best battery on any Rom I've used to date that's why I chose to go back to 5.0.1, but your milage may very. So far my phone is sipping battery. Besides, you may be right but I did this for the option of choice, more roms to flash is always a good thing.
Hangoverr said:
5.1.1 is better than 5.0.1 in battery and performance. You should have jumped to 4.4.4.
Click to expand...
Click to collapse
g1-and-only said:
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Click to expand...
Click to collapse
1 tip for you.
Not just 5.0.1 You can flash kitkat 4.4.4 also with 5.1.1 bootloader/baseband
Flash any kitkat rom along with nadia kernel 4.4.4 and it will work flawlessly
https://mega.nz/#!accnkb6B!f_wdM79WXZ2UYy2El87DXYctihB40MBjV4imBKlhoDo
I didn't know that.
Would it be stock tmobile 4.4.4 or the rent a center one? After trying so many I was curious to see about going to 5.0.1 without any alt kernels, close to stock because of the battery drain that's plagued our N4 after the 6.0 updates. I know darthstalker uses a stock tmo kernel he just changed enforcing to permissive. Only on v2 does it work on 5.0.1 but v1 could be used on 4.4.4, but there was more done on the second version so that's why I've now flashed v2 of dstalker.
Trex888 said:
1 tip for you.
Not just 5.0.1 You can flash kitkat 4.4.4 also with 5.1.1 bootloader/baseband
Flash any kitkat rom along with nadia kernel 4.4.4 and it will work flawlessly
https://mega.nz/#!accnkb6B!f_wdM79WXZ2UYy2El87DXYctihB40MBjV4imBKlhoDo
Click to expand...
Click to collapse
Also works on 6.0.1 ?
But you can't use darthstalker on 6.0.1:victory:
noob4598 said:
Also works on 6.0.1
Click to expand...
Click to collapse
Still nothing for the t3?
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Click to expand...
Click to collapse
Because many users like me had issues with battery shutdown at 20% & random reboots with marshmallow .while on lollipop or kitkat doesn't happen.marshmallow is good and very well optimized but not good for note 4.
I was also on 6.0.1 and I followed your instructions. I flashed both the modem and kernel successfully. Darthstalker is installed, but my question is can I flash a stock tw rom with out issue. I want to sim unlock my phone but my octoplus box requires stock 5.1.1.
Yes, you can flash stock 5.1.1 though Odin.
gwest04 said:
I was also on 6.0.1 and I followed your instructions. I flashed both the modem and kernel successfully. Darthstalker is installed, but my question is can I flash a stock tw rom with out issue. I want to sim unlock my phone but my octoplus box requires stock 5.1.1.
Click to expand...
Click to collapse
This worked great on my n910t.
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
g1-and-only said:
Yes, you can flash stock 5.1.1 though Odin.
Click to expand...
Click to collapse
Well it worked. Ty for your work on this.
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Click to expand...
Click to collapse
Besides the random shutdowns, LP's multitasking was better. I don't recall exactly what now, but I remember being disappointed in the MM implementation of it. Can anyone comment on what LP multitasking had?
Flashing the 910T all the way back to ANIH (KitKat) has always been possible with Odin, as far as I know. I haven't experimented fully but I have jumped back and forth a couple of times from firmwares noted as "no way back" without problems. It's only if you insist on using .zips via recovery that problems arise.
It's the 910T3 that has problems even with Odin.
Quick question ... if im on qe2 6.0.1 will this work as well ? im rooted stock, unlocked for metro pcs it would be nice to load 4.4.4 on this i got just the rom for it lol
The Development section is for people to post their own original development work in compliance with the sticky titled "Rules for Posting in Development." Please do no share links to other people's work in that section.
THREAD MOVED
g1-and-only said:
Hello, merry Christmas and happy new year as I'm so proud to bring to you all a way to downgrade to 5.0.1 even if you have updated to the new pk firmware. I'm sorry to say that this obviously only works on the 910T model. I could go into a long story about how I've been rooting and roming since the g1 but i wont, instead ill get right into the good stuff. To downgrade flash odin 5.1.1,( im not sure if you even have to do this part but it doesn't hurt) boot up, set up, root it by flashing recovery (TWRP), make sure you unselect auto reboot from odin. after the flash is complete pull the battery, place back in after 30 sec and hold up on the volume, home button, and power. In odin (before you do the following make sure to wipe everything 3x times in recovery and reboot back into recovery then reboot to download mode) flash the following, in BL slot flash the COD6 kernel, and in the CP slot flash COD6 modem. All will pass. Now I didn't boot up, i pulled the battery again and booted to recovery which will still be TWRP, now i did a factory reset and then flashed DaRTHSTALKER v2 and rebooted not expecting it to boot but to my surprise it did and for the last 1hour its been running perfect
I will have some snap shots that I'll be uploading in the next few minutes.
Here are the links for COD6
http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2902574
Click to expand...
Click to collapse
Ok so, as it turns out, my device is apparently an ACTUAL 910T3. DOK2 T3 ROM still fails, but this time it gave the normal "fused 3>binary 1" error that youre supposed to get if you try to downgrade BL's. Progress. Now, lets see if i can get a T3 DOK2/DOG1 kernel/modem to crack this baby open. Anyone know where i can find TWRP flashable kernel/modem of that sort?
Edit: Use the COD kernel for the BL slot. Download the DOK2 T3 ROM from https://forum.xda-developers.com/no...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 Open the md5 file in winrar. Extract the modem.bin to a folder. Flash modem.bin in TWRP (I used 3.09). Make sure "auto reboot" is unchecked. Wait 10-15 seconds after TWRP says "reset." Pull battery. Flash a 5.1.1 T3 compatible ROM (I used a backup of TEKxodus with the rage 1.8 ZL kernel, ymmv) then flash a DOK2 kernel like https://forum.xda-developers.com/no...t/kernel-beastmode-stock-1-0b-n910t3-t3238775
Looks like data will work with this setup, but wifi does not. Cant get wifi to work on any ROM at all besides MM ones. If you can live without wifi, it looks like T3 users will be just fine. If you cant ... well youre stuck with MM for now. Cause Wifi wont work if your BL and modem versions dont match (and MM modem apparently doesnt like LP which isnt surprising). I found a DOK2 T3 kernel, and it did nothing to crack this thing open. Odin failed to flash it. Looks like simple solutions are out. Unless i missed something etremely obvious.
Araltd said:
I've been running 601, several note 7 ports and the battery has been very respectable. Why go back?
Sent from my Samsung Note 6
Click to expand...
Click to collapse
Im getting great battery life on Max overdrive edge 7 port on 6.0.1