I have a pixel 4a with stock rom and recovery that is boot looping after an update. The device has a couple pictures I would like to recover and I was hoping I could use adb to pull those files from the device. The device does have a passcode that I know and and I am able to boot into resuce mode and run "abd devices", and it shows the device in rescue.
When I try to run, "adb shell ls, I get "error:closed"
I tried abd pull "/sdcard/DCIM" and received, "adb: error: connect failed: closed"
Any help is greatly appreciated!
This might be an obvious question, but have you tried booting up in safe mode?
JohnC said:
This might be an obvious question, but have you tried booting up in safe mode?
Click to expand...
Click to collapse
I read holding the power button and tapping the logo was the shortcut but that did not do anything. How do you boot it in safemode?
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Edit: Important: Safe mode removes some Home screen widgets.
JohnC said:
I think these are the steps:
When your phone is off
- Press your phone's power button.
- When the animation starts, press and hold your phone's volume down button. Keep holding it until theanimation ends and your phone starts in safe mode.
- You'll see "Safe mode" at the bottom of your screen.
Click to expand...
Click to collapse
I found that as well and just tried it a dozen times and I never get any safe mode idication at the bottom the screen. I only get a Google logo with a progress bar that never finishes.
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
JohnC said:
What version of android did the phone have, and what type of update did it try to do? (And OS Upgrade, or a security update)
Click to expand...
Click to collapse
Its running Android 11
It shows 11/RQ2A.210305.006/7119741 in recovery mode. It would have been up update pushed just before 4/4/21. I think it was security updates but I do not know how to verify that. My other Pixel 4a phone updated last around that same time and shows 11/RQ2A.210405.210305.005
This unfortunately is now outside of my experience, so I would be just guessing at this point.
So I was able to get into fast boot and use the flash utility provided by Google and Google chrome to detect the device, but when I try to flash it with sunfish i get an error about "oem unlocking" but I will have to dig further tomorrow. Hoping that I can get it to do something.
That error might be because your bootloader is locked, so it can't flash a new boot image to it.
The only way I know to unlock it is from the developer options in the settings, but that would require the phone to be able to bootup.
Adb sideload the stock OTA in recovery
Glad to hear that
Related
I have managed to get the PCeU Ransomware onto my Tab and now when I turn it on i immediately get the splash page asking me to pay up.
No matter what i do to try to get into Safemode or Recovery Mode it is no good I simply get the splash page up which prevents me getting any further in my attempts to remove it.
Any suggestions would be gratefully appreciated.
I forgot to add that the usual method of getting into recovery is as far as I know the power button and volume up after turning the device off first (I have tried up and down volume as well)....i feel however that the device never completely turns off as when I hit the turn off option on the lock screen it shuts down but i dont feel the vibration that i used to get when it did this.
Trasnadunta said:
I have managed to get the PCeU Ransomware onto my Tab and now when I turn it on i immediately get the splash page asking me to pay up.
No matter what i do to try to get into Safemode or Recovery Mode it is no good I simply get the splash page up which prevents me getting any further in my attempts to remove it.
Any suggestions would be gratefully appreciated.
I forgot to add that the usual method of getting into recovery is as far as I know the power button and volume up after turning the device off first (I have tried up and down volume as well)....i feel however that the device never completely turns off as when I hit the turn off option on the lock screen it shuts down but i dont feel the vibration that i used to get when it did this.
Click to expand...
Click to collapse
Try to force reboot recovery by using "adb reboot recovery" and wipe data and cache from here. If you want you can save data from TWRP
Greets
If you can get to download mode and reflash stock rom, it might work!
Cant get to download mode unfortunately. Is there any idiots guides for instructions for "adb reboot recovery"?
Scratch the above.. I found the above and was able to run the command prompt but the device does not appear to be found and when any command is run i get error: device '(null)' not found.
I can see the files on the device in Windows explorer however so would have assumed the drivers when correct.
I suspec the issue is that I cant get into usb debug because i cant get past the blasted ransomware splash screen.
Trasnadunta said:
Cant get to download mode unfortunately. Is there any idiots guides for instructions for "adb reboot recovery"?
Scratch the above.. I found the above and was able to run the command prompt but the device does not appear to be found and when any command is run i get error: device '(null)' not found.
I can see the files on the device in Windows explorer however so would have assumed the drivers when correct.
I suspec the issue is that I cant get into usb debug because i cant get past the blasted ransomware splash screen.
Click to expand...
Click to collapse
Hard boot into recovery and then factory reset. Vol Up + Power until screen pops up then keep holding just volume up.
Ok I won’t go into how I bot myself here but here’s where I am. Unlocked bootloader, no recovery, no rom, USB devices command isn’t showing anything anymore. When I boot it just sits in the white screen with the G for ever. I can hardboot to bootloader and when I try to boot recovery I just get a black screen with a picture of a dead android.
Please refrain from calling me an idiot as I’ve repeatedly told myself that many times.
Can anyone help me out of this???
Thanks
When you are on the screen with the broken Android hold the power button and volume up it should bring you to recovery I believe. It might be even hold the volume up first then tap the power key.
kotton666 said:
Ok I won’t go into how I bot myself here but here’s where I am. Unlocked bootloader, no recovery, no rom, USB devices command isn’t showing anything anymore. When I boot it just sits in the white screen with the G for ever. I can hardboot to bootloader and when I try to boot recovery I just get a black screen with a picture of a dead android.
Please refrain from calling me an idiot as I’ve repeatedly told myself that many times.
Can anyone help me out of this???
Thanks
Click to expand...
Click to collapse
eevanskiteboards said:
When you are on the screen with the broken Android hold the power button and volume up it should bring you to recovery I believe. It might be even hold the volume up first then tap the power key.
Click to expand...
Click to collapse
Thanks eevanskiteboards, the tip about booting when I had the dead android screen got me out of the ****. You're a legend! I had to hold the up volume and tap the power.
my steps were, for anyone else,
1. hardboot to bootloader
2. choose boot to recovery
3. screen with dead android , hold power button and tap up arrow
4. stock recovery appears
5. choose ADB sideload
6. sideload full OTA update from google after wipe.
7. profit!
interestingly when I did ADB Devices the phone never showed up yet I was still able to sideload?
anyhow now I am back to Oreo and I can try and get root again which I was unable to with Pie
I'm glad you made progress!
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
NZedPred said:
Use power and volume down (not up) to go into Fastboot mode. Then flash the stock images
Click to expand...
Click to collapse
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely shut off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
mycalculations said:
I tried that, but whenever I press any button, the phone is never turning completely off unless it dies. Even after that, it goes to the screen showing the secure boot integrity(Press power to continue/stop boot)
How can I completely **** off the device and restart it? And if system is messed up, will that leave my bootloader intact(I'm assuming so as boot is a different partition?)
Click to expand...
Click to collapse
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
NZedPred said:
Does holding down the power button for 5-10 seconds turn it off? Or if you do that does it appear to turn off and then restart?
If that fails to turn it off, try just holding power and volume down for 5 seconds, and if the screen flashes (goes off and then on) let go of the power button but keep holding volume down and hopefully it goes into Fastboot.
That should work unless you have a dodgy power or volume button. The bootloader is completely separate to the boot partition, and the fact that it's doing anything at all suggests that it's still functioning.
Only other option I can think of is trying ADB commands when it's in recovery mode, e.g. adb reboot bootloader. However, if you have the stock recovery, that may not work.
Click to expand...
Click to collapse
Thank You!!! It didn't work in the bootloop, so I had to let the phone drain its battery and shut itself off, then I was able to enter the bootloader and reinstall lineage. Thanks so much!
mycalculations said:
Hello, I recently came on a pixel phone to build and use lineageOS on. Upon rebuilding, I believe I performed adb sync wrong the device and damaged system. After that, my adb keys became unauthorized and I am unable to access the bootloader menu(I press power and volume, but phone boots into Bootloop). I tried the steps to get to bootloader menu, but the phone doesn't power completely off, and when I press the power button it gives me the launch screen saying press power to pause/continue boot, not allowing me to go into bootloader
My bootloop goes like this: Bootloader integrity screen(bootloader unlocked, cannot be verified) --> Google loading screen --> Android recovery. This shows 2 options with the message, "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device". The two options are to try again or data reset.
I press try again, and the same bootloop ensues, sometimes getting to lineage loading logo, but then back to the same recovery error regardless. If I press the buttons(power and vol up), to go into recovery, it just shows an android with a warning sign above it, giving a message saying "Error!" on the bottom. My adb on the computer shows as unauthorized, so I don't know how I can fix this. Google has said the warranty is expired and cannot do anything to help. Ideas to fix? Thanks for help in advance!
Click to expand...
Click to collapse
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
LANDTESTER said:
Similar problem when i try to flash pixel dust rom through adb sideload... After successful installation reboots to system through twrp it shows no os installed then after i cant get to bootloader only black screen shows no display and now on pc phone not detecting .... connect and disconnect sound is there but nothing on screen
Click to expand...
Click to collapse
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
Oh so after that i can get to bootloader .....hmm let me try thanks bro
mycalculations said:
Is ur bootloader unlocked? If so, use twrp to perform a full wipe and install from twrp as well. Of you can't access trwp, and are in a bootloop, do the same thing I did: let the phone lose all it's battery, so it's outta the loop, connect the phone to a charger, then hold power and volume down. This should get you into bootloader mode where you can then use fastboot to flash twrp.
Click to expand...
Click to collapse
My bootloader is unlocked but phone not detected on pc only black screen nothing else.... Red light flashes whenever connect to charger
I made the mistake of Factory Resetting my phone after a few failed attempts at remembering the Pattern to unlock the phone, in doing so I ended up being stuck in the set-up process because I forgot the Google account I was logged into on it before the Factory Reset, had been an account I just quickly made on the spot months ago just to set up an app on it. I'm posting here for help with this since I'm on day 4 of trying to find a way to bypass this and my head is ready to explode. I feel like someone with a fresh mind would be able to point me in the right direction.
If anyone can let me know if I'm doing something wrong or missing some steps that will help me try any one of these, or honestly any advice at all... I'd very much appreciate it and it'd help relieve a huge chunk of this ridiculous headache this has all been.
Thanks in advance!
What I've tried thus far --
- I know for most ways around this, USB debugging needs to be enabled. But since I cannot get past the initial set-up process, I can't access the settings to enable it.
- I also know that for a lot of Android devices USB debugging is enabled by default in Recovery Mode but everywhere I've searched for the hardware combination to boot into Recovery/Download mode, all say the same thing:
Turn phone off > Power up with Vol. Down + Power button until 'Download Mode' is displayed (for boot into Download mode, while holding Vol. Down + Power button plug OTG cable into device)
- My problem with this is that on my device, Vol. Down + Power button, restarts the phone. So instead of 'Download Mode', I'm just restarting the phone over and over again. I was able to get my phone to boot into was Safe mode using the Power button + Side button.
- I've also tried getting around this through a series of steps which involved the 'TalkBack' accessibility feature, but when I try toggling to enable it I just get a message saying "Complete setup first to continue"
From there --
I started looking up Stock ROMs that I'd be able to just flash the firmware. But for the life of me, I cannot seem to find anything for this device. And this is where I'm pretty much at now.
To remove FRP lock you boot into phone's Recovery mode and apply
1. Wipe data
2. Factory Reset
Every Android device gets shipped by default with Android Recovery.
xXx yYy said:
To remove FRP lock you boot into phone's Recovery mode and apply
1. Wipe data
2. Factory Reset
Every Android device gets shipped by default with Android Recovery.
Click to expand...
Click to collapse
I can't get my device to boot into Recovery mode. Everywhere I look up, it tells me to Power off device, then Press Vol. Down + Power key until the menu appears. But on my device, all that combination does is force the phone to restart.
Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Bafif said:
Device:
- Samsung Galaxy A12
- Rooted
- Magisk and Magisk Manager both updated
- Model sm-a127m
- Problem context: I could not find a recovery for my particular model and during the rooting process I somehow ended up not being able to access the recovery, after a long time I tried to install one from the TWRP Official App and this ended up happening.
Click to expand...
Click to collapse
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
bmwdroid said:
Going back to stock by flashing latest via Odin is what I would do and then start from scratch.
You took TWRP for a125f didn't you?
They have very different hardware, but I think it will work to return to stock.
Click to expand...
Click to collapse
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Bafif said:
Instead I re-flashed twrp, this time a version supposedly for a127m unofficially and the phone ended up blinking on and off a totally black screen. Now it doesn't enter download mode or recovery mode and the computer doesn't recognize it. I'm pretty ****ed up.
Click to expand...
Click to collapse
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
bmwdroid said:
Was it fully loaded before you started?
Is it possible that the battery is empty?
I'd leave for hours connected to the charger and test tomorrow again to get into download mode.
Click to expand...
Click to collapse
The battery is fine, it was loading almost the whole process because I flashed the last time from the PC and was at 70% before starting. The only thing it does since yesterday (it was not turned off at any time) is to flash between the screen turned on showing pure black color and the screen off.
If I press Volume Down Key and power key what it does is not to enter the Download Mode as before but show the Samsung A12 logo and then the warning of "unlocked bootloader" with the "Press Power Key to continue", then the same screen From Samsung A12 but with a warning of Custom Software and then begins to blink again.
I cannot turn it off or enter the recovery mode or enter the download mode. The battery is inaccessible to me although I could find a way to do it if it served something.
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
bmwdroid said:
@Bafif one last idea:
did you enable USB debugging in dev options before?
Then adb commands might be working.
1 To test if adb can see it (device connected to PC) :
command <adb devices>
Perhaps necessary to enter twice.
If yes you'll see a notification on the screen.
2 Then you can <adb reboot bootloader> to enter download mode.
If you don't get the notification I'm probably not able to give any further hints.
Click to expand...
Click to collapse
No luck, I guess it's bricked
PS C:\> adb devices
List of devices attached
PS C:\> adb reboot bootloader
error: device not found
PS C:\>
Bafif said:
No luck, I guess it's bricked....
Click to expand...
Click to collapse
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
bmwdroid said:
Sorry to read that.
Tried very long pressing power button (2 minutes or so) or other button combo like Vol up + down together plus power?
I don't own that device so can't test for you.
Click to expand...
Click to collapse
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Bafif said:
I GOT IT . What I did was wait for the battery to run out totally and then keep the two volume buttons pressed and connected the cable with the phone off, that opened the download mode. I just had to wait two days for completely draining. Thanks for paying attention to me
Click to expand...
Click to collapse
Glad to hear that.