Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.
same problem!
kaelthuzad said:
Hello everybody,
I managed to brick my mate 8 as per the title, honestly thinking why did i even bother, that whole saying "If it ain't broke, don't fix it." applies here 100%.
So i have been in the NXT-L29C636B180 which i put with the dload method (original was C636B103) and since then everything was good, all except the video camera that is.
So i wanted to try to get to the nougat update (561?) but i read that you need the 211 first. As i couldn't find it i used the android app: firmware finder, and using the proxy method i told basically the system that a new update is up and download it - so this is the update option in the settings..
So after it downloaded NXT-L29C636B211 then it restarted, starting unpacking, and the installation stopped at around 5% when it restarted by it self. And that was it...
I am in a screen where i cannot use the touch, but only the buttons on the side and have the options
"Reboot system now"
"Wipe data/ factory reset"
"Wipe cache partition"
Tried the cache and rebooting, didn't do anything.
Tried wiping, and reboot, then i go in another page
"Huawei eRecovery" where it asks to connect to the wifi and download but then throws an error message "Getting package info failed"
That is pretty much it, i tried putting the update.app in the dload folder in the sd card and tried to use that method but it wouldnt boot that (used the volume + and - and power buttons) but it took me back to one of the above.
Am i out of hope? Is there anything i can do to restore it?
I really appreciate the help.
Click to expand...
Click to collapse
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.
crazynitro said:
That happened to me too. you will still be able to enter fastboot. plug your phone to your pc and and press and hold the power and volume down. that should take you to the fastboot screen.
find the appropriate twrp recovery for your phone and use the command
fastboot flash recovery "recovery name".img. wait till its done.
press and hold the power and volume down button till the phone reboots. that will takeyou to twrp recovery. there you could either flash b210 or the beta b521 -- which i am on.
Click to expand...
Click to collapse
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.
kaelthuzad said:
Thank you for the response. I will give it a try today after work i am a complete noob so its the first time for me to see what fastboot is, never heard of TWRP, i was always stock so never needed to mess with my phones.
If i recall doing power and volume down while plugged it was taking me to the page i mentioned to wipe the data, reboot or wipe the cache.
I managed to go to the fastboot page on the phone by pressing volume - and then plugging the phone to the pc. Now in the white page on the phone it shows, Phone unlocked in red. Does this mean just it is carrier unlocked?
So do i need to have the bootloader unlocked to do anything here? How do i do that? I cannot buy the code i suppose now since my phone is bricked i will have to go the Huawei way? And how do i do that, i saw a site to create a HUawei ID but in the registration page it didn't mention UK anywhere (where i live), mentioned Hong Kong and other Asian territories. I bought the phone from Wonda mobile, and being the 636 i would think its the asian model anyway.
Regarding TWRP, i didnt install it from before the phone was bricked will i still be able to do what you mentioned? And for the image i need to use, do i need to go to the firmware i was in before (636B180) or the one i tried to go to (636B211)? I can't seem to find the 180 anymore anywhere.
Sorry for the mass amount of questions, trying to sort it i have the phone for less than a year and i am gutted for messing it up like that.
Click to expand...
Click to collapse
did u solve it plz i have same problem
first download NXT-L29C636B170 here: https://goo.gl/dHk8r8 , download Huawei extractor here: https://forum.xda-developers.com/showthread.php?t=2433454 ,unzip update.zip from B170 firmware downloaded, go to huawei extractor and choose UPDATE.APP (from B170 firmware extracted), and extract only recovery.img, download ADB Command here: https://goo.gl/05Rx06 unrar and copy recovery.img into ADB Command folder, put your phone in fastboot mode, turn off your device, then hold volume - and fast plug your phone into PC, now you are in fastboot mode,go to ADB Command folder and hold shift, holding shift key do click right with the mouse,and click on: open command window, now write: fastboot devices, enter, and you can see your device are connect, now write: fastboot flash recovery recovery.img, enter, when it finished write: fastboot reboot, and enter, then the system reboot, turn off your phone, now put UPDATE.APP (from B170 firmware) into dload folder in sdcard, with your phone off hold volume +, volume -, and power at the same time, then you can update by dload method,wait it finish and the phone reboot, now you're running NXT-L29C636B170, and if you want update to NXT-L29C636B211 you can find here: https://forum.xda-developers.com/mate-8/general/huawei-mate-8-stock-firmware-official-t3391727/amp/ unzip the update.zip and put UPDATE.APP (from B211) into dload folder in sdcard (obviously you need delete the UPDATE.APP from B170), now go to dialler and press *#*#2846579#*#* and project menu open, choose Software upgrade>SDCard Upgrate and yes, the system reboot , wait it finish and reboot, and you're now running NXT-L29C636B211. if you have any problem just tell me.
sorry for my bad english.
Hello guys, right now i'm in big troubles with my FRD-L09C432. I tried to flash the rollback package (wich was working yesterday) but this time after the flashing process phone won't boot, i tried to enter recovery mode but i couldn't. Then i entered in fastboot mode and unlocked bootloader in order to reset the phone. I entered yes on the screen and the phone tried to reboot but now it is stuck on "your phone is unlocked..." and at the bottom: "your phone is booting now". But nothing happen and right now i cannot access recovery, or fastboot or even dload nothing works, i disconnected the battery and started the phone again but nothing... When i try to rebbot it in fastboot, recovery or dload mode it just vibrates twice and show the same screen with "your phone is booting now"
I'm really desperate i have never had a hopeless situation like that, i need your help, thanks a lot for any suggestion or idea that i could try.
:crying:
Up...
Rayan19997 said:
Hello guys, right now i'm in big troubles with my FRD-L09C432. I tried to flash the rollback package (wich was working yesterday) but this time after the flashing process phone won't boot, i tried to enter recovery mode but i couldn't. Then i entered in fastboot mode and unlocked bootloader in order to reset the phone. I entered yes on the screen and the phone tried to reboot but now it is stuck on "your phone is unlocked..." and at the bottom: "your phone is booting now". But nothing happen and right now i cannot access recovery, or fastboot or even dload nothing works, i disconnected the battery and started the phone again but nothing... When i try to rebbot it in fastboot, recovery or dload mode it just vibrates twice and show the same screen with "your phone is booting now"
I'm really desperate i have never had a hopeless situation like that, i need your help, thanks a lot for any suggestion or idea that i could try.
:crying:
Click to expand...
Click to collapse
Here is a link to my own experience of a similar situation.
https://forum.xda-developers.com/honor-8/help/reverting-to-stock-t3685909
And here is another link that might help.
https://forum.xda-developers.com/honor-8/help/honor-8-hard-brick-t3709598
I hope these will help.
srgrusso said:
Here is a link to my own experience of a similar situation.
https://forum.xda-developers.com/honor-8/help/reverting-to-stock-t3685909
And here is another link that might help.
https://forum.xda-developers.com/honor-8/help/honor-8-hard-brick-t3709598
I hope these will help.
Click to expand...
Click to collapse
Thanks dude i'll read that for sure
Unfortunately i have no access to fastboot that's why even DC Phoenix cannot do anything...
fastboot ... conect phone to PC. If the phone its on or off dosend matter.
After conecting to PC hold volume - and power buton (first volume- !) .... and wait a while ... it may reboot severel times. befor enter fastboot.
After enter fastboot try this https://forum.xda-developers.com/honor-8/help/honor-8-hard-bricket-how-to-restore-t3739551
I pray to access this damn fastboot mode dude but i've tried everything and i cannot get into it even when i disconnect/reconnect the battery
My opinion is that the phone tries to reboot in order to reset itself but smthg prevent it from rebooting correctly, a friend told me the boot is damaged/corrupted
Go to one of those high street repair shops. They fixed mine for 80 pounds.
The tech tried with his Huawei flashing box but he couldn't detect the phone...
Did your device got unbriked?
No i bought one with the screen broken and i swapped thé motherboards, but the other is still bricked
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.