Database Info

[Q] code name android ics fastboot issue

hey guys, the issue I am having is that I am trying to side load rom manager touch but when I enter fastboot reboot bootloader it just says waiting for device. everything worked fine while running GB but now this. I also tried booting into fastboot and running the command, but still nothing. I downloaded the latest version of pda net. dont know if that makes a difference. also usb debugging is selected in developers options. any ideas?

Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk

gm` said:
Is ur phone in recovery mode? If not u need to turned off and hold power + volume up then try to flash it
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.

Yes u can via flashboot.
Flashboot recovery newrecovery.img
Sent from my Nexus S using Tapatalk

CaptEvo said:
Can you flash a .img file? I haven't tried that. But this still doesn't answer the question why fastboot commands or adb doesn't respond with this rom.
Click to expand...
Click to collapse
Because is not in fastboot mode
Sent from my Nexus S using Tapatalk

I get that, any idea how to get into fastboot now?

In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc

I would love to do that except when I go into boot loader there is no option for fastboot

albundy2010 said:
In order to issue a fastboot command the phone needs to be in fastboot.
You would not issue that command. You would issue adb reboot bootloader. Or just reboot boot loader on the terminal on the phone with su privileges
When the phone is in the bootloader put it in fastboot mode then you issue fastboot commands from a computer that is properly set up to do. Like fastboot devices. Or fastboot flash recovery recovery image name.img etc
Click to expand...
Click to collapse
Dear lord, I guess I forgot a bunch of stuff. Thanks for refreshing my memory
Got it done.

CaptEvo said:
I would love to do that except when I go into boot loader there is no option for fastboot
Click to expand...
Click to collapse
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S

DarkhShadow said:
The bootloader IS fastboot, just run the flash commands
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes thats true. But before running the commands run : fastboot devices. If you see a long number youre jn fastboot mode and the drivers are correctly installed.
Then you can run the commands
Sent from my Nexus S using xda premium

Booting only takes me to TWRP

So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.

Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?

Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.

I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk

edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...

cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!

I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.

Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app

The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.

hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.

So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?

tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)

RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk

[Q] Unable to install twrp

I'm trying to install a TWRP via ADB and it shows it was successful but when I enter recovery it goes to stock recovery, maybe I'm doing something wrong but I checked several videos and TUT's and i can't find a solution.
The phone is xt1032 gpe with unlocked bootloader ont 5.1 Lollipop, it's not rooted.
I think the problem is that after I send the commands "fastboot flash recovery twrp.img" and "fastboot reboot" I cant enter the to recovery to make the new recovery end the installation.
When i send the reboot command the phone doesn't reboot it just shows the battery charging symbol and when i touch de power button the phone boots up immediately i tried several combinations off keys and I still can't do it.
I really appreciate some help,
Thanks

Moto x model no.xt1052 upgrade pls
Sent from my XT1052 using Tapatalk

chandu shekar said:
Moto x model no.xt1052 upgrade pls
Sent from my XT1052 using Tapatalk
Click to expand...
Click to collapse
What? my phone is Moto G XT1032 and I'm looking for a solution not an upgrade

Your fastboot command is wrong.
Rename twrp as recovery.img(.img is the extension) copy it to adb folder and type "fastboot flash recovery recovery.img" without quotes.

pradeeppk said:
Your fastboot command is wrong.
Rename twrp as recovery.img(.img is the extension) copy it to adb folder and type "fastboot flash recovery recovery.img" without quotes.
Click to expand...
Click to collapse
thank you for your but tried and nothing, from what I understand I have flash recovery and then immediately enter recovery after the reboot and that's the part that it's not working

I didn't find any twrp for my phone. Please help
Sent from my SM-G313F

Neto. said:
thank you for your but tried and nothing, from what I understand I have flash recovery and then immediately enter recovery after the reboot and that's the part that it's not working
Click to expand...
Click to collapse
Found the solution, i just needed to press volume down and then volume up in the fastboot menu after flashing ther was no need for reboot

Bootloader unlock,Twrp Recovery and Rooting OPPO F1f Easy Guide and Index

Guys im opening this thread on how to unlock Boot loader and flashing twrp in steps clearly...as there are no clear guide to do this in main threads and people can also share things here...Thanks for the devs who are working for us[emoji3]
Thanks and all credit goes to Dev (Uberlaggydarwin) for developing the magic tool (Magictricks.zip) for unlock and initiating development of this device and all I need from you is just clicking thanks button below that's all [emoji12] [emoji12] [emoji12]
Sent from my F1f using XDA-Developers mobile app

Steps: Making bootloader unlockable
Download Magictricks.zip by (uberlaggydarwin) - go to stock recovery- select install from storage- select the downloaded zip- flash or update it.
This will make the boot loader unlockable and brings fastboot to our device...see below how to unlock bootloader through fastboot completely.
Sent from my F1f using XDA-Developers mobile app

Adb commands for fastboot and flash twrp.
First set up adb shell on your Windows..Download link available below...
Steps to command in adb shell properly to fastboot and to flash custom recovery...let's begin
1-Download adb and install adb drivers for oppo f1.
2-extract the files from adb.rar to your c directory in a folder named adb(creat one) or just extract the folder in c directory.
3-once the files are located in c:\adb go to start menu then search for cmd
4-Type in cd c:\adb then click enter
5-Type in "adb devices" it will show the connected devices it should be bunch of numbers
6-If you can't see them it means adb drivers for your device are not installed then install with adb installer
7- Disconnect your oppo f1 and put your phone in fastboot mode(press and hold vol+ and power button} u will see fastboot screen on phone then connect via usb then let the system install bootloader driver....proceed below
7-Then finally Command in fastboot for our device.
Put twrp recovery image(rename as twrp) in the same folder where adb is present then tick 'oem unlock' on developer option settings in the device before you continue.
Don't proceed here unless you flash "magictricks.zip" through stock recovery.
Starting Boot loader unlock and custom recovery steps:
Connect your device via usb in fastboot mode and command as below..
Type this "fastboot oem unlock" then press enter.(Will wipe your data so backup before you do and wait for reboot) command will show 'ok finished' with some like 0.07secs
Type this "fastboot flash recovery twrp.img" then press enter. wait it will flash then command will show 'ok finished' then disconnect and boot in to new recovery.....enjoy
Note - once u flash the recovery disconnect the phone and switch off from the fastboot then u should boot the twrp recovery first otherwise system will reflash the stock recovery...To boot in to twrp recovery command as "fastboot boot twrp.img" press enter
That's it you have unlocked your boot loader and installed twrp recovery successfully[emoji3] [emoji12] [emoji3] [emoji12]
Credits
Thanks to @uberlaggydarwin for developing magictricks to unlock
Download links:
Magictricks by uberlaggydarwin - https://strangebinaries.re/f1f/magictricks.zip
ADB driver installer(optional) - www14.zippyshare.com/v/ufYG71o0/file.html
ADB Folder files-https://drive.google.com/file/d/0B9SasC5iWK5kT1liMlpKRGY3LVU/view?usp=sharing
Twrp recovery for f1f - http://build.twrp.me/twrp/twrp-3.0.2-0-f1f.img

Rooting guide:
After installing TWRP recovery flash this Super Su Stable version and reboot then install super su from playstore if you dont see any icon
Flashable Su Binaries - http://forum.xda-developers.com/showthread.php?p=23427715
Sent from my F1f using XDA-Developers mobile app

reserve

Thankss a lot

drganbds said:
Adb commands for fastboot and flash twrp.
First set up adb shell on your Windows..Download link available below...
Steps to command adb properly please share it somebody[emoji12] ill share once I know and master it
1-Download adb and install adb drivers for oppo f1.
2-extract the files from adb.rar to your c directory in a folder named adb(creat one) or just extract the folder in c directory.
3-once the files are located in c:\adb go to start menu then search for cmd
4-Type in cd c:\adb then click enter
5-Type in "adb devices" it will show the connected devices it should be bunch of numbers
6-If you can't see them it means adb drivers for your device are not installed then install with adb installer
7-THEN FINALY COMMAND some for our device.
Put twrp recovery image(rename as twrp.img) in the same folder where adb is present then tick 'oem unlock' on developer option settings in the device before you continue.
Don't proceed here unless you flash "magictricks.zip" through stock recovery.
Starting Boot loader unlock and custom recovery steps:
Connect your device via usb and command as below..
Type this "fastboot oem unlock" then press enter.(Will wipe your data so backup before you do and wait for reboot)
stucked at waiting for device ( then i press vol + plus power button) command shows Ok finished but nothing happened to device no changes nothing...help please
Click to expand...
Click to collapse

I think you have not installed your adb drivers properly...use pdanet pc version to install otherwise use adb installer which is available in dl.
Sent from my F1f using XDA-Developers mobile app

Guys if u stuck at "waiting for device"
solution - disconnect the device, put it in fastboot mode (press and hold vol+ and power you will see fastboot screen)and connect it again then it will install bootloader drivers and continue. It will show 'ok finished' then u can continue to flash recovery and other stuffs...enjoy[emoji3] [emoji12] [emoji3] [emoji12]
Sent from my F1f using XDA-Developers mobile app

@ teteakholhring. you have done it right go head flashing recovery step.....now u unlocked the bootloader then flash the recovery
Thread re edited please check if u have doubts.

Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!

^^ I've read from other thread that right after you flashed the TWRP recovery image, you must start-up the phone in TWRP recovery first before eventually booting to Android.
I haven't unlock my phone yet though but I will once I see some custom ROMs available.
Sent from my F1f using Tapatalk

x36023x36023 said:
Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!
Click to expand...
Click to collapse
All your steps are perfectly right but once u flash the recovery disconnect the phone and switch off from the fastboot then u should boot the twrp recovery first otherwise system will reflash the stock recovery...
Do the recovery flash again and boot to twrp first...
It is not necessary that oem unlock will wipe your data so no worry.

Me too I'm waiting for available alternative roms to install twrp recovery ....I just flashed magictrick and it said that I have update the build.... Thanks sure it will be functional....

x36023x36023 said:
Hi
sorry about my poor English.
I am sure that I flashed magictricks.zip and ticked "OEM unlock"
and the phone is in fastboot mode.
And I typed in "fastboot oem unlock", it showed "Okay, finished",
then I typed in "fastboot flash recovery twrp.img", it also showed "Okay, finished".
Then nothing happen, my phone is still with stock recovery, and my data is stilled there, can someone give me a help?
I attached my cmd picture.
Thank you!
Click to expand...
Click to collapse
Ok you did everything right.. I've attached the picture how i did it.. I was busy solving the same problem.. Remove the usb when it says booting then it will boot into twrp recovery.. Then flash latest supersu..that's it download super user from playstore.. Thre you go.. You got what you wanted..

teteakholhring said:
Ok you did everything right.. I've attached the picture how i did it.. I was busy solving the same problem.. Remove the usb when it says booting then it will boot into twrp recovery.. Then flash latest supersu..that's it download super user from playstore.. Thre you go.. You got what you wanted..
Click to expand...
Click to collapse
Ya right guys...Please check this thread's main page everything was written clearly for how to do it correctly...enjoy
Sent from my F1f using XDA-Developers mobile app

hoping someone will upload a video on how to properly root our device.

wakaranay said:
hoping someone will upload a video on how to properly root our device.
Click to expand...
Click to collapse
What doubt you have? I'm here to clear it all and every steps are clearly explained in the main page...
Sent from my F1f using XDA-Developers mobile app

thank you for all your help
I made my phone rooted
but when I forced to delete original apps like original browser
and reboot
all the things on home page will disappear
when I delete original browser only
it still happened
this never happened on my other Sony device
can anyone tell me why

x36023x36023 said:
thank you for all your help
I made my phone rooted
but when I forced to delete original apps like original browser
and reboot
all the things on home page will disappear
when I delete original browser only
it still happened
this never happened on my other Sony device
can anyone tell me why
Click to expand...
Click to collapse
Use root app delete from playstore or manually remove .apk file along with .odex file...
Sent from my F1f using XDA-Developers mobile app

Fastboot on Samsung?

After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?

ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.

ferreraiury05 said:
After entering recovery I realized that it has a "Reboot to bootloader" on my Samsung phone. And it doesn't reboot to Download mode, instead, it reboots to a "Fastboot mode". Does this Fastboot really work or it's better do not modify anything there?
Click to expand...
Click to collapse
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture

SubwayChamp said:
It seems the A10? Which model is? At least type fastboot devices to see if it is listed in CMD, anyway locked as it is you couldn't do much.
Click to expand...
Click to collapse
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
fellpanda said:
Using Samsung Android 11 default ROM - nothing modified. I'm trying to boot custom recovery (twrp) temporarily from PC console.
What I did to set up adb and fastboot:
OEM unlocked, usb debugging active, not rooted.
I installed latest ADB and Fastboot. Also installed Samsung USB drivers. Samsung doesn't provide fastboot drivers, and I've read on some thread that AOSP drivers are used for that. So, I'm using Google's Bootloader Interface installed via Device Manager, because plenty of guides suggest that online.
Problem:
I can use adb when phone's on. But when it comes to fastboot, I can get into it by 'adb reboot bootloader' and, i can see the device is listed using 'fastboot devices', but i can't really do anything at all other than that command.
I tried 'fastboot oem device-info', 'fastboot boot twrp.img'. I don't get any error messages. When I execute a command, the command just stays there on the terminal like it is busy executing. Waiting for over 15 minutes and there's no change.
Ex: When I executed the boot command, the console output was stuck at 'Sending boot.img', without any progress.
Click to expand...
Click to collapse

crownvn said:
As I has knew since I used HTC M7. ''Locked'' status , it means the phone can't flash any custom ROM. my phone is Samsung M20 . it don't show as your picture
Click to expand...
Click to collapse
That's not my device, it's from a YouTube video, because I couldn't take any picture until now. My device is listed as unlocked.

Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.

xXx yYy said:
Samsung devices don't know of Fastboot mode but of Download ( aka ODIN ) mode, hence not any fastbbot command works.
Click to expand...
Click to collapse
ferreraiury05 said:
No, it's a A015M. After looking for some help, I realized that it really doesn't work.
Click to expand...
Click to collapse
I think fastboot is only there because it is a MTK device.

If it's a Samsung SM-A015M then it's not MTK, but Qualcomm based.

I have j7 2015 and i have twrp and i want to do "fastboot boot <magisk patched image>" but i can't do it because i can't get inside fastboot mode
Any soulotions please?
Sorry for bad English.

As said earlier here Samsung devices don't have a FASTBOOT mode

xXx yYy said:
As said earlier here Samsung devices don't have a FASTBOOT mode
Click to expand...
Click to collapse
Thanks so the only way to flash images only with modded TWRP or flashify

Abdullrahman_Dawaliby said:
Thanks so the only way to flash images only with modded TWRP or flashify
Click to expand...
Click to collapse
or odin

With fastboot it is possible to enable the UART serial interface for viewing kernel messages. Is it even possible to do that on Samsung devices, since fastboot is not available?