Stuck on TWRP splash Screen - Xiaomi Mi Pad Questions & Answers

Installed the Remix OS on my MiPad. Everything was working fine until the following happened
1. My OS seems to have crashed . There would be nothing on the screen other than the wallpaper. No icons.
2. Somehow tried to factory reset when I was able to get into setting via the notification menu.
3. Post this, my tablet can't boot to the OS, can't boot into fastboot via physical buttons or adb. I'm just stuck on the TWRP splash screen since then.
Please help.

Related

Please HELP! cannot get into recovey!

Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!

[Q] Nexus 5 MultiROM bricked? phone - Will not load out of bootloader/recovery

When i first installed MultiROM on Cyanogenmod, I would have to go through the bootloader to get anything but a black screen. From there, I could select Start, and then usually it would work. A pain, but it worked.
I just used MultiROM to install Android L preview and when it told me to restart, I got the same black screen I had gotten before. No biggie - I've been here before. When I went through the bootloader, I just went straight back to the black screen. I repeated the process a few times before I gave up.
I can still load into the MultiROM recovery menu, but the phone just wont show up in Android File Transfer or ADB. 
If possible, I'd like to keep the pictures that are on the phone, but if not, it's fine. I can't flash a new ROM because the phone wont show up in ADB.
It seems that there is a factory reset on the MultiROM recovery menu - does this work like a regular factory reset where it would reset to a version of cyanogenmod?
Any advice would be GREATLY appreciated.

Layers messed up the phone on AOSP 5.1.1

So I was experimenting with some customization tools (gravitybox, some other twrp modules) and everything was fine. Then I installed a custom layer I downloaded from the Play Store on Layer Manager and now the phone boots into the stock wallpaper, the screen is flashing, yellow led constantly on, there are no buttons anywhere, I can't do anything, the only command he can do is the screen used to turn the phone off, and even with that I've tried booting into safe mode and it's the same. I wanted to make a factory reset on TWRP but I can't even boot into recovery, it just shows the MI logo and boots normally. I also tried fastboot flashing TWRP again and although it flashes well the normal boot remains. Can someone help me?
EDIT: I managed to boot into TWRP, I was doing it wrong after all. I will reflash the ROM.
SkinCoffin said:
So I was experimenting with some customization tools (gravitybox, some other twrp modules) and everything was fine. Then I installed a custom layer I downloaded from the Play Store on Layer Manager and now the phone boots into the stock wallpaper, the screen is flashing, yellow led constantly on, there are no buttons anywhere, I can't do anything, the only command he can do is the screen used to turn the phone off, and even with that I've tried booting into safe mode and it's the same. I wanted to make a factory reset on TWRP but I can't even boot into recovery, it just shows the MI logo and boots normally. I also tried fastboot flashing TWRP again and although it flashes well the normal boot remains. Can someone help me?
Click to expand...
Click to collapse
If you're able to access twrp somehow, flash the rom again and just wipe cache and dalvik cache. You won't lose any data at all.
Edit - I don't think layers can mess with your recovery. Fastboot flash recovery and try booting into it by pressing volume up and power button. If that doesn't work.. Press power button and both volume up and down and see if it boots into recovery. Once it does, just flash the rom without wiping data.
Boot into TWRP & Mount "System"
Using File Manager navigate to /system/overlays
Delete all files one by one inside overlays folder
Reboot to system

TF201 suddenly bootlooping.

So I got myself a cheap TF201 tablet and decided to put Android 7.1 on it using this guide. I followed the instructions completely and everything went perfectly well.
Had TWRP 3.2.3.0 installed, Android 7.1 installed and it was working great. Rebooted a few times, set up my Google account in Android, started installing a few usual apps such as Chrome, etc. when suddenly the Pad completely locked up. It then rebooted and went straight to the TWRP logo screen, sat there for 10-20 seconds then rebooted. And now that is all it does - ASUS screen comes up for a couple of seconds with "This device is unlocked" in the upper left, then tries to go into recovery but it reboots instead.
I cannot access fastboot mode at all - holding PWR + Vol DN does nothing. I can access APX mode and I can briefly use ADB while the TWRP is up.
I have backups of all blobs and I have nvflash installed - I got through the whole guide step by step without a single problem.
Any help would be hugely appreciated!
I got quite the same issue here, I also flashed 7.1.2 yesterday and installed some stuff. Then today I wanted to install Magisk to root it. After the installation (I can't remember that it was successful but I think it wasn't because there was no Magisk app to find) I wanted to boot another time to the recovery and went into a bootloop. When I'm trying to boot to TWRP it stucks at the teamwin logo. Sadly I have no cable here at the moment to maybe reflash the recovery or try some other stuff.

Ulefone Armor 3T; Custom Recovery + Root

I'm having a bit of trouble with this. I've already been through NMaverick's guide, to very limited success. I was able to flash an older version of my firmware with SP Flash Tool, and get TWRP flashed and booted into recovery, disabled encryption, and installed Magisk. My screen is flickering, so I don't want to leave it like this.
Does anyone have any advice on how best to move to the newest firmware without losing TWRP/root?
Just to add: With my most recent firmware available, the screen doesn't flicker, all the stock functionality appears to work fine, but I can't boot into recovery. When I hold down Volume Up, the phone acts like it's stuck in a boot loop. I get a green line across the top of the screen after the boot logo, and then it tries to boot again. Letting go of Volume Up results in a normal boot to the OS.
Hello everyone, where I can find this version for the 3T or if someone has it in Backup, it is very important for me to find it:
CQ3060MF2_AGS32_Armor_3T_20181107_V01
Thank you

Categories

Resources