Hi, so I've updated to android 11 OneUI core 3 on my M31 but since I can't enter neither download or recovery modes. I press Power+Vol Up but it just boots as usual with no signal of recorery mode. If I press Power+Vol Down the phone keeps rebooting but never actually goes to download mode.
I do can enter recovery mode using ADB via PC but that's a very inconvenient way of doing it as it need the phone to be turned on and woking normally so if the phone break and I ever need to flash an image with Odin that's a no no.
Please share with me if you are having this problem. I didn't factory reset it yet because I don't want to go to the bank and register my phone again xD
EDIT: Ok... I found the issue.
Looks like sammy changed the way you get into recovery mode on Android 11(WTF?? why would you even do that??) and now you have one extra step to do (I would be very grateful if they've put a message about it after you update). In resume you don't need to worry your phone will break if you update to android 11, only the method officially changed.
To boot into recovery now you need to plug your phone on your PC, THEN press vol up + power.
Reference article: How to Boot into Recovery Mode on Samsung's One UI 3.0 Android 11 Update (New Method) (androidsage.com)
Well, i got a update too... but i was too lazy to download and install... so i'm good
Also, thanks for informing here. you saved many android devices.
Btw, i have no answer to your problem
But i hope everything will be solved and you will be good to go
Happy Androiding...........
In my case (UI 3.0 Android 11 DBT) I now need to have USB cable connected to PC before entering Recovery with VOL up and Power button. Download mode same as before with Vol up and Vol down and then plug in USB cable.
I had installed Android 11 but for some reason I had to go back to android 10. But after downgrading to android 10, I am not able to access Recovery or Bootloader.
Anybody please help.
Related
I was provided this device to try and help resolve the issue. I am not sure how it got to this point. I believe that it was rooted with a custom ROM, then the individual tried to install a stock ROM (method unknown).
The current situation is:
Galaxy Tab S 10.5 SM-T800 stuck in a bootloop with the TWRP logo on the screen. I can not get the tablet to go into download mode. I have tried all of the different methods to enter download mode, i.e. Power & Vol - & Home, Drain the battery > Plug into PC while holding Vol - & Home, Power & Vol + & Vol -. None of these combinations do anything. The only thing I can do to get a response is to press Power & Vol +, which reboots the device right back into the TWRP loop after the Samsung Logo. Power button alone does nothing.
The device is seen by Windows with the Samsung Drivers but is not mounted to a drive letter, and I can not mount it.
ADB , fastboot and Odin do not see the device.
I would like to flash a new rom either custom or stock, but I need to be able to get the device into download mode so it can be seen by odin.
Any help would be great.
Mike
Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.
I know it should be easy....
I know it should work but it is not, I will make a vid of the process and post. I can not make heads or tails.
Mike
ashyx said:
Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.
Click to expand...
Click to collapse
Is the home button actually working, are you pressing it firm enough?
If the home button doesn't register then the tablet will simply reboot.
Its a bit odd why twrp doesn't fully boot though unless it's the wrong one.
Does it hang at the twrp logo or continually reboot?
Quick background on situation.
I was running CM13 and I still have TWRP 3.0.2-0. I wanted to try out CM14 or some other variant. I went into TWRP Recovery Mode and Advanced WIPED everything except the Internal Storage and MicroSD (this is probably where I messed up?)
Then went to install and navigate to the new rom and gapps on my microsd card. Well TWRP does not see either. It lists both of them but with 0MB and unselectable. I tried two other card, no go (all FAT32). Tried OTG with 3 different thumb drives, same results. The OS is gone and all I get of course is the white ASUS boot screen loop. ADB doesn't see any devices as well (windows device manager see no new devices when I attached the cable or when I list devices).
The only thing I can boot into is TWRP and I have tried everything to access the SD/OTG without success.
So can I assume I have bricked this thing and must go onto the IntelSOC XFStik procedure? and if so, does having a working TWRP on there force me to deviate from the normal unbrick procedure I have see here and on youtube?
Or is it something really easy that I am missing? I am fairly novice (as noted by my current situation), so maybe it's an easy fix?
Any help is appreciated. Thanks.
@Endosmok
You have LP version twrp recovery? , not the mmbl twrp recovery installed ? which ends in 3.0.2.M1 ??
If you do have 3.0.2.0 for LP bootloader which early versions of CM13 used , then you can fastboot flash stock recovery for 4 20 40 196 in bootloader from here....
https://mega.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Thanks go to Shakalaca
To get into bootloader -- from Twrp , select reboot , select power off !
Count to ten after switching off.
Press power and vol + , release power when it vibes , release vol+ at asus screen.
Fastboot flash stock recovery for above LP .196 in bootloader , when flashed --- scroll via vol buttons to recovery and hit power. At the dead android , press power and vol+ together for 4 secs , release vol+
You should be in stock recovery now.
Scroll to `update over adb` and select .
adb sideload LP official firmware from asus for LP .196 or .198
If you need help to get thru this step , just ask:good:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Endosmok said:
Thanks for the response. I am not sure if I have the LP version. It was done back I think in April of last year... I looked around TWRP and I don't see anything except 3.0.2-0 listed.
So still a little confused. This is how i have been navigating so far....
Power button, volume up... I get to the dead robot. There I can see FASTBOOT MODE is in Red, product name, variant, IFWI, Serial #. The rest is either ? or unknown (bootloader version is unknown).
Then at the bottom i can see 'continue the fastboot process' in blue. With the volume rocker i can select, NORMAL BOOT, POWER OFF, RECOVERY MODE and RESTART BOOTLOADER. I have been select Recovery Mode to get into TWRP. Restart Bootloader gets me back to the dead robot. I would assume this is the bootloader. Normal Boot just gives me the white asus splash where it hangs. In TWRP i can see ADVANCED -> ADB Sideload, I can start and it shows starting adb sideload feature with the blue color scrolling. But still when I connect to the computer I get no connection and nothing is listed when i run adb devices.
My TWRP doesn't let me select either the OTG or MicroSD, they show 0MB but are listed. So no way for me to flash via TWRP. I figured if i can get the computer adb to recognize the phone I can try to sideload via there. But so far my device manager doesn't see a thing, not even an unknown device waiting for their proper drivers.
Where am i going wrong?
Click to expand...
Click to collapse
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
timbernot said:
You have LP bootloader .
Type in bootloader >
fastboot devices
If recognised, fastboot flash , follow my first reply above , adb wont be recognised until stock recovery is flashed and selected.
Please try to follow what as been already advised
It is V important to follow this from above , dont miss this step ;-
To get into bootloader -- from Twrp , select reboot , select power off !
Click to expand...
Click to collapse
Ok... let me get this straight.... before I sound too dumb...
You want me to go into the bootloader from TWRP (using Reboot > Power Off), even though I get to TWRP via the bootloader (recovery mode) from a power on?
Also, how do I know if fastboot is enabled? Is it when I see FASTBOOT MODE in the color red on the bootloader screen with 'continue the fastboot process' at the bottom?
I've done step by step what you wrote and I get to the bootloader but fastboot devices shows nothing (I've tried different computers/cables as well). I have the computer connect to the phone w/ bootloader screen on with what i wrote about FASTBOOT MODE in red and contine the fastboot process. If that is not correct, let me know. I did hold down the Volume Up for a bit longer
I'm almost thinking I have a hardware issue with my phone. I did replace the mic with a new module prior. I never checked if the usb storage was functioning after. Though it charges via the usb (even connected to a computer it charges but not recognized as a device). I'll have to double check that as well.... not sure why the sd card is not recognized though either... never touched that area. Could be the reason why TWRP can't access either the micro sd or otg?
I do appreciate the help... and i have been reading other threads... just seem to be at a stand still for now... suggestions are always welcome.
update: tried adjust the cable on the mic module ... no dice... replaced with older mic module, no dice... don't think it's a hardware issue.
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
audit13 said:
To get into fastboot mode, power off the phone. Press and hold the volume up button and press the volume button. Once the phone vibrates, let go of the power button, then the volume button. You should not be in fastboot mode. You can choose recovery, power off, etc. with the volume button when in fastboot mode.
Connect the phone to the computer. Do you see any Android devices in device manager? Do you see any unknow devices?
Did you open a command prompt window on your computer, connect the phone in fastboot mode, and type "fastboot devices" (without quotation marks) and press enter to see if the phone is recognized?
Click to expand...
Click to collapse
So made some progress here. I think it was a hardware issue now... I put back the new mic module and reconnected the cable and now I can see my SD card and the computer sees it as well in adb and fastboot. That's the good news....
But ran into a new issue when trying to install any ROM from my micro sd card. I get ERROR 7 no matter what ROM I try to install. I have verified that they are the proper roms for my Z00A ZE551ML but still a no go.
What steps should I take next if I can now communicate but get error 7?
Thanks
Which recovery are you using to flash and which file are you trying to flash?
I am using TWRP 3.0.2.-0. Using the install from zip. I select any rom (Nougat Based so far I have tried). RR, Lineage, Octopus, all with the same error.
The phone is running a MM bootloader? What about MM or LP based ROMs?
I believe Timbernot said it was an LP based. I believe I installed about April last year and it was 3.0.2-0
Looks exactly like this
https://forum.xda-developers.com/zenfone-2-laser/development/recovery-twrp-3-0-0-0-recovery-t3319704
You probably need an MM bootloader for custom Nougat ROMs. Did you try any LP-based ROMs?
I have not tried any LP based yet. I will try in a bit and forward the results.
Thanks
Post removed. Let's keep things respectful here folks. :good:
And remember, to each their own.
Cheers,
Darth
Senior Moderator
I have bricked lg e988 indonesia firmware rooted,updated to kitkat 4.4.2,cwm 6.4.0.4
Due to some issue I factory reset from settg menu and the phone rebooted to cwm recvry mode
I tried to rebootd to system but fail
I tried to flash stock rom via adb sideload but fail too so does with lg flash tool
So I thght smtg wth cwm then I tried to flash twrp loki 2.6 and then stuck to lg logo only until now
Pls help
You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.
ShadySquirrel said:
You're still soft bricked, just force your device into download mode and use LG Flash Tool to return back to stock and start again.
Click to expand...
Click to collapse
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue
hotmatua.parulian said:
Thank you for the respond. Mind if you share me on how to force my device into download mode?
I have tried the power + volume keys combination but nothing happened, back and stop at lg logo
Before i flash the twrp, i tried the LG Flash Tool, but i wont recognize the phone, something like usb connection issue
Click to expand...
Click to collapse
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.
ShadySquirrel said:
If I remember correctly (please check threads here, it's been a long time since I've used this device, so memories are fading), download mode is activated when you press Volume Up (or both of volume buttons) and insert USB cable. I know that E98x has some strange button sequences, like rebooting to recovery is a two step operation (Volume Up + Power until navbar blinks, then power button twice, that's the only way mine wanted to boot into recovery), so please check around.
As far as USB connection issues, don't use USB3+ ports and if you're on Windows 8.1+ and later, run with Administrator privileges. I never experienced that one (used LGFlashTools from inside VirtualBox running Win XP for all my needs, I'm not a Windows user), so can't really help much but forums are full with explanations how.
Click to expand...
Click to collapse
Thank you very much...now the phone is back to initial state. This what i've done:
1. Download LG Flash tool from http://lgflashtool.com/
2. Download LG USB Drivers from http://lgflashtool.com/
3. Install LG flash tool and LG USB Drivers
4. Plug usb cable to phone
5. Hold volume buttons and then plug the usb cable to PC (i use win 10)
6. Voila, the Download Mode icon is showed up
7. Run LG Flash Tool (Administrator privilege) & follow the instruction (i use e988 v20c stock firmware)
8. Phone back to normal (only if you use the correct stock firmware)
A very big thanks to ShadySquirrel
Hopefully this thread can also be used as reference for anyone who has the same issue as i had
I have been give samsung galaxy F41 with android version 9.0 but has limited functions which did not interest me. According to its specifications, it can be updated to android 10. I tried updating it using OTA method but it tells me there is no update and so I wanted to flash it using ODIN but it can not boot into download mode using the vol+, vol- and side Key combinations. Whenever I try it, it takes me to factory Mode and sometime it takes somewhere it gives me options of: recovery mode, fastboot mode and Normal boot. When I select Recovery Mode, it takes me to a window with the wording "No Commad". it stays there and then boot normally. When I select Fastboot mode, it stays there forever untill I press the side key and When I select Normal boot, it boots normally. please someone help me to boot this phone to download mode
press vol up and vol down together meanwhile connect your charger with ur pc and phone then it comes device unlock mode press vol up u will boot to download mode
Samsung Galaxy F41 Mobile Automatically switched off every 2 hours, and its starts after 1 hour,
how to fix it?
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!