Help! Stuck in recovery mode - Samsung Galaxy A71 Questions & Answers

The Android logo with an exclamation mark and the word "Error!". All the buttons unresponsive. Froze in recovery mode when selected the "Sideload" option by mistake and did not send anything via ADB.
The handset is on STOCK firmware, NOT rooted and has LOCKED bootloader. Not modded in any way; just connected via ADB.
Buttons not responsive. Pressing and holding the power button has no effect.
Do I have to wait until battery drains?
Funny thing, I have rooted phones for years, flashed ROMs, sideloaded, even created a ROM. Not an expert, just curious - and never came across such a situation with a completely locked phone.
This is my primary phone and is badly needed...
Thanks for any hints.

Never mind, after 30 mins or so, the phone suddenly rebooted to system after plugged in. Weird, but things seem to be back to normal.

Related

Milestone WILL NOT exit recovery. Even after sbf service flash.

Okay, ive had my milestone for approx 6 months. Havent had any problems and have been keeping up with all the latest mods, etc. I was running 2.2 CM6.1-RC1 and after a few days my touch screen started going out. Recovered to an older Nandroid, and still had touchscreen problems. I rebooted and went into recovery mode, and now, no matter what, even if i reboot the system using the reboot option in any recovery menu, it just restarts the phone and goes back to the orange exclamation mark. I've attempted flashing the GOT2.2 service SBF to the phone and it is still doing the same thing.
Any ideas?
Are you using Open Recovery? Are you saying that you can't reach the default recovery menu at all after pressing camera + up?
I figured it out. The camera button thinks its being held down. If i hit it on something hard, set the phone down and turn it on, it boots up fine.
Only now is that the touch screen is act sporadic, i can hardly even unlock the phone, sometimes it takes 10 tries just to get it to unlock. (was doing this before the recovery issues)

[Q] Question about recovery.

Hey guys, I certainly am not a rooting noob and will never be , but I rooted and flashed a friends captivate for him and ran into a problem.
I am not sure what exactly happened while it was in his possession, but he said he insterted a t-mo SIM and the device shutdown and would not go past the ATT screen.
I took the phone and messed around with it while reading the cappy forums and nothing worked. I could not get into recovery, but I could get into download mode. I then plugged it in again and found that adb was connected and so I then ran,
"adb reboot-bootloader"
suddenly the phone shut off and rebooted right into the normal load-up phase. Like WTF happened? I really do not want this to happen to him again, because he paid me like a hundred bucks for the phone and I would like it to work RIGHT.
Any help would be appreciated. Thanks
adb reboot recovery
captivate doenst have bootloader menu
or
Instructions for recovery mode:
have phone shut off
hold both volume buttons
press and hold power button
KEEP ALL 3 BUTTONS HELD for 3-5 seconds after screen comes on
after kernel bootscreen you will see clockwork recovery menu
if you already had the i9000 gingerbread bootloaders installed and skipped the steps in these instructions, the button combo would be different.
hold volume up then hold power
Yeah firstly, any button combination I tried did not work.
Also i understand there is no bootloader menu, but for some reason it pushed me out of that ATT screen and rebooted the phone and I had no clue what had happened.
Also, I am positive I ran "adb reboot-bootloader"

[SOLVED]Can't boot to bootloader

I finally found solution! Bootloader on my phone isn't nearly same as usual one, no white screen, just a few lines which designate modes. 4 are present:
-normal boot
-fastboot
-recovery
-UART boot
I accessed it by pressing and holding power button and volume up button at the same time during device boot.
I hope someone with a same problem will find this helpful!
I managed to boot to system but I still can't get in bootloader. No combos and neither adb works.
I got my HTC One from second hand several days ago and I instantly noticed that something wasn't right. System was naked, no bloatware, no usual settings, no proper identification so I decided to install custom rom. I tried to boot to bootloader which I wanted to unlock(I guessed it's locked 'cause recovery is stock) with key combos, adb but it simply didn't boot to bootloader nor it rebooted or sometimes it went to factory mode which is on chinese. Again, I tried to find which version of phone I own but I can't figure it out. Moreover, I downloaded and put stock rom on virtual sd card and booted to recovery, opened menu with power button and selected to install package from zip just like it's said in thread but it outputted 'Install /sdcard...' and nothing else for past couple hours. Recovery isn't frozen, It shows\hides menu when power button is pressed. I tried to force shut down it by holding only\in combination with power button\volume buttons but nothing happens. I don't know what else to do...
Any help would be appreciated.
EDIT: It eventually discharged but when I turn it on with charger in it I get blinking white screen on every 3 seconds and when long pressing power button phone just vibrates. In combination with volume down it keeps blinking on every 3 secs and with volume up on every 5 seconds. To me, it looks like it's trying to boot but bootloader can't find anything installed. Computer is recognizing usb device on the moments when I connect it with usb just like when device is rebooting.
Jon2555 said:
I got my HTC One from second hand several days ago and I instantly noticed that something wasn't right. System was naked, no bloatware, no usual settings, no proper identification so I decided to install custom rom. I tried to boot to bootloader which I wanted to unlock(I guessed it's locked 'cause recovery is stock) with key combos, adb but it simply didn't boot to bootloader nor it rebooted or sometimes it went to factory mode which is on chinese. Again, I tried to find which version of phone I own but I can't figure it out. Moreover, I downloaded and put stock rom on virtual sd card and booted to recovery, opened menu with power button and selected to install package from zip just like it's said in thread but it outputted 'Install /sdcard...' and nothing else for past couple hours. Recovery isn't frozen, It shows\hides menu when power button is pressed. I tried to force shut down it by holding only\in combination with power button\volume buttons but nothing happens. I don't know what else to do...
Any help would be appreciated.
Click to expand...
Click to collapse
You have a fake phone
I agree, you've probably got a counterfeit One, but you can't flash custom roms from stock recovery anyway.
Firstly, thank you for any answer. How do you mean 'fake'?! I got it in original box and IMEI's are same(on box and device) What can I do with it then?
I tried to flash stock rom designed for stock recovery, at least that's how I understood.
MIDN07100 (Europe, a guy from which I got device claimed that it's from England so this should fit)
IMEI:354436053103493(same on device and on box, checked with IMEI checker it appears as valid HTC One device)

[Q] Bricked Xperia c6603 that can't shut down

So the thing is, I decided to buy this phone from another person a few days ago while it was still working but it had this one problem where the owner told me about how the phone can't be shutdown unless the battery runs out of power. Any time you shut it down, it simply reboots instead. I thought it was most likely a problem I could fix after flashing, so I decided to buy it.
Using Flashtool I was able to see that if timed pressing the buttons and plugging it into my computer right before the reboot started, I could boot into flashmode. This phone came in the 4.4 KK firmware and the 10.5.1.A.0.292 Generic NCB build, so I flashed an older kernel and rooted it using Towelroot before reflashing the 10.5.1.A.0.292 Generic NCB kernal. After rooting (and testing if root apps can shut it down which didn't work either), with a locked bootloader I installed the XZDualRecovery using the method here because I was finding it so hard to unlock the bootloader and Flashtool wouldn't do it either. It automatically booted into TWRP recovery menu but when I tried to flash a ROM (existenz Ultimate 3.5 to be precise), it simply made the screen go black for a second and took me back to the recovery menu. So figuring it was a bad download, I downloaded a smaller ROM but when I rebooted I accidentally went into PhilZ Touch menu instead. Deciding to do the usual wipe before flashing, here's where I messed up like an idiot. I saw an option along the lines of "Wipe CLEAN for flashing ROM" or something and trusted it so much despite it saying it's gonna wipe the system partition clean as well (I still don't know why I accepted even when warned of that).
So basically now I have a system that boots the SONY splashscreen and then goes black with the back light still on unless the battery runs out. I can't shut it down no matter how long I hold the power button and if I restart, it boots back to the same thing. I have no recovery menu now thanks to my genius idea of wiping the system, and the only thing I can enter is flashmode. So when I try to flash an FTF firmware (I tried every firmware I could get) back into the phone with Flashtool, it would simply say "preparing for flashing" for about a minute before it says "device disconnected" because the phone decides to exit flash mode and boot normally. I have a locked bootloader (with bootloader unlocking allowed), so I can't flash recovery menus. When I try booting by holding the VolumeUp key and plugging it in, it enters flash mode only with the red LED on and I still get the same results on Flashtool.
Was wondering if there were any ways around this that I might have missed before deciding to open the phone and change the hardware? And if it comes to that, what would I need to change (have always been a software guy when it comes to phones)? Any tips and advice would be appreciated.
TLDR: Have a bricked c6603 from wiping the system, that can't shutdown and keeps rebooting and refuses to be flashed.
If you have time before the phone reboots, hold Volume UP and the power key for 15 seconds. The phone will vibrate once at 10 seconds. Keep holding the keys until you feel 3 vibrations. This will hard power down the phone.
Sent from my C6603
^I've tried this and it simply boots back up again.
Hmm. That should definitely shut the device down, not restart it.
Sounds like there could possibly be an issue with your power button. I've heard of issues with the power button after water damage. Have you checked the water ingress indicators under the flaps? If any are red, it points to earlier damage from water.
Sent from my C6603
kingvortex said:
Hmm. That should definitely shut the device down, not restart it.
Sounds like there could possibly be an issue with your power button. I've heard of issues with the power button after water damage. Have you checked the water ingress indicators under the flaps? If any are red, it points to earlier damage from water.
Sent from my C6603
Click to expand...
Click to collapse
Seems like you're right, I just checked it and it indeed has a faded red color on it. Do you think if I take the phone apart it the power button could be fixed or should I swap something else inside this from another Xperia?
7ty6er said:
^I've tried this and it simply boots back up again.
Click to expand...
Click to collapse
I experienced this problem
Pls hold down volume When u connect your phone to pc via flashtool,
It will connect in flash mode
After that , just flash 0.230 kernel via flash mode ( kernel not rom )
Then disconnect your phone
Turn it off ( hold power button and volume up till it vibrates 3 times )
Then before it turn on again , hold down the volume down and connect it to pc via usb and this time flash 0.283 Rom ( not kernel )
This worked for me

Bricked Nexus 6 (Not your typical thread)

So first things first:
I am not a noob, I have been flashing phones for years
The phone has an UNLOCKED bootloader
I know what a bootloader/recovery are etc
So last night I upgraded my phone to 6.0.1. I then decided to root it and get a kernel on for color control. So I download one of the new kernels (Elementalx) for 6.0.1 and the systemless root that he recommended in his post. I flash both files and boot the phone, the phone bootloops twice after the password to boot screen and then it works fine. I install a few things adjust a few things (nothing pertaining to root) and then before I jump into the shower I reboot it. I look at it after a few minutes and it is sitting at the google screen with the padlock, no worries it has happened before so I reboot it only to be met with this same screen. Over and over it just halts here. I do the button trick to get into the bootloader, no dice. No button combination can get me past this screen.
I then go over to my PC and try it out and see if I am getting a Q_BULK issue (I had it happen to my Galaxy Nexus before) and the PC doesn't even acknowledge it, so now I am getting a little worried. I cannot power off the device normally, it just reboots back to here. I can manage a trick with the power cable and some quick button presses to enter the "charging" mode and from there it appears to shut down. Upon boot though it comes right back to this halt. :-/
So, does anyone have ANY experience with this before I contact Motorola? I really don't want to because I have frame swapped and don't look kindly on the process of undoing it for a replacement, but if it must be then it must be. Below is a TLR
Phone boots to Google/padlock screen
CANNOT access the bootloader/recovery through normal means
PC does not recognize it (I did prior in both fastboot and recovery so the drivers are all installed)
the phone does NOT appear to be in Q_BULK
the phone will not shut down, it just boots back to here
It "was" running ElementalX and the systemless root (both are the newest) for 6.0.1
-Current status, sitting on this screen waiting to die... but it has an almost full charge
OK, first off... YOU ARE A NEWBIE.
Turn off the phone and boot to bootloader and use that to load your custom recovery and restore your working backup.
Failing that, fastboot flash the stock image from bootloader mode.
What are you hoping to accomplish by draining your battery completely, this can only make matters worse.
@scryan you are a funny man?
you didnt say anything about trying to get into recovery.. i assume you tried getting unto your recovery?
Hold power button, up and down button all at the same time. If you are on stock recovery wipe user data and cache. See if you can boot into the bootloader afterwards. That's unusual you cannot get into stock or custom (if you have it) recovery.
So you're main problem here is that you can't get into your bootloader or recovery right now? Hmm..... that can't be good. My best guess would be to keep trying to get it into your bootloader, just keep on holding volume down and power for a long time, hopefully if you can get into either bootloader or recovery you can fastboot flash a clean stock image, or restore a nandroid backup (assuming you have one) with TWRP. My best guess though.
Briefly, your device powers on, so there's sign of life. It is either your cable, pc' usb port or the usb socket of the phone is at fault. Did you try with another usb cable at another usb port in the pc ?
Let the phone power down completely. And when it dies, connect it to a charger while briefly holding the vol down button to get into the bootloader. It might take a while since the phone doesn't have any juice but this trick might just work.
If already no warranty, so dissasembly the deive, re-attack your battery

Categories

Resources