Question [Help] Phone stuck in boot menu after trying adreno driver - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

stuck in bootloop after applying Konabees driver config. Now I'm stuck in boot menu with nothing.
adb commands comes with whenever I'm trying something fastboot mode.
"error: no devices/emulators found"
Project Elixir recovery mode is available in slot b but can's seems to do anything. any help regarding how to fix the loop and install twrp and rom would be appreciated.

Get TWRP or OrangeFox from their official site
Get SDK Platform Tools from official Google Dev site
Install Android USB driver from Mi Flash or from Windows Update "Optional drivers"
"fastboot boot twrp.img"
Reflash ROM without Data-Format. If it doesn't boot, you have to format data.
BTW, is the Adreno driver a Magisk Module? Magisk Modules can be removed by deleting its folder in /data/adb/modules/*

Thanks for the quick reply. It worked, needed to format data sadly.

Related

[Q] Boot Loop and not entering recovery!

I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!
Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!
Am on windows and i had fastboot_adb(1.0.32) already installed.
Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.

F400S + CM13 - Can't boot recovery [TWRP] + Fastboot not working - Win10 x64

Morning All
I've been running CM13 for a while now on my F400S but was having issue with TWRP not backing up all my data. I figured that this may have been because I recently encrypted my device and I was using TWRP 2.8.70 and not 3.0.0.0.
I installed TWRP Manager and allowed it root access, told it to install 3.0.0.0 which then resulted in me getting the "Secure Booting Error! Cause: Boot certification verify" message when the device restarted.
My device still boots into CM13 and is useable, I just can't get into TWRP. I've looked at the LG Flash tool both the old and the 2014 versions, but I'd prefer not to wipe the device and rebuild it from scratch if possible. I could if needed and my most recent backup is the 20th March.
I wondered if I could use ADB and Fastboot to flash TWRP 3.0.0.0 to the device and hopefully rectify the issue. However I can't seem to get Fastboot to speak to the device.
ADB gives me:-
C:\adb>adb devices
List of devices attached
LGF400S5af0af79 device
However, Fastboot gives me:-
C:\adb>fastboot oem get_identifier_token
< waiting for device >
....and never retreives any information.
I've tried the following drivers [I'm using Windows 10 x64]:-
LGUnitedMobileDriver_S50MAN310AP22_ML_WHQL_Ver_3.10.1
LGUnitedMobileDriver_S51MAN312AP22_ML_WHQL_Ver_3.12.3
LG-Mobile-Driver_v3.14.1
LGMobileDriver_WHQL_Ver_4.0.4
and also the driver that the LG Mobile Support Tool downloads which I believe is 3.08.
I forcefully selected the driver to use via Device Manager, rebooted but Fastboot still doesn't seem to connect to the device.
I'm not sure if I'm going about this the right way, or if anyone can suggest any alternative driver or method of resolving the issue with TWRP please?
Bump.
Bump.

Won't boot need help I don't know what to do

EDIT:
I finally did manage to install TWRP, and then flash lineage and then addonsu.
But I forgot opengapps.
Can I install gapp later ?
I can't link my phone to the computer anymore. is there something special to do in lineageos ?
OLD POST (completely irrelevant now)
Hello,
I'm stuck at boot. The phone stays with a black screen showing "Cyanogen mod ready" forever.
I don't know what to do from here.
All I can do is boot into fastboot (volume up + power) but I don't see what I can do there.
Thanks if you can help me out.
How I got there: I had a functionning cyanogenOs 6.0.1 and decided to install lineageOs.
I figured I had to 1) unlock the bootloader 2) install twrp 3) install lineage 4) install gapps
I installed adb and fastboot on linux computer.
did "adb reboot bootloader"
then from fastboot I did "fastboot devices" and then "fastboot oem unlock". then clicked "Yes" and "reboot android"
correct drivers installed? there should be a notif in status bar usb charging,transfer files etc.

Unable to flash TWRP via fastboot

Hello, I have a huuuuge problem.
Every time I try to flash TWRP through cmd, nothing happenes. I have all needed files, my phone is being recognized in adb devices, reboots on command, is on fastboot devices list, reboots on fastboot reboot command, but it totally do nothing when I use fastboot flash recovery twrp.img command. Maybe it's my drivers fault, because last time i uninstalled my device through Device Manager, somehow it worked and I flashed TWRP. But then I switched to MIUI and as expected TWRP was removed. And I cannot flash it, please help
Did you update to latest MIUI?
Yes, right now I'm on Global Stable.
Turn your pc into a new one then you will.
Why turn your PC into a new one? resetting?
IsnĀ“t there another solution?
Removes old data such as adb,platformtool, twrp.then can do it.I've come across and solved this way Do not know why
xx
Posted another tread:
I struggled a lot installing TWRP. I did not succeed flashing TWRP from my PC. My solution was:
Starting up TWRP: fastboot boot twrp.img / boot command only boot and does not flash.
Thereafter installed Magisk 17.1 from TWRP for rooting
Thereafter flashed TWRP / I tested flashing both by using Flashify and TWTP Manager and both worked.
Maybe by using Flashify I had to use an older version of TWRP. Think TWRP Manager let me install 3.2.3-0 direct without problems.

magisk instructions

guys please give me noob friendly instructions for installing magisk latest ver on my lenovo p2 15.1 latest build .
Same
First make sure you have USB debugging enabled on your phone, then install ADB on your PC. Connect the phone to the PC and in the installation folder (ADB > platform-tools) shift right click and choose Open command window here. Type adb devices and authorize your PC on the phone. Download the ROM and extract boot.img from it, transfer it to your phone. On the phone install Magisk Manager and patch the boot.img (Install > Patch boot image). Transfer patched_boot.img back onto the PC (to the ADB > platform-tools folder), then boot your phone into fastboot (VOL down and POWER buttons). Repeat the Open command window here step and type fastboot flash boot patched_boot.img. Reboot your phone (fastboot reboot). You are now rooted on custom ROM.
After installing magisk , do I need to install any module to prevent boot loop like f2fs loop module etc .
Check if you can install modules. If you're facing problems, then you will need to change a few things. The "cannot mount magisk_merge.img" issue for example can be solved by patching and flashing boot image from here https://forum.xda-developers.com/lenovo-p2/development/kernel-f2fs-upstreamed-kernel-twrp-t3845976. I tried tinkering with modules for it and ended up bricking my phone. I would also recommend using TWRP from this thread, it got rid of my second problem (which I now forgot).
Just remember that you will need to flash the patched custom kernel after any ROM update.

Categories

Resources