Related
Multiple Tool Flash Recovery Check and unlock Bootloader
Download unzip somewhere inside PC and run with double click the Recovery-Tool.bat .
Follow instructions and check Bootloader Unlock *flash TWRP or Stock Recovery etc. Try it with your own responsibility.
Alternative you can put new TWRPS inside phone and Flash them through there as image files.
https://drive.google.com/file/d/1O3BgtajkXBT43pQBn66LeJ45G7tb_f5_/view?usp=sharing
Great ¡¡¡
Many thanks
Unlock stock 26s too?
dakok said:
Unlock stock 26s too?
Click to expand...
Click to collapse
Not yet..in the future..
senks bro
what does this do? And what does it mean for useage?
gaatjesprikker said:
what does this do? And what does it mean for useage?
Click to expand...
Click to collapse
Because I realized that you don't know.. so...with check bootloader tool you find out if your bootloader is locked or unlocked and you could proceed with safety to flash custom recovery to have the full abilities of this phone at your hands. Because if you try to flash any other Rom with locked bootloader you can have a full brick. And the second is that you have the power to choose between 2 recovery's or to flash back with 2 click's the official Stock recovery to have it if and when some Nougat or else Rom came out.
Doesn't work
Good day! Tried your program on my phone (5.8.020S, bought at jd.com) - doesn't work. USB debugging is on. Phone turned on in fastboot mode.
As a new user I can't post links to screenshots, may be I will send you a private message?
voldemaar said:
Good day! Tried your program on my phone (5.8.020S, bought at jd.com) - doesn't work. USB debugging is on. Phone turned on in fastboot mode.
As a new user I can't post links to screenshots, may be I will send you a private message?
Click to expand...
Click to collapse
Nothing is wrong. You just have locked your bootloader without permission to unlock. Did you put 26s with TWRP? THAT'S WHY. You must have stock locked allowed bootloader for unlock.
Great work !
Everything working well !
f2fs
If it possible to made f2fs working in recovery?
LordGiborg said:
If it possible to made f2fs working in recovery?
Click to expand...
Click to collapse
Search at BBS.le I think there is a custom with f2fs support.
CrisBalGreece said:
Search at BBS.le I think there is a custom with f2fs support.
Click to expand...
Click to collapse
Thx for your advise.
But it's really hard to find something there, and page loading sooooooooooo slow...
Thread closed on OP's request
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
thanks, it worked for me. appreciate.
Your welcome.
What did u even use to root?
What build is this for?
It works with me....Thank you so much.
this works also on 320fn?
fraizzo said:
this works also on 320fn?
Click to expand...
Click to collapse
Sadly not
JustAnotherAndroid said:
What did u even use to root?
Click to expand...
Click to collapse
I used magisk
Sands207 said:
What build is this for?
Click to expand...
Click to collapse
I don't remember
Is this process can unlock the phone from sprint ?
No, call sprint, then ask to unlock
crimsonrommer said:
If you Have accidentally disabled Developer options and your phone was rooted, you probably went into a bootloop, and you think the only solution is a full odin restore, bu thats not true, there is an odin flashable package that allows you to bypass the FRP custom image block message and lets you boot into the os, from there enable oem unlocking, and reroot your device with supersu. I will attach the odin flashable below for those who need it.
Click to expand...
Click to collapse
Simply turning off usb debugging will not throw your phone into a boot loop normally unless ou had some bad hardware or custom settings.. Only time ive seen that happen is by using data from other models. Easy way to get past it is to just take out your battery for a bit, replace it then boot into upload mode. Next youll have to try various combos releasing the buttons and presing again quickly to get back to the download mode. Alternatively boot into TWRP/STock recovery, use AT+ Commands or use a application that will boot back.
Awesome you found a little trick to simplify it ! Keep it up!
EDIT: Ohh i see.. you are on a custom rom / binary? I still have yet to have this happen but to a J700 with SynexOS on it.. Ill give this a try.
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Andriano24 said:
This is kind of storytime... I got the application by redeeming a code that was posted as a gift on their fanpage at Facebook. I had to sent them via Telegram the Google play ID order, something that I couldn't find. I explained that and they understood me and said that if I could send the code that I got the application, they are gonna send be the actual files. So I received the files and I'm ready to begin! I don't have much spare time so I'm gonna do this whenever I have the time to do so. Wish me luck! I'm gonna keep you guys updated and let you know what happened.
Click to expand...
Click to collapse
knox to 0x0?
DaniPS2002 said:
knox to 0x0?
Click to expand...
Click to collapse
Yeah that's what the app suppose to do
Andriano24 said:
Yeah that's what the app suppose to do
Click to expand...
Click to collapse
the app name is knox reset 0x0 (0)?
DaniPS2002 said:
the app name is knox reset 0x0 (0)?
Click to expand...
Click to collapse
Yes
Okay, let we know!
MarcusBS said:
Okay, let we know!
Click to expand...
Click to collapse
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Andriano24 said:
I've stuck in a step. Sadly I cannot complete now the instructions given because I can't turn the systemless root into system mode
Click to expand...
Click to collapse
What do you mean you can't turn systemless root into system mode?
ashyx said:
What do you mean you can't turn systemless root into system mode?
Click to expand...
Click to collapse
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Andriano24 said:
https://android.stackexchange.com/q...om-systemless-root-to-system-traditional-root
Check that out
Click to expand...
Click to collapse
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
ashyx said:
I actually meant what is preventing you from installing supersu in system mode, it's simple enough? Also which device is this?
Click to expand...
Click to collapse
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Andriano24 said:
I flash the super su, then try to full unroot, my phone reboots and I press the combination of keys to go to twrp recovery, go to terminal thingy, type the code and the last step I do is flashing again the supersu. But then I boot into system I stuck on the logo screen
Click to expand...
Click to collapse
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
ashyx said:
You've lost me Tbh. I don't understand what steps you are performing and why.
Type what code?
Click to expand...
Click to collapse
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Andriano24 said:
Didn't you see the post I send you? The "code" is
Echo SYSTEMLESS=false > /data/.supersu
Click to expand...
Click to collapse
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
[Deleted by me]
ashyx said:
OK first things first. You have to reinstall SuperSu for that code to work AND a patched boot.img.
Second for what reason do you need SuperSU to be in system mode?
Click to expand...
Click to collapse
Thank you for your time. But can you wrote the full steps below? Because I'm tired of getting into a bootloop only because I am not able to understand the instructions! You can do it only of you want to!
Secondary, the Knox Reset app has a plugin to make the success rate bigger of turning the 0x1 back to 0x0 (as far as I know) and the plugin needs system mode root :/
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Andriano24 said:
Lol right now I'm not rooted because I'm tired of the bootloops while rying to system mode root
Click to expand...
Click to collapse
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
ashyx said:
Easiest way is to reroot systemless. After rooting back up the boot partition with TWRP.
Unroot then install SuperSU in system mode.
Finally restore the boot.img from the backup.
Reboot.
Note also be aware that system mode root is hit and miss on devices running nougat.
You still haven't stated which device?
Click to expand...
Click to collapse
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Andriano24 said:
Oh sorry I forgot about that! I have the Samsung galaxy A5 2017 running...... nougat.....
Click to expand...
Click to collapse
Then you have a 50/50 chance of root working in system mode.
Also tbh I think this knox app is fake or it just fakes knox to 0x0 the same way Magisk can.
hey guys I have a SM-g965f and 960F, I'm trying to see if the bootloader will let me install twrp after 7 days
imgur.com/a/9cBiSEQ
please help thank you!
Those screenshots dont mean anything.if you have oem unlock option, when you dont go into odin mode as soon as you press factory reset button you will have to wait another 7 days.
Sent from my Galaxy S9+ using XDA Labs
gsser said:
Those screenshots dont mean anything.if you have oem unlock option, when you dont go into odin mode as soon as you press factory reset button you will have to wait another 7 days.
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
ok so my S9 did pop that earlier today, when I hit it, it ask for my phone to be reset, which I did, when I boot back into download mode, it says OEM unlock off but prenormal mode is still on?
S9ROOT said:
ok so my S9 did pop that earlier today, when I hit it, it ask for my phone to be reset, which I did, when I boot back into download mode, it says OEM unlock off but prenormal mode is still on?
Click to expand...
Click to collapse
Then you have to keep your device on 168 hours again like i am doing...
Sent from my Galaxy S9+ using XDA Labs
gsser said:
Then you have to keep your device on 168 hours again like i am doing...
Sent from my Galaxy S9+ using XDA Labs
Click to expand...
Click to collapse
the problem is, when that prenormal state is off, can you flash a custom binary? because from what I have seen, samsung lock it down pretty hard now, but I cant find a definite answer that you can flash after 7 days.}
I have no problem waiting, but I just want to know if there are peopel out there with the upgraded bootloader can still custom recovery, due to this new implementation, it seems like if its not an official binary from Samsung you cant flash anything at all. OEM unlock is just to unlock the phone without utilizing your email.
S9ROOT said:
the problem is, when that prenormal state is off, can you flash a custom binary? because from what I have seen, samsung lock it down pretty hard now, but I cant find a definite answer that you can flash after 7 days.}
I have no problem waiting, but I just want to know if there are peopel out there with the upgraded bootloader can still custom recovery, due to this new implementation, it seems like if its not an official binary from Samsung you cant flash anything at all. OEM unlock is just to unlock the phone without utilizing your email.
Click to expand...
Click to collapse
like i said it will be useless in pie because there are no custom binaries(TWRP) for pie.
it is most likely will be done with oreo firmware. There is no point of waiting for rmm state normal in pie. if you have a pie compatible custom recovery then fiine you can wait but we dont have pie compatible recovery(as far as i know).
Like i said before i have waited 7 days after i enabled oem unlock in pie, after the reset i waited 7 days more but rmm state didnt went to normal state.
gsser said:
like i said it will be useless in pie because there are no custom binaries(TWRP) for pie.
it is most likely will be done with oreo firmware. There is no point of waiting for rmm state normal in pie. if you have a pie compatible custom recovery then fiine you can wait but we dont have pie compatible recovery(as far as i know).
Like i said before i have waited 7 days after i enabled oem unlock in pie, after the reset i waited 7 days more but rmm state didnt went to normal state.
Click to expand...
Click to collapse
you are not making sense right now, I am not in android 9 Pie, I am still in oreo.
S9ROOT said:
you are not making sense right now, I am not in android 9 Pie, I am still in oreo.
Click to expand...
Click to collapse
Edit, got confused over some threads sorry. I am on 60 hours, still no oem unlock toggle appeared. We can only ask who had to wait after toggling oem unlock on.
Overall, gotta wait 7 more days for rmm state, no promises but nothing else to do... until then no custom binary can be flashed
Bootloader lock and account frp is off but rmm is blocking custom binaries, so when you have rmm state normal, you will be able to flash twrp.
Sent from my Galaxy S9+ using XDA Labs
dang I wish somebody has the answer to this....someone gotta done this before.
S9ROOT said:
dang I wish somebody has the answer to this....someone gotta done this before.
Click to expand...
Click to collapse
1 week wait is understandable but after factory reset is just bull****. Literally they are making anything they can to prevent roms and kernels...
Sent from my Galaxy S9+ using XDA Labs
Samsung Galaxy Tab A7 Lite was distributed by our state government for promoting technology in the state. (JUST ELECTION THINGS)
Anyways, the Tabs are coming with Samsung Knox security which cannot be uninstalled, disabled, debloated with adb. The Tabs also come with restrictions by software to change wallpaper of lockscreen / homescreen and probably many other restrictions. (tracking and other stuffs) ALTHOUGH I MANAGED TO REMOVE THE WALLPAPER RESTRICTION (Screenshot attached) The Tab also comes with a work profile already by Govt.
The problem is that if you try to unlock the bootloader you can't boot by to the system because of the policies enrolled with the each device specifically. As of now i couldn't find any TWRP or any Custom ROM to flash and fix those things or ROOT or at least try to. Please hit me up if any development comes for the same.
[ THIS IS A TUTORIAL TO BRING BACK THE TAB TO YOUR OLD STATE ]
Now on to the steps to fix :
STEPS :
1. Lock bootloader by going to download mode (turn off the device, press both vol keys and connect USB untill the blue screen (download mode) pops up), then follow the menu.
2. Flash stock Firmware. After booting setup as usual and that's it. You should be back to your original state.
3. Force reboot to stock recovery and format data/erase data after flashing stock firware. (this setp is IMP if the step 1&2 didn't work alone)
Enjoy YogiJi's Smile FACE
LINKS :
Firmware [ SM-T225_INS_T225XXU1AUI3 ]
ODIN
Samsung Drivers
My bootloader is probably locked coz the download mode does say OEM lock on
However even after flashing it with the stock firmwares I tried AUI3 and AUJ1 for the Indian region still can't seem to get past that issue
-_-
Yup flashed again and still the same
Insomniac05 said:
Yup flashed again and still the same
Click to expand...
Click to collapse
lock your bootloader again OEM
AddictedA1 said:
lock your bootloader again OEM
Click to expand...
Click to collapse
Again? How? like it's locked already I don't get the option to open the boot lock menu in the download mode nor the pop up saying that it is unlocked
Insomniac05 said:
Again? How? like it's locked already I don't get the option to open the boot lock menu in the download mode nor the pop up saying that it is unlocked
Click to expand...
Click to collapse
knox saying cant create profile means its detected OEM unlocked so... poweroff hold volume up+down then plugin cable after few sec warning appear second option press volume up longer then lock bootloder option will come..... again boot enjoy yogi n F privacy
AddictedA1 said:
knox saying cant create profile means its detected OEM unlocked so... poweroff hold volume up+down then plugin cable after few sec warning appear second option press volume up longer then lock bootloder option will come..... again boot enjoy yogi n F privacy
Click to expand...
Click to collapse
I don't have that option to press the volume up button longer and go into the boot lock menu coz the loader is already locked as shown in the download mode
Insomniac05 said:
I don't have that option to press the volume up button longer and go into the boot lock menu coz the loader is already locked as shown in the download mode
Click to expand...
Click to collapse
If your bootloader is locked (Be sure) then perform a factory reset once, via stock recovery. That should solve your issue.
For further help you can text me on TG - https://t.me/fastboot_boot_life
Insomniac05 said:
My bootloader is probably locked coz the download mode does say OEM lock on
However even after flashing it with the stock firmwares I tried AUI3 and AUJ1 for the Indian region still can't seem to get past that issue
Click to expand...
Click to collapse
buddy sorry to be a bearer of bad news but your warranty is void (CHECK WARRANTY VOID 0X01), knox is preventing you from booting up. It can't be fixed by installing stock firmware. Either go to service centre (they might not accept the device due to its warranty status but if there is a way then they might take cash to fix it)
else wait for some other firmware and twrp. that's the only way
alp47470 said:
If your bootloader is locked (Be sure) then perform a factory reset once, via stock recovery. That should solve your issue.
For further help you can text me on TG - https://t.me/fastboot_boot_life
Click to expand...
Click to collapse
have you ever tried flashing stock firmware to your device?
starkprime74 said:
have you ever tried flashing stock firmware to your device?
Click to expand...
Click to collapse
It show warranty void etc in mine too after i unlocked bootloader probably because it's samsung's policy unlike other brands like OnePlus. After flashing stock fw and a factory reset via stock recovery you can boot back to previous state. Factory reset is important because because just locking the bootloader isn't completing wiping out system and when you boot back you can see previous WiFi already connected. That's why factory reset via recovery is important.
Insomniac05 said:
I don't have that option to press the volume up button longer and go into the boot lock menu coz the loader is already locked as shown in the download mode
Click to expand...
Click to collapse
Fixed now??
alp47470 said:
Fixed now??
Click to expand...
Click to collapse
Nope unfortunately not
Here's what I did
Reset the device
Entered Download Mode (bootloader is locked for sure)
Flashed using Odin
Reset the device again
And still the same
Also did ur issue just start coz of unlocking?? I did flash a magisk patched AP as well
Insomniac05 said:
Nope unfortunately not
Here's what I did
Reset the device
Entered Download Mode (bootloader is locked for sure)
Flashed using Odin
Reset the device again
And still the same
Also did ur issue just start coz of unlocking?? I did flash a magisk patched AP as well
Click to expand...
Click to collapse
Bro. Why aren't you doing a factory reset AFTER flashing stock FW? Factory reset after flashing stock is IMP. Check OP instructions
alp47470 said:
Bro. Why aren't you doing a factory reset AFTER flashing stock FW? Factory reset after flashing stock is IMP. Check OP instructions
Click to expand...
Click to collapse
I did man
I even wrote "Reset the device again" after "Flashed using Odin"
Insomniac05 said:
Nope unfortunately not
Here's what I did
Reset the device
Entered Download Mode (bootloader is locked for sure)
Flashed using Odin
Reset the device again
And still the same
Also did ur issue just start coz of unlocking?? I did flash a magisk patched AP as well
Click to expand...
Click to collapse
Yes my issue began right after unlocking which was easily reversed once I locked the loader.
In your case you flashed a custom rom which caused the Knox to trip and thus causing further issue.
Insomniac05 said:
I did man
I even wrote "Reset the device again" after "Flashed using Odin"
Click to expand...
Click to collapse
were you able to fix this?
nitinvaid said:
were you able to fix this?
Click to expand...
Click to collapse
Yes I was check the post on removing knox
Insomniac05 said:
Yes I was check the post on removing knox
Click to expand...
Click to collapse
where is it? and will it work on S21-Ultra