Hi. I've recently bought my TF700 and upgraded to JRO03C.US_epad-10.4.4.25-20121228 (JB 4.1.1). Now I want to root my device, so I first unlocked the bootloader using the ASUS unlocker. That went fine, since it says "the device is unlocked" in the boot sequence. The device boots and works properly.
Now I wanted to get to the stock recovery mode for a backup, but it fails miserably. I get to the four icon menu (RCK, Android, USB, Wipe) and select RCK. Then an android icon with a blue rotating icosahedron in its chest apears for a couple of seconds and then a "dead" android with it's cover opened and a "!" enclosed in a red triangle. After a couple of minutes, the device reboots normally (I can force that by pressing down the power button for 10 seconds).
I tried to get to fastboot by choosing the USB icon, but it does nothing (just freezes in the four icon screen and stops responding to any other buttons); the PC doesn't see an USB device of any kind. I tried connecting the USB cable both before and after selecting the USB icon with no difference. I'm sure I have at least some good drivers because I can use adb with my device when the OS is running.
I'm new to this device, so I may be doing something wrong. Any suggestions? Thanks in advance.
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
_that said:
The stock recovery can only apply stock updates, you cannot use it for making backups.
Fastboot mode should display some message similar to "fastboot protocol enabled", the rest appears to be driver problem on your PC. Fastboot mode uses a different USB ID, so having ADB working does not mean that also Fastboot will work.
Click to expand...
Click to collapse
Thank you, _that. Whatever drivers it might need, I cannot install them because no USB device of any kind appears in my computer besides my keyboard. I think I should be getting "Starting Fastboot USB download protocol" or something. How can I get fastboot to work?
Sorry, it seems it was a USB port problem! I changed the port and the fastboot device is now available in my PC. Fastboot is now able to send commands like 'reboot' to my device.
Thanks for your clarification about the stock recovery mode, _that.
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
georgepcde said:
Perhaps try to reboot into bootloader manualy. For this first switch off your device, then press power button and volume (-) together. As soon as the tab vibrates, release the power button and switch the screen lock two or three times. Then you should get into the bootloader mode and can try to use the adb commands. Of corse, with a connected usb cable.
Sent from my A700 using xda app-developers app
Click to expand...
Click to collapse
Good thought but no luck.
Thanks, though.
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
rgkjr1 said:
Hi All:
First-time poster here. I searched the forums but could not find an answer to my problem.
I want to root my A700 and install a custom ROM but I can't get the bootloader unlocked. I have followed the instructions from this post but can't get past the first step. ADB definitely recognizes my device [adb devices] by returning the correct s/n. When I enter [adb reboot-bootloader] my tab reboots but then hangs on the green Acer logo and goes no further. Any attempts to use ADB result in a "waiting for device" message. My only option is to power off by holding the power button then reboot normally.
Here's my device/PC info:
A700:
Android version: 4.1.1
Kernel version: 3.1.10+
Image version: Acer_AV051_A700_RV18RC01_PA_CUS1
Build Number: Acer_AV051_A700_1.052.00_PA_CUS1
PC:
Windows 8 Pro 64bit
Android SDK 64 bit (I also tried 32bit with no luck)
I have rooted devices before so I am not totally new to the process, but no expert either! Any thoughts?
Thanks in advance for any advice/info shared!
Note: Had to use Acer USB driver for ICS. There was no USB driver for JB. Could that be the problem?
Click to expand...
Click to collapse
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
smirneger said:
After rebooting with "adb reboot bootloader" you should be in the bootloader, and in fastboot mode. Try issuing "fastboot devices" after rebooting.
Edit: Just tried the unlock guide from that thread, and with the ICS driver from Acer. Getting the driver to install was way worse than unlocking the bootloader (many "installations" that didn't create any files for whatever reason).
After ADB recognized my tab, I was able to follow the guide up to the "flash recovery" part.
- with "adb reboot-bootloader" you should land in the bootloader. It only shows the Acer logo and some very small written things in the upper-right corner;
- from here on you need to use fastboot: "fastboot oem unlock". Typing "fastboot devices", as I said before, works just like "adb devices";
- the whole unlocking procedure is very frustrating, because the instructions are so small and the timeout so fast. If I'm not mistaken, you need to choose with VOL- and confirm with VOL+.
PS: pmrmx was faster
Click to expand...
Click to collapse
pmrmx774 said:
After the ADB reboot-bootloader, there should be some really tiny white type in the upper left corner of the green logo screen.
This is when you type "fastboot OEM unlock" then volume +, then volume -
The tiny type should change. Forever after you will have a tiny message up there about the bootloader is unlocked.
Click to expand...
Click to collapse
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
rgkjr1 said:
Unfortunately, the problem is that the little white text never appears - that's where it hangs - the screen is completly blank except for the green Acer logo. And if I try to enter "fastboot devices" I simply get another adb prompt (nothing else - it just jumps to a new line.) If I enter "fastboot oem unlock", adb returns "<waiting for device>" and then goes nowhere. All the while, for both commands, the tab is stuck on the Acer logo.
Click to expand...
Click to collapse
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
hey_joe said:
You probably need to install adb USB drivers ( android universal USB driver I think which is different than the Acer USB driver ). While adb will work when tablet is in USB debugging mode, once it rebooted your PC can't communicate with it anymore that's why its waiting for the device.
Sent from my A701 using xda app-developers app
Click to expand...
Click to collapse
Thanks, hey_joe. I actually already tried that but decided to try again. This time it worked! I don't know what I did differently but bootloader is now unlocked!
Thanks, All!!!
Tablet ubislate 9ci hanging on bootloading
Dear sir/madam, I am new to this forum. I purchased a new tablet Datawind Ubislate 9ci. It is a 9 inch no-bluetooth tablet.
>Details:
>*.Android 4.1.1
>*.Rock chip RK2928
>*.KERNEL linux version 3.0.36 i was trying to install CWM through mobile odin and ROM manager but my tablet was not supported so i downloaded build.prop editor from google play and changed it to some other cwm recognizable model viz. Samsung, nexus etc. When i was doing the above mentioned procedure, suddenly my tablet is coming up to bootloading and hanging there only and not opening i tried to go to recovery by pressing power and vol but i am not getting recovery menu, i also tried to hard reset by pressing reset with a needle at the back but all in vain again hanging on bootloading i also tried press and hold power & vol- and several other combinations , all in vain so kindly help me and guide me Thank you
Hello there. First of all thank you for your support. I'm here because I have the same problem as OP, but first a little context.
I have already rooted my A700 before, without any difficulties. But after a crash, I restored it to factory and tried to redo the whole procedure.
So, here I am, USB driver installed (I had to modify android_winusb manually for windows to finally accept the drivers), adb up and running, adb reboot-bootloader executed and...
Acer screen, no text, just like the OP. And a yellow "Fastboot" device in my Device Manager window. So I'm stuck here. I've tried to uninstall/reinstall the google USB drivers to no avail, unlike OP. I can access the Acer recovery with the reboot recovery prompt, but I'm not confident enough to ignore the step in this tutorial.
Additional precisions : when the device is stuck with the Acer Logo (without text) trying to use a fastboot prompt (like oem unlock) only gives me the <Waiting for device> message.
I could use the Acer recovery to install a rom from external storage, but I'm unsure if it's a good idea to NOT use CWM or TWRP
Thank you, I'm starting to miss Android 4.4 (yeah, because the Acer update manager give an error 400)
Update : I did manage to access fastboot. Just as I had to modify android_winusb with the PID of my tablet when it was running, I also had to edit the file with the PID of the tablet waiting in fastboot. I didn't noticed they were different.
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
After you use the volume down key to highlight "Fastboot", do you then press the volume up key to select it? If you just sit there and wait it will reboot normally. You must press the volume up key after you've highlighted the menu option.
akkay1 said:
Dear All,
Please help me regarding fastboot. When I press 3 keys (vol-up, vol-down and power key) while phone is off. I see the black and white screen written boot modes. From there when I select AP Fastbood device is restart with red Motorola logo and end up on home screen.. I have tried several times to turn off the device and repeat this process but no issue still there..
Moreover, if I did not select any options from boot modes than device automatically rebooted after 3 or 4 seconds..
Please help me out.. I want to unlock the boot loader root and install custom ROM..
Currently Model Number is XT925 and device is completely stock.. never rooted before...
thanks and regards,
Click to expand...
Click to collapse
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.
Thank-you for the Response
bweN diorD said:
try this,
-install adb on your pc
-plug in phone when powered up
- open a command prompt in your adb dir
- type in: adb devices then enter. it should show your phone in the prompt. also check your phone, there may be a popup to acknowledge.
- rerun adb devices until it shows your phone properly or you cant proceed
-now type in: adb reboot bootloader
if it works, the phone should reboot to the fastboot screen.
if it doesnt stick in fastboot, im sorry but i dont know what else to tell you to try.
Click to expand...
Click to collapse
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.
akkay1 said:
Thankyou so much for the reply, i followed your instructions and finally get in fastboot mode and unlocked the boot loader. However, is there any way from which I can go into recovery.. because through hardware way I am unable to go in recovery. Thanks
EDIT: I have tried entering command adb reboot recovery, then phone was rebooted and there was green android on screen with chest open.. thats it... i have waited for few minutes and rebooted the device mannually.
Click to expand...
Click to collapse
That's the entry to stock recovery. You have to push a combination of buttons from there to get into recovery. I forget the button combination, it has been posted many times, try searching or wait for someone else to jump in with the answer.
Sent from my LG-VS980 using XDA Premium 4 mobile app
Not sure where to post this question been reading so many post my eyes are tired......
- XT926 upgraded to kitkat 183.46 last week via flash in RSD from JB 4.1.2
- Root went well DONE (Towel root .apk)
- Unlock went well DONE (Motopocalypse .apk) yes fastboot shows the #3
- Flashed TWRP 2.7.1 DONE (did it using the adb in motopocolypse)
- Backed up my current stock ROM in TWRP seemed to go well the program confirmed the backup was successful...So I thought
- Got confident and wanted to try flashing CM11 (Kitkat version)
- After flashing CM11 my phone got stuck at boot like many others have.... no problem I backed up my stock ROM in TWRP.....So I thought
- Went to restore my stock ROM using TWRP and yup you guessed it like many others the restore failed half way through
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????
wonka144 said:
Not a big deal starting fresh can be a good thing BUT I really need my old text messages and all I have is a USB backup of the phone (Internal/SDcard) on my PC and of course the TWRP back-up on the SDcard that won’t restore ...... Is there any way to get these messages back to my phone????
Click to expand...
Click to collapse
Not sure how to help you with your immediate problem at hand, but going forward, I definitely recommend the sms backup + from the Google Play Store. Nice thing with that app is, you can link it to your gmail account, and all your text messages are backed up to your gmail.
Hello everyone!
I'm trying to root my Shield K1 (Android 6.0) since hours, without success because:
I have no acces via adb. Im using the latest adb and also the right drivers (see picture) but I alwas get the message "unauthorized" in adb.
I can't boot my tablet into fastboot mode. When I press the power button + volume up to come into the menu and I select fastboot protocol, the tablet just starts again into the same menu - so i don't get into the fastboot mode. Pressing the powerbutton + volume down don't works either.
I have tried already almost everything: uninstallig drivers/reinstalling it, factory reset on my K1,...
So how I can root my phone without adb or fastboot? Can anyone help?
Even the recovery mode is broken I think, after booting into it, the green android with an red triangle is shown.
Is there something wrong with my K1?
PS: In the menu, which is shown after pressing power + volume up, is standing:
[nvtboot] (version UNDEF_BUILD]
[bootloader] (version UNDEF_BUILD]
Device - locked
You need to enable USB debugging in the developer settings and then allow debugging access from your computer by accepting a popup on your tablet.
Yes, I know this and I did this of course. But there never poped up something on my tablet.
So I also resetted the debugging setting, wiped the tablet, but nothing helped.
1. Sometimes the micro USB cable you use can be bad so I would suggest trying a different cable (especially since you have a K1 which doesn't come with a charger or cable).
2. Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen. Also, recovery mode on the stock tablet just shows the android icon and triangle, so your recovery mode is fine.
I would suggest booting the tablet into android (so not the fast boot or recovery mode) and connect it to the windows PC using different cables until the authorisation pop up come up.
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
fl4r3 said:
Fastboot mode is that screen with the menu, that's why "fastboot protocol" just takes you back to the same screen.
Click to expand...
Click to collapse
Thanks so much mate! :good: That's the sentence, that helped me. I didn't know this menu is already the fastboot mode. So if one know this it's quite easy to proceed.
Problem solved - tablet already rooted
The adb access is still "unauthorized" but doesn't matter anymore.
No problem, glad you you got it sorted.
It's odd your ADB access is still unauthorised, but at least it still works.
jpk17 said:
I am having the same issues as the OP, the only difference is my bootloader says "unlocked."
I was able to get authorization from the computer, no issues there, however fastboot will not find the device and neither will adb when at the "fastboot mode."
I'm trying to get fastboot so I can flash a recovery, but no luck to this point.
Anyone have any ideas or suggestions?
Click to expand...
Click to collapse
Just as an FYI....I got mine working. Needed to reinstall the nvidia drivers... Got authorization, etc... so assumed working and as we all know assuming is bad!
Sent from my wx_na_wf using Tapatalk
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.