[Q] Why should I change my bootloader? - Galaxy S 4 Q&A, Help & Troubleshooting

I am running a i9505 and dont see difference between bootloaders?
Arent they used for flashing with odin?

Make it simple..
1- Bootloader starts firstly before kernel, system.. etc
2- Bootloader prepares environment for the phone to boot..
3- New bootloader has something called "knox" which detects custom things flashed to your phone.. and currently if you triggered knox 0x1 there's no way back !
4- Old bootloader doesn't contain that "knox" ****..
Good luck

Related

[Q] N9005 rooted, locked bootloader

I want to install a linux OS, however, I am getting errors concerning permissions and/or looped devices (I have removed Knox). I believe I need a different Kernel.
My device was rooted yesterday (Odin for PC), by a friend as I do not have access to a windows machine and couldn't get Odin working via a VM. I can confirm that I now have root access.
When I boot into download mode it says: qualcomm secureboot: enable (csb) - I assume this means my bootloader is locked?
Is it possible to unlock the bootloader, without using a windows PC, so that I can install a recovery and use Omega Files Pro (or similar) to flash an Omega rom? Is it even necessary to unlock my bootloader in order to flash a rom (my warranty is already void, but I do not want to brick/damage my phone)?
Thank you for your help.
Bootloader can not be unlocked at this time.
The locked BL makes it impossible to downgrade from KK to JB. But you can flash roms/recovery/kernel.
Read the guide that is linked in my sig to see how.
Khizar said:
The locked BL makes it impossible to downgrade from KK to JB. But you can flash roms/recovery/kernel.
Read the guide that is linked in my sig to see how.
Click to expand...
Click to collapse
Just make sure if you're on KK then you flash a KK rom....

[Q] Rooted S4 GT-I9505, How to update from 4.2.2 to more recent ? - keep root

Hello,
I'm using a SGS4 rooted since more than one year and a half (odin, flash a small root bin file if I remember well, flash counter set to 1, no custom recovery and no nandroid backup)
Since I want to implement NFC card emulation now avaliable in android 4.4 in one of my apps, I'd like to update.
I've seen few threads on the subject, and most of them date from a long time (am I late ? ). I'd like to know how I could update normally my actual rom (provided by Orange, precisely I9505XXUAME2), or move to another slightly modified rom like the base rom provided by samsung without all these apps that you can only remove with root.
I don't want to have any data issue I've read about, I don't want to lose my actual apps and their data. (Nandroid backup then restoring apps and their data through nandroid manager?)
Also, if possible i'd like to update without losing my start screen, my parameters, etc... (in the worst case I'd re-set them manually). And finally of course I want to have it rooted at the end of the process.
In fact I want it to be just like if I had done an OTA update, then rooted it.
Also, How to update without setting the Knox counter to 1 ? (My flash counter is set to 1, should I use Triangle Away?)
Is there any simpler way than flashing the new firmware and then importing everything from my old data to the new and reinstalling the changes I made to the system (like avast & such) ?
Also, maybe there exists newest versions of the firmware, but without the new bootloader that has the knox counter ?
Thanks in advance!
tboss1995 said:
Thanks in advance!
Click to expand...
Click to collapse
1. You can't receive OTA updates if you have rooted your device. You have to flash the firmwares via ODIN.
2. You don't need wipe nothing if you flash new stock firmware. Instructions: Flash new firmware (if you don't have wifi flash it one time more), root it again then and you're done. Your data don't have to be affected (maybe you only have to reinstall some app if the data/cache was moved to the SDCARD).
3. Flashing one new stock firmware don't modify KNOX. You actived KNOX rooting your device or flashing one custom recovery. Knox: 0x1 can't be reset. Triangle away only reset the flash counter.
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
tboss1995 said:
Thanks for your fast answer !
So, flashing a firmware doesn't impact the data.
Updating via Kies sets the Knox counter. Updating via odin doesn't ? Don't I have to do any sort of un-root before updating ?
Is there anything specific I should know about root ? Because I don't want to flash a firmware that I won't be able to root without setting the knox counter.
Also I think that since we can't revert the bootloader update, maybe i'd better not update that bootloader so that I can update future versions and root them without setting knox counter, by installing a knox-free rom even before a knox-free root is released...
Where can I find these roms?
Click to expand...
Click to collapse
1. Updating via ODIN or Kies don't set the KNOX counter. Downgrading YES.
2. Root dissapear if you flash new update via ODIN.
3. You can flash latest firmware and root them without KNOX. Take a look for the method: HERE.
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
tboss1995 said:
Thanks for the answer again!
Howerver I still have 3 questions because I like to understand what I'm doing :
1. I understand the two terms ROM (OS of the phone) and bootloader (after a certain update, it adds the knox counter, and you can't downgrade it, and it also prevents towelroot from working). What is the called "kernel" ?
2. Up to exactly what version of the bootloader/rom does towelroot work ?
3. What is the difference between "knox-free" and "knox counter 0"? At the end of the method, will I have the new bootloader with a knox counter set to 0, or the old bootloader ?
Click to expand...
Click to collapse
1. Take a look: HERE.
2. Nobody know it.
3. - KNOX free: This therm is used for the custom ROMS normally. This mean that flashing this ROM dont touch the KNOX counter.
- KNOX counter: You still having your device in warranty if you have KNOX:0x0. You void your warranty if you have KNOX:0x1 in DOWNLOAD MODE.
So it means I'll still have the new bootloader ?
For those who may come to read this article and don't want to watch a video, I've found an article explaining what kernels are. http://m.androidcentral.com/android-z-what-kernel

Test bootloader 910H - possible reset for Knox Warranty?

Hi, guys!
There is on guy on 4pda that has bootloader with the following in Download mode:
Code:
Odin mode
Product Name: SM-N910H
Current Binary: Samsung official
System Status: Custom
Reactivation Lock (KK): OFF
Secure Download: enabled
Knox warranty void: 0
AP SWAEV: 0 (test devise)
I believe that this is test device, and accordingly to Note 3 story it can give a possibility to reset Knox Warranty counter. Could some one of gurus please advice how we can backup and share his bootloader?
Thanks a lot in adnance!
This may help to backup sboot and param. And maybe other can restore with it. But we must be calm. And wait for advanced help.
Wanam tool
https://play.google.com/store/apps/details?id=ma.wanam.partitions
kadiremrah said:
This may help to backup sboot and param. And maybe other can restore with it. But we must be calm. And wait for advanced help.
Wanam tool
https://play.google.com/store/apps/details?id=ma.wanam.partitions
Click to expand...
Click to collapse
The only problem - it requires root. And I don't know yet if that guy has a root. Flashing root with Odin may change warranty bit. Any other idea?
Re flashing stock ROM will replace original bootloader.
I strongly NOT in favor of making backup of bootloader and restore using anything other than Odin. In world of flashing if anything is RISKY it's only and one bootloader. Also I don't believe any method of restoring bootloader other than Odin will work anymore on newer device. Either it will make no effect OR IT CAN BRICK device.
Also If anyone have boot loader with re engineering which reset knox warranty - I do not recommend to try UNLESS you must required to do it.
Say for example your device have something wrong and you needs to send to service station - still you can flash that bootloader if required isn't? Only condition when you cant flash bootloader is
-Faulty USB pin - Who cares for warranty ? It does cost couple of $ why we should take risk for complete device?
-Hard bricked with unable to boot to download mode - How samsung service station can find your Knox status in this condition?
So Flash such bootloader only you really need it when required with own risk.
Thank you very much for advice.
But on Note 3 there was procedure to restore Knox warranty bit exactly by flashing test bootloader with Odin. I just want not to loose possibility to have a solution... Of course, I will think twice before flashing that BL, but at lease we will have some data to explore! Isn't it?
Obviously it's marvelous thing to have possibility to reset knox but only thing I suggest is to use as only real needy case not for fun /experiment.
Sent from my SM-N910G using xda premium
So - any idea on how to copy bootloader?
I furtunately found this gide:
http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911
I hope it will help!
Zer0r said:
So - any idea on how to copy bootloader?
Click to expand...
Click to collapse
But why you need to copy bootloader? You can get it from stock ROM file too. simply unzip stock ROM tar.md5 and you will have it.
BTW exynos version requires only one file for bootloader sboot.bin
dr.ketan said:
But why you need to copy bootloader? You can get it from stock ROM file too. simply unzip stock ROM tar.md5 and you will have it.
BTW exynos version requires only one file for bootloader sboot.bin
Click to expand...
Click to collapse
I need to copy bootloader from Developer Edition phone. That bootloader is unlocked. I have access to one of such phones, that is why all thiss mess
Oh ok got it now.
Sent from my SM-N910G using xda premium
So - here is bootloader with param partition. If anybody wants to explore them - you are welcome!
This bootloader is from Test Devirce. It doesn't locked, so any unoficcial actions wit device doesn't affect on Knox Warranty Void bit, it is checked.
Who is going to test it? :laugh:
Is it possible to reset N910C device? Testers waiting for you??
megatooth said:
Who is going to test it? :laugh:
Click to expand...
Click to collapse
Other file should be used for testing, not that. That file can not be flashed via Odin as a bootloader.
I will not post it, because it is a bit risky. And there some backup preparation should be done before flashing. But anyone who wants to be a volonteer - welcome in PM, please.
Well, unfortunately it does nothing. I tested and flashed it on my own device - bootloader has changed, but not to (test device) status, and the Warranty bit was not resetted to 0... But we tried!
I want to thank a man who helped me a lot - @A.S._id.
On Note 3 prosedure was.
* Flash sboot an param
* Reboot download mode again
* Flash stock rom of your region from odin
* Factory reset on stock recovery
* Boot system
* Again download mode
* Re flash stock rom
* Factory reset and boot
This was working on note 3.
Zer0r said:
Well, unfortunately it does nothing. I tested and flashed it on my own device - bootloader has changed, but not to (test device) status, and the Warranty bit was not resetted to 0... But we tried!
I want to thank a man who helped me a lot - @A.S._id.
Click to expand...
Click to collapse
Any news? Sorry for spamming. @Zer0r Did you tried to reflash stock ROM and as well reset factory as the same procedures with Note 3? Post some images from successfull changing Bootloader please. I'm curious to that bootloader too. Mine is 910C.
tuannghia1985 said:
Any news? Sorry for spamming. @Zer0r Did you tried to reflash stock ROM and as well reset factory as the same procedures with Note 3? Post some images from successfull changing Bootloader please. I'm curious to that bootloader too. Mine is 910C.
Click to expand...
Click to collapse
No news, bootloader from test device, which, as we thought clearing warranty bit, didn't clearing...
Here is bootloaders for flashing via odin, one from test device, and different from realise device, you can to try flash them and make sure...
https://yadi.sk/d/IUpILBpjh2JKW
p.s.
as it turned out - the test device has ceased to be a test, after he flashed stock firmware
http://cs3-3.4pda.to/6337019/%C1%E5...d4b8c000000007ac5697c47447c2fe32cb87a6142b1cb
Any update?

[Q] Not rooted properly, and wan't stock bootloader back, and unroot!. (Not Firmware,

Hi, I accidently rooted and installed cwm on my galaxy s4 gt i9-505, without disabling knox, and now I want to go back to the orginal samsung bootloader, (I don't not want to know how to get the stock firmware), I want to unroot and restore the bootloader, really need help asap, would be apperiated thanks.
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Not sure what is there to fix - if phone boots correctly it is good.
If you try to revert back to knox 0x0 I'm afraid it is not possible.
Flashing root and cwm doesn't replace your bootloader
How do you accidentally flash root and a customised recovery?
Imtigerclaw said:
Update: I'm on Android L 5.0.1, and installed cwm before rooting which was a silly mistake, because knox then countered that, and it's conflicting root problems when I tryed to root afterwards, but now I just want to go back to the Samsung bootloader, root issue fix but still don't know how to fix bootloader.
Click to expand...
Click to collapse
You are really mixing things up.
A custom recovery has nothing to do with Knox. A custom recovery gives no problems with Knox. It's impossible.
You are on the samsung bootloader. You cannot change it to a custom (there isn't even any).
If you want root just flash cf auto root and then delete knox. That's all.

[HOWTO][GUIDE] Flash anything on G925F without tripping Knox

How to Root your SM-G925F (International S6 Edge):
This should work on both 5.0.2 and 5.1.1. I have upgraded to 5.1.1 before doing this.
I recommend you hold off on this operation if your device is still running 5.0.2 and don't want to upgrade to 5.1.1.
If you want to keep 5.0.2 and still perform this operation than you must use a compatible 5.0.2 Kernel and TWRP - posted below.
WARNING: Because of the engineering bootloader which is 5.0.2 you're going to lose the Fingerprint scanner. If you can live without it then proceed.
Root without tripping Knox and having all the functionality (keeping the Fingerprint scanner working) on 5.1.1 is not possible.
Only for 5.1.1, custom kernel and TWRP for 5.0.2 posted below + also a different method for 5.0.2
1. Download ODIN v 3.10.6 from http://forum.xda-developers.com/showthread.php?t=2711451 and extract it to a folder.
2. Search online/PM me for the engineering bootloader for your device G925F
3. Download the 3 archives from: http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866
3.a.1 TWRP 2.8.7.1 for S6 Edge - https://www.androidfilehost.com/?fid=24052804347765202
3.a.2 TWRP 2.8.7.1 for S6 - https://twrp.me/devices/samsunggalaxys6.html
3.b.1 Unikernel latest version - recommended kernel with so many benefits, now also working with devices that are using the enginnering bootloader (no need for 3.c. if choosing this kernel) - http://forum.xda-developers.com/showthread.php?p=60533128
3.b.2 Alex-V Kernel - works on a G925F that has an engineering bootloader. All the other ones mess with the display in a way that you'll get a white screen with greenish non-understandable ui elements - https://www.androidfilehost.com/?fid=24052804347765201
3.c. Super SU - https://www.androidfilehost.com/?fid=24052804347765203
4. Disable Reactivation lock by going into Settings -> Lock screen and security -> Find My Mobile -> Login with your Samsung Account and then disable Reactivation lock
5. Disable Fingerprint screen lock type by going into Settings -> Lock screen and security -> Screen lock type and select any other screen type than Fingerprint
6. Copy to the your device's sdcard (phone): custom kernel and rest of downloaded files to flash
7. Shut down device and start in Download Mode (with the phone turned off keep pressing on power, volume down and home at the same time until a green screen pops up, then you'll need to press on the volume up key)
8. First you'll need to flash the engineering bootloader. Open ODIN and click on BT and select the appropriate sbin file downloaded at step 2. Flash it and wait for the device to reboot.
Don't be alarmed by the green text that will appear in the top left corner when the Samsung logo is being displayed. It's 100% normal and the device hasn't suffered any damage.
9. Enter Download Mode again and this time in ODIN, go to options and uncheck the Reboot device. Click on AP and select the TWRP 2.8.7.1 and flash it.
10. The device won't reboot because you've unchecked the Reboot device option. You'll need to press on power + volume down + home until the device turns off and then pres on power + volume up + home until you'll see the device enter the TWRP recovery. At that point the buttons can be released.
11. Inside TWRP press on Install and navigate to where you have stored the custom kernel and rest of the files. Select the custom kernel (then add another zip to flash and then select Super SU if using Alex-V kernel). Flash them and reboot your device.
12. Congratulations now you have a rooted G925F with Knox fuse intact!
13. You can now flash anything custom on your device without tripping Knox as long as you don't flash the bootloader with a stock one, you need to keep the engineering bootloader flashed.
If you want to return to stock at anytime you can flash a full stock ROM from Samsung and all should be fine. Knox isn't going to get tripped because everything is returning to stock, even the bootloader.
14. WARNING: Before flashing anything else after you've successfully acquired root you should backup your EFS partition just in case via TWRP recovery.
All credits for rooting and installing TWRP on G925F go to Alex-V, AndreiLux, simple Team, chainfire
The research on which kernel is going to root and work perfectly with a G925F that has an engineering bootloader installed go to me. A lot of trial and error, white & greenish screen, overheat etc...
If you have any questions post below.
Enjoy!
Custom Kernel and TWRP only for 5.0.2 - untested but should work
http://forum.xda-developers.com/galaxy-s6-edge/development/28-04-2015-hybridmax-kernel-t3095373
Different workaroung for making it work for 5.0.2 users
If you're device is running 5.0.2 and it gets stuck on the Samsung screen, in order to fix it you'll need to flashed a stock 5.1.1 ROM then repeat the tutorial and all will work as expected with Knox being intact.
Device on which you can use the following custom ROM tutorial:
G925F 5.1.1 rooted with engineering bootloader
1. Download the 5.1.1 custom ROM you want
2.Download Unikernel or Alex-V's kernel
3.Copy to your device the files downloaded at 1 and 2
4.Boot your device into TWRP (recovery mode)
5.Flash the 5.1.1 custom ROM and the custom kernel. (you can select multiple things to flash one after another without rebooting the device afterwards)
6.After the ROM is flashed you'll need to continue the flashing procedure and not reboot the device until the custom kernel is also flashed
7.After the 2 packages have been flashed successfully you can reboot the device and enjoy your new rooted G925F running a custom ROM, custom Kernel and with your Knox intact.
Enjoy!
WARNING:
If you try to flash any other kernel, one that's not built specifically for G925F like Unikernel or Alex-V's you'll end up with a wrong TSP FW version, one that belongs to G920. Currently the only fix available for this issue is to use a specifically built kernel/stock kernel for G925F.
Here's what you're going to get after flashing any unified kernel (check via *#2663#)
Phone's TSP FW version: ST015681 - incorrect (G920)
Part's TSP FW version: ST0195E4 - correct (G925)
TSP threshold: 512
config tsp fw version: G920_ST_3A1F
tsp checksum data: 1B5C2E4D
Both Phone and Part have to have the same version, the correct one ST0195E4 for G925. If you try to use the TSP FW Update command you will make them both have the G920 TSP FW...so until a solution for this is found we cannot use any unified kernel while running the engineering bootloader.
Latest BOOTLOADER/MODEM/Stock-Kernel Packages for S6 G920F/I/T & S6 Edge G925F/I/T models
http://forum.xda-developers.com/showpost.php?p=60112855&postcount=3
- credit goes to @edgarf28
How to fix cm.bin flash failed - stuck in download mode
http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736
Disclaimer: Proceed with extreme caution as I take no responsibility for any damages to your phone. Do it at your own risk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reserved
Only F? No luck on W8 or A?
Does also engineering boot loader gives ability to reset knox too...?
I know Samsung service center can do it...
Or can we change the model with the engineering bootloader? (Aka switch W8 to F, T to A, others vise versa)
(Looking at HTC all series with S-OFF like god mode)
Sent from my iPad using Tapatalk
ytwytw said:
Only F? No luck on W8 or A?
Does also engineering boot loader gives ability to reset knox too...?
I know Samsung service center can do it...
Or can we change the model with the engineering bootloader? (Aka switch W8 to F, T to A, others vise versa)
(Looking at HTC all series with S-OFF like god mode)
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Unfortunately only F and T have been leaked for both G920 & G925.
I don't know about resetting Knox. I am under the impressing that the Knox Fuse is a psihical hardware one and once it gets burnt there's no way going back.
Haven tried to change the model, I'm guessing you are referring to a deeper change, not only to what's displayed inside the About, which would be pretty hard without deep knowledge of how a Samsung phone knows what model it is.
if it was a fuse it woudnt come on S3/Note2 because these phones were built before knox was even announced, unless they had a spare efuse lying around in the phones just to activate it in near future....
Hey is this a thread to promote Alex´s work? if so its fine, but i found that Aou kernel has a solution for the fingerprint issue on the Tmovile variants over the Unix kernel, am i wrong?
eltoffer said:
Hey is this a thread to promote Alex´s work? if so its fine, but i found that Aou kernel has a solution for the fingerprint issue on the Tmovile variants over the Unix kernel, am i wrong?
Click to expand...
Click to collapse
Yes and no. It promotes the only combination that is available to have a rooted G925F with custom kernel, rom, Knox intact running 5.1.1. Aou is only available for G92xT. I'm not aware of any workaround to fix the fingerprint sensor on 5.1.1 while running on a 5.0.2 engineering bootloader.
pmichaelro said:
How to Root your SM-G925F (International S6 Edge):
If you have any questions post below.
Enjoy!
Click to expand...
Click to collapse
Hi , i really want to try this one and im sure there's people out there willing to know aswell is there anyway you can provide us with screenshot of your phone version / rom and what is your current knox after doing this method ived been searching for an answer (Found only g925t) and i wanna make sure if it does work with F, so im still doing my research properly before attempting this . thank you
Repulsa said:
Hi , i really want to try this one and im sure there's people out there willing to know aswell is there anyway you can provide us with screenshot of your phone version / rom and what is your current knox after doing this method ived been searching for an answer (Found only g925t) and i wanna make sure if it does work with F, so im still doing my research properly before attempting this . thank you
Click to expand...
Click to collapse
Added screenshots
I sent you PM about bootloader you didn't answered me.
slavush said:
I sent you PM about bootloader you didn't answered me.
Click to expand...
Click to collapse
I've checked my PM's and saw that I answered them all. I haven't received any PM from you though. Send me one and I will answer you. Thanks
Hey buddy i know this is a stupid question but i don't know why hehe: if we root, and then flash the OEM sboot.bin and/or kernel we should keep the root, right? but we also recover the fingerprint sensor, or how it works?
eltoffer said:
Hey buddy i know this is a stupid question but i don't know why hehe: if we root, and then flash the OEM sboot.bin and/or kernel we should keep the root, right? but we also recover the fingerprint sensor, or how it works?
Click to expand...
Click to collapse
If you don't want to trip Knox you first have to flash the engineering bootloader, this will make the fingerprint scanner to not work. Then you can flash any custom kernel/rom without tripping knox. If you flash the OEM bootloader but keep anything else custom flashed you will trip Knox. So it's up to you. Keep Knox intact, lose fingerprint scanner, enjoy root and customisation or keep everything stock or don't care about knox and flash anything you want.
pmichaelro said:
If you don't want to trip Knox you first have to flash the engineering bootloader, this will make the fingerprint scanner to not work. Then you can flash any custom kernel/rom without tripping knox. If you flash the OEM bootloader but keep anything else custom flashed you will trip Knox. So it's up to you. Keep Knox intact, lose fingerprint scanner, enjoy root and customisation or keep everything stock or don't care about knox and flash anything you want.
Click to expand...
Click to collapse
Ok thanks for your PM reply, so lets get clear...
if you say fingerprint scanner issue is due to the sboot if i flash the stock 5.1.1 one over the root ONLY (everything else stock), am i going to trip knox? i do not think so, can't see why would it be so
eltoffer said:
Ok thanks for your PM reply, so lets get clear...
if you say fingerprint scanner issue is due to the sboot if i flash the stock 5.1.1 one over the root ONLY (everything else stock), am i going to trip knox? i do not think so, can't see why would it be so
Click to expand...
Click to collapse
I'll explain one more time.
You need to keep the engineering bootloader flashed at all times if you want to flash a custom kernel in order to get root and not trip Knox.
If you flash the engineering bootloader,then the kernel and then flash the stock bootloader back you are going to trip knox because you would be running a custom kernel. Is that more clear now?
pmichaelro said:
I'll explain one more time.
You need to keep the engineering bootloader flashed at all times if you want to flash a custom kernel in order to get root and not trip Knox.
If you flash the engineering bootloader,then the kernel and then flash the stock bootloader back you are going to trip knox because you would be running a custom kernel. Is that more clear now?
Click to expand...
Click to collapse
Ok maybe I explain myself in a wrong way
1.- flash sboot.bin 5.0.2
2.- flash twrp recovery
3.- flash SU.zip
4.- flash back stock recovery 5.1.1 (at this point we achieved root and an intacted Knox)
5.- flash back stock sboot.bin 5.1.1 (so here we recover the fingerprint scanner)
This is the way I think, where is the fail? Sorry if I'm an annoying guy XD
NOTE: I'm only concerning about getting root I don't care about custom roms or so, just root
Enviado desde mi S6 Edge Gold
eltoffer said:
Ok maybe I explain myself in a wrong way
1.- flash sboot.bin 5.0.2
2.- flash twrp recovery
3.- flash SU.zip
4.- flash back stock recovery 5.1.1 (at this point we achieved root and an intacted Knox)
5.- flash back stock sboot.bin 5.1.1 (so here we recover the fingerprint scanner)
This is the way I think, where is the fail? Sorry if I'm an annoying guy XD
NOTE: I'm only concerning about getting root I don't care about custom roms or so, just root
Enviado desde mi S6 Edge Gold
Click to expand...
Click to collapse
You misses a step there. In order to get root you'll need to flash a custom kernel. That's a deal breaker if you want to keep root, knox intact and return to stock bootloader. You simply cannot have this combination.
pmichaelro said:
You misses a step there. In order to get root you'll need to flash a custom kernel. That's a deal breaker if you want to keep root, knox intact and return to stock bootloader. You simply cannot have this combination.
Click to expand...
Click to collapse
Hi i tested this on my s6 edge 5.0.2 stocked rooted rom (pingpong root), I follow the instruction , Got stuck after flashing the bootloader engineering (Green on top).Boot into download mode then i flash the twrp using odin (untick auto reboot) Turn off the device and trying to boot into recovery but to no avail (Power/Volup/home) ,Repeat the process atleast 3 times , Thats ok so i give up I tried flashing the Stock samsung firmware 5.0.2 using odin (Tested 3 times aswell its keep failing cm.bin or .mbn or something in odin ).
There you go No matter how many times i flashed the stock 5.0.2 via odin keep saying cm.bin .. FAIL .. so i had to flashed stocked 5.1.1 samsung firmware in order for the phone to boot but my knox still 0x0 and thats fine . Or i might did something wrong .. anyways no worries i did it before i send it to them to get a new replacement (DPixel) as long its still 0x0 and Thanks...
Repulsa said:
Hi i tested this on my s6 edge 5.0.2 rooted using pingpong , I follow the instruction , Got stuck after flashing the bootloader engineering (Green on top).Boot into download mode then i flash the twrp using odin (untick auto reboot) Turn off the device and trying to boot into recovery but to no avail (Power/Volup/home) ,Repeat the process atleast 3 times , Thats ok so i give up I tried flashing the Stock samsung firmware 5.0.2 using odin (Tested 3 times aswell its keep failing cm.bin or .mbn or something in odin ).
There you go No matter how many times i flashed the stock 5.0.2 via odin keep saying cm .. FAIL .. so i had to flashed stocked 5.1.1 samsung firmware in order for my phone to boot. but my knox still 0x0 and thats fine . Or i might did something wrong .. anyways Ill test it out on 5.1.1 firmware later Thanks tho...
Click to expand...
Click to collapse
This is because you already have 5.1.1 baseband installed, you can't downgrade that IMG
Enviado desde mi S6 Edge Gold
Am I missing something?
I followed every step, and everything was successfull until the point I tried to flash xtroselite, once the flash is done, if the screen goes black i can not get it on anymore, just a white band in top. Any idea?
Thank you in advance.

Categories

Resources