Nexus 4 - broken screen, encrypted, can't enter lock pattern at boot - Nexus 4 Q&A, Help & Troubleshooting

CM13, MultiROM TWRP 3.0.0.0
Touchscreen doesn't react to anything.
I connected mouse via OTG with external power and TWRP can use it, so I can decrypt and mount /data in recovery. But when Android boots and asks for lock pattern, it can't see any otg devices. I tried flashing other kernels, such as Quanta, Revival and HellSpawn, but nothing works. Adding android.hardware.usb.host.xml also doesn't help.
Is there any other option to get phone fully booted?
Thanks.

Related

[Q] [problem] Encrypted device with broken touch screen

Hi, guys,
Please advice.
I have Nexus 4 with TWRP recovery and Cm10.2.
The device is encrypted. Yesterday the phone fell down and now touch screen doesn't work. Everything else works fine, only touch screen fails.
My backup system has stopped working a couple of months ago and I haven't noticed it
So, now I need at least to create a backup of the device and pull it to PC.
How can I do that?
Normal boot: stuck at decryption password screen,
adb devices shows nothing.
TWRP boot: stuck at decryption password screen,
adb devices works (recovery mode). I don't know how to enter password via adb...
CWM boot: stuck at decryption password screen,
adb devices works (recovery mode). doesn't have support of FDE.
Any thoughts?

Stuck in a bootloop after flashing 4.4 via fastboot

So, yeah! I tried to flash the Factory Images of 4.4 to my nexus 10 via fastboot and now its stuck in a bootloop. I tried to flash a custom recovery (twrp-2.6.3.1) and I was able to flash it. But, it says that the device is encrypted and that I need to enter the password in order to mount anything. I can mount my flashdrive, where I keep all my backups, via usb-otg and TWRP is able to recognize it but nothing can be flashed because, again, none of the partitions can be mounted... Can anybody help?

Can't boot to TWRP recovery mode

I installed TWRP through the pc using ADB.
its is installed but when I try to boot to TWRP (by holding the buttons) it shows me a password box. I have no idea which password it is. It is neither the miui account password nor the phone lock password. I didn't find any video about this. Every problem I've seen with other people was in the TWRP but I couldn't even boot to it If anyone faced this issue let me know how to fix it.
backup all your data-photos,music, etc because you will have to format your entire data and internal storage. This will remove the encryption on TWRP. Then flash Orange Fox recovery, it is far more stable compared to other unofficial TWRP ports/versions.
how do I format the internal storage?

[SOLVED] Unable to enter TWRP/Stock recovery and can't boot into system

Hi,
I have been using my P Smart (FIG-LX1) for a while with LineageOS 16 and decided to move on to Android 10. Installed LineageOS 17.1 (found it on this forum) and pph-Magisk 20.3 for root - it did work, but the system was unstable so i decided to try AOSP 10.0 instead. I entered TWRP, wiped cache,dalvik,system and data, flashed the ROM, gapps etc. It was advised to now flash stock recovery and use it to do a factory reset - and now i'm stuck here.
After flashing the recovery_ramdisk img the phone stopped being able to enter any recovery at all. The system itself does not boot (stuck on the "Your device has been unlocked (...) Your device is booting now..." screen forever), the recovery never appears (previously in the start screen with 'unlocked device' warning it used to suggest pressing volume UP to enter recovery, now it only shows "Your device is booting now"). As i can still access fastboot, I tried flashing TWRP again - the TWRP splash screen does appear, but the phone gets stuck on it. Also tried flashing another system's img - nothing changed.
Is there anything I can do or did i just brick it completely?
Thanks for help!
SOLVED:
Apparently running fastboot erase on system and userdata partitions made me able to boot into recovery/erecovery again. I do have another problem now, but it's not connected with this one so I will create another thread for that.
Could you try help me? I can't even get ADB to work anymore

[Help] Bootloop after updating, usb debugging not enabled.

Using the miflash tool I flashed stock firmware (some version of android 8) after previously having a custom ROM installed. Everything worked fine until I rebooted after updating to the latest version using OTA.
My phone never got past the android one screen where it would freeze part way through, and after removing my sim card I could get to the pin unlock screen before the lock screen but after inputting the correct pin it would reboot and ask me for it again and again. I can get into fastboot fine but since usb debugging wasn't enabled and my bootloader is locked I can't reflash.
Booting into recovery also only brings me to a screen where the android mascot has a red triangle with an exclamation mark and a message saying "No command", so I can't factory reset.
Is there anything I can do to unlock the bootloader in this state or factory reset? (all flash tools and fastbooting into TWRP require the bootloader to be unlocked which in turn requires usb debugging to be activated)
Thanks for your time.
Update: I messed around with stuff on the cli based tissot tool and used option 2 to boot me into TWRP. It didn't do that but brought me into android where a system process kept repeatedly closing until a random factory reset happened.
I then got into normal android for a bit before I had to reboot (did remember to unlock the bootloader this time). I can now install twrp fine but every time I install the stock rom using miflash or try to install resurrection remix through twrp I get the same bootloop issue.
For some reason also my internal storage is completely empty no matter what i do so i need to sideload roms via sd card. And sometimes twrp gives me the error "failed to mount /system"
Trying the latest version of LineageOS next.
Update 2: if you have the same issue I had, the only working fix I've found is this restore point for twrp. Have not tried to update yet in case it breaks again but will make a final update with how that goes.
[SOLVED] Mi A1 BOOTLOOP
THIS PROBLEM IS VERY ANNOYING!! (The reason is because i didn't backup EFS before i flash Custom ROM) And I would like to share how to RESOLVE it. **your phone must be Unlocked Bootloader. Search Google how to do it. (Quick tip: in Fastboot...
forum.xda-developers.com

Categories

Resources