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
Related
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.
stuff you need to download to root your vivo v9/v9+
SuperSu
ADB Drivers
TWRP Recovery
1. First of all, keep it in mind that the rooting process requires the installed custom TWP Recovery on your device.
2. When it comes to enabling USB debugging, you need to visit Settings -> About Phone -> Tap on Build number till to see the message on display screen like “You are now a developer.”
3. You can now have the developer option, so visit Settings -> Developer options -> Enable USB debugging and make sure to enable OEM to unlock.
4. It is necessary to download TWRP recovery image for a device
5. Now, the user can connect the device to PC using the USB cable. Make sure to check that the PC has all Vivo V9 USB driver gets installed. You can now create a folder and name it as Fastboot and copy to the TWRP Recovery img in Fastboot folder.
6. You can now press the Right keys click + left shift to open the command prompt window and choose the Open command window here.
7. By following the given below command, you can now boot the device Vivo V9 into the fastboot mode.
fastboot reboot bootloader
Mac: ./fastboot devices
Windows: fastboot devices
8. The user can now check the connected device list by entering the command below.
fastboot devices
Mac: ./fastboot devices
Windows: fastboot devices
9. To flash TWRP recovery follows the command below
Fastboot Flash TWRP recovery.img.
Mac: ./fastboot devices
Windows: fastboot devices
10. Finally, thus the TWRP recovery is successfully installed on your device.
11. To reboot your device make sure to follow the command Fastboot Reboot
For more information go to https://techcyder.com/
How To Root Vivo V9 from TWRP [STEPS]
1. It is necessary for the users to download rooting package in Vivo V9
2. You can now place the root zip on the SD card
3. Make sure your device to boot it into TWRP recovery mode
4. Hold the keys Power + Volume down to boot in custom recovery mode
5. Once if you entered TWRP recovery mode, you could release the keys
6. Get set to click on Backup and complete the backup process of a current OS. It will help during the flashing process in case if anything goes wrong.
7. The user can click on the option “Install” and get SuperSU zip file.
8. You need to swipe the button to confirm the process of installation.
9. Finally, the rooting process is done successfully, and you can tap reboot system.
9. Thus the rooting is done on your device with the help of SuperSU.
Conclusion: Root Vivo V9 and Install TWRP Recovery
So, the Vivo V9 users who all are looking forward to customizing their device for many exciting features to experience can check out the above process. It is necessary for the users to follow all the steps without skipping it.
To know how to root Vivo V9, check Androidtek.com. You will find Root Vivo V9 and install TWRP recovery article there.
What? People use sites other than XDA?
Is it work on Vivo V9 with Snapdragon 450? Because here in Indonesia, Vivo use Snapdragon 450
ferlie said:
Is it work on Vivo V9 with Snapdragon 450? Because here in Indonesia, Vivo use Snapdragon 450
Click to expand...
Click to collapse
Yes this method will work for your device
how?
hi, how can I root vivo v9 without losing updates from o.t a? Im afraid i might lost updates
Kenfabz said:
hi, how can I root vivo v9 without losing updates from o.t a? Im afraid i might lost updates
Click to expand...
Click to collapse
U need to install red wolf twrp recovery so that you can still get ota updates
Thanks for sharing us......
no root, no twrp download, any ideas?
Hi!
kingoroot not worket for this phone
Download TWRP Recovery for Vivo V9 (Link added soon) in url http://androidtek.com/how-to-root-vivo-v9-and-install-twrp-recovery/
How download twrp for this phone?
OEM_Unlock enable , developer mode enable , USB debugging enable.
adb reboot bootloader ENTER
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:MTP eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
fastboot flashing unlock ENTER
FAILED (remote: unknown command or device is lock)
finished. total time: 0.009s
download this adb
https://forum.xda-developers.com/general/rooting-roms/how-to-unlock-bootloader-vivo-phones-t3686690
fastboot bbk vivo_bsp unlock_vivo
FAILED (remote: unknown command or device is lock)
finished. total time: 0.012s
princebhat115 said:
U need to install red wolf twrp recovery so that you can still get ota updates
Click to expand...
Click to collapse
Do you have link to red wolf twrp version for vivo v9?
zeroonea said:
Do you have link to red wolf twrp version for vivo v9?
Click to expand...
Click to collapse
I believe it doesn't even exists. Vivo V9 have already dead development. Like LG G6.
latest kingroot not work for me
It stuck at 1%
method2 not success.
problem with command Fastboot flash recovery.img
It's say (remote: unknown command or device is lock)
i have adb driver installed. OEM_Unlock enable , developer mode enable , USB debugging enable.
phooza said:
latest kingroot not work for me
It stuck at 1%
method2 not success.
problem with command Fastboot flash recovery.img
It's say (remote: unknown command or device is lock)
i have adb driver installed. OEM_Unlock enable , developer mode enable , USB debugging enable.
Click to expand...
Click to collapse
The correct command is "fastboot flash recovery recovery.img"
Will this work with the Y71?
Hi there,
I am very new to this topic and have never worked with Adroid before, so please bare with me
Will this process work for the new Vivo Y71? (released in China 1 month ago)
I bought it in Shenzhen a few weeks back and went into a shop in Honk-Kong to have them install Google Play Store. Now, I don't know whether they already rooted the device to install Google Play. How can I see if the device is already rooted?
I have the problem, that some of the system prompts (like, error messages) are still in Chinese. The rest of the OS is in English. I would like to eventually install a ROM with support for German or at least full English support.
I know, lots of questions. Sorry if they're stupid!
best
But there is no custom recovery for Vivo V9 yet. Correct me if I am wrong.
edeoldi said:
Hi there,
I am very new to this topic and have never worked with Adroid before, so please bare with me
Will this process work for the new Vivo Y71? (released in China 1 month ago)
I bought it in Shenzhen a few weeks back and went into a shop in Honk-Kong to have them install Google Play Store. Now, I don't know whether they already rooted the device to install Google Play. How can I see if the device is already rooted?
I have the problem, that some of the system prompts (like, error messages) are still in Chinese. The rest of the OS is in English. I would like to eventually install a ROM with support for German or at least full English support.
I know, lots of questions. Sorry if they're stupid!
best
Click to expand...
Click to collapse
Kingroot is not working with my fone
invincible authority said:
The correct command is "fastboot flash recovery recovery.img"
Click to expand...
Click to collapse
thank you but I use correct command
fastboot flash recovery recovery.img
not work. It's still "unknown command or devices is lock"
may be i think stock rom v9 is lock for install twrp fastboot mode
akalifa said:
Hi!
kingoroot not worket for this phone
Download TWRP Recovery for Vivo V9 (Link added soon) in url http://androidtek.com/how-to-root-vivo-v9-and-install-twrp-recovery/
How download twrp for this phone?
OEM_Unlock enable , developer mode enable , USB debugging enable.
adb reboot bootloader ENTER
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:MTP eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
fastboot flashing unlock ENTER
FAILED (remote: unknown command or device is lock)
finished. total time: 0.009s
download this adb
https://forum.xda-developers.com/general/rooting-roms/how-to-unlock-bootloader-vivo-phones-t3686690
fastboot bbk vivo_bsp unlock_vivo
FAILED (remote: unknown command or device is lock)
finished. total time: 0.012s
Click to expand...
Click to collapse
U need to unlock ur device first
U need to unlock your device first
princebhat115 said:
U need to unlock your device first
Click to expand...
Click to collapse
How?
a bit similer with this case
my friend bought it 20 days ago and he unlock it
but he cant flash twrp as like guides
he had no expirience before this
so i get tablet and tried to solve the problem but
fastboot doesnt work properly
fastboot devices/reboot/device-info works
but
fastboot flash recovery twrp.img/ flash boot boot.img(guide on carbon rom)/boot twrp.img/and etc that for flashing or change any system
does not work
massage like failed(long link/bigger than max allowed)
changing everytime i try
i though there might some issues when my friend unlock the bootloader
so i 'fastboot oem lock' and try to unlock again
but from then fastboot not work properly
can be boot or 'adb reboot fastboot' to fastboot
but it become unknown device on windows device manager
fastboot command not work
when mi flash try to detect device, fastboot mode end and 'press any key to power off' screen came out
some times it working for few seconds so i try unlock with official xiaomi tool but tool said 'already unlocked'
right after i locked bootloader i used 'fastboot oem device-info' and checked bootloader is locked
i can switch oem unlock on/off in developer option but it doesnt change anything
i searched as i can and edl mode looks last
but few things to consider
1. its official chinese rom and working now
2. i dont know broken fastboot can be restored with flashing rom with edl (i flash rom with update app in settings but not solved)
3. adb reboot edl doesnt work it just rebooted(should teardown it but i dont know what pin to short)
the reason why i trying to install custom rom(or eu rom) is my friend and i not live in native english country
hope i get some help
thx
Ryzen CPU?
thE_29 said:
Ryzen CPU?
Click to expand...
Click to collapse
ryzen 1, 2, intel sandy etc
tried all i got
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
KrakmanCz said:
Im almost sure flashing stock rom with MiFlashTool should solve this problem as it does flash partritions as recovery and fastboot too. Have you tried this one?
Click to expand...
Click to collapse
nope
cant go into edl mode until i teardown it
miflash 2018 doesnt connect with pad on fastboot mode
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
chocodesk said:
ryzen 1, 2, intel sandy etc
tried all i got
Click to expand...
Click to collapse
Ok, when you also tried Intel.. But Ryzen CPUs have major problems with the flash tool and the tablet. Would not do anything on Ryzen PCs.
KrakmanCz said:
miflash should connect to mi devices when in fastboot mode. I would consider checking drivers for the device, try to install MiSuite, it should install all drivers needed for those actions. Also, in the fastboot mode you are trying some commands, are you using Windows 10 Powershell or basic cmd?
Click to expand...
Click to collapse
on basic
with was detected as fastboot before
but know its unknown on device manager
update driver doesnt work
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Dannyboy3210 said:
Try using a usb 2.0 port? If you ever need to, hard reset is holding all buttons at once for 30 seconds.
Click to expand...
Click to collapse
i tried 2.0 and 3.0
not work
tablet owner decide to use it on stock chinese rom
not in my hand now
$ adb reboot bootloader
List devices on fastboot :
$ fastboot devices
XXXXXX fastboot
Check if bootloader is unlocked :
$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.003s
Flash TWRP recovery :
$ fastboot flash recovery recovery.img
Sending 'recovery' (54400 KB) OKAY [ 1.540s]
Writing 'recovery' OKAY [ 0.410s]
Finished. Total time: 1.952s
Reboot your device
$ fastboot reboot
Rebooting
Finished. Total time: 0.000s
I installed TWRP on MIUI 10 using this description. On the end , after TWRP installed - I rebooted again to TWRP and installed stock rom at once . I not tested , but theory says , MIUI will reflash recovery if it will be booted in this situation .
Sorry to piggy-back off this post, but I'm having a similar issue with my Mi Pad I just received:
I can boot it into Fastboot mode no problem, even see it listed when I use the "Fastboot devices" command. When I run the OEM info everything comes back true for unlocked.
However, when I try to flash anything I get the max size error or just a "FAILED" and it kicks the Mi Pad to a black screen with the white text "Press any key to shut down".
Any ideas?
*edit*
I've continued testing, and I'm really at a loss here. See the response I'm getting using fastboot:
\minimal_adb_fastboot_1.4.3_portable>fastboot flash boot kernel.img
target didn't report max-download-size
sending 'boot' (15060 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I can transfer files in windows no problem... I can use adb commands no problem... fastboot just doesnt seem to work.
I figured out my issue. You cannot use USB 3 ports to connect and run fastboot commands. I bought a cheap USB 2 hub, ran the cable from that and had no problems at all.
I have a weird condition. First of all I was using Android 9 with twrp. Everything was fine. Today I decided to install Lineage 17.1 and first of all I needed the A10 stock rom. So I decided to use Official Fastboot rom. Installed and booted. I turn the dev options on.
Used Adb reboot fastboot to get into fastboot mode. Used the commands that I used to use.
fastboot getvar current-slot (it says A)
fastboot set_active b
fastboot erase boot
fastboot flash boot twrp.img (everything was fine. no errors so far.)
fastboot reboot recovery (I press vol+ button)
Phone boots to fastboot mode. when I try fastboot continue it changes slots and boot OS. I tried to flash twrp or orange fox or different versions of recovery to both slot but nothing works. I always end up with fastboot screen.
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.016s]
It seems OK?
I cannot install A9 it gives error (rollback protection maybe?)
How can I flash recovery now? Please help.
Edit: I will try to gain root access patching boot.img with magisk. Maybe somehow I gain access to recovery again. -> Got root access but no recovery
Solved. Tried thousands of recoveries and one worked.
Hello.
I requested help on wrong forum, first person that responded redirected me here.
Here's the copy-pasted contents of that post.
I have a Motorola. I typically leave my cellphone attached to my computer with USB so it can charge, slowly but surely.
When I wanted to get on my way I noticed my phone wouldn't start which I found interesting.
I left it on a charger for some time and when I held the power button to power up, I noticed it got stuck at boot.
What it typically does is open boot screen with Motorola logo, vibrate, start an animation and after mid-boot say "halo Moto" and then leave me at home screen.
But this time, it just get stuck on a boot screen. It shows the boot screen with Motorola logo, vibrates and then does nothing (until battery dies, I left it for an hour?)
I pressed the volume down and power button to enable debugging.
I get a "FastBoot AP Flash Mode" menu.
The options are:
Start (which puts me back into stuck boot)
Restart Bootloader (which restarts the FastBoot)
Recovery Mode (which gives me this: "No Command" with an Android icon, does nothing more]
Power Off (which powers off the phone)
Bootloader Logs (which changes some text to: "Fastboot Reason: Reboot mode set to FastBoot" or "Volume button down")
Switch Tools Mode (which toggles text between Tools Mode Config: DISABLED and ENABLED, no idea of other effects)
BARCODES (which probably shows scannable code so that professionals needn't type the ID)
I wanted to send it back to the seller, but they claim that they take no responsibility for loss of information, all my data is stuck on 128GB on the internal memory.
I would like to go to service for data recovery, but I due to COVID-19 everything's closed.
What could I potentially do to restore my phone? And if I can't, I can send it back, but how do I backup my data?
It's Motorola One Zoom.
Click to expand...
Click to collapse
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
ilia3367 said:
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
Click to expand...
Click to collapse
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
yeetusAAA said:
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
Click to expand...
Click to collapse
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The situation changed slightly since I came back from work.
Previously device appeared as unknown device.
With name "fastboot parker S", I have it in search history.
After rebooting (and installing 50 drivers) my device appears as "Motorola ADB Interface", however execution of commands don't end successfully.
Code:
X:\Applications\MinimalADBFB>fastboot -help
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw <bootable-partition> <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader|emergency] Reboot device [into bootloader or emergency mode].
reboot-bootloader Reboot device into bootloader.
oem <parameter1> ... <parameterN> Executes oem specific command.
stage <infile> Sends contents of <infile> to stage for
the next command. Supported only on
Android Things devices.
get_staged <outfile> Receives data to <outfile> staged by the
last command. Supported only on Android
Things devices.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the
form <protocol>:<hostname>[:port] where
<protocol> is either tcp or udp.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all slots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--skip-reboot Will not reboot the device when
performing commands that normally
trigger a reboot.
--disable-verity Set the disable-verity flag in the
the vbmeta image being flashed.
--disable-verification Set the disable-verification flag in the vbmeta image being flashed.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
X:\Applications\MinimalADBFB>fastboot -getvar current-slot
fastboot: unknown option -- g
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot reboot bootloader
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.016s
X:\Applications\MinimalADBFB>
About all those "remote" failures, the commands do appear in "Bootloader Logs", and the text is something like:
"cmd: getvar:slot-count" and "cmd: set_active:a". As someone with Android unrelated programming background I see nothing that would indicate an error on the phone.
Manually rebooting to fastboot doesn't change anything, rebooting the device in general doesn't solve the issue.
After rebooting I redid my steps:
Code:
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.004s
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (status read failed (Too many links))
finished. total time: 0.005s
X:\Applications\MinimalADBFB>
Too many links? Corrupted file system?
Try to update the adb & fastboot drivers.
Phone is downloading into Recovery?
Ejects from the attached archive adb folder to the root of the C:\ drive.
I didn't have a problem with these drivers.
ilia3367 said:
Try to update the adb & fastboot drivers.
Click to expand...
Click to collapse
How? There doesn't seem to be official link to fastboot, every next website I visited has different edition. Half of links are dead, others have viruses. Even manufacturers of phones seem to have different drivers.
Phone is downloading into Recovery?
Click to expand...
Click to collapse
No, the phone is stuck at boot. It doesn't automatically fallback into Recovery, nothing changed since last time I entered "Recovery Mode".
Ejects from the attached archive adb folder to the root of the C:\ drive.
Click to expand...
Click to collapse
I placed the files in plain C:\, executing your commands invoked following response:
Code:
C:\>fastboot getvar current-slot
< waiting for any device >
current-slot: a
Finished. Total time: 0.001s
C:\>fastboot --set-active=a
fastboot: error: Device does not support slots
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
ilia3367 said:
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
Click to expand...
Click to collapse
Device Manager calls my phone "Motorola ADB Interface".
fastboot devices says:
Code:
C:\>fastboot devices
ZY226KZGT5 fastboot
"Your phone is in the correct boot Slot A, where you should install the firmware."
Is there a way to recover data first?
"Is the bootloader locked?"
I have no idea.
Screen mentions:
"oem_locked"
"AP Fastboot Flash Mode (Secure)"
Code:
C:\>fastboot flashing get_unlock_ability
(bootloader) use "oem get_unlock_data" and web portal
(bootloader) http://motorola.com/unlockbootloader
OKAY [ 0.005s]
Finished. Total time: 0.008s
"Is there a way to recover data first?" - Are you sure there's something left? Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
ilia3367 said:
"Is there a way to recover data first?" - Are you sure there's something left?
Click to expand...
Click to collapse
I had 120GB of data on it, before it crapped out on me.
Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
Click to expand...
Click to collapse
Which file? Tehre's no bat file in the zip you provided.
yeetusAAA said:
I had 120GB of data on it, before it crapped out on me.
Which file? Tehre's no bat file in the zip you provided.
Click to expand...
Click to collapse
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
yeetusAAA said:
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Code:
C:\>fastboot getvar all
getvar:all FAILED (Status read failed (Too many links))
Finished. Total time: 0.005s
yeetusAAA said:
What does getvar all say?
Click to expand...
Click to collapse
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
sd_shadow said:
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I see. Thanks.
bricked phone
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
death1426 said:
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
Click to expand...
Click to collapse
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
does not show up in device manager
sd_shadow said:
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
no unfortunately it does not already tried placing it in edl mode with a cable but no to avail also installed Qualcomm drivers just to be sure uncertain what i can do at this point