I am running a year old Moto E 1st Gen dual SIM (Indian version). Recently I installed CyanogenMod condor 12.1 nightly build (was running from June 18th). Today I tried to update it using CyanDelta. When I picked up my phone to wake it upI found it would not wake up. Since then it will not boot. It boots up to the Warning screen for unlocked bootloader and does nothing.
When I hold the power and volume button down to get the Fastboot mode screen, it refuses to enter TWRP recovery - it just gets stuck at the TeamWin splash screen.
I am using Linux. I ran fastboot -w . It claims to have wiped the cache and userdata. Then I could no longer reboot from the Fastboot mode menu - it started saying "Boot not validated." Recovery also produced the message "recovery not validated."
I tried to flash TWRP again with fastboot flash recovery <twrp image>. I got this error message at the console:
target reported max download size of 299892736 bytes
sending 'recovery' (7300 KB)...
OKAY [ 0.291s]
writing 'recovery'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 5.340s
The phone also displayed the "Mismatched partition size" recovery. The situation is the same - hangs at TeamWin splash screen, refuses to boot.
What do I do now?
I could try to flash the stock firmware again, but I use Linux, and I can't find the mfastboot tool for Linux anywhere (Motorola has yet to send me an invite for their developer software and all the external sites only have the Windows tool). I suspect that won't work either when I'm not able to flash a recovery.
Related
I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
rupeshchan said:
I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
Click to expand...
Click to collapse
this is moto e1 section in forum this is not for moto e2..and you have to unlock bootloader if u want root or install custom rom..this is not mtk devices in mtk devcies this kingroot works ..u cant root or install using kingroot ...just ask in moto e2 section:silly::silly:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
-z3r0- said:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
Click to expand...
Click to collapse
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
One question dude, were you on marshmallow before trying kingroot?
Yes bro!!
rupeshchan said:
Yes bro!!
Click to expand...
Click to collapse
Okay then flash Systemless SuperSu to root.
Will you explain "how to" step by step? If possible?? Or share the link, please
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
-z3r0- said:
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
Thanks a lot. :fingers-crossed:
help me
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
same problem happened to me
model is moto e xt-1521
i am not able to go dev settings
jhn
OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Try to create a Thread in the One Plus X Section .
OnePlus X (Onyx) - Soft bricked
Boots into Fastboot mode, gets detected by PC.
No OS, No Recovery.
Problem: Recovery gets flashed successfully using adb and fastboot. But when trying to boot into recovery using commands, it says FAILED (remote:dtb not found); and when trying to boot into recovery using physical buttons, then it just stays on the OnePlus boot logo till eternity.
I tried using a flash tool as well(got from XDA), but the result is same.
Here is a look from cmd:
C:\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
C:\platform-tools>fastboot flash recovery twrp-3.0.2-0-onyx.img
target reported max download size of 536870912 bytes
sending 'recovery' (14758 KB)...
OKAY [ 0.466s]
writing 'recovery'...
OKAY [ 0.260s]
finished. total time: 0.728s
C:\platform-tools>fastboot boot twrp-3.0.2-0-onyx.img
downloading 'boot.img'...
OKAY [ 0.465s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.505s
I tried flashing twrp 2.8.7.0(onyx) but still I got the same error. (remote:dtb not found). No matter what, but it just won't boot into recovery.
How it happened:
Long back, I unlocked my bootloader, installed twrp recovery and also achieved root access. Then I flashed CM13. It was working quite fine. But then OOS 3(Official) came out for OnePlus X, so I decided to download it and flash it too. It was working all fine. But then I realised that I lost my root access and my recovery was changed back to stock OnePlus recovery. After that I tried for 2 days to flash twrp back, but I continued to get that (remote:dtb not found) error. It was quite desperate; then I thought to lock the bootloader back and unlocking it back again. But the moment I used the command "fastboot oem unlock", my phone didn't ask me for a yes or no, so I tried restarting it. But it was too late, my phone got soft-bricked till then. I am trying to fix this since days, PLEASE SOMEONE HELP!!
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
JonSchnee777 said:
Hey guys,
I have an European LG G5 H850 with an unlocked bootloader. It is my first time rooting, and after unlocking the bootloader, I wanted to boot TWRP once, but I didn't want to install it, but instead keep the stock recovery untouched. So I booted into the bootloader, entered "fastboot boot twrp.img" and I got this message:
downloading 'boot.img'...
OKAY [ 0.462s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.482s
I have absolutely no idea what I'm doing wrong. I made sure twrp.img is referring to the correct file, and I tried both the Android SDK platform tools and the 15 seconds ADB installer, but none of them worked. When I try flashing the recovery with "fastboot flash recovery twrp.img", it seems to work because this appears:
target reported max download size of 536870912 bytes
sending 'recovery' (20900 KB)...
OKAY [ 0.471s]
writing 'recovery'...
OKAY [ 0.198s]
finished. total time: 0.670s
But when I try to boot into the bootloader again, it just gives me the option to do a factory reset, nothing else. So I assume that something went wrong. I have absolutely no idea what it could be, so please help me. I also asked on reddit, but didn't get any answers so far. Any help would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
The "fastboot boot twrp.img" command didn't work for me either, but the keystroke to do a "factory reset" -- which is really a keystroke to enter recovery -- did work. Specifically, I
powered down the LG G5 completely (nothing attached to the USB-C port, or battery pull)
with the power off (preferably via battery pulled), held down the Volume Down and Power/Fingerprint buttons
As soon as the LG logo appeared, released and re-pressed the Power/Fingerprint button, all the while continuing to hold down Volume Down
Held down both while the LG logo showed, releasing them after the white screen appeared asking whether you want to do a full erase. Answer yes (Press and release Volume Down until the Yes is grey, then press Power/Fingerprint button)
It prompts you once again. Answer yes again the same way.
At this point after a few seconds, TWRP starts. It hasn't actually done an erase.
This is important: after fastboot flash recovery twrp.img, you need to pull the battery to power down, and then follow the instructions above to enter TWRP. Do not boot into system with the stock ROM after fastboot. It will replace TWRP with the stock recovery at boot time, and in that scenario, the full erase mentioned above actually does erase data and internal storage.
TWRP will on first start change the system image (once you "allow modification") so that the stock ROM stops replacing it at boot time.
If you did boot up the stock ROM after fastboot, you will need to re-enter fastboot and flash TWRP again (power down with USB-C port clear, hold down Volume Up, insert USB-C cable, fastboot flash recovery twrp.img). Then pull the battery with fastboot still running, then boot into TWRP as above.
Unfortunately most writeups aren't crystal clear about the correct sequence of steps. Most cover some steps and gloss over others.
You aren't doing anything wrong.
LG did not put the typical Fastboot commands into the bootloader.
Fastboot flash does not work either.
You need to follow the other methods available on xda to get TWRP on your device.
Edit: woops. That's only with H830. Follow the instructions in the H850 TWRP thread.
Sent from my LG-H830 using Tapatalk
Hello, I'm having a problem to install CrDroid ROM on my phone. I unlocked bootloader also the "critical" option.
I started trying to install OrangeFox but I had some weird problem, when booting from it I had random generated characters (like they were encrypted) on the "sdcard" path. So I couldn't do anything from it.
Somehow I think I messed up my "a" and "b" boot slot though.
My default active slot from the factory was "b" so I tried all that with "a" slot but had no luck.
I managed to get TWRP installed on slot "b" which boots into TWRP recovery if I press volume+ and power, and if not the phone boots to the normal android one factory ROM.
I then gone through TWRP and installed CrDroid Rom through the zip (crDroidAndroid-10.0-20200413-laurel_sprout-v6.5) and after the successful installation of the zip the phone reboots.
And slot "a" gets activated and it just shows fastboot mode.
So anyway the thing is on slot "a" the phone does nothing even with volume+ and power it just goes into fastboot mode.
If I activate slot "b" the phone works as I stated above.
I tried flashing TWRP while slot "a" is active but still won't go into recovery. Just shows fastboot
I also just realized that when booting to slot "b" on the factory rom Wifi is broken, it turns off immediately. MAC Address is changed to 02:00:00:00:00:00
I flashed persist.img through fastboot (fastboot flash persist persist.img ) and didn't fix it.
Also I can't make GSM Calls. "System UI Not Responding"
Any ideas?
Should reset the phone fully at stock, so both a/b slot will be factory stock, and start over? Is there anyway to do it?
Welp, I'm trying to install "laurel_sprout_global_images_V10.3.16.0.PFQMIXM_9.0" rom through miflash tool 2019.12.6.0 and it's been 50 mins on "flashing".
I made sure "current_slot" was "A" before starting.
Also changed the folder name of the rom to something simple.
And I selected "clean all and lock"
After I disconnected now both slots A and B are going into fastboot mode.
Then I tried to manually flash some .imgs through fastboot commands:
Fastboot flash boot boot.img
Fastboot flash recovery twrp.img
Fastboot flash system system.img
While i am on "active_slot a" it turned out instead of going to fastboot, it goes to the "android" "unlocked" screen and bootloops.
Volume+ and power gives "No command" with the dead android picture, so no twrp or any type of recovery.
Any ideas maybe?
Ok so after trying again with MiFlash tool I still get to endless flashing.
I saw that on the bottom of the log:
info2:Erasing 'system_a'...
:info1:"Flash system_a error"
:info2: OKAY [ 0.068s]
:info1:$pause
:info2:Sending sparse 'system_a' 1/4 (785408 KB)...
:info2: OKAY [ 18.979s]
:info2:Writing 'system_a' 1/4...
:info2: OKAY [ 0.001s]
:info2:Sending sparse 'system_a' 2/4 (785408 KB)...
:info2: OKAY [ 24.204s]
:info2:Writing 'system_a' 2/4...
:info2: OKAY [ -0.000s]
:info2:Sending sparse 'system_a' 3/4 (767916 KB)...
:info2:FAILED (data write failure (Unknown error))
:info2:Finished. Total time: 54.210s
Maybe it can help?
Okay so this messaged fixed the flashing time for me:
"you must put fastboot.exe adb.exe and AdbWinApi.dll AdbWinUsbApi.dll in folder with flash_all.bat .... and "flash system_a error" is gone "
I remember experiencing that when using usb 3.0