CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.
dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Good Info today morning i've flashed with TWRP but went on successful I am happy it did not Brick, But here on in Future will keep this in mind, Any possibilities now that the device is working fine are there any chances of bricking in future.
If bootloader is flashable through cwm zip then its possible to flash it via a full custom rom zip too then ? logical ?
theres a dev in Note 2 community who included the bootloader in his 4.3 rom ...i make sure I look at the skeleton of the zip after downloading. i never went to his thread again.
at that time everyone said bootloader doesnt get flashed through cwm. but whatever the case all devs have a moral responsibility to inform from before in changelog or instructions if bootloader is included in his rom zip whether it gets flashed or not. It should not be done surreptiously.
anyway good post, important discussions, should be made sticky :good:
Thank you DR.KETAN for this very important advice.
I have flashed by odin but about to flash by CWM last night.
Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium
dr.ketan said:
Who have successfully flashed have nothing to worry or nothing needs to do now.
If it includes in cwm plain or including rom risk remains same.
I can even make simple utility with which you can flash bootloader with simple application on device by just keeping bootloader file on SD card. But I will never do that.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
So bootloader= odin. End of story
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
You mean to say that if we flash it through CWM or through any simple utility like you mentioned then there are chances of the bootloader going to the wrong partitions? Is that what you are trying to say?
I am thinking is there any way to find out which is the correct partition for the bootloader then?
Sent From My New Galaxy S5 GT-N7100
dr.ketan said:
Bootloader.tar.md5 = odin.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:
Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium
palace35mm said:
Hi Doc this bootloader.tar.md5 file should be put in which option in Odin?
PDA
Phone
Bootloader
I think its the bootloader but want to be 100% sure.:laugh:
Click to expand...
Click to collapse
Bootloader or pda any.
I recommend bootloader.
Sent from my SM-N900 using xda premium
dr.ketan said:
Bootloader will flash to partition on which cwm script have mentioned. But look thread in op where partition was defined correctly even though it was bricked also we don't have complete mechanism and information about knox stuff and how Samsung have managed it.
When you flash with odin Samsung have already coded file where and how to flash and it will go correctly. Another big issue is cwm itself can't stop flashing if file is corrupted. Only concern here is bootloader, if you flashed corrupted recovery /modem/kernel chances of brick is almost nil and your device can be survived by correcting it. But when you flash wrong bootloader /corrupt bootloader there may not have any combo key working so you will be helpless. It may or may not rescued by jtag box.
So always wise decision is use only tar.md5 format with odin to make safest land.
Just remember if anything most dangerous in terms of flashing it's bootloader.
Sent from my SM-N900 using xda premium
Click to expand...
Click to collapse
Yeah that is the most important thing of all.
And it's better to be safe with the bootloader. I don't think we have a hard unbrick method like the note 3 through sdcard.
So it's better to be safe [emoji106]
Sent From My New Galaxy S5 GT-N7100
dr.ketan said:
CWM flashable bootloader safety concern.
I have recently seen users here flashing bootloader with CWM, here is my just head up for safety concern of CWM flashble bootloader
Here is link to post by well known X-Note ROM developer @soloilmeglio regarding forcing bootloader with CWM
http://forum.xda-developers.com/showthread.php?t=2609561
even chances are less than a 1% it will be huge for terms of breaking device. We rarely rare seen any reported brick device by bad method of flashing on XDA.
Irrespective of this another concern is MD5 check. I strongly recommend to flash bootloader with MD5 check only. Once on CWM flashable format hardly any newbies doing md5 check before every flashing (even Philz have included built in). Any corrupted bootloader download flashing will high possibly end with brick. Bootloader best to be flashed with Odin with tar.md5 format so any corrupt download will auto fail bootloader flashig even one have not checked it.
Hope this will be enough to understand
Regards
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.-flash using Odin for bootloader tab.
Click to expand...
Click to collapse
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?
dr.ketan said:
CWM flashable bootloader safety concern.
PS : Anyone requires safe ND3 Kitkat bootloader with tar.md5 it is here.
Click to expand...
Click to collapse
Thanks @dr.ketan for all your wonderful works, insight and knowledge:thumbup:
My concern is can we flash the above bootloader on DN3 rc2 rom provided by the great E-team?
Sent from my GT-N7100 using XDA Premium 4 mobile app
Bootloader is not rom dependent. You can flash on any kitkat based ROM.
Sent from my SM-N900 using xda premium
haybill said:
I repeat--many thanks for the warning---I will take notice--might even re-flash with ODIN--since you say that the original zip was not correct?
Click to expand...
Click to collapse
No you need not to Reflash if your bootloader information is correct.
I didn't get you about original zip. Can you point me exactly?
Sent from my SM-N900 using xda premium
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No you can't downgrade your bootloader because of Knox security implemented
Sent From My New Galaxy S5 GT-N7100
---------- Post added at 11:24 AM ---------- Previous post was at 11:20 AM ----------
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100
i vote for no tinkering with official BL....for personal experiments fine but for community...no
ive come across many expert users who havent been able to use their wifi even with mj5 bl or later, reverting to stock hasnt helped either.
justkiddinghere said:
Can we change bootloader frequently ?
Like I am on kitkat now then go to jellybean MJ5 then again kitkat ? No issue?
Click to expand...
Click to collapse
No.
Probably this one is last for Note2, you may not need to flash bootloader in future. (I don't think Note2 will get 5.0 ever)
but No it's requires only when there is major OS change and once you have 4.3 OR 4.4 bootloader, you can't downgrade but still can use 4.3 by flashin ROM with CWM OR Odin without having bootloader in it.
smeet.somaiya said:
@dr.ketan
I was just wondering if we could remove the Knox security or Knox part of the code from the bootloader files I mean sboot.bin,param.bin and tz.img so that we can get a Knox free kitkat bootloader. I know that won't work for people who already flashed MK4 and later. But it would really be helpful for people on MJ5 as they can retain warranty and be Knox free.
Is this possible?
Sent From My New Galaxy S5 GT-N7100
Click to expand...
Click to collapse
I am too small to do it.
Related
*Question aswered *
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this R: Install newer CM and AOSP Roms without random reboots and to actually boot them
-how to install it R: Follow the guide on the link providen in this post below
-what are the risk R: If you dont instal the right bootloader for the right device = brick. But the proccess is the same to flash a ROM
-is there any issues known with this bootloader R: Still waiting
-can we flash old roms that worked on the old bootloader on this one R: YES !
-how do we know if we need the new bootloader before flashing a rom. R: Open a terminal emulator and run those commands : su *enter*
getpro ro.bootloader And check if you have the newest booloader referred to the guide on the link below
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
kruse1944 said:
Hi, am I the only one to be really confused about this new bootloader thing that we need to flash certains roms? Theres is no guide at all on our T999(v) to explain what
-are the benefits to install this
-how to install it
-what are the risk
-is there any issues known with this bootloader
-can we flash old roms that worked on the old bootloader on this one
-how do we know if we need the new bootloader before flashing a rom.
As you can see all those questions are not really understood from our T999(v) forum. I've researched on the forum for any information and I've found only this guy that provide MD5 bootloader with a few instructions http://forum.xda-developers.com/showthread.php?t=2282603 but really this is confusing. I do not want to make a fatal mistake and brick my S3 so this is why i'm asking all those questions to you guys. For info I own the SGT-T999v.
Click to expand...
Click to collapse
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Aerowinder said:
In the thread you linked, there is a T999v link. So you'll want to take that. Do not flash our bootloader on your phone. Must be T999v bootloader.
We don't have access to a changelog. Need to do it to flash newer AOSP ROMs. Why? Because the older ones were causing rebooting issues.
There is no risk as long as you get the bootloader for your device.
You can flash old ROMs.
Click to expand...
Click to collapse
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Bootloader shouldn't cause signal issues. But flashable over recovery is correct.
Sent from my SGH-T999 using xda premium
kruse1944 said:
Thank bro, that is what i wanna hear. But the guy is saying to flash the zip (of the t999v version) over the recovery, I thought it would be with Odin (like a firmware upgrade). Also i've heard some user have poor battery life since MD5 bootloader and bad 4G..?
Click to expand...
Click to collapse
Stop talking about MD5. That firmware is not for your phone. I want to be certain you aren't going to flash that. As for battery life, I had to revert to LJC because of battery drain. The AOSP ROMs only require LJA or newer for us. I don't remember your firmware versions.
Safe to use recovery to flash this stuff. You could make an Odin package, but it would be a waste of time.
IXChicharitoXI said:
Just flash the zip through CWM or TWRP. The guy says in the OP he made the flashable files so you don't have to use a computer for this process.
If you get bad 4g, then just flash the modem you're on. There's a modem sticky thread in the development section.
Bootloader and modem/baseband are not the same thing.
I have the DLJA modem and the MD5 bootloader. I haven't had any issues at all.
Remember, if you have a T999v, only flash modems and bootloaders made for that specific device. It will clearly say in the op when you read it.
Goodluck.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Great thank you! So i've looked for my actual bootloader on my S3 with those commands : su getpro ro.bootloader I was surprised, it told me that I already have the T999VVDLL1 bootloader required for newer AOSP CM roms.
All of this is correct.
You also do have the option of flashing the latest firmware for your model device using Odin.
As long as you've upgraded to VLDLL1 via OTA, Kies or Odin you don't need to do anything.
Sent from my SGH-T999L using xda premium
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
WoodenDiamond71 said:
I want to flash CM10.2 on my rooted 4.3 MK3 s3. Is it possible to flash that rom on the phone although Cm10.2 is android 4.2.2?
Thanks!
Click to expand...
Click to collapse
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
joeyhdownsouth said:
As long as the file you download does not downgrade the boot loader. ROM zips will not do this unless otherwise noted. Flashing tar files through ODIN can brick your phone if you downgrade Android version number because tar files reflash every part of the phone, including bootloader.
sent from my GS3
Click to expand...
Click to collapse
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
WoodenDiamond71 said:
You're correct about the downgrading the bootloader part since i have learned my lesson the first time, but as far as flashing the rom is concerned my recovery will not flash it and i get the broken android as the background and my recovery says the installation was aborted. I am using philz touch recovery 6 btw.
Click to expand...
Click to collapse
You should be also getting a status 7 error, because the bootloader you currently have (MK3) is not listed as one of the "approved" bootloaders in the updater-script for any 4.3.x ROM based on AOSP. You will need to go into the updater-script and modify one of the lines to match your bootloader, or get rid of the assert lines altogether. Any KitKat 4.4.x ROM's will have your bootloader listed, so this is not necessary for the newest ROM's.
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
WoodenDiamond71 said:
How would I do that? Is there a tutorial I can follow
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/791952-all-in-one-guide-modifying-custom-sprint-roms-virgin-mobile-use.html
This is a tutorial I have put together on Android Forums for the rooted Virgin Mobile community (SGS3), since we have to always modify or delete the asserts in order to get Sprint ROM's to flash on our phones. Principle is the same for any Sprint user in your situation. I also just made a YouTube video showing how to do the relevant parts of my tutorial.
https://www.youtube.com/watch?v=IZnYSrUIXKM
Hope this helps! Feel free to PM me if need be for any clarification.
Sweet!! Thanks I'll check it out later once I get out of work. Thanks once again I'll pm if it worked
Sent from my SPH-L710 using Tapatalk
Hi,
Have a Note II as an alternative phone. Apparently, the phone worked correctly until last month. It started to reboot, not too much, but it happened. Well, I tried to give a solution changing the ROM (when it started with the problem I was in 4.4.2 OmniROM). My first try was with Omega ROM, cause it was my first custom ROM when I bought the phone with 4.1.2 in, but the problem persist (maybe increment the number of reboots-freezes/day) so I changed it again to Android Revolution HD, but it only increment the reboots/freezes.
It seems that it's not a ROM installation problem or something like that, maybe it's a hardware problem, but I would like to hear your opinions about it.
Now the phone have:
TWRP recovery
Rooted
Android Revolution HD
I am thinking on put the stock ROM and bootloader with Odin. What do you think?
Thanks!
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
mat9v said:
Could you enter recovery, format /system /data /cache and flash clean Omni > reboot >reboot to recovery >flash Gapps> reboot and observe without installing any apps. Until it freezes or reboots anyway.
Click to expand...
Click to collapse
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Edit:
jakuburban said:
My dad also has note 2,he had the same problem on many different roms.
He had to give it back to repair. They've replaced power button and something else, after that the phone seems normal.
Sent from galaxy n7105
Click to expand...
Click to collapse
Did you repair it even with custom ROM? Samsung does not accept it, right? Anyway, my phone is not in guarantee time.
Thanks!
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
pep0te said:
Hi mat9v,
Thanks for your reply. I am in the office now, but I will try it as soon as I can. I thought on your suggestion too, so I will give a chance .
In case of it does not working, if I restore to stock ROM, will it restore the bootloader and recovery automatically too?
My actual bootloader if I am not wrong, is MJ5 bootloader (to fix the WiFi problems with custom ROMs in 4.3).
Thanks!
Click to expand...
Click to collapse
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
jakuburban said:
Nah, of course I restored it to official 4.1.2 so everything was like new.
If You don't have guarantee, not good
Sent from galaxy n7105
Click to expand...
Click to collapse
Hope I can fix it by other way then . Thanks!
mat9v said:
Yes, it will overwrite both bootloader and recovery, unroot and so on. Be careful with KNOX and look for TriangleAway to reset flash status to factory.
Click to expand...
Click to collapse
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
pep0te said:
Hope I can fix it by other way then . Thanks!
Hm, could you explain me a bit? Sorry if my question is stupid.
Thanks a lot.
Click to expand...
Click to collapse
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
mat9v said:
If you want to return the phone to service center you mast be careful to maintain KNOX status 0 and Software status: Factory or they may refuse to fix the phone (warranty void by messing with software) - it's not such a big deal here in Europe but in US there are some stupid rules like that. So long as you remain on MJ5 bootloader you should have no problem with KNOX when you flash Samsung firmware but Firmware status: Modified vs Factory require using TriangleAway program to reset specific counters. Find it on Playstore and follow the link there to explanation on how to proceed.
Click to expand...
Click to collapse
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
pep0te said:
Hi mat9v,
Just fyi, I am from Europe . So this mean that I should check if Firmware status is "Modified" or "Factory" and KNOX = 0. In case of it is "Modified" (most probably right?) or KNOX = 1 or more, I must use TriangleAway to reset the counters.
That's okay, thank you all for your help . I will try and give my feedback asap!
Click to expand...
Click to collapse
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
mat9v said:
You can't reset KNOX counter if you are on a bootloader newer than MJ5 (it's been tested that on MJ5 you can deal with it by flashing earlier firmware along with older bootloader). More info HERE
Click to expand...
Click to collapse
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
pep0te said:
How can I check my bootloader? I am almost sure that is MJ5 but... better to check.
Thanks!
Edit:
The stock ROM I should install is the 4.3 I choose in sammobile, right? Spain country in my case.
http://www.sammobile.com/firmwares/3/?download=23362
Thank you.
Click to expand...
Click to collapse
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Amazing, alright now. Hope I can fix this usual problem...
Thanks for your complete and helpful answers!
mat9v said:
To check bootloader install "Info" by Nag from Playstore and look in OS category.
Yes, but it will flash bootloader newer than MJ5 I think (MJ9 if my memory serves me right) and you may not be able to set KNOX to 0. Also you must play with TriangleAway before flashing stock 4.3 because it does not work on stock (root required).
Since you are in Europe, it should not matter too much (according to European law) so if someone makes any heat just say that it a law
Click to expand...
Click to collapse
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
pep0te said:
Hi again,
My bootloader (Info app) is:
Bootloader: N7100XXDLL7
I think this is the old (4.1.2) right?
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
mat9v said:
Yes, and it is probably the reason for Android Revolution problems. If I remember correctly it is a 4.3 rom and they have compatibility problems with older bootloaders - the results are random reboots and freezes (there is a lot about it in Phoenix rom thread). To comfortably use TW 4.3 rom it's best to update bootloader to MJ5. AOSP roms should not be affected though so I suppose that there was some other cause for this. You can flash 4.1.2 on this bootloader without issue, be mindful to safeguard data from your internal sdcard as you may loose them all.
I would advise testing standard 4.1.2 version and if everything works fine, flashing something new (with MJ5 bootloader for compatibility sake).
Click to expand...
Click to collapse
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
pep0te said:
Thanks. You suggest to flash 4.1.2 stock from sammobile right? I mean, it should install the same bootloader that I have now.
Thanks again!
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Yes, exactly.
mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Okay, I will do it then. Thanks a lot! :fingers-crossed:
mat9v said:
Yes, exactly.
Click to expand...
Click to collapse
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
pep0te said:
Hey mat9v,
I am trying to reset the counter but it still shows "1" (before this, it showed "7"). Do you know why can't get to fully reset it?
Thanks!
Click to expand...
Click to collapse
To fully reset the counter it has to be done in certain order. I do not remember exactly in which order the sequence of events should proceed but it went something like this:
- run triangle away
- reboot
- enter download mode (odin version)
- flash stock rom
If you reboot even once to custom rom (this I'm certain) or even custom recovery (I think) the triangle away effect will be gone and the count returns to 1 because it detects custom rom/kernel.
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Im having the same problems. odin is giving no love on updating the bootloader
Kenny_ken said:
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Click to expand...
Click to collapse
Did you try to flash the kernel as stated in the installation instructions of the rom that your trying to install?
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
TeamFox said:
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
Click to expand...
Click to collapse
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
asin_punk said:
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
Click to expand...
Click to collapse
To clear things up i have already got agni kernel installed via recovery. I just cant update my bootloader via odin.
problem flashing mj5 bootloader and agni kernel too
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
anandsaurabh said:
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
Click to expand...
Click to collapse
Agni kernel is only flashable via recovery not with odin.. Its a zip file.. U can flash it using CWM or Philz Or twrp recoveries
Sent from my GT-N7100 using XDA Premium 4 mobile app
U r right hazin ... That file can be flashed only via recovery... But I m not able to flash it.. It goes into aroma installer, does its work and says done but does not show on settings... I e saved log file too of that process...
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
did you fix the problem ?
apuntigam said:
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
Click to expand...
Click to collapse
having the same thing now...
Davids said:
having the same thing now...
Click to expand...
Click to collapse
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
so the phone is dead ?
apuntigam said:
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
Click to expand...
Click to collapse
noting to do to bring back wifi&BT ?
Davids said:
noting to do to bring back wifi&BT ?
Click to expand...
Click to collapse
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
apuntigam said:
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
Click to expand...
Click to collapse
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Davids said:
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Click to expand...
Click to collapse
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
apuntigam said:
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
Click to expand...
Click to collapse
i have the 7100..
somthing for that device..
Davids said:
i have the 7100..
somthing for that device..
Click to expand...
Click to collapse
Ok, then it's a completely different discussion... not sure why the bootloader would be failing in that case, since it was built for that device. You could try a different Odin? (Assuming of course that your are NOT trying to DOWNGRADE the bootloader... it's well known that you can't downgrade the bootloarder to MJ5 from something more recent).
Otherwise, I'm sure there are equally useful ROMs for the N7100 in the Note 2 Original Development forum.
But, since your device is probably pretty old and almost certainly out of warranty by now, I would seriously consider flashing the latest official Samsung ROM to get the latest bootloader and then flash whatever you want on top of that. Voiding the warranty is irrelevant if you're already out of warranty. But, I have heard that even with the latest bootloader some people still have trouble with wifi and BT. In that case all I can suggest is playing around with different ROMs until you find something that works for you. As I'm not a N7100 user I can't really offer more advice than that, sorry man.
Guys where I can find a REAL WORKING link to download mj5 or higher bootloader??
I tried a lot & most of them are obselete
Maybe downnload the latest stock ROM from sammobile.com and extract the bootloader?
https://www.sammobile.com/firmwares/database/GT-N7105/
]So I was stuck in a hard place and needed a recovery fix and couldn't find one... I stumbled across an .Img file so u converted it to a .tar file and shall share in hopes that people who make the mistake as I did don't have to go the the grueling process of flashing all the way back to mk2 and lose everything that they currently had and starting over
Download = https://www.dropbox.com/s/mx1933wuc...short route to recover from such a situation.
Cool!
Sent from my iPhone using Tapatalk
Maybe this is very commendable, but maybe not. What phone do you have? What rom did you have to begin with? What firmware was this image file made from? Basically, you need to be much more specific if you're actually trying to help some other people.
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Can you Be more Specific
Which recovery is this . I downloaded it and the file is only 10.5kb . Its a really small file .. also my bootloader is locked so if i flash this in odin . I most likely will get a fail or a paper weight ...
spirodave said:
Which recovery is this . I downloaded it and the file is only 10.5kb . Its a really small file .. also my bootloader is locked so if i flash this in odin . I most likely will get a fail or a paper weight ...
Click to expand...
Click to collapse
i had boot fail odin flashed it and it booted; so im sharing.
dkephart said:
Maybe this is very commendable, but maybe not. What phone do you have? What rom did you have to begin with? What firmware was this image file made from? Basically, you need to be much more specific if you're actually trying to help some other people.
Yrs,
dkephart
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
This is for the White AT&T Branded S4, i found the img file, converted it for .tar; i believe its the MK2 version, i was locked out of phone because of trying to flash a custom recovery because im experimentive; i flashed this and my phone booted back and i didnt lose anything...
Im personally running a rooted NC1 4.4.2 rom using Safestrap since the bootloader is locked.;;
s0xpan said:
This is for the White AT&T Branded S4, i found the img file, converted it for .tar; i believe its the MK2 version, i was locked out of phone because of trying to flash a custom recovery because im experimentive; i flashed this and my phone booted back and i didnt lose anything...
Im personally running a rooted NC1 4.4.2 rom using Safestrap since the bootloader is locked.;;
Click to expand...
Click to collapse
.. pLEASE VERIFY WHICH VERSION THIS IS . ? YOU SAID IT MIGHT BE MK2 . CAN YOU FIND OUT FOR SURE
Im pretty sure this is in the wrong thread .. this should be in Q/A help and troubleshooting.. Be prepared for a bunch of PMS 'ers
spirodave said:
.. No one will be able to use this file because it isnt labeled in the title .. SO MY ? IS ..WHAT IS THIS FILE PLEASE TITLE IT ..? SORRY MY CAPS LOCK IS STUCK ON MY COMPUTER..
I GUESS IT WOULD BE USEFUL FOR SOMETHING ..BUT NO ONE WILL KNOW WHAT IT IS UNLESS YOU TELL US ..YOU SAID YOU THINK IT MIGHT BE MK2 ???? WHY WOULD I FLASH SOMETHING THAT I DONT EVEN KNOW WHAT IT IS AND WHATS WORSE IS YOU DONT EVEN KNOW FOR SURE ..ITS A GOOD WAY TO BRICK SOMEONES BABY..DONT TAKE THIS THE WRONG WAY EITHER. I APPRECIATE ANY TOOLS I CAN PUT IN MY BOX ..THIS COULD BEA NICE THING TO HAVE ..
Click to expand...
Click to collapse
it's simply the mk2 stock recovery img; incase you tried to custom flash a recovery (which has been proven to fail) and the bootloader kicks you out (non-safestrap recovery like actual recovery recovery)
...i apologize for not being more specific.
i was in a jam at work when i tried to flash custom clockworkmod recovery to my main recovery via safestrap and got bootlooped due to our locked bootloader. I found the recovery.img file under some thread and i formatted it to work with odin; flashed it to my device an SGH-i337 and it allowed me to boot back up normally. so for me it was a safe haven, and im just trying to help others who tend to experiment even when told not to.
s0xpan said:
it's simply the mk2 stock recovery img; incase you tried to custom flash a recovery (which has been proven to fail) and the bootloader kicks you out (non-safestrap recovery like actual recovery recovery)
...i apologize for not being more specific.
i was in a jam at work when i tried to flash custom clockworkmod recovery to my main recovery via safestrap and got bootlooped due to our locked bootloader. I found the recovery.img file under some thread and i formatted it to work with odin; flashed it to my device an SGH-i337 and it allowed me to boot back up normally. so for me it was a safe haven, and im just trying to help others who tend to experiment even when told not to.
Click to expand...
Click to collapse
Right on ...Thanks man .. Yeah this will help .. I had it happen when falshing a rom and i lost safestrap and was stuck in a boot loop ..So this would be very helpful in that case ..I wish this would be for NB1 or NC1 ..Especially since there is a root method for 4.4 usinf towelroot