[SOLVED!!] Recover data with TWRP after device is stuck on boot loop?

[SOLVED!!] Recover data with TWRP after device is stuck on boot loop? - General Questions and Answers

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.

Related

bricked huawei g730

hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help

SP log files attached
thanks

I have same problem.How to solve it.

same problem, what to do???

elkhopoa said:
hello there,
I have huawei g730-u10
"MTK6582, quadcore cortex A7, 1GB Ram, 4GB Rom"
last week, I was trying to install a CWM recovery using "mobile uncle" app. after it finished , a prompt for restarting appears and I pressed "yes".
it was the last time seeing my phone alive!!! it restarts to huawei logo for about 20 seconds and restarts again and again and again....
unfortunately my device doesn't have a rom online, even on HUAWEI website, so, I downloaded a similar phone ROM "hdc-s5-gold" to use its preloader, cache, boot , etc
the problem is when I connect the phone to SP flashtools the red bar appears and then it holds for seconds and a message with connection loss appears while the phone is going in its infinite restart.. so the flashtools seems to find the phone for a while but fails to write to it thanks to power loss.
notes:
1. I have tried many flashtool versions
2. I have tried with and without battery connection, and with and without volume up holding.
3. the phone can't access to CWM, download mode or factory reset mode.
4. the drivers are installed shows: "MT65xx preloader" and I think there is no driver problem
5. even when I connect the phone to charger, it keeps restarting and the charging logo doesn't appear
I appreciate any help
Click to expand...
Click to collapse
Universal unbrick guide:
Terminology - types of bricks:
Soft brick - often occurs in the shape of a bootloop or any other problems with booting such as always getting to recovery or not getting past the carrier logo. This type of a brick, which shows some signs of life, can in most cases be fixed.
Hard brick - As the name implies, your phone can essentially used as a brick and it shows no signs of life. This kind of a brick is rare and in theory should be unfixable. However there are advanced methods of fixing your phones such as JTAG, but they require extra tools and accessories.
The decision:
Is my phone soft or hard bricked?
If you answer yes to all of the questions below you probably have a hard birck:
Test as said in order!
Nothing happenes when you hold or press the power button
You cannot get the screen to even turn on by pressing or holding any combination of buttons on your phone
Nothing happenes if you do the same as about but with your phone plugged into a charger
Nothing happenes when you plug your phone into a computer
When you plug in your phone into a computer it does not recognize it as a phone, storage or any other media device
Nothing happenes when you try all of the above again, but with removing the battery in between steps for 10 seconds and putting it back in again
Nothing happenes when you try all of the above again, but after leaving the phone plugged into a charger for 2 hours
If all of the questions are a "yes", then you either have a broken charging port and and a discharged battery or you have a hard brick.
The unbricking:
There are many methods of unbricking and they are all different to each phone. Here I will list the most common methods that often succeed.
Samsung users skip to 4. method.
1. If you have access to a stock recovery:
Method 1:
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Choose “Wipe Cache Partition”.
5. Choose “Wipe Data / Factory Reset” to delete all your settings and apps, using the correct ROM.
6. Reboot your device.
Method 2:
Download the stock rom for your phone. It should be in ".zip" format. Make sure it's the official version
(Find it by Googling something like "[your phone model] stock rom")
Put the file on your phone's external SD card.
Make sure that the rom is for your exact phone model.
1. Shut down / turn off your phone.
2. Boot into Recovery mode – hold down the volume down button and then hold the power button (the button combination is different for every phone. Look yours up on Google)
3. Use volume keys to navigate the menus, and power button to select the menu items (Again, might be different for every phone)
4. Select "apply update from external storage"
5. Navigate to the zip file you copied to your phone
6. Install it.
If you get Status Error 7 that means you didn't download an official stock rom.
2. If you have access to a custom recovery:
Method 1:
Try stock recovery method 1
Method 2:
1. Find a stable custom rom for your phone or if you want to download the stock rom
Make sure that the rom is for your exact phone model.
2.. Copy the zip file to the phone's external SD.
3. Install the zip
(If you have a custom recovery you probably know the drill)
3. If you have access to fastboot mode:
First install ADB and fastboot drivers (if you haven't already):
To install it on windows there is a handy tool called the 15 Second ADB installer which will install pretty much everything you need.
On Ubuntu install with:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
On Fedora:
Code:
sudo dnf install android-tools
On OS X using Homebrew:
Code:
brew install android-platform-tools
Once you have the drivers installed you have to find a recovery image for your phone to install a custom recovery.
You can try one of the popular recoveries such as CWM or TWRP.
You need to get the recoveryNameHere.img file for your phone.
Find it by Googling:
"[your phone model] TWRP recovery"
or
"[your phone model] CWM recovery"
Make sure that the recovery is for your exact phone model.
Now on your phone enter fastboot mode:
Turn your phone off.
You can try different button combinations. For my phone it's holding power and volume down buttons.
Once you're in fastboot mode plug your phone into a computer and open your terminal/cmd.
Type in:
Code:
fastboot devices
You should see a list of devices. There should be only one device ID number.
If you see the ID it's working. If you don't you didn't install the Google USB driver properly (on Windows) and if it says "'fastboot' is not a recognized command" or "No command 'fastboot' found" then you didn't even install your drivers.
If you have problems with installing Google "how to install adb and fastboot drivers"
Now that you know fastboot is working type in:
Code:
fastboot flash recovery C:\Path\To\Recovery.img
Replace "C:\Path\To\Recovery.img" with an actuall path of the recovery file you downloaded.
It should say success.
If it doesn't try to execute:
Code:
fastboot oem unlock
This will delete all data you had on your phone (games, game progress, apps...).
Now try
Code:
fastboot flash recovery C:\Path\To\Recovery.img
again.
Once you're done type in:
Code:
fastboot reboot
And your phone should still not work. Now what you have to do it try the custom recovery method above (number 2.)
4. If you have a Samsung device:
Try this tutorial of unbricking with Odin: click here

Bootlop / cannot enter TWRP from Bootloader Menu / Power button stuck

Hi guys,
I currently have some issues with my beloved N5. I try to be as specific as I can (therefore the text will be a bit longer)
First things first: My device is experiencing the well known "stuck power button problem".
But I also do have problems which are not related to that one (at least thats what I believe).
Overview:
CM 13.1
ElementalX Kernel
TWRP on 3.0.20
Main issue: I can not start my phone regularly. When not plugged in, it just does not respond at all.
If it is plugged in I can get into the bootloader with only pressing Volume down (because the power button is stuck inside). Weird fact #1: in bootloader the power button should work to confirm a specific task like Start, or boot into recovery but it doesnt. Also: the phone is steady in the bootloader and does not keep rebooting.
Therefore I wanted to perform a backup (nandroid or at least all media) and reflash my ROM to see whether it is more of a software issue. I tried booting into TRWP which is not working (device shuts down after Google logo (might be because of the power button issue?).
I know that I can flash the recovery again through adb or the Nexus ToolKit but obviously I want to save my data first.
As far as I know there is no option as adb pull or through the recovery to save those only being in bootloader mode, am I right?
Question: Can I dirty flash without losing data? If thats not the cure, what else could help?
Other facts to know: while running
Code:
adb devices
I get that the
Code:
"adb server version (36) doesnt match this client (35): killing...
but then:
Code:
*daemon started successfully*
(same in Nexus Toolkit).
If I continue with
Code:
adb backup
it says: no devices / emulators found. Altough the nexus toolkit (and fastboot devices) say:
Code:
FASTBOOT: 03181238e07723e0 fastboot
If you made it until here thank you for reading :good: and I would be even more pleased if someone could help.
Best,
McRacoon

I have this problem to , i cant use my volume and power button in ROM / TWRP ,

I got lost, which data you want to save ?
fastboot flash boot recovery.img | fastboot reboot than gets you to recovery from where you can save data.

@Redchi: not really exactly my problem but if you can get into recovery you can use your touchscreen in TRWP?!
@icrunchbanger thanks for your reply.
I want to save all my data like videos, pictures, whatsapp chats etc.
I know how to flash the recovery (again). The question was whether I can save any data without a working recovery (just from the bootloader). Imo it is not possible but maybe you guys know how to do so.
If I reflash the recovery I still can not enter it as the phone reboots itself every 5 seconds due to the stuck power button. The reflashing operation is not finished (Nexus Toolkit says: "Waiting for your device" and times out after a while) and the battery icon pops up every 3 seconds.
Edit: and yes I tried several workarounds to unstuck the power button like flicking against the button, tapping on table, cleaning etc. The only thing I haven't done is tearing the motherboard apart and replacing the whole button itself.

I recommend removing the motherboard, applying pure alcohol around the area, and then quickly pressing and releasing the power button? If this doesn't work, I suggest replacing the power button.

i can use button to get bootloader + TWRP , but my Button volume up down and power cant use in Rom or TWRP, i do no this software or hardware ,? my nexus normaly use but not have button , I use mikey or double tab to wake get screen on , i use apk to get volume , sorry bad english

[Completed] Recover a non-working Hipstreet Spectrum

Hi everyone. I have a Hipstreet Spectrum that currently will not boot.
At one point last year, I attempted to install google play onto what is essentially a Chinese tablet (hipstreet) and messed something up. I can't recall what, but I do know it was just a matter of installing apks - I didn't try to flash the device - was surprised I was able to soft-brick it
The tablet will attempt to boot several times, and then auto-enter the recovery menu. Boot does not make it past the Hipstreet Spectrum splash screen
From the recovery menu, I have options to reboot, apply update from adb, apply update from sdcard, wipe data, wipe cache, and wipe media.
I'm asked to select an option using the volume keys, of which this particular tablet has none.
Using adb, I do not have access to /system or /data (then are listed as empty).
Using adb, I do not have access to shell as /system/bin does not exist
Using adb, I am unable to mount /system as I get error code 0 ("remount failed: Success")
I can't send volume input event codes from adb as I do not has access to the shell
The tablet has a reset button you can press with a paperclip - doesn't fix the boot issue
adb reboot bootloader seems to turn the device in a charging state
adb reboot-bootloader seems to turn the device in a charging state
adb reboot fastboot seems to turn the device in a charging state
When the device is in this "charging state" I need to hold the power button down to turn it off. When I press it again it will attempt to boot
My PC does not see the device when it is in this "charging state"
By "charging state" I mean that the device display turns off, then shows the "battery filling" animation.
I opened up the tablet and there are no hidden volume buttons
Was unable to find a way to read any sort of boot logs - no even sure where the device is in the boot process
Any ideas on what I can try next?

darkphoenix16 said:
Hi everyone. I have a Hipstreet Spectrum that currently will not boot.
At one point last year, I attempted to install google play onto what is essentially a Chinese tablet (hipstreet) and messed something up. I can't recall what, but I do know it was just a matter of installing apks - I didn't try to flash the device - was surprised I was able to soft-brick it
The tablet will attempt to boot several times, and then auto-enter the recovery menu. Boot does not make it past the Hipstreet Spectrum splash screen
From the recovery menu, I have options to reboot, apply update from adb, apply update from sdcard, wipe data, wipe cache, and wipe media.
I'm asked to select an option using the volume keys, of which this particular tablet has none.
Using adb, I do not have access to /system or /data (then are listed as empty).
Using adb, I do not have access to shell as /system/bin does not exist
Using adb, I am unable to mount /system as I get error code 0 ("remount failed: Success")
I can't send volume input event codes from adb as I do not has access to the shell
The tablet has a reset button you can press with a paperclip - doesn't fix the boot issue
adb reboot bootloader seems to turn the device in a charging state
adb reboot-bootloader seems to turn the device in a charging state
adb reboot fastboot seems to turn the device in a charging state
When the device is in this "charging state" I need to hold the power button down to turn it off. When I press it again it will attempt to boot
My PC does not see the device when it is in this "charging state"
By "charging state" I mean that the device display turns off, then shows the "battery filling" animation.
I opened up the tablet and there are no hidden volume buttons
Was unable to find a way to read any sort of boot logs - no even sure where the device is in the boot process
Any ideas on what I can try next?
Click to expand...
Click to collapse
Greetings and welcome to assist. It looks like you have tried almost everything already, if you can get the original rom from the manufacturer you could install it from sd card. You can also try sp flashtools as well
Good Luck
Sawdoctor

Shield Tablet problems: ADB, Recovery Mode, Fastboot... = DEAD?

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!!!

Question TA-1188 in red state, can't unlock bootloader and OS won't start

I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.

J_029 said:
I tried to downgrade from Android 11 to Android 10 a few months ago. Back then I had no knowledge about everything related to Bootloader Unlocking and other things.
I followed a tutorial. But my phone got bricked. So I followed an unbrick guide a few months later. I got it back to a state where I have basic Fastboot access.
But when I try to start the phone, is says Red State, Your device has failed verification. Incorrect Signature. Please download Image with correct signature or disable secure boot.
Now I don't have the Bootloader unlocked. I also can't do that with Fastboot. Results in the error that I am not permitted to do that. I also tried flashing TWRP but it says:
'download for partition 'recovery' is not allowed'.
Is there a way to get it working again? I would really need this phone again.
I have not made any backups. Also It says in Fastboot that my device is called: 0123456789ABCDEF. I dont think that is good because other phones I used fastboot on had a normal name.
Click to expand...
Click to collapse
I'm dealing with that issue right now and my device won't even charge or turn on. Let me know if you find a fix. Did you try mtkclient already?

I have found a solution to fix red state. I also unlocked the bootloader afterwards and rooted the device.
The solution to fix red state is as following:
1. Go to: https://androidfilehost.com/?fid=2188818919693749336 and download the firmware (Its from FIH-Firmware.HikariCalyx.com Tutorial how to unlock bootloader)
2. Open SP Flash tool and load the firmware using the scatter file called MT6761_Android_scatter.txt
3. Select Format + Download and klick the download button
4. Now take your phone (Make sure to have it connected to a charger for over an hour bevore doing this, even tho the charging symbol might not show up) and hold down the volume buttons and while holding them, connect the phone to the pc using usb cable.
5. Wait for it to finish downloading.
6. When complete you should be able to start into fastboot. That can take up to one minute. Try putting the battery back in if it doesnt start after holding buttons over a minute.
7. When in fastboot, make sure the drivers are loaded. For this go into Device Manager. If there is an unknown device called Android, select update Driver > Search on my Computer > Select from a list. Then scroll down to TCL and then select Android ADB Interface. The device manager might tell you that it might not be the correct driver, but just continue.
8. Type into ADB and Fastboot window:
fastboot reboot recovery
9. When you see android laying on its back, hold power button and press volume up button (sometimes you have to press it 6 times), then the recovery menu should open up. Now select Wipe Data Factory reset. Select Yes and let it reset. After that start the phone again.
10. Your phone should start normal now. The startup can take up to 10 minutes. if it hasnt started after 30 minutes, repeat the procedure to reset it.
11. To get IMEI back, you have to unlock the bootloader and root the device. If you want to do that tell me. Its a bit complicated but i can tell you.
Make sure to follow the steps exactly

Thanks for the response, my device is a mt8163 and I have mtkclient if I can find the proper firmware what command would I use to flash the file

Database Info

welcome