{
"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"
}
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
ZModder said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
what? you didn't do anything. you found a story file talking about fastboot which anyone can radio access by sideloading a android root browser apk.... this has been known since the oculus go first dropped in like 2015....
you need a bootloader unlock code or script which only facebook can give you...it doesnt exist anywhere on the device and is not hidden...
you can try tool "mod" a system file but even if you somehow got the device to bypass the files intregity checks, it wouldnt actually work because you are "sandboxed". any changes you make will not alter system. functions or settings at all until you escape the "sandbox" which can only be done via a unlocked bootloader.
if still you somewhere tricked your device into saving any mods you made to system files, your device either will stop booting the OS or most basic device functions will stop worki g..
so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager.
but fastboot does nothing and adb even too.... what is this? is it any usefull?
raeumler said:
so i tried to go to fastboot mode. but something went wrong (i pressed vol- and vol+ and pwr at bad timing) now the screen is black, no buttons are working, you cant even hold pwr to reset the devices. and it looks like its a bootloader mode. i got this in my devicer manager. View attachment 5628753
but fastboot does nothing and adb even too.... what is this? is it any usefull?
Click to expand...
Click to collapse
That mode is used to flash the device but I doubt you can flash unofficial firmware.
Zillion said:
View attachment 5599971
The only thing to do is to get a kernel exploit or something to turn **get_unlock_ability** into 1 qnd then just unlock the bootloader in fastboot mode.
Sound easy but will not be as it requires editing a root filesystem file.
Click to expand...
Click to collapse
How about the new DirtyCred exploit?
Related
So I'm currently trying to root my S10e (SM-G970F) but I ran into a problem; I can't disable Samsung's VaultKeeper from download mode.
I also noticed that the download mode looks different compared to everything else I've found online. Here's a pic:
{
"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"
}
There is no "extra" text on the left side such as binary info etc.
But the main problem is that I can't disable the VaultKeeper because holding Vol+ for any amount of seconds on download mode doesn't do anything. Vol- also doesn't do anything, neither does the Bixby-button (as expected).
Both of the methods I've used to access the download mode show the same screen.
With adb I've tried: adb reboot bootloader, adb reboot-bootloader, adb reboot download
By first shutting down the phone and opening it by holding Bixby, Vol+ (Vol- has no effect) and the power button. Then selecting "Reboot to bootloader".
And of course before both methods I've made sure that the "OEM unlocking" setting and "USB debugging" are turned on.
I feel lost. Maybe some of you have ran into this same problem? I've already searched around the forum but couldn't find any threads/info that worked for me. Let me know if I possibly missed something.
@meven123123123:
The most common method to enter Download mode is to turn the phone off and then - while holding the Vol- and Bixby buttons - to connect it to the PC via USB cable.
If this doesn't work, you should post some more infos, e.g. the exact device model (is it e.g. the G970F Exynos model which has an unlockable bootloader) and Android version.
okij said:
@meven123123123:
while holding the Vol- and Bixby buttons - to connect it to the PC via USB cable.
Click to expand...
Click to collapse
For some reason I kept thinking that power button needs to be held as well but doing exactly what you said worked!
Big thanks to you! And sorry for my ignorance
@meven123123123: I'm glad that it worked and that I could help!
How exactly did you get the Vaultkeeper mode to show? I also only have two options
Post resolved, turned out that phone was a fake chinese one. No way to unbrick it as there is no known OS to flash it.
--------------------------
Ok, some backstory a friend brought this phone from Peru to Argentina (so I'm assuming it's a SM-A908B global version), seems network wasn't working, so someone tried to "fix" it and sort of bricked it. I said, ok give it to me and I'll just flash an official firmware to bring it back to life. But I can't enter download mode.
-Phone turns on but it's stuck in logo screen (I noticed from some videos that their phone has a 5G after A90)
Spoiler
{
"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"
}
-Turning it off and pressing volume up + volume down and putting usb cable goes to "Factory" (This also happens when powering off and powering on with volume down + power button)
Spoiler
-Volume up + power button goes to this:
Spoiler
Then you can access fastboot and recovery mode
Spoiler
-From recovery menu, "reboot to bootloader" takes you to fastboot, so it's the same as the second option from the previous menu.
-Bonus image from "root integrity check" where we can see that previous person tried to change IMEI and ****ed up
Spoiler
So far I tried:
-A basic wipe data/factory reset, but obviously it didn't work.
-Extracting recovery.img from AP_A908BXXU4CTL3_CL20174301_QB36568574_REV00_user_low_ship_MULTI_CERT_meta_OS10.tar (and extracting from lz4) and flashing it via fastboot, but it fails as it says it doesn't have permission to flash recovery.
-The same with System.img extracted from the AP file, but fastboot flash just fails (I could try to do this via adb in recovery, but I would like a second opinion here).
Any help would be very welcomed. How to get access to download mode to flash an official firmware, or how to flash a odin firmware via recovery mode (I tried searching for this but couldn't find much).
What happened for this to report modified file ??
Are you asking about the log of "root integrity check"? I don't know what the previous person tried to do with the phone, probably tried to root it and failed. Looks like some system files were modified
@Zero.G
Use Samsung ODIN to fix phone.
jwoegerbauer said:
@Zero.G
Use Samsung ODIN to fix phone.
Click to expand...
Click to collapse
Of course, that IS my idea, but i can't use odin because i can't enter download mode
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
speedmetal444 said:
When I use "fastboot reboot fastboot" command it only reboots and turns on the phone.
I want to try install a GSI rom but I can't get into it.. Is there a way to make it happen?
Am I wrong trying to install it this way? I was reading some forums and I tried a few things without results.
Click to expand...
Click to collapse
Try this:
First reboot to recovery, once you're there select reboot to bootloader, then press and hold VOL UP while it's rebooting, after that voila your now on Fastboot mode.
{
"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"
}
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
speedmetal444 said:
Thx for your reply! And sorry for my poor explanation about the problem, I know how to get into fastboot mode but there is another instance of it, and its fastbootD mode that allows you to make modifications on the dynamic partition called "super", the suposed way to get into it is typing the command "fastboot reboot fastboot" in the normal fastboot mode, but nothing happens, the phone just reboots into normal system.
When I try to erase system in normal fastboot mode it cannot find that partition cause this is in super, it will be great if we can experiment with that but Im stuck right now...
I dont know if this worth it.... Any of you already tried a GSI rom?
Click to expand...
Click to collapse
Yes, but unfortunately their SW REV was just 0, but by device’s one is always 1 (i.e. too high for TWRP and GSI’s atm)
(* Samsung blocks SW REV downgrades at all, the only way to bypass is to run the below for not waiting)
Now it needs waits, or if you don’t wait, you instead need to shut MTK ‘‘secure’’ boot and ‘‘secure’’ Download off at all.
Helix-one said:
View attachment 5299239
Click to expand...
Click to collapse
Are you going to flash TWRP by ADB sideloads on the A12's Recovery mode? If yes, good luck!
With the help of @sd_shadow I managed to install OFFICIAL FIRMWARE using manual FASTBOOT only.
Now I need copy of STOCK RECOVERY IMAGE & Fastboot command to install it. Thanks in advance.
austin_dreq said:
With the help of @sd_shadow I managed to install OFFICIAL FIRMWARE using manual FASTBOOT only.
Now I need copy of STOCK RECOVERY IMAGE & Fastboot command to install it. Thanks in advance.
Click to expand...
Click to collapse
Stock Recovery is part of Boot partition (boot.img) on most devices with a/b systems
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
sd_shadow said:
Stock Recovery is part of Boot partition (boot.img) on most devices with a/b systems
How A/B Partitions and Seamless Updates Affect Custom Development on XDA
You may have heard of Seamless Updates before. It involves something called "A/B partitions." What is it and how does it affect custom development on XDA?
www.xda-developers.com
Click to expand...
Click to collapse
Oh thanks... But I cannot enter recovery mode?
I remember my phone can with unlocked bootloader. In recovery I restored and it was locked but not updating (Mar security Japan region)... Then I explored August updated ROMs...
Any suggestion how to lock bootloader again?
{
"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"
}
Recovery from Fastboot mode (up - up - power)... Nothing
austin_dreq said:
View attachment 5401873Recovery from Fastboot mode (up - up - power)... Nothing
Click to expand...
Click to collapse
That's recovery
@ that screen hold power button and tap volume up button
Charge your battery 30% or more.
Turn off the phone.
Press and hold the Volume Down button and the Power button at the same time until the phone turns on.
Press the Volume Down button until you see Recovery mode.
Press the Power button to restart in Recovery mode.
If you see an Android robot with a red exclamation mark, press and hold the Power button and, while holding it down, press and release the Volume up button.
Reset my phone| Motorola Support ROE
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.[[ANSWERSUMMARY]]
motorola-global-en-roe.custhelp.com
I got a pixel4a phone, but the startup screen looks like a factory mode screen. how can i remove this screen, thanks a lot
{
"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"
}
that's not a lot of info to go by. what did you do prior to getting this screen? since when has this screen been showing? is it rooted? did you do low level stuff with it, and if so, did you do it through a computer or on the phone directly?
the first thing you would want to do is to check if you can enter recovery mode (stock will do if you don't have an aftermarket) and see if you can do something with that, like, say; factory reset.
the next thing you could try is to first backup your flash, and I mean from sector 0 to EOF, and a second backup per partition, then flash a stock rom you could get online.
I WOULD preffer to just diagnose the problem and fix it non-destructively but phones and their OSes are not built to accomodate repair beyond changing the screen/batery and resetting/flasing the ROM
P.S. throw in the chipset type while you're at it I.E. MTK or QLM
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
1. Enable ADB ( AKA USB Debugging ) on phone
2. Connect computer and phone via USB-cable
3. On computer run ADB command
Code:
adb reboot
oldmaize said:
Thank you for your response, bro! This phone is a second-hand phone. When I received it, it only had the factory mode. I flashed Android 11 through the website flash.android.com, but every time I boot up the phone, the screen will display for a few seconds before entering the system. I searched online and it seems that the phone is still in factory mode and needs to be activated to normal mode, but I haven't found a way to switch to normal mode.
Click to expand...
Click to collapse
well, taht just sounds like the ROM didn't come with a boot animation/logo so I suggest if you want one you can well... there's not much you can do without tripping tamper triggers I.E. install rootkit & modify system partition (can't be done post pie) or unpack system image, insert the animation/logo and repack, but then you have an orange state device and that's not much better than that factory logo, or you lock it without image verification enabled and hope that something doesn't rely on it
android isn't built to be moded, so you have to mod it before building an hoo boy is that a wild ride
P.S. on second read, the ROM might be in eng mode instead of userdebug or user
you could check it by either terminal emulator, issueing the command `getprop` and search for build variant or do so through adb