SOS ASAP stuck on bootloop... Solved! - Xiaomi Redmi 3s Questions & Answers

Help me!
I run AOSP 7.3 and TWRP 3.4.0.0 (or 3.3.0.0, i don't remember)
I flashed orangefox 11 following this: https://techrrival.com/flash-recovery-adb-fastboot/
after last step: (Reboot the Device Type the following command to reboot your device “fastboot reboot”), phone stuck loading AOSP.
I then managed to re flash TWRP 3.4.0.0 trying to solve the problem but still stuck loading AOSP...
The problem is that when i run ADB commands it responds: error: no device\emulators found,
I managed to solve it the first time by killing adb and exiting usb device, then running again, but now this doesnt work anymore.
Please Help as this is my main and only phone...
By pressing and holding both volume buttons and power button for 15 seconds, After vibration signal released the power button, while keep holding both volume buttons I’ve successfully booted into TWRP recovery.
By choosing reboot to system it still stuck loading AOSP.
What should i do now?
I wiped cache and everything went back to normal.

Related

[Q] Problem when attempting to flash TWRP

Hello,
I rooted my phone with no issues. Then when preparing to get TWRP on my phone I was setting up ADB via this tutorial
http://www.youtube.com/watch?v=XslKnEE4Qo8
and got the phone to be recognized as device in the cmd window, but when doing the adb reboot bootloader step, the phone just reboots to vzw logo and then the home screen. After being stuck at that step I tried this method http://androidfannetwork.com/2013/09/18/twrp-recovery-available-for-lg-g2-att-and-verizon/ using flashify but after flashing and hitting the reboot button my phone wouldn't turn on and thought I bricked it until I waited a few and then had to hold the power button down for 15 seconds and it turned on. But now I can't get to the white screen reset menu (Stock recovery menu?) using the power+vol down method. Is my stock recovery borked? Any tips on how to get twrp on my phone, hoping it installs over the broken stock recovery. Thanks in advance for reading this.

a6000 shut down during MIUI flash, won't boot into recovery

Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.

Not booting into TWRP

Hey everyone,
I decided to root my lg g6 and got a fickle. After unlocking the device and flashing TWRP I tried to boot into it (''adb reboot recovery'' command) and it deleted all data and then twrp shows on screen for a split second and almost instantly boots normally into android so I set it up while still being unable to access twrp and any of it's functions. Does anyone have any idea what could be the problem?
P.S. Of it helps: before that i had a problem that every time I tried to use the ''adb reboot recovery'' command the console said ''no devices/emulators found''. After a couple tries I wanted to check whether the phone was connected just to make sure (''adb devices'') and after that it worked and I ran into the problem above.
Thanks for all the answers
When you first unlock BL and flash recovery you have to manually enter recovery mode.
Hold power and vol down till it turns off. Hold same buttons again until you see lg logo. Release power and press and hold again.
Then ask you to wipe etc hit yes both times and it will boot to twrp.
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Ulrih said:
I tried that but it still doesn't go into twrp. After confirming that wipe stuff it just boots into android (without wiping)
Click to expand...
Click to collapse
You have to flash TWRP recovery and when it complete then use the button combo to boot into twrp, otherwise it will boot and restore the recovery.
flash twrp
button combo to twrp
done
Yes I've done that but the problem still exist.
btw thanks for the help
Maybe try fastboot flash recovery recovery.img
Try the all-in-one tool on this forum
By the way, I am running into the same issue.. I have a LG G6 US997,.. I have tried installing TWRP unofficial ones so many times and every time i manually try to access the recovery.. the phone simply wipes all my data to default
Hello,
I have the same problem. Did anyone figure out how to solve it? I'd highly appreciate any help.
If I try to boot into recovery, it asks me to factory reset, i hit yes twice and then the phone just goes on to boot normally. The data is not wiped but I can't get into TWRP.
If I enter "fastboot reboot recovery" after flashing TWRP it returns "fastboot: usage: unknown reboot target recovery"

Stuck at "Google" screen after TWRP wipe

Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
goister said:
Hi,
I did a TWRP wipe (everything checked) to prepare for a restore to stock, but my device is now stuck at the very first "Google" screen with the pad lock icon at the bottom. How do I get it to boot?
Click to expand...
Click to collapse
So since everything was checked, that means you wiped the system partition. The device will not boot if you do that unless you flash a factory image via fastboot or new ROM via TWRP
OK, I thought wiping /system would just bring it back to factory state. 2 questions now
1. How do I get to recovery when it's always stuck at the Google screen with no adb access? Would I have to wait for the battery to run out (hence turn off), charge it for a while, then use the buttons to boot to recovery, or is there a faster way?
2. I am actually trying to revert to stock ROM (downloaded at https://developers.google.com/android/images#angler) by following step 10 of the Heisenburg guide (https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928) which advises me to use fastboot to flash the individual images. In my case, how do I boot to fastboot?
OK, so I managed to boot to the bootloader and run the following commands as per the Heisenberg guide (using the stock MTC20L firmware)
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash cache C:\angler\images\cache.img
(above command is unnecessary on Android 7.1.2 and above)
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Everything was successful, and I did a fastboot reboot after that.
However, my device still doesn't boot up. This time. It's boot loops for a few times before turning off.
I tried booting up to bootloader with power/vol-. Curiously, I can now only do this when cable is connected. If cable is disconnected, the orange LED just blinks once when power button is pressed, and nothing happens. Once cable is connected, then I'm able to boot up to bootloader with the button combination. I then retried the flash process again, but still no go. I noticed after fastboot reboot that the orange LED blinked a few times before rebooting and boot looping.
Kinda stuck now, any ideas?
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Face_Plant said:
Try booting into recovery and doing a factory reset. I've had that happen to me a few times after flashing factory images and a wipe in recovery always fixed it.
Just for future information: if at any time the device is stuck in a bootloop you can get it to robot into recovery by holding the power and volume down buttons for 10 seconds, or get it to boot into bootloader by holding power and volume up buttons for 10 seconds.
Click to expand...
Click to collapse
Thanks. Booting into stock recovery shows an exclamation sign with "no command", since I don't have TWRP anymore. Would I need to first flash TWRP before I can do a factory reset?
I just tried flashing to the same sock firmware as before the problem happened (7.1.2 N2G47W) but still same problem. I notice that after the Google logo disappears and the screen goes blank, the orange LED blinks 10 times before rebooting.
Edit: Tried factory resetting in stock recovery (by holding down power button and pressing vol+), the rebooting after factory reset. Still getting a boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
goister said:
OK I solved the problem. Apparently if you reboot after the flash, you need to disconnect the USB cable, else it will boot loop.
Click to expand...
Click to collapse
brother help me! i am facing same issue
first little info abt my device.
my device was running on android nougat with twrp recovery installed but the device was not rooted.
so get back to stock and install oreo I followed every step given on http://www.androidexplained.com/nexus-6p-revert-stock/ but somehow my phone is stuck at bootloop with no recovery installed.
Please help me here.
As per the Heisenberg guide, if you don't install root (SuperSU or Magisk), TWRP won't stick, so you'll go back to stock recovery.
For me, simply unplugging the USB cable after rebooting after a flash solved my problem. For some reason, if the cable is connected during reboot, it would boot loop.
brother, somehow I managed to install twrp. but everytime I touch it 2-3 times the phone gets switched off.
then it keeps rebooting to 'Google' logo.
can you tell me what should I do now?
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
tommast said:
@goister Hi how you manage to get to recovery when it's always stuck at the Google screen with no adb access. Please I am stuck there
Click to expand...
Click to collapse
hi, did youmanage to solve this problem? I am aving the exct same problem. Disconnecting the ucb isnt working for me

Can't reach recovery mode

Hello,
i found my old zuk z1 and updated everything. TWRP to 3.2.1 and lineageos to last nightly. This was working. Then i tried a opengapps mini package for ARM. Since this, my phone can't start any more. With lineageos there was a reboot after 5 minutes to recovery and i tried to delete everything and flashed lineageos with different version, but still reboots after 5 minutes. So i tried an other image AospExtended-v7.2-ham-20200521-1100-UNOFFICIAL and now i have an endless boot screen without reboot and recovery. I can't reach it manually. I tried every Combination with Power Button, Vol up, vol down, both, and with home button. Until Vibration, 10 sek....nothing works, i can't reach recovery mode anymore
how could i recover my zuk1 ?
update, there was an error with vol down, so i can't go recovery with buttons. But you can reach it with adb and
Code:
adb reboot recovery

Categories

Resources