Related
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
in the main setting, application, developer settings.. is usb debugging enabled?
stoo said:
I'm attempting to flash clockwork recovery and can't get the phone to respond to fastboot devices when in fastboot mode. I've tried everything I can find with regards to the drivers (pdanet, usbdeview, etc) and I can get google's and pdanet's drivers working fine with the phone booted normally (responds to adb devices). The problem seems to be that windows appears not to even notice that the phone is plugged in in fastboot mode and does not appear in the device manager, making the manual installation of drivers an impossibility.
Anyone know how to fix this?
Click to expand...
Click to collapse
When I first set up ADB and Fastboot on my pc, I was getting a response when writing 'adb devices' in the console. However, 'fastboot devices' returned absolutely nothing.
Solution (with phone connected to pc and usb debugging cheched):
1-shut down the phone
2-press and hold Volume Up key + Power
3-once in bootloader interface, in the pc command prompt, type 'fastboot devices'.
Voila!
By the way, don't mount the phone as usb storage device.
Thanks for the responses guys but yes, USB debugging is enabled and yes, I've used that way to get to fastboot mode as well as adb reboot bootloader
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
vstar said:
Hi stoo
I have a same issue - did you managed to find solution for yours?
Cheers,
Wiktor
Click to expand...
Click to collapse
easy way to set up fastboot
Any solution
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
OK So I am in the exact same situation.
Nexus S, Broken power button, adb can see the device, fastboot cannot. fastboot cannot be navigated with the volume keys.
I also want to put an other rom onto it, but firstly I want to put TWRP recovery on it, as it supports touch, CW needs the power
button which like mentioned does not work.
I would rather not unsolder my power button to get into fastboot, any suggestions on how that might still be achieved?
thx
catalinu said:
Have the same problem: locked bootloader, not rooted 4.1.2. In ADB everything is ok, drivers ok (in device manager), can get it through "adb devices". But when I boot in fastboot (adb reboot bootloader), I hear the ti-da windows sound (usb unpluged - from adb session), but no ta-di when the phone re-boot in fastboot. No exclamation mark in device manager, nothing. The USB receive nothing when in fastboot. Is it possible that the fastboot image is corrupted? Can I reflash it? Or any other advice?
Thanks
EDIT - SOLVED - at least this step
The problem was the famous "broken power button"! I knew that I had problems with the power button (didn't work - that's why I try to flash a rom (4.2.1 or customized) with sleep tile in notification area).
I thought that the button is all the time OFF and don't switch to ON, but I finally understood that when when I boot in fastmode it freeze before installing device on the PC (I also had no volume up / down navigation in fastboot, a sign that it was frozen). So I ended to consider that the power button was permanently in ON position. I opened my phone and I measure the impedance on the power button. I had ~ 4ohms in off position of the button and 1.8 ohms (cheap multimetter.... probably should be almost 0) in on position. I measured also on volume switch where I had ~ infinite on off position, so I concluded that the button if blocked. I tried to see if I can resurrect it but no choice, so I took it off (unsoldered). I put the battery and the USB cable and boot it. From ADB I reboot it in fastboot and voila! The device popped in device manager! One problem solved! BUT...
I tried to use the Nexus Root Toolkit and it boots in fastmode and try to unlock the bootloader, but it asked me on phone screen if I agree for unlocking. I was able to use the volume to select Yes but I couldn't choose it with power! I had no option but to take the battery off. Starting from that point it was almost impossible to power it again. When I plugged the USB it shown the battery icon (charging). I tried every trick that I found on web, but nothing worked (even to fast plug / unplug many times the USB to overcharge it, but nothing). I was able only by pressing on the middle of volume (so Up and DOWN in the same time) and plus the USB to get to the screen of unlocking bootloader, but without the options YES/NO on the screen. Seems that it saves this state between boots, but why no option? Finally I was unable to boot at all, and it is like totally bricked
I thought that the power button is a simple switch ON / OFF, so I soldered 2 wires and I tried to touch them (short circuit) to simulate the ON, but nothing happened. Is it the button more complex that a simple switch? no ideea...
So now have a better phone than before (at least theoretically it should be able to fastboot), but it values zero because I can't power it on....
Click to expand...
Click to collapse
Yes, it should have been better for me to have also a possibility to enter in fastboot with the power button blocked in ON position, but I didn't find. And now I know no way how to power it up...
fastboot drivers
http://www.samsung.com/us/support/owners/product/GT-I9020PWAATT#
has anybody considered using this executable from samsung ..
from what i understood when installing it ,it only unzips the contents at programfiles/Samsung/drivers
then you can check this thread to install them spesifically http://forum.xda-developers.com/showthread.php?t=1901617
..In short.
Go to
"Device Manager"
find
"Android 1.0" or something like that (i had my device in fastboot/bootloader mode, dont know if it was necessary)
install drivers from the drivers directory and install
P.S. Mine is an ordinary 9023nexus s (slcd) though
be a bit more careful with nexus s4g
I can imagine that you all are tired of reading this headline, but seriously, ME TOO.
I have been looking for information about this issue during several weeks and I have not found any solution, so I would extremely thank you if you take your time reading this problem and trying to help me finding a solution.
Some months ago I tried to flash a ROM on my Shield Tablet, I followed all the steps from a topic in this forum: [Complete Guide] SHIELD Tablet K1 Root, Custom Rom and Xposed Framework but I wanted to try a different ROM: CARBON-CR-5.1-MOO-WEEKLY-shieldtablet-20170216-0454 (the name of the file) And now I have a tablet that is stuck on the Carbon launch screen every time I turn it on, when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Thank you in advance. I hope your knowledge will help me and other people with the same problem. If you need more information of this problem let me know and I'll answer ASAP. If you have any idea tell me and I'll try it.
Warlain said:
when I press volumen down + power it goes into the screen buttt as soon as I press recovery mode the only thing it does is to restart itself and stays stuck in the NVIDIA screen. The Minimal ADB and Fastboot do not recognize the tablet with the adb devices command.
When I turn on the tablet (and stays stuck into the IOS icon as I mentioned before) and connect it to the PC the device manager recognize the tablet as a Portable device with the name: MTP USB device, when I press the power+volumen down the PC recognize the tablet as an Android Device -> Android Bootloader Interface. And this is all the information I have about my problem...
May you help me?
Click to expand...
Click to collapse
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Fastboot with TWRP
Type “fastboot devices” Copy and make sure your Shield Tablet is visible.
If your Shield Tablet is listed, type “fastboot boot twrp-20151227-EXPERIMENTAL-shieldtablet-m.img” Copy (or whatever you named it) and hit enter. If your TRWP image filename has a space in it, you may have issues.
After 15 seconds or so (be patient), you should see the TWRP Recovery screen. Note: This experimental version has some UI issues, just keep at it.
You may be prompted with something to do with the system being READ ONLY. Accept the default and swipe.
Click to expand...
Click to collapse
Use fastboot to wipe cache (fastboot erase cache) then try to flash TWRP (with fastboot) again. This will often clear up issues with being unable to boot to TWRP (at least on other devices).
If you are able to boot TWRP, restore the TWRP backup (if you made one) or put another ROM on the phone, and flash it.
I also have this kind of problem. After i update twrp by flashing it and restore a backup the sistem doesnt show. Stucks on nvidia logo. I tried even restore my recent backup but nothing also. Any idea ?
'Artemis' said:
Your device is not, dead, it's only taking some time to reflect
First of all, I understood that you're able to access to the device's bootloader menu, through the button combo (black screen with white text, "continue","restart bootloader","recovery mode"), and you selected "recovery mode".
Now, unless you have flashed a custom recovery, there's nothing to do with the shield's stock recovery, so, just enter in the bootloader menu as you did, without selecting any option.
You are now in "fastboot mode", in order to check your device's connection you have to write in the adb shell
Code:
fastboot devices
If you see your device you can now boot a custom recovery that will help you to fix the problems you caused, I would follow this link: (copy-paste, can't post links)
"nvidiashieldzone.com/shield-tablet/shield-tablet-root/root-shield-tablet-v1-marshmallow/"
And do the 8th step, in "Root procedure"
Click to expand...
Click to collapse
Done, Thank you a lot! It starts working again!!!
Heya peoples, I have a problem and am hoping for some help in a work around.
I am trying to root my J3 but my volume up button does not work. I have adb installed, and the correct drivers for my phone. I can use adb command to reboot to the bootloader and it brings me to the Odin "downloading" screen. I can then use the program to install TWRP so I can root. Everything goes fine up until this point. After TWRP is installed there is a single massive problem I am hoping there is a work around for. My volume up button does not work. I can only reboot to recover using adb once the phone boots up, and I read that if you let that happen it overwrites TWRP with the stock recovery (which is what happens when I do this). I read that you have to reboot directly from the downloading screen into recovery using Vol up and home and power. But I can't do that since my Vol up doesn't work. When I am at the download screen after installing TWRP none of the adb commands work so I can't reboot directly to recovery to access TWRP the first time. I hope this all makes since, and I hope someone has some advice because as far as I can tell I can't continue passed this point without a working volume up button.
A little more info in case it matters. When using adb command prompt I have to type ".\adb" instead of "adb" as the tutorials say. When I do ".\adb devices" my device shows up as connected. After rebooting to the bootloader using adb, typing ".\fastboot devices" shows nothing is attached, and any command I try to put in results in "waiting on devices". Checking the device management at this point does not show any unknown usb devices (one guide I read said if fastboot wasn't recognizing to check to update drivers if something was showing as unknown usb".
Basically hoping there is some way of booting directly to recovery from bootloader without having to use the vol up key combination so I can access TWRP for the first time. Any help at all is appreciated. I realize having a working volume button would take all the headache out of this but unfortunately fixing it is not an option at the moment.
Edit: I have also unlocked the bootloader using the Crom Services app from samsung, and have developer options and usb debugging enable.
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
CopaseticDream said:
Question: If I use an app to remap the buttons would that work? Wont be around a computer until tonight. Does remapping the buttons affect it at the level of being in bootloader (because if so I could just switch the up and down volume, use adb to reboot to bootloader then power/home/and remapped volume to reboot to recovery). But I feel like it wouldn't work if the app is not actually changig it but intercepting the button press and then changing it. I dunno.
Click to expand...
Click to collapse
Can this device even be rooted? Doesn't virgin lock their devices?
In any case if you flash twrp to the boot partition (rename it to boot.img) it'll boot directly to twrp then just use twrp to flash to the recovery partition.
Reflash the stock boot.img back to the boot partition.
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger
Good day, everybody!
So.. here's the deal.
I have a Samsung Galaxy A22, and it's been a while since I've seen the Android 13 update notification, but never had the time to do it (and I wish I never did).
Decided to finally do it on the 1st of January (yk, to start the year right!) and oh boy who knew I'd get stuck on a boot loop. I didn't even do a backup!
I've looked for countless how-to's online (on how to get out of the boot loop) and encountered people with my same problem: some advised to go into Recovery Mode and "Remove Cache Partition" and "Repair Apps". Managed to do it, no success.
Some say there's no way of saving the data if I want my phone back, but I've seen some glimpses of hope such as ADB and Fastboot or Odin Mode. Tried the first ones, but if I do "Reboot to Bootloader" I only get a black screen with an "Entering in Fastboot" in red.. and it stays stuck there, is it supposed to? I didn't really get how those work..
While for Odin Mode, I've been suggested to reinstall the OS, but not to downgrade since that would result in a factory reset.
Should I wait for the next android version, so that I can upgrade manually once it's out?
Also, by looking into Odin Mode I've found out about TWRP and how it comes with a working MTP connection and ADB enabled which allows you to extract almost all data stored on your device and even create physical images from them, as long as the device's bootloader (OEM?) is unlocked.
I looked for guides to unlock it buuut they all lead to my phone being on, which I can't do since my phone's on a boot loop.
So, in conclusion, here are my questions:
1- Are other samsung users here having my same issue?
2 - Is there a way, apart from the ones I listed, to get out of the boot loop without having to do a short reset?
3 - How do ADB & Fastboot work and how would they aid me into recovering my media?
4 - Can I unlock my bootloader while stuck on a boot loop?
Thank you everybody, hope someone out there knows a thing or two about this situation!!
EDIT 1:
Should anyone need a guide to samsung odin, I've found this very clear one! https://forum.xda-developers.com/t/...unked-noobs-guide-to-samsung-devices.4405681/
As for when I'll flash the next version, I've read that the next Android 13 update will come out with the Samsung S23, whose release date is expected during February 2023. Hopingly, it will soon be extended for other samsung phones as well! I'll make sure to update this thread once it does and how flashing it goes, since that's gonna be the final solution to us "bootlooped phoned" people! ;D
EDIT 2:
Good day everybody! Guess what? I've just found out Samsung has dropped a new firmware like, LONG AGO! Imagine the look of immense surprise in my face when I've seen it after "just wanting to check" moments ago!
Here's how it went:
I downloaded all the files needed from https://samfw.com/firmware/, the one I was looking for was A225FXXU3CWA6! Took a while, but totally worth it. All that was left was to put my phone in odin mode
(HOW TO ENTER ODIN MODE: turn off your phone (if in bootloop, do it forcefully by pressing power off & volume down simultaneously). connect your USB cable to your computer, but not your phone yet. now, press and hold the volume up and volume down buttons and at the same time, connect the USB cable to your phone)
Opened the ODIN3_v3.14.4 program on my computer, put the files accordingly (follow the guide I've mentioned in my first edit! USERDATA must be left empty & only put HOME_CSC where CSC is asked, if you wish to preserve your data!). NOW START!! Took 7:27 minutes!! AND EVERYTHING WAS STILL THERE! photos, music, videos, whatsapp messages, JUST THE SAME! and since it updated it was cooler too!
Patience truly is a virtue! <3 huuuuge thanks to alecxs (hope he doesn't mind me mentioning him!) for helping me through it all, and to the whole XDA community for existing, always eager to help! y'all are the best!! <3
Hope everyone who had my same problem can now sleep in peace and live happier haha!
nanawa said:
Good day, everybody!
So.. here's the deal.
I have a Samsung Galaxy A22, and it's been a while since I've seen the Android 13 update notification, but never had the time to do it (and I wish I never did).
Decided to finally do it on the 1st of January (yk, to start the year right!) and oh boy who knew I'd get stuck on a boot loop. I didn't even do a backup!
I've looked for countless how-to's online (on how to get out of the boot loop) and encountered people with my same problem: some advised to go into Recovery Mode and "Remove Cache Partition" and "Repair Apps". Managed to do it, no success.
Some say there's no way of saving the data if I want my phone back, but I've seen some glimpses of hope such as ADB and Fastboot or Odin Mode. Tried the first ones, but if I do "Reboot to Bootloader" I only get a black screen with an "Entering in Fastboot" in red.. and it stays stuck there, is it supposed to? I didn't really get how those work..
While for Odin Mode, I've been suggested to reinstall the OS, but not to downgrade since that would result in a factory reset.
Should I wait for the next android version, so that I can upgrade manually once it's out?
Also, by looking into Odin Mode I've found out about TWRP and how it comes with a working MTP connection and ADB enabled which allows you to extract almost all data stored on your device and even create physical images from them, as long as the device's bootloader (OEM?) is unlocked.
I looked for guides to unlock it buuut they all lead to my phone being on, which I can't do since my phone's on a boot loop.
So, in conclusion, here are my questions:
1- Are other samsung users here having my same issue?
2 - Is there a way, apart from the ones I listed, to get out of the boot loop without having to do a short reset?
3 - How do ADB & Fastboot work and how would they aid me into recovering my media?
4 - Can I unlock my bootloader while stuck on a boot loop?
Thank you everybody, hope someone out there knows a thing or two about this situation!!
Click to expand...
Click to collapse
I'm sorry to hear that your Samsung Galaxy A22 is stuck in a boot loop. Boot loops can be frustrating, but there are a few steps you can try to try to fix the problem.
Are other Samsung users having the same issue? It's possible that other Samsung users are experiencing similar issues with their devices after the Android 13 update. It's always a good idea to check for any known issues or bugs with a new update before installing it.
Is there a way to get out of the boot loop without a factory reset? One option you can try is to boot the device into Safe Mode, which will disable all third-party apps and allow you to determine if a third-party app is causing the boot loop. To boot into Safe Mode, follow these steps:
Turn off the device.
Press and hold the Power key past the model name screen.
When "SAMSUNG" appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key until the device finishes restarting.
Safe mode will display in the bottom left corner of the screen.
If the device is able to boot into Safe Mode without encountering a boot loop, it's likely that a third-party app is causing the problem. In this case, you can try uninstalling any recently downloaded apps to see if that fixes the issue.
How do ADB and Fastboot work and how would they help me recover my data? ADB (Android Debug Bridge) and Fastboot are tools that allow you to communicate with your Android device from a computer. ADB can be used to run commands on the device, install apps, and perform other tasks. Fastboot allows you to flash factory images, boot images, and other files to your device.
If your device is stuck in a boot loop and you can't access the Android operating system, you may be able to use ADB and Fastboot to fix the problem. For example, you might be able to use ADB to sideload a new version of the Android operating system, or use Fastboot to flash a factory image to your device.
Can I unlock the bootloader while stuck in a boot loop? Unfortunately, it's not possible to unlock the bootloader of your device while it's stuck in a boot loop. The bootloader must be unlocked while the device is powered on and fully operational.
In summary, there are a few steps you can try to try to fix the boot loop issue on your Samsung Galaxy A22, such as booting into Safe Mode or using ADB and Fastboot to sideload a new version of the Android operating system. However, if these steps don't work, you may need to perform a factory reset to fix the problem. Be aware that a factory reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Here are a few more steps you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Clear the cache partition: The cache partition stores temporary files and data, and sometimes these files can become corrupt and cause issues with the device. To clear the cache partition, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe cache partition."
Press Power key to select.
Press the Volume down key to highlight "yes" and press the Power key to select.
When the wipe cache partition is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Attempt to boot the device into Download Mode: Download Mode allows you to flash firmware and other files to your device using a tool like Odin. To boot into Download Mode, follow these steps:
Turn off the device.
Press and hold the Volume down key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys.
An warning screen will display. Press the Volume up key to continue.
The device will now be in Download Mode.
From Download Mode, you may be able to use a tool like Odin to flash a factory image or other firmware to your device in an attempt to fix the boot loop issue.
Try using a different charger or charging cable: In some cases, a faulty charger or charging cable can cause issues with the device, including boot loops. If you have access to another charger or charging cable, try using it to see if that helps fix the problem.
Contact Samsung support: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to contact Samsung support for further assistance. They may be able to provide additional troubleshooting steps or repair options.
I hope these additional steps are helpful!
Also, here are a few more things you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Check for any updates: It's possible that a software update may be available that can fix the boot loop issue on your device. To check for updates, follow these steps:
From the Home screen, tap the Apps icon.
Tap Settings.
Scroll to and tap Software update.
Tap Download and install.
If an update is available, follow the on-screen prompts to download and install the update.
Keep in mind that installing a software update may require a stable internet connection and enough storage space on your device.
Perform a hard reset: A hard reset, also known as a factory reset, will erase all data and restore the device to its original factory settings. This can be a useful option if the boot loop issue is caused by a software problem that can't be resolved through other means. To perform a hard reset, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe data/factory reset."
Press Power key to select.
Press the Volume down key to highlight "Yes -- delete all user data."
Press Power key to select and start the master reset.
When the master reset is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Check for any physical damage: In some cases, physical damage to the device can cause it to become stuck in a boot loop. If you suspect that your device has suffered physical damage, it's a good idea to have it inspected by a professional.
Consider seeking professional repair: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to seek professional repair services. A trained technician may be able to diagnose and fix the problem with your device.
With regards to this thread's title
Recover data with TWRP after device is stuck on boot loop?take note that you can recover user-data when phone gets booted into recovery mode ( Stock Recovery is good , TWRP isn't needed ) because in this mode you via ADB can pull the data you are interested in.
yeah welcome to bull****-bingo
(besides its fully restricted no adb) stock recovery doesn't have any access to /data at all. TWRP recovery does not support Samsung Encryption, no way to decrypt /data.
unlocking bootloader is no option as encryption keys are tied to the bootloader status and boot/recovery image signatures.
There is no way to access your data other than fix boot-loop and unlock screen.
install Odin3, download stock ROM at current bootloader level same as device (you can find on download mode screen) and flash HOME_CSC (instead CSC) to keep userdata partition.
if no HOME_CSC file exist, unpack files and flash partitions manually from mtkclient (do a backup before)
@Alecxs
it's not me who is the idiot here ... Take note that ADB is supported in Stock Recovery mode.
@nanawa
To boot into Stock Recovery mode ( Stock Recovery mode refers to Android's bootable partition in which the recovery console is installed ) on a Galaxy A22 5G is to use the physical buttons of the phone:
{
"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"
}
This is fairly straightforward. One needs to turn off the phone, press the required buttons and the phone will go straight to Stock Recovery mode.
Before one can run ADB commands in Stock Recovery mode ( one needs to have the proper ADB and USB drivers for the Galaxy A22 5G, as provided by Samsung, installed on PC ) one of course must have phone initially unplugged before entering Stock Recovery mode. When phone is started in Stock Recovery mode one has to connect phone with PC via USB-cable and start USB-Debug mode - AKA ADB.
In USB-Debug mode you even can start an Android shell and remove any encryption as shown next
Code:
mkdir C:\DCIM 2>nul
adb devices
adb shell "su && echo '--set_encrypted_filesystem=off' > /cache/recovery/command"
adb pull /sdcard/DCIM C:\DCIM
dir C:\DCIM | more
you don't have any android device running android 5+ otherwise you would know that in stock recovery adb is limited to one single cmd that is called sideload
what you can do with adb in stock recovery is NOTHING
also your "remove" of encryption is bull****. data cannot decrypted without credentials not even with root lol.
what you're referring to is cmd (on /cache partition) to disable encrypted fs (requires formatting), used only for OTA update zip unrelated to adb (and unrelated to decryption)
maybe it works on your ancient android emulator but that's different from android smartphones. do not provide "solutions" you haven't tested yourself.
To keep you updated:
When running recovery image from debuggable builds (i.e. -eng or -userdebug build variants, or ro.debuggable=1 in /prop.default), adbd service is enabled and started by default, which allows ADB communication. A device should be listed under adb devices
adb devices
List of devices attached
1234567890abcdef recovery
Although /system/bin/adbd is built from the same code base as the one in the normal boot, may be for most only a subset of ADB commands are meaningful under recovery, such as adb root, adb shell, adb push, adb pull etc. Since Android Q, adb shell no longer requires manually mounting /system from recovery menu.
which device you have tested was able to run adb root, adb shell, adb push, adb pull in stock recovery?
which device is released as eng or -userdebug build? name a single one
bonus: which stock recovery is able to mount encrypted /data (and how the lock screen pattern is requested without touch screen)?
of course, you have no proof and no arguments, as always...
https://forum.xda-developers.com/t/retrieving-files-from-internal-memory.4523487/post-87905167
ChristianMorris said:
Also, here are a few more things you can try if your Samsung Galaxy A22 is stuck in a boot loop:
Check for any updates: It's possible that a software update may be available that can fix the boot loop issue on your device. To check for updates, follow these steps:
From the Home screen, tap the Apps icon.
Tap Settings.
Scroll to and tap Software update.
Tap Download and install.
If an update is available, follow the on-screen prompts to download and install the update.
Keep in mind that installing a software update may require a stable internet connection and enough storage space on your device.
Perform a hard reset: A hard reset, also known as a factory reset, will erase all data and restore the device to its original factory settings. This can be a useful option if the boot loop issue is caused by a software problem that can't be resolved through other means. To perform a hard reset, follow these steps:
Turn off the device.
Press and hold the Volume up key and the Bixby key, then press and hold the Power key.
When the green Android logo displays, release all keys (‘Installing system update’ will show for about 30 – 60 seconds before showing the Android system recovery menu options).
Press the Volume down key several times to highlight "wipe data/factory reset."
Press Power key to select.
Press the Volume down key to highlight "Yes -- delete all user data."
Press Power key to select and start the master reset.
When the master reset is complete, "Reboot system now" is highlighted.
Press the Power key to restart the device.
Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding.
Check for any physical damage: In some cases, physical damage to the device can cause it to become stuck in a boot loop. If you suspect that your device has suffered physical damage, it's a good idea to have it inspected by a professional.
Consider seeking professional repair: If you've tried all of the above steps and are still unable to fix the boot loop issue, you may need to seek professional repair services. A trained technician may be able to diagnose and fix the problem with your device.
Click to expand...
Click to collapse
Thank you a whole lot for taking the time to write all this, means a lot to me Christian!
But.. I can't manage to get into Safe Mode. I believe it's because it isn't a third-party app triggering the boot loop (since it all started with the update and solely because of it) but I might be wrong, as I'm not quite familiar with how that works.
As for the cache partition... I tried, but it didn't change anything
"Keep in mind that a hard reset will erase all data from your device, so it's important to make a backup of your important data before proceeding." Does this mean I can still make that backup, even if my phone's on bootloop?
Also.. you advised to use ADB, but can I do that if the bootloader wasn't unlocked in the first place?
Again, thank you so much for replying, truly!! <3
xXx yYy said:
With regards to this thread's title
Recover data with TWRP after device is stuck on boot loop?take note that you can recover user-data when phone gets booted into recovery mode ( Stock Recovery is good , TWRP isn't needed ) because in this mode you via ADB can pull the data you are interested in.
Click to expand...
Click to collapse
Thank you for correcting it!
As for "stock recovery", would you please elaborate? that's the first I'm hearing of it!
aIecxs said:
yeah welcome to bull****-bingo
(besides its fully restricted no adb) stock recovery doesn't have any access to /data at all. TWRP recovery does not support Samsung Encryption, no way to decrypt /data.
unlocking bootloader is no option as encryption keys are tied to the bootloader status and boot/recovery image signatures.
There is no way to access your data other than fix boot-loop and unlock screen.
install Odin3, download stock ROM at current bootloader level same as device (you can find on download mode screen) and flash HOME_CSC (instead CSC) to keep userdata partition.
if no HOME_CSC file exist, unpack files and flash partitions manually from mtkclient (do a backup before)
Click to expand...
Click to collapse
Oh my, I think I'm understanding less and less..
Does this mean ADB can't help?
Regarding the "current bootloader level same as device" I can find on the download mode screen.. I don't get what I'm supposed to look for, I attached a pic of the screen I get, if you may be so kind to tell me what to do!
xXx yYy said:
@Alecxs
it's not me who is the idiot here ... Take note that ADB is supported in Stock Recovery mode.
@nanawa
To boot into Stock Recovery mode ( Stock Recovery mode refers to Android's bootable partition in which the recovery console is installed ) on a Galaxy A22 5G is to use the physical buttons of the phone:
This is fairly straightforward. One needs to turn off the phone, press the required buttons and the phone will go straight to Stock Recovery mode.
Before one can run ADB commands in Stock Recovery mode ( one needs to have the proper ADB and USB drivers for the Galaxy A22 5G, as provided by Samsung, installed on PC ) one of course must have phone initially unplugged before entering Stock Recovery mode. When phone is started in Stock Recovery mode one has to connect phone with PC via USB-cable and start USB-Debug mode - AKA ADB.
In USB-Debug mode you even can start an Android shell and remove any encryption as shown next
Code:
mkdir C:\DCIM 2>nul
adb devices
adb shell "su && recovery --set_filesystem_encryption=off"
adb pull /sdcard/DCIM C:\DCIM
dir C:\DCIM | more
Click to expand...
Click to collapse
Okok, now I get what stock recovery mode is.. I thought it was a new thing :')
So, once in stock recovery, do I just run ADB and copy paste the code you wrote?
As for the rest of the discussion I can't understand a single thing, can I or can I not retrieve data with ADB? @aIecxs @xXx yYy
Also this might be dumb to say but regarding "and how the lock screen pattern is requested without touch screen)?" my phone's also locked by finger pattern! if that makes sense (also idk why I'm writing in bold I'm so new to this.. but please don't fight folks, I appreciate the help you're both giving me!)
no worry, you're not the only one who doesn't understand much...
on PC download platform-tools then connect device in recovery mode and install usb drivers. now add platform-tools directory to path (or navigate to directory with 'cd') in cmd.exe
if adb is available you should see device serialno when typing 'adb devices'. that's all, the rest won't work (but please try anyway, just to proof him wrong xD)
RP SWREV: B3 means bootloader level = 3
bootloader is downgrade protected, so even in case you manage to flash ROM with lower bootloader level (for example with mtkclient) device won't boot.
you can only flash ROM with same or higher bootloader level because of downgrade protection.
kindly upload picture of recovery mode screen too, so we can check for official ROM that matches best.
nanawa said:
As for the rest of the discussion I can't understand a single thing, can I or can I not retrieve data with ADB? @aIecxs @xXx yYy
Click to expand...
Click to collapse
Because you tagged me:
1. When device got booted into Recovery mode, a stripped down version of Android is loaded
what allows to perform basic tasks - this is comparable with WinRE what is based on Windows PC's recovery environment that exists by default on all Windows PCs .
2. When booting Android device into Recovery mode device's /data partition doesn't get mounted, thus no locks are got activated.
3. According to source-code of file recovery.cpp what is part of AOSP v13
/** The recovery tool communicates with the main system through /cache files.* /cache/recovery/command - INPUT - command line for tool, one arg per line* /cache/recovery/log - OUTPUT - combined log file from recovery run(s)** The arguments which may be supplied in the recovery.command file:* --update_package=path - verify install an OTA package file* --install_with_fuse - install the update package with FUSE. This allows installation of large* packages on LP32 builds. Since the mmap will otherwise fail due to out of memory.* --wipe_data - erase user data (and cache), then reboot* --prompt_and_wipe_data - prompt the user that data is corrupt, with their consent erase user* data (and cache), then reboot* --wipe_cache - wipe cache (but not user data), then reboot* --show_text - show the recovery text menu, used by some bootloader (e.g. http://b/36872519).* --set_encrypted_filesystem=on|off - enables / diasables encrypted fs* --just_exit - do nothing; exit and reboot*
Click to expand...
Click to collapse
any encryption can get disabled, thus all user-data beome fully readable: as I've shown some posts above this can be achieved running an ADB command whilst in Recovery mode.
DO NOT TAG ME ANYMORE BECAUSE I NO LONGER PARTICIPATE THIS THREAD.
despites that's all hypothetical (you never tested you just defend your fantasy) that requires root permissions to write on /cache (we don't have) furthermore 'disabled' is nothing else than 'destroyed' in that context and requires formatting. in no way the data can be decrypted/accessed like that (as already stated)
again, in stock recovery no adb commands work.