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
Related
Hi all,
After a looong night flashing and downloading again and again trying different methods, I'm out of ideas.
I have a uk n9005 (btu) that was happily running out of the box 4.3 stock until yesterday night. No root, no flash attempts before.
I started by flashing german 4.4 (dbt) without wiping before (big mistake, maybe) and without pit file and no repartition nor bootloader update checked. The error came out and I flashed again with the pit file. I let the phone reboot, but it didn't go further than the boot animation. I take out the battery and boot in the recovery. That is when I saw the can't mount \data error for the first time.
I tried to wipe, although it was impossible since the data was not mounted. However I could (and still can) wipe cache. I restarted the phone, and again the same situation, stuck in boot animation. From this moment I've tried many things:
- Flashing the bootloader separately and then the rom. no results (data not mounted and stuck in boot animation)
- Flashing custom recovery and after, official cm11 nightly and another cm11 based rom. no results (data not mounted and stuck in boot animation)
- Downgrading to 4.3. Not possible. Thank you Samsung!
- Firmware recovery with kies 3.0. no results since 4.4 has not been released for my region (maybe waiting for if to come out would be a solution)
- Flashing Polish and german (againg) 4.4 with and without pit file. no results (data not mounted and stuck in boot animation)
The only thing I can think of that I haven't tried yet is flashing a custom kernel, but I can't see any advantage in doing that. Next approach is taking it to the technical service to see if they can solve this situation. I'm afraid they're going to ask for almost as much money as a new note 3 costs...
P.D: I know I haven't taken part a lot in this forum, but I've been reading it for years, since I started playing with my SGS back in 2011. This is the first time I'm really lost after spending the night searching the forum (not only the note 3 section). This really pisses me off, with my previous phones I could always find a way to bring them back to life, but with SGS4 and SGN3 things are totally different thanks to samsung. (sorry for this looong post)
Thank you in advance
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Hundsbuah said:
have you checked repartitioning when using the pit file?
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click to expand...
Click to collapse
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Contruk27 said:
Yes, in fact I think it is checked automatically after you select the pit file.
Thank you anyway.
Any other ideas?
Click to expand...
Click to collapse
Did you try it with different Odin versions?
Pierre118 said:
Did you try it with different Odin versions?
Click to expand...
Click to collapse
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Contruk27 said:
Nope... I used last version, I read somewhere that it was safer...
I will try with an older one when I get home
Thank you for the idea!
Click to expand...
Click to collapse
No problem. Let us know the result.
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
ultramag69 said:
I'd try Odin 3.04, with the original stock polish rom.
I had no trouble using the Polish KK rom that came in 4 pieces, AP, BL, CP and CSC. I flashed 2 Note 3's using this with no problems whatsoever.
I can't say for sure you won't but it's worth a try...
Also, check to see if your Knox warranty has been tripped as this can happen when fooling around with roms.
You will have no love with Kies even when your region receives KK rom as Kies doesn't recognise bootloaders since MJ3... Good going Samsung, have had a few months to fix and have done NOTHING...
Click to expand...
Click to collapse
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Contruk27 said:
I've been searching for a rom in 4 pieces but I haven't find it. I downloaded 2 polish roms and neither of them was in 4 pieces. Can you tell me where can I find it? Because at the moment it's impossible to download anything from sammobile... Thank you!
My knox warranty was tripped just after the fail size error in odin, the first time I attempted to flash. However that's not my main concern now... haha
"Nice" to know that about kies. At this moment, the only reason to buy another samsung phone is the big community behind it :victory:. I thought they were going to do something about the bloatware, but it's getting even worse every time a new phone is announced...
Click to expand...
Click to collapse
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
ultramag69 said:
Not sure anymore, I no longer have the rom... And it was through Sammobile I got it.
Possibly someone might have it and share it with you....
Click to expand...
Click to collapse
It's going to be difficult that someone has it, since most people prefer 1 file roms. I will pray to sammobile haha
I'm not an expert, so I don't know if it's something critical for the phone (data mounted) to boot, but whenever I had this problem before with my previous phones, I was able to fix it by flashing a sock rom with odin or going back to the previous rom. So, my main concern now is that after all the flashing I've made, I still can't mount \data.
i wanted to try custom rom i rooted, had custom recovery and when i went to move from stock to cm11 and i didnt like it i tried to revert back to stock now im not able to do nothing im getting bunch of errors
odin fails to flash i tried all kinds of odin tuts
even tried chainfires one click setup nope fails
and i have this text on phone thats states i have write protection on...
but point is i just want to recover my phone all i can get into is recovery and download mode fine but thats it and when i try to flash anything in recovery i get state 7 or error 7 poping up im worried i just got the phone and i want it back to being alive agian any help be very much help i been up hours trying everything
sph-L720
Windows 8.1 x64
all usb drivers installed 4 times
krazeyfire said:
i wanted to try custom rom i rooted, had custom recovery and when i went to move from stock to cm11 and i didnt like it i tried to revert back to stock now im not able to do nothing im getting bunch of errors
odin fails to flash i tried all kinds of odin tuts
even tried chainfires one click setup nope fails
and i have this text on phone thats states i have write protection on...
but point is i just want to recover my phone all i can get into is recovery and download mode fine but thats it and when i try to flash anything in recovery i get state 7 or error 7 poping up im worried i just got the phone and i want it back to being alive agian any help be very much help i been up hours trying everything
sph-L720
Windows 8.1 x64
all usb drivers installed 4 times
Click to expand...
Click to collapse
When you trying Odin back the firmware you need to make sure your not trying to downgrade if you updated from 4.3 or above. If you are on 4.3 or above make sure your either using the same firmware or a newer firmware. If you use an old firmware it will always fail. So downloading the newest firmware will be your best bet.
Sent from my SPH-L720 using XDA Free mobile app
Same Boat with a friends phone
I am flashing NAE and NG2 firmware to the sprint s4 (no fails) but after the flash I am still only able to get to recovery and download mode. Side note: when trying to nandroid back up the phone reboots and will not create a backup. Please advise what if any fix I may look into.
Thank you,
Erik
erikbenedict3 said:
I am flashing NAE and NG2 firmware to the sprint s4 (no fails) but after the flash I am still only able to get to recovery and download mode. Side note: when trying to nandroid back up the phone reboots and will not create a backup. Please advise what if any fix I may look into.
Thank you,
Erik
Click to expand...
Click to collapse
ive gotten it restored back to stock but the sprint boot animation is gone i want that back i was fond of it so if anyone know how to restore the oringal sprint carrier boot animation w/ sound?
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
mintor said:
Hello.
I have a problem with my S4 i9500. I've successfully rooted it and flashed custom recovery. But I'd also like to install custom rom on it, and there is where problem begins. Every time I flash rom and reboot it stucks at boot logo. I've tried it with Philz and TWRP recoveries and three different kitkat AOSP based roms. But the situation looks the same every time, despite waiting over 15-30 minutes the system doesn't boot properly, it stucks at boot logo. Creating backups and restoring stock rooted rom works flawlessly however with both recoveries.
I've also tired twice to install rom without doing factory reset before and then it goes trough boot logo, however stucks at "android is being actualised" window or something like that.
I hoped to get rid of ugly and slow touchwiz from my phone as fast as possible, but with no succes so far. What am I doing wrong?
Sorry for possible mistakes, english is not my first language.
Click to expand...
Click to collapse
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Lennyz1988 said:
It should just work.
- Is your bootloader up to date?
- Running latest modem?
- Try not to flash it from your external sd but from your internal.
- Use something like Airdroid to transer the files from your laptop to your phone. I find it more reliable then cabled.
- Redownload the rom again.
- Use TWRP recovery. The rest is outdated.
- Make sure to properly wipe in the recovery. Maybe even wipe your internal storage (/data).
That's what comes to mind.
Click to expand...
Click to collapse
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
mintor said:
How do I check bootloader version and update it if necesarry?
I tried flashing both from internal and external memory, with te same result (no success).
Also, I didn't transfer roms form PC, I downloaded them directly to my phone. I did it the same way with my older phones and never had an issue like this.
Click to expand...
Click to collapse
As silly as it sounds, try to download them on your pc and then transfer them.
Lennyz1988 said:
As silly as it sounds, try to download them on your pc and then transfer them.
Click to expand...
Click to collapse
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
mintor said:
I was unable to get airdroid working correctly. I'm not sure if it wasn't because of SD restrictions on Kitkat. Maybe this causes my problem as well? I also realized that many file related operations like renaming a folder, deleting files and even downloading it is unsuccessful unless I use stock samsung app. I've transferred the rom later via USB cable and flashed, but the problem still occurs.
Click to expand...
Click to collapse
What roms are you trying to flash?
Lennyz1988 said:
What roms are you trying to flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-s4/i9500-develop/rom-t2913193
http://forum.xda-developers.com/showthread.php?t=2688387
and CM11 found outside XDA, I cannot find link.
I also tried to flash CM10.2 and 10.1, but both recoveries refused to even flash it.
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
mintor said:
I found out that the problem is I cannot flash kernel. I tried to flash few of them, but nothing changed in About device/Kernel Version. I also have SE for Android status "Enforcing".
Click to expand...
Click to collapse
What does it say your model is when you are in download mode?
Lennyz1988 said:
What does it say your model is when you are in download mode?
Click to expand...
Click to collapse
Do you mean "Product name"? It's SHV-E300K
It's Korean model. I'm not sure if GT-I9500 ROMs will work correctly on SHV-E300K (if it's booting), due to too many differences between International and Korean version.
Sent from my ASUS_Z00AD
mintor said:
Do you mean "Product name"? It's SHV-E300K
Click to expand...
Click to collapse
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Lennyz1988 said:
Then why did you say you have an i9500? You have a SHV-E300K which is a completely different model.
Click to expand...
Click to collapse
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
mintor said:
Because in About device/Model number it shows I9500. Sorry, I didn't know the info from download mode is more important. Why would it show different things anyway?
Click to expand...
Click to collapse
Because you can change it manually, but you cannot change the model in in download mode.
forum.xda-developers.com/showthread.php?t=2284543&page=101
Use that thread for reference.
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.
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.