Question lost touchscreen - Moto G Power (2021)

so i was able to unlock the bootloader, and flash the magiskpatched.img to the boot partition and successfully rebooted, however, i lost the touchscreen, anybody aware of a fix for this?

update: I flashed the original boot.img to the boot partition, still no touchscreen...

Related

bricked after updating to 5.1 and problems with unencrypted boot.img

Hey guys,
I installed last time the unencrypted boot.img to speed things up and yesterday I tried to flash to factory 5.1, but I believe I flashed all images like system, cache, recovery, vendor, but I may have messed up with boot and bootloader. I think I only flashed bootloader and forgot to flash boot, after reboot the device get in a loop, and I can't unlock the bootloader to push the boot.img
Is there a way to push the boot/bootloader.img without needing to unlock the bootloader?
Mephisto_POA said:
Hey guys,
I installed last time the unencrypted boot.img to speed things up and yesterday I tried to flash to factory 5.1, but I believe I flashed all images like system, cache, recovery, vendor, but I may have messed up with boot and bootloader. I think I only flashed bootloader and forgot to flash boot, after reboot the device get in a loop, and I can't unlock the bootloader to push the boot.img
Is there a way to push the boot/bootloader.img without needing to unlock the bootloader?
Click to expand...
Click to collapse
Not if you relocked your bootloader. Time to start the warranty exchange/repair process.
cam30era said:
Not if you relocked your bootloader. Time to start the warranty exchange/repair process.
Click to expand...
Click to collapse
Looks like I'll need to contact Google RMA Monday ...

issue with bootloader re-locked?

Hello guys, I have a weird issue
Few weeks ago I unlocked the bootloader, installed TWRP, rooted, flashed a kernel, etc. All went fine. Today I tried to flash an updated TWRP via fastboot and it tells me the bootloader is locked! I've seen some people with the same problem, can anybody help!?
Thanks in advance :good:
nobody faced the same issue? In other forum someone had the same problem and had to unlock again the bootloader after flashing back the stock recovery but, what causes the issue of the bootloader re-locked out of nowhere, when TWRP, root... everything is working just fine?
Just unlock it again? also it's way easier to flash recoverys with Flashify
unlocking it again will wipe my data, and also it's not sure it will re-lock itself again. I would like to be able to use fastboot in case I have to flash sth using it

Overwritten boot with twrp!

Hi all, I tried to flash twrp after unlocking bootloader but the site I followed was wrong, ended up with twrp on boot partition! I've since tried to fastboot various system and boot images with no luck, keeps giving file size errors. Booted twrp from fastboot to flash lineage but that ends with error code 7?! Tried to fastboot update stock room too but same problem with file size, the system img is actually broken up into 50 odd files, I presume to avoid the file size problem, however there's no flash all script. Help!!

Stuck in fastboot

I made a mess, I really did. Was on Paranoid Q5 and wanted to try the CrDroid 7, so flashed DFE to decrypt the phone. However this made the phone stuck in fastboot. Don't really know if I misunderstood some instruction, or got hold of wrong file...
But here's the real problem - I cant install TWRP through the fastboot!
The Shell does report "sending, OKAY, writing, OKAY", but it wont reboot to TWRP either through ADB or manually.
Is this a common problem? Any help would be appreciated...
When I experienced something like that in the past, I used fastboot to directly boot to recovery, and then permanently flash twrp from inside this temporarily booted twrp. After flashing, reboot again to recovery and you are now ready to flash a new rom of your choice.
So you flashed dfe then rebooted but phone stuck in fastboot? Which dfe zip did you use?
It appears that DFE wiped all the partitions that's why even the recovery is not being flashed because partitions are not getting detected.
The easiest way to boot your phone is to flash stock ROM using flash tool to recreate the partitions. After that anything else can be done.

fixing wiped asus rog phone 6 pro

due to my inexperience with rooting phones, i have managed to delete everything from my phone.
i mean everything.
the boot.img, recovery.img, system.img ... everything
the phone still boots to the bootloader but wont let me flash most partitions without booting into fastbootd.
fastbootd was part of the recovery image so i cant boot to it.
i can flash the boot partition for some reason and it will boot to it.
the phone bootloader was unlocked so it will boot anything from the boot partition.
due to me not knowing to change a setting in android, i cant flash the other partitions without first restoring the original software.
i cant do this without a recovery.
due to the same setting in android, i also cant boot any image through fastboot except the original stock boot image that is basicly useless to me.
i would think the solution to my problem would be to temporarily flash a recovery image to the boot partition and boot to fastbootd from there, but twrp and the stock image are both too large to fit in the boot partition.
is there some way i can get fastbootd in the boot partition?

Categories

Resources