[Q] "Fastboot enabled" but Bricked and Milstone. any solution? - Motorola Droid and Milestone General

Hi everyone.
I got bricked but fastboot enabled milestone.
I can access "Bootloader(PRDCT enable)" and "Bootloader Fastboot Mode"
a. I can't flash SBF via RSD Lite.
RSD Lite error - Error sending RQSF boot command. Device API Error: 0xE00200EB Command:RQSF (0xE00200EB)
b. I can't access Recovery mode
I erase Recovery partition via fastboot and can't flash that partition with CG47.smg (http://and-developers.com/partitions:cdt)
What can I do?

Related

I thin its bricked

I have custom ROM 5.x.x pacman edition I think, I pressed factory reset or something like this from settings. It was having problem because I didnt have gaps. I flashed gaps, but after this the phone is stucked at bootloader. My phone is xt1068 but pc doesnt recognize it.
Now I think I have even bigger problem I was playing with the custom recovery and wiped all the data on sdcard folder. The PC recognize Titan Fastboot device or something like this. Is it possible to transfer to sd card new rom using other device, and then use the sd card on the Moto G?
Can you access twrp recovery?
I can access philz recovery.
Edit: mfastboot has access but it gives error when mfastboot update retail.zip, "Failed to load"... when mfastboot devices it says, ZX1D22D9T8 fastboot. Gives error when trying to flash twrp recovery too.
Edit 2: target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error after trying.
ffup57 said:
I can access philz recovery.
Edit: mfastboot has access but it gives error when mfastboot update retail.zip, "Failed to load"... when mfastboot devices it says, ZX1D22D9T8 fastboot. Gives error when trying to flash twrp recovery too.
Edit 2: target max-sparse-size: 256MB
error: cannot load 'twrp.img': No error after trying.
Click to expand...
Click to collapse
Then flash latest twrp and then ROM+gapps.
Dont wipe anything with fastboot.
You have to unzip the file and mfastboot every file inside.
It worked but after I rooted with kango root then ota update, the phone reboot into stock recovery and it says no command.
Fail don't use kingo.
To root just flash SuperSU.
Check the return to stock guide follow all steps.
Flash twrp then flash SuperSU.
Stick to the proven guides
Pd. I think stock recovery is always empty there is some kind of key combination to bring up the command

[solved] XT1039 Fastboot TWRP recovery boot up failed

Let me explain my situation; I have a rooted device with custom recovery TWRP-2.8.7.0-thea.img., upgraded to lolipop 5.2 some months ago and now I accidentally forgot my android lock pattern after quickly changing the pattern. And now I wanted to factory reset via fastboot, but it just went into normal powerup.
Recovery will not boot in fastboot mode. I get this error "boot up failed"/ I flashed recovery with fastboot
Fastboot commands that I used:
C:\Program Files (x86)\Minimal ADB and Fastboot/fastboot.exe flash recovery C:\a
ndroid/twrp-thea.img
I also tried: fastboot erase recovery and redo the command above but still fails with the same error "boot up failed"
Bootloader: 411A
Build version: Blur_Version.23.21.17.peregrine_reteu.reteuall.en.EU
Ardent Censer said:
Let me explain my situation; I have a rooted device with custom recovery TWRP-2.8.7.0-thea.img., upgraded to lolipop 5.2 some months ago and now I accidentally forgot my android lock pattern after quickly changing the pattern. And now I wanted to factory reset via fastboot, but it just went into normal powerup.
Recovery will not boot in fastboot mode. I get this error "boot up failed"/ I flashed recovery with fastboot
Fastboot commands that I used:
C:\Program Files (x86)\Minimal ADB and Fastboot/fastboot.exe flash recovery C:\a
ndroid/twrp-thea.img
I also tried: fastboot erase recovery and redo the command above but still fails with the same error "boot up failed"
Bootloader: 411A
Build version: Blur_Version.23.21.17.peregrine_reteu.reteuall.en.EU
Click to expand...
Click to collapse
You're flashing files for wrong device.
Here you can find correct files for it: http://forum.xda-developers.com/moto-g/4g-development
Yes, you're right, it was indeed the wrong version.
I needed this one: http://forum.xda-developers.com/mot...ection-somcom3xs-experimental-corner-t2996266
then i deleted /data/system/gesture.key then rebooted and I can use my phone again.
Problem solved

Help anyone? Fastboot command error

I have a rooted device then i updated my device via firmware finder without unrooting my device. But my recovery was on stock recovery and erecovery was twrp. After update installed device automatically been unrooted. Phone is unlocked frp is unlocked too but when i try to flash twrp on fastboot mode it wont flash (command error) even when i type "fastboot oem device-info" it will get same error.
Can someone know what exactly is the problem. I just want to flash twrp so that i can root my device again. Thanks in advance.
Have you activated USB debug in the device settings?
Yes.

Moto E5 Plus Error: Failed to load kernel! After ROM install

Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
rmercer said:
Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
Click to expand...
Click to collapse
Looks like the E5 forum handles E5+ too (their TWRP says for E5+) and I see your post there. I'm not familiar with your phone but did you try a factory reset? Another option might be to fastboot flash the boot.img from your model's firmware on lolinet - see here - which should restore your stock kernel. Either option will delete your personal data though but sometimes no other choice. See what they say over there & maybe post in the TWRP thread where OP looks to know his stuff.
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
rmercer said:
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
Click to expand...
Click to collapse
Make sure it's the correct official firmware version for your software channel &/or vendor. You need to unzip the firmware into a temp directory on a computer, then you'll see boot.img among many files, copy it into your fastboot folder, connect the phone (do a 'fastboot devices' to make sure it's working), then type 'fastboot flash boot boot.img' and when it's done reboot. Also try a factory reset first if you can.

Please help! I've bricked my Moto G6!

When I boot my phone, it says:
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from normal boot mode
I've tried wiping and flashing several roms on it through TWRP, but keep getting this error. What am I doing wrong? The bootloader is unlocked and the device is rooted, if that helps.
I followed the instructions here: https://forum.xda-developers.com/moto-g6/how-to/stock-firmware-moto-g6-t3792292
and the device is now booting. But it said it was encrypting the data which doesn't sound right, I don't want that.
Before you flashed the stock ROM again, was the device encrypted?

Categories

Resources