Related
I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.
OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US
If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.
Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.
Hold power button until phone turns off. Turn phone on while holding volume down.
tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.
lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again
Hi everyone im stuck on the resurection of my device (moto g 2013 8GB updated to 5.1 with [5.1 GPE 1 click] from This forum.
I've tried everything or almost for now, cant get it out of that loop.
*Battery pulling.
*hard buttons combinations.
*fastboot and ADB. (not in fastboot mode so.. And as i did flash de 1click before the loop USB Dbgn isn't enabled)
*i think i've tried every toolkit on this forum.
*Raped google search for over a week trying every posible method-
*Only thing left is to take it to church for a blessing. but im not a believer D:
ADD: i've rooted with a "boot.img" from this forum i think it was a 2015 file.
before this i had not 1 issue with the phone. just unlockd the bootloader a few days ago and updated to 5.1 from 5.0.2 becouse of a wifi issue (unknow mac adress) i had to reboot it like 10 times until it appeared again (original mac adress from device, still wrote it down i have it somewhere.)
I think this would be my first post on this forum and it took me over a week to do it becouse this (asking you-comunity) is my last resource.
PS: i had it going betwen 5.0.2 and 5.1 like 4 times to try solving the wifi issue.. only thing it got me was the "line" on the screen like if it where a problem with vertical sync. (i think you are all very familiar with that issue after downgrading the kernel i think.)
the phone just turns it self on everytime. (everytime)
i was able to boot into recovery before the last flash touching the place were the hardware volume button goes (with a neddle) untill it didnt workd anymore and i send it to a store to repair the volume rockers. still no recovery or bootloader boot.
my pc (laptop with 7-32bit recognices it as xt1032. and the one with xp as MTP.)
I've installed every posible thing that i found to bring it back to life even the android sdk full every pkg from 5.0.2 to 5.1 and extras, Motorola drivers and ADB. tried online searching automated from windows and listing it from a folder with the google one. tried adding the hardware manualy and have every ADB thing that i found on device mng but everyone is wit a yellow triangle. (No USB Debuging enabled so why bother anymore.)
I think that's about it.
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
i m sorry for my english, isnt my native lang. And for making it over complicated.
i cant enter fastboot mode or give any order to the phone trough fastboot on a console.
I have installed a TWRP touch, just cant acces it. dont know if it is the hardware button (Vol -) or what.
so it dosnt show up on fastboot devices nor adb devices.
am i not understanding something ?
Thanks for replying and taking the time to help!
Enter fastboot mode by turning on phone while holding Volume Down.
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
dieguitwow1 said:
tried again just in case. No luck, wont boot into recovery or bootloader mode. vol (-) or power and vol (-)
it just "tries" to boot up normaly and gets stuck on "android starting" untill "initializing apps" 4 colours flying and reboots again.
Click to expand...
Click to collapse
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
If the volume rocker is not broken, then you should be able to enter fastboot mode. Hold power button until phone turns off completely.
Click to expand...
Click to collapse
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
dieguitwow1 said:
did that, tried pulling the battery off and holding the keys (down and power or just vol down) and starting it. no way it goes into bootloader or recovery. When i do any of those things the phone just powers back up it self and boots into system or tries to, and get stuck in bootloop.
Im gonna try a gtag cable or something like that tomorrow from a friend. would it work to send it to bootloader or recovr?
Click to expand...
Click to collapse
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
lost101 said:
You seem to be making things massively over-complicated.
Flash latest TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Example fastboot command:
fastboot flash recovery twrp.img
If you cannot enter TWRP, use ONLY this fastboot command:
fastboot erase userdata
Via TWRP, flash latest GPE Optimized ROM from here: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510
Click to expand...
Click to collapse
lost101 said:
Enter fastboot mode by turning on phone while holding Volume Down.
Click to expand...
Click to collapse
lost101 said:
You said you had the volume rocker repaired - but it seems at least, vol down is not working. I have no experience with jtag kits or commands.
Click to expand...
Click to collapse
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
dieguitwow1 said:
i think it's not repaired properly, or the last time i flashed it fastboot might have send a command like "fastboot normalboot" or something like that. Would that be stoping me from entering recovery mode or fastboot?
Click to expand...
Click to collapse
If you power phone off completely, then no commands are remembered. The button is broken.
lost101 said:
If you power phone off completely, then no commands are remembered. The button is broken.
Click to expand...
Click to collapse
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a niddle until it stoped working is there a fix for it? :fingers-crossed:
dieguitwow1 said:
Thanks! so, what should i do now? is there any way to fix it or bypass it ?
i was "touching" the button with a needle until it stopped working is there a fix for it? :fingers-crossed:
Click to expand...
Click to collapse
Sorry, I can't help you with that. If you know someone good with a soldering iron, maybe they can fix it - otherwise, try another repair shop.
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
dieguitwow1 said:
its still seen by my PC with XP. As xt1032 on the bootloop can i do something ? moto device mngr starts with de Moto logo on the sys tray..
Click to expand...
Click to collapse
adb reboot bootloader
lost101 said:
adb reboot bootloader
Click to expand...
Click to collapse
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
dieguitwow1 said:
even if "USB Debuging" isn't enabled?
Edit: Result= [ Error: device ´<null>´ not found ]
Click to expand...
Click to collapse
Yes, USB Debugging would need to be enabled.
lost101 said:
Yes, USB Debugging would need to be enabled.
Click to expand...
Click to collapse
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
dieguitwow1 said:
so, apart from taking it to repair again for the button, what can i do?:fingers-crossed:
Click to expand...
Click to collapse
I am not aware of any other options.
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
dieguitwow1 said:
i managed to recover the phone it works normaly but screen goes off and on all the time, every 5 sec. Except on Bootloader Mode.
Click to expand...
Click to collapse
What has changed? Did you get the vol button fixed?
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
xymic said:
Hello guys,
I just replaced screen on my 64GB OPO. Phone was fine before screen broke and I had a PIN lock on it. Now, when I turn on phone, I cannot do anything on my phone besides pulling down notification bar and swipe notifications. If I try to unlock by entering my PIN, screen turns off right after. If I enter wrong PIN, it will say Wrong PIN, but as soon as I enter right PIN, screen turns off.
I'm not sure why this is happening. I decided to boot into recovery and reflash the ROM. I hold Power + Vol Down, but phone starts booting normally, no recovery. Then, I try to go into Fastboot by Power + Vol UP, and phone boots normally, no fastboot. At this point, I cannot access recovery or fastboot. Then, I try ADB on laptop, I get "Unauthorized." I can't authorize ADB RSA dialog on my phone because as I said, when I enter my PIN to unlock my phone, screen turns off. Recovery, Fastboot, and ADB worked perfectly before replacing screen.
Anyone know how to fix this?. Thank you
TL;DR:
Replaced screen. Entering my PIN turns screen off immediately. No recovery, No fastboot, ADB gives "Unauthorized" Error.
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
You can use this,it does not uses fastboot and instead uses hardware debugging port.
Also using this on Xp system will make it easier to detect the device.
Click to expand...
Click to collapse
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
xymic said:
I looked at that tool before I made this thread and in 3rd step, it says to press Power + Vol Up? Doesn't that mean you have to be in fastboot? Anyway, I tried it in Windows 10 and it didn't do anything. My phone gets detected by my laptop and everything. I will try in Windows XP and see if anything changes.
Click to expand...
Click to collapse
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Mr.Ak said:
No, power+vol+ is actually done to trigger the qualcomm port,if your device can't boot to fastboot,it means it's actually dead then your pc should be able to detect it as "Qhs_bulk" or "usb qcom diagnostics 9006".
Make sure you install the drivers given in the thread or Qualcomm 2012 drivers.Again this procedure doesn't work on fastboot/adb drivers!
You'll have to disable driver signature check on win8/10,Xp works without any issues.
Click to expand...
Click to collapse
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
xymic said:
Oh ok. I will try soon. I'll report back with results.
Thanks for your help man!
Click to expand...
Click to collapse
Click "Thanks" button
How can I get my Galaxy Note 20 Ultra out of stuck at 'entering fastboot mode'?
Hold down power and volume down until it reboots back to recovery. I got stuck there last week and that's what worked for me.
Sent from my SM-N986U1 using Tapatalk
Is this problem solved? I cannot boot into bootloader mode, thanks!
Switch off the device. Then hold volume up and down buttons and insert the USB cable plugged to PC. You will get to download/odin mode
shantanil said:
Switch off the device. Then hold volume up and down buttons and insert the USB cable plugged to PC. You will get to download/odin mode
Click to expand...
Click to collapse
Download mode is different from fatboot mode, I can enter, and works ok download mode. However, fastboot does not, it gets stuck in entering fastboot mode and no fastboot command works
I got same issue here, I've tried rooting via TWRP and after data wipe and "reboot to recovery" it got stuck in same thing and doesn't move at all, if I hold power and vol down it just boots the device which i dont want since i need to flash magisk as a last step. if anyone encountered this or knows how to fix it i'd be helpful
I'm not rooted but I've had past Samsung devices that I was able to root and if I'm not mistaken Samsung phones aren't able to boot into fastboot mode because Samsung removed the ability to. You can run commands via ADB mode but I think that's about it
adj998 said:
I'm not rooted but I've had past Samsung devices that I was able to root and if I'm not mistaken Samsung phones aren't able to boot into fastboot mode because Samsung removed the ability to. You can run commands via ADB mode but I think that's about it
Click to expand...
Click to collapse
Yea I fixed it somehow I don't even know myself
i cant eneter into download mode by using volume up and volume down ... the only thing that happens is the battery display kicks in .. is there a trick on how long to hold the volume bottons .. or any special way of doing it .. or for the usb c while trying to connect it to the computer
it gets stuck into fastboot entering if i try to do it the old fashion way .. please help
Guys, turn off the phone, press volume up and volume down together, and plug the usb cable while pressing volume up and down, and wait until the phone enter in downloading mode. This work for me.
leonardo_evaldy said:
Guys, turn off the phone, press volume up and volume down together, and plug the usb cable while pressing volume up and down, and wait until the phone enter in downloading mode. This work for me.
Click to expand...
Click to collapse
Thanks Man. This worked.
Since we can"t enter into fastboot mode is it possible to flash boot.img with adb commands?
I m having the same problem with a21s(a217f). I can t enter download mode using key combinations and the other way launching it from recovery doesn t work, it stays stuck at,, entering fastboot mode,,
The ROM is already bricked, it says in recovery when i try to factory reset the following error:,, can t mount. /system (structure needs cleaning)
Even with,, apply up. with adb,, doesn t work, it just doesn t get detected on my computer when i checked with adb tools.
! The only thing that works is that I can access my sd card and apply a update from sd card but I don t know where to get the update file. (I ll edit if it works to flash stock rom from,, apply update from sd card,, )
Anybody got some ideas or should i burn my motherboard and replace it?
sorry for bad english
Honestly plug device into PC.
Power off device
hold all 3 side buttons. Volume up and down and power/bixby.
Should usually work.
After in fast boot you must press a button Volume button to find via odin.
ivoe said:
Honestly plug device into PC.
Power off device
hold all 3 side buttons. Volume up and down and power/bixby.
Should usually work.
After in fast boot you must press a button Volume button to find via odin.
Click to expand...
Click to collapse
I already did that, unplugged the battery, reconnected it after 1min, connected my phone to the computer and pressed all 3 side buttons, still doesn t work. I guess the download mode is deleted or something..
Volume up & down, no side key, then connect to PC. Works for me. Connect to PC first does not work for me.
guru96 said:
I already did that, unplugged the battery, reconnected it after 1min, connected my phone to the computer and pressed all 3 side buttons, still doesn t work. I guess the download mode is deleted or something..
Click to expand...
Click to collapse
It wouldn't be deleted as it's a safety protocol if the device has a bad update and freaks out.
Maybe try to person above method.
Normally I can enter download mode with any of these methods if you cannot I'd suggest trying to get the device replaced due to software malfunction
altojd said:
Since we can"t enter into fastboot mode is it possible to flash boot.img with adb commands?
Click to expand...
Click to collapse
Samsung phones use a tool called Odin to flash firmware. If you're flashing custom firmware firmware you'll need to have your bootloader unlocked.
I got mine into download mode just now. It's a Galaxy A13 .. Like stated above, try to hold all three buttons down and connect to USB. I had to let go before it showed the battery charge icon. From off. If not from off try from charging. I think that's what I did just now. Plug the usb -> let it show the charging icon (from powered off!) -> hold all three buttons, let it power on, let go. DONE.
just follow this video it helped me a lot to unlock my boot loader