[SOLVED]XT1072 doesn't boot and doesn't start twrp - Moto G 2014 LTE Q&A, Help & Troubleshooting

I want to clarify that it all happened while the phone was on, I wasn't fiddling with fastboot etc.
everything happened a few months ago: I can't remember if it was switched off or released, if I was using it or if it was on standby; the fact is that immediately afterwards my thea did not want to boot any more (it remained on the motorola logo) and not even in twrp (again it remained on the twrp logo), but fastboot worked. I remember having made a few attempts, and that sometimes the fastboot was blocked and the phone didn't turn off, and that I had to remove the battery.
Now I've got it back, and now:
system doesn't boot, but the fastboot mode works fine and doesn't crash anymore. The twrp instead, remains at the initial screen, but from adb is recognized as recovery, and I can use some commands.
What can I do?
thanks for the answers, always if there will be any

ok, i've resolved with this: https://forum.xda-developers.com/moto-g-lte/general/stock-6-0-marshmallow-europe-reteu-t3338075

Related

Htc one mini 2 stuck in startscreen - fastboot mode available.

About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Montor said:
About two months back, I rooted my htc one mini 2.
Unlocked the bootloader, installed a new recovery (This one) and finally rooted the device. I wanted to install different fonts for it, and in the process relocked the bootloader again.
Now, after several weeks of not doing anything regarding the root, my phone has errors after errors.
First, Google Play stopped working, and along with it, Youtube and the Play Store of course.
About two weeks later, even the "internet" app stopped working.
Today i wanted to start my phone only to find it stuck in the starting screen. (Looks like this)
What I want to do now is get my phone factory resetted, not rooted anymore and WORKING.
What I tried to do is get the phone into fastbood mode (this worked) and connecting it with the "Minimal ADB and Fastboot" console. (This did NOT work)
Rebooting the device from the fastboot menu did not work, it either gets stuck in the loading screen again or directly enters fastboot.
What can I do to make my phone work again?
I hope you can help me :/
Montor
Click to expand...
Click to collapse
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
csoulr666 said:
Try unlocking the bootloader again.Flash the custom recovery and then flash the stock rom available in the development section. It looks like your system partition got corrupted
Click to expand...
Click to collapse
How can i unlock the bootloader again?
The only way i know is via the console and "fastboot oem unlock" - i cant get my phone to connect though.
The available devices the console gives me are an emulator and three times my phone, which is/are offline.
Edit:
Stupid me. "Fastboot oem devices" and it shows my phone in fastboot mode.
Next problem: "fastboot oem unlock" does not work, and flashing the recovery with "fastboot flash myrecovery.img" doesn't work either :/
Edit 2: Managed to unlock the bootloader again (mistook the android folder with de adb folder, no unlocktoken there of course)
Directly after unlocking the bootloader again, the device went into recovery mode, showed the recovery starting logo, and went black.
After turning it back on, it got stuck in the starting screen again - will have to wait for it to run out of battery.
Edit 3: Flashed the recovery, but i can't seem to find a stock rom (only one i did find is this here - and the files are down...)
Solved it!
Just did a factory reset in bootloader menu.
(I hope i didn't forget anything, since I don't know s*** about android development)

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.

Oddest Brick Ever - Kindle Fire (Tate)

History of the issue at hand:
I was running a new rom that was marshmallow based. It was running fine but lost root privileges so I attempted to boot into recovery and install the stable version of SuperSU for the device. I wiped the dalvik and cache and rebooted through TWRP recovery and the system went into a bootloop. Solution: Read XDA forums to find a way to fix the device. Went on ebay and bought a fastboot cable, waited 3 weeks, cable comes in and gets me to fastboot mode, but I am running Windows 10, creating a new problem. Solution: Partition the HDD on my computer and install Windows 7 Professional. This now fixed the driver issue. Plugged in the cable, with the new drivers installed and voila - Fastboot mode.
Seems pretty easy right? Wrong. After trying several utilites, I still cannot seem to get the Kindle to get out of the current situation it is in.
The device was rooted with the 2nd bootloader added over 2 years ago. Every ROM I have ran has been successful. Every time a new ROM was used or tried a backup was done and the device wiped properly before install. I made sure that every ROM was for my specific device (Tate).
Here is what I can do:
If I power on the Kindle, it briefly shows the logo, then the fastboot logo and goes blank
If I power on the Kindle by plugging in the factory cable and quickly entering any command (it is already typed) like "fastboot erase cache" the system will remain in fastboot with the fastboot logo on the screen. My sdk does recognize the device and states it is in fastboot.
From here I have no idea where to go. I can type any command I like, such as erase cache, recovery, system or any multitude of things and the command prompt takes it time to show the device is working on the command. However, the device remains unresponsive and has the same issues when attempting to reboot. When flashing anything the target size of the device remains unchanged at 1006632960 bytes, which seems to tell me that device is receiving the command but not writing anything to the device. This probably also means that anything that is on the device causing it to continuously bootloop or fail is not being erased or properly formatted.
All I have is fastboot and time. Time to scratch my head and wonder if the device is truly and totally bricked. i am under the assumption that if I have a working fastboot that I should be able to at least accomplish something. Even if it means reverting it to bare bones stock and starting the whole process over. I will be happy to answer any questions you all have regarding the system via here or PM.
Please assist this old man and thank you in advance for your time.
Give it a try
While I wasn't in the same weird brick scenario as you. My device would show up on my pc as fastboot and or regular adb. But, I would get no video. The solution which I have no idea why worked was to pop the back cover off. Then disconnect the battery from the mobo. Wait a few seconds. Connect it back to the mobo. After that video showed back up. Then proceeded on my way.
Not sure if what I did will help you. But. Then again I didn't think simply disconnecting the battery and reconnecting it would solve video issues.
You definitely do have a weird brick scenario. Good Luck!

Stuck in fastboot with bootloop (Pixel 4a 5g)

As the title states, my phone is stuck in a bootloop, and only fastboot works. Trying to go into recovery or rescue mode results in going back to the bootloop instead of actually going to rescue/recovery mode. Any fastboot commands result in `waiting for device` even though it shows the device in `fastboot devices`.
Is there anything I can do to try to get it to work again?
I have gotten it into recovery mode before and was able to factory reset it, however when I plugged it in the phone crashed and went back into a bootloop, and now loading into recovery mode does not work.
Also if it's any help, I previously had the device rooted with magisk, I powered it off and when I powered it back on it went into a bootloop (I did not make any changes like installing/updating magisk plugins prior to shutting it down).
Update to this: I was able to install graphene os via command line.

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