Database Users

Can't Enter Stock Recovery

I tried unrooting my phone, but it got stuck in a boot loop.
When I try to enter to recovery mode to factory reset I get an android lying on its back with a red triangle.
I've tried a bunch of combinations of buttons, but the phone just turns off if I hold power + volume up.

In cmd prompt on the PC type: adb reboot recovery. That should work.
Sent from my Nexus 4 using xda premium

nmunro said:
I tried unrooting my phone, but it got stuck in a boot loop.
When I try to enter to recovery mode to factory reset I get an android lying on its back with a red triangle.
I've tried a bunch of combinations of buttons, but the phone just turns off if I hold power + volume up.
Click to expand...
Click to collapse
that is the stock recovery. what you want to do is flash the factory img via the bootloader/fastboot.

You have the buttons right, but you don't really hold the two down. It's a bit tricky but once you figure out the exact way to do it, it's easy.
Press and hold the power button then immediately after press volume up. Then let go. The menu will appear.

gee2012 said:
In cmd prompt on the PC type: adb reboot recovery. That should work.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
It said:
daemon not running, starting it now
daemon started successfully
error:device not found
Still not working...

El Daddy said:
You have the buttons right, but you don't really hold the two down. It's a bit tricky but once you figure out the exact way to do it, it's easy.
Press and hold the power button then immediately after press volume up. Then let go. The menu will appear.
Click to expand...
Click to collapse
<3

nmunro said:
It said:
daemon not running, starting it now
daemon started successfully
error:device not found
Still not working...
Click to expand...
Click to collapse
Reinstall the usb drivers and turn on usb debugging in settings/developer options.

gee2012 said:
Reinstall the usb drivers and turn on usb debugging in settings/developer options.
Click to expand...
Click to collapse
I have USB debugging on, re-installed the device driver and under device manager it shows Samsung Android ADB device.
Still says device not found.

nmunro said:
I have USB debugging on, re-installed the device driver and under device manager it shows Samsung Android ADB device.
Still says device not found.
Click to expand...
Click to collapse
Your device should be called Nexus 4 and not Samsung. Install the drivers from here http://forum.xda-developers.com/showthread.php?t=1996051, after that connect the phone through usb, look in device manager and delete the device. Reconnect again and choose manualy wich drivers to install and choose the driver you just installed. Now your device is called Nexus 4.

your stock recovery over wrote your custom recovery and that made the little android with the triangle come up. all you have to do is reflash a custom recovery using fastboot.
go to zedomax channel at www.nexus4root.com and he gives you video instructions using the cmd on your computer

Try this:
Go into bootloader and recovery
You will see the android with the red triangle
hold power and press volume up (tricky part)
wipe cache
If this doesnt work try doing a factory reset instead

Screen black (broken) - How to recovery data (no usb-debug)

Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!

Maybe try a mouse with OTG. Would be horribly difficult i guess. But can probably work.
Also with any recovery, it would require your pin to enter the recovery (for decrypting the partitions); so that's a no go.
All you can try is to just boot the phone normally and try any input with an external mouse with OTG. Bring it to a point where the phone is powered on and unlocked so that you can copy data off the flash storage in MTP mode.
Ps: why don't you try to normally boot the phone and use fingerprint unlock?

did you trying with this link?

bluuquthug said:
did you trying with this link?
Click to expand...
Click to collapse
Using this tutorial in this case would make no sense, since the damage is physical and this way you're going to lose all the data currently stored on the phone.

willjeffery said:
Hi all,
I have a particularly tricky case here. A OnePlus 3T with a broken screen (its black, can't tell if its registering taps) which I need to recovery data (photos) from. Normally I'd just use ADB but of course usb-debugging isn't enabled. I've tried rebooting into recovery... hold the power button and vol-down until the phone vibrates, keep holding for a few seconds. Then wait. Then vol down twice and power again to hopefully select English but the when I try
Code:
adb devices
nothing comes up on the list.
I'm wondering if anyone has any ideas how I can recover data/photos from this device.
One again the facts are:
-OnePlus 3T
-screen is broken, black, doesn't display anything
-usb-debugging is NOT enabled
-i can see the device in fastboot mode (boot w/ vol-up+power)
Thanks!
Click to expand...
Click to collapse
if you have no usb-debugging and cannot see screen you are out of luck. same thing happen to me. the only thing that worked was I had twrp recovery and was able to boot into it. Recovery by default is in mtp so you will be able to see all your folders and transfer pics or backup files. last resort was to send it to oneplus repair which will cost about 100 bucks and you will get your phone back within 7 days remember to tell them to not reset phone because they will if you dont. good luck

You can also recover the data very easy through data recovery softwares. No usb-debugging and cannot see screen you are out of luck. I also have to face same problem the only thing that worked was I had twrp recovery and was able to boot into it.

You can try to flash TWRP in fastboot, then reboot recovery via fastboot command. MTP would work unless a pin is required in TWRP.

I can feel the situation,the phone doesn't work properly.

Instantly reboots after booting into recovery

I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help

Patala1 said:
I installed LineageOS 14.1 but I was having some blue screens so I decided to go back to stock ROM but I had a brainfart and rebooted after wiping everything except microSD, and now I can't boot my phone normaly, nor enter recovery mode or download mode.
What is happening with TWRP recovery mode is that it seems to load properly but then it doesn't give me options or anything it just starts formatting cache or something for like 2 seconds and then just tries to reboot normally, but there's no OS so it just gives me a blue screen(im not at home right now but im panicking, i will upload a video for better understanding in a couple hours).
And with download mode it just stays on the charging screen.
Did I just brick my ****ing phone? Im on the verge of tears, I have been watching videos and reading for the past 2 hours and nothing seems to help
Click to expand...
Click to collapse
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.

mayankjet said:
To boot into download mode, you must first turn it off then connect your phone to pc and then long press power up button.
As with the twrp formatting cache or something like that, you must have downloaded a buggy version. For now, if you have a pc nearby try to boot into twrp with adb.
Click to expand...
Click to collapse
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help

Patala1 said:
Download mode still isn't working with the computer im trying, are you saying I just have to turn it off, plug it into the pc(charging screen appears), and just hold power button alone until I get to DL mode? Does my computer need a specific driver already installed for this?
And how would I go about giving my phone commands with adb if I can't boot it into anything? Should my pc recognize the device and be able to use adb when it's in the blue "Subsystem Crash" screen, or maybe when in the first 2 screens before booting into recovery where you have to press "Yes" twice, or when? Maybe when it's charging?
Thanks a lot for the help
Click to expand...
Click to collapse
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.

mayankjet said:
Yes, you need to turn off your phone and plug the usb cable in your phone while holding volume up button until it goes into download mode( you must connect it to a pc or laptop). Also, you don't need specific drivers for that.
To boot into twrp with adb, you must first boot into os, or boot into twrp with hardware keys, assuming you can't do any of these then your only option is flashing a new kdz via download mode.
Edit: You need adb drivers installed on your pc if you're going to use adb commands on your pc.
Click to expand...
Click to collapse
Fixed it, thank you a lot my friend, saved my ass

Patala1 said:
Fixed it, thank you a lot my friend, saved my ass
Click to expand...
Click to collapse
:good:

OK I have added the fix in guide

Is it possible to boot this phone with a broken power button?

Hello all, I have a Moto G5 Plus and I am currently exploring as many ways as possible to get this thing to boot with a broken power button. The phone has USB debugging enabled because I thought that was all I would need if it ever did completely drain its battery. It did die this weekend and I'm finding it more difficult than anticipated to boot this thing. Options I've tried:
1. Pushing extremely hard on the power button. For awhile this worked, seems to be completely hosed now though.
2. Booting into Fast Boot, which is great, except to actually boot the phone it requires a button press of the power button.
3. Android Debug Bridge, which does not seem to recognize my phone. I was hoping the adb reboot command would work in this case, but so far no luck. Could be a drivers issue.
Is there any tool available that is specific to the Moto G5 plus that can boot this phone? I would think any tool that can flash it should also have the power to boot it, but I'm not sure where to start. Any ideas would be appreciated, thank you!
*** This was solved, I posted an update as the first reply. ***

Just wanted to give an update for anyone who finds this in the future. I believe that USB debugging is required to be on, I installed Android Debug Bridge like normal as well as the basic motorola drivers. Boot your phone into fast boot by holding down the volume button and then plugging in your phone in the PC. From here open a command prompt from within the adb folder "left shift + right click > open command prompt". Issue the command "fastboot reboot" and your phone will reboot and boot up.

greengreenwine said:
Just wanted to give an update for anyone who finds this in the future. I believe that USB debugging is required to be on, I installed Android Debug Bridge like normal as well as the basic motorola drivers. Boot your phone into fast boot by holding down the volume button and then plugging in your phone in the PC. From here open a command prompt from within the adb folder "left shift + right click > open command prompt". Issue the command "fastboot reboot" and your phone will reboot and boot up.
Click to expand...
Click to collapse
If your phone is booted you can use something like this to reboot, boot into TWRP or fastboot without the need of the powerbutton:
https://play.google.com/store/apps/details?id=phongit.quickreboot
It's a standard app on my device.
Sent from my Moto G5 Plus using XDA Labs

It is cool, that you have fixed it.. but you should clbsider on sending it to be fixed, if your device freezes and you don't have ylur computer with you, you'll end with a dead phone for the day...

I think I bricked my P10 Lite. Need help please

I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!

Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?

Alaunus said:
I was messing with my P10 Lite and I accidentally wiped the Vendor partition (not sure if I wiped anything else) with TWRP. After the phone rebooted it said something about a critical error during boot and went into erecovery. It gave me two options( I don't remember the second one) and I chose factory reset. It started doing it's thing but I guess something went wrong because it wasn't able to boot and it started to bootloop.
I managed to get into fastboot once. The bootloader and FRP should be unlocked but I am not sure as I think I semi accidentally used the command to relock the bootloader in the hopes of it doing the automatic low level factory reset. After that restart, the phone wanted to boot up but after the Huawei logo it went into the EMUI logo which I've shown in the pictures. Now I can't use any button combination and can't enter any menu. I also can't shut down the phone as it bootloops into the EMUI logo after I press the power button. I opened the phone and turned it off by detaching the battery cable but after holding the power down key and plugging the usb cable into the phone it still boots into the EMUI logo right after the Huawei logo.
I guess not being able to enter fastboot is the major issue and after hours of googling I am yet to find a solution.
Edit: I am a newb!
Please help!
Click to expand...
Click to collapse
Dload method. Put sd card in other phone or some card readers and put appropriate files.

nemanjsb said:
Dload method. Put sd card in other phone or some card readers and put appropriate files.
Click to expand...
Click to collapse
I've already tried that. I've placed the appropriate files into my SDcard but I can't use any button commands including volume up+down+power. When I press them my device just boots into the EMUI logo and nothing happens.
Edit: It boots into the EMUI logo even if I only press the power button. Pressing volume down + usb also boots me into the EMUI logo

DaarkZek said:
Why did you delete the vendor partition, you could try plugging the phone into your computer and checking if you can do anything with fastboot while it's showing emui logo?
Click to expand...
Click to collapse
I measured once and not trice before cutting... I was also not paying enough attention/in a hurry...

Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".

Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
Ok, it seems like not all is lost about my phone. I managed to get into fastboot. In my situation, pressing volume down + usb cable while the battery was plugged into the phone did not work. That was before I opened up my phone's case and disconnected the battery cable.
As I mentioned before, I had opened my phone and disconnected the battery cable because that was the only way to shut it off.
What I did after I disconnected the battery cable was the following:
1 - Hold volume down and don't release it
2 - Plug in USB
3 - Plug in the battery cable into the phone's mobo.
That booted me into fastboot. Right now, the phone says my bootloader in unlocked and my FRP is locked. What would be the best way to flash the new stock OS on my phone?

Aalesund said:
Power OFF the phone.
Press and Hold VOL Down and connect the phone to PC via USB cable. The phone should boot into Bootloader (fastboot mode). Does this method work?
or try this:
Press and Hold VOL Up and connect the phone to PC via USB cable. The phone should boot into eRecovey mode and then then select "Download latest stock rom and install".
Click to expand...
Click to collapse
I have downloaded THIS and THIS for the new OS but by talking with Alexxxx1 in THIS discussion I learnt that Huawei has implemented a security patch in their latest update, which I've most likely installed, that prevents you from rolling back your OS version. That means I need to install the .386 version, which should be the last if I am not wrong, instead of the .378 correct? Though I heavily dislike patches like this I guess I can't do anything about that...