Database Users

[Solved!!!]Cant get out of bootloop! - stock rooted.

Hi Everyone.
Ok, So my phone was on Stock MJ1, Rooted with Kingo (Knox 0x0) and I had Xposed tweaks. (Its the 900W8)
I was screwing with the BUILD.PROP file and changed the value of dalvik.vm.heapgrowthlimit=128m to 124
Now I have a bootloop!
Please help!
Is there a way to re-insert a backup of my build.prop file into root? Maybe with ADB or something?
I dont want to wipe my phone or trip knox and I dont know what to do.
Im completely stuck.

JF-GINO said:
Hi Everyone.
Ok, So my phone was on Stock MJ1, Rooted with Kingo (Knox 0x0) and I had Xposed tweaks. (Its the 900W8)
I was screwing with the BUILD.PROP file and changed the value of dalvik.vm.heapgrowthlimit=128m to 124
Now I have a bootloop!
Please help!
Is there a way to re-insert a backup of my build.prop file into root? Maybe with ADB or something?
I dont want to wipe my phone or trip knox and I dont know what to do.
Im completely stuck.
Click to expand...
Click to collapse
You are basically hosed. You will have flash a stock system.img and cache.img.
ADB won't be active in a bootloop.

You could try flashing a zip with just the right build.prop in it. I don't know if and how that's possible though, but I think it is.

designgears said:
You are basically hosed. You will have flash a stock system.img and cache.img.
ADB won't be active in a bootloop.
Click to expand...
Click to collapse
Is it possible to flash the original build.prop using the stock recovery like Macbreq suggested?
If not, then if i trip my knox and put cwm on it could i flash it them or is my cache damaged too much to boot?
If i can only recover the way you suggested, how do i do this?

Put it in download mode and flash MJ1 stock rom with ODIN...
You shouldn't loose all your stuff and it will just need to be rooted again... Easy...

ultramag69 said:
Put it in download mode and flash MJ1 stock rom with ODIN...
You shouldn't loose all your stuff and it will just need to be rooted again... Easy...
Click to expand...
Click to collapse
I dont know my full CSC code,..Where can I find Stock (rogers) MJ1 without this? I think from memory its RWC-N900W8VLUBMJ1.....Does it matter?
Will this also trip my Knox?

JF-GINO said:
I dont know my full CSC code,..Where can I find Stock (rogers) MJ1 without this? I think from memory its RWC-N900W8VLUBMJ1.....Does it matter?
Will this also trip my Knox?
Click to expand...
Click to collapse
OK, if its stock go to recovery mode. It will tell you your CSC code at the bottom of the screen...
Then try sammobile.com to find your stock rom.If you can't find there you might have to try searching further afield but I don't know where, sammobile generally has what I want.
If you can't find any way to do this you may need to do an emergency firmware recovery by Kies 3 BUT you will loose all data... You will have a working phone though. Just remember that Kies 3 will upgrade to the latest firmware thats out so if you have root and an old bootloader and a new firmware is out with the anti-root firmware you will trigger Knox to get root back...

ultramag69 said:
OK, if its stock go to recovery mode. It will tell you your CSC code at the bottom of the screen...
Then try sammobile.com to find your stock rom.If you can't find there you might have to try searching further afield but I don't know where, sammobile generally has what I want.
If you can't find any way to do this you may need to do an emergency firmware recovery by Kies 3 BUT you will loose all data... You will have a working phone though. Just remember that Kies 3 will upgrade to the latest firmware thats out so if you have root and an old bootloader and a new firmware is out with the anti-root firmware you will trigger Knox to get root back...
Click to expand...
Click to collapse
Thanks, The Csc code says: RWC so I guess I can use any RWC MJ1 firmware...
BTW, I dont know if its just samsung, but can I not just flash my old build.prop using stock recovery?
It also gives an Apply update from ADB in recovery... Is it possible without reflashing this way?

JF-GINO said:
Thanks, The Csc code says: RWC so I guess I can use any RWC MJ1 firmware...
BTW, I dont know if its just samsung, but can I not just flash my old build.prop using stock recovery?
It also gives an Apply update from ADB in recovery... Is it possible without reflashing this way?
Click to expand...
Click to collapse
I wouldn't, any thing goes wrong its likelier to trigger Knox, especially as you are playing around with download mode. Personally I'd just reflash the firmware and move on from there...

ultramag69 said:
I wouldn't, any thing goes wrong its likelier to trigger Knox, especially as you are playing around with download mode. Personally I'd just reflash the firmware and move on from there...
Click to expand...
Click to collapse
Thank you! I did exactly what you said and you where 100% correct.
Just in case anyone suffers a bootloop from screwing around, this is a perfect solution.
I found my Stock firmware from here :
http://samsung-updates.com/device/?id=SM-N900W8
I Flashed it and everything booted without tripping knox and my stuff was all intact! It just put stock overtop.
All I had to do was re-root, re-install my mods and delete the bloat again... 20min later I was back where I started.
If anyone wants a tutorial on how to do this this, go here:
http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Thanks again everyone, especially ultramag69

JF-GINO said:
Thank you! I did exactly what you said and you where 100% correct.
Just in case anyone suffers a bootloop from screwing around, this is a perfect solution.
I found my Stock firmware from here :
http://samsung-updates.com/device/?id=SM-N900W8
I Flashed it and everything booted without tripping knox and my stuff was all intact! It just put stock overtop.
All I had to do was re-root, re-install my mods and delete the bloat again... 20min later I was back where I started.
If anyone wants a tutorial on how to do this this, go here:
http://www.droidviews.com/how-to-install-restore-stock-firmware-on-samsung-galaxy-note-3-all-models/
Thanks again everyone, especially ultramag69
Click to expand...
Click to collapse
No problem, glad to help :good:

[Q] boot failure, logo stuck.

Hey guys, i will go direct into topic
i have note 2 n7100
1- i made a factory reset from settings menu on phone then the mobile didn't load again (stuck into logo)
2- tried all recovery ROM with all methods and no luck.
3- Downloaded and installed official ROM from SAMMOBILE and the mobile loaded and worked.
4- Installed a custom ROM.
5- Made a wipe to go back for the official ROM again and starting from here everything went bad..
my mobile didn't accept any ROMS, recovery or anything.
just rebooted and stuck on Samsung logo
i tried many things for 3 days but no luck.
Please HELP.
-----
-----
EDIT:
i know that wiping from recovery mode might solve the problem ,, but i don't have access to recovery mode. i have access to download mode. and sure i tried MANY times to flash recovery roms with ODIN and no luck.

Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk

sufiyankatra said:
Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
rom of what ?
CWM is a recovery and i said that all of recovery roms were failed.

probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk

monteiro-ribas said:
probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk
Click to expand...
Click to collapse
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo

siimoz said:
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo
Click to expand...
Click to collapse
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?

EmptyArea said:
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?
Click to expand...
Click to collapse
There's no recovery enabled
i tried to flash (philz , twrp2 and cmw 2 ) none of them is booting.

So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A

EmptyArea said:
So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A
Click to expand...
Click to collapse
here it is:
ODIN MODE
Product name: GT-N7100
CUSTOM BINARY DOWNLOAD: YES (12 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
RP SWREV: A2

So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/

EmptyArea said:
So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/
Click to expand...
Click to collapse
Thank you for your help, i am downloading a different stock ROM now.
but can you please tell me more about that downgrading thing?

I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.

EmptyArea said:
I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.
Click to expand...
Click to collapse
still.. i don't know how to make the Custom recovery work! as you see in the boot loader i tried to flash 12 times and nothing happened.

And you've tried flashing a full stock 4.3 rom from Sammobile right? Running odin as win XP (if on 7)

SM-N910U Recovery Image NK7

Hello,
I recently flashed CWM for my device but had Reactivation lock on so I cannot boot my device because the binary counter is custom. I think if I flashed the stock recovery.img (NK7 build) I should be fine and wont lose any of my info on my phone. Is this the case and if so anyone know of any faster downloads than sam mobile?

I though Knox counter was only for guarranty purposes, didnt know it could block your device
Sent from my Galaxy NOTE 4

Well lesson learned, DONT KEEP reactivation lock set to on. I was only able to find a MD5 file for the whole restore, though I may be able to break it up.

Was able to fix it by extracting the tar.md5 file, but my device is trying to boot into recovery and that wont work because there is something wrong with chainfire's root method. My recovery will never load and at this point I dont think I can flash a custom one, full restore is only option. If that works...fingers crossed.

final fix was just doing full odin restore....weird I kept all of my data?

zhable said:
Well lesson learned, DONT KEEP reactivation lock set to on. I was only able to find a MD5 file for the whole restore, though I may be able to break it up.
Click to expand...
Click to collapse
Where is the reactivation lock?

Ita under settings -> security -> reactivation lock. Note i was able to flash the stock recovery.img but due to something with chainfires root method it messes up stock recovery. So i was stuck in a recovery bootloop.

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

Cant boot, cant eneter recovery after flashing TWRP

hello everyone, my galaxy s8 was on stock rom, it was rooted with odin and super su, i made a mistake....
i installed twrp and wanted to flash it, it said that that it all flashed correctly, when i rebooted the phone it got stuck on the galaxy s8 logo, wont turn off and wont enter recovery mode, only thing i can do is enter download mode.
i tried to do whats written in this topic:
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
im not 100% sure of my firmware version, its the one that came out with galaxy s8 when it launched 6.1 or 7.1
so i download the BL file to use it in odin, i tried the 1AQF7 and 1AQG7 also 1AGDG...
nothing helps, whenever i enter download mode and press START on odin with BL file added and straight away after pressing start hold down the volume down, plus bixby plus power i get the writing in odin NAND write start, i can never get beyond that, does that mean no matter how fast i try pressing all 3 buttons down, bixby and power i will never be able to fix the boot? or am i to slow?
can i push the needed file to fix the bootloader with ADB?
what else can i do now? is it anyhow possible to fix the boot, or if not to somehow please recover the data and transfer it to my pc memory? and start from scratch again with the phone as a last solution.
thank you all so much for your help in advance, been trying all day to fix it with odin, but no luck.
when i enter download mode this is written on my screen, maybe it helps:
odin mode
download speed:fast
product name: sm-g950f
current binary: custom
system status: custom
fap lock: off
oem lock: off
secure download: enabled
CCIC=S2MM005 hw: 6 boot 7 main:35
WARRANTY VOID 1 (0x0500)
RP SWREV: B:1 K:1 S:1
DID =0077ce53b1c2
EVT 1.1
LOT_ID=NBV09
rest is chip id etc which i think cant help anything.
thank you all once more

can someone please give me any help to boot back into android or recovery or recover my files ?

drazenm said:
can someone please give me any help to boot back into android or recovery or recover my files ?
Click to expand...
Click to collapse
i do not think you will b able to recover or boot back into android but you should be able to flash an official firmware using odin to get your phone up and running again.
you should always back up important stuff on your phone before attempting any flashing

How about using Odin to 'dirty' flash the exact firmware last working on your phone? For "dirty", I meant flashing home_csc which doesn't force a data wipe.

ikeny said:
How about using Odin to 'dirty' flash the exact firmware last working on your phone? For "dirty", I meant flashing home_csc which doesn't force a data wipe.
Click to expand...
Click to collapse
i have nothing to loose, how can i perform that? i think i know the firmware that ive used, but if i dont how can i be sure which one ive used ?
thank you .

if anyone can help/explain, so i know if i can do anything or i will have to wipe my phone

drazenm said:
i have nothing to loose, how can i perform that? i think i know the firmware that ive used, but if i dont how can i be sure which one ive used ?
thank you .
Click to expand...
Click to collapse
Go to sammobile.com, search firmware by country and carrier.

ikeny said:
Go to sammobile.com, search firmware by country and carrier.
Click to expand...
Click to collapse
i downloaded the firmware that i think i used, and i also downloaded the newest one. so what do i do now ?

drazenm said:
i downloaded the firmware that i think i used, and i also downloaded the newest one. so what do i do now ?
Click to expand...
Click to collapse
Google - how to flash firmware with Odin.

ikeny said:
Google - how to flash firmware with Odin.
Click to expand...
Click to collapse
i know how to flash firmware with odin but how am i to do it to repair my current firmware or patch it up as you have said?
so i dont overwrite and loose ma data?
thank you

I have issue too. I flash custom binary and bootloader don't allow boot to recovery via hard buttons. Now I boot to recovery via computer or rooted rom.