very strange brick - help! xt1771 - Moto E4 Plus Questions & Answers

photos.app.goo.gl/Goh5m8S8UksAmEdG6
Focus on left inferior corner shows the message "device unlocked", in addition i cant put on fastboot mode.
Some moments before i was on i bootloop in twrp and i also cannot flash another boot image, because the adb in cmd said that wasnt a "image", so i decided to erase boot, bootloader, system to try to get out. However i entered in another bootloop that is mencioned on video.

Related

Messed up. Stuck in fastboot, commands not working.

So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.

XT1064 Stuck in fastboot mode (Recovery option wont open)

Hi guys, I buyed a phone used phone with this problem. The original owner tryed to flash a custom rom and at the middle of the progress the phone shut down because low battery. Then, when they turned on the phone, it only boot in fastboot mode. In fastboot mode, Recovery option wont open, Normal boot wont open too. The bootloader is unlocked. Then, i tryed to flsah a 5.0.2 stock rom but the console show me up an error like "FAILED" or "bootloader FAILED" The phone shows "recovery downgrade" in purple. I tryed 6.0.0 too and Kit Kat for the XT1064 USA version. I cant flash nothing, always the same error. i installed Motorola drivers, ADB, etc. Any help?
Bootloader version is: 48.07. I serarched this number in google and it shows a 5.1.1 custom rom. Propably this rom was the same that he tryed to flash before, i dont know. Unlocked status also is 3.
Edit 1: When a choose "Normal boot" it says: Invalid boot Image Header! Fastboot reason: Fall-Through from recovery boot mode.
When i choose "Recovery" it says: Invalid boot Image Header
boot up failed
When i choose "Factory": The phone just restarts into fastboot again...
Checking Motorola Device Update, the firmware inside this phone is: 21.11.17.titan.retuaws.retuaws.en.us what it means, it have android 5.0.2 Lollipop, right?
Hope you can help me
Thanks.

Stuck at "your device is booting now..." after flashing a rom

When I was trying to root my P10 I was trying to install SuperSU via TWRP but my file names were crypted, and I couldn't find the .zip file.
After some research I found out that it's a common problem, and can be solved by flashing a custom rom (no-verity-opt-encrypt.xxx.zip)... And that is supposed to decrypt the filenames.
After sideloading that file, I can't boot my phone as I get stuck on a screen saying: "your device is booting now..."
I can get to huawei eRecovery by pressing the volume up - I can't do a factory reset, it just says your device is not supported.
I can also get to fastboot & recovery mode screen, and by typing "fastboot devices" in console I can see my device's number so I can acces it.
If I type fastboot flash recovery twrp-3.1.0-0-P10.img it would successfully fiinish but it wont do anything.
Can I somehow fix this?
EDIT: saved the phone with
https://forum.xda-developers.com/p10/help/model-t3713886/post74719465#post74719465

Bricked leeco le2

Hi guys,
I've a leeco le2, it's in some sort of bootloop. I now have a phone which I hope is not actually bricked.
To cut to the chase:
The phone boot loops - it shows the "Leeco" on the black background for less than a second, then reboots, after 2 seconds, it comes back up with the "Leeco" and reboots, and so on.
I can get into fastboot mode. Interestingly, the status shows "Device is LOCKED"
I cant get to recovery mode. It just goes into the boot loop again.
Using the adb tools, I cant issue the "fastboot flashing unlock" or "fastboot oem unlock" commands because it returns: "FAILED (remote: 'oem unlock is not allowed')"
I am unable to get into the phone OS to change the settings because the phone is boot looping
. I am flashed several time in flashone,qfil and Miracle thunder but problem is same.
Given the fact I am unable to get to recovery, I am unable to sideload an OTA zip. And given the fact that I cant boot into the OS, I cant enable oem unlocking.
Do I have any hope at resurrecting this phone in any way? please help me
Check this : https://forum.xda-developers.com/t/...-le-2-s3-noob-friendly.3515555/#post-69996355

Question URGENT! I have seemed to bricked my Note 10 5G to a point where I can not unbrick it. Please help!

So, I installed TWRP on to my Note 10 5G, and I rooted it with magisk successfully. But then magisk could update the app to v24 but it couldn't update the root itself. So I downloaded magisk v24, changed it to magisk.zip (not .apk) and tried to boot into TWRP but (to me) it didn't seem to be booting into it. I tried `adb reboot recovery` and `fastboot reboot recovery` but it didn't seem to work... or maybe it did work but I didn't realise that it had to show that "bootloader unlocked" bootscreen before going into TWRP.
So anyways when I thought it didn't work I tried to reflash it so I did fastboot flash a couple times but I can't remember what partition (I should of just refollowed the tutorial I was watching) but it seemed to erase the whole SDCard and stop it from booting (well it did boot but then it'd shut off and try to boot again). From there I could only get into fastboot. So I downloaded some sort of boot.img and flashed it to boot partition but then I broke it more and now I can't even get into fastboot and it's stuck in this infinite loop where:
It'd show that "bootloader unlocked icon" boot screen, then a glitchy static bar would come across the bottom of the screen for like 4 seconds before shutting off and then going back to that "bootloader unlocked" screen.
I can't detect it with ADB now, or get into fastboot to recover it. I wish I was more patient for TWRP to load.
So, what can I do now?
Spoiler
I swear I have an update curse. The last time I updated something was my PC's bios and accidentally turned it off and corrupted it. I fear that something like that could of happened.
(I got a new Mac since then tho, which is what I'm writing this post on.)
I'll help you tomorrow. Do you have Camellian?. Is your Device based on Mediatek?

Categories

Resources